WO2023201489A1

WO2023201489A1 - Communication method, terminal device, and network device

Info

Publication number: WO2023201489A1
Application number: PCT/CN2022/087497
Authority: WO
Inventors: 张晋瑜; 胡荣贻; 王淑坤
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-04-18
Filing date: 2022-04-18
Publication date: 2023-10-26

Abstract

The present application relates to a communication method, a terminal device, and a network device. The method comprises: when a terminal device switches to an initial downlink (DL) bandwidth part (BWP), determining the state of a measurement gap (MG), wherein the state of the MG is an activated state or a deactivated state.

Description

Communication method, terminal equipment and network equipment

Technical field

The present application relates to the field of communication, and more specifically, to a communication method, terminal equipment and network equipment.

Background technique

When the terminal equipment works in different bandwidth segments (Bandwidth Part, BWP), for measurement, take the synchronization signal block (Synchronization Signal and PBCH Block, SSB) measurement as an example. Even if it is the same measurement object, when the terminal equipment works in Different BWPs may also have different measurement requirements, for example, a measurement gap (Measurement Gap, MG) is required or no MG is required. However, there is no clear conclusion yet on determining the status of the MG based on the bandwidth segment in which the terminal device works.

Contents of the invention

Embodiments of the present application provide a communication method, terminal equipment, and network equipment that can determine the status of an MG when the terminal equipment switches to a specific BWP, such as an initial downlink BWP or a dormant BWP.

The embodiment of the present application provides a communication method, including:

When the terminal device switches to the initial downlink DL bandwidth segment BWP, the state of the measurement interval MG is determined, and the state of the MG is an activated state or a deactivated state.

The network device determines the state of the measurement interval MG when the terminal device switches to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

When the terminal device switches to the dormant bandwidth segment BWP, the state of the measurement interval MG is determined, and the state of the MG is an activated state or a deactivated state.

The network device determines the state of the measurement interval MG in the case where the terminal device switches to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

An embodiment of the present application provides a terminal device, including:

The first determination unit is configured to determine the state of the measurement interval MG when switching to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

This embodiment of the present application provides a network device, including:

The second determination unit is configured to determine the state of the measurement interval MG when the terminal device switches to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

An embodiment of the present application provides a terminal device, including:

The third determination unit is configured to determine the state of the measurement interval MG when switching to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

The fourth determination unit is used to determine the state of the measurement interval MG when the terminal device switches to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

An embodiment of the present application provides a terminal device, including a processor, a memory, and a transceiver. The memory is used to store computer programs, and the processor is used to control the transceiver to communicate with other devices. The processor is also used to call and run the computer program stored in the memory, so that the terminal device executes the above application to the terminal device. side communication method.

An embodiment of the present application provides a network device, including a processor, a memory, and a transceiver. The memory is used to store computer programs, and the processor is used to control the transceiver to communicate with other devices. The processor is also used to call and run the computer programs stored in the memory, so that the network device performs the above-mentioned application to the network. Device side communication method.

Embodiments of the present application provide a chip that is used to implement the above communication method applied to the terminal device side; or to implement the above communication method applied to the network device side.

Specifically, the chip includes: a processor, used to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned communication method applied to the terminal device side; or, used to implement the above-mentioned communication method applied to the network Communication method on the device side.

Embodiments of the present application provide a computer-readable storage medium for storing a computer program. When the computer program is run by a device, the device performs the above-mentioned communication method applied to the terminal device side; or, performs the above-mentioned communication method applied to the network. Communication method on the device side.

Embodiments of the present application provide a computer program product, including computer program instructions, which cause the computer to execute the above communication method applied to the terminal device side; or to execute the above communication method applied to the network device side.

Embodiments of the present application provide a computer program that, when run on a computer, causes the computer to execute the above communication method applied to the terminal device side; or to execute the above communication method applied to the network device side.

In the embodiment of this application, the status of the MG can be determined when the terminal device switches to a specific BWP, such as the initial downlink BWP or the dormant BWP.

Description of the drawings

Figure 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

Figure 2 is a schematic diagram of a BWP switching scenario according to an embodiment of the present application.

Figure 3 is a schematic flowchart 1 of a communication method according to an embodiment of the present application.

Figure 4 is a schematic flowchart 2 of a communication method according to an embodiment of the present application.

Figure 5 is a schematic flow chart 3 of a communication method according to an embodiment of the present application.

Figure 6 is a schematic flow chart 4 of a communication method according to an embodiment of the present application.

Figure 7 is a schematic block diagram 1 of a terminal device according to an embodiment of the present application.

Figure 8 is a schematic block diagram 1 of a network device according to an embodiment of the present application.

Figure 9 is a second schematic block diagram of a terminal device according to an embodiment of the present application.

Figure 10 is a second schematic block diagram of a network device according to an embodiment of the present application.

Figure 11 is a schematic block diagram of a communication device according to an embodiment of the present application.

Figure 12 is a schematic block diagram of a chip according to an embodiment of the present application.

Figure 13 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

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 (Code Division Multiple Access, CDMA) system, broadband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), wireless fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

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 communication, but also support, for example, Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, etc. , the embodiments of the present application can also be applied to these communication systems.

In a possible implementation manner, the communication system in the embodiment of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or an independent ( Standalone, SA) network deployment scenario.

In a possible implementation, the communication system in the embodiment of the present application can be applied to unlicensed spectrum, where the unlicensed spectrum can also be considered as shared spectrum; or, the communication system in the embodiment of the present application can also be applied to Licensed spectrum, where licensed spectrum can also be considered as unshared spectrum.

The embodiments of this application describe various embodiments in combination with network equipment and terminal equipment. The terminal equipment may also be called user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

The terminal device can be a station (ST) in the WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, or a personal digital processing unit. (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or in the future Terminal equipment in the evolved Public Land Mobile Network (PLMN) network, etc.

In the embodiment of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites). superior).

In the embodiment of this application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, or an augmented reality (Augmented Reality, AR) terminal. Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.

As an example and not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones. Use, such as various types of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In the embodiment of this application, the network device may be a device used to communicate with mobile devices. The network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA. , or it can be a base station (NodeB, NB) in WCDMA, or an evolutionary base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network network equipment (gNB) or network equipment in the future evolved PLMN network or network equipment in the NTN network, etc.

As an example and not a limitation, in the embodiment of the present application, the network device may have mobile characteristics, for example, the network device may be a mobile device. Optionally, the network device can be a satellite or balloon station. For example, the satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite ) satellite, etc. Optionally, the network device may also be a base station installed on land, water, etc.

In this embodiment of the present application, network equipment can provide services for a cell, and terminal equipment communicates with the network equipment through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell. The cell can be a network equipment ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell). The small cell here can include: urban cell (Metro cell), micro cell (Micro cell), pico cell ( Pico cell), femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission services.

Figure 1 illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In a possible implementation, the communication system 100 may include multiple network devices 110 , and the coverage of each network device 110 may include other numbers of terminal devices 120 , which is not limited in this embodiment of the present application.

In a possible implementation, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), etc. The application examples do not limit this.

Among them, network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with access network equipment. The access network equipment can be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system or authorized auxiliary access long-term evolution (LAA- Evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also known as "small base station"), pico base station, access point (access point, AP), Transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc.

It should be understood that in the embodiments of this application, devices with communication functions in the network/system may be called communication devices. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiments of the present application, which will not be described again here; the communication equipment also It may include other devices in the communication system, such as network controllers, mobility management entities and other network entities, which are not limited in the embodiments of this application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship that describes related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and they exist alone. B these three situations. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

It should be understood that the "instruction" mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.

In the description of the embodiments of this application, the term "correspondence" can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed, configuration and being. Configuration and other relationships.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be optionally combined with the technical solutions of the embodiments of the present application, and they all belong to the embodiments of the present application. protected range.

Here, before describing the embodiments of the present application, the concepts involved in the embodiments of the present application will be described first; specifically:

First, pre-configured measurement gap (pre-MG);

The main reason why NR introduces pre-MG is that when the UE works in different bandwidth segments (Bandwidth Part, BWP), for synchronization signal block (Synchronization Signal and PBCH Block, SSB) measurement, even if the same measurement object is measured in different BWP, there may also be different measurement needs. As shown in Figure 2, when the UE works in BWP1, that is, the UE activates BWP1, the frequency domain range of SSB is completely included in the frequency domain range of activated BWP1, and the sub-carrier space (Sub-Carrier Space, SCS) /Cyclic Prefix (CP) is the same. At this time, SSB measurement can be completed without MG. When the UE switches from BWP1 to (switch) BWP2, the frequency domain range of SSB is not within the frequency domain range of BWP2, that is, the SSB is not included in the BWP2 activated by the UE. At this time, the MG is required, that is, it can be performed within the MG. Measurement of SSB. Here, there are many ways to switch BWP. For example, timer (timer) or downlink control information (Downlink Control Information, DCI) can quickly complete BWP switching.

Specifically, take measurement of SSB as an example. Whether it is same-frequency measurement or inter-frequency measurement, when measuring SSB, one of the judgment conditions for whether an MG is required is: whether the frequency domain range of the SSB is within the frequency domain range of the BWP currently activated by the UE; therefore, with the BWP switching , the demand for MG for SSB measurement will also change.

Further, taking measurement of CSI-RS as an example. In the existing protocol, the same-frequency measurement does not require the MG, while the inter-frequency measurement requires the MG. Moreover, positioning reference signal (Positioning Reference Signal, PRS) measurements in related protocols also require MG.

Here, pre-MG can also be used for inter-frequency CSI-RS measurement and PRS measurement, but pre-MG needs to be always active and cannot dynamically change with BWP switching. For example, when the UE needs to perform inter-frequency CSI-RS measurement or PRS measurement, the network device can choose to configure a common MG (that is, the MG involved in Rel-16), or configure the pre-MG to always be active.

The configuration and release of MG in related protocols need to be completed through Radio Resource Control (RRC) signaling, and the delay is relatively large. Therefore, in order to allow the configuration of the MG to be adaptively adjusted with the switching of the BWP, the MG is enhanced, that is, the pre-MG is introduced. In this way, it is convenient to consider the mechanism of activating/deactivating the pre-MG with the switching of the BWP.

It should be noted that a pre-MG is pre-configured for each UE, that is, per-UE, or a pre-MG is pre-configured for each frequency range (Frequency Range, FR), that is, per-FR, and BWP Switching changes the status of the corresponding pre-MG, such as activation status or deactivation status. In this way, it is more consistent with the configuration structure of the existing MG (that is, the ordinary MG mentioned above), and has a relatively small impact on the system; based on this. In the subsequent discussion of Rel-17, only the solution of per-UE pre-configuring a pre-MG, or per-FR pre-configuring a pre-MG was considered.

Second, bandwidth segment (Bandwidth Part, BWP)

The core of BWP is to define an access bandwidth smaller than the cell system bandwidth and terminal bandwidth capabilities. The terminal's sending and receiving operations are all performed within this BWP, thereby achieving more flexible, more efficient, and lower energy consumption terminal operations. Moreover, the BWP configuration adopts the two-layer signaling mechanism of "RRC configuration + DCI/timer activation". In actual applications, before RRC is established, the UE cannot obtain the BWP configured in RRC signaling. However, the UE needs to determine the search space and monitor the required system messages within a certain bandwidth range, such as System Information Block (SIB) messages and paging (Paging) messages.

For the primary cell (PCell), in view of the situation that BWP cannot be configured through RRC signaling before RRC is established, the concept of initial BWP (initial BWP) is added. One method is to determine the bandwidth of a set of data resources indicated in the master system module (Master Information Block, MIB), such as CORESET#0, as the initial downlink BWP (initial DL BWP). Another method is to separately configure an initial DL BWP through the SIB1 information in the SIB message. This is mainly due to the fact that related technologies find that a larger BWP than the bandwidth of CORESET#0 (up to 96RB) is required in some scenarios. Moreover, considering UE energy saving, in some cases, UE will fall back to initial DL BWP. For example, when the timer corresponding to BWP times out and the downlink default BWP is not configured, the UE will fall back to the initial DL BWP. Here, the default BWP is one of the BWPs configured by the network device for the terminal device. If there is no explicit instruction, the initial BWP will be used as the default BWP.

For the secondary cell (SCell), considering the energy saving requirements of the UE, one of the BWPs can be configured as a dormant BWP (dormant BWP). Physical Downlink Control Channel (PDCCH) detection is not configured on the dormant BWP. In this way, when the secondary cell (that is, the carrier) is switched to the dormant BWP, the entire carrier corresponding to the dormant BWP will enter the dormant state. Compared with SCell deactivation, the UE needs to perform some RRM measurements and Channel Quality Indication (CQI) measurements in the dormant carrier state for data scheduling after carrier wake-up.

Specifically, when the UE switches to initial DL BWP, the UE side determines the status of the MG as follows:

Figure 3 is a schematic flowchart 1 of a communication method according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.

S310. When the terminal device switches to the initial downlink DL bandwidth segment BWP, determine the state of the measurement interval MG, and the state of the MG is an activated state or a deactivated state.

Here, the initial DL BWP is the BWP corresponding to PCell, that is, the network device is configured for PCell.

In a specific example, the MG is a pre-configured measurement interval pre-MG; the pre-MG is obtained by enhancing the MG; here, the state of the pre-MG (such as activation state or deactivation state) will change with Changes when BWP switches. In another specific example, the MG may also be a Network control small gap (NCSG) configured through RRC signaling, etc. Preferably, the solution provided by this embodiment is particularly suitable for the scenario where the MG is a pre-MG. That is to say, S310 is specifically: when the terminal device switches to the initial DL BWP, determine the state of the pre-MG, and the state of the pre-MG is an activated state or a deactivated state.

It should be noted that in actual applications, the terminal device only needs to confirm the MG when it successfully switches to the initial DL BWP (in this example, the timing of successfully switching to the initial DL BWP is called the successful switching timing). status. The timing of confirming the status of the MG (in this example, referred to as the status determination timing, for example, when the terminal device switches to the initial DL BWP, or at any time after the terminal device switches to the initial DL BWP), is different from the configuration of the MG. (This configuration can be performed on the terminal device side, or on the network device side, and there is no restriction on the specific configuration end here) and the timing (in this example, the timing of completing the configuration of the MG status is simply referred to as the configuration completion timing). Different, as long as the configuration of the MG status is completed before the terminal device needs to confirm the MG status. In actual applications, it may also happen that the terminal device needs to confirm the status of the MG but the configuration has not been completed. At this time, the terminal device needs to wait for the configuration of the MG status. In this way, after the configuration is completed, the terminal device then confirms the MG's status. state.

Based on the above analysis, it can be seen that there are three timings, namely the timing of successful switching, the timing of status confirmation, and the timing of configuration completion. In addition to the timing of successful switching being earlier than the timing of status confirmation, there are also the following situations:

Scenario 1: The configuration completion time is earlier than the successful switching time. At this time, since the successful switching time is earlier than the status confirmation time, the configuration completion time must also be earlier than the status confirmation time.

Scenario 2: The configuration completion time is the same as the successful switching time, both of which are earlier than the status confirmation time.

Scenario 3: The configuration completion time is later than the successful switching time, but earlier than the status confirmation time.

Scenario 4: The configuration completion time is later than the status confirmation time. In this case, it must also be later than the successful switching time. In this case, the terminal device may need to wait for the MG status configuration to be completed before determining the measurement interval MG status.

It can be understood that the solution of this application does not specifically limit the order of the above three timings (it can be understood that, except for the successful switching timing being earlier than the status determination timing, the sequence of other timings is not limited). In practical applications, as long as it can Solutions for implementing S310 are all within the protection scope of this application solution, and are not exhaustive here.

It is worth noting that the MG described in the solution of this application can be replaced by pre-MG. The following content uses MG as an example to illustrate, and the pre-MG example will not be described again.

In this application solution, the terminal device can use the following two methods to determine the status of the MG, specifically including:

For the first method on the terminal device side of the initial DL BWP solution, the terminal device independently determines the status of the MG;

The first determination method: default or protocol stipulation; the state of the MG is the terminal device's default or protocol stipulation. For example, the terminal device defaults the state of the MG to the activated state, or the terminal device defaults the state of the MG to the deactivated state. For another example, the terminal device determines that the state of the MG is an activated state or a deactivated state based on protocol regulations. This method is simple and requires no additional signaling instructions.

It can be understood that, for the default mode, in order to facilitate the terminal device and the network device to confirm that the MG status is the same, the network device and the terminal device need to agree in advance. For example, the terminal device and the network device both default to the MG status as activated. status, or, the default MG status is deactivated. For the protocol stipulation method, the status of the MG determined by the terminal device and the network device based on the protocol is the same, for example, both are in an activated state or a deactivated state.

It can be understood that other agreement methods can also be used in actual applications. This application solution does not limit this. As long as the status of the MG confirmed by the network device and the terminal device is the same, it is within the protection scope of this application solution. There is no limit here. Lift.

The second determination method: judgment mechanism; specifically includes:

The status of the MG is determined based on the frequency domain relationship between the measurement object and the target carrier; further, the status of the MG is determined based on the frequency domain relationship to determine whether an MG is needed; for example, the status of the MG When it is determined that an MG is required based on the frequency domain relationship, it is an activated state. When it is determined that an MG is not required based on the frequency domain relationship, the state of the MG is a deactivated state.

It should be noted that this example is in a BWP handover scenario, so the UE capabilities and network indication information have been confirmed. Based on this, when the UE capabilities and/or network indication information are determined, the status of the MG is determined based on measurements. The frequency domain relationship between the object and the target carrier is determined.

For example, in the case of SSB measurement, if at least one of the following conditions is met, SSB intra-frequency measurement does not require an MG: the UE indicates through signaling that intra-frequency measurement does not require an MG (that is, the UE supports no-gap capability) ; SSB is within the active BWP; the current active BWP is the initial BWP.

Based on this, for SSB co-frequency measurement, if the UE supports no-gap capability and the network indication information confirms that the UE uses no-gap capability, then SSB co-frequency measurement does not require an MG. At this time, the status of the MG That is, it is a deactivated state, and there is no need to determine based on the frequency domain relationship between the measurement object and the target carrier. Otherwise, if the UE does not support no-gap capability, the status of the MG needs to be determined based on the frequency domain relationship between the measurement object and the target carrier.

Further, continuing with SSB measurement, SSB inter-frequency measurement does not require MG when all the following conditions are met: UE supports inter-frequency measurement without MG; the network indicates that inter-frequency measurement is not applicable to MG; SSB activates BWP within.

Based on this, for SSB inter-frequency measurement, if the above three conditions are met (including that the UE supports inter-frequency measurement and does not require an MG), then the SSB inter-frequency measurement does not require an MG. At this time, the state of the MG is deactivated. Activation status. If the UE does not support inter-frequency measurement and does not require the MG capability, at this time, SSB inter-frequency measurement must require the MG, and the state of the MG is the active state and does not need to be determined based on the frequency domain relationship between the measurement object and the target carrier. . In other cases, it needs to be determined based on the frequency domain relationship between the measurement object and the target carrier.

It can be understood that the above is only an illustrative description, and there may be other situations, which are not exhaustive here.

That is to say, when the UE capability and/or network indication information is determined, the terminal device can also determine the status of the MG based on the frequency domain relationship between the measurement object and the target carrier; further, the terminal device can determine the status of the MG based on the frequency domain relationship between the measurement object and the target carrier. The frequency domain relationship determines whether an MG is needed, and then determines the state of the MG based on whether the MG is needed. For example, when the terminal device determines that an MG is needed based on the frequency domain relationship, it determines that the state of the MG is an active state; When the terminal device determines that the MG is not needed based on the frequency domain relationship, it determines that the state of the MG is a deactivated state.

It can be understood that in this example, the target carrier is a carrier configured by the network device for the terminal device, for example, it is at least part of the carriers configured by the network device for the terminal device. In a specific example, the target carriers are all carriers configured by the network device for the terminal device.

It should be noted that the frequency domain relationship between the measurement object and the target carrier may be specifically at least one of the following relationships:

The first frequency domain relationship: the frequency domain relationship between the frequency domain range corresponding to the measurement object and the frequency domain range of the target carrier. At this time, the target carrier is a deactivated carrier or a dormant carrier, and the frequency domain range of the target carrier refers to the entire frequency domain range of the target carrier.

The second frequency domain relationship: the frequency domain relationship between the frequency domain range corresponding to the measurement object and the frequency domain range corresponding to the activated BWP in the target carrier.

The third frequency domain relationship: the frequency domain relationship between the frequency domain range corresponding to the measurement object and the frequency domain range corresponding to any one or more BWPs configured in the target carrier. At this time, the target carrier is a dormant carrier.

Based on this, the frequency domain range corresponding to the target carrier can be: the frequency domain range of the target carrier itself (that is, the entire frequency domain range of the target carrier), or the frequency domain range corresponding to the activated BWP in the target carrier, or the target carrier The frequency domain range corresponding to one configured BWP, or a combination of frequency domain ranges corresponding to multiple (two or more) BWPs configured for the target carrier. For the convenience of description, any of the above possibilities are referred to below in terms of the frequency domain range corresponding to the target carrier.

Further, in this example, when the frequency domain range corresponding to the measurement object is within the frequency domain range corresponding to the target carrier, the MG is not required; at this time, the terminal device can determine that the state of the MG is a deactivated state. Otherwise, when the frequency domain range corresponding to the measurement object is not within the frequency domain range corresponding to the target carrier, an MG is required; at this time, the terminal device can determine that the state of the MG is an active state.

Here, it can be understood that if the frequency domain range corresponding to the measurement object is at least one frequency domain range corresponding to the target carrier, such as the frequency domain range of the target carrier, or the frequency domain range corresponding to the activated BWP in the target carrier, etc., then it can be Confirm that MG is not required. Correspondingly, if the frequency domain range corresponding to the measurement object is not within all the frequency domain ranges corresponding to the target carrier, for example, it is not within the frequency domain range of the target carrier, and it is not within the frequency domain range corresponding to the activation of BWP in the target carrier, etc., then confirmation is required. MG.

For example, the network device configures three measurement objects for the terminal device, and each measurement object corresponds to a certain frequency domain range; the network device configures 4 carriers for the terminal device, for example, all 4 carriers are target carriers; or, Three of the four carriers, for example, carrier 1 to carrier 3, are target carriers, and the frequency domain where carrier 4 is located is far away from the frequency domain where the measurement object is located, so they are not used as target carriers. This example does not impose specific restrictions on this; as follows Take 4 carriers as target carriers as an example to illustrate; only when the frequency domain range of all measurement objects is within the frequency domain range corresponding to the target carrier (any one of the 4 carriers is enough), can the measurement object be deemed to correspond to The frequency domain range is within the frequency domain range corresponding to the target carrier; otherwise, if the frequency domain range of one or more measurement objects is not within the frequency domain range corresponding to the target carrier, it means that the frequency domain range corresponding to the measurement object is not Within the frequency domain range corresponding to the target carrier.

For example, the frequency domain range of measurement object 1 is within the frequency domain range corresponding to target carrier 1, and the frequency domain ranges of measurement objects 2 and 3 are both within the frequency domain range corresponding to target carrier 2. At this time, it can be determined that the measurement object corresponds to The frequency domain range is within the frequency domain range corresponding to the target carrier. On the contrary, the frequency domain ranges of measurement objects 2 and 3 are both within the frequency domain range of target carrier 2, but measurement object 1 is not within the frequency domain range corresponding to any of the target carriers from target carrier 1 to target carrier 4 of the network equipment. At this time, , it is considered that the frequency domain range of the measurement object is not within the frequency domain range corresponding to the target carrier.

It can be understood that, for the case where the MG is a pre-MG, the state of the pre-MG can also be determined based on the frequency domain relationship to determine whether the MG is required; for example, the state of the pre-MG is based on The state of the pre-MG is an activated state when it is determined that an MG is required based on the frequency domain relationship, and the state of the pre-MG is a deactivated state when it is determined that an MG is not required based on the frequency domain relationship. Here, as to how to determine whether an MG is required, reference can be made to the above example, which will not be described again here.

For the second method on the terminal device side of the initial DL BWP solution, the status of the MG is controlled by the network device; specifically including:

The status of the MG is determined based on status indication information; wherein the status indication information is used to indicate that the status of the MG is an activated state or a deactivated state; specifically, the status indication information is used to indicate that the terminal device When switching to the initial DL BWP, the state of the MG is the activated state or the deactivated state. In this method, the terminal device receives the status indication information from the network device.

As mentioned above, the terminal device only needs to confirm the status of the MG when it successfully switches to the initial DL BWP. The timing of confirming the status of the MG, the timing of receiving the status indication information (referred to as the receiving timing in this example), and the timing of successfully parsing the status indication information and obtaining the status of the MG (referred to as the parsing timing in this example) may be as follows. Several situations:

First, the reception timing is later than the successful switching timing; in this case, the terminal device receives the status indication information only after successfully switching to the initial DL BWP, and then parses the status indication information to determine the status of the MG.

Second, the reception timing is earlier than the successful switching timing; in this case, there may be a situation where the parsing timing is earlier than the status confirmation timing. For example, the terminal device first receives the status indication information and parses the status indication information, Obtain the status of the MG. At this time, the terminal device has not yet successfully switched to the initial DL BWP. Therefore, the terminal device can temporarily store the parsed status of the MG, and then determine the status of the MG after successfully switching to the initial DL BWP. .

It can be understood that the solution of this application does not specifically limit the above-mentioned timing. As long as the solution that can determine the status of the MG based on the status indication information falls within the protection scope of the solution of this application, it is not exhaustive here.

Here, in an example, the status indication information is carried by a system message. Further, the system message also includes: configuration information of the initial DL BWP. That is to say, the status indication information may be carried by a system message containing the configuration information of the initial DL BWP.

Further, in a specific example, the status indication information is carried by the SIB message in the system message. In practical applications, the SIB message may also include SIB1, SIB2, SIB3, etc. In this case, the status indication information may be carried by any one of SIB1, SIB2, and SIB3 in the SIB message. Preferably, the status indication information may be carried by the SIB1; further, the SIB1 also includes configuration information of the initial DL BWP. That is to say, while the network device configures the initial DL BWP in SIB1, it can also configure activation (ON)/deactivation (OFF) indication information (that is, status indication information). The ON/OFF indication information is used to indicate When the terminal device switches to the initial DL BWP, the state of the MG is the activated state or the deactivated state. In this way, by modifying the information of SIB1, the initial DL BWP and the ON/OFF indication information of the MG can be associated simply and effectively.

In another specific example, the status indication information is carried by the MIB message in the system message. At this time, the MIB message implicitly carries (for example, carried by CORESET#0 in the MIB message) the configuration information of the initial DL BWP. . That is to say, while the network device configures the initial DL BWP in the MIB message, it can also configure ON/OFF indication information (that is, status indication information). The ON/OFF indication information is used to indicate when the terminal device switches to the desired state. In the case of the initial DL BWP, the state of the MG is the activated state or the deactivated state. In this way, by modifying the MIB message, the initial DL BWP and the MG's ON/OFF indication information can be associated simply and effectively.

It can be understood that the solution of this application does not limit the specific system messages carrying status indication information. As long as the system message can carry the status indication information, it is within the protection scope of the solution of this application, and is not exhaustive here.

It should be noted that in the actual application of this method, the UE has not yet established an RRC connection with the network device, and has not completed MG (or pre-MG) related capability reporting and measurement object (Measuring Object, MO) configuration. Based on this, the network device needs to consider the configured ON/OFF indication information when configuring the corresponding measurement object.

In another example, the status indication information is carried by RRC signaling. That is to say, ON/OFF indication information (that is, status indication information) is configured through RRC signaling. In this example, the RRC signaling also includes BWP configuration information. For example, the ON/OFF indication information is placed in the BWP configuration information. That is, the network device configures the BWP configuration information in the RRC signaling and at the same time configures the corresponding ON/OFF indication information, the ON/OFF indication information is used to indicate that the state of the MG is an activated state or a deactivated state when the terminal device switches to the initial DL BWP.

Further, in a specific example, the status indication information is carried by serving cell configuration (servingCellconfig) information in the RRC signaling. In this example, the RRC signaling also includes BWP configuration information; for example, the ON/OFF indication information is placed in the newly added information (or field) in the servingCellconfig information.

For example, while configuring the BWP configuration information in the servingCellconfig information, the network device adds an initial downlink BWP preconfiguration interval pattern (preGapStatueForInitialDownlinkBWP) field to configure the ON/OFF indication information corresponding to the initial downlink BWP. Here, the format of the preGapStatueForInitialDownlinkBWP field is as follows:

preGapStatueForInitialDownlinkBWP ENUMERATED{ON,OFF}.

Among them, ON means that the state of the MG is the activated state when the terminal device switches to the initial DL BWP; OFF means that the state of the MG is the deactivated state when the terminal device switches to the initial DL BWP. .

It can be understood that the above preGapStatueForInitialDownlinkBWP is only an indication of the status indication information corresponding to the initial downlink BWP. In actual applications, this field can be in other formats, such as OFF by default, or network configuration is required only when ON, such as:

preGapStatueForInitialDownlinkBWP ON, optional;

Alternatively, a set of sequences is used to indicate the status of MGs corresponding to multiple BWPs. One of the statuses of the MGs corresponding to multiple BWPs (such as the first one) corresponds to the initial downlink BWP, such as:

preGapStatueForDownlinkBWP SEQUENCE(SIZE(1..numOfBwp))OF OnOffIndicator.

In practical applications, the serving cell configuration information may also include at least one of the following fields:

Downlink BWP release list (downlinkBWP-ToReleaseList);

Add modification list of downlink BWP (downlinkBWP-ToAddModList);

BWP’s deactivation timer (bwp-InactivityTimer);

Default downlink BWP identifier (defaultDownlinkBWP-Id).

It can be understood that in actual applications, the status indication information corresponding to the initial downlink BWP can be included in the serving cell configuration information, servingCellconfig information, or other cell-level configuration information; further, servingCellconfig can include the above BWP configuration information, or for In RRC signaling, the configuration information of BWP is the same level of information. This application solution does not limit this. As long as the cell-level RRC signaling carries status indication information corresponding to the initial downlink BWP, it is within the protection scope of this application solution. , not exhaustive here.

In another example, the status indication information is carried by RRC signaling. That is to say, ON/OFF indication information (that is, status indication information) is configured through RRC signaling. In this example, the ON/OFF indication information can be specifically represented by the bits in the bitmap corresponding to the carrier. The bitmap corresponding to the carrier is carried in the RRC signaling. At this time, the RRC signaling can also Carrying BWP configuration information, the solution of this application does not limit other information carried by RRC. Only the RRC signaling carries the bitmap corresponding to the carrier, and the bits in the Bitmap can represent ON/OFF indication information, both of which are included in this application. within the scope of the program.

Further, for the case where the ON/OFF indication information is represented by the bits in the Bitmap corresponding to the carrier, a new bit can be added to the Bitmap corresponding to the carrier, that is, there is a bit in the bitmap corresponding to the carrier to represent the ON/OFF of the initial DL BWP. OFF indication information, the bits in the remaining bits are used to indicate the relevant information of the DL BWP corresponding to the bit in other DL BWPs corresponding to the carrier, for example, indicating the activation status or activation status of the MG of the DL BWP corresponding to the bit.

For example, there are N DL BWPs corresponding to the carrier (that is, the DL BWP configured on the carrier). At this time, the length of the Bitmap corresponding to the carrier is N+1, where the first bit in the Bitmap indicates the initial The status of the MG corresponding to the DL BWP. For example, when the first bit is 0, the indication is OFF, and when the first bit is 1, the indication is ON; and the remaining N bits are used to indicate the DL BWP corresponding to the carrier. This bit corresponds to the MG status of the DL BWP. It can be understood that the above is only a specific example. In actual applications, the bits representing the ON/OFF indication information can also be other bits in the Bitmap, and the solution of this application is not limited to this.

It can be understood that in the above example, the UE is configured with one MG, or the UE is configured with (or corresponds to) one MG. If the UE is configured with (or corresponds to) two or more MGs, refer to the following example.

In another example, the status indication information is carried by RRC signaling, and the status indication information is used to indicate that the status of the MG is the deactivation status when the terminal device switches to the initial DL BWP. Further, the status indication information is carried by the deactivated MG list corresponding to the initial DL BWP in the RRC signaling, that is, the deactivated MG list records the MGs when the terminal device switches to the initial DL BWP. Unique identification (ID). That is to say, in this example, if the deactivated MG list corresponding to the initial DL BWP carries the unique identifier of the MG, it can be confirmed that when the UE switches to the initial DL BWP, the status of the MG corresponding to the unique identifier is deactivated. Activated state; while other MGs preconfigured for the UE, that is, other MG IDs are not in the deactivated MG list corresponding to the initial DL BWP, the status of other MGs defaults to the activated state or is stipulated by the protocol. For example, the network device configures two MGs for the UE, and the unique identifiers are MG1 and MG2 respectively; the UE receives the RRC signaling and parses it to obtain MG1 in the deactivated MG list corresponding to the initial DL BWP. At this time, It can be confirmed that when the UE switches to the initial DL BWP, the state of the MG corresponding to MG1 is the deactivated state, and the state of the MG corresponding to MG2 is the default activated state.

Here, the RRC signaling also includes servingCellconfig information, and the status indication information is carried by the servingCellconfig information. That is, the deactivated MG list corresponding to the initial DL BWP can also be in the servingCellconfig information. For example, the network device adds a deactivated MG list (deactivatedMeasGapListForInitialDownlinkBWP) field corresponding to the initial DL BWP in the servingCellconfig information to indicate which MGs need to be deactivated when the UE switches to the initial DL BWP.

Here, the format of the deactivatedMeasGapListForInitialDownlinkBWP field is as follows:

deactivatedMeasGapListForInitialDownlinkBWP SEQUENCE(SIZE(1,maxNorfGapId-r17))of MeasGapId-r17,OPTIONAL.

Or, the RRC signaling also includes the configuration information of the BWP. At this time, the status indication information is in the configuration information of the BWP, that is, the deactivated MG list corresponding to the initial DL BWP can also be in the BWP. configuration information. Or, the status indication information is not in the configuration information of the BWP.

Or, the RRC signaling includes servingCellconfig information, and the servingCellconfig information includes the configuration information of the BWP. At this time, the status indication information is in the configuration information of the BWP, that is, the deactivated MG corresponding to the initial DL BWP. The list is in the configuration information of the BWP. That is to say, the servingCellconfig information of the RRC signaling is configured with BWP configuration information, and the BWP configuration information is configured with a deactivated MG list corresponding to the initial DL BWP.

Alternatively, the BWP configuration information may not be included in the servingCellconfig information. For example, in RRC signaling, the servingCellconfig information and the BWP configuration information are information at the same level, etc. This application solution does not limit this.

It should be noted that the configuration information of the MG can be outside the deactivated MG list, and the deactivated MG list only records the unique identifier of the MG associated with the BWP (for example, the initial DL BWP). At this time, as long as it can pass The unique identifier of the MG can uniquely locate the configuration information of the MG.

It can be understood that the above is only a specific example. In practical applications, as long as the deactivated MG list is included in the RRC signaling, and the deactivated MG list records the MG corresponding to the initial DL BWP described in the solution of this application. Unique identifiers all fall within the scope of protection of this application plan.

It should be noted that the way in which the UE determines the status of the MG by default or based on protocol regulations can be used in combination with the way in which the network device configures the status of the MG. In this case, the configuration of the network device is mainly used to determine the status of the MG. For example, in an example, when the terminal device switches to the initial DL BWP, the state of the MG is activated by default or based on protocol regulations. At this time, if the network device is in the deactivated MG list of RRC signaling If the MG corresponding to the initial DL BWP is configured, after receiving the RRC signaling, the UE can determine that the status of the MG corresponding to the initial DL BWP is the deactivated state when the terminal device switches to the initial DL BWP. Otherwise, if the network device does not configure the deactivated MG list corresponding to the initial DL BWP, then the status of the MG is the activated state when the terminal device switches to the initial DL BWP.

Here, when the UE switches to initial DL BWP, the solution on the network device side is as follows:

Figure 4 is a schematic flowchart 2 of a communication method according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.

S410: The network device determines the state of the measurement interval MG when the terminal device switches to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

In a specific example, the MG is a preconfigured measurement interval pre-MG; the pre-MG is obtained by enhancing the MG. Here, the state of the pre-MG (such as activation state or deactivation state) will change with BWP switching. In another specific example, the MG may also be a Network control small gap (NCSG) configured through RRC signaling, etc. Preferably, the solution provided by this embodiment is particularly suitable for the scenario where the MG is a pre-MG. That is, S410 is specifically: the network device determines the state of the pre-MG when the terminal device switches to the initial DL BWP, and the state of the pre-MG is an activated state or a deactivated state.

In this example, there are several timings, namely: the timing when the network device determines the status of the MG (this example is called the network confirmation timing), the timing when the network device configures the status of the MG (this example is called the network configuration timing), and the terminal The timing of the device switching to the initial DL BWP (this example is called the timing of successful switching); based on this, the following situations exist:

The network configuration timing is earlier than the network confirmation timing; in this case, the successful switching timing may be earlier than the network configuration timing, or the successful switching timing may be later than the network confirmation timing, or the successful switching timing may be between the network configuration timing and the network confirmation timing.

It can be understood that the solution of this application does not specifically limit the order of the above three opportunities. In practical applications, as long as the solution can realize S410, it is within the protection scope of the solution of this application, and is not exhaustive here.

In this application solution, the network device can use the following two methods to determine the status of the MG, specifically including:

Method 1 for the network equipment side of the initial DL BWP solution: Network equipment and terminal equipment agree on the confirmation method;

The first confirmation method: default or protocol stipulation; the status of the MG is the network device's default or protocol stipulation. For example, the network device defaults the state of the MG to the activated state, or the network device defaults the state of the MG to the deactivated state. For another example, the network device determines that the state of the MG is an activated state or a deactivated state based on protocol regulations. This method is simple and requires no additional signaling instructions.

The second confirmation method: judgment mechanism; specifically includes:

For example, taking SSB measurement, if at least one of the following conditions is met, SSB intra-frequency measurement does not require an MG: the UE indicates through signaling that intra-frequency measurement does not require an MG (that is, the UE supports no-gap capability) ; SSB is within the active BWP; the current active BWP is the initial BWP.

That is to say, when the UE capability and/or network indication information is determined, the network device can also determine the status of the MG based on the frequency domain relationship between the measurement object and the target carrier; further, the network device can determine the status of the MG based on the frequency domain relationship. The domain relationship determines whether an MG is needed, and then determines the status of the MG based on whether the MG is needed. For example, when the network device determines that an MG is needed based on the frequency domain relationship, it determines that the status of the MG is an active state; so When the network device determines that the MG is not needed based on the frequency domain relationship, it determines that the state of the MG is a deactivated state.

Further, in this example, when the frequency domain range corresponding to the measurement object is within the frequency domain range corresponding to the target carrier, the MG is not required; at this time, the terminal device can determine that the state of the pre-MG is the deactivated state. . Otherwise, when the frequency domain range corresponding to the measurement object is not within the frequency domain range corresponding to the target carrier, an MG is required; at this time, the terminal device can determine that the state of the pre-MG is an active state. Here, the specific method of determining whether an MG is required may refer to the above description on the terminal device side, and will not be described again here.

Here, it can be understood that if the frequency domain range corresponding to the measurement object is at least one frequency domain range corresponding to the target carrier, such as the frequency domain range of the target carrier, or the frequency domain range corresponding to the activated BWP in the target carrier, etc., then it can be Confirm that MG is not required. Correspondingly, if the frequency domain range corresponding to the measurement object is not within all the frequency domain ranges corresponding to the target carrier, for example, it is not within the frequency domain range of the target carrier, and it is not within the frequency domain range corresponding to the activation of BWP in the target carrier, etc., then confirmation is required. MG. For specific examples, reference may be made to the above-mentioned examples on the UE side, which will not be described again here.

It can be understood that, for the case where the MG is a pre-MG, the state of the pre-MG can also be determined based on the frequency domain relationship to determine whether the MG is needed; for example, the state of the pre-MG is based on The state of the pre-MG is an activated state when it is determined that an MG is required based on the frequency domain relationship, and the state of the pre-MG is a deactivated state when it is determined that an MG is not required based on the frequency domain relationship. Here, as to how to determine whether an MG is required, reference can be made to the above example, which will not be described again here.

Method 2 for the network device side of the initial DL BWP solution: the network device controls the status of the MG.

The network device sends status indication information, where the status indication information is used to indicate that the status of the MG is an activation state or a deactivation state; specifically, the status indication information is used to indicate that the terminal device switches to the In the case of initial DL BWP, the state of the MG is activated or deactivated.

In an example, after S410, the network device sends status indication information. That is, the timing of sending the status indication information is later than the timing of the network confirming the status of the MG.

Further, in a specific example, the status indication information is carried by the SIB message in the system message. In practical applications, the SIB message may also include SIB1, SIB2, SIB3, etc. In this case, the status indication information may be carried by any one of SIB1, SIB2, and SIB3 in the SIB message. Preferably, the status indication information can be carried by the SIB1; further, the SIB1 also includes the configuration information of the initial DL BWP. That is to say, while the network device configures the initial DL BWP in SIB1, it can also configure activation (ON)/deactivation (OFF) indication information (that is, status indication information). The ON/OFF indication information is used to indicate When the terminal device switches to the initial DL BWP, the state of the MG is the activated state or the deactivated state. In this way, by modifying the information of SIB1, the initial DL BWP and the ON/OFF indication information of the MG can be associated simply and effectively.

For example, while configuring the BWP configuration information in the servingCellconfig information, the network device also adds a preGapStatueForInitialDownlinkBWP field to configure ON/OFF indication information. Here, the format of the preGapStatueForInitialDownlinkBWP field is as follows:

preGapStatueForInitialDownlinkBWP ENUMERATED{ON,OFF}.

preGapStatueForInitialDownlinkBWP ON, optional;

Or, a set of sequences is used to indicate the status of MGs corresponding to multiple BWPs, and one of the statuses (such as the first one) of the MGs corresponding to multiple BWPs corresponds to the initial downlink BWP, such as:

preGapStatueForDownlinkBWP SEQUENCE(SIZE(1..numOfBwp))OF OnOffIndicator.

Downlink BWP release list (downlinkBWP-ToReleaseList);

Add modification list of downlink BWP (downlinkBWP-ToAddModList);

BWP’s deactivation timer (bwp-InactivityTimer);

Default downlink BWP identifier (defaultDownlinkBWP-Id).

It can be understood that in actual applications, the status indication information corresponding to the initial downlink BWP can be included in the serving cell configuration information, or other cell-level configuration information; further, the servingCellconfig information can include the above BWP configuration information, or In the RRC signaling, the configuration information of the BWP is the same level of information. The solution of this application does not limit this. As long as the RRC signaling at the cell level carries the status indication information corresponding to the initial downlink BWP, it is within the protection scope of the solution of this application. There is no exhaustive list here.

In another example, the status indication information is carried by RRC signaling, and the status indication information is used to indicate that the status of the MG is the deactivated status when the terminal device switches to the initial DL BWP. Further, the status indication information is carried by the deactivated MG list corresponding to the initial DL BWP in the RRC signaling, that is, the deactivated MG list records the MGs when the terminal device switches to the initial DL BWP. Unique identification (ID). That is to say, in this example, if the deactivated MG list corresponding to the initial DL BWP carries the unique identifier of the MG, it can be confirmed that when the UE switches to the initial DL BWP, the status of the MG corresponding to the unique identifier is deactivated. Activated state; while other MGs preconfigured for the UE, that is, other MG IDs are not in the deactivated MG list corresponding to the initial DL BWP, the status of other MGs defaults to the activated state or is stipulated by the protocol. For example, the network device configures two MGs for the UE, and the unique identifiers are MG1 and MG2 respectively; the UE receives the RRC signaling and parses it to obtain MG1 in the deactivated MG list corresponding to the initial DL BWP. At this time, It can be confirmed that when the UE switches to the initial DL BWP, the state of the MG corresponding to MG1 is the deactivated state, and the state of the MG corresponding to MG2 is the default activated state.

Here, when the UE switches to dormant BWP, the solution on the UE side is as follows:

Figure 5 is a schematic flow chart 3 of a communication method according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.

S510: When the terminal device switches to the dormant bandwidth segment BWP, determine the state of the measurement interval MG, and the state of the MG is an activated state or a deactivated state.

Here, the sleep BWP is the BWP corresponding to the SCell, that is, the network device is configured for the SCell.

In a specific example, the MG is a pre-configured measurement interval pre-MG; the pre-MG is obtained by enhancing the MG; here, the state of the pre-MG (such as activation state or deactivation state) will change with Changes when BWP switches. In another specific example, the MG may also be a Network control small gap (NCSG) configured through RRC signaling, etc. Preferably, the solution provided by this embodiment is particularly suitable for the scenario where the MG is a pre-MG. That is to say, S510 is specifically: when the terminal device switches to the dormant BWP, determine the state of the pre-MG, and the state of the pre-MG is an activated state or a deactivated state.

It should be noted that in actual applications, the terminal device only needs to confirm the status of the MG when it successfully switches to the dormant BWP (in this example, the timing of successfully switching to the dormant BWP is called the successful switching timing). . The timing of confirming the status of the MG (in this example, referred to as the status determination timing, for example, when the terminal device switches to the dormant BWP, or at any time after the terminal device switches to the dormant BWP), is different from the status of the MG after the configuration is completed. (This configuration can be performed on the terminal device side, or on the network device side. There is no restriction on the specific configuration end here.) The timing (in this example, the timing of completing the configuration of the MG status is referred to as the configuration completion timing) can be different. As long as the configuration of the MG status is completed before the terminal device needs to confirm the MG status. In actual applications, it may also happen that the terminal device needs to confirm the status of the MG but the configuration has not been completed. At this time, the terminal device needs to wait for the configuration of the MG status. In this way, after the configuration is completed, the terminal device then confirms the MG's status. state.

It can be understood that the solution of this application does not specifically limit the order of the above three timings (it can be understood that, except for the successful switching timing being earlier than the status determination timing, the sequence of other timings is not limited). In practical applications, as long as it can Solutions for implementing S510 are all within the protection scope of this application solution, and are not exhaustive here.

For the first method on the terminal device side of the dormant BWP solution, the terminal device independently determines the status of the MG;

The first determination method: default or protocol stipulation; the state of the MG is the terminal device's default or protocol stipulation. For example, the terminal device defaults the state of the MG to the activated state, or the terminal device defaults the state of the MG to the deactivated state. For another example, the terminal device determines that the state of the MG is an activated state or a deactivated state based on protocol regulations. Obviously, this method is simple and requires no additional signaling instructions.

It can be understood that, for the default mode, in order to facilitate the terminal device and the network device to confirm that the MG status is the same, the network device and the terminal device need to agree in advance. For example, the terminal device and the network device both default to the MG status as activated. status, or, the default MG status is deactivated. For the protocol stipulation method, the status of the MG determined by the terminal device and the network device based on the protocol is the same, such as an activated state or a deactivated state.

In a specific example, the terminal device determines that the state of the pre-MG is a deactivated state by default or based on a protocol. That is to say, in this method, the UE does not need to consider the status indication information (used to instruct the terminal device to switch to the dormant bandwidth segment BWP to determine the status of the pre-MG) when making judgments, or regardless of the status indication information on the network device side. The indicated state is ON or OFF, and the UE defaults to the deactivated state for subsequent processing. Of course, in actual applications, for the default mode, the network device side does not need to configure the status indication information. Further, in order to facilitate the terminal device and the network device to confirm that the MG status is the same, at this time, the network device also defaults to the deactivated status of the MG. In this way, it lays the foundation for full utilization of resources (such as those corresponding to dormant BWP), and at the same time, the flexibility is higher.

The second determination method: judgment mechanism; specifically includes:

Judgment mechanism one: The status of the MG is determined based on the frequency domain relationship between the measurement object and the target carrier. Further, the status of the MG is determined based on the frequency domain relationship to determine whether the MG is required. For example, the state of the MG is the activated state when it is determined that the MG is needed based on the frequency domain relationship, and the state of the MG is the deactivated state when it is determined that the MG is not needed based on the frequency domain relationship.

That is to say, when the UE capability and/or network indication information is determined, the terminal device determines the status of the MG based on the frequency domain relationship between the measurement object and the target carrier; further, the terminal device determines the status of the MG based on the frequency domain relationship. The domain relationship determines whether an MG is needed, and then determines the status of the MG based on whether the MG is needed. For example, when the terminal device determines that an MG is needed based on the frequency domain relationship, it determines that the status of the MG is an active state; When the terminal device determines that the MG is not needed based on the frequency domain relationship, it determines that the state of the MG is a deactivated state.

It can be understood that in this example, the target carrier is a carrier configured by the network device for the terminal device. For example, the target carrier is at least part of the carriers configured by the network device for the terminal device. Here, the at least part of the carriers includes the carrier where the dormant BWP is located; or the target carrier is the network device for the terminal device. All configured carriers, including the carrier where the dormant BWP is located.

Here, it can be understood that the frequency domain range corresponding to the measurement object is at least one frequency domain range corresponding to the target carrier, such as within the frequency domain range of the target carrier, or within the frequency domain range corresponding to activating BWP in the target carrier, Or within the frequency domain range of at least one BWP configured on the target carrier, etc., it can be confirmed that no MG is required.

Correspondingly, the frequency domain range corresponding to the measurement object is not within all frequency domain ranges corresponding to the target carrier, such as not within the frequency domain range of the target carrier, and not within the frequency domain range corresponding to the activation of BWP in the target carrier, and not within the target carrier. Within the frequency domain range of at least one configured BWP, etc., it is confirmed that an MG is required.

For example, the network device configures three measurement objects for the terminal device, and each measurement object corresponds to a certain frequency domain range; the network device configures 4 carriers for the terminal device (the 4 carriers are all target carriers); this When, only when the frequency domain ranges of all measurement objects are within the frequency domain range corresponding to the target carrier (any one of the four target carriers is enough), can it be determined that the frequency domain range corresponding to the measurement object is within the frequency domain range corresponding to the target carrier. Within the frequency domain range; otherwise, if the frequency domain range of one or more measurement objects is not within the frequency domain range corresponding to the target carrier, it means that the frequency domain range corresponding to the measurement object is not within the frequency domain range corresponding to the target carrier. .

Judgment mechanism two: The difference between judgment mechanism two and judgment mechanism one is that they target different target carriers during the judgment process.

Specifically, in the first judgment mechanism, the target carrier is a carrier configured by the network device for the terminal device. For example, the target carrier is specifically all carriers configured by the network device for the terminal device, and all the carriers include The carrier where the dormant BWP is located also includes other carriers. The target carrier in the second judgment mechanism is a carrier other than the carrier corresponding to the dormant BWP among the carriers configured by the network device for the terminal device. For example, in the second judgment mechanism, the target carrier is one or more of the remaining carriers after removing the carrier where the dormant BWP is located among all the carriers configured by the network device for the terminal device. For another example, the target carrier in the second judgment mechanism is the remaining carrier after excluding the carrier where the dormant BWP is located among all the carriers configured by the network device for the terminal device.

For example, the network device configures four carriers for the terminal device, namely carrier 1, carrier 2, carrier 3 to carrier 4; among which, the carrier 4 is the carrier where the dormant BWP is located; the target in the second judgment mechanism The carrier can be carrier 1, carrier 2, and carrier 3 (or at least one of carrier 1 to carrier 3. This application solution does not limit this, and can be based on the frequency between the frequency domain where the non-dormant carrier is located and the frequency domain where the measurement object is located. domain interval to select the target carrier); the following description takes the target carriers as carrier 1, carrier 2 and carrier 3 as an example. If the network device configures three measurement objects for the terminal device, at this time, only when the frequency domain ranges of all measurement objects fall within the frequency domain range corresponding to any carrier from carrier 1 to carrier 3, can the measurement object be determined to correspond to The frequency domain range falls within the frequency domain range corresponding to the target carrier; otherwise, if there are one or more measurement objects whose frequency domain range does not fall within the frequency domain range corresponding to any carrier from carrier 1 to carrier 3, then all It means that the frequency domain range corresponding to the measurement object does not fall within the frequency domain range corresponding to the target carrier.

For example, the frequency domain range of measurement object 1 falls within the frequency domain range corresponding to carrier 1, and the frequency domain ranges of measurement objects 2 and 3 both fall within the frequency domain range corresponding to carrier 2. At this time, it can be determined that the measurement object corresponds to The frequency domain range falls within the frequency domain range corresponding to the target carrier. On the contrary, the frequency domain ranges of measurement objects 2 and 3 both fall within the frequency domain range corresponding to carrier 2, but measurement object 1 does not fall within the frequency domain range corresponding to any of carriers 1 to 3. At this time, both It is considered that the frequency domain range of the measurement object does not fall within the frequency domain range corresponding to the target carrier.

For the second method on the terminal device side of the dormant BWP solution: the status of the MG is controlled by the network device; specifically includes:

The terminal device receives the status indication information from a network device. The status of the MG in S510 is determined based on the status indication information.

As mentioned above, the terminal device only needs to confirm the status of the MG when it successfully switches to the dormant BWP. The timing of confirming the status of the MG, the timing of receiving the status indication information (referred to as the receiving timing in this example), and the timing of successfully parsing the status indication information and obtaining the status of the MG (hereinafter referred to as the parsing timing) may include the following: situation:

First, the reception timing is later than the successful switching timing; in this case, the terminal device receives the status indication information only after successfully switching to the dormant BWP, and then parses the status indication information to determine the status of the MG.

Second, the reception timing is earlier than the successful switching timing; in this case, there may be a situation where the parsing timing is earlier than the status confirmation timing. For example, the terminal device first receives the status indication information and parses the status indication information, Obtain the status of the MG. At this time, the terminal device has not yet successfully switched to the dormant BWP. Therefore, the terminal device can temporarily store the parsed status of the MG, and then determine the status of the MG after successfully switching to the dormant BWP.

In an example, the status indication information is used to indicate that the status of the MG is a deactivated state; specifically, the status indication information is used to indicate that the MG is in a deactivated state when the terminal device switches to the dormant BWP. The status is deactivated. At this time, S510 determines the status of the MG specifically: determining that the status of the MG is the deactivated state. Here, the status indication information is carried by RRC signaling. That is to say, the indication information indicating the deactivation state (OFF) (that is, the status indication information) is configured through RRC signaling. In this example, the RRC signaling also includes BWP configuration information. For example, the OFF indication information is placed in the servingCellconfig information. For example, while configuring the configuration information of the BWP in the servingCellconfig information, the network device also configures OFF indication information. The OFF indication information is used to indicate that the status of the MG is when the terminal device switches to the dormant BWP. Deactivated state. Here, the OFF indication information in the servingCellconfig information can be information at the same level as the BWP configuration information. The solution of this application does not limit this. As long as the OFF indication information is carried in RRC signaling, it will be included in the solution of this application. within the scope of protection. This makes network control easier and more flexible.

In another example, the status indication information is indication information corresponding to the carrier corresponding to the dormant BWP, and is used to indicate that the status of the MG is an activated state or a deactivated state. At this time, S510 determines the status of the MG specifically: determining whether the status of the MG is a deactivated state or a deactivated state. In this example, the status indication information is carrier level indication information, and the carrier level indication information is used to indicate the status of the MG when the terminal device switches to the dormant BWP. That is to say, the carrier in the dormant state (that is, the carrier corresponding to the dormant BWP) is regarded as a deactivated carrier, and then the ON/OFF indication information of the deactivated carrier layer is configured, and then the ON/OFF indication information of the deactivated carrier layer is configured. Indication information to determine the status of the MG. At this time, the status indication information is carried by RRC signaling. That is to say, the carrier layer indication information (that is, the status indication information) is configured through RRC signaling. Further, the RRC signaling may include the configuration information of the BWP, or the configuration information of the carrier corresponding to the dormant BWP. For example, the RRC signaling includes the configuration information of the BWP and the configuration information of the carrier corresponding to the dormant BWP. In this case, the configuration information of the carrier corresponding to the dormant BWP and the configuration information of the BWP can be the same level of configuration information. .

It should be noted that the way in which the UE determines the status of the MG by default or based on protocol regulations can be used in combination with the way in which the network device configures the status of the MG. In this case, the configuration of the network device is mainly used to determine the status of the MG. For example, in one example, when the terminal device switches to the initial DL BWP, the state of the MG is activated by default or based on protocol regulations. At this time, if the network device is in the deactivated MG list of RRC signaling If the MG corresponding to the initial DL BWP is configured, after receiving the RRC signaling, the UE can determine that the status of the MG corresponding to the initial DL BWP is the deactivated state when the terminal device switches to the initial DL BWP. Otherwise, if the network device does not configure the deactivated MG list corresponding to the initial DL BWP, then the status of the MG is the activated state when the terminal device switches to the initial DL BWP.

Here, when the UE switches to dormant BWP, the solution on the network device side is as follows:

Figure 6 is a schematic flow chart 4 of a communication method according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.

S610: The network device determines the state of the measurement interval MG when the terminal device switches to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

Here, the initial sleep BWP is the BWP corresponding to the SCell, that is, the network device is configured for the SCell.

In a specific example, the MG is a pre-configured measurement interval pre-MG; the pre-MG is obtained by enhancing the MG; here, the state of the pre-MG (such as activation state or deactivation state) will change with Changes when BWP switches. In another specific example, the MG may also be a Network control small gap (NCSG) configured through RRC signaling, etc. Preferably, the solution provided by this embodiment is particularly suitable for the scenario where the MG is a pre-MG. That is to say, S610 is specifically: the network device determines the state of the pre-MG when the terminal device switches to the dormant BWP, and the state of the pre-MG is the activated state or the deactivated state.

In this example, there are several timings, namely: the timing when the network device determines the status of the MG (this example is called the network confirmation timing), the timing when the network device configures the status of the MG (this example is called the network configuration timing), and the terminal The timing when the device switches to sleep BWP (this example is called the timing of successful switching); based on this, there are the following situations:

It can be understood that the solution of this application does not specifically limit the order of the above three timings. In practical applications, as long as the solution can realize S610, it is within the protection scope of the solution of this application, and is not exhaustive here.

Method 1 for the network device side of the dormant BWP solution: the network device and the terminal device agree on the confirmation method;

In a specific example, the network device determines that the state of the pre-MG is a deactivated state by default or based on a protocol. Here, in order to facilitate the terminal device and the network device to confirm that the MG status is the same, at this time, the terminal device also defaults to the deactivated status of the MG. This provides greater flexibility and facilitates network control.

The second confirmation method: judgment mechanism; specifically includes:

Judgment mechanism one: The status of the MG is determined based on the frequency domain relationship between the measurement object and the target carrier. Further, the status of the MG is determined based on the frequency domain relationship to determine whether the MG is needed. For example, the state of the MG is the activated state when it is determined that the MG is needed based on the frequency domain relationship, and the state of the MG is the deactivated state when it is determined that the MG is not needed based on the frequency domain relationship.

That is to say, when the UE capability and/or network indication information is determined, the network device determines the status of the MG based on the frequency domain relationship between the measurement object and the target carrier; further, the network device determines the status of the MG based on the frequency domain relationship. The domain relationship determines whether an MG is needed, and then determines the status of the MG based on whether the MG is needed. For example, when the network device determines that an MG is needed based on the frequency domain relationship, it determines that the status of the MG is an active state; When the network device determines that the MG is not needed based on the frequency domain relationship, it determines that the state of the MG is a deactivated state.

Further, in this example, when the frequency domain range corresponding to the measurement object is within the frequency domain range corresponding to the target carrier, the MG is not required; at this time, the network device can determine that the state of the MG is a deactivated state. Otherwise, when the frequency domain range corresponding to the measurement object is not within the frequency domain range corresponding to the target carrier, an MG is required; at this time, the network device can determine that the state of the MG is an active state.

Here, it can be understood that the frequency domain range corresponding to the measurement object is at least one frequency domain range corresponding to the target carrier, such as within the frequency domain range of the target carrier, or within the frequency domain range corresponding to activating BWP in the target carrier, Or within the frequency domain range corresponding to at least one BWP configured on the target carrier, etc., it can be confirmed that MG is not required.

For example, the network device configures three measurement objects for the terminal device, and each measurement object corresponds to a certain frequency domain range; the network device configures 4 carriers for the terminal device (the 4 carriers are all target carriers); this When, only when the frequency domain range of all measurement objects is within the frequency domain range corresponding to the target carrier (any one of the four carriers is enough), can it be determined that the frequency domain range corresponding to the measurement object is within the frequency domain range corresponding to the target carrier. Within the frequency domain range; otherwise, if the frequency domain range of one or more measurement objects is not within the frequency domain range corresponding to the target carrier, it means that the frequency domain range corresponding to the measurement object is not within the frequency domain range corresponding to the target carrier. .

Specifically, in the first judgment mechanism, the target carrier is a carrier configured by the network device for the terminal device. For example, the target carrier is specifically all carriers configured by the network device for the terminal device, and all the carriers include The carrier where the dormant BWP is located also includes other carriers. The target carrier in the second judgment mechanism is a carrier other than the carrier corresponding to the dormant BWP among the carriers configured by the network device for the terminal device. For example, in the second judgment mechanism, the target carrier is one or more of the remaining carriers after removing the carrier where the dormant BWP is located among all the carriers configured by the network device for the terminal device. Preferably, the target carrier in the second judgment mechanism is the remaining carrier (which may also be called other carriers) after removing the carrier where the dormant BWP is located among all the carriers configured by the network device for the terminal device. For a specific example, refer to the example of the second judgment mechanism of the UE, which will not be described again here.

Method 2 on the network device side of the dormant BWP solution: the network device controls the status of the MG.

The network device sends status indication information.

In an example, after S610, the network device sends status indication information. That is, the timing of sending the status indication information is later than the timing of the network confirming the status of the MG.

In an example, the status indication information is used to indicate that the status of the MG is a deactivated state; specifically, the status indication information is used to indicate that the MG is in a deactivated state when the terminal device switches to the dormant BWP. The status is deactivated. Here, the status indication information is carried by RRC signaling. That is to say, the indication information indicating the deactivation state (OFF) (that is, the status indication information) is configured through RRC signaling. In this example, the RRC signaling also includes BWP configuration information. For example, the OFF indication information is placed in the servingCellconfig information. For example, while configuring the configuration information of the BWP in the servingCellconfig information, the network device also configures OFF indication information. The OFF indication information is used to indicate that the status of the MG is when the terminal device switches to the dormant BWP. Deactivated state. Here, the OFF indication information in the servingCellconfig information can be information at the same level as the BWP configuration information. The solution of this application does not limit this. As long as the OFF indication information is carried in RRC signaling, it will be included in the solution of this application. within the scope of protection. This makes network control easier and more flexible.

In another example, the status indication information is indication information corresponding to the carrier corresponding to the dormant BWP, and is used to indicate that the status of the MG is an activated state or a deactivated state. In this example, the status indication information is carrier level indication information, and the carrier level indication information is used to indicate the status of the MG when the terminal device switches to the dormant BWP. That is to say, the carrier in the dormant state (that is, the carrier corresponding to the dormant BWP) is regarded as a deactivated carrier, and then the ON/OFF indication information of the deactivated carrier layer is configured, and then the ON/OFF indication information of the deactivated carrier layer is configured. Indication information to determine the status of the MG. At this time, the status indication information is carried by RRC signaling. That is to say, the carrier layer indication information (that is, the status indication information) is configured through RRC signaling. Further, the RRC signaling may include the configuration information of the BWP, or the configuration information of the carrier corresponding to the dormant BWP. For example, the RRC signaling includes the configuration information of the BWP and the configuration information of the carrier corresponding to the dormant BWP. In this case, the configuration information of the carrier corresponding to the dormant BWP and the configuration information of the BWP may be the same level of configuration. information.

Figure 7 is a schematic block diagram 1 of a terminal device according to an embodiment of the present application. The terminal device 700 may include:

The first determining unit 710 is configured to determine the state of the measurement interval MG when switching to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

In one implementation, the status of the MG is determined based on status indication information; wherein the status indication information is used to indicate that the status of the MG is an activated state or a deactivated state.

In one implementation, the terminal device 700 further includes: a first receiving unit configured to receive the status indication information from a network device.

In one implementation, the status indication information is carried by a system message.

In one implementation, the system message further includes: configuration information of the initial DL BWP.

In an implementation manner, the status indication information is carried by Radio Resource Control (RRC) signaling.

In an implementation manner, the status indication information is carried by the serving cell configuration information in the RRC signaling.

In an implementation manner, the status indication information is carried by BWP configuration information in the RRC signaling.

In an implementation manner, the state of the MG is default or specified by the protocol.

In one implementation, the measurement interval MG is a preconfigured measurement interval pre-MG.

The terminal device 700 in the embodiment of the present application can implement the corresponding functions of the terminal device in the foregoing method embodiment. For the corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the terminal device 700, please refer to the corresponding description in the above method embodiment, and will not be described again here. It should be noted that the functions described for each module (sub-module, unit or component, etc.) in the terminal device 700 of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by the same module. Module (submodule, unit or component, etc.) implementation.

Figure 8 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 800 may include:

The second determining unit 810 is configured to determine the state of the measurement interval MG when the terminal device switches to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

In one embodiment, it also includes:

The first sending unit is configured to send status indication information, where the status indication information is used to indicate that the status of the MG is an activation state or a deactivation state.

The network device 800 in the embodiment of the present application can implement the corresponding functions of the network device in the foregoing method embodiment. For the corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the network device 800, please refer to the corresponding description in the above method embodiment, and will not be described again here. It should be noted that the functions described for each module (sub-module, unit or component, etc.) in the network device 800 of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by the same Module (submodule, unit or component, etc.) implementation.

Figure 9 is a second schematic block diagram of a terminal device according to an embodiment of the present application. The terminal device 900 may include:

The third determination unit 910 is configured to determine the state of the measurement interval MG when switching to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

In one implementation, the status of the MG is determined based on the frequency domain relationship between the measurement object and the target carrier.

In one implementation, the status of the MG is determined based on the frequency domain relationship to determine whether an MG is required.

In one implementation, the state of the MG is an active state when it is determined that an MG is required based on the frequency domain relationship.

In one implementation, the state of the MG is a deactivated state when it is determined that the MG is not needed based on the frequency domain relationship.

In an implementation manner, the target carrier is a carrier configured by a network device for the terminal device.

In one implementation, the target carrier is a carrier other than the carrier corresponding to the dormant BWP among the carriers configured by the network device for the terminal device.

In one implementation, the status of the MG is determined based on status indication information.

In one embodiment, it also includes:

The second receiving unit is configured to receive the status indication information from the network device.

In an implementation manner, the status indication information is used to indicate that the status of the MG is a deactivated state.

In one implementation, the status indication information is indication information corresponding to the carrier corresponding to the dormant BWP, and is used to indicate that the status of the MG is an activated state or a deactivated state.

In one implementation, the state of the MG is deactivated by default or specified by the protocol.

The terminal device 900 in the embodiment of the present application can implement the corresponding functions of the terminal device in the foregoing method embodiment. For the corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the terminal device 900, please refer to the corresponding description in the above method embodiment, and will not be described again here. It should be noted that the functions described for each module (sub-module, unit or component, etc.) in the terminal device 900 in the embodiment of the application can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by the same module. Module (submodule, unit or component, etc.) implementation.

Figure 10 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 1000 may include:

The fourth determining unit 1010 is configured to determine the state of the measurement interval MG when the terminal device switches to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.

In one embodiment, it also includes:

The second sending unit is configured to send status indication information, where the status indication information is used to indicate that the status of the MG is a deactivated state.

In one embodiment, it also includes:

The third sending unit is configured to send status indication information, where the status indication information is indication information corresponding to the carrier corresponding to the dormant BWP, and is used to indicate the status of the MG when the terminal device switches to the dormant BWP. is activated or deactivated.

The network device 1000 in the embodiment of the present application can implement the corresponding functions of the network device in the foregoing method embodiment. For the corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the network device 1000, please refer to the corresponding description in the above method embodiment, and will not be described again here. It should be noted that the functions described for each module (sub-module, unit or component, etc.) in the network device 1000 of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by the same Module (submodule, unit or component, etc.) implementation.

Figure 11 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device 1100 includes a processor 1110, and the processor 1110 can call and run a computer program from the memory, so that the communication device 1100 implements the method in the embodiment of the present application.

In a possible implementation, the communication device 1100 may further include a memory 1120. The processor 1110 can call and run the computer program from the memory 1120, so that the communication device 1100 implements the method in the embodiment of the present application.

The memory 1120 may be a separate device independent of the processor 1110, or may be integrated into the processor 1110.

In a possible implementation, the communication device 1100 may also include a transceiver 1130, and the processor 1110 may control the transceiver 1130 to communicate with other devices. Specifically, the communication device 1100 may send information or data to, or receive data from, other devices. Information or data sent.

Among them, the transceiver 1130 may include a transmitter and a receiver. The transceiver 1130 may further include an antenna, and the number of antennas may be one or more.

In a possible implementation manner, the communication device 1100 may be a network device according to the embodiment of the present application, and the communication device 1100 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For simplicity, in This will not be described again.

In a possible implementation manner, the communication device 1100 can be a terminal device in the embodiment of the present application, and the communication device 1100 can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For simplicity, in This will not be described again.

Figure 12 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1200 includes a processor 1210, and the processor 1210 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

In a possible implementation, the chip 1200 may also include a memory 1220. The processor 1210 can call and run the computer program from the memory 1220 to implement the method executed by the terminal device or network device in the embodiment of the present application.

The memory 1220 may be a separate device independent of the processor 1210, or may be integrated into the processor 1210.

In a possible implementation, the chip 1200 may also include an input interface 1230. The processor 710 can control the input interface 1230 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

In a possible implementation, the chip 1200 may also include an output interface 1240. The processor 1210 can control the output interface 1240 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

In a possible implementation manner, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, this chip is not mentioned here. Again.

In a possible implementation manner, the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiment of the present application. For the sake of brevity, this is not mentioned here. Again.

The chips used in network equipment and terminal equipment can be the same chip or different chips.

It should be understood that the chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.

The processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (FPGA), an application specific integrated circuit (ASIC), or Other programmable logic devices, transistor logic devices, discrete hardware components, etc. The above-mentioned general processor may be a microprocessor or any conventional processor.

The memory mentioned above may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM).

It should be understood that the above memory is an exemplary but not restrictive description. For example, the memory in the embodiment of the present application can also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, memories in embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

Figure 13 is a schematic block diagram of a communication system according to an embodiment of the present application. The communication system 1300 includes a terminal device 1310 and a network device 1320.

When the terminal device 1310 switches to the initial downlink DL bandwidth segment BWP, the status of the measurement interval MG is determined, and the status of the MG is an activated state or a deactivated state; the network device 1320 determines when the terminal device switches to the initial downlink DL bandwidth segment BWP. In the case of segment BWP, the state of the interval MG is measured, and the state of the MG is the activated state or the deactivated state;

Alternatively, when the terminal device 1310 switches to the dormant bandwidth segment BWP, the status of the measurement interval MG is determined, and the status of the MG is an activated state or a deactivated state; the network device 1320 determines that when the terminal device switches to the dormant bandwidth segment BWP In case of measurement interval, the state of the MG is the activated state or the deactivated state.

The terminal device 1310 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1320 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, no further details will be given here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may 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 processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted over a wired connection from a website, computer, server, or data center (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center. 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 integrated with one or more available media. The available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), etc.

It should be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application. are covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method of communication including:

When the terminal device switches to the initial downlink DL bandwidth segment BWP, the state of the measurement interval MG is determined, and the state of the MG is an activated state or a deactivated state.
The method according to claim 1, wherein the state of the MG is determined based on state indication information; wherein the state indication information is used to indicate that the state of the MG is an activated state or a deactivated state.
The method of claim 2, further comprising:

Receive the status indication information from a network device.
The method according to claim 3, wherein the status indication information is carried by a system message.
The method according to claim 4, wherein the system message further includes: configuration information of the initial DL BWP.
The method according to claim 3, wherein the status indication information is carried by Radio Resource Control (RRC) signaling.
The method according to claim 6, wherein the status indication information is carried by serving cell configuration information in the RRC signaling.
The method according to claim 6 or 7, wherein the status indication information is carried by BWP configuration information in the RRC signaling.
The method according to claim 1, wherein the state of the MG is default or specified by the protocol.
The method according to any one of claims 1 to 9, wherein the measurement interval MG is a preconfigured measurement interval pre-MG.
A method of communication including:

The network device determines the state of the measurement interval MG when the terminal device switches to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.
The method of claim 11, further comprising:

The network device sends status indication information, where the status indication information is used to indicate that the status of the MG is an activation state or a deactivation state.
The method of claim 12, wherein the status indication information is carried by a system message.
The method according to claim 13, wherein the system message further includes: configuration information of the initial DL BWP.
The method according to claim 12, wherein the status indication information is carried by Radio Resource Control (RRC) signaling.
The method according to claim 15, wherein the status indication information is carried by serving cell configuration information in the RRC signaling.
The method according to claim 15 or 16, wherein the status indication information is carried by BWP configuration information in the RRC signaling.
The method according to claim 11, wherein the state of the MG is default or specified by the protocol.
The method according to any one of claims 11 to 18, wherein the measurement interval MG is a preconfigured measurement interval pre-MG.
A method of communication including:

When the terminal device switches to the dormant bandwidth segment BWP, the state of the measurement interval MG is determined, and the state of the MG is an activated state or a deactivated state.
The method according to claim 20, wherein the state of the MG is determined based on the frequency domain relationship between the measurement object and the target carrier.
The method according to claim 21, wherein the status of the MG is determined based on the frequency domain relationship to determine whether an MG is required.
The method of claim 22, wherein the state of the MG is an active state when it is determined that an MG is required based on the frequency domain relationship.
The method according to claim 22 or 23, wherein the state of the MG is a deactivated state when it is determined that the MG is not needed based on the frequency domain relationship.
The method according to any one of claims 21 to 24, wherein the target carrier is a carrier configured by a network device for the terminal device.
The method according to any one of claims 21 to 24, wherein the target carrier is a carrier other than the carrier corresponding to the dormant BWP among the carriers configured by the network device for the terminal device.
The method according to claim 20, wherein the status of the MG is determined based on status indication information.
The method of claim 27, further comprising:

The terminal device receives the status indication information from a network device.
The method according to claim 27 or 28, wherein the status indication information is used to indicate that the status of the MG is a deactivated status.
The method according to claim 27 or 28, wherein the status indication information is indication information corresponding to the carrier corresponding to the dormant BWP, and is used to indicate that the status of the MG is an activated state or a deactivated state.
The method according to any one of claims 28 to 30, wherein the status indication information is carried by Radio Resource Control (RRC) signaling.
The method according to claim 31, wherein the status indication information is carried by BWP configuration information in the RRC signaling.
The method according to claim 20, wherein the state of the MG is default or specified by the protocol.
The method according to claim 33, wherein the state of the MG defaults to a deactivated state; or, the protocol stipulates that the state is a deactivated state.
The method according to any one of claims 20 to 34, wherein the measurement interval MG is a preconfigured measurement interval pre-MG.
A method of communication including:

The network device determines the state of the measurement interval MG in the case where the terminal device switches to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.
The method according to claim 36, wherein the state of the MG is determined based on the frequency domain relationship between the measurement object and the target carrier.
The method according to claim 37, wherein the status of the MG is determined based on the frequency domain relationship to determine whether an MG is required.
The method of claim 38, wherein the state of the MG is an active state when it is determined that an MG is required based on the frequency domain relationship.
The method according to claim 38 or 39, wherein the state of the MG is a deactivated state when it is determined that the MG is not needed based on the frequency domain relationship.
The method according to any one of claims 37 to 40, wherein the target carrier is a carrier configured by a network device for the terminal device.
The method according to any one of claims 37 to 40, wherein the target carrier is a carrier other than the carrier corresponding to the dormant BWP among the carriers configured by the network device for the terminal device.
The method of claim 36, further comprising:

The network device sends status indication information, where the status indication information is used to indicate that the status of the MG is a deactivated state.
The method of claim 36, further comprising:

The network device sends status indication information, where the status indication information is indication information corresponding to the carrier corresponding to the dormant BWP, and is used to indicate that the status of the MG is the active status when the terminal device switches to the dormant BWP. or deactivated state.
The method according to claim 43 or 44, wherein the status indication information is carried by Radio Resource Control (RRC) signaling.
The method according to claim 45, wherein the status indication information is carried by BWP configuration information in the RRC signaling.
The method according to claim 36, wherein the state of the MG is default or specified by the protocol.
The method according to claim 47, wherein the state of the MG is deactivated by default or specified by protocol.
The method according to any one of claims 36 to 48, wherein the measurement interval MG is a preconfigured measurement interval pre-MG.
A terminal device including:

The first determination unit is configured to determine the state of the measurement interval MG when switching to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.
The device according to claim 50, wherein the state of the MG is determined based on state indication information; the state indication information is used to indicate that the state of the MG is an activated state or a deactivated state.
The device of claim 51, further comprising:

The first receiving unit is configured to receive the status indication information from the network device.
The device of claim 52, wherein the status indication information is carried by a system message.
The device according to claim 53, wherein the system message further includes: configuration information of the initial DL BWP.
The device according to claim 52, wherein the status indication information is carried by Radio Resource Control (RRC) signaling.
The device according to claim 55, wherein the status indication information is carried by serving cell configuration information in the RRC signaling.
The device according to claim 55 or 56, wherein the status indication information is carried by BWP configuration information in the RRC signaling.
The device according to claim 50, wherein the state of the MG is default or specified by the protocol.
The device according to any one of claims 50 to 58, wherein the measurement interval MG is a preconfigured measurement interval pre-MG.
A network device that includes:

The second determination unit is configured to determine the state of the measurement interval MG when the terminal device switches to the initial downlink DL bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.
The device of claim 60, further comprising:

The first sending unit is configured to send status indication information, where the status indication information is used to indicate that the status of the MG is an activation state or a deactivation state.
The device according to claim 61, wherein the status indication information is carried by a system message.
The device according to claim 62, wherein the system message further includes: configuration information of the initial DL BWP.
The device according to claim 61, wherein the status indication information is carried by Radio Resource Control (RRC) signaling.
The device according to claim 64, wherein the status indication information is carried by serving cell configuration information in the RRC signaling.
The device according to claim 64 or 65, wherein the status indication information is carried by BWP configuration information in the RRC signaling.
The device according to claim 60, wherein the state of the MG is default or specified by the protocol.
The device according to any one of claims 60 to 67, wherein the measurement interval MG is a preconfigured measurement interval pre-MG.
A terminal device including:

The third determination unit is configured to determine the state of the measurement interval MG when switching to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.
The device according to claim 69, wherein the state of the MG is determined based on the frequency domain relationship between the measurement object and the target carrier.
The device according to claim 70, wherein the status of the MG is determined based on the frequency domain relationship to determine whether an MG is required.
The device of claim 71, wherein the state of the MG is an active state if it is determined that an MG is required based on the frequency domain relationship.
The device according to claim 71 or 72, wherein the state of the MG is a deactivated state when it is determined that the MG is not needed based on the frequency domain relationship.
The device according to any one of claims 70 to 73, wherein the target carrier is a carrier configured by a network device for the terminal device.
The device according to any one of claims 70 to 73, wherein the target carrier is a carrier other than the carrier corresponding to the dormant BWP among the carriers configured by the network device for the terminal device.
The device according to claim 69, wherein the status of the MG is determined based on status indication information.
The apparatus of claim 76, further comprising:

The second receiving unit is configured to receive the status indication information from the network device.
The device according to claim 76 or 77, wherein the status indication information is used to indicate that the status of the MG is a deactivated status.
The device according to claim 76 or 77, wherein the status indication information is indication information corresponding to the carrier corresponding to the dormant BWP, and is used to indicate that the status of the MG is an activated state or a deactivated state.
The device according to any one of claims 77 to 79, wherein the status indication information is carried by Radio Resource Control (RRC) signaling.
The device according to claim 80, wherein the status indication information is carried by BWP configuration information in the RRC signaling.
The device according to claim 69, wherein the state of the MG is default or specified by the protocol.
The device according to claim 82, wherein the state of the MG is a deactivated state by default or specified by the protocol.
The device according to any one of claims 69 to 83, wherein the measurement interval MG is a preconfigured measurement interval pre-MG.
A network device that includes:

The fourth determination unit is used to determine the state of the measurement interval MG when the terminal device switches to the dormant bandwidth segment BWP, and the state of the MG is an activated state or a deactivated state.
The device of claim 85,

Wherein, the state of the MG is determined based on the frequency domain relationship between the measurement object and the target carrier.
The device of claim 86,

Wherein, the status of the MG is determined based on the frequency domain relationship to determine whether the MG is required.
The device of claim 87,

Wherein, the state of the MG is an active state when it is determined that an MG is required based on the frequency domain relationship.
The device according to claim 87 or 88, wherein the state of the MG is a deactivated state when it is determined that the MG is not needed based on the frequency domain relationship.
The device according to any one of claims 86 to 89, wherein the target carrier is a carrier configured by a network device for the terminal device.
A device according to any one of claims 86 to 89,

Wherein, the target carrier is a carrier other than the carrier corresponding to the dormant BWP among the carriers configured by the network device for the terminal device.
The apparatus of claim 85, further comprising:

The second sending unit is configured to send status indication information, where the status indication information is used to indicate that the status of the MG is a deactivated state.
The apparatus of claim 85, further comprising:

The third sending unit is configured to send status indication information, where the status indication information is indication information corresponding to the carrier corresponding to the dormant BWP, and is used to indicate the status of the MG when the terminal device switches to the dormant BWP. is activated or deactivated.
The device according to claim 92 or 93, wherein the status indication information is carried by Radio Resource Control (RRC) signaling.
The device according to claim 94, wherein the status indication information is carried by BWP configuration information in the RRC signaling.
The device according to claim 85, wherein the state of the MG is default or specified by the protocol.
The device according to claim 96, wherein the state of the MG is a deactivated state by default or specified by the protocol.
The device according to any one of claims 85 to 97, wherein the measurement interval MG is a preconfigured measurement interval pre-MG.
A terminal device, including: a processor, a memory and a transceiver. The memory is used to store computer programs. The processor is used to control the transceiver to communicate with other devices. The processor is also used to call and run the memory. A computer program is stored to cause the terminal device to perform the method as described in any one of claims 1 to 10, or to perform the method as described in any one of claims 20 to 35.
A network device, including: a processor, a memory and a transceiver. The memory is used to store computer programs. The processor is used to control the transceiver to communicate with other devices. The processor is also used to call and run the memory. A stored computer program to cause the network device to execute the method as claimed in any one of claims 11 to 19, or to execute the method as claimed in any one of claims 36 to 49.
A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method as claimed in any one of claims 1 to 10, or executes the method as claimed in any one of claims 1 to 10 The method of any one of 20 to 35.
A chip, including: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method as claimed in any one of claims 11 to 19, or executes the method as claimed in any one of claims 11 to 19 The method of any one of 36 to 49.
A computer-readable storage medium for storing a computer program, which when the computer program is run by a device, causes the device to perform the method as claimed in any one of claims 1 to 10, or to perform the method as claimed in claim 20 The method described in any one of to 35.
A computer-readable storage medium for storing a computer program, which when the computer program is run by a device, causes the device to perform the method as claimed in any one of claims 11 to 19, or to perform the method as claimed in claim 20 The method described in any one of to 35.
A computer program product, comprising computer program instructions, the computer program instructions causing a computer to perform the method according to any one of claims 1 to 10, or to perform the method according to any one of claims 20 to 35 .
A computer program product, comprising computer program instructions, the computer program instructions causing a computer to perform the method according to any one of claims 11 to 19, or to perform the method according to any one of claims 36 to 49 .
A computer program that causes a computer to perform the method as described in any one of claims 1 to 10, or to perform the method as described in any one of claims 20 to 35.
A computer program that causes a computer to perform the method as described in any one of claims 11 to 19, or to perform the method as described in any one of claims 36 to 49.
A communications system including:

Terminal equipment, used to perform the method according to any one of claims 1 to 10;

Network equipment, used to perform the method according to any one of claims 11 to 19.
A communications system including:

Terminal equipment, used to perform the method according to any one of claims 20 to 35;

Network equipment, used to perform the method according to any one of claims 36 to 49.