WO2020091662A1 - Mobility procedure - Google Patents

Mobility procedure Download PDF

Info

Publication number
WO2020091662A1
WO2020091662A1 PCT/SE2019/051063 SE2019051063W WO2020091662A1 WO 2020091662 A1 WO2020091662 A1 WO 2020091662A1 SE 2019051063 W SE2019051063 W SE 2019051063W WO 2020091662 A1 WO2020091662 A1 WO 2020091662A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility procedure
condition
message
wireless device
candidate target
Prior art date
Application number
PCT/SE2019/051063
Other languages
French (fr)
Inventor
Cecilia EKLÖF
Pradeepa Ramachandra
Icaro L. J. Da Silva
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020091662A1 publication Critical patent/WO2020091662A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports

Definitions

  • Examples of the present disclosure relate to determining if a mobility procedure is associated with a condition.
  • An RRC_CONNECTED UE in LTE (LTE may also be called EUTRA) can be configured by the network to perform measurements and, upon triggering measurement reports the network may send a handover command to the UE.
  • the handover command may in LTE e.g. be an RRCConnectionReconfiguration with a field called mobilityControllnfo and in NR, it e.g. may be an RRCRecon figuration with a reconfigurationWithSync field.
  • reconfigurations are actually prepared by the target cell upon a request from the source node (over X2 interface in case of EUTRA-EPC or Xn interface in case of EUTRA-5GC or NR) and takes into account the existing RRC configuration the UE has with source cell (which are provided in the inter-node request).
  • source node over X2 interface in case of EUTRA-EPC or Xn interface in case of EUTRA-5GC or NR
  • source cell which are provided in the inter-node request.
  • reconfiguration provided by target contains all information the UE needs to access the target cell, e.g., random access configuration, a new C-RNTI assigned by the target cell and security parameters enabling the UE to calculate new security keys associated to the target cell so the UE can send a handover complete message on SRB1 (encrypted and integrity protected) based on new security keys upon accessing the target cell.
  • Figure 1 summarizes the flow signalling between UE, source node and target node during a handover procedure.
  • measurement control and reports are exchanged between UE and source gNB.
  • the source gNB makes a handover (HO) decision.
  • source gNB sends a handover request to a target gNB.
  • target gNB performs admission control.
  • target gNB sends a HO request acknowledge to source gNB.
  • Uu handover trigger information is exchanged between UE and source gNB. The UE detaches from the old cell and synchronises to the new cell.
  • source gNB sends SN status transfer to target gNB, and delivers buffered and in transit user data to target gNB.
  • the source gNB may also forward user data to target gNB.
  • the target gNB buffers user data from source gNB.
  • the UE synchronises to the new cell (target gNB) and completed RRC HO procedure. User data may then be exchanged between UE and target gNB. User data may be forwarded from target gNB to User Plane Function(s).
  • target gNB sends a path switch request to AMF.
  • AMF and UPF(s) exchange path switch related 5G CN internal signalling and actual DL path switch is performed in UPF(s).
  • User data may then be exchanged between target gNB and UPF(s).
  • AMF returns a path switch request ack to the target gNB.
  • target gNB sends a UE context release to source gNB.
  • handover may be referred to as mobility in RRC_CONNECTED, e.g.:
  • Mobility in RRC_CONNECTED is Network-based as the network has best info regarding current situation such as load conditions, resources in different nodes, available frequencies, etc. Network can also take into account the situation of many UEs in the network, for a resource allocation perspective.
  • Network prepares a target cell before the UE accesses that cell.
  • Source provides UE with the RRC configuration to be used in the target cell, including SRB1 configuration to send HO complete.
  • UE is provided by target with a target C-RNTI i.e. target identifies UE from MSG.3 on MAC level for the HO complete message. Hence, there is no context fetching, unless a failure occurs.
  • target C-RNTI i.e. target identifies UE from MSG.3 on MAC level for the HO complete message.
  • network provides needed information on how to access the target e.g. RACH configuration, so the UE does not have to acquire SI prior to the handover.
  • CFRA Contention Free Radio Aceess
  • target identifies the UE from the preamble (MSG.1).
  • CFRA Contention Free Radio Aceess
  • HO Command RRCConnectionReconfiguration with mobilityControllnfo and RRCReconfiguration with a reconfigurationWithSync field
  • HO Command is normally sent when the radio conditions for the UE are already quite bad. That may lead to that the HO Command may not reach the UE in time if the message is segmented or there are retransmissions.
  • condition handover or“early handover command”.
  • RRC signaling for the handover to the UE earlier.
  • a condition could e.g.
  • the threshold Y used in a preceding measurement reporting event should then be chosen lower than the one in the handover execution condition. This allows the serving cell to prepare the handover upon reception of an early measurement report and to provide the RRCConnectionReconfiguration with mobilityControllnfo at a time when the radio link between the source cell and the UE is still stable. The execution of the handover is done at a later point in time (and threshold) which is considered optimal for the handover execution.
  • Figure 2 depicts an example with just a serving and a target cell.
  • the network should then have the freedom to issue conditional handover commands for several of those candidates.
  • the RRCConnectionReconfiguration for each of those candidates may differ e.g. in terms of the HO execution condition (RS to measure and threshold to exceed) as well as in terms of the RA preamble to be sent when a condition is met.
  • serving gNB may exchange user plane data with the UE.
  • the UE sends a measurement report with“low” threshold to serving gNB.
  • the serving gNB maks a HO decision based on this early report.
  • the serving gNB sends an early HO request to a target gNB.
  • the target gNB accepts the HO request and builds a RRC config.
  • the target gNB returns a HO ack including the RRC config to the serving gNB in step 3.
  • a conditional HO command with“high” threshold is sent to the UE.
  • measurements by the UE may fulfil the HO condition of the conditional HO command.
  • the UE thus triggers the pending conditional handover.
  • the UE performs synchronization and random access with the target gNB in step 5, and HO confirm is exchanged in step 6.
  • target gNB infoms serving gNB that HO is completed.
  • the target gNB may then exchange user plane data with the UE.
  • Some examples may rely on context fetching called where a condition is also provided to the UE and, upon the fulfillment of the condition the UE executes resume.
  • This may comprise a method executed by a UE in RRC connected mode, the method including: Receiving a message containing at least one condition from the network and monitoring the fulfillment of the provided condition;
  • serving gNB may exchange user plane data with the UE.
  • the UE sends a measurement report with“low” threshold to serving gNB.
  • the serving gNB maks a HO decision based on this early report.
  • the serving gNB sends an early HO request to a target gNB.
  • the target gNB accepts the HO request.
  • the target gNB returns a HO ack to the serving gNB in step 3.
  • a conditional HO command with “high” threshold is sent to the UE.
  • measurements by the UE may fulfil the HO condition of the conditional HO command.
  • the UE thus triggers the pending conditional handover.
  • the UE performs synchronization and random access with the target gNB in step 5, and in step 6 sends a RRCConnectionResumeRequest message to the target gNB.
  • the target gNB may then exchange user plane data with the UE
  • the baseline solution for configuration of handover assumes that the UE actions on handover execution are triggered by the reception of an RRC reconfiguration like message containing the HO Command. If we use NR RRC as an example, the UE performs a handover execution (called reconfiguration with sync in NR) upon the reception of an RRCReconfiguration message containing a reconfigurationWithSync field (which is part of CellGroupConfig IE). Then, all necessary actions for the handover execution are triggered upon the reception of the message.
  • NR RRC a handover execution upon the reception of an RRCReconfiguration message containing a reconfigurationWithSync field (which is part of CellGroupConfig IE).
  • the UE shall perform the following actions upon reception of the RRCReconfiguration ⁇ .
  • the UE reguire the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling reguest configuration, sounding RS configuration), if any, upon acguiring the SFN of that target SpCell;
  • the UE is only required to acquire broadcasted SIB 1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
  • the network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG).
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the MCG is configured as specified in TS 36.331 [10]
  • the network provides the configuration parameters for a cell group in the CellGroupConfig IE.
  • the UE performs the following actions based on a received CellGroupConfia IE:
  • the UE shall perform the following actions to execute a reconfiguration with sync.
  • the UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the
  • conditional handover is not supported in 3GPP specifications of Release 15.
  • information i.e. configuration, fields, lEs
  • the exact same configuration and fields for handovers e.g. exact same message and same configuration procedures
  • the reception of a message in one case leads to the execution, while in conditional handover the execution of actions is determined by conditions.
  • a method is proposed that comprises a solution for configuring conditional mobility and lists things in the configuration which are new compared to configuration of legacy handover.
  • One aspect of the present disclosure provides a method performed by a wireless device.
  • the method comprises determining, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and if the mobility procedure is not associated with a condition, carrying out the mobility procedure.
  • a further aspect of the present disclosure provides a method performed by a base station.
  • the method comprises sending a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
  • a still further aspect of the present disclosure provides a wireless device comprising a processor and a memory.
  • the memory contains instructions executable by the processor such that the wireless device is operable to determine, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and if the mobility procedure is not associated with a condition, carrying out the mobility procedure.
  • Another aspect of the present disclosure provides a base station comprising a processor and a memory.
  • the memory contains instructions executable by the processor such that the base station is operable to send a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
  • An additional aspect of the present disclosure provides a wireless device configured to determine, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and if the mobility procedure is not associated with a condition, carrying out the mobility procedure.
  • a further aspect of the present disclosure provides a base station configured to send a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
  • Figure 1 summarizes signalling between a UE, source node and target node during a handover procedure
  • Figure 2 summarizes signalling between a UE, serving node and target node during a conditional handover procedure
  • Figure 3 summarizes signalling between a UE, serving node and target node during a conditional RRC Resume procedure
  • Figure 4A is a flow chart of an example of a method performed by a wireless device
  • Figure 4B is a flow chart of an example of a method performed by a base station
  • Figure 5 shows an example of a wireless network in accordance with some embodiments
  • Figure 6 shows an example of a User Equipment (UE) in accordance with some embodiments
  • Figure 7 is a schematic block diagram illustrating a virtualization environment in accordance with some embodiments.
  • Figure 8 shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments
  • Figure 9 shows a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments
  • Figure 10 shows methods implemented in a communication system in accordance with some embodiments
  • FIG. 11 shows methods implemented in a communication system in accordance with some embodiments
  • Figure 12 shows methods implemented in a communication system in accordance with some embodiments
  • Figure 13 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • Figure 14 illustrates a schematic block diagram of virtualization apparatus in accordance with some embodiments.
  • Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • some examples comprise a mechanism for configuration of conditional mobility, so that the UE can recognize the configuration of conditional handover (or other mobility procedure), recognize the conditions, trigger the actions when the conditions are fulfilled and perform the intended actions when the conditions are fulfilled.
  • a method 400 shown in Figure 4A is a flow chart of an example of a method 400 performed by a wireless device.
  • the method 400 comprises, in step 402, determining, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition.
  • the message may be received by the wireless device, for example from or via a serving cell of the wireless device.
  • the method also comprises, in step 404, if the mobility procedure is not associated with a condition, carrying out the mobility procedure.
  • the mobility procedure may (if not associated with a condition) be carried out immediately, for example immediately following receipt of the message, or otherwise not in response to a condition associated with the mobility procedure (as there may be no such condition).
  • a wireless device may be aware of whether a message pertaining to a mobility procedure is associated with a condition or not, and hence may in some examples undertake actions according to whether the mobility procedure is associated with a condition or not. For example, if the mobility procedure is associated with the condition, the method may comprise carrying out the mobility procedure upon determining that the condition has been met. This may comprise in some examples monitoring at the wireless device one or more signals (e.g. reference signals) received at the wireless device, e.g. from one or more candidate target cells for the mobility procedure.
  • signals e.g. reference signals
  • determining whether the mobility procedure is associated with a condition comprises determining whether a flag or field in the message indicates that the mobility procedure is associated with the condition.
  • Determining whether the mobility procedure is associated with a condition may in some examples comprise determining whether the message includes one or more information elements associated with the condition.
  • the presence of one or more particular information elements may indicate that the mobility procedure is associated with a condition.
  • the one or more information elements may in some examples convey information relating to the mobility procedure or the condition.
  • the one or more information elements may identify the condition for the mobility procedure.
  • determining whether the mobility procedure is associated with a condition may comprise determining a type of the message. For example, if the message is one type of message (e.g. one type of RRC message), the mobility procedure may not be associated with a condition, whereas if the message is another type of message (e.g. another type of RRC message), the mobility procedure may be associated with a condition.
  • the message is one type of message (e.g. one type of RRC message)
  • the mobility procedure may be associated with a condition.
  • the message may configure a respective mobility procedure associated with each of one or more additional candidate target cells.
  • the message may for example include configuration information in respect of multiple target cells (the candidate cell and the additional candidate target cell(s)).
  • the message may in some examples contain a plurality of RRC Reconfiguration messages, each RRC Reconfiguration message configuring the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells. That is, for example, each RRC Reconfiguration message may contain configuration information for a respective target cell.
  • the mobility procedure may in some examples be associated with the condition and a candidate target cell, and the method may further comprise receiving the message, and receiving one or more additional messages, each additional message configuring a respective mobility procedure associated with each of one or more additional candidate target cells.
  • configuration information relating to each of a plurality of candidate target cells may be received in one or more messages, for example one message per candidate target cell.
  • the respective mobility procedure associated with each of the candidate target cell and the one or more additional candidate target cells is associated with the condition, or a respective additional condition.
  • the mobility procedure associated with the candidate target cells may all be associated with the same condition, may be associated with individual conditions, or groups of candidate target cells may be associated with a condition for that group.
  • the message identifies the condition.
  • the message may comprise an RRC Connection Reconfiguration message or a RRC Reconfiguration message.
  • the mobility procedure may comprise a handover to a target cell or a resume procedure (e.g. RRC Resume procedure) to a candidate target cell associated with the mobility procedure.
  • determining that the condition has been met comprises monitoring a parameter, such as for example the signal strength of one or more signals (e.g. reference signal(s)) received (e.g. at the wireless device) from one or more candidate target cells.
  • determining that the condition has been met comprises determining that the parameter exceeds a threshold.
  • the parameter may comprise a signal strength of at least one candidate target cell associated with the mobility procedure at the wireless device.
  • the condition may in some examples comprise whether a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold.
  • the method comprises configuring the conditional mobility procedure in response to a signal strength of a candidate target cell being greater than the signal strength of a serving cell of the wireless device by a second threshold, wherein the second threshold is lower than the first threshold.
  • the conditional mobility procedure may be set up when the lower threshold is met or exceeded, and triggered (e.g. to move the wireless device to a new cell) once the higher threshold has been met or exceeded.
  • determining that the condition has been met comprises determining that an A3 event has been triggered.
  • the method may then in some examples comprise triggering the A3 event when a signal strength of a candidate target cell is greater than a signal strength of a serving cell of the wireless device by a first threshold.
  • Figure 4B is a flow chart of an example of a method 420 performed by a base station.
  • the method 420 comprises, in step 422, sending a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
  • the wireless device may be able to identify whether the mobility procedure is associated with a condition or not, and may thus carry out actions accordingly.
  • the wireless device may carry out the method disclosed above.
  • a flag or field in the message indicates whether the mobility procedure is associated with the condition. Additionally or alternatively, the message may include one or more information elements associated with the condition if the mobility procedure is associated with the condition. The one or more information elements may identify the condition for the mobility procedure. In some examples, a type of the message indicates whether the mobility procedure is associated with the condition.
  • the mobility procedure is in some examples associated with the condition and a candidate target cell, and the message further configures, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
  • the message may for example contain a plurality of RRC Reconfiguration messages, each RRC Reconfiguration message configuring, for the wireless device, the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells.
  • the mobility procedure is associated with the condition and a candidate target cell
  • the method further comprises sending the message, and sending one or more additional messages, each additional message configuring, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
  • the respective mobility procedure associated with each of the candidate target cell and the one or more additional candidate target cells may be associated with the condition (e.g. the same condition).
  • the respective mobility procedure associated with each of the additional candidate target cells is associated with a respective additional condition (e.g. each mobility procedure is associated with individual conditions, or each of a plurality of conditions applies to a group of mobility procedures).
  • the method may comprise receiving configuration details associated with each mobility procedure from a respective cell associated with the mobility procedure, e.g. using an appropriate interface between base stations (eNBs, gNBs etc) or cells.
  • the message identifies the condition.
  • the message comprises an RRC Connection Reconfiguration message or a RRC Reconfiguration message.
  • the mobility procedure comprises a handover to a target cell or a resume procedure (e.g. RRC Resume procedure) to a candidate target cell associated with the mobility procedure.
  • the condition may in some examples comprise whether a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold.
  • the message may thus configure the wireless device to carry out the conditional mobility procedure in response to a signal strength of a candidate target cell being greater than the signal strength of a serving cell of the wireless device by a second threshold, wherein the second threshold is lower than the first threshold.
  • the base station is associated with a serving cell of the wireless device.
  • Some examples comprise a method for configuring the user equipment, UE (or wireless device, which may be used herein in place of UE) with conditional handover.
  • the configuration may be done in an RRC message containing the handover (HO) Command (RRCConnectionReconfiguration with mobilityControllnfo and RRCReconfiguration with a reconfigurationWithSync field).
  • HO handover
  • RRCConnectionReconfiguration with mobilityControllnfo and RRCReconfiguration with a reconfigurationWithSync field the terms handover and reconfiguration with sync may be used interchangeably or have a similar meaning.
  • a conditional handover may also be called a conditional reconfiguration with sync.
  • At least some, or at least most, of the UE (and/or network) actions defined in some examples may be performed in NR or LTE.
  • the configuration of a conditional HO received in NR and executed in NR may be performed in NR or LTE.
  • the method is also application in the other following cases, at least: UE is configured with a condition HO in NR, then the condition is triggered and UE executes the HO in LTE;
  • UE is configured with a condition HO in LTE, then the condition is triggered and UE executes the HO in NR;
  • UE is configured with a condition HO in RAT-1 , then the condition is triggered and UE executes the HO in RAT-2.
  • a mobility procedure which may comprise the change of a cell (e.g. serving cell), e.g. for a wireless device or UE.
  • the method also comprises the case where a cell is added, for example in case of multi-connectivity scenarios such as carrier aggregation, dual connectivity, EN-DC, NR-DC, MR-DC, etc, where the addition may in some examples also be referred to as a mobility procedure.
  • the configuration of a conditional mobility procedure or HO as described in some examples may be described as a conditional configuration for SCG addition or SCell addition, or equivalent.
  • the UE may be able to distinguish conditional handover (e.g. HO is executed upon the triggering of a condition) from handover (e.g. HO is executed upon the reception of the message).
  • conditional handover e.g. HO is executed upon the triggering of a condition
  • handover e.g. HO is executed upon the reception of the message.
  • HO is used in place of mobility procedure, though herein the term HO can be used interchangeably with mobility procedure where appropriate.
  • the UE could distinguish handover from conditional handover in one or more different ways:
  • Solution a It could be indicated as a flag in the RRC message that the configuration is a conditional handover. That may be a flag or field in the same message used to indicate a handover. And, if that is present the UE does not execute the handover until the associated condition is triggered.
  • the message may be an RRCReconfiguration or an RRCConnectionReconfiguration.
  • Solution b/ A certain IE (information element) or a number of lEs indicate that it is a conditional handover if these lEs are present in the message.
  • That IE may be the configuration associated to the condition itself, which may comprise implicitly or explicitly: o Measurement threshold(s) associated to measurement quantities (e.g. for RSRP, RSRQ, SINR) for comparing the quality of at least an SpCell (e.g. PCell the UE is connected to) with the quality of at least one neighbour cell in a given frequency;
  • At least one pointer to at least one element or field provided in the measConfig to that UE may receive a measConfig with a list of measurement identifiers each defined by the triplet (measld, measObject, reportConfig). Then, upon using one of the identifiers in this field in CHO, the UE knows that the condition is associated to an already configured measurement identity.
  • Solution c/ A new RRC message can be defined for conditional handover, see details below.
  • That message comprises at least one condition associated to at least one RRCReconfiguration message, where each is possibly signaled as a bit string or using the message IE itself.
  • a single condition may be associated to multiple RRCReconfiguration like messages, where each message is only associated to a possible candidate cell.
  • each condition may have its own associated RRCReconfiguraiton message, each associated to a potential target cell. That may be seen as a signalling optimization as the size of the message may become critical in case the UE receives conditional configurations for a high number of potential target candidate cells.
  • the UE receives a set of RRCReconfiguration messages inside the RRCConditionalReconfiguration message and, consider these RRCReconfiguration messages (at least one) as stored. This is similar to what is done with the RRC Reconfiguration upon suspension. Then, when the condition is triggered the associated reconfiguration is restored. Another alternative is to say that the message is only applied upon the triggering of the condition. It also needs to be recognized in network (X2/S1/Xn/Sn) signaling that the HANDOVER REQUEST sent from source eNB to target eNB via X2/S1/Xn/Sn is applicable for a conditional handover. The recognition can be done in the same way as for the RRC message, e.g. a flag, certain IE(s) or a new message.
  • the message for configuration of conditional handover can be the existing RRC(Connection)Reconfiguration ( RRCConnectionReconfiguration in LTE and RRCReconfiguration in NR) or a new message. Some of these examples were shown above.
  • the structure of the message can be done in different ways.
  • the message contains information about the configuration in target eNB and, more specifically in the potential target cell. This information is in the baseline built as an RRC message in target gNB and sent to source eNB as a transparent container (e.g. a bit string) which is then forwarded to the UE.
  • the message can be structured in different ways.
  • the RRC message could be one message containing RRC messages from multiple eNBs in the form of a number of bit strings. If that is the case the RRC message sent to the UE is built in source eNB instead and source eNB includes the RRC messages from the different target eNBs as bit strings.
  • the source eNB may also include other information in the message, e.g. related to the conditions.
  • the target eNB may send information about the target configuration explicitly (i.e. not in the form of a bit string of a compiled RRC message) to source eNB, which builds the RRC message sent to the UE. This requires some updates to network signaling (X2/S1/Xn/Sn).
  • the current messages are HANDOVER REQUEST and HANDOVER REQUEST ACKNOWLEDGE and the HANDOVER REQUEST ACKNOWLEDGE could be updated to contain explicit information to source eNB about the target UE configuration, instead of the existing transparent container. Alternatively new messages could be defined.
  • the RRC message from each target eNB is forwarded to the UE one by one, i.e. the UE receives a number of RRC reconfiguration messages.
  • the conditions could be sent from each target respectively, or there could also be one reconfiguration message from source eNB containing the conditions.
  • the RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) including and security configuration.
  • Signalling radio bearer SRB1 or SRB3
  • OPTIONAL Cond FullConfig dedicatedNAS-MessageList SEQUENCE ( SIZE ( 1.. maxDRB ) ) OF DedicatedNAS-Message
  • nextHopChainingCount NextHopChainingCount
  • a possible implementation of Solution b/ described above (e.g. a field called condReconfiguration of IE CondReconfiguration including a trigger/execution configuration, like an A3/A5 event is used to enable the UE to identify this is a conditional handover and not a legacy handover) is the following, which shows an example of an ASN.1 code encoding the configuration message, the fields and lEs:
  • the RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and security configuration.
  • Signalling radio bearer SRB1 or SRB3
  • dedicatedNAS-MessageList SEQUENCE ( SIZE ( 1.. maxDRB ) ) OF DedicatedNAS-Message
  • condReconfiguration CondReconfiguration OPTIONAL masterCe11Group OCTET (CONTAINING CellGroupConfig ) OPTIONAL, — Need M
  • nextHopChainingCount NextHopChainingCount
  • the IE ReportConfigNR specifies criteria for triggering of an NR measurement reporting event. Measurement reporting events are based on cell measurement results, which can either be derived based on SS/PBCH block or CSI-RS. These events are labelled AN with N equal to 1 , 2 and so on.
  • Event A1 Serving becomes better than absolute threshold
  • Event A2 Serving becomes worse than absolute threshold
  • Event A3 Neighbour becomes amount of offset better than PCell/PSCell
  • Event A4 Neighbour becomes better than absolute threshold
  • Neighbour/SCell becomes better than another absolute threshold2.
  • Event A6 Neighbour becomes amount of offset better than SCell.
  • Periodical PeriodicalReportConfig eventTriggered EventTriggerConfig, reportCGI ReportCGI
  • EventTriggerConfig : : SEQUENCE ⁇
  • eventA4 SEQUENCE ⁇ a4-Threshold MeasTriggerQuantity
  • PeriodicalReportConfig : : SEQUENCE ⁇
  • NR-RS-Type :: ENUMERATED ⁇ ssb, csi-rs ⁇
  • MeasTriggerQuantity : : CHOICE ⁇
  • Solution d shows an example of the ASN.1 code and field description of this new message (including the ReportConfigNR lEs, where the execution conditions are configured):
  • the RRCConditionalReconfiguration message is the command to modify an RRC connection upon the triggering of an associated condition. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and security configuration.
  • Signalling radio bearer SRB1 or SRB3
  • RRCConditionalReconfiguration-IEs SEQUENCE ⁇ condReconfigurationList SEQUENCE (SIZE ( 1.. maxCondReconfigurations ) ) OF
  • dedicatedNAS-MessageList SEQUENCE ( SIZE ( 1.. maxDRB ) ) OF DedicatedNAS-Message
  • nextHopChainingCount NextHopChainingCount
  • the IE ReportConfigNR specifies criteria for triggering of an NR measurement reporting event. Measurement reporting events are based on cell measurement results, which can either be derived based on SS/PBCH block or CSI-RS. These events are labelled AN with N equal to 1 , 2 and so on.
  • Event A1 Serving becomes better than absolute threshold
  • Event A2 Serving becomes worse than absolute threshold
  • Event A3 Neighbour becomes amount of offset better than PCell/PSCell
  • Event A4 Neighbour becomes better than absolute threshold
  • Event A5 PCell/PSCell becomes worse than absolute thresholdl AND Neighbour/SCell becomes better than another absolute threshold2.
  • Event A6 Neighbour becomes amount of offset better than SCell.
  • EventTriggered EventTriggerConfig reportCGI ReportCGI
  • EventTriggerConfig : : SEQUENCE ⁇
  • PeriodicalReportConfig : : SEQUENCE ⁇
  • NR-RS-Type :: ENUMERATED ⁇ ssb, csi-rs ⁇
  • MeasTriggerQuantity : : CHOICE ⁇
  • the actions related to handover are in some examples triggered upon the reception of the RRC message containing HO (or mobility procedure) Command (e.g. RRCRecon figuration in NR or RRCConnectionReconfiguration in LTE).
  • RRCRecon figuration in NR or RRCConnectionReconfiguration in LTE.
  • the RRC message triggers the action to monitor if the conditions are fulfilled instead, and no handover is performed when the message is received.
  • the actions related to handover currently defined in 3GPP TS 36.331 in relation to“Reception of RRC(Connection)Reconfiguration” need to be expanded to“Reception of RRC(Connection) Reconfiguration of fulfillment of conditions for conditional handover”.
  • conditional handover is configured in an RRCReconfiguration message including a field and IE indicating to the UE that this is a conditional handover, rather than a legacy handover i.e. that the UE needs monitor execution conditions
  • RRCReconfiguration message including a field and IE indicating to the UE that this is a conditional handover, rather than a legacy handover i.e. that the UE needs monitor execution conditions
  • the UE shall:
  • the UE shall perform the following actions upon reception of the RRCReconfiguration not including condReconfiguration or, if included, upon the triggering of the associated condition in condReconfiguration :
  • RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
  • the UE may require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
  • the SFN of the respective target SpCell e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration
  • stop timer T390 if running, for all access categories
  • search SpaceSIB 1 if the active downlink BWP, which is indicated by the firstActiveDowniinkBWP-id for the target SpCell of the MCG, has a common search space configured by search SpaceSIB 1 :
  • the UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located. 5.3.5.x Triggering of condReconfiguration
  • the UE Upon the triggering of the condition condReconfiguration, the UE shall:
  • the UE shall:
  • the UE shall:
  • the UE shall perform the following actions upon reception of the RRCReconfiguration ⁇ .
  • RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. 2> else ( RRCReconfiguration was received via SRB3):
  • the UE may require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CGI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
  • the SFN of the respective target SpCell e.g. measurement gaps, periodic CGI reporting, scheduling request configuration, sounding RS configuration
  • stop timer T390 if running, for all access categories
  • search SpaceSIB 1 4> acquire the SIB 1 of the target SpCell of the MCG, as specified in 5.2.2.3.1 which is scheduled as specified in TS 38.213 [13];
  • the UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
  • the UE shall perform the following actions upon reception of the RRCReconfiguration not including condReconfiguration or, if included, upon the triggering of the associated condition in condReconfiguratiorr.
  • RRCReconfigurationComplete message 1 > if the RRCReconfiguration message includes the dedicatedSystemlnformationDelivery. 2> perform the action upon reception of System Information as specified in 5.2.2.4; > set the content of RRCReconfigurationComplete message as follows:
  • RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
  • the UE may require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
  • the SFN of the respective target SpCell e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration
  • stop timer T390 if running, for all access categories
  • search SpaceSIB 1 if the active downlink BWP, which is indicated by the firstActiveDowniinkBWP-id for the target SpCell of the MCG, has a common search space configured by search SpaceSIB 1 :
  • the UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
  • the actions are, in addition to execution the actual handover, e.g. stopping of timers T310, T312 and T370 and starting of timer T304.
  • the triggering condition is fulfilled in the UE, but no notification from the UE is sent.
  • the actions are triggered when the condition is fulfilled.
  • the UE triggers an event when the triggering condition is fulfilled.
  • the event could be the existing A3 event or a new event.
  • a MeasurementReport is sent according to existing behavior.
  • the UE sends a message other than MeasurementReport when the triggering condition is fulfilled.
  • the message could be an existing RRC message or a new message or a lower layer notification.
  • the network configures conditional mobility when a certain event has been fulfilled in the UE.
  • the A3 event is used to trigger a non-conditional handover and it can also be used to trigger conditional handover.
  • the A3 event could be used both for triggering conditional handover and for triggering the fulfilment of the triggering condition for conditional handover.
  • two different thresholds need to be connected to the A3 event, i.e. one new threshold needs to be defined.
  • One threshold is configured for the A3 event as in legacy (that threshold will trigger the configuration of conditional handover) and a new threshold is configured in RRCRecon figuration message in relation to the configuration of conditional handover.
  • a new event could be defined to trigger conditional mobility, i.e. there are two different events which trigger configuration of conditional handover and which trigger the fulfilment of the triggering condition. See also the examples related to triggering condition of conditional mobility.
  • a wireless network such as the example wireless network illustrated in Figure 5.
  • the wireless network of Figure 5 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ1 10, QQ1 10b, and QQ110c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node QQ160 and wireless device (WD) QQ1 10 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.1 1 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node QQ160 and WD QQ1 10 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio 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
  • 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 may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such 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 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), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.
  • network node QQ160 illustrated in the example wireless network of Figure 5 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node QQ160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node QQ160 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.
  • network node QQ160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node QQ160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, 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 QQ160.
  • Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry QQ170 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 QQ160 components, such as device readable medium QQ180, network node QQ160 functionality.
  • processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry QQ170 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174.
  • radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units
  • processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170.
  • some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer- executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, 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
  • Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160.
  • Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190.
  • processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
  • Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ1 10. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162.
  • antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192.
  • the digital data may be passed to processing circuitry QQ170.
  • the interface may comprise different components and/or different combinations of components.
  • network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190.
  • interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).
  • Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz.
  • An omni-directional antenna may be used to transmit/receive radio signals in any direction
  • a sector antenna may be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna may be referred to as MIMO.
  • antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
  • Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160.
  • network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187.
  • power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node QQ160 may include additional components beyond those shown in Figure 5 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle- mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • PDA personal digital assistant
  • a wireless cameras a gaming console or device
  • a music storage device a playback appliance
  • a wearable terminal device a wireless endpoint
  • a mobile station a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (L
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • NB-loT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device QQ1 10 includes antenna QQ11 1 , interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137.
  • WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ1 10, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ1 10.
  • Antenna QQ11 1 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ11 1 may be separate from WD QQ1 10 and be connectable to WD QQ110 through an interface or port. Antenna QQ1 1 1 , interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ11 1 may be considered an interface.
  • interface QQ114 comprises radio front end circuitry QQ1 12 and antenna QQ11 1.
  • Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116.
  • Radio front end circuitry QQ1 14 is connected to antenna QQ11 1 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ11 1 and processing circuitry QQ120.
  • Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ1 11.
  • WD QQ1 10 may not include separate radio front end circuitry QQ1 12; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ11 1.
  • Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ1 12 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ1 18 and/or amplifiers QQ1 16. The radio signal may then be transmitted via antenna QQ1 11.
  • antenna QQ1 11 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112.
  • the digital data may be passed to processing circuitry QQ120.
  • the interface may comprise different components and/or different combinations of components.
  • Processing circuitry QQ120 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 WD QQ1 10 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.
  • processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry QQ120 of WD QQ1 10 may comprise a SOC.
  • RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.
  • some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium.
  • some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry QQ120 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ1 10, but are enjoyed by WD QQ1 10 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120.
  • Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120.
  • processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
  • User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ1 10. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ1 10. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ1 10. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ1 10, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ1 10, and to allow processing circuitry QQ120 to output information from WD QQ110.
  • User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
  • Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ1 10 which need power from power source QQ136 to carry out any functionality described or indicated herein.
  • Power circuitry QQ137 may in certain embodiments comprise power management circuitry.
  • Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.
  • Figure 6 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE QQ2200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE QQ200 as illustrated in Figure 6, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 6 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ21 1 , memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof.
  • Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in Figure 6, or only a subset of the components. The 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.
  • processing circuitry QQ201 may be configured to process computer instructions and data.
  • Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, 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 QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE QQ200 may be configured to use an output device via input/output interface QQ205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE QQ200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a.
  • Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243a may comprise a Wi-Fi network.
  • Network connection interface QQ21 1 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201.
  • ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227.
  • Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221 , which may comprise a device readable medium.
  • processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231.
  • Network QQ243a and network QQ243b may be the same network or networks or different network or networks.
  • Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b.
  • communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.1 1 , CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.
  • communication subsystem QQ231 may be configured to include any of the components described herein.
  • processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIG. 7 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390.
  • Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment QQ300 comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360.
  • Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360.
  • Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines QQ340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.
  • processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.
  • hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.
  • CPE customer premise equipment
  • NFV network function virtualization
  • 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.
  • virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225.
  • Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.
  • a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ41 1 , such as a radio access network, and core network QQ414.
  • Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c.
  • Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415.
  • a first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c.
  • a second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491 , QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.
  • Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420.
  • Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 8 as a whole enables connectivity between the connected UEs QQ491 , QQ492 and host computer QQ430.
  • the connectivity may be described as an over-the-top (OTT) connection QQ450.
  • Host computer QQ430 and the connected UEs QQ491 , QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ41 1 , core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications.
  • base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491.
  • base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.
  • host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500.
  • Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities.
  • processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer QQ510 further comprises software QQ511 , which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518.
  • Software QQ511 includes host application QQ512.
  • Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.
  • Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530.
  • Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 9) served by base station QQ520.
  • Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510.
  • Connection QQ560 may be direct or it may pass through a core network (not shown in Figure 9) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.
  • Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531 , which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532.
  • Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510.
  • an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510.
  • client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data.
  • OTT connection QQ550 may transfer both the request data and the user data.
  • Client application QQ532 may interact with the user to generate the user data that it provides.
  • host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 9 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491 , QQ492 of Figure 8, respectively.
  • the inner workings of these entities may be as shown in Figure 9 and independently, the surrounding network topology may be that of Figure 8.
  • OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment.
  • the teachings of these embodiments may improve the data rate, latency, power consumtion and/or connectivity and thereby provide benefits such as improved connectivity (e.g. connection reliability and/or connection continuity) and/or other benefits.
  • 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 OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both.
  • sensors may be deployed in or in association with communication devices through which OTT connection QQ550 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 QQ51 1 , QQ531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.
  • FIG 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section.
  • the host computer provides user data.
  • substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application.
  • step QQ620 the host computer initiates a transmission carrying the user data to the UE.
  • step QQ630 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ640 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 1 1 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 1 1 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • step QQ810 the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data.
  • substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application.
  • substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step QQ930 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • Figure 14 illustrates a schematic block diagram of an apparatus WW00 in a wireless network (for example, the wireless network shown in Figure 5).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device QQ110 or network node QQ160 shown in Figure 5).
  • Apparatus WW00 is operable to carry out the example method described with reference to Figure VV and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure VV is not necessarily carried out solely by apparatus WW00. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus WW00 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause determining unit WW02, mobility procedure unit WW04, and any other suitable units of apparatus WW00 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus WW00 includes determining unit WW02 configured to determine, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and mobility procedure unit WW04 configured to, if the mobility procedure is not associated with a condition, carry out the mobility procedure.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • a method performed by a wireless device comprising:
  • determining whether the mobility procedure is associated with a condition comprises determining whether a flag or field in the message indicates that the mobility procedure is associated with the condition.
  • determining whether the mobility procedure is associated with a condition comprises determining whether the message includes one or more information elements associated with the condition.
  • determining whether the mobility procedure is associated with a condition comprises determining a type of the message.
  • the message further configures a respective mobility procedure associated with each of one or more additional candidate target cells.
  • the method further comprises receiving the message, and receiving one or more additional messages, each additional message configuring a respective mobility procedure associated with each of one or more additional candidate target cells.
  • determining that the condition has been met comprises determining that the parameter exceeds a threshold.
  • determining that the condition has been met comprises determining that an A3 event has been triggered.
  • determining that the condition has been met comprises determining that an A3 event has been triggered.
  • triggering the A3 event when a signal strength of a candidate target cell is greater than a signal strength of a serving cell of the wireless device by a first threshold.
  • a method performed by a base station comprising:
  • the message further configures, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
  • the message contains a plurality of RRC Reconfiguration messages, each RRC Reconfiguration message configuring, for the wireless device, the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells.
  • the method further comprises sending the message, and sending one or more additional messages, each additional message configuring, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
  • a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold.
  • a wireless device comprising:
  • - power supply circuitry configured to supply power to the wireless device.
  • a base station comprising:
  • - power supply circuitry configured to supply power to the base station.
  • a user equipment comprising:
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;
  • the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;
  • a battery connected to the processing circuitry and configured to supply
  • a communication system including a host computer comprising:
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • a user equipment configured to communicate with a base station, the UE
  • a communication system including a host computer comprising:
  • a communication interface configured to forward user data to a cellular
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • the cellular network further includes a base station configured to communicate with the UE.
  • the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
  • a communication system including a host computer comprising:
  • a - communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing request data
  • the host computer receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • the method of the previous embodiment further comprising, at the UE, providing the user data to the base station.
  • the method of the previous 2 embodiments further comprising:
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • the host computer receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A
  • the method of the previous embodiment further comprising at the base station, receiving the user data from the UE.

Landscapes

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

Abstract

A method performed by a wireless device is provided, the method comprising determining, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and if the mobility procedure is not associated with a condition, carrying out the mobility procedure.

Description

MOBILITY PROCEDURE
Technical Field
Examples of the present disclosure relate to determining if a mobility procedure is associated with a condition.
Background
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.
An RRC_CONNECTED UE in LTE (LTE may also be called EUTRA) can be configured by the network to perform measurements and, upon triggering measurement reports the network may send a handover command to the UE. The handover command may in LTE e.g. be an RRCConnectionReconfiguration with a field called mobilityControllnfo and in NR, it e.g. may be an RRCRecon figuration with a reconfigurationWithSync field.
These reconfigurations (e.g. the handover commands) are actually prepared by the target cell upon a request from the source node (over X2 interface in case of EUTRA-EPC or Xn interface in case of EUTRA-5GC or NR) and takes into account the existing RRC configuration the UE has with source cell (which are provided in the inter-node request). Among other parameters that reconfiguration provided by target contains all information the UE needs to access the target cell, e.g., random access configuration, a new C-RNTI assigned by the target cell and security parameters enabling the UE to calculate new security keys associated to the target cell so the UE can send a handover complete message on SRB1 (encrypted and integrity protected) based on new security keys upon accessing the target cell.
Figure 1 summarizes the flow signalling between UE, source node and target node during a handover procedure. In step 1 of Figure 1 , measurement control and reports are exchanged between UE and source gNB. In step 2, the source gNB makes a handover (HO) decision. In step 3, source gNB sends a handover request to a target gNB. In step 4, target gNB performs admission control. In step 5, target gNB sends a HO request acknowledge to source gNB. In step 6, Uu handover trigger information is exchanged between UE and source gNB. The UE detaches from the old cell and synchronises to the new cell. In step 7, source gNB sends SN status transfer to target gNB, and delivers buffered and in transit user data to target gNB. The source gNB may also forward user data to target gNB. The target gNB buffers user data from source gNB. In step 8, the UE synchronises to the new cell (target gNB) and completed RRC HO procedure. User data may then be exchanged between UE and target gNB. User data may be forwarded from target gNB to User Plane Function(s). In step 9, target gNB sends a path switch request to AMF. In step 10, AMF and UPF(s) exchange path switch related 5G CN internal signalling and actual DL path switch is performed in UPF(s). User data may then be exchanged between target gNB and UPF(s). In step 11 , AMF returns a path switch request ack to the target gNB. In step 12, target gNB sends a UE context release to source gNB.
Both in LTE and NR, some principles exist for handovers, HO, (or in more general terms, handover may be referred to as mobility in RRC_CONNECTED), e.g.:
Mobility in RRC_CONNECTED is Network-based as the network has best info regarding current situation such as load conditions, resources in different nodes, available frequencies, etc. Network can also take into account the situation of many UEs in the network, for a resource allocation perspective.
Network prepares a target cell before the UE accesses that cell. Source provides UE with the RRC configuration to be used in the target cell, including SRB1 configuration to send HO complete.
UE is provided by target with a target C-RNTI i.e. target identifies UE from MSG.3 on MAC level for the HO complete message. Hence, there is no context fetching, unless a failure occurs. To speed up the handover, network provides needed information on how to access the target e.g. RACH configuration, so the UE does not have to acquire SI prior to the handover.
UE may be provided with CFRA (Contention Free Radio Aceess) resources, i.e. in that case target identifies the UE from the preamble (MSG.1). The principle behind here is that the procedure can always be optimized with dedicated resources. In CHO that might be a bit tricky as there is uncertainty about the final target but also the timing.
Security is prepared before the UE accesses the target cell i.e. Keys must be refreshed before sending RRC Connection Reconfiguration Complete message, based on new keys and encrypted and integrity protected so UE can be verified in target cell.
Both full and delta reconfiguration are supported so that the HO command can be minimized.
Mobility robustness Work Item in Rel-16 for LTE and NR and Conditional HO
Two new work items for mobility enhancements in LTE and NR have started in 3GPP in release 16. The main objectives of the work items are to improve the robustness at handover and to decrease the interruption time at handover.
One problem related to robustness at handover is that the HO Command (RRCConnectionReconfiguration with mobilityControllnfo and RRCReconfiguration with a reconfigurationWithSync field) is normally sent when the radio conditions for the UE are already quite bad. That may lead to that the HO Command may not reach the UE in time if the message is segmented or there are retransmissions.
In LTE and NR, different solutions to increase mobility robustness have been discussed in the past. One solution discussed in NR is called“conditional handover” or“early handover command”. In order to avoid the undesired dependence on the serving radio link upon the time (and radio conditions) where the UE should execute the handover, the possibility to provide RRC signaling for the handover to the UE earlier should be provided. To achieve this, it should be possible to associate the HO command with a condition e.g. based on radio conditions possibly similar to the ones associated to an A3 event, where a given neighbour becomes X db better than source/serving cell. As soon as the condition is fulfilled, the UE executes the handover in accordance with the provided handover command. Such a condition could e.g. be that the quality of the target cell or beam becomes X dB stronger than the serving cell. The threshold Y used in a preceding measurement reporting event should then be chosen lower than the one in the handover execution condition. This allows the serving cell to prepare the handover upon reception of an early measurement report and to provide the RRCConnectionReconfiguration with mobilityControllnfo at a time when the radio link between the source cell and the UE is still stable. The execution of the handover is done at a later point in time (and threshold) which is considered optimal for the handover execution.
Figure 2 depicts an example with just a serving and a target cell. In practice there may often be many cells or beams that the UE reported as possible candidates based on its preceding RRM measurements. The network should then have the freedom to issue conditional handover commands for several of those candidates. The RRCConnectionReconfiguration for each of those candidates may differ e.g. in terms of the HO execution condition (RS to measure and threshold to exceed) as well as in terms of the RA preamble to be sent when a condition is met. In Figure 2, serving gNB may exchange user plane data with the UE. In step 1 , the UE sends a measurement report with“low” threshold to serving gNB. The serving gNB maks a HO decision based on this early report. In step 2, the serving gNB sends an early HO request to a target gNB. The target gNB accepts the HO request and builds a RRC config. The target gNB returns a HO ack including the RRC config to the serving gNB in step 3. In step 4, a conditional HO command with“high” threshold is sent to the UE. Subsequently, measurements by the UE may fulfil the HO condition of the conditional HO command. The UE thus triggers the pending conditional handover. The UE performs synchronization and random access with the target gNB in step 5, and HO confirm is exchanged in step 6. In step 7, target gNB infoms serving gNB that HO is completed. The target gNB may then exchange user plane data with the UE.
While the UE evaluates the condition, it should continue operating per its current RRC configuration, i.e., without applying the conditional HO command. When the UE determines that the condition is fulfilled, it disconnects from the serving cell, applies the conditional HO command and connects to the target cell. These steps are equivalent to the current, instantaneous handover execution.
Some examples may rely on context fetching called where a condition is also provided to the UE and, upon the fulfillment of the condition the UE executes resume. This may comprise a method executed by a UE in RRC connected mode, the method including: Receiving a message containing at least one condition from the network and monitoring the fulfillment of the provided condition;
Upon the fulfillment of a condition triggering an RRC Resume procedure or an equivalent procedure towards at least one target cell comprising:
This may be summarized by the flow diagram in Figure 3, which summarizes signalling between a UE, serving node and target node during a conditional RRC Resume procedure. In Figure 3, serving gNB may exchange user plane data with the UE. In step 1 , the UE sends a measurement report with“low” threshold to serving gNB. The serving gNB maks a HO decision based on this early report. In step 2, the serving gNB sends an early HO request to a target gNB. The target gNB accepts the HO request. The target gNB returns a HO ack to the serving gNB in step 3. In step 4, a conditional HO command with “high” threshold is sent to the UE. Subsequently, measurements by the UE may fulfil the HO condition of the conditional HO command. The UE thus triggers the pending conditional handover. The UE performs synchronization and random access with the target gNB in step 5, and in step 6 sends a RRCConnectionResumeRequest message to the target gNB. The target gNB may then exchange user plane data with the UE
There currently exist certain challenge(s). For example, the baseline solution for configuration of handover (or reconfiguration with sync) assumes that the UE actions on handover execution are triggered by the reception of an RRC reconfiguration like message containing the HO Command. If we use NR RRC as an example, the UE performs a handover execution (called reconfiguration with sync in NR) upon the reception of an RRCReconfiguration message containing a reconfigurationWithSync field (which is part of CellGroupConfig IE). Then, all necessary actions for the handover execution are triggered upon the reception of the message. An example implementation of the baseline
configuration according to TS 38.331 , sub-clause 5.3 is shown below:
*******************************************************************************************************
5.3.5.3 Reception of an RRCReconfiguration by the UE
The UE shall perform the following actions upon reception of the RRCReconfiguration·.
1 > if the RRCReconfiguration includes the fullConfig :
2> perform the radio configuration procedure as specified in 5.3.5.11 ; 1 > if the RRCReconfiguration includes the masterCellGroup :
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1 > if the RRCReconfiguration includes the masterKeyUpdate\
2> perform security key update procedure as specified in 5.3.5.7;
1 > if the RRCReconfiguration includes the secondaryCellGroup·.
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1 > if the RRCReconfiguration message contains the radioBearerConfig·.
2> perform the radio bearer configuration according to 5.3.5.6;
1 > if the RRCReconfiguration message includes the measConfig·.
2> perform the measurement configuration procedure as specified in 5.5.2;
1 > if the RRCReconfiguration message includes the dedicatedSIBI -Delivery.
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
1 > if the RRCReconfiguration message includes the dedicatedSystemlnformationDelivery.
2> perform the action upon reception of System Information as specified in 5.2.2.4;
1 > set the content of RRCReconfigurationComplete message as follows:
2> if the RRCReconfiguration includes the masterCellGroup containing the
reportUplinkTxDirectCurrent, or;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the
reportUplinkTxDirectCurrent
3> include the uplinkTxDirectCurrentList,
1 > if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCReconfiguration was received via SRB1 :
3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E- UTRA RRC message RRCConnectionReconfigurationComplete as specified in
TS 36.331 [10];
3> if reconfigurationWithSync was included in spCellConfig of an SCG: 4> initiate the random access procedure on the SpCell, as specified in TS 38.321
[3];
3> else:
4>the procedure ends;
NOTE: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2> else (RRCRecon figuration was received via SRB3):
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE: For EN-DC, in the case of SRB1 , the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case of SRB3, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.
1 > else:
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
1 > if reconfigurationWithSvnc was included in spCellConfig of an MCG or SCG, and when
MAC of an NR cell group successfully completes a random access procedure triggered above;
2> stop timer T304 for that cell group;
2> apply the parts of the CQI reporting configuration, the scheduling reguest
configuration and the sounding RS configuration that do not reguire the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that
reguire the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling reguest configuration, sounding RS configuration), if any, upon acguiring the SFN of that target SpCell;
2> if the reconfigurationWithSvnc was included in spCellConfig of an MCG: 3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-ld for the target SpCell of the MCG, has a common search space configured:
4> acquire the SIB1 of the target SoCell of the MCG, as specified in 5.2.2.3.1 ;
2>the procedure ends.
NOTE: The UE is only required to acquire broadcasted SIB 1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
*******************************************************************************************************
5.3.5.5 Cell Group configuration
5.3.5.5.1 General
The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). For EN-DC, the MCG is configured as specified in TS 36.331 [10] The network provides the configuration parameters for a cell group in the CellGroupConfig IE.
The UE performs the following actions based on a received CellGroupConfia IE:
1 > if the CellGroupConfia contains the spCellConfig with reconfigurationWithSvnc.
2> perform Reconfiguration with sync according to 5.3.5.5.2:
2> resume all suspended radio bearers and resume SCG transmission for all radio bearers, if suspended;
1 > if the CellGroupConfig contains the rlc-BearerToReleaseList
2> perform RLC bearer release as specified in 5.3.5.5.3;
1 > if the CellGroupConfig contains the rlc-BearerToAddModList
2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4;
1 > if the CellGroupConfig contains the mac-CellGroupConfig·.
2> configure the MAC entity of this cell group as specified in 5.3.5.5.5;
1 > if the CellGroupConfig contains the sCellToReleaseList
2> perform SCell release as specified in 5.3.5.5.8;
1 > if the CellGroupConfig contains the spCellConfig·.
2> configure the SpCell as specified in 5.3.5.5.7; 1 > if the CellGroupConfig contains the sCellToAddModList
2> perform SCell addition/modification as specified in 5.3.5.5.9.
*******************************************************************************************************
5.3.5.5.2 Reconfiguration with sync
The UE shall perform the following actions to execute a reconfiguration with sync.
1 > stop timer T310 for the corresponding SoCell, if running;
1 > start timer T304 for the corresponding SpCell with the timer value set to t304 , as included in the reconfigurationWithSvnc ;
1 > if the freguencylnfoDL is included:
2> consider the target SpCell to be one on the SSB frequency indicated by the
freguencylnfoDL with a physical cell identity indicated by the physCellld ;
1 > else:
2> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellld ;
1 > start synchronising to the DL of the target SpCell and acquire the MIB of the target
SpCell as specified in 5.2.2.3.1 ;
NOTE: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the
reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
1 > reset the MAC entity of this cell group;
1 > consider the SCell(s) of this cell group, if configured, to be in deactivated state:
1 > apply the value of the newU E-Identity as the C-RNTI for this cell group;
Editor's Note: Verify that this does not configure some common parameters which are later discarded due to e.g. SCell release or due to LCH release.
1 > configure lower layers in accordance with the received s pCellConfigCommon:
1 > configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync. *******************************************************************************************************
The configuration of conditional handover is not supported in 3GPP specifications of Release 15. One of the challenges that is addressed by at least some examples disclosed herein is that the information (i.e. configuration, fields, lEs) provided to the UE for a handover or for a conditional handover may overlap. However, it could be problematic if the exact same configuration and fields for handovers (e.g. exact same message and same configuration procedures) are used for conditional handovers, as the reception of a message in one case leads to the execution, while in conditional handover the execution of actions is determined by conditions.
Summary
Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. In some examples, a method is proposed that comprises a solution for configuring conditional mobility and lists things in the configuration which are new compared to configuration of legacy handover.
One aspect of the present disclosure provides a method performed by a wireless device. The method comprises determining, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and if the mobility procedure is not associated with a condition, carrying out the mobility procedure.
A further aspect of the present disclosure provides a method performed by a base station. The method comprises sending a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
A still further aspect of the present disclosure provides a wireless device comprising a processor and a memory. The memory contains instructions executable by the processor such that the wireless device is operable to determine, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and if the mobility procedure is not associated with a condition, carrying out the mobility procedure. Another aspect of the present disclosure provides a base station comprising a processor and a memory. The memory contains instructions executable by the processor such that the base station is operable to send a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
An additional aspect of the present disclosure provides a wireless device configured to determine, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and if the mobility procedure is not associated with a condition, carrying out the mobility procedure.
A further aspect of the present disclosure provides a base station configured to send a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
Brief Description of the Drawings
For a better understanding of examples of the present disclosure, and to show more clearly how the examples may be carried into effect, reference will now be made, by way of example only, to the following drawings in which:
Figure 1 summarizes signalling between a UE, source node and target node during a handover procedure;
Figure 2 summarizes signalling between a UE, serving node and target node during a conditional handover procedure;
Figure 3 summarizes signalling between a UE, serving node and target node during a conditional RRC Resume procedure;
Figure 4A is a flow chart of an example of a method performed by a wireless device;
Figure 4B is a flow chart of an example of a method performed by a base station;
Figure 5 shows an example of a wireless network in accordance with some embodiments; Figure 6 shows an example of a User Equipment (UE) in accordance with some embodiments;
Figure 7 is a schematic block diagram illustrating a virtualization environment in accordance with some embodiments;
Figure 8 shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;
Figure 9 shows a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;
Figure 10 shows methods implemented in a communication system in accordance with some embodiments;
Figure 11 shows methods implemented in a communication system in accordance with some embodiments;
Figure 12 shows methods implemented in a communication system in accordance with some embodiments;
Figure 13 shows methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and
Figure 14 illustrates a schematic block diagram of virtualization apparatus in accordance with some embodiments.
Detailed Description
The following sets forth specific details, such as particular embodiments or examples for purposes of explanation and not limitation. It will be appreciated by one skilled in the art that other examples may be employed apart from these specific details. In some instances, detailed descriptions of well-known methods, nodes, interfaces, circuits, and devices are omitted so as not obscure the description with unnecessary detail. Those skilled in the art will appreciate that the functions described may be implemented in one or more nodes using hardware circuitry (e.g., analog and/or discrete logic gates interconnected to perform a specialized function, ASICs, PLAs, etc.) and/or using software programs and data in conjunction with one or more digital microprocessors or general purpose computers. Nodes that communicate using the air interface also have suitable radio communications circuitry. Moreover, where appropriate the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.
Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.
Certain embodiments may provide one or more of the following technical advantage(s). For example, some examples comprise a mechanism for configuration of conditional mobility, so that the UE can recognize the configuration of conditional handover (or other mobility procedure), recognize the conditions, trigger the actions when the conditions are fulfilled and perform the intended actions when the conditions are fulfilled.
Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
In some embodiments, there is provided a method 400 shown in Figure 4A, which is a flow chart of an example of a method 400 performed by a wireless device. The method 400 comprises, in step 402, determining, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition. The message may be received by the wireless device, for example from or via a serving cell of the wireless device. The method also comprises, in step 404, if the mobility procedure is not associated with a condition, carrying out the mobility procedure. The mobility procedure may (if not associated with a condition) be carried out immediately, for example immediately following receipt of the message, or otherwise not in response to a condition associated with the mobility procedure (as there may be no such condition).
Thus a wireless device may be aware of whether a message pertaining to a mobility procedure is associated with a condition or not, and hence may in some examples undertake actions according to whether the mobility procedure is associated with a condition or not. For example, if the mobility procedure is associated with the condition, the method may comprise carrying out the mobility procedure upon determining that the condition has been met. This may comprise in some examples monitoring at the wireless device one or more signals (e.g. reference signals) received at the wireless device, e.g. from one or more candidate target cells for the mobility procedure.
In some examples, determining whether the mobility procedure is associated with a condition comprises determining whether a flag or field in the message indicates that the mobility procedure is associated with the condition.
Determining whether the mobility procedure is associated with a condition may in some examples comprise determining whether the message includes one or more information elements associated with the condition. Thus for example the presence of one or more particular information elements may indicate that the mobility procedure is associated with a condition. The one or more information elements may in some examples convey information relating to the mobility procedure or the condition. For example, the one or more information elements may identify the condition for the mobility procedure.
In some examples, determining whether the mobility procedure is associated with a condition may comprise determining a type of the message. For example, if the message is one type of message (e.g. one type of RRC message), the mobility procedure may not be associated with a condition, whereas if the message is another type of message (e.g. another type of RRC message), the mobility procedure may be associated with a condition.
In some examples, where the mobility procedure is associated with the condition and a candidate target cell, the message may configure a respective mobility procedure associated with each of one or more additional candidate target cells. Thus the message may for example include configuration information in respect of multiple target cells (the candidate cell and the additional candidate target cell(s)). The message may in some examples contain a plurality of RRC Reconfiguration messages, each RRC Reconfiguration message configuring the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells. That is, for example, each RRC Reconfiguration message may contain configuration information for a respective target cell.
The mobility procedure may in some examples be associated with the condition and a candidate target cell, and the method may further comprise receiving the message, and receiving one or more additional messages, each additional message configuring a respective mobility procedure associated with each of one or more additional candidate target cells. Thus, for example, configuration information relating to each of a plurality of candidate target cells may be received in one or more messages, for example one message per candidate target cell.
In some examples, the respective mobility procedure associated with each of the candidate target cell and the one or more additional candidate target cells is associated with the condition, or a respective additional condition. For example, the mobility procedure associated with the candidate target cells may all be associated with the same condition, may be associated with individual conditions, or groups of candidate target cells may be associated with a condition for that group.
In some examples, the message identifies the condition. The message may comprise an RRC Connection Reconfiguration message or a RRC Reconfiguration message. The mobility procedure may comprise a handover to a target cell or a resume procedure (e.g. RRC Resume procedure) to a candidate target cell associated with the mobility procedure.
In some examples, determining that the condition has been met comprises monitoring a parameter, such as for example the signal strength of one or more signals (e.g. reference signal(s)) received (e.g. at the wireless device) from one or more candidate target cells. Thus in some examples, determining that the condition has been met comprises determining that the parameter exceeds a threshold. The parameter may comprise a signal strength of at least one candidate target cell associated with the mobility procedure at the wireless device.
The condition may in some examples comprise whether a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold. This, in some examples the method comprises configuring the conditional mobility procedure in response to a signal strength of a candidate target cell being greater than the signal strength of a serving cell of the wireless device by a second threshold, wherein the second threshold is lower than the first threshold. Thus, for example, the conditional mobility procedure may be set up when the lower threshold is met or exceeded, and triggered (e.g. to move the wireless device to a new cell) once the higher threshold has been met or exceeded.
In some examples, determining that the condition has been met comprises determining that an A3 event has been triggered. The method may then in some examples comprise triggering the A3 event when a signal strength of a candidate target cell is greater than a signal strength of a serving cell of the wireless device by a first threshold.
Some examples of this disclosure also provide a method performed by a base station. Figure 4B is a flow chart of an example of a method 420 performed by a base station. The method 420 comprises, in step 422, sending a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition. Thus, the wireless device may be able to identify whether the mobility procedure is associated with a condition or not, and may thus carry out actions accordingly. In some examples, the wireless device may carry out the method disclosed above.
In some examples, a flag or field in the message indicates whether the mobility procedure is associated with the condition. Additionally or alternatively, the message may include one or more information elements associated with the condition if the mobility procedure is associated with the condition. The one or more information elements may identify the condition for the mobility procedure. In some examples, a type of the message indicates whether the mobility procedure is associated with the condition.
The mobility procedure is in some examples associated with the condition and a candidate target cell, and the message further configures, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells. The message may for example contain a plurality of RRC Reconfiguration messages, each RRC Reconfiguration message configuring, for the wireless device, the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells.
In some examples, the mobility procedure is associated with the condition and a candidate target cell, and the method further comprises sending the message, and sending one or more additional messages, each additional message configuring, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
The respective mobility procedure associated with each of the candidate target cell and the one or more additional candidate target cells may be associated with the condition (e.g. the same condition). The respective mobility procedure associated with each of the additional candidate target cells is associated with a respective additional condition (e.g. each mobility procedure is associated with individual conditions, or each of a plurality of conditions applies to a group of mobility procedures). In some examples, the method may comprise receiving configuration details associated with each mobility procedure from a respective cell associated with the mobility procedure, e.g. using an appropriate interface between base stations (eNBs, gNBs etc) or cells.
In some examples, the message identifies the condition. In some examples, the message comprises an RRC Connection Reconfiguration message or a RRC Reconfiguration message. In some examples, the mobility procedure comprises a handover to a target cell or a resume procedure (e.g. RRC Resume procedure) to a candidate target cell associated with the mobility procedure.
The condition may in some examples comprise whether a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold. The message may thus configure the wireless device to carry out the conditional mobility procedure in response to a signal strength of a candidate target cell being greater than the signal strength of a serving cell of the wireless device by a second threshold, wherein the second threshold is lower than the first threshold.
In some examples, the base station is associated with a serving cell of the wireless device.
Particular example embodiments will now be described.
Some examples comprise a method for configuring the user equipment, UE (or wireless device, which may be used herein in place of UE) with conditional handover. The configuration may be done in an RRC message containing the handover (HO) Command (RRCConnectionReconfiguration with mobilityControllnfo and RRCReconfiguration with a reconfigurationWithSync field). In some examples the terms handover and reconfiguration with sync may be used interchangeably or have a similar meaning. Hence, in some examples a conditional handover may also be called a conditional reconfiguration with sync.
At least some, or at least most, of the UE (and/or network) actions defined in some examples may be performed in NR or LTE. In other words, for example, the configuration of a conditional HO received in NR and executed in NR. However, the method is also application in the other following cases, at least: UE is configured with a condition HO in NR, then the condition is triggered and UE executes the HO in LTE;
UE is configured with a condition HO in LTE, then the condition is triggered and UE executes the HO in NR;
Or, in more general terms, UE is configured with a condition HO in RAT-1 , then the condition is triggered and UE executes the HO in RAT-2.
At least some, or at least most, of the UE (and/or network) actions defined in some examples are described in terms of handover or reconfigurations with sync, examples of a mobility procedure, which may comprise the change of a cell (e.g. serving cell), e.g. for a wireless device or UE. However, in some examples the method also comprises the case where a cell is added, for example in case of multi-connectivity scenarios such as carrier aggregation, dual connectivity, EN-DC, NR-DC, MR-DC, etc, where the addition may in some examples also be referred to as a mobility procedure. In that case, the configuration of a conditional mobility procedure or HO as described in some examples may be described as a conditional configuration for SCG addition or SCell addition, or equivalent.
Examples related to recognition of conditional handover
The UE may be able to distinguish conditional handover (e.g. HO is executed upon the triggering of a condition) from handover (e.g. HO is executed upon the reception of the message). In this case, HO is used in place of mobility procedure, though herein the term HO can be used interchangeably with mobility procedure where appropriate. The UE could distinguish handover from conditional handover in one or more different ways:
Solution a / It could be indicated as a flag in the RRC message that the configuration is a conditional handover. That may be a flag or field in the same message used to indicate a handover. And, if that is present the UE does not execute the handover until the associated condition is triggered. The message may be an RRCReconfiguration or an RRCConnectionReconfiguration.
Solution b/ A certain IE (information element) or a number of lEs indicate that it is a conditional handover if these lEs are present in the message. That IE may be the configuration associated to the condition itself, which may comprise implicitly or explicitly: o Measurement threshold(s) associated to measurement quantities (e.g. for RSRP, RSRQ, SINR) for comparing the quality of at least an SpCell (e.g. PCell the UE is connected to) with the quality of at least one neighbour cell in a given frequency;
o A time to trigger so that the condition needs to hold for that time to be considered triggered
o Other measurement related parameters e.g. as defined in the A3 event defined in NR or LTE;
o At least one pointer to at least one element or field provided in the measConfig to that UE. For example, the UE may receive a measConfig with a list of measurement identifiers each defined by the triplet (measld, measObject, reportConfig). Then, upon using one of the identifiers in this field in CHO, the UE knows that the condition is associated to an already configured measurement identity.
Solution c/ A new RRC message can be defined for conditional handover, see details below. That message comprises at least one condition associated to at least one RRCReconfiguration message, where each is possibly signaled as a bit string or using the message IE itself. In that solution, a single condition may be associated to multiple RRCReconfiguration like messages, where each message is only associated to a possible candidate cell. Or, alternatively, each condition may have its own associated RRCReconfiguraiton message, each associated to a potential target cell. That may be seen as a signalling optimization as the size of the message may become critical in case the UE receives conditional configurations for a high number of potential target candidate cells.
o In this solution, we may also introduce the concept of stored and restore context and/or message. In this case, the UE receives a set of RRCReconfiguration messages inside the RRCConditionalReconfiguration message and, consider these RRCReconfiguration messages (at least one) as stored. This is similar to what is done with the RRC Reconfiguration upon suspension. Then, when the condition is triggered the associated reconfiguration is restored. Another alternative is to say that the message is only applied upon the triggering of the condition. It also needs to be recognized in network (X2/S1/Xn/Sn) signaling that the HANDOVER REQUEST sent from source eNB to target eNB via X2/S1/Xn/Sn is applicable for a conditional handover. The recognition can be done in the same way as for the RRC message, e.g. a flag, certain IE(s) or a new message.
Examples related to the conditional handover message
The message for configuration of conditional handover can be the existing RRC(Connection)Reconfiguration ( RRCConnectionReconfiguration in LTE and RRCReconfiguration in NR) or a new message. Some of these examples were shown above. The structure of the message can be done in different ways. The message contains information about the configuration in target eNB and, more specifically in the potential target cell. This information is in the baseline built as an RRC message in target gNB and sent to source eNB as a transparent container (e.g. a bit string) which is then forwarded to the UE. For conditional handover the message can be structured in different ways.
The RRC message could be one message containing RRC messages from multiple eNBs in the form of a number of bit strings. If that is the case the RRC message sent to the UE is built in source eNB instead and source eNB includes the RRC messages from the different target eNBs as bit strings. The source eNB may also include other information in the message, e.g. related to the conditions.
In some examples, the target eNB may send information about the target configuration explicitly (i.e. not in the form of a bit string of a compiled RRC message) to source eNB, which builds the RRC message sent to the UE. This requires some updates to network signaling (X2/S1/Xn/Sn). The current messages are HANDOVER REQUEST and HANDOVER REQUEST ACKNOWLEDGE and the HANDOVER REQUEST ACKNOWLEDGE could be updated to contain explicit information to source eNB about the target UE configuration, instead of the existing transparent container. Alternatively new messages could be defined.
In some examples of how the target candidate configurations can be provided to the UE, the RRC message from each target eNB is forwarded to the UE one by one, i.e. the UE receives a number of RRC reconfiguration messages. The conditions could be sent from each target respectively, or there could also be one reconfiguration message from source eNB containing the conditions.
Below one can see a possible implementation of Solution a / which is described above (e.g. a flag called condReconfiguration is used to identify this is a conditional handover) is the following, which shows an example of an ASN.1 code encoding the configuration message and the field description of condReconfiguraiiorr.
*************************************************************************************************
- RRCReconfiguration
The RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) including and security configuration.
Signalling radio bearer: SRB1 or SRB3
RLC-SAP: AM
Logical channel: DCCH
Direction: Network to UE
RRCReconfignration massage
— ASN1START
— TAG-RRCRECONFIGURATION-START
RRCReconfiguration : := SEQUENCE {
rrc-Transactionldentifier RRC-Transactionldentifier,
criticalExtensions CHOICE {
rrcReconfiguration RRCReconfiguration-1Es ,
criticalExtensionsFuture SEQUENCE { }
}
}
RRCReconfiguration-IEs ::= SEQUENCE {
radioBearerConfig RadioBearerConfig OPTIONAL, — Need M
secondaryCellGroup OCTET STRING (CONTAINING CellGroupConfig ) OPTIONAL, — Need M
measConfig MeasConfig OPTIONAL, — Need M
lateNonCriticalExtension OCTET STRING
OPTIONAL,
nonCriticalExtension RRCReconfiguration-v!530-IEs
OPTIONAL
}
RRCReconfiguration-vl530-1Es SEQUENCE {
masterCe11Group OCTET STRING (CONTAINING CellGroupConfig)
OPTIONAL, — Need M
fullConfig ENUMERATED {true}
OPTIONAL, — Cond FullConfig dedicatedNAS-MessageList SEQUENCE ( SIZE ( 1.. maxDRB ) ) OF DedicatedNAS-Message
OPTIONAL, — Cond nonHO
masterKeyUpdate MasterKeyUpdate
OPTIONAL, — Cond MasterKeyChange
dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1)
OPTIONAL, — Need N
dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING Systemlnformation )
OPTIONAL, — Need N
otherConfig OtherConfig
OPTIONAL, — Need N
nonCriticalExtension SEQUENCE { }
OPTIONAL
}
RRCReconfiguration-vl6-IEs : := SEQUENCE {
condReconfiguration ENUMERATED {true}
masterCe11Group OCTET STRING (CONTAINING Ce11GroupConfig ) OPTIONAL Need M
fullConfig ENUMERATED {true}
OPTIONAL, — Cond FullConfig
dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB) ) OF DedicatedNAS-Message OPTIONAL, — Cond nonHO
masterKeyUpdate MasterKeyUpdate
OPTIONAL, — Cond MasterKeyChange
dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) OPTIONAL, — Need N
dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING Systemlnformation ) OPTIONAL, — Need N
otherConfig OtherConfig OPTIONAL, — Need N
nonCriticalExtension SEQUENCE { }
OPTIONAL
}
MasterKeyUpdate : := SEQUENCE {
keySetChangelndicator BOOLEAN,
nextHopChainingCount NextHopChainingCount ,
nas-Container OCTET STRING
OPTIONAL, Cond securityNASC
}
— TAG-RRCRECONFIGURATION-STOP
ASN1STOP
Figure imgf000024_0001
*************************************************************************************************
A possible implementation of Solution b/ described above (e.g. a field called condReconfiguration of IE CondReconfiguration including a trigger/execution configuration, like an A3/A5 event is used to enable the UE to identify this is a conditional handover and not a legacy handover) is the following, which shows an example of an ASN.1 code encoding the configuration message, the fields and lEs:
*************************************************************************************************
- RRCReconfiguration
The RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and security configuration.
Signalling radio bearer: SRB1 or SRB3
RLC-SAP: AM
Logical channel: DCCH
Direction: Network to UE
RRCReconfiguration message
— ASN1START
— TAG-RRCRECONFIGURATION-START
RRCReconfiguration : := SEQUENCE {
rrc-Transactionldentifier RRC-Transactionlidentifier,
criticalExtensions CHOICE {
rrcReconfiguration RRCReconfiguration-IEs ,
criticalExtensionsFuture SEQUENCE { } RRCReconfiguration-IEs SEQUENCE {
radioBearerConfig RadioBearerConfig OPTIONAL, — Need M
secondaryCellGroup OCTET STRING (CONTAINING CellGroupConfig ) OPTIONAL, — Need M
measConfig MeasConfig OPTIONAL, — Need M
lateNonCriticalExtension OCTET STRING
OPTIONAL,
nonCriticalExtension RRCReconfiguration-vl530-1Es
OPTIONAL
}
RRCReconfiguration-vl530-1Es SEQUENCE {
masterCe11Group OCTET STRING (CONTAINING CellGroupConfig )
OPTIONAL, — Need M
fullConfig ENUMERATED {true}
OPTIONAL, — Cond FullConfig
dedicatedNAS-MessageList SEQUENCE ( SIZE ( 1.. maxDRB ) ) OF DedicatedNAS-Message
OPTIONAL, — Cond nonHO
masterKeyUpdate MasterKeyUpdate
OPTIONAL, — Cond MasterKeyChange
dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) OPTIONAL, — Need N
dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING Systemlnformation ) OPTIONAL, — Need N
otherConfig OtherConfig OPTIONAL, — Need N
nonCriticalExtension SEQUENCE { }
OPTIONAL
}
RRCReconfiguration-vl6-IEs : := SEQUENCE
condReconfiguration CondReconfiguration OPTIONAL , masterCe11Group OCTET (CONTAINING CellGroupConfig ) OPTIONAL, — Need M
fullConfig ENUMERATED { true }
OPTIONAL, — Cond FullConfig
dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB) ) OF DedicatedNAS-Message OPTIONAL, — Cond nonHO
masterKeyUpdate MasterKeyUpdate
OPTIONAL, — Cond MasterKeyChange
dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) OPTIONAL, — Need N
dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING Systemlnformation ) OPTIONAL, — Need N
otherConfig OtherConfig OPTIONAL, — Need N
nonCriticalExtension SEQUENCE { }
OPTIONAL
} MasterKeyUpdate : := SEQUENCE {
keySetChangelndicator BOOLEAN,
nextHopChainingCount NextHopChainingCount ,
nas-Container OCTET STRING
OPTIONAL, Cond securityNASC
CondReconfiguration : := SEQUENCE {
eventTriggerCHO ReportConfigNR
TAG-RRCRECONFIGURATION-STOP
ASN1STOP
Figure imgf000026_0001
— ReportConfigNR
The IE ReportConfigNR specifies criteria for triggering of an NR measurement reporting event. Measurement reporting events are based on cell measurement results, which can either be derived based on SS/PBCH block or CSI-RS. These events are labelled AN with N equal to 1 , 2 and so on.
Event A1 : Serving becomes better than absolute threshold;
Event A2: Serving becomes worse than absolute threshold;
Event A3: Neighbour becomes amount of offset better than PCell/PSCell;
Event A4: Neighbour becomes better than absolute threshold;
Event A5: PCell/PSCell becomes worse than absolute thresholdl AND
Neighbour/SCell becomes better than another absolute threshold2. Event A6: Neighbour becomes amount of offset better than SCell.
ReportConfigNR information element
— ASN1START
TAG-REPORT-CONFIG-START
ReportConfigNR ::= SEQUENCE {
reportType CHOICE {
periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig, reportCGI ReportCGI
}
}
ReportCGI SEQUENCE {
cellForWhichToReportCGI PhysCellld,
EventTriggerConfig : := SEQUENCE {
eventld CHOICE {
eventAl SEQUENCE {
al-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger
},
eventA2 SEQUENCE {
a2-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger
},
eventA3 SEQUENCE {
a3-Offset MeasTriggerQuantityOffset , reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger, useWhiteCellList BOOLEAN
},
eventA4 SEQUENCE { a4-Threshold MeasTriggerQuantity,
reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger,
useWhiteCellList BOOLEAN
},
eventA5 SEQUENCE {
a5-Thresholdl MeasTriggerQuantity,
a5-Threshold2 MeasTriggerQuantity,
reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger,
useWhiteCellList BOOLEAN
},
eventA6 SEQUENCE {
a6-Offset MeasTriggerQuantityOffset , reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger,
useWhiteCellList BOOLEAN
}, rsType NR-RS-Type, reportInterval ReportInterval ,
reportAmount ENUMERATED {rl, r2 , r4, r8, r!6, r32, r64, infinity} , reportQuantityCell MeasReportQuantity,
maxReportCells INTEGER (1.. maxCellReport ) , reportQuantityRsIndexes MeasReportQuantity OPTIONAL, — Need R
maxNrofRSIndexesToReport INTEGER (1.. axNroflndexesToReport) OPTIONAL, — Need R
includeBeamMeasurements BOOLEAN
reportAddNeighMeas ENUMERATED {setup} OPTIONAL, — Need R
}
PeriodicalReportConfig : : = SEQUENCE {
rsType NR-RS-Type reportInterval ReportInterval ,
reportAmount ENUMERATED {rl, r2, r4, r8, rl6, r32, r64, infinity} , reportQuantityCell MeasReportQuantity,
maxReportCells INTEGER (1..maxCellReport) , reportQuantityRsIndexes MeasReportQuantity OPTIONAL, — Need R
maxNrofRsIndexesToReport INTEGER (1..maxNroflndexesToReport) OPTIONAL, — Need R
includeBeamMeasurements BOOLEAN
useWhiteCellList BOOLEAN
}
NR-RS-Type :: = ENUMERATED {ssb, csi-rs}
MeasTriggerQuantity : := CHOICE {
rsrp RSRP-Range ,
rsrq RSRQ-Range ,
sinr SINR-Range
}
MeasTriggerQuantityOffset CHOICE {
rsrp INTEGER (-30..30) ,
rsrq INTEGER (-30..30) ,
sinr INTEGER (-30..30)
}
MeasReportQuantity SEQUENCE {
rsrp BOOLEAN,
rsrq BOOLEAN,
sinr BOOLEAN
}
— TAG-REPORT-CONFIG-START
— ASN1STOP
Figure imgf000029_0001
Figure imgf000030_0001
Figure imgf000031_0001
Figure imgf000031_0002
*************************************************************************************************
A possible implementation of Solution d described above (where a new RRC message can be defined for conditional handover) is the following, which shows an example of the ASN.1 code and field description of this new message (including the ReportConfigNR lEs, where the execution conditions are configured):
*************************************************************************************************
- RRCConditionalReconfiguration
The RRCConditionalReconfiguration message is the command to modify an RRC connection upon the triggering of an associated condition. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and security configuration.
Signalling radio bearer: SRB1 or SRB3
RLC-SAP: AM
Logical channel: DCCH
Direction: Network to UE
BRCCondltionalReconfignration massage
ASN1START
TAG-RRCCONDITIONALRECONFIGURATION-START
RRCcONDITIONALReconfiguration SEQUENCE {
rrc-Transactionldentifier RRC-Transactionldentifier
criticalExtensions CHOICE {
rrcConditionalReconfiguration RRCConditionalReconfiguration-IEs criticalExtensionsFuture SEQUENCE { }
RRCConditionalReconfiguration-IEs SEQUENCE { condReconfigurationList SEQUENCE (SIZE ( 1.. maxCondReconfigurations ) ) OF
CondReconfiguration,
}
CondReconfiguration :: = SEQUENCE {
rrcReconfigurationToApply RRCReconfiguration,
eventTriggerCHO ReportConfigNR,
} lateNonCriticalExtension OCTET STRING
OPTIONAL,
nonCriticalExtension RRCReconfiguration-vl530-1Es
OPTIONAL
}
— TAG- RRCCONDITIONALRECONFIGURATION -STOP
ASN1STOP
BRCReconfiguration message
— ASN1START
— TAG-RRCRECONFIGURATION-START
RRCReconfiguration : := SEQUENCE {
rrc-Transactionldentifier RRC-Transactionldentifier,
criticalExtensions CHOICE {
rrcReconfiguration RRCReconfiguration-IEs ,
criticalExtensionsFuture SEQUENCE { }
}
}
RRCReconfiguration-IEs SEQUENCE {
radioBearerConfig RadioBearerConfig OPTIONAL, — Need M
secondaryCellGroup OCTET STRING (CONTAINING CellGroupConfig ) OPTIONAL, — Need M
measConfig MeasConfig OPTIONAL, — Need M
lateNonCriticalExtension OCTET STRING
OPTIONAL,
nonCriticalExtension RRCReconfiguration-vl530-1Es
OPTIONAL
} RRCReconfiguration-vl530-IEs = SEQUENCE {
masterCe11Group OCTET STRING (CONTAINING CellGroupConfig )
OPTIONAL, — Need M
fullConfig ENUMERATED {true}
OPTIONAL, — Cond FullConfig
dedicatedNAS-MessageList SEQUENCE ( SIZE ( 1.. maxDRB ) ) OF DedicatedNAS-Message
OPTIONAL, — Cond nonHO
masterKeyUpdate MasterKeyUpdate
OPTIONAL, — Cond MasterKeyChange
dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) OPTIONAL, — Need N
dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING Systemlnformation ) OPTIONAL, — Need N
otherConfig OtherConfig OPTIONAL, — Need N
nonCriticalExtension SEQUENCE { }
OPTIONAL
}
RRCReconfiguration-vl6-IEs : := SEQUENCE {
masterCe11Group OCTET STRING (CONTAINING CellGroupConfig ) OPTIONAL, — Need M
fullConfig ENUMERATED {true}
OPTIONAL, — Cond FullConfig
dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB) ) OF DedicatedNAS-Message OPTIONAL, — Cond nonHO
masterKeyUpdate MasterKeyUpdate
OPTIONAL, — Cond MasterKeyChange
dedicatedSIBi-Delivery OCTET STRING (CONTAINING SIB1) OPTIONAL, — Need N
dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING Systemlnformation ) OPTIONAL, — Need N
otherConfig OtherConfig OPTIONAL, — Need N
nonCriticalExtension SEQUENCE { }
OPTIONAL
}
MasterKeyUpdate : := SEQUENCE {
keySetChangelndicator BOOLEAN,
nextHopChainingCount NextHopChainingCount ,
nas-Container OCTET STRING
OPTIONAL, Cond securityNASC
}
— TAG-RRCRECONFIGURATION-STOP
ASN1STOP - ReportConfigNR
The IE ReportConfigNR specifies criteria for triggering of an NR measurement reporting event. Measurement reporting events are based on cell measurement results, which can either be derived based on SS/PBCH block or CSI-RS. These events are labelled AN with N equal to 1 , 2 and so on.
Event A1 : Serving becomes better than absolute threshold;
Event A2: Serving becomes worse than absolute threshold;
Event A3: Neighbour becomes amount of offset better than PCell/PSCell;
Event A4: Neighbour becomes better than absolute threshold;
Event A5: PCell/PSCell becomes worse than absolute thresholdl AND Neighbour/SCell becomes better than another absolute threshold2.
Event A6: Neighbour becomes amount of offset better than SCell.
ReportConfigNR information element
— ASN1START
— TAG-REPORT-CONFIG-START
ReportConfigNR ::= SEQUENCE {
reportType CHOICE {
periodical PeriodicalReportConfig,
eventTriggered EventTriggerConfig, reportCGI ReportCGI
ReportCGI SEQUENCE {
cellForWhichToReportCGI PhysCellld,
EventTriggerConfig : := SEQUENCE {
eventld CHOICE {
eventAl SEQUENCE {
al-Threshold MeasTriggerQuantity
reportOnLeave BOOLEAN, hysteresis Hysteresis ,
timeToTrigger TimeToTrigger
},
eventA2 SEQUENCE {
a2-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger
},
eventA3 SEQUENCE {
a3-Offset MeasTriggerQuantityOffset , reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger,
useWhiteCellList BOOLEAN
},
eventA4 SEQUENCE {
a4-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger,
useWhiteCellList BOOLEAN
},
eventA5 SEQUENCE {
a5-Thresholdl MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger,
useWhiteCellList BOOLEAN
},
eventA6 SEQUENCE {
a6-Offset MeasTriggerQuantityOffset , reportOnLeave BOOLEAN,
hysteresis Hysteresis ,
timeToTrigger TimeToTrigger,
useWhiteCellList BOOLEAN
}, rsType NR-RS-Type reportInterval ReportInterval
reportAmount ENUMERATED {rl, r2 , r4, r8, rl6, r32, r64 , infinity} , reportQuantityCell MeasReportQuantity
maxReportCells INTEGER (1.. maxCellReport ) reportQuantityRsIndexes MeasReportQuantity
OPTIONAL, — Need R
maxNrofRSIndexesToReport INTEGER ( 1.. maxNrofIndexesToReport )
OPTIONAL, — Need R
includeBeamMeasurements BOOLEAN,
reportAddNeighMeas ENUMERATED {setup}
OPTIONAL, — Need R
}
PeriodicalReportConfig : : = SEQUENCE {
rsType NR-RS-Type, reportInterval ReportInterval ,
reportAmount ENUMERATED {rl, r2, r4, r8, rl6, r32, r64, infinity} , reportQuantityCell MeasReportQuantity,
maxReportCells INTEGER (1..maxCellReport) , reportQuantityRsIndexes MeasReportQuantity OPTIONAL, — Need R
maxNrofRSIndexesToReport INTEGER (1..maxNroflndexesToReport) OPTIONAL, — Need R
includeBeamMeasurements BOOLEAN
useWhiteCellList BOOLEAN
}
NR-RS-Type ::= ENUMERATED {ssb, csi-rs}
MeasTriggerQuantity : : = CHOICE {
rsrp RSRP-Range ,
rsrq RSRQ-Range ,
sinr SINR-Range
}
MeasTriggerQuantityOffset CHOICE {
rsrp INTEGER (-30..30) , rsrq INTEGER (-30..30) , sinr INTEGER (-30..30)
MeasReportQuantity SEQUENCE {
rsrp BOOLEAN, rsrq BOOLEAN, sinr BOOLEAN
— TAG-REPORT-CONFIG-START
— ASN1STOP
Figure imgf000038_0001
Figure imgf000039_0001
Figure imgf000039_0002
Figure imgf000040_0001
Examples related to the triggering condition of conditional mobility
The actions related to handover are in some examples triggered upon the reception of the RRC message containing HO (or mobility procedure) Command (e.g. RRCRecon figuration in NR or RRCConnectionReconfiguration in LTE). At conditional handover the RRC message triggers the action to monitor if the conditions are fulfilled instead, and no handover is performed when the message is received. The actions related to handover currently defined in 3GPP TS 36.331 in relation to“Reception of RRC(Connection)Reconfiguration” need to be expanded to“Reception of RRC(Connection) Reconfiguration of fulfillment of conditions for conditional handover”.
The following is a possible implementation for solution b / described above (where the conditional handover is configured in an RRCReconfiguration message including a field and IE indicating to the UE that this is a conditional handover, rather than a legacy handover i.e. that the UE needs monitor execution conditions) :
******************************************************************************************************* 5.3.5.3 Reception of an RRCReconfiguration by the UE
The UE shall:
1 > if the RRCReconfiguration includes the condReconfiguration and the condition is not being monitored:
2> starts to monitor the condition associated to condReconfiguration ;
2> procedure ends;
The UE shall perform the following actions upon reception of the RRCReconfiguration not including condReconfiguration or, if included, upon the triggering of the associated condition in condReconfiguration :
1 > if the RRCReconfiguration includes the fullConfig :
2> perform the radio configuration procedure as specified in 5.3.5.11 ;
1 > if the RRCReconfiguration includes the masterCellGroup·.
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1 > if the RRCReconfiguration includes the masterKeyUpdate\
2> perform security key update procedure as specified in 5.3.5.7;
1 > if the RRCReconfiguration includes the secondaryCellGroup·.
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1 > if the RRCReconfiguration message contains the radioBearerConfig·.
2> perform the radio bearer configuration according to 5.3.5.6;
1 > if the RRCReconfiguration message includes the measConfig·.
2> perform the measurement configuration procedure as specified in 5.5.2;
1 > if the RRCReconfiguration message includes the dedicatedSIBI -Delivery.
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
1 > if the RRCReconfiguration message includes the dedicatedSystemlnformationDelivery.
2> perform the action upon reception of System Information as specified in 5.2.2.4; > set the content of RRCReconfigurationComplete message as follows:
2> if the RRCRecon figuration includes the masterCellGroup containing the
reportUplinkTxDirectCurrent, or;
2> if the RRCRecon figuration includes the secondaryCellGroup containing the
reportUplinkTxDirectCurrent
3> include the uplinkTxDirectCurrentList,
> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCRecon figuration was received via SRB1 :
3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E- UTRA RRC message RRCConnectionReconfigurationComplete as specified in
TS 36.331 [10];
3> if reconfigurationWithSync was included in spCellConfig of an SCG:
4> initiate the random access procedure on the SpCell, as specified in TS 38.321
[3];
3> else:
4>the procedure ends;
NOTE: The order the UE sends the
RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2> else (RRCRecon figuration was received via SRB3):
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE: For EN-DC, in the case RRCReconfiguration is received via SRB1 , the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3, the random access is triggered by the MAC layer due to arrival of
RRCReconfigurationComplete.
> else: 2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> if this is the first RRCRecon figuration message after successful completion of the RRC re-establishment procedure:
3> resume SRB2 and DRBs that are suspended;
> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a random access procedure;
2> stop timer T304 for that cell group;
2> apply the parts of the CQI reporting configuration, the scheduling request
configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that
require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> stop timer T390, if running, for all access categories;
3> if RRCRecon figuration does not include dedicatedSIBI -Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDowniinkBWP-id for the target SpCell of the MCG, has a common search space configured by search SpaceSIB 1 :
4> acquire the SIB 1 of the target SpCell of the MCG, as specified in 5.2.2.3.1 which is scheduled as specified in TS 38.213 [13];
4> upon acquiring SIB1, perform the actions specified in section 5.2.2.4.2.
2>the procedure ends.
NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located. 5.3.5.x Triggering of condReconfiguration
Upon the triggering of the condition condReconfiguration, the UE shall:
1 > perform actions as specified in 5.3.5.3;
*******************************************************************************************************
The following is a possible implementation for solution c/ described above:
*******************************************************************************************************
5.3.5.X Reception of an RRCConditionalReconfiguration by the UE
The UE shall:
1 > store the received RRCRecon figuration messages;
1 > starts to monitor the conditions in condReconfigurationList,
5.3.5.X.1 Triggering of a condition in condReconfigurationList
The UE shall:
1 > restore the RRCRecon figuration message associated to the triggered condition;
1 > perform actions the reception of an RRCReconfiguration as specified in 5.3.5.3;
5.3.5.3 Reception of an RRCReconfiguration by the UE
The UE shall perform the following actions upon reception of the RRCReconfiguration·.
1 > if the RRCReconfiguration includes the fullConfig :
2> perform the radio configuration procedure as specified in 5.3.5.11 ;
1 > if the RRCReconfiguration includes the masterCellGroup·.
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1 > if the RRCReconfiguration includes the masterKeyUpdate\
2> perform security key update procedure as specified in 5.3.5.7;
1 > if the RRCReconfiguration includes the secondaryCellGroup·. 2> perform the cell group configuration for the SCG according to 5.3.5.5;
1 > if the RRCRecon figuration message contains the radioBearerConfig·.
2> perform the radio bearer configuration according to 5.3.5.6;
1 > if the RRCRecon figuration message includes the measConfig·.
2> perform the measurement configuration procedure as specified in 5.5.2;
1 > if the RRCRecon figuration message includes the dedicatedSIBI -Delivery·.
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
1 > if the RRCRecon figuration message includes the dedicatedSystemlnformationDelivery.
2> perform the action upon reception of System Information as specified in 5.2.2.4; 1 > set the content of RRCReconfigurationComplete message as follows:
2> if the RRCRecon figuration includes the masterCellGroup containing the
reportUplinkTxDirectCurrent, or;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the
reportUplinkTxDirectCurrent
3> include the uplinkTxDirectCurrentList,
1 > if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCReconfiguration was received via SRB1 :
3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E- UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10];
3> if reconfigurationWithSync was included in spCellConfig of an SCG:
4> initiate the random access procedure on the SpCell, as specified in TS 38.321
[3];
3> else:
4>the procedure ends;
• NOTE: The order the UE sends the
RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. 2> else ( RRCReconfiguration was received via SRB3):
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
• NOTE: For EN-DC, in the case RRCReconfiguration is received via SRB1 , the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3, the random access is triggered by the MAC layer due to arrival of
RRCReconfigurationComplete.
1 > else:
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure:
3> resume SRB2 and DRBs that are suspended;
1 > if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when
MAC of an NR cell group successfully completes a random access procedure;
2> stop timer T304 for that cell group;
2> apply the parts of the CGI reporting configuration, the scheduling request
configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that
require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CGI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> stop timer T390, if running, for all access categories;
3> if RRCReconfiguration does not include dedicatedSIBI -Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDowniinkBWP-id for the target SpCell of the MCG, has a common search space configured by search SpaceSIB 1 : 4> acquire the SIB 1 of the target SpCell of the MCG, as specified in 5.2.2.3.1 which is scheduled as specified in TS 38.213 [13];
4> upon acquiring SIB1, perform the actions specified in section 5.2.2.4.2.
2>the procedure ends.
· NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
The UE shall perform the following actions upon reception of the RRCReconfiguration not including condReconfiguration or, if included, upon the triggering of the associated condition in condReconfiguratiorr.
1 > if the RRCReconfiguration includes the fullConfig :
2> perform the radio configuration procedure as specified in 5.3.5.11 ;
1 > if the RRCReconfiguration includes the masterCellGroup·.
2> perform the cell group configuration for the received masterCellGroup according to
5.3.5.5;
1 > if the RRCReconfiguration includes the masterKeyUpdate\
2> perform security key update procedure as specified in 5.3.5.7;
1 > if the RRCReconfiguration includes the secondaryCellGroup·.
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1 > if the RRCReconfiguration message contains the radioBearerConfig·.
2> perform the radio bearer configuration according to 5.3.5.6;
1 > if the RRCReconfiguration message includes the measConfig·.
2> perform the measurement configuration procedure as specified in 5.5.2;
1 > if the RRCReconfiguration message includes the dedicatedSIBI -Delivery.
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
1 > if the RRCReconfiguration message includes the dedicatedSystemlnformationDelivery. 2> perform the action upon reception of System Information as specified in 5.2.2.4; > set the content of RRCReconfigurationComplete message as follows:
2> if the RRCRecon figuration includes the masterCellGroup containing the
reportUplinkTxDirectCurrent, or;
2> if the RRCRecon figuration includes the secondaryCellGroup containing the
reportUplinkTxDirectCurrent
3> include the uplinkTxDirectCurrentList,
> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (MCG is E-UTRA):
2> if RRCRecon figuration was received via SRB1 :
3> submit the RRCReconfigurationComplete via the EUTRA MCG embedded in E-
UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10];
3> if reconfigurationWithSync was included in spCellConfig of an SCG:
4> initiate the random access procedure on the SpCell, as specified in TS 38.321
[3];
3> else:
4>the procedure ends;
NOTE: The order the UE sends the
RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2> else (RRCRecon figuration was received via SRB3):
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE: For EN-DC, in the case RRCReconfiguration is received via SRB1 , the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3, the random access is triggered by the MAC layer due to arrival of
RRCReconfigurationComplete.
> else: 2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> if this is the first RRCRecon figuration message after successful completion of the RRC re-establishment procedure:
3> resume SRB2 and DRBs that are suspended;
> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG, and when MAC of an NR cell group successfully completes a random access procedure;
2> stop timer T304 for that cell group;
2> apply the parts of the CQI reporting configuration, the scheduling request
configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that
require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> stop timer T390, if running, for all access categories;
3> if RRCRecon figuration does not include dedicatedSIBI -Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDowniinkBWP-id for the target SpCell of the MCG, has a common search space configured by search SpaceSIB 1 :
4> acquire the SIB 1 of the target SpCell of the MCG, as specified in 5.2.2.3.1 which is scheduled as specified in TS 38.213 [13];
4> upon acquiring SIB1, perform the actions specified in section 5.2.2.4.2.
2>the procedure ends.
NOTE: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.
5.3.5.x Triggering of condReconfiguration Upon the triggering of the condition condReconfiguration , the UE shall:
1 > perform actions as specified in 5.3.5.3;
*******************************************************************************************************
The actions are, in addition to execution the actual handover, e.g. stopping of timers T310, T312 and T370 and starting of timer T304.
There can be different ways to define that the triggering condition is fulfilled:
The triggering condition is fulfilled in the UE, but no notification from the UE is sent. The actions are triggered when the condition is fulfilled.
The UE triggers an event when the triggering condition is fulfilled. The event could be the existing A3 event or a new event. When an event is triggered a MeasurementReport is sent according to existing behavior.
The UE sends a message other than MeasurementReport when the triggering condition is fulfilled. The message could be an existing RRC message or a new message or a lower layer notification.
Examples related to configuration of conditions
In some examples, the network configures conditional mobility when a certain event has been fulfilled in the UE. The A3 event is used to trigger a non-conditional handover and it can also be used to trigger conditional handover. The A3 event could be used both for triggering conditional handover and for triggering the fulfilment of the triggering condition for conditional handover. In such case two different thresholds need to be connected to the A3 event, i.e. one new threshold needs to be defined. One threshold is configured for the A3 event as in legacy (that threshold will trigger the configuration of conditional handover) and a new threshold is configured in RRCRecon figuration message in relation to the configuration of conditional handover.
Alternatively, a new event could be defined to trigger conditional mobility, i.e. there are two different events which trigger configuration of conditional handover and which trigger the fulfilment of the triggering condition. See also the examples related to triggering condition of conditional mobility. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 5. For simplicity, the wireless network of Figure 5 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ1 10, QQ1 10b, and QQ110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ1 10 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.1 1 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
Network node QQ160 and WD QQ1 10 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of 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)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such 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). Yet further examples of network nodes include 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), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
In Figure 5, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of Figure 5 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
Similarly, network node QQ160 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. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, 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 QQ160.
Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
Processing circuitry QQ170 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 QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).
In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 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 QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units
In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer- executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ1 10. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components.
In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown). Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used. Alternative embodiments of network node QQ160 may include additional components beyond those shown in Figure 5 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle- mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
As illustrated, wireless device QQ1 10 includes antenna QQ11 1 , interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ1 10, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ1 10.
Antenna QQ11 1 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ11 1 may be separate from WD QQ1 10 and be connectable to WD QQ110 through an interface or port. Antenna QQ1 1 1 , interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ11 1 may be considered an interface.
As illustrated, interface QQ114 comprises radio front end circuitry QQ1 12 and antenna QQ11 1. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ1 14 is connected to antenna QQ11 1 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ11 1 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ1 11. In some embodiments, WD QQ1 10 may not include separate radio front end circuitry QQ1 12; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ11 1. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ1 14. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ1 12 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ1 18 and/or amplifiers QQ1 16. The radio signal may then be transmitted via antenna QQ1 11. Similarly, when receiving data, antenna QQ1 11 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components.
Processing circuitry QQ120 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 WD QQ1 10 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.
As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ1 10 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120. In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ1 10, but are enjoyed by WD QQ1 10 as a whole, and/or by end users and the wireless network generally.
Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ1 10. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ1 10. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ1 10. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ1 10, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ1 10, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ1 10 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.
Figure 6 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, 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). Alternatively, 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). UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in Figure 6, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 6 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
In Figure 6, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ21 1 , memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 6, or only a subset of the components. The 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.
In Figure 6, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
In Figure 6, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ21 1 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.
Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221 , which may comprise a device readable medium.
In Figure 6, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks. Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.1 1 , CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.
The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
Figure 7 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
The functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.
During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.
As shown in Figure 7, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.
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.
In the context of NFV, virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).
Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Figure 7.
In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.
With reference to Figure 8, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ41 1 , such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491 , QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.
Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420. Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).
The communication system of Figure 8 as a whole enables connectivity between the connected UEs QQ491 , QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491 , QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ41 1 , core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.
Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 9. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510 further comprises software QQ511 , which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.
Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 9) served by base station QQ520. Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in Figure 9) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.
Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531 , which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides.
It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 9 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491 , QQ492 of Figure 8, respectively. This is to say, the inner workings of these entities may be as shown in Figure 9 and independently, the surrounding network topology may be that of Figure 8.
In Figure 9, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, power consumtion and/or connectivity and thereby provide benefits such as improved connectivity (e.g. connection reliability and/or connection continuity) and/or other benefits.
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. There may further be an optional network functionality for reconfiguring OTT connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550 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 QQ51 1 , QQ531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.
Figure 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
Figure 1 1 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 1 1 will be included in this section. In step QQ710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
Figure 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
Figure 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.
Figure 14 illustrates a schematic block diagram of an apparatus WW00 in a wireless network (for example, the wireless network shown in Figure 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device QQ110 or network node QQ160 shown in Figure 5). Apparatus WW00 is operable to carry out the example method described with reference to Figure VV and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure VV is not necessarily carried out solely by apparatus WW00. At least some operations of the method can be performed by one or more other entities.
Virtual Apparatus WW00 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause determining unit WW02, mobility procedure unit WW04, and any other suitable units of apparatus WW00 to perform corresponding functions according one or more embodiments of the present disclosure.
As illustrated in Figure 14, apparatus WW00 includes determining unit WW02 configured to determine, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition, and mobility procedure unit WW04 configured to, if the mobility procedure is not associated with a condition, carry out the mobility procedure.
The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
The following enumerated embodiments are provided as part of this disclosure.
Group A Embodiments
1. A method performed by a wireless device, the method comprising:
- determining, from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition; and
- if the mobility procedure is not associated with a condition, carrying out the mobility procedure.
2. The method of embodiment 1 , further comprising, if the mobility procedure is
associated with the condition, carrying out the mobility procedure upon determining that the condition has been met. 3. The method of embodiment 1 or 2, wherein determining whether the mobility procedure is associated with a condition comprises determining whether a flag or field in the message indicates that the mobility procedure is associated with the condition.
4. The method of any of embodiments 1 to 3, wherein determining whether the mobility procedure is associated with a condition comprises determining whether the message includes one or more information elements associated with the condition.
5. The method of embodiment 4, wherein the one or more information elements identify the condition for the mobility procedure.
6. The method of any of embodiments 1 to 5, wherein determining whether the mobility procedure is associated with a condition comprises determining a type of the message.
7. The method of any of embodiments 1 to 6, wherein the message is received from a serving cell of the wireless device.
8. The method of any of embodiments 1 to 7, wherein the mobility procedure is
associated with the condition and a candidate target cell, and the message further configures a respective mobility procedure associated with each of one or more additional candidate target cells.
9. The method of embodiment 8, wherein the message contains a plurality of RRC Reconfiguration messages, each RRC Reconfiguration message configuring the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells.
10. The method of any of embodiments 1 to 7, wherein the mobility procedure is
associated with the condition and a candidate target cell, and the method further comprises receiving the message, and receiving one or more additional messages, each additional message configuring a respective mobility procedure associated with each of one or more additional candidate target cells.
11. The method of any of embodiments 8 to 10, wherein the respective mobility
procedure associated with each of the candidate target cell and the one or more additional candidate target cells is associated with the condition. 12. The method of any of embodiments 8 to 10, wherein the respective mobility procedure associated with each of the additional candidate target cells is associated with a respective additional condition.
13. The method of any of embodiments 1 to 12, wherein the message identifies the
condition.
14. The method of any of embodiments 1 to 13, wherein the message comprises an RRC Connection Reconfiguration message or a RRC Reconfiguration message.
15. The method of any of embodiments 1 to 14, wherein the mobility procedure
comprises a handover to a target cell or a resume procedure to a candidate target cell associated with the mobility procedure.
16. The method of embodiment 15, wherein the resume procedure comprises an RRC Resume procedure.
17. The method of any of embodiments 1 to 16, wherein determining that the condition has been met comprises monitoring a parameter.
18. The method of embodiment 17, wherein determining that the condition has been met comprises determining that the parameter exceeds a threshold.
19. The method of embodiment 16 or 17, wherein the parameter comprises a signal strength of at least one candidate target cell associated with the mobility procedure at the wireless device.
20. The method of any of embodiments 1 to 19, wherein the condition comprises whether a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold.
21. The method of embodiment 20, comprising configuring the conditional mobility
procedure in response to a signal strength of a candidate target cell being greater than the signal strength of a serving cell of the wireless device by a second threshold, wherein the second threshold is lower than the first threshold.
22. The method of any of embodiments 1 to 21 , wherein determining that the condition has been met comprises determining that an A3 event has been triggered. 23. The method of embodiment 22, comprising triggering the A3 event when a signal strength of a candidate target cell is greater than a signal strength of a serving cell of the wireless device by a first threshold.
24. The method of any of the previous embodiments, further comprising:
- providing user data; and
- forwarding the user data to a host computer via the transmission to the base station.
Group B Embodiments
25. A method performed by a base station, the method comprising:
- sending a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
26. The method of embodiment 25, wherein a flag or field in the message indicates
whether the mobility procedure is associated with the condition.
27. The method of embodiment 25 or 26, wherein the message includes one or more information elements associated with the condition if the mobility procedure is associated with the condition.
28. The method of embodiment 27, wherein the one or more information elements
identify the condition for the mobility procedure.
29. The method of any of embodiments 25 to 28, wherein a type of the message
indicates whether the mobility procedure is associated with the condition.
30. The method of any of embodiments 25 to 28, wherein the mobility procedure is
associated with the condition and a candidate target cell, and the message further configures, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
31. The method of embodiment 30, wherein the message contains a plurality of RRC Reconfiguration messages, each RRC Reconfiguration message configuring, for the wireless device, the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells. 32. The method of any of embodiments 25 to 29, wherein the mobility procedure is associated with the condition and a candidate target cell, and the method further comprises sending the message, and sending one or more additional messages, each additional message configuring, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
33. The method of any of embodiments 30 to 32, wherein the respective mobility
procedure associated with each of the candidate target cell and the one or more additional candidate target cells is associated with the condition.
34. The method of any of embodiments 30 to 32, wherein the respective mobility
procedure associated with each of the additional candidate target cells is associated with a respective additional condition.
35. The method of any of embodiments 30 to 34, comprising receiving configuration details associated with each mobility procedure from a respective cell associated with the mobility procedure.
36. The method of any of embodiments 25 to 35, wherein the message identifies the condition.
37. The method of any of embodiments 25 to 36, wherein the message comprises an RRC Connection Reconfiguration message or a RRC Reconfiguration message.
38. The method of any of embodiments 25 to 37, wherein the mobility procedure
comprises a handover to a target cell or a resume procedure to a candidate target cell associated with the mobility procedure.
39. The method of embodiment 37, wherein the resume procedure comprises an RRC Resume procedure.
40. The method of any of embodiments 25 to 39, wherein the condition comprises
whether a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold.
41. The method of embodiment 40, wherein the message configures the wireless device to carry out the conditional mobility procedure in response to a signal strength of a candidate target cell being greater than the signal strength of a serving cell of the wireless device by a second threshold, wherein the second threshold is lower than the first threshold.
42. The method of any of embodiments 25 to 41 , wherein the base station is associated with a serving cell of the wireless device.
43. The method of any of the previous embodiments, further comprising:
- obtaining user data; and
- forwarding the user data to a host computer or a wireless device.
Group C Embodiments
44. A wireless device, the wireless device comprising:
- processing circuitry configured to perform any of the steps of any of the
Group A embodiments; and
- power supply circuitry configured to supply power to the wireless device.
45. A base station, the base station comprising:
- processing circuitry configured to perform any of the steps of any of the
Group B embodiments;
- power supply circuitry configured to supply power to the base station.
46. A user equipment (UE), the UE comprising:
- an antenna configured to send and receive wireless signals;
- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;
- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; - an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;
- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and
- a battery connected to the processing circuitry and configured to supply
power to the UE.
47. A communication system including a host computer comprising:
- processing circuitry configured to provide user data; and
- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),
- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
48. The communication system of the previous embodiment further including the base station.
49. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
50. The communication system of the previous 3 embodiments, wherein:
- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and
- the UE comprises processing circuitry configured to execute a client
application associated with the host application. 51. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
- at the host computer, providing user data; and
- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
52. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
53. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
54. A user equipment (UE) configured to communicate with a base station, the UE
comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
55. A communication system including a host computer comprising:
- processing circuitry configured to provide user data; and
- a communication interface configured to forward user data to a cellular
network for transmission to a user equipment (UE),
- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
56. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
57. The communication system of the previous 2 embodiments, wherein: - the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and
- the UE’s processing circuitry is configured to execute a client application associated with the host application.
58. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
- at the host computer, providing user data; and
- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
59. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.
60. A communication system including a host computer comprising:
- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,
- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
61. The communication system of the previous embodiment, further including the UE.
62. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
63. The communication system of the previous 3 embodiments, wherein: - the processing circuitry of the host computer is configured to execute a host application; and
- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. The communication system of the previous 4 embodiments, wherein:
- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and
- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. The method of the previous 2 embodiments, further comprising:
- at the UE, executing a client application, thereby providing the user data to be transmitted; and
- at the host computer, executing a host application associated with the client application. The method of the previous 3 embodiments, further comprising:
- at the UE, executing a client application; and - at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,
- wherein the user data to be transmitted is provided by the client application in response to the input data. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. The communication system of the previous embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein:
- the processing circuitry of the host computer is configured to execute a host application;
- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A
embodiments. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.
ABBREVIATIONS
At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).
1x RTT CDMA2000 1x Radio Transmission Technology
3GPP 3rd Generation Partnership Project
5G 5th Generation
ABS Almost Blank Subframe
ARQ Automatic Repeat Request
AWGN Additive White Gaussian Noise
BCCH Broadcast Control Channel
BCH Broadcast Channel
CA Carrier Aggregation
CC Carrier Component
CCCH SDUCommon Control Channel SDU
CDMA Code Division Multiplexing Access
CGI Cell Global Identifier
CIR Channel Impulse Response
CP Cyclic Prefix
CPICH Common Pilot Channel
CPICH Ec/No CPICH Received energy per chip divided by the power density in the band
CQI Channel Quality information
C-RNTI Cell RNTI
CSI Channel State Information
DCCH Dedicated Control Channel
DL Downlink
DM Demodulation
DMRS Demodulation Reference Signal
DRX Discontinuous Reception
DTX Discontinuous Transmission
DTCH Dedicated Traffic Channel
DUT Device Under Test
E-CID Enhanced Cell-ID (positioning method)
E-SMLC Evolved-Serving Mobile Location Centre
ECGI Evolved CGI eNB E-UTRAN NodeB
ePDCCH enhanced Physical Downlink Control Channel
E-SMLC evolved Serving Mobile Location Center
E-UTRA Evolved UTRA
E-UTRAN Evolved UTRAN
FDD Frequency Division Duplex
FFS For Further Study
GERAN GSM EDGE Radio Access Network
gNB Base station in NR
GNSS Global Navigation Satellite System
GSM Global System for Mobile communication
HARQ Hybrid Automatic Repeat Request
HO Handover
HSPA High Speed Packet Access
HRPD High Rate Packet Data
LOS Line of Sight
LPP LTE Positioning Protocol
LTE Long-Term Evolution
MAC Medium Access Control
MBMS Multimedia Broadcast Multicast Services
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MBSFN ABS MBSFN Almost Blank Subframe
MDT Minimization of Drive Tests
MIB Master Information Block
MME Mobility Management Entity
MSC Mobile Switching Center
NPDCCH Narrowband Physical Downlink Control Channel
NR New Radio
OCNG OFDMA Channel Noise Generator
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
OSS Operations Support System
OTDOA Observed Time Difference of Arrival
O&M Operation and Maintenance
PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel
PCell Primary Cell
PCFICH Physical Control Format Indicator Channel
PDCCH Physical Downlink Control Channel
PDP Profile Delay Profile
PDSCH Physical Downlink Shared Channel
PGW Packet Gateway
PHICH Physical Hybrid-ARQ Indicator Channel
PLMN Public Land Mobile Network
PM I Precoder Matrix Indicator
PRACH Physical Random Access Channel
PRS Positioning Reference Signal
PSS Primary Synchronization Signal
PUCCH Physical Uplink Control Channel
PUSCH Physical Uplink Shared Channel
RACH Random Access Channel
QAM Quadrature Amplitude Modulation
RAN Radio Access Network
RAT Radio Access Technology
RLM Radio Link Management
RNC Radio Network Controller
RNTI Radio Network Temporary Identifier
RRC Radio Resource Control
RRM Radio Resource Management
RS Reference Signal
RSCP Received Signal Code Power
RSRP Reference Symbol Received Power OR
Reference Signal Received Power
RSRQ Reference Signal Received Quality OR
Reference Symbol Received Quality
RSSI Received Signal Strength Indicator
RSTD Reference Signal Time Difference
SCH Synchronization Channel
SCell Secondary Cell
SDU Service Data Unit SFN System Frame Number
SGW Serving Gateway
SI System Information
SIB System Information Block
SNR Signal to Noise Ratio
SON Self Optimized Network
SS Synchronization Signal
SSS Secondary Synchronization Signal
TDD Time Division Duplex
TDOA Time Difference of Arrival
TOA Time of Arrival
TSS Tertiary Synchronization Signal
TTI Transmission Time Interval
UE User Equipment
UL Uplink
UMTS Universal Mobile Telecommunication System
USIM Universal Subscriber Identity Module
UTDOA Uplink Time Difference of Arrival
UTRA Universal Terrestrial Radio Access
UTRAN Universal Terrestrial Radio Access Network
WCDMA Wide CDMA
WLAN Wide Local Area Network

Claims

1. A method (400) performed by a wireless device, the method comprising:
- determining (402), from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition; and if the mobility procedure is not associated with a condition, carrying out (404) the mobility procedure.
2. The method of claim 1 , further comprising, if the mobility procedure is associated with the condition, carrying out the mobility procedure upon determining that the condition has been met.
3. The method of claim 2, wherein determining that the condition has been met
comprises monitoring a parameter, and determining that the parameter exceeds a threshold.
4. The method of claim 3, wherein the parameter comprises a signal strength of at least one candidate target cell associated with the mobility procedure at the wireless device.
5. The method of any of claims 1 to 4, wherein determining (402) whether the mobility procedure is associated with a condition comprises determining whether a flag or field in the message indicates that the mobility procedure is associated with the condition.
6. The method of any of claims 1 to 5, wherein determining (402) whether the mobility procedure is associated with a condition comprises determining whether the message includes one or more information elements associated with the condition, wherein the one or more information elements identify the condition for the mobility procedure.
7. The method of any of claims 1 to 6, wherein the mobility procedure is associated with the condition and a candidate target cell, and the message further configures a respective mobility procedure associated with each of one or more additional candidate target cells.
8. The method of claim 7, wherein the message contains a plurality of RRC
Reconfiguration messages, each RRC Reconfiguration message configuring the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells.
9. The method of any of claims 1 to 8, wherein the mobility procedure is associated with the condition and a candidate target cell, and the method further comprises receiving the message, and receiving one or more additional messages, each additional message configuring a respective mobility procedure associated with each of one or more additional candidate target cells.
10. The method of any of claims 1 to 9, wherein the mobility procedure comprises a handover to a target cell or a resume procedure to a candidate target cell associated with the mobility procedure.
11. The method of any of claims 1 to 10, wherein the condition comprises whether a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold.
12. The method of claim 11 , comprising configuring the conditional mobility procedure in response to a signal strength of a candidate target cell being greater than the signal strength of a serving cell of the wireless device by a second threshold, wherein the second threshold is lower than the first threshold.
13. A method (420) performed by a base station, the method comprising:
- sending (422) a message to a wireless device to configure a mobility
procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
14. The method of claim 13, wherein a flag or field in the message indicates whether the mobility procedure is associated with the condition.
15. The method of claim 13 or 14, wherein the message includes one or more
information elements associated with the condition if the mobility procedure is associated with the condition, wherein the one or more information elements identify the condition for the mobility procedure.
16. The method of any of claims 13 to 15, wherein the mobility procedure is associated with the condition and a candidate target cell, and the message further configures, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
17. The method of claim 16, wherein the message contains a plurality of RRC
Reconfiguration messages, each RRC Reconfiguration message configuring, for the wireless device, the mobility procedure associated with a respective one of the candidate target cell and the one or more additional candidate target cells.
18. The method of any of claims 13 to 17, wherein the mobility procedure is associated with the condition and a candidate target cell, and the method further comprises sending the message, and sending one or more additional messages, each additional message configuring, for the wireless device, a respective mobility procedure associated with each of one or more additional candidate target cells.
19. The method of any of claims 16 to 18, comprising receiving configuration details
associated with each mobility procedure from a respective cell associated with the mobility procedure.
20. The method of any of claims 13 to 19, wherein the message identifies the condition.
21. The method of any of claims 13 to 20, wherein the mobility procedure comprises a handover to a target cell or a resume procedure to a candidate target cell associated with the mobility procedure.
22. The method of any of claims 13 to 21 , wherein the condition comprises whether a signal strength of a candidate target cell associated with the mobility procedure is greater than a signal strength of a serving cell of the wireless device by a first threshold, and/or whether the signal strength of the candidate target cell is greater than a signal strength threshold.
23. The method of claim 22, wherein the message configures the wireless device to carry out the conditional mobility procedure in response to a signal strength of a candidate target cell being greater than the signal strength of a serving cell of the wireless device by a second threshold, wherein the second threshold is lower than the first threshold.
24. The method of any of claims 13 to 23, wherein the base station is associated with a serving cell of the wireless device.
25. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method according to any one of the preceding claims.
26. A subcarrier containing a computer program according to claim 25, wherein the
subcarrier comprises one of an electronic signal, optical signal, radio signal or computer readable storage medium.
27. A computer program product comprising non transitory computer readable media having stored thereon a computer program according to claim 25.
28. A wireless device comprising a processor and a memory, the memory containing instructions executable by the processor such that the wireless device is operable to: determine (402), from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition; and if the mobility procedure is not associated with a condition, carrying out (404) the mobility procedure.
29. The wireless device of claim 28, wherein the memory contains instructions
executable by the processor such that the wireless device is operable to perform the method of any of claims 2 to 12.
30. A base station comprising a processor and a memory, the memory containing
instructions executable by the processor such that the base station is operable to: send (422) a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
31. The apparatus of claim 30, wherein the memory contains instructions executable by the processor such that the base station is operable to perform the method of any of claims 14 to 24.
32. A wireless device configured to: determine (402), from a message configuring a mobility procedure for the wireless device, whether the mobility procedure is associated with a condition; and if the mobility procedure is not associated with a condition, carrying out (404) the mobility procedure.
33. The wireless device of claim 32, wherein the wireless device is configured to perform the method of any of claims 2 to 12.
34. A base station configured to: send (422) a message to a wireless device to configure a mobility procedure for the wireless device, wherein the mobility procedure indicates whether the mobility procedure is associated with a condition.
35. The base station of claim 34, wherein the base station is configured to perform the method of any of claims 14 to 24.
PCT/SE2019/051063 2018-11-01 2019-10-28 Mobility procedure WO2020091662A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862754198P 2018-11-01 2018-11-01
US62/754,198 2018-11-01

Publications (1)

Publication Number Publication Date
WO2020091662A1 true WO2020091662A1 (en) 2020-05-07

Family

ID=68426790

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2019/051063 WO2020091662A1 (en) 2018-11-01 2019-10-28 Mobility procedure

Country Status (1)

Country Link
WO (1) WO2020091662A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111935051A (en) * 2020-07-16 2020-11-13 Oppo广东移动通信有限公司 Method and device for detecting sequence number of synchronous signal block, terminal and storage medium
WO2022010398A1 (en) * 2020-07-10 2022-01-13 Telefonaktiebolaget Lm Ericsson (Publ) Conditional reconfiguration based on data traffic
CN115413066A (en) * 2021-05-29 2022-11-29 上海朗帛通信技术有限公司 Method and arrangement in a communication node used for wireless communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100124203A1 (en) * 2008-11-17 2010-05-20 Qualcomm Incorporated Conditional access terminal initiation of delayed handover
WO2018113661A1 (en) * 2016-12-23 2018-06-28 夏普株式会社 User mobility method and equipment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100124203A1 (en) * 2008-11-17 2010-05-20 Qualcomm Incorporated Conditional access terminal initiation of delayed handover
WO2018113661A1 (en) * 2016-12-23 2018-06-28 夏普株式会社 User mobility method and equipment
US20190380081A1 (en) * 2016-12-23 2019-12-12 Sharp Kabushiki Kaisha Method and device for user mobility

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "Signaling procedure for conditional handover", vol. RAN WG2, no. Chengdu, China; 20181008 - 20181012, 28 September 2018 (2018-09-28), XP051523648, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F103bis/Docs/R2%2D1814194%2Ezip> [retrieved on 20180928] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022010398A1 (en) * 2020-07-10 2022-01-13 Telefonaktiebolaget Lm Ericsson (Publ) Conditional reconfiguration based on data traffic
CN111935051A (en) * 2020-07-16 2020-11-13 Oppo广东移动通信有限公司 Method and device for detecting sequence number of synchronous signal block, terminal and storage medium
CN111935051B (en) * 2020-07-16 2023-07-18 Oppo广东移动通信有限公司 Method, device, terminal and storage medium for detecting sequence number of synchronous signal block
CN115413066A (en) * 2021-05-29 2022-11-29 上海朗帛通信技术有限公司 Method and arrangement in a communication node used for wireless communication

Similar Documents

Publication Publication Date Title
KR102343682B1 (en) Reporting of NSA/SA NR Indicators
US12004249B2 (en) Flexible resume and reconfigurations in multi-radio dual connectivity and standalone scenarios
EP3874813B1 (en) Mobility procedure
US20220394565A1 (en) Determining Security Keys
CN112956230A (en) Measurement configuration in NR-DC
US20240098588A1 (en) Measurement reporting for conditional handover candidates
US11317308B2 (en) Update of cell quality derivation parameters
EP3791682B1 (en) Cell id selection in multi cell id scenarios
US20230007623A1 (en) Release, Suspend and Reconfiguration in Paging
EP4014532A1 (en) Updating a pci in a du-cu split architecture
WO2020091662A1 (en) Mobility procedure
US20230284312A1 (en) Reconnection cell id in rlf report
US20220182911A1 (en) Conditional Mobility in a Wireless Communication Network
US20230068134A1 (en) Synchronization and Random Access During Connection Resume
US20220408295A1 (en) Validity Area for Early Measurement
US20220015038A1 (en) Mobile Terminated Early Data Transmission Reachability for RAN Context
WO2020153884A1 (en) Configuration of conditional mobility procedure
US11026204B2 (en) Methods providing release and re-direct message contents and UE behavior and related wireless devices
US20220369174A1 (en) Method for coordination of control plane traffic management during device reconfigurations and related apparatus
US20230308995A1 (en) User equipment positioning for new radio (nr)
WO2022214844A1 (en) Master node to enb change with sn node direct forwarding
EP4039053A1 (en) Group signalling aspects for nr-nr dual connectivity (nr-dc) and reconfiguration

Legal Events

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

Ref document number: 19797846

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19797846

Country of ref document: EP

Kind code of ref document: A1