WO2019028732A1 - Transmissions de données au cours d'un processus d'accès aléatoire - Google Patents

Transmissions de données au cours d'un processus d'accès aléatoire Download PDF

Info

Publication number
WO2019028732A1
WO2019028732A1 PCT/CN2017/096800 CN2017096800W WO2019028732A1 WO 2019028732 A1 WO2019028732 A1 WO 2019028732A1 CN 2017096800 W CN2017096800 W CN 2017096800W WO 2019028732 A1 WO2019028732 A1 WO 2019028732A1
Authority
WO
WIPO (PCT)
Prior art keywords
timer
during
data
message
causing
Prior art date
Application number
PCT/CN2017/096800
Other languages
English (en)
Inventor
Yanji Zhang
Haitao Li
Original Assignee
Nokia Solutions And Networks Oy
Nokia Shanghai Bell Co., Ltd
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 Nokia Solutions And Networks Oy, Nokia Shanghai Bell Co., Ltd filed Critical Nokia Solutions And Networks Oy
Priority to PCT/CN2017/096800 priority Critical patent/WO2019028732A1/fr
Priority to CN201780093775.XA priority patent/CN111034327B/zh
Publication of WO2019028732A1 publication Critical patent/WO2019028732A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • the invention relates generally to wireless communications.
  • Wireless communication system design aims at reducing latencies and power consumption. This is becoming more and more relevant as machine type communication (MTC) devices and internet-of-things (IoT) emerge.
  • MTC machine type communication
  • IoT internet-of-things
  • One possibil-ity to achieve this is to allow data transfer during a random access process. How-ever, there are unsolved issues related to such data transfer.
  • Figure 1A presents a communication network, according to an embod-iment
  • Figure 1B shows a general overview of a contention based random ac-cess process
  • FIGS. 1 and 3 show methods, according to some embodiments
  • FIGS 4 to 6 illustrate signaling flow diagrams, according to some embodiments.
  • FIGS 7 to 8 illustrate apparatuses, according to some embodiments.
  • Embodiments described may be implemented in a radio system, such as in at least one of the following: Worldwide Interoperability for Micro-wave Access (WiMAX) , Global System for Mobile communications (GSM, 2G) , GSM EDGE radio access Network (GERAN) , General Packet Radio Service (GRPS) , Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA) , high-speed packet access (HSPA) , Long Term Evolution (LTE) , and/or LTE-Advanced.
  • WiMAX Worldwide Interoperability for Micro-wave Access
  • GSM Global System for Mobile communications
  • GERAN GSM EDGE radio access Network
  • GRPS General Packet Radio Service
  • UMTS Universal Mobile Telecommunication System
  • W-CDMA basic wideband-code division multiple access
  • HSPA high-speed packet access
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • 5G has been envisaged to use multiple-input-multiple-output (MIMO) multi-antenna transmission techniques, more base stations or nodes than the current network deployments of LTE (aso-called small cell concept) , including macro sites operating in co-operation with smaller local area access nodes and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple-input-multiple-output
  • 5G will likely be comprised of more than one radio access technology (RAT) , each optimized for certain use cases and/or spectrum.
  • RAT radio access technology
  • 5G mobile communications may have a wider range of use cas-es and related applications including video streaming, augmented reality, differ-ent ways of data sharing and various forms of machine type applications, includ-ing vehicular safety, different sensors and real-time control.
  • 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integradable with existing legacy radio access technologies, such as the LTE.
  • NFV network functions virtualization
  • a virtual-ized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of cus-tomized hardware.
  • Cloud computing or cloud data storage may also be utilized.
  • radio communications this may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of serv-ers, nodes or hosts.
  • SDN Software-Defined Networking
  • Big Data Big Data
  • all-IP all-IP
  • FIG. 1A illustrates an example of a communication system to which embodiments of the invention may be applied.
  • the system may comprise a con-trol node 110 providing a cell 100.
  • Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. In another point of view, the cell may define a coverage area or a service area of the access node 110.
  • the control node 110 may be an evolved Node B (eNB) as in the LTE and LTE-A, or any other apparatus ca-pable of controlling radio communication and managing radio resources within a cell.
  • eNB evolved Node B
  • the implementation may be similar to LTE-A, or e.g. apply virtualized networks, as described above.
  • the control node 110 may be called a base station, network node, or an access node.
  • the system may be a cellular communication system composed of a radio access network of access nodes, each controlling a respective cell or cells.
  • the access node 110 may provide user equipment (UE) 120 (one or more UEs) with wireless access to other networks such as the Internet.
  • the wireless access may comprise downlink (DL) communication from the eNB 110 to the UE 120 and uplink (UL) communication from the UE 120 to the eNB 110.
  • one or more local area access nodes may be arranged within a control area of a macro cell access node.
  • the local area access node may provide wireless access within a sub-cell that may be comprised within a macro cell. Examples of the sub-cell may include a micro, pico and/or femto cell. Typically, the sub-cell provides a hot spot within a macro cell.
  • the operation of the local area access node may be controlled by an access node under whose control area the sub-cell is provided.
  • the access nodes may be connected to each other with an interface.
  • LTE specifica-tions call such an interface as X2 interface.
  • IEEE 802.11 network i.e. wireless local area network, WLAN, WiFi
  • a similar interface Xw may be provided between access points.
  • Other communication methods between the access nodes may also be possible.
  • the access node 110 may be further connected via another interface to a core network 130 of the cellular communication system.
  • the LTE specifica-tions specify the core network as an evolved packet core (EPC) , and the core net-work may comprise a mobility management entity (MME) 132 and a gateway node 134.
  • EPC evolved packet core
  • MME mobility management entity
  • the MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and also handle signalling connections between the terminal devices and the core network 130.
  • the gateway node 134 may han- die data routing in the core network 130 and to/from the terminal devices.
  • the control node 110 may control a plurality of spa-tially separated access points/nodes (APs/ANs) acting as transmit/receive (Tx/Rx) nodes.
  • the access nodes may comprise e.g. a medium access control (MAC) layer and a physical (PHY) layer, whereas the “central” control node com-prises the layers above MAC layer, such as a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layers.
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource control
  • IP internet protocol
  • the embodiments may be also applicable to narrow-band (NB) IoT systems which may enable a wide range of devices and services to be connected using cellular telecommunications bands.
  • NB-IoT is a narrowband radio technol-ogy designed for the Internet of Things (IoT) and is one of technologies standard-ized by the 3rd Generation Partnership Project (3GPP) .
  • 3GPP IoT technolo-gies also suitable to implement the embodiments include MTC and eMTC (en-hanced Machine-Type Communication) .
  • NB-IoT focuses specifically on low cost, long battery life, and enabling a large number of connected devices.
  • the NB-IoT technology is deployed “in-band” in spectrum allocated to Long Term Evolution (LTE) -using resource blocks within a normal LTE carrier, or in the unused re-source blocks within a LTE carrier’s guard-band -or “standalone” for deploy-ments in dedicated spectrum.
  • LTE Long Term Evolution
  • RA random access
  • the UE 120 selects one of the available RACH preambles and transmits it in a mes-sage (Msg) 1 from the UE 120 to eNB 110.
  • Msg mes-sage
  • the UE also needs to derive identity to the network so that network can address it in next step.
  • the identity which UE will use is called RA-RNTI (random access radio network temporary identity) .
  • the eNB 110 sends a random access response (RAR) to UE 120 as Msg2 addressed to UE with the relevant RA-RNTI.
  • Msg2 may by default carry the fol-lowing information: Temporary C-RNTI, which is another identity given to the UE 120; timing advance (TA) value, which provides means for the UE to compensate for the round trip delay caused by UE’s distance from the eNB; and an uplink grant resource, which is assigned as an initial resource to UE so that it can use uplink shared channel.
  • TA timing advance
  • an uplink grant resource which is assigned as an initial resource to UE so that it can use uplink shared channel.
  • the UE 120 sends Msg3 to the network. This Msg3 may be called ′′RRC connection request message′′ .
  • the UE is identified by the temporary C-RNTI. Thereafter, the eNB may send Msg4 to the UE for contention resolution. All Msg1, Msg2, Msg3, Msg4 are MAC level messages. After the RRC connection request of Msg3 is processed, a RRC response will be sent by eNB 110 to the UE 120. In an embodi-ment, although not shown, the RRC message (e.g. the RRC Connection Setup mes-sage) is multiplexed with the Msg4 (i.e. sent with the MAC contention resolution CE).
  • the concept of RA process is considered to be well-known to a skilled person and is not discussed in-depth here.
  • New radio envisages small data transmission in an inactive state (RRC_INACTIVE) for supporting UL/DL transmissions/responses and subsequent transmissions after the Msg3 of the RA and before the radio resource control (RRC) connection setup is completed by the RRC response, without the UE having to move to an RRC Connected state (RRC_CONNECTED) . That is, it is not neces-sary to transfer the UE to the RRC Connected state even if the UE triggers the RA procedure together with data transmission. It is foreseen the similar principle could be applied for NB-IoT case to ease the specification effort.
  • RRC_INACTIVE small data transmission in an inactive state
  • RRC_CONNECTED RRC Connected state
  • the UE 120 has only few packets to be sent to the net-work 110. If the UE 120 transits to connected state just for those few UL data transmissions and then transits back to idle state, the UE power consumption and the signalling overhead will increase, which is not desired. Therefore in case UE 120 has only small amount data in the buffer, it may be preferable and beneficial to send them during RA procedure, without needing to transit UE to the connect-ed state.
  • T300 is defined in LTE to supervise the RRC connection pro-cedure.
  • the details of T300 and the related activities that are performed at the UE due to the running of the timer T300 are considered to be known by a skilled per-son, and specified by the standard specifications. For example, when T300 is run-ning, the UE by default (i.e. as specified in standard specifications) continues per-forming cell reselection, which may require neighbor cell measurements and cell evaluations.
  • the RRC response message from the access node 110 may be sent to the UE 120 with a delay, in order to first complete the user plane data transmis-sions during the RA process.
  • T300 the existing handling of T300 is followed:
  • the UE 120 power will be wasted because the UE 120 keeps on performing cell reselection related activities (e.g. monitoring of neighbor cells) also during the small data transmissions in the RA process, because this activity is tied to the T300 timer run-ning.
  • Cell re-selection evaluation may mean that the UE keeps on monitoring for DL reference signals from other cells to see if those would be more suitable for connection than the cell to which the UE tries to connect with via the RA process.
  • the late RRC response from the access node 110 may cause the expiration of T300 which cause unnecessary fake failure indica-tion to upper layer. That is because when the timer T300 ex-pires, the UE 120 may consider the connection attempt unsuc-cessful and inform upper layers.
  • the upper layer may be e.g. non-access stratum (NAS) layer.
  • NAS non-access stratum
  • T300 Too early expiration of T300 may also abort ongoing small data transmissions.
  • step 402 the UE sends preamble in Msg1 to eNB.
  • step 404 The eNB replies RAR to provide the UL grant for Msg3 and possibly for some user data transmission.
  • the UE sends the Msg3 comprising e.g. the RRC request message, MAC control ele-ment (CE) which may carry information about the buffer size at the UE, and po-tential MAC Data packet data unit (PDU) , if the UL grant in RAR allows that.
  • the eNB obtains/retrieves UE context based on the info sent in msg3.
  • step 408 possible contention resolution msg4 may be sent.
  • the eNB 110 may then in step 410 decide to allow subse-quent data transmission during RA procedure without transiting the UE to con-nected state by providing UL grant for the data remained in UL buffer.
  • the eNB may become aware of such data based on a buffer size indication conveyed in the MAC CE in Msg3 and/or the MAC PDU received in Msg3.
  • the MAC CE may be a MAC DPR CE for example, where DPR stands for Data Volume and Power Head- room Report. Consequently in step 412 the eNB may send further scheduling in-formation, such as one or more uplink grants to the UE (these are in addition to the one that has been sent in Msg2) . Also resources for downlink transmissions may be provided.
  • the UE 120 and the eNB 110 may perform the data transfer (s) (e.g. transmit and/or receive data) .
  • the UE 120 sends UL data based on the scheduling information provided by eNB 110 and receive potential DL data.
  • the response to the Msg3 is a RRC suspend message sent by the eNB in step 416, which message keeps the UE in the idle mode, as shown with reference numeral 418.
  • the eNB sends the RRC response message after all the UL and DL data transmission are completed.
  • An alternative for the RRC response may be an RRC connection resume message which may transit the UE 120 to a connected state.
  • the delay between RRC request (Msg3) from the UE 120 and the response from eNB 110 in step 416 may be enlarged, as shown with dot-dashed vertical arrow in Figure 4.
  • the T300 is started (shown with ref-erence numeral 430) by the UE 120 at the transmission of the Msg3. Due to the enlarged delay between the RRC response of step 416, the T300 timer may expire at step 432 which may cause an RRC connection failure indication to upper layers, among other undesired effects.
  • the existing han-dling of timer T300 needs to be optimized.
  • T300 is a cell specific parameter which is applied for all the UEs served by the cell for which the access node 110 provides coverage to. For those UEs which have no data transmission requirement during RA procedure, to simply set a larger value of T300 will impact the RRC connection resume procedure for those UEs. For ex-ample, the UEs have to wait for the expiration of the T300 to indicate the failure of the connection resumption attempt, which prolong the access delay and waste the power unnecessarily. Therefore, this is not a suitable solution.
  • the embodiments of the invention propose solutions which enable data transmissions during RA procedure before the UE 120 receives an RRC response from the access node 110 for the request the UE 120 has sent, and avoid unnecessary operations for the “fake fault” caused by the expiration of T300.
  • Figures 2 and 3 depict methods to accomplish this.
  • FIG. 2 illustrates a method performed e.g. by the UE 120.
  • Step 200 the UE 120 may indicate to the access node (e.g. eNB) 110 during a random access (RA) process about a need for subsequent data transfer between the UE 120 and the access node 110.
  • the UE may stop cell re-selection evaluation at a predetermined trigger before the data transfer, and then in step 204 perform the transfer of the data during the RA process, which may comprise transmitting and/or receiving of the data.
  • the cell reselection evaluation may be continued/re-started later, e.g. when the UE makes another RA-process. That is, the cell re-selection evaluation is stopped at least for the duration of the data transfer.
  • Cell re-selection evaluation is a process known to a skilled person. It may comprise activities the UE needs to perform in order to determine whether a neighboring cell is better suitable for the UE than the current cell to which the RA process is performed (e.g. whether the signal quality is better from the neighbor-ing cell) . This may comprise not only monitoring the cells but also to process the monitoring results, etc. Therefore, stopping the cell re-selection evaluation reduc-es power consumption.
  • Figure 3 then depicts the process from the access node’s point of view, such as from the eNB 110 point of view.
  • the eNB 110 determines dur-ing the RA process to allow subsequent data transfer between the eNB 110 and the UE 120.
  • the eNB 110 causes the UE 120 to stop cell re-selection evaluation at the predetermined trigger before the data transfer, and in step 304 the eNB 110 performs the transfer of the data during the RA process.
  • the data transfers denotes that the UE 120 is to send data in uplink to the eNB 110. In an embodiment, the data transfers denotes that the eNB 110 is to send data in downlink to the UE 120. In an embodiment, the data transfers denotes data transfers both in downlink and uplink directions.
  • the subsequent data comprises data that is to be transferred after a message 3 of the RA process and before an RRC level response from the access node 110 (e.g. step 416 of Figure 4) .
  • the UE may be in an RRC idle state or in an RRC inactive state while performing the data trans-fers.
  • the UE 120 may have already transmitted some (initial) small data transmissions during the msg3 of the RA process. However, in some cases the UE 120 has more data to be transmitted (i.e. data that is to be transmit-ted in idle mode after the msg3 message) , and such data is denoted as subsequent data.
  • the subsequent data may be user plane data.
  • the predetermined trigger at the UE is at least one of: reception of a configuration of a UE-specific timer during the RA process, re-ception of a configuration of a UE-specific T300 timer extension during the RA process, reception of scheduling information (e.g. step 412) for the UE during the RA process.
  • the scheduling information may be carried by PDCCH downlink con-trol information (DCI) , wherein different format is applied for UL data and DL data.
  • DCI downlink con-trol information
  • the access node 110 may cause the predetermined trigger at the UE at least one of: transmission of a configuration of a UE-specific timer during the RA process, transmission of a configuration of a UE-specific T300 timer extension during the RA process, transmission of scheduling information (e.g. step 412) for the UE during the RA process.
  • the UE-specific timer and the UE-specific T300 timer extension are ex-plained below in details.
  • FIG. 5 shows an embodiment where the T300 timer is stopped and a UE specific timer is employed. Steps 400-412 are the same as in Figure 4.
  • the UE 120 stops of a T300 timer at the predetermined trigger.
  • the T300 may be stopped before the timer T300 expires. Stopping the timer means that the cell re-selection evaluation and related activities, which are by default tied to the running of T300 by 3GPP specifications, are also stopped. These include e.g. stop-ping monitoring downlink reference signals (e.g. stopping cell re-selection related measurements) . This reduces the power consumption at the UE 120.
  • stop-ping monitoring downlink reference signals e.g. stopping cell re-selection related measurements
  • the false RRC connection failure events are not triggered to upper layers, because the T300 timer does not expire but is stopped.
  • the T300 timer is stopped at the reception of the RRC response of step 416, but, as explained above, the transfer of the subsequent data in idle mode may cause an expiration of the T300 before the RRC response message is received in step 416. Therefore, inten-tionally stopping the timer before it expires and before reception of the RRC mes-sage at step 416 may be beneficial.
  • the UE 120 may be start a new timer at the predetermined trigger in step 434.
  • This new timer may be an UE specific timer.
  • the timer may be called an UE-specific transmit timer, for example.
  • the network e.g. the access node 110
  • the network may define the new timer and indicate the new timer to the UE 120. The data transfer may then take place during the UE-specific timer running.
  • the running of the new timer does not trigger those activities on.
  • One purpose of the new timer is to keep control of the access pro-cess at the eNB, by limiting the time the UE needs to wait for the RRC response.
  • the new timer configuration may be indicated to the UE 120 by the eNB 110 in step 413A, e.g. via a MAC message.
  • the configuration of the new timer may be indicated already in system information e.g. via broadcast-ing, in the RAR message in step 402, or configured to the UE 112.
  • the duration of the new timer may be based on the amount of UL data in the buffer of the UE 120 (based on the indication in the Msg3) , and on the amount of DL data to the UE 120 in the buffer of the eNB 110. From the amount of data in the buffer (s) , the eNB 110 may make an estimation on how long the data transmission would last. For bigger amount of data, the duration for the new tim-er may be set longer by the network. Further the duration of the new timer may be based on the remaining duration of the T300. E.g. if the remaining duration is long, then the new timer may be longer, than if the remaining duration of the T300 before expiry was short.
  • one motivation for establishing/defining the new timer by the network and indicating that to the UE 120 for UE’s application is to super-vise the whole RRC procedure and decide whether and how long the UE needs to wait for the RRC response from the eNB.
  • the UE may have to detect the response from eNB endlessly in case it is lost. If the UE does not get any response from the eNB before the new timer expires, the UE indicates the failure to upper layers and the upper layer will make a decision on how to proceed fur-ther.
  • the new timer is stopped by the UE at the reception of the RRC response from the access node 110, wherein the RRC message is re-ceived as a response to the Msg3 of the RA process, e.g. in step 416.
  • the eNB 110 may send an RRC message to the UE as a response to the Msg3 of the RA process, wherein the RRC message is configured to cause a stop of the UE-specific timer.
  • the stopping is shown in Figure 5 with reference numeral 436. The stopping of the timer avoids the expiry of the timer, and thus avoids RRC connection failure indications.
  • the RRC response is an RRC suspend message which causes the UE 120 to stay in an RRC idle mode or an RRC connection resume message which causes the UE 120 to switch to an RRC con-nected mode.
  • the UE 120 may trigger a con-nection failure message to upper layers.
  • one option for the predetermined trigger for stopping the T300 and starting the new timer is the reception of a configuration of the new timer during the RA process at step 413A. That way the eNB 110 may cause the stop of the T300 and the start of the new timer at the UE by sending a message which provides the value of the new timer.
  • the message may be e.g. a MAC CE sent during the RA process in step 413A.
  • the UE 120 may stop cell re-selection related measurements as well as cell re-selection evaluation.
  • the UE 120 may already at that point be aware of the new timer configuration, since the timer configuration may have been re-ceived already e.g. in system information (such as system information block or master information block) or in a RAR message of step 404.
  • the pre-determined trigger for stopping the T300 and starting the new timer may be e.g. the reception of scheduling information at step 412 for the UE during the RA pro-cess.
  • the UE 120 stops T300, and starts the new timer.
  • UE may stop cell re-selection related measurements as well as cell re-selection evaluation. In this way the network can also control the trigger by decid-ing when and if to send the scheduling information to the UE 120.
  • a UE specific T300 timer extension is possible. This is shown in Figure 6, which is otherwise the same as Figure 5, but instead of the UE specific timer, a UE specific T300 timer extension is used. Such re-configuration for the T300 may take place in step 413B where the eNB 110 may re-configure the existing T300 timer with a longer duration. The step 413A is not present in Figure 6 because there is no need for the UE specific timer in this embodiment.
  • Alternative options for reconfiguring T300 include indicating a new value for the T300 already in sys-tem information, or in a RAR Msg2, for example.
  • the UE 120 may be config-ured to apply the new T300 value (i.e. extend the timer value) upon the prede- termined trigger in step 438 of Figure 6, based on the received reconfiguration of the T300 timer.
  • the UE and the eNB may cause an extension of the T300 timer of the UE at the predetermined trigger. Since the network decides when to cause the predetermined trigger, this allows the control of the access procedure to remain at the network side.
  • the predetermined trigger may be at least one of: reception of a configuration of a UE-specific T300 timer extension during the RA process, and a reception of the scheduling information at step 412 for the UE during the RA pro-cess.
  • the network may control the operation by causing the new T300 configuration at the UE. This happens by deciding when to send the new value (re-configuration) for the T300 or when and if to allocate resources to the UE as part of the scheduling information of step 412.
  • the UE needs to perform cell reselection related procedures (e.g. neighbor cell meas-urement, ranking, etc. ) , which are unnecessary at the time when the UE 120 is doing the proposed early data transmission (i.e. data transmissions in idle mode) . Therefore, as the T300 is extended as proposed in the embodiment of Figure 6, the UE behaviour during the extended T300 timer running may need some en-hancement. In an embodiment, the UE modifies those activities, during the T300 extension, that are by default performed due to running of the T300 timer (due to specifications, for example) .
  • cell reselection related procedures e.g. neighbor cell meas-urement, ranking, etc.
  • the modification of the activities may comprise at least stopping cell re-selection related measurements as well as the cell re-selection evaluation at the UE. This guarantees that the power consumption of the UE is reduced during the extension. The subsequent data is then transferred dur-ing the running of the extended T300.
  • the extended T300 timer is stopped by the UE at the reception of the RRC response from the access node 110, wherein the RRC message is received as a response to the Msg3 of the RA process, e.g. in step 416.
  • the eNB 110 may send an RRC message to the UE as a response to the Msg3 of the RA process, wherein the RRC message is configured to cause a stop of the extended T300 timer.
  • the stopping is shown in Figure 6 with refer-ence numeral 440. The stopping of the timer avoids the expiry of the timer, and thus avoids RRC connection failure indications.
  • the RRC re-sponse is an RRC suspend message which causes the UE 120 to stay in an RRC idle mode or an RRC connection resume message which causes the UE 120 to switch to an RRC connected mode. If the extended T300 timer expires before being stopped (i.e. before step 416/440) , then the UE indicates RRC failure to upper layers.
  • the length of the extension may be determined in the similar manner as the duration for the new timer, e.g. based on amount of data the UE has in the UL buffer.
  • the access node 110 can send the RRC set-up message after the small da-ta transmissions in steps 414A/414B and before the new timer /extended T300 timer expires.
  • the eNB 110 may decide not to allow small data transmissions and directly transit the UE to RRC connected mode by sending an RRC resume message in step 416.
  • the network if the network prefers the UE to stay in idle state to avoid unnecessary signaling overhead, the network sets the new timer /extended T300 timer to cover the estimated small data transmis-sion. Then upon the corresponding timer expiry or by the eNB 110 transmitting RRC suspend message in step 416, the UE returns back to the idle mode without connection being established.
  • the proposed embodiments leave the access procedure control to the network side.
  • the proposals provide means to stop the running T300 and start a new defined timer, or extending the currently running T300, based on the request from the eNB (steps 413A/413B) or based on whether the extra data transmission is scheduled by the eNB 110 during the RA procedure, after the UE 120 may have already transmitted first some UL data multiplexed with Msg3.
  • the proposals may provide some advantages including:
  • NPDCCH narrow-band PDCCH
  • MPDCCH MTC PDCCH
  • An embodiment as shown in Figure 7, provides an apparatus 10 com-prising a control circuitry (CTRL) 12, such as at least one processor, and at least one memory 14 including a computer program code (PROG) , wherein the at least one memory and the computer program code (PROG) , are configured, with the at least one processor, to cause the apparatus to carry out any one of the above-described processes.
  • CTRL control circuitry
  • PROG computer program code
  • the memory 14 may be implemented using any suitable da-ta storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the apparatus 10 may be or be comprised in an ac-cess node, such as a base station (also called a base transceiver station, a Node B, a radio network controller, or an evolved Node B, for example) .
  • a base station also called a base transceiver station, a Node B, a radio network controller, or an evolved Node B, for example
  • the apparatus 10 is or is comprised in the eNB 110.
  • the apparatus 10 may further comprise communication interface (TRX) 16 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols.
  • TRX communication interface
  • the apparatus 10 may also comprise a user interface 18 comprising, for example, at least one keypad, a microphone, a touch display, a display, a speaker, etc.
  • the user interface may be used to control the apparatus by a user.
  • the control circuitry 12 may comprise an access control circuitry 20 for determining whether or not to allow other devices to access the network via the apparatus 10, e.g. based on the RA process, according to any of the embodi-ments.
  • the circuitry 20 may also be responsible for handling the RA process and for allocating radio resources for data transfers, for example.
  • the circuitry 20 may also participate in data transmissions/receptions by using scheduled radio resources during the RA process, for example.
  • the control circuitry 12 may comprise a timer control circuitry 22 for controlling (e.g. setting up, defining, extending) the T300 timer and possible the new timer, according to any of the embodiments.
  • the circuitry 22 may also be responsible for provisioning the timers and thus for causing timer related activi-ties at the UE.
  • An embodiment as shown in Figure 8, provides an apparatus 50 com-prising a control circuitry (CTRL) 52, such as at least one processor, and at least one memory 54 including a computer program code (PROG) , wherein the at least one memory and the computer program code (PROG) , are configured, with the at least one processor, to cause the apparatus to carry out any one of the above-described processes.
  • CTRL control circuitry
  • PROG computer program code
  • the memory 54 may be implemented using any suitable da-ta storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the apparatus 50 may comprise the terminal device of a cellular communication system, e.g. a user equipment (UE) , a user terminal (UT) , a computer (PC) , a laptop, a tabloid computer, a cellular phone, a mobile phone, a communicator, a smart phone, a palm computer, or any other communi-cation apparatus.
  • the apparatus 50 is comprised in such a terminal device.
  • the apparatus 50 may be or comprise a module (to be attached to the UE) providing connectivity, such as a plug-in unit, an “USB dongle” , or any other kind of unit. The unit may be installed either inside the UE or attached to the UE with a connector or even wirelessly.
  • the apparatus 50 may further comprise communication interface (TRX) 56 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols.
  • TRX communication interface
  • the apparatus 50 may also comprise a user interface 58 comprising, for example, at least one keypad, a microphone, a touch display, a display, a speaker, etc.
  • the user interface may be used to control the apparatus by a user.
  • the control circuitry 52 may comprise an access control circuitry 60 for establishing connection attempt to the network e.g. via the apparatus 10, e.g. based on the RA process, according to any of the embodiments.
  • the circuitry 60 may also be responsible for data transmissions by using received UL grants and for data receptions during the RA process, for example.
  • the control circuitry 52 may comprise a timer control circuitry 62 for controlling and applying the T300 timer and the possible the new timer, accord-ing to any of the embodiments.
  • the circuitry 62 may be responsible for e.g. start-ing and stopping the timer (s) .
  • the circuitry 64 may be responsible for e.g. per-forming activities that are related to the timer expiry, for example, such indicating RRC failure to upper layers.
  • the control circuitry 52 may comprise a cell-reselection circuitry 64 for controlling cell re-selection procedures, according to any of the embodiments.
  • the circuitry 64 may be responsible for e.g. performing activities that are related to the timer running, for example, such as cell re-selection including cell monitor-ing, measurements and cell evaluation.
  • an apparatus carrying out at least some of the em-bodiments described comprises at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to carry out the functionalities according to any one of the embod-iments described.
  • the computer program code when the at least one processor exe-cutes the computer program code, the computer program code causes the appa-ratus to carry out the functionalities according to any one of the embodiments described.
  • the apparatus carrying out at least some of the embodiments comprises the at least one processor and at least one memory including a computer program code, wherein the at least one processor and the computer program code perform at least some of the functionalities ac-cording to any one of the embodiments described.
  • the at least one processor, the memory, and the computer program code form processing means for carrying out at least some of the embodiments described.
  • the apparatus carrying out at least some of the embodi-ments comprises a circuitry including at least one processor and at least one memory including computer program code. When activated, the circuitry causes the apparatus to perform the at least some of the functionalities according to any one of the embodiments described.
  • the apparatus may be shared between two physically separate devices forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
  • the apparatus may comprise a remote control unit (RCU) , such as a host computer or a server computer, operatively coupled (e.g. via a wireless or wired network) to a remote radio head (RRH) located in the base station.
  • RCU remote control unit
  • RRH remote radio head
  • at least some of the described processes may be performed by the RCU.
  • the execution of at least some of the described processes may be shared among the RRH and the RCU.
  • the RCU may generate a virtual network through which the RCU communicates with the RRH.
  • virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network.
  • Network virtualization may involve platform virtualization, often com-bined with resource virtualization.
  • Network virtualization may be categorized as external virtual networking which combines many networks, or parts of net-works, into the server computer or the host computer (i.e. to the RCU) .
  • External network virtualization is targeted to optimized network sharing.
  • Another catego-ry is internal virtual networking which provides network-like functionality to the software containers on a single system. Virtual networking may also be used for testing the terminal device.
  • the virtual network may provide flexible distribu-tion of operations between the RRH and the RCU.
  • any digital signal processing task may be performed in either the RRH or the RCU and the boundary where the responsibility is shifted between the RRH and the RCU may be selected according to implementation.
  • circuitry refers to all of the fol-lowing: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and soft-ware (and/or firmware) , such as (as applicable) : (i) a combination of proces-sor (s) or (ii) portions of processor (s) /software including digital signal proces-sor (s) , software, and memory (ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor (s) or a por-tion of a microprocessor (s) , that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry applies to all uses of this term in this application.
  • circuitry would also cover an implementation of mere-ly a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and/or firmware.
  • circuitry would also cover, for example and if applicable to the particular element, a baseband inte-grated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another net-work device.
  • At least some of the processes described in connec-tion with some of the Figures may be carried out by an apparatus comprising cor-responding means for carrying out at least some of the described processes.
  • Some example means for carrying out the processes may include at least one of the fol-lowing: detector, processor (including dual-core and multiple-core pro- cessors) , digital signal processor, controller, receiver, transmitter, en-coder, decoder, memory, RAM, ROM, software, firmware, display, user interface, display circuitry, user interface circuitry, user interface software, display software, circuit, antenna, antenna circuitry, and circuit-ry.
  • the appa-ratus (es) of embodiments may be implemented within one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field program-mable gate arrays (FPGAs) , processors, controllers, micro-controllers, micropro-cessors, other electronic units designed to perform the functions described here-in, or a combination thereof.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field program-mable gate arrays
  • processors controllers, micro-controllers, micropro-cessors, other electronic units designed to perform the functions described here-in, or a combination thereof.
  • the implementation can be carried out through modules of at least one chip set (e.g. procedures, functions, and so on) that perform the functions described herein.
  • the software codes may be stored in a memory unit and executed by processors.
  • the memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art.
  • the components of the systems described herein may be rearranged and/or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the giv-en figures, as will be appreciated by one skilled in the art.
  • Embodiments as described may also be carried out in the form of a computer process defined by a computer program or portions thereof. Embodi-ments of the methods described in connection with some of the Figures may be carried out by executing at least one portion of a computer program comprising corresponding instructions.
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
  • the computer program may be stored on a computer program distribu-tion medium readable by a computer or a processor.
  • the computer program me-dium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program medium may be a non-transitory medium. Coding of software for carrying out the embod-iments as shown and described is well within the scope of a person of ordinary skill in the art.
  • a method comprising: in-dicating, by a user equipment (UE) to an access node during a random access (RA) process, a need for subsequent data transfer between the UE and the access node; stopping cell re-selection evaluation at the UE at a predetermined trigger before the data transfer; and performing the transfer of the data during the RA process.
  • UE user equipment
  • RA random access
  • Various embodiments of the first aspect may comprise at least one fea-ture from the following bulleted list:
  • the subsequent data comprises user plane data that is to be transferred after a message 3 of the RA process and before a radio resource control (RRC) response from the access node.
  • RRC radio resource control
  • the predetermined trigger is at least one of: reception of a con-figuration of a UE-specific timer during the RA process, recep-tion of a configuration of a UE-specific T300 timer extension during the RA process, reception of scheduling information for the UE during the RA process.
  • RRC radio resource control
  • ⁇ a configuration for the UE-specific timer is received in one of the following: system information, and a medium access control (MAC) message during the RA-process.
  • system information e.g., system information
  • MAC medium access control
  • ⁇ extending a T300 timer of the UE at the predetermined trigger; modifying at least some activities, during the extension, that are by default performed due to running of the T300 timer, where-in the modification of activities comprises at least stopping cell re-selection related measurements as well as the cell re-selection evaluation; and causing the transfer of the data during the running of the extended T300.
  • ⁇ a configuration for the extended T300 timer is received in one of the following: system information, and a medium access con-trol (MAC) message during the RA-process.
  • system information e.g., system information
  • MAC medium access con-trol
  • a method comprising: determin-ing, by an access node during a random access (RA) process, to allow subsequent data transfer between the access node and a given user equipment (UE) ; causing the UE to stop cell re-selection evaluation at a predetermined trigger before the data transfer; and performing the transfer of the data during the RA process.
  • RA random access
  • UE user equipment
  • Various embodiments of the second aspect may comprise at least one feature from the following bulleted list:
  • the predetermined trigger is caused at the UE by at least one of: transmission of a configuration of a UE-specific timer during the RA process, transmission of a configuration of a UE-specific T300 timer extension during the RA process, transmission of scheduling information for the UE during the RA process.
  • ⁇ causing a stop of a T300 timer of the UE at the predetermined trigger; and causing a start of a UE-specific timer at the UE, wherein the data transfer takes place during the UE-specific timer running.
  • ⁇ causing an extension of a T300 timer of the UE at the predeter-mined trigger, wherein the extension of the T300 timer further causes, at the UE, modification of activities, during the exten-sion, that are by default related to running of the T300 timer, wherein the modification of activities comprises at least stop-ping cell re-selection related measurements as well as the cell re-selection evaluation; and causing the transfer of the data during the running of the extended T300.
  • an apparatus comprising: at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to perform operations comprising: indicating, to an access node during a random access (RA) process, a need for subsequent data transfer between the UE and the access node; stopping cell re-selection evaluation at the UE at a predetermined trigger before the data transfer; and performing the transfer of the data during the RA process.
  • RA random access
  • Various embodiments of the third aspect may comprise at least one feature from the following bulleted list:
  • the subsequent data comprises user plane data that is to be transferred after a message 3 of the RA process and be-fore a radio resource control (RRC) response from the access node.
  • RRC radio resource control
  • the predetermined trigger is at least one of: reception of a configuration of a UE-specific timer during the RA process, reception of a configuration of a UE-specific T300 timer exten-sion during the RA process, reception of scheduling information for the UE during the RA process.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus further to perform operations comprising: stop-ping a T300 timer of the UE at the predetermined trigger; and starting a UE-specific timer at the UE, wherein the data transfer takes place during the UE-specific timer running.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus further to perform operations comprising: stop-ping the UE-specific timer at a reception of a radio resource control (RRC) message from the access node, wherein the RRC message is received as a response to a message3 of the RA pro-cess.
  • RRC radio resource control
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus further to perform operations comprising: upon expiry of the UE-specific timer without reception of an RRC message, triggering a connection failure message to an upper layer.
  • a configuration for the UE-specific timer is received in one of the following: system information, a medium access con-trol (MAC) message during the RA-process.
  • MAC medium access con-trol
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus further to perform operations comprising: ex-tending a T300 timer of the UE at the predetermined trigger; modifying at least some activities, during the extension, that are by default performed due to running of the T300 timer, where-in the modification of activities comprises at least stopping cell re-selection related measurements as well as the cell re-selection evaluation; and causing the transfer of the data during the running of the extended T300.
  • a configuration for the extended T300 timer is re-ceived in one of the following: system information, a medium access control (MAC) message during the RA-process.
  • system information e.g., system information
  • MAC medium access control
  • the apparatus is a user equipment.
  • an apparatus comprising: at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus to perform operations comprising: determining during a random access (RA) process to allow subse-quent data transfer between an access node and a given user equipment (UE) ; causing the UE to stop cell re-selection evaluation at a predetermined trigger be-fore the data transfer; and performing the transfer of the data during the RA pro-cess.
  • RA random access
  • UE user equipment
  • Various embodiments of the fourth aspect may comprise at least one feature from the following bulleted list:
  • the predetermined trigger is caused at the UE by at least one of: transmission of a configuration of a UE-specific timer during the RA process, transmission of a configuration of a UE-specific T300 timer extension during the RA process, transmission of scheduling information for the UE during the RA process.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus further to perform operations comprising: caus-ing a stop of a T300 timer of the UE at the predetermined trig-ger; and causing a start of a UE-specific timer at the UE, where-in the data transfer takes place during the UE-specific timer running.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus further to perform operations comprising: send-ing an RRC message to the UE as a response to a message 3 of the RA process after the data transfer, wherein the RRC mes-sage is configured to cause a stop of the UE-specific timer.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus further to perform operations comprising: caus-ing an extension of a T300 timer of the UE at the predetermined trigger, wherein the extension of the T300 timer further causes, at the UE, modification of activities, during the extension, that are by default related to running of the T300 timer, wherein the modification of activities comprises at least stopping cell re-selection related measurements as well as the cell re-selection evaluation; and causing the transfer of the data during the run-ning of the extended T300.
  • a computer program product em-bodied on a distribution medium readable by a computer and comprising pro-gram instructions which, when loaded into an apparatus, execute the method ac-cording to the first or second aspect.
  • a computer program product com-prising program instructions which, when loaded into an apparatus, execute the method according to the first or second aspect.
  • an apparatus comprising means for performing the method according to the first or second aspect.
  • the apparatus comprises at least one processor; and at least one memory comprising computer program code, and wherein the at least one memory and the computer program code are configured, with the at least one processor to cause the apparatus to provide said means.

Landscapes

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

Abstract

L'invention concerne un procédé, consistant à : indiquer, par un équipement d'utilisateur (UE), à un nœud d'accès pendant un processus d'accès aléatoire (RA), un besoin de transfert de données ultérieur entre l'UE et le nœud d'accès; interrompre une évaluation de resélection de cellule au niveau de l'UE à un déclencheur prédéfini avant le transfert de données; et exécuter le transfert des données pendant le processus de RA.
PCT/CN2017/096800 2017-08-10 2017-08-10 Transmissions de données au cours d'un processus d'accès aléatoire WO2019028732A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2017/096800 WO2019028732A1 (fr) 2017-08-10 2017-08-10 Transmissions de données au cours d'un processus d'accès aléatoire
CN201780093775.XA CN111034327B (zh) 2017-08-10 2017-08-10 在随机接入过程期间的2数据传输

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/096800 WO2019028732A1 (fr) 2017-08-10 2017-08-10 Transmissions de données au cours d'un processus d'accès aléatoire

Publications (1)

Publication Number Publication Date
WO2019028732A1 true WO2019028732A1 (fr) 2019-02-14

Family

ID=65272944

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/096800 WO2019028732A1 (fr) 2017-08-10 2017-08-10 Transmissions de données au cours d'un processus d'accès aléatoire

Country Status (2)

Country Link
CN (1) CN111034327B (fr)
WO (1) WO2019028732A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021208880A1 (fr) * 2020-04-13 2021-10-21 华为技术有限公司 Procédé de contrôle d'état de commande de ressource radio d'un équipement utilisateur et appareil associé
WO2022052118A1 (fr) * 2020-09-14 2022-03-17 Mediatek Singapore Pte. Ltd. Appareil et procédés pour lancer une transmission de petites données dans l'état inactif nr
WO2022077220A1 (fr) 2020-10-13 2022-04-21 Nokia Shanghai Bell Co., Ltd. Restriction d'une procédure d'accès aléatoire

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022011519A1 (fr) * 2020-07-13 2022-01-20 Oppo广东移动通信有限公司 Procédé de transmission de données et dispositif terminal
WO2023082114A1 (fr) * 2021-11-10 2023-05-19 Oppo广东移动通信有限公司 Procédé et appareil de communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103052136A (zh) * 2011-10-13 2013-04-17 工业和信息化部电信传输研究所 一种lte终端的通信方法和lte终端
WO2015065257A1 (fr) * 2013-11-01 2015-05-07 Telefonaktiebolaget L M Ericsson (Publ) Dispositif sans fil, nœud de réseau d'accès hertzien et procédés dans celui-ci pour fournir une information de transfert incluant l'identité de cellule
CN106413120A (zh) * 2015-07-31 2017-02-15 华为技术有限公司 数据发送方法、装置及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2013260295B2 (en) * 2012-05-10 2017-05-04 Samsung Electronics Co., Ltd. Method and system for connectionless transmission during uplink and downlink of data packets

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103052136A (zh) * 2011-10-13 2013-04-17 工业和信息化部电信传输研究所 一种lte终端的通信方法和lte终端
WO2015065257A1 (fr) * 2013-11-01 2015-05-07 Telefonaktiebolaget L M Ericsson (Publ) Dispositif sans fil, nœud de réseau d'accès hertzien et procédés dans celui-ci pour fournir une information de transfert incluant l'identité de cellule
CN106413120A (zh) * 2015-07-31 2017-02-15 华为技术有限公司 数据发送方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA ET AL.: "Data transmission in INACTIVE", 3GPP TSG-RAN WG2 MEETING #96 R2-167706, 18 November 2016 (2016-11-18), XP051177524 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021208880A1 (fr) * 2020-04-13 2021-10-21 华为技术有限公司 Procédé de contrôle d'état de commande de ressource radio d'un équipement utilisateur et appareil associé
WO2022052118A1 (fr) * 2020-09-14 2022-03-17 Mediatek Singapore Pte. Ltd. Appareil et procédés pour lancer une transmission de petites données dans l'état inactif nr
WO2022077220A1 (fr) 2020-10-13 2022-04-21 Nokia Shanghai Bell Co., Ltd. Restriction d'une procédure d'accès aléatoire
EP4211977A4 (fr) * 2020-10-13 2023-11-08 Nokia Technologies Oy Restriction d'une procédure d'accès aléatoire

Also Published As

Publication number Publication date
CN111034327B (zh) 2023-06-20
CN111034327A (zh) 2020-04-17

Similar Documents

Publication Publication Date Title
CN110476442B (zh) 用于无线通信的覆盖增强模式切换
CN112369116B (zh) 基站网络共享配置
TWI756355B (zh) 用於為非3gpp存取建立使用者平面連接的機制
US20230362883A1 (en) Beam paging assistance
TWI766950B (zh) 新無線電量測和配置
CN113330800B (zh) 多无线电接入技术-双连通性和载波聚集中的副蜂窝小区群配置
US20200205156A1 (en) Lte coexistence with 5g nr
JP2023015354A (ja) 非アクティブ状態におけるデュアルコネクティビティの運用
US11956660B2 (en) Triggering measurements before the completion of connection resumption
WO2019137472A1 (fr) Procédé et appareil de reprise après défaillance de faisceau
US20200267084A1 (en) Methods and apparatus for signaling offset in a wireless communication system
WO2019028732A1 (fr) Transmissions de données au cours d'un processus d'accès aléatoire
US11882475B2 (en) Idle mode radio measurements
KR20210142634A (ko) 메이크-비포어-브레이크 핸드오버 동안의 소스 셀 연결 핸들링
CN113039833A (zh) 基于上行链路的前向移动性
US11570818B2 (en) Beam failure recovery
US11223991B2 (en) Connection establishment in inter-RAT communication system
JP2023502936A (ja) マルチｓｉｍ ｕｅ接続モード動作のための方法
US20210076407A1 (en) Methods and apparatus for signaling offset in a wireless communication system
EP3678441B1 (fr) Amélioration de la procédure d'accès
US12003985B2 (en) Carrier measurements
EP3314975B1 (fr) Connectivité multiple
WO2023050132A1 (fr) Améliorations de collecte de données pour découpage en tranches de réseau
EP3979754A1 (fr) Accès initial

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

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

Country of ref document: EP

Kind code of ref document: A1