WO2017193883A1 - 基站、用户设备和相关方法 - Google Patents
基站、用户设备和相关方法 Download PDFInfo
- Publication number
- WO2017193883A1 WO2017193883A1 PCT/CN2017/083425 CN2017083425W WO2017193883A1 WO 2017193883 A1 WO2017193883 A1 WO 2017193883A1 CN 2017083425 W CN2017083425 W CN 2017083425W WO 2017193883 A1 WO2017193883 A1 WO 2017193883A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- gap configuration
- anchor
- transmission
- configuration
- transmission gap
- Prior art date
Links
Images
Classifications
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
Definitions
- the present disclosure relates to the field of wireless communication technologies, and more particularly, to a method of base station, user equipment, and associated physical channel transmit gap configuration.
- MTC Machine Type Communication
- LTE Long Term Evolution Project
- MTC Machine Type Communication
- MTC is a data communication service that does not require human involvement.
- Large-scale deployment of MTC user equipment can be used in security, tracking, billing, measurement, and consumer electronics.
- Applications include video surveillance, supply chain tracking, smart meters, and remote monitoring.
- MTC requires lower power consumption, supports lower data transmission rates and lower mobility.
- the current LTE system is mainly aimed at human-to-human communication services.
- the key to achieving the scale competitive advantage and application prospect of MTC services lies in the fact that LTE networks support low-cost MTC devices.
- MTC equipment needs to be installed in the basement of the residential building or protected by insulated foil, metal window or thick wall of traditional buildings, compared to conventional equipment terminals (such as mobile phones, tablets, etc.) in LTE networks.
- the air interface will obviously suffer from more severe penetration losses.
- 3GPP decided to study the design and performance evaluation of MTC devices with additional 20dB coverage enhancement. It is worth noting that MTC devices located in poor network coverage areas have the following characteristics: very low data transmission rate, very loose latency requirements and limited Mobility.
- the LTE network can further optimize some signaling and/or channels to better support the MTC service.
- Non-Patent Document RP-140990 New Work Item.
- the LTE Rel-13 system needs to support the uplink and downlink 1.4MHz RF bandwidth of the MTC user equipment to work in any system bandwidth (for example, 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, 20MHz, etc.).
- the standardization of this work item will be completed by the end of 2015.
- NB-IoT user equipment User Equipment, UE
- UE User Equipment
- the NB-IoT user equipment will support the uplink and downlink 180KHz RF bandwidth, and support three modes of operation: stand-alone mode, protection With operation mode (guard-band) and in-band operation mode (in-band).
- the independent mode of operation is to implement NB-IOT on the existing GSM band, that is, the frequency band working with the existing GERAN system and the potentially deployed scatter band of the IoT.
- the guard band mode of operation is to implement NB-IOT on the guard band of an LTE carrier, that is, to use the band used as the guard band in the LTE band.
- the in-band mode of operation is to implement NB-IOT on the existing LTE band, that is, to utilize the frequency band actually transmitted on the LTE band.
- Different bearer modes may use different physical parameters and processing mechanisms.
- the 3GPP RAN1 working group divides the physical resource block (PRB) or anchor carrier of the NB IoT into an anchor PRB (anchor PRB) or an anchor carrier and a non-anchor PRB or a non-anchor carrier (non -anchor carrier).
- anchor PRB refers to the anchor PRB and the anchor carrier
- non-anchor PRB refers to the non-anchor PRB and the non-anchor carrier.
- NB-PBCH NB-IoT related physical broadcast channel
- NB-PSS primary synchronization signal
- NB-SSS secondary synchronization signal
- SIB system information block
- the unicast transmission data such as the physical downlink control channel (PDCCH), the physical downlink shared channel (PDSCH), and the physical uplink shared channel (PUSCH) related to the NB-Io T can be received or transmitted only from the non-anchor PRB.
- the anchor PRB may also be used by the user equipment to receive or send the NB-IoT-related PDCCH, Data for unicast transmission such as PDSCH and PUSCH.
- the base station may configure a non-anchor PRB for the user equipment by using a radio resource control (RRC) connection setup message, an RRC connection reestablishment message, an RRC reconfiguration message, an RRC connection resume message, or the like.
- RRC radio resource control
- the RAN1 Working Group agreed to configure a transmit gap configuration for the anchor PRB and an additional transmit gap configuration for the other non-anchor PRBs.
- the RAN2 Working Group agreed to indicate whether the non-anchor PRB contains the NB-IoT-related physical broadcast channel (NB-PBCH) and the primary synchronization signal (NB) with 1-bit information.
- NB-PBCH NB-IoT-related physical broadcast channel
- NB-SSS primary synchronization signal
- SIB System Information Block
- the non-anchor PRB may contain a physical broadcast channel (NB-PBCH), a primary synchronization signal (NB-PSS)/secondary synchronization signal (NB-SSS), and/or a system information block (SIB) associated with the NB-IoT.
- NB-PBCH physical broadcast channel
- NB-PSS primary synchronization signal
- NB-SSS secondary synchronization signal
- SIB system information block
- a base station comprising: a transmitting unit that transmits a first transmission gap configuration for an anchor carrier, and transmits a second transmission gap configuration for a non-anchor carrier;
- the two transmit gap configuration uses any of the following three terms: the first transmit gap configuration, a transmit gap configuration for a non-anchor carrier, or no transmit gap.
- the first transmit gap configuration is configured by a system information block SIB; the second transmit gap configuration is configured by user equipment specific radio resource control RRC signaling.
- a method in a base station comprising: transmitting a first transmission gap configuration for an anchor carrier; transmitting a second transmission gap configuration for a non-anchor carrier; wherein the second The transmit gap configuration uses any of the following three terms: the first transmit gap configuration, a transmit gap configuration for a non-anchor carrier, or no transmit gap.
- the first transmit gap configuration is configured by a system information block SIB; the second transmit gap configuration is configured by user equipment specific radio resource control RRC signaling.
- a user equipment comprising: a receiving unit, receiving a first transmission gap configuration for an anchor carrier, and receiving a second transmission gap configuration for a non-anchor carrier;
- the second transmit gap configuration uses any of the following three terms: the first transmit gap configuration, a transmit gap configuration for a non-anchor carrier, or no transmit gap.
- the first transmit gap configuration is configured by a system information block SIB; the second transmit gap configuration is configured by user equipment specific radio resource control RRC signaling.
- a method in a user equipment comprising: receiving a first transmission gap configuration for an anchor carrier; receiving a second transmission gap configuration for a non-anchor carrier;
- the two transmit gap configuration uses any of the following three terms: the first transmit gap configuration, a transmit gap configuration for a non-anchor carrier, or no transmit gap.
- the first transmit gap configuration is configured by a system information block SIB; the second transmit gap configuration is configured by user equipment specific radio resource control RRC signaling.
- FIG. 1 shows a block diagram of a base station in accordance with an embodiment of the present disclosure.
- FIG. 2 shows a flow diagram of a method in a base station in accordance with an embodiment of the disclosure.
- FIG. 3 shows a block diagram of a user equipment in accordance with an embodiment of the present disclosure.
- FIG. 4 shows a flow diagram of a method in a user equipment in accordance with an embodiment of the disclosure.
- the following uses the LTE mobile communication system and its subsequent evolved version as an example application environment, Taking a base station and a user equipment supporting NB-IOT as an example, various embodiments according to the present disclosure are specifically described. However, it should be noted that the present disclosure is not limited to the following embodiments, but is applicable to more other wireless communication systems, such as future 5G cellular communication systems. Moreover, it can be applied to other base stations and user equipment, such as base stations and user equipments supporting eMTC, MMTC, and the like.
- FIG. 1 shows a block diagram of a base station 100 in accordance with an embodiment of the present disclosure.
- the base station 100 includes a transmitting unit 120.
- Base station 100 can also include an optional configuration unit 110.
- base station 100 may also include other functional units necessary to perform its functions, such as various processors, memories, radio frequency signal processing units, baseband signal processing units, and other physical downlink channel transmission processing units, to name a few.
- processors such as various processors, memories, radio frequency signal processing units, baseband signal processing units, and other physical downlink channel transmission processing units, to name a few.
- radio frequency signal processing units such as various processors, memories, radio frequency signal processing units, baseband signal processing units, and other physical downlink channel transmission processing units
- the transmitting unit 120 transmits a first transmission gap configuration for the anchor carrier and transmits a second transmission gap configuration for the non-anchor carrier.
- the second transmission gap configuration uses any one of the following three terms: the first transmission gap configuration, a transmission gap configuration for a non-anchor carrier, or no transmission gap.
- the first transmit gap configuration is configured by a system information block SIB; the second transmit gap configuration is configured by user equipment specific radio resource control RRC signaling.
- configuration unit 110 configures a first gap configuration for the anchor carrier and selectively configures a second gap configuration for the non-anchor carrier.
- the sending unit 120 sends a non-anchor carrier and an indicator, the indicator indicating whether the non-anchor carrier contains a physical broadcast channel NB-PBCH related to the narrowband Internet of Things NB-IoT, a primary synchronization signal NB-PSS, and a secondary synchronization Signal NB-SSS and/or system information block SIB.
- NB-PBCH physical broadcast channel
- NB-PSS primary synchronization signal
- NB-SSS secondary synchronization Signal
- SIB system information block SIB
- the transmitting unit 120 transmits the non-anchor carrier using the first gap configuration.
- the transmitting unit 120 adopts The second gap is configured to transmit the non-anchor carrier. If the configuration unit 110 does not configure the second gap configuration, the sending unit 120 uses the first gap configuration to send the non-anchor carrier. wave.
- the configuration unit 110 configures a transmission gap of the NB-IoT physical channel.
- the NB-IoT physical channel of the present invention includes an NB-IoT physical downlink channel (for example, NB-IoT physical downlink control channel: NB-PDCCH, NB-IoT physical downlink shared channel: NB-PDSCH) and/or NB-IoT Physical uplink channel (eg, NB-IoT physical uplink shared channel: NB-PUSCH, NB-IoT physical uplink control channel: NB-PUCCH).
- NB-IoT physical downlink channel for example, NB-IoT physical downlink control channel: NB-PDCCH, NB-IoT physical downlink shared channel: NB-PDSCH
- NB-IoT Physical uplink channel eg, NB-IoT physical uplink shared channel: NB-PUSCH, NB-IoT physical uplink control channel: NB-PUCCH.
- the PRB of NB-IoT can be divided into anchor PRB and non-anchor PRB.
- the anchor PRB contains NB-PBCH, NB-PSS/NB-SSS and/or SIB associated with NB-IoT.
- the NB-IoT UE can access the NB-IoT system through the anchor PRB. Once the UE accesses the system and enters the RRC link state, the base station can configure the UE to the PRBs of other NB-IoTs through high layer signaling.
- the NB-IoT PRB accessing the NB-IoT system is an anchor PRB, and the other NB-IoT PRBs are non-anchor PRBs, and the UE performs only unicast transmission and reception on the non-anchor PRB.
- the repeated transmission technology is mainly used.
- TDM Time Division Multiplexing
- the UE with good channel state will get the scheduling opportunity, and the UE that needs the large coverage enhancement will send the sub-spatial.
- the frame is regarded as an invalid subframe, that is, when the base station transmits a channel to a UE that requires large coverage enhancement, and when a large coverage enhanced UE reception channel is required, the subframe within the transmission gap is skipped.
- the configuration unit 110 may separately configure a transmission gap for the anchor PRB and other non-anchor PRBs, that is, there may be two transmission gap configurations.
- One transmit gap configuration is used for the anchor PRB and the other transmit gap configuration is used for the other non-anchor PRBs.
- the transmit gap configuration for non-anchor PRBs is optional.
- the NB-IoT base station can configure the UE to the PRBs containing NB-PBCH, NB-PSS/NB-SSS and/or SIB related to NB-IoT, these PRBs.
- the UE is a non-anchor PRB, but for some in the NB-IoT system
- it may be an anchor PRB, that is, some UEs are accessed through the PRB to access the NB-IoT system.
- the base station 100 can indicate to the UE whether the configured non-anchor PRB contains NB-PBCH, NB-PSS/NB-SSS and/or SIB associated with the NB-IoT with 1-bit information (ie, an indicator).
- the 1-bit information may be indicated by a field "anchorCarrier" in UE-specific RRC signaling.
- anchorCarrier When the anchorCarrier is set to "true”, it means that the configured non-anchor PRB contains NB-PBCH, NB-PSS/NB-SSS and/or SIB related to NB-IoT; when anchorCarrier is set to "false” , indicating that the configured non-anchor PRB does not contain NB-PBCH, NB-PSS/NB-SSS, and/or SIB related to NB-IoT.
- the transmission gap configuration of the anchor PRB is used for The transmission of the non-anchor PRB.
- the sending unit 120 uses the transmission gap configuration of the non-anchor PRB for the transmission of the non-anchor PRB; if the configuration unit 110 does not configure the transmission gap configuration of the non-anchor PRB, the sending unit 120 adopts the transmission gap configuration of the anchor PRB. Used for the transmission of non-anchor PRBs.
- the sending unit 120 uses the transmission gap configuration of the non-anchor PRB for the transmission of the non-anchor PRB; if the configuration unit 110 does not configure the transmission gap configuration of the non-anchor PRB, the non-anchor PRB is not sent. gap.
- the configured non-anchor PRB contains NB-PBCH, NB-PSS/NB-SSS and/or SIB related to NB-IoT, ie when the anchorCarrier is set to "true"
- the sending unit 120 uses the transmission gap configuration of the non-anchor PRB for the transmission of the non-anchor PRB; if the configuration unit 110 does not configure the transmission gap configuration of the non-anchor PRB, the transmitting unit 120 adopts the anchor PRB.
- the transmit gap configuration is used for the transmission of non-anchor PRBs.
- the configuration unit 110 When the configured non-anchor PRB does not contain the NB-PBCH, NB-PSS/NB-SSS, and/or SIB associated with the NB-IoT, that is, when the anchorCarrier is set to "false", if the configuration unit 110 is configured with a non-anchor PRB
- the transmission gap configuration is performed by the sending unit 120 using the transmission gap of the non-anchor PRB for the transmission of the non-anchor PRB; if the configuration unit 110 is not configured with the transmission gap configuration of the non-anchor PRB, the non-anchor PRB is not There is a transmission gap.
- a domain may be specifically defined in the UE-specific RRC signaling, by which the transmission gap configuration employed by the configured non-anchor PRB is directly indicated.
- a 1-bit field is defined. When the field is "1" (or “true"), the transmitting unit 120 uses the transmission gap configuration of the anchor PRB for the transmission of the non-anchor PRB; when the field is "0" ( Or “false"), the transmitting unit 120 uses the transmission gap configuration of the non-anchor PRB for the transmission of the non-anchor PRB.
- it may be an anchor PRB, a non-anchor PRB containing NB-PBCH associated with NB-IoT, NB-PSS/NB-SSS and/or SIB, NB-PBCH not associated with NB-IoT, NB-
- the non-anchor PRBs of the PSS/NB-SSS and/or the SIB configure the first, second, and third gap configurations, respectively.
- the transmitting unit 120 employs the first gap configuration for transmission of the anchor PRB and the second gap parameter for transmission of the non-anchor PRB. If the domain anchorCarrier is set to "false", the transmitting unit 120 uses the first gap parameter for the transmission of the anchor PRB and the third gap parameter for the transmission of the non-anchor PRB.
- the configuration unit 110 does not have a gap configuration configured, there is no transmission gap on both the anchor PRB and the non-anchor PRB (if the non-anchor PRB is present).
- the transmit gap configuration information for the anchor PRB and the non-anchor PRB is configured by the SIB.
- the transmit gap configuration information of the anchor PRB is configured by the SIB, and the transmit gap configuration information of the non-anchor PRB is configured by UE-specific RRC signaling.
- the transmit gap configuration information for the anchor PRB and the non-anchor PRB is configured by UE-specific RRC signaling.
- the transmit gap configuration information of the anchor PRB and the non-anchor PRB is configured by MAC (Medium Access Control) signaling.
- MAC Medium Access Control
- the radio resource control signaling may refer to whether the non-anchor carrier contains NB-PBCH, NB-PSS, NB-SSS, and/or SIB associated with the NB-IoT.
- configuration unit 110 can also configure the gap configuration in one of the following ways:
- the configuration unit 110 can configure one gap configuration A, and the gap configuration A includes two gap configurations (or parameters): the first gap configuration (or parameter) is used for the anchor PRB, and the second gap configuration (or parameter) is used. Non-anchor PRB. Wherein, the gap configuration A is optional.
- gap configuration A is not configured, there is no transmission gap on both the anchor PRB and the non-anchor PRB (if the non-anchor PRB is present).
- gap configuration A is configured, and if the domain anchorCarrier is set to "true", then the transmitting unit 120 employs the first gap configuration (or parameter) for the transmission of the non-anchor PRB.
- gap configuration A is configured, and if the domain anchorCarrier is set to "false", at this time, if a second gap configuration (or parameter) appears in the gap configuration A, the transmitting unit 120 adopts the second gap configuration (or parameter) ) for the transmission of the non-anchor PRB; if the second gap configuration (or parameter) does not appear in the gap configuration A, there is no transmission gap on the non-anchor PRB.
- the domain anchorCarrier indicates whether the configured non-anchor PRB contains NB-PBCH, NB-PSS/NB-SSS, and/or SIB related to the narrowband Internet of Things.
- the gap configuration and/or gap parameters may be configured by SIB and/or RRC and/or MAC (Medium Access Control) signaling.
- the configuration unit 110 can configure one gap configuration A, and the gap configuration A includes two gap configurations (or parameters): the first gap configuration (or parameter) is used for the anchor PRB, and the second gap configuration (or parameter) is used. Non-anchor PRB. Wherein, the gap configuration A is optional.
- gap configuration A is not configured, there is no transmission gap on both the anchor PRB and the non-anchor PRB (if the non-anchor PRB is present).
- gap configuration A is configured, and if the domain anchorCarrier is set to "true", at this time, if a second gap configuration (or parameter) appears in the gap configuration, the transmitting unit 120 adopts the second gap configuration (or parameter). For the transmission of the non-anchor PRB; if the second gap configuration (or parameter) does not appear in the gap configuration A, the transmitting unit 120 uses the first gap configuration (or parameter) for the transmission of the non-anchor PRB.
- gap configuration A is configured, and if the domain anchorCarrier is set to "false", at this time, if a second gap configuration (or parameter) occurs in the gap configuration, the transmitting unit 120 adopts the second gap configuration (or parameter).
- the transmitting unit 120 adopts the second gap configuration (or parameter). For non-anchor PRB transmission; if there is no second gap configuration (or parameter) in the gap configuration, there is no transmission gap on the non-anchor PRB.
- the domain anchorCarrier indicates whether the configured non-anchor PRB contains NB-PBCH, NB-PSS/NB-SSS, and/or SIB related to the narrowband Internet of Things.
- the gap configuration and/or gap parameters may be by SIB and/or RRC and/or MAC (media Body access control: Medium Access Control) signaling.
- the configuration unit 110 can configure one gap configuration A, and the gap configuration A includes two gap configurations (or parameters): the first gap configuration (or parameter) is used for the anchor PRB, and the second gap configuration (or parameter) is used. Non-anchor PRB. Wherein, the gap configuration A is optional.
- gap configuration A is not configured, there is no transmission gap on both the anchor PRB and the non-anchor PRB (if the non-anchor PRB is present).
- gap configuration A is configured, and if the domain anchorCarrier is set to "true", then the transmitting unit 120 employs the first gap configuration (or parameter) for the transmission of the non-anchor PRB.
- gap configuration A is configured, and if the domain anchorCarrier is set to "false", at this time, if a second gap configuration (or parameter) appears in the gap configuration A, the transmitting unit 120 adopts the second gap configuration (or parameter) For the transmission of the non-anchor PRB; if the second gap configuration (or parameter) does not appear in the gap configuration A, the transmitting unit 120 uses the first gap configuration (or parameter) for the transmission of the non-anchor PRB.
- the domain anchorCarrier indicates whether the configured non-anchor PRB contains NB-PBCH, NB-PSS/NB-SSS, and/or SIB related to the narrowband Internet of Things.
- the gap configuration and/or gap parameters may be configured by SIB and/or RRC and/or MAC (Medium Access Control) signaling.
- the configuration unit 110 can configure one gap configuration A, and the gap configuration A includes two gap configurations (or parameters): the first gap configuration (or parameter) is used for the anchor PRB, and the second gap configuration (or parameter) is used. Non-anchor PRB. Wherein, the gap configuration A is optional.
- gap configuration A is not configured, there is no transmission gap on both the anchor PRB and the non-anchor PRB (if the non-anchor PRB is present).
- a domain is specifically configured in the UE-specific RRC signaling, and the domain directly indicates the transmission gap configuration (or parameter) adopted by the configured non-anchor PRB.
- a 1-bit field is defined. When the field is "1" (or “true"), the transmitting unit 120 uses the first gap configuration (or parameter) for the transmission of the non-anchor PRB; when the field is When "0" (or “false"), the transmitting unit 120 uses the first gap configuration (or parameter) for the transmission of the non-anchor PRB.
- the gap configuration and/or gap parameters may be by SIB and/or RRC and/or MAC (media Body access control: Medium Access Control) signaling.
- the configuration unit 110 can configure one gap configuration A, and the gap configuration A includes three gap configurations (or parameters): the first gap configuration (or parameter) is used for the anchor PRB, and the second gap configuration (or parameter) is used.
- the non-anchor PRB contains NB-PBCH, NB-PSS/NB-SSS and/or SIB related to NB-IoT, and the third gap configuration (or parameter) is used for non-anchor PRB, and non-anchor
- the anchor PRB does not contain NB-PBCH, NB-PSS/NB-SSS and/or SIB associated with NB-IoT.
- the gap configuration A is optional.
- gap configuration A is not configured, there is no transmission gap on both the anchor PRB and the non-anchor PRB (if the non-anchor PRB is present).
- gap configuration A is configured, and if the domain anchorCarrier is set to "true", then the transmitting unit 120 uses the first gap configuration (or parameter) for the transmission of the anchor PRB, with the second gap configuration (or parameter) The transmission of the non-anchor PRB.
- gap configuration A is configured, and if the domain anchorCarrier is set to "false", then the transmitting unit 120 employs the first gap configuration (or parameter) for the transmission of the anchor PRB, with the third gap configuration (or parameter) The transmission of the non-anchor PRB.
- the domain anchorCarrier indicates whether the configured non-anchor PRB contains NB-PBCH, NB-PSS/NB-SSS, and/or SIB related to the narrowband Internet of Things.
- the gap configuration and/or gap parameters may be configured by SIB and/or RRC and/or MAC (Medium Access Control) signaling.
- method 200 includes the following steps.
- step S210 a first transmission gap configuration for the anchor carrier is transmitted.
- a second transmit gap configuration for the non-anchor carrier is transmitted.
- the second transmission gap configuration uses any one of the following three terms: the first transmission gap configuration, a transmission gap configuration for a non-anchor carrier, or no transmission gap.
- the method 200 further includes configuring a first gap configuration for the anchor carrier and selectively configuring a second gap configuration for the non-anchor carrier.
- the method 200 further includes transmitting a non-anchor carrier and an indicator indicating whether the non-anchor carrier contains a physical broadcast channel associated with the narrowband Internet of Things NB-IoT NB-PBCH, primary synchronization signal NB-PSS, secondary synchronization signal NB-SSS and/or system information block SIB.
- the first gap configuration is used to transmit the non-anchor carrier.
- the indicator indicates that the non-anchor carrier does not contain the NB-PBCH, NB-PSS, NB-SSS, and/or SIB associated with the NB-IoT: if the second gap configuration is configured, the second gap configuration is used to send Non-anchor carrier, if the second gap configuration is not configured, the first gap configuration is used to transmit the non-anchor carrier.
- the indicator includes a domain anchorCarrier.
- the first gap configuration and the second gap configuration are carried by system information blocks.
- the first gap configuration and the second gap configuration are carried by user equipment specific radio resource control signaling.
- the first gap configuration is carried by the system information block and the second gap configuration is carried by the user equipment specific radio resource control signaling.
- radio resource control signaling refers to whether the non-anchor carrier contains NB-PBCH, NB-PSS, NB-SSS, and/or SIB associated with NB-IoT.
- FIG. 3 shows a block diagram of a user equipment UE 300 in accordance with an embodiment of the present disclosure.
- the UE 300 includes a receiving unit 320.
- the UE 300 may also include an optional extraction unit 310.
- the UE 300 may also include other functional units necessary to implement its functions, such as various processors, memories, radio frequency signal processing units, baseband signal processing units, and other physical uplink channel transmission processing units, to name a few.
- a detailed description of these well-known elements has been omitted for the sake of brevity.
- the receiving unit 320 receives a first transmit gap configuration for the anchor carrier and receives a second transmit gap configuration for the non-anchor carrier.
- the second transmission gap configuration uses any one of the following three terms: the first transmission gap configuration, a transmission gap configuration for a non-anchor carrier, or no transmission gap.
- the extraction unit 310 extracts a first gap configuration for the anchor carrier and extracts a second gap configuration if a second gap configuration for the non-anchor carrier is available.
- receiving unit 320 receives an indicator and a non-anchor carrier, the indicator indicating non Whether the anchor carrier contains a physical broadcast channel NB-PBCH, a primary synchronization signal NB-PSS, a secondary synchronization signal NB-SSS, and/or a system information block SIB associated with the narrowband Internet of Things NB-IoT.
- the indicator indicates non Whether the anchor carrier contains a physical broadcast channel NB-PBCH, a primary synchronization signal NB-PSS, a secondary synchronization signal NB-SSS, and/or a system information block SIB associated with the narrowband Internet of Things NB-IoT.
- the receiving unit 320 employs the first gap configuration to receive the non-anchor carrier.
- the receiving unit 320 When the indicator indicates that the non-anchor carrier does not contain the NB-PBCH, NB-PSS, NB-SSS, and/or SIB associated with the NB-IoT: if the extracting unit 310 extracts the second gap configuration, the receiving unit 320 adopts The second gap is configured to receive the non-anchor carrier, and if the extracting unit 310 does not extract the second gap configuration, the receiving unit 320 employs the first gap configuration to receive the non-anchor carrier.
- the indicator includes a domain anchorCarrier.
- the first gap configuration and the second gap configuration are carried by system information blocks.
- the first gap configuration and the second gap configuration are carried by user equipment specific radio resource control signaling.
- the first gap configuration is carried by the system information block and the second gap configuration is carried by the user equipment specific radio resource control signaling.
- radio resource control signaling refers to whether the non-anchor carrier contains NB-PBCH, NB-PSS, NB-SSS, and/or SIB associated with NB-IoT.
- FIG. 4 shows a flow diagram of a method 400 performed by a user equipment UE in accordance with an embodiment of the disclosure. As shown, method 400 includes the following steps.
- a first transmit gap configuration for the anchor carrier is received.
- a second transmit gap configuration for the non-anchor carrier is received.
- the second transmission gap configuration uses any one of the following three terms: the first transmission gap configuration, a transmission gap configuration for a non-anchor carrier, or no transmission gap.
- the method 400 further includes extracting a first gap configuration for the anchor carrier and extracting the second gap configuration if a second gap configuration for the non-anchor carrier is available.
- the method 400 further includes: receiving an indicator and a non-anchor carrier, the indicator indicating whether the non-anchor carrier includes a physical broadcast channel NB-PBCH associated with the narrowband Internet of Things NB-IoT, a primary synchronization signal NB-PSS, Secondary synchronization signal NB-SSS and/or system information block SIB.
- the first gap configuration is used to receive the non-anchor carrier.
- the indicator indicates that the non-anchor carrier does not contain the NB-PBCH, NB-PSS, NB-SSS, and/or SIB associated with the NB-IoT: if the second gap configuration is extracted, the second gap configuration is used to receive The non-anchor carrier, if the second gap configuration is not extracted, the first gap configuration is employed to receive the non-anchor carrier.
- the indicator includes a domain anchorCarrier.
- the first gap configuration and the second gap configuration are carried by system information blocks.
- the first gap configuration and the second gap configuration are carried by user equipment specific radio resource control signaling.
- the first gap configuration is carried by the system information block and the second gap configuration is carried by the user equipment specific radio resource control signaling.
- radio resource control signaling refers to whether the non-anchor carrier contains NB-PBCH, NB-PSS, NB-SSS, and/or SIB associated with NB-IoT.
- the methods and apparatus of the present disclosure have been described above in connection with the preferred embodiments. Those skilled in the art will appreciate that the methods shown above are merely exemplary. The methods of the present disclosure are not limited to the steps and sequences shown above.
- the network nodes and user equipment shown above may include more modules, for example, may also include modules that may be developed or developed in the future for base stations, or UEs, and the like.
- the various logos shown above are merely exemplary and not limiting, and the disclosure is not limited to the specific cells as examples of such identifications. Many variations and modifications can be made by those skilled in the art in light of the teachings of the illustrated embodiments.
- the above-described embodiments of the present disclosure may be implemented by software, hardware, or a combination of both software and hardware.
- the base station and various components within the user equipment in the above embodiments may be implemented by various devices including, but not limited to, analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, and programmable processing. , Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), Programmable Logic Devices (CPLDs), and more.
- ASICs Application Specific Integrated Circuits
- FPGAs Field Programmable Gate Arrays
- CPLDs Programmable Logic Devices
- base station refers to a mobile having a large transmission power and a relatively large coverage area.
- Communication data and control switching center including resource allocation scheduling, data receiving and sending functions.
- User equipment refers to a user mobile terminal, for example, a terminal device including a mobile phone, a notebook, etc., which can perform wireless communication with a base station or a micro base station.
- embodiments of the present disclosure disclosed herein can be implemented on a computer program product.
- the computer program product is a product having a computer readable medium encoded with computer program logic that, when executed on a computing device, provides related operations to implement The above technical solution of the present disclosure.
- the computer program logic When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present disclosure.
- Such an arrangement of the present disclosure is typically provided as software, code, and/or other data structures, such as one or more, that are arranged or encoded on a computer readable medium such as an optical medium (eg, CD-ROM), floppy disk, or hard disk.
- Software or firmware or such a configuration may be installed on the computing device such that one or more processors in the computing device perform the technical solutions described in the embodiments of the present disclosure.
- each functional module or individual feature of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by circuitry, typically one or more integrated circuits.
- Circuitry designed to perform the various functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs) or general purpose integrated circuits, field programmable gate arrays (FPGAs), or others.
- a general purpose processor may be a microprocessor, or the processor may be an existing processor, controller, microcontroller, or state machine.
- the above general purpose processor or each circuit may be configured by a digital circuit or may be configured by a logic circuit.
- the present disclosure may also use integrated circuits obtained using the advanced technology.
- the program running on the device according to the invention can be controlled by a central processing unit (CPU)
- CPU central processing unit
- the program or information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory system.
- a program for realizing the functions of the embodiments of the present invention can be recorded on a computer readable recording medium.
- the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
- the so-called "computer system” herein 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 of a short-term dynamic storage program, or any other recording medium readable by a computer.
- circuitry e.g., monolithic or multi-chip integrated circuits.
- Circuitry designed to perform the functions described in this specification can 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.
- 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. In the case of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology, the present invention can also be implemented using these new integrated circuit technologies.
- the present invention is not limited to the above embodiment. Although various examples of the embodiments have been described, the invention is not limited thereto.
- Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other home appliances.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
- Transmitters (AREA)
Abstract
Description
Claims (8)
- 一种基站,包括:发送单元,发送用于锚载波的第一发送间隙配置,并且发送用于非锚载波的第二发送间隙配置;其中,所述第二发送间隙配置使用以下三项中的任一项:所述第一发送间隙配置、用于非锚载波的发送间隙配置、或者没有发送间隙。
- 根据权利要求1所述的基站,其中,所述第一发送间隙配置是由系统信息块SIB配置;所述第二发送间隙配置是由用户设备特定的无线资源控制RRC信令配置。
- 一种基站中的方法,包括:发送用于锚载波的第一发送间隙配置;发送用于非锚载波的第二发送间隙配置;其中,所述第二发送间隙配置使用以下三项中的任一项:所述第一发送间隙配置、用于非锚载波的发送间隙配置、或者没有发送间隙。
- 根据权利要求3所述的方法,其中,所述第一发送间隙配置是由系统信息块SIB配置;所述第二发送间隙配置是由用户设备特定的无线资源控制RRC信令配置。
- 一种用户设备,包括:接收单元,接收用于锚载波的第一发送间隙配置,并且接收用于非锚载波的第二发送间隙配置;其中,所述第二发送间隙配置使用以下三项中的任一项:所述第一发送间隙配置、用于非锚载波的发送间隙配置、或者没有发送间隙。
- 根据权利要求5所述的用户设备,其中,所述第一发送间隙配置是由系统信息块SIB配置;所述第二发送间隙配置是由用户设备特定的无线资源控制RRC信令配置。
- 一种用户设备中的方法,包括:接收用于锚载波的第一发送间隙配置;接收用于非锚载波的第二发送间隙配置;其中,所述第二发送间隙配置使用以下三项中的任一项:所述第一发送间隙配置、用于非锚载波的发送间隙配置、或者没有发送间隙。
- 根据权利要求7所述的方法,其中,所述第一发送间隙配置是由系统信息块SIB配置;所述第二发送间隙配置是由用户设备特定的无线资源控制RRC信令配置。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/099,674 US20190159179A1 (en) | 2016-05-11 | 2017-05-08 | Base station, user equipment, and related method |
EP17795501.0A EP3457779A4 (en) | 2016-05-11 | 2017-05-08 | BASE STATION, USER DEVICE AND RELATED PROCEDURE |
IL262841A IL262841A (en) | 2016-05-11 | 2018-11-06 | Base station, user equipment, and associated method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610308482.6A CN107371240B (zh) | 2016-05-11 | 2016-05-11 | 基站、用户设备和相关方法 |
CN201610308482.6 | 2016-05-11 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017193883A1 true WO2017193883A1 (zh) | 2017-11-16 |
Family
ID=60266312
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/083425 WO2017193883A1 (zh) | 2016-05-11 | 2017-05-08 | 基站、用户设备和相关方法 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20190159179A1 (zh) |
EP (1) | EP3457779A4 (zh) |
CN (1) | CN107371240B (zh) |
BR (1) | BR112018072778A8 (zh) |
IL (1) | IL262841A (zh) |
WO (1) | WO2017193883A1 (zh) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3584966B1 (en) * | 2017-02-17 | 2024-02-07 | LG Electronics Inc. | Signal transmission/reception method between terminal and base station in wireless communication system supporting narrowband internet of things, and device supporting same |
WO2018231918A1 (en) * | 2017-06-13 | 2018-12-20 | Intel IP Corporation | Paging and essential system information block (sib) transmission in the unlicensed internet of things (u-iot) system |
EP3637818B1 (en) * | 2017-08-10 | 2022-05-04 | Huawei Technologies Co., Ltd. | Signal sending and receiving method and device |
EP3735756A4 (en) * | 2018-01-03 | 2021-07-07 | Lenovo (Beijing) Limited | NON-ANCHORING CARRIER FREQUENCY OFFSET INDICATION |
KR102456934B1 (ko) | 2018-02-28 | 2022-10-21 | 삼성전자주식회사 | 무선 통신 시스템에서의 데이터 송수신 방법 및 장치 |
CN112042253B (zh) * | 2018-04-04 | 2022-10-11 | 华为技术有限公司 | 通信方法、装置及计算机可读存储介质 |
WO2019191919A1 (zh) * | 2018-04-04 | 2019-10-10 | 华为技术有限公司 | 时分双工物联网中传输系统信息块类型一的方法和装置 |
US11470649B2 (en) * | 2019-02-22 | 2022-10-11 | Qualcomm Incorporated | Transmission gap configuration for random access messages |
US20220159720A1 (en) * | 2019-05-13 | 2022-05-19 | Nokia Solutions And Networks Oy | Mechanism for transmission for wideband system in unlicensed spectrum |
WO2021051379A1 (en) | 2019-09-20 | 2021-03-25 | Lenovo (Beijing) Limited | Non anchor carrier synchronization signal |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101873646A (zh) * | 2009-04-27 | 2010-10-27 | 大唐移动通信设备有限公司 | 一种多载波聚合系统的测量间隙的配置方法及装置 |
CN102271415A (zh) * | 2010-06-01 | 2011-12-07 | 中兴通讯股份有限公司 | 随机接入过程与载波操作过程冲突的处理方法和系统 |
CN102325334A (zh) * | 2010-05-04 | 2012-01-18 | 宏碁股份有限公司 | 处理量测间隙配置的方法及相关通信装置 |
CN102356592A (zh) * | 2009-03-17 | 2012-02-15 | 高通股份有限公司 | 双小区高速上行链路包接入的设备与方法 |
CN103260242A (zh) * | 2012-02-17 | 2013-08-21 | 华为技术有限公司 | 配置载波的方法及装置 |
-
2016
- 2016-05-11 CN CN201610308482.6A patent/CN107371240B/zh active Active
-
2017
- 2017-05-08 BR BR112018072778A patent/BR112018072778A8/pt not_active Application Discontinuation
- 2017-05-08 WO PCT/CN2017/083425 patent/WO2017193883A1/zh unknown
- 2017-05-08 US US16/099,674 patent/US20190159179A1/en not_active Abandoned
- 2017-05-08 EP EP17795501.0A patent/EP3457779A4/en not_active Withdrawn
-
2018
- 2018-11-06 IL IL262841A patent/IL262841A/en unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102356592A (zh) * | 2009-03-17 | 2012-02-15 | 高通股份有限公司 | 双小区高速上行链路包接入的设备与方法 |
CN101873646A (zh) * | 2009-04-27 | 2010-10-27 | 大唐移动通信设备有限公司 | 一种多载波聚合系统的测量间隙的配置方法及装置 |
CN102325334A (zh) * | 2010-05-04 | 2012-01-18 | 宏碁股份有限公司 | 处理量测间隙配置的方法及相关通信装置 |
CN102271415A (zh) * | 2010-06-01 | 2011-12-07 | 中兴通讯股份有限公司 | 随机接入过程与载波操作过程冲突的处理方法和系统 |
CN103260242A (zh) * | 2012-02-17 | 2013-08-21 | 华为技术有限公司 | 配置载波的方法及装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3457779A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN107371240A (zh) | 2017-11-21 |
EP3457779A1 (en) | 2019-03-20 |
CN107371240B (zh) | 2022-12-06 |
BR112018072778A2 (pt) | 2019-03-12 |
EP3457779A4 (en) | 2019-12-11 |
US20190159179A1 (en) | 2019-05-23 |
IL262841A (en) | 2018-12-31 |
BR112018072778A8 (pt) | 2022-06-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017193883A1 (zh) | 基站、用户设备和相关方法 | |
US11626947B2 (en) | Communication method and communications device | |
JP6507168B2 (ja) | ユーザ機器、基地局、物理下り制御チャネルを受信する方法、および、物理下り制御チャネルを送信する方法 | |
CN105101044B (zh) | 寻呼消息接收/发送方法及其相关设备 | |
WO2017157115A1 (zh) | 物理共享信道参数的确定机制以及基站和用户设备 | |
WO2016107518A1 (zh) | 寻呼消息的接收/发送方法及相关网络节点和用户设备 | |
WO2016107520A1 (zh) | 针对寻呼消息的资源分配方法及网络节点和用户设备 | |
WO2015103952A1 (zh) | 物理信道配置方法以及基站和用户设备 | |
WO2015110035A1 (zh) | 物理上行链路信道配置方法以及基站和用户设备 | |
WO2017114498A1 (zh) | 基于非访问层消息的数据传输方法、基站和用户设备 | |
WO2017118394A1 (zh) | 上行参考信号传输方法和接收方法、以及用户设备和基站 | |
WO2016015609A1 (zh) | 用于配置物理信道起始符号的方法以及基站和用户设备 | |
US10772089B2 (en) | Method and base station for configuring non-anchor physical resource block, and method and user equipment for determining location of non-anchor physical resource block | |
WO2016070765A1 (zh) | 传输随机接入响应方法以及基站和用户设备 | |
WO2017114350A1 (zh) | 窄带物联网物理下行信道的复用方法、基站和用户设备 | |
WO2017118398A1 (zh) | 上行传输子载波带宽指示方法和选择方法、以及基站和用户设备 | |
WO2017076319A1 (zh) | 物理信道的配置方法以及基站和用户设备 | |
WO2017166930A1 (zh) | 配置非锚物理资源块的方法和基站、确定非锚物理资源块位置的方法和用户设备 | |
CN114679770B (zh) | Pdcch的监听方法和设备 | |
WO2017114349A1 (zh) | 解调参考信令的资源配置方法、基站和用户设备 | |
US11363650B2 (en) | Fifth generation (5G) global unique temporary identity (GUTI) reallocation for cellular-internet of things (CIOT) | |
IL261301A (en) | Method, network node and wireless device adapted to insert gaps in retrievable transmission for the Internet of Things (dl nb-iot) | |
WO2017161973A1 (zh) | 数据传输方法、用户设备和基站 | |
WO2018201968A1 (zh) | 用户设备、基站和相关方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112018072778 Country of ref document: BR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17795501 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2017795501 Country of ref document: EP Effective date: 20181211 |
|
ENP | Entry into the national phase |
Ref document number: 112018072778 Country of ref document: BR Kind code of ref document: A2 Effective date: 20181106 |