WO2020088512A1 - 用户设备和用户设备执行的方法 - Google Patents

用户设备和用户设备执行的方法 Download PDF

Info

Publication number
WO2020088512A1
WO2020088512A1 PCT/CN2019/114314 CN2019114314W WO2020088512A1 WO 2020088512 A1 WO2020088512 A1 WO 2020088512A1 CN 2019114314 W CN2019114314 W CN 2019114314W WO 2020088512 A1 WO2020088512 A1 WO 2020088512A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink resource
configured uplink
user equipment
resource configuration
rrc
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/114314
Other languages
English (en)
French (fr)
Inventor
常宁娟
刘仁茂
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Sharp Corp
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 Sharp Corp filed Critical Sharp Corp
Priority to MX2021004823A priority Critical patent/MX2021004823A/es
Priority to US17/288,882 priority patent/US12143984B2/en
Priority to EP19877770.8A priority patent/EP3876629A4/en
Priority to AU2019373784A priority patent/AU2019373784B2/en
Publication of WO2020088512A1 publication Critical patent/WO2020088512A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower where the power saving management affects multiple terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • 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/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • 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/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • 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/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to the technical field of wireless communication, and more specifically, the present disclosure relates to a user equipment and a method executed by the user equipment.
  • NB-IoT NarrowBand Internet of Things
  • RP-181451 New WID on R16 enhancement for NB-IoT
  • MTC Machine Type Communication
  • One of the goals of this research project is to improve the efficiency of uplink transmission to reduce the energy consumption of user equipment (User Equipment, UE).
  • a UE in an idle state there are two ways for a UE in an idle state to send uplink data:
  • One way is to enter the RRC connected state through a radio connection control (Radio Resource Control, RRC) connection establishment / recovery process, that is The network side establishes a connection to send upstream data in the RRC connection state; another way is to use the early data transmission mechanism (Early Data Transmission (EDT) introduced in version 15).
  • EDT Early Data Transmission
  • the third message in the random access process will be small.
  • the data packets are sent to the base station together.
  • using the EDT method obviously saves signaling overhead and consumes less UE energy than entering the RRC connected state and sending uplink data.
  • the above version 16 wants to further improve the efficiency of uplink transmission and reduce UE energy consumption.
  • pre-configured uplink resource transmission the manner in which the UE in the RRC idle state sends uplink data on the pre-configured resources is called pre-configured uplink resource transmission.
  • This 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 problem of the configuration and management of pre-configured uplink resources.
  • the paging mechanism can reduce the power consumption of the UE.
  • the PDCCH and / or PDSCH need to be repeatedly transmitted in order to correctly receive information from the base station or correctly transmit information to the base station.
  • the UE wants to detect the paging message it needs to wake up from the sleep state to detect whether there is its own paging message on each PO. In most cases, the UE will not have a paging message.
  • the UE when the UE is in the coverage enhancement state, it needs to repeatedly receive the PDCCH or PDSCH multiple times to detect whether there is its own paging message, but most of the time there is no own paging message. Therefore, the power of the UE will be largely lost. For MTC or NB-IoT users, reducing the power consumption of the UE is extremely important. Therefore, in the 3GPP Rel-15 standard specification, for the UE in the idle state, physical wake-up signaling is introduced. That is to design a physical wake-up signaling before detecting the paging message on each PO.
  • the UE detects the physical wake-up signaling, it detects the paging message on the subsequent PO; if the UE does not detect the physical wake-up signaling, it does not detect the subsequent paging message on the PO, and directly returns to the sleep state.
  • UE-group WUS UE-group-based physical wake-up signaling
  • the UE may only perform WUS monitoring in the WUS corresponding to the group associated with itself. How to configure and use WUS based on UE grouping is called a problem that needs to be solved, and a solution method is proposed in this disclosure.
  • the present invention provides a method and user equipment executed by a user equipment, which is a method and user equipment executed by a user equipment that can solve the problem of configuration and management of pre-configured uplink resources.
  • a method performed by a user equipment comprising: receiving an RRC message including a pre-configured uplink resource configuration, the RRC message including an RRC connection related message configured by a base station, The user equipment determines whether the pre-configured uplink resource configuration is for an anchor carrier or a non-anchor carrier according to carrier information in the pre-configured uplink resource configuration.
  • the carrier information in the pre-configured uplink resource configuration includes: according to the presence or absence of the carrier information; or according to the value of the carrier information; or According to the carrier index included in the carrier information.
  • the method according to the first aspect of the embodiment of the present disclosure further includes: saving the received pre-configured uplink resource configuration; and when the user equipment enters the RRC idle state, according to the saved Pre-configured uplink resource configuration, pre-configured uplink resource configuration for relevant protocol layers.
  • the method according to the first aspect of the embodiments of the present disclosure further includes: when the user equipment enters the RRC connected state, deleting or retaining the related configuration of the pre-configured uplink resource configuration.
  • the deleting the related configuration of the pre-configured uplink resource configuration includes at least one of the following operations: deleting the saved pre-configured uplink resource configuration; deleting the The configured pre-configured uplink resource; and a timer for determining the validity of the pre-configured uplink resource, and the related configuration that retains the pre-configured uplink resource configuration includes at least one of the following operations: the application receives The pre-configured uplink resource configuration included in the RRC message; and restarting the timer being executed.
  • the pre-configured uplink resource configuration included in the RRC message received by the application includes using the pre-configured uplink resource configuration included in the received RRC message Configure an uplink resource configuration to replace the saved pre-configured uplink resource configuration.
  • the method according to the first aspect of the embodiments of the present disclosure further includes: the user equipment sending uplink data on the configured pre-configured uplink resources; and the bottom layer of the user equipment does not receive the data from the base station
  • the upper layer of the user equipment is sent instruction information for notifying the bottom layer that the response of the uplink transmission of the pre-configured resource has not been received.
  • the bottom layer includes a MAC layer and / or a physical layer
  • the upper layer includes an RRC layer
  • the method according to the first aspect of the embodiments of the present disclosure further includes: the upper layer performing a fallback operation, that is, using EDT to send uplink data by triggering a random access procedure, or using a traditional RRC connection establishment that is not EDT /
  • the recovery process is to enter the RRC connected state to send upstream data
  • the fallback operation includes at least one of the following operations: starting or restarting the T300 timer; reestablishing the radio link control RLC layer corresponding to the data radio bearer DRB and / or signaling radio bearer SRB; re-data radio bearer DRB and / or The PDCP layer of the packet data aggregation protocol corresponding to the signalling radio bearer SRB; delete the security key derived for performing uplink data transmission on the pre-configured uplink resource; suspend all SRB and DRB except SRB0; and configure the lower layer to suspend Integrity protection and encryption functions.
  • a user equipment including: a processor; and a memory that stores instructions; the instructions are executed when executed by the processor according to any one of the first aspect The method performed by the user equipment.
  • FIG. 1 is a flowchart schematically illustrating the method performed by the user equipment according to Embodiment 1 of the present disclosure.
  • FIG. 2 is a flowchart schematically illustrating the method performed by the user equipment according to Embodiment 2 of the present disclosure.
  • FIG. 3 is a flowchart schematically illustrating the method performed by the user equipment according to Embodiment 3 of the present disclosure.
  • FIG. 4 is a flowchart schematically illustrating a method performed by the user equipment according to Embodiment 4 of the present disclosure.
  • FIG. 5 is a flowchart schematically illustrating the method performed by the user equipment according to Embodiment 5 of the present disclosure.
  • FIG. 6 is a block diagram schematically showing user equipment related to the present disclosure.
  • LTE Long Term Evolution
  • NR New Radio
  • the base station in the present disclosure is an entity for communicating with user equipment, and may be any type of base station, and may refer to Node B or Evolved Node B (Evolved Node B, eNB) or Access Point (Access Point, AP). It is a 5G communication system base station gNB, or a micro base station, a pico base station, a macro base station, a home base station, etc .; the cell may also be a cell under any type of base station mentioned above.
  • the user equipment may also refer to a terminal or an access terminal or a station or a mobile station.
  • the user equipment may be a cellular phone or a PDA (Personal Digital Assistant), a cordless phone or a laptop computer or a mobile phone or a smart phone or a handheld device or a netbook.
  • PDA Personal Digital Assistant
  • Anchor carrier anchor carrier, frequency division duplex system (Frequency Division Duplex, FDD) refers to the UE considers to transmit NB-IoT related physical broadcast channel (NPBCH), primary synchronization signal (NPSS) / auxiliary synchronization signal (NSSS) , System information block (SIB-NB) and other carriers.
  • Time Division Duplex (TDD) refers to the carrier that UE considers to transmit NB-IoT related physical broadcast channel (NPBCH), primary synchronization signal (NPSS) / secondary synchronization signal (NSSS), etc. That is, the UE receives the synchronization signal, broadcast channel and / or system information on the anchor carrier.
  • the uplink carrier corresponding to the anchor carrier is also referred to as an anchor carrier or an uplink anchor carrier.
  • the uplink carrier corresponding to the anchor carrier is in an FDD system, generally through the system information block 2 Frequency information (such as ul-carrierfreq information element) to indicate to the user.
  • Non-anchor carrier non-anchor carrier.
  • FDD FDD
  • TDD TDD
  • the UE TDD
  • the non-anchor carrier is only used to receive or send data unicast related to the NB-IoT-related physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), and physical uplink shared channel (PUSCH).
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • CarrierConfigDedicated-NB information element This information element is used to configure a carrier in the NB-IoT system.
  • the carrier may be an anchor carrier or a non-anchor carrier.
  • the configuration includes an uplink carrier configuration and a downlink carrier configuration.
  • the downlink carrier configuration includes one or more of frequency information of the carrier, downlink available subframe information, non-anchor carrier downlink gap (gap) information, in-band carrier information, and the like.
  • the uplink carrier configuration includes uplink carrier frequency information and / or TDD uplink and downlink alignment offset information.
  • This information element is generally contained in the physicalconfigdedicated information element in the radioresourceconfigdedicated information element and is sent to the UE through UE-specific RRC information such as an RRC connection reconfiguration message.
  • the radioresourceconfigdedicated information element is used to establish / modify / release the radio bearer and modify the radio media control (Medium Access Control, MAC) configuration and modification of the dedicated physical layer configuration, etc.
  • the physicalconfigdedicated information element is used to specify the UE-specific physical channel configuration.
  • dl-configList information element included in system information, used to configure non-anchor carriers used for paging and random access procedures. Contains a list of non-anchor carrier configurations.
  • ul-configList information element included in the system information, used to configure the non-anchor carrier used for the random access process, and contains a non-anchor carrier list.
  • the small data transmission optimization scheme in R15 has been further optimized from the control plane and the user plane for the characteristics of small data transmission.
  • the optimization content is mainly to transmit small data along with message 3 during the random access process, because this optimization method can complete data transmission at an earlier time than traditional data transmission methods. Therefore, it is called early data transmission.
  • small data small data or small packet
  • early data early data
  • Enhanced coverage level In the enhanced coverage technology, the degree of enhanced coverage is divided into multiple enhanced coverage levels. For example, in NB-IoT, three enhanced coverage levels are defined. In MTC, four enhanced coverage levels are defined. In some enhanced coverage methods, each enhanced coverage level may correspond to a different set of wireless parameter configurations, such as random access configuration (such as PRACH (Phvsical Random Access Chanan) resources).
  • random access configuration such as PRACH (Phvsical Random Access Chanan) resources.
  • PRACH Physical Random Access Chanan
  • Physical downlink control channel can refer to PDCCH in 3GPP LTE / LTE-A (Long Term Evolution / Long Term Evolution-Advanced) or MPDCCH (MTC PDCCH) used for machine type communication or used for NPDCCH or NR (New Radio, also known as 5G) NR-PDCCH of Narrowband Internet of Things communication, etc.
  • the physical downlink shared channel may refer to a physical downlink shared channel (Physical Downlink Shared CHANnnel, PDSCH) in 3GPP LTE / LTE-A (Long Term Evolution / Long Term Evolution-Advanced) or NPDSCH or NR for narrowband Internet of Things communication -PDSCH etc.
  • Physical signaling / channel can refer to physical wake-up signaling (Wake Up Signal, WUS) / channel, or physical-to-sleep signaling (Go-To-Sleep Signal, GTS) / channel, etc.
  • the physical wake-up signaling / channel refers to a UE in an idle mode or a UE in a discontinuous reception (Discontinuous Reception, DRX) state in RRC connection mode, receiving or detecting or decoding a physical downlink control channel and / or a physical downlink shared channel Before, the physical wakeup signaling / channel needs to be detected or decoded.
  • DRX discontinuous Reception
  • the physical wake-up signaling / channel refers to a UE in an idle mode or a UE in a discontinuous reception (Discontinuous Reception, DRX) state in an RRC connected mode, receiving or detecting or decoding a physical downlink control channel and / or Before the physical downlink shared channel, the physical wakeup signaling / channel needs to be detected or decoded. If the physical wake-up signaling / channel is detected or decoded, the subsequent physical downlink control channel and / or physical downlink shared channel are detected or decoded.
  • DRX discontinuous Reception
  • the physical de-sleep signaling / channel refers to a UE in an idle mode or a UE in a discontinuous reception (Discontinuous Reception, DRX) state in an RRC connection mode, receiving or detecting or decoding a physical downlink control channel and / or physical downlink sharing Before the channel, the physical de-sleep signaling / channel needs to be detected or decoded.
  • DRX discontinuous Reception
  • the UE does not detect or decode the subsequent physical downlink control channel and / or physical downlink shared channel, but directly goes to sleep.
  • the physical de-sleep signaling / channel refers to a UE in an idle mode or a UE in a discontinuous reception (Discontinuous Reception, DRX) state in RRC connected mode, receiving or detecting or decoding a physical downlink control channel and / or Before the physical downlink shared channel, the physical de-sleep signaling / channel needs to be detected or decoded.
  • DRX discontinuous Reception
  • the subsequent physical downlink control channel and / or physical downlink shared channel are not detected or decoded. If the physical wake-up signaling is not detected or decoded, the subsequent physical downlink control channel and / or physical downlink shared channel are received or detected or decoded.
  • a paging occasion (Paging Occasion, PO) is a subframe on which there may be a paging-radio network temporary identifier (P-RNTI) to scramble and schedule paging messages PDCCH or MPDCCH or NPDCCH.
  • P-RNTI paging-radio network temporary identifier
  • PO refers to the starting subframe in which the MPDCCH is repeatedly transmitted.
  • NPDCCH scrambled using P-RNTI PO refers to the starting subframe in which NPDCCH is repeatedly transmitted, unless the subframe determined by PO is not a valid NB-IoT downlink subframe.
  • the subframe determined by PO is not a valid NB-IoT downlink subframe, the first valid NB-IoT downlink subframe after PO is the starting subframe for repeated transmission of NPDCCH.
  • a paging radio frame (Paging Frame, PF) is a radio frame, which may contain one or more POs.
  • PF paging radio frame
  • the UE When DRX is adopted, the UE only needs to monitor one PO in each DRX cycle period.
  • Paging Narrowband is a narrowband, and the UE receives paging messages on the narrowband.
  • PF, PO and PNB are determined using the DRX parameters provided by the system information and using the following formula.
  • i_s Use index i_s to look up Table 1, Table 2, Table 3, or Table 4 according to the duplex mode and system bandwidth to obtain PO. Among them, i_s is obtained by the following formula:
  • i_s floor (UE_ID / N) mod Ns, Ns, (2)
  • the paging narrowband PNB is determined by the following formula:
  • PNB floor (UE_ID / (N * Ns)) mod Nn (3)
  • the calling carrier is determined by the smallest paging carrier n that satisfies the following formula (4):
  • IMSI International Mobile Subscriber Identity
  • USIM Universal Subscriber Identity Module
  • T DRX cycle of the UE.
  • T 512. Otherwise, T is determined by the shortest DRX cycle of the UE-specific DRX cycle (if higher layers have been configured) and the default DRX cycle of system information broadcast. If the higher layer does not configure the UE-specific DRX cycle, the default DRX cycle is used. The UE-specific DRX cycle does not apply to NB-IoT.
  • ⁇ Nn the number of paging narrowbands provided in the system information
  • IMSI mod 1024 if using P-RNTI scrambling on PDCCH
  • IMSI mod 16384 if using P-RNTI scrambling on MPDCCH, or using P-RNTI scrambling on NPDCCH and the UE supports receiving paging messages on non-anchor carriers, and if the non-anchor carrier is provided in the system information Configuration information of paging messages.
  • MaxPagingCarriers the number of configured paging carriers provided in the system information
  • the paging mechanism can reduce the power consumption of the UE.
  • the PDCCH and / or PDSCH need to be sent repeatedly in order to correctly receive information from the base station or send information to the base station correctly.
  • the UE wants to detect the paging message it needs to wake up from the sleep state to detect whether there is its own paging message on each PO. In most cases, the UE will not have a paging message.
  • the UE when the UE is in the coverage enhancement state, it needs to repeatedly receive the PDCCH or PDSCH multiple times to detect whether there is its own paging message, but most of the time there is no own paging message. Therefore, the power of the UE will be largely lost. For MTC or NB-IoT users, reducing the power consumption of the UE is extremely important. Therefore, in the 3GPP Rel-15 standard specification, for the UE in the idle state, physical wake-up signaling is introduced. That is to design a physical wake-up signaling before detecting the paging message on each PO.
  • the UE detects the physical wake-up signaling, it detects the paging message on the subsequent PO, that is, detects the PDCCH (or MPDCCH or NPDCCH) scrambled using P-RNTI and receives the PDSCH scheduled by the PDCCH (or MPDCCH or NPDCCH) (Or NPDCCH). If the UE does not detect the physical wake-up signaling, it does not detect the subsequent paging message on the PO and directly returns to the sleep state.
  • the PDCCH or MPDCCH or NPDCCH
  • UE-group WUS physical wake-up signaling based on UE grouping or physical de-sleep signaling
  • UEs corresponding to a certain PO may be divided into several groups, and one or more groups of UEs use one WUS.
  • the newly introduced UE-group WUS or Rel-16 UE-group WUS should not affect the existence and performance of the existing Rel-15 WUS. In other words, when the system supports Rel-16UE-group WUS, it can also support Rel-15 WUS.
  • Rel-16 UEs need to be divided into UEs that support UE-group WUS and UEs that do not support UE-group WUS. Therefore, there are three types of UEs that support WUS functions in Rel-16 systems: Rel-15WUS UE or legacy WUS UE (Legacy WUS UE: LWUS UE), UE-group WUS UE (NGWUS UE) and UE-support UE-group. group WUS UE (GWUS UE).
  • the following embodiments of the present disclosure provide a solution to how to configure the GWUS of the UE group. Through the method, the GWUS transmission based on the UE group can be implemented, so that the UE knows the configuration of the GWUS, and can monitor its associated based on the UE group GWUS, to achieve the purpose of energy saving.
  • pre-configured uplink resources there may be two ways.
  • Configure uplink resources that is, the allocated uplink resources are shared by multiple UEs, and can be a shared resource pool. In this way, multiple UEs may use one resource to send uplinks, so that there is potential competition to cause conflicts and cause transmission failures. .
  • 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 present disclosure uses the RRC idle state UE as a typical scenario to illustrate the following solutions, unless otherwise specified, the following embodiments of the present disclosure are also applicable to RRC connected state UEs, such as the carrier configuration implementation in Embodiment 1.
  • the method can also be applied to the pre-configured uplink resource configuration used when the RRC connected state UE performs uplink data transmission.
  • the version 13 system only supports UEs to camp on the anchor carrier, that is, to initiate a random access process for establishing a connection with the network side on the anchor carrier or accept from the anchor carrier for downlink Service paging message, but it can support the UE to configure a non-anchor carrier for the UE (ie, the carrier configured through the CarrierConfigDedicated-NB information element) through RRC dedicated messages such as RRC connection reconfiguration message after entering the connected state.
  • the uplink and downlink services of the UE are transferred to the configured non-anchor carrier, thereby achieving load balancing between the anchor carrier and the non-anchor carrier.
  • the random access process on the non-anchor carrier and the function of receiving paging are added.
  • This function is to carry an uplink non-anchor carrier configuration list (that is, the aforementioned ul-configList information) in the system information. Element) and the downlink non-anchor carrier configuration list (that is, the aforementioned dl-configList information element).
  • the UE can select a non-anchor carrier in the uplink non-anchor carrier list for random access according to certain rules (see section 5.1 of 3GPP protocol document 36.321), or it can follow certain rules (see section 7 of GPP protocol document 36.304) ) Select a non-anchor carrier to monitor / receive paging in the downlink non-anchor carrier list.
  • this disclosure proposes how to configure pre-configured uplink resources for UEs on anchor carriers and non-anchor carriers Solution.
  • the dedicated pre-configured resource may be the UE configured by the base station through RRC dedicated signaling when the UE was in the RRC connected state, such as an RRC connection release message, an RRC connection reconfiguration message , RRC connection establishment message, RRC connection recovery message and other messages related to RRC connection.
  • the UE in the RRC idle state may use the dedicated pre-configured uplink resource to send uplink data.
  • the traditional transmission mode such as receiving the paging message and entering the RRC connection state for downlink service transmission
  • the fallback to the traditional transmission mode may also be triggered by a transmission failure on the pre-configured uplink resource. In this case, how to implement the fallback to the traditional transmission mode is also a concern of the present disclosure.
  • indication (indicate / indication) and notification (notify / notification) or notification / information (information / information) can be interchanged.
  • UE can refer to NB-IoT UE, Bandwidth Reduced Complexity (BL) UE, or enhanced coverage (UE) UE, or other UEs such as 5G NR UE.
  • PRACH, NPRACH, and RACH may be replaced.
  • the pre-configured uplink resource may also be called a pre-configured uplink grant (uplink) or a pre-allocated uplink resource (preallocated uplink) resource or a pre-allocated uplink grant (preallocated uplink grant).
  • Coverage enhancement level (Coverage Enhancement level) is equivalent to enhanced coverage level (Enhanced Coverage level), or can also be called repetition level (Repetition Level).
  • FIG. 1 is a flowchart schematically illustrating the method performed by the user equipment according to Embodiment 1 of the present disclosure.
  • This embodiment proposes a method for configuring pre-configured uplink resources. Implemented on user equipment UE.
  • step S101 the UE receives an RRC message including a pre-configured uplink resource configuration.
  • the RRC message may be an RRC connection release message; alternatively, it may be an RRC connection reconfiguration message, an RRC connection reestablishment message, an RRC connection establishment message, an RRC connection recovery message, and other RRC connection related messages.
  • RRC connection release message may be an RRC connection release message; alternatively, it may be an RRC connection reconfiguration message, an RRC connection reestablishment message, an RRC connection establishment message, an RRC connection recovery message, and other RRC connection related messages.
  • the UE uses an anchor carrier (that is, the UE considers that the pre-configured uplink resource is for an anchor carrier); if the pre-configured uplink resource If the carrier information in the configuration is set to "non-anchor" or "dedicated” carrier, the UE uses the carrier configured through the CarrierConfigDedicated information element in the dedicated RRC message, that is, the UE considers that the configured pre-configured uplink resource is for CarrierConfigDedicated information The dedicated carrier configured by the element.
  • the UE uses an anchor carrier (that is, the UE considers that the pre-configured uplink resource is for an anchor carrier) ; If the carrier information in the pre-configured uplink resource configuration is set to "1" or "FALSE”, the UE uses the carrier configured through the CarrierConfigDedicated information element in the dedicated RRC message, that is, the UE considers the configured pre-configured uplink resource It is for the dedicated carrier configured by the CarrierConfigDedicated information element. At this time, the carrier information may indicate whether an anchor carrier is used for pre-configuration of uplink resources.
  • the UE uses the anchor carrier (that is, the UE considers that the pre-configured uplink resource is for the anchor carrier); if all If the carrier information in the pre-configured uplink resource configuration is set to "0" or "TURE”, the UE uses the carrier configured through the CarrierConfigDedicated information element in the dedicated RRC message, that is, the UE considers that the configured pre-configured uplink resource is for CarrierConfigDedicated Dedicated carrier configured by the information element.
  • the carrier information may indicate whether a dedicated (non-anchor) carrier is used for pre-configuring uplink resources.
  • the carrier information in the pre-configured uplink resource configuration includes a carrier index used to indicate which carrier in the system information is used for pre-configured uplink resources.
  • the carrier index value is "0" corresponding to the uplink corresponding to the anchor carrier, that is, the anchor carrier is used for pre-configuration of the uplink resource, and the carrier index value is "1" corresponding to the The first entry in the ul-configList information element; the carrier index value of "2" corresponds to the second entry in the ul-configList information element, and so on.
  • the carrier index value is "0" corresponding to an anchor carrier, that is, an anchor carrier is used for pre-configuring uplink resources, and the carrier index value is "1" corresponding to the dl -the first entry in the configList information element; the carrier index value is "2" corresponding to the second entry in the dl-configList information element, and so on.
  • the downlink carrier in the pre-configured uplink resource may be used for downlink scheduling of data retransmission and / or downlink reception in response to uplink data, and so on.
  • Step S102 The UE saves the received pre-configured uplink resource configuration.
  • Step S103 When the UE enters the RRC idle state (or leaves the RRC connected state or the RRC inactive state), the saved pre-configured uplink resource configuration is applied.
  • a pre-configured uplink resource validity timer is started.
  • the pre-configured uplink resource configuration saved by the application refers to configuring the relevant protocol layer according to the saved pre-configured uplink resource configuration.
  • the pre-configured uplink resource validity timer is used to determine whether the pre-configured uplink resource is valid. For example, when the timer runs, the saved or configured pre-configured uplink resources are considered valid; when the timer does not run or times out, the saved or configured pre-configured uplink resources are considered invalid.
  • the timer is a time alignment timer (TimeAlignmentTimer, TAT).
  • TAT is used in the prior art to control how long a MAC entity considers a serving cell to be in an uplink alignment (ie, uplink synchronization) state. That is, when the TAT is running, the UE MAC entity considers that the corresponding serving cell is uplink aligned, and the pre-configured uplink resources are valid at this time; when the TAT is not running or times out, the UE MAC entity considers the corresponding The serving cell is not aligned on the uplink, and the pre-configured uplink resource is invalid at this time.
  • TAT time alignment timer
  • FIG. 2 is a flowchart schematically illustrating the method performed by the user equipment according to Embodiment 2 of the present disclosure.
  • This embodiment provides a method for managing pre-configured uplink resources.
  • the UE if the UE enters the RRC connected state, the UE considers that the saved pre-configured uplink resources for the RRC idle state are useless, and the UE can delete the pre-configured uplink resource related configuration by itself to avoid When the UE is in the connected state, resource management energy consumption caused by the pre-configured uplink resource related configuration is performed.
  • step S201 the UE enters the RRC connected state.
  • the entering the RRC connected state may be an RRC message received by the UE to instruct the UE to enter the connected state, preferably, an RRC connection recovery message or an RRC connection establishment message.
  • Step S202 the UE performs one or more of the following operations:
  • Operation 1 Release (saved) pre-configured uplink resource configuration.
  • Operation 2 Release (configured) pre-configured uplink resources.
  • Operation 3 Stop the timer for determining the validity of the pre-configured uplink resource.
  • the "release” may also be “delete”.
  • FIG. 3 is a flowchart schematically illustrating the method performed by the user equipment according to Embodiment 3 of the present disclosure.
  • This embodiment provides another method for managing pre-configured uplink resources.
  • the UE if the UE enters the RRC connected state, the UE considers that the pre-configured uplink resources saved for the RRC idle state can be used after the UE enters the idle state again, so the UE retains the pre-configured uplink resource related Configuration, so that if the network side configures a pre-configured uplink resource for the UE when it enters the idle state again, the signaling overhead caused by re-configuring the pre-configured uplink resource can be reduced or avoided.
  • step S301 the UE enters the RRC connected state.
  • the entering the RRC connected state may be an RRC message received by the UE to instruct the UE to enter the connected state, preferably, an RRC connection recovery message or an RRC connection establishment message.
  • Step S302 The UE performs one or more of the following operations:
  • Operation 1 If the RRC message includes a pre-configured uplink resource configuration, the UE applies the pre-configured uplink resource configuration received. If the UE has previously saved the pre-configured uplink resource configuration, the pre-configured uplink resource configuration received by the application further includes that the UE updates the saved pre-configured uplink resource configuration, that is, using the pre-configuration contained in the received RRC message Configure the uplink resource configuration to replace the saved pre-configured resource pre-configured uplink resource configuration.
  • Operation 2 If there is a running timer for determining the validity of the pre-configured uplink resource, restart the timer for determining the validity of the pre-configured uplink resource.
  • FIG. 4 is a flowchart schematically illustrating a method performed by the user equipment according to Embodiment 4 of the present disclosure.
  • a UE configured with pre-configured uplink resources will use the corresponding pre-configured uplink resources to send uplink.
  • the UE will choose to fall back to the traditional uplink transmission method, that is, use the EDT to send uplink data or use the EDT to trigger the random access process.
  • the non-EDT traditional RRC connection establishment / recovery process enters the RRC connection state to send uplink data.
  • This embodiment provides a method in which a UE configured with pre-configured uplink resources fails to transmit on the pre-configured uplink resources and thus falls back to the traditional uplink transmission method. Performed on UE in RRC idle state.
  • step S401 The bottom layer of the UE performs pre-configured uplink resource transmission, that is, the UE uses the pre-configured uplink resources to send uplink data.
  • the bottom layer refers to the MAC layer and / or the physical layer.
  • step S401 it may further include that the RRC determines to use the pre-configured uplink resources to send the uplink data, and indicates to the bottom layer to use the pre-configured uplink resources to send the uplink data.
  • Step S402 If the bottom layer does not receive any response information from the base station, for example, it is used to confirm that the uplink transmission in step S401 is an indication of successful reception or reception failure, the bottom layer sends an indication message to the upper layer (RRC layer) for Informing the upper layer that the bottom layer has not received the response of the uplink transmission of the pre-configured resource, or informing the upper layer that the bottom layer of the pre-configured resource fails to transmit the uplink, the indication information can also be understood as an instruction to request the upper layer to perform a fallback to the traditional uplink transmission.
  • RRC layer the upper layer
  • the determination that the bottom layer does not receive any response from the base station may be determined based on a certain time, for example, no response is received within a period of time after sending the uplink data. Or the UE has not received any response after performing a certain number of retransmissions on the uplink data. Alternatively, the response may be a response indicating successful reception.
  • this step further includes that the MAC layer clears the MAC layer related cache, which may be a message 3 cache or a hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) cache.
  • the MAC layer clears the MAC layer related cache, which may be a message 3 cache or a hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) cache.
  • HARQ Hybrid Automatic Repeat reQuest
  • Step S403 After receiving the instruction in step S402 from the bottom layer, the RRC layer performs the operation of the traditional uplink transmission mode of the fallback.
  • the operation may include one or more of the following:
  • Operation 1 Start or restart the T300 timer.
  • Operation 2 Reconstruct the Radio Link Control (RLC) layer corresponding to the Data Radio Bearer (Data Radio) Bearer (DRB) and / or Signaling Radio Bearer (Signalling Radio Bearer, SRB).
  • RLC Radio Link Control
  • Operation 3 Reconstruct the packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer corresponding to the data radio bearer (Data Radio) Bearer (DRB) and / or signaling radio bearer (Signalling Radio Bearer, SRB).
  • Packet Data Convergence Protocol Packet Data Convergence Protocol
  • DRB Data Radio Bearer
  • SRB Signaling Radio Bearer
  • Operation 4 Delete the security key derived for performing uplink data transmission on the pre-configured uplink resources.
  • Operation 5 Suspend all SRB and DRB, SRB0 is not included here.
  • Operation 6 Configure lower layer suspend integrity protection and encryption functions.
  • FIG. 5 is a flowchart schematically illustrating the method performed by the user equipment according to Embodiment 5 of the present disclosure.
  • the RRC layer determines whether to use the pre-configured uplink resource transmission method or the traditional uplink data transmission method .
  • the judgment of whether the pre-configured uplink resource is valid is judged by the RRC layer in some cases, for example, based on whether the serving cell changes, and in some other cases by the MAC layer, as described above The judgment is based on whether the TAT times out.
  • the interaction information between the MAC layer and the RRC layer is needed to complete the determination of whether to use the pre-configured uplink resource transmission mode as a whole.
  • a solution method for inter-layer interaction information is provided.
  • step S501 the UE MAC entity judges that the pre-configured uplink resource is invalid.
  • the judgment may be based on the pre-configured uplink resource validity timer or TAT, or may be based on a transmission failure on the pre-configured resource, or may be based on a downlink channel quality such as RSRP exceeding a configured threshold.
  • Step S502 When the UE MAC entity determines that the pre-configured uplink resource is invalid, the UE MAC layer sends a pre-configured uplink resource invalid indication to the UE RRC layer, that is, the RRC layer indicates that the pre-configured uplink resource is invalid.
  • the indication may also indicate a specific invalid reason, such as a timeout of a pre-configured uplink resource validity timer or a TAT timeout.
  • Step S503 The RRC layer receiving the indication from the MAC layer may release the pre-configured uplink resource configuration.
  • Step S503 is optional, that is, the RRC layer may also choose not to release the pre-configured uplink resource configuration after receiving the indication, but directly fall back to the traditional uplink data sending method.
  • RRC when determining whether to use the pre-configured uplink resource transmission mode, RRC needs to determine based on whether the pre-configured uplink resource (configuration) is valid, that is, only when there is a valid pre-configured uplink resource. Use a pre-configured uplink resource transmission method.
  • the present disclosure provides a method performed by a user equipment capable of solving the configuration and management problems of pre-configured uplink resources.
  • FIG. 6 is a block diagram schematically showing user equipment related to the present disclosure.
  • the user equipment UE80 includes a processor 801 and a memory 802.
  • the processor 801 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 802 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 802 stores program instructions. When the instruction is executed by the processor 801, the above method executed by the user equipment described in detail in the present invention may be executed.
  • This embodiment provides a method for configuring a physical wake-up signal based on UE grouping, which may be implemented on a UE or a base station or a system including the UE and the base station.
  • the UE and the base station can complete the reception or transmission of the WUS based on the configured packet-based WUS, so as to achieve the purpose of saving UE energy consumption and using the least WUS resources to achieve the UE energy saving.
  • the method includes: dividing GWUS UEs corresponding to a certain PO into several UE groups, and assigning one WUS to each group or groups of UEs. For example, support UE-groups corresponding to a certain PO-WUS UEs are divided into 4 groups: G1, G2, G3, and G4. If a GWUS is allocated to each group of UEs, four WUSs are needed: GWUS1, GWUS2, GWUS3, and GWUS4, which correspond to G1, G2, G3, and G4, respectively.
  • 4 groups of UEs can be combined, with a total of 15 combinations: G1, G2, G3, G4, G1 + G2, G1 + G3, G1 + G4, G2 + G3, G2 + G4, G3 + G4, G1 + G2 + G3, G1 + G2 + G4, G1 + G3 + G4, G2 + G3 + G4, G1 + G2 + G3 + G4.
  • One GWUS can be allocated for each combination, and 15 GWUS are required. Alternatively, certain combinations may be selected, and a GWUS is assigned to the selected combinations.
  • G1, G2, G3, G4, G1 + G2, G1 + G3, G1 + G4, G2 + G3, G2 + G4, G3 + G4, G1 + G2 + G3 + G411 combinations are the 11 combinations 11 GWUS are allocated: GWUS1, GWUS2, ..., GWUS10, GWUS11.
  • the base station sends GWUS1; when the G1 and G2 UEs have a paging message at the same time, the base station sends GWUS5; when the G1, G2, G3, and G4 UEs have a paging message at the same time, the base station sends GWUS11.
  • G1, G2, G3, and G4 are each assigned a GWUS, and G1 + G2 + G3 + G4 is separately assigned a GWUS (which may also be referred to as a common CWUS). In this way, 5 GWUS are required.
  • the common WUS (Common WUS, CWUS) may be configured through system information or UE-specific RRC signaling, MAC signaling, or physical layer signaling, and the CWUS may be configured as LWUS or newly defined WUS.
  • Rel-16 does not support UE-group WUS UE can be configured as LWUS UE, or Rel-16 does not support UE-group WUS UE configured WUS is LWUS, that is Rel-16 does not support UE-group WUS UE use LWUS works.
  • a newly defined WUS may be configured for UEs that Rel-16 does not support UE-group WUS.
  • one or more groups of UEs in several groups can be configured to use LWUS UEs, or several groups that support UE-group WUS for Rel-16
  • the WUS configured by a certain group or groups of UEs in the group is LWUS, that is, Rel-16 supports one group or groups of UEs in several groups of UE-group WUS to use LWUS for work.
  • the multiplexing between LWUS and GWUS, and between GWUS and GWUS can be Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM) , FDM + TDM, FDM + CDM, TDM + CDM or FDM + TDM + CDM.
  • the multiplexing mode between LWUS and GWUS may be different from the multiplexing mode between GWUS and GWUS.
  • TDM is used between LWUS and GWUS
  • CDM is used between GWUS and GWUS.
  • FDM is used between LWUS and GWUS
  • CDM or FDM + CDM is used between GWUS and GWUS.
  • the multiplexing mode between LWUS and GWUS and the multiplexing mode between GWUS and GWUS use the same multiplexing mode, for example, the same using CDM or one of the above-mentioned possible multiplexing modes.
  • the base station can configure the multiplexing mode between LWUS and GWUS according to its operating environment (for example, the number of served UEs, etc.). Alternatively, the base station configures the multiplexing mode between LWUS and GWUS and / or the multiplexing mode between GWUS and GWUS individually or in the same configuration according to the number of supported UE groups or other possible parameters.
  • FDM is multiplexed based on one or more physical resource blocks (PRB).
  • PRB physical resource blocks
  • FDM is multiplexing based on one or more subcarriers.
  • TDM is based on one or more orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing: OFDM) symbols for multiplexing.
  • OFDM Orthogonal Frequency Division Multiplexing
  • TDM is multiplexed based on one or more subframes.
  • TDM is multiplexed based on one or more radio frames.
  • TDM is multiplexed based on one or more discontinuous reception (DRX) cycles.
  • eDRX enhanced discontinuous reception
  • CDM is multiplexed based on different basic sequences. Alternatively, CDM is multiplexed based on different coverage codes (Cover Codes) of the same basic sequence.
  • the cover code may be a frequency domain cover code or a time domain cover code. For example, in a PRB with 12 subcarriers, 12 orthogonal cover codes can be generated; alternatively, the cover codes are generated based on time domain OFDM symbols.
  • the UE determines which group it belongs to based on its UE identity.
  • the UE and the base station need to know the configuration information of multiple UE groups and the GWUS based on the UE group before they can monitor / send the GWUS associated with the corresponding group based on the UE group.
  • the following gives various combinations of UE groupings and association methods between multiple GWUSs, but it is worth noting that the UE in this disclosure learns about the various combinations of UE groupings and association methods between multiple GWUSs. Two implementation methods are described.
  • the configuration information of the GWUS includes a GWUS list, and each item in the list corresponds to a GWUS, that is, a resource configuration of a GWUS.
  • the resource configuration may be time domain resources, frequency domain resources, code domain resources, and / or space domain resources.
  • the GWUS configuration information also includes information about the number of UE groups and / or a bitmap.
  • the UE group number information is used to indicate the number of UE groups; the bitmap is used to indicate whether each combination is associated with a GWUS in the GWUS list among the multiple combinations based on the UE group.
  • the length of the bitmap is Bits.
  • the maximum possible number of combinations between groups of N UE groups is also (Ie G1, G2 ..., GN, G1 + G2, G1 + G3, ..., G1 + GN, G2 + G3, G2 + G4, ..., G2 + GN, G3 + G4, ... G3 + GN, ..., GM + G (M + 1), ..., GM + GN, G (N-1) + GN, G1 + G2 + G3, G1 + G2 + G4, ..., G1 + G2 + GN, G1 + G3 + G4, G1 + G2 + ... + GN), so that each bit in the bitmap corresponds to A combination of each group of UE grouping or a GWUS corresponding to the combination.
  • the bit For a certain bit, if the value of the bit is set to 1, the GWUS associated with the combination of UE groups corresponding to the bit is included in the GWUS list, and if the value of the bit is set to 0, the bit The GWUS associated with the combination of the corresponding UE group is not included in the GWUS list, that is, the GWUS associated with the combination of the UE group is not configured.
  • each group has a maximum of 15 combinations, namely G1, G2, G3, G4, G1 + G2, G1 + G3, G1 + G4, G2 + G3, G2 + G4, G3 + G4, G1 + G2 + G3, G1 + G2 + G4, G1 + G3 + G4, G2 + G3 + G4, G1 + G2 + G3 + G4.
  • the length of the bitmap is 15, and each bit corresponds to one of the above 15 combinations.
  • bit 1 corresponds to G1
  • bit 2 corresponds to G2
  • bit 3 corresponds to G3
  • bit 4 corresponds to G4
  • bit 5 corresponds to G1 + G2 + G3 + G4.
  • the one-to-one correspondence between the bit sequence of the bitmap and the various combinations of the UE group needs to be specified in advance or configured in signaling (for example, when the number of groups is 1, the GWUS list contains only one GWUS1 configuration ; When the number of groups is 2, the order of the bits in the bitmap corresponding to the group combination is bit 1 to bit 3, and the corresponding group combination is G1, G2, G1 + G2; when the number of groups is 3, The order in which the bits in the bitmap correspond to the group combination is bit 1 to bit 7, and the corresponding group combination in sequence is G1, G2, G3, G1 + G2, G1 + G3, G2 + G3, G1 + G2 + G3; When the number of groups is 4, as described in the previous example, it will not be repeated
  • the network side does not necessarily configure an associated GWUS for each of the 15 combinations.
  • the network side configures the associated GWUS for 11 of the 15 combinations, and the corresponding GWUS configuration is included in the GWUS list in the GWUS configuration, that is, the GWUS list includes 11 items GWUS1 to GWUS11.
  • the bit value in the bitmap is indicated by the bit value in the bitmap.
  • the value of the bitmap is 111111111100001, it means that G1, G2, G3, G4, G1 + G2, G1 + G3, G1 + G4, G2 + G3, G2 + G4, G3 + G4, G1 + G2 + G3 are configured GWUS corresponding to the + G411 combinations, and GWUS is not configured for the four combinations of G1 + G2 + G3, G1 + G2 + G4, G1 + G3 + G4, G2 + G3 + G4.
  • the number of items with the bit set to 1 in the bitmap is the same as the number of GWUS items in the GWUS list, and the order of the items with the bit set to 1 in the bitmap and the order of the GWUS items in the GWUS list Consistent, that is, the first bit of the low bit (or high bit or leftmost or rightmost) in the bitmap corresponds to the first item in the GWUS list, and the low bit (or high bit or (Leftmost or rightmost) The second digit corresponds to the second item in the GWUS list, and so on.
  • GWUS1 ⁇ 11 respectively correspond to G1, G2, G3, G4, G1 + G2, G1 + G3, G1 + G4, G2 + G3, G2 + G4, G3 + G4, G1 + G2 + G3 + G4 11 combinations.
  • each GWUS in addition to the GWUS column included in the GWUS configuration and / or the number of UE group information, each GWUS includes a group (combination) information, and the group (combination) information is used to indicate The association relationship between the UE group or the combination of UE groups corresponding to the GWUS. In this way, the association relationship between multiple GWUS and multiple UE groups or combinations of UE groups is configured.
  • the GWUS configuration list in the GWUS configuration information contains 11 GWUS items, corresponding to 11 GWUS, namely GWUS1 to GWUS11.
  • Each GWUS configuration contains its associated grouping (combination) information, such as the grouping (combination) information contained in the GWUS1 configuration information indicates G1, and the grouping (combination) information included in the GWUS2 configuration information indicates G2, GWUS3
  • the grouping (combination) information included in the configuration information indicates G3, the grouping (combination) information included in the GWUS4 configuration information indicates G4, and the grouping (combination) information included in the GWUS5 configuration information indicates G1 + G2. analogy.
  • the grouping (combination) information is a bitmap
  • the length of the bitmap is the length of the number of packets
  • the bits of the bitmap are from low to high (or from high to low or left) To the right or from right to left)
  • the sequence is the same as the sequence of the group number of the UE grouping combination from small to large (or from small to large). For example, for GWUS5 (that is, the fifth item in the GWUS list), the grouping (combination) information indicates 1100, and for GWUS6 (that is, the sixth item in the GWUS list), the grouping (combination) information indicates 1010.
  • the UE After learning the correspondence or association between the GWUS and the combination of the UE group in the above GWUS list, the UE monitors the GWUS associated or corresponding to the group based on its own group without having to monitor the UE ’s own Group GWUS not related to achieve the purpose of UE power saving.
  • the number of UE groups is 4 groups, and the UE determines its grouping as group 2 (G2) through information and formulas such as UE identification, and 11 combinations G1, G2, G3, G4, and G1 are configured on the network side + G2, G1 + G3, G1 + G4, G2 + G3, G2 + G4, G3 + G4, G1 + G2 + G3 + G4 corresponding to GWUS1 ⁇ 11, the UE monitors its own group 2 corresponding to G2 GWUS, that is, GWUS2 ⁇ GWUS5 ⁇ GWUS8 ⁇ GWUS9 ⁇ GWUS11, without or without monitoring GWUS1 ⁇ GWUS3 ⁇ GWUS4 ⁇ GWUS6 ⁇ GWUS7 ⁇ GWUS10.
  • the GWUS associated with the UE is configured through dedicated signaling, that is, the UE needs to monitor all GWUS configured through dedicated signaling.
  • the GWUS associated with the UE is configured through dedicated signaling.
  • the network side delivers all GWUS used by the cell through system information, that is, it is included in a GWUS list.
  • the GWUS configured by the dedicated signaling of the UE includes a bitmap, and the length of the bitmap is consistent with the number of GWUS (or the number of items in the GWUS list).
  • Each bit in the bitmap corresponds to a GWUS. If the corresponding bit in the bitmap is set to 1, the UE monitors the GWUS corresponding to the bit. If the corresponding bit in the bitmap is set to 0, the UE No or no need to monitor the GWUS corresponding to this bit.
  • the order of the bits in the bitmap is the same as the order of their corresponding GWUS in the GWUS list.
  • the GWUS configuration information includes the GWUS corresponding to each UE group.
  • the order of the GWUS in the GWUS configuration list corresponds to the order of the group number of the UE group from small to large (or from large to small). If the number of UE groups is N groups, the first item in the GWUS list corresponds to the group 1 of the UE group, namely G1, and the second item in the GWUS list corresponds to the group 2 of the UE group, namely G2, and so on.
  • the Nth item in the list corresponds to the group N (GN) of the UE grouping.
  • the above configuration may be implemented through system information or UE-specific RRC signaling or MAC signaling or physical layer signaling.
  • the method of the present disclosure and the involved devices have been described above in conjunction with the preferred embodiments. Those skilled in the art can understand that the methods shown above are only exemplary, and the embodiments described above can be combined with each other without conflict.
  • the method of the invention is not limited to the steps and sequence shown above.
  • the user equipment shown above may include more modules, for example, it may also include modules that can be developed or developed in the future and can be used for a base station, MME, or UE, and so on.
  • the various identifications shown above are only exemplary and not restrictive, and the present disclosure is not limited to specific cells as examples of these identifications. Many changes and modifications can be made by those skilled in the art based on the teachings of the illustrated embodiments.
  • various components inside the base station and the user equipment in the above embodiments can be implemented by a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processing Device, application specific integrated circuit (ASIC), field programmable gate array (FPGA), programmable logic device (CPLD), etc.
  • DSP digital signal processing
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • CPLD programmable logic device
  • base station may refer to a mobile communication data and control switching center with a large transmission power and a wide coverage area, including functions such as resource allocation scheduling, data reception and transmission, and the like.
  • User equipment may refer to user mobile terminals, including, for example, mobile phones, notebooks, and other terminal devices that can communicate wirelessly with base stations or micro base stations.
  • 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 for example, 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供一种用户设备执行的方法及用户设备，包括：接收包含预配置上行资源配置的RRC消息，所述RRC消息包括由基站配置的与RRC连接相关的消息，所述用户设备根据所述预配置上行资源配置中的载波信息，来确定所述预配置上行资源配置是针对锚载波还是针对非锚载波。

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连接建立/恢复过程进入连接态传输上行。
本公开中，RRC空闲态的UE通过预配置的资源上发送上行数据的方式称为预配置上行资源发送。本公开主要就如何实现预配置上行资源发送的问题提出解决方法，更具体而言，就预配置上行资源的配置和管理问题提出解决方法。
此外，在3GPP Rel-14标准规范中，对于处于空闲模式的UE，采用寻呼机制可以减少UE的功率损耗。而当UE信道状态不好，需要采用覆盖增强时，PDCCH和/或PDSCH需要重复发送，才能从基站正确接收到信息或正确发送信息到基站。当UE要检测寻呼消息前，需要从睡眠状态中唤醒以在每一PO上检测是否有自己的寻呼消息。而在大多时候，UE都不会有寻呼消息。这样，当UE处于覆盖增强状态时，需要多次重复地接收PDCCH或PDSCH才能检测到是否有自己的寻呼消息，而大多数时候是没有自己的寻呼消息。因此，会大量损耗UE的功率。而对于MTC或NB-IoT用户而言，降低UE的功率损耗极为重要。所以，在3GPP Rel-15标准规范中，对于处于空闲状态的UE，引入了物理唤醒信令。即以在每一PO上检测寻呼消息前，设计一物理唤醒信令。如果UE检测到该物理唤醒信令，则检测随后PO上的寻呼消息；如果UE没有检测到该物理唤醒信令，则不检测随后PO上的寻呼消息，直接回到睡眠状态。在前述Rel-16的新工作项目中，其目的之一是引入基于UE分组的物理唤醒信令(UE-group WUS)，或物理去睡眠信令，以进一步减少UE的功率损耗。基于UE分组的WUS中，UE可以仅在与自己关联的分组所对应的WUS执行监听WUS即可。而如何配置和使用基于UE分组的WUS称为需要解决的问题，本公开中就该问题提出了解决方法。
发明内容
为了解决上述问题中的至少一部分，本发明提供了一种用户设备执行的方法以及用户设备，是能够解决预配置上行资源的配置和管理问题的用户设备执行的方法以及用户设备。
根据本公开实施例的第一方面，提供一种用户设备执行的方法，包括：接收包含预配置上行资源配置的RRC消息，所述RRC消息包括由基站配置的与RRC连接相关的消息，所述用户设备根据所述预配置上行资源配置中的载波信息，来确定所述预配置上行资源配置是针对锚载波还是针对非 锚载波。
根据本公开实施例的第一方面的所述方法，所述根据所述预配置上行资源配置中的载波信息包括：根据所述载波信息的有无；或根据所述载波信息的取值；或根据所述载波信息包含的载波索引。
根据本公开实施例的第一方面的所述方法，还包括：保存所接收到的所述预配置上行资源配置；和在所述用户设备进入RRC空闲态的情况下，按照所保存的所述预配置上行资源配置，对相关协议层进行预配置上行资源的配置。
根据本公开实施例的第一方面的所述方法，还包括：在所述用户设备进入RRC连接态的情况下，删除或保留所述预先配置上行资源配置的相关配置。
根据本公开实施例的第一方面的所述方法，所述删除所述预先配置上行资源配置的相关配置包括下列操作中的至少一个操作：删除所保存的所述预配置上行资源配置；删除所配置的所述预配置上行资源；和停止用于确定预配置上行资源有效性的定时器，所述保留所述预先配置上行资源配置的相关配置包括下列操作中的至少一个操作：应用接收到的所述RRC消息中包含的所述预配置上行资源配置；和对正在执行的所述定时器进行重启。
根据本公开实施例的第一方面的所述方法，所述应用接收到的所述RRC消息中包含的所述预配置上行资源配置包括：用接收到的所述RRC消息中包含的所述预配置上行资源配置来替换所保存的所述预配置上行资源配置。
根据本公开实施例的第一方面的所述方法，还包括：所述用户设备在所配置的所述预配置上行资源上发送上行数据；和在所述用户设备的底层未接收到来自基站的任何响应信息的情况下，向所述用户设备的上层发送用于告知所述底层未接收到所述预配置资源的上行传输的响应的指示信息。
根据本公开实施例的第一方面的所述方法，所述底层包括MAC层和/或物理层，所述上层包括RRC层。
根据本公开实施例的第一方面的所述方法，还包括：所述上层执行回退操作，即：通过触发随机接入过程使用EDT来发送上行数据、或使用非EDT的传统RRC连接建立/恢复过程以进入RRC连接态来发送上行数据，
该回退操作包括下列操作中的至少一个操作：启动或重启T300定时器；重建数据无线承载DRB和/或信令无线承载SRB对应的无线链路控制RLC层；重新数据无线承载DRB和/或信令无线承载SRB对应的包数据汇聚协议PDCP层；删除为了在所述预配置上行资源上执行上行数据发送所派生的安全密钥；挂起除了SRB0以外的所有SRB和DRB；和配置下层挂起完整性保护和加密功能。
根据本公开实施例的第二方面，提供一种用户设备，包括：处理器；以及存储器，存储有指令；所述指令在由所述处理器运行时执行根据所述第一方面中任一项所述的用户设备执行的方法。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1是示意性示出本公开实施例1的用户设备执行的方法的流程图。
图2是示意性示出本公开实施例2的用户设备执行的方法的流程图。
图3是示意性示出本公开实施例3的用户设备执行的方法的流程图。
图4是示意性示出本公开实施例4的用户设备执行的方法的流程图。
图5是示意性示出本公开实施例5的用户设备执行的方法的流程图。
图6是示意性示出本公开所涉及的用户设备的框图。
具体实施方式
根据结合附图对本公开示例性实施例的以下详细描述，本公开的其它方面、优势和突出特征对于本领域技术人员将变得显而易见。
在本公开中，术语“包括”和“含有”及其派生词意为包括而非限制；术语“或”是包含性的，意为和/或。
在本说明书中，下述用于描述本公开原理的各种实施例只是说明，不应该以任何方式解释为限制公开的范围。参照附图的下述描述用于帮助全面理解由权利要求及其等同物限定的本公开的示例性实施例。下述描述包括多种具体细节来帮助理解，但这些细节应认为仅仅是示例性的。因此，本领域普通技术人员应认识到，在不背离本公开的范围和精神的情况下， 可以对本文中描述的实施例进行多种改变和修改。此外，为了清楚和简洁起见，省略了公知功能和结构的描述。此外，贯穿附图，相同参考数字用于相似功能和操作。
下文以长期演进(Long Term Evolution，LTE)移动通信系统中的NB-IoT及其后续的演进版本作为示例应用环境，具体描述了根据本公开的多个实施方式。然而，需要指出的是，本公开不限于以下实施方式，而是可适用于更多其它的无线通信系统，如机器类型通信(Machine Type Communication，MTC)系统中，也可以用于5G下一代无线通信系统(New Radio，NR)中。
本公开中的基站是用于与用户设备通信的一个实体，可以是任何类型基站，可以指Node B或演进的Node B(Evolved Node B，eNB)或接入点(Access Point，AP)也可以是5G通信系统基站gNB、或者微基站、微微基站、宏基站、家庭基站等；所述小区也可以是上述任何类型基站下的小区。所述的用户设备也可以指终端或接入终端或站点或移动站点等。用户设备可以是蜂窝电话或掌上电脑(Personal Digital Assistant，PDA)或无绳电话或笔记本电脑或移动电话或智能手机或手持设备或上网本等。
不同的实施例之间也可以结合工作。
下面先对本公开涉及到的一些概念和进行说明。值得注意的是，在下文的描述中的一些命名仅是实例说明性的，而不是限制性的，也可以作其他命名。
锚载波：anchor carrier，对频分双工系统(Frequency Division Duplex，FDD)指的是UE认为传输NB-IoT相关的物理广播信道(NPBCH)、主同步信号(NPSS)/辅同步信号(NSSS)、系统信息块(SIB-NB)等的载波。对时分双工系统(Time Division Duplex，TDD)指的是UE认为传输NB-IoT相关的物理广播信道(NPBCH)、主同步信号(NPSS)/辅同步信号(NSSS)等的载波。即UE在锚载波上接收同步信号、广播信道和/或系统信息。在本公开中，为了方便描述，如无特殊说明，将锚载波对应的上行载波也称为锚载波或上行锚载波，所述锚载波对应的上行载波在FDD系统中，一般通过系统信息块2中的频率信息(如ul-carrierfreq信息元素)来指示给用户。
非锚载波：non-anchor carrier，对FDD，指UE认为不传输NB-IoT相 关的NPBCH、NPSS、NSSS、SIB-NB等数据的载波，对TDD，指UE认为不传输NB-IoT相关的NPBCH、NPSS、NSSS等数据的载波。即UE认为非锚载波仅用于接收或发送NB-IoT相关的物理下行控制信道(PDCCH)、物理下行共享信道(PDSCH)、物理上行共享信道(PUSCH)等单播传输的数据。
CarrierConfigDedicated-NB信息元素：该信息元素用于在NB-IoT系统中配置一个载波。所述载波可以是一个锚载波，也可以是一个非锚载波。其配置包含一个上行载波配置和一个下行载波配置。其中，所述下行载波配置包含所述载波的频率信息，下行可用子帧信息、非锚载波下行间隔(gap)信息、带内载波信息等中的一种或多种。所述上行载波配置包含上行载波频率信息和/或TDD上下行对齐偏移信息等。该信息元素一般包含在radioresourceconfigdedicated信息元素中的physicalconfigdedicated信息元素中通过UE专用的RRC信息如RRC连接重配置消息下发给UE，其中radioresourceconfigdedicated信息元素用于建立/修改/释放无线承载、修改无线媒介控制(Medium Access Control，MAC)配置以及修改专用物理层配置等，physicalconfigdedicated信息元素用于指定UE特定的物理信道配置。
dl-configList信息元素：包含在系统信息中，用于配置包含用于寻呼和随机接入过程的非锚载波。包含一个非锚载波配置列表。
ul-configList信息元素：包含在系统信息中，用于配置包含用于随机接入过程的非锚载波，包含一个非锚载波列表。
早期数据传输(Early Data Transmission，EDT)：
R15中的小数据传输优化方案从控制面和用户面针对小数据传输的特性做了进一步的优化。对于上行数据传输来说，优化的内容主要是在随机接入过程中伴随消息3一起传输小数据，因为这种优化方式相较传统数据传输方式而言，能够在更早的时刻完成数据传输，所以称为早期数据传输，本公开中，小数据(small data或small packet)可等同于早期数据(early data)。
增强覆盖等级：增强覆盖技术中将需要增强覆盖的程度分为多个增强覆盖等级，比如在NB-IoT中，定义了三个增强覆盖等级。在MTC中，定义了四个增强覆盖等级。在一些增强覆盖方法中，每一个增强覆盖等级可以对应一套不同的无线参数配置，如随机接入配置(如PRACH(Phvsical  Random Access CHannel)资源)。UE的媒体接入控制(Medium Access Control)层在发起随机接入时，会根据所测量的RSRP和系统信息中收到的用于确定增强覆盖等级的RSRP门限值来判断UE的增强覆盖等级，并根据所确定的增强覆盖等级选择对应的随机接入资源(如preamble)和参数(如随机接入响应窗口大小)来发起随机接入过程。
物理下行控制信道(Physical Downlink Control Channel，PDCCH)：可以指3GPP LTE/LTE-A(Long Term Evolution/Long Term Evolution-Advanced)中的PDCCH或用于机器类通信的MPDCCH(MTC PDCCH)或用于窄带物联网通信的NPDCCH或NR(New Radio，也可称为5G)的NR-PDCCH等。所述物理下行共享信道可以指3GPP LTE/LTE-A(Long Term Evolution/Long Term Evolution-Advanced)中的物理下行共享信道(Physical Downlink Shared CHannnel，PDSCH)或用于窄带物联网通信的NPDSCH或NR-PDSCH等。
物理信令/信道：可以指物理唤醒信令(Wake Up Signal，WUS)/信道，或物理去睡眠信令(Go-To-Sleep Signal，GTS)/信道等。所述物理唤醒信令/信道指处于空闲模式的UE或处于RRC连接模式的非连续接收(Discontinuous Reception，DRX)状态的UE，在接收或检测或解码物理下行控制信道和/或物理下行共享信道之前，需要检测或解码该物理唤醒信令/信道。如果所述的物理唤醒信令被检测或解码到，则接收或检测或解码随后的物理下行控制信道和/或物理下行共享信道。备选地，所述物理唤醒信令/信道指处于空闲模式的UE或处于RRC连接模式的非连续接收(Discontinuous Reception，DRX)状态的UE，在接收或检测或解码物理下行控制信道和/或物理下行共享信道之前，需要检测或解码该物理唤醒信令/信道。如果所述的物理唤醒信令/信道被检测或解码到，则检测或解码随后的物理下行控制信道和/或物理下行共享信道。如果所述的物理唤醒信令/信道没有被检测或解码到，则不检测或不解码随后的物理下行控制信道和/或物理下行共享信道。或者说忽略或跳过随后的物理下行控制信道和/或物理下行共享信道。所述物理去睡眠信令/信道指处于空闲模式的UE或处于RRC连接模式的非连续接收(Discontinuous Reception，DRX)状态的UE，在接收或检测或解码物理下行控制信道和/或物理下行共享信道之前，需要检测或解码该物理去睡眠信令/信道。如果所述的物理去睡眠信令/信道被检测或解码到，则UE不检测或不解码随后的物理下行控制信道和/或物理下 行共享信道，而直接进入睡眠状况。备选地，所述物理去睡眠信令/信道指处于空闲模式的UE或处于RRC连接模式的非连续接收(Discontinuous Reception，DRX)状态的UE，在接收或检测或解码物理下行控制信道和/或物理下行共享信道之前，需要检测或解码该物理去睡眠信令/信道。如果所述的物理去睡眠信令/信道被检测或解码到，则不检测或不解码随后的物理下行控制信道和/或物理下行共享信道。如果所述的物理唤醒信令没有被检测或没有解码到，则接收或检测或解码随后的物理下行控制信道和/或物理下行共享信道。
LTE中的寻呼机制：
在3GPP Rel-14标准规范中，处于空闲模式下的UE可以采用非连续接收来减少功率损耗。一个寻呼时机(Paging Occasion，PO)是一个子帧，在该子帧上可能会有使用寻呼无线网络临时标识(Paging-Radio Network Temporary Identifier，P-RNTI)加扰，并调度寻呼消息的PDCCH或MPDCCH或NPDCCH。在使用P-RNTI加扰的MPDCCH的情况下，PO指MPDCCH重复发送的起始子帧。在使用P-RNTI加扰的NPDCCH的情况下，PO指NPDCCH重复发送的起始子帧，除非由PO所决定的子帧不是一个有效的NB-IoT下行子帧。当由PO所决定的子帧不是一个有效的NB-IoT下行子帧时，则PO后的第一个有效的NB-IoT下行子帧即为NPDCCH重复发送的起始子帧。
寻呼无线帧(Paging Frame，PF)是一个无线帧，该帧可能包含一个或多个PO。当DRX被采用时，UE只需在每一个DRX循环周期内监测一个PO。
寻呼窄带(Paging Narrowband，PNB)是一个窄带，UE在该窄带上接收寻呼消息。
PF、PO和PNB是用系统信息所提供的DRX参数，采用以下公式来决定的。
PF由以下公式给出：
SFN mod T＝(T div N)*(UE_ID mod N)         (1)
使用索引i_s根据双工模式和系统带宽查表1、表2、表3或表4，可得到PO。其中，i_s通过以下公式得到：
i_s＝floor(UE_ID/N)mod Ns          (2)
对于FDD：
表1(PDCCH或NPDCCH由P-RNTI加扰，或MPDCCH由P-RNTI加扰且系统带宽大于3MHz时)
Ns PO，i_s＝0 PO，i_s＝1 PO，i_s＝2 PO，i_s＝3
1 9 N/A N/A N/A
2 4 9 N/A N/A
4 0 4 5 9
表2(MPDCCH由P-RNTI加扰且系统带宽为1.4MHz和3MHz)
Ns PO，i_s＝0 PO，i_s＝1 PO，i_s＝2 PO，i_s＝3
1 5 N/A N/A N/A
2 5 5 N/A N/A
4 5 5 5 5
对于TDD(所有的上/下行配置)：
表3(PDCCH由P-RNTI加扰，或MPDCCH由P-RNTI加扰且系统带宽大于3MHz时)
Ns PO，i_s＝0 PO，i_s＝1 PO，i_s＝2 PO，i_s＝3
1 0 N/A N/A N/A
2 0 5 N/A N/A
4 0 1 5 6
表4(MPDCCH由P-RNTI加扰且系统带宽为1.4MHz和3MHz)
Ns PO，i_s＝0 PO，i_s＝1 PO，i_s＝2 PO，i_s＝3
1 1 N/A N/A N/A
2 1 6 N/A N/A
4 1 1 6 6
如果所检测到的MPDCCH是由P-RNTI加扰的，则寻呼窄带PNB由以下公式所决定：
PNB＝floor(UE_ID/(N*Ns))mod Nn        (3)
如果所检测到的NPDCCH是由P-RNTI加扰的，并且UE支持在非锚载波上接收寻呼消息，而且，如果在系统信息中为非锚载波提供了寻呼消息的配置信息，则寻呼载波由满足以下公式(4)的最小寻呼载波n所决定：
Figure PCTCN2019114314-appb-000001
                                       
Figure PCTCN2019114314-appb-000002
每当系统信息中的DRX参数发生改变时，存储在UE中的系统信息DRX参数需要在UE中进行本地更新。如果UE没有国际移动用户识别码(International Mobile Subscriber Identity，IMSI)，例如UE没有通用用户标识模块(Universal Subsriber Identity Module，USIM)而需要发起紧急呼叫时，UE需要在以上PF、i_s和PNB公式中使用缺省标识UE_ID＝0。
以下参数用于计算PF、i_s、PNB和NB-IoT的寻呼载波：
·T：UE的DRX周期。除了NB-IoT之外，如果高层配置了UE特定的扩展的DRX值为512个无线帧，则T＝512。否则，T由UE特定的DRX周期(如果高层已配置)和系统信息广播的缺省DRX周期二者中的最短DRX周期所决定。如果高层没有配置UE特定的DRX周期，则采用缺省的DRX周期。UE特定的DRX周期不适用于NB-IoT。
·N：min(T，nB)
·Ns：max(1，nB/T)
·Nn：系统信息中所提供的寻呼窄带的数目
·UE_ID：
IMSI mod 1024，如果使用P-RNTI加扰在PDCCH上
IMSI mod 4096，如果使用P-RNTI加扰在NPDCCH上
IMSI mod 16384，如果使用P-RNTI加扰在MPDCCH上，或使用P-RNTI加扰在NPDCCH上且UE支持在非锚载波上接收寻呼消息，并且如果在系统信息中为非锚载波提供了寻呼消息的配置信息。
·maxPagingCarriers：系统信息中提供的已配寻呼载波数
·Weight(i)：NB-IoT第i个寻呼载波的权重
IMSI是一连串的10进制数字(0..9)，IMSI在公式中被解释成10进制整数，其中第1位为最高位，以此类推。例如：IMSI＝12(digit 1＝1，digit 2＝2)，计算时该IMSI被解释成10进制数“12”，而不是“1*16+2＝18”。
在3GPP Rel-14标准规范中，对于处于空闲模式的UE，采用寻呼机制可以减少UE的功率损耗。而当UE信道状态不好，需要采用覆盖增强时，PDCCH和/或PDSCH需要重复发送，才能从基站正确接收到信息或正确发 送信息到基站。当UE要检测寻呼消息前，需要从睡眠状态中唤醒以在每一PO上检测是否有自己的寻呼消息。而在大多时候，UE都不会有寻呼消息。这样，当UE处于覆盖增强状态时，需要多次重复地接收PDCCH或PDSCH才能检测到是否有自己的寻呼消息，而大多数时候是没有自己的寻呼消息。因此，会大量损耗UE的功率。而对于MTC或NB-IoT用户而言，降低UE的功率损耗极为重要。所以，在3GPP Rel-15标准规范中，对于处于空闲状态的UE，引入了物理唤醒信令。即以在每一PO上检测寻呼消息前，设计一物理唤醒信令。如果UE检测到该物理唤醒信令，则检测随后PO上的寻呼消息，即检测使用P-RNTI加扰的PDCCH(或MPDCCH或NPDCCH)以及接收由该PDCCH(或MPDCCH或NPDCCH)调度的PDSCH(或NPDCCH)。如果UE没有检测到该物理唤醒信令，则不检测随后PO上的寻呼消息，直接回到睡眠状态。
为了进一步减少UE的功率损耗，可以引入基于UE分组的物理唤醒信令(UE-group WUS)，或物理去睡眠信令。例如，可以将对应于某一PO的UEs分成若干组，某一组或多组UEs采用一个WUS。考虑后向兼容性，新引入的UE-group WUS或Rel-16UE-group WUS不要影响现有Rel-15 WUS的存在和性能。也就是说，当系统支持Rel-16UE-group WUS时，可以同时支持Rel-15 WUS。另外，考虑到并不是所有Rel-16的UEs都支持UE-group WUS功能，需要将Rel-16的UEs分成支持UE-group WUS的UEs和不支持UE-group WUS的UEs。因此，在Rel-16的系统中有3类支持WUS功能的UE：Rel-15WUS UE或遗留WUS UE(Legacy WUS UE：LWUS UE)、不支持UE-group WUS UE(NGWUS UE)和支持UE-group WUS UE(GWUS UE)。本公开下述实施例就如何配置UE分组的GWUS提出解决方法，通过所述方法，可以实现基于UE分组的GWUS传输，使得UE获知GWUS的配置，并能够基于UE的分组来监听其所关联的GWUS，达到节能的目的。
而对于前述预配置上行资源，可以有两种方式，一种是专用预配置上行资源，即为一个UE预分配专用的上行资源，这样上行数据传输不会产生碰撞冲突另一种是共享的预配置上行资源，即所分配的上行资源是多个UE共享的，可以是一个共享资源池，这种方式下，多个UE可能使用一个资源 发送上行，从而存在潜在的竞争引起冲突而导致发送失败。最近的3GPP会议上达成结论是支持通过RRC专用信令为UE分配专用预配置上行资源，而是否支持共享预配置上行资源尚未定论。预配置上行资源是通过RRC消息预先分配给UE使用的上行资源，所述预配置上行资源可以是在RRC连接态分配的用于当UE处于RRC空闲态时的上行数据传输和/或用于RRC连接态，也可以是通过系统信息告知给UE用于RRC空闲态时的上行数据传输。虽然本公开以RRC空闲态的UE为典型场景来阐述下述解决方法，但如无特殊说明，本公开下述实施例也同样适用于RRC连接态的UE，比如实施例1中的载波配置实现方式也可适用于用于RRC连接态UE进行上行数据传输时的预配置上行资源配置。
在NB-IoT系统中，版本13的系统中，仅支持UE驻留在锚载波上，即在锚载波上发起用于和网络侧建立连接的随机接入过程或者从锚载波上接受用于下行业务的寻呼消息，但可以支持UE在进入连接态后，通过RRC专用消息如RRC连接重配置消息为UE配置一个非锚载波(即通过CarrierConfigDedicated-NB信息元素所配置的载波)，这样可以将UE的上下行业务转移到所配置的非锚载波上去，进而实现锚载波和非锚载波之间的负载均衡。在版本14的系统中，增加了对在非锚载波上的随机接入过程和接收寻呼的功能，这个功能是通过在系统信息中携带一个上行非锚载波配置列表(即前述ul-configList信息元素)和下行非锚载波配置列表(即前述dl-configList信息元素)来实现的。UE可以根据一定的规则(可参见3GPP协议文档36.321中5.1章节)在上行非锚载波列表中选择一个非锚载波进行随机接入过程，或者可以根据一定规则(可参见GPP协议文档36.304第7章节)在下行非锚载波列表中选择一个非锚载波监听/接收寻呼。对所述预配置上行资源，为了最大限度利用NB-IoT系统资源，实现锚载波和非锚载波的负载均衡，本公开中对如何在锚载波和非锚载波上为UE配置预配置上行资源提出解决方法。
对于专用的预配置上行资源来说，专用的预配置资源可以是所述UE在之前处于RRC连接状态时由基站通过RRC专用信令对其进行配置的如RRC连接释放消息、RRC连接重配置消息、RRC连接建立消息、RRC连接恢复消息等与RRC连接相关的消息。处于RRC空闲态的UE可以使用所述专用预配置上行资源发送上行数据。但当UE回退到传统传输方式如因为 接收到寻呼消息而需要进入到RRC连接状态进行下行业务传输时，如何处理用于空闲状态的预配置上行资源成为需要解决的问题。此外，所述回退到传统传输方式也可能是由于在预配置上行资源上的传输失败所触发的，在这种情况下，如何实现回退到传统传输方式也是本公开所关注的问题。
本公开下述实施例中，指示(indicate/indication)和通知(notify/notification)或知会/信息(inform/information)可以互换。UE可以指NB-IoT UE、带宽降低低复杂度(Bandwidth reduced Low complexity，BL)UE、或在增强覆盖(enhanced coverage)中的UE、也可以是其他UE如5G NR UE。在本公开中，PRACH、NPRACH和RACH可以替换。所述预配置上行资源也可称为预配置上行许可(uplink grant)或预分配上行资源(preallocated uplink resource)或预分配上行许可(preallocated uplink grant)等。覆盖增强等级(Coverage Enhancement level)等同于增强覆盖等级(Enhanced Coverage level)，或者也可称重复等级(Repetition Level)。
实施例1
图1是示意性示出本公开实施例1的用户设备执行的方法的流程图。
下面，结合图1来详细说明本公开实施例1的用户设备执行的方法。
该实施例提出了一种预配置上行资源的配置方法。在用户设备UE上实施。
如图1所示，步骤S101：UE接收包含预配置上行资源配置的RRC消息。优选地，所述RRC消息可以是RRC连接释放消息；备选地，可以是RRC连接重配置消息、RRC连接重建立消息、RRC连接建立消息、RRC连接恢复消息等与RRC连接相关的消息。以下给出所述预配置上行资源配置的载波信息的几种实现方式。
在一种实施方式中，若所述预配置上行资源配置中不包含载波信息，则UE使用锚载波(即UE认为所述预配置上行资源是针对锚载波的)；若所述预配置上行资源配置中的载波信息置为“non-anchor carrier”或“dedicated carrier”，则UE使用通过专用RRC消息中的CarrierConfigDedicated信息元素所配置的载波，即UE认为所配置的预配置上行资源是针对CarrierConfigDedicated信息元素所配置的专用载波的。
在一种实施方式中，若所述预配置上行资源配置中的载波信息置为“0” 或“TURE”，则UE使用锚载波(即UE认为所述预配置上行资源是针对锚载波的)；若所述预配置上行资源配置中的载波信息置为“1”或“FALSE”，则UE使用通过专用RRC消息中的CarrierConfigDedicated信息元素所配置的载波，即UE认为所配置的预配置上行资源是针对CarrierConfigDedicated信息元素所配置的专用载波的。此时，所述载波信息可以表示是否使用锚载波用于预配置上行资源。反之也可，若所述预配置上行资源配置中的载波信息置为“1”或“FALSE”，则UE使用锚载波(即UE认为所述预配置上行资源是针对锚载波的)；若所述预配置上行资源配置中的载波信息置为“0”或“TURE”，则UE使用通过专用RRC消息中的CarrierConfigDedicated信息元素所配置的载波，即UE认为所配置的预配置上行资源是针对CarrierConfigDedicated信息元素所配置的专用载波的。此时，所述载波信息可以表示是否使用专用(非锚)载波用于预配置上行资源。
在另一种实施方式中，所述预配置上行资源配置中的载波信息包含一个载波索引，用于指示使用系统信息中的哪个载波用于预配置上行资源。对于预配置上行资源配置中的上行载波，所述载波索引值为“0”对应于锚载波对应的上行，即使用锚载波用于预配置上行资源，所述载波索引值为“1”对应于所述ul-configList信息元素中的第一个条目(entry)；所述载波索引值为“2”对应于所述ul-configList信息元素中的第二个条目，以此类推。对于预配置上行资源配置中的下行载波，所述载波索引值为“0”对应于锚载波，即使用锚载波用于预配置上行资源，所述载波索引值为“1”对应于所述dl-configList信息元素中的第一个条目(entry)；所述载波索引值为“2”对应于所述dl-configList信息元素中的第二个条目，以此类推。所述预配置上行资源中的下行载波可用于数据重传的下行调度和/或用于响应上行数据的下行接收等。
步骤S102：UE保存收到的预配置上行资源配置。
步骤S103：当UE进入RRC空闲态(或称离开RRC连接态或RRC不活动态(inactive))时，应用所保存的预配置上行资源配置。可选地，开启预配置上行资源有效性定时器。所述应用所保存的预配置上行资源配置指的是按照所保存的预配置上行资源配置对相关协议层进行配置。所述预配置上行资源有效性定时器，用于确定预配置上行资源是否有效。例如，当所述定时器运行时，认为所保存或所配置的预配置上行资源有效；当所述 定时器不运行或超时时，认为所保存或所配置的预配置上行资源无效。
对所述预配置上行资源有效性定时器，有一种实现方式是所述定时器是时间对齐定时器(Time Alignment Timer，TAT)。TAT是现有技术中用于控制MAC实体认为一个服务小区在多长时间内是处于上行对齐(即上行同步)状态的。也就是说，当TAT运行时，UE MAC实体认为所对应的服务小区是上行对齐的，此时所述预配置上行资源是有效的；当TAT不运行或超时后，UE MAC实体认为所对应的服务小区不是上行对齐的，此时所述预配置上行资源是无效的。
实施例2
图2是示意性示出本公开实施例2的用户设备执行的方法的流程图。
下面，结合图2来详细说明本公开实施例2的用户设备执行的方法。
该实施例给出了一种预配置上行资源的管理方法。在该实施例中，若UE进入RRC连接态，则UE认为所保存的用于RRC空闲态的预配置上行资源是没有用的，UE可以自行删除所述预配置上行资源相关配置，以此避免在UE处于连接态时执行由预配置上行资源相关配置所带来的资源管理能耗。
如图2所示，步骤S201：UE进入RRC连接状态。
所述进入RRC连接态可以是UE接收到用于指示UE进入连接态的RRC消息，优选地，是RRC连接恢复消息或RRC连接建立消息。
步骤S202：UE执行下述操作的一种或多种：
操作1：释放(所保存的)预配置上行资源配置。
操作2：释放(所配置的)预配置上行资源。
操作3：停止用于确定预配置上行资源有效性的定时器。
所述“释放”也可以是“删除”。
实施例3：
图3是示意性示出本公开实施例3的用户设备执行的方法的流程图。
下面，结合图3来详细说明本公开实施例3的用户设备执行的方法。
该实施例给出了另一种预配置上行资源的管理方法。在该实施例中，若UE进入RRC连接态，则UE认为所保存的用于RRC空闲态的预配置上 行资源可以在UE再次进入空闲态后使用，所以UE会保留所述预配置上行资源相关配置，这样若网络侧在UE再次进入空闲态时对其配置预配置上行资源时，可以减少或避免重新配置所述预配置上行资源带来的信令开销。
如图3所示，步骤S301：UE进入RRC连接状态。
所述进入RRC连接态可以是UE接收到用于指示UE进入连接态的RRC消息，优选地，是RRC连接恢复消息或RRC连接建立消息。
步骤S302：UE执行下述操作的一种或多种：
操作1：若所述RRC消息中包含预配置上行资源配置，则UE应用所收到的预配置上行资源配置。若UE之前有保存的预配置上行资源配置，则所述应用所收到的预配置上行资源配置还包括，UE更新所保存的预配置上行资源配置，即用收到的RRC消息中包含的预配置上行资源配置替换所保存的预配置资源预配置上行资源配置。
操作2：如果有正在运行的用于确定预配置上行资源有效性的定时器，则重新启动用于确定预配置上行资源有效性的定时器。
实施例4
图4是示意性示出本公开实施例4的用户设备执行的方法的流程图。
下面，结合图4来详细说明本公开实施例4的用户设备执行的方法。
一般来说，配置了预配置上行资源的UE会使用所对应的预配置上行资源来发送上行。但在一些情况下，比如UE没有有效的TA，或者所要发送的上行数据量较大等，UE会选择回退到传统上行发送方式，即通过触发随机接入过程使用EDT来发送上行数据或使用非EDT的传统RRC连接建立/恢复过程来进入RRC连接态发送上行数据。
本实施例给出了一种配置了预配置上行资源的UE在预配置的上行资源上发送不成功从而回退到传统上行发送方式的方法。在RRC空闲态的UE上执行。
如图4所示，步骤S401：UE底层执行预配置上行资源发送，即UE使用预配置的上行资源发送上行数据。所述底层指MAC层和/或物理层。
在步骤S401之前，还可以包括RRC确定使用预配置上行资源的方式发送上行数据，并向底层指示使用预配置上行资源的方式发送上行数据。
步骤S402：若底层未接收到来自基站的任何响应信息，比如用于确认 步骤S401中的上行发送是成功收到或接收失败的指示，则底层向上层(RRC层)发送一个指示信息，用于告知上层所述底层未收到预配置资源上行传输的响应，或者说告知上层所述底层的预配置资源上行传输失败，该指示信息也可以理解为请求上层执行回退到传统上行发送的指示。
所述底层未接收到来自基站的任何响应的确定可以是基于一定的时间来确定的，比如在发送完上行数据后的一段时间内未收到任何响应。或者UE对所述上行数据执行了一定次数的重传后，仍未接收到任何响应的。可选地，所述响应可以是指示成功接收的响应。
可选地，该步骤还包括，MAC层清空MAC层相关缓存，可以是消息3缓存或者混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)缓存。
步骤S403：当收到来自底层的步骤S402中的指示后，RRC层执行回退的传统上行传输方式的操作所述操作可以包括下述一项或多项：
操作1：启动或重启T300定时器。
操作2：重建数据无线承载(Data Radio Bearer，DRB)和/或信令无线承载(Signalling Radio Bearer，SRB)对应的无线链路控制(Radio Link Control，RLC)层。
操作3：重建数据无线承载(Data Radio Bearer，DRB)和/或信令无线承载(Signalling Radio Bearer，SRB)对应的包数据汇聚协议(Packet Data Convergence Protocol，PDCP)层。
操作4：删除为在预配置上行资源上执行上行数据发送所派生的安全密钥。
操作5：挂起所有的SRB和DRB，此处不包括SRB0。
操作6：配置下层挂起完整性保护和加密功能。
实施例5
图5是示意性示出本公开实施例5的用户设备执行的方法的流程图。
下面，结合图5来详细说明本公开实施例5的用户设备执行的方法。
对于预配置上行资源的使用，有一种实现方式是，当有上行数据需要传输时(如基于NAS层的请求)，由RRC层来判断是使用预配置上行资源传输方式还是使用传统上行数据传输方式，在所述预配置上行资源是否有效的判断在一些情况下是由RRC层来判断的，比如基于服务小区是否改变 来判断，在一些其他情况下是由MAC层来判断的，比如前面所述基于TAT是否超时来判断。此时就需要MAC层和RRC层之间的交互信息来完成整个是否使用预配置上行资源传输方式的确定，本实施例中提供了一种层间交互的信息的解决方法。
如图5所示，步骤S501：UE MAC实体判断预配置上行资源是无效的。所述判断可以是基于所述预配置上行资源有效性定时器或TAT，也可以是基于在预配置资源上的发送失败，也可以是基于下行信道质量如RSRP超过一个配置的门限值。
步骤S502：当UE MAC实体判断预配置上行资源是无效的时，UE MAC层向UE RRC层发送一个预配置上行资源无效指示，即向RRC层指示所述预配置上行资源是无效的。可选地，所述指示也可以指示具体的无效原因，比如预配置上行资源有效性定时器超时或TAT超时。
步骤S503：收到来自MAC层的该指示的RRC层，可以释放所述预配置上行资源配置。
步骤S503是可选地，即RRC层也可以选择在收到所述指示后，不释放所述预配置上行资源配置，而直接回退到传统上行数据发送方式。在这种实现方式下，RRC在判断是否使用预配置上行资源传输方式时就需要基于所述预配置的上行资源(配置)是否有效来确定，即仅在有有效的预配置上行资源时，才能使用预配置上行资源传输方式。
这样，根据上述的各个实施例所述，本公开提供了一种能够解决预配置上行资源的配置和管理问题的用户设备执行的方法。
变形例
下面，利用图6来说明作为一种变形例的可执行本公开上面所详细描述的用户设备执行的方法的用户设备。
图6是示意性示出本公开所涉及的用户设备的框图。
如图6所示，该用户设备UE80包括处理器801和存储器802。处理器801例如可以包括微处理器、微控制器、嵌入式处理器等。存储器802例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器802上存储 有程序指令。该指令在由处理器801运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
实施例6
本实施例给出了一种基于UE分组的物理唤醒信号的配置方法，可以在UE或基站或包含UE和基站的系统上实施。通过该方法，UE和基站可以基于所配置的基于分组的WUS完成WUS的接收或发送，从而达到节省UE能耗以及使用最少的WUS资源来达到UE节省能耗的目的。
所述方法包括：将对应于某一PO的GWUS UEs分成若干UE组，为每一组或多组UE分配一个WUS。例如，将对应于某一PO的支持UE-group WUS UEs分成4组：G1、G2、G3和G4。如果为每一组UE分配一个GWUS，则需要4个WUS：GWUS1、GWUS2、GWUS3和GWUS4，分别对应于G1、G2、G3和G4。备选地，可以为4组UE进行组合，共有15种组合：G1、G2、G3、G4、G1+G2、G1+G3、G1+G4、G2+G3、G2+G4、G3+G4、G1+G2+G3、G1+G2+G4、G1+G3+G4、G2+G3+G4、G1+G2+G3+G4。可以为每一种组合分别分配一个GWUS，则需要15个GWUS。备选地，可以选出某几种组合，为所选出的组合分别分配一个GWUS。例如，G1、G2、G3、G4、G1+G2、G1+G3、G1+G4、G2+G3、G2+G4、G3+G4、G1+G2+G3+G411种组合，分别为这11中组合分配11个GWUS：GWUS1、GWUS2，...，GWUS10、GWUS11。当G1的UE有寻呼消息时，基站发送GWUS1；当同时G1和G2的UE有寻呼消息时，基站发送GWUS5；当同时G1、G2、G3和G4的UE有寻呼消息时，基站发送GWUS11。备选地，G1、G2、G3、G4分别分配一个GWUS，而为G1+G2+G3+G4单独分配一个GWUS(也可以称为共同的CWUS)。这样，需要5个GWUS。备选地，可以通过系统信息或UE特定的RRC信令或MAC信令或物理层信令为共同的WUS(Common WUS，CWUS)进行配置，将CWUS配置成LWUS或新定义的WUS。
Rel-16不支持UE-group WUS的UE可以被配置为LWUS UE，或者为Rel-16不支持UE-group WUS的UE配置的WUS为LWUS，即Rel-16不支持UE-group WUS的UE使用LWUS进行工作。备选地，可以为Rel-16不支持UE-group WUS的UE配置新定义的WUS。
备选地，对于Rel-16支持UE-group WUS的UE，可以将若干个分组中的某一组或多组UE配置为使用LWUS UE，或者为Rel-16支持UE-group WUS的若干个分组中的某一组或多组UE配置的WUS为LWUS，即Rel-16支持UE-group WUS的若干个分组中的某一组或多组UE使用LWUS进行工作。
LWUS与GWUS之间、GWUS与GWUS之间的复用可以是时分复用(Time Division Multiplexing，TDM)、频分复用(Frequency Division Multiplexing，FDM)、码分复用(Code Division Multiplexing，CDM)、FDM+TDM、FDM+CDM、TDM+CDM或FDM+TDM+CDM。LWUS与GWUS之间的复用方式可以不同于GWUS与GWUS之间的复用方式。例如，LWUS与GWUS之间采用TDM，而GWUS与GWUS之间采用CDM。备选地，LWUS与GWUS之间采用FDM，而GWUS与GWUS之间采用CDM或FDM+CDM。备选地，LWUS与GWUS之间的复用方式和GWUS与GWUS之间的复用方式采用同一复用方式，例如，同一采用CDM或上述可能的复用方式之一。
基站可以根据其运行环境(例如，所服务的UE数等)对LWUS与GWUS之间的复用方式进行配置。备选地，基站根据所支持的UE组数或其它可能的参数，对LWUS与GWUS之间的复用方式和/或GWUS与GWUS之间的复用方式进行单独配置或同一配置。
FDM是基于一个或多个物理资源块(PRB)为单位进行复用。备选地，FDM是基于一个或多个子载波为单位进行复用。
TDM是基于一个或多个正交频分复用(Orthogonal Frequency Division Multiplexing：OFDM)符号为单位进行复用。备选地，TDM是基于一个或多个子帧为单位进行复用。备选地，TDM是基于一个或多个无线帧为单位进行复用。备选地，TDM是基于一个或多个非连续接收(Discontinuous Reception：DRX)周期为单位进行复用。备选地，TDM是基于一个或多个增强的非连续接收(Enhanced Discontinuous Reception：eDRX)周期为单位进行复用。
CDM是基于不同的基础序列进行复用。备选地，CDM是基于同一的基础序列的不同覆盖码(Cover Code)进行复用。所述的覆盖码可以是频域覆盖码也可以是时域覆盖码。例如，在一个PRB中有12个子载波，可以生 成12个正交覆盖码；备选地，所述的覆盖码是基于时域的OFDM符号所生成。采用CDM方式时有2种传输方式：某一时刻只传输一个码(基础序列或覆盖码)，以及某一时刻传输多个码(基础序列或覆盖码)。
在一种实现方式中，UE基于其UE标识来确定其属于哪个分组。UE和基站需要获知多个UE分组以及基于UE分组的GWUS的配置信息后，才能基于UE的分组来监听/发送对应的分组所关联的GWUS。下面给出UE分组的多种组合和多个GWUS之间的关联方式，但值得注意的是，本公开所述UE获知UE分组的多种组合和多个GWUS之间的关联方式并不限于下述两种实现方式。
在一种实现方式中，所述GWUS的配置信息包含一个GWUS列表，列表中的每一项对应一个GWUS，即包含一个GWUS的资源配置。所述资源配置可以是时域资源、频域资源、码域资源和/或空域资源。除此之外，所述GWUS配置信息还包含一个UE分组个数信息和/或一个比特位图。所述UE分组个数信息用于指示UE分组的个数；所述比特位图用于指示基于UE分组的多个组合中，每个组合是否关联到GWUS列表中的一个GWUS。在UE分组的个数为N时，所述比特位图的长度为
Figure PCTCN2019114314-appb-000003
个比特。N个UE分组的各组之间的组合最大可能的个数也是
Figure PCTCN2019114314-appb-000004
Figure PCTCN2019114314-appb-000005
个(即G1，G2......，GN，G1+G2，G1+G3，......，G1+GN，G2+G3，G2+G4，......，G2+GN，G3+G4，......G3+GN，......，GM+G(M+1)，……，GM+GN，G(N-1)+GN，G1+G2+G3，G1+G2+G4，……，G1+G2+GN，G1+G3+G4，G1+G2+......+GN)，这样比特位图中的每一个比特对应于UE分组的各组的一个组合或所述组合所对应的GWUS。对某一个比特，若所述比特的值置为1，则该比特所对应的UE分组的组合所关联的GWUS包含在所述GWUS列表中，若所述比特的值置为0，则该比特所对应的UE分组的组合所关联的GWUS不包含在所述GWUS列表中，即没有配置该UE分组的组合所关联的GWUS。例如，UE分组的个数为4组G1～G4，那么各组的组合最多有15个组合，即G1、G2、G3、G4、G1+G2、G1+G3、G1+G4、G2+G3、G2+G4、G3+G4、G1+G2+G3、G1+G2+G4、G1+G3+G4、G2+G3+G4、G1+G2+G3+G4。此时比特位图的长度为15，每一个比特对应于上述15个组合中的一个，比如比特1对应于G1，比特2对应于G2，比特3对应于G3，比特4对应于G4，比特5对应于G1+G2，以此类推，比 特15对应于G1+G2+G3+G4。比特位图的比特的排列顺序和UE分组的各种组合的一一对应关系需要事先规定或在信令中进行配置(比如，当分组个数为1时，GWUS列表中仅包含一个GWUS1的配置；当分组个数为2时，比特位图中的各个比特对应到分组组合的顺序为比特1到比特3依次对应的分组组合为G1、G2、G1+G2；当分组个数为3时，比特位图中的各个比特对应到分组组合的顺序为比特1到比特7依次对应的分组组合为G1、G2、G3、G1+G2、G1+G3、G2+G3、G1+G2+G3；当分组个数为4时，如前例所述，此处不赘述)。但网络侧并不一定对15种组合都配置一个关联的GWUS。在该例子下，网络侧对15种组合中的11个组合配置了关联的GWUS，其对应的GWUS配置包含在GWUS配置中的GWUS列表中，即GWUS列表中包含11项GWUS1～GWUS11。此时15种组合中哪些组合配置了关联的GWUS则通过所述比特位图中的比特值来指示。若比特位图的值为111111111100001，则表示配置了G1、G2、G3、G4、G1+G2、G1+G3、G1+G4、G2+G3、G2+G4、G3+G4、G1+G2+G3+G411种组合所对应的GWUS，而对G1+G2+G3、G1+G2+G4、G1+G3+G4、G2+G3+G4这四种组合没有配置GWUS。比特位图中的比特置为1的项的个数和GWUS列表中的GWUS项数一致，且比特位图中的比特置为1的项的排列顺序和GWUS列表中的GWUS项的排列顺序一致，即比特位图中的指为1的低位(或高位或最左边或最右边)第一位对应于GWUS列表中的第一项，比特位图中的值为1的低位(或高位或最左边或最右边)第二位对应于GWUS列表中的第二项，以此类推。通过上述方式，所配置的多个GWUS和UE分组的各个组合之间的对应关系就可以通过所述比特位图以及比特位图和UE分组的各个组合之间的对应关系来获知。在上述的例子中，GWUS1～11分别依次对应于G1、G2、G3、G4、G1+G2、G1+G3、G1+G4、G2+G3、G2+G4、G3+G4、G1+G2+G3+G4 11种组合。
在另一种实现方式中，除了GWUS配置中包含的GWUS列和/或UE分组的个数信息之外，每一个GWUS包含了一个分组(组合)信息，所述分组(组合)信息用于指示该GWUS所对应的UE分组或UE分组的组合之间的关联关系。通过这种显示的方式来配置多个GWUS和多个UE分组或UE分组的组合之间的关联关系。以上述例子来说，GWUS配置信息中的GWUS配置列表中包含了11个GWUS项，对应11个GWUS即 GWUS1～GWUS11。每个GWUS的配置包含其关联的分组(组合)信息，如GWUS1的配置信息中包含的分组(组合)信息指示为G1，GWUS2的配置信息中包含的分组(组合)信息指示为G2，GWUS3的配置信息中包含的分组(组合)信息指示为G3，GWUS4的配置信息中包含的分组(组合)信息指示为G4，GWUS5的配置信息中包含的分组(组合)信息指示为G1+G2，以此类推。在一种实现方式下，所述分组(组合)信息是比特位图，比特位图的长度为分组个数的长度，比特位图的比特的从低位到高位(或从高位到低位或从左到右或从右到左)顺序和UE分组组合的组号从小到大(或从小到大)的顺序一致。比如对于GWUS5(即GWUS列表中的第五项)，其分组(组合)信息指示为1100，对于GWUS6(即GWUS列表中的第六项)，其分组(组合)信息指示为1010。
在获知了上述GWUS列表中各项GWUS和UE分组的组合之间的对应关系或关联关系后，UE基于自己的分组去监听所述分组所关联或对应的GWUS，而无需去监听与UE自己的分组不关联的GWUS，以达到UE省电的目的。还以上述例子为例，UE分组个数为4组，UE通过比如UE标识等信息和公式确定其分组为组2即G2，在网络侧配置了11个组合G1、G2、G3、G4、G1+G2、G1+G3、G1+G4、G2+G3、G2+G4、G3+G4、G1+G2+G3+G4所对应的GWUS1～11时，UE监听与自己的分组2即G2所对应的GWUS，即GWUS2\GWUS5\GWUS8\GWUS9\GWUS11，而不去或不需要去监听GWUS1\GWUS3\GWUS4\GWUS6\GWUS7\GWUS10。
在又一种实现方式中，UE所关联的GWUS通过专用信令来配置，即UE需要监听通过专用信令配置的所有GWUS。
在又一种实现方式中，UE所关联的GWUS通过专用信令来配置。在这种方式下，网络侧通过系统信息下发该小区所用的所有GWUS，即包含在一个GWUS列表中。在UE的专用信令配置的GWUS中，包含一个比特位图，比特位图的长度和GWUS的个数(或称GWUS列表的项数)一致。比特位图中的每一个比特对应一个GWUS，若比特位图中所对应的比特置为1，则UE监听该比特所对应的GWUS，若比特位图中所对应的比特置为0，则UE不去或不需要去监听该比特所对应的GWUS。比特位图中的比特的排列顺序与其对应的GWUS在GWUS列表中的顺序一样。
在又一种实现方式下，GWUS配置信息中包含每一个UE分组所对应 的GWUS。GWUS配置列表中GWUS的排列顺序和UE分组的组号从小到大(或从大到小)的顺序一一对应。若UE分组的个数为N组，则GWUS列表中的第一项对应于UE分组的组1即G1，GWUS列表中的第二项对应于UE分组的组2即G2，以此类推，GWUS列表中的第N项对应于UE分组的组N即GN。
上述所出现的配置可以通过系统信息或UE特定的RRC信令或MAC信令或物理层信令实现。
上文已经结合优选实施例对本公开的方法和涉及的设备进行了描述。本领域技术人员可以理解，上面示出的方法仅是示例性的，而且以上说明的各实施例在不发生矛盾的情况下能够相互组合。本发明的方法并不局限于上面示出的步骤和顺序。上面示出的用户设备可以包括更多的模块，例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的，本公开并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
应该理解，本公开的上述实施例可以通过软件、硬件或者软件和硬件两者的结合来实现。例如，上述实施例中的基站和用户设备内部的各种组件可以通过多种器件来实现，这些器件包括但不限于：模拟电路器件、数字电路器件、数字信号处理(DSP)电路、可编程处理器、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、可编程逻辑器件(CPLD)，等等。
在本申请中，“基站”可以指具有较大发射功率和较广覆盖面积的移动通信数据和控制交换中心，包括资源分配调度、数据接收发送等功能。“用户设备”可以指用户移动终端，例如包括移动电话、笔记本等可以与基站或者微基站进行无线通信的终端设备。
运行在根据本公开的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统 中。
用于实现本公开各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种用户设备执行的方法，包括：
    接收包含预配置上行资源配置的RRC消息，
    所述RRC消息包括由基站配置的与RRC连接相关的消息，
    所述用户设备根据所述预配置上行资源配置中的载波信息，来确定所述预配置上行资源配置是针对锚载波还是针对非锚载波。
  2. 根据权利要求1所述的方法，其中，
    所述根据所述预配置上行资源配置中的载波信息包括：
    根据所述载波信息的有无；或
    根据所述载波信息的取值；或
    根据所述载波信息包含的载波索引。
  3. 根据权利要求1所述的方法，其中，还包括：
    保存所接收到的所述预配置上行资源配置；和
    在所述用户设备进入RRC空闲态的情况下，按照所保存的所述预配置上行资源配置，对相关协议层进行预配置上行资源的配置。
  4. 根据权利要求3所述的方法，其中，还包括：
    在所述用户设备进入RRC连接态的情况下，
    删除或保留所述预先配置上行资源配置的相关配置。
  5. 根据权利要求4所述的方法，其中，
    所述删除所述预先配置上行资源配置的相关配置包括下列操作中的至少一个操作：
    删除所保存的所述预配置上行资源配置；
    删除所配置的所述预配置上行资源；和
    停止用于确定预配置上行资源有效性的定时器，
    所述保留所述预先配置上行资源配置的相关配置包括下列操作中的至少一个操作：
    应用接收到的所述RRC消息中包含的所述预配置上行资源配置；和
    对正在执行的所述定时器进行重启。
  6. 根据权利要求3所述的方法，其中，
    所述应用接收到的所述RRC消息中包含的所述预配置上行资源配置包 括：
    用接收到的所述RRC消息中包含的所述预配置上行资源配置来替换所保存的所述预配置上行资源配置。
  7. 根据权利要求3所述的方法，其中，还包括：
    所述用户设备在所配置的所述预配置上行资源上发送上行数据；和
    在所述用户设备的底层未接收到来自基站的任何响应信息的情况下，向所述用户设备的上层发送用于告知所述底层未接收到所述预配置资源的上行传输的响应的指示信息。
  8. 根据权利要求7所述的方法，其中，
    所述底层包括MAC层和/或物理层，
    所述上层包括RRC层。
  9. 根据权利要求7所述的方法，其中，还包括：
    所述上层执行回退操作，即：通过触发随机接入过程使用EDT来发送上行数据、或使用非EDT的传统RRC连接建立/恢复过程以进入RRC连接态来发送上行数据，
    该回退操作包括下列操作中的至少一个操作：
    启动或重启T300定时器；
    重建数据无线承载DRB和/或信令无线承载SRB对应的无线链路控制RLC层；
    重新数据无线承载DRB和/或信令无线承载SRB对应的包数据汇聚协议PDCP层；
    删除为了在所述预配置上行资源上执行上行数据发送所派生的安全密钥；
    挂起除了SRB0以外的所有SRB和DRB；和
    配置下层挂起完整性保护和加密功能。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的方法。
PCT/CN2019/114314 2018-11-01 2019-10-30 用户设备和用户设备执行的方法 Ceased WO2020088512A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
MX2021004823A MX2021004823A (es) 2018-11-01 2019-10-30 Equipo de usuario y metodo ejecutado por el equipo de usuario.
US17/288,882 US12143984B2 (en) 2018-11-01 2019-10-30 User equipment and method executed by user equipment
EP19877770.8A EP3876629A4 (en) 2018-11-01 2019-10-30 USER DEVICE AND PROCEDURE PERFORMED BY THE USER DEVICE
AU2019373784A AU2019373784B2 (en) 2018-11-01 2019-10-30 User equipment and method executed by user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811297892.0A CN111132328B (zh) 2018-11-01 2018-11-01 用户设备和用户设备执行的方法
CN201811297892.0 2018-11-01

Publications (1)

Publication Number Publication Date
WO2020088512A1 true WO2020088512A1 (zh) 2020-05-07

Family

ID=70461834

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/114314 Ceased WO2020088512A1 (zh) 2018-11-01 2019-10-30 用户设备和用户设备执行的方法

Country Status (6)

Country Link
US (1) US12143984B2 (zh)
EP (1) EP3876629A4 (zh)
CN (1) CN111132328B (zh)
AU (1) AU2019373784B2 (zh)
MX (1) MX2021004823A (zh)
WO (1) WO2020088512A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022021143A1 (en) 2020-07-29 2022-02-03 Qualcomm Incorporated Release of preconfigured uplink resource for small data transmission

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112913296A (zh) * 2018-11-02 2021-06-04 华为技术有限公司 一种资源配置方法及装置
ES3038065T3 (en) * 2019-01-11 2025-10-09 Zte Corp Preconfiguring dedicated resource information in idle mode
US11582829B2 (en) * 2019-11-01 2023-02-14 Qualcomm Incorporated Preconfigured uplink resource release counter management
WO2022000488A1 (en) * 2020-07-03 2022-01-06 Lenovo (Beijing) Limited Methods and apparatuses for access control of a small size and infrequent data transmission
CN113965941B (zh) * 2020-07-20 2025-03-21 维沃移动通信有限公司 信道监听方法、装置及通信设备
CN114071709B (zh) * 2020-07-31 2023-07-25 展讯半导体(南京)有限公司 寻呼载波的确定及寻呼方法、装置、存储介质、终端、基站
CN114071687B (zh) * 2020-07-31 2023-04-07 维沃移动通信有限公司 上行定时提前ta值处理方法、装置及终端
BR112023001311A2 (pt) 2020-08-06 2023-02-14 Qualcomm Inc Técnicas de multi-feixe para transferência de dados pequenos através dos recursos de uplink préconfigurados
KR20220033012A (ko) * 2020-09-08 2022-03-15 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 rrc 연결 재개 절차를 위한 타이머 제어를 위한 방법 및 장치
CN114389744A (zh) * 2020-10-16 2022-04-22 夏普株式会社 由用户设备执行的方法以及用户设备
EP4338531A4 (en) * 2021-05-10 2025-01-22 Lenovo (Beijing) Limited METHOD AND DEVICE FOR HANDLING SMALL DATA TRANSMISSION
US20240357559A1 (en) * 2021-08-20 2024-10-24 Beijing Xiaomi Mobile Software Co., Ltd. Configuration information sending method and apparatus, configuration information obtaining method and apparatus, communication apparatus, and storage medium
CN117377052A (zh) * 2022-07-01 2024-01-09 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置
US20240373360A1 (en) * 2023-05-05 2024-11-07 Qualcomm Incorporated Groupcast configuration deactivation
CN120343575A (zh) * 2024-01-17 2025-07-18 中兴通讯股份有限公司 一种环境物联网的复用方法及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734463A (zh) * 2016-08-12 2018-02-23 电信科学技术研究院 接收多播业务的方法、发送多播业务的方法及装置
WO2018044388A1 (en) * 2016-09-02 2018-03-08 Qualcomm Incorporated Narrowband communication for different device capabilities in unlicensed spectrum

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080285566A1 (en) * 2007-04-27 2008-11-20 Interdigital Technology Corporation Method and apparatus for providing and utilizing radio link control and medium access control packet delivery notification
EP2360866A1 (en) * 2010-02-12 2011-08-24 Panasonic Corporation Component carrier activation and deactivation using resource assignments
CN102238750A (zh) * 2010-04-23 2011-11-09 中兴通讯股份有限公司 无线资源控制连接重建触发方法及装置
JP2014143616A (ja) * 2013-01-24 2014-08-07 Ntt Docomo Inc ユーザ装置、ゲートウェイ装置、無線基地局、移動通信システム及び移動通信方法
US10292148B2 (en) * 2014-11-07 2019-05-14 Panasonic Intellectual Property Corporation Of America Resource allocation for transmissions on unlicensed carriers
CN113938866B (zh) * 2015-04-27 2025-01-07 华为技术有限公司 一种数据传输方法、装置及系统
WO2018084762A1 (en) * 2016-11-04 2018-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Methods, computer program, carrier, computer program product and apparatus for managing small data transmissions from user equipments
CN106658758A (zh) * 2017-02-10 2017-05-10 北京小米移动软件有限公司 状态转换方法、状态保持方法、装置及用户设备
CN108633003B (zh) * 2017-03-16 2021-10-01 华为技术有限公司 一种资源分配方法和装置以及终端设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734463A (zh) * 2016-08-12 2018-02-23 电信科学技术研究院 接收多播业务的方法、发送多播业务的方法及装置
WO2018044388A1 (en) * 2016-09-02 2018-03-08 Qualcomm Incorporated Narrowband communication for different device capabilities in unlicensed spectrum

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP PROTOCOL DOCUMENT 36.304
3GPP PROTOCOL DOCUMENT 36.321
ERICSSON: "Rel-14 dedicated carrier configuration", 3GPP DRAFT; R2-1700770, 17 February 2017 (2017-02-17), Athens, Greece, pages 1 - 5, XP051223009 *
See also references of EP3876629A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022021143A1 (en) 2020-07-29 2022-02-03 Qualcomm Incorporated Release of preconfigured uplink resource for small data transmission
EP4190075A4 (en) * 2020-07-29 2024-03-20 Qualcomm Incorporated PRE-CONFIGURED UPLINK RESOURCE RELEASE FOR SMALL DATA TRANSMISSION
US12550226B2 (en) 2020-07-29 2026-02-10 Qualcomm Incorporated Release of preconfigured uplink resource for small data transmission

Also Published As

Publication number Publication date
MX2021004823A (es) 2021-06-15
EP3876629A1 (en) 2021-09-08
CN111132328B (zh) 2024-12-27
US20220007392A1 (en) 2022-01-06
AU2019373784A1 (en) 2021-06-03
EP3876629A4 (en) 2022-05-18
CN111132328A (zh) 2020-05-08
AU2019373784B2 (en) 2024-09-26
US12143984B2 (en) 2024-11-12

Similar Documents

Publication Publication Date Title
AU2019373784B2 (en) User equipment and method executed by user equipment
TWI734007B (zh) 基站、使用者設備和相關方法
EP3791623B1 (en) Method and apparatus for handling radio access network notification area (rna) update configuration upon reject
CN111405648B (zh) 用于扩展的不连续接收（drx）的ran过程
JP6685384B2 (ja) 無線通信システムにおけるｓｉアップデート、ｅａｂアップデート及びｐｗｓメッセージを通知するための方法及び装置
CN106576231B (zh) 针对扩展空闲非连续接收的空闲模式增强
US12156134B2 (en) Method executed by user equipment, and user equipment
US20190373578A1 (en) Method for relaying paging and relay user equipment, and paging reception method and remote user equipment
WO2020114483A1 (zh) 用户设备、基站及其方法
CN105409307B (zh) 在非授权频谱上寻呼用户设备
US9294976B2 (en) Method for transceiving a signal to/from a mobile femtocell in a wireless communication system, and apparatus for same
CN109565872B (zh) 针对网络切片和网络共享的小区级隔离
US11051356B2 (en) Soft discontinuous reception (soft DRX)
CN114731727B (zh) 辅小区休眠指示的配置
CN116671188A (zh) 侧链通信的非连续接收
WO2010111820A1 (zh) 一种随机接入方法、演进基站及终端设备
CN117596721A (zh) 用于多播/广播服务相关操作的方法和设备
WO2024199288A1 (zh) 由用户设备执行的方法以及用户设备
WO2024094061A1 (zh) 由用户设备执行的方法以及用户设备
WO2025061038A1 (zh) 由用户设备执行的方法以及用户设备
WO2024199354A1 (zh) 由用户设备执行的方法以及用户设备
WO2025140273A1 (zh) 由用户设备执行的方法以及用户设备
WO2024230778A1 (zh) 由用户设备执行的方法以及用户设备
WO2024140669A1 (zh) 由用户设备执行的方法以及用户设备
WO2025232735A1 (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: 19877770

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

Country of ref document: AU

Date of ref document: 20191030

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019877770

Country of ref document: EP

Effective date: 20210601