WO2020251443A1 - Garantir la récence de mesure d'équipement utilisateur - Google Patents

Garantir la récence de mesure d'équipement utilisateur Download PDF

Info

Publication number
WO2020251443A1
WO2020251443A1 PCT/SE2020/050523 SE2020050523W WO2020251443A1 WO 2020251443 A1 WO2020251443 A1 WO 2020251443A1 SE 2020050523 W SE2020050523 W SE 2020050523W WO 2020251443 A1 WO2020251443 A1 WO 2020251443A1
Authority
WO
WIPO (PCT)
Prior art keywords
measurement
measurements
connection
network
message
Prior art date
Application number
PCT/SE2020/050523
Other languages
English (en)
Inventor
Oumer Teyeb
Icaro L. J. Da Silva
Sangwook Han
Sebastian LINDQVIST
Patrik Rugeland
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 WO2020251443A1 publication Critical patent/WO2020251443A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • CA Carrier Aggregation
  • DC Dual Connectivity
  • UEs take measurements of the radio environment, and report these measurements back to the network. Such measurements may include, for example, Radio Resource Management (RRM) measurements.
  • RRM Radio Resource Management
  • measurements may include Channel Quality Indicator (CQI), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Carrier Received Signal Strength Indicator (RSSI) measurements.
  • CQI Channel Quality Indicator
  • RSRP Reference Signal Received Power
  • RSRQ Reference Signal Received Quality
  • RSSI Carrier Received Signal Strength Indicator
  • the measurements taken by the UE may be used for a variety of purposes, e.g., link adaptation, packet scheduling, and/or determining whether to handover.
  • the UE and the base station are not connected. Although the UE can traditionally receive certain data broadcast by the base station (e.g., system information (SI)), the base station is generally unaware of the UE and unicast transmissions to or from the UE cannot be performed.
  • SI system information
  • the connected state the UE and base station are connected and the transfer of unicast data to and from the UE is supported.
  • the UE and base station are not actively exchanging unicast data, but the base station is aware of the UE and maintains an access stratum (AS) context for the UE. While the UE is not able to communicate with the base station to the same degree as it would while in the connected state, the UE is not entirely disconnected as in the idle state.
  • AS access stratum
  • a UE being transitioned to a power saving state can be configured by the network to perform idle mode measurements that are reported back to the network upon transition back to a connected state. If so configured, the UE will perform idle mode measurements for a specified duration, but is not required to continue performing these idle mode measurements indefinitely.
  • a UE may stop performing idle mode measurements after a given duration (e.g., in response to expiration of a given timer).
  • determining that the connection is required comprises determining that the UE needs to set up a new connection, and transitioning from the power saving state comprises transitioning from an idle state. In some such embodiments, determining that the connection is required is based on receiving a paging message addressed to the UE with a Core Network identifier.
  • determining that the UE lacks measurements that meet a freshness criteria comprises determining that one or more measurements stored at the UE are invalid.
  • determining that the UE lacks measurements that meet a freshness criteria comprises, upon determining that the connection is required, determining that a measurement timer has not expired.
  • taking the measurement while in the power saving state is responsive to determining that a cell on which the UE is camping supports reporting the measurement.
  • the method further comprises transmitting a message requesting the connection. In some such embodiments, the method further comprises refraining from transmitting the message requesting the connection until the taking of the measurement has been completed. Additionally or alternatively, in some embodiments, transmitting the message is in response to failing to locate a cell having sufficient quality within a threshold period of time.
  • the method further comprises receiving, in a Radio Resource Control (RRC) Setup or RRC Resume message, a request for the measurement taken while in the power saving state.
  • RRC Radio Resource Control
  • the method further comprises receiving, subsequent to receiving an RRC Setup or RRC Resume message, a request for the measurement taken while in the power saving state.
  • the method further comprises sending a response to the RRC Setup or RRC Resume message before the taking of the measurement has been completed.
  • sending the response to the RRC Setup or RRC Resume message before the taking of the measurement has been completed is in response to predicting that the taking of the measurement will be completed before receiving a request for the measurement.
  • sending the response to the RRC Setup or RRC Resume message before the taking of the measurement has been completed comprises sending, in the response, incomplete results obtained from having not yet completed taking the measurement.
  • the method further comprises taking further measurements until a measurement reporting request is received.
  • the method further comprises taking further measurements until a measurement timer expires.
  • the UE comprises processing circuitry and interface circuitry communicatively coupled to the processing circuitry.
  • the processing circuitry is configured to, responsive to determining, while the UE is in a power saving state, that a connection with a network node is required and the UE lacks a measurement meeting a freshness criteria, remain in the power saving state to take the measurement before transitioning to a connected state with the network node.
  • the processing circuitry is further configured to report the measurement to the network node via the interface circuitry while the measurement meets the freshness criteria.
  • the UE is further configured to perform any of the methods described above.
  • Other embodiments include a computer program, comprising instructions which, when executed on processing circuitry of a UE, cause the processing circuitry to carry out any of the method described above.
  • Figure 1 is a schematic diagram illustrating an example wireless communication network, according to one or more embodiments of the present disclosure.
  • Figure 3 is a state diagram illustrating an example state machine that defines specific states for an SCell, according to one or more embodiments of the present disclosure.
  • Figure 6 is a schematic diagram illustrating an example 5G network, according to one or more embodiments of the present disclosure.
  • Figures 9A and 9B are signaling diagrams illustrating examples of connection establishment procedures in an LTE network, according to one or more embodiments of the present disclosure.
  • Figures 10A-E are signaling diagrams illustrating examples of connection resume procedures in an NR network, according to one or more embodiments of the present disclosure.
  • Figures 11A-D are signaling diagrams illustrating examples of connection resume procedures in an LTE network, according to one or more embodiments of the present disclosure.
  • Figure 12 is an ASN.1 sample illustrating an example definition of parts of an
  • RRCConnectionRelease message according to one or more embodiments of the present disclosure.
  • Figure 13 is an ASN.1 sample illustrating an example definition of parts of an
  • MeasldleConfig Information Element (IE), according to one or more embodiments of the present disclosure.
  • Figure 14 is an ASN.1 sample illustrating an example definition of parts of an
  • RRCReconnectionSetupComplete IE RRCReconnectionSetupComplete IE, according to one or more embodiments of the present disclosure.
  • Figure 15 is an ASN.1 sample illustrating an example definition of parts of an
  • RRCReconnectionResumeComplete IE RRCReconnectionResumeComplete IE, according to one or more embodiments of the present disclosure.
  • Figure 17 is an ASN.1 sample illustrating an example definition of parts of an
  • UEInformationResponse message according to one or more embodiments of the present disclosure.
  • Figures 18-21 are signaling diagrams illustrating different examples of early
  • Figure 22 is a flow diagram illustrating an example method implemented by a UE, according to one or more embodiments of the present disclosure.
  • Figures 23-26 are signaling diagrams illustrating different examples of reporting a fresh measurement, according to various embodiments of the present disclosure.
  • Figure 28 is a schematic block diagram illustrating an example wireless network, according to one or more embodiments of the present disclosure.
  • Figure 29 is a schematic block diagram illustrating an example UE, according to one or more embodiments of the present disclosure.
  • Figure 31 is a schematic block diagram illustrating an example telecommunication network connected via an intermediate network to a host computer, according to one or more embodiments of the present disclosure.
  • Figure 32 is a schematic block diagram illustrating an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to one or more embodiments of the present disclosure.
  • the network node 20 may, e.g., be referred to as Evolved NodesBs (eNBs) or a gNodeBs (gNBs) in accordance with particular Third Generation Partnership Project (3GPP) standards (e.g., Evolved Universal Terrestrial Radio Access (E-UTRA) or New Radio (NR), respectively).
  • eNBs Evolved NodesBs
  • gNBs gNodeBs
  • 3GPP Third Generation Partnership Project
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • NR New Radio
  • a UE 50 as described herein may be, or may be comprised in, a machine or device that performs monitoring or measurements, and transmits the results of such monitoring measurements to the network node 20, another device, or another network.
  • a UE 50 as described herein may be comprised in a vehicle and may perform monitoring and/or reporting of the vehicle’s operational status or other functions associated with the vehicle.
  • CA Long Term Evolution
  • LTE Long Term Evolution
  • Carriers that are aggregated together are referred to as component carriers (CCs).
  • the PCell is the cell towards which the UE has established a Radio Resource Control (RRC) connection, e.g., by participating in an access procedure or by handover from another cell 15.
  • RRC Radio Resource Control
  • CA Carrier Aggregation
  • MAC Media Access Control
  • MAC gets grants for a certain cell 15 and multiplexes data from different bearers to one transport block being sent on that cell 15.
  • MAC also controls how that process is done.
  • One or more SCells can be“added” (a.k.a.“configured”) for the UE 50 using RRC signaling (e.g., using the RRCConnectionReconfiguration message).
  • RRC signaling e.g., using the RRCConnectionReconfiguration message.
  • PSCell Primary SCell
  • Adding an SCell is a process that typically takes hundreds of milliseconds.
  • a cell 15 is configured for the UE 50, it becomes a“serving cell” for that UE 50.
  • the SCell When an SCell is configured/added via RRC, the SCell starts in the deactivated state.
  • the network node 20 i.e. , the eNB
  • the SCell can indicate that the SCell should activate- upon-configuration, or change states, at least using the RRCConnectionReconfiguration message.
  • the eNB configures lower layers to consider the SCell to be in activated state. Otherwise, if the received RRCConnectionReconfiguration message includes the sCellState parameter for that SCell and the sCellState indicates dormant, the eNB configures lower layers to consider the SCell to be in dormant state. Otherwise, the eNB configures lower layers to consider the SCell to be in deactivated state.
  • MAC CE MAC Control Element
  • the network may be assisted by RRM measurements reported by a UE 50.
  • RRCConnectionReconfiguration message is shown in the example ASN.1 description shown in Figure 5.
  • NR 175 cell 15 This deployment is often referred to as“non-standalone NR.” Notice that, in this case, the functionality of an NR 175 cell 15 is limited and would be used for connected mode UEs 50 as a booster and/or diversity leg, but a UE 50 in the RRCJDLE state would not be able to camp on these NR 175 cells 15.
  • RRC connection establishment involves Signaling Radio Bearer 1 (SRB1) establishment.
  • SRB1 Signaling Radio Bearer 1
  • the procedure is also used to transfer the initial Non Acccess Stratum (NAS) dedicated information/message from the UE 50 to the network 10.
  • NAS Non Acccess Stratum
  • the RRC connection resume procedure is followed by a successful network suspend.
  • the UE 50 sends an
  • RRCResumeRequest or RRCResumeRequestl message to the network node 20 (step 305) and receives an RRCReject message in response (step 340).
  • the UE 50 If the UE 50 supports carrier aggregation between serving carrier and the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry, and the measCellList is included, the UE 50 will consider PCell and cells identified by each entry within the measCellList to be applicable for idle mode measurement reporting. If the measCellList is not included, the UE 50 will consider PCell and up to maxCellMeasldle strongest identified cells whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold (if any) to be applicable for idle mode measurement reporting.
  • the UE 50 sets the content of the RRCConnectionResuleComplete message differently, depending on whether an NB-loT scenario is involved. Except in NB-loT scenarios, if the SIB2 contains idleModeMeasurements, and the UE 50 has IDLE mode measurement information available in VarMeasldleReport, the UE 50 includes the idleMeasAvailable, and stops the T331 timer (if running). In NB-loT, if the UE 50 supports serving cell idle mode measurements reporting and servingCellMeaslnfo is present in SystemlnformationBlockType2-NB, the UE 50 sets the measResultServCell to include the measurements of the serving cell. Note that the UE 50 includes the latest results of the serving cell measurements as used for cell
  • the UE 50 submits the RRCConnectionResumeComplete message to lower layers for transmission, and the procedure ends.
  • the network 10 may finally request that the UE 10 report these available measurements, e.g., as shown in the example signaling illustrated in Figure 16.
  • FIG. 17 illustrates an example ASN.1 definition of a UEInformationResponse message.
  • a work item has been approved in Rel-16 to enhance the setup of CA/DC in NR.
  • One of the objectives for early measurement reporting is for early and fast reporting of measurement information availability from neighbor and serving cells to reduce delay setting up MR-DC and/or CA.
  • 3GPP is going to investigate solutions to enable early measurements performed when the UE is in RRCJNACTIVE or RRCJDLE state and, reporting mechanisms for when the UE enters RRC_CONNECTED.
  • the UE 50 reports early measurements in UEInformationResponse after a request from the network 10 in UEInformationRequest transmitted after the UE 50 sends an RRCResumeComplete or, after security is activated when the UE 50 comes from idle without stored context (as in LTE Rel-15).
  • the UE 50 reports early measurements with (e.g. multiplexed with or as part of the message) RRCResumeComplete.
  • the UE 50 reports early measurements with (e.g. multiplexed with or as part of the message) RRCResumeRequest.
  • the UE 50 relies on a measurement configuration, which may be provided with dedicated signaling when the UE 50 is suspended to RRCJNACTIVE or when the UE 50 is released to RRCJDLE. That measurement configuration indicates how the UE 50 shall perform these measurements to be reported when the UE 50 resumes (in the case of coming from RRCJNACTIVE or setups up a connection, in the case of coming from
  • RAN2 confirms that current specifications allow that UEInformationRequest (or equivalent message to be specified in NR) can be sent by the network immediate after Security Mode Command without network having to wait for Security Mode Complete (similar to sending of Reconfiguration after SMC).
  • UEInformationRequest or equivalent message to be specified in NR
  • RAN2 confirms that current specifications allow that UEInformationRequest (or equivalent message to be specified in NR) can be sent by the network immediate after Security Mode Command without network having to wait for Security Mode Complete (similar to sending of Reconfiguration after SMC).
  • UEInformationRequest or equivalent message to be specified in NR
  • UEInformationRequest i.e. via UEInformationRequest and UEInformationResponse like messages
  • Sending early measurement report is network controlled.
  • the network can request early measurement report in RRCResume, whereas for NR INACTIVE, early measurement reporting can be sent in RRCResumeComplete (though it will require further study as to whether these cases should similarly be applied to LTE RRCConnectionResume and RRCConnectionResumeComplete message).
  • NR early measurements can be configured in both NR RRCRelease message and NR system information, though it will require further study as to whether there are differences in the configuration that can be provided by RRCRelease and SI. It has also been agreed to introduce some indication about the cell's early measurement support in NR system information.
  • a single validity timer (similar to measldleDuration in LTE euCA) is mandatory indicated only in NR RRCRelease message, i.e. not included in NR SIB.
  • lEs can be optionally configured per NR frequency in both NR RRCRelease message and NR SIB that indicate: 1) a list of frequencies and optionally cells (similar to measCellList in LTE euCA) the UE 50 is required to perform early
  • a cell quality threshold similar to qualityThreshold in LTE euCA
  • the UE 50 is required to report the measurement results only for the cells which met the configured thresholds. Notwithstanding, it will require further study as to whether adopt a validity area (similar to validityArea in LTE euCA) to indicate the list of cells within which UE 50 is required to perform early measurements, and if the UE 50 reselects to a cell outside this list, the early measurements are no longer required (same as timer expiry). If such is absent, the UE 50 will not have area limitation of early measurements.
  • SSB based measurements and for both IDLE and INACTIVE early measurements: 1) SSB frequencies to be measured can be located out of sync faster; 2) RSRP and RSRQ can be configured as cell and beam measurement quantity; and 3) the configuration parameters provided per SSB frequency follow the same principles as those provided in SIB2/4 for the purposes of Idle/lnactive mobility.
  • LTE euCA cell / beam SI NR is not introduced as measurement quantity in NR early measurement configuration in Rel-16.
  • the UE 50 For SSB based beam level measurement configurations, the UE 50 is required to report the beam with the highest measurement quantity, and it will require further study as to whether additional beams can be reported.
  • the UE 50 can be configured with one of the 3 beam reporting types: 1) no beam reporting; 2) only beam identifier; and 3) both beam identifier and quantity. It will require further study as to whether to support CSI-RS based NR early measurements.
  • an LTE UE 50 in IDLE mode, IDLE with suspended, and INACTIVE can be configured with NR early measurements to support fast setup of (NG)EN-DC (i.e. euCA is extended to support NR measurements).
  • Figures 18-21 reflect examples of signaling in accordance with the examples discussed above.
  • Figures 18 and 19 illustrates different examples of early measurement reporting in LTE/NR IDLE mode in Rel-16 during connection setup.
  • Figure 20 illustrates an example of early measurement reporting in LTE IDLE with suspended, LTE INACTIVE mode, or NR INACTIVE mode in Rel-16.
  • Figure 21 illustrates an example of early measurement reporting in NR INACTIVE mode in Rel-16, though it will require further study as to whether such may be applicable to LTE IDLE with suspended and LTE INACTIVE modes.
  • a UE 50 being transitioned to a power saving state can be configured by the network 10 to perform idle mode measurements for early reporting upon transition. If so configured, the UE 50 will perform the idle mode measurements for the specified measldleDuration. Because the UE 50 is not required to continue performing measurements after the T331 timer expires according to traditional methods, when transitioning the UE 50 to the connected state from the power saving state, the network 10 may end up receiving a measurement result that is quite old. That is, the measurement results the UE 50 has readily available may not reflect current conditions for the UE 50. Therefore, if the network 10 were to configure the UE 50 based on these old measurements, it could cause the UE 50 to be configured with CA/DC information that is not optimal, or even worse, could lead to a communication failure.
  • a power saving state e.g. idle or inactive
  • embodiments of the present disclosure propose mechanisms to start/restart idle measurements for early reporting.
  • embodiments may use a freshness criteria to determine whether a measurement is suitable for reporting to the network 10.
  • embodiments of the present disclosure include a method 400 implemented by a UE 50.
  • the method 400 comprises responsive to determining, while the UE 50 is in a power saving state, that a connection with a network node 20 is required and the UE 50 lacks a measurement meeting a freshness criteria, remaining in the power saving state to take the measurement before transitioning to a connected state with the network node 20 (block 410).
  • the method 400 further comprises reporting the measurement to the network node 20 while the measurement meets the freshness criteria (block 420).
  • the term“freshness criteria” is the criteria by which a measurement is judged to be suitable for being included in reporting while in the connected state. Various such criteria will be discussed in greater detail below.
  • the UE 50 may determine that a connection is required based on one or more criteria, depending on the embodiment. For example, the UE 50, while in the power saving state, may detect the arrival of data to be sent on the uplink.
  • Figure 23 illustrates signaling between a UE 50 and a network node 20, consistent with such an example.
  • the UE 50 is initially in a connected state (RRC_CONNECTED) (step 505) and receives a release message (RRCRelease) (step 510) indicating that the UE 50 should enter a power saving state (RRCJDLE) (step 515).
  • the release message also includes a measurement configuration (measConfig) that configures the UE 50 to perform measurements while in the power saving state.
  • the UE 50 performs measurements while in the power saving state in accordance with the measurement configuration received from the network node 20 (step 520). Subsequently, data arrives at the UE 50 for transmission on an uplink (step 525). In response, the UE 50 detects that it lacks a measurement that meets a freshness criteria, and in response, takes a measurement while in the power saving state (block 530).
  • the UE 50 Having obtained a fresh measurement, the UE 50 sends a connection request
  • RRCSetupRequest to the network node 20 (step 535), and receives a connection setup message (RRCSetup) from the network node 20 in response (step 540).
  • RRCSetup a connection setup message from the network node 20 in response
  • the UE 50 responds to the network node 20 in turn with a connection setup completion message
  • connection setup completion message may, for example, include an indication that the UE 50 has a measurement available (i.e., a
  • the UE 50 then enters the connected state (RRC_CONNECTED) (step 550).
  • the UE 50 receives a security mode command from the network node 20 (step 555).
  • the UE 50 also receives measurement request message (UEInformationRequest) (step 560).
  • the UE 50 responds to the security mode command with a completion message
  • the UE 50 also responds to the measurement request message (UEInformationResponse) with a measurement report comprising the fresh measurement (step 570).
  • the UE 50 receives a connection reconfiguration message
  • RRCReconfiguration from the network node 20, e.g., that reconfigures the UE 50 based on the measurement included in the measurement report (step 575).
  • the UE 50 responds with a connection reconfiguration completion message (RRCReconfigurationComplete) (step 580).
  • the example of Figure 23 provides an example of a UE 50 that, in response to detecting that a connection is required, enables the network 10 to receive a fresh measurement that can provide a basis for properly configuring that connection. While the UE 50 detects that the connection is required due to the arrive of data to be transmitted on the uplink while in the power saving mode, according to other embodiments, the UE 50 may detect that a connection is required in other ways.
  • Figure 24 illustrates an example that is substantially similar to Figure 23, with the exception that in the example of Figure 24, the UE 50 detects that a connection is required based on a paging message received from the network node 20 (step 585) rather than due to the arrival of data to be transmitted on the uplink.
  • the UE 50 takes a fresh measurement while in the power saving state, and reports the fresh measurement while in the connected state. According to other embodiments, the UE 50 may report the fresh measurement before entering the connected state.
  • Figures 25 and 26 illustrate examples of such embodiments.
  • steps 505 through 530 are substantially similar to those illustrated in Figure 23, with the exception that the power saving state in this example is the RRCJNACTIVE state (step 615) instead of RRCJDLE (step 515).
  • connection request (step 635), connection setup (step 640), and connection setup completion (step 645) messages are also different from those shown in Figures 23 and 24.
  • the connection request message is an RRCResumeRequest
  • the connection setup message is an RRCResume message
  • the connection setup completion message is an RRCSetupComplete message.
  • the UE 50 does not indicate to the network node 20 that a measurement is available. Rather, in this example, the UE receives a measurement request in the connection setup message (step 640), and the UE 50 provides the fresh measurement to the network node 20 in the connection setup completion message (step 645) before transitioning to the connected state (step 550).
  • the UE 50 and network node 20 also do not exchange security mode messages (e.g., the security mode configuration from the previous connection may be saved and reused). Further, since the UE 50 earlier reported the fresh measurement while in the power saving state, the UE 50 does not receive a measurement request from the network node 20 and report the measurement to the network node 20 while in the connected state.
  • security mode messages e.g., the security mode configuration from the previous connection may be saved and reused.
  • the UE 50 may receive a connection reconfiguration message (RRCReconfiguration) from the network node 20, e.g., that reconfigures the UE 50 based on the measurement included in the measurement report (step 575), and the UE 50 responds with a connection reconfiguration completion message (RRCReconfigurationComplete) (step 580).
  • RRCReconfiguration connection reconfiguration message
  • RRCReconfigurationComplete connection reconfiguration completion message
  • the example of Figure 26 is substantially similar to the example of Figure 25, except that the UE 50 determines that the connection is required based on receiving a paging message (step 585).
  • a request to report the measurement may be received upon transitioning to a connected state, whereas in others the request may be received before transitioning to the connected state. Further, in some embodiments the measurement may be reported before transitioning to the connected state, whereas in others, the measurement is reported after transitioning to the connected state. Further, in some embodiments, determining that the connection is required comprises receiving data for transmission on a uplink of the connection, whereas in other embodiments, determining that the connection is required comprises receiving paging indicating that data will be arriving on a downlink of the connection.
  • the UE 50 determines that measurement is required based, at least in part, on a freshness criteria.
  • a measurement may fail to meet the freshness criteria if measurements at the UE 50 are either unavailable or invalid upon the triggering of connection establishment/resumption procedures. Additionally or alternatively, a measurement may fail to meet the freshness criteria if the T331 timer (or equivalent timer based on measldleDuration) is running when the connection resumption/establishment procedure is triggered. Additionally or alternatively, a measurement may fail to meet the freshness criteria if the UE 50 has not accumulated enough idle mode measurements when the connection resumption/establishment procedure is triggered (e.g. fewer than a threshold number of measurements have been performed so far, only cell level measurement has been gathered, only a certain number of cells/frequencies have been measured, and/or measurement has been performed for less than a threshold duration of time).
  • Embodiments may further include additional, lesser, or different signaling from that illustrated in the examples of Figures 23-26.
  • the UE 50 may receive a request to report the measurement according to signaling that is broadcast in the cell that is the target of the desired connection.
  • taking the measurement may comprise taking the measurement according to an already stored idle measurement configuration, whereas in other embodiments, taking the measurement comprises taking the measurement according to a configuration signaled in the request.
  • the UE 50 performs idle mode measurements upon the triggering of a connection establishment or resume procedure.
  • One or more such embodiments improve on traditional techniques because according to such traditional techniques, if an idle measurement is not available or is out of date when the connection establishment or resume procedure is initiated, the network will not be able to receive any early measurements and will have to rely on blind configuration of CA/DC or wait for the UE 50 to be configured, perform, and report connected mode measurements, which can take considerable time. Additionally or alternatively, by performing early measurement in accordance with one or more embodiments described herein, it is more likely that the UE 50 can maintain synchronization with the cell, particularly when the measurement is taken right before RRC connection.
  • embodiments herein include any and all apparatus, systems, computer programs, computer-readable mediums, and carriers that correspond to the methods discussed above. Particular embodiments of the present disclosure will now be described in greater detail. Although most of the embodiments described herein focus on NR embodiments for the sake of brevity. However, it will be readily appreciated that the embodiments described herein are also applicable to LTE. For example, references to the RRCSetup message can be replaced with references to the RRCConnectionSetup. Similarly, references to the RRCResume message can be replaced with references to the RRCConnectionResume message. Other similar changes can also be made as appropriate.
  • power saving state refers to any of the states whose procedures are optimized for power savings, such as idle with stored context (like in the LTE Rel-15 solution with suspend/resume procedures), idle without stored context (like the NR Idle state) or inactive (like the one standardized for NR and LTE connected to 5GC).
  • Embodiments may also be applied in inter-RAT use cases, e.g., when the UE suspends or releases in a first RAT (e.g., LTE), performs cell selection/re-selection to a cell in a second RAT (e.g., NR), and determines that it needs to resume or establish a connection in that second RAT.
  • a first RAT e.g., LTE
  • a second RAT e.g., NR
  • Embodiments include a method executed by a UE 50 (e.g., a wireless terminal) for early measurement reporting of idle mode measurements.
  • the UE 50 may receive an idle mode measurement configuration either in a dedicated message (e.g. RRCRelease, RRCconnectionRelease) or broadcast message (e.g. SIB5, SIB4, etc). Accordingly, the UE 50 may perform an idle mode measurement according to the idle mode measurement configuration while in a power saving state.
  • a dedicated message e.g. RRCRelease, RRCconnectionRelease
  • broadcast message e.g. SIB5, SIB4, etc.
  • the UE may determine that there is a need to initiate a connection establishment or reestablishment procedure (depending on whether the UE is in the idle or inactive state, respectively). This determination may be based on one or more factors
  • the UE may receive a paging message addressed to the UE 50 with a RAN identifier (e.g. in an Inactive RNTI (l-RNTI)). In that case, the UE 50 is in the inactive state and the connection needs to be resumed.
  • a RAN identifier e.g. in an Inactive RNTI (l-RNTI)
  • the UE 50 may receive a paging message addressed to the UE 50 with a CN identifier (e.g. in an l-RNTI). In that case, if the UE 50 is in the inactive state, the UE 50 needs to be moved to the idle state. From the idle state, the connection needs to be set up.
  • a CN identifier e.g. in an l-RNTI
  • a NAS layer of the UE 50 may make an internal request to an AS layer of the UE 50 requesting that data be transmitted on an uplink. In that case, the UE 50 initiates a connection resume or setup procedure, depending on whether the UE 50 is in the inactive or idle state, respectively.
  • the NAS layer of the UE 50 may send a request to the AS layer of the UE 50 to transmit a NAS signaling message (e.g., a Registration Area Update message). In that case, the UE 50 initiates a connection resume or setup procedure, depending on whether the UE 50 is in the inactive or idle state, respectively.
  • a NAS signaling message e.g., a Registration Area Update message
  • the AS layer of the UE 50 may internally request to perform a RAN Area Update. In that case the UE 50 is in an inactive state and the UE 50 initiates a resume procedure.
  • the UE 50 determines the need to perform or continue performing early
  • the determination that the UE 50 needs to perform or continue performing early measurements may be based on one or more factors.
  • the UE 50 may determine that an early measurement is needed based on the unavailability or invalidity of early measurements at the UE 50 upon the triggering of connection establishment/ resumption procedures.
  • the UE 50 may determine that an early measurement is needed based on the T331 timer (or equivalent timer based on measldleDuration) not being expired when the connection resumption/establishment procedure is triggered.
  • the UE 50 may determine that an early measurement is needed based on the UE 50 not having accumulated enough idle mode measurements when the connection resumption/establishment procedure is triggered. For example, at the time that connection resumption/establishment is triggered, the UE 50 may have performed fewer than a required number of measurements, performed measurements for less than a threshold amount of time, may have only performed cell level measurements so far, and/or may have measured less than a threshold number of cells and/or frequencies.
  • the UE 50 was not performing idle measurements at the time the UE determined that a connection is needed because the UE 50 was configured to start idle measurements only once it determines that it needs to resume or establish a connection.
  • the UE 50 may receive an idleMeasConfig but not perform any idle measurements until the UE 50 determines that the connection is needed. This may, in some embodiments, save the UE 50 power in the power saving state compared to traditional techniques (e.g., Rel- 15-based solutions) because the UE 50 only performs idle measurements for early reporting upon the attempt to resume or establish a connection.
  • the UE 50 is not performing idle measurements at the time the UE 50 determines that a connection is needed because the T331 timer had expired. In other words, the UE 50 may have received an idleMeasConfig and performed idle measurements while the T331 timer was running. However, upon expiry of the T331 timer, the UE 50 may stop performing idle measurements. In that case, the UE 50 may behave differently depending on the particular embodiment.
  • the UE 50 upon expiry of the T331 timer, keeps the
  • measldleConfig stored but discards the latest measurement results that have been gathered before the timer T331 expired. Then, upon determining that a connection is needed, the UE 50 resumes performing the idle measurements for early reporting from the beginning, without any filtering associated with earlier samples obtained while the timer T331 was running.
  • the UE 50 upon expiry of the T331 timer, the UE 50 keeps the measldleConfig stored and stores the latest measurement results that have been gathered before the timer T331 expired. Then, upon determining the need to resume or establish a connection, the UE 50 resumes performing the idle measurements for early reporting taking into consideration the earlier samples obtained while the timer T331 was running. Alternatively, the UE 50 only takes into consideration those earlier samples obtained while the T331 timer was running that are still valid. The validity of earlier measurements may be determined based on how much time has elapsed between when the latest measurement was performed (e.g., when the T331 timer expired) and when the UE 50 determines that a connection is needed.
  • the UE 50 was not performing idle measurements at the time the UE 50 determined that a connection is needed because the UE 50 was camping in a cell that does not belong to a configured validity area in the measldleConfig at that time. In that case, upon determining that a connection is needed, the UE 50 may start performing idle
  • the UE 50 may start performing idle measurements for early reporting based on the measConfigldle broadcast by the new cell on which the UE 50 is camping.
  • the UE 50 may initiate or continuing performing the idle mode measurements based on an idle measurement configuration.
  • the idle measurement configuration may be already stored in the UE 50, or may be received in broadcast signaling at the target cell where the connection establishment or resumption is being performed.
  • the UE 50 when the UE 50 determines that a connection is needed, the UE 50 verifies that certain conditions are met before performing the idle measurements. For example, the UE 50 may determine whether the cell the UE 50 is camping on supports early measurements reporting. This determination may be performed by checking system information broadcast by that cell for an indication of whether early measurement reporting is supported.
  • the particular manner in which the UE 50 performs idle mode measurements may be dynamically configurable (e.g., based on a configuration received in the RRCRelease message or an SIB broadcast) or can be a statically-specified behavior that the UE 50 always applies upon being triggered to resume and/or set up a connection.
  • the UE 50 may be configured to apply different behaviors for setting up a connection as compared to resuming a connection.
  • the UE 50 may be configured to start and/or continue performing the measurements for either setting up a connection, resuming a connection, or both.
  • this behavior could also be dynamically- configurable, or it can be a static behavior that the UE 50 always adheres to.
  • the UE 50 may be configured to perform the idle mode measurements on a subset of the idle mode measurement configurations.
  • the UE 50 is configured to perform idle mode measurements on both beams and cells, when triggered to set up a connection, the UE 50 can be configured to only measure cells, only measure beams, or measure both cells and beams, whereas to resume a connection, the UE 50 can similarly be configured to only measure cells, only measure beams, or measure both cells and beams (i.e. , independently of whether cells and/or beams are measured when triggered to set up the connection).
  • the UE 50 may perform idle mode measurements only on cells/frequencies until it has detected a threshold number of cells and/or beams that fulfill some criteria, e.g. RSRP, RSRQ, and/or SINR above a threshold.
  • a threshold number of cells and/or beams that fulfill some criteria e.g. RSRP, RSRQ, and/or SINR above a threshold.
  • the UE 50 may perform idle mode measurements on cells/frequencies until it has accumulated a threshold number of measurement samples.
  • the UE 50 may perform idle mode measurement on cell/frequencies only until it has managed to measure a subset or all of the configured cells/frequencies to be measured.
  • the UE 50 may perform idle mode measurement on beams only (e.g. SSBs and/or CSI-RSs for the configured cells/frequencies), since these may be more prone to fast variations.
  • beams only e.g. SSBs and/or CSI-RSs for the configured cells/frequencies
  • the UE 50 may send a connection setup request or resume request message to the network 10, as appropriate (e.g., dependent on whether the UE 50 is, at this point, in the idle or inactive state, respectively). In some embodiments, the UE 50 refrains from sending the connection setup request (e.g., RRCSetupRequest) or resume request (e.g.,
  • RRCResumeRequest message until the early measurements are available. Notwithstanding, the UE 50 may send the connection setup (e.g., RRCSetup) or resume request (e.g.,
  • ResumeRequest message if the UE 50 has failed to locate an NR cell of sufficient quality after having searched for a threshold period of time after receiving MSG2 (RAR, Random Access Response).
  • the UE 50 receives a corresponding RRC Setup or RRC Resume message from the network 10 via the network node 20.
  • the UE 50 receives a request from the network 10 to report early measurements in this message (e.g., as an indicator in the RRC Resume message).
  • the UE 50 receives a request from the network 10 to report early measurement in a subsequent message (e.g., a UEInformationRequest message).
  • the UE 50 sending a response message to the RRC Setup or RRC Resume message (e.g., RRCSetupComplete, RRCResumeComplete, as appropriate).
  • the UE 50 refrains from sending the connection setup complete (e.g. RRCSetupComplete) or resume complete (e.g. RRCResumeComplete) message until the early measurements are available. Notwithstanding, the UE may send the connection setup complete (e.g. RRCSetupComplete) or resume complete (e.g. RRCResumeComplete) messages if UE 50 has not located an NR cell of sufficient quality after having searched for a threshold period of time after receiving MSG4 (RRC Connection Setup).
  • the UE 50 may indicate the availability of early measurements even if early measurements were not ready at that time. For example, the UE 50 may indicate the availability of the early measurements if the UE 50 anticipates that the early measurements will be ready by the time the UE 50 receives an information request for the measurements.
  • the UE 50 reports at least one of the idle measurements which have been obtained in accordance with the embodiments discussed above. That is, the UE 50 reports at least one measurement that was triggered based on a determination that the UE 50 needs to resume or establish a connection, that the UE 50 needs to perform a RAN Notification Area Update, that the T380 timer has expired, and/or that the UE 50 has entered a new cell 15 not in the UE’s configured RAN notification area. In some embodiments, these measurements may have been filtered, but also use samples taken after the UE 50 has internally started the procedure.
  • the UE 50 reports the idle measurements using a
  • UEInformationResponse message after sending a security mode command complete during connection setup or in an RRCResumeComplete message during connection resume.
  • the UE 50 includes in the RRCSetupComplete or
  • the included measurements are a subset of those that the UE 50 has been configured to perform. That is, at the time the UE 50 sends the
  • the UE 50 may not yet have performed all of the idle mode measurements that the UE 50 is configured to perform when triggered to set up or resume the connection, and may include those which have been performed thus far in the message. In some such embodiments, the UE 50 may indicate availability of further early measurements in the RRCSetupComplete or the
  • RRCResumeComplete which the network can later request, e.g., using a
  • the UE 50 may continue to perform idle mode measurements until the UE 50 has finished measuring every cell, beam, and/or frequency indicated in the idle mode measurement configuration being used, until the receives an UEInformationRequest message from the network, until a predefined or configured timer expires, and/or until a connected mode measurement configuration is received.
  • the UE 50 comprises processing circuitry 710 and interface circuitry 730.
  • the processing circuitry 710 is communicatively coupled to the interface circuitry 730, e.g., via one or more buses.
  • the user equipment 700 further comprises memory circuitry 720 that is communicatively coupled to the processing circuitry 710, e.g., via one or more buses.
  • the processing circuitry 710 is configured to perform one or more of the methods described herein (e.g., the method 400 of Figure 22).
  • the processing circuitry 710 may comprise one or more microprocessors,
  • the processing circuitry 710 may be programmable hardware capable of executing software instructions of a computer program 760 stored in the memory circuitry 720 whereby the processing circuitry 710 is configured.
  • the memory circuitry 720 of the various embodiments may comprise any non-transitory machine- readable media known in the art or that may be developed, whether volatile or non-volatile, including but not limited to solid state media (e.g., SRAM, DRAM, DDRAM, ROM, PROM, EPROM, flash memory, solid state drive, etc.), removable storage devices (e.g., Secure Digital (SD) card, miniSD card, microSD card, memory stick, thumb-drive, USB flash drive, ROM cartridge, Universal Media Disc), fixed drive (e.g., magnetic hard disk drive), or the like, wholly or in any combination.
  • solid state media e.g., SRAM, DRAM, DDRAM, ROM, PROM, EPROM, flash memory, solid state drive, etc.
  • removable storage devices e.g., Secure Digital (SD) card, miniSD card, microSD card, memory stick, thumb-drive, USB flash drive, ROM cartridge, Universal Media Disc
  • fixed drive e.g., magnetic hard disk drive
  • the interface circuitry 730 may be a controller hub configured to control the input and output (I/O) data paths of the user equipment 700.
  • I/O data paths may include data paths for exchanging signals over a communications network, data paths for exchanging signals with a user, and/or data paths for exchanging data internally among components of the user equipment 700.
  • the interface circuitry 730 may comprise a transceiver configured to send and receive communication signals over one or more of a cellular network, Ethernet network, or optical network.
  • the interface circuitry 730 may also comprise one or more of a graphics adapter, display port, video bus, touchscreen, graphical processing unit (GPU), display port, Liquid Crystal Display (LCD), and Light Emitting Diode (LED) display, for presenting visual information to a user.
  • the interface circuitry 730 may also comprise one or more of a pointing device (e.g., a mouse, stylus, touchpad, trackball, pointing stick, joystick), touchscreen, microphone for speech input, optical sensor for optical recognition of gestures, and keyboard for text entry.
  • the interface circuitry 730 may be implemented as a unitary physical component, or as a plurality of physical components that are contiguously or separately arranged, any of which may be communicatively coupled to any other, or may communicate with any other via the processing circuitry 710.
  • the interface circuitry 730 may comprise transmitter circuitry 740 configured to send communication signals over a communications network and receiver circuitry 750 configured to receive communication signals over the communications network.
  • the interface circuitry 730 may comprise a display and/or keyboard.
  • Other embodiments may include other permutations and/or arrangements of the above and/or their equivalents
  • the processing circuitry 710 is configured to determine, while the UE 50 is in a power saving state, that a connection with a network node 20 is required and the UE 50 lacks a measurement meeting a freshness criteria, and in response, remain in the power saving state to take the measurement before transitioning to a connected state with the network node 20.
  • the processing circuitry 710 is further configured to report the measurement to the network node 20 via the interface circuitry 730 while the measurement meets the freshness criteria.
  • the computer program 760 comprises instructions which, when executed on processing circuitry of a UE 50, cause the UE 50 to carry out any of the respective processing described above.
  • a computer program 760 in this regard may comprise one or more code modules corresponding to the means or units described above.
  • Embodiments further include a carrier containing such a computer program 760.
  • This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • embodiments herein include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.
  • Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a UE 50.
  • This computer program product may be stored on a computer readable recording medium.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-loT), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the
  • WiMax Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • Network 1106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless networks
  • wireless networks wireless networks
  • metropolitan area networks metropolitan area networks
  • Network node 1160 and WD 1110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 1160 includes processing circuitry 1170, device readable medium 1180, interface 1190, auxiliary equipment 1184, power source 1186, power circuitry 1187, and antenna 1162.
  • network node 1160 illustrated in the example wireless network of Figure 28 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • Network node 1160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1160.
  • Device readable medium 1180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1170.
  • 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
  • processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 1120 of WD 1110 may comprise a SOC.
  • RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 1124 and application processing circuitry 1126 may be combined into one chip or set of chips, and RF transceiver circuitry 1122 may be on a separate chip or set of chips.
  • Each transceiver may include transmitter 1233 and/or receiver 1235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1233 and receiver 1235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • Virtualization environment 1300 comprises general-purpose or special-purpose network hardware devices 1330 comprising a set of one or more processors or processing circuitry 1360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 1360 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 1390-1 which may be non-persistent memory for temporarily storing instructions 1395 or software executed by processing circuitry 1360.
  • Each hardware device may comprise one or more network interface controllers (NICs) 1370, also known as network interface cards, which include physical network interface 1380.
  • NICs network interface controllers
  • processing circuitry 1360 executes software 1395 to instantiate the hypervisor or virtualization layer 1350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 1350 may present a virtual operating platform that appears like networking hardware to virtual machine 1340.
  • hardware 1330 may be a standalone network node with generic or specific components.
  • Hardware 1330 may comprise antenna 1325 and may implement some functions via virtualization.
  • hardware 1330 may be part of a larger cluster of hardware (e.g., such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 1310, which, among others, oversees lifecycle management of applications 1320.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 1340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 1340, and that part of hardware 1330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • one or more radio units 13200 that each include one or more transmitters 13220 and one or more receivers 13210 may be coupled to one or more antennas 1325.
  • Radio units 13200 may communicate directly with hardware nodes 1330 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.
  • Figure 31 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes
  • Telecommunication network 1410 is itself connected to host computer 1430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, and a distributed server or as processing resources in a server farm.
  • Host computer 1430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 1421 and 1422 between telecommunication network 1410 and host computer 1430 may extend directly from core network 1414 to host computer 1430 or may go via an optional intermediate network 1420.
  • Communication system 1500 further includes UE 1530 already referred to. Its hardware 1535 may include radio interface 1537 configured to set up and maintain wireless connection 1570 with a base station serving a coverage area in which UE 1530 is currently located.
  • radio interface 1537 configured to set up and maintain wireless connection 1570 with a base station serving a coverage area in which UE 1530 is currently located.

Landscapes

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

Abstract

Un équipement utilisateur (UE) (50) détermine, tandis que l'UE (50) est dans un état d'économie d'énergie, qu'une connexion avec un nœud de réseau (20) est requise et que l'UE (50) n'a pas de mesure satisfaisant un critère de récence. En réponse, l'UE (50) reste dans l'état d'économie d'énergie pour prendre la mesure avant de passer à un état connecté avec le nœud de réseau (20). L'UE (50) rapporte la mesure au nœud de réseau (20) tandis que la mesure satisfait les critères de récence.
PCT/SE2020/050523 2019-06-14 2020-05-20 Garantir la récence de mesure d'équipement utilisateur WO2020251443A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962861990P 2019-06-14 2019-06-14
US62/861,990 2019-06-14

Publications (1)

Publication Number Publication Date
WO2020251443A1 true WO2020251443A1 (fr) 2020-12-17

Family

ID=70922106

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2020/050523 WO2020251443A1 (fr) 2019-06-14 2020-05-20 Garantir la récence de mesure d'équipement utilisateur

Country Status (1)

Country Link
WO (1) WO2020251443A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022263314A1 (fr) * 2021-06-18 2022-12-22 Nokia Technologies Oy Rapport de mesure accéléré (xmr)
WO2023193677A1 (fr) * 2022-04-06 2023-10-12 维沃移动通信有限公司 Procédé et appareil de traitement de mesure, terminal et dispositif côté réseau

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
APPLE: "Early Measurement Report in NR", vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), XP051730616, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN2/Docs/R2%2D1907172%2Ezip> [retrieved on 20190513] *
ERICSSON: "On Resuming Measurements", vol. RAN WG2, no. Reno, NV, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), XP051730688, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN2/Docs/R2%2D1907247%2Ezip> [retrieved on 20190513] *
QUALCOMM INCORPORATED: "UE behaviours in NR early measurements", vol. RAN WG2, no. Reno, Nevada, US; 20190513 - 20190517, 13 May 2019 (2019-05-13), XP051729049, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN2/Docs/R2%2D1905543%2Ezip> [retrieved on 20190513] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022263314A1 (fr) * 2021-06-18 2022-12-22 Nokia Technologies Oy Rapport de mesure accéléré (xmr)
WO2023193677A1 (fr) * 2022-04-06 2023-10-12 维沃移动通信有限公司 Procédé et appareil de traitement de mesure, terminal et dispositif côté réseau

Similar Documents

Publication Publication Date Title
AU2020361417B2 (en) Handling of stored conditional configuration in a wireless communication network
US20190306764A1 (en) Method for avoiding unnecessary actions in resume procedure
US11700661B2 (en) Inter-RAT (radio access technology) reestablishment enhancements in multi-RAT dual connectivity (MR-DC)
US11785511B2 (en) Inter-RAT (radio access technology) re-establishment enhancements in multi-RAT dual connectivity (MR-DC)
CN113439454A (zh) 早期测量中的波束信息
US11864086B2 (en) Radio network area update in a wireless communication system
CN111903157B (zh) 避免不必要动作的连接建立的方法和ue
US20220377629A1 (en) Failure Reporting in a Wireless Communication Network
EP4011156A1 (fr) Configuration de liaison latérale
WO2019073091A1 (fr) Gestion de paramètres dans des messages de libération/attente
US20210044964A1 (en) Managing a Temporary Subscriber Identifier Having an Extended Length During Connection Setup in 5G Networks
US20220312354A1 (en) Neighbor Cell Synchronization Upon State Transition
US20240080688A1 (en) Beam level reporting for serving cell in early measurements
EP3695628A1 (fr) Noeud de réseau, équipement d&#39;utilisateur (ue) et procédés effectués dans celui-ci
WO2022028229A1 (fr) Procédé et appareil pour effectuer une mesure associée à une ressource
WO2020251443A1 (fr) Garantir la récence de mesure d&#39;équipement utilisateur
US20230422309A1 (en) Secondary cell group (scg) activation and deactivation at secondary node (sn) addition
US20240056910A1 (en) Secondary cell group (scg) deactivation at mobility
US20220408295A1 (en) Validity Area for Early Measurement
US11871472B2 (en) Methods and apparatuses for wireless device timer configuration
US20220116810A1 (en) Measurements for carrier aggregation/dual connectivity setup
EP4278841A1 (fr) Maintien de synchronisation de liaison descendante pour groupe de cellules secondaires (scell) désactivées

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

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

Country of ref document: EP

Kind code of ref document: A1