WO2020200100A1 - 多发送接收点tpr配置方法、设备及存储介质 - Google Patents

多发送接收点tpr配置方法、设备及存储介质 Download PDF

Info

Publication number
WO2020200100A1
WO2020200100A1 PCT/CN2020/081702 CN2020081702W WO2020200100A1 WO 2020200100 A1 WO2020200100 A1 WO 2020200100A1 CN 2020081702 W CN2020081702 W CN 2020081702W WO 2020200100 A1 WO2020200100 A1 WO 2020200100A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
coreset
trp
channel configuration
physical channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/081702
Other languages
English (en)
French (fr)
Inventor
宋扬
孙鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2020200100A1 publication Critical patent/WO2020200100A1/zh
Priority to US17/486,876 priority Critical patent/US12041629B2/en
Anticipated expiration legal-status Critical
Priority to US18/747,357 priority patent/US20240340910A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signalling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a method, device and storage medium for configuring a TPR with multiple transmission and reception points.
  • the physical downlink control channel configuration (PDCCH-Config), the physical downlink shared channel configuration (PDSCH-Config), and the physical uplink control channel configuration (PUCCH-Config) are all based on the single transmission and reception point (Transmission Reception Point, TRP). )Designed. In each bandwidth part (Bandwidth Part, BWP), only one PDCCH-Config, PDSCH-Config or PUCCH-Config can function at the same time. When Radio Resource Control (RRC) reconfigures a PDCCH-Config, PDSCH-Config or PUCCH-Config, the new configuration takes effect.
  • RRC Radio Resource Control
  • the terminal may receive PDCCH or PDSCH sent by multiple TRPs, or the terminal may send PUCCH to multiple TRPs. Therefore, the configuration in the related technology cannot meet the requirements of the multiple TRP scenario.
  • the embodiments of the present disclosure provide a method, device, and storage medium for configuring a multi-transmitting-receiving-point TPR to solve the problem that the configuration cannot meet the requirements of a multi-TRP scenario.
  • embodiments of the present disclosure provide a method for configuring multiple TPRs, the method including:
  • Multiple CORESETs correspond to multiple TRPs, and at least one CORESET of the multiple CORESETs corresponds to one TRP.
  • embodiments of the present disclosure provide a device for configuring multiple TPRs, the device including:
  • the first configuration unit is used to configure one physical channel configuration information element IE corresponding to multiple control resource sets CORESET; or,
  • the second configuration unit is used to configure multiple physical channel configuration IEs corresponding to multiple CORESETs
  • multiple CORESETs correspond to multiple TRPs, and at least one CORESET of the multiple CORESETs corresponds to one TRP.
  • embodiments of the present disclosure provide a device for configuring multiple TPRs.
  • the device includes: a processor, a memory, and a computer program stored in the memory and running on the processor.
  • the computer program is executed when the processor is executed. The steps of the multiple TPR configuration method provided by the embodiments of the present disclosure.
  • the embodiments of the present disclosure provide a computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the steps of the multiple TPR configuration method provided by the embodiments of the present disclosure are implemented .
  • the configured physical channel configuration can meet the requirements of the multiple TRP scenario.
  • FIG. 1 shows a schematic flowchart of a multi-TPR configuration method provided by an embodiment of the present disclosure
  • FIG. 2 shows a schematic diagram of the hardware structure of a multi-TPR configuration device provided by an embodiment of the present disclosure
  • FIG. 3 shows a schematic diagram of the hardware structure of a terminal device provided by an embodiment of the present disclosure.
  • embodiments of the present disclosure provide a multiple TPR configuration method, device, and storage medium. The following first describes in detail the multiple TPR configuration method provided by the embodiments of the present disclosure.
  • the multiple TPR configuration method provided by the embodiment of the present disclosure is optionally applicable to multiple TPR configuration devices.
  • the multi-TPR configuration device can be a base station, which can be a commonly used base station, an evolved base station (evolved node base station, eNB), or a network side device in a 5G system (such as next generation base station). node base station, gNB) or a network side device in a subsequent evolved communication system.
  • eNB evolved node base station
  • gNB next generation base station
  • gNB network side device in a subsequent evolved communication system.
  • the above terms do not constitute a limitation on the protection scope of the present disclosure.
  • the multiple TPR configuration method provided by the embodiments of the present disclosure may include: configuring one physical channel configuration IE to correspond to multiple CORESETs, or configuring multiple physical channel configuration IEs to correspond to multiple CORESETs. Among them, multiple CORESETs correspond to multiple TRPs, and at least one CORESET of the multiple CORESETs corresponds to one TRP.
  • the configured physical channel configuration can meet the requirements of the multi-TRP scenario.
  • the multiple TPR configuration method provided by the embodiment of the present disclosure may further include: configuring a correspondence between at least one CORESET and one TRP among the multiple CORESETs.
  • the multiple TPR configuration method provided by the embodiment of the present disclosure is shown in FIG. 2, and FIG. 2 shows a schematic flowchart of the multiple TPR configuration method provided by the embodiment of the present disclosure.
  • Multiple TPR configuration methods can include:
  • S101 Configure one physical channel configuration IE to correspond to multiple CORESETs, or configure multiple physical channel configuration IEs to correspond to multiple CORESETs.
  • S102 Configure a corresponding relationship between at least one CORESET of the multiple CORESETs and one TRP.
  • the physical channel configuration IE includes at least one of the following items:
  • Physical downlink control channel configuration IE Physical downlink control channel configuration IE (Physical downlink control channel-Config IE, PDCCH-Config IE), physical downlink shared channel configuration IE (Physical downlink shared channel-Config IE, PDSCH-Config IE) and physical uplink control channel configuration IE (Physical Uplink Control Channel-Config IE, PUCCH-Config IE).
  • configuring the correspondence between at least one CORESET of the multiple CORESETs and one TRP may include: grouping multiple CORESETs to obtain multiple CORESET groups; configuring each CORESET group with one TRP Correspondence.
  • one CORESET group includes multiple CORESETs.
  • CORESETs For there are 6 CORESETs, and the 6 CORESETs are: CORESET1, CORESET2, CORESET3, CORESET4, CORESET5, and CORESET6.
  • the 6 CORESETs are divided into three groups: CORESET group, CORESET group two and CORESET group.
  • CORESET group includes: CORESET1 and CORESET2 and CORESET3;
  • CORESET group includes: CORESET4 and CORESET5;
  • CORESET group includes: CORESET6.
  • Each CORESET group corresponds to a TRP.
  • configuring the association relationship between at least one CORESET of the multiple CORESETs and one TRP may include: determining multiple default CORESETs, each of which corresponds to a TRP; configuring other CORESETs to correspond to one default CORESET respectively Relationship. Therefore, at least two CORESETs that have an association relationship correspond to one TRP. Furthermore, the correspondence between each default CORESET and one TRP can be explicitly configured, so as to determine the correspondence between at least two CORESETs and one TRP that have an association relationship.
  • the correspondence between CORESET and TRP may be configured in the physical downlink control channel configuration IE (PDCCH-Config IE) of radio resource control (Radio Resource Control, RRC) signaling.
  • PDCCH-Config IE physical downlink control channel configuration IE
  • RRC Radio Resource Control
  • At least one CORESET of the multiple CORESETs corresponds to one TRP, which may include: grouping the multiple CORESETs to obtain multiple CORESET groups, wherein each CORESET group corresponds to one TRP.
  • At least one CORESET of the plurality of CORESETs corresponds to one TRP, which may include: determining a plurality of default CORESETs; configuring the association relationship between at least one other CORESET and one default CORESET respectively; and CORESET with an association relationship. Corresponds to a TRP.
  • the correspondence between CORESET and TRP can also be configured in other radio resource control (Radio Resource Control, RRC) signaling, that is, the relationship between CORESET and TRP can be added to RRC signaling.
  • RRC Radio Resource Control
  • Correspondence configuration IE IE.
  • configuring one physical channel configuration IE corresponding to multiple CORESETs may include: configuring the domain included in the physical channel configuration IE to correspond to multiple configuration IEs.
  • each configuration IE is associated with multiple CORESETs corresponding to a TRP, or each configuration IE is associated with a CORESET group corresponding to the TRP, or each configuration IE is associated with the TCI state of the CORESET group corresponding to a TRP.
  • the physical channel configuration IE includes the physical downlink control channel configuration PDCCH-Config IE; the above domain includes at least one of the following domains:
  • Downlink Preemption field transmit power control-physical uplink shared channel (tpc-PUSCH) field, transmit power control-physical uplink control channel (tpc-PUCCH) field and transmit power control-channel sounding reference signal (tpc) -SRS) domain.
  • tpc-PUSCH power control-physical uplink shared channel
  • tpc-PUCCH transmit power control-physical uplink control channel
  • tpc-SRS power control-channel sounding reference signal
  • the physical channel configuration IE includes the physical downlink shared channel configuration PDSCH-Config IE; the aforementioned domain includes at least one of the following domains:
  • PDSCH initialization data scrambling code dataScramblingIdentityPDSCH
  • mcs-Table modulation and coding scheme table
  • maxNrofCodeWordsScheduledByDCI the maximum number of codewords that can be scheduled for downlink control information
  • aperiodic triggered zero-power channel state information reference signal resources Set related aperiodic-ZP-CSI-RS-ResourceSetsToAddModList field and aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList field.
  • the physical channel configuration IE includes the physical uplink control channel configuration PUCCH-Config IE; the above-mentioned fields include at least one of the fields included in the PUCCH-Config IE.
  • PUCCH resource set field PUCCH resource field, PUCCH format field, scheduling request resource field, multi-channel status information physical uplink control channel resource (multi-CSI-PUCCH-ResourceList) field, timing list (dl-DataToUL-ACK) field, reference Signal and PUCCH spatial relationship domain and PUCCH power control (pucch-PowerControl) domain.
  • the PUCCH resource set field includes: PUCCH resource set add and modify (resourceSetToAddModList) field and PUCCH resource set release (resourceSetToReleaseList) field.
  • the PUCCH resource domain includes: PUCCH resource add modification (resourceSetToAddModList) domain and PUCCH resource release (resourceToReleaseList) domain.
  • the PUCCH format domain includes: format1 domain, format2 domain, format3 domain and format4 domain.
  • the scheduling request resource domain includes: a scheduling request resource addition modification (schedulingRequestResourceToAddModList) domain and a scheduling request resource release (schedulingRequestResourceToReleaseList) domain.
  • the spatial relationship domain between the reference signal and the PUCCH includes: the spatial relationship addition and modification (spatialRelationInfoToAddModList) domain between the reference signal and the PUCCH and the spatial relationship release (spatialRelationInfoToReleaseList) domain between the reference signal and the PUCCH.
  • configuring the domain included in the physical channel configuration IE corresponds to multiple configuration IEs, which may include: expanding the domain included in the physical channel configuration IE into multiple domains; wherein each domain corresponds to one configuration IE.
  • the configuration PDCCH-Config IE Take the configuration PDCCH-Config IE as an example. Extend the downlinkPreemption field in the PDCCH-Config IE into N fields, and the N fields are respectively the downlinkPreemption field, the downlinkPreemption1 field,..., the downlinkPreemptionN-1 field.
  • the aforementioned extended N domains are respectively associated with multiple CORESETs or one CORESET group. That is, the above N domains respectively correspond to one configuration IE.
  • the downstreamPreemption domain, the downstreamPreemption1 domain,..., the downstreamPreemptionN-1 domain can be associated with multiple CORESET ID or CORESET ID groups in sequence, for example, according to the default CORESET ID from small to large, or CORESET group ID from small to small The larger order is related in turn.
  • the downlinkPreemption1, tpc-PUSCH1, tpc-PUCCH1, and tpc-SRS1 in the PDCCH-Config.
  • the PDCCH is sent on the CORESET with the larger CORESET ID, use the downlinkPreemption2, tpc-PUSCH2, tpc-PUCCH2, and tpc-SRS2 in the PDCCH-Config.
  • OPTIONAL indicates that the item is optional.
  • the extended multiple fields are located at the end of the physical channel configuration IE.
  • the physical channel configuration can be compatible with lower version terminal devices.
  • configuring the domain included in the physical channel configuration IE corresponds to multiple configuration IEs, which may include: extending the domain included in the physical channel configuration IE into an IE configuration sequence; wherein, each element in the IE configuration sequence Corresponds to a configuration.
  • the configuration IE corresponding to the domain is associated with multiple TRPs.
  • the expanded IE configuration sequence is as follows:
  • the IE configuration sequence includes N elements, and each element corresponds to a configuration IE.
  • the first element in the IE configuration sequence is associated with the smaller CORESET ID
  • the second element in the IE configuration sequence is associated with the smaller CORESET ID
  • the smaller CORESET ID and the larger CORESET ID correspond to each other A TRP.
  • DCI scheduling Downlink Control Information (DCI) scheduling, uplink dynamic grant scheduling, or configured grant type 2: RRC configuration transmission period, L1/L2 layer control signaling activation or In deactivation) scheduling
  • the TRP can be determined by the CORESET of the DCI that sends the signaling, so that the terminal can determine which configuration IE of each domain included in the PDCCH-Config IE, PDSCH-Config IE, or PUCCH-Config IE should be applied to the terminal received PDCCH, PDSCH, and PUCCH sent by the terminal.
  • TRP Transmission Configuration Indicator
  • the multiple TPR configuration device may use any one of the above domains to configure multiple TPRs using the same configuration.
  • the TCI state (TCI-States) field may include the TCI state of all TRPs, and the TCI state of each BWP may be a global number.
  • the global numbering in the embodiments of the present disclosure refers to sequential numbering in the order of natural numbers.
  • each CORESET can activate its own MAC CE through a Medium Access Control (MAC) control element (CE).
  • MAC Medium Access Control
  • CE Control element
  • multiple physical channel configuration IEs may be configured to correspond to multiple CORESETs.
  • Configuring multiple physical channel configuration IEs corresponding to multiple CORESETs may include: configuring a field in each of the multiple physical channel configuration IEs to correspond to any one of the following items: at least one CORESET , A CORESET group and a TRP.
  • a physical channel configuration IE does not have a domain associated with any of the following items: at least one CORESET, one CORESET group, and one TRP; then, the physical channel configuration IE is associated with one CORESET, one CORESET group, and one TRP by default.
  • each PUCCH-Config IE corresponds to a CORESET group.
  • the code for configuring 3 PDCCH-Config IEs at the same time may be:
  • multiple physical channel configurations can be made on each BWP at the same time, and the configured physical channel configuration can meet the requirements of multiple TRP scenarios.
  • the embodiment of the present disclosure also provides a multi-TPR configuration device.
  • Multiple TPR configuration devices can include:
  • the first configuration unit is used to configure one physical channel configuration information element IE to correspond to multiple control resource sets CORESET. or,
  • the second configuration unit is used to configure multiple physical channel configuration IEs corresponding to multiple CORESETs.
  • multiple CORESETs correspond to multiple TRPs, and at least one CORESET of the multiple CORESETs corresponds to one TRP.
  • At least one CORESET of the multiple CORESETs corresponds to one TRP, including: grouping the multiple CORESETs to obtain multiple CORESET groups; wherein, each CORESET group corresponds to one TRP.
  • At least one CORESET of the plurality of CORESETs corresponds to a TRP, including: determining a plurality of default CORESETs; configuring an association relationship between at least one other CORESET and one default CORESET respectively; wherein there is an association relationship
  • the CORESET corresponds to a TRP.
  • the multi-TPR configuration device provided by the embodiment of the present disclosure may further include:
  • the third configuration unit is used to configure the correspondence between at least one CORESET and one TRP among the multiple CORESETs.
  • the third configuration unit may be specifically used for:
  • the third configuration unit may be specifically used for:
  • the corresponding relationship may be configured in the physical downlink control channel configuration IE.
  • the first configuration unit may be specifically used for:
  • the domain included in the configuration physical channel configuration IE corresponds to multiple configuration IEs; among them, each configuration IE is associated with a TRP corresponding to multiple CORESETs, or each configuration IE is associated with a TRP corresponding CORESET group, or each configuration IE is associated
  • the transmission configuration of the CORESET group corresponding to a TRP indicates the TCI status.
  • the first configuration unit may be specifically used for:
  • the domain included in the physical channel configuration IE is extended to an IE configuration sequence; wherein, each element in the IE configuration sequence corresponds to a configuration IE.
  • the configuration IE corresponding to the domain is associated with multiple TRPs.
  • the second configuration unit may be specifically used to configure the correspondence between a field and any one of the following items in each physical channel configuration IE of the multiple physical channel configuration IEs :
  • At least one CORESET, one CORESET group, and one TRP At least one CORESET, one CORESET group, and one TRP.
  • a physical channel configuration IE if there is no domain associated with any one of the following items in a physical channel configuration IE: at least one CORESET, one CORESET group and one TRP;
  • the physical channel configuration IE is associated with a default CORESET, a CORESET group, and a TRP.
  • the physical channel configuration IE includes at least one of the following items:
  • Fig. 2 shows a schematic diagram of the hardware structure of a multi-TPR configuration device provided by an embodiment of the present disclosure.
  • the multi-TPR configuration device includes: a memory 301, a processor 302, a transceiver 303, and a computer program stored on the memory 301 and running on the processor 302.
  • the processor 302 may be used to configure one physical channel configuration information element IE to correspond to multiple control resource sets CORESET, or to configure multiple physical channel configuration IEs to correspond to multiple CORESETs, where multiple CORESETs correspond to multiple TRPs. At least one CORESET in one CORESET corresponds to one TRP.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 302 and various circuits of the memory represented by the memory 301 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further descriptions are provided herein.
  • the bus interface provides the interface.
  • the transceiver 303 may be multiple elements, including a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium, and for receiving and transmitting data under the control of the processor 302.
  • the processor 302 is responsible for managing the bus architecture and general processing, and the memory 301 can store data used by the processor 302 when performing operations.
  • the embodiment of the present disclosure further provides a multi-TPR configuration device, including a processor 302, a memory 301, and a computer program stored in the memory 301 and running on the processor 302.
  • the computer program is executed by the processor 302.
  • Each process applied to the embodiment of the multiple TPR configuration method is implemented during execution, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • FIG. 3 shows a schematic diagram of the hardware structure of a terminal device provided by an embodiment of the present disclosure.
  • the terminal device 400 includes but is not limited to: a radio frequency unit 401, a network module 402, an audio output unit 403, an input unit 404, a sensor 405, a display unit 406, a user input unit 407, an interface unit 408, a memory 409, a processor 410, and Power supply 411 and other components.
  • Those skilled in the art can understand that the structure of the terminal device shown in FIG. 3 does not constitute a limitation on the terminal device, and the terminal device may include more or fewer components than shown in the figure, or a combination of certain components, or different components Layout.
  • terminal devices include, but are not limited to, mobile phones, tablet computers, notebook computers, palmtop computers, vehicle-mounted terminals, wearable devices, and pedometers.
  • the processor 410 is configured to receive PDCCH or PDSCH of multiple TRPs according to the physical channel configuration IE; or, send PUCCH to multiple TRPs.
  • the configured physical channel configuration can meet the requirements of multiple TRP scenarios.
  • the radio frequency unit 401 can be used for receiving and sending signals in the process of sending and receiving information or talking. Specifically, the downlink data from the base station is received and processed by the processor 410; Uplink data is sent to the base station.
  • the radio frequency unit 401 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 401 can also communicate with the network and other devices through a wireless communication system.
  • the terminal device provides users with wireless broadband Internet access through the network module 402, such as helping users to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 403 can convert the audio data received by the radio frequency unit 401 or the network module 402 or stored in the memory 409 into audio signals and output them as sounds. Moreover, the audio output unit 403 may also provide audio output related to a specific function performed by the terminal device 400 (for example, call signal reception sound, message reception sound, etc.).
  • the audio output unit 403 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 404 is used to receive audio or video signals.
  • the input unit 404 may include a graphics processing unit (GPU) 4041 and a microphone 4042.
  • the graphics processor 4041 is configured to monitor images of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. Data is processed.
  • the processed image frame can be displayed on the display unit 406.
  • the image frame processed by the graphics processor 4041 may be stored in the memory 409 (or other storage medium) or sent via the radio frequency unit 401 or the network module 402.
  • the microphone 4042 can receive sound and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to a mobile communication base station via the radio frequency unit 401 in the case of a telephone call mode for output.
  • the terminal device 400 also includes at least one sensor 405, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 4061 according to the brightness of the ambient light.
  • the proximity sensor can close the display panel 4061 and the display panel 4061 when the terminal device 400 is moved to the ear. / Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three-axis), and can detect the magnitude and direction of gravity when it is stationary, and can be used to identify the posture of the terminal device (such as horizontal and vertical screen switching, related games) , Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, percussion), etc.; sensor 405 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, Infrared sensors, etc., will not be repeated here.
  • the display unit 406 is used to display information input by the user or information provided to the user.
  • the display unit 406 may include a display panel 4061, and the display panel 4061 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 407 can be used to receive input numeric or character information, and generate key signal input related to user settings and function control of the terminal device.
  • the user input unit 407 includes a touch panel 4071 and other input devices 4072.
  • the touch panel 4071 also called a touch screen, can collect user touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 4071 or near the touch panel 4071. operating).
  • the touch panel 4071 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the user's touch position, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it To the processor 410, the command sent by the processor 410 is received and executed.
  • the touch panel 4071 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 407 may also include other input devices 4072.
  • other input devices 4072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the touch panel 4071 can cover the display panel 4061. When the touch panel 4071 detects a touch operation on or near it, it transmits it to the processor 410 to determine the type of the touch event. The type of event provides corresponding visual output on the display panel 4061.
  • the touch panel 4071 and the display panel 4061 are used as two independent components to implement the input and output functions of the terminal device, in some embodiments, the touch panel 4071 and the display panel 4061 can be integrated
  • the implementation of the input and output functions of the terminal device is not specifically limited here.
  • the interface unit 408 is an interface for connecting an external device with the terminal device 400.
  • the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 408 may be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the terminal device 400 or may be used to connect to the terminal device 400 and external Transfer data between devices.
  • the memory 409 can be used to store software programs and various data.
  • the memory 409 may mainly include a storage program area and a storage data area.
  • the storage program area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data (such as audio data, phone book, etc.) created by the use of mobile phones.
  • the memory 409 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the processor 410 is the control center of the terminal device. It uses various interfaces and lines to connect the various parts of the entire terminal device, runs or executes the software programs and/or modules stored in the memory 409, and calls the data stored in the memory 409 , Perform various functions of the terminal equipment and process data, so as to monitor the terminal equipment as a whole.
  • the processor 410 may include one or more processing units; optionally, the processor 410 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, and application programs, etc.
  • the adjustment processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 410.
  • the terminal device 400 may also include a power supply 411 (such as a battery) for supplying power to various components.
  • a power supply 411 (such as a battery) for supplying power to various components.
  • the power supply 411 may be logically connected to the processor 410 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal device 400 includes some functional modules not shown, which will not be repeated here.
  • the embodiment of the present disclosure also provides a computer-readable storage medium, the computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by a processor, the implementation of the multiple TPR configuration method embodiments provided by the embodiments of the present disclosure Each process can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.
  • the functional blocks shown in the above-mentioned structural block diagram can be implemented as hardware, software, firmware, or a combination thereof.
  • it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, and so on.
  • ASIC application specific integrated circuit
  • the elements of the present disclosure are programs or code segments used to perform required tasks.
  • the program or code segment may be stored in a machine-readable medium, or transmitted on a transmission medium or communication link through a data signal carried in a carrier wave.
  • "Machine-readable medium" may include any medium that can store or transmit information.
  • machine-readable media examples include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and so on.
  • the code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种多发送接收点TPR配置方法、设备及存储介质。该方法包括:配置一个物理信道配置信息元素IE对应多个控制资源集CORESET;或者,配置多个物理信道配置IE对应多个CORESET;其中,多个CORESET对应多个TRP,多个CORESET中的至少一个CORESET对应一个TRP。

Description

多发送接收点TPR配置方法、设备及存储介质
相关申请的交叉引用
本申请主张在2019年3月29日在中国提交的中国专利申请No.201910253502.8的优先权,其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域,尤其涉及一种多发送接收点TPR配置方法、设备及存储介质。
背景技术
在相关技术中,物理下行控制信道配置(PDCCH-Config)、物理下行共享信道配置(PDSCH-Config)、物理上行控制信道配置(PUCCH-Config)均是基于单发送接收点(Transmission Reception Point,TRP)设计的。在每个带宽部分(Bandwidth Part,BWP)上同时只能有一个PDCCH-Config、PDSCH-Config或PUCCH-Config起作用。当无线资源控制(Radio Resource Control,RRC)重新配置一个PDCCH-Config、PDSCH-Config或PUCCH-Config后,则新配置生效。
对于多TRP场景,终端可能会接收多个TRP发送的PDCCH或PDSCH,或者,终端可能会向多个TRP发送PUCCH。则相关技术中的配置不能满足多TRP场景的需求。
发明内容
本公开实施例提供一种多发送接收点TPR配置方法、设备及存储介质,以解决配置不能满足多TRP场景需求的问题。
第一方面,本公开实施例提供了一种多TPR配置方法,所述方法包括:
配置一个物理信道配置信息元素(Information Element,IE)对应多个控制资源集(CORESET);或者,
配置多个物理信道配置IE对应多个CORESET;其中,
多个CORESET对应多个TRP,多个CORESET中的至少一个CORESET对应一个TRP。
第二方面,本公开实施例提供了一种多TPR配置设备,所述设备包括:
第一配置单元,用于配置一个物理信道配置信息元素IE对应多个控制资源集CORESET;或者,
第二配置单元,用于配置多个物理信道配置IE对应多个CORESET;
其中,多个CORESET对应多个TRP,多个CORESET中的至少一个CORESET对应一个TRP。
第三方面,本公开实施例提供了一种多TPR配置设备,所述设备包括:处理器、存储器及存储在存储器上并可在处理器上运行的计算机程序,计算机程序被处理器执行时实现本公开实施例提供的多TPR配置方法的步骤。
第四方面,本公开实施例提供了一种计算机可读存储介质,所述计算机可读存储介质上存储计算机程序,计算机程序被处理器执行时实现本公开实施例提供的多TPR配置方法的步骤。
本公开实施例的多TPR配置方法、设备及存储介质,所配置出的物理信道配置能够满足多TRP场景需求。
附图说明
为了更清楚地说明本公开实施例的技术方案,下面将对本公开实施例中所需要使用的附图作简单地介绍,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1示出了本公开实施例提供的多TPR配置方法的流程示意图;
图2示出了本公开实施例提供的多TPR配置设备的硬件结构示意图;
图3示出了本公开实施例提供的终端设备的硬件结构示意图。
具体实施方式
下面将详细描述本公开的各个方面的特征和示例性实施例,为了使本公开的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本公 开进行进一步详细描述。应理解,此处所描述的具体实施例仅被配置为解释本公开,并不被配置为限定本公开。对于本领域技术人员来说,本公开可以在不需要这些具体细节中的一些细节的情况下实施。下面对实施例的描述仅仅是为了通过示出本公开的示例来提供对本公开更好的理解。
需要说明的是,在本文中,诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下,由语句“包括……”限定的要素,并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
为了解决相关技术问题,本公开实施例提供一种多TPR配置方法、设备及存储介质。下面首先对本公开实施例提供的多TPR配置方法进行详细说明。
本公开实施例提供的多TPR配置方法可选地适用于多TPR配置设备。多TPR配置设备可以为基站,该基站可以为通常所用的基站,也可以为演进型基站(evolved node base station,eNB),还可以为5G系统中的网络侧设备(例如下一代基站(next generation node base station,gNB)或者后续演进通信系统中的网络侧设备。然而,上述用词并不构成对本公开保护范围的限制。
本公开实施例提供的多TPR配置方法可以包括:配置一个物理信道配置IE对应多个CORESET,或者,配置多个物理信道配置IE对应多个CORESET。其中,多个CORESET对应多个TRP,多个CORESET中的至少一个CORESET对应一个TRP。
本公开实施例的多TPR配置方法,所配置出的物理信道配置能够满足多TRP场景需求。
在本公开的一个实施例中,本公开实施例提供的多TPR配置方法还可以包括:配置多个CORESET中的至少一个CORESET与一个TRP的对应关系。本公开实施例提供的多TPR配置方法如图2所示,图2示出了本公开实施例提供的多TPR配置方法的流程示意图。多TPR配置方法可以包括:
S101:配置一个物理信道配置IE对应多个CORESET,或者,配置多个 物理信道配置IE对应多个CORESET。
S102:配置多个CORESET中的至少一个CORESET与一个TRP的对应关系。
在本公开的一个实施例中,物理信道配置IE包括以下所列项中的至少一种:
物理下行控制信道配置IE(Physical downlink control channel-Config IE,PDCCH-Config IE)、物理下行共享信道配置IE(Physical downlink shared channel-Config IE,PDSCH-Config IE)和物理上行控制信道配置IE(Physical Uplink Control Channel-Config IE,PUCCH-Config IE)。
在本公开的一个实施例中,配置多个CORESET中的至少一个CORESET与一个TRP的对应关系,可以包括:将多个CORESET进行分组,得到多个CORESET组;配置每个CORESET组与一个TRP的对应关系。
可以理解的是,一个CORESET组包括多个CORESET。
示例性地,假设有6个CORESET,6个CORESET分别为:CORESET1、CORESET2、CORESET3、CORESET4、CORESET5和CORESET6。将6个CORESET分为三组:CORESET一组、CORESET二组和CORESET三组,其中,CORESET一组包括:CORESET1和CORESET2和CORESET3;CORESET二组包括:CORESET4和CORESET5;CORESET三组包括:CORESET6。其中每个CORESET组对应一个TRP。更进一步,可以显式配置CORESET一组对应TRP1,配置CORESET二组对应TRP2,配置CORESET三组对应TRP3。
在本公开的一个实施例中,配置多个CORESET中的至少一个CORESET与一个TRP的关联关系,可以包括:确定多个默认CORESET,每个默认CORESET对应一个TRP;配置其他CORESET分别与一个默认CORESET的关联关系。因此具有关联关系的至少两个CORESET对应一个TRP。更进一步,可以显式配置每个默认CORESET与一个TRP的对应关系,从而确定具有关联关系的至少两个CORESET与一个TRP的对应关系。
在本公开的一个实施例中,CORESET与TRP的对应关系,可以配置在无线资源控制(Radio Resource Control,RRC)信令的物理下行控制信道配置IE(PDCCH-Config IE)中。
在本公开的一个实施例中,多个CORESET中的至少一个CORESET对应一个TRP,可以包括:将多个CORESET进行分组,得到多个CORESET组,其中每个CORESET组对应一个TRP。
在本公开的一个实施例中,多个CORESET中的至少一个CORESET对应一个TRP,可以包括:确定多个默认CORESET;配置其他至少一个CORESET分别与一个默认CORESET的关联关系;其中具有关联关系的CORESET对应一个TRP。
在本公开的一个实施例中,CORESET与TRP的对应关系,还可以配置在其他无线资源控制(Radio Resource Control,RRC)信令中,也就是说,可以在RRC信令中增加CORESET与TRP的对应关系的配置IE。
在本公开的一个实施例中,配置一个物理信道配置IE对应多个CORESET,可以包括:配置物理信道配置IE包括的域对应多个配置IE。
其中,每个配置IE关联一个TRP对应的多个CORESET,或,每个配置IE关联一个TRP对应的CORESET组,或,每个配置IE关联一个TRP对应的CORESET组的TCI状态。
在本公开的一个实施例中,物理信道配置IE包括物理下行控制信道配置PDCCH-Config IE;上述域包括以下所列域中的至少一种:
下行链路优先权(downlinkPreemption)域、发送功率控制-物理上行共享信道(tpc-PUSCH)域、发送功率控制-物理上行控制信道(tpc-PUCCH)域和发送功率控制-信道探测参考信号(tpc-SRS)域。
在本公开的一个实施例中,物理信道配置IE包括物理下行共享信道配置PDSCH-Config IE;上述域包括以下所列域中的至少一种:
PDSCH初始化数据扰码(dataScramblingIdentityPDSCH)域、调制和编码方案表(mcs-Table)域、下行控制信息可调度的最大编码码字数量(maxNrofCodeWordsScheduledByDCI)域以及非周期触发的零功率信道状态信息参考信号资源集相关的aperiodic-ZP-CSI-RS-ResourceSetsToAddModList域和aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList域。
在本公开的一个实施例中,物理信道配置IE包括物理上行控制信道配置PUCCH-Config IE;上述域包括PUCCH-Config IE包括的域中的至少一种。
可以理解的是,PUCCH-Config IE包括以下域:
PUCCH资源集域、PUCCH资源域、PUCCH格式域、调度请求资源域、多信道状态信息物理上行控制信道资源(multi-CSI-PUCCH-ResourceList)域、定时列表(dl-DataToUL-ACK)域、参考信号与PUCCH的空间关系域和PUCCH功率控制(pucch-PowerControl)域。
其中,PUCCH资源集域包括:PUCCH资源集添加修改(resourceSetToAddModList)域和PUCCH资源集释放(resourceSetToReleaseList)域。PUCCH资源域包括:PUCCH资源添加修改(resourceSetToAddModList)域和PUCCH资源释放(resourceToReleaseList)域。PUCCH格式域包括:format1域、format2域、format3域和format4域。调度请求资源域包括:调度请求资源添加修改(schedulingRequestResourceToAddModList)域和调度请求资源释放(schedulingRequestResourceToReleaseList)域。参考信号与PUCCH的空间关系域包括:参考信号与PUCCH的空间关系添加修改(spatialRelationInfoToAddModList)域和参考信号与PUCCH的空间关系释放(spatialRelationInfoToReleaseList)域。
在本公开的一个实施例中,配置物理信道配置IE包括的域对应多个配置IE,可以包括:将物理信道配置IE包括的域扩展为多个域;其中,每个域对应一个配置IE。
以配置PDCCH-Config IE为例。将PDCCH-Config IE中的downlinkPreemption域扩展为N个域,N个域分别为downlinkPreemption域、downlinkPreemption1域、……、downlinkPreemptionN-1域。上述扩展的N个域分别关联多个CORESET或一个CORESET组。即上述N个域分别对应一个配置IE。
可以按照预设的关联关系,downlinkPreemption域、downlinkPreemption1域、……、downlinkPreemptionN-1域依次关联到多个CORESET ID或CORESET ID组,例如按照默认CORESET ID由小到大,或CORESET组ID由小到大的顺序依次关联。在CORESET ID较小的CORESET上发送PDCCH时,使用PDCCH-Config中的downlinkPreemption1、tpc-PUSCH1、tpc-PUCCH1、tpc-SRS1。在CORESET ID较大的CORESET上发送的PDCCH时,使用PDCCH-Config中的downlinkPreemption2、tpc-PUSCH2、tpc-PUCCH2、 tpc-SRS2。
扩展为两个配置域代码如下:
downlinkPreemption1 SetupRelease{DownlinkPreemption}OPTIONAL,
downlinkPreemption2 SetupRelease{DownlinkPreemption}OPTIONAL,
tpc-PUSCH1 SetupRelease{PUSCH-TPC-CommandConfig}OPTIONAL,
tpc-PUSCH2 SetupRelease{PUSCH-TPC-CommandConfig}OPTIONAL,
tpc-PUCCH1 SetupRelease{PUCCH-TPC-CommandConfig}OPTIONAL,
tpc-PUCCH2 SetupRelease{PUCCH-TPC-CommandConfig}OPTIONAL,
tpc-SRS1 SetupRelease{SRS-TPC-CommandConfig}OPTIONAL,
tpc-SRS2 SetupRelease{SRS-TPC-CommandConfig}OPTIONAL,
其中,OPTIONAL表示该项为可选项。
在本公开的一个实施例中,扩展的多个域位于物理信道配置IE最后。
位于PDCCH-Config IE最后的扩展出的两个配置域代码如下:
downlinkPreemption1 SetupRelease{DownlinkPreemption}OPTIONAL,
tpc-PUSCH1 SetupRelease{PUSCH-TPC-CommandConfig}OPTIONAL,
tpc-PUCCH1 SetupRelease{PUCCH-TPC-CommandConfig}OPTIONAL,
tpc-SRS1 SetupRelease{SRS-TPC-CommandConfig}OPTIONAL,
downlinkPreemption2 SetupRelease{DownlinkPreemption}OPTIONAL,
tpc-PUSCH2 SetupRelease{PUSCH-TPC-CommandConfig}OPTIONAL,
tpc-PUCCH2 SetupRelease{PUCCH-TPC-CommandConfig}OPTIONAL,
tpc-SRS2 SetupRelease{SRS-TPC-CommandConfig}OPTIONAL,
通过将扩展的多个域配置于物理信道配置IE最后,使得物理信道配置能够兼容较低版本的终端设备。
在本公开的一个实施例中,配置物理信道配置IE包括的域对应多个配置IE,可以包括:将物理信道配置IE包括的域扩展为IE配置序列;其中,IE配置序列中的每一个元素对应一个配置。
在本公开的一个实施例中,对于物理信道配置IE中仅对应一个配置IE的域,所述域对应的配置IE关联多个TRP。
以配置PDCCH-Config IE中的downlinkPreemption域为例。将downlinkPreemption域扩展为IE配置序列。扩展后的IE配置序列如下:
downlinkPreemption sequence(SIZE(1..N))OF SetupRelease{DownlinkPreemption}OPTIONAL,
其中,该IE配置序列中包括N个元素,每个元素对应一个配置IE。
假设N为2,IE配置序列中第一个元素关联到较小的CORESET ID,IE配置序列中第二个元素关联到较小的CORESET ID;较小的CORESET ID和较大的CORESET ID分别对应一个TRP。在CORESET ID较小的CORESET上发送PDCCH时,使用PDCCH-Config中的downlinkPreemption域序列中的第一个元素对应的配置。在CORESET ID较大的CORESET上发送PDCCH时,使用PDCCH-Config中的downlinkPreemption域序列中的第二个元素对应的配置。
在本公开的一个实施例中,下行控制信息(Downlink Control Information,DCI)调度、上行动态授权调度或配置授权类型2(Configured grant type 2:RRC配置发送周期,L1/L2层控制信令激活或去激活)调度,均可通过发送信令的DCI所属的CORESET确定TRP,从而终端可以确定PDCCH-Config IE、PDSCH-Config IE或PUCCH-Config IE包括的各域的哪个配置IE应用于终端接收的PDCCH、PDSCH,以及终端发送的PUCCH。
在本公开的一个实施例中,对于RRC配置授权的PUSCH、PUCCH、信道探测参考信号(Sounding Reference Signal,SRS)传输配置授权类型1(Configured grant type 1:RRC配置或激活的上行传输授权),可以由配置的传输配置指示(Transmission Configuration Indicator,TCI)确定与TRP的关联,从而终端可以确定PDCCH-Config IE、PDSCH-Config IE或PUCCH-Config IE包括的各域的哪个配置IE应用于终端接收的PDCCH、PDSCH,以及终端发送的PUCCH。
在本公开的一个实施例中,多TPR配置设备可以采用上述任意一个域配置多个TPR使用相同的配置。
在本公开的一个实施例中,TCI状态(TCI-States)域可以包括所有的TRP的TCI状态,每个BWP的TCI状态可以为全局编号。
其中,本公开实施例的全局编号指按照自然数顺序依次编号。
在本公开的一个实施例中,各个CORESET可以通过媒体接入控制(Medium Access Control,MAC)控制单元(Control Element,CE)激活各 自的MAC CE。PDSCH的TCI分别对应各自CORESET激活的TCI。
在本公开的一个实施例中,可以配置多个物理信道配置IE对应多个CORESET。配置多个物理信道配置IE对应多个CORESET,可以包括:在多个物理信道配置IE中的每一个物理信道配置IE内配置一个域与以下所列项中任意一种的对应关系:至少一个CORESET、一个CORESET组和一个TRP。
在本公开的一个实施例中,若一个物理信道配置IE中不存在与以下所列项中任意一种具有关联关系的域:至少一个CORESET、一个CORESET组和一个TRP;则,该物理信道配置IE与默认的一个CORESET、一个CORESET组和一个TRP关联。
示例性地,假设配置3个PUCCH-Config IE对应3个CORESET组。则同时配置3个PUCCH-Config IE,每个PUCCH-Config IE对应一个CORESET组。并且在每个PUCCH-Config IE内配置一个defaultControlResourceSetGroupID域与默认CORESET ID对应。
同时配置3个PDCCH-Config IE的代码可能为:
PDCCH-Config1::=SEQUENCE{
defaultControlResourceSetGroupID ControlResourceSetId
……
}
PDCCH-Config2::=SEQUENCE{
defaultControlResourceSetGroupID ControlResourceSetId
……
}
PDCCH-Config3::=SEQUENCE{
defaultControlResourceSetGroupID ControlResourceSetId
……
}
通过配置多个物理信道配置IE对应多个CORESET组,可以使得每个BWP上同时有多个物理信道配置,进而所配置出的物理信道配置能够满足多 TRP场景需求。
与上述的方法实施例相对应,本公开实施例还提供一种多TPR配置设备。多TPR配置设备可以包括:
第一配置单元,用于配置一个物理信道配置信息元素IE对应多个控制资源集CORESET。或者,
第二配置单元,用于配置多个物理信道配置IE对应多个CORESET。
其中,多个CORESET对应多个TRP,多个CORESET中的至少一个CORESET对应一个TRP。
在本公开的一个实施例中,多个CORESET中的至少一个CORESET对应一个TRP,包括:将所述多个CORESET进行分组,得到多个CORESET组;其中,每个CORESET组对应一个TRP。
在本公开的一个实施例中,所述多个CORESET中的至少一个CORESET对应一个TRP,包括:确定多个默认CORESET;配置其他至少一个CORESET分别与一个默认CORESET的关联关系;其中,具有关联关系的CORESET对应一个TRP。
在本公开的一个实施例中,本公开实施例提供的多TPR配置设备还可以包括:
第三配置单元,用于配置多个CORESET中的至少一个CORESET与一个TRP的对应关系。
在本公开的一个实施例中,第三配置单元,具体可以用于:
将多个CORESET进行分组,得到多个CORESET组;
配置每个CORESET组与一个TRP的对应关系。
在本公开的一个实施例中,第三配置单元,具体可以用于:
确定多个默认CORESET;
配置其他CORESET分别与一个默认CORESET的关联关系;
配置具有关联关系的两个CORESET与一个TRP的对应关系。
在本公开的一个实施例中,对应关系可以配置在物理下行控制信道配置IE中。
在本公开的一个实施例中,第一配置单元,具体可以用于:
配置物理信道配置IE包括的域对应多个配置IE;其中,每个配置IE关 联一个TRP对应的多个CORESET,或,每个配置IE关联一个TRP对应的CORESET组,或,每个配置IE关联一个TRP对应的CORESET组的传输配置指示TCI状态。
在本公开的一个实施例中,第一配置单元,具体可以用于:
将物理信道配置IE包括的域扩展为多个域;其中,每个域对应一个配置IE;或,
将物理信道配置IE包括的域扩展为IE配置序列;其中,IE配置序列中的每一个元素对应一个配置IE。
在本公开的一个实施例中,对于所述物理信道配置IE中仅对应一个配置IE的域,所述域对应的配置IE关联多个TRP。
在本公开的一个实施例中,第二配置单元,具体可以用于:在多个物理信道配置IE中的每一个物理信道配置IE内配置一个域与以下所列项中任意一种的对应关系:
至少一个CORESET、一个CORESET组和一个TRP。
在本公开的一个实施例中,若一个物理信道配置IE中不存在与以下所列项中任意一种具有关联关系的域:至少一个CORESET、一个CORESET组和一个TRP;
则该物理信道配置IE与默认的一个CORESET、一个CORESET组和一个TRP关联。
在本公开的一个实施例中,物理信道配置IE包括以下所列项中的至少一种:
物理下行控制信道配置PDCCH-Config IE;
物理下行共享信道配置PDSCH-Config IE;
物理上行控制信道配置PUCCH-Config IE。
图2示出了本公开实施例提供的多TPR配置设备的硬件结构示意图。多TPR配置设备包括:存储器301、处理器302、收发机303及存储在存储器301上并可在处理器302上运行的计算机程序。
其中,处理器302可以用于:配置一个物理信道配置信息元素IE对应多个控制资源集CORESET,或者,配置多个物理信道配置IE对应多个CORESET,其中,多个CORESET对应多个TRP,多个CORESET中的至少 一个CORESET对应一个TRP。
其中,在图2中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器302代表的一个或多个处理器和存储器301代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口提供接口。收发机303可以是多个元件,即包括发送机和收发机,提供用于在传输介质上与各种其他装置通信的单元,用于在处理器302的控制下接收和发送数据。处理器302负责管理总线架构和通常的处理,存储器301可以存储处理器302在执行操作时所使用的数据。
可选地,本公开实施例还提供一种多TPR配置设备,包括处理器302,存储器301,以及存储在存储器301上并可在处理器302上运行的计算机程序,该计算机程序被处理器302执行时实现应用于多TPR配置方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
图3示出了本公开实施例提供的终端设备的硬件结构示意图。该终端设备400包括但不限于:射频单元401、网络模块402、音频输出单元403、输入单元404、传感器405、显示单元406、用户输入单元407、接口单元408、存储器409、处理器410、以及电源411等部件。本领域技术人员可以理解,图3中示出的终端设备结构并不构成对终端设备的限定,终端设备可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。在本公开实施例中,终端设备包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
处理器410,用于根据物理信道配置IE,接收多个TRP的PDCCH或PDSCH;或者,向多个TRP发送PUCCH。
通过本公开实施例,所配置出的物理信道配置能够满足多TRP场景需求。
应理解的是,本公开实施例中,射频单元401可用于收发信息或通话过程中,信号的接收和发送,具体地,将来自基站的下行数据接收后,给处理器410处理;另外,将上行的数据发送给基站。通常,射频单元401包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外,射频单元401还可以通过无线通信系统与网络和其他设备通信。
终端设备通过网络模块402为用户提供了无线的宽带互联网访问,如帮 助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元403可以将射频单元401或网络模块402接收的或者在存储器409中存储的音频数据转换成音频信号并且输出为声音。而且,音频输出单元403还可以提供与终端设备400执行的特定功能相关的音频输出(例如,呼叫信号接收声音、消息接收声音等等)。音频输出单元403包括扬声器、蜂鸣器以及受话器等。
输入单元404用于接收音频或视频信号。输入单元404可以包括图形处理器(Graphics Processing Unit,GPU)4041和麦克风4042,图形处理器4041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元406上。经图形处理器4041处理后的图像帧可以存储在存储器409(或其它存储介质)中或者经由射频单元401或网络模块402进行发送。麦克风4042可以接收声音,并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元401发送到移动通信基站的格式输出。
终端设备400还包括至少一种传感器405,比如光传感器、运动传感器以及其他传感器。具体地,光传感器包括环境光传感器及接近传感器,其中,环境光传感器可根据环境光线的明暗来调节显示面板4061的亮度,接近传感器可在终端设备400移动到耳边时,关闭显示面板4061和/或背光。作为运动传感器的一种,加速计传感器可检测各个方向上(一般为三轴)加速度的大小,静止时可检测出重力的大小及方向,可用于识别终端设备姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等;传感器405还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等,在此不再赘述。
显示单元406用于显示由用户输入的信息或提供给用户的信息。显示单元406可包括显示面板4061,可以采用液晶显示器(Liquid Crystal Display,LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板4061。
用户输入单元407可用于接收输入的数字或字符信息,以及产生与终端 设备的用户设置以及功能控制有关的键信号输入。具体地,用户输入单元407包括触控面板4071以及其他输入设备4072。触控面板4071,也称为触摸屏,可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板4071上或在触控面板4071附近的操作)。触控面板4071可包括触摸检测装置和触摸控制器两个部分。其中,触摸检测装置检测用户的触摸方位,并检测触摸操作带来的信号,将信号传送给触摸控制器;触摸控制器从触摸检测装置上接收触摸信息,并将它转换成触点坐标,再送给处理器410,接收处理器410发来的命令并加以执行。此外,可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板4071。除了触控面板4071,用户输入单元407还可以包括其他输入设备4072。具体地,其他输入设备4072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆,在此不再赘述。
进一步地,触控面板4071可覆盖在显示面板4061上,当触控面板4071检测到在其上或附近的触摸操作后,传送给处理器410以确定触摸事件的类型,随后处理器410根据触摸事件的类型在显示面板4061上提供相应的视觉输出。虽然在图3中,触控面板4071与显示面板4061是作为两个独立的部件来实现终端设备的输入和输出功能,但是在某些实施例中,可以将触控面板4071与显示面板4061集成而实现终端设备的输入和输出功能,具体此处不做限定。
接口单元408为外部装置与终端设备400连接的接口。例如,外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元408可以用于接收来自外部装置的输入(例如,数据信息、电力等等)并且将接收到的输入传输到终端设备400内的一个或多个元件或者可以用于在终端设备400和外部装置之间传输数据。
存储器409可用于存储软件程序以及各种数据。存储器409可主要包括存储程序区和存储数据区,其中,存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等;存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外, 存储器409可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器410是终端设备的控制中心,利用各种接口和线路连接整个终端设备的各个部分,通过运行或执行存储在存储器409内的软件程序和/或模块,以及调用存储在存储器409内的数据,执行终端设备的各种功能和处理数据,从而对终端设备进行整体监控。处理器410可包括一个或多个处理单元;可选地,处理器410可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器410中。
终端设备400还可以包括给各个部件供电的电源411(比如电池),可选地,电源411可以通过电源管理系统与处理器410逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外,终端设备400包括一些未示出的功能模块,在此不再赘述。
本公开实施例还提供一种计算机可读存储介质,该计算机可读存储介质上存储有计算机程序指令;该计算机程序指令被处理器执行时实现本公开实施例提供的多TPR配置方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。其中,所述的计算机可读存储介质,如只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等。
需要明确的是,本公开并不局限于上文所描述并在图中示出的特定配置和处理。为了简明起见,这里省略了对已知方法的详细描述。在上述实施例中,描述和示出了若干具体的步骤作为示例。但是,本公开的方法过程并不限于所描述和示出的具体步骤,本领域的技术人员可以在领会本公开的精神后,作出各种改变、修改和添加,或者改变步骤之间的顺序。
以上所述的结构框图中所示的功能块可以实现为硬件、软件、固件或者它们的组合。当以硬件方式实现时,其可以例如是电子电路、专用集成电路(ASIC)、适当的固件、插件、功能卡等等。当以软件方式实现时,本公开的元素是被用于执行所需任务的程序或者代码段。程序或者代码段可以存储在机器可读介质中,或者通过载波中携带的数据信号在传输介质或者通信链路上传送。“机器可读介质”可以包括能够存储或传输信息的任何介质。机器 可读介质的例子包括电子电路、半导体存储器设备、ROM、闪存、可擦除ROM(EROM)、软盘、CD-ROM、光盘、硬盘、光纤介质、射频(RF)链路,等等。代码段可以经由诸如因特网、内联网等的计算机网络被下载。
还需要说明的是,本公开中提及的示例性实施例,基于一系列的步骤或者装置描述一些方法或系统。但是,本公开不局限于上述步骤的顺序,也就是说,可以按照实施例中提及的顺序执行步骤,也可以不同于实施例中的顺序,或者若干步骤同时执行。
以上所述,仅为本公开的具体实施方式,所属领域的技术人员可以清楚地了解到,为了描述的方便和简洁,上述描述的系统、模块和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。应理解,本公开的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本公开揭露的技术范围内,可轻易想到各种等效的修改或替换,这些修改或替换都应涵盖在本公开的保护范围之内。

Claims (14)

  1. 一种多发送接收点TPR配置方法,包括:
    配置一个物理信道配置信息元素IE对应多个控制资源集CORESET;或者,
    配置多个物理信道配置IE对应多个CORESET;其中,
    所述多个CORESET对应多个TRP,所述多个CORESET中的至少一个CORESET对应一个TRP。
  2. 根据权利要求1所述的方法,其中,所述多个CORESET中的至少一个CORESET对应一个TRP,包括:
    将所述多个CORESET进行分组,得到多个CORESET组;其中,每个CORESET组对应一个TRP。
  3. 根据权利要求1所述的方法,其中,所述多个CORESET中的至少一个CORESET对应一个TRP,包括:
    确定多个默认CORESET;配置其他至少一个CORESET分别与一个默认CORESET的关联关系;其中,具有关联关系的CORESET对应一个TRP。
  4. 根据权利要求1所述的方法,其中,所述方法还包括:
    配置所述多个CORESET中的至少一个CORESET与一个TRP的对应关系。
  5. 根据权利要求4所述的方法,其中,所述对应关系配置在物理下行控制信道配置PDCCH-Config IE中。
  6. 根据权利要求1所述的方法,其中,所述配置一个物理信道配置IE对应多个控制资源集CORESET,包括:
    配置所述物理信道配置IE包括的至少一个域对应多个配置IE;其中,每个配置IE关联一个TRP对应的多个CORESET,或,每个配置IE关联一个TRP对应的CORESET组,或,每个配置IE关联一个TRP对应的CORESET组的传输配置指示TCI状态。
  7. 根据权利要求6所述的方法,其中,所述配置所述物理信道配置IE包括的至少一个域对应多个配置IE,包括:
    将所述物理信道配置IE包括的至少一个域扩展为多个域;其中,每个域对应一个配置IE;或,
    将所述物理信道配置IE包括的至少一个域扩展为IE配置序列;其中,所述IE配置序列中的每一个元素对应一个配置IE。
  8. 根据权利要求7所述的方法,其中,对于所述物理信道配置IE中仅对应一个配置IE的域,所述域对应的配置IE关联多个TRP。
  9. 根据权利要求1所述的方法,其中,所述配置多个物理信道配置IE对应多个CORESET,包括:
    在所述多个物理信道配置IE中的每一个物理信道配置IE内配置一个域与以下所列项中任意一种的关联关系:
    至少一个CORESET、一个CORESET组和一个TRP。
  10. 根据权利要求9所述的方法,其中,若一个物理信道配置IE中不存在与以下所列项中任意一种具有关联关系的域:
    至少一个CORESET、一个CORESET组和一个TRP;
    则该物理信道配置IE与默认的一个CORESET、一个CORESET组和一个TRP关联。
  11. 根据权利要求1所述的方法,其中,所述物理信道配置IE包括以下所列项中的至少一种:
    物理下行控制信道配置PDCCH-Config IE;
    物理下行共享信道配置PDSCH-Config IE;
    物理上行控制信道配置PUCCH-Config IE。
  12. 一种多发送接收点TPR配置设备,包括:
    第一配置单元,用于配置一个物理信道配置信息元素IE对应多个控制资源集CORESET;或者,
    第二配置单元,用于配置多个物理信道配置IE对应多个CORESET;
    其中,所述多个CORESET对应多个TRP,所述多个CORESET中的至少一个CORESET对应一个TRP。
  13. 一种多发送接收点TPR配置设备,包括:处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序,所述计算机程序被所 述处理器执行时实现如权利要求1至11中任一项所述的多发送接收点TPR配置方法的步骤。
  14. 一种计算机可读存储介质,其中,所述计算机可读存储介质上存储计算机程序,所述计算机程序被处理器执行时实现如权利要求1至11中任一项所述的多发送接收点TPR配置方法的步骤。
PCT/CN2020/081702 2019-03-29 2020-03-27 多发送接收点tpr配置方法、设备及存储介质 Ceased WO2020200100A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/486,876 US12041629B2 (en) 2019-03-29 2021-09-27 Multi-transmission reception point (TRP) configuration method and device, and storage medium
US18/747,357 US20240340910A1 (en) 2019-03-29 2024-06-18 Multi-transmission reception point (trp) configuration method and device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910253502.8 2019-03-29
CN201910253502.8A CN111435920B (zh) 2019-03-29 2019-03-29 多发送接收点trp配置方法、设备及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/486,876 Continuation US12041629B2 (en) 2019-03-29 2021-09-27 Multi-transmission reception point (TRP) configuration method and device, and storage medium

Publications (1)

Publication Number Publication Date
WO2020200100A1 true WO2020200100A1 (zh) 2020-10-08

Family

ID=71580121

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/081702 Ceased WO2020200100A1 (zh) 2019-03-29 2020-03-27 多发送接收点tpr配置方法、设备及存储介质

Country Status (3)

Country Link
US (2) US12041629B2 (zh)
CN (1) CN111435920B (zh)
WO (1) WO2020200100A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11569951B2 (en) 2019-08-15 2023-01-31 Ofinno, Llc Radio link monitoring in a multi-TRP scenario
WO2022027640A1 (en) 2020-08-07 2022-02-10 JRD Communication (Shenzhen) Ltd. Transmitter, receiver and communication method for improving uplink transmission with configured grant
KR20220027652A (ko) * 2020-08-27 2022-03-08 삼성전자주식회사 무선 통신 시스템에서 협력 통신을 이용한 데이터 송수신 방법 및 장치
WO2022067501A1 (en) * 2020-09-29 2022-04-07 Lenovo (Beijing) Limited Methods and apparatus of resource mapping and signaling indication for joint coreset for enhanced pdcch transmission with multiple trps
EP4335199A4 (en) * 2021-05-08 2025-01-15 Qualcomm Incorporated Transmission control indicator state update for multiple transmit receive points
CN117426075A (zh) * 2021-05-17 2024-01-19 Oppo广东移动通信有限公司 多点通信协调机制及其操作方法
CN117676875A (zh) * 2022-08-12 2024-03-08 华为技术有限公司 上行传输方法以及相关装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109451585A (zh) * 2018-04-04 2019-03-08 华为技术有限公司 一种通信方法及装置
US20190098520A1 (en) * 2017-09-27 2019-03-28 Electronics And Telecommunications Research Institute Method for managing radio resources in communication system and apparatus for the same

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10219259B2 (en) * 2016-05-13 2019-02-26 Qualcomm Incorporated Uplink-based cell selection
CN108271259B (zh) * 2016-12-30 2023-10-24 华为技术有限公司 控制信道的资源指示方法、用户设备和网络设备
US11134492B2 (en) * 2017-04-12 2021-09-28 Samsung Electronics Co., Ltd. Method and apparatus for beam recovery in next generation wireless systems
CN109121205B (zh) * 2017-06-22 2021-08-24 维沃移动通信有限公司 一种资源指示方法、移动终端及基站
CN109392140B (zh) * 2017-08-11 2020-07-28 维沃移动通信有限公司 一种用于监听pdcch的方法、终端及网络设备
CN112969223B (zh) * 2017-08-11 2022-09-30 中兴通讯股份有限公司 参数配置、功率确定方法及装置、通信节点
CN113316920B (zh) * 2019-01-11 2023-09-12 Lg电子株式会社 在无线通信系统中发送/接收数据的方法及其装置
WO2020165702A1 (en) * 2019-02-15 2020-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Harq ack for multi-pdcch scheduled pdsch transmission over multiple transmission reception points

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190098520A1 (en) * 2017-09-27 2019-03-28 Electronics And Telecommunications Research Institute Method for managing radio resources in communication system and apparatus for the same
CN109451585A (zh) * 2018-04-04 2019-03-08 华为技术有限公司 一种通信方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Summary of AI: 7.2.8.2 Enhancements on Multi-TRP/Panel Transmission of Offline Discussion", 3GPP TSG RAN WG1 MEETING #96 R1-190ABCD (R1-1903541 FROM 3GPP.ORG), 1 March 2019 (2019-03-01), XP051707743, DOI: 20200601152612X *
VIVO: "Further Discussion on Multi-TRP Transmission", 3GPP TSG RAN WG1 #96BIS R1-1904096, 12 April 2019 (2019-04-12), XP051699474, DOI: 20200601152735PX *

Also Published As

Publication number Publication date
US12041629B2 (en) 2024-07-16
CN111435920B (zh) 2022-03-22
CN111435920A (zh) 2020-07-21
US20240340910A1 (en) 2024-10-10
US20220015078A1 (en) 2022-01-13

Similar Documents

Publication Publication Date Title
US11576183B2 (en) Method of receiving downlink channel, method of sending downlink channel, terminal and base station
KR102676152B1 (ko) 지시 정보의 전송 방법 및 통신 장치
CN111435920B (zh) 多发送接收点trp配置方法、设备及存储介质
US11936474B2 (en) Transmission antenna switching method and terminal device
US20220360472A1 (en) Uplink transmission method and apparatus, device, and storage medium
US20220369293A1 (en) Beam information determining method, terminal, and network side device
WO2020216209A1 (zh) 指示空间关系信息的方法及装置、通信设备
CN113225818B (zh) Qcl的确定方法、终端及网络侧设备
WO2021179966A1 (zh) 信号传输方法、信息指示方法和通信设备
CN110034876A (zh) Pucch资源指示、处理方法、网络侧设备、用户终端
WO2019091266A1 (zh) 载波配置方法、用户终端和网络侧设备
WO2021027713A1 (zh) 上行传输方法、上行传输控制方法及相关设备
WO2020228529A1 (zh) 半静态调度配置的配置方法、设备及系统
WO2021018130A1 (zh) 物理上行链路控制信道传输方法、装置、设备及介质
WO2020182124A1 (zh) 传输方法、网络设备和终端
WO2019157915A1 (zh) Csi资源类型的确定方法、终端和网络侧设备
WO2021155807A1 (zh) 传输控制方法、终端及网络设备
US11452081B2 (en) Spatial relationship determination method, terminal and base station
WO2020228537A1 (zh) 资源确定方法、资源指示方法、终端及网络侧设备
WO2020147778A1 (zh) 测量间隔的处理方法、网络设备、终端设备和存储介质
CN113271681B (zh) Pusch传输方法、终端及网络设备
KR102589486B1 (ko) 업링크 전송 방법 및 단말
US12446009B2 (en) Resource indication method and communications device
CN112888012B (zh) 测量目的确定方法、装置、设备及介质
WO2020200101A1 (zh) 信道处理方法、装置、终端设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20783894

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20783894

Country of ref document: EP

Kind code of ref document: A1