KR20200085772A - Techniques and devices for carrier management - Google Patents

Abstract

A method, base station (BS), user equipment (UE), device and computer program product for wireless communication are provided. The BS and the UE can communicate using a narrowband Internet of Things (NB-IoT) communication system. However, the frequency, time and/or power associated with the transmission of SIB1-NB on a non-anchor carrier may not be configured for NB-IoT. In some aspects, the BS can determine parameters for transmission in the NB-IoT, such as time domain location parameter, frequency domain location parameter, repetition quantity, power boosting parameter, and the like. In some aspects, the UE may decide to send a connection request message on a different carrier than the random access channel message.

Description

Techniques and devices for carrier management

[0001] This application claims priority to PCT (Patent Cooperation Treaty) patent application number PCT/CN2017/111308 filed on November 16, 2017 under the name "TECHNIQUES AND APPARATUSES FOR CARRIER MANAGEMENT", the above patent application thereby It is expressly incorporated by reference herein.

[0002] Aspects of the present disclosure generally relate to wireless communication, and more particularly to techniques and apparatus for carrier management.

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging and broadcasts. Conventional wireless communication systems can utilize multiple-access technologies that can support communication with multiple users by sharing available system resources (eg, bandwidth, transmit power, etc.). Examples of such multi-access technologies are code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems. , Single-carrier frequency-division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard announced by the Third Generation Partnership Project (3GPP).

[0004] A wireless communication network can include a number of base stations (BSs) that can support communication for a number of user equipments (UEs). The UE can communicate with the BS via the downlink and uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, the BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), 5G BS, 5G Node B, and the like.

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless communication devices to communicate at the city level, country level, regional level and even global level. 5G, which may also be referred to as New Radio (NR), is a set of enhancements to the LTE mobile standard announced by the Third Generation Partnership Project (3GPP). 5G improves spectral efficiency, lowers costs, improves services, uses new spectrum, and uses CP-OFDM (OFDM with cyclic prefix) on the downlink (DL) and uplink (UL) CP-OFDM and/or SC-FDM (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink), as well as beamforming, multiple-input multiple-output (MIMO) antenna It is designed to better support mobile broadband Internet access by supporting technology and carrier aggregation to better integrate with other open standards. However, as the demand for mobile broadband access continues to increase, there is a need for further improvements in LTE and 5G technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards using these technologies.

[0006] BS and UE can communicate using a carrier. For example, in a narrowband Internet of Things (NB-IoT) time division duplex (TDD) operation, a BS and a UE are a group of channels delivered using at least one carrier, such as a broadcast channel, a shared channel, It can communicate using downlink channels, uplink channels, and the like. The first physical resource block (PRB) may include a narrowband primary synchronization signal, a narrowband secondary synchronization signal, and the like. The first PRB may be an anchor carrier for the network. One or more second PRBs may be configured using system information block signaling, radio resource control signaling, etc. as non-anchor carriers for paging, random access procedures and unicast transmissions.

[0007] The SIB1-NB (system information block type 1 narrowband) message can be transmitted on an anchor carrier and multiplexed with a narrowband secondary synchronization signal as in a time division multiplexing communication system. In some cases, SIB1-NB may be transmitted on a non-anchor carrier, such as based at least in part on an indication associated with a master information block, such as the quantity of repetition of SIB1-NB from a set of neighboring cells. When the repetitions exceed the critical quantity, inter-cell interference for SIB1-NB can be reduced. However, the frequency, time, repetition quantity, power, etc. associated with the transmission of SIB1-NB on a non-anchor carrier may not be configured.

[0008] Some aspects described herein can provide a mechanism for carrier management. For example, the BS can determine a frequency domain location parameter, a time domain location parameter, etc. for transmitting a message. Similarly, the UE can identify a plurality of carriers and send a connection request message (eg, Msg3 type message) using at least one of the plurality of carriers. In this case, these at least one carrier is different for the connection request message than for the random access channel message, so that the time delay associated with sending the connection request message is reduced and the possibility of collision between the connection request message and the random access channel message is reduced. Can be reduced. In this way, the BS and the UE can enable messaging using a non-anchor carrier, such as for SIB1-NB messages, connection request messages (eg, msg3 type messages), and the like.

[0009] In aspects of the present disclosure, methods, user equipment, base stations, devices and computer program products are provided.

[0010] In some aspects, the method may include the base station transmitting a master information block message comprising an indicator identifying a frequency domain location parameter or time domain location parameter for the non-anchor carrier or anchor carrier. The method may include the step of the base station transmitting a system information block type 1 (SIB1) message to the user equipment according to the frequency domain location parameter or the time domain location parameter using a non-anchor carrier or an anchor carrier.

[0011] In some aspects, the base station can include a memory and at least one processor coupled to the memory. The memory and the at least one processor can be configured to transmit a master information block message including an indicator identifying a frequency domain location parameter or time domain location parameter for a non-anchor carrier or anchor carrier. The memory and at least one processor may be configured to transmit a system information block type 1 (SIB1) message to user equipment according to a frequency domain location parameter or a time domain location parameter using a non-anchor carrier or anchor carrier.

[0012] In some aspects, the apparatus may include means for transmitting a master information block message including an indicator identifying a frequency domain location parameter or time domain location parameter for a non-anchor carrier or anchor carrier. The apparatus may include means for transmitting a system information block type 1 (SIB1) message to a user equipment according to a frequency domain location parameter or a time domain location parameter, using a non-anchor carrier or an anchor carrier.

[0013] In some aspects, a computer program product can include a non-transitory computer-readable medium storing computer executable code. The code may include a code for transmitting a master information block message including an indicator identifying a frequency domain location parameter or time domain location parameter for a non-anchor carrier or anchor carrier. The code may include a code for transmitting a system information block type 1 (SIB1) message to a user equipment according to a frequency domain location parameter or a time domain location parameter using a non-anchor carrier or anchor carrier.

[0014] In some aspects, a method may include, in a time division duplex network for random access, transmitting, by the user equipment, a random access channel using a first one of the plurality of carriers. The method may include transmitting, by the user equipment, a connection request message using a second carrier different from the first carrier among the plurality of carriers.

[0015] In some aspects, the user equipment can include a memory and at least one processor coupled to the memory. The memory and the at least one processor may be configured to transmit a random access channel using a first one of a plurality of carriers in a time division duplex network for random access. The memory and the at least one processor may be configured to transmit a connection request message using a second carrier different from the first carrier among the plurality of carriers.

[0016] In some aspects, an apparatus may include means for transmitting a random access channel using a first one of a plurality of carriers in a time division duplex network for random access. The apparatus may include means for transmitting a connection request message using a second carrier different from the first carrier among the plurality of carriers.

[0017] In some aspects, a computer program product can include a non-transitory computer-readable medium storing computer executable code. The code may include a code for transmitting a random access channel using a first carrier among a plurality of carriers in a time division duplex network for random access. The code may include a code for transmitting a connection request message using a second carrier different from the first carrier among the plurality of carriers.

[0018] Aspects are generally described herein, with reference to the accompanying specification and drawings, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, which are substantially illustrated by and exemplified by them. Wireless communication devices, access points and processing systems.

[0019] The foregoing has outlined rather broadly the features and technical advantages of the examples according to the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as a basis for modifying or designing other structures to accomplish the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The features of the concepts disclosed herein (both how they are structured and how they operate), together with the associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limitations of the claims.

1 is a diagram illustrating an example of a wireless communication network.
2 is a diagram illustrating an example of a base station that communicates with a user equipment (UE) in a wireless communication network.
3 is a diagram illustrating an example logical architecture of a distributed radio access network (RAN).
4 is a diagram illustrating an example physical architecture of a distributed RAN.
5 is a diagram illustrating an example of carrier management.
6 is a diagram illustrating an example of carrier management.
7 is a diagram illustrating an example of carrier management.
8 is a diagram illustrating an example of carrier management.
9 is a diagram illustrating an example of carrier management.
10 is a flowchart of a wireless communication method.
11 is a conceptual data flow diagram illustrating data flow between different modules/means/components in an exemplary apparatus.
12 is a diagram illustrating an example of a hardware implementation for an apparatus using a processing system.
13 is a flowchart of a wireless communication method.
14 is a conceptual data flow diagram illustrating data flow between different modules/means/components in an example apparatus.
15 is a diagram illustrating an example of a hardware implementation for an apparatus using a processing system.

[0035] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the configurations in which the concepts described herein may be practiced. The detailed description includes specific details for purposes of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0036] Various aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”) It will be illustrated in the accompanying drawings. These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0037] By way of example, an element, or any part of an element, or any combination of elements, can be implemented using a “processing system” that includes one or more processors. Examples of processors are microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, And other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, It will be broadly interpreted to mean applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, and the like.

[0038] Accordingly, in one or more exemplary embodiments, the described functions may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, functions can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. The storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM), or other optical disk storage. Used to store computer-executable code in the form of secondary, magnetic disk storage or other magnetic storage devices, combinations of computer-readable media of the types described above, or instructions or data structures that can be accessed by a computer. Can include any other medium.

[0039] While aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure include other generation-based communication systems, such as 5G technologies, 5G and beyond. It is noted that it can be applied to fields.

[0040] 1 is a diagram illustrating a network 100 in which aspects of the present disclosure may be practiced. The network 100 may be an LTE network or some other wireless network, such as a 5G network. The wireless network 100 may include multiple BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. BS is an entity that communicates with user equipments (UEs), and may also be referred to as a base station, 5G BS, Node B, gNB, 5G NB, access point, transmit receive point (TRP), and the like. Each BS can provide communication coverage for a particular geographic area. In 3GPP, the term “cell” may refer to the coverage area of the BS and/or the BS subsystem serving this coverage area, depending on the context in which the term is used.

[0041] The BS can provide communication coverage for macro cells, pico cells, femto cells and/or other types of cells. The macro cell can cover a relatively large geographic area (eg, several kilometers in radius) and can allow unrestricted access by service subscribed UEs. A pico cell can cover a relatively small geographic area and can allow unrestricted access by service subscribed UEs. A femto cell can cover a relatively small geographic area (eg, home), and is constrained by UEs (eg, UEs within a closed subscriber group (CSG)) that have an association with the femto cell. You can allow access. The BS for a macro cell may be referred to as a macro BS. The BS for the pico cell may be referred to as the pico BS. The BS for a femto cell may be referred to as a femto BS or home BS. In the example shown in FIG. 1, BS 110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c is femto It may be a femto BS for cell 102c. The BS can support one or multiple (eg 3) cells. The terms "eNB", "base station", "5G BS", "gNB", "TRP", "AP", "Node B", "5G NB" and "cell" can be used interchangeably herein. .

[0042] In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move depending on the location of the mobile BS. In some examples, BSs, using any suitable transport network, through various types of backhaul interfaces, such as a direct physical connection, virtual network, etc., one or more other BSs or network nodes in the access network 100 Fields (not shown) and/or interconnected with each other.

[0043] The wireless network 100 may also include relay stations. A relay station is an entity capable of receiving transmission of data from an upstream station (eg, BS or UE) and transmitting transmission of data to a downstream station (eg, UE or BS). The relay station may also be a UE capable of relaying transmissions to other UEs. In the example shown in FIG. 1, the relay station 110d can communicate with the macro BS 110a and the UE 120d to facilitate communication between the macro BS 110a and the UE 120d. The relay station may also be referred to as a relay BS, relay base station, relay, and the like.

[0044] The wireless network 100 can be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, and the like. These different types of BSs in wireless network 100 may have different transmit power levels, different coverage areas and different impact on interference. For example, macro BSs may have a high transmit power level (eg, 5 to 40 watts), while pico BSs, femto BSs and relay BSs may have lower transmit power levels (eg, 0.1 to 2 watts). Can.

[0045] Network controller 130 can be coupled to a set of BSs and can provide coordination and control for these BSs. The network controller 130 can communicate with BSs through a backhaul. BSs can also communicate with each other indirectly or directly, such as through a wireless or wired backhaul. In some aspects, network controller 130 can determine a plurality of carriers to be used for communications. For example, the network controller 130 includes a first carrier for an anchor channel for narrowband Internet of Things (NB-IoT) time division duplex (TDD) communication, and a non-anchor channel for NB-IoT TDD communication. For at least one second carrier. Additionally, the network controller 130 transmits a message for causing a connection request message to be transmitted using a carrier different from the random access channel request message, such as a non-anchor carrier identified in a plurality of carriers. can do.

[0046] The UEs 120 (eg, 120a, 120b, 120c) may be scattered throughout the wireless network 100, and each UE may be stationary or mobile. The UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, or the like. The UE is a cellular phone (eg, a smart phone, such as UEs 120b and/or 120d), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, wireless local loop) station, tablet, camera, gaming device, netbook, smartbook, ultrabook, medical device or equipment, biometric sensors/devices (e.g., UE 120c), wearable devices (smart watches, Smart clothing, smart glasses, smart wristbands, smart jewelry (eg, smart rings, smart bracelets), entertainment devices (eg, music or video devices, or satellite radio), vehicle components or sensors, smart meters/sensors , Industrial manufacturing equipment, global positioning system devices, smart home devices (e.g., smart appliances, smart bulbs, etc., such as UE 120a), or any other suitable device configured to communicate via wireless or wired media. have.

[0047] Some UEs may be considered as machine-type communication (MTC) or evolved or advanced machine-type communication (eMTC) UEs. MTC and eMTC UEs, for example, base stations, other devices (eg, remote devices) or robots, drones, remote devices that can communicate with any other entity, such as sensors, meters, monitors, location tags, etc. It includes. A wireless node may provide connectivity to, or connectivity to, a network (eg, a wide area network, such as the Internet or a cellular network) over a wired or wireless communication link. Some UEs can be considered IoT devices, and/or can be implemented as can be implemented as NB-IoT devices. Some UEs may be considered CPE (Customer Premises Equipment). The UE 120 may be included inside a housing that accommodates the components of the UE 120, such as processor components, memory components, and the like.

[0048] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, and the like. Frequency may also be referred to as a carrier, frequency channel, or the like. Each frequency can support a single RAT in a given geographic area, to avoid interference between wireless networks of different RATs. In some cases, 5G RAT networks can be deployed.

[0049] In some examples, access to the air interface can be scheduled, where a scheduling entity (eg, a base station) allocates resources for communication between some or all devices and equipment within a service area or cell of this scheduling entity. Within this disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, dependent entities utilize the resources allocated by the scheduling entity.

[0050] Base stations are not the only entities that can function as scheduling entities. That is, in some examples, a UE may function as a scheduling entity that schedules resources for one or more dependent entities (eg, one or more other UEs). In this example, the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication. The UE may function as a scheduling entity in a peer-to-peer (P2P) network and/or in a mesh network. In the mesh network example, UEs may optionally communicate directly with each other in addition to communicating with a scheduling entity.

[0051] Thus, in a wireless communication network with cellular access, P2P configuration and mesh configuration with scheduled access to time-frequency resources, the scheduling entity and one or more dependent entities can communicate using the scheduled resources.

[0052] As indicated above, FIG. 1 is provided by way of example only. Other examples are possible and may be different from those described with respect to FIG. 1.

[0053] FIG. 2 shows a block diagram 200 of the design of base station 110 and UE 120, which may be one of the base stations of FIG. 1 and one of the UEs. The base station 110 may have T antennas 234a to 234t, and the UE 120 may have R antennas 252a to 252r, where, generally, T≥1 and R≥1 to be.

[0054] In the base station 110, the transmitting processor 220 receives data for one or more UEs from the data source 212, and is based on the channel quality indicators (CQI) received from the UE to each UE. Selects one or more modulation and coding schemes (MCS) for, processes data (eg, encodes and modulates) for each UE based at least in part on the selected MCS(s) for the UE, and for all UEs Data symbols can be provided. The transmission processor 220 also processes system information and control information (eg, CQI requests, grants, upper layer signaling, etc.) (eg, for semi-static resource partitioning information (SRPI)), Overhead symbols and control symbols can be provided. The transmit processor 220 may also generate reference symbols for reference signals (eg, CRS) and synchronization signals (eg, primary synchronization signal (PSS) and secondary synchronization signal (SSS)). For example, the transmission processor 220 can generate reference symbols associated with a system information block (SIB) message for transmission on a non-anchor carrier. The transmit (TX) multiple-input multiple-output (MIMO) processor 230, if applicable, performs spatial processing (eg, precoding) on data symbols, control symbols, overhead symbols and/or reference symbols. ), and may provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 may process an individual output symbol stream (eg, for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process the output sample stream (eg, convert to analog, amplify, filter, and upconvert) to obtain a downlink signal. The T downlink signals from the modulators 232a through 232t can be transmitted through the T antennas 234a through 234t, respectively. According to various aspects described in more detail below, synchronization signals may be generated using location encoding to convey additional information.

[0055] In UE 120, antennas 252a through 252r may receive downlink signals from base station 110 and/or other base stations, and receive the received signals to demodulators (DEMODs) 254a through 254r, respectively. Can provide. Each demodulator 254 may condition the received signal (eg, filter, amplify, downconvert and digitize) to obtain input samples. Each demodulator 254 may further process input samples (eg, for OFDM, etc.) to obtain received symbols. MIMO detector 256 may acquire received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols, if applicable, and provide the detected symbols. The receive (RX) processor 258 processes (eg, demodulates and decodes) the detected symbols, provides decoded data for the UE 120 to the data sink 260, and provides decoded control information and system information. Controller/processor 280. The channel processor can determine RSRP, RSSI, RSRQ, CQI, and the like.

[0056] On the uplink, at the UE 120, the transmit processor 264 reports data including data from the data source 262 and reports from the controller/processor 280 (eg, RSRP, RSSI, RSRQ, CQI, etc.). Control information). For example, the transmission processor 264 processes data, such as data identifying a plurality of carriers, and transmits a connection request message using one of the plurality of carriers, such as an anchor carrier, a non-anchor carrier, and the like. It can be enabled. The transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 are precoded by TX MIMO processor 266, if applicable, and by modulators 254a-254r (eg, for DFT-s-OFDM, CP-OFDM, etc.) It is further processed and can be transmitted to the base station 110. At base station 110, uplink signals from UE 120 and other UEs are received by antennas 234, processed by demodulators 232, and by MIMO detector 236, if applicable. Detected and further processed by the receiving processor 238, decoded data and control information for the data and control information transmitted by the UE 120 can be obtained. The receiving processor 238 can provide the decoded data to the data sink 239 and the decoded control information to the controller/processor 240. The base station 110 includes a communication unit 244 and may communicate with the network controller 130 through the communication unit 244. The network controller 130 can include a communication unit 294, a controller/processor 290 and a memory 292.

[0057] The controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 are carriers as described in more detail elsewhere herein. One or more techniques associated with management may be performed. For example, the controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 may be, for example, the method 1000 of FIG. 10, FIG. The method 1300 of the 13 and/or other processes described herein may be performed or directed. Memories 242 and 282 may store data and program codes for BS 110 and UE 120, respectively. The scheduler 246 can schedule UEs for data transmission on the downlink and/or uplink.

[0058] As indicated above, Figure 2 is provided by way of example only. Other examples are possible and may be different from those described with respect to FIG. 2.

[0059] 5G may refer to radios configured to operate according to a new air interface (eg, other than an Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interface) or a fixed transport layer (eg, other than an Internet Protocol (IP)). In aspects, 5G may utilize OFDM with CP on the uplink (referred to herein as cyclic prefix OFDM or CP-OFDM) and/or SC-FDM, and may utilize CP-OFDM on the downlink, and And support for half-duplex operation using TDD. In aspects, 5G may utilize, for example, OFDM with CP on the uplink (herein referred to as CP-OFDM) and/or discrete Fourier transform spread orthogonal frequency-division multiplexing (DFT-s-OFDM), It utilizes CP-OFDM on the downlink and may include support for half-duplex operation using TDD. 5G is eMBB (Enhanced Mobile Broadband) service targeting broadband (e.g. 80 MHz (megahertz) or higher), mmW (millimeter wave) targeting high carrier frequencies (e.g. 60 GHz (gigahertz)), not backward compatible It may include a mission-critical service targeting massive reliable MTC (mMTC) and/or ultra reliable low latency communications (URLLC) targeting MTC techniques.

[0060] A single component carrier bandwidth of 100 MHz may be supported. The 5G resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz (kilohertz) over a 0.1 ms duration. Each radio frame may include 50 subframes having a length of 10 ms. Consequently, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (ie, DL or UL) for data transmission, and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL control data as well as DL/UL data.

[0061] Beamforming can be supported, and the beam direction can be dynamically configured. MIMO transmissions with precoding can also be supported. MIMO configurations in DL can support up to 8 transmit antennas, and in the case of multi-layer DL transmissions, up to 8 streams, up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE can be supported. Aggregation of multiple cells can be supported using up to 8 serving cells. Alternatively, 5G can support different air interfaces than OFDM-based interfaces. 5G networks may include entities such as central units or distributed units.

[0062] The RAN may include a central unit (CU) and distributed units (DU). A 5G BS (eg, gNB, 5G Node B, Node B, transmit receive point (TRP), access point (AP)) may correspond to one or multiple BSs. 5G cells may be configured as access cells (ACells) or data only cells (DCells). For example, an RAN (eg, central unit or distributed unit) may configure cells. DCells may be cells that are used for carrier aggregation or dual connectivity but not for initial access, cell selection/reselection or handover. In some aspects, DCells may not transmit synchronization signals. In some aspects, DCells can transmit synchronization signals. 5G BSs may transmit downlink signals indicating the cell type to UEs. Based at least in part on the cell type indication, the UE can communicate with the 5G BS. For example, the UE may determine 5G BSs to consider cell selection, access, handover and/or measurement based at least in part on the indicated cell type.

[0063] 3 illustrates an example logical architecture of distributed RAN 300, in accordance with aspects of the present disclosure. The 5G access node 306 may include an access node controller (ANC) 302. The ANC may be a central unit (CU) of the distributed RAN 300. The backhaul interface to the next generation core network (NG-CN) 304 may be terminated at the ANC. The backhaul interface to neighboring next generation access nodes (NG-ANs) may be terminated at the ANC. The ANC can include one or more TRPs 308 (which may also be referred to as BSs, 5G BSs, Node Bs, 5G NBs, APs, gNB or any other terminology). As described above, TRP can be used interchangeably with "cell".

[0064] The TRPs 308 may be a distributed unit (DU). The TRPs may be connected to one ANC (ANC 302) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS) and service specific AND deployments, the TRP can be connected to more than one ANC. The TRP may include one or more antenna ports. TRPs may be configured to serve traffic to the UE individually (eg, dynamic selection) or jointly (eg, joint transmission).

[0065] The local architecture of RAN 300 can be used to illustrate the fronthaul definition. An architecture can be defined that supports fronthauling solutions across different deployment types. For example, the architecture can be based at least in part on transmission network capabilities (eg, bandwidth, latency, and/or jitter).

[0066] The architecture can share features and/or components with LTE. According to aspects, the next generation AN (NG-AN) 310 may support dual connectivity with 5G. NG-AN can share a common fronthaul for LTE and 5G.

[0067] The architecture may enable collaboration between TRPs 308 and between TRPs 308. For example, collaboration may be pre-set over and/or within TRPs via ANC 302. According to aspects, there may or may not be any inter-RPP interface required.

[0068] According to aspects, dynamic configuration of split logical functions may exist within the architecture of RAN 300. PDCP, RLC, and MAC protocols can be deployed adaptively to ANC or TRP.

[0069] According to various aspects, the BS may include a central unit (CU) (eg, ANC 302) and/or one or more distributed units (eg, one or more TRPs 308).

[0070] As indicated above, FIG. 3 is provided by way of example only. Other examples are possible and may be different from those described with respect to FIG. 3.

[0071] 4 illustrates an example physical architecture of a distributed RAN 400, in accordance with aspects of the present disclosure. A centralized core network unit (C-CU) 402 may host core network functions. The C-CU can be centrally located. In an effort to handle peak capacity, C-CU functionality can be offloaded (eg, with advanced wireless services (AWS)).

[0072] A centralized RAN unit (C-RU) 404 may host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU may have a distributed deployment. The C-RU may be closer to the network edge.

[0073] A distributed unit (DU) 406 may host one or more TRPs. The DU can be located at the edges of the network with radio frequency (RF) functionality.

[0074] As indicated above, FIG. 4 is provided by way of example only. Other examples are possible and may be different from those described with respect to FIG. 4.

[0075] 5 is a diagram illustrating an example 500 for carrier management for transmitting SIB1-NB on a non-anchor carrier in the case of an NB-IoT in-band deployment mode.

[0076] At 510, a base station (eg, BS 110) can determine a frequency domain location for an anchor carrier from a plurality of potential frequency domain locations. For example, the base station can determine a plurality of potential frequency domain locations for the anchor carrier, based at least in part on the stored information.

[0077] At 520, the base station can determine the center frequency for the in-band communication system (eg, LTE communication system).

[0078] At 530, the base station can identify the offset index value for the anchor carrier, relative to the center frequency. In some aspects, the offset index value may be a physical resource block (PRB) index offset (P) for the anchor carrier, relative to the center frequency. The base station can signal an index offset in this MIB to enable the UE (eg, UE 120) to determine the frequency location of the anchor carrier after decoding the master information block (MIB). have. In some aspects, the MIB indicates a frequency location, such as PRB is adjacent to the center frequency and is in a lower frequency range than this center frequency, or PRB is adjacent to the center frequency and is higher than this center frequency It may include a 1-bit indicator indicating that it is in range.

[0079] At 540, the base station selects a different frequency domain location for the non-anchor carrier so that the non-anchor carrier can be in the PRB opposite the anchor carrier for the center frequency position. For example, the base station may determine that the physical resource block index offset for the non-anchor carrier is an inverse of the physical resource block index offset for the anchor carrier. In other words, for the anchor carrier physical resource block index offset (P), the non-anchor carrier physical resource block index offset is -P. In this way, the base station eliminates the need to transmit information to signal the frequency location of the non-anchor carrier for the SIB-NB, thereby reducing the utilization of network resources. The UE determines a frequency domain location parameter that identifies the frequency domain location of the non-anchor carrier based at least in part on the offset index of the anchor carrier, thereby signaling the frequency domain location of the anchor carrier and the frequency domain location of the non-anchor carrier The use of network resources can be reduced compared to requiring separate messages.

[0080] As indicated above, FIG. 5 is provided as an example. Other examples are possible and may be different from those described with respect to FIG. 5.

[0081] 6 is a diagram illustrating an example 600 for carrier management.

[0082] At 610, the base station (eg, BS 110) may decide to provide an anchor carrier and a non-anchor carrier in a common resource block group. For example, in an LTE communication system with a 10 MHz (megahertz) bandwidth, a base station uses a physical resource block (PRB) with an index 9 for an anchor carrier and an index 10 and/or an index 11 for a non-anchor carrier. You can decide to use physical resource blocks. In this case, the physical resource blocks of the anchor carrier and the non-anchor carrier are included in the single resource block group (RGB3) of index 3, where the physical resource blocks (PRB 9) for the non-anchor carrier are 1 and/or This follows the physical resource block (PRB 10 and/or 11) for the anchor carrier, with a physical resource block offset value of 2.

[0083] At 620, similarly, the base station may decide to use physical resource blocks 35 with index 33 and/or index 34 for the non-anchor carrier and physical resource block 35 for the anchor carrier. In this case, the physical resource blocks of the anchor carrier and the non-anchor carrier are included in the single resource block group (RGB 11) of index 11, where the physical resource block (PRB 35) for the non-anchor carrier is -1 and/or Or physical resource blocks (PRB 34 and/or 33) for the anchor carrier, with an offset value of -2. In some aspects, one of the set of four physical resource block offset index values may be signaled to the UE using a 2-bit indicator, and the UE frequency of the non-anchor carrier based at least in part on the signaled offset index value. Can be identified. In this way, the degradation of physical resource block group utilization is reduced, based at least in part on reducing the likelihood of misalignment of resource block groups and carriers for an in-band LTE communication system.

[0084] As indicated above, FIG. 6 is provided as an example. Other examples are possible and may be different from those described with respect to FIG. 6.

[0085] 7 is a diagram illustrating an example 700 for carrier management for SIB1-NB in both anchor carrier and non-anchor carrier.

[0086] At 710, at least one base station (eg, BS 110) may provide a plurality of cells for SIB1-NB transmission. In some aspects, SIB1-NB can be associated with a specific period, such as a 2560 millisecond (ms) period, which particular carrier has a transmission time interval (TTI) length of 80 ms for SIB1-NB transmission. Field and non-anchor carriers. In some aspects, SIB1-NB, when transmitted on an anchor carrier, subframe 0 of alternating radio frames (eg, radio frames 1, 3, 5, etc. or radio frames 2, 4, 6, 8, etc.) It may be transmitted in a specific subframe of a specific radio frame, such as subframe 0). Additionally or alternatively, when transmitted on a non-anchor carrier, the SIB1-NB is subframe 0 and subframe 5 of alternating radio frames (eg, radio frames 1, 3, 5, etc. or radio frames) 2, 4, 6, 8, etc., and can be transmitted on subframe 0 and subframe 5).

[0087] At 720, the base station may transmit an anchor carrier and/or a non-anchor carrier over one or more of the plurality of cells. In some aspects, the base station can determine a power boosting parameter for transmissions of the anchor carrier and/or non-anchor carrier. For example, in the case of an in-band operating mode or a guard band operating mode using a common power amplifier for physical resource blocks of a carrier, power boosting for a non-anchor carrier for SIB1-NB transmission may be 3 dB (decibel). . In contrast, power boosting for the anchor carrier can be 6 dB. As a result, the base station can allocate a larger number of subframes for transmission of SIB1-NB on the non-anchor carrier compared to the number of subframes for transmission of SIB1-NB on the anchor carrier. For example, the base station may transmit SIB1-NB in each subframe of index 0 and subframe of index 5, in alternate radio frames on a non-anchor carrier, and index in alternate radio frames on an anchor carrier SIB1-NB may be transmitted in each subframe of 0. In this case, the base station may repetitively transmit SIB1-NB 16 times on a non-anchor carrier or repeat SIB1-NB 8 times on an anchor carrier. In some aspects, the base station can transmit SIB1-NB on both the anchor carrier and/or the non-anchor carrier. For example, the base station may transmit SIB1-NB repeatedly on the anchor carrier and SIB1-NB repeatedly on the non-anchor carrier twice.

[0088] In some aspects, the non-anchor carrier can be adjacent to the anchor carrier in a common guard band. In some aspects, the non-anchor carrier can be at a frequency location opposite the anchor carrier in the guard band. In some aspects, the non-anchor carrier can be in an in-band physical resource block (PRB) adjacent to the anchor carrier.

[0089] As indicated above, FIG. 7 is provided as an example. Other examples are possible and may be different from those described with respect to FIG. 7.

[0090] 8 is a diagram illustrating an example 800 for carrier management for SIB1-NB on a non-anchor carrier.

[0091] As shown in FIG. 8, the base station (eg, BS 110) may provide SIB1-NB in a standalone mode or in a guard band operating mode using a plurality of power amplifiers. For example, the base station can provide SIB1-NB with common power boosting parameters for anchor carrier and non-anchor carrier. In this case, the number of subframes and frames for SIB1-NB transmission may be common to the anchor carrier and the non-anchor carrier.

[0092] At 810 and 820, the base station can provide a set of 4 repetitions of SIB1-NB transmission in each 2560 ms SIB1-NB period and using a carrier length of 160 ms. In this case, the base station can determine a frame offset of 0 ms, 160 ms, 320 ms, and 480 ms given a 2560 ms period. In some aspects, the base station can provide SIB1-NB transmission in a 10 ms period of each 160 ms period in the carrier.

[0093] At 830 and 840, in contrast, the base station can provide a set of 8 iterations of SIB1-NB transmission in each 2560 ms period. In this case, the base station can determine the frame offset of 0 ms or 160 ms. In some aspects, the base station can transmit SIB1-NB in subframe 0 of the alternating radio frames. For example, the base station may select between transmitting in odd indexed radio frames or transmitting in even indexed radio frames, based at least in part on the cell identifier associated with the cell, the SIB1-NB repetition quantity per period, and the like. have. In this case, as shown, the base station transmits the first SIB1-NB for a cell with an even PCID (physical cell identity value) in alternating parts of the SIB1-NB period and an odd physical cell identity value (PCID). ) May decide to transmit the second SIB1-NB.

[0094] As indicated above, FIG. 8 is provided as an example. Other examples are possible and may be different from those described with respect to FIG. 8.

[0095] 9 is a diagram illustrating an example 900 for carrier management for sending a random access message.

[0096] At 910, in the case of a frequency division duplex (FDD) NB-IoT communication system, a user equipment (eg, UE 120) uses an NB-PRACH or narrowband physical random access channel (NPRACH) and connection request message (eg, on a common carrier). PUSCH (Msg3 type message using a physical uplink shared channel) may be transmitted. For example, a user equipment may transmit a 180 kilohertz (kilohertz) band channel having a specific NB-PRACH periodicity and a first portion allocated for NB-PRACH transmission and a second portion available for connection request message. In some aspects, when a conflict occurs for an NB-PRACH transmission and connection request message, the user equipment may defer transmission of the connection request message to a later uplink subframe that does not overlap with the NB-PRACH resource.

[0097] At 920, in the case of a time division duplex (TDD) NB-IoT communication system, a user equipment may transmit an NB-PRACH and connection request message on one or more carriers. In some aspects, UE 120 may transmit a random access channel and connection request message using a common carrier. In this case, delaying the transmission of the connection request message, as in the downlink-preferred configuration, may cause excessive delay as a result of uplink subframes below a threshold quantity assigned to user equipment. For example, in TDD configuration type 2, user equipment may be assigned two uplink subframes in each frame, and NB-PRACH may be transmitted in parts of both of these two uplink subframes. In some aspects, the user equipment may enable the connection request message and NB-PRACH to be transmitted on different carriers rather than on a common carrier as for FDD NB-IoT. In some aspects, UE 120 may transmit a random access channel using a first carrier and a connection request message using a second carrier different from the first carrier. For example, based at least in part on receiving a bit indicator in a random access response (RAR) message or in a system information block message, the user equipment may include a plurality of carriers, such as two non-anchor carriers, Anchor carriers and non-anchor carriers, and the like. In this case, the user equipment transmits the NB-PRACH on the first carrier among the plurality of carriers (eg, the anchor carrier, or the non-anchor carrier among the plurality of non-anchor carriers), and the second of the plurality of carriers It is possible to send a connection request message on a carrier (eg, on a non-anchor carrier).

[0098] In some aspects, the user equipment can receive a message indicative of different carriers for the NB-PRACH and connection request message, and at least in part whether the NB-PRACH can be multiplexed with the connection request message in a single physical resource block. Based on, it is possible to determine whether to transmit the NB-PRACH and connection request message on different carriers. For example, the user equipment may determine whether to transmit the NB-PRACH and the connection request message on different carriers, based at least in part on the number of NB-PRACH subcarriers, the transmission bandwidth for the connection request message, and the like.

[0099] As indicated above, FIG. 9 is provided as an example. Other examples are possible and may be different from those described with respect to FIG. 9.

[00100] 10 is a flowchart of a wireless communication method 1000 for transmitting SIB1-NB on a non-anchor carrier. The method may be performed by a base station (eg, BS 110, device 1102/1102', BS 1450, etc.).

[00101] At 1010, in some aspects, the base station can determine a plurality of parameters for the non-anchor carrier or anchor carrier. For example, a base station (eg, using controller/processor 240, etc.) can determine a plurality of parameters for at least one of a non-anchor carrier or an anchor carrier, where the plurality of parameters are frequency domain location parameters and time Contains domain location parameters.

[00102] At 1020, the base station may transmit a master information block message identifying a plurality of parameters. For example, a base station (eg, using a controller/processor 240, a transmit processor 220, a TX MIMO processor 230, a MOD 232, an antenna 234, etc.) is a frequency domain location parameter, a time domain location parameter And a master information block message identifying the back.

[00103] At 1030, the base station may transmit a system information block type 1 (SIB1) message. For example, a base station (eg, using a controller/processor 240, a transmit processor 220, a TX MIMO processor 230, a MOD 232, an antenna 234, etc.) is a frequency domain location parameter, a time domain location parameter Depending on the like, a non-anchor carrier or an anchor carrier may be used to transmit the SIB1 message to user equipment. In some aspects, the base station can generate a SIB1 message for NB-IoT communications with user equipment. In some aspects, the SIB1 message can be a different type of message, such as a different type of system information block message, a non-system information block message, and the like.

[00104] The method 1000 can include additional aspects, such as any single aspect or any combination of aspects described below.

[00105] In some aspects, the SIB1 message is transmitted in subframe 0 and subframe 5 of the alternating radio frames of the non-anchor carrier. In some aspects, the SIB1 message is transmitted in subframe 0 of the alternating radio frames of the anchor carrier. In some aspects, a frequency domain location parameter associated with a physical resource block offset for a center frequency is identified, the anchor carrier is in a first frequency range greater than the center frequency by a physical resource block offset, and the non-anchor carrier is a physical resource block The second frequency range is less than the center frequency by the offset, or the non-anchor carrier is in the first frequency range greater than the center frequency by the physical resource block offset, and the anchor carrier is a second frequency less than the center frequency by the physical resource block offset. Is in range.

[00106] In some aspects, the non-anchor carrier is in at least one first physical resource block of the resource block group, and the non-anchor carrier is in at least one second physical resource block of the resource block group, and the at least one agent is The two physical resource blocks are connected to the at least one first physical resource block without one or more physical resource blocks of the resource block group between the at least one first physical resource block and the at least one second physical resource block. In some aspects, the non-anchor carrier and anchor carrier are associated with a common guard band. In some aspects, the at least one second physical resource block is an in-band physical resource block. In some aspects, the non-anchor carrier is in the first guard band and the anchor carrier is in a second guard band different from the first guard band.

[00107] In some aspects, the size or value for an indicator in which at least one of the plurality of parameters is identified is based at least in part on a deployment mode, the deployment mode being in-band deployment mode, guard band It is at least one of operation in a batch mode, either a batch mode or a standalone batch mode. In some aspects, the frequency domain location parameter or time domain location parameter is based at least in part on an offset indicator that identifies a resource block offset for the anchor carrier. In some aspects, the offset indicator is based at least in part on the resource block group, and the anchor carrier and non-anchor carrier are on resource blocks of the resource block group. In some aspects, the frequency domain location for the non-anchor carrier is opposite the frequency domain location of the anchor carrier relative to the center frequency.

[00108] In some aspects, at least one of the plurality of parameters is identified based at least in part on the physical resource block index offset of the anchor carrier. In some aspects, at least one of the plurality of parameters is identified based at least in part on a resource block group of in-band communication. In some aspects, at least one repetition of the SIB1 message is transmitted on the anchor carrier, and at least one repetition of the SIB1 message is transmitted on the non-anchor carrier.

[00109] In some aspects, for a non-anchor carrier, the power boosting parameter of the plurality of parameters is less than the power value for the anchor carrier. In some aspects, the repetition quantity of transmissions on the non-anchor carrier exceeds the repetition quantity of transmissions on the anchor carrier. In some aspects, the subframe or frame for the SIB1 message is determined based at least in part on the cell identifier or repetition configuration.

[00110] 10 shows example blocks of a wireless communication method, in some aspects, the method is additional blocks other than the blocks shown in FIG. 10, fewer blocks than the blocks, different from the blocks Blocks, or blocks arranged differently from the blocks may be included. Additionally or alternatively, two or more blocks shown in FIG. 10 may be performed simultaneously.

[00111] 11 is a conceptual data flow diagram 1100 illustrating the data flow between different modules/means/components in the example device 1102. Device 1102 may be a BS. In some aspects, the device 1102 includes a receiving module 1104, a determining module 1106 and/or a transmitting module 1108.

[00112] The receiving module 1104 can receive information associated with NB-IoT communication from the user equipment 1150 and as data 1110. In some aspects, the receiving module 1104 can receive the master information block message. For example, the receiving module 1104 may receive a master information block message including a group of bits for signaling the NB-IoT carrier frequency.

[00113] The decision module 1106 can receive information associated with determining a plurality of parameters for NB-IoT communication from the receiving module 1104 and as data 1112. In some aspects, the determination module 1106 can determine a plurality of parameters for the non-anchor carrier of the plurality of carriers. For example, the determination module 1106 can determine a frequency domain location parameter, time domain location parameter, and the like for the non-anchor carrier. In some aspects, the determination module 1106 can determine the plurality of parameters based at least in part on the information in the master information block message. For example, the determination module 1106 can determine the frequency location of the non-anchor carrier, based at least in part on the group of bits included in the master information block message.

[00114] In some aspects, the determination module 1106 can determine a parameter among the plurality of parameters based at least in part on the deployment mode for the NB-IoT. For example, in the case of in-band deployment mode, the determination module 1106 determines the physical resource block index offset value where 5 bits of the master information block message identify the offset of the non-anchor carrier or anchor carrier from the center frequency of the communication system. You can decide to display In this case, the offset of the non-anchor carrier may be the inverse of the offset of the anchor carrier. Additionally or alternatively, in the case of guard band placement or in-band placement, the master information block may include 2 bits associated with identifying a physical resource block index offset of a group of four configured physical resource block index offsets. . In some aspects, the determination module 1106 can determine a parameter among the plurality of parameters based at least in part on the resource block group of the anchor carrier. For example, the determination module 1106 can determine the resource block group of the anchor carrier, and determine the frequency location and/or time location of the non-anchor carrier such that the non-anchor carrier is in the same resource block group.

[00115] In some aspects, the determination module 1106 can determine the power boosting parameter among the plurality of parameters for the non-anchor carrier. For example, the determination module 1106 can determine that the non-anchor carrier will be associated with less power value than for the anchor carrier. Additionally or alternatively, decision module 1106 can determine that the non-anchor carrier and anchor carrier will be associated with a common power value.

[00116] The sending module 1108 can receive information associated with sending the data 1116 to the user equipment 1150 from the decision module 1106 and as the data 1114. In some aspects, the transmission module 1108 can transmit a master information block message to identify a plurality of parameters (eg, time domain location parameter, frequency domain location parameter, etc.) associated with the system information block message. In some aspects, the transmission module 1108 can transmit repetitions of the system information block message to the user equipment 1150. For example, the transmission module 1108 can transmit multiple repetitions in an anchor carrier, a non-anchor carrier, a combination of an anchor carrier and a non-anchor carrier, and the like. In some aspects, the sending module 1108 can transmit a certain number of repetitions of the system information block message. For example, when transmitting on a non-anchor carrier with a lower power boosting value, the transmitting module 1108 transmits a greater number of repetitions on the non-anchor carrier than when transmitting on an anchor carrier with a larger power boosting value. can do. In some aspects, the transmission module 1108 can transmit using a specific subset of resources, such as subframes or a specific subset of frames. For example, the transmission module 1108 may transmit using a specific subframe or frame based at least in part on a cell identifier for a cell, a repetition configuration (eg, configured repetition quantity), and the like.

[00117] The apparatus may include additional modules that perform each of the blocks of the algorithm in the flow chart described above in FIG. 10. Therefore, each block in the above-described flowchart of FIG. 10 may be performed by modules, and the apparatus may include one or more of these modules. The modules can be one or more hardware components specifically configured to perform the stated processes/algorithms, or can be implemented by a processor configured to perform the stated processes/algorithms, or computer-readable for implementation by the processor It may be stored in a possible medium, or any combination thereof.

[00118] The number and arrangement of modules shown in FIG. 11 is provided as an example. Indeed, there may be additional modules other than those shown in FIG. 11, fewer modules than the modules, modules different from the modules, or modules arranged differently from the modules. Further, two or more modules shown in FIG. 11 may be implemented in a single module, or the single module shown in FIG. 11 may be implemented as multiple distributed modules. Additionally or alternatively, the set of modules shown in FIG. 11 (eg, one or more modules) may perform one or more functions described as being performed by another set of modules shown in FIG. 11. .

[00119] 12 is a diagram 1200 illustrating an example of a hardware implementation for an apparatus 1102 ′ using the processing system 1202. Device 1102' may be a BS.

[00120] The processing system 1202 can be implemented with a bus architecture, represented generally by the bus 1204. The bus 1204 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1202 and overall design constraints. The bus 1204 is a variety of circuitry including one or more processors and/or hardware modules, modules 1104, 1106, 1108 and computer-readable media/memory 1208 represented by processor 1206. Link them together. The bus 1204 can also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits that are well known in the art and will no longer be described accordingly.

[00121] The processing system 1202 can be coupled to the transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1212. The transceiver 1210 provides a means for communicating with various other devices through a transmission medium. The transceiver 1210 receives signals from one or more antennas 1212, extracts information from the received signals, and provides the extracted information to the processing system 1202, specifically, the receiving module 1104. In addition, the transceiver 1210 receives information from the processing system 1202, specifically the transmission module 1108, and, based at least in part on the received information, signals to be applied to the one or more antennas 1212. To create. The processing system 1202 includes a processor 1206 coupled to a computer-readable medium/memory 1208. The processor 1206 is responsible for general processing including the execution of software stored on a computer-readable medium/memory 1208. Software, when executed by processor 1206, causes processing system 1202 to perform the various functions described above for any particular device. Computer-readable medium/memory 1208 may also be used to store data manipulated by processor 1206 when executing software. The processing system further includes at least one of the modules 1104, 1106 and 1108. The modules may be software modules resident/stored on the computer readable medium/memory 1208 and run on the processor 1206, one or more hardware modules coupled to the processor 1206, or any combination thereof. . The processing system 1202 may be a component of the BS 110, and may include at least one of a TX MIMO processor 230, an RX processor 238 and/or a controller/processor 240 and/or memory 242. Can.

[00122] In some aspects, the apparatus for wireless communication 1102/1102' transmits a master information block message including an indicator identifying a frequency domain location parameter or time domain location parameter for a non-anchor carrier or anchor carrier. And means for transmitting a system information block type 1 (SIB1) message to user equipment according to a frequency domain location parameter or a time domain location parameter, using a non-anchor carrier or an anchor carrier. The means described above can be one or more of the processing system 1202 of the device 1102' and/or the modules described above of the device 1102 configured to perform the functions recited by the means described above. As described above, the processing system 1202 can include a TX MIMO processor 230, a receiving processor 238 and/or a controller/processor 240. Therefore, in one configuration, the means described above may be a TX MIMO processor 230, a receive processor 238 and/or a controller/processor 240 configured to perform the functions mentioned by the means described above.

[00123] 12 is provided as an example. Other examples are possible and may be different from those described with respect to FIG. 12.

[00124] 13 is a flowchart of a wireless communication method 1300 for transmitting a connection request message. The method may be performed by user equipment (eg, UE 120, UE 1150, device 1402/1402', etc.).

[00125] At 1310, in some aspects, the user equipment can identify a plurality of carriers. For example, user equipment (eg, using controller/processor 280, etc.) can identify multiple carriers in a time division duplex network for random access.

[00126] At 1320, the user equipment may transmit a random access channel using the first carrier among the plurality of carriers. For example, user equipment (eg, using controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) is at least used to identify multiple carriers. A random access channel preamble may be transmitted using a first carrier among a plurality of carriers based in part.

[00127] At 1330, the user equipment may transmit a connection request message using a second carrier among the plurality of carriers. For example, a user equipment (eg, using a controller/processor 280, a transmission processor 264, a TX MIMO processor 266, a MOD 254, an antenna 252, etc.) is a first carrier among a plurality of carriers A connection request message may be transmitted using a second carrier different from.

[00128] Method 1300 can include additional aspects, such as any single aspect or any combination of aspects described below.

[00129] In some aspects, the plurality of carriers includes at least one anchor carrier and at least one non-anchor carrier used for random access channel messages. In some aspects, the second carrier for the connection request message is based at least in part on the carrier selection indicator from the random access response message (msg2).

[00130] In some aspects, the second carrier for the connection request message is based at least in part on predetermined information or a received system information block message. In some aspects, the connection request message is transmitted using the next available subframe that does not overlap with the random access channel resource. In some aspects, at least one of the plurality of carriers is based at least in part on a carrier selection indicator of the random access message.

[00131] In some aspects, the plurality of carriers includes another non-anchor carrier or anchor carrier. In some aspects, the connection request message and the random access channel message are multiplexed in a common resource block. In some aspects, the second carrier for the connection request message is selected based at least in part on the transmission bandwidth associated with the connection request message and the quantity of random access channel subcarriers.

[00132] In some aspects, the connection request message and the random access channel message are transmitted using a common carrier among a plurality of carriers. In some aspects, a plurality of carriers are identified based at least in part on stored information or received system information block messages. In some aspects, the connection request message is transmitted using the next available subframe that does not overlap with the random access channel resource.

[00133] 13 shows exemplary blocks of a method of wireless communication, in some aspects, the method may include additional blocks other than those shown in FIG. 13, fewer blocks than the blocks, and different from the blocks Blocks, or blocks arranged differently from the blocks may be included. Additionally or alternatively, two or more blocks shown in FIG. 13 may be performed simultaneously.

[00134] 14 is a conceptual data flow diagram 1400 illustrating data flow between different modules/means/components in the example device 1402. Device 1402 may be a UE. In some aspects, the device 1402 includes a receiving module 1404, an identification module 1406 and/or a transmitting module 1408.

[00135] The receiving module 1404 can receive information associated with identifying a plurality of carriers, from the base station 1450 and as data 1410. In some aspects, the receiving module 1404 can receive the carrier selection indicator. For example, the receiving module 1404 requests a random access with a bit indicator that identifies a different carrier (eg, different for the carrier for transmitting the NB-PRACH) to send a connection request message (eg, Msg3 type message). You can receive the message. Additionally or alternatively, the receiving module 1404 can receive a system information block message identifying a different carrier.

[00136] The identification module 1406 can receive information associated with identifying a plurality of carriers, from the receiving module 1404 and as data 1412. Additionally or alternatively, the identification module 1406 can identify a plurality of carriers based at least in part on the stored configuration. In some aspects, the identification module 1406 can identify a plurality of carriers in a time division duplex network. For example, the identification module 1406 can identify the non-anchor carrier for the connection request message and the anchor carrier for the NB-PRACH message. In some aspects, the identification module 1406 can identify the carrier for sending the connection request message based at least in part on the received carrier selection indicator.

[00137] In some aspects, the identification module 1406 can identify the carrier for the connection request message based at least in part on the characteristics of the NB-PRACH. For example, based at least in part on the connection request message and the NB-PRACH being able to be multiplexed in a physical resource block, the identification module 1406 causes the transmission module 1408 to send the connection request message and the NB-PRACH to different carriers. It is possible to decide whether to transmit or to transmit on a common carrier. In some aspects, the identification module 1406 causes the transmission module 1408 to differently transport the connection request message and the NB-PRACH based at least in part on the number of random access channel subcarriers, the transmission bandwidth associated with the connection request message, and the like. You can decide whether you want them to transmit or to transmit on a common carrier.

[00138] The transmission module 1408 can receive information associated with sending a connection request message as the data 1416 to the base station 1450 from the identification module 1406 and as data 1414. For example, the transmission module 1408 may transmit using at least one of a plurality of carriers, such as a connection request using a non-anchor carrier and an NB-PRACH using an anchor carrier. have. In some aspects, the transmission module 1408 can transmit a connection request message in a subframe that does not overlap with the random access channel resource. For example, when the transmission module 1408 has to transmit the NB-PRACH using the random access channel resource and the resource for the connection request message collides with the random access channel resource, the transmission module 1408 connects in the next available subframe. You can send a request message. Additionally or alternatively, the transmission module 1408 can transmit a connection request message using a different carrier than for the NB-PRACH. In some aspects, the transmission module 1408 can multiplex the connection request message and the NB-PRACH to a common carrier.

[00139] The apparatus may include additional modules that perform each of the blocks of the algorithm in the flow chart described above in FIG. 13. Therefore, each block in the above-described flowchart of FIG. 13 may be performed by modules, and the apparatus may include one or more of these modules. The modules can be one or more hardware components specifically configured to perform the stated processes/algorithms, or can be implemented by a processor configured to perform the stated processes/algorithms, or computer-readable for implementation by the processor It may be stored in a possible medium, or any combination thereof.

[00140] The number and arrangement of modules shown in FIG. 14 is provided as an example. Indeed, there may be additional modules other than those shown in FIG. 14, fewer modules than those modules, modules different from those modules, or modules arranged differently from the modules. Also, two or more modules shown in FIG. 14 may be implemented in a single module, or the single module shown in FIG. 14 may be implemented as multiple distributed modules. Additionally or alternatively, the set of modules shown in FIG. 14 (eg, one or more modules) may perform one or more functions described as being performed by another set of modules shown in FIG. 14. .

[00141] 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1402 ′ using processing system 1502. Device 1402' may be a UE.

[00142] The processing system 1502 can be implemented with a bus architecture, represented generally by the bus 1504. The bus 1504 can include any number of interconnecting buses and bridges depending on the specific application of the processing system 1502 and the overall design constraints. The bus 1504 includes various circuits, including one or more processors and/or hardware modules, modules 1404, 1406, 1408 and computer-readable media/memory 1508 represented by the processor 1506. Link them together. The bus 1504 can also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits that are well known in the art and will no longer be described accordingly.

[00143] The processing system 1502 can be coupled to the transceiver 1510. The transceiver 1510 is coupled to one or more antennas 1512. The transceiver 1510 provides a means for communicating with various other devices via a transmission medium. The transceiver 1510 receives signals from one or more antennas 1512, extracts information from the received signals, and provides the extracted information to the processing system 1502, specifically, the receiving module 1404. In addition, the transceiver 1510 receives information from the processing system 1502, specifically, the transmission module 1408, and, based at least in part on the received information, signals to be applied to the one or more antennas 1512. To create. Processing system 1502 includes a processor 1506 coupled to computer-readable medium/memory 1508. The processor 1506 is responsible for general processing including execution of software stored on a computer-readable medium/memory 1508. Software, when executed by processor 1506, causes processing system 1502 to perform the various functions described above for any particular device. Computer-readable medium/memory 1508 can also be used to store data manipulated by processor 1506 when executing software. The processing system further includes at least one of the modules 1404, 1406 and 1408. The modules may be software modules resident/stored on the computer readable medium/memory 1508 and run on the processor 1506, one or more hardware modules coupled to the processor 1506, or any combination thereof. . The processing system 1502 may be a component of the UE 120, and may include at least one of a TX MIMO processor 266, an RX processor 258 and/or a controller/processor 280 and/or memory 282. Can.

[00144] In some aspects, an apparatus for wireless communication 1402/1402' means for transmitting a random access channel using a first one of a plurality of carriers in a time division duplex network for random access, and a plurality of carriers And a means for transmitting a connection request message using a second carrier different from the first carrier. The means described above can be one or more of the processing system 1502 of the device 1402 ′ and/or the modules described above of the device 1402 configured to perform the functions recited by the means described above. As described above, the processing system 1502 can include a TX MIMO processor 266, an RX processor 258 and/or a controller/processor 280. Therefore, in one configuration, the means described above may be a TX MIMO processor 266, an RX processor 258 and/or a controller/processor 280 configured to perform the functions mentioned by the means described above.

[00145] 15 is provided as an example. Other examples are possible and may be different from those described with respect to FIG. 15.

[00146] It is understood that the specific order or hierarchy of blocks in the processes/flow charts disclosed is an illustration of example approaches. It is understood that based on design preferences, a specific order or hierarchy of blocks in processes/flow charts may be rearranged. Additionally, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[00147] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein, but should be consistent with the maximum scope consistent with the literary claims, where reference to a singular element, unless specifically stated otherwise, It is intended to mean "one or more", not "one and only one". The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as “exemplary” is not necessarily construed as being preferred or advantageous over other aspects. Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as “at least one of A, B or C”, “at least one of A, B and C” and “A, B, C or any combination thereof” can be any combination of A, B and/or C And multiples of A, multiples of B or multiples of C. Specifically, combinations such as "at least one of A, B or C", "at least one of A, B and C" and "A, B, C or any combination thereof" are only A, only B, only C , A and B, A and C, B and C, or A and B and C, wherein any such combinations can include one or more members or members of A, B or C. All structural and functional equivalents to elements of the various aspects described throughout this disclosure, which will be known to those skilled in the art or will be known later, are expressly incorporated herein by reference and covered by the claims. Is intended. Moreover, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. No claim element should be construed as a means plus function unless the element is explicitly stated using the phrase “means for”.

Claims (80)

A base station transmitting a master information block message including an indicator identifying a frequency domain location parameter or a time domain location parameter for a non-anchor carrier or anchor carrier; And
Transmitting, by the base station, a system information block type 1 (SIB1) message to user equipment according to the frequency domain location parameter or the time domain location parameter using the non-anchor carrier or the anchor carrier.
Containing,
Wireless communication method. According to claim 1,
The SIB1 message is transmitted in subframe 0 and subframe 5 of the alternating radio frames of the non-anchor carrier,
Wireless communication method. According to claim 1,
The SIB1 message is transmitted in subframe 0 of alternating radio frames of the anchor carrier,
Wireless communication method. According to claim 1,
The frequency domain location parameter identifies a physical resource block offset for the center frequency,
The anchor carrier is in a first frequency range greater than the center frequency by the physical resource block offset, and the non-anchor carrier is in a second frequency range less than the center frequency by the physical resource block offset, or
The non-anchor carrier is in the first frequency range greater than the center frequency by the physical resource block offset, and the anchor carrier is in the second frequency range less than the center frequency by the physical resource block offset,
Wireless communication method. According to claim 1,
The non-anchor carrier is in at least one first physical resource block of the resource block group, and
The non-anchor carrier is in at least one second physical resource block of the resource block group, and the at least one second physical resource block includes the at least one first physical resource block and the at least one second physical resource block. Interfacing with the at least one first physical resource block without one or more physical resource blocks of the resource block group between resource blocks,
Wireless communication method. The method of claim 5,
The non-anchor carrier and the anchor carrier are associated with a common guard band,
Wireless communication method. The method of claim 5,
The at least one second physical resource block is an inband physical resource block,
Wireless communication method. According to claim 1,
The non-anchor carrier is in a first guard band, and the anchor carrier is in a second guard band different from the first guard band,
Wireless communication method. According to claim 1,
The size or value for the indicator is based at least in part on a deployment mode, and
The batch mode,
In-band deployment mode,
Guard band placement mode, or
Standalone batch mode
At least one of
Wireless communication method. According to claim 1,
The frequency domain location parameter or the time domain location parameter is based at least in part on an offset indicator identifying a resource block offset for the anchor carrier,
Wireless communication method. The method of claim 10,
The offset indicator is based at least in part on a group of resource blocks, and
The anchor carrier and the non-anchor carrier are in resource blocks of the resource block group,
Wireless communication method. According to claim 1,
The frequency domain location for the non-anchor carrier is opposite the frequency domain location of the anchor carrier with respect to the center frequency,
Wireless communication method. According to claim 1,
The subframe or frame for the SIB1 message is determined based at least in part on the cell identifier or repetition configuration,
Wireless communication method. In a time division duplex network for random access, the user equipment transmits a random access channel using a first one of a plurality of carriers; And
The user equipment transmits a connection request message using a second carrier different from the first carrier among the plurality of carriers.
Containing,
Wireless communication method. The method of claim 14,
The plurality of carriers includes at least one anchor carrier and at least one non-anchor carrier used in a random access channel message,
Wireless communication method. The method of claim 14,
The second carrier for the connection request message is based at least in part on a carrier selection indicator from a random access response message,
Wireless communication method. The method of claim 14,
The second carrier for the connection request message is based at least in part on predetermined information or a received system information block message,
Wireless communication method. The method of claim 14,
The second carrier for the connection request message is based at least in part on the transmission bandwidth associated with the connection request message and the number of random access channel subcarriers,
Wireless communication method. The method of claim 14,
The connection request message and the random access channel message are transmitted using a common carrier among the plurality of carriers,
Wireless communication method. The method of claim 19,
The connection request message is transmitted using the next available subframe that does not overlap with the random access channel resource,
Wireless communication method. Memory; And
One or more processors operably coupled to the memory
It includes,
The memory and the one or more processors are:
To transmit a master information block message comprising an indicator identifying a frequency domain location parameter or time domain location parameter for a non-anchor carrier or anchor carrier; And
Using the non-anchor carrier or the anchor carrier, a system information block type 1 (SIB1) message is transmitted to user equipment according to the frequency domain location parameter or the time domain location parameter.
Consisting of,
Base station for wireless communication. The method of claim 21,
The SIB1 message is transmitted in subframe 0 and subframe 5 of the alternating radio frames of the non-anchor carrier,
Base station for wireless communication. The method of claim 21,
The SIB1 message is transmitted in subframe 0 of alternating radio frames of the anchor carrier,
Base station for wireless communication. The method of claim 21,
The frequency domain location parameter identifies a physical resource block offset for the center frequency,
The anchor carrier is in a first frequency range greater than the center frequency by the physical resource block offset, and the non-anchor carrier is in a second frequency range less than the center frequency by the physical resource block offset, or
The non-anchor carrier is in the first frequency range greater than the center frequency by the physical resource block offset, and the anchor carrier is in the second frequency range less than the center frequency by the physical resource block offset,
Base station for wireless communication. The method of claim 21,
The non-anchor carrier is in at least one first physical resource block of the resource block group, and
The non-anchor carrier is in at least one second physical resource block of the resource block group, and the at least one second physical resource block includes the at least one first physical resource block and the at least one second physical resource block. Interfacing with the at least one first physical resource block without one or more physical resource blocks of the resource block group between resource blocks,
Base station for wireless communication. The method of claim 25,
The non-anchor carrier and the anchor carrier are associated with a common guard band,
Base station for wireless communication. The method of claim 25,
The at least one second physical resource block is an in-band physical resource block,
Base station for wireless communication. The method of claim 21,
The non-anchor carrier is in a first guard band, and the anchor carrier is in a second guard band different from the first guard band,
Base station for wireless communication. The method of claim 21,
The size or value for the indicator is based at least in part on the placement mode, and
The batch mode,
In-band deployment mode,
Guard band placement mode, or
Standalone batch mode
At least one of
Base station for wireless communication. The method of claim 21,
The frequency domain location parameter or the time domain location parameter is based at least in part on an offset indicator identifying a resource block offset for the anchor carrier,
Base station for wireless communication. The method of claim 30,
The offset indicator is based at least in part on a group of resource blocks, and
The anchor carrier and the non-anchor carrier are in resource blocks of the resource block group,
Base station for wireless communication. The method of claim 21,
The frequency domain location for the non-anchor carrier is opposite the frequency domain location of the anchor carrier with respect to the center frequency,
Base station for wireless communication. The method of claim 21,
The subframe or frame for the SIB1 message is determined based at least in part on the cell identifier or repetition configuration,
Base station for wireless communication. Memory; And
One or more processors operably coupled to the memory
It includes,
The memory and the one or more processors are:
In a time division duplex network for random access, to transmit a random access channel using a first one of a plurality of carriers; And
To transmit a connection request message using a second carrier different from the first carrier among the plurality of carriers
Consisting of,
User equipment for wireless communication. The method of claim 34,
The plurality of carriers includes at least one anchor carrier and at least one non-anchor carrier used in a random access channel message,
User equipment for wireless communication. The method of claim 34,
The second carrier for the connection request message is based at least in part on a carrier selection indicator from a random access response message,
User equipment for wireless communication. The method of claim 34,
The second carrier for the connection request message is based at least in part on predetermined information or a received system information block message,
User equipment for wireless communication. The method of claim 34,
The second carrier for the connection request message is based at least in part on the transmission bandwidth associated with the connection request message and the number of random access channel subcarriers,
User equipment for wireless communication. The method of claim 34,
The connection request message and the random access channel message are transmitted using a common carrier among the plurality of carriers,
User equipment for wireless communication. The method of claim 39,
The connection request message is transmitted using the next available subframe that does not overlap with the random access channel resource,
User equipment for wireless communication. A non-transitory computer-readable storage medium storing one or more instructions for wireless communication,
The one or more instructions, when executed by one or more processors of the base station, cause the one or more processors to:
Send a master information block message comprising an indicator identifying a frequency domain location parameter or a time domain location parameter for a non-anchor carrier or anchor carrier; And
Using the non-anchor carrier or the anchor carrier, a system information block type 1 (SIB1) message is transmitted to a user equipment according to the frequency domain location parameter or the time domain location parameter.
Containing one or more instructions,
Non-transitory computer-readable storage medium. The method of claim 41,
The SIB1 message is transmitted in subframe 0 and subframe 5 of the alternating radio frames of the non-anchor carrier,
Non-transitory computer-readable storage medium. The method of claim 41,
The SIB1 message is transmitted in subframe 0 of alternating radio frames of the anchor carrier,
Non-transitory computer-readable storage medium. The method of claim 41,
The frequency domain location parameter identifies a physical resource block offset for the center frequency,
The anchor carrier is in a first frequency range greater than the center frequency by the physical resource block offset, and the non-anchor carrier is in a second frequency range less than the center frequency by the physical resource block offset, or
The non-anchor carrier is in the first frequency range greater than the center frequency by the physical resource block offset, and the anchor carrier is in the second frequency range less than the center frequency by the physical resource block offset,
Non-transitory computer-readable storage medium. The method of claim 41,
The non-anchor carrier is in at least one first physical resource block of the resource block group, and
The non-anchor carrier is in at least one second physical resource block of the resource block group, and the at least one second physical resource block includes the at least one first physical resource block and the at least one second physical resource block. Interfacing with the at least one first physical resource block without one or more physical resource blocks of the resource block group between resource blocks,
Non-transitory computer-readable storage medium. The method of claim 45,
The non-anchor carrier and the anchor carrier are associated with a common guard band,
Non-transitory computer-readable storage medium. The method of claim 45,
The at least one second physical resource block is an in-band physical resource block,
Non-transitory computer-readable storage medium. The method of claim 41,
The non-anchor carrier is in a first guard band, and the anchor carrier is in a second guard band different from the first guard band,
Non-transitory computer-readable storage medium. The method of claim 41,
The size or value for the indicator is based at least in part on the placement mode, and
The batch mode,
In-band deployment mode,
Guard band placement mode, or
Standalone batch mode
At least one of
Non-transitory computer-readable storage medium. The method of claim 41,
The frequency domain location parameter or the time domain location parameter is based at least in part on an offset indicator identifying a resource block offset for the anchor carrier,
Non-transitory computer-readable storage medium. The method of claim 50,
The offset indicator is based at least in part on a group of resource blocks, and
The anchor carrier and the non-anchor carrier are in resource blocks of the resource block group,
Non-transitory computer-readable storage medium. The method of claim 41,
The frequency domain location for the non-anchor carrier is opposite the frequency domain location of the anchor carrier with respect to the center frequency,
Non-transitory computer-readable storage medium. The method of claim 41,
The subframe or frame for the SIB1 message is determined based at least in part on the cell identifier or repetition configuration,
Non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium storing one or more instructions for wireless communication,
The one or more instructions, when executed by one or more processors of user equipment, cause the one or more processors to:
In a time division duplex network for random access, a random access channel is transmitted using a first one of a plurality of carriers; And
Among the plurality of carriers, a connection request message is transmitted using a second carrier different from the first carrier.
Containing one or more instructions,
Non-transitory computer-readable storage medium. The method of claim 54,
The plurality of carriers includes at least one anchor carrier and at least one non-anchor carrier used in a random access channel message,
Non-transitory computer-readable storage medium. The method of claim 54,
The second carrier for the connection request message is based at least in part on a carrier selection indicator from a random access response message,
Non-transitory computer-readable storage medium. The method of claim 54,
The second carrier for the connection request message is based at least in part on predetermined information or a received system information block message,
Non-transitory computer-readable storage medium. The method of claim 54,
The second carrier for the connection request message is based at least in part on the transmission bandwidth associated with the connection request message and the number of random access channel subcarriers,
Non-transitory computer-readable storage medium. The method of claim 54,
The connection request message and the random access channel message are transmitted using a common carrier among the plurality of carriers,
Non-transitory computer-readable storage medium. The method of claim 59,
The connection request message is transmitted using the next available subframe that does not overlap with the random access channel resource,
Non-transitory computer-readable storage medium. Means for transmitting a master information block message comprising an indicator identifying a frequency domain location parameter or time domain location parameter for a non-anchor carrier or anchor carrier; And
Means for transmitting a system information block type 1 (SIB1) message to user equipment according to the frequency domain location parameter or the time domain location parameter using the non-anchor carrier or the anchor carrier
Containing,
Device for wireless communication. The method of claim 61,
The SIB1 message is transmitted in subframe 0 and subframe 5 of the alternating radio frames of the non-anchor carrier,
Device for wireless communication. The method of claim 61,
The SIB1 message is transmitted in subframe 0 of alternating radio frames of the anchor carrier,
Device for wireless communication. The method of claim 61,
The frequency domain location parameter identifies a physical resource block offset for the center frequency,
The anchor carrier is in a first frequency range greater than the center frequency by the physical resource block offset, and the non-anchor carrier is in a second frequency range less than the center frequency by the physical resource block offset, or
The non-anchor carrier is in the first frequency range greater than the center frequency by the physical resource block offset, and the anchor carrier is in the second frequency range less than the center frequency by the physical resource block offset,
Device for wireless communication. The method of claim 61,
The non-anchor carrier is in at least one first physical resource block of the resource block group, and
The non-anchor carrier is in at least one second physical resource block of the resource block group, and the at least one second physical resource block includes the at least one first physical resource block and the at least one second physical resource block. Interfacing with the at least one first physical resource block without one or more physical resource blocks of the resource block group between resource blocks,
Device for wireless communication. The method of claim 65,
The non-anchor carrier and the anchor carrier are associated with a common guard band,
Device for wireless communication. The method of claim 65,
The at least one second physical resource block is an in-band physical resource block,
Device for wireless communication. The method of claim 61,
The non-anchor carrier is in a first guard band, and the anchor carrier is in a second guard band different from the first guard band,
Device for wireless communication. The method of claim 61,
The size or value for the indicator is based at least in part on the placement mode, and
The batch mode,
In-band deployment mode,
Guard band placement mode, or
Standalone batch mode
At least one of
Device for wireless communication. The method of claim 61,
The frequency domain location parameter or the time domain location parameter is based at least in part on an offset indicator identifying a resource block offset for the anchor carrier,
Device for wireless communication. The method of claim 70,
The offset indicator is based at least in part on a group of resource blocks, and
The anchor carrier and the non-anchor carrier are in resource blocks of the resource block group,
Device for wireless communication. The method of claim 61,
The frequency domain location for the non-anchor carrier is opposite the frequency domain location of the anchor carrier with respect to the center frequency,
Device for wireless communication. The method of claim 61,
The subframe or frame for the SIB1 message is determined based at least in part on the cell identifier or repetition configuration,
Device for wireless communication. In a time division duplex network for random access, means for transmitting a random access channel using a first one of a plurality of carriers; And
Means for transmitting a connection request message using a second carrier different from the first carrier among the plurality of carriers
Containing,
Device for wireless communication. The method of claim 74,
The plurality of carriers includes at least one anchor carrier and at least one non-anchor carrier used in a random access channel message,
Device for wireless communication. The method of claim 74,
The second carrier for the connection request message is based at least in part on a carrier selection indicator from a random access response message,
Device for wireless communication. The method of claim 74,
The second carrier for the connection request message is based at least in part on predetermined information or a received system information block message,
Device for wireless communication. The method of claim 74,
The second carrier for the connection request message is based at least in part on the transmission bandwidth associated with the connection request message and the number of random access channel subcarriers,
Device for wireless communication. The method of claim 74,
The connection request message and the random access channel message are transmitted using a common carrier among the plurality of carriers,
Device for wireless communication. The method of claim 79,
The connection request message is transmitted using the next available subframe that does not overlap with the random access channel resource,
Device for wireless communication.

Images