KR20190036552A - Method for performing random access, user equipment, and base station - Google Patents

Abstract

A method for performing random access at a user equipment (UE) is provided, the method comprising the steps of: receiving configuration information from a base station, the configuration information including anchor carriers supporting random access and / or one or more non- Marked -; Selecting, as a random access carrier, an anchor carrier and / or one or more non-anchor carriers supporting random access according to the configuration information; And performing random access using the random access carrier. Also provided is a method for performing random access at a base station, and a corresponding UE and base station.

Description

Method for performing random access, user equipment, and base station

The present invention relates to the field of wireless communication technology. In particular, the present invention relates to a method for random access, corresponding user equipment (UE), and corresponding base station.

With a wide range of applications of the Internet of Things and its terminal devices, it becomes critical to address the issue of specifying the wireless network technology provided for the communication of the things Internet. The 3rd Generation Partnership Project (3GPP) aims to design radio access technology with low complexity and low throughput to meet the needs of the wireless Internet, A new access system is currently being developed for the purpose of designing radio access technology with low complexity and low throughput to meet the needs of the wireless Internet referred to as Narrowband-Internet of Things (NB-IoT). Features of this access technology include supporting large devices with low throughput, low latency sensitivity, extremely low device cost, extremely low power consumption, and optimized network architecture.

In NB-IoT, this UE with low throughput, extremely low device cost, and low power consumption has only a 180 kHz network bandwidth, referred to as a carrier (or referred to as a cell) Supports physical resource blocks in long term evolution (LTE); The UE needs to support three deployment modes: a stand-alone deployment mode, a guard-band deployment mode, and an in-band deployment mode. The stand-alone mode of operation is for implementing the NB-IoT on the existing GSM frequency band, i.e. the operating frequency band of the existing GERAN system and the interspersed frequency band potentially developed by IoT. The guard-band mode of operation is for implementing the NB-IoT using the frequency band in the LTE frequency band used as a guard band in one LTE carrier's guard band. The in-band mode of operation is for implementing the NB-IoT in the existing LTE frequency band, i.e., using the frequency band in the LTE frequency band for actual transmission. The different bearer modes may employ different physical parameters and processing mechanisms.

In Release 13, the carriers of NB-IoT are divided into anchor carriers and non-anchor carriers. The UE may be a physical broadcast channel (PBCH), a primary synchronization signal (PSS) / a secondary synchronization signal (SSS), or a system information block (SIB ), It is assumed that the NB-IoT related data is to be transmitted, the anchor carrier is defined as a carrier; When the UE does not assume that NB-IoT related data such as PBCH, PSS, SSS, or SIB should be transmitted, the non-anchor carrier is defined as a carrier. That is, the UE determines whether the non-anchor carrier is a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), or a physical uplink shared channel ) ≪ / RTI > (PUSCH) associated with the NB-IoT. When the eNB does not configure a non-anchor carrier for the UE, the anchor carrier may also be used by the UE to receive or transmit NB-IoT related unicast transmitted data such as PDCCH, PDSCH, or PUSCH. the eNB may configure a non-anchor carrier for the UE by using a radio resource control (RRC) connection establishment message, an RRC connection re-establishment message, an RRC connection reconfiguration message, and an RRC connection restoration message.

Release 13 In NB-IoT, the UE performs a random access process only on an anchor carrier. After the base station eNB has configured the non-anchor carrier for the UE, the UE will operate on the non-anchor carrier in the RRC connection process until the UE needs to perform random access or is reassigned to another non-anchor carrier will be. When a UE operating on a non-anchor carrier needs to perform random access, the UE will return to the anchor carrier to perform random access.

The 3GPP RAN # 72 conference has approved a new Release 14 NB-IoT project to improve NB-IoT in Release 13, including supporting random access on non-anchor carriers. However, a solution to how to support random accesses on non-anchor carriers is not provided in the prior art.

In order to solve the above-mentioned technical problems, the present invention proposes a solution as to how to support random accesses on non-anchor carriers.

According to a first aspect of the present invention, a method is provided for random access performed in a user equipment (UE). The method comprising: receiving configuration information from a base station; configuration information indicating an anchor carrier and / or one or more non-anchor carriers supporting random access; Selecting, as a random access carrier, a carrier from among the anchor carriers supporting random access and / or one or more non-anchor carriers according to the configuration information; And performing random access by using a random access carrier.

In an embodiment, the step of selecting, as a random access carrier, an anchor carrier supporting random access and / or one or more non-anchor carriers according to the configuration information is a random selection scheme, , Or as a random access carrier in accordance with predefined rules, selecting a carrier from an anchor carrier and / or one or more non-anchor carriers that support random access indicated by the configuration information.

In an embodiment, the random access carrier is an uplink carrier if the downlink carrier on which the UE receives a paging message on it is configured with a corresponding uplink carrier, and the uplink carrier supports random access.

In an embodiment, the step of selecting, as a random access carrier, an anchor carrier supporting random access and / or a carrier from one or more non-anchor carriers, according to the configuration information, Selecting an anchor carrier that supports random access indicated by the configuration information as a random access carrier if the link carrier is not configured with a corresponding uplink carrier or the corresponding uplink carrier configured does not support random access; Anchor carrier and / or one or more non-anchor carriers that support random access indicated by the configuration information, in a random selection manner, in the same probability random selection scheme, or in accordance with predefined rules, as random access carriers And selecting a carrier.

In an embodiment, when a physical downlink control channel (PDCCH) or higher layer specifies a carrier for the UE to perform random access, the random access carrier is a specified carrier.

In an embodiment, the random access carrier is a non-anchor carrier with an RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB information element configured by the RRC.

In an embodiment, when the serving carrier of the UE supports random access, the random access carrier is a serving carrier.

In an embodiment, selecting a carrier from the anchor carrier supporting random access and / or one or more non-anchor carriers as a random access carrier, according to the configuration information, ≪ / RTI > further selecting a random access carrier based on the random access carrier.

In an embodiment, the step of selecting, as a random access carrier, an anchor carrier supporting random access and / or a carrier from one or more non-anchor carriers according to the configuration information comprises adding a random access carrier based on the data size . ≪ / RTI >

In an embodiment, selecting a random access carrier based on data size comprises comparing a potential message size with a predetermined threshold; And selecting the random access carrier according to the comparison result.

In an embodiment, the configuration information indicates one or more random access resource configurations for random access.

In an embodiment, the configuration information includes an indication to indicate whether the corresponding non-anchor carrier shares the same random access resource configuration with an anchor carrier.

In an embodiment, the RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB configurations of the anchor carriers are different from the RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB configurations of the non-anchor carriers.

In an embodiment, the NPRACH-ParametersList-NB configuration of the anchor carrier is different from the NPRACH-ParametersList-NB configuration of the non-anchor carrier.

In an embodiment, one or more non-anchor carriers in one or more non-anchor carriers share the same random access resource configuration with an anchor carrier.

In an embodiment, the random access resource configuration is RACH-ConfigCommon-NB; NPRACH-ConfigSIB-NB; Or NPRACH-ParametersList-NB.

In an embodiment, the configuration information includes an indicator for indicating whether the corresponding anchor carrier or non-anchor carrier supports random access. When the value of the indicator is set to "True" or "Setup" or "1", the corresponding anchor carrier or non-anchor carrier supports random access; When the value of the indicator is set to "False" or "Release" or "0", the corresponding non-anchor carrier does not support random access.

In an embodiment, the configuration information includes indicating whether the corresponding non-anchor carrier adopts the same random access resource configuration as that of the anchor carrier. When the value of the indicator is set to "True" or "Set up" or "1", the corresponding non-anchor carrier adopts the same random access resource configuration as that of the anchor carrier; If the value of the indication is set to " false ", " released ", or " 0 " or no indication is displayed, the corresponding non-anchor carrier adopts a random access resource configuration different from that of the anchor carrier.

According to a second aspect of the present invention, a method is provided for random access performed at a base station. The method includes: generating configuration information-configuration information indicating an anchor carrier that supports random access and / or one or more non-anchor carriers; And transmitting the configuration information for the UE to perform random access to the user equipment (UE).

In an embodiment, transmitting the configuration information to the UE comprises broadcasting configuration information in the system information; Or transmitting configuration information by using RRC dedicated signaling.

According to a third aspect of the present invention, a user equipment (UE) is provided. Wherein the UE is configured to receive configuration information from a base station, the configuration information indicating an anchor carrier and / or one or more non-anchor carriers supporting random access; According to the configuration information, as the random access carrier, a selection unit configured to select a carrier from an anchor carrier supporting random access and / or one or a plurality of non-anchor carriers; And a random access execution unit configured to perform random access by using a random access carrier.

In an embodiment, the selection unit may comprise an anchor carrier supporting random access indicated by the configuration information and / or one or more than one < RTI ID = 0.0 >Lt; RTI ID = 0.0 > non-anchor < / RTI >

In an embodiment, the random access carrier is an uplink carrier when the downlink carrier on which the UE receives the paging message on it is configured with a corresponding uplink carrier, and the uplink carrier supports random access.

In an embodiment, the selection unit may be configured as a random access carrier if the downlink carrier on which the UE receives the paging message on it is not configured with a corresponding uplink carrier, or the corresponding uplink carrier configured does not support random access, Or an anchor carrier that supports random access indicated by information, or supports random access indicated by the configuration information as a random access method, in the same probability random selection method, or according to a predefined rule, as a random access carrier And is further configured to select a carrier from an anchor carrier and / or one or more non-anchor carriers.

In an embodiment, when a physical downlink control channel (PDCCH) or higher layer specifies a carrier for the UE to perform random access, the random access carrier is a specified carrier.

In an embodiment, the random access carrier is a non-anchor carrier with RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB information elements configured by RRC.

In an embodiment, when the serving carrier of the UE supports random access, the random access carrier is a serving carrier.

In an embodiment, the selection unit is further configured to further select a random access carrier based on the improved coverage level of the UE.

In an embodiment, the selection unit is further configured to further select a random access carrier based on the data size.

In an embodiment, selecting a random access carrier based on data size comprises comparing a potential message size with a predetermined threshold; And selecting the random access carrier according to the comparison result.

In an embodiment, the configuration information indicates one or more random access resource configurations for random access.

In an embodiment, the configuration information includes an indication to indicate whether the corresponding non-anchor carrier shares the same random access resource configuration with an anchor carrier.

In an embodiment, the RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB configurations of the anchor carriers are different from the RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB configurations of the non-anchor carriers.

In an embodiment, the NPRACH-ParametersList-NB configuration of the anchor carrier is different from the NPRACH-ParametersList-NB configuration of the non-anchor carrier.

In an embodiment, one or more non-anchor carriers in one or more non-anchor carriers share the same random access resources with an anchor carrier.

In an embodiment, the random access resource configuration is RACH-ConfigCommon-NB; NPRACH-ConfigSIB-NB; Or NPRACH-ParametersList-NB.

In an embodiment, the configuration information includes indicating whether the corresponding anchor carrier or non-anchor carrier supports random access. When the value of the indicator is set to "True" or "Set up" or "1", the corresponding anchor carrier or non-anchor carrier supports random access; When the value of the indicator is set to " false " or " released " or " 0 ", the corresponding non-anchor carrier does not support random access.

In an embodiment, the configuration information includes indicating whether the corresponding non-anchor carrier adopts the same random access resource configuration as that of the anchor carrier. When the value of the indicator is set to "True" or "Set up" or "1", the corresponding non-anchor carrier adopts the same random access resource configuration as that of the anchor carrier; If the value of the indication is set to " false ", " released ", or " 0 " or no indication is displayed, the corresponding non-anchor carrier adopts a random access resource configuration different from that of the anchor carrier.

According to a fourth aspect of the present invention, a base station is provided. The base station is configured to generate the configuration information - the configuration information is indicative of an anchor carrier that supports random access and / or one or more non-anchor carriers; And a transmission unit configured to transmit configuration information for the UE to perform random access to the user equipment (UE).

In an embodiment, the transmitting unit broadcasts the configuration information in the system information; Or to transmit configuration information by using RRC dedicated signaling.

Specific embodiments of the invention are described in detail with reference to the following description and accompanying drawings; And ways in which the principles of the present invention are employed are exemplified. It is to be understood that the embodiments of the present invention are not limited in scope. Within the spirit and scope defined by the appended claims, embodiments of the invention may include various modifications, modifications, and equivalents.

The features described and / or illustrated for a particular embodiment may be used in one or more other embodiments in the same or similar manner, or may be combined with features in other embodiments, or in other embodiments May be used to replace the features of FIG.

The term " comprise / include " as used herein refers to the presence of features, whole pieces, steps, or components, but is not limited to the presence of other features, Quot; does not exclude the presence or addition of one or more of the foregoing.

These and other features of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings.
1 schematically illustrates a flow diagram of a method 100 for random access performed in a UE according to an embodiment of the present invention;
Figure 2 schematically illustrates a flow diagram of a method 200 for random access performed at a base station in accordance with an embodiment of the present invention;
3 schematically illustrates a structural block diagram of a UE 300 in accordance with an embodiment of the present invention;
4 schematically illustrates a structural block diagram of a base station 400 in accordance with an embodiment of the present invention;
5 schematically illustrates a flow diagram of a method 500 for random access performed in a UE according to an embodiment of the present invention;
Figure 6 schematically illustrates a flow diagram of a method 600 for random access performed at a source base station in accordance with an embodiment of the present invention;
FIG. 7 schematically illustrates a flow diagram of a method 700 for random access performed at a target base station in accordance with an embodiment of the present invention;
Figure 8 schematically illustrates a structural block diagram of a UE 800 in accordance with an embodiment of the present invention;
9 schematically illustrates a structural block diagram of a source base station 900 in accordance with an embodiment of the present invention; And
10 schematically illustrates a structural block diagram of a target base station 1000 in accordance with an embodiment of the present invention.

With reference to the accompanying drawings, the above-described and other features of the present invention will become more apparent from the following description. In the drawings and accompanying drawings, specific embodiments of the invention are disclosed, which illustrate some implementations in which the principles of the invention may be employed. It is to be understood that the invention is not to be limited to the specific embodiments described below but rather, all such modifications, variations and equivalents as fall within the scope defined by the appended claims. Additionally, for simplicity, a detailed description of known techniques not directly related to the present invention is omitted in order to avoid confusion regarding the understanding of the present invention.

Referring to the accompanying drawings and specific embodiments, the random access method proposed by the present invention is described in more detail below.

A plurality of embodiments in accordance with the present invention are specifically described below by using the LTE mobile communication system and its later evolved versions as exemplary application environments and using the NB-IoT as an exemplary implementation technical scenario. It should be understood, however, that the application environment of the present invention is not limited to the above exemplary application environments, but is applicable to many other wireless communication systems, such as future 5G cellular communication systems. Further, the implementation technical scenarios of the present invention are also not limited to NB-IoT, but are also applicable to other non-NB-IoT devices and systems, such as the improved Machine Type Communication (MTC) It is possible.

Hereinafter, the explanation is provided by using the eNB as an example of the base station. However, it should be understood that the base station described in the present invention is not limited thereto, but may further include various base stations such as a macro base station, a micro base station, or a pico base station.

Information Elements (IEs) mainly involved in the present invention are introduced below first.

RACH-ConfigCommon-NB: This information element includes the following parameters (also referred to as information elements): preambleTransMax-CE for indicating the maximum number of transmissions of the preamble, power ramping step powerRampingStep and preamble initial receive target power and a rach-InfoList containing at least one of a raR-ResponseWindowSize for indicating the size of the random access response window and a set of mac-ContentionResolutionTimer for indicating the contention resolution time, and a rach-InfoList indicating the random access response window size . It should be noted that the RACH-ConfigCommon-NB may further include other general parameters for defining random access, in addition to the one or more parameters listed.

NPRACH-ConfigSIB-NB: This information element includes the following parameters: nprach-CP-Length for indicating the transmission cycle prefix length of the NPRACH, and nprach-CP-Length for indicating the criteria for the UE to select the NPRACH resource. IoT Physical Random Access Channel (NPRACH) configuration comprising at least one of an nprach-ParametersList, an nprach-ParametersList, an nprach-ParametersList, and an nprach-ParametersList each of which constitutes NPRACH parameters for a set of NPRACH resources .

NPRACH-ParametersList: This information element contains the following parameters: nprach-Periodicity to indicate the NPRACH resource period, nprach-StartTime to indicate the start position of the NPRACH resource in one cycle, and the frequency domain location of the NPRACH resource Nprach-NumSubcarriers for indicating the number of subcarriers contained in one NPRACH resource, nprach-NumSubcarriers for calculating the starting subcarrier number of NPRACH subcarriers supporting multi-carrier Msg3 transmission reserved for UE, -SubcarrierMSG3-RangeStart, and maxNumPreambleAttemptCE to indicate the maximum number of transmissions of the preamble on each PRACH resource, numRepetitionsPerPreambleAttempt to indicate the number of iterations at each transmission of the NPRACH on each PRACH resource, RAR, Msg3 retransmission , And the maximum number of iterations of the NPDCCH common search space associated with Msg4 StartSF-CSS-RA, and NPDCCH common search space (denoted as npdcch-StartSF-CSS-RA) to indicate the start subcarrier configuration of the npdcch-NumRepetitions-RA, RAR, Msg3 retransmission, and NPDCCH common search space associated with Msg4 And npdcch-Offset-RA for indicating the partial period offset of the starting subcarrier of the first sub-carrier (e.g., CSS). It should be noted that the nprach-ParametersList may further include other parameters for configuring the NPRACH not directly included in the NPRACH-ConfigSIB-NB, in addition to the one or more parameters listed.

In the present invention, RACH-ConfigCommon-NB, NPRACH-ConfigSIB-NB, and NPRACH-ParametersList-NB related to an anchor carrier are respectively expressed as RACH-ConfigCommonAnchor-NB, NPRACH-ConfigSIBAnchor-NB and NPRACH-ParametersListAnchor-NB; Note that RACH-ConfigCommon-NB, NPRACH-ConfigSIB-NB, and NPRACH-ParametersList-NB associated with non-anchor carriers are represented as RACH-ConfigCommonNonAnchor-NB, NPRACH-ConfigSIBNonAnchor-NB, and NPRACH-ParametersListNonAnchor-NB, respectively. .

The random access resources involved in the present invention include, but are not limited to, information elements RACH-ConfigCommon-NB and / or information element NPRACH-ConfigSIB-NB and / or information element NPRACH-ParametersList- Quot; refers to the parameters acquired by the UE prior to performing the access.

A method for random access performed in a UE according to an embodiment of the present invention will be described below with reference to FIG. 1 schematically illustrates a flow diagram of a method 100 for random access performed in a UE according to an embodiment of the present invention.

As shown in FIG. 1, in step S110, the UE receives configuration information from the eNB. The configuration information indicates an anchor carrier that supports random access and / or one or more non-anchor carriers. The configuration information includes at least configuration information of one or more non-anchor carriers available for random access. The configuration information may also be broadcast in the system information. For example, the configuration information is received via the SystemInformationBlockType2-NB IE defined by the 3GPP standard TS36.331, and / or additionally via the RadioResourceConfigCommonSIB-NB IE included in the SystemInformationBlockType2-NB. The configuration information may also be transmitted using RRC dedicated signaling. The RRC dedicated signaling may be an RRC reconfiguration message. For example, the configuration information is received via the RRCConnectionReconfiguration-NB IE defined by TS 36.331, and / or additionally via the RadioResourceConfigDedicated-NB IE included in the RRCConnectionReconfiguration-NB. The RadioResourceConfigDedicated-NB information element is used to establish, modify, or release a radio bear (RB) and / or modify the MAC master configuration and modify a particular physical layer configuration.

The method for constructing the anchor carrier and / or non-anchor carrier related parameters (parameters including, but not limited to, uplink and downlink carrier frequencies and random access resources) (E.g., parameters may be broadcast in system information) or in a unicast manner (e.g., by using RRC dedicated signaling, where the RRC dedicated signaling may be an RRC reconfiguration message, etc.) It should be noted that this is not limited to this.

In step S120, the UE selects, as a random access carrier, a carrier from an anchor carrier supporting random access and / or one or a plurality of non-anchor carriers according to the configuration information.

In an implementation, step S120 may be an anchor carrier supporting random access indicated by the configuration information, and / or an anchor carrier supporting random access indicated by the configuration information, in a random selection manner, in the same probability random selection manner, Or selecting a carrier from a plurality of non-anchor carriers. For example, for a UE identity having a number of random access carriers (which may include an anchor carrier and / or a non-anchor carrier) or a number of random access carriers corresponding to an improved coverage level n, The carrier corresponding to the value obtained by performing the modulo operation (mod) is used as a random access carrier. The UE identity may be a C-RNTI or S-TMSI or IMSI or other identities to distinguish between different UEs.

In an implementation, if the downlink carrier on which the UE receives the paging message on it is configured with a corresponding uplink carrier and the uplink carrier (which may be an uplink carrier corresponding to an anchor carrier or a non-anchor carrier) The random access carrier is an uplink carrier, i.e., a carrier on which the UE receives the paging message.

In an implementation, step S120 includes the steps of: if the downlink carrier on which the UE receives the paging message on it is not configured with a corresponding uplink carrier, or if the corresponding uplink carrier configured does not support random access, , Selecting an anchor carrier that supports random access indicated by the configuration information, or selecting the anchor carrier that supports the random access indicated by the configuration information, in a random selection scheme, in the same probability random selection scheme, or in accordance with predefined rules, Anchor carrier supporting access and / or one or more non-anchor carriers.

In an implementation, when the physical downlink control channel (PDCCH) or upper layer indicates a carrier for the UE to perform random access, the random access carrier is the indicated carrier. For example, if the PDCCH order or higher layer (e.g., RRC) indicates a carrier for the UE to perform random access, the UE performs random access on the indicated carrier. The PDCCH sequence may adopt the following method: returning the indication information in the DCI. The indication information may be indicative of the frequency of the uplink / downlink carrier over which the UE is performing random access, or any carrier in the anchor carriers and / or non-anchor carriers available for random access configured by the base station And an indication to indicate that it should be used as a random access carrier. For example, anchor carriers and / or non-anchor carriers are numbered according to the sequence of carriers appearing in the configuration list, of which the sequential number is indicated in the DCI.

In an implementation, the random access carrier is a non-anchor carrier with RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB information elements configured by the RRC.

In an implementation, if the serving carrier of the UE (e.g., the UE is capable of performing reception and / or transmission of unicast data on the carrier) supports random access (e.g., configured with random access resources) Is the serving carrier, i.e., the UE performs random access on the serving carrier. The serving carrier may be an anchor carrier or a non-anchor carrier.

If the serving carrier of the UE (i.e., the UE is capable of performing reception and / or transmission of unicast data on the carrier) is not used as a random access carrier (e.g., not configured as a random access resource) And may select a carrier available for random access in order to perform random access. Preferably, the UE performs random access on an anchor carrier (including uplink and downlink carriers). Alternatively, the carrier may be an anchor carrier supporting random access indicated by the configuration information and / or one or more < RTI ID = 0.0 > Are selected from non-anchor carriers. For example, for a UE identity having a number of random access carriers (which may include an anchor carrier and / or a non-anchor carrier) or a number of random access carriers corresponding to an improved coverage level n, mod ) Is used as a random access carrier. The UE identity may be a C-RNTI or S-TMSI or IMSI or other identities to distinguish between different UEs.

In an implementation, step S120 may comprise further selecting a random access carrier based on the improved coverage level of the UE.

For example, the UE may select a corresponding carrier as a random access carrier based on the measured signal strength (measured RSRP or improved coverage level). That is, the UE determines a corresponding random access carrier (a plurality of corresponding random access carriers may exist) according to the measured RSRP; And if there are a plurality of corresponding random access carriers, the UE may select the carriers in the same probability random selection manner or according to a set rule. The configuration rule may include using as a random access carrier a carrier corresponding to the value obtained by performing a modulo operation (mod) on the UE identity with the improved coverage level n. The UE identity may be a C-RNTI or S-TMSI or IMSI or other identities to distinguish between different UEs. Alternatively, if the UE determines that the improved coverage level is n (e.g., determines an improved coverage level according to the measured RSRP), the UE may send a random access carrier corresponding to the improved coverage level n Select. If there are a plurality of random access carriers (which may include an anchor carrier and / or a non-anchor carrier) corresponding to the improved coverage level n, then the UE may select the carrier in the same probability random selection manner, It is possible. The configuration rule may include using as a random access carrier a carrier corresponding to the value obtained by performing a modulo operation (mod) on the UE identity with the improved coverage level n. The UE identity may be a C-RNTI or S-TMSI or IMSI or other identities to distinguish between different UEs.

In an implementation, step S120 may comprise further selecting a random access carrier based on the data size. For example, the potential message size is compared with a predetermined threshold, and then the random access carrier is selected according to the result of the comparison.

In an implementation, the configuration information indicates one or more random access resource configurations for random access.

In an implementation, the configuration information includes an indication to indicate whether the corresponding non-anchor carrier shares the same random access resource configuration with an anchor carrier.

In an embodiment, the RACH-ConfigCommon-NB and / or the NPRACH-ConfigSIB-NB configuration of the anchor carrier is different from the RACH-ConfigCommon-NB and / or the NPRACH-ConfigSIB-NB configuration of the non-anchor carrier.

In an implementation, the NPRACH-ParametersList-NB configuration of the anchor carrier is different from the NPRACH-ParametersList-NB configuration of the non-anchor carrier.

In an implementation, one or more non-anchor carriers in one or more non-anchor carriers share the same random access resource configuration with an anchor carrier.

In an implementation, the random access resource configuration is RACH-ConfigCommon-NB; NPRACH-ConfigSIB-NB; Or NPRACH-ParametersList-NB.

In an implementation, the configuration information includes an indicator for indicating whether the corresponding anchor carrier or non-anchor carrier supports random access. When the value of the indicator is set to "True" or "Set up" or "1", the corresponding anchor carrier or non-anchor carrier supports random access; When the value of the indicator is set to " false " or " released " or " 0 ", the corresponding non-anchor carrier does not support random access.

In an implementation, the configuration information includes indicating whether the corresponding non-anchor carrier adopts the same random access resource configuration as that of an anchor carrier. When the value of the indicator is set to "True" or "Set up" or "1", the corresponding non-anchor carrier adopts the same random access resource configuration as that of the anchor carrier; If the value of the indication is set to " false ", " released ", or " 0 " or no indication is displayed, the corresponding non-anchor carrier adopts a random access resource configuration different from that of the anchor carrier.

In the example, the UE randomly selects from the anchor carriers and / or non-anchor carriers a carrier that can be used as random access carriers to perform random access.

In another example, when one or more non-anchor carriers available for random access are configured, the UE selects a non-anchor carrier from the non-anchor carriers as a random access carrier. Preferably, the UE randomly selects non-anchor carriers from non-anchor carriers as a random access carrier. Alternatively, the UE selects a non-anchor carrier as a random access carrier, according to predefined rules. For example, for a UE identity having a number of random access carriers (which may include an anchor carrier and / or a non-anchor carrier) or a number of random access carriers corresponding to an improved coverage level n, mod ) Is used as a random access carrier. The UE identity may be a C-RNTI or S-TMSI or IMSI or other identities to distinguish between different UEs.

In another example, when only one uplink carrier available for random access is configured, the UE performs random access on the uplink carrier. Preferably, the uplink carrier is an uplink carrier of the anchor carrier. Preferably, the UE uses the downlink carrier of the anchor carrier as a downlink carrier for performing random access. Alternatively, the UE may select the carrier from the downlink non-anchor carriers and / or the downlink anchor carriers configured as a downlink carrier for performing random access, for example, with the same probability random selection scheme. Optionally, the UE selects non-anchor carriers from the configured downlink non-anchor carriers and / or downlink anchor carriers as downlink carriers for random access, according to predefined rules. For example, for a UE identity having a number of random access downlink carriers (which may include anchor carriers and / or non-anchor carriers) or a number of random access downlink carriers corresponding to an improved coverage level n The carrier corresponding to the value obtained by performing the operation (mod) with the address is used as the random access carrier. The UE identity may be a C-RNTI or S-TMSI or IMSI or other identities to distinguish between different UEs.

In step S130, the UE performs random access by using a random access carrier.

A method for random access performed at a base station in accordance with an embodiment of the present invention will be described below with reference to FIG. 2 schematically illustrates a flow diagram of a method 200 for random access performed at a base station in accordance with an embodiment of the present invention.

As shown in FIG. 2, in step S210, the eNB generates configuration information. The configuration information indicates an anchor carrier that supports random access and / or one or more non-anchor carriers. For example, the configuration information herein may be the configuration information received by the UE from the eNB in step S110.

In step S220, the eNB transmits configuration information for the UE to perform random access to the UE.

Methods for configuring one or more non-anchor carriers as random access carriers and for configuring corresponding random access resources are described in detail below.

The configuration information of the non-anchor carrier includes one or more of the following information elements: RACH-ConfigCommonNonanchor-NB, NPRACH-ConfigSIBNonanchor-NB, NPRACH-ParametersListNonanchor-NB, and dl- CarrierFreq, downlinkBitmapNonAnchor, dl -GapNonAnchor, and inbandCarrierInfo, and UL-CarrierConfigDedicated-NB associated with the uplink carrier configuration. The information element dl-CarrierFreq is used to indicate a downlink carrier which is a physical resource block that is not used to transmit the E-UTRA PSS / SSS / PBCH; The information element downlinkBitmapNonAnchor is used to indicate the NB-IoT downlink subframe configuration of the downlink transmission of the non-anchor carrier; The information element DL-GapNonAnchor is used to indicate the downlink transmission gap configuration of the non-anchor carrier; The information element inbandCarrierInfo includes information elements defined in 3GPP standard TS 36.331, such as the configuration of in-band non-anchor carriers, e.g., indexToMidPRB, eutra-NumCRS-Ports, and eutraControlRegionSize; And the information element UL-CarrierConfigDedicated-NB is used to indicate the uplink carrier. The non-anchor carrier configuration information may be divided into two parts: non-anchor carrier common configuration information and non-anchor carrier dedicated configuration information. The non-anchor carrier common configuration information includes non-anchor carrier configuration information shared by all non-anchor carriers. The non-anchor carrier dedicated configuration information includes only applicable configuration information to the corresponding non-anchor carriers. For example, the non-anchor carrier common configuration information may include RACH-ConfigCommonNonanchor-NB and / or NPRACH-ConfigSIBNonanchor-NB and / or NPRACH-ParametersListNonanchor-NB and / or downlinkBitmapNonAnchor and / or DL-GapNonAnchor information elements ; And the configuration information of other non-anchor carriers not included in the non-anchor carrier common configuration information may be included in the non-anchor carrier dedicated configuration information. If the information element dl-CarrierFreq and / or the information element UL-CarrierConfigDedicated-NB are included in the non-anchor carrier common configuration information, it indicates that these non-anchor carriers may share the uplink carrier and / or the downlink carrier do. If the dedicated configuration information of each non-anchor carrier does not include the information element dl-CarrierFreq and / or the information element UL-CarrierConfigDedicated-NB and the information element is included in the common configuration information, the uplink carrier and / Or a downlink carrier may be employed; And if the dedicated configuration information of each non-anchor carrier does not include the information element dl-CarrierFreq and / or the information element UL-CarrierConfigDedicated-NB and the information element is also not included in the common configuration information, A carrier and / or downlink carrier may be employed. Optionally, if the dedicated configuration information of each non-anchor carrier further comprises a carrier indication information element, then the carrier indication information element indicates that the dedicated configuration information of some non-anchor carrier is information element dl-CarrierFreq and / or information element UL When not including -CarrierConfigDedicated-NB, it indicates whether the corresponding non-anchor carrier adopts uplink carrier and / or downlink carrier in common configuration information or adopts uplink carrier and / or downlink carrier of anchor carrier . Specifically, when the value of the indication information element is set to " True " or " Set up " or " 1 ", the UE selects the uplink carrier and / or downlink carrier in the common configuration information ; When the value of the indication information element is set to " false " or " released ", or when the indicator is absent, the UE determines that the corresponding non- ≪ / RTI > And vice versa.

Optionally, the non-anchor carrier configuration information further comprises a first indicator for indicating whether a corresponding non-anchor carrier can be used as a random access carrier; And the first indicator may be included in the non-anchor carrier dedicated configuration information. Specifically, when the value of the indicator is set to " true " or " set up " or " 1 ", the UE determines that the corresponding non-anchor carrier is a random access carrier (i.e., the UE can perform random access on the carrier) Determine that it can be used; When the value of the indicator is set to "false" or "released" or "0" or when the indicator is absent, the UE determines that the corresponding non-anchor carrier should not be used as a random access carrier; And vice versa.

Optionally, the non-anchor carrier configuration information may be used to indicate whether the corresponding non-anchor carrier adopts the random access resource configuration of the anchor carrier or to indicate whether the PSS / SSS / NPBCH / SIB-NB is transmitted on the non- (Where a non-anchor carrier may adopt a random access resource configuration of an anchor carrier when PSS / SSS / NPBCH / SIB-NB is transmitted on a non-anchor carrier). Specifically, when the value of the indicator is set to "True" or "Set up" or "1", the UE determines that the corresponding non-anchor carrier adopts the random access resource configuration of the anchor carrier; When the value of the indicator is set to "false" or "released" or "0" or when the indicator is absent, the UE determines that the corresponding non-anchor carrier does not adopt the random access resource configuration of the anchor carrier. The second indicator may be included in the non-anchor carrier dedicated configuration information.

Optionally, the non-anchor carrier configuration information may comprise a third (i. E., 3 < th > used for indicating the improved coverage level (number of repetitions or repetition level) of the UE, Lt; / RTI > Specifically, the UE compares the measured signal strength (e.g., RSRP value) with the value of the third indicator; And if the measured signal strength is greater or less than the value of the third indicator, the corresponding non-anchor carrier may be used as a random access carrier for the UE. The third indicator may be included in the non-anchor carrier dedicated configuration information.

Optionally, the configuration information indicates that the anchor carrier is a random access carrier (an uplink carrier on which the UE can transmit an uplink message, such as a preamble, and a downlink, such as a random access response (RAR) (E.g., a corresponding downlink carrier capable of receiving a message on it). Specifically, when the value of the indicator is set to " True " or " Set up " or " 1 ", the UE determines that an anchor carrier can be used as a random access carrier; When the value of the indicator is set to "false" or "released" or "0" or when the indicator is absent, the UE determines that the anchor carrier can not be used as a random access carrier; And vice versa.

Optionally, the configuration information further includes a threshold for the UE to select a carrier for performing random access. When the random access is triggered by a higher layer (e.g., a CCCH logical channel), the UE compares the size of a service data unit (SDU) of the CCCH plus MAC header with a threshold, And then selects a carrier for random access from the corresponding random access carriers. If the random access is not triggered by a higher layer (i.e., CCCH logical channel), the UE may compare the potential message size (which may compare the uplink transmission data plus MAC header plus MAC control element required to be transmitted) with a threshold And selects a carrier for random access from the corresponding random access carriers according to the comparison result. For example, if the size or potential message size of the SDU in the CCCH plus MAC header is lower than the threshold, the UE performs random access on the anchor carrier; If the size or potential message size of the SDU in the CCCH plus MAC header is greater than the threshold, the UE performs random access on the non-anchor carrier (e.g., if multiple non-anchor carriers are available from random access, One of the anchor carriers may be selected randomly or may be selected according to a predefined rule). For example, for a UE identity having a number of random access carriers (which may include an anchor carrier and / or a non-anchor carrier) or a number of random access carriers corresponding to an improved coverage level n, mod ) Is used as a random access carrier. The UE identity may be a C-RNTI or S-TMSI or IMSI or other identities to distinguish between different UEs; The reverse is also true.

Optionally, the configuration information includes configuration information of a plurality of sets of non-anchor carriers, and each set of non-anchor carriers may be configured by the UE at different coverage levels (number of iterations) . Each set of non-anchor carriers may also each be composed of different random access resources, and the plurality of sets of non-anchor carriers may share a portion of the random access resource configurations. For example, the plurality of sets of non-anchor carriers share RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB and / or NPRACH-ParametersList-NB.

Optionally, the configuration information further comprises an anchor carrier related random access resource configuration and a non-anchor carrier related random access resource configuration. Preferably, the anchor carrier and the non-anchor carrier may share portions of the parameters of the random access resource configuration. That is, the random access resource configurations of anchor carriers and non-anchor carriers include a common random access resource configuration portion and a dedicated random access resource configuration portion. The common random access resource configuration portion includes the random access resource configuration parameters applicable to the anchor carrier and the non-anchor carrier, while the random access resource configuration parameters included in the dedicated random access resource configuration portion include the anchor carrier or non-anchor carrier It is only applicable.

Specifically, the eNB configures a common RACH-ConfigCommon-NB for anchor carriers and all non-anchor carriers and configures NPRACH-ConfigSIBAnchor-NB and / or NPRACH-ParametersListAnchor-NB for anchor carriers; The eNB then configures NPRACH-ConfigSIBNonAnchor-NB and / or NPRACH-ParametersListNonAnchor-NB for non-anchor carriers.

Alternatively, the eNB may configure a common NPRACH-ConfigSIB-NB for anchor carriers and all non-anchor carriers, configure RACH-ConfigCommonAnchor-NB and / or NPRACH-ParametersListAnchor-NB for anchor carriers; The eNB then configures RACH-ConfigCommonNonAnchor-NB and / or NPRACH-ParametersListNonAnchor-NB for non-anchor carriers.

Alternatively, the eNB may construct a common NPRACH-ParametersList-NB for anchor carriers and all non-anchor carriers,

Configure RACH-ConfigCommonAnchor-NB and / or NPRACH-ConfigSIBAnchor-NB; The eNB then configures RACH-ConfigCommonNonAnchor-NB and / or NPRACH-ConfigSIBNonAnchor-NB for non-anchor carriers.

Alternatively, the eNB may configure a common RACH-ConfigCommon-NB and an NPRACH-ConfigSIB-NB for anchor carriers and all non-anchor carriers, and an NPRACH-ParametersListAnchor-NB for anchor carriers; The eNB then constructs an NPRACH-ParametersListNonAnchor-NB for non-anchor carriers.

Alternatively, the eNB may be used for anchor carriers and common for all non-anchor carriers

Configure NPRACH-ParametersList-NB and RACH-ConfigCommon-NB, configure NPRACH-ConfigSIBAnchor-NB for anchor carriers; The eNB then configures the NPRACH-ConfigSIBNonAnchor-NB for non-anchor carriers.

Alternatively, the eNB may be used for anchor carriers and common for all non-anchor carriers

Configure NPRACH-ParametersList-NB and NPRACH-ConfigSIB-NB, configure RACH-ConfigCommonAnchor-NB for anchor carriers; The eNB then configures the RACH-ConfigCommonNonAnchor-NB for non-anchor carriers.

Alternatively, the eNB may configure a common RACH-ConfigCommon-NB, NPRACH-ConfigSIB-NB, and NPRACH-ParametersList-NB for the anchor carrier and all non-anchor carriers. In this case, all of the anchor carriers and non-anchor carriers adopt the same random access resource configuration.

Alternatively, the eNB may configure a common RACH-ConfigCommonNonAnchor-NB and / or NPRACH-ConfigSIBNonAnchor-NB and / or NPRACH-ParametersListNonAnchor-NB for all non-anchor carriers.

Alternatively, the eNB may configure RACH-ConfigCommonNonAnchor-NB and / or NPRACH-ConfigSIBNonAnchor-NB and / or NPRACH-ParametersListNonAnchor-NB for each non-anchor carrier, respectively. Optionally, some or all of the random access resources (which may include RACH-ConfigCommonNonAnchor-NB and / or NPRACH-ConfigSIBNonAnchor-NB and / or NPRACH-ParametersListNonAnchor-NB) available for random access It is contemplated that the random access resources of the corresponding non-anchor carriers are configured identically for the random access resources of the anchor carriers.

Alternatively, the eNB may include configuration information of a non-anchor carrier in one or a plurality of separate information elements, and may include configuration of one or more random access resources in one or more other separate information elements And may then display each of the non-anchor carriers to which the corresponding random access resource should be applied, in each of the configured random access resources. For example, five non-anchor carriers are configured and the configuration information of the non-anchor carriers includes the following information elements: dl-CarrierFreq, downlinkBitmapNonAnchor, dl-GapNonAnchor, and inbandCarrierInfo associated with the downlink carrier configuration, CarrierConfigDedicated-NB related to the configuration; It is assumed that three random access resources are configured and the random access resources include some or all of the following information elements: RACH-ConfigCommonNonanchor-NB, NPRACH-ConfigSIBNonanchor-NB, and NPRACH-ParametersListNonanchor-NB. The eNB indicates, in the random access resources, non-anchor carriers for which random access resources should be applied, respectively. Specifically, the configured non-anchor carriers may be represented in the form of a bitmap; Or configured non-anchor carriers may be numbered, and then the numbers are displayed.

Random access resources (which may include RACH-ConfigCommonNonAnchor-NB and / or NPRACH-ConfigSIBNonAnchor-NB and / or NPRACH-ParametersListNonAnchor-NB) are not included in the configuration information corresponding to the anchor carrier and non- It should be noted that the individual random access resources of the anchor carrier and the non-anchor carrier exist as common information in the form of a list in which the random access resources in the corresponding list should be displayed, respectively. Specifically, assuming that the list includes two RACH-ConfigCommonNonAnchor-NB and / or two NPRACH-ConfigSIBNonAnchor-NB and / or two NPRACH-ParametersListNonAnchor-NB, the first RACH- / Or NPRACH-ConfigSIBNonAnchor-NB and / or NPRACH-ParametersListNonAnchor-NB may be specified as a random access resource configuration of an anchor carrier; The second RACH-ConfigCommonNonAnchor-NB and / or NPRACH-ConfigSIBNonAnchor-NB and / or NPRACH-ParametersListNonAnchor-NB in the list may be specified as a random access resource configuration of the non-anchor carrier; And vice versa.

A UE according to an embodiment of the present invention will be described below with reference to FIG. 3 schematically illustrates a structural block diagram of a UE 300 in accordance with an embodiment of the present invention. The UE 300 may perform a method for random access, for example, the method 100 described in detail previously, as shown in FIG. 1, in accordance with an embodiment of the present invention.

3, the UE 300 includes a receiving unit 310, a selecting unit 320, and a random access executing unit 330. [ Those skilled in the art will appreciate that only the receiving unit 310, the selecting unit 320, and the random access executing unit 330 related to the present invention may be used in the UE 300 of FIG. 3 to avoid the confusion of the present invention. And the like. However, it is to be understood that although a person skilled in the art will not be shown in FIG. 3, a UE according to an embodiment of the present invention further includes other basic units forming the UE.

Receiving unit 310 is configured to receive configuration information from a base station, and the configuration information indicates an anchor carrier that supports random access and / or one or more non-anchor carriers.

The selection unit 320 is configured, as a random access carrier, to select a carrier from the anchor carriers that support random access and / or from one or more non-anchor carriers, depending on the configuration information.

The random access execution unit 330 is configured to perform random access by using a random access carrier.

In an embodiment, the selection unit 320 may be implemented as a random selection scheme, an equal probability random selection scheme, or according to predefined rules, as a random access carrier, an anchor carrier supporting random access indicated by configuration information, and / And is further configured to select a carrier from one or more non-anchor carriers.

In an embodiment, the random access carrier is an uplink carrier if the downlink carrier on which the UE receives the paging message on it is configured with a corresponding uplink carrier, and the uplink carrier supports random access.

In an implementation, if the downlink carrier on which the UE receives the paging message on it is not configured with a corresponding uplink carrier, or if the corresponding uplink carrier configured does not support random access, An anchor carrier that supports random access indicated by the configuration information, a random access method, a random probability selection method, or a random access carrier indicated by a configuration information in accordance with a predefined rule And / or one or more non-anchor carriers.

In an implementation, when a physical downlink control channel (PDCCH) or higher layer specifies a carrier for a UE to perform random access, the random access carrier is a specified carrier.

In an implementation, the random access carrier is a non-anchor carrier with RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB information elements configured by the RRC.

In an implementation, when the serving carrier of the UE supports random access, the random access carrier is a serving carrier.

In an implementation, the selection unit 320 is further configured to further select a random access carrier based on the improved coverage level of the UE.

In an implementation, the selection unit 320 is further configured to further select a random access carrier based on the data size.

In an embodiment, selecting a random access carrier based on data size may include comparing a potential message size with a predetermined threshold; And selecting a random access carrier according to the comparison result.

In an implementation, the configuration information indicates one or more random access resource configurations for random access.

In an implementation, the configuration information includes an indication to indicate whether the corresponding non-anchor carrier shares the same random access resource configuration with an anchor carrier.

In an embodiment, the RACH-ConfigCommon-NB and / or the NPRACH-ConfigSIB-NB configuration of the anchor carrier is different from the RACH-ConfigCommon-NB and / or the NPRACH-ConfigSIB-NB configuration of the non-anchor carrier.

In an implementation, the NPRACH-ParametersList-NB configuration of the anchor carrier is different from the NPRACH-ParametersList-NB configuration of the non-anchor carrier.

In an implementation, one or more non-anchor carriers in one or more non-anchor carriers share the same random access resources with an anchor carrier.

In an implementation, the random access resource configuration is RACH-ConfigCommon-NB; NPRACH-ConfigSIB-NB; Or NPRACH-ParametersList-NB.

In an implementation, the configuration information includes an indicator for indicating whether the corresponding anchor carrier or non-anchor carrier supports random access. When the value of the indicator is set to "True" or "Set up" or "1", the corresponding anchor carrier or non-anchor carrier supports random access; When the value of the indicator is set to " false " or " released " or " 0 ", the corresponding non-anchor carrier does not support random access.

In an implementation, the configuration information includes indicating whether the corresponding non-anchor carrier adopts the same random access resource configuration as that of an anchor carrier. When the value of the indicator is set to "True" or "Set up" or "1", the corresponding non-anchor carrier adopts the same random access resource configuration as that of the anchor carrier; If the value of the indication is set to " false ", " released ", or " 0 " or no indication is displayed, the corresponding non-anchor carrier adopts a random access resource configuration different from that of the anchor carrier.

A base station according to an embodiment of the present invention will be described below with reference to FIG. 4 schematically illustrates a structural block diagram of a base station 400 in accordance with an embodiment of the present invention. The base station 400 may perform a method for random access, for example, the method 200 described in detail previously, as illustrated in FIG. 2, in accordance with an embodiment of the present invention.

As shown in FIG. 4, the base station 400 includes a generating unit 410 and a transmitting unit 420. It should be appreciated by those of ordinary skill in the art that only the generating unit 410 and the transmitting unit 420 related to the present invention are shown in the base station 400 of FIG. 4 to avoid confusion of the present invention. It should be understood, however, that although the artisan of ordinary skill in the art is not shown in FIG. 4, the base station in accordance with an embodiment of the present invention further includes other basic units forming a base station.

The generating unit 410 is configured to generate configuration information, and the configuration information indicates an anchor carrier that supports random access and / or one or more non-anchor carriers.

The transmission unit 420 is configured to transmit configuration information to the user equipment (UE) for the UE to perform random access.

In an implementation, the transmission unit 420 may broadcast configuration information in the system information; Or to transmit configuration information by using RRC dedicated signaling.

A random access method in the switching scenario, i. E., A process in which the UE randomly accesses the target base station during the switching process from the source base station to the target base station is provided below. A method for determining if an anchor carrier or a non-anchor carrier is a carrier supporting random access, and a method for determining whether a UE supports one or more non-anchors that support random access to perform the random access involved in the following embodiments. Selection methods for selecting non-anchor carriers from carriers include, but are not limited to those previously described in the present invention, and are not repeatedly described in the following embodiments.

In the present invention, a carrier may also be represented as a cell or a physical resource block (PRB).

A method for random access performed in a UE according to an embodiment of the present invention will be described below with reference to FIG. 5 schematically illustrates a flow diagram of a method 500 for random access performed in a UE according to an embodiment of the present invention.

As shown in FIG. 5, in step S510, the UE receives a switching command message from the eNB. The switching command message includes information for the target anchor carrier, that is, information for displaying the target carrier or the target cell for the current switching. At this stage, a switching command message is used to instruct the UE to perform the switching operation. For example, the switching command message may be an RRC connection reconfiguration message that includes a mobility control information element. Optionally, the switching command message may be used to configure a non-anchor carrier (also referred to as a target non-anchor carrier) to be used by the UE during or after the current switching process, It may also include anchor carrier configuration information.

In step S520, the UE determines, based on the switching command message, whether to use a target anchor carrier or a non-anchor carrier to perform random access.

Optionally, prior to S520, the UE begins to perform downlink synchronization to synchronize to the target anchor carrier, and / or receives system information on the target anchor carrier. The system information herein includes non-anchor carrier configuration information including the RACH configuration corresponding to the non-anchor carrier and the PRACH configuration, for example, associated information to be acquired in order to perform random access on the target non-anchor carrier . For example, the non-anchor carrier configuration information may include non-anchor carrier frequency or index number, indication information for indicating whether the non-anchor carrier is a random access carrier, downlinkBitmapNonAnchor, dl-GapNonAnchor, inbandCarrierInfo configurations, and so on. For specific details, reference is made to the above-mentioned random access configuration section of the present invention. Alternatively, the UE may obtain the relevant information to be acquired in order to perform random access on the target non-anchor carrier, e.g., from the eNB with a switching command, by dedicated signaling.

In an implementation, step S520 may comprise determining to use a target anchor carrier to perform random access if the switching command message does not include non-anchor carrier configuration information for the target non-anchor carrier have.

For example, if the switching command message does not include non-anchor carrier configuration information, the UE may perform one or more of the following actions:

Determining that the UE has a dedicated random access channel configuration for a target anchor carrier if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- The UE performs random access on the target anchor carrier.

In an implementation, step S520 includes the step of determining whether the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and wherein the switching command message or target cell system information includes random access configuration information , It may be determined to use a target anchor carrier to perform random access.

For example, if the switching command message includes non-anchor carrier configuration information and the switching command message or target cell system information corresponds to the target non-anchor carrier (e.g., random access configuration information is nprach-config and / / RTI > and / or rach-configcommon), the UE performs one or more of the following actions:

Determining that the UE has a dedicated random access channel configuration for a target anchor carrier if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- The UE performs random access on the target anchor carrier.

In an implementation, step S520 may comprise the step of determining if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and the target non-anchor carrier indicated by the non-anchor carrier configuration information does not support random access , It may be determined to use a target anchor carrier to perform random access.

For example, if the switching command message includes non-anchor carrier configuration information and the target non-anchor carrier indicated by the non-anchor carrier configuration information is not a random access carrier, the UE performs one or more of the following actions do:

- determining that the UE has a dedicated random access channel configuration for an anchor carrier if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- The UE performs random access on the target anchor carrier.

In this embodiment, the anchor carrier refers to the target anchor carrier; The fact that the non-anchor carrier is not a random access carrier may be learned from indication information received from the eNB, or may be learned based on the fact that the random access carrier list received from the eNB does not include non-anchor carriers, May be learned based on the fact that the non-anchor carrier list received from the non-anchor carrier includes a non-anchor carrier, but does not include a RA carrier indication (e.g., the first indicator) corresponding to the non-anchor carrier. However, the present invention is not limited to the above-described methods.

In an implementation, step S520 includes the step of determining whether the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and wherein the switching command message or target cell system information includes random access configuration information , Determining to use a target non-anchor carrier to perform random access.

For example, if the switching command message includes non-anchor carrier configuration information and the switching command message or target cell system information corresponds to the target non-anchor carrier (e.g., random access configuration information is nprach-config and / / RTI > and / or rach-configcommon), the UE performs one or more of the following actions:

Determining that the UE has a dedicated random access channel configuration for a non-anchor carrier if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- the UE performing random access on the target non-anchor carrier.

In an implementation, step S520 further comprises the steps of: if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and the target non-anchor carrier indicated by the non-anchor carrier configuration information supports random access, And determining to use a target non-anchor carrier to perform random access.

For example, if the switching command message includes non-anchor carrier configuration information, the UE performs one or more of the following actions:

Determining that the UE has a dedicated random access channel configuration for a target non-anchor carrier if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- the UE performing random access on the target non-anchor carrier.

In an implementation, step S520 includes determining to use a target non-anchor carrier to perform random access if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier It is possible.

For example, if the switching command message includes non-anchor carrier configuration information and the target non-anchor carrier indicated by the non-anchor carrier configuration information supports random access, then the UE performs one or more of the following actions :

Determining that the UE has a dedicated random access channel configuration for a non-anchor carrier if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- the UE performing random access on the target non-anchor carrier.

In this embodiment, although the target non-anchor carrier supports random access may be learned in accordance with explicit indication information received from the eNB, the present invention is not limited to this method.

In an implementation, step S520 may include determining that the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier, and that the switching command message or target cell system information indicates that the target anchor carrier does not support random access Anchor carrier configuration information indicates that the target non-anchor carrier does not support random access, a non-anchor carrier is selected from one or more carriers that support random access to perform random access ≪ / RTI >

For example, an indication to indicate that the switching command message includes non-anchor carrier configuration information and that the switching command message or target cell system information does not support random access (e.g., the fourth indicator ), The UE performs one or more of the following actions:

If the target non-anchor carrier supports random access, then

If the switching command message includes a dedicated random access channel configuration (RACH-ConfigDedicated), the UE determines that the dedicated random access channel configuration is for a target non-anchor carrier; And

The UE performs random access on the target non-anchor carrier; or

If the target non-anchor carrier does not support random access, then

The UE may select as a random access carrier a non-anchor carrier from one or more carriers that support random access (e.g., selecting a non-anchor carrier by using the method 100 in FIG. 1) Lt; / RTI > And

Determining that the UE is for a non-anchor carrier with a dedicated random access channel configuration if the switching command message includes a dedicated random access channel configuration (RACH-ConfigDedicated); And

The UE performs random access on the selected non-anchor carrier.

In an implementation, step S520 may be performed in which the switching command message does not include non-anchor carrier configuration information for the target non-anchor carrier, and / or the switching command message or target cell system information indicates that the target anchor carrier < And selecting non-anchor carriers for random access from one or more carriers that support random access when indicating that the non-anchor carriers are not supported.

For example, if the switching command message does not include non-anchor carrier configuration information and / or the switching command message or target cell system information indicates that the target anchor carrier does not support random access, Performs a plurality of the following operations:

- UE selecting as a random access carrier one non-anchor carrier from one or more carriers supporting random access (e.g., using a method 100 in FIG. 1 for a non-anchor carrier) ≪ / RTI > And

Determining that the UE is for a non-anchor carrier with a dedicated random access channel configuration if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- The UE performs random access on the selected non-anchor carrier.

In an implementation, step S520 includes the step of determining whether the switching command message comprises non-anchor carrier configuration information for the target non-anchor carrier, and wherein the switching command message or target cell system information comprises a random access configuration And may include selecting a non-anchor carrier from one or more carriers that support random access to perform random access if it does not include the message.

For example, if the switching command message includes non-anchor carrier configuration information and the switching command message or target cell system information corresponds to the target non-anchor carrier (e.g., random access configuration information is nprach-config and / / Or rach-configcommon, etc.), the UE performs one or more of the following actions:

- UE selecting as a random access carrier a non-anchor carrier from one or more carriers supporting random access (e.g., selecting a non-anchor carrier by using method 100 in FIG. 1) Lt; / RTI > And

Determining that the UE is for a non-anchor carrier with a dedicated random access channel configuration if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- The UE performs random access on the selected non-anchor carrier.

In an implementation, step S520 includes the steps of: if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and if the target non-anchor carrier does not support random access, And selecting non-anchor carriers from the one or more carriers that support the access.

For example, if the switching command message includes non-anchor carrier configuration information and the target non-anchor carrier does not support random access, the UE performs one or more of the following actions:

- UE selecting as a random access carrier a non-anchor carrier from one or more carriers supporting random access (e.g., selecting a non-anchor carrier by using method 100 in FIG. 1) Lt; / RTI > And

Determining that the UE is for a non-anchor carrier with a dedicated random access channel configuration if the switching command message comprises a dedicated random access channel configuration (RACH-ConfigDedicated); And

- The UE performs random access on the selected non-anchor carrier.

In step S530, the UE performs random access by using a target anchor carrier or a non-anchor carrier according to the determination result.

In the above embodiments, the carrier used to perform the random access (process) may be actually considered as the carrier pair including the downlink carrier and the corresponding uplink carrier. Thus, the performance of random access on a carrier as described in the present invention can be achieved by transmitting a preamble and / or MSG3 on the uplink carrier of the carrier pair, and transmitting the RAR and / Or < / RTI > receiving MSG4.

In an implementation, if the switching command message includes RACH-ConfigDedicated configuration information, the RACH-ConfigDedicated configuration information is valid for the determined target anchor carrier or non-anchor carrier. In this case, step S530 may include sending a preamble and / or MSG3 message to the target base station on the determined uplink carrier associated with the determined target anchor carrier or non-anchor carrier; And receiving the RAR and / or MSG4 message from the target base station on the downlink carrier associated with the determined target anchor carrier or non-anchor carrier.

In an implementation, the non-anchor carrier configuration information is included in the radioresource-configdedicated information element or the physicalconfig-dedicated information element of the switching command message.

In an implementation, the switching command message is an RRC connection reconfiguration message that includes mobility control information.

Based on the above embodiment, optionally, the present invention may further include the following UE behaviors.

UE Behavior 1: After MSG3 is transmitted, if the UE is an NB-IoT UE and is configured with a non-anchor carrier and the current random access process is triggered by switching (RRC message), within the PDCCH transmission received on the anchor carrier It is contemplated that the included UL grant or DL assignment is valid for non-anchor carriers.

UE behavior 2: UE is an NB-IoT UE and is configured with a non-anchor carrier; When the random access preamble is transmitted on the anchor carrier, the UE determines that the UL grant included in the RAR is valid for the non-anchor carrier.

UE behavior 3: With respect to the NB-IoT UE, if the switching command message (i.e., the RRC connection reconfiguration message including the mobility control information element) includes a non-anchor carrier configuration (carrierConfigDedicated) The new carrier is immediately used after the last transmission block carrying the subsequent RRC response message corresponding to the process is confirmed by the MAC layer. This UE behavior is for situations where the UE is configured with non-anchor carriers in the switching command, and the random access process during switching is performed on the target anchor carrier.

UE behavior 4: UE is an NB-IoT UE and is configured with a non-anchor carrier; With respect to non-contention-based random access, when transmitted on another non-anchor carrier that supports random access different from the non-anchor carrier configured with a random access preamble, - It is determined to be valid for the anchor carrier.

UE behavior 5: UE is an NB-IoT UE and is configured with a non-anchor carrier; In connection with contention-based random access, when a random access preamble is transmitted on another non-anchor carrier that supports random access, different from the configured non-anchor carrier, the UE may transmit a preamble on it or perform random access It is determined that the UL acknowledgment or DL allocation included in the received PDCCH transmission on the non-anchor carrier is valid for the non-anchor carrier configured.

UE behaviors 4 and 5 are for situations where the UE is configured as a non-anchor carrier but the configured non-anchor carrier does not support random access and the random access process is for another non-anchor carrier Lt; / RTI >

To support random access on non-anchor carriers, the present invention further proposes the following embodiments.

In an embodiment, all steps of the UE's random access process are performed on the same carrier (i. E., Referring to the carrier pair herein, including uplink and downlink carriers). Specifically, the carrier (pair) on which the subsequent steps of the random access process are performed on is the same as the carrier (pair) on which the preamble is transmitted. In this case, in a random access process performed on a non-anchor carrier, the UE determines that the UL grant included in the RAR is valid for the non-anchor carrier; And the UE determines that the UL grant or DL assignment included in the received PDCCH transmission after transmission of MSG3 is valid for the non-anchor carrier.

A method for random access performed in a base station according to an embodiment of the present invention will be described below with reference to Figs. 6 and 7. Fig. 6 schematically illustrates a flow diagram of a method 600 for random access performed at a source base station in accordance with an embodiment of the present invention. 7 schematically illustrates a flow diagram of a method 700 for random access performed at a target base station in accordance with an embodiment of the present invention.

As shown in FIG. 6, in step S610, the source eNB generates a switching command message. The switching command message includes information about the target anchor carrier (i. E., Information for indicating the target carrier or target cell for the current switching), or the switching command message includes information about the target anchor carrier, and the target non- (I.e., information for configuring the non-anchor carrier (also referred to as target non-anchor carrier) used by the user equipment UE during or after the current switching process) .

In step S620, the source eNB sends a switching command message to the UE such that the UE may use a target anchor carrier, a target non-anchor carrier, or a non-anchor carrier selected from one or more carriers supporting random access Thereby performing random access. The switching command message is used to instruct the UE to perform the switching operation. For example, the switching command message may be an RRC connection reconfiguration message that includes a mobility control information element.

In an implementation, the non-anchor carrier configuration information is included in the radioresource-configdedicated information element or the physicalconfig-dedicated information element of the switching command message.

As shown in FIG. 7, in step S710, the source eNB determines whether to receive random access from the UE on the target anchor carrier or non-anchor carrier, based on switching related information. The switching related information includes information about the target anchor carrier.

Optionally, in step S710, the target eNB may also send to the UE by dedicated signaling, e.g., with a switching command, the relevant information to be acquired in order to perform random access on the target non-anchor carrier. The relevant information to be acquired in order to perform random access on the target non-anchor carrier is, for example, non-anchor carrier configuration information including a RACH configuration and a PRACH configuration corresponding to non-anchor carriers. The non-anchor carrier configuration information may include, for example, non-anchor carrier frequency or index number, indication information for indicating whether the non-anchor carrier is a random access carrier, downlinkBitmapNonAnchor, dl-GapNonAnchor, inbandCarrierInfo configurations, and so on.

In an implementation, step S710 determines whether to receive random access on the target anchor carrier or to respond to random access if the switching related information does not include non-anchor carrier configuration information for the target non-anchor carrier ≪ / RTI >

In an implementation, step S710 is a step S710 where the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and the switching related information or target cell system information includes the random access configuration information corresponding to the target non- (E.g., random access configuration information may include nprach-config and / or rach-configcommon), it may be determined to receive random access on the target anchor carrier or to respond to random access It is possible.

In an implementation, step S710 may comprise the step of determining if the switching related information includes non-anchor carrier configuration information for the target non-anchor carrier and the target non-anchor carrier indicated by the non-anchor carrier configuration information does not support random access , It may comprise determining to receive random access on the target anchor carrier or to respond to random access.

In an implementation, step S710 is a step S710 where the switching related information includes non-anchor carrier configuration information for the target non-anchor carrier and the switching related information or the target cell system information includes the random access configuration information corresponding to the target non- (E.g., random access configuration information may include nprach-config and / or rach-configcommon) to determine whether to receive random access on the target non-anchor carrier or to respond to random access You may.

In an implementation, step S710 may comprise the steps of: if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and the target non-anchor carrier indicated by the non-anchor carrier configuration information supports random access, Determining to receive random access on the target non-anchor carrier or to respond to random access.

In an implementation, step S710 determines whether to receive random access on the target non-anchor carrier or to respond to random access if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier . ≪ / RTI >

In an implementation, step S710 determines whether the switching related information includes non-anchor carrier configuration information for the target non-anchor carrier and whether switching related information or target cell system information indicates that the target anchor carrier does not support random access Anchor carrier configuration information indicating that the target non-anchor carrier does not support random access, and responding to random access or receiving random access on a non-anchor carrier that supports random access You may.

For example, if switching related information includes non-anchor carrier configuration information and switching related information or target cell system information indicates that the target anchor carrier does not support random access (e.g., supported by a different fourth indicator) When displayed, the target eNB performs the following actions:

- if the target non-anchor carrier supports random access, the target eNB receives random access on the target non-anchor carrier or responds to random access; And

- when the target non-anchor carrier does not support random access, the target eNB receives random access or responds to random access on a non-anchor carrier supporting random access.

In an implementation, step S710 may comprise the step of determining whether the switching related information does not include non-anchor carrier configuration information for the target non-anchor carrier and / or wherein the switching command message or target cell system information is configured such that the target anchor carrier supports random access , It may include receiving random access on a non-anchor carrier supporting random access or responding to random access.

In an implementation, step S710 is a step S710 where the switching related information includes non-anchor carrier configuration information for the target non-anchor carrier and the switching related information or the target cell system information includes the random access configuration information corresponding to the target non- (For example, random access configuration information may include nprach-config and / or rach-configcommon), it may be possible to receive random access on a non-anchor carrier that supports random access, ≪ / RTI >

In an implementation, step S710 may include the step of, if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and if the target non-anchor carrier does not support random access, Receiving random access on an anchor carrier or responding to random access.

In step S720, the target eNB receives random access from the UE or responds to random access on the target anchor carrier or non-anchor carrier according to the determination result.

In an implementation, if the switching command message includes RACH-ConfigDedicated configuration information, the RACH-ConfigDedicated configuration information is valid for the determined target anchor carrier or non-anchor carrier. In this case, step S720 may include receiving a preamble and / or MSG3 message from the UE on the determined uplink carrier associated with the determined target anchor carrier or non-anchor carrier; And sending the RAR and / or MSG4 message to the UE on a downlink carrier associated with the determined target anchor carrier or non-anchor carrier.

A UE according to an embodiment of the present invention will be described below with reference to FIG. FIG. 8 schematically illustrates a structural block diagram of a UE 800 in accordance with an embodiment of the present invention. The UE 800 may perform a method for random access according to an embodiment of the present invention, for example, the method 500 described in detail previously as shown in FIG.

8, the UE 800 includes a receiving unit 810, a determining unit 820, and a random access executing unit 830. [ Those skilled in the art will appreciate that only the receiving unit 810, the determining unit 820, and the random access executing unit 830 related to the present invention may be used in the UE 800 of FIG. 8 to avoid the confusion of the present invention. And the like. However, it is to be understood that although a person of ordinary skill in the art is not shown in FIG. 8, the UE according to an embodiment of the present invention further includes other basic units forming the UE.

Receiving unit 810 is configured to receive a switching command message from the source base station. The switching command message includes information about the target anchor carrier.

The determination unit 820 is configured to determine, based on the switching command message, whether to use a target anchor carrier or a non-anchor carrier to perform random access.

The random access execution unit 830 is configured to perform random access by using a target anchor carrier or a non-anchor carrier according to the determination result.

In an implementation, the decision unit 820 may further determine to use a target anchor carrier to perform random access if the switching command message does not include non-anchor carrier configuration information for the target non-anchor carrier do.

In an implementation, decision unit 820 may determine that the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and that the switching command message or target cell system information corresponds to the target non- If it does not contain information, it is further configured to use a target anchor carrier to perform random access.

In an implementation, decision unit 820 determines that the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and that the target non-anchor carrier indicated by the non-anchor carrier configuration information does not support random access If not, to use a target anchor carrier to perform random access.

In an implementation, decision unit 820 may determine that the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and that the switching command message or target cell system information corresponds to the target non- Anchor < / RTI > carrier to perform random access, if the target non-anchor carrier is included.

In an implementation, decision unit 820 determines if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and the target non-anchor carrier indicated by the non-anchor carrier configuration information supports random access , And to use the target non-anchor carrier to perform random access.

In an implementation, decision unit 820 may further determine to use a target non-anchor carrier to perform random access if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier .

In an implementation, decision unit 820 determines that the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and that the switching command message or target cell system information indicates that the target anchor carrier does not support random access And indicates that the non-anchor carrier configuration information indicates that the target non-anchor carrier does not support random access, from the one or more carriers supporting random access to perform random access, . ≪ / RTI >

In an implementation, decision unit 820 determines that the switching command message does not include non-anchor carrier configuration information for the target non-anchor carrier, and / or the switching command message or target cell system information indicates that the target anchor carrier is a random access Anchor carrier from one or more carriers that support random access to perform random access when indicating that the non-anchor carrier is not supported.

In an implementation, decision unit 820 may determine that the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and that the switching command message or target cell system information is a random access Anchor carrier from one or more carriers that support random access in order to perform random access if it does not include a configuration message.

In an implementation, decision unit 820 determines if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and if the target non-anchor carrier does not support random access, And is further configured to select a non-anchor carrier from one or more carriers that support random access.

In an implementation, the non-anchor carrier configuration information is included in the radioresource-configdedicated information element or the physicalconfig-dedicated information element of the switching command message.

In an implementation, the switching command message is an RRC connection reconfiguration message that includes mobility control information.

In an implementation, if the switching command message includes RACH-ConfigDedicated configuration information, the RACH-ConfigDedicated configuration information is valid for the determined target anchor carrier or non-anchor carrier. In this case, the random access enforcement unit 830 sends a preamble and / or MSG3 message to the target base station on the determined uplink carrier associated with the determined target anchor carrier or non-anchor carrier; And to receive the RAR and / or MSG4 message from the target base station on the downlink carrier associated with the determined target anchor carrier or non-anchor carrier.

A base station according to an embodiment of the present invention will be described below with reference to FIG. 9 schematically illustrates a structural block diagram of a source base station 900 in accordance with an embodiment of the present invention. The source base station 900 may perform a method for random access, for example, the method 600 described in detail previously, as illustrated in FIG. 6, in accordance with an embodiment of the present invention.

As shown in FIG. 9, the source base station 900 includes a generating unit 910 and a transmitting unit 920. Those skilled in the art should understand that only the generating unit 910 and the transmitting unit 920 relating to the present invention are shown in the source base station 900 of FIG. 9 to avoid confusion of the present invention. It should be understood, however, that although the artisan of ordinary skill in the art is not shown in FIG. 9, the base station in accordance with an embodiment of the present invention further includes other basic units forming a base station.

The generating unit 910 is configured to generate a switching command message. The switching command message includes information about the target anchor carrier, or the switching command message includes information about the target anchor carrier and non-anchor carrier configuration information for the target non-anchor carrier.

The transmitting unit 920 is configured to send a switching command message to a user equipment (UE) such that the UE can receive a target anchor carrier, a target non-anchor carrier, or a non-anchor carrier selected from one or more carriers that support random access Carriers are used to perform random access.

In an implementation, the non-anchor carrier configuration information is included in the radioresource-configdedicated information element or the physicalconfig-dedicated information element of the switching command message.

In an implementation, the switching command message is an RRC connection reconfiguration message that includes mobility control information.

A base station according to an embodiment of the present invention will be described below with reference to FIG. 10 schematically illustrates a structural block diagram of a target base station 1000 in accordance with an embodiment of the present invention. The target base station 1000 may perform a method for random access according to an embodiment of the present invention, for example, the method 700 described in detail previously, as shown in FIG.

As shown in FIG. 10, the target base station 1000 includes a determination unit 1010 and a random access execution unit 1020. Those skilled in the art should understand that only the decision unit 1010 and the random access execution unit 1020 relating to the present invention are shown in the target base station 1000 of FIG. 10 to avoid confusion of the present invention. It should be understood, however, that although the artisan of ordinary skill in the art is not shown in FIG. 10, the base station in accordance with embodiments of the present invention further includes other basic units forming a base station.

The determination unit 1010 is configured to determine, based on the switching related information, whether to receive random access from the user equipment (UE) on the target anchor carrier or non-anchor carrier. The switching related information includes information about the target anchor carrier.

The random access execution unit 1020 is configured to receive random access from the UE or respond to random access on the target anchor carrier or non-anchor carrier according to the determination result.

In an implementation, decision unit 1010 determines whether to receive random access on the target anchor carrier or to respond to random access if the switching related information does not include non-anchor carrier configuration information for the target non-anchor carrier .

In an implementation, the determination unit 1010 determines whether the switching command message includes non-anchor carrier configuration information for a target non-anchor carrier and the switching related information or target cell system information is a random access configuration corresponding to a target non- Information is not included, it is further configured to determine whether to receive random access on the target anchor carrier or to respond to random access.

In an implementation, decision unit 1010 determines that the switching related information includes non-anchor carrier configuration information for the target non-anchor carrier and that the target non-anchor carrier indicated by the non-anchor carrier configuration information does not support random access If not, to receive random access on the target anchor carrier or to respond to random access.

In an implementation, the determination unit 1010 determines whether the switching related information includes non-anchor carrier configuration information for the target non-anchor carrier and the switching related information or the target cell system information is a random access configuration corresponding to the target non- Information is included, it is further configured to determine to receive random access on the target non-anchor carrier or to respond to random access.

In an implementation, decision unit 1010 determines if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier and the target non-anchor carrier indicated by the non-anchor carrier configuration information supports random access , And is further configured to determine to receive random access on the target non-anchor carrier or to respond to random access.

In an implementation, decision unit 1010 receives random access on the target non-anchor carrier or responds to random access if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier .

In an implementation, decision unit 1010 determines that the switching related information includes non-anchor carrier configuration information for the target non-anchor carrier and that switching related information or target cell system information indicates that the target anchor carrier does not support random access Anchor carrier configuration information indicating that the target non-anchor carrier does not support random access, and to receive random access on a non-anchor carrier that supports random access or to add .

In an implementation, the determination unit 1010 determines that the switching related information does not include non-anchor carrier configuration information for the target non-anchor carrier and / or the switching command message or target cell system information indicates that the target anchor carrier has random access And is further configured to receive random access on the non-anchor carrier supporting random access or to respond to random access if it indicates that it does not.

In an implementation, the determination unit 1010 determines whether the switching related information includes non-anchor carrier configuration information for the target non-anchor carrier and the switching related information or the target cell system information is a random access configuration corresponding to the target non- And is further configured to receive or respond to random access on a non-anchor carrier that supports random access if it does not include information.

In an implementation, the determination unit 1010 determines whether the non-anchor carrier configuration information includes a non-anchor carrier configuration information if the switching command message includes non-anchor carrier configuration information for the target non-anchor carrier, - is further configured to receive random access on an anchor carrier or to respond to random access.

In an implementation, if the switching command message includes RACH-ConfigDedicated configuration information, the RACH-ConfigDedicated configuration information is valid for the determined target anchor carrier or non-anchor carrier. In this case, random access enforcement unit 1020 receives the preamble and / or MSG3 message from the UE on the determined uplink carrier associated with the determined target anchor carrier or non-anchor carrier; And to forward the RAR and / or MSG4 message to the UE on the downlink carrier associated with the determined target anchor carrier or non-anchor carrier.

Certain embodiments of the present invention are disclosed in detail above with reference to the accompanying drawings; And ways in which the principles of the present invention are employed are exemplified. It is to be understood that the embodiments of the present invention are not limited in scope. Within the spirit and scope defined by the appended claims, embodiments of the invention may include various modifications, modifications, and equivalents.

The features described and / or illustrated for a particular embodiment may be used in one or more other embodiments in the same or similar manner, or may be combined with features in other embodiments, or in other embodiments May be used to replace the features of FIG.

As used herein, the term " comprise / include " refers to the presence of features, integers, steps, or components, but is not limited to the inclusion of one or more of the other features, And does not exclude the presence or addition of one or more of the foregoing.

A program operating on a device according to the present invention may be a program that enables a computer to implement the functions of embodiments of the present invention by controlling a central processing unit (CPU). The information processed by the program or program may be stored in a nonvolatile memory such as volatile memory (e.g., random access memory (RAM)), a hard disk drive (HDD), a nonvolatile memory Or may be temporarily stored in other memory systems.

A program for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable recording medium. Corresponding functions can be achieved by reading the recorded programs on the recording medium and by executing the programs by the computer system. The so-called " computer system " may be a computer system embedded in the device, which may include operating systems or hardware (e.g., peripherals). "Computer-readable recording medium" may be a semiconductor recording medium readable by a computer, an optical recording medium, a magnetic recording medium, a short-time dynamic memory program, or any other recording medium.

The various features or functional modules of the devices utilized in the above embodiments may or may not be implemented by circuits (e.g., monolithic or multi-chip integrated circuits). Circuits designed to perform the functions described in this description may be implemented using general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or any combination of the above. A general purpose processor may be a microprocessor, or it may be any existing processor, controller, microcontroller, or state machine. The circuit may be a digital circuit or an analog circuit. One or more embodiments of the present invention may also be implemented using these new integrated circuit technologies when new integrated circuit technologies replacing existing integrated circuits arise due to advances in semiconductor technology.

Furthermore, the present invention is not limited to the embodiments described above. While various examples of the described embodiments have been described, the invention is not so limited. Fixed or non-removable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances, may be used as terminal devices or communication devices have.

Embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific structures are not limited to the above embodiments, and the present invention also includes any design modifications that do not depart from the main idea of the present invention. In addition, various modifications may be made to the present invention within the scope of the claims, and embodiments resulting from appropriate combinations of the technical means disclosed in the different embodiments are also included within the scope of the present invention. Additionally, components having the same effect as described in the above embodiments may be replaced with each other.

Claims (40)

CLAIMS What is claimed is: 1. A method for random access performed at a user equipment (UE)
Receiving configuration information from a base station, the configuration information indicating an anchor carrier and / or one or more non-anchor carriers supporting random access;
Selecting, as a random access carrier, a carrier from the anchor carrier and / or the one or more non-anchor carriers that support random access according to the configuration information; And
Performing random access by using the random access carrier
≪ / RTI > The method of claim 1, wherein selecting a carrier from the anchor carrier and / or the one or more non-anchor carriers that support random access, as a random access carrier,
A method as claimed in any one of the preceding claims, wherein the at least one anchor carrier and / or the one or more non-interleaved carriers supporting random access indicated by the configuration information, in the random selection manner, in the same probability random selection manner, Selecting a carrier from the anchor carriers. 2. The method of claim 1, wherein if the downlink carrier on which the UE receives the paging message is configured with a corresponding uplink carrier and the uplink carrier supports random access, then the random access carrier is the uplink carrier Way. The method of claim 1, wherein selecting a carrier from the anchor carrier and / or the one or more non-anchor carriers that support random access, as a random access carrier,
If the downlink carrier on which the UE receives the paging message on it is not configured with a corresponding uplink carrier, or if the corresponding uplink carrier configured does not support random access, as the random access carrier, Selecting the anchor carriers that support random access, or supporting random access indicated by the configuration information as the random access carrier, in a random selection manner, in the same probability random selection manner, or according to a predefined rule And selecting a carrier from the anchor carrier and / or the one or more non-anchor carriers. 2. The method of claim 1, wherein when a physical downlink control channel (PDCCH) or an upper layer specifies a carrier for a UE to perform random access, the random access carrier is the specified carrier. 2. The method of claim 1, wherein the random access carrier is a non-anchor carrier having a RACH-ConfigCommon-NB and / or an NPRACH-ConfigSIB-NB information element configured by an RRC. The method of claim 1, wherein if the serving carrier of the UE supports random access, the random access carrier is the serving carrier. 2. The method of claim 1, wherein selecting a carrier from the anchor carrier and / or the one or more non-anchor carriers supporting random access as a random access carrier, according to the configuration information, And further selecting the random access carrier based on an enhanced coverage level. 2. The method of claim 1, wherein, in accordance with the configuration information, selecting a carrier from the anchor carrier and / or the one or more non-anchor carriers that support random access, as a random access carrier, And further selecting the random access carrier. 10. The method of claim 9, wherein selecting the random access carrier based on a data size comprises:
Comparing the potential message size with a predetermined threshold; And
Selecting the random access carrier according to a result of the comparison
≪ / RTI > 10. The method of any one of claims 1 to 9, wherein the configuration information represents one or more random access resource configurations for random access. 10. The method of any one of claims 1 to 9, wherein the configuration information includes an indication to indicate whether a corresponding non-anchor carrier shares the same random access resource configuration with the anchor carrier. 10. The method of any one of claims 1 to 9, wherein the RACH-ConfigCommon-NB and / or the NPRACH-ConfigSIB-NB configuration of the anchor carrier is based on RACH-ConfigCommon-NB and / or NPRACH- Different from the -NB configuration. 10. The method of any one of claims 1 to 9, wherein the NPRACH-ParametersList-NB configuration of the anchor carrier is different from the NPRACH-ParametersList-NB configuration of the non-anchor carrier. 10. The method of any one of claims 1 to 9, wherein one or more non-anchor carriers in the one or more non-anchor carriers share the same random access resource configuration with the anchor carrier. 10. The method according to any one of claims 1 to 9,
RACH-Config Command-NB;
NPRACH-ConfigSIB-NB; or
NPRACH-ParametersList-NB
≪ / RTI > 10. A method according to any one of claims 1 to 9, wherein the configuration information comprises an indicator for indicating whether the corresponding anchor carrier or non-anchor carrier supports random access; When the value of the indicator is set to "True" or "Setup" or "1", the corresponding anchor carrier or non-anchor carrier supports random access; When the value of the indicator is set to "False" or "Release" or "0", the corresponding non-anchor carrier does not support random access. 10. The method of any one of claims 1 to 9, wherein the configuration information comprises indicating whether the corresponding non-anchor carrier adopts the same random access resource configuration as the random access resource configuration of the anchor carrier; When the value of the indicator is set to "true" or "set up" or "1", the corresponding non-anchor carrier adopts the same random access resource configuration as the random access resource configuration of the anchor carrier; The corresponding non-anchor carrier adopts a random access resource configuration different from the random access resource configuration of the anchor carrier when the value of the indication is set to " false ", " released ", or " 0 & How to. A method for random access performed at a base station,
Generating configuration information, wherein the configuration information indicates an anchor carrier that supports random access and / or one or more non-anchor carriers; And
The UE transmitting the configuration information for performing random access to the UE
≪ / RTI > The method of claim 1, wherein the transmitting the configuration information to a UE comprises:
Broadcasting the configuration information from the system information; or
Transmitting the configuration information by using RRC dedicated signaling
≪ / RTI > A user equipment (UE)
A receiving unit configured to receive configuration information from a base station, the configuration information indicating an anchor carrier supporting random access and / or one or more non-anchor carriers;
According to the configuration information, as a random access carrier, a selection unit configured to select a carrier from the anchor carrier supporting random access and / or the one or more non-anchor carriers; And
A random access execution unit configured to perform random access by using the random access carrier,
/ RTI > 22. The apparatus of claim 21,
A method as claimed in any one of the preceding claims, wherein the at least one anchor carrier and / or the one or more non-interleaved carriers supporting random access indicated by the configuration information, in the random selection manner, in the same probability random selection manner, Wherein the UE is further configured to select carriers from the anchor carriers. 22. The method of claim 21, wherein if the downlink carrier on which the UE receives the paging message is configured with a corresponding uplink carrier and the uplink carrier supports random access, then the random access carrier is the uplink carrier UE. 22. The apparatus of claim 21,
If the downlink carrier on which the UE receives the paging message on it is not configured with a corresponding uplink carrier, or if the corresponding uplink carrier configured does not support random access, as the random access carrier, Selecting an anchor carrier that supports random access, or supporting random access indicated by the configuration information as a random access scheme, in the same probability random selection scheme, or in accordance with predefined rules, as the random access carrier Wherein the UE is further configured to select a carrier from the anchor carrier and / or the one or more non-anchor carriers. 22. The UE of claim 21, wherein when a physical downlink control channel (PDCCH) or higher layer specifies a carrier for the UE to perform random access, the random access carrier is the specified carrier. 22. The UE of claim 21, wherein the random access carrier is a non-anchor carrier having an RACH-ConfigCommon-NB and / or NPRACH-ConfigSIB-NB information element configured by RRC. 22. The UE of claim 21, wherein if the serving carrier of the UE supports random access, the random access carrier is the serving carrier. 22. The UE of claim 21, wherein the selection unit is further configured to further select the random access carrier based on an improved coverage level of the UE. 22. The UE of claim 21 wherein the selection unit is further configured to further select the random access carrier based on a data size. 30. The method of claim 29, wherein selecting the random access carrier based on a data size comprises:
Comparing the potential message size to a predetermined threshold; And
Selecting the random access carrier according to the comparison result
/ RTI > 30. A UE as claimed in any one of claims 21 to 29, wherein the configuration information indicates one or a plurality of random access resource configurations for random access. 30. A UE as claimed in any one of claims 21 to 29, wherein the configuration information comprises an indication to indicate whether a corresponding non-anchor carrier shares the same random access resource configuration with the anchor carrier. 30. The method of any one of claims 21 to 29, wherein the RACH-ConfigCommon-NB and / or the NPRACH-ConfigSIB-NB configuration of the anchor carrier is based on RACH-ConfigCommon-NB and / or NPRACH- UE different from the NB configuration. 30. A UE according to any one of claims 21 to 29, wherein the NPRACH-ParametersList-NB configuration of the anchor carrier is different from the NPRACH-ParametersList-NB configuration of the non-anchor carrier. 30. A UE as claimed in any one of claims 21 to 29, wherein one or more non-anchor carriers in the one or more non-anchor carriers share the same random access resources with the anchor carrier. 30. The method of any one of claims 21 to 29, wherein the random access resource configuration comprises:
RACH-Config Command-NB;
NPRACH-ConfigSIB-NB; or
NPRACH-ParametersList-NB
Gt; UE < / RTI > 30. A method according to any one of claims 21 to 29, wherein the configuration information comprises an indicator for indicating whether the corresponding anchor carrier or non-anchor carrier supports random access; When the value of the indicator is set to "True" or "Set up" or "1", the corresponding anchor carrier or non-anchor carrier supports random access; The corresponding non-anchor carrier does not support random access when the value of the indicator is set to "False" or "Release" or "0". 30. The method of any one of claims 21 to 29, wherein the configuration information comprises indicating whether the corresponding non-anchor carrier adopts the same random access resource configuration as the random access resource configuration of the anchor carrier; When the value of the indicator is set to "true" or "set up" or "1", the corresponding non-anchor carrier adopts the same random access resource configuration as the random access resource configuration of the anchor carrier; The corresponding non-anchor carrier adopts a random access resource configuration different from the random access resource configuration of the anchor carrier when the value of the indication is set to " false ", " released ", or " 0 & UE. As a base station,
A generation unit configured to generate configuration information, the configuration information indicating an anchor carrier supporting random access and / or one or more non-anchor carriers; And
A transmission unit configured to transmit the configuration information to the UE for user equipment (UE)
/ RTI > 40. The apparatus of claim 39,
Broadcasting the configuration information from the system information; or
To transmit the configuration information by using RRC dedicated signaling
A base station further configured.

Images