WO2020114289A1 - 由用户设备执行的方法以及用户设备 - Google Patents
由用户设备执行的方法以及用户设备 Download PDFInfo
- Publication number
- WO2020114289A1 WO2020114289A1 PCT/CN2019/121269 CN2019121269W WO2020114289A1 WO 2020114289 A1 WO2020114289 A1 WO 2020114289A1 CN 2019121269 W CN2019121269 W CN 2019121269W WO 2020114289 A1 WO2020114289 A1 WO 2020114289A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- tat
- configuration
- value
- rrc
- idle state
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0078—Timing of allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
- H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
-
- 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
Definitions
- the present disclosure relates to the technical field of wireless communication, and more specifically, the present disclosure relates to a method performed by user equipment and user equipment.
- NB-IoT NarrowBand Internet of Things
- RP-181451 New WID on R16 enhancement for NB-IoT
- RP-181878 revised WID for additional MTC
- One of the goals of these two research projects is to improve the efficiency of uplink transmission to reduce the energy consumption of user equipment (User Equipment, UE).
- one feasible method is to pre-allocate available uplink resources for users in RRC idle state.
- TA upstream time advance
- the UE will delete the allocated pre-configured uplink resources and/or release the corresponding pre-configured uplink resource configuration or consider The allocated pre-configured uplink resources are invalid.
- One of the methods for the UE to determine whether the uplink is synchronized ie, whether the TA is available/valid is the TA validity timer.
- the manner in which the UE in the RRC idle state sends the uplink data through the pre-configured uplink resources is called pre-configured/preallocated uplink (Resource, PUR) transmission.
- the present disclosure mainly proposes a solution to the problem of how to implement the transmission of pre-configured uplink resources, and more specifically, a solution to the configuration and processing of the TA validity timer of the pre-configured uplink resources.
- the present disclosure provides a method performed by a user equipment and a user equipment, which can implement the configuration of a TA validity timer of a pre-configured uplink resource, and thus can realize the TA effectiveness of a pre-configured uplink resource
- the processing of the sex timer can thereby improve the efficiency of uplink transmission and reduce the energy consumption of the user equipment.
- a method performed by a user equipment UE including: the UE enters an RRC idle state, and enables pre-configured uplink resource PUR transmission; the UE determines idleness as a time alignment timer TAT for PUR transmission The configuration value of the state TAT; and the UE starts or restarts the idle state TAT according to the configuration value.
- the idle state TAT is different from the connected state TAT used for the RRC connected state or the random access process, and the PUR transmission configuration obtained from the network side by the UE before entering the RRC idle state includes the idle state TAT
- the idle TAT configuration value is adopted as the configuration value.
- the UE may adopt the public TAT included in the system information obtained from the network side before entering the RRC idle state as the configuration value when the PUR transmission configuration does not include the idle TAT configuration The configured value.
- the TAT-specific configuration value acquired from the network side before entering the RRC idle state is adopted as the configuration value.
- the UE may determine whether the TAT dedicated configuration obtained from the network side before entering the RRC idle state is saved when the PUR transmission configuration does not include the idle TAT configuration, and the UE saves the In the case of a TAT-specific configuration, the value of the TAT-specific configuration is adopted as the configuration value, and when the TAT-specific configuration is not saved, the configuration value is adopted from the network side before entering the RRC idle state The value of the public TAT configuration included in the obtained system information.
- the idle state TAT is the same as the connected state TAT used in the RRC connected state or the random access process, and the UE uses the system information obtained from the network side before entering the RRC idle state as the configuration value The value of the public TAT configuration contained in.
- the idle state TAT is the same as the connected state TAT used for the RRC connected state or the random access process
- the UE saves the TAT dedicated configuration obtained from the network side before entering the RRC idle state
- the value of the TAT-specific configuration is adopted as the configuration value
- the system information acquired from the network side before entering the RRC idle state is included as the configuration value in the case where the TAT-specific configuration is not saved
- the UE may be configured with a variety of determination methods for determining the validity of the time-aligned TA, including TAT-based determination methods and other determination methods.
- the UE may stop the corresponding TAT if it determines that the TA is invalid based on other determination methods.
- a user equipment including: a processor; and a memory that stores instructions; wherein the instructions execute the above method when executed by the processor.
- the configuration of the TA validity timer of the pre-configured uplink resource can be realized, and furthermore, the processing of the TA validity timer of the pre-configured uplink resource can be realized, thereby improving uplink Transmission efficiency and lower energy consumption of user equipment.
- FIG. 1 is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.
- FIG. 2 is a block diagram showing user equipment related to the present disclosure.
- LTE Long Term Evolution
- NR New Radio
- the base station in the present disclosure may be any type of base station, including Node B, enhanced base station eNB, or 5G communication system base station gNB, or micro base station, pico base station, macro base station, home base station, etc.; the cell may also be any of the above Cell under type base station.
- TA may be Time Advance or Time Alignment, or TA amount or TA value, etc., unless explicitly stated.
- the RRC idle state can also be the RRC inactive state (RRC inactive state) or the RRC suspended state (RRC suspended state)
- pre-configured uplink resources there are two ways, one is dedicated pre-configured uplink resources, that is, pre-allocate dedicated uplink resources for a UE, so that uplink data transmission will not cause collision conflicts, and the other is shared pre-configuration
- Uplink resources that is, the allocated uplink resources are shared by multiple UEs, may be a shared resource pool. In this manner, multiple UEs may use one resource to send uplinks, so that there may be potential competition to cause conflicts and result in transmission failure.
- a conclusion was reached at the recent 3GPP conference that it supports the allocation of dedicated pre-configured uplink resources for UEs through RRC dedicated signaling, and whether it supports the sharing of pre-configured uplink resources has not yet been determined.
- the pre-configured uplink resource is an uplink resource pre-allocated to the UE for use by an RRC message, and the pre-configured uplink resource may be allocated in the RRC connected state for uplink data transmission when the UE is in the RRC idle state and/or for RRC The connected state may also be notified to the UE through system information for uplink data transmission in the RRC idle state.
- the dedicated pre-configured resources may be configured by the base station through RRC dedicated signaling when the UE was previously in the RRC connected state, such as RRC connection release message, RRC connection reconfiguration Information, RRC connection establishment message, RRC connection recovery message, etc.
- the UE in the RRC idle state may use the dedicated pre-configured uplink resource to send uplink data.
- a UE entering the RRC idle state needs to determine that the TA is valid to use the pre-configured uplink resources.
- Current methods to determine the effectiveness of TA include:
- the serving cell changes. That is, if the serving cell where the UE camps on changes, the UE considers that the TA of the PUR acquired through the serving cell is invalid.
- the change of the serving cell where the UE is camped is usually caused by cell reselection. After the serving cell is changed, the uplink transmission path of the UE may cause the TA acquired and saved in the serving cell where the original camp is invalid.
- the downlink measurement result of the serving cell changes.
- the downlink measurement result here generally refers to the reference signal received power (Reference Signal Received Power, RSRP).
- RSRP Reference Signal Received Power
- TA validity timer When the TA validity timer is running, the UE determines that the acquired and saved TA is valid, otherwise, when the TA validity timer is not running or times out, the UE determines that the acquired and saved TA is invalid.
- the TA obtained by the UE is obtained by the UE in the RRC connected state before entering the RRC idle state.
- the UE can obtain the TA through the TA command in the random access response, or can access the control layer control element (Medium Access) through the TA command medium. Control, Control, Element, MAC) to obtain TA.
- the UE saves the TA previously used in the RRC connected state for use in PUR transmission in the idle state.
- this disclosure does not limit the above TA acquisition method.
- the TA used by the idle UE for PUR transmission may also be the last (most recent) TA previously saved or selected or processed from multiple TAs previously saved.
- a TA may be the last (most recent) TA previously saved or selected or processed from multiple TAs previously saved.
- the UE is only supported to send data in the RRC connected state or the random access process. During these processes, the UE also maintains a TA validity timer for the acquired TA, called a time alignment timer (TimeAlignmentTimer, TAT).
- TAT time alignment timer
- the UE obtains the value of the TAT through system broadcast (that is, carried in the TimeAlignmentTimerCommon information element in the system information block 2), which is called a common TAT value.
- the base station can also configure a dedicated TAT value for the UE (that is, the TimeAlignmentTimerDedicated information element in the MAC-mainconfig information element) through a dedicated RRC message such as an RRC connection reconfiguration message. At this time, the UE will use the dedicated TAT value to replace the previous system information TAT received.
- the TAT in the existing mechanism is called a connected state TAT
- the TA validity timer used for PUR transmission is called an idle state TAT or a PUR transmission TAT (referred to as TAT-PUR).
- the value of the TAT is used to control the length of time that the UE considers the uplink synchronization or uplink alignment of the serving cell where the UE resides.
- it is used to control the length of time that the UE considers the uplink synchronization or uplink alignment of the serving cell where the UE resides for PUR transmission.
- indication indication
- notification notify/notification
- notification/information information/information
- UE can refer to NB-IoT, UE, bandwidth reduction, low complexity (Bandwidth reduced, low complexity)
- the PUR may also be referred to as a pre-configured uplink grant (uplink) or a pre-allocated uplink resource (preallocated uplink) resource or a pre-allocated uplink grant (preallocated uplink grant).
- uplink uplink
- pre-allocated uplink resource pre-allocated uplink
- pre-allocated uplink grant preallocated uplink grant
- FIG. 1 is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.
- the user equipment UE performs the configuration of TAT for PUR transmission.
- the method performed by the UE includes step 101, step 102, and step 103.
- step 101 the UE enters the RRC idle state, and enables pre-configured uplink resource PUR transmission.
- the UE determines the configuration value of the idle TAT, which is the TAT used for PUR transmission.
- step 103 the UE starts or restarts the idle TAT according to the determined configuration value.
- the configuration of TAT for PUR transmission can be realized, whereby the efficiency of uplink transmission can be improved and the energy consumption of user equipment can be reduced.
- the TAT is applied to all configured PUR configurations; or the TAT may be configured for one
- the PUR configuration is specific, which means that each PUR configuration can correspond to a TAT.
- This embodiment provides a TAT configuration method for PUR transmission, which is performed on the UE.
- the idle state TAT and the connected state TAT are different timers, that is, the UE maintains two different TATs.
- Step 1 The UE enters the RRC idle state, and PUR transmission is enabled.
- the UE entering the RRC idle state may be triggered by receiving the RRC connection release message, may also be caused by the timeout of the data inactivation timer, or may be due to a wireless link failure or RRC connection re-establishment failure, etc. This is not limited in this disclosure. Entering the RRC idle state can also be expressed as leaving the RRC connected state or leaving the RRC active state.
- the "PUR transmission is enabled" means that the UE is configured with PUR and/or the configured PUR is enabled.
- the enabling may also be triggered after the UE enters the RRC connected state, that is, not triggered by an explicit enable command, for example, when the UE performs an operation to enter the RRC connected state or leave the RRC connected state, the UE enables PUR is sent, and the PUR transmission configuration received before is applied.
- the PUR transmission configuration is carried in the RRC connection release message.
- Step 2 The UE determines whether the received PUR transmission configuration includes the idle TAT configuration (such as the TimerAlignmentTimer-PUR information element or TimerAlignmentTimer-idle information element), if it is, the UE applies the idle TAT configuration included Value; if not, that is, the idle TAT configuration is not included in the PUR transmission configuration, the UE applies the value of the public TAT configuration included in the system information,
- the idle TAT configuration such as the TimerAlignmentTimer-PUR information element or TimerAlignmentTimer-idle information element
- the common TAT configuration included in the system information is the TimerAlignmentTimerCommon information element in the foregoing system information block 2.
- the common TAT configuration included in the system information is not the TimerAlignmentTimerCommon information element in the foregoing system information block 2, but another TimerAlignmentTimerCommon-PUR information element configured through the system information.
- the TimerAlignmentTimerCommon information element in the system information block 2 is mainly used for the TAT in the connected state, and in addition, a new TimerAlignmentTimerCommon-PUR information element is defined for PUR transmission in the idle state.
- the UE still uses the configuration of the TimerAlignmentTimerCommon information element in the system information block 2.
- Step 3 The UE starts the idle TAT.
- the UE when the UE receives the system information including the TimerAlignmentTimerCommon-PUR information element, it does not apply the received TimerAlignmentTimerCommon-PUR.
- the TimerAlignmentTimerCommon-PUR information element is not applied immediately when the corresponding system information is received, but when the UE enters the RRC idle state and is enabled Only applied when PUR is transmitted.
- the idle state UE with PUR configured/enabled receives the TAT configuration included in the system information (such as when the system information is updated), the TAT configuration included in the system information received is applied.
- the UE does not save the TAT-specific configuration or the PUR configuration previously received does not include the TAT configuration, the UE applies the TAT configuration included in the received system information.
- the execution conditions of the steps in this embodiment also include the way the TAT is configured to confirm the validity of the TA.
- the UE considers that the TAT is configured as a way to confirm the validity of the TA.
- the configuration of TAT for PUR transmission can be realized, whereby the efficiency of uplink transmission can be improved and the energy consumption of user equipment can be reduced.
- This embodiment provides a TAT configuration method for PUR transmission, which is performed on the UE.
- the idle state TAT and the connected state TAT are different timers, that is, the UE maintains two different TATs.
- Step i The UE enters the RRC idle state, and PUR transmission is enabled.
- Step 1 is the same as step 1 in Embodiment 1, and is not repeated here.
- Step 2 The UE determines whether the received PUR transmission configuration includes the idle TAT configuration (such as the TimerAlignmentTimer-PUR information element or TimerAlignmentTimer-idle information element), if it is, the UE applies the idle TAT configuration included Value; if not, that is, the idle TAT configuration is not included in the PUR transmission configuration, the UE applies the TAT-specific configuration saved (that is, the TimeAlignmentTimerDedicated information element in the MAC-mainconfig information element). In another implementation, if the idle TAT configuration is not included in the PUR transmission configuration, the UE further determines whether there is a saved TAT-specific configuration. If so, the UE applies the saved TAT-specific configuration for PUR transmission, if If not, the UE applies the public TAT configuration included in the system information for PUR transmission.
- the idle TAT configuration such as the TimerAlignmentTimer-PUR information element or TimerAlignmentTimer-idle information element
- the common TAT configuration included in the system information is the TimerAlignmentTimerCommon information element in the foregoing system information block 2.
- the common TAT configuration included in the system information is not the TimerAlignmentTimerCommon information element in the foregoing system information block 2, but another TimerAlignmentTimerCommon-PUR information element configured through the system information.
- the TimerAlignmentTimerCommon information element in the system information block 2 is mainly used for the TAT in the connected state, and in addition, a new TimerAlignmentTimerCommon-PUR information element is defined for PUR transmission in the idle state.
- the UE still uses the configuration of the TimerAlignmentTimerCommon information element in the system information block 2.
- the saved dedicated TAT configuration is obtained from the network side during the previous RRC connection process when the UE is in the RRC connection state.
- the UE needs to save the TAT dedicated configuration when entering the RRC idle state in step 1.
- the saved TAT specific configuration may be released when the UE enters the RRC connection state again, for example, when an RRC connection establishment or RRC connection recovery process is initiated or when an RRC connection establishment or RRC connection recovery message is received.
- the saved TAT dedicated configuration may also be released after step 2 or step 3.
- Step 3 The UE starts the idle TAT.
- the idle state UE with PUR configured/enabled receives the TAT configuration included in the system information (such as when the system information is updated), the TAT configuration included in the system information received is applied.
- the UE does not save the TAT-specific configuration or the PUR configuration previously received does not include the TAT configuration, the UE applies the TAT configuration included in the received system information.
- the execution conditions of the steps in this embodiment also include the way the TAT is configured to confirm the validity of the TA.
- the manner in which the TAT is configured to confirm the validity of the TA can be described in Embodiment 1.
- the configuration of TAT for PUR transmission can be realized, whereby the efficiency of uplink transmission can be improved and the energy consumption of user equipment can be reduced.
- This embodiment provides a TAT configuration method for PUR transmission, which is performed on the UE.
- the idle state TAT and the connected state TAT are the same timer, that is, the UE maintains the same TAT, and is used for both the connected state data transmission and the idle state PUR transmission.
- Step 1 The UE enters the RRC idle state, and PUR transmission is enabled.
- This step is the same as that described in Embodiment 1, and is not repeated here.
- Step 2 The UE applies the value of the public TAT configuration included in the system information for PUR transmission.
- the common TAT configuration included in the system information is the TimerAlignmentTimerCommon information element in the foregoing system information block 2.
- the common TAT configuration included in the system information is not the TimerAlignmentTimerCommon information element in the foregoing system information block 2, but another TimerAlignmentTimerCommon-PUR information element configured through the system information.
- the TimerAlignmentTimerCommon information element in the system information block 2 is mainly used for the TAT in the connected state, and in addition, a new TimerAlignmentTimerCommon-PUR information element is defined for PUR transmission in the idle state.
- the UE still uses the configuration of the TimerAlignmentTimerCommon information element in the system information block 2.
- step 2 the UE first determines whether there is a saved TAT-specific configuration. If yes, the UE-utilized TAT-specific configuration is used for PUR transmission. If not, the UE application system information contains The public TAT configuration is used for PUR transmission.
- Step 3 If the TAT is running, the UE restarts the TAT.
- the execution conditions of the steps in this embodiment also include the way the TAT is configured to confirm the validity of the TA.
- the manner in which the TAT is configured to confirm the validity of the TA can be described in Embodiment 1.
- the idle-state UE with PUR transmission enabled initiates a random access procedure
- the running TAT is stopped.
- the initiation of the random access process may be RRC triggered, such as RRC connection establishment trigger, or may be triggered by the MAC layer itself, such as updating the TA by triggering random access after the PUR is invalid.
- the idle state UE with PUR configured/enabled receives the TAT configuration included in the system information (such as when the system information is updated)
- the TAT configuration included in the system information received by the application is applied .
- the UE does not have the TAT-specific configuration saved, the UE applies the TAT configuration included in the system information received.
- the UE in the RRC connected state is configured with a PUR configuration for idle PUR transmission, if the TAT times out, the UE does not release the configured PUR configuration.
- the configuration of TAT for PUR transmission can be realized, whereby the efficiency of uplink transmission can be improved and the energy consumption of user equipment can be reduced.
- This embodiment proposes a TAT processing method for PUR, which is executed on the UE.
- the base station may configure more than one TA effectiveness determination method for the UE.
- more than one TA validity determination method is configured and includes a TAT-based TA validity determination method, if the UE determines that the TA is invalid, the corresponding TAT is stopped.
- the UE determining that the TA is invalid may be a TA validity determination method based on other non-TAT.
- the TA invalidation can be further expressed as PUR invalidation.
- the UE MAC stops the TAT.
- the UE considers that the PUR is invalid or the UE releases the PUR resource/configuration may be executed when the UE receives an RRC command from the base station to release the PUR resource/configuration.
- the TAT processing for PUR transmission can be realized, whereby the efficiency of uplink transmission can be improved and the energy consumption of user equipment can be reduced.
- the user equipment UE20 includes a processor 201 and a memory 202.
- the processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like.
- the memory 202 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory.
- the memory 202 stores program instructions. When the instruction is executed by the processor 201, the instruction may perform the above-mentioned method executed by the user equipment described in detail in the present disclosure.
- the program running on the device may be a program that causes a computer to realize the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU).
- the program or information processed by the program may be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
- the program for realizing the functions of the embodiments of the present disclosure may be recorded on a computer-readable recording medium.
- the corresponding functions can be realized by causing the computer system to read the programs recorded on the recording medium and execute the programs.
- the so-called "computer system” here may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
- the "computer-readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium that dynamically stores a program for a short time, or any other recording medium readable by a computer.
- circuits eg, single-chip or multi-chip integrated circuits.
- Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above devices.
- DSPs digital signal processors
- ASICs application specific integrated circuits
- FPGAs field programmable gate arrays
- a general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
- the above circuit may be a digital circuit or an analog circuit.
- the present disclosure is not limited to the above-mentioned embodiment. Although various examples of the embodiments have been described, the present disclosure is not limited to this.
- Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本公开提供了一种由用户设备执行的方法以及用户设备,所述方法包括:UE进入RRC空闲态,并且使能了预配置上行资源PUR传输;UE确定作为用于PUR传输的时间对齐定时器TAT的空闲态TAT的配置值;以及UE根据所述配置值来启动或重新启动所述空闲态TAT。
Description
本公开涉及无线通信技术领域,更具体地,本公开涉及一种由用户设备执行的方法以及用户设备。
2018年6月,在第三代合作伙伴计划(3rd Generation Partnership Project:3GPP)RAN#80次全会上,一个关于窄带物联网(NarrowBand Internet Of things,NB-IoT)进一步增强的版本16的新工作项目(参见RP-181451:New WID on R16 enhancement for NB-IoT)和一个关于机器类型通信(Machine Type Communication,MTC)进一步增强的版本16的新工作项目(参见RP-181878,revised WID for additional MTC enhancement)获得批准。这两个研究项目的目标之一就是提高上行传输的效率以降低用户设备(User Equipment,UE)的能量消耗。
在现有技术中,空闲态的UE若要发送上行数据,有两种方式:一种方式是通过无线连接控制(Radio Resource Control,RRC)连接建立/恢复过程进入到RRC连接态,即在与网络侧建立连接的RRC连接状态下发送上行数据;另一种方式是采用在版本15引入的早期数据传输机制(Early Data Transmission,EDT),在随机接入过程中的第三条消息中将小数据包一起发送给基站。对于小数据包来说,采用EDT方式显然比进入RRC连接态再发送上行数据更加节省信令开销以及消耗更少的UE能量。上述版本16中想要进一步提高上行传输的效率和降低UE能耗。在当前正在进行的提高上行传输效率以降低UE能耗的技术讨论中,一种可行的方法是为RRC空闲态的用户预分配可用的上行资源,UE在有上行数据到达时,若其上行仍处于与网络侧的同步状态(即有有效的上行时间提前(Time Advance,TA)),则可以通过预分配的上行资源完成上行传输,而无须通过随机接入过程进行上行传输或通过RRC连接建立/恢复过程进入连接态 进行上行传输。若空闲态的UE确定其上行不处于同步状态,则UE不可以使用预配置的上行资源,此时UE会删除所分配的预配置上行资源和/或释放相应的预配置上行资源配置或者认为所分配的预配置上行资源无效。UE确定上行是否同步(即TA是否可用/有效)的方法之一就是TA有效性定时器。
本公开中,RRC空闲态的UE通过预配置的上行资源发送上行数据的方式称为预配置上行资源(Preconfigured/preallocated Uplink Resource,PUR)发送。本公开主要就如何实现预配置上行资源发送的问题提出解决方法,更具体地,就预配置上行资源的TA有效性定时器的配置和处理提出解决方法。
发明内容
为了解决上述问题中的至少一部分,本公开提供了一种由用户设备执行的方法以及用户设备,能够实现预配置上行资源的TA有效性定时器的配置,进而能够实现预配置上行资源的TA有效性定时器的处理,由此能够提高上行传输的效率和降低用户设备的能量消耗。
根据本公开,提出了一种由用户设备UE执行的方法,包括:UE进入RRC空闲态,并且使能了预配置上行资源PUR传输;UE确定作为用于PUR传输的时间对齐定时器TAT的空闲态TAT的配置值;以及UE根据所述配置值来启动或重新启动所述空闲态TAT。
在上述方法中,可以是,所述空闲态TAT与用于RRC连接态或随机接入过程的连接态TAT不同,UE在进入RRC空闲态之前从网络侧获取的PUR传输配置中包含空闲态TAT配置的情况下,作为所述配置值而采用所述空闲态TAT配置的值。
在上述方法中,可以是,UE在所述PUR传输配置中不包含空闲态TAT配置的情况下,作为所述配置值,采用进入RRC空闲态之前从网络侧获取的***信息中包含的公共TAT配置的值。
在上述方法中,可以是,UE在所述PUR传输配置中不包含空闲态TAT配置的情况下,作为所述配置值,采用进入RRC空闲态之前从网络侧获取的TAT专用配置的值。
在上述方法中,可以是,UE在所述PUR传输配置中不包含空闲态 TAT配置的情况下,判断是否保存有进入RRC空闲态之前从网络侧获取的TAT专用配置,UE在保存有所述TAT专用配置的情况下,作为所述配置值而采用所述TAT专用配置的值,在未保存有所述TAT专用配置的情况下,作为所述配置值而采用进入RRC空闲态之前从网络侧获取的***信息中包含的公共TAT配置的值。
在上述方法中,可以是,所述空闲态TAT与用于RRC连接态或随机接入过程的连接态TAT相同,UE作为所述配置值而采用进入RRC空闲态之前从网络侧获取的***信息中包含的公共TAT配置的值。
在上述方法中,可以是,所述空闲态TAT与用于RRC连接态或随机接入过程的连接态TAT相同,UE在保存有进入RRC空闲态之前从网络侧获取的TAT专用配置的情况下,作为所述配置值而采用所述TAT专用配置的值,在未保存有所述TAT专用配置的情况下,作为所述配置值而采用进入RRC空闲态之前从网络侧获取的***信息中包含的公共TAT配置的值。
在上述方法中,可以是,UE被配置了多种确定时间对齐TA的有效性的确定方式,包括基于TAT的确定方式和其他确定方式。
在上述方法中,可以是,UE在基于其他确定方式而确定TA无效的情况下,停止对应的TAT。
根据本公开,提出了一种用户设备,包括:处理器;以及存储器,存储有指令;其中,所述指令在由所述处理器运行时执行上述方法。
发明效果
根据本公开的由用户设备执行的方法以及用户设备,能够实现预配置上行资源的TA有效性定时器的配置,进而能够实现预配置上行资源的TA有效性定时器的处理,由此能够提高上行传输的效率和降低用户设备的能量消耗。
通过下文结合附图的详细描述,本公开的上述和其它特征将会变得更加明显,其中:
图1是示出了根据本公开的实施例的由用户设备执行的方法的流程图。
图2是表示本公开所涉及的用户设备的框图。
根据结合附图对本公开示例性实施例的以下详细描述,本公开的其它方面、优势和突出特征对于本领域技术人员将变得显而易见。
在本公开中,术语“包括”和“含有”及其派生词意为包括而非限制;术语“或”是包含性的,意为和/或。
在本说明书中,下述用于描述本公开原理的各种实施例只是说明,不应该以任何方式解释为限制公开的范围。参照附图的下述描述用于帮助全面理解由权利要求及其等同物限定的本公开的示例性实施例。下述描述包括多种具体细节来帮助理解,但这些细节应认为仅仅是示例性的。因此,本领域普通技术人员应认识到,在不背离本公开的范围和精神的情况下,可以对本文中描述的实施例进行多种改变和修改。此外,为了清楚和简洁起见,省略了公知功能和结构的描述。此外,贯穿附图,相同参考数字用于相似功能和操作。
下文以长期演进(Long Term Evolution,LTE)移动通信***中的NB-IoT及其后续的演进版本作为示例应用环境,具体描述了根据本公开的多个实施方式。然而,需要指出的是,本公开不限于以下实施方式,而是可适用于更多其它的无线通信***,如机器类型通信(Machine Type Communication,MTC)***中,也可以用于5G下一代无线通信***(New Radio,NR)中。
本公开中的基站可以是任何类型基站,包含Node B、增强基站eNB,也可以是5G通信***基站gNB、或者微基站、微微基站、宏基站、家庭基站等;所述小区也可以是上述任何类型基站下的小区。在本公开中,在无明确说明的前提下,TA可以是时间提前(Time Advance)也可以是时间对齐(Time Alignment),也可称TA量或TA值等。RRC空闲态也可以是RRC非活动态(RRC inactive状态)或者RRC挂起状态(RRC suspended状态)
对于预配置上行资源,可以有两种方式,一种是专用预配置上行资源,即为一个UE预分配专用的上行资源,这样上行数据传输不会产生碰撞冲突,另一种是共享的预配置上行资源,即所分配的上行资源是多个UE共享的,可以是一个共享资源池,这种方式下,多个UE可能使用一个资源 发送上行,从而存在潜在的竞争引起冲突而导致发送失败。最近的3GPP会议上达成结论是支持通过RRC专用信令为UE分配专用预配置上行资源,而是否支持共享预配置上行资源尚未定论。预配置上行资源是通过RRC消息预先分配给UE使用的上行资源,所述预配置上行资源可以是在RRC连接态分配的用于当UE处于RRC空闲态时的上行数据传输和/或用于RRC连接态,也可以是通过***信息告知给UE用于RRC空闲态时的上行数据传输。
对于专用的预配置上行资源来说,专用的预配置资源可以是所述UE在之前处于RRC连接状态时由基站通过RRC专用信令对其进行配置的,如RRC连接释放消息、RRC连接重配置信息、RRC连接建立消息、RRC连接恢复消息等。处于RRC空闲态的UE可以使用所述专用预配置上行资源发送上行数据。
如背景技术所述,进入到RRC空闲态的UE需要确定TA有效才能使用预配置上行资源。目前确定TA有效性的方法包括:
1.服务小区改变。即若UE所驻留的服务小区发生改变,则UE认为通过该服务小区所获取的PUR的TA无效。UE所驻留的服务小区的改变通常是由小区重选引起的,变更了服务小区后,UE的上行发送路径可能导致在原来所驻留的服务小区中所获取和保存的TA无效。
2.服务小区的下行测量结果发生变化。这里的下行测量结果一般指的是参考信号接收功率(Reference Signal Received Power,RSRP)。当UE所驻留的服务小区的下行测量结果发生改变超过某个门限值时,UE认为所获取和保存的TA无效。
3.TA有效性定时器。在TA有效性定时器运行时,UE判定所获取和保存的TA有效,否则,在TA有效性定时器不运行或超时时,UE判定所获取和保存的TA无效。
上述UE所获取的TA是UE在进入RRC空闲态之前在RRC连接状态所获取的。在之前的RRC连接建立过程中或RRC连接持续过程中的随机接入过程中UE可以通过随机接入响应中的TA命令来获取TA,或者可以通过TA命令媒介接入控制层控制元素(Medium Access Control Control Element,MAC CE)来获得TA。在UE进入RRC空闲态后,UE保存之前在RRC连接态所使用的TA,以用于在空闲态的PUR传输所使用。但 本公开并不限定上述TA获取方法,比如空闲态UE用于PUR传输所使用的TA也可以是之前保存的最后(最近)一次的TA或者之前保存的多次TA中所选择出来或处理得到的一个TA。
在现有机制中,仅支持UE在RRC连接态或随机接入过程中来发送数据。UE在这些过程中也会为所获得的TA维护一个TA有效性定时器,称为时间对齐定时器(TimeAlignmentTimer,TAT)。对于用于连接态的TAT,UE通过***广播(即***信息块2中的TimeAlignmentTimerCommon信息元素中携带)获取TAT的值,称其为公共TAT值。但基站也可以通过专用RRC消息如RRC连接重配置消息为UE配置一个专用TAT值(即MAC-mainconfig信息元素中的TimeAlignmentTimerDedicated信息元素),此时UE会使用专用TAT值来取代之前在***信息中收到的TAT。
本公开下述实施例中,就用于PUR传输的TA有效性定时器的配置和操作给出实现方法。为了方便描述,称现有机制中的TAT为连接态TAT,用于PUR传输的TA有效性定时器称为空闲态TAT或PUR传输TAT(简称TAT-PUR)。所述TAT的值用于控制UE认为其驻留的服务小区上行同步或上行对齐的时间长度。当用于PUR传输时,用于控制UE认为对于PUR传输其驻留的服务小区上行同步或上行对齐的时间长度。
本公开下述实施例中,指示(indicate/indication)和通知(notify/notification)或知会/信息(inform/information)可以互换。UE可以指NB-IoT UE、带宽降低低复杂度(Bandwidth reduced Low complexity
,BL)UE、或在增强覆盖(enhanced coverage)中的UE、也可以是其他UE如5G NR UE。本公开中,所述PUR也可称为预配置上行许可(uplink grant)或预分配上行资源(preallocated uplink resource)或预分配上行许可(preallocated uplink grant)等。不同的实施例之间也可以结合工作。
图1是示出了根据本公开的实施例的由用户设备执行的方法的流程图。在该方法中,用户设备UE执行了用于PUR传输的TAT的配置。
具体而言,如图1所示,UE执行的方法包括步骤101、步骤102和步骤103。在步骤101中,UE进入RRC空闲态,并且使能了预配置上行资源PUR传输。在步骤102中,UE确定空闲态TAT的配置值,该空 闲态TAT是用于PUR传输的TAT。在步骤103中,UE根据所确定的配置值来启动或重新启动空闲态TAT。
根据上述方法,能够实现用于PUR传输的TAT的配置,由此能够提高上行传输的效率和降低用户设备的能量消耗。
以下,详细描述本公开的若干实施例。在下述实施例中,若UE被配置了多于一个PUR配置(即对应了多个PUR资源),则所述TAT是对所有配置的PUR配置作用的;或者也可以是所述TAT是对一个PUR配置特定的,也就是说可以对每一个PUR配置对应一个TAT。
UE侧的实施例
实施例1
该实施例给出了一种用于PUR传输的TAT配置方式,在UE上执行。优选地,空闲态TAT和连接态TAT是不同的定时器,即UE维护两个不同的TAT。
步骤1:UE进入RRC空闲状态,且使能了PUR传输。
该步骤中,UE进入RRC空闲状态可以是接收到RRC连接释放消息所触发的,也可以是数据非激活定时器超时所引起的,或者也可以是由于无线链路失败或RRC连接重建立失败等引起的,本公开中对此不作限制。进入RRC空闲状态也可以表述为离开RRC连接状态或者离开RRC活动状态。所述“使能了PUR传输”指的是UE被配置了PUR且/或所配置的PUR被使能。所述使能也可以是UE进入RRC连接状态后所触发的,即并非通过显式的使能命令所触发的,比如当UE执行进入RRC连接状态或离开RRC连接状态的操作时,UE使能PUR发送,并应用之前所收到的PUR传输配置。优选地,所述PUR传输配置是通过RRC连接释放消息中所携带的。
步骤2:UE判断所收到的PUR传输配置中是否包含了空闲态TAT配置(如表示为TimerAlignmentTimer-PUR信息元素或称TimerAlignmentTimer-idle信息元素),若是,则UE应用所包含的空闲态TAT配置的值;若否,即PUR传输配置中未包含空闲态TAT配置,则UE应用***信息中所包含的公共TAT配置的值,
优选地,所述***信息中所包含的公共TAT配置是前述***信息块2 中的TimerAlignmentTimerCommon信息元素。备选地,所述***信息中所包含的公共TAT配置不是前述***信息块2中的TimerAlignmentTimerCommon信息元素,而是另一通过***信息所配置的TimerAlignmentTimerCommon-PUR信息元素。在这种实现方式中,***信息块2中的TimerAlignmentTimerCommon信息元素主要用于连接态的TAT,而另外通过定义一个新的TimerAlignmentTimerCommon-PUR信息元素来用于空闲态下的PUR传输。
可选地,若***信息中TimerAlignmentTimerCommon-PUR信息元素不存在(即未配置),则UE仍使用***信息块2中的TimerAlignmentTimerCommon信息元素的配置。
步骤3:UE启动空闲态TAT。
可选地,UE在接收到包含TimerAlignmentTimerCommon-PUR信息元素的***信息时,并不应用所收到的TimerAlignmentTimerCommon-PUR。也就是说,不同于传输的RRC配置在接收到时就立即应用,TimerAlignmentTimerCommon-PUR信息元素并不是在接收到相应的***信息时就立即应用的,而是在UE进入RRC空闲态且使能了PUR传输时才应用的。
在一种实现方式中,配置/使能了PUR的空闲态UE在接收了***信息中包含的TAT配置时(比如在***信息更新时),应用所收到的***信息中包含的TAT配置。可选地,若UE没有保存的TAT专用配置或者在之前收到的PUR配置中不包含TAT配置,则UE应用所收到的***信息中包含的TAT配置。
此外,如前所述,UE确认TA有效性的方式可以有多种,所以可选地,在该实施例中的步骤的执行条件,还包括TAT被配置为确认TA有效性的方式。TAT被配置为确认TA有效性的方式可以使通过一个显示信息元素来配置的(如TA validation::=SEQUENCE{TAT,serving cell DL RSRP,serving cell change,......}),也可以使通过上述TAT的配置来隐式指示的。在一种实现方式中,若***信息中包含了TimerAlignmentTimerCommon-PUR信息元素(或称TimerAlignmentTimerCommon-idle信息元素)或者PUR传输配置中包含了TimerAlignmentTimer-PUR信息元素(或称TimerAlignmentTimer-idle信息元素),则UE认为TAT被配置为确认TA有效性的方式。
根据实施例1,能够实现用于PUR传输的TAT的配置,由此能够提高上行传输的效率和降低用户设备的能量消耗。
实施例2
该实施例给出了一种用于PUR传输的TAT配置方式,在UE上执行。优选地,空闲态TAT和连接态TAT是不同的定时器,即UE维护两个不同的TAT。
步骤i:UE进入RRC空闲状态,且使能了PUR传输。
步骤1与实施例1中步骤1相同,此处不赘述。
步骤2:UE判断所收到的PUR传输配置中是否包含了空闲态TAT配置(如表示为TimerAlignmentTimer-PUR信息元素或称TimerAlignmentTimer-idle信息元素),若是,则UE应用所包含的空闲态TAT配置的值;若否,即PUR传输配置中未包含空闲态TAT配置,则UE应用所保存的TAT专用配置(即MAC-mainconfig信息元素中的TimeAlignmentTimerDedicated信息元素)。在另一种实现方式中,若PUR传输配置中未包含空闲态TAT配置,则UE进一步判断是否有保存的TAT专用配置,若有,则UE应用所保存的TAT专用配置用于PUR传输,若没有,则UE应用***信息中所包含的公共TAT配置用于PUR传输。
优选地,所述***信息中所包含的公共TAT配置是前述***信息块2中的TimerAlignmentTimerCommon信息元素。备选地,所述***信息中所包含的公共TAT配置不是前述***信息块2中的TimerAlignmentTimerCommon信息元素,而是另一通过***信息所配置的TimerAlignmentTimerCommon-PUR信息元素。在这种实现方式中,***信息块2中的TimerAlignmentTimerCommon信息元素主要用于连接态的TAT,而另外通过定义一个新的TimerAlignmentTimerCommon-PUR信息元素来用于空闲态下的PUR传输。
可选地,若***信息中TimerAlignmentTimerCommon-PUR信息元素不存在(即未配置),则UE仍使用***信息块2中的TimerAlignmentTimerCommon信息元素的配置。
在步骤2中,所述保存的TAT专用配置,是UE处于RRC连接状态时在之前的RRC连接过程中从网络侧获取的。若要用于空闲态的PUR传输,则UE在步骤1中进入RRC空闲状态时要保存所述TAT专用配置。 可选地,所保存的TAT专用配置可以在UE再次进入RRC连接态时释放,比如在发起RRC连接建立或RRC连接恢复过程时或者在收到RRC连接建立或RRC连接恢复消息时。可选地,也可以在步骤2或步骤3之后释放所保存的TAT专用配置。
步骤3:UE启动空闲态TAT。
在一种实现方式中,配置/使能了PUR的空闲态UE在接收了***信息中包含的TAT配置时(比如在***信息更新时),应用所收到的***信息中包含的TAT配置。可选地,若UE没有保存的TAT专用配置或者在之前收到的PUR配置中不包含TAT配置,则UE应用所收到的***信息中包含的TAT配置。
此外,如前所述,UE确认TA有效性的方式可以有多种,所以可选地,在该实施例中的步骤的执行条件,还包括TAT被配置为确认TA有效性的方式。TAT被配置为确认TA有效性的方式可以参见实施例1中所述。
根据实施例2,能够实现用于PUR传输的TAT的配置,由此能够提高上行传输的效率和降低用户设备的能量消耗。
实施例3:
该实施例给出了一种用于PUR传输的TAT配置方式,在UE上执行。优选地,空闲态TAT和连接态TAT是同一个定时器,即UE维护同一个TAT,既用于连接态的数据传输也用于空闲态的PUR传输。
步骤1:UE进入RRC空闲状态,且使能了PUR传输。
该步骤和实施例1中所述相同,此处不赘述。
步骤2:UE应用***信息中所包含的公共TAT配置的值用于PUR传输。
优选地,所述***信息中所包含的公共TAT配置是前述***信息块2中的TimerAlignmentTimerCommon信息元素。备选地,所述***信息中所包含的公共TAT配置不是前述***信息块2中的TimerAlignmentTimerCommon信息元素,而是另一通过***信息所配置的TimerAlignmentTimerCommon-PUR信息元素。在这种实现方式中,***信息块2中的TimerAlignmentTimerCommon信息元素主要用于连接态的TAT,而另外通过定义一个新的TimerAlignmentTimerCommon-PUR信息元素来用于空闲态下的PUR传输。
可选地,若***信息中TimerAlignmentTimerCommon-PUR信息元素不存在(即未配置),则UE仍使用***信息块2中的TimerAlignmentTimerCommon信息元素的配置。
在另一种实现方式中,步骤2中UE先判断是否有保存的TAT专用配置,若有,则UE应用所保存的TAT专用配置用于PUR传输,若没有,则UE应用***信息中所包含的公共TAT配置用于PUR传输。
所述保存的TAT专用配置参见实施例2中所述。
步骤3:如果TAT正在运行,UE重新启动TAT。
不同于现有机制中在UE进入RRC空闲态时会重置MAC而停止正在运行的TAT,在该实施例中,考虑到使用同一个TAT应用于连接态的数据传输和空闲态的PUR传输,在UE进入RRC空闲态执行重置MAC时,若配置和/或使能了PUR传输,则不停止正在运行的TAT,而是保持其运行或者如步骤3中重启TAT。
此外,如前所述,UE确认TA有效性的方式可以有多种,所以可选地,在该实施例中的步骤的执行条件,还包括TAT被配置为确认TA有效性的方式。TAT被配置为确认TA有效性的方式可以参见实施例1中所述。
在一种实现方式中,当使能了PUR传输的空闲态UE发起随机接入过程时,停止正在运行的TAT。所述随机接入过程的发起可以是RRC触发的如RRC连接建立触发的,也可以是MAC层自己触发的,比如PUR无效后通过触发随机接入来更新TA等。
在另一种实现方式中,配置/使能了PUR的空闲态UE在接收了***信息中包含的TAT配置时(比如在***信息更新时),应用所收到的***信息中包含的TAT配置。可选地,若UE没有保存的TAT专用配置,则UE应用所收到的***信息中包含的TAT配置。
在一种实现方式中,处于RRC连接态的UE若配置了用于空闲态PUR传输的PUR配置,若TAT超时,则UE不释放已配置的PUR配置。
根据实施例3,能够实现用于PUR传输的TAT的配置,由此能够提高上行传输的效率和降低用户设备的能量消耗。
实施例4
该实施例提出了一种用于PUR的TAT的处理方法,在UE上执行。
如前所述,确定TA有效性的方法有多种,基站可以为UE配置多于 一种TA有效性确定方法。当配置了多于一种TA有效性确定方法且其中包括基于TAT的TA有效性确定方法时,若UE确定TA无效,则停止对应的TAT。此处UE确定TA无效可以是基于其他非TAT的TA有效性确定方式。所述TA无效也可进一步表述为PUR无效。
在另一种实现方式中,当UE认为PUR无效或UE释放PUR资源和/或PUR配置时,UE MAC停止所述TAT。所述UE认为PUR无效或UE释放PUR资源/配置可以是当UE收到来自基站的用于释放PUR资源/配置的RRC命令时执行。
根据实施例4,能够实现用于PUR传输的TAT的处理,由此能够提高上行传输的效率和降低用户设备的能量消耗。
图2是表示本公开所涉及的用户设备UE的框图。如图2所示,该用户设备UE20包括处理器201和存储器202。处理器201例如可以包括微处理器、微控制器、嵌入式处理器等。存储器202例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器202上存储有程序指令。该指令在由处理器201运行时,可以执行本公开详细描述的由用户设备执行的上述方法。
运行在根据本公开的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器***中。
用于实现本公开各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机***读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机***”可以是嵌入在该设备中的计算机***,可以包括操作***或硬件(如***设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如, 单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器,也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路,也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下,本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外,本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例,但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备,如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上,已经参考附图对本公开的实施例进行了详细描述。但是,具体的结构并不局限于上述实施例,本公开也包括不偏离本公开主旨的任何设计改动。另外,可以在权利要求的范围内对本公开进行多种改动,通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外,上述实施例中所描述的具有相同效果的组件可以相互替代。
Claims (10)
- 一种由用户设备UE执行的方法,包括:UE进入RRC空闲态,并且使能了预配置上行资源PUR传输;UE确定作为用于PUR传输的时间对齐定时器TAT的空闲态TAT的配置值;以及UE根据所述配置值来启动或重新启动所述空闲态TAT。
- 根据权利要求1所述的方法,其中,所述空闲态TAT与用于RRC连接态或随机接入过程的连接态TAT不同,UE在进入RRC空闲态之前从网络侧获取的PUR传输配置中包含空闲态TAT配置的情况下,作为所述配置值而采用所述空闲态TAT配置的值。
- 根据权利要求2所述的方法,其中,UE在所述PUR传输配置中不包含空闲态TAT配置的情况下,作为所述配置值,采用进入RRC空闲态之前从网络侧获取的***信息中包含的公共TAT配置的值。
- 根据权利要求2所述的方法,其中,UE在所述PUR传输配置中不包含空闲态TAT配置的情况下,作为所述配置值,采用进入RRC空闲态之前从网络侧获取的TAT专用配置的值。
- 根据权利要求2所述的方法,其中,UE在所述PUR传输配置中不包含空闲态TAT配置的情况下,判断是否保存有进入RRC空闲态之前从网络侧获取的TAT专用配置,UE在保存有所述TAT专用配置的情况下,作为所述配置值而采用所述TAT专用配置的值,在未保存有所述TAT专用配置的情况下,作为所述配置值而采用进入RRC空闲态之前从网络侧获取的***信息中包含的公共TAT配置的值。
- 根据权利要求1所述的方法,其中,所述空闲态TAT与用于RRC连接态或随机接入过程的连接态TAT相同,UE作为所述配置值而采用进入RRC空闲态之前从网络侧获取的 ***信息中包含的公共TAT配置的值。
- 根据权利要求1所述的方法,其中,所述空闲态TAT与用于RRC连接态或随机接入过程的连接态TAT相同,UE在保存有进入RRC空闲态之前从网络侧获取的TAT专用配置的情况下,作为所述配置值而采用所述TAT专用配置的值,在未保存有所述TAT专用配置的情况下,作为所述配置值而采用进入RRC空闲态之前从网络侧获取的***信息中包含的公共TAT配置的值。
- 根据权利要求1所述的方法,其中,UE被配置了多种确定时间对齐TA的有效性的确定方式,包括基于TAT的确定方式和其他确定方式。
- 根据权利要求8所述的方法,其中,UE在基于其他确定方式而确定TA无效的情况下,停止对应的TAT。
- 一种用户设备,包括:处理器;以及存储器,存储有指令;其中,所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP19892149.6A EP3893569A1 (en) | 2018-12-06 | 2019-11-27 | Method executed by user equipment and user equipment |
US17/297,864 US20220039098A1 (en) | 2018-12-06 | 2019-11-27 | Method performed by user equipment, and user equipment |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811491037.3A CN111294928A (zh) | 2018-12-06 | 2018-12-06 | 由用户设备执行的方法以及用户设备 |
CN201811491037.3 | 2018-12-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020114289A1 true WO2020114289A1 (zh) | 2020-06-11 |
Family
ID=70975180
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/121269 WO2020114289A1 (zh) | 2018-12-06 | 2019-11-27 | 由用户设备执行的方法以及用户设备 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20220039098A1 (zh) |
EP (1) | EP3893569A1 (zh) |
CN (1) | CN111294928A (zh) |
WO (1) | WO2020114289A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022031704A1 (en) * | 2020-08-03 | 2022-02-10 | Kyungmin Park | Methods, apparatuses and system for uplink resource configuration |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110831145B (zh) | 2018-08-09 | 2021-05-18 | 华为技术有限公司 | 无线通信的方法和装置 |
CA3126402A1 (en) * | 2019-01-11 | 2020-02-20 | Zte Corporation | Preconfiguring dedicated resource information in idle mode |
JP7220798B2 (ja) * | 2019-02-01 | 2023-02-10 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | 到達時間差ベースのタイミングアドバンス変更検出 |
US11582829B2 (en) * | 2019-11-01 | 2023-02-14 | Qualcomm Incorporated | Preconfigured uplink resource release counter management |
US11758497B2 (en) * | 2019-12-23 | 2023-09-12 | Qualcomm Incorporated | Timing advance simplification for stationary and low mobility user equipments |
US20230262586A1 (en) * | 2020-07-03 | 2023-08-17 | Lenovo (Beijing) Ltd. | Methods and apparatuses for access control of a small size and infrequent data transmission |
CN114071687B (zh) * | 2020-07-31 | 2023-04-07 | 维沃移动通信有限公司 | 上行定时提前ta值处理方法、装置及终端 |
KR20230048006A (ko) * | 2020-08-06 | 2023-04-10 | 퀄컴 인코포레이티드 | 미리 구성된 업링크 리소스들을 통한 스몰 데이터 전달을 위한 멀티-빔 기법 |
CN114390545A (zh) * | 2020-10-16 | 2022-04-22 | 展讯通信(上海)有限公司 | 数据传输处理方法及相关装置 |
CN115175276A (zh) * | 2021-04-06 | 2022-10-11 | 展讯通信(上海)有限公司 | 数据处理方法、装置和用户设备 |
CA3222885A1 (en) * | 2021-08-04 | 2023-02-09 | Lenovo (Beijing) Limited | Methods and apparatuses for determining synchronization validity timer |
CN118104322A (zh) * | 2021-12-15 | 2024-05-28 | Oppo广东移动通信有限公司 | 上行同步中的定时提前量维持方法、终端设备和网络设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101835271A (zh) * | 2009-03-12 | 2010-09-15 | 华为技术有限公司 | 一种资源释放和分配的方法、装置及网络设备 |
CN102014476A (zh) * | 2009-10-10 | 2011-04-13 | 大唐移动通信设备有限公司 | 上行同步方法、***和设备 |
US20160100409A1 (en) * | 2012-01-25 | 2016-04-07 | Ofinno Technologies, Llc | Wireless Multicarrier Random Access Process |
CN108337728A (zh) * | 2017-01-19 | 2018-07-27 | 中兴通讯股份有限公司 | 一种定时提前维护方法、装置及*** |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012153993A2 (ko) * | 2011-05-10 | 2012-11-15 | 삼성전자 주식회사 | 반송파 집적 기술을 사용하는 무선통신시스템에서 타임 정렬 타이머를 적용하는 방법 및 장치 |
US11147117B2 (en) * | 2018-09-28 | 2021-10-12 | Mediatek Singapore Pte. Ltd. | Timing advance validation for transmission in preconfigured uplink resources in NB-IoT |
US10667323B1 (en) * | 2018-11-27 | 2020-05-26 | Asustek Computer Inc. | Method and apparatus for releasing preconfigured uplink resources configuration in a wireless communication system |
-
2018
- 2018-12-06 CN CN201811491037.3A patent/CN111294928A/zh active Pending
-
2019
- 2019-11-27 US US17/297,864 patent/US20220039098A1/en not_active Abandoned
- 2019-11-27 EP EP19892149.6A patent/EP3893569A1/en not_active Withdrawn
- 2019-11-27 WO PCT/CN2019/121269 patent/WO2020114289A1/zh unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101835271A (zh) * | 2009-03-12 | 2010-09-15 | 华为技术有限公司 | 一种资源释放和分配的方法、装置及网络设备 |
CN102014476A (zh) * | 2009-10-10 | 2011-04-13 | 大唐移动通信设备有限公司 | 上行同步方法、***和设备 |
US20160100409A1 (en) * | 2012-01-25 | 2016-04-07 | Ofinno Technologies, Llc | Wireless Multicarrier Random Access Process |
CN108337728A (zh) * | 2017-01-19 | 2018-07-27 | 中兴通讯股份有限公司 | 一种定时提前维护方法、装置及*** |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022031704A1 (en) * | 2020-08-03 | 2022-02-10 | Kyungmin Park | Methods, apparatuses and system for uplink resource configuration |
US11576194B2 (en) | 2020-08-03 | 2023-02-07 | Ofinno, Llc | Uplink resource configuration |
CN116171631A (zh) * | 2020-08-03 | 2023-05-26 | 欧芬诺有限责任公司 | 用于上行链路资源配置的方法、装置和*** |
JP2023535995A (ja) * | 2020-08-03 | 2023-08-22 | オフィノ, エルエルシー | アップリンクリソース構成 |
EP4246861A2 (en) | 2020-08-03 | 2023-09-20 | Ofinno, LLC | Methods, apparatuses and system for uplink resource configuration |
JP7362093B2 (ja) | 2020-08-03 | 2023-10-17 | オフィノ, エルエルシー | アップリンクリソース構成 |
EP4246861A3 (en) * | 2020-08-03 | 2023-12-27 | Ofinno, LLC | Methods, apparatuses and system for uplink resource configuration |
US11950227B2 (en) | 2020-08-03 | 2024-04-02 | Honor Device Co., Ltd. | Periodic radio resource |
JP7476438B2 (ja) | 2020-08-03 | 2024-05-01 | オナー デバイス カンパニー リミテッド | アップリンクリソース構成 |
CN116171631B (zh) * | 2020-08-03 | 2024-05-07 | 荣耀终端有限公司 | 用于上行链路资源配置的方法、装置和*** |
Also Published As
Publication number | Publication date |
---|---|
US20220039098A1 (en) | 2022-02-03 |
CN111294928A (zh) | 2020-06-16 |
EP3893569A1 (en) | 2021-10-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020114289A1 (zh) | 由用户设备执行的方法以及用户设备 | |
US11596019B2 (en) | Wireless communication device and method | |
US11558870B2 (en) | Method and device for processing carrier activation | |
US11653328B2 (en) | User equipment and method executed thereby, base station and method executed thereby, and mobile control entity and method executed 1HEREBY | |
EP3780759B1 (en) | Method executed by user equipment and user equipment | |
JP6095035B2 (ja) | ページング最適化のための方法 | |
US11405850B2 (en) | Access control method and user equipment | |
WO2022127731A1 (zh) | 小区变更方法以及用户设备 | |
WO2019192387A1 (zh) | 接入控制方法及用户设备 | |
WO2022121982A1 (zh) | 执行侧行通信中继重选的方法及用户设备 | |
WO2022053003A1 (zh) | 一种rrc连接释放的方法及装置 | |
WO2019233472A1 (zh) | 由用户设备执行的方法以及用户设备 | |
US20230038417A1 (en) | Data transmission method and apparatus | |
US20220167452A1 (en) | User equipment and pre-configured uplink resource transmission method performed thereby | |
WO2022078287A1 (zh) | 由用户设备执行的方法以及用户设备 | |
US11224092B2 (en) | Method and apparatus for resetting medium access control layer | |
WO2022194242A1 (zh) | 由用户设备执行的方法以及用户设备 | |
WO2020083182A1 (zh) | 由用户设备执行的方法及用户设备 | |
RU2769540C2 (ru) | Способ конфигурации ширины полосы и электронное устройство для его осуществления | |
WO2022022444A1 (zh) | 由用户设备执行的方法以及用户设备 | |
US20240224172A1 (en) | Method performed by sidelink remote user equipment, and user equipment | |
WO2022078239A1 (zh) | 带宽配置方法和用户设备 | |
WO2021244387A1 (zh) | 由用户设备执行的方法及用户设备 | |
WO2022152111A1 (zh) | 方法及用户设备 | |
WO2020015736A1 (zh) | 用户设备的控制方法以及用户设备 |
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: 19892149 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019892149 Country of ref document: EP Effective date: 20210706 |