WO2020029926A1 - 一种带宽部分处理方法及装置 - Google Patents
一种带宽部分处理方法及装置 Download PDFInfo
- Publication number
- WO2020029926A1 WO2020029926A1 PCT/CN2019/099310 CN2019099310W WO2020029926A1 WO 2020029926 A1 WO2020029926 A1 WO 2020029926A1 CN 2019099310 W CN2019099310 W CN 2019099310W WO 2020029926 A1 WO2020029926 A1 WO 2020029926A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bwp
- carrier
- default
- group
- terminal
- Prior art date
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 19
- 230000009849 deactivation Effects 0.000 claims abstract description 157
- 238000000034 method Methods 0.000 claims abstract description 124
- 238000012545 processing Methods 0.000 claims description 77
- 230000011664 signaling Effects 0.000 claims description 19
- 230000003213 activating effect Effects 0.000 claims description 11
- 239000013256 coordination polymer Substances 0.000 claims description 3
- 125000004122 cyclic group Chemical group 0.000 claims description 3
- 230000006854 communication Effects 0.000 abstract description 27
- 230000008569 process Effects 0.000 abstract description 21
- 238000012544 monitoring process Methods 0.000 abstract description 8
- 230000006870 function Effects 0.000 description 30
- 238000010586 diagram Methods 0.000 description 24
- 230000004913 activation Effects 0.000 description 23
- 238000001994 activation Methods 0.000 description 23
- 238000004891 communication Methods 0.000 description 23
- 238000013461 design Methods 0.000 description 17
- 230000005540 biological transmission Effects 0.000 description 7
- 238000004590 computer program Methods 0.000 description 7
- 230000008054 signal transmission Effects 0.000 description 4
- 235000019800 disodium phosphate Nutrition 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000003190 augmentative effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0096—Indication of changes in allocation
- H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0241—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where no transmission is received, e.g. out of range of the transmitter
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present application relates to the field of communication technologies, and in particular, to a bandwidth part (BWP) processing method and device.
- BWP bandwidth part
- the system bandwidth or the bandwidth of the carrier up to 400 megahertz (MHz).
- the terminal usually supports a bandwidth capability smaller than the system bandwidth or the carrier bandwidth.
- the bandwidth capability of the terminal may refer to the maximum supported bandwidth of the terminal.
- the bandwidth capability supported by the terminal may be 20MHz, 50MHz, 100MHz, and so on.
- each BWP may include some resources in the frequency domain. For example, a section of continuous resources; for example, a BWP includes a set of continuous resource blocks (RBs) on a carrier.
- a network device (for example, a base station) may assign a terminal to a BWP that the terminal can support. The network device can activate the BWP configured for the terminal, and then perform signal transmission with the terminal on the activated BWP. Currently, at the same time, the network device activates only one BWP on the carrier for the terminal on a carrier, so that the network device and the terminal transmit signals on the activated BWP.
- NR systems can support more and more types of services. Signals of different types of services may need to be transmitted through different BWPs on the carrier. If a carrier supports only one activated BWP at the same time, It is difficult to meet the signal transmission requirements. In order to transmit signals of multiple different types of services in time, multiple BWPs on a carrier can be activated. However, when multiple BWPs are activated at the same time on a carrier, if the existing processing method is still used for BWP activation and deactivation processing, unnecessary operations may be caused, thereby increasing the power consumption of the device.
- the embodiments of the present application provide a method and an apparatus for processing a bandwidth portion, so as to reduce power consumption of a device in a communication process.
- an embodiment of the present application provides a method for processing a bandwidth portion.
- the method may be executed by a terminal or a communication device (such as a chip system) capable of supporting the terminal to implement the method.
- the method performed by the terminal is taken as an example. Describe.
- the method includes: when a deactivation timer corresponding to an activated first BWP expires, determining whether a carrier in which the first BWP is located includes a second BWP in an activated state, and when the carrier includes a second BWP in an activated state To deactivate the first BWP.
- the present application provides a device for processing a bandwidth portion, including: a unit or a means for performing each step in the first aspect above.
- the present application provides a bandwidth part processing device, including at least one processor for connecting to a memory, where the at least one processor is configured to call a program stored in the memory to execute the method provided in the first aspect .
- the memory may be a memory inside the device or a memory outside the device.
- the present application provides a bandwidth processing device, including at least one processor and an interface circuit, where the at least one processor is configured to execute the method provided in the first aspect above.
- the present application provides a bandwidth part processing program, which is executed by a processor to execute the method in the first aspect above.
- a program product such as a computer-readable storage medium, including the program of the fifth aspect.
- a BWP performs deactivation. Without the need to perform the BWP handover process after the deactivation timer corresponding to the activated first BWP expires, as in the prior art, specifically, perform deactivation on the first BWP and activate the default BWP or initial in the carrier BWP. With the method of the present application, only the first BWP is deactivated to avoid unnecessary BWP switching processes.
- the terminal since the above method no longer activates the default BWP or the initial BWP, the terminal does not need to monitor the default BWP or the initial BWP. It only needs to monitor the second BWP in the current carrier, which can reduce the overhead of the terminal monitoring the BWP, thereby reducing the power consumption of the terminal during communication.
- the second BWP may be a default BWP or an initial BWP, and may also be a non-default BWP and a non-initial BWP, which is not limited in this application.
- the second BWP is taken as a non-default BWP and a non-initial BWP as an example.
- the terminal when the carrier includes the second BWP in an activated state, the terminal may not activate a default BWP or an initial BWP in the carrier. In this way, the terminal does not need to monitor the default BWP or the initial BWP, which can reduce the overhead of the terminal monitoring the BWP, thereby reducing the power consumption of the terminal during communication.
- the terminal when the carrier does not include the second BWP in an activated state, the terminal activates a default BWP or an initial BWP in the carrier.
- the number of default BWPs configured in the carrier is not limited in this application. In a possible design, the number of default BWPs in the carrier is at least two. In this design, the terminal activating the default BWP in the carrier may include: activating all BWPs included in at least two of the default BWPs, or activating at least two of the default BWPs that meet a preset rule BWP.
- the preset rule may include:
- the BWP index is the largest
- BWP index is the smallest
- the maximum sub-carrier spacing SCS SCS
- the cyclic prefix CP is the largest
- CP is minimal; or,
- the parameters are the same as those of the first BWP.
- the carrier includes at least two BWP groups, each BWP group includes at least one BWP, and the number of BWPs in an active state at the same time in each BWP group is 1 or 0.
- determining whether the carrier where the first BWP is located includes a second BWP in an activated state includes:
- the first BWP group does not include the default BWP
- a BWP group, the second BWP group is a BWP group that does not include the first BWP among the at least two BWP groups; or
- the first BWP group does not include the default BWP and the initial BWP
- One BWP BWP group, and the second BWP group is a BWP group that does not include the first BWP among the at least two BWP groups.
- the carrier includes at least two BWP groups, and each of the BWP groups includes at least one BWP.
- determining whether the carrier on which the first BWP is located includes a second BWP in an active state includes: determining in a first BWP group whether a second BWP in an active state is included, and the first BWP The group is a BWP group including the first BWP among the at least two BWP groups.
- the timing durations of the deactivation timers corresponding to the BWPs in the same BWP group are the same.
- the timing duration of the deactivation timer may be carrier-specific or BWP-specific.
- the carrier specificity can be understood as that the timing duration of the deactivation timers maintained by any activated non-default BWP on the same carrier is the same.
- BWP specific can be understood as that the timing of the deactivation timer corresponds to a specific non-default BWP.
- the timing of the deactivation timer is configured as BWP specific, the deactivation timing maintained by multiple non-default BWPs in a carrier The timing of the router can be different.
- the timing duration of the deactivation timer may be related to a parameter of the BWP in the carrier.
- the parameters of the BWP may include SCS and / or CP.
- the BWP group is pre-configured through a predefined rule or configured through signaling.
- the predefined rules include that the parameters of BWPs in the same BWP group are the same, or that the BWPs in the same BWP group are configured with the same default BWP.
- FIGS. 1a to 1c are schematic diagrams of a configuration of BWP in a carrier bandwidth provided by an embodiment of the present application
- FIG. 2 is a schematic diagram of a communication system applicable to an embodiment of the present application.
- FIG. 3 is a schematic diagram of a network architecture according to an embodiment of the present application.
- FIG. 4 is a schematic diagram of another network architecture according to an embodiment of the present application.
- FIG. 5 is an implementation flowchart of a method for processing a bandwidth part according to an embodiment of the present application
- FIG. 6a to FIG. 6c are schematic diagrams of a method for processing a bandwidth part according to an embodiment of the present application.
- FIG. 7 is an implementation flowchart of another method for processing a bandwidth part according to an embodiment of the present application.
- FIG. 8 is a schematic diagram of another method for processing a bandwidth part according to an embodiment of the present application.
- FIG. 9 is an implementation flowchart of another method for processing a bandwidth part according to an embodiment of the present application.
- FIG. 10 is a schematic diagram of another method for processing a bandwidth part according to an embodiment of the present application.
- FIG. 11 is a schematic structural diagram of a bandwidth part processing apparatus according to an embodiment of the present application.
- FIG. 12 is a schematic diagram of a terminal according to an embodiment of the present application.
- Terminal which can be a device that provides voice and / or data connectivity to users, also known as user equipment (UE), mobile station (MS), mobile terminal (MT) Wait.
- UE user equipment
- MS mobile station
- MT mobile terminal
- some examples of terminals are: mobile phones, tablet computers, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (augmented reality) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, and smart grids Wireless terminals, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and the like.
- a network device may refer to a device in a wireless network, such as a radio access network (RAN) node (or device) that connects a terminal to the wireless network, and may also be referred to as a base station.
- RAN nodes are: Node B (gNB) which continues to evolve, transmission reception point (TRP), evolved Node B (eNB), radio network controller (radio network controller), RNC), Node B (Node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home NodeB, or home NodeB, HNB) Baseband unit (BBU), or wireless fidelity (Wifi) access point (AP).
- TRP transmission reception point
- eNB evolved Node B
- RNC radio network controller
- Node B Node B, NB
- BSC base station controller
- BTS base transceiver station
- home base station e.g., home NodeB, or home NodeB, HNB
- BBU Base
- the RAN may include a centralized unit (CU) node and a distributed unit (DU) node.
- CU centralized unit
- DU distributed unit
- This structure separates the protocol layer of the eNB in a long term evolution (LTE) system. Some protocol layer functions are centrally controlled by the CU. The remaining part or all of the protocol layer functions are distributed in the DU. Centralized control of DU.
- LTE long term evolution
- System bandwidth refers to the bandwidth supported by a carrier in the NR system, which can also be called carrier bandwidth or carrier.
- the carrier bandwidth of the NR system can be one of 10 MHz, 15 MHz, 20 MHz, 50 MHz, 100 MHz, and 400 MHz.
- the carrier wave may refer to a radio wave used for modulating a signal to be transmitted, for example, a sine wave.
- Carrier signal usually refers to the sinusoidal signal used to modulate the signal to be transmitted, is a concept corresponding to the carrier.
- BWP refers to the resources configured for the terminal in the NR system to adapt to the bandwidth capacity of the terminal. For example, a set of consecutive RBs on the carrier bandwidth, and multiple BWPs can be configured on a carrier, such as One carrier can be configured with 4 BWPs. Among them, the BWP in the activated state is the currently available BWP.
- the bandwidth part is sometimes referred to as a carrier bandwidth part, a subband bandwidth, a narrowband bandwidth, or another name. The name is not limited in this application. For convenience of description, The name is BWP as an example.
- a BWP contains K (K> 0) subcarriers; or, a BWP is a frequency domain resource where N non-overlapping RBs are located, and the subcarrier interval of the RBs can be 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, 480KHz Or other values; or, a BWP is a frequency domain resource where M non-overlapping resource block groups (RBGs) are located, for example, an RBG includes P (P> 0) consecutive RBs, and the children of the RBs
- the carrier spacing (SCS) can be 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, 480KHz or other values, for example, it is an integer multiple of 2.
- FIG. 1a shows a case where a BWP is configured in a carrier bandwidth.
- a network device may first allocate a BWP within a terminal bandwidth capability range to a terminal, and of course, may further allocate some or all resources in the BWP to the terminal for data transmission.
- Network devices can configure different BWP conditions for terminals based on actual scenarios. For example, in order to save the power consumption of the terminal, the network device may allocate a BWP to the terminal according to the service volume of the terminal.
- the terminal When the terminal has no service data transmission or only a small amount of service data transmission, the terminal can be assigned a smaller BWP for receiving control information and a small amount of data information, as shown in BWP1 in Figure 1b; when the terminal has a large amount of service data to be transmitted It is possible to allocate a larger bandwidth part to the terminal, as shown in BWP2 in FIG. 1b.
- BWP1 in Figure 1b When the terminal has no service data transmission or only a small amount of service data transmission, the terminal can be assigned a smaller BWP for receiving control information and a small amount of data information, as shown in BWP1 in Figure 1b; when the terminal has a large amount of service data to be transmitted It is possible to allocate a larger bandwidth part to the terminal, as shown in BWP2 in FIG. 1b.
- Network devices can assign corresponding BWPs to terminals based on different service types of the terminals, as shown in Figure 1c. As shown, a BWP can correspond to a service type.
- the BWP can be configured with a parameter set (numerology) that can meet the service requirements. It can be known from FIG. 1b that different BWPs can occupy partially overlapping frequency domain resources. It can be known from FIG. 1c that different BWPs can also occupy completely different frequency domain resources and use different numerology. In the embodiment of the present application, the numerology corresponding to different BWPs may be the same or different, which is not limited in the present application. It can be understood that, in FIG. 1a to FIG. 1c, only one or two BWPs are configured in one carrier is taken as an example for description. In actual applications, multiple BWPs may be configured in a carrier, which is not limited in this application.
- the BWP described in this application may be a downlink BWP for the terminal to perform downlink reception, and at this time, the bandwidth of the BWP does not exceed the receiving bandwidth capability of the terminal; or the BWP may also be an uplink BWP for the terminal to perform For uplink transmission, the bandwidth of the BWP does not exceed the transmission bandwidth capability of the terminal.
- numerology refers to the parameters used by the communication system. For example, it may refer to a series of physical layer parameters in an air interface.
- a BWP can correspond to a numerology.
- the NR system can support multiple numerology, and multiple numerology can be used simultaneously.
- the numerology may include one or more of the following parameter information: subcarrier interval, cyclic prefix (CP) information, time unit information, bandwidth, etc.
- the information of the CP may include a CP length and / or a CP type.
- the CP may be a normal CP (normal CP, NCP), or an extended CP (extended CP, ECP).
- the time unit is used to represent a time unit in the time domain.
- the time unit may be a sampling point, a symbol, a mini-slot, a slot, a subframe, or a radio frame.
- the information of the time unit may include the type, length, or structure of the time unit.
- numerology can include the subcarrier interval and CP. See Table 1. Table 1 shows the numerology defined by the subcarrier interval and CP that can be currently supported in the NR system:
- Subcarrier interval 2 ⁇ ⁇ 15 (kHz) CP type 0 15 Normal 1 30 conventional 2 60 Regular or extended 3 120 conventional 4 240 conventional
- the network device can assign a terminal with a BWP with a subcarrier interval of 15KHz and a BWP with a subcarrier interval of 30KHz, and the terminal can You can switch to different BWP to transmit signals.
- the numerology corresponding to different BWPs may be the same or different.
- the subcarrier interval may be an integer greater than or equal to zero. For example, it may be 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, 480KHz, and the like.
- the subcarrier interval is an interval value between the center position or the peak position of two adjacent subcarriers in the frequency domain in an orthogonal frequency division multiplexing (OFDM) system.
- OFDM orthogonal frequency division multiplexing
- the subcarrier interval in the LTE system is 15KHz
- the subcarrier interval in the NR system can be 15kHz, or 30kHz, or 60kHz, or 120kHz.
- Initial BWP used for initial random access of the terminal, and may include initial downlink BWP and initial uplink BWP. It can be understood that during the initial random access process of the terminal, the terminal can transmit signals or perform related operations with the network device through the initial BWP.
- Non-initial BWP is a concept corresponding to the initial BWP.
- BWPs other than the initial BWP included in the carrier can be called non-initial BWP.
- BWP switch used to switch the activated BWP.
- a network device for example, a base station
- RRC radio resource control
- the network device can pass RRC Message or downlink control information (downlink control information) to switch the activated BWP, that is, activate the new BWP and deactivate the old BWP.
- the handover method is to carry the index of the target activated BWP in the RRC message or DCI, so that the terminal performs the BWP handover.
- the terminal When the terminal is switching over BWP, the terminal performs a deactivation operation on the BWP that was originally working and an activation operation on the target BWP to be switched.
- the terminal when the deactivation timer corresponding to the currently activated BWP expires, the terminal performs a BWP handover, that is, the terminal performs a deactivation operation on the original working BWP and an activation operation on the target BWP to be switched.
- a BWP handover that is, the terminal performs a deactivation operation on the original working BWP and an activation operation on the target BWP to be switched.
- FDD frequency division duplex
- the BWP switching in the downlink communication process and the BWP switching in the uplink communication process can be performed independently, that is, only the downlink BWP can be performed through an RRC message or DCI.
- Uplink BWP for time division duplex (TDD) system, the downlink BWP and uplink BWP appear and switch in pairs, for example, when the downlink BWP is switched, the uplink BWP corresponding to the downlink BWP It also switches at the same time.
- TDD time division duplex
- multiple BWPs can be configured on one carrier. For example, 4 BWPs can be configured on one carrier. .
- one of the multiple downlink BWPs configured in the downlink carrier except the initial downlink BWP can be set as the default BWP.
- the downlink BWP with a narrower bandwidth among multiple downlink BWPs can be set as The default BWP.
- the default BWP involved in this application can also be referred to as the default downlink BWP, which is a unified description, and is hereinafter described as the default BWP.
- the introduction of the default BWP in the NR system can, on the one hand, enable the network device to correctly find the terminal when the terminal and the network device have different understandings of the currently active BWP.
- a network device may send a DCI indicating a BWP switch to the terminal, so that the terminal switches the currently activated BWP. If the DCI is lost, the terminal does not receive the DCI, and the terminal will not switch the currently activated BWP at this time, and the network device incorrectly It is considered that the terminal has performed a BWP switch, and then dispatched the terminal on a misunderstood activated BWP, but could not receive a response from the terminal.
- the terminal After a period of time, the terminal can fall back to the default BWP so that the network device can be found again on the default BWP The terminal. On the other hand, when the terminal has not been scheduled for a long time, it can fall back to the default BWP with a narrow bandwidth, which can reduce the power consumption of the terminal.
- Non-default BWP is a concept corresponding to the default BWP.
- BWPs other than the default BWP included in the carrier can be called non-default BWP.
- Deactivation timer (bwpInactivityTimer).
- the non-default BWP activated in the carrier maintains a corresponding deactivation timer.
- the deactivation timer corresponding to the non-default BWP is started.
- the deactivation timer expires, the BWP switch is executed. It can be understood that the deactivation timer is used to control the time when the BWP is activated.
- the terminal may switch from the currently activated BWP to the default BWP when performing a BWP switch; otherwise, if the carrier is not configured with a default BWP, the terminal may perform a BWP switch from the currently activated BWP to the initial BWP .
- switching from the currently activated BWP to the default BWP refers to performing a deactivation operation on the currently activated BWP and activating the default BWP.
- switching from the currently activated BWP to the initial BWP refers to performing a deactivation operation on the currently activated BWP and activating the initial BWP.
- the timing of the deactivation timer refers to the time from the start of the deactivation timer to the timeout, which can be determined by the total value and the granularity (or the counting unit).
- the active state can refer to a workable state.
- the BWP in the activated state means that the BWP is in a working state, for example, a state in which signals can be sent or received.
- the inactive state is a concept corresponding to the active state and can refer to a non-working state.
- BWP is inactive means BWP is in a non-working state. Exemplarily, a BWP in an inactive state cannot be used for signal transmission or reception.
- Activated BWP refers to a BWP in an activated state, which can also be understood as a BWP that can send and / or receive signals.
- An inactivated BWP is a concept corresponding to an activated BWP, and refers to a BWP in an inactive state. It can also be understood as a BWP that cannot send and / or receive signals.
- Deactivation of BWP can also be described as "deactivating" BWP, which refers to converting BWP from active to inactive state. It can also be understood as converting working BWP to non-working BWP.
- FIG. 2 is a schematic diagram of a communication system applicable to an embodiment of the present application.
- the terminal 130 may access a wireless network to obtain services of an external network (such as the Internet) through the wireless network, or communicate with other terminals through the wireless network.
- the wireless network includes a radio access network (RAN) 110 and a core network (CN) 120.
- the RAN 110 is used to connect the terminal 130 to the wireless network
- the CN 120 is used to manage and provide the terminal. Gateway for communication with the Internet.
- the network architecture shown in FIG. 2 only includes two terminals as an example for description, but the embodiment of the present application is not limited thereto.
- the network architecture may also include more terminals; similarly, the network architecture It may also include more RAN 110, and may also include other equipment.
- the network architecture includes a CN device and a RAN device.
- the RAN device includes a baseband device and a radio frequency device.
- the baseband device can be implemented by one node or multiple nodes.
- the radio frequency device can be implemented independently from the baseband device, can also be integrated in the baseband device, or part of the remote device. Partially integrated in the baseband device.
- a RAN device eNB
- eNB includes a baseband device and a radio frequency device, where the radio frequency device can be remotely arranged relative to the baseband device, such as a remote radio unit.
- RRU is arranged remotely relative to the BBU.
- the control plane protocol layer structure may include a radio resource control (RRC) layer, a packet data convergence layer protocol (PDCP) layer, a radio link control (RLC) layer, and a media interface. Functions of the protocol layer such as the media access control (MAC) layer and the physical layer.
- RRC radio resource control
- PDCP packet data convergence layer protocol
- RLC radio link control
- Functions of the protocol layer such as the media access control (MAC) layer and the physical layer.
- the user plane protocol layer structure can include the functions of the protocol layers such as the PDCP layer, the RLC layer, the MAC layer, and the physical layer; in one implementation, the PDCP layer can also include a service data adaptation (SDAP) layer .
- SDAP service data adaptation
- a RAN device can implement the functions of protocol layers such as RRC, SDAP, PDCP, RLC, and MAC by one node; or multiple nodes can implement the functions of these protocol layers; for example, in an evolved structure, a RAN device can include a centralized unit (centralized unit, CU) and distributed unit (DU), multiple DUs can be centrally controlled by one CU. As shown in FIG. 3, the CU and DU can be divided according to the protocol layer of the wireless network. For example, the functions of the PDCP layer and above are set in the CU, and the functions of the protocol layers below PDCP, such as the RLC layer and the MAC layer are set in the DU.
- This division of the protocol layer is only an example. It can also be divided at other protocol layers, for example, at the RLC layer.
- the functions of the RLC layer and above are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU.
- it is divided in a certain protocol layer, for example, setting some functions of the RLC layer and functions of the protocol layer above the RLC layer in the CU, and setting the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer in the DU.
- it can also be divided in other ways, for example, by delay, and the function that needs to meet the delay requirement in processing time is set in the DU, and the function that does not need to meet the delay requirement is set in the CU.
- the radio frequency device can be remote, not placed in the DU, or integrated in the DU, or part of the remote can be integrated in the DU, without any restrictions here.
- control plane (CP) and user plane (UP) of the CU can also be separated and separated into different entities to implement, respectively, the control plane CU entity (CU-CP entity). ) And the user plane CU entity (CU-UP entity).
- the signaling generated by the CU can be sent to the terminal through the DU, or the signaling generated by the terminal can be sent to the CU through the DU.
- the DU can directly transmit to the terminal or the CU through protocol layer encapsulation without parsing the signaling. If the following embodiments involve the transmission of such signaling between the DU and the terminal, at this time, the sending or receiving of signaling by the DU includes this scenario.
- the signaling at the RRC or PDCP layer will eventually be processed as the PHY layer signaling and sent to the terminal, or it will be transformed from the received PHY layer signaling.
- the RRC or PDCP layer signaling can also be considered to be sent by the DU, or sent by the DU and the RF load.
- the CU may be divided into network devices on the RAN side.
- the CU may also be divided into network devices on the CN side, which is not limited herein.
- the devices in the following embodiments of the present application may be located in a terminal or a network device according to the functions they implement.
- the network device may be a CU node, or a DU node, or a RAN device including a CU node and a DU node.
- the network device can configure multiple BWPs on one carrier, and can independently configure numerology for each BWP in the multiple BWPs, which is used to support multiple service types and / or communication scenarios in the system frequency resource.
- a network device can configure multiple BWPs for a terminal on a carrier, but at the same time, a network device activates only one of the BWPs configured for the terminal on a carrier, so that the network device and the terminal transmit signals on the activated BWP .
- the network device For the uplink carrier, the network device is configured and activated by the uplink BWP, and for the downlink carrier, the network device is configured and activated by the downlink BWP.
- the network device is configured as a terminal to configure the downlink BWP as an example.
- signals of different service types and / or communication scenarios may need to be transmitted through different BWPs on the carrier.
- the terminal performs BWP handover, deactivates BWP1 and activates the default BWP, and the terminal needs to monitor BWP2 and the default BWP (for example, monitor the PDCCH);
- the terminal monitoring BWP means that the terminal monitors the data and / or control channel on the BWP.
- an embodiment of the present application provides a method for processing a part of a bandwidth.
- a deactivation timer corresponding to an activated first BWP expires, it is determined whether a carrier in which the first BWP is located includes an activated second BWP.
- the carrier includes a second BWP in an activated state, the first BWP is deactivated.
- the terminal does not need to monitor the PDCCH in the default BWP or the initial BWP, and only needs to be in the current carrier Monitoring on the second BWP can reduce the overhead of the terminal monitoring on the BWP, thereby reducing the power consumption of the terminal during communication.
- FIG. 5 is an implementation flowchart of a method for processing a bandwidth part according to an embodiment of the present application. As shown in FIG. 5, the method includes:
- the involved method may be executed by a terminal or a communication device (such as a chip system) capable of supporting the terminal to implement the method.
- a terminal or a communication device such as a chip system
- steps S101 to S102 may be executed by the terminal.
- the first BWP and the second BWP are different BWPs on the same carrier, and the BWP may be a downlink BWP or an uplink BWP.
- the BWP when the terminal is a signal receiving end, the BWP is a downlink BWP, and conversely, when the terminal is a signal transmitting end, the BWP is an uplink BWP.
- the carrier is a downlink carrier and the BWP is a downlink BWP.
- the method in FIG. 5 is applicable to a scenario in which a default BWP is configured in a carrier unit.
- the default BWP configured in the carrier unit refers to the default BWP configured in a carrier, which can be used to roll back any default non-initial or non-default BWP in the carrier to the default BWP.
- the timing duration of the deactivation timer may be determined by a total value and a counting granularity (or a counting unit). For example, when the total value of the deactivation timer configured by the network device is 100, and the counting granularity is 1ms, the timing duration of the deactivation timer is 100ms. As another example, when the total value of the deactivation timer configured by the network device is 100, and the counting granularity is 1 symbol, the timing duration of the deactivation timer is 100 symbol.
- the counting granularity of each count of the deactivation timer may be 1 ms, or 0.1 ms, or 1 slot, or the duration of a symbol, which is not limited in this application.
- the timing duration of the deactivation timer may be related to the parameters of the BWP in the carrier.
- the counting granularity of the deactivation timer may be related to the parameters of the BWP in the carrier.
- the value of the counting granularity slot may be the value of the slot corresponding to the BWP with the largest / smallest slot value among all BWPs configured on the carrier.
- the timing duration of the deactivation timer may be carrier-specific or BWP-specific.
- the count granularity and total value of the deactivation timer may be carrier-specific or BWP-specific.
- the carrier-specific and BWP-specific explanations are explained below by taking the timing of the deactivation timer as an example.
- Carrier-specific means that the deactivation timers maintained by non-default BWPs activated on the same carrier have the same timing.
- a carrier includes three non-default BWPs, and each activated non-default BWP maintains a corresponding deactivation timer. If the timing of the deactivation timer is set to be carrier-specific, the carrier The timings of the three deactivation timers maintained by the last three non-default BWPs in the activated state are the same. For example, if the timing of the deactivation timer configured by a network device for a carrier is 100ms, the timing of the deactivation timer maintained by each non-default BWP on the carrier is 100ms.
- the timing of the deactivation timer configured by a network device for a carrier is 100 slots
- the timing of the deactivation timer maintained by each non-default BWP on the carrier is 100 slots
- the slot value is the carrier
- the slot value corresponding to the BWP with the largest slot value among all the BWPs configured on the carrier is an example. If the slot value corresponding to the BWP with the largest slot value among all the BWPs configured on the carrier is 0.5ms, then each non-default on the carrier
- the timing duration of the deactivation timer corresponding to the BWP can be configured in the RRC cell where the network device configures the carrier where the corresponding BWP is located.
- the configuration parameters of the timing duration of the deactivation timer can be the duration itself, Or the value of other factors that determine the duration, such as totals and / or count granularity.
- BWP-specific means that the timing duration of the deactivation timer corresponds to a non-default BWP.
- a carrier includes 3 non-default BWPs, namely a first non-default BWP, a second non-default BWP, and a third non-default BWP, and the activated first non-default BWP maintains a first deactivation timer.
- the activated second non-default BWP maintains a second deactivation timer
- the activated third non-default BWP maintains a third deactivation timer.
- the first deactivation timer, the second deactivation timer, and the third deactivation timer may correspond to three timing durations, respectively.
- the network device may configure the timing of the deactivation timer corresponding to the first non-default BWP configuration to be 100ms, configure the timing of the deactivation timer corresponding to the second non-default BWP configuration to be 50ms, and configure the third non-default BWP configuration.
- the timing duration of the corresponding deactivation timer is 20ms; in this example, the timing duration of the deactivation timer corresponding to the BWP can be configured in the RRC cell where the network device configures the corresponding BWP.
- the network device may configure the timing of the deactivation timer corresponding to the first non-default BWP to be 100 slot 1 , slot 1 is the slot value corresponding to the first default BWP, and configure the deactivation timing corresponding to the second non-default BWP. is a timing length of 50slot 2, slot 2 is the second default value BWP corresponding slot, a third non-default configuration BWP activation timing corresponding to the duration timer is 20slot 3, slot 3 corresponding to the third slot default BWP Value; in this example, the timing of the deactivation timer corresponding to the BWP can be configured in the RRC cell where the network device configures the corresponding BWP.
- the network device may configure the timing of the deactivation timer maintained by the activated non-default BWP in the carrier to be 100 slots, where slot is the slot value corresponding to the activated non-default BWP.
- the slot corresponding to the activated non-default BWP1 is 1ms
- the timing of the deactivation timer maintained by non-default BWP1 is 100ms
- the slot corresponding to the activated non-default BWP2 is 0.5ms
- the timing of the deactivation timer maintained by non-default BWP2 is 50ms; in this example
- the timing of the deactivation timer corresponding to the BWP can be configured in the RRC cell in which the network device configures the carrier where the corresponding BWP is located, or in the RRC cell in which the network device configures the serving cell where the corresponding BWP is located.
- the timing duration of the deactivation timer is BWP specific, the counting granularity and total value of the corresponding deactivation timer are also BWP specific.
- the timing of the deactivation timers corresponding to different BWPs may be the same, or may be different.
- the timing of the deactivation timer corresponding to the BWP can be configured in the RRC cell where the network device configures the corresponding BWP, or it can be configured in the RRC cell where the network device configures the corresponding BWP carrier
- the configuration parameter of the timing duration of the deactivation timer may be the duration itself, or a value of another factor that determines the duration, such as a total value and / or a counting granularity.
- the terminal when the terminal determines that the carrier where the first BWP is located includes the second BWP in an activated state, the terminal deactivates the first BWP.
- the deactivation of the first BWP can be understood as performing a deactivation operation on the first BWP. After the first BWP is deactivated, the first BWP is switched from an activated state to an inactive state.
- the second BWP may be a default BWP or an initial BWP.
- the second BWP can also be a non-default BWP and a non-initial BWP.
- non-default BWP and non-initial BWP refer to BWPs that are neither the default BWP nor the initial BWP in the carrier.
- the terminal may not activate the default BWP or the initial BWP in the carrier on the basis of performing S102.
- the deactivation timer corresponding to the activated first BWP expires, a BWP handover procedure needs to be performed.
- the first BWP is deactivated and the default BWP or initial BWP in the carrier is activated.
- the method of the present application only the first BWP is deactivated to avoid unnecessary BWP switching processes.
- the terminal since the method does not activate the default BWP or the initial BWP, the terminal does not need to monitor the default BWP or the initial BWP, only The need to monitor the second BWP in the current carrier can reduce the overhead of the terminal monitoring the BWP, thereby reducing the power consumption of the terminal during communication.
- the default BWP or the initial BWP in the carrier may not be activated.
- the default BWP when the carrier is configured with the default BWP, the default BWP is not activated, and when the carrier is not configured with the default BWP, the initial BWP is not activated.
- the carrier on which the first BWP is located is configured with a default BWP.
- the terminal determines that the carrier on which the first BWP is located does not include an active state.
- the first BWP is deactivated, and the default BWP in the carrier is activated. It can also be understood that the terminal performs BWP handover from the first BWP on the carrier to the default BWP.
- the number of default BWPs configured in a carrier is not limited.
- One carrier may be configured with one default BWP, and of course, more than one default BWP may be configured. More than one default BWP configured in a carrier may be configured. Called the default BWP group.
- the terminal may activate the default BWP in the carrier in the following manner.
- the terminal activates all BWPs included in at least two default BWPs. It can also be understood that the terminal activates all BWPs in the default BWP group. In this manner, all default BWPs on a carrier may be in the same state, for example, in the active state at the same time, or in the inactive state at the same time.
- the network device may deactivate some default BWPs by sending a BWP switch command, so that all the default BWPs on a carrier can also be in different states, that is, some of the default BWPs are in the activated state and the other part By default, BWP is inactive.
- the second method The terminal activates at least two BWPs included in the default BWP that satisfy a preset rule. It can also be understood that the terminal activates the BWP in the default BWP group according to a preset rule. In this way, all default BWPs on a carrier can be in different states, for example, one BWP in the default BWP group is active, other BWPs in the default BWP group are inactive, or, in the default BWP group One BWP is in the inactive state, and the other BWPs in the BWP group are in the active state by default.
- the preset rules may include any of the following:
- the maximum BWP index, the minimum BWP index, the SCS maximum, the SCS minimum, the CP maximum, the CP minimum, and the parameters of the first BWP that are currently deactivated are the same.
- the terminal may activate one BWP with a maximum BWP index / SCS maximum / CP maximum included in at least two default BWPs, or may activate a minimum BWP index included in at least two default BWPs
- One BWP with / SCS minimum / CP minimum can also activate one BWP with the same parameters as the first BWP currently deactivated.
- the parameters of the first BWP may include SCS and / or CP.
- activating a BWP with the same parameters as the first BWP can be understood as activating a BWP with the same SCS and / or CP as the first BWP.
- the terminal may also activate multiple BWPs that meet the preset rules.
- the terminal may activate two BWPs in the three default BWPs that are the same as the SCS and / or CP of the first BWP.
- the carrier where the first BWP is located is not configured with the default BWP.
- the terminal determines that the carrier where the first BWP is located does not include the active state.
- the second BWP is set, the first BWP is deactivated, and the initial BWP in the carrier is activated. It can also be understood that the terminal performs BWP handover from the first BWP on the carrier to the initial BWP.
- FIG. 6a is a schematic diagram of a bandwidth part processing method according to an embodiment of the present application.
- a carrier is configured with a default BWP and three non-default BWPs in FIG. 6a, namely BWP1, BWP2, and BWP3, where BWP1 is in an activated state, BWP2, BWP3, and a default BWP are in an inactive state.
- the terminal may determine that the second BWP in the activated state is not included on the current carrier, and then perform a BWP handover, that is, deactivate BWP1 and activate the default BWP.
- FIG. 6b is a schematic diagram of another bandwidth part processing method provided by an embodiment of the present application.
- a carrier is configured with a default BWP and three non-default BWPs in FIG. 6b, namely BWP1, BWP2, and BWP3, where BWP1 and BWP2 are in an activated state, and BWP3 and the default BWP are in an inactive state.
- the terminal may determine that the current carrier includes a second BWP (activated BWP2) in an activated state, and then only deactivates BWP1 and does not perform BWP handover.
- FIG. 6c is a schematic diagram of another bandwidth partial processing method according to an embodiment of the present application.
- a default BWP and three non-default BWPs are configured on a carrier in FIG. 6c, which are BWP1, BWP2, and BWP3, among which BWP1 and the default BWP are both active, and BWP2 and BWP3 are inactive .
- the terminal may determine that the current carrier includes a second BWP in the activated state (the activated default BWP), and then only deactivates BWP1 and does not perform BWP handover.
- the deactivation timer corresponding to one activated BWP expires is used as an example for description. In actual application, there may be a case where the deactivation timers corresponding to multiple activated BWPs on the current carrier expire simultaneously.
- the terminal determines whether the current carrier also includes the second BWP in the active state. If the current carrier also includes the second BWP in the active state, the terminal only deactivates the multiple activated BWPs. If the current carrier does not include the second BWP in the activated state, the terminal performs BWP handover, that is, deactivates the multiple activated BWPs, and activates the default BWP in the carrier.
- the terminal may adopt different BWP processing methods according to different scenarios.
- the above method in FIG. 5 is applicable to a scenario in which a default BWP is configured in a carrier unit.
- the following describes the BWP processing method provided in this application for a scenario in which a default BWP is configured in units of BWP groups.
- multiple BWPs included in one carrier may be configured as multiple BWP groups, so that at least two BWP groups may be included in one carrier, and each BWP group includes at least one BWP.
- the BWP group in the carrier can be configured through signaling. For example, it can be configured through RRC signaling. It can also be pre-configured through predefined rules. Exemplarily, the predefined rule may include that the parameters of the BWP in the same BWP group are the same, or that the BWP configuration in the same BWP group is the same as the default BWP; or, both rules are satisfied. And set the number of BWPs that are active at the same time in each BWP group to 1 or 0.
- each BWP group is considered to be equivalent to a carrier in an independent Rel-15 system, so that after the BWP grouping, it can communicate with the Rel-15 system. compatible.
- the number of default BWPs configured in each BWP group is not limited.
- the number of default BWPs configured in each BWP group can be configured through a predefined rule or signaling.
- the default BWP is configured through a predefined rule
- the BWP with the smallest bandwidth in a BWP group may be configured as the default BWP.
- the number of default BWPs configured in each BWP group is 1 or 0 as an example for description.
- the following describes a BWP processing method provided in this application for a scenario in which a default BWP is configured by using a BWP group as a unit.
- FIG. 7 is an implementation flowchart of another bandwidth partial processing method according to an embodiment of the present application.
- the method includes:
- the first BWP group is a BWP group including the first BWP in at least two BWP groups configured in a carrier
- the second BWP group is a BWP group.
- the timing duration of the deactivation timer may be determined by a total value and a counting granularity (or a counting unit).
- the timing duration of the deactivation timer may be carrier-specific or BWP-specific or BWP group-specific.
- the count granularity and total value of the deactivation timer may be carrier-specific or BWP-specific or BWP-group-specific.
- the BWP group specific is explained with the timing duration of the deactivation timer, that is, the BWP group specific means that the timing duration of the deactivation timer corresponding to the BWP in the same BWP group is the same.
- the counting granularity of the deactivation timer may be related to a parameter of a certain BWP in the BWP group.
- the granularity of the count of the deactivation timer may be the length of a symbol on the BWP with the maximum BWP index / the minimum BWP index / the maximum SCS / the minimum SCS in the BWP group.
- a possible implementation manner for determining whether to include the second BWP in the activated state in the second BWP group is described in S201a. For example, when the deactivation timer corresponding to the activated first BWP expires, the terminal may determine whether the first BWP group includes the default BWP, and if the first BWP group includes the default BWP, perform a BWP switch, that is, deactivate The first BWP, and activate the default BWP; if the default BWP is not included in the first BWP group, it is determined whether to include the second BWP in the activated state in the second BWP group.
- an initial BWP may be configured for a carrier where the first BWP is located, and the initial BWP may belong to a certain BWP group or may not belong to any BWP group.
- S201a can be applied to the scenario where the initial BWP does not belong to any BWP group.
- S201b gives another possible implementation manner for determining whether to include the second BWP in the activated state in the second BWP group.
- S201b may be applicable to the scenario where the initial BWP belongs to a certain BWP group.
- S201b When the deactivation timer corresponding to the activated first BWP expires, and when the first BWP group does not include the default BWP and the initial BWP, determine whether to include the activated second BWP in the second BWP group.
- the meanings of the first BWP group and the second BWP group are the same as those in S201a, and details are not described herein again.
- the terminal can determine whether the first BWP group includes the default BWP. If the first BWP group includes the default BWP, the first BWP is deactivated and activated.
- the default BWP if the default BWP is not included in the first BWP group, it is further judged whether the initial BWP is included in the first BWP group; if the initial BWP is included in the first BWP group, the first BWP is deactivated and the initial BWP is activated ; If neither the default BWP nor the initial BWP is included in the first BWP group, determine whether to include the second BWP in the activated state in the second BWP group.
- S201a and S201b are two implementation modes respectively for different scenarios.
- the terminal may apply one of the implementation modes according to the actual scenario.
- FIG. 8 is a schematic diagram of another method for processing a bandwidth part according to an embodiment of the present application.
- three BWP groups are configured on one carrier in FIG. 8, namely BWP group 1, BWP group 2, and BWP group 3, wherein a default BWP is configured in BWP group 1, and an initial BWP is configured in BWP group 2.
- the default BWP is not configured in BWP group 3.
- BWP group 1 also includes activated BWP1
- BWP group 2 also includes activated BWP2
- BWP group 3 includes activated BWP3.
- the terminal can determine that the BWP group 1 includes the default BWP, so the terminal deactivates BWP 1 and activates the default BWP in BWP group 1. .
- the terminal can determine that the BWP group 2 does not include the default BWP but includes the initial BWP, so the terminal deactivates the BWP2 and activates the initial BWP .
- the terminal can determine that BWP group 3 includes neither the default BWP nor the initial BWP, so the terminal can be in BWP group 1 and BWP It is determined in group 2 whether the second BWP in the active state is included.
- BWP handover is performed, that is, BWP3 is deactivated and the initial BWP in the current carrier is activated.
- multiple BWPs included in one carrier may be configured as multiple BWP groups, so that at least two BWP groups may be included in one carrier, and each BWP group includes at least one BWP.
- the BWP group in the carrier can be configured through signaling. For example, it can be configured through RRC signaling. It can also be pre-configured through predefined rules. Exemplarily, the predefined rule may include that the parameters of the BWP in the same BWP group are the same, or that the BWP configuration in the same BWP group is the same as the default BWP; or, both rules are satisfied. And configure a BWP group under this scenario to include multiple BWPs that are active at the same time.
- FIG. 9 is an implementation flowchart of another method for processing a bandwidth part according to an embodiment of the present application. As shown in FIG. 9, the method includes:
- the first BWP group is a BWP group including at least two BWP groups configured in a carrier
- the second BWP group is a group of at least two BWP groups configured in a carrier that does not include the first BWP. BWP group.
- the timing duration of the deactivation timer may also be determined by a total value and a counting granularity (or a counting unit).
- the timing duration of the deactivation timer may be carrier-specific or BWP-specific or BWP group-specific.
- the count granularity and total value of the deactivation timer may be carrier-specific or BWP-specific or BWP-group-specific.
- the counting granularity of the deactivation timer may be related to a parameter of a certain BWP in the BWP group.
- the granularity of the count of the deactivation timer may be the length of a symbol on the BWP with the maximum BWP index / the minimum BWP index / the maximum SCS / the minimum SCS in the BWP group.
- the terminal can determine whether the current carrier includes other activated BWPs, and if the current carrier includes other activations BWP, the terminal does not perform BWP switching, which can avoid unnecessary BWP switching processes.
- the non-default BWP corresponding to the same parameter may be mapped to the same default BWP in a manner predefined by the protocol.
- a non-default BWP corresponding to the same default BWP in one carrier is configured as a BWP group as an example, and the BWP processing method provided in the third embodiment is exemplified.
- each BWP group includes a default BWP.
- FIG. 10 is a schematic diagram of another bandwidth partial processing method according to an embodiment of the present application.
- six BWPs are configured on one carrier, including four non-default BWPs, namely BWP1, BWP2, BWP3, and BWP4, and two default BWPs, which are default BWP1 and default BWP2, respectively.
- BWP1 and BWP2 correspond to the same default BWP1
- BWP3 and BWP4 correspond to the same default BWP2.
- the terminal can determine whether the second BWP in the activated state is included in the BWP group where BWP1 is located. As shown in FIG. 10, BWP1 in BWP1 is located in Including BWP2 in the active state, the terminal only performs deactivation of BWP1, and does not perform BWP handover. In addition, if BWP2 is in an inactive state in FIG. 10, the terminal performs BWP handover, that is, deactivates BWP1 and activates default BWP1.
- the terminal includes a hardware structure and / or a software module corresponding to each function.
- the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
- each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
- the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
- an embodiment of the present application further provides an apparatus for implementing any one of the foregoing methods.
- an apparatus is provided that includes a unit (or means) for implementing each step performed by a terminal in any one of the foregoing methods. ).
- FIG. 11 is a schematic structural diagram of a bandwidth processing device 1100 according to an embodiment of the present application.
- the bandwidth processing device 1100 includes a determination unit 1101 and a deactivation unit 1102.
- the determining unit 1101 may be configured to determine when the deactivation timer corresponding to the activated first BWP expires, and to determine whether the carrier on which the first BWP is located includes a second BWP in the activated state.
- the deactivation unit 1102 may be configured to be used when the carrier is in the carrier. When the second BWP is included in an activated state, the first BWP is deactivated.
- the first BWP and the second BWP involved in the bandwidth part processing device 1100 are different BWPs in the same carrier, and the BWP may be a downlink BWP or an uplink BWP.
- the carrier is a downlink carrier and the BWP is a downlink BWP.
- the timing duration of the deactivation timer may be determined by a total value and a counting granularity (or a counting unit).
- the timing duration of the deactivation timer may be carrier-specific or BWP-specific.
- the count granularity and total value of the deactivation timer may also be carrier-specific or BWP-specific.
- the timing duration of the deactivation timer may be related to the parameters of the BWP in the carrier.
- the counting granularity of the deactivation timer may be related to the parameters of the BWP in the carrier.
- the counting granularity is a slot
- the value of the slot may be the value of the slot corresponding to the BWP with the largest / smallest slot value among all BWPs configured on the carrier.
- the second BWP may be a default BWP or an initial BWP.
- the second BWP may also be a non-default BWP and a non-initial BWP.
- the deactivation unit 1102 may not activate the default BWP or the initial BWP in the carrier on the basis of deactivating the first BWP. BWP.
- the deactivation unit 1102 may not activate the default BWP, and when the carrier is not configured with the default BWP, the deactivation unit 1102 may not activate the initial BWP.
- the deactivation unit 1102 may not activate the default BWP or the initial BWP in the carrier on the basis of deactivating the first BWP.
- the bandwidth part processing device 1100 may further include an activation unit 1103.
- the deactivation unit 1102 and the activation unit 1103 may be integrated into one unit, or may be independent units.
- the carrier on which the first BWP is located is configured with a default BWP.
- the determining unit 1101 determines that the carrier on which the first BWP is located does not include the active state.
- the deactivation unit 1102 deactivates the first BWP
- the activation unit 1103 activates a default BWP in the carrier. It can also be understood that the deactivation unit 1102 and the activation unit 1103 perform BWP handover, and switch from the first BWP on the carrier to the default BWP.
- the number of default BWPs configured in a carrier is not limited.
- One carrier may be configured with one default BWP, and of course, more than one default BWP may be configured. More than one default BWP configured in a carrier may be configured. Called the default BWP group.
- the activation unit 1103 may activate the default BWP in the carrier in the following manner.
- the activation unit 1103 may be configured to activate all BWPs included in at least two default BWPs.
- all default BWPs on a carrier may be in the same state, for example, in the active state at the same time, or in the inactive state at the same time.
- the network device may deactivate some default BWPs by sending a BWP switch command, so that all the default BWPs on a carrier can also be in different states, that is, some of the default BWPs are in the activated state and the other part By default, BWP is inactive.
- the activation unit 1103 may be configured to activate at least two BWPs included in the default BWP that meet a preset rule. In this way, all default BWPs on a carrier can be in different states, for example, one BWP in the default BWP group is active, other BWPs in the default BWP group are inactive, or, in the default BWP group One BWP is in the inactive state, and the other BWPs in the BWP group are in the active state by default.
- the preset rules may include any of the following:
- the maximum BWP index, the minimum BWP index, the SCS maximum, the SCS minimum, the CP maximum, the CP minimum, and the parameters of the first BWP that are currently deactivated are the same.
- the activation unit 1103 may activate one BWP with a maximum BWP index / SCS maximum / CP maximum included in at least two default BWPs, or may activate BWPs included in at least two default BWPs.
- a BWP with the smallest index / the smallest SCS / the smallest CP can also activate a BWP with the same parameters as the first BWP currently deactivated.
- the parameters of the first BWP may include SCS and / or CP.
- activating a BWP with the same parameters as the first BWP can be understood as activating a BWP with the same SCS and / or CP as the first BWP.
- the activation unit 1103 may activate one or more BWPs that satisfy a preset rule. For example, if the number of default BWPs in the carrier is three, the activation unit 1103 may activate two BWPs in the three default BWPs that are the same as the SCS and / or CP of the first BWP.
- a carrier where the first BWP is located is not configured with a default BWP.
- the determining unit 1101 determines that the carrier where the first BWP is located does not include the second BWP in the activated state, the deactivating unit 1102 deactivates the first BWP, and the activating unit 1103 and Activate the initial BWP in this carrier.
- the following describes the scenario of configuring the default BWP in units of BWP groups.
- multiple BWPs included in one carrier may be configured as multiple BWP groups, so that at least two BWP groups may be included in one carrier, and each BWP group includes at least one BWP.
- the BWP group in the carrier can be configured through signaling. It can also be pre-configured through predefined rules. And set the number of BWPs that are active at the same time in each BWP group to 1 or 0.
- the number of default BWPs configured in each BWP group is not limited.
- the number of default BWPs configured in each BWP group can be configured through a predefined rule or signaling.
- the number of default BWPs configured in each BWP group is 1 or 0.
- an initial BWP may also be configured for the carrier where the first BWP is located.
- the initial BWP may belong to a certain BWP group or not belong to any BWP group.
- the initial BWP does not belong to any BWP group.
- the determining unit 1101 is further configured to:
- the deactivation unit 1102 is further configured to:
- the second BWP group includes a second BWP in an activated state, deactivate the first BWP;
- the activation unit 1103 is further configured to:
- the initial BWP on the carrier where the first BWP is located is activated.
- BWP switching may be performed.
- the deactivation unit 1102 is configured to deactivate the first BWP
- the activation unit 1103 is configured to activate the default BWP.
- the initial BWP belongs to a certain BWP group.
- the determining unit 1101 may be further configured to:
- the deactivation unit 1102 may be further configured to:
- the second BWP group includes a second BWP in an activated state, deactivate the first BWP;
- the activation unit 1103 may be further configured to:
- the initial BWP on the carrier where the first BWP is located is activated.
- the BWP switching is performed. Specifically, the deactivation unit 1102 performs deactivation of the first BWP, and the activation unit 1103 performs activation of the default BWP. If the default BWP is not included in the first BWP group, but the initial BWP is included, the BWP switching is performed. Specifically, the deactivation unit 1102 performs deactivation of the first BWP, and the activation unit 1103 performs activation of the initial BWP.
- the first BWP group is a BWP group including the first BWP among at least two BWP groups configured in the carrier
- the second BWP group is a BWP group including the first BWP among the at least two BWP groups configured in the carrier.
- the timing duration of the deactivation timer can be determined by the total value and the counting granularity (or the counting unit).
- the timing of the deactivation timer may be carrier-specific or BWP-specific or BWP group-specific.
- the count granularity and total value of the deactivation timer may be carrier-specific or BWP-specific or BWP-group-specific.
- the timing duration of the deactivation timer may be related to the parameters of the BWP in the carrier.
- the counting granularity of the deactivation timer may be related to a parameter of a certain BWP in the BWP group.
- the counting granularity is a slot
- the value of the slot may be the value of the slot corresponding to the BWP with the largest / smallest slot value among all BWPs configured on the carrier.
- the counting granularity of the deactivation timer may be the length of a symbol on the BWP with the maximum BWP index / minimum BWP index / maximum SCS / minimum SCS in the BWP group.
- multiple BWPs included in one carrier may be configured as multiple BWP groups, so that at least two BWP groups may be included in one carrier, and each BWP group includes at least one BWP.
- the BWP group in the carrier can be configured through signaling. It can also be pre-configured through predefined rules. Exemplarily, the predefined rule may include that the parameters of the BWP in the same BWP group are the same, or that the BWP configuration in the same BWP group is the same default BWP. You can configure multiple BWPs in the same BWP group to be active at the same time.
- the determining unit 1101 may be further configured to:
- the deactivation timer corresponding to the activated first bandwidth part BWP expires, it is determined in the first BWP group whether the second BWP in the activated state is included, and the first BWP group includes all the at least two BWP groups. Describe the BWP group of the first BWP;
- the deactivation unit 1102 may be further configured to:
- the carrier includes a second BWP in an activated state
- the first BWP is deactivated.
- the first BWP group is a BWP group including the first BWP among at least two BWP groups configured in the carrier
- the second BWP group is a BWP group including the first BWP among the at least two BWP groups configured in the carrier.
- the timing duration of the deactivation timer can be determined by the total value and the counting granularity (or the counting unit).
- the timing of the deactivation timer may be carrier-specific or BWP-specific or BWP group-specific.
- the count granularity and total value of the deactivation timer may be carrier-specific or BWP-specific or BWP-group-specific.
- the timing duration of the deactivation timer may be related to the parameters of the BWP in the carrier.
- the counting granularity of the deactivation timer may be related to the parameters of the BWP in the carrier.
- the counting granularity is a slot
- the value of the slot may be the value of the slot corresponding to the BWP with the largest / smallest slot value among all BWPs configured on the carrier.
- the counting granularity of the deactivation timer may be the length of a symbol on the BWP with the maximum BWP index / minimum BWP index / maximum SCS / minimum SCS in the BWP group.
- the determination unit 1101 may determine whether other activated BWPs are included on the current carrier, and if the current carrier includes For other activated BWPs, BWP switching is not performed, and unnecessary BWP switching processes can be avoided.
- This application does not limit how multiple BWPs correspond to the same default BWP.
- the non-default BWP corresponding to the same parameter for example, SCS and / or CP
- each unit in the above device can be a separately established processing element, or it can be integrated and implemented in a certain chip of the device.
- it can also be stored in the form of a program in the memory and called and executed by a certain processing element of the device.
- all or part of these units can be integrated together or can be implemented independently.
- each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in a processor element or in a form called by software through a processing element.
- the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, for example: one or more application-specific integrated circuits (ASICs), or, one or Multiple microprocessors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.
- ASICs application-specific integrated circuits
- DSPs Multiple microprocessors
- FPGAs field programmable gate arrays
- the unit in the device can be implemented in the form of a processing element scheduler
- the processing element may be a general-purpose processor, such as a central processing unit (CPU) or another processor that can call a program.
- CPU central processing unit
- these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
- SOC system-on-a-chip
- FIG. 12 is a schematic structural diagram of a terminal according to an embodiment of the present application. It may be the terminal in the above embodiments, and is used to implement the operation of the terminal in the above embodiments.
- the terminal includes: an antenna 1201, a radio frequency part 1202, and a signal processing part 1203.
- the antenna 1201 is connected to the radio frequency part 1202.
- the radio frequency part 1202 receives the information sent by the network device through the antenna 1201, and sends the information sent by the network device to the signal processing part 1203 for processing.
- the signal processing section 1203 processes the information of the terminal and sends it to the radio frequency section 1202.
- the radio frequency section 1202 processes the information of the terminal and sends it to the network device via the antenna 1201.
- the signal processing section 1203 may include a modulation and demodulation subsystem to implement processing of each communication protocol layer of the data; it may also include a central processing subsystem to implement processing of the terminal operating system and the application layer; in addition, it may also include Other subsystems, such as multimedia subsystem, peripheral subsystem, etc. Among them, the multimedia subsystem is used to control the terminal camera and screen display, and the peripheral subsystem is used to achieve connection with other devices.
- the modem subsystem can be a separately set chip.
- the above device for a terminal may be located in the modem subsystem.
- the modem subsystem may include one or more processing elements 12031, for example, including a main control CPU and other integrated circuits.
- the modulation and demodulation subsystem may further include a storage element 12032 and an interface circuit 12033.
- the storage element 12032 is used to store data and programs, but the program used to execute the method performed by the terminal in the above method may not be stored in the storage element 12032, but stored in a memory other than the modem subsystem, and used When the modem subsystem is loaded and used.
- the interface circuit 12033 is used to communicate with other subsystems.
- the above device for a terminal may be located in a modem subsystem.
- the modem subsystem may be implemented by a chip.
- the chip includes at least one processing element and an interface circuit, and the processing element is configured to execute any method performed by the terminal.
- Each step of the interface circuit is used to communicate with other devices.
- the unit that implements each step in the above method in the terminal may be implemented in the form of a processing element scheduler.
- a device applied to a terminal includes a processing element and a storage element, and the processing element calls a program stored by the storage element to execute the above.
- the storage element may be a storage element whose processing element is on the same chip, that is, an on-chip storage element.
- the program for executing the method executed by the terminal in the above method may be a storage element on a different chip from the processing element, that is, an off-chip storage element.
- the processing element calls or loads the program from the off-chip storage element to the on-chip storage element to call and execute the method executed by the terminal in the foregoing method embodiments.
- a unit applied to a terminal to implement each step in the above method may be configured as one or more processing elements, and these processing elements are provided on a modulation and demodulation subsystem.
- the processing elements here may be Integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated together to form a chip.
- the unit that implements each step in the above method in the terminal may be integrated together and implemented in the form of a system-on-a-chip (SOC), which is used to implement the above method.
- SOC system-on-a-chip
- At least one processing element and storage element may be integrated in the chip, and the method executed by the terminal may be implemented by the processing element calling a stored program of the storage element; or, at least one integrated circuit may be integrated in the chip to implement the above terminal
- the functions of some units are implemented in the form of a program called by a processing element, and the functions of some units are implemented in the form of an integrated circuit.
- the above apparatus applied to a terminal may include at least one processing element and an interface circuit, where at least one processing element is configured to execute any method performed by the terminal provided by the foregoing method embodiments.
- the processing element may execute a part or all of the steps executed by the terminal in a manner of calling the program stored in the storage element in a first manner; or a method of integrating the logic of the hardware in the processor element with the instruction in a second manner: Some or all of the steps performed by the terminal are performed in a manner; of course, some or all of the steps performed by the terminal may also be performed in combination with the first and second methods.
- the processing elements here are the same as described above, and may be general-purpose processors, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or one or more micro-processing Processor DSP, or one or more FPGAs, or a combination of at least two of these integrated circuit forms.
- general-purpose processors such as a CPU
- integrated circuits configured to implement the above methods, such as: one or more ASICs, or one or more micro-processing Processor DSP, or one or more FPGAs, or a combination of at least two of these integrated circuit forms.
- a storage element may be a single memory or a collective term for multiple storage elements.
- the embodiment of the present application further provides a communication system, which includes one or more of the foregoing terminals, and optionally, may further include a network device.
- An embodiment of the present application further provides a bandwidth part processing apparatus, which is applied to a terminal and includes at least one processing element (or chip) for performing the foregoing method embodiments.
- the present application provides a program for processing a bandwidth part, which is used to execute the method in the foregoing embodiment when executed by a processor.
- the present application also provides a program product, such as a computer-readable storage medium, including the program of the bandwidth part processing method mentioned above.
- the embodiments of the present application may be provided as a method, a system, or a computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
- computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
- Embodiments of the present application are described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions.
- These computer program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, so that the instructions generated by the processor of the computer or other programmable data processing device are used to generate instructions Means for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.
- These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions
- the device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.
- These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种带宽部分处理方法及装置,该方法包括:当激活的第一BWP对应的去激活定时器超时,确定第一BWP所在的载波中是否包括处于激活态的第二BWP,当所述载波中包括处于激活态的第二BWP时,去激活所述第一BWP。通过该方法,可避免不必要的BWP切换流程,进一步的,由于该方法后续不再激活默认BWP或者初始BWP,终端也无需再监听默认BWP或者初始BWP,只需要监听当前载波中的第二BWP,可降低终端监听BWP的开销,从而降低通信过程中终端的功耗。
Description
本申请要求在2018年8月9日提交中国专利局、申请号为201810904442.7、发明名称为《一种带宽部分处理方法及装置》的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信技术领域,尤其涉及一种带宽部分(bandwidth part,BWP)处理方法及装置。
在第5代移动通信(the 5
th generation,5G)新空口(new radio,NR)***中,***带宽或者载波带宽可以达到400兆赫兹(MHz)。而终端通常情况下支持的带宽能力小于***带宽或者载波带宽,终端的带宽能力可以是指终端最大可支持的带宽大小,例如终端支持的带宽能力可能为20MHz、50MHz、100MHz等。
为了适配终端的带宽能力,可以在一个载波(carrier)上配置多个BWP,每个BWP可以包括频域上的部分资源。例如一段连续的资源;例如,一个BWP包含载波上一组连续的资源块(resource block,RB)。网络设备(例如基站)可以为终端分配该终端能够支持的BWP。网络设备可激活为终端所配置的BWP,进而在激活的BWP上和该终端进行信号传输。目前在同一时刻,网络设备在一个载波上只为终端激活该载波上的一个BWP,从而网络设备和终端在该激活的BWP上传输信号。
随着5G***带宽的增大,NR***可支持的业务类型也越来越多,不同类型业务的信号可能需要通过载波上不同的BWP传输,若一个载波在同一时刻仅支持一个激活的BWP,很难满足信号的传输需求,为及时传输多个不同类型业务的信号,可激活一个载波上的多个BWP。然而,当一个载波在同一时刻有多个BWP处于激活态时,对于BWP的激活和去激活处理如果仍沿用现有的处理方法,可能会引起不必要的操作,从而增加设备的功耗。
发明内容
本申请实施例提供一种带宽部分处理方法及装置,以降低通信过程中设备的功耗。
第一方面,本申请实施例提供一种带宽部分处理方法,该方法可由终端或能够支持终端实现该方法的通信装置(例如芯片***)执行,在本申请中,以由终端执行该方法为例进行描述。该方法包括:当激活的第一BWP对应的去激活定时器超时,确定第一BWP所在的载波中是否包括处于激活态的第二BWP,当所述载波中包括处于激活态的第二BWP时,去激活所述第一BWP。
第二方面,本申请提供一种带宽部分处理装置,包括:包括用于执行以上第一方面各个步骤的单元或手段(means)。
第三方面,本申请提供一种带宽部分处理装置,包括至少一个处理器,用于与存储器连接,所述至少一个处理器用于调用所述存储器中存储的程序以执行以上第一方面提供的方法。该存储器可以为该装置内的存储器,也可以为该装置外的存储器。
第四方面,本申请提供一种带宽部分处理装置,包括至少一个处理器和接口电路,所 述至少一个处理器用于执行以上第一方面提供的方法。
第五方面,本申请提供一种带宽部分处理程序,该程序在被处理器执行时用于执行以上第一方面的方法。
第六方面,提供一种程序产品,例如计算机可读存储介质,包括第五方面的程序。
可见,在以上各个方面,终端在确定激活的第一BWP对应的去激活定时器超时之后,若确定所述第一BWP所在的载波中还包括处于激活态的第二BWP,则对所述第一BWP执行去激活。而无需像现有技术中一样,当激活的第一BWP对应的去激活定时器超时之后,需要执行BWP切换流程,具体的,对第一BWP执行去激活,并激活载波中的默认BWP或者初始BWP。采用本申请的方法,仅对第一BWP执行去激活,可避免不必要的BWP切换流程,进一步的,由于上述的方法不再激活默认BWP或者初始BWP,终端也无需再监听默认BWP或者初始BWP,只需要监听当前载波中的第二BWP,可降低终端监听BWP的开销,从而降低通信过程中终端的功耗。
在以上各方面中,第二BWP可以为默认BWP或初始BWP,也可以为非默认BWP和非初始BWP,本申请不做限定。
在一种可能的设计中,以第二BWP为非默认BWP和非初始BWP为例。在该种设计中,当所述载波中包括处于激活态的所述第二BWP时,终端还可以不激活所述载波中的默认BWP或初始BWP。这样,终端无需监听默认BWP或者初始BWP,可降低终端监听BWP的开销,从而降低通信过程中终端的功耗。
在一种可能的设计中,当所述载波中不包括处于激活态的所述第二BWP时,终端激活所述载波中的默认BWP或初始BWP。
本申请中对载波中配置的默认BWP的数量不做限定。在一种可能的设计中,所述载波中的默认BWP的数量为至少两个。在该种设计中,终端激活所述载波中的默认BWP,可包括:激活至少两个所述默认BWP中包括的全部BWP,或者,激活至少两个所述默认BWP中包括的满足预设规则的BWP。
在一种可能的设计中,所述预设规则可以包括:
BWP索引最大;
BWP索引最小;
子载波间隔SCS最大;
SCS最小;
循环前缀CP最大;
CP最小;或,
与所述第一BWP的参数相同。
在一种可能的设计中,所述载波包括至少两个BWP组,每个BWP组内包括至少一个BWP,每个BWP组内同一时刻处于激活态的BWP的数量为1或0。在该种设计中,确定所述第一BWP所在的载波中是否包括处于激活态的第二BWP,包括:
当第一BWP组不包括默认BWP时,在第二BWP组内确定是否包括处于激活态的第二BWP,所述第一BWP组为所述至少两个BWP组中包括所述第一BWP的BWP组,所述第二BWP组为所述至少两个BWP组中不包括所述第一BWP的BWP组;或者,
当第一BWP组不包括默认BWP和初始BWP时,在第二BWP组内确定是否包括处于激活态的第二BWP,所述第一BWP组为所述至少两个BWP组中包括所述第一BWP 的BWP组,所述第二BWP组为所述至少两个BWP组中不包括所述第一BWP的BWP组。
在一种可能的设计中,所述载波包括至少两个BWP组,每个所述BWP组内包括至少一个BWP。在该种设计中,确定所述第一BWP所在的载波中是否包括处于激活态的第二BWP,包括:在第一BWP组内确定是否包括处于激活态的第二BWP,所述第一BWP组为所述至少两个BWP组中包括所述第一BWP的BWP组。
在一种可能的设计中,同一个所述BWP组内的BWP对应的去激活定时器的定时时长相同。
在一种可能的设计中,所述去激活定时器的定时时长可以为载波特定或BWP特定的。其中载波特定可以理解为,同一载波上任意激活的非默认BWP所维护的去激活定时器的定时时长相同。BWP特定可以理解为,去激活定时器的定时时长与特定非默认BWP对应,当去激活定时器的定时时长被配置为BWP特定时,一个载波中的多个非默认BWP所维护的去激活定时器的定时时长可以不同。
在一种可能的设计中,所述去激活定时器的定时时长可以与所述载波中BWP的参数相关。所述的BWP的参数可以包括SCS和/或CP。
在一种可能的设计中,所述BWP组通过预定义规则预先配置或者通过信令配置。
在一种可能的设计中,所述预定义规则包括同一个所述BWP组内的BWP的参数相同,或者,同一个所述BWP组内的BWP配置同一个默认BWP。
图1a-图1c为本申请实施例提供的BWP在载波带宽中的配置示意图;
图2为本申请实施例可应用的一种通信***的示意图;
图3为本申请实施例提供的一种网络架构的示意图;
图4为本申请实施例提供的另一种网络架构的示意图;
图5为本申请实施例提供的一种带宽部分处理方法的实施流程图;
图6a-图6c为本申请实施例提供的带宽部分处理方法示意图;
图7为本申请实施例提供的另一种带宽部分处理方法的实施流程图;
图8为本申请实施例提供的又一种带宽部分处理方法示意图;
图9为本申请实施例提供的又一种带宽部分处理方法的实施流程图;
图10为本申请实施例提供的又一种带宽部分处理方法示意图;
图11为本申请实施例提供的一种带宽部分处理装置结构示意图;
图12为本申请实施例提供的一种终端示意图。
下面结合说明书附图对本申请进行具体说明。
首先,对本申请中的部分用语进行解释说明,以便于本领域技术人员理解。
1)、终端,可以是指向用户提供语音和/或数据连通性的设备,又称之为用户设备(user equipment,UE)、移动台(mobile station,MS)、移动终端(mobile terminal,MT)等。例如,具有无线连接功能的手持式设备、车载设备等。目前,一些终端的举例为:手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device,MID)、可穿戴设备,虚拟现实(virtual reality,VR)设备、增强现实(augmented reality,AR)设 备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
2)、网络设备,可以是指无线网络中的设备,例如将终端接入到无线网络的无线接入网(radio access network,RAN)节点(或设备),又可以称为基站。目前,一些RAN节点的举例为:继续演进的节点B(gNB)、传输接收点(transmission reception point,TRP)、演进型节点B(evolved Node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(Node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved NodeB,或home Node B,HNB)、基带单元(base band unit,BBU),或无线保真(wireless fidelity,Wifi)接入点(access point,AP)等。另外,在一种网络结构中,RAN可以包括集中单元(centralized unit,CU)节点和分布单元(distributed unit,DU)节点。这种结构将长期演进(long term evolution,LTE)***中eNB的协议层拆分开,部分协议层的功能放在CU集中控制,剩下部分或全部协议层的功能分布在DU中,由CU集中控制DU。
3)、***带宽,是指NR***中一个载波支持的带宽,也可称为载波带宽或者载波等。例如NR***的载波带宽可以为10MHz、15MHz、20MHz、50MHz、100MHz以及400MHz等中的一种。
4)、载波,可以是指用于调制待发送信号的无线电波,例如,正弦波。载波信号,通常是指用于调制待传输信号的正弦信号,是与载波相对应的一个概念。
5)、BWP,是指在NR***中为适配终端的带宽能力,在载波带宽内为终端配置的资源,例如,载波带宽上一组连续的RB,一个载波中可配置多个BWP,例如一个载波可以配置4个BWP。其中,处于激活状态的BWP为当前可用BWP。此外,带宽部分有时也可称为载波带宽部分(carrier bandwidth part)、子带(subband)带宽、窄带(narrowband)带宽,或者其他的名称,本申请对名称并不做限定,为了便于描述,以名称是BWP为例说明。例如,一个BWP包含K(K>0)个子载波;或者,一个BWP为N个不重叠的RB所在的频域资源,该RB的子载波间隔可以为15KHz、30KHz、60KHz、120KHz、240KHz、480KHz或其他值;或者,一个BWP为M个不重叠的资源块组(resource block group,RBG)所在的频域资源,例如,一个RBG包括P(P>0)个连续的RB,该RB的子载波间隔(subcarrier spacing,SCS)可以为15KHz、30KHz、60KHz、120KHz、240KHz、480KHz或其他值,例如为2的整数倍。请参考图1a-图1c所示,为本申请实施例提供的三种BWP在载波带宽中的配置情况。图1a为在载波带宽中配置一个BWP的情况,网络设备可先为终端分配在终端带宽能力范围内的BWP,当然还可以进一步为终端分配该BWP中的部分或全部资源用于数据传输。网络设备可根据实际场景为终端配置不同的BWP情况。例如,为了节省终端的功耗,网络设备可以根据终端的业务量为终端分配BWP。当终端没有业务数据传输或只有少量业务数据传输时,可以为终端分配较小的BWP用于接收控制信息和少量的数据信息,如图1b所示的BWP1;当终端有大量业务数据需要传输时,可以为终端分配较大的带宽部分,如图1b所示的BWP2。又例如,由于5G中可以支持多种业务类型、通信场景,针对不同的业务类型、通信场景,可以配置不同的参数,网络设备可以根据终端不同的业务类型为终端分配相应的BWP,如图1c所示,一个BWP 可以对应一种业务类型,为了满足该业务类型的业务需求,可以将该BWP配置能够满足业务需求的参数集(numerology)。其中,由图1b可知,不同的BWP可以占用部分重叠的频域资源。由图1c可知,不同的BWP也可以占用完全不同的频域资源以及使用不同的numerology。在本申请实施例中,不同BWP对应的numerology可以相同也可以不同,本申请不作限制。可以理解的是,图1a-图1c中仅以在一个载波中配置一个或两个BWP为例说明,实际应用中可在载波中配置多个BWP,本申请不做限定。
示例性地,本申请中所述的BWP可以是下行BWP,用于终端进行下行接收,此时该BWP的带宽不超过终端的接收带宽能力;或者,BWP也可以是上行BWP,用于终端进行上行发送,此时该BWP的带宽不超过终端的发送带宽能力。
6)、numerology,是指通信***所采用的参数。例如可以是指空口(air interface)中的一系列物理层参数。一个BWP可以对应一个numerology。其中,NR***可支持多种numerology,多个numerology可以同时使用。numerology可以包括以下参数信息中的一个或多个:子载波间隔,循环前缀(cyclic prefix,CP)的信息,时间单位的信息,带宽等。CP的信息可以包括CP长度和/或者CP类型。例如,CP可以为常规CP(normal CP,NCP),或者扩展CP(extended CP,ECP)。时间单位用于表示时域内的时间单元,例如可以为采样点、符号、微时隙(mini-slot)、时隙(slot)、子帧(subframe)或者无线帧等等。时间单位的信息可以包括时间单位的类型、长度或者结构等。例如,numerology可以包括子载波间隔和CP,参阅表1所示,表1给出了NR***中目前可以支持的、由子载波间隔和CP定义的numerology:
表1
μ | 子载波间隔=2 μ·15(kHz) | CP类型 |
0 | 15 | 常规(normal) |
1 | 30 | 常规 |
2 | 60 | 常规或扩展(extended) |
3 | 120 | 常规 |
4 | 240 | 常规 |
其中,μ用于确定子载波间隔,例如,μ=0时,子载波间隔为15kHz,μ=1时,子载波间隔为30kHz。
以子载波间隔为例,若终端支持子载波间隔15kHz和30kHz,则网络设备可以为终端分配一个子载波间隔为15KHz的BWP,和一个子载波间隔为30KHz的BWP,终端根据不同的场景和业务需求,可以切换到不同的BWP上传输信号。当终端支持多个BWP时,其中不同的BWP对应的numerology可以相同也可以不同。
其中,子载波间隔可以为大于等于0的整数。例如可以为15KHz、30KHz、60KHz、120KHz、240KHz、480KHz等。子载波间隔,是正交频分复用(orthogonal frequency division multiplexing,OFDM)***中,频域上相邻的两个子载波的中心位置或峰值位置之间的间隔值。例如,LTE***中的子载波间隔为15KHz,NR***的子载波间隔可以是15kHz,或30kHz,或60kHz,或120kHz等。
7)、初始(initial)BWP,用于终端的初始随机接入,可包括初始下行BWP和初始上行BWP。可以理解为在终端的初始随机接入过程中,终端可通过初始BWP与网络设备传输信号或执行相关操作。
8)、非初始BWP,是与初始BWP相对应的一个概念,载波中包括的除初始BWP之外的BWP均可称为非初始BWP。
9)、BWP切换(switch),用于切换激活的BWP。一种可能的实现方式中,在终端的随机接入过程完成后,网络设备(例如基站)通过无线资源控制(radio resource control,RRC)消息为终端配置一个或多个BWP,网络设备可以通过RRC消息或下行控制信息(downlink control information,DCI)来切换激活的BWP,即,激活新的BWP,以及去激活旧的BWP。切换的方法,是在RRC消息或DCI中携带目标激活BWP的索引,从而使得终端进行BWP切换。终端在BWP切换时,终端对原来工作的BWP进行去激活操作,以及对待切换的目标BWP进行激活操作。另一种可能的实现方式中,在当前激活的BWP对应的去激活定时器超时时,终端执行BWP切换,即终端对原来工作的BWP进行去激活操作,以及对待切换的目标BWP进行激活操作。示例性地,对于频分双工(frequency division duplexing,FDD)制式的***,下行通信过程中的BWP切换和上行通信过程中的BWP切换可以独立进行,即可以通过RRC消息或DCI仅对下行BWP/上行BWP进行切换;对于时分双工(time division duplexing,TDD)制式的***,下行BWP和上行BWP是成对出现和切换的,例如对下行BWP进行切换时,与该下行BWP对应的上行BWP也同时进行切换。
10)、默认(default)BWP,在NR***中,除了用于初始随机接入的初始BWP外,还可在一个载波上配置多个BWP,示例性地,可在一个载波上配置4个BWP。对于下行通信来说,可将下行载波中配置的除初始下行BWP之外的多个下行BWP中的一个下行BWP设置为默认BWP,例如可以将多个下行BWP中带宽较窄的下行BWP设置为默认BWP。本申请中所涉及的默认BWP,也可称为默认下行BWP,为统一描述,下文中均描述为默认BWP。在NR***中引入默认BWP,一方面可在终端和网络设备对当前激活(active)BWP理解不一致时,使得网络设备能够正确找到该终端。例如,网络设备可向终端发送指示BWP切换的DCI,以使终端切换当前激活的BWP,若该DCI丢失,导致终端未接收到该DCI,此时终端不会切换当前激活BWP,而网络设备误认为终端已执行BWP切换,进而在误解的激活BWP上调度终端,但并不能收到终端的响应,一段时间之后,终端可回退到默认BWP上,以使网络设备可在默认BWP上重新找到该终端。另一方面,可在终端长时间没有被调度时,回退到带宽较窄的默认BWP上,可降低终端的功率消耗。
11)、非默认BWP,是与默认BWP相对应的一个概念,载波中包括的除默认BWP之外的BWP均可称为非默认BWP。
12)、去激活定时器(bwpInactivityTimer),载波中激活的非默认BWP自身维护一个对应的去激活定时器,当载波中一个非默认BWP被激活时,启动与该非默认BWP对应的去激活定时器,当该去激活定时器超时时,会执行BWP切换。可以理解为,去激活定时器用于控制BWP处于激活态的时间。具体的,若该载波配置了默认BWP,终端执行BWP切换可从当前激活的BWP切换到默认BWP,否则,若该载波未配置默认BWP,终端执行BWP切换可从当前激活的BWP切换到初始BWP。其中,从当前激活的BWP切换到默认BWP是指对当前激活的BWP执行去激活操作,并激活默认BWP。类似地,从当前激活的BWP切换到初始BWP是指对当前激活的BWP执行去激活操作,并激活初始BWP。
13)、去激活定时器的定时时长,是指从去激活定时器启动到超时运行的时长,可以由总计数值和计数粒度(或者称之为计数单位)决定。
14)、激活态,可以是指可工作的状态。BWP处于激活态是指BWP处于可工作的状态,例如,可实现信号发送或接收的状态。非激活态,是与激活态相对应的一个概念,可以是指不可工作的状态。BWP处于非激活态是指BWP处于不可工作的状态。示例性地,处于非激活态的BWP不可以用于信号发送或接收。
15)、激活的BWP,是指处于激活态的BWP,也可以理解为可发送和/或接收信号的BWP。未激活的BWP,是与激活的BWP相对应的一个概念,是指处于非激活态的BWP,也可以理解为不可发送和/或接收信号的BWP。
16)、去激活,对BWP执行去激活,也可以描述为“去激活”BWP,是指将BWP从激活态转换为非激活态,也可以理解为,将可工作的BWP转换为不可工作的BWP。
17)、在本申请的描述中,除非另有说明,“多个”是指两个或两个以上,其它量词与之类似。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
18)、名词“网络”和“***”经常交替使用,但本领域的技术人员可以理解其含义。
需要说明的是,在本申请的描述中,“第一”、“第二”等词汇,仅用于区分描述的目的,而不能理解为指示或暗示相对重要性,也不能理解为指示或暗示顺序。
请参考图2,其为本申请实施例可应用的一种通信***的示意图。如图2所示,终端130可接入到无线网络,以通过无线网络获取外网(例如因特网)的服务,或者通过无线网络与其它终端通信。该无线网络中包括无线接入网(radio access network,RAN)110和核心网(core network,CN)120,其中RAN110用于将终端130接入到无线网络,CN120用于对终端进行管理并提供与外网通信的网关。应理解,图2所示的网络架构中仅以包括两个终端为例进行说明,但本申请实施例并不限于此,例如,网络架构中还可以包括更多的终端;类似地,网络架构中也可以包括更多的RAN110,并且还可以包括其它设备。
请参考图3,其为本申请实施例提供的一种网络架构的示意图。如图3所示,该网络架构包括CN设备和RAN设备。其中RAN设备包括基带装置和射频装置,其中基带装置可以由一个节点实现,也可以由多个节点实现,射频装置可以从基带装置拉远独立实现,也可以集成在基带装置中,或者部分拉远部分集成在基带装置中。例如,在长期演进(long term evolution,LTE)通信***中,RAN设备(eNB)包括基带装置和射频装置,其中射频装置可以相对于基带装置拉远布置,例如射频拉远单元(remote radio unit,RRU)相对于BBU拉远布置。
RAN设备和终端之间的通信遵循一定的协议层结构。例如控制面协议层结构可以包括无线资源控制(radio resource control,RRC)层、分组数据汇聚层协议(packet data convergence protocol,PDCP)层、无线链路控制(radio link control,RLC)层、媒体接入控制(media access control,MAC)层和物理层等协议层的功能。用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层等协议层的功能;在一种实现中,PDCP层之上还可以包括业务数据适配(service data adaptation protocol,SDAP)层。
RAN设备可以由一个节点实现RRC、SDAP、PDCP、RLC和MAC等协议层的功能;或者可以由多个节点实现这些协议层的功能;例如,在一种演进结构中,RAN设备可以包括集中单元(centralized unit,CU)和分布单元(distributed unit,DU),多个DU可以由一个CU集中控制。如图3所示,CU和DU可以根据无线网络的协议层划分,例如PDCP 层及以上协议层的功能设置在CU,PDCP以下的协议层,例如RLC层和MAC层等的功能设置在DU。
这种协议层的划分仅仅是一种举例,还可以在其它协议层划分,例如在RLC层划分,将RLC层及以上协议层的功能设置在CU,RLC层以下协议层的功能设置在DU;或者,在某个协议层中划分,例如将RLC层的部分功能和RLC层以上的协议层的功能设置在CU,将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。此外,也可以按其它方式划分,例如按时延划分,将处理时间需要满足时延要求的功能设置在DU,不需要满足该时延要求的功能设置在CU。
此外,射频装置可以拉远,不放在DU中,也可以集成在DU中,或者部分拉远部分集成在DU中,在此不作任何限制。
请继续参考图4,相对于图3所示的架构,还可以将CU的控制面(CP)和用户面(UP)分离,分成不同实体来实现,分别为控制面CU实体(CU-CP实体)和用户面CU实体(CU-UP实体)。
在以上网络架构中,CU产生的信令可以通过DU发送给终端,或者终端产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装而透传给终端或CU。以下实施例中如果涉及这种信令在DU和终端之间的传输,此时,DU对信令的发送或接收包括这种场景。例如,RRC或PDCP层的信令最终会处理为PHY层的信令发送给终端,或者,由接收到的PHY层的信令转变而来。在这种架构下,该RRC或PDCP层的信令,即也可以认为是由DU发送的,或者,由DU和射频装载发送的。
在以上实施例中可以将CU划分为RAN侧的网络设备,此外,也可以将CU划分为CN侧的网络设备,在此不做限制。
本申请以下实施例中的装置,根据其实现的功能,可以位于终端或网络设备。当采用以上CU-DU的结构时,网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的RAN设备。
在无线通信***中,例如5G***中,可支持的业务类型和/或通信场景越来越多,故提出了支持多种numerology的设计。针对不同的业务类型和/或通信场景,可以独立设置numerology。网络设备可以在一个载波中配置多个BWP,并可以为该多个BWP中的每个BWP独立配置numerology,用于在***频率资源中支持多种业务类型和/或通信场景。
目前,网络设备在一个载波上可以为终端配置多个BWP,但是在同一时刻,在一个载波上网络设备只为终端激活其中配置的一个BWP,从而网络设备和终端在该激活的BWP上传输信号。对于上行载波,网络设备配置和激活的为上行BWP,对于下行载波,网络设备配置和激活的为下行BWP,本申请实施例中以网络设备为终端配置下行BWP为例进行说明。然而,不同业务类型和/或通信场景的信号可能需要通过载波上不同的BWP传输,若一个载波在同一时刻仅支持一个激活的BWP,很难满足信号的传输需求,为及时传输多个不同类型业务的信号,可激活一个载波上的多个BWP。然而,当一个载波在同一时刻有多个BWP处于激活态时,对于BWP的处理现有技术中并没有相应的解决方法,如果仍沿用现有的处理方法,可能会引起不必要的操作,从而增加设备的功耗。例如,假设网络设备为终端配置了BWP1、BWP2和默认BWP,且BWP1和BWP2当前处于激活态。若BWP1对应的去激活定时器超时,采用现有技术的方法,终端执行BWP切换,将去激活BWP1,并激活默认BWP,进而终端需要监听BWP2和默认BWP(例如,对PDCCH进 行监听);在本申请中,终端监听BWP是指终端在BWP上对数据和/或控制信道进行监听。显然若仍沿用现有技术的方法,会引起不必要的操作,从而增加设备的功耗。
基于上述存在的问题,本申请实施例提供一种带宽部分处理方法,通过在激活的第一BWP对应的去激活定时器超时时,确定第一BWP所在的载波中是否包括处于激活态的第二BWP,当载波中包括处于激活态的第二BWP时,去激活第一BWP。通过该方法,可避免不必要的BWP切换流程,且,由于BWP切换流程通常需要一定的时间,故通过该方法还可节省BWP处理时间。进一步的,当第二BWP为非默认BWP或初始BWP时,由于该方法后续不再激活默认BWP或者初始BWP,终端也无需再在默认BWP或者初始BWP对PDCCH进行监听,只需要在当前载波中的第二BWP上进行监听,可降低终端在BWP上进行监听的开销,从而降低通信过程中终端的功耗。
实施例一:
请参考图5,其为本申请实施例提供的一种带宽部分处理方法的实施流程图。参阅图5所示,该方法包括:
S101:当激活的第一BWP对应的去激活定时器超时,确定第一BWP所在的载波中是否包括处于激活态的第二BWP。
本申请实施例中,所涉及的方法可由终端或能够支持终端实现该方法的通信装置(例如芯片***)执行,在本申请中,以由终端执行该方法为例进行描述。则步骤S101~S102可以均由终端来执行。
需要说明的是,本申请实施例中第一BWP和第二BWP为同一载波中不同的BWP,该BWP可以是下行BWP或上行BWP。例如,当终端为信号接收端时,该BWP是下行BWP,反之,当终端为信号发送端时,该BWP是上行BWP。本申请中以载波为下行载波、BWP为下行BWP为例说明。
图5中的方法可适用于以载波为单位配置默认BWP的场景。以载波为单位配置默认BWP,是指一个载波中配置的默认BWP,可用于该载波中任意激活的非初始或非默认BWP回退到该默认BWP。
本申请实施例中,去激活定时器的定时时长,可以由总计数值和计数粒度(或者称之为计数单位)决定。例如,网络设备配置去激活定时器的总计数值为100,计数粒度为1ms时,去激活定时器的定时时长为100ms。又例如,网络设备配置去激活定时器的总计数值为100,计数粒度为1symbol时,去激活定时器的定时时长为100symbol。其中,去激活定时器每次计数的计数粒度可以是1ms,或0.1ms,或1个slot,或1个symbol的持续时长,本申请不做限定。本申请中,去激活定时器的定时时长可以与载波中BWP的参数相关。示例性地,去激活定时器的计数粒度可以与载波中BWP的参数相关。例如计数粒度slot的值可以为该载波上配置的所有BWP中slot值最大/最小的BWP对应的slot的值。
本申请实施例中,去激活定时器的定时时长可以为载波特定或BWP特定的。相应的,去激活定时器的计数粒度和总计数值可以为载波特定或BWP特定的。下面以去激活定时器的定时时长为例对载波特定和BWP特定进行解释。
载波特定,是指同一载波上激活的非默认BWP所维护的去激活定时器的定时时长相同。示例性地,假设一个载波上包括3个非默认BWP,每个激活的非默认BWP维护一个对应的去激活定时器,若将该去激活定时器的定时时长设置为载波特定的,则该载波上3个非默认BWP在激活态时分别维护的3个去激活定时器的定时时长相同。例如,网络设 备对一个载波配置的去激活定时器的定时时长为100ms,则该载波上每个非默认BWP激活时所维护的去激活定时器的定时时长为100ms。又例如,网络设备为一个载波配置的去激活定时器的定时时长为100slot,则该载波上每个非默认BWP激活时所维护的去激活定时器的定时时长为100slot,以slot的值为载波上配置的所有BWP中slot值最大的BWP对应的slot的值为例,若该载波上配置的所有BWP中slot值最大的BWP对应的slot的值为0.5ms,则该载波上每个非默认BWP激活时所维护的去激活定时器的定时时长为100slot=50ms。可以理解的是,若去激活定时器的定时时长为载波特定的,则相应的去激活定时器的计数粒度和总计数值也是载波特定的。
在本例中,BWP对应的去激活定时器的定时时长,可以配置在网络设备对相应BWP所在载波进行配置的RRC信元中,该去激活定时器的定时时长的配置参数可以为时长本身、或决定时长的其它因子的值,例如总计数值和/或计数粒度。
BWP特定,是指去激活定时器的定时时长与非默认BWP对应。示例性地,假设一个载波上包括3个非默认BWP,分别为第一非默认BWP、第二非默认BWP和第三非默认BWP,且激活的第一非默认BWP维护第一去激活定时器,激活的第二非默认BWP维护第二去激活定时器,激活的第三非默认BWP维护第三去激活定时器,若将该载波上的去激活定时器的定时时长设置为BWP特定的,则上述第一去激活定时器、第二去激活定时器以及第三去激活定时器可分别对应三个定时时长。例如,网络设备可对第一非默认BWP配置对应的去激活定时器的定时时长为100ms,对第二非默认BWP配置对应的去激活定时器的定时时长为50ms,对第三非默认BWP配置对应的去激活定时器的定时时长为20ms;在本例中,BWP对应的去激活定时器的定时时长,可以配置在网络设备对相应BWP进行配置的RRC信元中。又例如,网络设备可对第一非默认BWP配置对应的去激活定时器的定时时长为100slot
1,slot
1为第一默认BWP对应的slot值,对第二非默认BWP配置对应的去激活定时器的定时时长为50slot
2,slot
2为第二默认BWP对应的slot值,对第三非默认BWP配置对应的去激活定时器的定时时长为20slot
3,slot
3为第三默认BWP对应的slot值;在本例中,BWP对应的去激活定时器的定时时长,可以配置在网络设备对相应BWP进行配置的RRC信元中。又例如,网络设备可配置载波中激活的非默认BWP所维护的去激活定时器的定时时长为100slot,其中slot为激活的非默认BWP对应的slot值,如激活的非默认BWP1对应的slot为1ms,则非默认BWP1维护的去激活定时器的定时时长为100ms,激活的非默认BWP2对应的slot为0.5ms,则非默认BWP2维护的去激活定时器的定时时长为50ms;在本例中,BWP对应的去激活定时器的定时时长,可以配置在网络设备对相应BWP所在载波进行配置的RRC信元中,也可以配置在网络设备对相应BWP所在服务小区进行配置的RRC信元中。可以理解的是,若去激活定时器的定时时长为BWP特定的,则相应的去激活定时器的计数粒度和总计数值也是BWP特定的。另外,不同BWP对应的去激活定时器的定时时长可以相同,或可以不同。
在本例中,BWP对应的去激活定时器的定时时长,可以配置在网络设备对相应BWP进行配置的RRC信元中,或可以配置在网络设备对相应BWP所在载波进行配置的RRC信元中,该去激活定时器的定时时长的配置参数可以为时长本身、或决定时长的其它因子的值,例如总计数值和/或计数粒度。
S102:当载波中包括处于激活态的第二BWP时,去激活第一BWP。
本申请实施例中,当终端确定第一BWP所在的载波中包括处于激活态的第二BWP时, 去激活第一BWP。
其中,去激活第一BWP,可以理解为对第一BWP执行去激活操作,对第一BWP去激活之后,使得第一BWP由激活态转换为非激活态。
本申请实施例中,第二BWP可以是默认BWP或初始BWP。当然,第二BWP也可以是非默认BWP和非初始BWP。需要说明的是,非默认BWP和非初始BWP,是指载波中既不是默认BWP也不是初始BWP的BWP。
一种可能的实现方式中,在第二BWP为非默认BWP和非初始BWP的情况下,终端在执行S102的基础上,还可不激活载波中的默认BWP或初始BWP。而采用现有的方法,当激活的第一BWP对应的去激活定时器超时之后,需要执行BWP切换流程,具体的,对第一BWP执行去激活,并激活载波中的默认BWP或者初始BWP。而采用本申请的方法仅对第一BWP执行去激活,可避免不必要的BWP切换流程,进一步的,由于该方法不激活默认BWP或者初始BWP,终端也无需再监听默认BWP或者初始BWP,只需要监听当前载波中的第二BWP,可降低终端监听BWP的开销,从而降低通信过程中终端的功耗。
当然,对于第二BWP为默认BWP或初始BWP的情况下,也可不激活载波中的默认BWP或初始BWP。
需要说明的是,在上述实现方式中,在载波配置了默认BWP的情况下,不激活默认BWP,在载波未配置默认BWP的情况下,不激活初始BWP。
上面描述了当终端确定第一BWP所在的载波中包括处于激活态的第二BWP的处理过程,以下描述终端确定第一BWP所在的载波中不包括处于激活态的第二BWP的处理过程。
一种可能的实现方式中,假设第一BWP所在的载波被配置了默认BWP,当激活的第一BWP对应的去激活定时器超时,终端确定第一BWP所在的载波中不包括处于激活态的第二BWP时,去激活第一BWP,并激活该载波中的默认BWP。也可以理解为,终端执行BWP切换从该载波上的第一BWP切换到默认BWP。
本申请实施例中,对载波中配置的默认BWP的数量不做限定,一个载波中可以配置一个默认BWP,当然也可以配置多于一个的默认BWP,载波中配置的多于一个的默认BWP可以称为默认BWP组。当一个载波中配置默认BWP组时,即,当该载波中的默认BWP的数量为至少两个时,终端可采用如下方式激活该载波中的默认BWP。
第一种方式:终端激活至少两个默认BWP中包括的全部BWP。也可以理解为终端激活默认BWP组内的全部BWP。在该种方式中,一个载波上的全部默认BWP可以处于相同状态,例如,同时处于激活态,或者同时处于非激活态。可选的,在该种方式中,网络设备可通过发送BWP切换命令对某些默认BWP去激活,使得一个载波上的全部默认BWP也可处于不同状态,即一部分默认BWP处于激活态,另一部分默认BWP处于非激活态。
第二种方式:终端激活至少两个默认BWP中包括的满足预设规则的BWP。也可以理解为终端根据预设规则激活默认BWP组内的BWP。在该种方式中,一个载波上的全部默认BWP可以处于不同的状态,例如,默认BWP组内的一个BWP处于激活态,默认BWP组内的其它BWP处于非激活态,或者,默认BWP组内的一个BWP处于非激活态,默认BWP组内的其它BWP处于激活态。
其中,预设规则可包括以下任意一项:
BWP索引最大、BWP索引最小、SCS最大、SCS最小、CP最大、CP最小以及与当前去激活的第一BWP的参数相同。
示例性地,在上述第二种方式中,终端可激活至少两个默认BWP中包括的BWP索引最大/SCS最大/CP最大的一个BWP,也可激活至少两个默认BWP中包括的BWP索引最小/SCS最小/CP最小的一个BWP,还可激活与当前去激活的第一BWP的参数相同的一个BWP。
其中,第一BWP的参数可包括SCS和/或CP等。示例性地,激活与第一BWP的参数相同的一个BWP,可以理解为激活与第一BWP的SCS和/或CP相同的一个BWP。
需要说明的是,在上述第二种方式中,终端也可激活满足预设规则的多个BWP。示例性地,若载波中默认BWP的数量为三,终端可激活三个默认BWP中与第一BWP的SCS和/或CP相同的两个BWP。
另一种可能的实现方式中,假设第一BWP所在的载波未被配置默认BWP,当激活的第一BWP对应的去激活定时器超时,终端确定第一BWP所在的载波中不包括处于激活态的第二BWP时,去激活第一BWP,并激活该载波中的初始BWP。也可以理解为,终端执行BWP切换从该载波上的第一BWP切换到初始BWP。
下文中以具体的实例,对实施例一提供的BWP处理方法进行举例说明。
请参考图6a,其为本申请实施例提供的一种带宽部分处理方法示意图。参阅图6a所示,图6a中一个载波上配置一个默认BWP,以及3个非默认BWP,分别为BWP1,BWP2和BWP3,其中BWP1处于激活态,BWP2、BWP3以及默认BWP均处于非激活态。当BWP1对应维护的去激活定时器超时后,终端可确定当前载波上不包括处于激活态的第二BWP,则执行BWP切换,即,去激活BWP1,并激活默认BWP。
请参考图6b,其为本申请实施例提供的另一种带宽部分处理方法示意图。参阅图6b所示,图6b中一个载波上配置一个默认BWP,以及3个非默认BWP,分别为BWP1,BWP2和BWP3,其中BWP1和BWP2处于激活态,BWP3和默认BWP均处于非激活态。当BWP1对应维护的去激活定时器超时后,终端可确定当前载波上包括处于激活态的第二BWP(激活的BWP2),则仅去激活BWP1,不执行BWP切换。
请参考图6c,其为本申请实施例提供的又一种带宽部分处理方法示意图。参阅图6c所示,图6c中一个载波上配置一个默认BWP,以及3个非默认BWP,分别为BWP1,BWP2和BWP3,其中BWP1和默认BWP均处于激活态,BWP2和BWP3均处于非激活态。当BWP1对应维护的去激活定时器超时后,终端可确定当前载波上包括处于激活态的第二BWP(激活的默认BWP),则仅去激活BWP1,不执行BWP切换。
本申请实施例中,上面均以一个激活的BWP对应的去激活定时器超时为例说明,在实际应用中,可能存在当前载波上多个激活的BWP分别对应的去激活定时器同时超时的情况,在该种情况下,终端确定当前载波中是否还包括处于激活态的第二BWP,若当前载波中还包括处于激活态的第二BWP,则终端仅去激活这多个激活的BWP,若当前载波中不包括处于激活态的第二BWP,则终端执行BWP切换,即,去激活这多个激活的BWP,并激活载波中的默认BWP。
本申请实施例中,终端可根据不同的场景采用不同的BWP处理方法。上述图5中的方法可适用于以载波为单位配置默认BWP的场景。以下针对以BWP组为单位配置默认BWP的场景,对本申请提供的BWP处理方法进行说明。
实施例二:
1、以BWP组为单位配置默认BWP的场景一
在该种场景下,可将一个载波中包括的多个BWP配置为多个BWP组,使得一个载波中可包括至少两个BWP组,每个BWP组内包括至少一个BWP。其中,载波中的BWP组可通过信令配置。例如,可通过RRC信令配置。也可通过预定义规则预先配置。示例性地,预定义规则可包括同一个BWP组内的BWP的参数相同,或者,同一个BWP组内的BWP配置同一个默认BWP;或者,这两个规则均满足。并配置每个BWP组内同一时刻处于激活态的BWP的数量为1或0。这样,相当于对于Rel-15***中的终端只配置一个BWP组,使得每个BWP组单独来看相当于一个独立的Rel-15***中的一个载波,使得BWP分组之后可与Rel-15***兼容。
此外,在该种场景下,对于每个BWP组内配置的默认BWP的数量不做限定。其中,每个BWP组内配置的默认BWP的数量可通过预定义规则或信令配置。示例性地,当通过预定义规则配置默认BWP时,可将一个BWP组内带宽最小的BWP配置为默认BWP。
本申请实施例中,以在每个BWP组内配置的默认BWP的数量为1或0为例进行说明。下面针对以BWP组为单位配置默认BWP的场景,对本申请中提供的BWP处理方法进行说明。
请参考图7,其为本申请实施例提供的另一种带宽部分处理方法的实施流程图。参阅图7所示,该方法包括:
S201a:当激活的第一BWP对应的去激活定时器超时,且当第一BWP组不包括默认BWP时,在第二BWP组内确定是否包括处于激活态的第二BWP。
在实施例二中,第一BWP组为载波中配置的至少两个BWP组中包括第一BWP的BWP组,第二BWP组为载波中配置的至少两个BWP组中不包括第一BWP的BWP组。
本申请实施例中,去激活定时器的定时时长,可以由总计数值和计数粒度(或者称之为计数单位)决定。去激活定时器的定时时长可以为载波特定或BWP特定或BWP组特定的。类似的,去激活定时器的计数粒度和总计数值可以为载波特定或BWP特定或BWP组特定的。关于载波特定和BWP特定的解释可参见实施例一中的描述,此处不再赘述。示例性地,以去激活定时器的定时时长对BWP组特定进行解释,即,BWP组特定是指同一个BWP组内的BWP对应的去激活定时器的定时时长相同。
一种可能的实现方式中,去激活定时器的计数粒度可以和BWP组内的某个BWP的参数相关。示例性地,去激活定时器的计数粒度可以是该BWP组内BWP索引最大/BWP索引最小/SCS最大/SCS最小的BWP上一个符号(symbol)的长度。
S201a中描述了一种可能的在第二BWP组内确定是否包括处于激活态的第二BWP的实现方式。示例性地,当激活的第一BWP对应的去激活定时器超时,终端可判断第一BWP组内是否包括默认BWP,若第一BWP组内包括默认BWP,则执行BWP切换,即,去激活第一BWP,并激活该默认BWP;若第一BWP组内不包括默认BWP,则在第二BWP组内确定是否包括处于激活态的第二BWP。
需要说明的是,实施例二中还可为第一BWP所在的载波配置初始BWP,该初始BWP可以归属于某个BWP组,也可以不归属于任何一个BWP组。S201a可适用于初始BWP不归属于任何一个BWP组的场景。
以下S201b给出另一种可能的在第二BWP组内确定是否包括处于激活态的第二BWP的实现方式。S201b可适用于初始BWP归属于某一个BWP组的场景。
S201b:当激活的第一BWP对应的去激活定时器超时,且当第一BWP组不包括默认 BWP和初始BWP时,在第二BWP组内确定是否包括处于激活态的第二BWP。在该种实现方式中,第一BWP组和第二BWP组的含义与S201a中含义相同,此处不再赘述。
示例性地,当激活的第一BWP对应的去激活定时器超时,终端可判断第一BWP组内是否包括默认BWP,若第一BWP组内包括默认BWP,则去激活第一BWP,且激活该默认BWP;若第一BWP组内不包括默认BWP,则进一步判断第一BWP组内是否包括初始BWP,若第一BWP组内包括初始BWP,则去激活第一BWP,且激活该初始BWP;若第一BWP组内既不包括默认BWP也不包括初始BWP,则在第二BWP组内确定是否包括处于激活态的第二BWP。
需要说明的是,S201a和S201b为两种分别针对不同场景的实现方式,在实际应用中,终端可根据实际场景应用其中的一种实现方式。
S202:当第二BWP组内包括处于激活态的第二BWP时,去激活第一BWP。通过该方法仅去激活第一BWP,而不执行BWP切换,示例性地,不再激活载波中的初始BWP,可避免不必要的BWP切换流程,进而可降低终端设备监听BWP的开销,从而降低终端的功耗。
S203:当第二BWP组内不包括处于激活态的第二BWP时,激活第一BWP所在载波上的初始BWP。
下文中以具体的实例,对实施例二提供的BWP处理方法进行举例说明。
请参考图8,其为本申请实施例提供的又一种带宽部分处理方法示意图。参阅图8所示,图8中一个载波上配置3个BWP组,分别为BWP组1、BWP组2以及BWP组3,其中BWP组1中配置了默认BWP,BWP组2中配置了初始BWP,BWP组3中未配置默认BWP。此外,BWP组1中还包括激活的BWP1,BWP组2中还包括激活的BWP2,BWP组3中包括激活的BWP3。当BWP组1中激活的BWP1对应的去激活定时器超时时,采用实施例二的方法,终端可确定BWP组1中包括默认BWP,故终端去激活BWP1,并激活BWP组1中的默认BWP。当BWP组2中激活的BWP2对应的去激活定时器超时时,采用实施例二的方法,终端可确定BWP组2中不包括默认BWP但包括初始BWP,故终端去激活BWP2,并激活初始BWP。当BWP组3中激活的BWP3对应的去激活定时器超时时,采用实施例二的方法,终端可确定BWP组3既不包括默认BWP也不包括初始BWP,故终端可在BWP组1和BWP组2内确定是否包括处于激活态的第二BWP,若BWP组1和BWP组2内包括处于激活态的第二BWP,则仅去激活BWP3,否则,若BWP组1和BWP组2内不包括处于激活态的第二BWP,则执行BWP切换,即,去激活BWP3,并激活当前载波中的初始BWP。
实施例三:
2、以BWP组为单位配置默认BWP的场景二
在该种场景下,可将一个载波中包括的多个BWP配置为多个BWP组,使得一个载波中可包括至少两个BWP组,每个BWP组内包括至少一个BWP。其中,载波中的BWP组可通过信令配置。例如,可通过RRC信令配置。也可通过预定义规则预先配置。示例性地,预定义规则可包括同一个BWP组内的BWP的参数相同,或者,同一个BWP组内的BWP配置同一个默认BWP;或者,这两个规则均满足。并配置该场景下一个BWP组内可以包括多个同时处于激活态的BWP。
以下针对以BWP组为单位配置默认BWP的场景,对本申请中提供的另一种BWP处 理方法进行说明。
请参考图9,其为本申请实施例提供的又一种带宽部分处理方法的实施流程图。参阅图9所示,该方法包括:
S301:当激活的第一带宽部分BWP对应的去激活定时器超时,在第一BWP组内确定是否包括处于激活态的第二BWP,所述第一BWP组为所述至少两个BWP组中包括所述第一BWP的BWP组。
在实施例三中,第一BWP组为载波中配置的至少两个BWP组中包括第一BWP的BWP组,第二BWP组为载波中配置的至少两个BWP组中不包括第一BWP的BWP组。
在实施例三中,去激活定时器的定时时长,也可以由总计数值和计数粒度(或者称之为计数单位)决定。去激活定时器的定时时长可以为载波特定或BWP特定或BWP组特定的。类似的,去激活定时器的计数粒度和总计数值可以为载波特定或BWP特定或BWP组特定的。关于载波特定、BWP特定以及BWP组特定的解释可参见实施例一和实施例二中的描述,此处不再赘述。
一种可能的实现方式中,去激活定时器的计数粒度可以和BWP组内的某个BWP的参数相关。示例性地,去激活定时器的计数粒度可以是该BWP组内BWP索引最大/BWP索引最小/SCS最大/SCS最小的BWP上一个符号(symbol)的长度。
S302:当载波中包括处于激活态的第二BWP时,去激活第一BWP。
以上以载波中非默认BWP被配置默认BWP的情况说明,即非默认的BWP会关联到默认的BWP的情况。在载波中某一非默认BWP未被配置默认BWP的情况下,若该非默认BWP对应的去激活定时器超时,终端可判断当前载波上是否包括其它激活的BWP,若当前载波上包括其它激活的BWP,则终端不执行BWP切换,可避免不必要的BWP切换流程。
需要说明的是,实施例三中对如何将多个BWP对应同一默认BWP不做限定。示例性地,可以通过协议预定义的方式,将同一参数(例如SCS和/或CP)对应的非默认BWP对应到同一个默认BWP。
下文中以将一个载波中对应同一默认BWP的非默认BWP配置为一个BWP组为例,对实施例三提供的BWP处理方法进行举例说明。在该种情况下,可以理解为每个BWP组内包括一个默认BWP。
请参考图10,其为本申请实施例提供的又一种带宽部分处理方法示意图。参阅图10所示,图10中一个载波上配置6个BWP,包括4个非默认BWP,分别为BWP 1、BWP2、BWP 3以及BWP4,以及两个默认BWP,分别为默认BWP1和默认BWP2。其中,BWP 1和BWP2对应同一默认BWP1,BWP 3和BWP4对应同一默认BWP2。当BWP1对应的去激活定时器超时时,采用实施例三的方法,终端可在BWP1所在的BWP组内确定是否包括处于激活态的第二BWP,由图10可知,BWP1所在的BWP组1中包括处于激活态的BWP 2,故终端仅执行去激活BWP1,不执行BWP切换。此外,若图10中BWP2处于非激活态,则终端执行BWP切换,即,去激活BWP1,并激活默认BWP1。
上述主要从终端的角度对本申请实施例提供的方案进行了介绍。可以理解的是,终端为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元及算法步骤,本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行, 取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能,但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对终端进行功能单元的划分,例如,可以对应各个功能划分各个功能单元,也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
基于相同的发明构思,本申请实施例还提供用于实现以上任一种方法的装置,例如,提供一种装置包括用以实现以上任一种方法中终端所执行的各个步骤的单元(或手段)。
一种可能的实施方式中,本申请实施例提供一种带宽部分处理装置1100。该带宽部分处理装置1100可以应用于终端。图11所示为本申请实施例提供的一种带宽部分处理装置1100的结构示意图,参阅图11所示,该带宽部分处理装置1100包括确定单元1101和去激活单元1102。其中,确定单元1101可用于当激活的第一BWP对应的去激活定时器超时,确定第一BWP所在的载波中是否包括处于激活态的第二BWP,去激活单元1102可用于当所述载波中包括处于激活态的所述第二BWP时,去激活所述第一BWP。
其中,上述带宽部分处理装置1100中涉及的第一BWP和第二BWP为同一载波中不同的BWP,该BWP可以是下行BWP或上行BWP。本申请中以载波为下行载波、BWP为下行BWP为例说明。
可选的,去激活定时器的定时时长,可以由总计数值和计数粒度(或者称之为计数单位)决定。
可选的,去激活定时器的定时时长可以为载波特定或BWP特定的。相应的,去激活定时器的计数粒度和总计数值也可以为载波特定或BWP特定的。
本申请实施例中,去激活定时器的定时时长可以与载波中BWP的参数相关。示例性地,去激活定时器的计数粒度可以与载波中BWP的参数相关。例如计数粒度若为slot,slot的值可以为该载波上配置的所有BWP中slot值最大/最小的BWP对应的slot的值。
一种可能的实现方式中,第二BWP可以是默认BWP或初始BWP。
另一种可能的实现方式中,第二BWP也可以是非默认BWP和非初始BWP。
一种可能的实现方式中,在第二BWP为非默认BWP和非初始BWP的情况下,去激活单元1102在去激活所述第一BWP的基础上,还可不激活载波中的默认BWP或初始BWP。示例性地,在载波配置了默认BWP的情况下,去激活单元1102可以不激活默认BWP,在载波未配置默认BWP的情况下,去激活单元1102可以不激活初始BWP。
当然,对于第二BWP为默认BWP或初始BWP的情况下,去激活单元1102在去激活所述第一BWP的基础上,也可不激活载波中的默认BWP或初始BWP。
以上仅描述了当确定单元1101确定第一BWP所在的载波中包括处于激活态的第二BWP的处理过程,以下描述确定单元1101确定第一BWP所在的载波中不包括处于激活态的第二BWP的处理过程。
一种可能的实现方式中,所述带宽部分处理装置1100还可以包括激活单元1103,具体实现时去激活单元1102和激活单元1103可以集成为一个单元,也可以是独立的单元。在该种实现方式中,假设第一BWP所在的载波被配置了默认BWP,当激活的第一BWP对应的去激活定时器超时,确定单元1101确定第一BWP所在的载波中不包括处于激活态的第二BWP时,去激活单元1102去激活第一BWP,激活单元1103激活该载波中的默认 BWP。也可以理解为,去激活单元1102和激活单元1103执行BWP切换,从该载波上的第一BWP切换到默认BWP。
本申请实施例中,对载波中配置的默认BWP的数量不做限定,一个载波中可以配置一个默认BWP,当然也可以配置多于一个的默认BWP,载波中配置的多于一个的默认BWP可以称为默认BWP组。当一个载波中配置默认BWP组时,激活单元1103可采用如下方式激活该载波中的默认BWP。
第一种方式:激活单元1103可用于激活至少两个默认BWP中包括的全部BWP。在该种方式中,一个载波上的全部默认BWP可以处于相同状态,例如,同时处于激活态,或者同时处于非激活态。可选的,在该种方式中,网络设备可通过发送BWP切换命令对某些默认BWP去激活,使得一个载波上的全部默认BWP也可处于不同状态,即一部分默认BWP处于激活态,另一部分默认BWP处于非激活态。
第二种方式:激活单元1103可用于激活至少两个默认BWP中包括的满足预设规则的BWP。在该种方式中,一个载波上的全部默认BWP可以处于不同的状态,例如,默认BWP组内的一个BWP处于激活态,默认BWP组内的其它BWP处于非激活态,或者,默认BWP组内的一个BWP处于非激活态,默认BWP组内的其它BWP处于激活态。
其中,预设规则可包括以下任意一项:
BWP索引最大、BWP索引最小、SCS最大、SCS最小、CP最大、CP最小以及与当前去激活的第一BWP的参数相同。
示例性地,在上述第二种方式中,激活单元1103可激活至少两个默认BWP中包括的BWP索引最大/SCS最大/CP最大的一个BWP,也可激活至少两个默认BWP中包括的BWP索引最小/SCS最小/CP最小的一个BWP,还可激活与当前去激活的第一BWP的参数相同的一个BWP。
可选的,第一BWP的参数可包括SCS和/或CP。示例性地,激活与第一BWP的参数相同的一个BWP,可以理解为激活与第一BWP的SCS和/或CP相同的一个BWP。
需要说明的是,在上述第二种方式中,激活单元1103可以激活满足预设规则的一个或多个BWP。示例性地,若载波中默认BWP的数量为三,激活单元1103可激活三个默认BWP中与第一BWP的SCS和/或CP相同的两个BWP。
另一种可能的实现方式中,假设第一BWP所在的载波未被配置默认BWP。当激活的第一BWP对应的去激活定时器超时,确定单元1101确定第一BWP所在的载波中不包括处于激活态的第二BWP时,去激活单元1102去激活第一BWP,激活单元1103并激活该载波中的初始BWP。
以下针对以BWP组为单位配置默认BWP的场景进行说明。
一、以BWP组为单位配置默认BWP的场景一
在该种场景下,可将一个载波中包括的多个BWP配置为多个BWP组,使得一个载波中可包括至少两个BWP组,每个BWP组内包括至少一个BWP。其中,载波中的BWP组可通过信令配置。也可通过预定义规则预先配置。并配置每个BWP组内同一时刻处于激活态的BWP的数量为1或0。
此外,在该种场景下,对于每个BWP组内配置的默认BWP的数量不做限定。其中,每个BWP组内配置的默认BWP的数量可通过预定义规则或信令配置。
一种可能的实施方式中,每个BWP组内配置的默认BWP的数量为1或0。
需要说明的是,该场景下还可为第一BWP所在的载波配置初始BWP,该初始BWP可以归属于某个BWP组,也可以不归属于任何一个BWP组。
一种可能的实施方式中,初始BWP不归属于任何一个BWP组。确定单元1101还用于:
当激活的第一BWP对应的去激活定时器超时,且当第一BWP组不包括默认BWP时,在第二BWP组内确定是否包括处于激活态的第二BWP;
所述去激活单元1102还用于:
当第二BWP组内包括处于激活态的第二BWP时,去激活第一BWP;
所述激活单元1103还用于:
当第二BWP组内不包括处于激活态的第二BWP时,激活第一BWP所在载波上的初始BWP。
此外,若第一BWP组内包括默认BWP,则可执行BWP切换。具体的,去激活单元1102用于去激活第一BWP,激活单元1103用于激活该默认BWP。
一种可能的实施方式中,初始BWP归属于某个BWP组。确定单元1101还可用于:
当激活的第一BWP对应的去激活定时器超时,且当第一BWP组不包括默认BWP和初始BWP时,在第二BWP组内确定是否包括处于激活态的第二BWP;
所述去激活单元1102还可用于:
当第二BWP组内包括处于激活态的第二BWP时,去激活第一BWP;
所述激活单元1103还可用于:
当第二BWP组内不包括处于激活态的第二BWP时,激活第一BWP所在载波上的初始BWP。
此外,若第一BWP组内包括默认BWP,则执行BWP切换,具体的,去激活单元1102执行去激活第一BWP,激活单元1103执行激活该默认BWP。若第一BWP组内不包括默认BWP,但包括初始BWP,则执行BWP切换,具体的,去激活单元1102执行去激活第一BWP,激活单元1103执行激活该初始BWP。
其中第一BWP组为载波中配置的至少两个BWP组中包括第一BWP的BWP组,第二BWP组为载波中配置的至少两个BWP组中不包括第一BWP的BWP组。
该场景下,去激活定时器的定时时长,可以由总计数值和计数粒度(或者称之为计数单位)决定。去激活定时器的定时时长可以为载波特定或BWP特定的或BWP组特定的。相应的,去激活定时器的计数粒度和总计数值可以为载波特定或BWP特定的或BWP组特定的。
一种可能的实现方式中,去激活定时器的定时时长可以与载波中BWP的参数相关。示例性地,去激活定时器的计数粒度可以和BWP组内的某个BWP的参数相关。例如计数粒度若为slot,slot的值可以为该载波上配置的所有BWP中slot值最大/最小的BWP对应的slot的值。又例如,去激活定时器的计数粒度可以是该BWP组内BWP索引最大/BWP索引最小/SCS最大/SCS最小的BWP上一个符号(symbol)的长度。
二、以BWP组为单位配置默认BWP的场景二
在该种场景下,可将一个载波中包括的多个BWP配置为多个BWP组,使得一个载波中可包括至少两个BWP组,每个BWP组内包括至少一个BWP。其中,载波中的BWP组可通过信令配置。也可通过预定义规则预先配置。示例性地,预定义规则可包括同一个 BWP组内的BWP的参数相同,或者,同一个BWP组内的BWP配置同一个默认BWP。并配置该场景下一个BWP组内可以有多个同时处于激活态的BWP。
一种可能的实施方式中,确定单元1101还可用于:
当激活的第一带宽部分BWP对应的去激活定时器超时,在第一BWP组内确定是否包括处于激活态的第二BWP,所述第一BWP组为所述至少两个BWP组中包括所述第一BWP的BWP组;
所述去激活单元1102还可用于:
当载波中包括处于激活态的第二BWP时,去激活第一BWP。
其中第一BWP组为载波中配置的至少两个BWP组中包括第一BWP的BWP组,第二BWP组为载波中配置的至少两个BWP组中不包括第一BWP的BWP组。
该种场景下,去激活定时器的定时时长,可以由总计数值和计数粒度(或者称之为计数单位)决定。去激活定时器的定时时长可以为载波特定或BWP特定的或BWP组特定的。相应的,去激活定时器的计数粒度和总计数值可以为载波特定或BWP特定的或BWP组特定的。
一种可能的实现方式中,去激活定时器的定时时长可以与载波中BWP的参数相关。示例性地,去激活定时器的计数粒度可以与载波中BWP的参数相关。例如计数粒度若为slot,slot的值可以为该载波上配置的所有BWP中slot值最大/最小的BWP对应的slot的值。又例如,去激活定时器的计数粒度可以是该BWP组内BWP索引最大/BWP索引最小/SCS最大/SCS最小的BWP上一个符号(symbol)的长度。
上述以载波中非默认BWP被配置默认BWP的情况说明。在载波中某一非默认BWP未被配置默认BWP的情况下,若该非默认BWP对应的去激活定时器超时,确定单元1101可确定当前载波上是否包括其它激活的BWP,若当前载波上包括其它激活的BWP,则不执行BWP切换,可避免不必要的BWP切换流程。
本申请中对如何将多个BWP对应同一默认BWP不做限定。示例性地,可以通过协议预定义的方式,将同一参数(例如SCS和/或CP)对应的非默认BWP对应到同一个默认BWP。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分,实际实现时可以全部或部分集成到一个物理实体上,也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现;也可以全部以硬件的形式实现;还可以部分单元以软件通过处理元件调用的形式实现,部分单元以硬件的形式实现。例如,各个单元可以为单独设立的处理元件,也可以集成在装置的某一个芯片中实现,此外,也可以以程序的形式存储于存储器中,由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起,也可以独立实现。这里所述的处理元件又可以成为处理器,可以是一种具有信号的处理能力的集成电路。在实现过程中,上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中,以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路,例如:一个或多个特定集成电路(application specific integrated circuit,ASIC),或,一个或多个微处理器(digital singnal processor,DSP),或,一个或者多个现场可编程门阵列(field programmable gate array,FPGA),或这些集成电路形式中至少两种的组合。再如,当装置中的单元可以通过处理元件调度程序的形式实现时,该处理元件可以是通用 处理器,例如中央处理器(central processing unit,CPU)或其它可以调用程序的处理器。再如,这些单元可以集成在一起,以片上***(system-on-a-chip,SOC)的形式实现。
请参考图12,其为本申请实施例提供的一种终端的结构示意图。其可以为以上实施例中的终端,用于实现以上实施例中终端的操作。如图12所示,该终端包括:天线1201、射频部分1202、信号处理部分1203。天线1201与射频部分1202连接。在下行方向上,射频部分1202通过天线1201接收网络设备发送的信息,将网络设备发送的信息发送给信号处理部分1203进行处理。在上行方向上,信号处理部分1203对终端的信息进行处理,并发送给射频部分1202,射频部分1202对终端的信息进行处理后经过天线1201发送给网络设备。
信号处理部分1203可以包括调制解调子***,用于实现对数据各通信协议层的处理;还可以包括中央处理子***,用于实现对终端操作***以及应用层的处理;此外,还可以包括其它子***,例如多媒体子***,周边子***等,其中多媒体子***用于实现对终端相机,屏幕显示等的控制,周边子***用于实现与其它设备的连接。调制解调子***可以为单独设置的芯片。可选的,以上用于终端的装置可以位于该调制解调子***。
调制解调子***可以包括一个或多个处理元件12031,例如,包括一个主控CPU和其它集成电路。此外,该调制解调子***还可以包括存储元件12032和接口电路12033。存储元件12032用于存储数据和程序,但用于执行以上方法中终端所执行的方法的程序可能不存储于该存储元件12032中,而是存储于调制解调子***之外的存储器中,使用时调制解调子***加载使用。接口电路12033用于与其它子***通信。以上用于终端的装置可以位于调制解调子***,该调制解调子***可以通过芯片实现,该芯片包括至少一个处理元件和接口电路,其中处理元件用于执行以上终端执行的任一种方法的各个步骤,接口电路用于与其它装置通信。在一种实现中,终端实现以上方法中各个步骤的单元可以通过处理元件调度程序的形式实现,例如应用于终端的装置包括处理元件和存储元件,处理元件调用存储元件存储的程序,以执行以上方法实施例中终端执行的方法。存储元件可以为处理元件处于同一芯片上的存储元件,即片内存储元件。
在另一种实现中,用于执行以上方法中终端所执行的方法的程序可以在与处理元件处于不同芯片上的存储元件,即片外存储元件。此时,处理元件从片外存储元件调用或加载程序于片内存储元件上,以调用并执行以上方法实施例中终端执行的方法。
在又一种实现中,应用于终端的装置实现以上方法中各个步骤的单元可以是被配置成一个或多个处理元件,这些处理元件设置于调制解调子***上,这里的处理元件可以为集成电路,例如:一个或多个ASIC,或,一个或多个DSP,或,一个或者多个FPGA,或者这些类集成电路的组合。这些集成电路可以集成在一起,构成芯片。
终端实现以上方法中各个步骤的单元可以集成在一起,以片上***(system-on-a-chip,SOC)的形式实现,该SOC芯片,用于实现以上方法。该芯片内可以集成至少一个处理元件和存储元件,由处理元件调用存储元件的存储的程序的形式实现以上终端执行的方法;或者,该芯片内可以集成至少一个集成电路,用于实现以上终端执行的方法;或者,可以结合以上实现方式,部分单元的功能通过处理元件调用程序的形式实现,部分单元的功能通过集成电路的形式实现。
可见,以上应用于终端的装置可以包括至少一个处理元件和接口电路,其中至少一个处理元件用于执行以上方法实施例所提供的任一种终端执行的方法。处理元件可以以第一 种方式:即调用存储元件存储的程序的方式执行终端执行的部分或全部步骤;也可以以第二种方式:即通过处理器元件中的硬件的集成逻辑电路结合指令的方式执行终端执行的部分或全部步骤;当然,也可以结合第一种方式和第二种方式执行终端执行的部分或全部步骤。
这里的处理元件同以上描述,可以是通用处理器,例如CPU,还可以是被配置成实施以上方法的一个或多个集成电路,例如:一个或多个ASIC,或,一个或多个微处理器DSP,或,一个或者多个FPGA等,或这些集成电路形式中至少两种的组合。
存储元件可以是一个存储器,也可以是多个存储元件的统称。
根据本申请实施例提供的方法,本申请实施例还提供一种通信***,其包括前述的一个或多于一个终端,可选的,还可包括网络设备。
本申请实施例还提供一种带宽部分处理装置,应用于终端,包括用于执行以上方法实施例的至少一个处理元件(或芯片)。
本申请提供一种带宽部分处理的程序,该程序在被处理器执行时用于执行以上实施例的方法。
本申请还提供一种程序产品,例如计算机可读存储介质,包括上述涉及的带宽部分处理方法的程序。
本领域内的技术人员应明白,本申请实施例可提供为方法、***、或计算机程序产品。因此,本申请实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请实施例是参照根据本申请实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。
Claims (18)
- 一种带宽部分处理方法,其特征在于,包括:当激活的第一带宽部分BWP对应的去激活定时器超时,确定所述第一BWP所在的载波中是否包括处于激活态的第二BWP;当所述载波中包括处于激活态的所述第二BWP时,去激活所述第一BWP。
- 如权利要求1所述的方法,其特征在于,所述第二BWP为默认BWP或初始BWP。
- 如权利要求1所述的方法,其特征在于,所述第二BWP为非默认BWP和非初始BWP。
- 如权利要求3所述的方法,其特征在于,当所述载波中包括处于激活态的所述第二BWP时,所述方法还包括:不激活所述载波中的默认BWP或初始BWP。
- 如权利要求1至3任一项所述的方法,其特征在于,当所述载波中不包括处于激活态的所述第二BWP时,所述方法还包括:激活所述载波中的默认BWP或初始BWP。
- 如权利要求5所述的方法,其特征在于,当所述载波中的默认BWP的数量为至少两个时;所述激活所述载波中的默认BWP,包括:激活至少两个所述默认BWP中包括的全部BWP;或者,激活至少两个所述默认BWP中包括的满足预设规则的BWP。
- 如权利要求6所述的方法,其特征在于,所述预设规则包括:BWP索引最大;BWP索引最小;子载波间隔SCS最大;SCS最小;循环前缀CP最大;CP最小;或与所述第一BWP的参数相同。
- 如权利要求1所述的方法,其特征在于,所述载波包括至少两个BWP组,每个BWP组内包括至少一个BWP,每个BWP组内同一时刻处于激活态的BWP的数量为1或0;所述确定所述第一BWP所在的载波中是否包括处于激活态的第二BWP,包括:当第一BWP组不包括默认BWP时,在第二BWP组内确定是否包括处于激活态的第二BWP,所述第一BWP组为所述至少两个BWP组中包括所述第一BWP的BWP组,所述第二BWP组为所述至少两个BWP组中不包括所述第一BWP的BWP组;或者,当第一BWP组不包括默认BWP和初始BWP时,在第二BWP组内确定是否包括处于激活态的第二BWP,所述第一BWP组为所述至少两个BWP组中包括所述第一BWP的BWP组,所述第二BWP组为所述至少两个BWP组中不包括所述第一BWP的BWP组。
- 如权利要求1所述的方法,其特征在于,所述载波包括至少两个BWP组,每个所述BWP组内包括至少一个BWP;所述确定所述第一BWP所在的载波中是否包括处于激活态的第二BWP,包括:在第一BWP组内确定是否包括处于激活态的第二BWP,所述第一BWP组为所述至少两个BWP组中包括所述第一BWP的BWP组。
- 如权利要求8或9所述的方法,其特征在于,同一个所述BWP组内的BWP对应的去激活定时器的定时时长相同。
- 如权利要求8至10任一项所述的方法,其特征在于,所述BWP组通过预定义规则预先配置或者通过信令配置。
- 如权利要求11所述的方法,其特征在于,所述预定义规则包括同一个所述BWP组内的BWP的参数相同,和/或者,同一个所述BWP组内的BWP配置同一个默认BWP。
- 如权利要求1至9任一项所述的方法,其特征在于,所述去激活定时器的定时时长为载波特定或BWP特定的。
- 如权利要求1至13任一项所述的方法,其特征在于,所述去激活定时器的定时时长与所述载波中BWP的参数相关。
- 一种带宽部分处理装置,其特征在于,包括用于执行如权利要求1至14任一项所述方法的各个步骤的单元。
- 一种带宽部分处理装置,其特征在于,包括至少一个处理器和接口电路,所述至少一个处理器用于执行如权利要求1至14任一项所述的方法。
- 一种终端,其特征在于,包括权利要求15或16所述的用于带宽部分处理的装置。
- 一种存储介质,其特征在于,包括程序,该程序被处理器执行时用于执行如权利要求1至14任一项所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP19848219.2A EP3820072A4 (en) | 2018-08-09 | 2019-08-05 | METHOD AND DEVICE FOR PROCESSING A WIDE PART |
US17/171,677 US11936596B2 (en) | 2018-08-09 | 2021-02-09 | Bandwidth part processing method and apparatus |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810904442.7 | 2018-08-09 | ||
CN201810904442.7A CN110830200B (zh) | 2018-08-09 | 2018-08-09 | 一种带宽部分处理方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/171,677 Continuation US11936596B2 (en) | 2018-08-09 | 2021-02-09 | Bandwidth part processing method and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020029926A1 true WO2020029926A1 (zh) | 2020-02-13 |
Family
ID=69413414
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/099310 WO2020029926A1 (zh) | 2018-08-09 | 2019-08-05 | 一种带宽部分处理方法及装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US11936596B2 (zh) |
EP (1) | EP3820072A4 (zh) |
CN (1) | CN110830200B (zh) |
WO (1) | WO2020029926A1 (zh) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020034159A1 (zh) * | 2018-08-16 | 2020-02-20 | 北京小米移动软件有限公司 | 带宽部分调整方法和带宽部分调整装置 |
WO2021077277A1 (en) * | 2019-10-22 | 2021-04-29 | Qualcomm Incorporated | Secondary cell dormancy using dormancy profile |
US11855836B2 (en) * | 2020-01-31 | 2023-12-26 | Qualcomm Incorporated | Indicating user equipment capability for beam failure detection |
CN115314175A (zh) * | 2021-05-08 | 2022-11-08 | 维沃移动通信有限公司 | 带宽部分处理方法、装置及终端 |
CN115604751A (zh) * | 2021-07-08 | 2023-01-13 | 维沃移动通信有限公司(Cn) | 初始带宽部分确定方法、装置及相关设备 |
CN113993217A (zh) * | 2021-10-28 | 2022-01-28 | 北京长焜科技有限公司 | 一种bwp切换的方法 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018036560A1 (en) * | 2016-08-25 | 2018-03-01 | Huawei Technologies Co., Ltd. | System and method for multiplexing traffic |
WO2018063944A1 (en) * | 2016-09-30 | 2018-04-05 | Qualcomm Incorporated | Signaling and determination of slot and mini-slot structure |
Family Cites Families (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130114571A1 (en) * | 2011-11-07 | 2013-05-09 | Qualcomm Incorporated | Coordinated forward link blanking and power boosting for flexible bandwidth systems |
CN117134867A (zh) * | 2016-11-02 | 2023-11-28 | 交互数字专利控股公司 | 接收机带宽适配 |
KR102326369B1 (ko) * | 2017-03-16 | 2021-11-15 | 베이징 시아오미 모바일 소프트웨어 컴퍼니 리미티드 | 절삭된 버퍼 상태 보고 |
US10873911B2 (en) * | 2017-03-23 | 2020-12-22 | Ofinno, LCC | Uplink transmission power adjustment |
WO2019061080A1 (zh) * | 2017-09-27 | 2019-04-04 | Oppo广东移动通信有限公司 | 一种切换带宽部分的方法、终端设备及计算机存储介质 |
US11133912B2 (en) * | 2017-10-02 | 2021-09-28 | Qualcomm Incorporated | Bandwidth part activation, deactivation, and switching in wireless communications |
KR102546852B1 (ko) * | 2017-11-13 | 2023-06-22 | 닛본 덴끼 가부시끼가이샤 | 무선 단말 및 그 방법 |
CN109802781B (zh) * | 2017-11-16 | 2023-01-06 | 夏普株式会社 | 用于处理载波激活的方法及其设备 |
DE112017008206T5 (de) * | 2017-11-17 | 2020-08-13 | Apple Inc. | Vorübergehende Behandlung der Funktionen drahtloser Kommunikationsvorrichtungen |
CN109803354A (zh) * | 2017-11-17 | 2019-05-24 | 北京展讯高科通信技术有限公司 | 一种部分载波带宽bwp切换方法以及装置 |
KR102564966B1 (ko) * | 2017-12-27 | 2023-08-09 | 가부시키가이샤 엔티티 도코모 | 유저단말 및 무선 통신 방법 |
EP3506713B1 (en) * | 2017-12-28 | 2023-03-01 | ASUSTek Computer Inc. | Method and apparatus of selecting bandwidth part for random access (ra) procedure in a wireless communication system |
WO2019127405A1 (zh) * | 2017-12-29 | 2019-07-04 | Oppo广东移动通信有限公司 | 下行带宽部分激活及去激活的方法、终端设备及网络设备 |
US11800525B2 (en) * | 2018-01-11 | 2023-10-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and devices for control of bandwidth part switching |
JP2019140452A (ja) * | 2018-02-07 | 2019-08-22 | シャープ株式会社 | 通信システムおよび通信装置 |
KR20200110359A (ko) * | 2018-02-12 | 2020-09-23 | 삼성전자주식회사 | 상향링크 정보를 전송하는 방법 및 장치 |
EP3528561A1 (en) * | 2018-02-15 | 2019-08-21 | Panasonic Intellectual Property Corporation of America | User equipment and base station involved in improved paging procedures |
WO2019159297A1 (ja) * | 2018-02-15 | 2019-08-22 | 株式会社Nttドコモ | ユーザ端末及び無線通信方法 |
US10834749B2 (en) * | 2018-02-19 | 2020-11-10 | Electronics And Telecommunications Research Institute | Method for bandwidth part management in communication system and apparatus for the same |
KR102638627B1 (ko) * | 2018-02-23 | 2024-02-21 | 삼성전자 주식회사 | 무선 통신 시스템에서 불연속 수신 수행 시 설정된 상향링크 데이터의 재전송을 수행하는 방법 및 장치 |
CN110198568B (zh) * | 2018-02-24 | 2021-03-09 | 维沃移动通信有限公司 | 带宽变换的方法和用户设备 |
CN110324890B (zh) * | 2018-03-30 | 2022-05-17 | 维沃移动通信有限公司 | 部分带宽激活定时器的控制方法及终端 |
US10917892B2 (en) * | 2018-04-04 | 2021-02-09 | Lg Electronics Inc. | Method for performing bandwidth part switching by a user equipment |
KR102477564B1 (ko) * | 2018-04-05 | 2022-12-14 | 주식회사 아이티엘 | 무선 통신 시스템에서 빔 실패 복구 동작 방법 및 장치 |
CN112385187A (zh) * | 2018-05-14 | 2021-02-19 | 诺基亚技术有限公司 | 用于新无线电带宽部分操作的方法、***和装置 |
KR102544861B1 (ko) * | 2018-05-24 | 2023-06-19 | 삼성전자 주식회사 | 무선 통신 시스템에서 단말의 전력 소모 감소 방법 및 장치 |
CN110621044B (zh) * | 2018-06-20 | 2021-06-11 | 维沃移动通信有限公司 | 调整带宽的方法、移动终端、网络侧设备和介质 |
CN110691415B (zh) * | 2018-07-06 | 2022-11-01 | 大唐移动通信设备有限公司 | 一种随机接入方法及终端 |
CN112438033A (zh) * | 2018-07-26 | 2021-03-02 | 索尼公司 | 通信设备、基础设施设备以及方法 |
WO2020027601A1 (ko) * | 2018-08-01 | 2020-02-06 | 엘지전자 주식회사 | 무선 통신 시스템에서 채널 상태 정보를 송수신하는 방법 및 이를 위한 장치 |
JP2020025183A (ja) * | 2018-08-07 | 2020-02-13 | シャープ株式会社 | 端末装置および基地局装置 |
WO2020032705A1 (ko) * | 2018-08-09 | 2020-02-13 | 엘지전자 주식회사 | 무선 통신 시스템에서 신호를 송수신 하는 방법 및 이를 지원하는 장치 |
-
2018
- 2018-08-09 CN CN201810904442.7A patent/CN110830200B/zh active Active
-
2019
- 2019-08-05 EP EP19848219.2A patent/EP3820072A4/en active Pending
- 2019-08-05 WO PCT/CN2019/099310 patent/WO2020029926A1/zh unknown
-
2021
- 2021-02-09 US US17/171,677 patent/US11936596B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018036560A1 (en) * | 2016-08-25 | 2018-03-01 | Huawei Technologies Co., Ltd. | System and method for multiplexing traffic |
WO2018063944A1 (en) * | 2016-09-30 | 2018-04-05 | Qualcomm Incorporated | Signaling and determination of slot and mini-slot structure |
Non-Patent Citations (4)
Title |
---|
"Remaing Issues on Bandwidth Parts for NR", 3GPP TSG RAN WGI MEETING #90 RI-1713964, 11 August 2017 (2017-08-11), XP051316756 * |
"Remaining Details of BWP", 3GPP TSG RAN WGI MEETING #90 R1-1714117, 11 August 2017 (2017-08-11), XP051316756 * |
HUAWEI ET AL.: "Discussion on Initial Active BWP ID [H031", 3GPP TSG-RAN WG2 MEETING #AH-1801 R2-1801484, 17 January 2018 (2018-01-17), XP051386971 * |
See also references of EP3820072A4 |
Also Published As
Publication number | Publication date |
---|---|
US20210167934A1 (en) | 2021-06-03 |
EP3820072A1 (en) | 2021-05-12 |
EP3820072A4 (en) | 2021-10-20 |
CN110830200A (zh) | 2020-02-21 |
CN110830200B (zh) | 2021-09-07 |
US11936596B2 (en) | 2024-03-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020029926A1 (zh) | 一种带宽部分处理方法及装置 | |
US11398885B2 (en) | Signal transmission method and apparatus | |
CN109246826A (zh) | Drx配置方法、终端设备、网络设备和通信*** | |
WO2018210254A1 (zh) | 频域资源的处理方法、装置及*** | |
US20150029913A1 (en) | Signal transmission method and apparatus | |
WO2019128680A1 (zh) | 一种确定bwp状态的方法、设备及*** | |
JP2023123707A (ja) | 次世代無線ネットワークにおけるパケットデータ収束プロトコルの複製 | |
TWI449451B (zh) | 載波管理方法及通訊裝置 | |
WO2021227755A1 (zh) | 一种切换方法及装置 | |
WO2012163023A1 (zh) | 分配多载波资源的方法、基站、和终端 | |
WO2020052536A1 (zh) | 一种通信方法及装置 | |
WO2020029850A1 (zh) | 一种通信方法和装置 | |
WO2020143490A1 (zh) | 通信方法及装置 | |
US20230053143A1 (en) | Communication method, apparatus, and system | |
WO2020216132A1 (zh) | 传输信息的方法和装置 | |
WO2021163979A1 (zh) | 通信方法、设备及*** | |
WO2020063016A1 (zh) | 一种数据传输、bwp切换方法及设备 | |
EP2859763B1 (en) | Enhanced power saving optimized configuration handling | |
WO2019062746A1 (zh) | 通信方法、装置和*** | |
WO2021027551A1 (zh) | 一种通信方法及装置 | |
JP2024073481A (ja) | 通信方法及び装置 | |
WO2023109879A1 (zh) | 射频链路切换方法和通信装置 | |
WO2019223558A1 (zh) | 一种通信方法、装置及*** | |
WO2022253049A1 (zh) | 一种下行调度方法及装置 | |
WO2021208819A1 (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: 19848219 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019848219 Country of ref document: EP Effective date: 20210208 |