Patent Application
20240154766
The disclosure relates to, but is not limited to, a field of wireless communication technologies, in particular to a method for configuring a control resource set (CORESET) #0, an apparatus for configuring a CORESET #0, a communication device, and a storage medium.
A user equipment (UE) may perform cell search after being turned on. Usually, the cell search is mainly accomplished by detecting downlink synchronization channels and signals. For example, the UE goes through steps such as cell identity (ID) acquisition, frequency synchronization, and downlink time synchronization during the cell search process.
A Synchronization Signal and PBCH block (SSB) usually involves and is composed of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS) and a Physical Broadcast Channel (PBCH).
The control resource set (CORESET) #0 is a CORESET for scheduling a System Information Block 1 (SIB1). In detail, a Physical Downlink Control Channel (PDCCH) corresponding to SIB1 is mapped in a type0-PDCCH Common Search Space (CSS). In a frequency domain, the type0-PDCCH CSS is mapped to the CORESET #0.
The lower 4 bits of “pdcch-ConfigSIB1” of a signaling carried in the PBCH indicate configuration of the type0-PDCCH CSS, and the upper 4 bits indicate configuration of the CORESET #0.
A first aspect of the disclosure provides a method for configuring a CORESET #0, performed by a base station. The method includes: configuring the CORESET #0 according to a subcarrier spacing (SCS) of a synchronization signal and physical broadcast channel block (SSB).
A second aspect of the disclosure provides a method for configuring a CORESET #0, performed by a user equipment (UE). The method includes: receiving configuration information of the CORESET #0 configured according to a SCS of a SSB.
A third aspect of the disclosure provides a communication device, including a processor, a transceiver, and a memory storing programs executable by the processor. When the processor executes the executable programs, the method for configuring a CORESET #0 of the first aspect or the second aspect is implemented.
It is understandable that the above general description and the following detailed descriptions are illustrative and explanatory only and are not used to limit embodiments of the disclosure.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise represented. The implementations set forth in the following description of embodiments do not represent all implementations consistent with the embodiments of the disclosure. Instead, they are merely examples of apparatuses and methods consistent with aspects related to the embodiments of the disclosure as recited in the appended claims.
The terms used in the embodiments of the disclosure are only for the purpose of describing specific embodiments, and are not intended to limit the embodiments of the disclosure. The singular forms of “a” and “the” used in the disclosure and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term “and/or” as used herein refers to and includes any or all possible combinations of one or more associated listed items.
It is understandable that although the terms “first”, “second”, and “third” may be used in the embodiments of the disclosure to describe various information, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the term “if” as used herein can be interpreted as “when”, “while” or “in response to determining”.
The UE 11 may be a device that provides voice and/or data connectivity to a user. The UE 11 may communicate with one or more core networks via a Radio Access Network (RAN). The UE 11 may be an Internet of Things (IoT) UE, such as a sensor device, a mobile phone (or “cellular” phone), and a computer with an IoT UE. The UE 11 may also be a stationary, portable, pocket-sized, handheld, computer-built, or vehicle-mounted device, such as, a Station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, or a UE. Or, the UE 11 may be an unmanned aerial vehicle device. Or, the UE 11 may be an in-vehicle device, for example, an electronic control unit (ECU) having a wireless communication function, or a wireless communication device external to the ECU. Or, the UE 11 can also be a roadside device, for example, a street light, a signal light, or other roadside devices having the wireless communication function.
The access device 12 may be a network side device in the wireless communication system. The wireless communication system may be the 4th Generation (4G) mobile communication system, also known as a Long Term Evolution (LTE) system. Or, the wireless communication system may also be a 5G system, also known as a New Radio (NR) system or a 5G NR system. Or, the wireless communication system may be any next generation system of the 5G system. The access network in the 5G system may be called a New Generation-RAN (NG-RAN) or a machine type communication (MTC) system.
The access device 12 can be an evolved access device (eNB) employed in the 4G system. Or, the access device 12 may be an access device (gNB) with a centralized distributed architecture employed in the 5G system. When the access device 12 adopts the centralized distributed architecture, it usually includes a Central Unit (CU) and at least two Distributed Units (DUs). The CU is equipped with protocol stacks of a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, or a Media Access Control (MAC) layer. The DU is equipped with a protocol stack of a physical (PHY) layer, and the specific implementation of the access device 12 is not limited in the embodiment of the disclosure.
A wireless connection can be established between the access device 12 and the UE 11 via a radio interface. In different implementations, the radio interface is a radio interface based on the 4G standard. Or, the radio interface is a radio interface based on the 5G standard, such as a NR. Or, the radio interface may also be a radio interface based on the standard of the next generation of 5G.
In some embodiments, End to End (E2E) connections can also be established between the UEs 11 in scenarios, such as, Vehicle to Vehicle (V2V) communication, Vehicle to Infrastructure (V2I) communication, and Vehicle to Pedestrian (V2P) communication in Vehicle to Everything (V2X) communication.
In some embodiments, the above wireless communication system may also include a network management device 13.
The plurality of access devices 12 are connected to the network management device 13 respectively. The network management device 13 may be a core network device in the wireless communication system, for example, a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Or, the network management device may be other core network devices, such as a Serving GateWay (SGW), a Public Data Network GateWay (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS), etc. The implementation form of the network management device 13 is not limited in the embodiments of the disclosure.
Configuration of a control resource set (CORES ET) #0 may include at least one of the followings:
A 52.6 GHz carrier can use a higher subcarrier spacing (SCS). For example, the SCS can be as high as 960 kHz. That is, a maximum SCS of data can reach 960 kHz, and other optional values are 480k kHz, 240 kHz, 120 kHz, and 60 kHz. The frequency range of the frequency range 2 (FR2) for 5G is a range of 7.126 Ghz to 52.6 Ghz, and the SCS of the SSB of RF2 adopts 240 kHz or 120 kHz. For 52.6 GHz to 71 GHz. In order to support unlicensed and simplified system designs, data and the SSB adopt the same SCS as far as possible. In this way, for the SCS of large data, the SCS of the SSB may support new (non-existing) designs.
In the related art, only two kinds of SCS are supported in the SSB. If a new high SCS needs to be supported, a new design method needs to be given, taking into account both licensed bands and unlicensed bands. Meanwhile, a higher frequency band may introduce a new beam-based Listen Before Talk (LBT), which requires that there are idle symbols between SSBs for performing LBT. This is not supported by the SSB pattern involves two SCSs in the FR2 band in the relate art. The configuration of the SSB and the CORESET #0 in the related art can be as one or more elements in Table 1, Table 2, Table 3 or Table 4.
Table 1 is a set of resource blocks and slot symbols of CORESET for Type0—Physical Downlink Control Channel (PDCCH) search space set when SCSs of {SSB, PDCCH} is {120, 60} kHz.
Table 2 is a set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when SCSs of {SSB, PDCCH} is {120, 120} kHz.
Table 3 is a set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when SCSs of {SSB, PDCCH} is {240, 60} kHz.
Table 4 is a set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when SCSs of {SSB, PDCCH} is {240, 120} kHz.
In Tables 1 to 4, NRBCORESET indicates the number of RBs in the frequency domain occupied by the CORESET #0, and NsymbCORESET indicates the number of symbols in the time domain occupied by the CORESET #0.
In case of a new SCS (e.g., 240 kHz, 480 kHz, or 960 kHz), the SCS being 60 kHz in the configuration of CORESET #0 containing 60 kHz and 240 kHz in the related art is replaced with the new SCS, and associated tables are rewritten.
If the SCS of the SSB uses 240 kHz, the SCSs of the SSB in the related art are replaced with {240, 240}, {120, 240} respectively, and associated tables are rewritten.
Since the SCS is changed, a bit used to indicate a Quasi Co-Location (QCL) in the unlicensed band (New radio unlicensed band, NRU) becomes unusable and needs to be newly defined. Because there are no other reserved bits, it may be defined in the table. That is, the SCS used for the representation of the QCL in the unauthorized band needs to be removed from the table.
In an embodiment, a QCL representation method is provided as follows:
In view of this, a configuration table of the CORESET #0 is redefined as Table 5 according to the SCS of the SSB, which is provided as follows:
In Table 5, NRBCORESET indicates the number of RBs in the frequency domain occupied by the CORESET #0, and NSYMBCORESET indicates the number of symbols in the time domain occupied by the CORESET #0.
The configuration of the CORESET #0 shown in Table 5 can be carried out for the SCS of the SSB being 120 kHz, 240 kHz, 480 kHz, or 960 kHz.
A SCS indication is defined as one bit in the SSB indicating the SCS of the CORESET #0.
If the SSB uses one of 480 kHz or 960 kHz (indicated by x), the SCS indication in the SSB represents that the SCS of the CORESET #0 is {120, x} or {x, 120}, depending on the SCS of the SSB. If 240 kHz is used, the bit in the SSB indicates that the SCS of the CORESET #0 is 1120, 2401.
It is noted that when configuring the CORESET #0, each element in Table 5 can be used alone, or multiple elements can be used in combination.
As illustrated in
At step S110, the CORESET #0 is configured according to a SCS of a SSB.
Both the SCS of the SSB and the configuration of the CORESET #0 need to meet a bandwidth supported by a UE. If the SCS of SSB and/or a SCS of the CORESET #0 exceeds the bandwidth supported by the UE, it may cause the UE to fail to receive the information transmitted by the SSB and the CORESET #0. Or, if a bandwidth configured for the SCS of the SSB and/or the CORESET #0 is too small, the information transmitted by the SSB and the CORESET #0 occupies a large amount of time resources in the time domain, resulting in a larger transmission delay.
In the embodiment of the disclosure, the SCS of the SSB is configured according to the bandwidth supported by the UE, and the CORESET #0 is usually a CORESET that is closest to the SSB and monitored when the UE initially accesses. If the CORESET #0 is configured according to the SCS of the SSB, the CORESET #0 that is usable for the UE can be configured without re-determining the bandwidth supported by the UE.
In this way, in the embodiment of the disclosure, after the SCS of the SSB is determined, one or more of: the SCS of the CORESET #0, a frequency-domain relative location and/or a time-domain relative location between the CORESET #0 and the SSB are determined, which has the feature of easy configuration of the CORESET #0.
In an embodiment, when a system bandwidth is 52.6 Ghz to 71 Ghz, the CORESET #0 is configured according to the SCS of the SSB. Or, when the system bandwidth is above 52.6 Ghz or above 71 Ghz, the CORESET #0 is configured according to the SCS of the SSB.
In an embodiment of the disclosure, configuring the CORESET #0 includes at least one of the followings:
In the embodiment of the disclosure, the candidate value supported by the SCS of the SSB is an integer multiple of 120 kHz from 120 kHz to 960 kHz, which has the characteristic that the SCS of the SSB is large. That is, the frequency domain bandwidth occupied by the SSB is large. Thus, the time domain resources occupied by the SSB may be relatively reduced. In this way, the duration for the UE to receive the SSB may be short, which improves the transmission efficiency of the SSB.
In another embodiment of the present disclosure, configuring the CORESET #0 according to the SCS of the SSB includes:
Since the SCS of the SSB reaches 240 kHz or above, similarly, the SCS of the CORESET #0 is configured to be 120 kHz or above, so that a frequency domain bandwidth occupied by the CORESET #0 increases, which reduces the time domain resources occupied by the CORESET #0, and improves the transmission efficiency of the information transmitted by the CORESET #0.
In some embodiments, the SSB carries an indication bit for indicating the SCS of the CORESET #0.
In this way, the SSB carries the indication bit, after receiving the SSB, the UE can know the SCS of the CORESET #0 according to the indication bit in the SSB. For example, the indication bit is carried within a Physical Broadcast Channel (PBCH) of the SSB.
In an embodiment of the disclosure, a carrier band in which the SSB and the CORESET #0 are located includes:
A frequency of the second band is lower than a frequency of the first band.
The first band is a high-frequency band relative to the second band. In the embodiments of the disclosure, the method for configuring a CORESET #0 can be applied to a high-frequency band and a low-frequency band.
In an embodiment of the disclosure, the first band may include: any band with a frequency equal to or greater than 52.6 Ghz. For example, the first band may be a band with a frequency within the range from 52.6 Ghz to 74 Ghz.
In some embodiments, in response to the carrier band in which the SSB and the CORESET #0 are located being the first band, the SCS of the SSB and a QCL use different indication bits;
For the CORESET #0 and the SSB configured on different bands, the number of SCSs supported by the SSB are differently. If the number of SCSs supported by the SSB is small, the indication bit for indicating the SCS of the SSB may have a remaining bit value for indicating the QCL. Therefore, since the first band is a high-frequency band, it supports a large number of candidate SCSs, so that more indication bits is required for indicating the SCS of the SSB, and thus the indication bit for indicating the SCS of the SSB no longer indicate the QCL.
The second band is a low frequency band. A system bandwidth cell of the low frequency band is small, thus it supports a small amount of SCSs of the SSB, so that the indication bit for indicating the SCS of SSB may have a remaining bit value that can be used to indicate the QCL, thereby reducing bit overhead.
In some embodiments, in response to the SCS of the SSB and the QCL using different indication bits, the QCL shares the same indication bit with a first offset value between the SSB and the CORESET #0. The first offset value is a number of RBs offset between the SSB and the CORESET #0.
In order to save bit overhead, if the carrier band in which the SSB and the CORESET #0 are located is the first band, the first offset value and the QCL share the same indication bit, thereby realizing the feature of small bit overhead.
In some embodiments, a bit value of the indication bit for indicating the first offset value between the SSB and the CORESET #0 is different from a bit value for indicating the QCL.
In some embodiments, four types of indication values of the QCL are indicated by the same bit value shared by different indication indexes.
In some embodiments, configuring the CORESET #0 according to the SCS of the SSB includes at least one of the followings:
In the embodiment of the disclosure, since the system bandwidth is sufficiently large, in order to further reduce the transmission delay and improve the transmission efficiency, the multiplexing pattern of the CORESET #0 and the SSB uses pattern 2, i.e., frequency division multiplexing is performed in the frequency domain, and the CORESET #0 and the SSB are aligned at a starting location in the time domain.
The CORESET #0 supports at least one of 240 kHz, 480 kHz and 960 kHz, i.e., the CORESET #0 occupies a sufficiently large bandwidth on each time-domain unit, the amount of information that can be sent by the CORESET #0 corresponding to in frequency-domain resource unit corresponding to a symbol in the time domain is increased Therefore, 1 symbol configured in the time domain can be sufficient to accomplish the transmission of the information to be carried by the CORESET #0.
In an embodiment, kSSB is used to indicate a number of REs offset between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB after the number of RBs are spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB.
If the SCS of the SSB is one of 240 kHz, 480 kHz and 960 kHz, the number of RBs configured for the CORESET #0 in the frequency domain is 48 or 96, which is highly compatible with the related art, and can configure 48 or 96 RBs in the case of the SCS of the SSB or the SCS of the CORESET #0 being 240 kHz, 480 kHz and 960 kHz, so that the bandwidth of the CORESET #0 is sufficiently large to realize fast transmission through large bandwidth occupation in the frequency domain.
In some embodiments, in response to the SCS of the SSB including at least one of 240 kHz, 480 kHz and 960 kHz, configuring the number of RBs spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB to be 97, −41 or −42, includes at least one of the followings:
In a specific implementation, there are multiple numbers of RBs spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB. In the embodiment of the disclosure, the number of RBs spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB is configured to be at least one of 97, −41 and −42, and the specific number is further determined according to the number of REs during configuration, so that the implementation is simple and conforms to the phenomenon of minimal waste of resources.
As illustrated in
At step S210, configuration information of the CORESET #0 configured according to a SCS of a SSB is received.
The configuration information may be in the pdcch-ConfigSIB1 signaling carried by a PBCH. In the embodiment of the disclosure, the configuration information of the CORESET#0 is configured according to the SCS of the SSB.
In some embodiments, a candidate value of the SCS of the SSB includes at least one of the followings:
In the embodiment of the disclosure, the SSB is aimed at the large system bandwidth of 5G or the system bandwidth of any future mobile communication generation of 5G. Therefore, the SCS of the SSB does not use the small SCS of 60 kHz. By using the large SCS configuration, the amount of information carried by the CORESET #0 can be increased and can occupy less resources in the time domain, thereby reducing the transmission delay.
In some embodiments, the configuration information indicates that:
In some embodiments, the SSB carries an indication bit for indicating the SCS of the CORESET #0.
In some embodiments, a carrier band in which the SSB and the CORESET #0 are located includes:
A frequency of the second band is lower than a frequency of the first band.
For example, the first band includes: 52.6 GHz to 74 GHz.
For example, in response to the carrier band in which the SSB and the CORESET #0 are located being the first band, the SCS of the SSB and a QCL use different indication bits;
For example, in response to the SCS of the SSB and the QCL using different indication bits, the QCL shares the same indication bit with a first offset value between the SSB and the CORESET #0, in which the first offset value is a number of RBs offset between the SSB and the CORESET #0.
For example, a bit value of the indication bit used to indicate the first offset value between the SSB and the CORESET #0 is different from a bit value for indicating the QCL.
For example, four types of indication values of the QCL are indicated by the same bit value shared by different indication indexes.
For example, the configuration information indicates at least one of the followings:
For example, the configuration information includes a kSSB, the kSSB indicates a number of REs indicated by kSSB offset between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB after the number of RBs are spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB.
For example, in response to the SCS of the SSB including at least one of 240 kHz, 480 kHz and 960 kHz, the number of RBs spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB being 97, −41 or −42, including at least one of the followings:
The embodiment of the disclosure provides a configuration of a CORESET #0 that may be as follows: in the case of a new SCS (e.g., 960 kHz) of the SSB, the SCS being 60 kHz in the configuration of CORESET #0 containing 60 kHz and 240 kHz is replaced with the new SCS, and associated configuration tables of CORESET #0 are rewritten. For example, the configurations in the preceding Tables 1, 2, and 3 are modified by changing the 60 kHz of the CORESET #0 to 240 kHz, 480 kHz, or 960 kHz.
For example, if the SCS of the SSB uses 240 kHz, the configurations of SCS in Tables 1 and 3 are replaced with {240, 240} and {120, 240} respectively, and the configuration table for CORESET #0 is rewritten. The rewritten configuration table can be shown in Table 5.
Since the SCS is changed, a bit used to indicate the QCL in the unauthorized band (New radio unlicensed band, NRU) becomes unusable and needs to be newly defined. Because there are no other reserved bits, it may be defined in the table. That is, the SCS used for the representation of the QCL in the unauthorized band needs to be removed from the table.
In view of this, the specific QCL representation method is provided as follows: representing using a reserved/unused bit of the offset value (Offset), i.e., representing using a combination of values of the offset and the QCL.
The indication for SCS may be represented by one bit in the SSB, such as CORESET #0 SCS indication.
If the SSB uses one of 480 kHz and 960 kHz (indicated by x), the SCS indication in the SSB represents {120, x} or {x, 120}, depending on the SCS of the SSB. If 240 kHz is used, the SCS indication in the SSB represents {120, 240}.
As illustrated in
a configuring module 510, configured to configure the CORESET #0 according to a SCS of a SSB.
In some embodiments, the configuring module 510 may be a program module. After the program module is executed by a processor, it can configure the CORESET #0 according to the SCS of the SSB.
In some embodiments, the configuring module 510 may further include: a hardware and software combination module. The hardware and software combination module includes but is not limited to: a programmable array. The programmable array includes but is not limited to: a field programmable array or a complex programmable array.
In some embodiments, the configuring module 510 may further include: a pure hardware module. The pure hardware module includes but is not limited to: an application specific integrated circuit.
It can be understood that a candidate value of the SCS of the SSB includes at least one of the followings:
It can be understood that the configuring module 510 is configured to implement at least one of:
It can be understood that the SSB carries an indication bit for indicating the SCS of the CORESET #0.
It can be understood that a carrier band in which the SSB and the CORESET #0 are located includes:
It can be understood that the first band includes: 52.6 GHz to 74 GHz.
It can be understood that in response to the carrier band in which the SSB and the CORESET #0 are located being the first band, the SCS of the SSB and a QCL use different indication bits;
It can be understood that in response to the SCS of the SSB and the QCL using different indication bits, the QCL shares the same indication bit with a first offset value between the SSB and the CORESET #0, in which the first offset value is a number of RBs offset between the SSB and the CORESET #0.
It can be understood that a bit value of the indication bit used to indicate the first offset value between the SSB and the CORESET #0 is different from a bit value for indicating the QCL.
It can be understood that four types of indication values of the QCL are indicated by the same bit value shared by different indication indexes.
It can be understood that configuring the CORESET #0 according to the SCS of the SSB includes at least one of the followings:
It can be understood that kSSB is used to indicate a number of REs offset between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB after the number of RBs are spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB.
It can be understood that the configuring module 510 is configured to implement at least one of:
As illustrated in
In some embodiments, the receiving module 610 may be a program module. After the program module is executed by a processor, it can receive the configuration information of the CORESET #0 configured by a base station side according to the SCS of the SSB.
In some embodiments, the receiving module 610 may further include: a hardware and software combination module. The hardware and software combination module includes but is not limited to: a programmable array. The programmable array includes but is not limited to: a field programmable array or a complex programmable array.
In some embodiments, the receiving module 610 may further include: a pure hardware module. The pure hardware module includes but is not limited to: an application specific integrated circuit.
In some embodiments, a candidate value of the SCS of the SSB includes at least one of the followings:
In some embodiments, the configuration information indicates that
In some embodiments, the SSB carries an indication bit for indicating the SCS of the CORESET #0.
In some embodiments, a carrier band in which the SSB and the CORESET #0 are located includes:
In some embodiments, the first band includes: 52.6 GHz to 74 GHz.
In some embodiments, in response to the carrier band in which the SSB and the CORESET #0 are located being the first band, the SCS of the SSB and a QCL use different indication bits;
In some embodiments, in response to the SCS of the SSB and the QCL using different indication bits, the QCL shares the same indication bit with a first offset value between the SSB and the CORESET #0, in which the first offset value is a number of RBs offset between the SSB and the CORESET #0.
In some embodiments, a bit value of the indication bit used to indicate the first offset value between the SSB and the CORESET #0 is different from a bit value for indicating the QCL.
In some embodiments, four types of indication values of the QCL are indicated by the same bit value shared by different indication indexes.
In some embodiments, the configuration information indicates at least one of the followings:
in response to the SCS of the SSB including at least one of 240 kHz, 480 kHz and 960 kHz, a number of RBs spaced between a frequency domain lower boundary of the CORESET #0 being 97, −41 or −42.
In some embodiments, the configuration information includes a kSSB, the kSSB indicates a number of REs offset between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB after a number of RBs are spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB.
In some embodiments, in response to the SCS of the SSB including at least one of 240 kHz, 480 kHz and 960 kHz, the number of RBs spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB being 97, −41 or −42, including at least one of the followings:
in response to the SCS of the SSB including at least one of 240 kHz, 480 kHz and 960 kHz, and the number of REs indicated by the kSSB being 0, the number of RBs spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB being −41;
in response to the SCS of the SSB including at least one of 240 kHz, 480 kHz and 960 kHz, and the number of REs indicated by the kSSB being greater than 0, the number of RBs spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB being −42; and
in response to the SCS of the SSB including at least one of 240 kHz, 480 kHz and 960 kHz, and the number of REs indicated by the kSSB being any real number, the number of RBs spaced between the frequency domain lower boundary of the CORESET #0 and the frequency domain lower boundary of the SSB being 97.
An embodiment of the disclosure provides a communication device, including:
The processor may include various types of storage mediums, which are non-transitory computer storage mediums capable of continuing to memorize information stored thereon after the communication device is powered down.
The communication device includes: a UE or a base station.
The processor may be connected to the memory via a bus, to read executable programs stored on the memory, e.g., at least one of the methods as shown in
In the technical solution provided by the embodiments of the disclosure, the CORESET #0 is configured according to the SCS of the SSB. The CORESET #0 configured in this way can, on the one hand, enable the UE to easily perform configuration according to a bandwidth supported by the UE under the condition of successfully receiving the SSB. On the other hand, by configuring the CORESET #0 according to the SCS of the SSB, the SCS supported by the CORESET #0 can be consistent with the SCS of the SSB, which simplifies the UE's reception of the CORESET #0. For example, the SCS of the SSB supports 120 kHz, 240 kHz, 480 kHz and 960 kHz, thus, corresponding to one of 120 kHz, 240 kHz, 480 kHz and 960 kHz, a larger SCS is configured for the CORESET #0. In this way, less time domain resources can be configured for the CORESET #0 under the condition that an amount of information in a required transmission band remains unchanged or changes little, thereby reducing a transmission delay for transmitting the CORESET #0 and improving a transmission efficiency.
As illustrated in
The processing component 802 typically controls overall operations of the UE 800, such as the operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps in the above described method. Moreover, the processing component 802 may include one or more modules which facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support the operation of the UE 800. Examples of such data include instructions for any applications or methods operated on the UE 800, contact data, phonebook data, messages, pictures, videos, etc. The memory 804 may be implemented using any type of volatile or non-volatile memory devices, or a combination thereof, such as a Static Random-Access Memory (SRAM), an Electrically-Erasable Programmable Read Only Memory (EEPROM), an Erasable Programmable Read Only Memory (EPROM), a Programmable Read Only Memory (PROM), a Read Only Memory (ROM), a magnetic memory, a flash memory, a magnetic or optical disk.
The power component 806 provides power to various components of the UE 800. The power component 806 may include a power management system, one or more power sources, and any other components associated with the generation, management, and distribution of power in the UE 800.
The multimedia component 808 includes a screen providing an output interface between the UE 800 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes the touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also sense a duration and a pressure associated with the touch or swipe action. In some embodiments, the multimedia component 808 includes a front-facing camera and/or a rear-facing camera. When the UE 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and/or the rear-facing camera can receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or has focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a microphone (MIC) configured to receive an external audio signal when the UE 800 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 further includes a speaker to output audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, such as a keyboard, a click wheel, buttons, and the like. The buttons may include, but are not limited to, a home button, a volume button, a starting button, and a locking button.
The sensor component 814 includes one or more sensors to provide status assessments of various aspects of the UE 800. For instance, the sensor component 814 may detect an open/closed status of the UE 800, relative positioning of components, e.g., the display and the keypad, of the UE 800, a change in position of the UE 800 or a component of the UE 800, a presence or absence of user contact with the UE 800, an orientation or an acceleration/deceleration of the UE 800, and a change in temperature of the UE 800. The sensor component 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor component 814 may also include a light sensor, such as a Complementary Metal Oxide Semiconductor (CMOS) or a Charge-Coupled Device (CCD) image sensor, for use in imaging applications. In some embodiments, the sensor component 814 may also include an accelerometer sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communication, wired or wirelessly, between the UE 800 and other devices. The UE 800 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof. In an embodiment, the communication component 816 receives a broadcast signal from an external broadcast management system or broadcast associated information via a broadcast channel. In an embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on a Radio Frequency Identification (RFID) technology, an Infrared Data Association (IrDA) technology, an Ultra-Wide Band (UWB) technology, a Blue Tooth (BT) technology, and other technologies.
In an exemplary embodiment, the UE 800 may be implemented with one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components, for performing the above described method.
In the exemplary embodiments, there is also provided a non-transitory computer readable storage medium including instructions, such as the memory 804, executable by the processor 820 in the UE 800, for performing the above method. For example, the non-transitory computer-readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disc, and an optical data storage device.
As illustrated in
As illustrated in
The communication device 900 may also include a power component 926 configured to perform power management of the communication device 900, a wired or wireless network interface 950 configured to connect the communication device 900 to a network, and an input/output (I/O) interface 958. The communication device 900 may operate based on an operating system stored in the memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed here. The disclosure is intended to cover any variations, uses, or adaptations of the disclosure following the general principles thereof and including such departures from the disclosure as come within known or customary practice in the art. It is intended that the specification and examples be considered as illustrative only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be appreciated that the disclosure is not limited to the exact construction that has been described above and illustrated in the accompanying drawings, and that various modifications and changes can be made without departing from the scope thereof. It is intended that the scope of the disclosure only be limited by the appended claims.
This application a U.S. national phase of International Application No. PCT/CN2021/082175, filed on Mar. 22, 2021, the entire contents of which are incorporated herein by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2021/082175 | 3/22/2021 | WO |
