Bandwidth part BWP processing method, device and storage medium

Abstract

Embodiments of the present application provide a method, device, and storage medium for processing bandwidth parts (BWPs). The method includes: a terminal device receiving first configuration information sent by a network device, determining the DRX status corresponding to different service types based on the first configuration information, and then determining whether to maintain or change the BWP corresponding to the current service type based on the DRX status corresponding to the different service types. This processing solves the problem of switching between BWPs for different service types, ensuring that data from different service types can be effectively received.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a method, device, and storage medium for processing a bandwidth part (BWP). Background Art

[0002] In 5G New Radio (NR) systems, the system bandwidth, or the bandwidth of a single carrier, can be 400 MHz. This is significantly larger than the 20 MHz maximum bandwidth of the Long Term Evolution (LTE) system. If a terminal remains on a wideband carrier, power consumption is significant. Therefore, a bandwidth part (BWP) is introduced. This is a portion of the system bandwidth, such as 10 MHz or 100 MHz, over which the terminal can communicate with network equipment.

[0003] The network equipment of the NR system can adjust the BWP according to the actual throughput of the terminal. For example, when the terminal rate is very low, a smaller bandwidth can be configured for the terminal, such as Figure 1 BWP1 shown in (a); When the terminal rate requirement is high, a larger bandwidth can be configured for the terminal, such as Figure 1 BWP2 shown in (b); The terminal supports high rate or operates in carrier aggregation (CA) mode, and multiple BWPs can be configured for the terminal, such as Figure 1 Currently, NR system terminals do not support working on two BWPs at the same time, that is, even if the network equipment configures multiple BWPs for the terminal, it can only work on one of the multiple BWPs at the same time. Summary of the Invention

[0004] The embodiments of the present application provide a method, device, and storage medium for processing a bandwidth part (BWP) to ensure that data of different service types can be effectively received.

[0005] In a first aspect, an embodiment of the present application provides a method for processing a bandwidth part (BWP), including:

[0006] The terminal device receives first configuration information sent by the network device, where the first configuration information is used to indicate a first discontinuous reception (DRX) configuration parameter and a second DRX configuration parameter;

[0007] The terminal device maintains or changes the current BWP according to the first configuration information.

[0008] In a second aspect, an embodiment of the present application provides a method for processing a bandwidth part BWP, including:

[0009] When determining to switch from the first BWP to the second BWP, the terminal device adjusts the first DRX state and / or the second DRX state;

[0010] The first DRX state corresponds to a first BWP, and the second DRX state corresponds to a second BWP.

[0011] In a third aspect, an embodiment of the present application provides a method for processing a bandwidth portion BWP, including:

[0012] The network device sends first configuration information to the terminal device, where the first configuration information is used to indicate a first discontinuous reception DRX configuration parameter and a second DRX configuration parameter, so that the terminal device maintains or changes a current BWP according to the first configuration information.

[0013] In a fourth aspect, an embodiment of the present application provides a terminal device, including:

[0014] a receiving module, configured to receive first configuration information sent by a network device, where the first configuration information is used to indicate a first discontinuous reception (DRX) configuration parameter and a second DRX configuration parameter;

[0015] A processing module is configured to maintain or change a current BWP according to the first configuration information.

[0016] In a fifth aspect, an embodiment of the present application provides a terminal device, including:

[0017] a processing module, configured to adjust the first DRX state and / or the second DRX state when determining to switch from the first BWP to the second BWP;

[0018] The first DRX state corresponds to a first BWP, and the second DRX state corresponds to a second BWP.

[0019] In a sixth aspect, an embodiment of the present application provides a network device, including:

[0020] The sending module is used to send first configuration information to the terminal device, where the first configuration information is used to indicate a first discontinuous reception DRX configuration parameter and a second DRX configuration parameter, so that the terminal device maintains or changes the current BWP according to the first configuration information.

[0021] In a seventh aspect, an embodiment of the present application provides a terminal device, including:

[0022] transceivers, processors, and memory;

[0023] The memory stores computer-executable instructions;

[0024] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method as described in any one of the first aspects.

[0025] In one embodiment, the processor may be a chip.

[0026] In an eighth aspect, an embodiment of the present application provides a terminal device, including:

[0027] transceivers, processors, and memory;

[0028] The memory stores computer-executable instructions;

[0029] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method as described in any one of the second aspects.

[0030] In one embodiment, the processor may be a chip.

[0031] In a ninth aspect, an embodiment of the present application provides a network device, including:

[0032] transceivers, processors, and memory;

[0033] The memory stores computer-executable instructions;

[0034] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method as described in any one of the third aspects.

[0035] In one embodiment, the processor may be a chip.

[0036] In a tenth aspect, an embodiment of the present application may provide a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of the first aspects.

[0037] In the eleventh aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of the second aspects.

[0038] In the twelfth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of the third aspects.

[0039] In the thirteenth aspect, an embodiment of the present application provides a communication system, including: a terminal device and a network device; the terminal device is the terminal device described in the fourth or fifth aspect above, and the network device is the network device described in the sixth aspect above.

[0040] Embodiments of the present application provide a method, device, and storage medium for processing bandwidth parts (BWPs). The method includes: a terminal device receiving first configuration information sent by a network device, determining the DRX status corresponding to different service types based on the first configuration information, and then determining whether to maintain or change the BWP corresponding to the current service type based on the DRX status corresponding to the different service types. This processing solves the problem of switching between BWPs for different service types, ensuring that data from different service types can be effectively received. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of a network device configured with a BWP for a terminal device according to an embodiment of the present application;

[0042] Figure 2 A schematic diagram of a discontinuous reception (DRX) mechanism cycle provided in an embodiment of the present application;

[0043] Figure 3 A schematic diagram of the structure of a communication system provided in an embodiment of the present application;

[0044] Figure 4 A flowchart of a method for processing a bandwidth portion BWP provided in an embodiment of the present application;

[0045] Figure 5 A schematic diagram of the BWP corresponding to the two service types provided in the embodiment of the present application in the system bandwidth;

[0046] Figure 6 A flowchart of a method for processing a broadband part BWP provided in an embodiment of the present application;

[0047] Figure 7 A flowchart of a method for processing a bandwidth portion BWP provided in an embodiment of the present application;

[0048] Figure 8 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

[0049] Figure 9 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

[0050] Figure 10 A schematic diagram of the structure of a network device provided in an embodiment of the present application;

[0051] Figure 11A schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present application;

[0052] Figure 12 A schematic diagram of the hardware structure of a network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0054] The terms "first", "second", etc. in the specification, claims, and above-mentioned drawings of the embodiments of the present application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0055] In the LTE system, Multimedia Broadcast Multicast Service (MBMS) was introduced in 3GPP Release 6. MBMS is a technology that transmits data from a single data source to multiple user devices using shared network resources. While providing multimedia services, it effectively utilizes network resources and enables high-speed multimedia broadcast and multicast (256 kbp / s). Because the spectrum efficiency of MBMS in 3GPP Release 6 was low, insufficient to effectively carry and support mobile TV-type services, 3GPP explicitly proposed enhancing support for downlink high-speed MBMS services in the LTE project and defined design requirements for the physical layer and air interface. Release 9 introduced Evolved MBMS (E-MBMS). E-MBMS uses a Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) to transmit MBMS service data. This means that data is transmitted simultaneously across all cells using a unified frequency, while ensuring inter-cell synchronization. This approach significantly improves the overall signal-to-noise ratio distribution across the cell, and also increases spectrum efficiency.

[0056] However, typically, MBMS users are located in only a few cells within the MBSFN area. Sending MBMS services in cells without users wastes air interface resources. To address the MBSFN issue, the LTE system introduces the Single Cell Point to Multipoint (SC-PTM) method for MBMS service data transmission. This method selects only the cells where MBMS users are located to transmit data, saving air interface resources in other cells without users. The Multi-cell / multicast Coordination Entity (MCE) in the MBMS network architecture determines whether to use the SC-PTM or MBSFN transmission method.

[0057] For SC-PTM, new logical channels are introduced: Single Cell Multicast Control Channel (SC-MCCH) and Single Cell Multicast Transport Channel (SC-MTCH), which are mapped to the Downlink Shared Channel (DL-SCH) transport channel and the Physical Downlink Shared Channel (PDSCH). SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation and use Un-acknowledged Mode (UM) Radio Link Control (RLC). A new System Information Broadcast (SIB) type (SIB20) and a new Radio Network Temporary Identity (RNTI) (SC-N-RNTI) are also introduced. Among them, SIB20 is used to transmit the configuration information of SC-MCCH. There is only one SC-MCCH in a cell. The configuration information of SC-MCCH includes: the modification period, repetition period, and radio frame and subframe configuration information of SC-MCCH. SC-N-RNTI (fixed value FFFB) (Single Cell Notification RNTI) is used to identify the physical downlink control channel (Physical Downlink Control Channel, PDCCH) of the SC-MCCH change notification. One of the 8 bits in DCI 1C can be used to indicate the change notification. The modification period boundary is defined as SFN mod m = 0, where m is the modification period (sc-mcch-Modification Period) configured in SIB20.

[0058] The Discontinuous Reception (DRX) mechanism is a method proposed in LTE to reduce the energy consumption of terminal devices. The basic idea of DRX is to allow the terminal device to shut down some of its radio transceiver units and enter sleep mode when there is no data transmission, thereby reducing energy consumption.

[0059] In the LTE system, for the discontinuous reception mechanisms of unicast and multicast, terminal devices can run the DRX mechanisms for unicast and multicast respectively on the same carrier. For example, the terminal device determines whether to receive the control channel for unicast according to the unicast DRX mechanism, and the terminal device determines whether to receive the control channel for multicast according to the multicast DRX mechanism.

[0060] The following briefly introduces the unicast DRX mechanism.

[0061] DRX can be divided into DRX in idle state (Idle DRX) and DRX in connected state (Connected DRX, CDRX). In Idle DRX mode, the terminal device has no wireless resource connection and mainly monitors the call channel and broadcast channel. In order to achieve discontinuous reception, it is only necessary to configure a fixed sleep cycle. The DRX cycle in Idle-DRX mode is divided into active period and sleep period. In Connected-DRX mode, the terminal device has three states, namely active period, short DRX cycle (light sleep period) and long DRX cycle (deep sleep period), such as Figure 3 During the active period, the UE is in a power consumption mode; during the light sleep period and deep sleep period, the UE is in a power saving mode.

[0062] For Connected-DRX mode: During the active phase, the deactivation timer ti starts, and the terminal device turns on its receiver to detect the PDCCH and receive data packets from the network. Before the ti timer expires, the PDCCH indicates a downlink data transmission, and ti is restarted, re-entering the active phase. Otherwise, the terminal device enters the light sleep phase. In the short DRX cycle, the DRX short cycle timer ts specifies the number of short DRX cycles. A short DRX cycle tds consists of an on-duration Ton and a sleep period. Ton is the time the terminal device monitors the PDCCH, waiting for / receiving uplink and downlink data transmissions from the base station. During the sleep phase, the terminal device turns off its transceiver and does not monitor the PDCCH. When the PDCCH indicates a downlink data transmission, the terminal device enters the active phase from the short DRX cycle. Otherwise, the terminal device remains in the short DRX cycle until the ts timer expires, entering the deep sleep phase. In the long sleep cycle, tdl is the deep sleep period, which consists of the on-duration Ton and the sleep period. The Ton of the long sleep cycle can be the same as the short DRX cycle, but the sleep period is different. If the PDCCH indicates a downlink transmission, the terminal device transitions from a long sleep cycle to an active state. Otherwise, the terminal device remains in a long sleep cycle. During the short and long DRX cycles, the network does not transmit any data packets to the terminal device. Radio Resource Control (RRC) coordinates the operation of these parameters to enable the terminal device to switch between these three states, achieving the energy-saving benefits of the DRX mechanism.

[0063] In an embodiment of the present application, the DRX timer for unicast includes at least one of the following: drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.

[0064] The DRX mechanism for multicast is similar to the DRX mechanism for unicast, and details can be found above.

[0065] In the embodiment of the present application, the DRX timer for multicast includes at least one of the following: onDurationTimerSCPTM, drx-InactivityTimerSCPTM.

[0066] Accordingly, the DRX configuration for multicast includes:

[0067] 1) When [(SFN*10)+subframenumber]modulo(SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset, start the timer onDurationTimerSCPTM; 2) When the terminal device receives the physical downlink control channel PDCCH scheduling, start the timer drx-Inactivity TimerSCPTM; 3) Only when the above-mentioned timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running, the downlink SC-PTM service (multicast service) is received.

[0068] Currently, the 5G New Radio (NR) system does not support multimedia broadcast and multicast services. However, with the continuous increase in mobile terminal user data, the demand for video services has increased, and with the rapid development of digital TV technology and network communication technology, wireless broadcast and multicast services have become one of the hot topics in the field of wireless applications. As an important implementation method for mobile TV, multimedia broadcast and multicast service technology will play an important role in the NR system and has great development prospects.

[0069] Since the NR system introduces a bandwidth part (BWP), different BWPs can be configured for unicast and multicast. BWP refers to a portion of the system bandwidth, which can be the carrier bandwidth. This bandwidth part is also called the carrier bandwidth part, operating bandwidth, or transmission bandwidth. The embodiments of the present application do not impose any restrictions on the name and abbreviation of the bandwidth part.

[0070] In the related art, a terminal device can only operate on one BWP during the same time period. Even if the network configures multiple BWPs for the terminal device, it can only operate on one of the multiple BWPs during the same time period. If the network configures a BWP dedicated to unicast and a BWP dedicated to MBMS for the terminal device, how to implement the switching between the BWP dedicated to unicast and the BWP dedicated to MBMS is a technical problem that needs to be solved urgently. In addition, different BWPs run different DRX mechanisms. The terminal device can run the unicast DRX mechanism on the unicast-dedicated BWP and the multicast DRX mechanism on the MBMS-dedicated BWP. How to implement the interoperability of the DRX mechanism for unicast and the DRX mechanism for MBMS is another technical problem that needs to be solved urgently.

[0071] In order to solve the above technical problems, an embodiment of the present application provides a method for processing BWP. The terminal device obtains the DRX configuration parameters corresponding to different service types, determines the DRX status corresponding to different service types, and then determines whether to switch the current BWP based on the DRX status. Different service types have different BWPs. When determining to switch the current BWP, the DRX timer corresponding to the different service types is adjusted accordingly to achieve interoperability of the DRX mechanisms corresponding to different service types. The above processing process can realize the effective transmission of service data of different service types, while minimizing the energy loss of the terminal device.

[0072] The following first briefly introduces a schematic diagram of the architecture of a communication system applicable to an embodiment of the present application.

[0073] Figure 3 This is a schematic diagram of the structure of a communication system provided in an embodiment of the present application. Figure 3 As shown, the communication system may include a network device 110 and a plurality of terminal devices 120 located within the coverage area of the network device 110 . Figure 3 One network device 110 and two terminal devices 120 are shown as an example.

[0074] In one embodiment, the communication system may include multiple network devices 110, and each network device may include another number of terminal devices 120 within its coverage area. The embodiment of the present application does not limit the number of network devices 110 and terminal devices 120 included in the communication system.

[0075] like Figure 3 As shown, the terminal device 120 is connected to the network device 110 in a wireless manner. For example, the network device 110 and the plurality of terminal devices 120 may perform wireless communication using unlicensed spectrum.

[0076] In one embodiment, the terminal devices 120 may perform device-to-device (D2D) communication with each other.

[0077] It is understandable that Figure 3 This is just a schematic diagram. The communication system may also include other network devices, such as core network devices, wireless relay devices and wireless backhaul devices, or may include other network entities such as network controllers and mobile management entities. The embodiments of the present application are not limited to this.

[0078] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, advanced long term evolution (LTE-A) system, new radio (NR) system, NR system evolution system, LTE on unlicensed band (LTE-based access to unlicensed spectrum, LTE-U) system, NR on unlicensed band (NR-based access to unlicensed spectrum, NR-U) system, universal mobile telecommunication system (UMTS), world wide interoperability for microwave access (WMI), etc. access, WiMAX) communication system, wireless local area networks (WLAN), wireless fidelity (WiFi), next generation communication system or other communication systems, etc.

[0079] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and vehicle-to-vehicle (V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0080] The system architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0081] The network devices involved in the embodiments of the present application may be ordinary base stations (such as NodeB or eNB or gNB), new radio controllers (new radio controller, NR controller), centralized network elements (centralized unit), new wireless base stations, radio frequency remote modules, micro base stations, relays, distributed network elements (distributed unit), transmission reception points (TRP), transmission points (TP) or any other devices. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network devices. For the convenience of description, in all embodiments of the present application, the above-mentioned devices that provide wireless communication functions for terminal devices are collectively referred to as network devices.

[0082] In the embodiments of the present application, the terminal device can be any terminal, for example, the terminal device can be a user equipment for machine type communication. That is, the terminal device can also be referred to as user equipment (UE), mobile station (MS), mobile terminal (mobile terminal), terminal, etc. The terminal device can communicate with one or more core networks via a radio access network (RAN). For example, the terminal device can be a mobile phone (or called a "cellular" phone), a computer with a mobile terminal, etc. For example, the terminal device can also be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device, which exchanges language and / or data with the radio access network. This is not specifically limited in the embodiments of the present application.

[0083] In one embodiment, the network device and terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; and can also be deployed in the air on aircraft, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the network device and terminal device.

[0084] In one embodiment, network devices and terminal devices, as well as terminal devices and terminal devices, may communicate through a licensed spectrum, or may communicate through an unlicensed spectrum, or may communicate through both a licensed spectrum and an unlicensed spectrum. Network devices and terminal devices, as well as terminal devices and terminal devices, may communicate through a spectrum below 7 gigahertz (GHz), or may communicate through a spectrum above 7 GHz, or may communicate through a spectrum below 7 GHz and a spectrum above 7 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used between network devices and terminal devices.

[0085] Based on the above communication system, the technical solutions provided by the embodiments of the present application are described in detail below through specific embodiments. It should be noted that the technical solutions provided by the embodiments of the present application may include part or all of the following contents, and the following specific embodiments may be combined with each other. For the same or similar concepts or processes, some embodiments may not be repeated.

[0086] Figure 4 This is a flow chart of a method for processing a bandwidth portion BWP provided in an embodiment of the present application. Figure 4 As shown, the method may include the following steps:

[0087] Step 201: The network device sends first configuration information to the terminal device, where the first configuration information is used to indicate a first DRX configuration parameter and a second DRX configuration parameter.

[0088] In the embodiment of the present application, the communication system supports multiple service types, such as unicast service and MBMS service. In one embodiment, MBMS service can be subdivided into broadcast service and multicast service (or multicast service). Different service types generally correspond to different DRX configuration parameters.

[0089] As an example, the first configuration information may be used to indicate DRX configuration parameters corresponding to unicast services and DRX configuration parameters corresponding to MBMS services. As another example, the first configuration information may be used to indicate DRX configuration parameters corresponding to unicast services and DRX configuration parameters corresponding to multicast services.

[0090] In one embodiment, the first DRX configuration parameter in the embodiment of the present application is for unicast services, and the second DRX configuration parameter is for multicast services; or, the first DRX configuration parameter is for multicast services, and the second DRX configuration parameter is for unicast services.

[0091] In an embodiment of the present application, DRX configuration parameters include the lengths (durations) of various timers and the lengths of various cycles. As an example, the DRX configuration parameters for unicast services may include the lengths of various unicast DRX timers (e.g., drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer, drx-ShortCycleTimer, drx-HARQ-RTT-Timer), short DRX cycles, long DRX cycles, sleep cycles, etc. As another example, the DRX configuration parameters for multicast services may include the lengths of various multicast DRX timers (e.g., onDurationTimerSCPTM, drx-InactivityTimerSCPTM), short DRX cycles, long DRX cycles, sleep cycles, etc.

[0092] The terminal device can determine whether the DRX of the service type is in an activated or deactivated state based on the DRX configuration parameters corresponding to different service types. If the DRX of the service type is in an activated state, the terminal device can monitor the PDCCH on the BWP corresponding to the service type and wait for or receive the uplink and downlink data of the service type. It should be noted that in the NR system, the terminal device cannot work on multiple BWPs at the same time. Therefore, the terminal device can only monitor the PDCCH on the BWP corresponding to a certain service type in the same period of time and wait for or receive the uplink and downlink data of this service type.

[0093] In order to ensure effective transmission of uplink and downlink data of different service types, step 202 may be used to maintain or change the current BWP.

[0094] Step 202: The terminal device maintains or changes the current BWP according to the first configuration information.

[0095] As can be seen from step 201, the first configuration information is used to indicate a first DRX configuration parameter and a second DRX configuration parameter, and different DRX configuration parameters correspond to different service types. Specifically, the terminal device determines a first DRX state based on the first DRX configuration parameter; the terminal device determines a second DRX state based on the second DRX configuration parameter; and the terminal device determines whether to maintain or change the current BWP based on at least one of the first DRX state and the second DRX state.

[0096] It should be understood that the first DRX state and the second DRX state determined by the terminal device correspond to different service types. If the first DRX configuration parameter corresponds to a first service type, such as a multicast service, the first DRX state determined by the terminal device is the DRX state for the first service type (such as a multicast service); if the second DRX configuration parameter corresponds to a second service type, such as a unicast service, the second DRX state determined by the terminal device is the DRX state for the second service type (such as a unicast service).

[0097] The first DRX state and the second DRX state each include the following two states: an activated state and a deactivated state. The activated state of the first DRX state means that downlink transmission of data of the first service type is detected on the BWP corresponding to the first service type, and the activated state of the second DRX state means that downlink transmission of data of the second service type is detected on the BWP corresponding to the second service type.

[0098] In the embodiment of the present application, the terminal device determines whether to maintain or change the current BWP according to at least one of the first DRX state and the second DRX state, including the following two possible implementation methods:

[0099] In a first possible implementation manner, the current BWP is the first BWP corresponding to the first service type, that is, the terminal device currently operates on the first BWP and detects downlink transmission of the first service type on the PDCCH of the first BWP.

[0100] Specifically, the terminal device determines to maintain or change the current BWP according to at least one of the first DRX state and the second DRX state, including at least one of the following situations:

[0101] In the first case, the terminal device determines whether to maintain or change the first BWP based on the first DRX state. Specifically, if the first DRX state is a deactivated state, it is determined to change the first BWP. Alternatively, if the first DRX state is an activated state, it is determined to maintain the first BWP. It should be noted that changing the first BWP includes: switching from the current first BWP to the second BWP, or expanding the current first BWP to cover both the first BWP and the second BWP. The second BWP is the BWP corresponding to the second service type. This solution only considers the first DRX state corresponding to the first service type corresponding to the current BWP. If the first DRX state is a deactivated state, the first BWP is changed. If the first DRX state is an activated state, in order to ensure the normal reception of the first service type data, the current first BWP is maintained.

[0102] In the second case, the terminal device determines whether to maintain or change the first BWP based on the second DRX state. Specifically, if the second DRX state is in the activated state, it is determined to change the first BWP. Alternatively, if the second DRX state is in the deactivated state, it is determined to maintain the first BWP. This solution only considers the second DRX state corresponding to the second service type. If the second DRX state is in the activated state, the first BWP is changed regardless of whether the first DRX state corresponding to the first service type corresponding to the current first BWP is in the activated state or the deactivated state. It can be seen that this solution implies that the processing priority of the second service type is greater than that of the first service type. If the second DRX state is in the deactivated state, the current first BWP is maintained to avoid unnecessary change operations and reduce the energy consumption of the terminal device.

[0103] In the third case, the terminal device determines to maintain or change the first BWP according to the first DRX state and the second DRX state.

[0104] Table 1

[0105]

[0106] As shown in Table 1, if both the first and second DRX states are activated, the terminal device can determine whether to maintain or change the current BWP based on the priority order of processing different service types. If both the first and second DRX states are deactivated, the current BWP is maintained to avoid unnecessary changes and reduce energy consumption of the terminal device.

[0107] In a second possible implementation, the current BWP is a second BWP corresponding to the second service type, i.e., the terminal device is currently operating on the second BWP and detects downlink transmission of the second service type on the PDCCH of the second BWP. The implementation principle of the terminal device determining whether to maintain or change the current BWP based on at least one of the first DRX state and the second DRX state is similar to that of the first implementation, and details are described above and are not repeated here.

[0108] In the technical solution provided by the embodiments of the present application, a terminal device receives first configuration information sent by a network device, determines the DRX status corresponding to different service types based on the first configuration information, and then determines whether to maintain or change the BWP corresponding to the current service type based on the DRX status corresponding to the different service types. This process solves the problem of switching between BWPs for different service types and ensures that data from different service types can be effectively received.

[0109] Based on the above solution, there is a special case where both the first DRX state and the second DRX state are activated. In this case, the terminal device can determine whether to maintain or change the current BWP based on the priority order of processing different service types.

[0110] Regarding the priority order for processing different types of services, the terminal device can obtain the priority order for processing different types of services based on user-defined settings (for example, the user can input and select a service to be processed first). The terminal device manufacturer can also pre-set the priority order for processing different types of services in the terminal device before the terminal device leaves the factory. The terminal device can also obtain the priority order for processing different types of services through the network device. The embodiments of the present application do not impose any restrictions on how the terminal device obtains the priority order for processing different types of services.

[0111] In summary, in some embodiments, before step 202, the following steps may also be included:

[0112] The terminal device obtains second configuration information, where the second configuration information is used to indicate the priority order of different service types of the terminal device.

[0113] Accordingly, step 202 specifically includes:

[0114] The terminal device maintains or changes the current BWP according to the first configuration information and the second configuration information.

[0115] Specifically, the terminal device determines the first DRX state based on the first DRX configuration parameter in the first configuration information; the terminal device determines the second DRX state based on the second DRX configuration parameter in the first configuration information; the terminal device maintains or changes the current BWP based on at least one of the first DRX state, the second DRX state and the priority order of processing different service types.

[0116] In one embodiment, the terminal device obtains the second configuration information, including: the terminal device obtains the second configuration information from the network device. It should be noted that the terminal device obtains the priority order of processing different service types through the network device, which can include the following two implementation methods:

[0117] In one implementation, the network device sends second configuration information to the terminal device, where the second configuration information is used to indicate the priority order of the terminal device in processing different service types. In another implementation, the terminal device sends a request message to the network device, and the network device sends the second configuration information to the terminal device based on the received request message.

[0118] In one embodiment, the terminal device obtaining the second configuration information includes: the terminal device obtaining pre-configured second configuration information. The pre-configured second configuration information is user-defined configuration information for the priority order of the terminal device for processing different service types, or factory-preset configuration information for the priority order of the terminal device for processing different service types.

[0119] In some embodiments, after the terminal device obtains the pre-configured second configuration information, the terminal device further includes: sending the second configuration information to the network device. In this way, the network side learns the priority order of processing different service types preset by different terminal devices, thereby achieving information synchronization between the network side and the terminal side.

[0120] In the above solution, the terminal device can determine the DRX states corresponding to different service types based on the first configuration information. When the DRX states corresponding to multiple service types are all active, the terminal device can combine the priority order of processing different service types indicated in the second configuration information to ultimately determine whether to maintain the current BWP or switch to another BWP. The above process solves the problem of switching between BWPs of different service types and ensures that data of different service types can be effectively received.

[0121] Based on the above embodiments, in one implementation, the terminal may change the current BWP in any of the following situations:

[0122] In the first case, the terminal device switches from the current BWP to a BWP different from the current BWP.

[0123] In the second case, the terminal device expands the current BWP.

[0124] The BWP different from the current BWP refers to a BWP different from the current BWP. For ease of understanding, it is assumed that the current BWP is BWP1 and the BWP different from the current BWP is BWP2. Figure 5 A schematic diagram showing BWP1 and BWP2 in system bandwidth is shown. Figure 5 As shown in (a), BWP1 and BWP2 are two completely independent BWPs; Figure 5 As shown in (b), BWP1 and BWP2 have a partial intersection; Figure 5 In (c) shown, BWP1 is contained in BWP2.

[0125] The above-mentioned BWP1 and BWP2 may correspond to different service types, for example, BWP1 is a multicast-only BWP, and BWP2 is a unicast-only BWP. That is, the current BWP and the BWP different from the current BWP may correspond to different service types.

[0126] In one embodiment, when a terminal device expands its current BWP, it covers both the current BWP and a BWP distinct from the current BWP. Expanding the current BWP essentially means that the current BWP remains a continuous BWP, but the terminal device operates at a larger bandwidth. For example, if the current BWP is BWP1 for a first service type (e.g., multicast service), and the terminal device determines that it needs to switch to BWP1 to detect a second service type (e.g., unicast service), the terminal device may expand the current BWP to simultaneously cover BWP1 corresponding to the first service type and BWP2 corresponding to the second service type.

[0127] In the embodiment of the present application, the network side may configure BWPs of different sizes according to the actual needs of different service types. The BWPs corresponding to different service types may overlap or not overlap, and the embodiment of the present application does not impose any limitation on this.

[0128] The technical solution provided by the above embodiment is described in detail below with reference to a specific example, wherein the first service type is a unicast service and the second service type is a multicast service.

[0129] Figure 6 This is a flow chart of a method for processing a broadband part BWP provided in an embodiment of the present application. Figure 6 As shown, the method provided in this embodiment may include the following steps:

[0130] Step 301: The network device sends first configuration information to the terminal device. The first configuration information includes DRX configuration parameters corresponding to unicast and DRX configuration parameters corresponding to multicast.

[0131] Step 302: The terminal device determines a DRX state according to the first configuration information, where the DRX state includes at least one of a unicast DRX state and a multicast DRX state.

[0132] Specifically, the terminal device determines the unicast DRX state according to the DRX configuration parameters corresponding to unicast in the first configuration information; the terminal device determines the multicast DRX state according to the DRX configuration parameters corresponding to multicast in the first configuration information.

[0133] Step 303: The terminal device maintains or changes the current BWP according to at least one of the unicast DRX state and the multicast DRX state.

[0134] In a possible implementation, the terminal device currently operates on a unicast-dedicated BWP. Accordingly, step 303 includes at least one of the following situations:

[0135] In the first case, the terminal device maintains or changes the unicast-dedicated BWP according to the unicast DRX state.

[0136] If the unicast DRX state is deactivated, the terminal device changes the unicast-dedicated BWP. This solution only considers the unicast DRX state, that is, regardless of whether the multicast DRX state is activated or deactivated, as long as the unicast DRX is in the deactivated state, the terminal device changes the unicast-dedicated BWP.

[0137] If the unicast DRX state is active, the terminal device can remain on the unicast dedicated BWP.

[0138] In the second case, the terminal device maintains or changes the unicast-dedicated BWP according to the multicast DRX status.

[0139] If the multicast DRX state is active, the terminal device changes to a unicast-dedicated BWP. This solution only considers the multicast DRX state. That is, regardless of whether the unicast DRX state is active or deactivated, as long as the multicast DRX is deactivated, the terminal device changes to a unicast-dedicated BWP. This shows that this solution implicitly prioritizes multicast services.

[0140] If the multicast DRX state is deactivated, the terminal device can remain on the unicast dedicated BWP.

[0141] In the third case, the terminal device maintains or changes the unicast-dedicated BWP according to the unicast DRX state and the multicast DRX state.

[0142] If the unicast DRX state is activated and the multicast DRX state is deactivated, the terminal device can remain on the unicast-dedicated BWP.

[0143] If the unicast DRX state is deactivated and the multicast DRX state is activated, the terminal device changes the unicast-dedicated BWP.

[0144] If both the unicast DRX state and the multicast DRX state are active, the terminal device can determine whether to maintain or change the unicast-dedicated BWP based on the priority of processing different service types. Specifically, if unicast is prioritized, the unicast-dedicated BWP is maintained; if multicast is prioritized, the unicast-dedicated BWP is changed.

[0145] If both the unicast DRX state and the multicast DRX state are in deactivated state, the terminal device can remain on the unicast dedicated BWP.

[0146] As an optional solution, the terminal device determines to change the unicast dedicated BWP according to at least one of the unicast DRX state and the multicast DRX state, including:

[0147] If any of the following conditions is met, the unicast-only BWP is changed:

[0148] (1) The unicast DRX state is deactivated;

[0149] (2) The multicast DRX state is active;

[0150] (3) Multicast priority is greater than unicast priority.

[0151] In one embodiment, the terminal device changes the unicast dedicated BWP, including:

[0152] The terminal device switches from a unicast-dedicated BWP to a multicast-dedicated BWP; or

[0153] The terminal device expands the unicast-dedicated BWP and covers both the unicast-dedicated BWP and the multicast-dedicated BWP.

[0154] In another possible implementation, the terminal device currently operates on a multicast-dedicated BWP. Accordingly, step 303 includes at least one of the following situations:

[0155] In the first case, the terminal device maintains or changes the multicast-dedicated BWP based on the multicast DRX state. If the multicast DRX state is deactivated, the terminal device changes the multicast-dedicated BWP. This solution only considers the multicast DRX state. That is, regardless of whether the unicast DRX state is activated or deactivated, the terminal device changes the multicast-dedicated BWP as long as the multicast DRX state is deactivated.

[0156] If the multicast DRX state is active, the terminal device can remain on the multicast-dedicated BWP.

[0157] In the second case, the terminal device maintains or changes the multicast-dedicated BWP according to the unicast DRX status.

[0158] If the unicast DRX state is active, the terminal device changes to the multicast-dedicated BWP. This solution only considers the unicast DRX state. That is, regardless of whether the multicast DRX state is active or deactivated, as long as the unicast DRX state is active, the terminal device changes to the multicast-dedicated BWP. This shows that this solution implicitly prioritizes unicast services.

[0159] If the unicast DRX state is deactivated, the terminal device can remain on the multicast-dedicated BWP.

[0160] In the third case, the terminal device maintains or changes the multicast-dedicated BWP according to the unicast DRX state and the multicast DRX state.

[0161] If the unicast DRX state is activated and the multicast DRX state is deactivated, the terminal device changes the multicast-dedicated BWP.

[0162] If the unicast DRX state is deactivated and the multicast DRX state is activated, the terminal device remains on the multicast-dedicated BWP.

[0163] If both the unicast DRX state and the multicast DRX state are active, the terminal device can determine whether to maintain or change the unicast-dedicated BWP based on the priority of processing different service types. Specifically, if unicast is prioritized, the multicast-dedicated BWP is changed; if multicast is prioritized, the multicast-dedicated BWP is maintained.

[0164] If both the unicast DRX state and the multicast DRX state are in deactivated state, the terminal device can remain on the multicast-dedicated BWP.

[0165] As an optional solution, the terminal device determines to change the multicast-dedicated BWP according to at least one of the unicast DRX state and the multicast DRX state, including:

[0166] If any of the following conditions is met, the multicast-specific BWP is changed:

[0167] (1) The multicast DRX state is deactivated;

[0168] (2) Unicast DRX state is active;

[0169] (3) Unicast priority is greater than multicast priority.

[0170] In one embodiment, the terminal device changes the multicast dedicated BWP, including:

[0171] The terminal device switches from a multicast-dedicated BWP to a unicast-dedicated BWP; or

[0172] The terminal device expands the multicast-specific BWP and covers both the multicast-specific BWP and the unicast-specific BWP.

[0173] Each of the above embodiments determines whether to maintain the current BWP or trigger BWP switching based on the DRX status corresponding to different service types, thereby enabling the terminal device to switch between BWPs corresponding to different service types, ensuring that the terminal device receives uplink and downlink data of different services in a timely manner. When the terminal device determines to trigger BWP switching, it can also adjust the DRX status corresponding to different service types through the following embodiments, achieving real-time control of the DRX mechanism corresponding to different service types and reducing terminal device energy consumption.

[0174] Figure 7 This is a flow chart of a method for processing a bandwidth portion BWP provided in an embodiment of the present application. Figure 7 As shown, the processing method provided in this embodiment includes the following steps:

[0175] Step 401: The terminal device determines to switch from a first BWP to a second BWP.

[0176] In an embodiment of the present application, the terminal device may switch from the current first BWP to the second BWP based on network configuration (e.g., downlink control information DCI or a timer). Alternatively, the terminal device may determine to switch from the current first BWP to the second BWP based on the processing method provided in any of the aforementioned embodiments.

[0177] In one embodiment, the first BWP corresponds to a multicast service, and the second BWP corresponds to a unicast service; or, the first BWP corresponds to a unicast service, and the second BWP corresponds to a multicast service.

[0178] Step 402: The terminal device adjusts the first DRX state and / or the second DRX state.

[0179] Specifically, step 402 includes:

[0180] The terminal device suspends or stops the timer corresponding to the first DRX state; and / or

[0181] The terminal device starts, restarts or restores the timer corresponding to the second DRX state.

[0182] The first DRX state corresponds to the first BWP, and the second DRX state corresponds to the second BWP.

[0183] In one embodiment, the timer corresponding to the first DRX state is a DRX timer for multicast, and the timer corresponding to the second DRX state is a DRX timer for unicast; or, the timer corresponding to the first DRX state is a DRX timer for unicast, and the timer corresponding to the second DRX state is a DRX timer for multicast.

[0184] The above scheme is described in detail below with reference to specific examples.

[0185] Example 1: If the terminal device is currently switched from a unicast-dedicated BWP to a multicast-dedicated BWP, the terminal device adjusts the DRX state for unicast and / or the DRX state for multicast.

[0186] Specifically, it may include at least one of the following situations:

[0187] In the first case, the terminal device suspends or stops the DRX timer for unicast, including at least one of the following timers:

[0188] drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL.

[0189] In the second case, the terminal device starts, restarts, or resumes a DRX timer for multicast, including at least one of the following timers:

[0190] onDurationTimerSCPTM, drx-InactivityTimerSCPTM.

[0191] Example 2: If the terminal device is currently switched from a multicast-dedicated BWP to a unicast-dedicated BWP, the terminal device adjusts the DRX state for unicast and / or the DRX state for multicast.

[0192] Specifically, it may include at least one of the following situations:

[0193] In the first case, the terminal device starts, restarts, or resumes a DRX timer for unicast, including at least one of the following timers:

[0194] drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL.

[0195] In the second case, the terminal device suspends or stops the DRX timer for multicast, including at least one of the following timers:

[0196] onDurationTimerSCPTM, drx-InactivityTimerSCPTM.

[0197] The technical solution provided in the embodiment of the present application is that when the terminal device determines to switch from the BWP corresponding to the current service type to the BWP corresponding to other service types, it adjusts the DRX timer corresponding to at least one of the service types to achieve real-time control of the DRX mechanism corresponding to different service types, thereby reducing the energy consumption of the terminal device.

[0198] The above describes in detail the method for processing the bandwidth part BWP provided in the embodiment of the present application. The following describes the terminal device and network device provided in the embodiment of the present application.

[0199] Figure 8 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. Figure 8 As shown, the terminal device of this embodiment includes:

[0200] A receiving module 501 is configured to receive first configuration information sent by a network device, where the first configuration information is used to indicate a first discontinuous reception (DRX) configuration parameter and a second DRX configuration parameter;

[0201] The processing module 502 is configured to maintain or change the current BWP according to the first configuration information.

[0202] In one embodiment, the processing module 502 is specifically configured to:

[0203] determining a first discontinuous reception (DRX) state according to the first DRX configuration parameter;

[0204] determining a second DRX state according to the second DRX configuration parameter;

[0205] Maintain or change a current BWP according to at least one of the first DRX state and the second DRX state.

[0206] In one embodiment, the processing module 502 is specifically configured to:

[0207] If at least one of the following conditions is met, the current BWP will be changed:

[0208] The first DRX state is a deactivated state;

[0209] The second DRX state is an activated state.

[0210] In one embodiment, the terminal device further includes: an acquisition module 503;

[0211] The acquisition module 503 is configured to acquire second configuration information before the processing module maintains or changes the current BWP according to the first configuration information, where the second configuration information is used to indicate the priority order of different services processed by the terminal device;

[0212] Accordingly, the processing module 502 is specifically configured to:

[0213] Maintain or change the current BWP according to the first configuration information and the second configuration information.

[0214] In one implementation, the acquisition module 503 is specifically configured to acquire the second configuration information from the network device.

[0215] In one implementation, the acquisition module 503 is specifically configured to acquire the pre-configured second configuration information.

[0216] In one embodiment, the terminal device further includes: a sending module 504;

[0217] The sending module 504 is configured to send the second configuration information to the network device after the obtaining module obtains the pre-configured second configuration information.

[0218] In one embodiment, the processing module 502 is specifically configured to:

[0219] determining a first DRX state according to the first DRX configuration parameter;

[0220] determining a second DRX state according to the second DRX configuration parameter;

[0221] Maintain or change a current BWP according to at least one of the first DRX state, the second DRX state, and the priority order.

[0222] In one embodiment, the processing module 502 changes the current BWP, including:

[0223] Switching from the current BWP to a BWP different from the current BWP; or

[0224] Expand the current BWP.

[0225] In one embodiment, the first DRX configuration parameter is for a unicast service, and the second DRX configuration parameter is for a multicast service; or

[0226] The first DRX configuration parameter is for a multicast service, and the second DRX configuration parameter is for a unicast service.

[0227] The terminal device provided in the embodiment of the present application is used to perform the above Figure 4 or Figure 6 The technical solution on the terminal device side of the method embodiment shown has similar implementation principles and technical effects, which will not be repeated here.

[0228] Figure 9 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. Figure 9 As shown, the terminal device of this embodiment includes:

[0229] The processing module 601 is configured to adjust the first DRX state and / or the second DRX state when determining to switch from the first BWP to the second BWP;

[0230] The first DRX state corresponds to a first BWP, and the second DRX state corresponds to a second BWP.

[0231] In one embodiment, the processing module 601 is specifically configured to:

[0232] pausing or stopping the timer corresponding to the first DRX state; and / or

[0233] Start, restart or resume the timer corresponding to the second DRX state.

[0234] In one embodiment, the first BWP corresponds to a multicast service, and the second BWP corresponds to a unicast service; or, the first BWP corresponds to a unicast service, and the second BWP corresponds to a multicast service.

[0235] In one embodiment, the timer corresponding to the first DRX state is a DRX timer for multicast, and the timer corresponding to the second DRX state is a DRX timer for unicast; or

[0236] The timer corresponding to the first DRX state is a DRX timer for unicast, and the timer corresponding to the second DRX state is a DRX timer for multicast.

[0237] The terminal device provided in the embodiment of the present application is used to perform the above Figure 7 The technical solution of the terminal device in the method embodiment shown has similar implementation principles and technical effects, which will not be repeated here.

[0238] Figure 10 This is a schematic diagram of the structure of a network device provided in an embodiment of the present application. Figure 10 As shown, the network device of this embodiment includes:

[0239] The sending module 701 is used to send first configuration information to the terminal device, where the first configuration information is used to indicate a first discontinuous reception DRX configuration parameter and a second DRX configuration parameter, so that the terminal device maintains or changes the current BWP according to the first configuration information.

[0240] In one embodiment, the sending module 701 is further configured to:

[0241] Sending second configuration information to the terminal device, where the second configuration information is used to indicate the priority order of the terminal device in processing different services.

[0242] In one embodiment, the first DRX configuration parameter is for a unicast service, and the second DRX configuration parameter is for a multicast service; or

[0243] The first DRX configuration parameter is for a multicast service, and the second DRX configuration parameter is for a unicast service.

[0244] The network device provided in the embodiment of the present application is used to perform the above Figure 4 or Figure 6 The technical solution on the network device side of the method embodiment shown has similar implementation principles and technical effects, which will not be repeated here.

[0245] It should be noted that it should be understood that the division of the various modules of the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, these modules can all be implemented in the form of software called by a processing element; or they can all be implemented in the form of hardware; or some modules can be implemented in the form of software called by a processing element, and some modules can be implemented in the form of hardware. For example, the processing module can be a separately established processing element, or it can be integrated into a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called by a processing element of the above device to perform the functions of the above-mentioned module. The implementation of other modules is similar. In addition, these modules can all or partly be integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0246] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented by scheduling program code on a processing element, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0247] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0248] Figure 11 This is a schematic diagram of the hardware structure of the terminal device provided in the embodiment of the present application. Figure 11 As shown, the terminal device may include: a processor 801, a memory 802, a transceiver 803, and an interface 804 for communicating with a network device.

[0249] The memory 802 stores computer-executable instructions;

[0250] The processor 801 executes the computer-executable instructions stored in the memory 802, so that the processor executes the technical solution of the method for processing the broadband part BWP on the terminal device side in any of the aforementioned method embodiments.

[0251] Figure 12 Schematic diagram of the hardware structure of the network device provided in the embodiment of this application. Figure 12 As shown, the network device may include: a processor 901, a memory 902, a transceiver 903, and an interface 904 for communicating with a terminal device.

[0252] The memory 902 stores computer-executable instructions;

[0253] The processor 901 executes the computer-executable instructions stored in the memory 902, so that the processor 901 executes the technical solution of the method for processing the broadband part BWP on the network device side in any of the aforementioned method embodiments.

[0254] The present application also provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement the technical solution on the terminal device side in any of the aforementioned method embodiments.

[0255] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the technical solution on the network device side in any of the aforementioned method embodiments.

[0256] An embodiment of the present application also provides a program, which, when executed by a processor, is used to execute the technical solution on the terminal device side in the aforementioned method embodiment.

[0257] An embodiment of the present application also provides a program, which, when executed by a processor, is used to execute the technical solution on the network device side in the aforementioned method embodiment.

[0258] An embodiment of the present application also provides a computer program product, including program instructions, which are used to implement the technical solution on the terminal device side in the aforementioned method embodiment.

[0259] An embodiment of the present application further provides a computer program product, including program instructions, which are used to implement the technical solution on the network device side in the aforementioned method embodiment.

[0260] An embodiment of the present application also provides a chip, including: a processing module and a communication interface, wherein the processing module can execute the technical solution on the terminal device side in the aforementioned method embodiment.

[0261] Furthermore, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module enables the processing module to execute the technical solution on the terminal device side.

[0262] An embodiment of the present application further provides a chip, including: a processing module and a communication interface, wherein the processing module can execute the technical solution on the network device side in the aforementioned method embodiment.

[0263] Furthermore, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module enables the processing module to execute the technical solution on the network device side.

[0264] In this application, "at least two" means two or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship; in the formula, the character " / " indicates that the previous and next associated objects are in a "division" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0265] It will be understood that the various numerical numbers involved in the embodiments of the present application are merely distinctions for the convenience of description and are not intended to limit the scope of the embodiments of the present application.

[0266] It can be understood that in the embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Claims

1. A method for processing a bandwidth part (BWP), characterized in that: include: The terminal device receives first configuration information sent by the network device, where the first configuration information is used to indicate a first discontinuous reception (DRX) configuration parameter and a second DRX configuration parameter; The terminal device maintains or changes the current BWP according to the first configuration information.

2. The method according to claim 1, characterized in that The terminal device maintains or changes the current BWP according to the first configuration information, including: The terminal device determines a first discontinuous reception (DRX) state according to the first DRX configuration parameter; The terminal device determines a second DRX state according to the second DRX configuration parameter; The terminal device maintains or changes the current BWP according to at least one of the first DRX state and the second DRX state.

3. The method according to claim 2, characterized in that The terminal device maintaining or changing a current BWP according to at least one of the first DRX state and the second DRX state includes: If at least one of the following conditions is met, the current BWP will be changed: The first DRX state is a deactivated state; The second DRX state is an activated state.

4. The method according to any one of claims 1 to 3, characterized in that Before the terminal device maintains or changes the current BWP according to the first configuration information, the terminal device further includes: The terminal device obtains second configuration information, where the second configuration information is used to indicate a priority order for the terminal device to process different services; The terminal device maintains or changes the current BWP according to the first configuration information, including: The terminal device maintains or changes the current BWP according to the first configuration information and the second configuration information.

5. The method according to claim 4, characterized in that The terminal device obtains the second configuration information, including: the terminal device obtains the second configuration information from the network device.

6. The method according to claim 4, characterized in that The terminal device obtains the second configuration information, including: the terminal device obtains pre-configured second configuration information.

7. The method according to claim 6, characterized in that After the terminal device acquires the pre-configured second configuration information, the method further includes: The second configuration information is sent to the network device.

8. The method according to claim 4, characterized in that The terminal device maintains or changes a current BWP according to the first configuration information and the second configuration information, including: The terminal device determines a first DRX state according to the first DRX configuration parameter; The terminal device determines a second DRX state according to the second DRX configuration parameter; The terminal device maintains or changes the current BWP according to at least one of the first DRX state, the second DRX state and the priority order.

9. The method according to claim 1, characterized in that The changes to the current BWP include: Switching from the current BWP to a BWP different from the current BWP; or Expand the current BWP.

10. The method according to claim 1, characterized in that The first DRX configuration parameter is for a unicast service, and the second DRX configuration parameter is for a multicast service; or The first DRX configuration parameter is for a multicast service, and the second DRX configuration parameter is for a unicast service.

11. A method for processing a bandwidth part (BWP), characterized in that: include: The network device sends first configuration information to the terminal device, where the first configuration information is used to indicate a first discontinuous reception DRX configuration parameter and a second DRX configuration parameter, so that the terminal device maintains or changes a current BWP according to the first configuration information.

12. The method according to claim 11, characterized in that The method further comprises: The network device sends second configuration information to the terminal device, where the second configuration information is used to indicate the priority order of the terminal device in processing different services.

13. The method according to claim 11, characterized in that The first DRX configuration parameter is for a unicast service, and the second DRX configuration parameter is for a multicast service; or The first DRX configuration parameter is for a multicast service, and the second DRX configuration parameter is for a unicast service.

14. A terminal device, characterized in that: include: a receiving module, configured to receive first configuration information sent by a network device, where the first configuration information is used to indicate a first discontinuous reception (DRX) configuration parameter and a second DRX configuration parameter; The processing module is configured to maintain or change the current bandwidth part BWP according to the first configuration information.

15. The device according to claim 14, characterized in that The processing module is specifically used to: determining a first discontinuous reception (DRX) state according to the first DRX configuration parameter; determining a second DRX state according to the second DRX configuration parameter; Maintain or change a current BWP according to at least one of the first DRX state and the second DRX state.

16. The device according to claim 15, characterized in that The processing module is specifically used to: If at least one of the following conditions is met, the current BWP will be changed: The first DRX state is a deactivated state; The second DRX state is an activated state.

17. The device according to any one of claims 14 to 16, characterized in that The terminal device further includes: an acquisition module; the acquisition module is configured to acquire second configuration information before the processing module maintains or changes the current BWP according to the first configuration information, wherein the second configuration information is used to indicate the priority order of the terminal device in processing different services; The processing module is specifically used to: Maintain or change the current BWP according to the first configuration information and the second configuration information.

18. The device according to claim 17, characterized in that The acquisition module is specifically configured to acquire the second configuration information from the network device.

19. The device according to claim 17, characterized in that The acquisition module is specifically configured to acquire the pre-configured second configuration information.

20. The device according to claim 19, characterized in that The terminal device further includes: a sending module; the sending module is configured to send the second configuration information to the network device after the acquisition module acquires the pre-configured second configuration information.

21. The apparatus according to claim 17, wherein The processing module is specifically used to: determining a first DRX state according to the first DRX configuration parameter; determining a second DRX state according to the second DRX configuration parameter; Maintain or change a current BWP according to at least one of the first DRX state, the second DRX state, and the priority order.

22. The apparatus according to claim 14, wherein The processing module changes the current BWP, including: Switching from the current BWP to a BWP different from the current BWP; or Expand the current BWP.

23. The device according to claim 14, characterized in that The first DRX configuration parameter is for a unicast service, and the second DRX configuration parameter is for a multicast service; or The first DRX configuration parameter is for a multicast service, and the second DRX configuration parameter is for a unicast service.

24. A network device, characterized in that: include: The sending module is used to send first configuration information to the terminal device, where the first configuration information is used to indicate a first discontinuous reception DRX configuration parameter and a second DRX configuration parameter, so that the terminal device maintains or changes the current bandwidth part BWP according to the first configuration information.

25. The device according to claim 24, characterized in that The sending module is further used for: Sending second configuration information to the terminal device, where the second configuration information is used to indicate the priority order of the terminal device in processing different services.

26. The device according to claim 24, characterized in that The first DRX configuration parameter is for a unicast service, and the second DRX configuration parameter is for a multicast service; or The first DRX configuration parameter is for a multicast service, and the second DRX configuration parameter is for a unicast service.

27. A terminal device, characterized in that: include: transceivers, processors, and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 10.

28. A network device, characterized in that: include: transceivers, processors, and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 11 to 13.

29. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method of any one of claims 1 to 10 or any one of claims 11 to 13 when the computer-executable instructions are executed by a processor.

Images