WO2022240334A1 - Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires - Google Patents

Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires Download PDF

Info

Publication number
WO2022240334A1
WO2022240334A1 PCT/SE2022/050431 SE2022050431W WO2022240334A1 WO 2022240334 A1 WO2022240334 A1 WO 2022240334A1 SE 2022050431 W SE2022050431 W SE 2022050431W WO 2022240334 A1 WO2022240334 A1 WO 2022240334A1
Authority
WO
WIPO (PCT)
Prior art keywords
spcell
measurement
scg
event
determining
Prior art date
Application number
PCT/SE2022/050431
Other languages
English (en)
Inventor
Icaro Leonardo DA SILVA
Jens Bergqvist
Liwei QIU
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 WO2022240334A1 publication Critical patent/WO2022240334A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00698—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • 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/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point

Definitions

  • the present disclosure is generally related to wireless networks and is more particularly related to conditional reconfigurations of cells in secondary cell groups (SCGs).
  • SCGs secondary cell groups
  • 3GPP 3rd-Generation Partnership Projection
  • Rel-17 Release 17
  • Part of this work involves enhancements to multi-radio dual-connectivity (MR-DC), which allows a user equipment (UE) to be connected to multiple cells, including cells operating according to each of the LTE and NR radio access technologies (RATs).
  • MR-DC multi-radio dual-connectivity
  • UE user equipment
  • RATs radio access technologies
  • MN master node
  • CPC conditional PSCell change
  • the T-SN determines the exact target candidate cells and provides the MN, in the S-NODE ADDITION REQUEST ACK, a RRCReconfiguration** per target candidate, including the SCG RRCReconfiguration (with the SCG reconfiguration with sync for CPC).
  • SCG stands for Secondary Cell Group or Second Cell Group.
  • the MN needs to generate the CPC configuration (shown as a Conditional PSCell Addition, CPA, in the figure) per target candidate, including that RRCReconfiguration** and the execution condition, which comprises one or two measurement identifier(s) associated to measId(s) configured in MeasConfig.
  • the conditional reconfiguration event of the 2 MeasId may have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold.
  • Table – ReportConfigNR Sectional reconfiguration candidate becomes amount of offset better than PCell/PSCell;
  • CondEvent A5 PCell/PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2;
  • ReportConfigNR SEQUENCE ⁇ reportType CHOICE ⁇
  • Cosmetic condTriggerConfig-r16 CondTriggerConfig-r16
  • Solution CondTriggerConfig-r16 SEQUENCE ⁇ condEventId CHOICE ⁇ condEventA3 SEQUENCE ⁇ a3-Offset MeasTriggerQuantityOffset, hysteresis Hysteresis, timeToTrigger TimeToTrigger ⁇ ,
  • Conditional PSCell Addition/Change CPAC
  • Proposal set 1B trigger/ condition related 11
  • A3/A5 execution condition should be supported while for conditional PSCell addition, A4/B1 like execution condition should be supported. 12 Allow having multiple triggering conditions (using “and”) for CPAC execution of a single candidate cell. Only single RS type per CPAC candidate is supported.
  • triggering quantities e.g., RSRP and RSRQ, RSRP and SINR, etc.
  • MN-initiated CPC the execution conditions (MeasId(s)) are determined by the MN, are configured in MN format, and refer to an MCG MeasConfig. That is evidenced by the agreement that says the following: 8a
  • UE upon reception of RRCReconfiguration/RRCConnectionReconfiguration message with CPAC configuration, UE responds with RRCReconfigurationComplete/RRCConnectionReconfigurationComplete message to the MN to inform that the message has been received.
  • the message does not include an embedded RRC complete message for source SN.
  • the RRCReconfigurationComplete does not include an embedded RRC complete message for source SN, it means the UE has not been configured with an SCG MeasConfig for the measId(s) associated to the execution condition(s).
  • the A3/A5 events configured for the UE would refer to the PCell as the serving cell. This is not useful for CPC.
  • an event A3 according to current specs would compare the target candidate with the PCell, with the condition being fulfilled if the target candidate in the PSCell frequency becomes better than the PCell, which is of no use, since, in fact, the intended behavior for executing CPC is when the target candidate in the PSCell frequency becomes better than the PSCell.
  • the UE determines that the measurement event is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG), performs (at least) measurements on the SpCell of the SCG (e.g., PSCell RSRP, PSCell RSRQ, PSCell SINR), and evaluates the execution condition(s) associated to the configured event based on the measurements on the SpCell of the Second Cell Group.
  • RSRP the Special Cell
  • SpCell Special Cell
  • SCG Second Cell Group
  • some embodiments of the techniques described herein include a method performed by a user equipment (UE) for conditional reconfiguration, where the method comprises receiving, from a network node, a message including a conditional PSCell change configuration, the message including, for at least one target candidate, a target candidate configuration and an execution condition associated to a measurement event.
  • This example method further comprises determining that the measurement event is based on a measurement of an SpCell of an SCG, for the user equipment, and performing measurements on the SpCell of the SCG.
  • This example method further comprises evaluating the execution condition, based on the measurements of the SpCell of the SCG, to determine whether to perform reconfiguration according to the target candidate configuration.
  • a wireless terminal also called a User Equipment (UE)
  • the method comprises receiving from the network a message including a CPC configuration comprising i) a target candidate configuration (per target candidate); ii) an execution condition associated to a measurement event (e.g., Conditional A3, Conditional A5), per target candidate, and including information enabling the UE to determine that the measurement event is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG).
  • RSRP Radio Resource Retention
  • SpCell Special Cell
  • SCG Second Cell Group
  • This example method also comprises determining that the measurement event is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG), performing (at least) measurements on the SpCell of the SCG; and evaluating the execution condition(s) associated to the configured event, based on the measurements on the SpCell of the Second Cell Group.
  • This method may further comprise, upon fulfillment of the execution condition(s), applying the target candidate configuration, executing CPC, and transmitting an RRC Reconfiguration Complete to the network.
  • MR-DC Multi-Radio Dual Connectivity
  • a network node operating as Master Node for a UE in Multi-Radio Dual Connectivity (MR-DC), which may be a gNodeB
  • the method comprising transmitting to the UE a message including a CPC configuration comprising i) a target candidate configuration (per target candidate); ii) an execution condition associated to a measurement event (e.g., Conditional A3, Conditional A5), per target candidate, and including information enabling the UE to determine that the measurement event is based on at least one measurement type (e.g., RSRP) of the SpCell of the Second Cell Group.
  • RSRP measurement type of the SpCell of the Second Cell Group
  • An example UE for conditional reconfiguration comprises, for instance, transmitter and receiver circuitry and processing circuitry operatively coupled to the transmitter and receiver circuitry, where the processing circuitry is configured to receive from a network node, via the receiver circuitry, a message including a conditional PSCell change configuration, the message including, for at least one target candidate, a target candidate configuration and an execution condition associated to a measurement event.
  • the processing circuitry is further configured to determine that the measurement event is based on a measurement of an SpCell of an SCG for the user equipment, perform measurements on the SpCell of the SCG, and evaluate the execution condition, based on the measurements of the SpCell of the SCG, to determine whether to perform reconfiguration according to the target candidate configuration.
  • FIG. 1 illustrates a signaling flow for a MN-CPC.
  • Figure 2 illustrates a signaling flow for a CPC according to some embodiments of the presently disclosed invention.
  • Figure 3 is a process flow diagram illustrating an example method according to some embodiments.
  • Figure 4 is another process flow diagram illustrating an example method as performed by a network node, according to some embodiments.
  • Figure 5 illustrates an example communication system in which embodiments of the present invention may be employed.
  • Figure 6 illustrates components of an example UE, according to some embodiments.
  • Figure 7 illustrates components of an example network node, according to some embodiments.
  • Figure 8 is a block diagram of a host server, according to some embodiments.
  • Figure 9 shows a virtualization environment.
  • Figure 10 illustrates example communications between a UE, network node, and host. DETAILED DESCRIPTION
  • different solutions are described for providing suitable information to the UE.
  • the UE determines to use PSCell for the events for CPC based on the inclusion of explicit signaling and/or the inclusion of a boolean FLAG set to TRUE.
  • One benefit of this explicit solution is that it allows the UE to apply the compliance check of the target candidate configuration only upon execution, as the determination step does not require the UE to check the content of the target candidate configuration upon CPC configuration (which may lead to a faster CPC configuration, due to lower processing delay).
  • the UE determines to use PSCell for the events for CPC based on the UE determining that the conditional reconfiguration is for CPC.
  • a benefit of this approach is that there is no need to define a new flag in specifications, and consequently there is no need to transmit this new flag to the UE to indicate that SpCell to be considered in the event is the PSCell.
  • this solution requires the UE to check the content target candidate configuration upon CPC configuration.
  • the benefit is reduced UE impact, i.e., no additional complexity at the UE and reuse of existing procedures.
  • the disclosed techniques it is possible to execute CPC towards a target PSCell according to the criteria that takes in account measurements on the PSCell, and not on the PCell. That prevents, for example, the UE executing CPC to a cell that is not the best in a serving frequency, as the PSCell serving frequency is different form the PCell serving frequency.
  • the UE determines to use PSCell for the events for CPC based on the inclusion of the explicit signaling and/or the inclusion of a boolean FLAG set to TRUE.
  • the explicit solution allows the UE to apply the compliance check of the target candidate configuration only upon execution, as the determination step does not require the UE to check the content of the target candidate configuration upon CPC configuration (which may lead to a faster CPC configuration, due to lower processing delay).
  • the UE determines to use PSCell for the events for CPC based on the UE determining that the conditional reconfiguration is for CPC.
  • a benefit of this approach is that there is no need to define a new flag in specifications, and consequently there is no need to transmit this new flag to the UE to indicate that SpCell to be considered in the event is the PSCell. However, that would require the UE to check the content target candidate configuration upon CPC configuration.
  • MN Master Node
  • MCG Master Cell Group
  • CU-gNB Central Unit gNodeB
  • CU-eNB Central Unit eNodeB
  • CPC Conditional PSCell Change
  • conditional reconfiguration or Conditional Configuration (since the message that is stored and applied upon fulfillment of a condition is an RRCReconfiguration or RRCConnectionReconfiguration).
  • conditional handover CHO
  • CPA Conditional PSCell Change
  • the document refers to a Conditional SN Change most of the time, to refer to the procedure from the UE perspective, to refer to procedures between network nodes wherein a node requests a target candidate SN (which may be the same as the Source SN or a neighbour SN) to configure a conditional PSCell Change (CPC) for at least one of its associated cells (cell associated to the target candidate SN).
  • CPC conditional PSCell Change
  • CPA conditional PSCell Change
  • Measurement event may correspond to an event whose entering conditions and/or leaving conditions have measurement results as input, as defined in 3GPP TS 38.331 in section 5.5.4, such as section 5.5.4.4 for Event A3 (Neighbour becomes offset better than SpCell) and section 5.5.4.6 for Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2).
  • a measurement event may be configured in Radio Resource Control (RRC), in the Information Element (IE) ReportConfigNR, and for the case of Conditional PSCell Change (CPC), the measurement events may be defined as follows: - CondEvent A3: Conditional reconfiguration candidate becomes amount of offset better than PCell/PSCell; - CondEvent A5: PCell/PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2;
  • the configuration of CPC refers to a conditional configuration or conditional reconfiguration. The principle for the configuration is the same with configuring triggering/execution condition(s) and a reconfiguration message to be applied when the triggering condition(s) are fulfilled.
  • CondConfigToAddModList The IE CHO-ConfigToAddModList concerns a list of conditional configurations to add or modify, with for each entry the cho-ConfigId and the associated condExecutionCond and condRRCReconfig.
  • CondConfigToAddModList-r16 :: SEQUENCE (SIZE (1..
  • CondConfigToAddMod-r16 CondConfigToAddMod-r16 :: SEQUENCE ⁇ condConfigId-r16 CondConfigId-r16, condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need S condRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Need S ... ⁇ -- TAG-CONDCONFIGTOADDMODLIST-STOP -- ASN1STOP************* end 3GPP specification excerpt**************** There can be different solutions for the problems described above.
  • a method at a wireless terminal also called a User Equipment (UE) comprises the UE receiving, from the network, a message including a CPC configuration, where the CPC configuration includes i) a target candidate configuration (per target candidate) and ii) an execution condition associated to a measurement event, where the measurement event can be an event based on measurements performed on the Special Cell (SpCell) of the Secondary Cell Group (SCG) i.e., the PSCell (Primary Secondary Cell Group cell).
  • SpCell Special Cell
  • SCG Secondary Cell Group
  • the method comprises more than one event being associated to the execution conditions (i.e., two measId(s) configured in an execution condition, e.g., cond Event A3 AND cond Even A5, or condEvent A3 based on RSRP AND cond Event A5 based on RSRQ).
  • the measurement event is a Conditional A3 event, configured as part of the MCG MeasConfig, but referring to the PSCell, i.e., CondEvent A3: Conditional reconfiguration candidate becomes amount of offset better than PSCell.
  • the CondEvent A3 is configured in MCG MeasConfig, the SpCell the UE shall consider is the PSCell (and not the PCell as in legacy).
  • the UE shall: 1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled; 1> use the SpCell for Mp, Ofp and Ocp. If a Cond A3 is configured in the MCG MeasConfig, but for CPC, the SpCell is the PSCell. NOTE 1: The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR.
  • Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
  • Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e., offsetMO as defined within measObjectNR corresponding to the neighbour cell).
  • Ocn is the cell specific offset of the neighbour cell (i.e., cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
  • Mp is the measurement result of the SpCell, not taking into account any offsets. If a Cond A3 is configured in the MCG MeasConfig, but for CPC, the SpCell is the PSCell. Ofp is the measurement object specific offset of the SpCell (i.e., offsetMO as defined within measObjectNR corresponding to the SpCell). If a Cond A3 is configured in the MCG MeasConfig, but for CPC, the SpCell is the PSCell.
  • Ocp is the cell specific offset of the SpCell (i.e., cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell. If a Cond A3 is configured in the MCG MeasConfig, but for CPC, the SpCell is the PSCell. Hys is the hysteresis parameter for this event (i.e., hysteresis as defined within reportConfigNR for this event). Off is the offset parameter for this event (i.e., a3-Offset as defined within reportConfigNR for this event).
  • Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS- SINR. Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.
  • Event A3 also applies to CondEvent A3. If a Cond A3 is configured in the MCG MeasConfig, but for CPC, the SpCell is the PSCell.
  • the measurement event may be a Conditional A5 event, configured as part of the MCG MeasConfig, but referring to the PSCell, i.e., CondEvent A5: PSCell becomes worse than absolute threshold1 AND Conditional reconfiguration candidate becomes better than another absolute threshold2.
  • CondEvent A5 PSCell becomes worse than absolute threshold1
  • Conditional reconfiguration candidate becomes better than another absolute threshold2.
  • the UE shall: 1> consider the entering condition for this event to be satisfied when both condition A5- 1 and condition A5-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e., at least one of the two, as specified below, is fulfilled; 1> use the SpCell for Mp.
  • the SpCell is the PSCell.
  • the parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell.
  • Mp is the measurement result of the NR SpCell, not taking into account any offsets. If a Cond A5 is configured in the MCG MeasConfig, but for CPC, the SpCell is the PSCell. Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
  • Ocn is the cell specific offset of the neighbour cell (i.e., cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.
  • Hys is the hysteresis parameter for this event (i.e., hysteresis as defined within reportConfigNR for this event).
  • Thresh1 is the threshold parameter for this event (i.e., a5-Threshold1 as defined within reportConfigNR for this event).
  • Thresh2 is the threshold parameter for this event (i.e., a5-Threshold2 as defined within reportConfigNR for this event).
  • Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS- SINR.
  • Ocn, Hys are expressed in dB.
  • Thresh1 is expressed in the same unit as Mp.
  • Thresh2 is expressed in the same unit as Mn.
  • the definition of Event A5 also applies to CondEvent A5. If a Cond A5 is configured in the MCG MeasConfig, but for CPC, the SpCell is the PSCell.
  • the measurement event may be a Conditional Ax event, configured as part of the MCG MeasConfig, but referring to the PSCell wherein at least one PSCell measurement (e.g., PSCell RSRP, PSCell RSRQ, PSCell SINR) is compared with a threshold and/or with a measurement of another cell such as a neighbour cell in the same frequency as the PSCell, a neighbour cell in another frequency than the PSCell, a neighbour cell in the PCell frequency. If a Cond Ax is configured in the MCG MeasConfig, but for CPC, the SpCell is the PSCell.
  • PSCell measurement e.g., PSCell RSRP, PSCell RSRQ, PSCell SINR
  • the measurement event may be a Conditional Ax event that refers to an SCell, configured as part of the MCG MeasConfig, but referring to the SCell of the SCG where at least one measurement of an SCell of the SCG (e.g., SCell-SCG RSRP, SCell-SCG RSRQ, SCell-SCG SINR) is compared with a threshold and/or with a measurement of another cell such as a neighbour cell in the same frequency as the SCell, a neighbour cell in another frequency than the SCell, a neighbour cell in a serving frequency.
  • the SpCell is the PSCell.
  • an execution condition can be configured as two measId(s), i.e., it may refer to two measurement events, so that the execution condition is considered to be fulfilled only when both events are considered to be simultaneously configured.
  • the conditional reconfiguration event of the 2 MeasId may have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold.
  • All references to the SpCell in all configured events combined for that execution conditions shall consider the PSCell, if the MeasId(s) for CPC are configured in the MCG MeasConfig and the UE determines these refer to a CPC configuration, i.e., the measId(s) are associated to execution conditions for CPC.
  • the UE may be configured in the MCG MeasConfig with two measId(s) for a given execution condition for CPC (e.g., MN-initiated), which may be two Cond Event A3 instances, one for RSRP and another for RSRQ so that the UE considers SpCell measurements as PSCell measurements (despite that being configured in MCG MeasConfig) i.e., the UE perform PSCell RSRP measurements for the first instance of Cond A3 and PSCell RSRQ measurements for the second instance of Cond A3.
  • CPC e.g., MN-initiated
  • MN-initiated may be two Cond Event A3 instances, one for RSRP and another for RSRQ so that the UE considers SpCell measurements as PSCell measurements (despite that being configured in MCG MeasConfig) i.e., the UE perform PSCell RSRP measurements for the first instance of Cond A3 and PSCell RSRQ measurements
  • the UE may be configured in the MCG MeasConfig with two measId(s) for a given execution condition for CPC (e.g., MN-initiated), which may be one Cond Event A3 instance and one Cond Event A5. Then, SpCell is considered the PSCell in both of the events.
  • CPC e.g., MN-initiated
  • reference to the SpCell in the configured events combined for that execution conditions shall consider the PSCell only for Cond Event 3 (or instances of event Cond Event A3), if the MeasId(s) for CPC are configured in the MCG MeasConfig and the UE determines these refer to a CPC configuration i.e., the measId(s) are associated to execution condition for CPC.
  • the UE may be configured in the MCG MeasConfig with two measId(s) for a given execution condition for CPC (e.g., MN-initiated), which may be one Cond Event A3 and one Cond Event A1 (Serving becomes better than absolute threshold).
  • SpCell in Cond Event A3 refers to the PSCell
  • the “Serving” in Event A1 refers to the PCell (which is the SpCell of the cell group wherein that has been configured, the MCG).
  • the UE may be configured in the MCG MeasConfig with two measId(s) for a given execution condition for CPC (e.g., MN-initiated), which may be one Cond Event A3 and one Cond Event A2 (Serving becomes worse than absolute threshold).
  • SpCell in Cond Event A3 refers to the PSCell
  • the “Serving” in Event A2 refers to the PCell (which is the SpCell of the cell group wherein that has been configured, the MCG).
  • Explicit Solution via UE Signaling One category of embodiments utilizes explicit signaling.
  • An example method comprises the UE receiving a message configuring CPC (e.g., RRCReconfiguration, RRCConnectionReconfiguration, RRCResume, RRCConnectionResume), the message including information enabling the UE to determine that the measurement event is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG), and the UE determining that the measurement event is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG).
  • CPC configuring CPC
  • the information enabling the UE to determine that the measurement event is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG), is an explicit signaling, i.e., field (e.g., of BOOLEAN type) and/or parameter and/or an information element (IE) in the IE MeasConfig, received by the UE as part of the MCG MeasConfig (i.e., not received in a container for SCG Reconfiguration(s)).
  • the explicit signaling can be configured in the IE MeasConfig, e.g., and stored in the UE variable associated to the MCG MeasConfig.
  • One example of the explicit signaling is a field (e.g., named pscell-cpc-r17) of IE BOOLEAN, that can be part of the IE for reporting configurations, such as ReportConfigNR, that is received by the UE in an RRCReconfiguration as part of the MCG configuration (i.e., as part of the MCG MeasConfig), where a value set to TRUE indicates that the UE shall consider as SpCell the PSCell instead of the PCell, as shown below:*************** begin proposed specification excerpt
  • ReportConfigNR SEQUENCE ⁇ reportType CHOICE ⁇
  • the explicit signaling may be configured in ReportConfigNR, but within the configured event (e.g., Cond Event A5, Cond Event A3), to indicate that the explicit signaling is only valid for that particular event. That would allow an event combination for CPC wherein one event instance refers to the SpCell as the PSCell and another event instance refers to the SpCell as the PCell, which is also comprised by the method.
  • ReportConfigNR information element -- ASN1START -- TAG-REPORTCONFIGNR-START
  • ReportConfigNR SEQUENCE ⁇ reportType CHOICE ⁇
  • CondTriggerConfig-r16 CondTriggerConfig-r16
  • Cosmetic CondTriggerConfig-r16 SEQUENCE ⁇ condEventId CHOICE ⁇ condEventA3
  • condEventA5 SEQUENCE ⁇ a5-Threshold1 MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, hysteresis Hysteresis,
  • the method upon determining based on the received explicit signaling (e.g., pscell-cpc shown above or equivalent) that the measurement event to be performed is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG), the method comprises performing (at least) measurements on the SpCell of the SCG based on the received explicit signaling.
  • the UE based on the explicit signaling received in the MCG MeasConfig, the UE perform PSCell measurements when it is required to perform SpCell measurements for the configured event.
  • the SpCell is the PSCell.
  • Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
  • Ofn is the measurement object specific offset of the neighbour cell (i.e., offsetMO as defined within measObjectNR corresponding to the neighbour cell).
  • Ocn is the cell specific offset of the neighbour cell (i.e., cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.
  • Hys is the hysteresis parameter for this event (i.e., hysteresis as defined within reportConfigNR for this event).
  • Thresh1 is the threshold parameter for this event (i.e., a5-Threshold1 as defined within reportConfigNR for this event).
  • Thresh2 is the threshold parameter for this event (i.e., a5-Threshold2 as defined within reportConfigNR for this event).
  • Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS- SINR. Ofn, Ocn, Hys are expressed in dB.
  • Thresh1 is expressed in the same unit as Mp.
  • Thresh2 is expressed in the same unit as Mn.
  • the definition of Event A5 also applies to CondEvent A5.
  • Ocn is the cell specific offset of the neighbour cell (i.e., cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
  • Mp is the measurement result of the SpCell, not taking into account any offsets. If pscell-cpc-r17 is present, the SpCell is the PSCell. Ofp is the measurement object specific offset of the SpCell (i.e., offsetMO as defined within measObjectNR corresponding to the SpCell). If pscell-cpc-r17 is present, the SpCell is the PSCell.
  • Ocp is the cell specific offset of the SpCell (i.e., cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell. If pscell-cpc-r17 is present, the SpCell is the PSCell. Hys is the hysteresis parameter for this event (i.e., hysteresis as defined within reportConfigNR for this event). Off is the offset parameter for this event (i.e., a3-Offset as defined within reportConfigNR for this event). Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS- SINR.
  • the UE if the entry condition(s) applicable for this event associated with the condReconfigId, i.e., the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, where the event refers to an SpCell and pscell-cpc-r17 is set to TRUE/ is configured, the UE considers the PSCell as the SpCell, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig, the UE considers the event associated to that measId to be fulfilled.
  • the conditional reconfiguration event of the 2 MeasId may have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold.
  • ********** end proposed specification excerpt may comprise, upon fulfillment of the execution condition(s), applying the target candidate configuration, executing CPC, and transmitting an RRC Reconfiguration Complete to the network.
  • the explicit signaling which enables the UE to determine that the measurement event is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG), may be a field that indicates what type of reconfiguration that the conditional reconfiguration concerns.
  • conditional-reconfiguration-type-r17 with values including e.g., “CPC”, “CHO” and/or “CPA”.
  • it may also include a value indicating that the conditional reconfiguration concerns more than one of these types, e.g., both “CHO” and “CPC” or both “CHO” and “CPA”, to support cases where the conditional reconfiguration includes that the UE performs both a HO and a PSCell change or addition, when the execution conditions are fulfilled.
  • the field (e.g., conditional-reconfiguration-type-r17) may e.g., be included in the IE MeasConfig and stored in the UE variable associated to the MCG MeasConfig, e.g., in the ReportConfigNR. In one example it is configured in ReportConfigNR, but within the configured event (e.g., Cond Event A5, Cond Event A3).
  • the configured event e.g., Cond Event A5, Cond Event A3
  • the explicit signaling indicates whether CPC is MN-initiated CPC (for which the measId(s) in the execution condition refer to the SCG MeasConfig even though the configuration is provided in the MCG format and in the existing field for the execution condition i.e., not the new field with transparent value generated by the S-SN).
  • Implicit Solution via UE Signaling Another category of embodiments utilizes implicit signaling to the UE.
  • the information enabling the UE to determine that the measurement event is based on at least one measurement type (e.g., RSRP) of the Special Cell (SpCell) of the Second Cell Group (SCG), is an implicit signaling that indicates to the UE that the conditional reconfiguration is for Conditional PSCell Change (CPC).
  • CPC Conditional PSCell Change
  • the UE determines that the conditional reconfiguration, possibly received as an MN Reconfiguration (i.e., received via MN via SRB1, and in MN format, and not as an SCG configuration), is a Release-17 CPC solution, in particular, MN-initiated CPC.
  • the UE determines that the conditional reconfiguration is a CPC configuration by determining that the target candidate configuration to be applied upon execution (i.e., the RRCReconfiguration configured in condRRCReconfig of IE OCTET STRING (CONTAINING RRCReconfiguration)) contains a reconfiguration for the PSCell, i.e., it contains an SCG RRCReconfiguration including a reconfiguration with sync for the SCG (transmitted in a series of nested IEs, such as ReconfigurationWithSync, ServingCellConfig, CellGroupConfig referring to the SCG).
  • the UE determines that the CondConfigToAddMod is for CPC if the stored condRRCReconfig (stored RRCReconfiguration for target candidate) contains a secondaryCellGroup (of IE CellGroupConfig) including the IE ReconfigurationWithSync (transmitted in a series of nested IE(s)/fields e.g., spCellConfig of IE SpCellConfig), as shown below:************ begin proposed specification excerpt
  • RRCReconfiguration-IEs SEQUENCE ⁇
  • the UE determines that the CondConfigToAddMod is for CPC if the stored condRRCReconfig (stored RRCReconfiguration for target candidate) contains a mrdc-SecondaryCellGroupConfig.
  • the UE does only need to check the parts of the target candidate configuration that are in MN format, as the field mrdc-SecondaryCellGroupConfig is still in MN format (but its content are in SN format).
  • the UE needs to determine within that field, which includes a message in SN format (which might be from a different RAT), which may increase a bit the complexity and/or the processing time.
  • a message in SN format which might be from a different RAT
  • An example of how this may be implemented in RRC is shown below for the Cond event A3:*************** begin proposed specification excerpt****************
  • the UE shall: 1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled; 1> use the SpCell for Mp, Ofp and Ocp.
  • a Cond A3 is for stored condRRCReconfig that contains a ReconfigurationWithSync for the secondaryCellGroup
  • the SpCell is the PSCell.
  • the cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR.
  • Inequality A3-1 Entering condition
  • Inequality A3-2 (Leaving condition) Mn + Ofn + Ocn + Hys ⁇ Mp + Ofp + Ocp + Off
  • Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
  • Ocn is the measurement object specific offset of the reference signal of the neighbour cell (i.e., offsetMO as defined within measObjectNR corresponding to the neighbour cell).
  • Ocn is the cell specific offset of the neighbour cell (i.e., cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
  • Mp is the measurement result of the SpCell, not taking into account any offsets. If a Cond A3 is for stored condRRCReconfig that contains a ReconfigurationWithSync for the secondaryCellGroup, the SpCell is the PSCell.
  • Ofp is the measurement object specific offset of the SpCell (i.e., offsetMO as defined within measObjectNR corresponding to the SpCell).
  • the SpCell is the PSCell.
  • Ocp is the cell specific offset of the SpCell (i.e., cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell.
  • the SpCell is the PSCell.
  • Hys is the hysteresis parameter for this event (i.e., hysteresis as defined within reportConfigNR for this event).
  • Off is the offset parameter for this event (i.e., a3-Offset as defined within reportConfigNR for this event).
  • Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS- SINR. Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.
  • the definition of Event A3 also applies to CondEvent A3. If a Cond A3 is for stored condRRCReconfig that contains a ReconfigurationWithSync for the secondaryCellGroup, the SpCell is the PSCell.
  • method utilizing the implicit signaling approach further comprise evaluating the execution condition(s) associated to the configured event based on the measurements on the SpCell of the Second Cell Group, where the UE determines that conditions are based on measurements on the PScell as the SpCell based on the UE determining that the conditional reconfiguration is for CPC, e.g., according to at least one of the described above.
  • the UE considers the PSCell as the SpCell, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig, consider the event associated to that measId to be fulfilled.
  • the UE shall: 1>for each condReconfigId within the VarConditionalReconfig: 2>consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync in the received condRRCReconfig to be applicable cell; 2>for each measId included in the measIdList within VarMeasConfig indicated in the condExecutionCond associated to condReconfigId: 3> if the stored condRRCReconfig associated to condReconfigId includes a secondaryCellGroup and a reconfigurationWithSync in spCellConfig: 4> consider the SpCell as the PSCell in the event; 3> if the entry condition(s) applicable for this event associated with the condReconfigId, i.e., the event corresponding with the condEventI
  • conditional reconfiguration event of the 2 MeasId may have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold.
  • methods utilizing any of the implicit signaling approaches described here may further comprise, upon fulfillment of the execution condition(s), applying the target candidate configuration, executing CPC, and transmitting an RRC Reconfiguration Complete to the network.
  • the UE performs the above actions, i.e., considers the SpCell to be the PSCell, only if the target candidate configuration to be applied upon execution only includes a ReconfigurationWithSync for the Secondary Cell Group.
  • the UE may, in some examples, consider the SpCell to be the PCell for some of the measurements/events/evaluations. In one alternative, the UE may then consider the SpCell to be the PCell for some measurements/events/evaluations and the SpCell to be the PSCell for some measurements/events/evaluations.
  • the UE may then e.g., determine to consider the SpCell to be the PCell or the PSCell based on the order of the configurations of the conditions/events, e.g., so that for the first condition/event the UE considers the SpCell to be the PCell whereas for the second condition/event the UE considers the SpCell to be the PSCell.
  • the UE may consider that the conditional reconfigurations (i.e., the target candidate configuration) to be applied upon execution concern a CPC based on another indication than the reconfiguration with sync for the SCG.
  • the target candidate configuration may then include another indication that the UE may determine that the configuration e.g., concerns a CPC. In these alternatives to the above embodiments, the UE may then use such indication to determine that it shall consider the SpCell to be the PSCell for the measurements/events/evaluations.
  • the UE relies on a new configuration for the execution condition (e.g., field, parameter, IE) that indicates that the UE shall consider that the associated measurement identities (one or two MeasId(s)) as being configured in the SCG MeasConfig.
  • This new configuration for the execution condition is primarily defined for SN-initiated CPC wherein the SN is responsible for setting execution conditions with MeasId(s) referred in the SCG MeasConfig, however, according to the method, the existence of such a new configuration for the execution condition is exploited by the MN to configured MN-initiated CPC.
  • the MN may configure the UE with the signaling as shown above also for MN-initiated CPC.
  • the MN configures the UE with MN-initiated CPC including a new configuration for the execution condition (corresponds to condExecutionCond2-r17) that indicates to the UE that the associated MeasId(s) are configured in the SCG MeasConfig, wherein the MN generates the CPC configuration and the SCG MeasConfig with SN assistance.
  • An example signaling flow diagram is shown in Figure 2.
  • the MN transmits a request to the SN the SN to generate an SCG MeasConfig (e.g., in an SCG RRC Reconfiguration), the request including the configuration the MN requires i.e., the measId, measObject, reportConfig and their mappings;
  • the request including an indicator with enumerated value, e.g., true, over Xn to request for generation of SCG MeasConfig.
  • the MN receives from the SN the SCG MeasConfig (e.g., in an SCG RRC Reconfiguration), including the CPC related measConfig i.e., the configuration of the MeasId(S) and associations to reportConfig and measObject; - As shown at step 3, the MN sends an SN Addition Request (for CPC) to the SN.
  • SCG MeasConfig e.g., in an SCG RRC Reconfiguration
  • the CPC related measConfig i.e., the configuration of the MeasId(S) and associations to reportConfig and measObject
  • the MN receives an SN Addition Request Acknowledgment, including target candidates configurations; - MN generates the CPC configuration, including per target candidate the new execution condition (condExecutionCond2-r17) for indicating to the UE that mesaId(s) refer to the SCG MeasConfig; o That includes additional steps of the MN requesting CPC to target candidate nodes (SN Addition Request from MN to SN candidate(s)), and receiving in the SN Addition Request Ack the target candidate configuration(s), to also be included in the CPC configuration per target candidate. - As shown at steps 4a and 5, the MN provides the CPC configuration to the UE.
  • the MN configures the UE with MN-initiated CPC including a new configuration for the execution condition (corresponds to condExecutionCond2-r17) that indicates to the UE that the associated MeasId(s) are configured in the SCG MeasConfig, wherein the MN generates the CPC configuration and the SCG MeasConfig without SN assistance.
  • the MN generates SCG MeasConfig (in SN format) as described in the previous set of embodiments, so that the UE interprets as if these would have been SCG configurations.
  • Figure 3 illustrates an example method, as might be carried out by a user equipment (UE) or, more generally, a wireless device, for conditional reconfiguration.
  • UE user equipment
  • This method may be considered a generalization of all of the above-described techniques for execution by a UE, and thus all of the variations described above should be considered as applying to this illustrated method. Note that where there are minor differences in terminology, slightly different terms or slightly different phrasings should be understood as interchangeable, unless the context indicates otherwise.
  • the illustrated method includes, as shown at block 310, the step of receiving, from a network node, a message including a conditional PSCell change configuration, the message including, for at least one target candidate, a target candidate configuration and an execution condition associated to a measurement event.
  • the method further comprises, as shown at block 320, determining that the measurement event is based on a measurement of a Special Cell (SpCell) of a Secondary Cell Group (SCG) for the user equipment.
  • the method further comprises performing measurements on the SpCell of the SCG, as shown at block 330, and, as shown at block 340, evaluating the execution condition, based on the measurements of the SpCell of the SCG, to determine whether to perform reconfiguration according to the target candidate configuration.
  • SpCell Special Cell
  • SCG Secondary Cell Group
  • the method may further comprise applying the target candidate configuration, upon determining that the execution condition is fulfilled, and transmitting a RRC Reconfiguration Complete message to the network, as shown at blocks 350 and 360.
  • the determining shown at block 320 is based on an explicit indication included in a measurement configuration (MeasConfig) received as part of a Master Cell Group (MCG) measurement configuration.
  • MCG Master Cell Group
  • This explicit indication may indicate that all events in the MCG measurement configuration referring to the SpCell that are for conditional reconfiguration apply to the SPCell of the SCG, for example.
  • this explicit indication may indicate that conditional events A3 and/or A5 in the MCG measurement configuration apply to the SPCell of the SCG.
  • the explicit indication may be associated with a configured event and indicate only that the configured event applies to the SPCell of the SCG.
  • the explicit indication may indicate one or more types of reconfiguration to which a conditional reconfiguration applies.
  • the determining shown at block 320 comprises determining that the measurement applies to the SpCell of the SCG by determining that the target candidate configuration contains a reconfiguration for the SpCell of the SCG. In others, this determining may comprise determining that the measurement applies to the SpCell of the SCG by determining that a stored RRCReconfiguration for the target candidate contains a secondaryCellGroup (of IE CellGroupConfig) including the IE ReconfigurationWithSync.
  • this determining may comprise determining that the measurement applies to the SpCell of the SCG by determining that the user equipment is already configured with multi- radio dual connectivity (MR-DC) and that a stored RRCReconfiguration for the target candidate contains a secondaryCellGroup (of IE CellGroupConfig) including the IE ReconfigurationWithSync.
  • this determining may comprise determining that the measurement applies to the SpCell of the SCG by determining that a stored RRCReconfiguration for the target candidate contains a mrdc-SecondaryCellGroupConfig.
  • the determining shown in block 320 may comprise determining that the measurement applies to the SpCell of the SCG based on an order of configurations of conditions in the message.
  • this determining may instead comprise determining that the measurement applies to the SpCell of the SCG based on an indication that one or more measurement identities are to be considered as configured in a SCG measurement configuration.
  • Figure 4 illustrates an example method, as might be carried out by a network node, such as a base station, for managing conditional reconfiguration. This method comprises, as shown at block 410, the step of sending, to a user equipment, a message including a conditional PSCell change configuration, the message including, for at least one target candidate, a target candidate configuration and an execution condition associated to a measurement event.
  • the method further comprises sending to the user equipment, as shown at block 420, an indication that the measurement event is based on a measurement of a Special Cell (SpCell) of a Secondary Cell Group (SCG) for the user equipment.
  • the indication may be included in the message, in some embodiments.
  • the indication is an explicit indication included in a measurement configuration (MeasConfig) received as part of a Master Cell Group (MCG) measurement configuration.
  • MCG Master Cell Group
  • the explicit indication indicates that all events in the MCG measurement configuration referring to the SpCell that are for conditional reconfiguration apply to the SpCell of the SCG.
  • the explicit indication indicates that conditional events A3 and/or A5 in the MCG measurement configuration apply to the SpCell of the SCG.
  • the explicit indication is associated with a configured event and indicates only that the configured event applies to the SpCell of the SCG.
  • the explicit indication indicates one or more types of reconfiguration to which a conditional reconfiguration applies.
  • the indication indicates that one or more measurement identities are to be considered as configured in a SCG measurement configuration.
  • Figure 5 shows an example of a communication system 500 in accordance with some embodiments.
  • the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508.
  • the access network 504 includes one or more access network nodes, such as network nodes 510a and 510b (one or more of which may be generally referred to as network nodes 510), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 510 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 512a, 512b, 512c, and 512d (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 510 and other communication devices.
  • the network nodes 510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 512 and/or with other network nodes or equipment in the telecommunication network 502 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 502.
  • the core network 506 connects the network nodes 510 to one or more hosts, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 506 includes one more core network nodes (e.g., core network node 508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • the host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and/or the telecommunication network 502, and may be operated by the service provider or on behalf of the service provider.
  • the host 516 may host a variety of applications to provide one or more service.
  • Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Micro
  • the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. In some examples, the UEs 512 are configured to transmit and/or receive information without direct human interaction.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 512 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504.
  • a UE may be configured for operating in single- or multi-radio or multi- standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • E-UTRAN Evolved-UMTS Terrestrial Radio Access Network
  • EN-DC Dual Connectivity
  • the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512c and/or 512d) and network nodes (e.g., network node 510b).
  • the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 514 may be a broadband router enabling access to the core network 506 for the UEs.
  • the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514.
  • the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 514 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub 514 may have a constant/persistent or intermittent connection to the network node 510b.
  • the hub 514 may also allow for a different communication scheme and/or schedule between the hub 514 and UEs (e.g., UE 512c and/or 512d), and between the hub 514 and the core network 506.
  • the hub 514 is connected to the core network 506 and/or one or more UEs via a wired connection.
  • the hub 514 may be configured to connect to an M2M service provider over the access network 504 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection.
  • the hub 514 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 510b.
  • the hub 514 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 510b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Figure 6 shows a UE 600 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, a memory 610, a communication interface 612, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 6. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 602 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 610.
  • the processing circuitry 602 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 602 may include multiple central processing units (CPUs).
  • the input/output interface 606 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 600.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device.
  • a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • the power source 608 is structured as a battery or battery pack.
  • Other types of power sources such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 608 may further include power circuitry for delivering power from the power source 608 itself, and/or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 608.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied.
  • the memory 610 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616.
  • the memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems.
  • the memory 610 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 610 may allow the UE 600 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 610, which may be or comprise a device-readable storage medium.
  • the processing circuitry 602 may be configured to communicate with an access network or other network using the communication interface 612.
  • the communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622.
  • the communication interface 612 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 618 and/or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., antenna 622) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 612 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 612, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • IoT Internet of Things
  • Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot.
  • UAV Un
  • a UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 600 shown in Figure 6.
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • Figure 7 shows a network node 700 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 700 includes a processing circuitry 702, a memory 704, a communication interface 706, and a power source 708.
  • the network node 700 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 700 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 700 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 704 for different RATs) and some components may be reused (e.g., a same antenna 710 may be shared by different RATs).
  • the network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 700.
  • RFID Radio Frequency Identification
  • the processing circuitry 702 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 700 components, such as the memory 704, to provide network node 700 functionality.
  • the processing circuitry 702 includes a system on a chip (SOC).
  • the processing circuitry 702 includes one or more of radio frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714.
  • RF radio frequency
  • the radio frequency (RF) transceiver circuitry 712 and the baseband processing circuitry 714 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 712 and baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.
  • the memory 704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read- only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer- executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 702.
  • 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-vol
  • the memory 704 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 702 and utilized by the network node 700.
  • the memory 704 may be used to store any calculations made by the processing circuitry 702 and/or any data received via the communication interface 706.
  • the processing circuitry 702 and memory 704 is integrated.
  • the communication interface 706 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 706 comprises port(s)/terminal(s) 716 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 706 also includes radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710.
  • Radio front-end circuitry 718 comprises filters 720 and amplifiers 722.
  • the radio front-end circuitry 718 may be connected to an antenna 710 and processing circuitry 702.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 710 and processing circuitry 702.
  • the radio front-end circuitry 718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 720 and/or amplifiers 722.
  • the radio signal may then be transmitted via the antenna 710.
  • the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718.
  • the digital data may be passed to the processing circuitry 702.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 700 does not include separate radio front-end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710.
  • all or some of the RF transceiver circuitry 712 is part of the communication interface 706.
  • the communication interface 706 includes one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).
  • the antenna 710 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 710 is separate from the network node 700 and connectable to the network node 700 through an interface or port.
  • the antenna 710, communication interface 706, and/or the processing circuitry 702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 708 provides power to the various components of network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein.
  • the network node 700 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708.
  • the power source 708 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 700 may include additional components beyond those shown in Figure 7 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700.
  • Figure 8 is a block diagram of a host 800, which may be an embodiment of the host 516 of Figure 5, in accordance with various aspects described herein.
  • the host 800 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 800 may provide one or more services to one or more UEs.
  • the host 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and a memory 812.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 6 and 7, such that the descriptions thereof are generally applicable to the corresponding components of host 800.
  • the memory 812 may include one or more computer programs including one or more host application programs 814 and data 816, which may include user data, e.g., data generated by a UE for the host 800 or data generated by the host 800 for a UE.
  • Embodiments of the host 800 may utilize only a subset or all of the components shown.
  • the host application programs 814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 814 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 800 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 814 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • Figure 9 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Hardware 904 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 908a and 908b (one or more of which may be generally referred to as VMs 908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.
  • the VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 906.
  • 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.
  • a VM 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 908, and that part of hardware 904 that executes that VM forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 908 on top of the hardware 904 and corresponds to the application 902.
  • Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization.
  • hardware 904 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of applications 902.
  • hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • FIG. 10 shows a communication diagram of a host 1002 communicating via a network node 1004 with a UE 1006 over a partially wireless connection in accordance with some embodiments.
  • host 1002 includes hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1002 also includes software, which is stored in or accessible by the host 1002 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1006 connecting via an over-the-top (OTT) connection 1050 extending between the UE 1006 and host 1002.
  • OTT over-the-top
  • the network node 1004 includes hardware enabling it to communicate with the host 1002 and UE 1006.
  • the connection 1060 may be direct or pass through a core network (like core network 506 of Figure 5) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1006 includes hardware and software, which is stored in or accessible by UE 1006 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1006 with the support of the host 1002.
  • an executing host application may communicate with the executing client application via the OTT connection 1050 terminating at the UE 1006 and host 1002.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1050 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1050.
  • the OTT connection 1050 may extend via a connection 1060 between the host 1002 and the network node 1004 and via a wireless connection 1070 between the network node 1004 and the UE 1006 to provide the connection between the host 1002 and the UE 1006.
  • connection 1060 and wireless connection 1070 over which the OTT connection 1050 may be provided, have been drawn abstractly to illustrate the communication between the host 1002 and the UE 1006 via the network node 1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1002 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1006.
  • the user data is associated with a UE 1006 that shares data with the host 1002 without explicit human interaction.
  • the host 1002 initiates a transmission carrying the user data towards the UE 1006.
  • the host 1002 may initiate the transmission responsive to a request transmitted by the UE 1006.
  • the request may be caused by human interaction with the UE 1006 or by operation of the client application executing on the UE 1006.
  • the transmission may pass via the network node 1004, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the network node 1004 transmits to the UE 1006 the user data that was carried in the transmission that the host 1002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 1006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1006 associated with the host application executed by the host 1002.
  • the UE 1006 executes a client application which provides user data to the host 1002.
  • the user data may be provided in reaction or response to the data received from the host 1002.
  • the UE 1006 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1006. Regardless of the specific manner in which the user data was provided, the UE 1006 initiates, in step 1018, transmission of the user data towards the host 1002 via the network node 1004.
  • the network node 1004 receives user data from the UE 1006 and initiates transmission of the received user data towards the host 1002.
  • the host 1002 receives the user data carried in the transmission initiated by the UE 1006.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1006 using the OTT connection 1050, in which the wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve the speed and efficiency of changes in secondary cell configuration, thus avoiding delays or degradations in throughput, or other quality-of-service interruptions or degradations. This is in turn may make applications run smoother and/or be more responsive.
  • factory status information may be collected and analyzed by the host 1002.
  • the host 1002 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1002 may store surveillance video uploaded by a UE.
  • the host 1002 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 1002 may be used for energy pricing, remote control of non- time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1002 and/or UE 1006.
  • sensors may be deployed in or in association with other devices through which the OTT connection 1050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1004. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1002.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1050 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality.
  • Embodiments of the various techniques, apparatuses, and systems described above include, but are not limited to, the following enumerated examples.
  • a method performed by a user equipment for conditional reconfiguration comprising: receiving, from a network node, a message including a conditional PSCell change configuration, the message including, for at least one target candidate, a target candidate configuration and an execution condition associated to a measurement event; determining that the measurement event is based on a measurement of a Special Cell (SpCell) of a Secondary Cell Group (SCG) for the user equipment; performing measurements on the SpCell of the SCG; and evaluating the execution condition, based on the measurements of the SpCell of the SCG, to determine whether to perform reconfiguration according to the target candidate configuration.
  • SpCell Special Cell
  • SCG Secondary Cell Group
  • MCG Master Cell Group
  • the explicit indication indicates that all events in the MCG measurement configuration referring to the SpCell that are for conditional reconfiguration apply to the SPCell of the SCG.
  • the explicit indication indicates that conditional events A3 and/or A5 in the MCG measurement configuration apply to the SPCell of the SCG. 6.
  • the explicit indication is associated with a configured event and indicates only that the configured event applies to the SPCell of the SCG. 7. The method of any of example embodiments 3-6, wherein the explicit indication indicates one or more types of reconfiguration to which a conditional reconfiguration applies. 8. The method of example embodiment 1 or 2, wherein said determining comprises determining that the measurement applies to the SpCell of the SCG by determining that the target candidate configuration contains a reconfiguration for the SpCell of the SCG. 9.
  • determining comprises determining that the measurement applies to the SpCell of the SCG by determining that a stored RRCReconfiguration for the target candidate contains a secondaryCellGroup (of IE CellGroupConfig) including the IE ReconfigurationWithSync. 10. The method of example embodiment 1 or 2, wherein said determining comprises determining that the measurement applies to the SpCell of the SCG by determining that the user equipment is already configured with multi-radio dual connectivity (MR-DC) and that a stored RRCReconfiguration for the target candidate contains a secondaryCellGroup (of IE CellGroupConfig) including the IE ReconfigurationWithSync. 11.
  • MR-DC multi-radio dual connectivity
  • determining comprises determining that the measurement applies to the SpCell of the SCG by determining that a stored RRCReconfiguration for the target candidate contains a mrdc- SecondaryCellGroupConfig. 12. The method of example embodiment 1 or 2, wherein said determining comprises determining that the measurement applies to the SpCell of the SCG based on an order of configurations of conditions in the message. 13. The method of example embodiment 1 or 2, wherein said determining comprises determining that the measurement applies to the SpCell of the SCG based on an indication that one or more measurement identities are to be considered as configured in a SCG measurement configuration. 14.
  • Group B Embodiments 15 A method performed by a network node for managing conditional reconfigurations, the method comprising: sending, to a user equipment, a message including a conditional PSCell change configuration, the message including, for at least one target candidate, a target candidate configuration and an execution condition associated to a measurement event; and sending, to the user equipment, an indication that the measurement event is based on a measurement of a Special Cell (SpCell) of a Secondary Cell Group (SCG) for the user equipment.
  • SpCell Special Cell
  • SCG Secondary Cell Group
  • the indication is an explicit indication included in a measurement configuration (MeasConfig) received as part of a Master Cell Group (MCG) measurement configuration.
  • MCG Master Cell Group
  • the explicit indication indicates that all events in the MCG measurement configuration referring to the SpCell that are for conditional reconfiguration apply to the SPCell of the SCG.
  • the explicit indication indicates that conditional events A3 and/or A5 in the MCG measurement configuration apply to the SPCell of the SCG.
  • the explicit indication is associated with a configured event and indicates only that the configured event applies to the SPCell of the SCG. 20.
  • a user equipment 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 processing circuitry. 24.
  • a network node 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 processing circuitry.
  • 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.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • the method of the previous embodiment further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. 31. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. 32.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host. 34.
  • the host of the previous 2 embodiments wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • the method of the previous embodiment further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. 37. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. 38.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • the processing circuitry of the host is configured to execute a host application that provides the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • 41. The method of the previous embodiment further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • a communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • a host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • UE user equipment
  • the host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • the method of the previous embodiment further comprising at the network node, transmitting the received user data to the host.

Landscapes

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

Abstract

Dans un procédé donné à titre d'exemple, un équipement utilisateur (UE) reçoit (310), en provenance d'un nœud de réseau, un message comprenant une configuration conditionnelle de changement de PScell, le message comprenant, pour au moins un candidat cible, une configuration candidate cible et une condition d'exécution associée à un événement de mesure. Le procédé comprend en outre la détermination (320) du fait que l'événement de mesure est basé sur une mesure d'une cellule spéciale, SpCell, d'un groupe de cellules secondaires, SCG, pour l'équipement utilisateur, la réalisation (330) de mesures sur la SpCell du SCG, ainsi que l'évaluation (340) de la condition d'exécution, sur la base des mesures de la SpCell du SCG, pour déterminer s'il faut effectuer une reconfiguration selon la configuration candidate cible.
PCT/SE2022/050431 2021-05-11 2022-05-04 Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires WO2022240334A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163187088P 2021-05-11 2021-05-11
US63/187,088 2021-05-11

Publications (1)

Publication Number Publication Date
WO2022240334A1 true WO2022240334A1 (fr) 2022-11-17

Family

ID=81648754

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/050431 WO2022240334A1 (fr) 2021-05-11 2022-05-04 Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires

Country Status (1)

Country Link
WO (1) WO2022240334A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024087578A1 (fr) * 2023-05-10 2024-05-02 Lenovo (Beijing) Limited Procédés et appareils pour cho avec des scg candidats pour une procédure cpc/cpa
EP4412308A1 (fr) * 2023-02-06 2024-08-07 Nokia Technologies Oy Procédé, appareil et programme informatique
EP4418737A1 (fr) * 2023-02-16 2024-08-21 Nokia Technologies Oy Appareil, procédé et programme informatique pour changement conditionnel de cellule primaire et secondaire initié par un noeud maître

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210099926A1 (en) * 2019-09-26 2021-04-01 FG Innovation Company Limited Method and apparatus for conditional pscell change

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210099926A1 (en) * 2019-09-26 2021-04-01 FG Innovation Company Limited Method and apparatus for conditional pscell change

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.331
CATT: "Introduction of Conditional PSCell Change for intra-SN without MN involvement", vol. RAN WG2, no. Elbonia; 20200224 - 20200306, 11 March 2020 (2020-03-11), XP051864781, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_109_e/Docs/R2-2002248.zip R2-2002248 revision of R2-2001043 introduction of CPC 38 331 based on R2-2001271-v4.docx> [retrieved on 20200311] *
ZTE CORPORATION ET AL: "Discussion on conditional PSCell addition/change", vol. RAN WG2, no. electronic; 20200817 - 20200828, 7 August 2020 (2020-08-07), XP051911776, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_111-e/Docs/R2-2006901.zip R2-2006901 Discussion on conditional PSCell addition and change.docx> [retrieved on 20200807] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4412308A1 (fr) * 2023-02-06 2024-08-07 Nokia Technologies Oy Procédé, appareil et programme informatique
EP4418737A1 (fr) * 2023-02-16 2024-08-21 Nokia Technologies Oy Appareil, procédé et programme informatique pour changement conditionnel de cellule primaire et secondaire initié par un noeud maître
WO2024087578A1 (fr) * 2023-05-10 2024-05-02 Lenovo (Beijing) Limited Procédés et appareils pour cho avec des scg candidats pour une procédure cpc/cpa

Similar Documents

Publication Publication Date Title
WO2022240334A1 (fr) Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires
WO2023014255A1 (fr) Gestion de configuration de qoe basée sur un événement
WO2023203240A1 (fr) Cas d&#39;utilisation du découpage du réseau pour l&#39;accès sans fil fixe (fwa)
US20240259921A1 (en) Signalling Approaches for Disaster PLMNS
US20240323995A1 (en) Secondary node requested measurement gaps at secondary node addition
US20240298203A1 (en) Signalling based minimization of drive test configuration availability
US20240334226A1 (en) Early radio measurement relaxation reporting
WO2023059238A1 (fr) Calcul d&#39;état de mobilité de dispositif de communication à l&#39;aide d&#39;une fréquence de référence
WO2024035305A1 (fr) Rapport de réussite de changement ou d&#39;ajout de pscell
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2024096791A1 (fr) Configuration de changement de scell primaire conditionnel intra-nœud secondaire
WO2023152683A1 (fr) Changement de pscell conditionnel initié par un nœud secondaire
WO2024210804A1 (fr) Signalement de sortie pour une combinaison d&#39;événements
WO2024035304A1 (fr) Signalisation de réseau de rapport de pscell réussie
WO2023219542A1 (fr) Configuration de mesure dans des réseaux sans fil
WO2024033808A1 (fr) Mesures de csi pour mobilité intercellulaire
WO2023068983A1 (fr) Rapport de mesurage basé sur des configurations de mesurage utilisant des indications de priorité spécifiques à la fréquence
WO2024210787A1 (fr) Informations de capacité d&#39;équipement utilisateur relatives à un temps de syntonisation de fréquence radio
WO2024176189A1 (fr) Configuration pour déclencher un rapport de qoe visible de ran
WO2024072306A1 (fr) Surveillance de détection de défaillance de faisceau
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2024220018A1 (fr) Alignement temporel pour mobilité intercellulaire
WO2024035311A1 (fr) Minimisation de portée de configuration de tests de disque pour différents types de réseau
WO2024079534A1 (fr) Réseau privé virtuel de couverture cinquième génération avec provisionnement sans contact
WO2023187741A1 (fr) Temps depuis des informations d&#39;échec dans une liste de rapports d&#39;échecs d&#39;établissement de connexion (cef)

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

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

Country of ref document: EP

Kind code of ref document: A1