WO2023077466A1 - Bwp回退方法、装置、设备及存储介质 - Google Patents

Bwp回退方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2023077466A1
WO2023077466A1 PCT/CN2021/129121 CN2021129121W WO2023077466A1 WO 2023077466 A1 WO2023077466 A1 WO 2023077466A1 CN 2021129121 W CN2021129121 W CN 2021129121W WO 2023077466 A1 WO2023077466 A1 WO 2023077466A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
terminal
type
downlink
default
Prior art date
Application number
PCT/CN2021/129121
Other languages
English (en)
French (fr)
Inventor
牟勤
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2021/129121 priority Critical patent/WO2023077466A1/zh
Priority to CN202180003789.4A priority patent/CN114175724A/zh
Publication of WO2023077466A1 publication Critical patent/WO2023077466A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/20—Negotiating bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of mobile communication, in particular to a BWP (Band Width Part, bandwidth part) fallback method, device, equipment and storage medium.
  • BWP Band Width Part, bandwidth part
  • a timer can be configured for a serving cell. If no PDCCH (Physical Downlink Control Channel, physical downlink control channel) is detected in the terminal, the terminal needs to switch to the default BWP.
  • PDCCH Physical Downlink Control Channel, physical downlink control channel
  • the downlink BWP is configured separately for the terminal, multiple downlink BWPs will be included at this time, and the terminal cannot determine the default BWP based on the downlink BWP to complete the fallback. Therefore, how the terminal falls back to the default BWP is an urgent problem to be solved.
  • the embodiment of the present application provides a BWP rollback method, device, equipment, and storage medium, which solves the problem that the terminal cannot determine the default BWP based on the downlink BWP to complete the rollback, improves the accuracy of determining the default BWP, and further improves the terminal's rollback. retreat efficiency. Described technical scheme is as follows:
  • a BWP fallback method is provided, the method is executed by a first type terminal, and the method includes:
  • the terminal of the first type determines a default BWP
  • the default BWP is the target BWP that the terminal switches from the currently monitored BWP to, and the default BWP is determined according to at least one of the following methods:
  • a BWP rollback method is provided, the method is performed by a network device, and the method includes:
  • the network device determines a default BWP for communicating with the first type of terminal, where the default BWP is a target BWP to which the network device switches from the current BWP;
  • the default BWP is determined according to at least one of the following methods:
  • a BWP rollback device includes:
  • a determining module configured to determine a default BWP for the first type of terminal in response to the expiration of the first timer with the currently monitored BWP;
  • the default BWP is the target BWP that the terminal switches from the currently monitored BWP to, and the default BWP is determined according to at least one of the following methods:
  • a BWP rollback device includes:
  • the determination module is configured such that the network device determines a default BWP for communicating with the first type of terminal in response to the timer corresponding to the first type of terminal being overtime, and the default BWP is a target BWP to which the network device switches from the current BWP to;
  • the default BWP is determined according to at least one of the following methods:
  • a terminal includes: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein, the processor is configured to load and execute executable Instructions are executed to implement the BWP fallback method as described above.
  • a network device includes: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and Executable instructions are executed to implement the BWP fallback method as described above.
  • a computer-readable storage medium is provided.
  • Executable program codes are stored in the readable storage medium, and the executable program codes are loaded and executed by a processor to implement the BWP rollback method as described above.
  • a chip includes a programmable logic circuit and/or program instructions, and when the chip runs on a terminal or a network device, it is used to implement the BWP fallback method as described above.
  • an embodiment of the present application provides a computer program product, which is used to implement the BWP fallback method in the foregoing aspect when the computer program product is executed by a processor of a terminal or a network device.
  • the terminal responds to the timeout of the first timer of the currently monitored BWP, and determines according to at least one of preset rules, indication information of network equipment, and communication protocols.
  • Default BWP and then switch from the currently monitored BWP to the default BWP, which solves the problem that the terminal cannot determine the default BWP based on the downlink BWP to complete the fallback, improves the accuracy of determining the default BWP, and improves the efficiency of terminal fallback.
  • Fig. 1 shows a block diagram of a communication system provided by an exemplary embodiment of the present application.
  • Fig. 2 shows a flowchart of a BWP fallback method provided by an exemplary embodiment of the present application.
  • Fig. 3 shows a flowchart of a BWP fallback method provided by an exemplary embodiment of the present application.
  • Fig. 4 shows a block diagram of a BWP fallback device provided by an exemplary embodiment of the present application.
  • Fig. 5 shows a block diagram of a BWP fallback device provided by an exemplary embodiment of the present application.
  • Fig. 6 shows a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.
  • first, second, third, etc. may be used in this application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of the present application, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, for example, the word “if” as used herein could be interpreted as “at” or “when” or “in response to a determination.”
  • FIG. 1 shows a block diagram of a communication system provided by an exemplary embodiment of the present application.
  • the communication system may include: a terminal 10 and a network device 20 .
  • the terminal 10 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem, as well as various forms of user equipment (User Equipment, UE), mobile station ( Mobile Station, MS) and so on.
  • UE User Equipment
  • MS Mobile Station
  • the network device 20 is a device deployed in an access network to provide a wireless communication function for the terminal 10 .
  • the network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points and so on. In systems using different radio access technologies, the names of devices with network device functions may be different. For example, in 5G NR systems, they are called gNodeB or gNB.
  • the term "network equipment" may change as communications technology evolves.
  • the above-mentioned devices that provide the wireless communication function for the terminal 10 are collectively referred to as network devices.
  • a connection can be established between the network device 20 and the terminal 10 through an air interface, so as to communicate through the connection, including signaling and data interaction.
  • the number of network devices 20 may be multiple, and communication between two adjacent network devices 20 may also be performed in a wired or wireless manner.
  • the terminal 10 can switch between different network devices 20 , that is, establish connections with different network devices 20 .
  • the "5G NR system" in the embodiment of the present application may also be called a 5G system or an NR system, but those skilled in the art can understand its meaning.
  • the technical solution described in the embodiment of this application can be applied to the 5G NR system, and can also be applied to the subsequent evolution system of the 5G NR system.
  • RedCap terminal a reduced capability terminal
  • NR-lite NR-lite
  • Non-RedCap traditional terminals
  • Fig. 2 shows a flowchart of a BWP fallback method provided by an exemplary embodiment of the present application, which can be applied to the first type of terminal as shown in Fig. 1, and the method includes at least part of the following contents :
  • Step 201 The terminal of the first type determines a default BWP in response to the expiration of the first timer with the currently monitored BWP; wherein the default BWP is a target BWP to which the terminal switches from the currently monitored BWP.
  • BWP is the bandwidth configured by the network device for the first type of terminal, and the terminal will monitor the BWP to receive the downlink transmission sent by the network device based on the BWP (such as PDCCH or PDSCH (Physical Downlink Shared Channel, Physical Downlink Shared Channel) Or BCH (Broadcast Channel, broadcast channel)).
  • the downlink transmission may include downlink control signaling and/or downlink user data.
  • the first timer is used for timing, and if the time period during which the terminal of the first type monitors the BWP without performing downlink transmission exceeds the timing period of the first timer, the first timer times out. In response to the expiration of the first timer, the terminal of the first type needs to switch the monitored BWP.
  • the terminal after the terminal switches to the BWP, it detects the downlink transmission on the BWP. If the first timer of the currently monitored BWP expires, it means that the terminal is on the BWP and the first If no downlink transmission is received within the time period of the timer, it is determined to switch from the currently monitored BWP to the default BWP at this time.
  • the first type terminal When the first type terminal determines that the first timer corresponding to the currently monitored BWP expires, the first type terminal first determines a target BWP to be switched, and the target BWP may be a default BWP. Then, the terminal of the first type switches from the currently monitored BWP to the determined default BWP.
  • the default BWP is determined according to at least one of instruction information of the network device, a preset rule, and a communication protocol.
  • the preset rule is used for the terminal to determine the default BWP from the BWP pre-configured on the network device and the BWP separately configured for the terminal.
  • the indication information of the network device is used to indicate the default BWP, or indicate to determine other BWPs as the default BWP.
  • the first type of terminal may be a RedCap UE.
  • the first timer is BWP-InactivityTimer; or any other suitable timer.
  • the first type of terminal refers to one type of terminal, and it may refer to one first type of terminal, or may refer to two or more first type of terminals.
  • the second-type terminal also refers to one type of terminal, which may refer to one second-type terminal, or may refer to two or more second-type terminals.
  • the terminal determines the default BWP according to at least one of the preset rules, the indication information of the network device and the communication protocol in response to the timeout of the first timer of the currently monitored BWP, and then starts from the currently monitored BWP.
  • the monitored BWP is switched to the default BWP, which solves the problem that the first type of terminal cannot determine the default BWP based on the downlink BWP to complete the fallback, improves the accuracy of determining the default BWP, and thus improves the efficiency of terminal fallback.
  • FIG. 2 explains how the terminal switches to the default BWP, and for the network device, the network device will also determine the default BWP that the terminal needs to switch to according to whether the first timer times out, please refer to Figure 2 for details 3 shown embodiment:
  • Step 301 The network device determines a default BWP for communicating with the first type of terminal in response to the timer corresponding to the first type of terminal being overtime, and the default BWP is a target BWP to which the network device switches from the current BWP.
  • the default BWP may be determined according to at least one of preset rules and communication protocols, for example.
  • the preset rule may be that the network device determines that the first timer for the first type of terminal detecting that the corresponding BWP has no downlink transmission expires.
  • the downlink transmission may include downlink control signaling and/or downlink user data.
  • the network device may maintain a timer corresponding to the first type of terminal. If the network device does not send a downlink transmission to the first type of terminal within the time period of the maintained timer, it indicates that the network device When the maintained timer expires, the network device determines the default BWP of the corresponding first-type terminal in response to the timer expires, and then switches from the current BWP to the determined default BWP. In a possible implementation manner, the timer corresponding to the network device is different from the first timer corresponding to the first type terminal, but the first timer corresponding to the network device is different from the first timer corresponding to the first type terminal. A timer has a corresponding timing duration.
  • the manner in which the network device determines to switch to the default BWP in the embodiment of the present application is similar to the manner in the above-mentioned embodiment shown in FIG. 2 , and will not be repeated here.
  • the timer may be BWP-InactivityTimer; or any other appropriate timer.
  • the default BWP is determined, and then the currently monitored BWP is switched to the default BWP, and the network device and the first type of terminal can respectively determine
  • the default BWP is used to ensure that it corresponds to the first type of terminal, which solves the problem that the default BWP cannot be determined based on the downlink BWP to complete the fallback, improves the accuracy of determining the default BWP, and thus improves the efficiency of terminal fallback.
  • the preset rules include at least one of the following information:
  • the first uplink BWP is a bandwidth part configured by the network device for the first type of terminal.
  • the bandwidth supported by the first type of terminal is the maximum bandwidth supported by the first type of terminal.
  • the relationship between the first uplink BWP and the bandwidth supported by the first type of terminal includes: the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, or the first uplink BWP is equal to the first type terminal bandwidth.
  • the first downlink BWP is a bandwidth part configured by the network device for the first type of terminal.
  • the bandwidth supported by the first type of terminal is the maximum bandwidth supported by the first type of terminal.
  • the relationship between the first downlink BWP and the bandwidth supported by the first type of terminal includes: the first downlink BWP is smaller than the bandwidth supported by the first type of terminal, the first downlink BWP is greater than the bandwidth supported by the first type of terminal, or the first downlink BWP Equal to the first type terminal bandwidth.
  • the second downlink BWP may be used for at least one of the following functions: random access, paging, or connected state.
  • first downlink BWP supports the use of the first type of terminal and the second type of terminal
  • second downlink BWP supports the use of the first type of terminal, which also means that the second downlink BWP only supports the use of the first type of terminal, not the second type terminal use.
  • the first-type terminal and the second-type terminal are two different types of terminals, and the capability of the first-type terminal is smaller than that of the second-type terminal.
  • the first type of terminal may be called a Reduced capability (reduced capability) terminal, or NR-lite for short.
  • the second type of terminal may be an ordinary terminal (Legacy UE).
  • the first type of terminal is suitable for Internet of Things services. Due to the extensive development of services such as video surveillance, smart home, wearable devices, and industrial sensors, a transmission rate of tens to hundreds of megabytes is required. In order to propose The first type of terminal is adapted to the Internet of Things business.
  • the first type of terminal provided by the embodiment of the present application has a simple structure and low design complexity, which not only meets the requirements of covering IoT devices, but also reduces the design requirements of the terminal and expands the adaptability of the terminal.
  • the default BWP includes the following situations:
  • the first type is the default BWP configured by the network device through terminal-specific signaling.
  • the network device configures a default BWP for the terminal through terminal-specific signaling, and the terminal may determine the default BWP configured by the network device as the default BWP to be switched.
  • terminal-specific signaling is signaling sent to the first type of terminal;
  • terminal-specific signaling may be signaling dedicated to the first type of terminal, or may be It is a field domain, IE (Information Element, information element), and one or more bits (bits) dedicated to configuring RedCap terminals in existing signaling.
  • the second type When the network device does not configure the default BWP through the terminal-specific signaling, the default BWP is the first downlink BWP configured by the SIB (System Info Block, system information block).
  • SIB System Info Block, system information block
  • the network device does not configure the default BWP through terminal-specific signaling, and at this time the first type of terminal also includes the first downlink BWP configured by the SIB, then the first type of terminal can use the SIB
  • the configured first downlink BWP is determined to be the default BWP.
  • the default BWP is the first downlink BWP configured by the MIB (Master Indication Block, master information block).
  • the network device does not configure the default BWP through terminal-specific signaling, and at this time the first type of terminal also includes the first downlink BWP configured in the MIB, then the first type of terminal can use the MIB
  • the configured first downlink BWP is determined as the default BWP.
  • the fourth type in the case that the network device does not configure the default BWP through the terminal-specific signaling, the default BWP is the second downlink BWP.
  • the first type of terminal is configured with a second downlink BWP, which is suitable for the first type of terminal. If the network device does not configure the default BWP through terminal-specific signaling, the first type The terminal may determine the second downlink BWP as the default BWP. In a possible implementation manner, the second downlink BWP is a BWP specially used by the first type of terminal; the second type of terminal cannot use the second downlink BWP.
  • the default BWP is the public BWP configured on the network device.
  • the network device can configure a public BWP for the first type of terminal, that is to say, all the first type of terminal can use the public BWP, and will not configure the default BWP for the first type of terminal, then the terminal needs When switching to the default BWP, determine the public BWP configured on the network device as the default BWP.
  • the default BWP is the BWP indicated by the configuration information of the network device, and the BWP is any one of the second downlink BWP, the first downlink BWP configured by the SIB, or the first downlink BWP configured by the MIB.
  • the network device's The BWP indicated by the configuration information is determined to be the default BWP.
  • the first downlink BWP or the first downlink BWP configured with the second downlink BWP or SIB can be indicated through the indication information of the network device. Any one of the first downlink BWPs configured in the MIB is determined as the default BWP, which improves the accuracy of determining the default BWP, thereby improving the efficiency of terminal fallback.
  • the default BWP is Default BWP configured by network devices through terminal-specific signaling.
  • the network device configures the default BWP through terminal-specific signaling, and at this time the first downlink BWP is smaller than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for
  • the default BWP configured by the network device may be determined as the default BWP to be switched by the first type of terminal.
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the network device configures the default BWP through terminal-specific signaling, and at this time the first downlink BWP configured by the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP At least in the case of random access or paging, the default BWP configured by the network device may be determined as the default BWP that the first type of terminal needs to switch.
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the network device configures the default BWP through terminal-specific signaling, and at this time, the first downlink BWP configured by the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is greater than the bandwidth supported by the first type of terminal.
  • the default BWP configured by the network device may be determined as the default BWP that the first type of terminal needs to switch.
  • the network device configures the default BWP for the first type of terminal, then the terminal determines that the first uplink BWP, the first downlink BWP and the bandwidth supported by the first type of terminal meet the conditions, and the second downlink BWP also
  • the default BWP configured by the network device can be determined as the default BWP that the first type of terminal needs to switch to, which improves the accuracy of determining the default BWP, thereby improving the efficiency of terminal fallback.
  • the default BWP is The first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB.
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the first downlink BWP is less than the bandwidth supported by the first type of terminal, and the first uplink BWP is less than the bandwidth supported by the first type of terminal bandwidth, and the second downlink BWP is at least used for random access or paging, the first downlink BWP configured in the SIB or the first downlink BWP configured in the MIB is determined as the default BWP.
  • the default BWP is The first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB.
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the first downlink BWP is smaller than the bandwidth supported by the first type of terminal, and the first uplink BWP is greater than the bandwidth supported by the first type of terminal bandwidth, and the second downlink BWP is at least used for random access or paging, the first downlink BWP configured in the SIB or the first downlink BWP configured in the MIB is determined as the default BWP.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB.
  • the default BWP is the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB, and an uplink BWP corresponding to the first downlink BWP is configured.
  • the frequency division duplex mode considering whether the first type of terminal is configured with the uplink BWP corresponding to the first downlink BWP, if the default BWP is determined, it can also Realize the configuration of uplink BWP to ensure uplink transmission and improve the accuracy of transmission.
  • the default BWP is the first one configured by the SIB The first downlink BWP configured by the next downlink BWP or MIB.
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the first downlink BWP is less than the bandwidth supported by the first type of terminal, and the first uplink BWP is less than the bandwidth supported by the first type of terminal bandwidth, and the second downlink BWP is used at least in the connected state, the first downlink BWP configured in the SIB or the first downlink BWP configured in the MIB is determined as the default BWP.
  • the terminal determines that the first uplink BWP, the first downlink BWP, and the bandwidth supported by the first type of terminal meet the conditions, and When the second downlink BWP is at least used for random access or paging or connected state, the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB can be determined as the default BWP, which improves the speed of determining the default BWP. accuracy, thereby improving the efficiency of terminal fallback.
  • the first downlink BWP configured by the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured in the MIB.
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the first downlink BWP configured by the SIB is greater than the bandwidth supported by the first type of terminal, and the first uplink BWP is smaller than the first If the type terminal supports bandwidth, and the second downlink BWP is at least used for random access or paging, the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB is determined as the default BWP.
  • the default BWP is the first downlink BWP configured in the MIB.
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the first downlink BWP configured by the SIB is greater than the bandwidth supported by the first type of terminal, and the first uplink BWP is greater than the first If the type terminal supports bandwidth, and the second downlink BWP is at least used for random access or paging, the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB is determined as the default BWP.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB;
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal
  • the first uplink BWP is greater than the bandwidth supported by the first type of terminal
  • the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB
  • the uplink BWP corresponding to the first downlink BWP is configured.
  • the frequency division duplex mode considering whether the first type of terminal is configured with the uplink BWP corresponding to the first downlink BWP, if the default BWP is determined, it can also Realize the configuration of uplink BWP to ensure uplink transmission and improve the accuracy of transmission.
  • the terminal determines that the first uplink BWP, the first downlink BWP, and the bandwidth supported by the first type of terminal meet the conditions , and the second downlink BWP is also used for random access or paging, then the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB can be determined as the default BWP, which improves the efficiency of determining the default BWP Accuracy, thereby improving the efficiency of terminal fallback.
  • the default BWP is the second downlink BWP .
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the first downlink BWP is less than the bandwidth supported by the first type of terminal, and the first uplink BWP is less than the bandwidth supported by the first type of terminal bandwidth, and the second downlink BWP is used at least in the connected state, the second downlink BWP is determined as the default BWP.
  • the default BWP is the second downlink BWP .
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the first downlink BWP is smaller than the bandwidth supported by the first type of terminal, and the first uplink BWP is greater than the bandwidth supported by the first type of terminal bandwidth, and the second downlink BWP is used at least in the connected state, the second downlink BWP is determined as the default BWP.
  • the default BWP is the first Two downlink BWP.
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the first downlink BWP configured by the SIB is greater than the bandwidth supported by the first type of terminal, and the first uplink BWP is smaller than the first If the type terminal supports bandwidth, and the second downlink BWP is used at least in the connected state, the second downlink BWP is determined as the default BWP.
  • the default BWP is the second downlink BWP.
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, and after determining that the downlink BWP configured by the SIB is greater than the bandwidth supported by the terminal, the uplink BWP is greater than the bandwidth supported by the terminal, and the second downlink BWP is at least In the case of the connected state, the second downlink BWP is determined as the default BWP.
  • the terminal determines that the first uplink BWP, the first downlink BWP, and the bandwidth supported by the first type of terminal meet the conditions, and When the second downlink BWP is also used in the connected state, the second downlink BWP may be determined as the default BWP, which improves the accuracy of determining the default BWP, thereby improving the efficiency of terminal fallback.
  • the default BWP is Public BWP for network device configuration.
  • the network device does not configure the default BWP for the first type of terminal through terminal-specific signaling, but the network device can configure the public BWP for the first type of terminal, and after determining that the first downlink BWP is less than the first type of terminal supports When the bandwidth and the first uplink BWP are greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging, the common BWP is determined as the default BWP.
  • the default BWP is the public BWP configured on the network device.
  • the network device does not configure a default BWP for the first type of terminal through terminal-specific signaling, but the network device can configure a public BWP for the first type of terminal, and after determining that the first downlink BWP is greater than the first type of terminal supports When the bandwidth and the first uplink BWP are smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging, the common BWP is determined as the default BWP.
  • the default BWP is the public BWP configured on the network device.
  • the network device does not configure a default BWP for the first type of terminal through terminal-specific signaling, but the network device can configure a public BWP for the first type of terminal, and after determining that the first downlink BWP is greater than the first type of terminal supports When the bandwidth and the first uplink BWP are greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging, the common BWP is determined as the default BWP.
  • the terminal determines the first uplink BWP, the second When the downlink BWP and the bandwidth supported by the first type of terminal meet the conditions, and the second downlink BWP is also used for random access or paging, the public BWP can be determined as the default BWP, which improves the accuracy of determining the default BWP , thereby improving the efficiency of terminal fallback.
  • Fig. 4 shows a block diagram of a BWP fallback device provided by an exemplary embodiment of the present application.
  • the device includes:
  • the determining module 401 is configured to determine a default BWP for the terminal of the first type in response to the expiration of the first timer of the currently monitored BWP; wherein the default BWP is a target BWP to which the terminal switches from the currently monitored BWP.
  • the apparatus shown in FIG. 4 is applied to a first type terminal.
  • the first type of terminal may be a RedCap UE.
  • the default BWP is determined according to at least one of indication information, preset rules, and communication protocols.
  • the preset rules include at least one of the following information:
  • the first downlink BWP supports the first type of terminal and the second type of terminal
  • the second downlink BWP supports the first type of terminal
  • the capability of the first type of terminal is smaller than that of the second type of terminal.
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the default BWP is the first downlink BWP configured by the system information block SIB;
  • the default BWP is the first downlink BWP configured for the main information block MIB.
  • the default BWP is the second downlink BWP.
  • the default BWP is a public BWP configured by the network device.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the first downlink BWP when the first downlink BWP is smaller than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured in the SIB or the first downlink BWP configured in the MIB.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured in the SIB or the first downlink BWP configured in the MIB.
  • the default BWP is SIB The configured first downlink BWP or the first downlink BWP configured by the MIB.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB, and an uplink BWP corresponding to the first downlink BWP is configured.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal
  • the first uplink BWP is greater than the bandwidth supported by the first type of terminal
  • the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB
  • the uplink BWP corresponding to the first downlink BWP is configured.
  • the default BWP is the second Two downlink BWP.
  • the default BWP is the first Two downlink BWP.
  • the first downlink BWP configured by the SIB when the first downlink BWP configured by the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is used at least in the connected state, the default The BWP is the second downlink BWP.
  • the default BWP is the second downlink BWP.
  • the default BWP is the BWP indicated by the configuration information of the network device, and the BWP is any one of the second downlink BWP, the first downlink BWP configured by the SIB, or the first downlink BWP configured by the MIB.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the public BWP configured on the network device.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the public BWP configured on the network device.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the public BWP configured on the network device.
  • the first timer is BWP-InactivityTimer; or any other appropriate timer.
  • the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to the needs.
  • the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the device and the method embodiment provided by the above embodiment belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.
  • Fig. 5 shows a block diagram of a BWP fallback device provided by an exemplary embodiment of the present application. Referring to Fig. 5, the device includes:
  • the determining module 501 is configured to determine a default BWP of the first type of terminal by the network device in response to the expiration of the timer corresponding to the first type of terminal, where the default BWP is a target BWP to which the network device switches from the currently monitored BWP.
  • the apparatus shown in FIG. 5 is applied to a network device.
  • the default BWP is determined according to at least one of preset rules and communication protocols.
  • the preset rules include at least one of the following information:
  • the first downlink BWP supports the first type of terminal and the second type of terminal
  • the second downlink BWP supports the first type of terminal
  • the capability of the first type of terminal is smaller than that of the second type of terminal.
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the default BWP is the first downlink BWP configured by the SIB.
  • the default BWP is the first downlink BWP configured in the MIB.
  • the default BWP is the second downlink BWP.
  • the default BWP is a public BWP configured by the network device.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the default BWP configured by the network device through terminal-specific signaling.
  • the first downlink BWP when the first downlink BWP is smaller than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured in the SIB or the first downlink BWP configured in the MIB.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured in the SIB or the first downlink BWP configured in the MIB.
  • the default BWP is SIB The configured first downlink BWP or the first downlink BWP configured by the MIB.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured in the SIB or the first downlink BWP configured in the MIB.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the first downlink BWP configured by the SIB or the first downlink BWP configured by the MIB, and an uplink BWP corresponding to the first downlink BWP is configured.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal
  • the first uplink BWP is greater than the bandwidth supported by the first type of terminal
  • the second downlink BWP is at least used for random access or paging
  • the default BWP is the first downlink BWP configured in the MIB
  • the uplink BWP corresponding to the first downlink BWP is configured.
  • the default BWP is the second Two downlink BWP.
  • the default BWP is the second Two downlink BWP.
  • the first downlink BWP configured by the SIB when the first downlink BWP configured by the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is used at least in the connected state, the default The BWP is the second downlink BWP.
  • the default BWP is the second downlink BWP.
  • the default BWP is the BWP indicated by the configuration information of the network device, and the BWP is any one of the second downlink BWP, the first downlink BWP configured by the SIB, or the first downlink BWP configured by the MIB.
  • the first downlink BWP when the first downlink BWP is less than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging,
  • the default BWP is the public BWP configured on the network device.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is smaller than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the public BWP configured on the network device.
  • the first downlink BWP configured in the SIB is greater than the bandwidth supported by the first type of terminal, the first uplink BWP is greater than the bandwidth supported by the first type of terminal, and the second downlink BWP is at least used for random access or paging
  • the default BWP is the public BWP configured on the network device.
  • the timer may be BWP-InactivityTimer; or any other appropriate timer.
  • the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to the needs.
  • the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the device and the method embodiment provided by the above embodiment belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.
  • FIG. 6 shows a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application, where the communication device includes: a processor 601 , a receiver 602 , a transmitter 603 , a memory 604 and a bus 605 .
  • the processor 601 includes one or more processing cores, and the processor 601 executes various functional applications and information processing by running software programs and modules.
  • the receiver 602 and the transmitter 603 can be realized as a communication component, and the communication component can be a communication chip.
  • the memory 604 is connected to the processor 601 through a bus 605 .
  • the memory 604 may be used to store at least one program code, and the processor 601 is used to execute the at least one program code, so as to implement various steps in the foregoing method embodiments.
  • Memory 604 can be realized by any type of volatile or nonvolatile storage device or their combination, volatile or nonvolatile storage device includes but not limited to: magnetic disk or optical disk, electrically erasable programmable read-only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Static Anytime Access Memory (SRAM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Programmable Read Only Memory (PROM).
  • EEPROM electrically erasable programmable read-only Memory
  • EPROM Erasable Programmable Read Only Memory
  • SRAM Static Anytime Access Memory
  • ROM Read Only Memory
  • Magnetic Memory Magnetic Memory
  • Flash Memory Programmable Read Only Memory
  • a computer-readable storage medium is also provided, and executable program code is stored in the readable storage medium, and the executable program code is loaded and executed by a processor to implement the implementation of each of the above methods.
  • the example provides a BWP fallback method executed by a communication device.
  • a chip in an exemplary embodiment, includes a programmable logic circuit and/or program instructions, and when the chip is run on a terminal or a network device, it is used to implement the method as provided in each method embodiment.
  • BWP fallback method when the chip is run on a terminal or a network device, it is used to implement the method as provided in each method embodiment.
  • a computer program product is provided, and when the computer program product is executed by a processor of a terminal or a network device, it is used to implement the BWP fallback method provided by the above method embodiments.
  • the program can be stored in a computer-readable storage medium.
  • the above-mentioned The storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk, and the like.

Landscapes

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

Abstract

本申请公开了一种BWP回退方法、装置、设备及存储介质，涉及移动通信领域。该方法包括：终端响应于与当前所监测的BWP的第一定时器超时，第一类型终端确定默认BWP；其中，默认BWP为终端从当前所监测的BWP切换至的目标BWP，默认BWP根据以下的至少一种方式确定：预设规则，网络设备的指示信息，以及，通信协议，本申请解决了终端无法基于下行BWP确定默认BWP以完成回退的问题，提高了确定默认BWP的准确性，进而提高终端回退的效率。

Description

BWP回退方法、装置、设备及存储介质 技术领域
本申请涉及移动通信领域，特别涉及一种BWP(Band Width Part，带宽部分)回退方法、装置、设备及存储介质。
背景技术
在NR(New Radio，新空口)系统中，对于一个服务小区来说，可以配置一个定时器，若终端在切换至某个带宽部分(Band Width Part，BWP)上，且在该BWP规定的时长内未检测到PDCCH(Physical Downlink Control Channel，物理下行控制信道)，则终端需要切换到默认BWP上。
但是，若为终端单独配置了下行BWP，此时会包括多个下行BWP，终端无法基于下行BWP确定默认BWP以完成回退，因此终端如何回退至默认BWP是亟需解决的问题。
发明内容
本申请实施例提供了一种BWP回退方法、装置、设备及存储介质，解决了终端无法基于下行BWP确定默认BWP以完成回退的问题，提高了确定默认BWP的准确性，进而提高终端回退的效率。所述技术方案如下：
根据本申请的一个方面，提供了一种BWP回退方法，所述方法由第一类型终端执行，方法包括：
响应于与当前所监测的BWP的第一定时器超时，第一类型终端确定默认BWP；
其中，所述默认BWP为所述终端从当前所监测的BWP切换至的目标BWP，所述默认BWP根据以下的至少一种方式确定：
预设规则，
网络设备的指示信息，以及，
通信协议。
根据本申请的一个方面，提供了一种BWP回退方法，所述方法由网络设备 执行，方法包括：
响应于对应于第一类型终端的定时器超时，网络设备确定与第一类型终端进行通信的默认BWP，默认BWP为网络设备从当前BWP切换至的目标BWP；
其中，所述默认BWP根据以下至少一种方式确定：
预设规则，以及，
通信协议。
根据本申请的一个方面，提供了一种BWP回退装置，装置包括：
确定模块，被配置为响应于与当前所监测的BWP的第一定时器超时，第一类型终端确定默认BWP；
其中，所述默认BWP为所述终端从当前所监测的BWP切换至的目标BWP，所述默认BWP根据以下的至少一种方式确定：
预设规则，
网络设备的指示信息，以及，
通信协议。
根据本申请的一个方面，提供了一种BWP回退装置，装置包括：
确定模块，被配置为响应于对应于第一类型终端的定时器超时，网络设备确定与第一类型终端进行通信的默认BWP，默认BWP为网络设备从当前BWP切换至的目标BWP；
其中，所述默认BWP根据以下至少一种方式确定：
预设规则，以及，
通信协议。
根据本申请的一个方面，提供了一种终端，终端包括：处理器；与处理器相连的收发器；用于存储处理器的可执行指令的存储器；其中，处理器被配置为加载并执行可执行指令以实现如上述方面的BWP回退方法。
根据本申请的一个方面，提供了一种网络设备，网络设备包括：处理器；与处理器相连的收发器；用于存储处理器的可执行指令的存储器；其中，处理器被配置为加载并执行可执行指令以实现如上述方面的BWP回退方法。
根据本申请的一个方面，提供了一种计算机可读存储介质，可读存储介质中存储有可执行程序代码，可执行程序代码由处理器加载并执行以实现如上述方面的BWP回退方法。
根据本申请的一个方面，提供了一种芯片，芯片包括可编程逻辑电路和/或 程序指令，当芯片在终端或网络设备上运行时，用于实现如上述方面的BWP回退方法。
根据本申请的一个方面，本申请实施例提供了一种计算机程序产品，当计算机程序产品被终端或网络设备的处理器执行时，其用于实现上述方面的BWP回退方法。
本申请实施例提供的技术方案至少包括如下有益效果：
本申请实施例提供的方法、装置、设备及存储介质，终端响应于与当前所监测的BWP的第一定时器超时，根据预设规则、网络设备的指示信息和通信协议中的至少一种确定默认BWP，再从当前所监测的BWP切换至默认BWP，解决了终端无法基于下行BWP确定默认BWP以完成回退的问题，提高了确定默认BWP的准确性，进而提高终端回退的效率。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出了本申请一个示例性实施例提供的通信系统的框图。
图2示出了本申请一个示例性实施例提供的BWP回退方法的流程图。
图3示出了本申请一个示例性实施例提供的BWP回退方法的流程图。
图4示出了本申请一个示例性实施例提供的BWP回退装置的框图。
图5示出了本申请一个示例性实施例提供的BWP回退装置的框图。
图6示出了本申请一个示例性实施例提供的通信设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装 置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也是旨在包括多数形式，除非上下文清楚地表示其它含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，例如，在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
下面，对本申请的应用场景进行说明：
图1示出了本申请一个示例性实施例提供的通信系统的框图，该通信系统可以包括：终端10和网络设备20。
终端10的数量通常为多个，每一个网络设备20所管理的小区内可以分布一个或多个终端10。终端10可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(User Equipment，UE)、移动台(Mobile Station，MS)等等。为方便描述，本申请实施例中，上面提到的设备统称为终端。
网络设备20是一种部署在接入网中用以为终端10提供无线通信功能的装置。网络设备20可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具备网络设备功能的设备的名称可能会有所不同，例如在5G NR系统中，称为gNodeB或者gNB。随着通信技术的演进，“网络设备”这一名称可能会变化。为方便描述，本申请实施例中，上述为终端10提供无线通信功能的装置统称为网络设备。网络设备20与终端10之间可以通过空口建立连接，从而通过该连接进行通信，包括信令和数据的交互。网络设备20的数量可以有多个，两个邻近的网络设备20之间也可以通过有线或者无线的方式进行通信。终端10可以在不同的网络设备20之间进行切换，也即与不同的网络设备20建立连接。
本申请实施例中的“5G NR系统”也可以称为5G系统或者NR系统，但本领域技术人员可以理解其含义。本申请实施例描述的技术方案可以适用于5G  NR系统，也可以适用于5G NR系统后续的演进系统。
随着通信技术的发展，为了适应新的通信场景，相关技术中提出了能力降低(Reduced capability)终端，简称RedCap终端，也可以称作NR-lite，这种终端一般需要满足低造价、低复杂度，一定程度的增强覆盖，功率节省等条件。相比较RedCap终端，普通的终端被称为非RedCap(Non-RedCap)终端或是传统终端(legacy UE)存在一定区别。
图2示出了本申请一个示例性实施例提供的BWP回退方法的流程图，示例性的可以应用于如图1所示的第一类型终端中，该方法包括以下内容中的至少部分内容：
步骤201：第一类型终端响应于与当前所监测的BWP的第一定时器超时，第一类型终端确定默认BWP；其中默认BWP为终端从当前所监测的BWP切换至的目标BWP。
其中，BWP为网络设备为第一类型终端配置的带宽，终端会监测BWP以接收网络设备基于该BWP发送的下行传输(例如PDCCH或物理下行共享信道PDSCH(Physical Downlink Shared Channel，物理下行共享信道)或BCH(Broadcast Channel，广播信道))。其中，下行传输(Downlink Transmission)可以包括下行控制信令和/下行用户数据。另外，第一定时器用于计时，若第一类型终端监测BWP未进行下行传输的时长超过第一定时器的定时时长，则第一定时器超时。响应于第一定时器超时，第一类型终端需要切换监测的BWP。
在本申请实施例中，终端切换至BWP后，检测BWP上的下行传输，若第一类型终端在与当前所监测的BWP的第一定时器超时的情况下，说明在该BWP上且第一定时器的定时时长内未接收到下行传输，此时确定从当前所监测的BWP切换至默认BWP。
第一类型终端在确定与当前所监测的BWP对应的第一定时器超时的情况下，则第一类型终端先确定待切换的目标BWP，该目标BWP可以为默认BWP。然后，第一类型终端从当前所监测的BWP切换至确定的默认BWP。
其中，默认BWP根据网络设备的指示信息、预设规则、通信协议之中的至少一个确定。
该预设规则用于终端从网络设备预先配置的BWP和为终端单独配置的BWP中确定默认BWP。网络设备的指示信息用于指示默认BWP，或者指示将 其他BWP确定为默认BWP。
在本公开实施例中，该第一类型终端可以为RedCap UE。
在一些实施例中，第一定时器为BWP-InactivityTimer；或是其他任何恰当的定时器。
需要说明的是，本公开实施例中，第一类型终端是指一个类型的终端，其可以指代一个第一类型的终端，也可以指代两个或两个以上第一类型的终端。同样的，第二类型终端也是指一个类型的终端，其可以指代一个第二类型的终端，也可以指代两个或两个以上第二类型的终端。
本申请实施例提供的方法，终端响应于与当前所监测的BWP的第一定时器超时，根据预设规则、网络设备的指示信息和通信协议中的至少一种确定默认BWP，再从当前所监测的BWP切换至默认BWP，解决了第一类型终端无法基于下行BWP确定默认BWP以完成回退的问题，提高了确定默认BWP的准确性，进而提高终端回退的效率。
图2所示的实施例对终端如何切换至默认BWP进行说明，而对于网络设备来说，网络设备也会根据第一定时器是否超时，来确定终端需要切换至的默认BWP，具体请参见图3所示实施例：
步骤301：网络设备响应于对应于第一类型终端的定时器超时，网络设备确定与第一类型终端进行通信的默认BWP，默认BWP为网络设备从当前BWP切换至的目标BWP。
其中，默认BWP可以示例性的根据预设规则、通信协议中的至少一个确定。
示例性的，该预设规则可以为网络设备确定第一类型终端检测对应的BWP没有下行传输的第一定时器超时。其中，下行传输可以包括下行控制信令和/或下行用户数据。
在一种可能的实现方式中，网络设备可以维护一个与第一类型终端对应的定时器，若网络设备在维护的定时器的定时时长内未向第一类型终端发送下行传输，则说明网络设备维护的定时器超时，则网络设备响应于该定时器超时，网络设备确定对应的第一类型终端的默认BWP，进而从当前BWP切换至确定的默认BWP。在一种可能的实现方式中，网络设备对应的定时器与第一类型终端对应的第一定时器为不同的定时器，但是该网络设备对应的第一定时器与第一类型终端对应的第一定时器具有相对应的计时时长。
本申请实施例中网络设备确定切换至默认BWP的方式与上述图2所示实施例的方式类似，在此不再赘述。
在一些实施例中，该定时器可以为BWP-InactivityTimer；或是其他任何恰当的定时器。
本申请实施例提供的方法，在网络设备确定对应于第一类型终端的定时器超时时确定默认BWP，再从当前所监测的BWP切换至默认BWP，网络设备会可以与第一类型终端各自确定默认BWP，以保证与第一类型终端对应，解决了无法基于下行BWP确定默认BWP以完成回退的问题，提高了确定默认BWP的准确性，进而提高终端回退的效率。
在图2和图3所示实施例的基础上，对预设规则所包括的信息进行说明。其中，预设规则包括以下至少一项信息：
(1)第一上行BWP与第一类型终端支持带宽之间的关系。
其中，第一上行BWP为网络设备为第一类型终端配置的带宽部分。第一类型终端支持带宽为第一类型终端所支持的最大带宽。
该第一上行BWP与第一类型终端支持带宽之间的关系包括：第一上行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽或第一上行BWP等于第一类型终端带宽。
(2)第一下行BWP与第一类型终端支持带宽之间的关系。
其中，第一下行BWP为网络设备为第一类型终端配置的带宽部分。第一类型终端支持带宽为第一类型终端所支持的最大带宽。
该第一下行BWP与第一类型终端支持带宽之间的关系包括：第一下行BWP小于第一类型终端支持带宽、第一下行BWP大于第一类型终端支持带宽或第一下行BWP等于第一类型终端带宽。
(3)第二下行BWP的作用。
其中，第二下行BWP可以用于以下的至少一种作用：随机接入、寻呼、或连接态。
另外，第一下行BWP支持第一类型终端和第二类型终端使用，第二下行BWP支持第一类型终端使用，也说明第二下行BWP只支持第一类型终端使用，而不支持第二类型终端使用。该第一类型终端和第二类型终端为两种不同类型的终端，第一类型终端的能力小于第二类型终端的能力。
在一些可能的实现方式中，该第一类型终端可以称为Reduced capability(能力缩减)终端，也可以简称NR-lite。该第二类型终端可以为普通终端(Legacy UE)。
在一些实施例中，该第一类型终端适用于物联网业务，由于视频监控、智能家居、可穿戴设备和工业传感器等业务的广泛发展，要求几十到几百兆的传输速率，为了提出了第一类型终端以适应该物联网业务。
本申请实施例提供的第一类型终端的结构简单，设计复杂度低，既满足覆盖物联网设备的要求，也降低了终端的设计需求，扩展了终端的适配性。
需要说明的是，上述实施例可以拆分为新实施例，或与其他实施例互相组合为新实施例，本申请对实施例之间的组合不做限定。
在图2或图3所示的实施例中，默认BWP包括以下情况：
第一种：默认BWP为网络设备通过终端专属信令配置的默认BWP。
其中，网络设备通过终端专属信令为终端配置默认BWP，则终端可以将网络设备配置的默认BWP确定为需要切换的默认BWP。在本公开的所有实施例中，“终端专属信令”是发送给第一类型终端的信令；“终端专属信令”可以是专用于第一类型终端这一类型终端的信令，也可以是一个已有信令中专用于配置RedCap终端的字段域、IE(Information Element，信息元素)、一个或多个比特(bit)。
第二种：在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为SIB(System Info Block，系统信息块)配置的第一下行BWP。
在本申请实施例中，还存在网络设备不通过终端专属信令配置默认BWP的情况，而此时第一类型终端还包括SIB配置的第一下行BWP，则第一类型终端可以将该SIB配置的第一下行BWP确定为默认BWP。
第三种：在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为MIB(Master Indication Block，主信息块)配置的第一下行BWP。
在本申请实施例中，还存在网络设备不通过终端专属信令配置默认BWP的情况，而此时第一类型终端还包括MIB配置的第一下行BWP，则第一类型终端可以将该MIB配置的第一下行BWP确定为默认BWP。
第四种：在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为第二下行BWP。
在本申请实施例中，第一类型终端配置有第二下行BWP，该第二下行BWP适用于第一类型终端，若出现网络设备不通过终端专属信令配置默认BWP的情况，则第一类型终端可以将第二下行BWP确定为默认BWP。在一种可能的实现方式中，第二下行BWP是专门供第一类型终端使用的BWP；第二类型终端不能使用该第二下行BWP。
第五种：在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为网络设备配置的公共BWP。
在本申请实施例中，网络设备可以为第一类型终端配置公共BWP，也就是说所有的第一类型终端均可以使用该公共BWP，而不会为第一类型终端配置默认BWP，则终端需要切换至默认BWP时，将网络设备配置的公共BWP确定为默认BWP。
第六种：默认BWP为网络设备的配置信息指示的BWP，BWP为第二下行BWP、SIB配置的第一下行BWP或MIB配置的第一下行BWP中的任一种。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，将网络设备的配置信息指示的BWP确定为默认BWP。
本申请实施例提供的方法，在网络设备未通过终端专属信令为第一类型终端配置默认BWP，则可以通过网络设备的指示信息指示将第二下行BWP、SIB配置的第一下行BWP或MIB配置的第一下行BWP中的任一种确定为默认BWP，提高了确定默认BWP的准确性，进而提高终端回退的效率。
需要说明的是，上述实施例可以拆分为新实施例，或与其他实施例互相组合为新实施例，本申请对实施例之间的组合不做限定。
在上述已说明默认BWP包括上述六种情况的前提下，对出现每种情况的条件进行说明；当然，这些情况并不是穷举，本领域内技术人员可以根据本公开的技术方案进行适应性调整：
针对出现上述实施例的第一种情况进行说明：
(1)在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
其中，网络设备通过终端专属信令配置了默认BWP，而此时第一下行BWP 小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，则可以将网络设备配置的默认BWP确定为第一类型终端需要切换的默认BWP。
(2)在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
其中，网络设备通过终端专属信令配置了默认BWP，而此时SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，则可以将网络设备配置的默认BWP确定为第一类型终端需要切换的默认BWP。
(3)在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
其中，网络设备通过终端专属信令配置了默认BWP，而此时SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，则可以将网络设备配置的默认BWP确定为第一类型终端需要切换的默认BWP。
需要说明的是，上述实施例可以拆分为新实施例，或与其他实施例互相组合为新实施例，本申请对实施例之间的组合不做限定。
本申请实施例提供的方法，网络设备为第一类型终端配置了默认BWP，则在终端确定第一上行BWP、第一下行BWP与第一类型终端支持带宽满足条件，且第二下行BWP也用于随机接入或寻呼的情况下，则可以将网络设备配置的默认BWP确定为第一类型终端需要切换的默认BWP，提高了确定默认BWP的准确性，进而提高终端回退的效率。
在上述已说明默认BWP包括上述六种情况的前提下，对出现每种情况的条件进行说明：
针对出现上述实施例的第二种和第三种情况进行说明：
(1)在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，将SIB配置的第一下行BWP或MIB配置的第一下行BWP确定为默认BWP。
(2)在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，将SIB配置的第一下行BWP或MIB配置的第一下行BWP确定为默认BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在另一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
本申请实施例中，按照频分双工模式或时分双工模式的不同，考虑第一类型终端是否配置与第一下行BWP对应的上行BWP，在保证确定了默认BWP的情况下，还能实现配置上行BWP以保证上行传输，提高了传输的准确性。
(3)在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，将SIB配置的第一下行BWP或MIB配置的第一下行BWP确定为默认BWP。
本申请实施例提供的方法，网络设备未通过终端专属信令为第一类型终端配置默认BWP，则在终端确定第一上行BWP、第一下行BWP与第一类型终端 支持带宽满足条件，且第二下行BWP至少用于随机接入或寻呼或连接态的情况下，则可以将SIB配置的第一下行BWP或MIB配置的第一下行BWP确定为默认BWP，提高了确定默认BWP的准确性，进而提高终端回退的效率。
需要说明的是，上述实施例可以拆分为新实施例，或与其他实施例互相组合为新实施例，本申请对实施例之间的组合不做限定。
在上述已说明默认BWP包括上述六种情况的前提下，对出现每种情况的条件进行说明：
针对出现上述实施例的第三种情况进行说明：
(1)在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为MIB配置的第一下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，将SIB配置的第一下行BWP或MIB配置的第一下行BWP确定为默认BWP。
(2)在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为MIB配置的第一下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，将SIB配置的第一下行BWP或MIB配置的第一下行BWP确定为默认BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，默认BWP为MIB配置的第一下行BWP；
在另一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随 机接入或寻呼的情况下，对于时分双工模式，默认BWP为MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
本申请实施例中，按照频分双工模式或时分双工模式的不同，考虑第一类型终端是否配置与第一下行BWP对应的上行BWP，在保证确定了默认BWP的情况下，还能实现配置上行BWP以保证上行传输，提高了传输的准确性。
另外，本申请实施例提供的方法，网络设备未通过终端专属信令为第一类型终端配置默认BWP，则在终端确定第一上行BWP、第一下行BWP与第一类型终端支持带宽满足条件，且第二下行BWP也用于随机接入或寻呼的情况下，则可以将SIB配置的第一下行BWP或MIB配置的第一下行BWP确定为默认BWP，提高了确定默认BWP的准确性，进而提高终端回退的效率。
需要说明的是，上述实施例可以拆分为新实施例，或与其他实施例互相组合为新实施例，本申请对实施例之间的组合不做限定。
在上述已说明默认BWP包括上述六种情况的前提下，对出现每种情况的条件进行说明：
针对出现上述实施例的第四种情况进行说明：
(1)在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，将第二下行BWP确定为默认BWP。
(2)在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，将第二下行BWP确定为默认BWP。
(3)在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行 BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，将第二下行BWP确定为默认BWP。
(4)在SIB配置的下行BWP大于终端支持带宽、上行BWP大于终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，并且在确定SIB配置的下行BWP大于终端支持带宽、上行BWP大于终端支持带宽，且第二下行BWP至少用于连接态的情况下，将第二下行BWP确定为默认BWP。
本申请实施例提供的方法，网络设备未通过终端专属信令为第一类型终端配置默认BWP，则在终端确定第一上行BWP、第一下行BWP与第一类型终端支持带宽满足条件，且第二下行BWP也用于连接态的情况下，则可以将第二下行BWP确定为默认BWP，提高了确定默认BWP的准确性，进而提高终端回退的效率。
需要说明的是，上述实施例可以拆分为新实施例，或与其他实施例互相组合为新实施例，本申请对实施例之间的组合不做限定。
在上述已说明默认BWP包括上述五种情况的前提下，对出现每种情况的条件进行说明：
针对出现上述实施例的第六种情况进行说明：
(1)在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，但是网络设备可以为第一类型终端配置公共BWP，在确定第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，将公共BWP确定为默认BWP。
(2)在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，但是网络设备可以为第一类型终端配置公共BWP，在确定第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，将公共BWP确定为默认BWP。
(3)在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在本申请实施例中，网络设备未通过终端专属信令为第一类型终端配置默认BWP，但是网络设备可以为第一类型终端配置公共BWP，在确定第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，将公共BWP确定为默认BWP。
本申请实施例提供的方法，在网络设备未通过终端专属信令为第一类型终端配置默认BWP，但是网络设备为第一类型终端配置公共BWP的情况下，在终端确定第一上行BWP、第一下行BWP与第一类型终端支持带宽满足条件，且第二下行BWP也用于随机接入或寻呼的情况下，则可以将公共BWP确定为默认BWP，提高了确定默认BWP的准确性，进而提高终端回退的效率。
需要说明的是，上述实施例可以拆分为新实施例，或与其他实施例互相组合为新实施例，本申请对实施例之间的组合不做限定。
图4示出了本申请一个示例性实施例提供的BWP回退装置的框图，参见图4，该装置包括：
确定模块401，被配置为响应于与当前所监测的BWP的第一定时器超时，第一类型终端确定默认BWP；其中默认BWP为终端从当前所监测的BWP切换至的目标BWP。
在本公开实施例中，如图4所示的装置应用于第一类型终端。在一些可能的方式中，该第一类型终端可以为RedCap UE。
其中，默认BWP根据指示信息、预设规则、通信协议之中的至少之一确定。
在一些实施例中，预设规则包括以下至少一项信息：
第一上行BWP与第一类型终端支持带宽之间的关系、第一下行BWP与第一类型终端支持带宽之间的关系以及第二下行BWP的作用；
其中，第一下行BWP支持第一类型终端和第二类型终端使用，第二下行BWP支持第一类型终端使用，第一类型终端的能力小于第二类型终端的能力。
在一些实施例中，默认BWP为网络设备通过终端专属信令配置的默认BWP。
在一些实施例中，在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为系统信息块SIB配置的第一下行BWP；
在一些实施例中，在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为主信息块MIB配置的第一下行BWP。
在一些实施例中，在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为第二下行BWP。
在一些实施例中，在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为网络设备配置的公共BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼 的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为MIB配置的第一下行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为MIB配置的第一下行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，默认BWP为MIB配置的第一下行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，默认BWP为MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下， 默认BWP为第二下行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在一些实施例中，在SIB配置的下行BWP大于终端支持带宽、上行BWP大于终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在一些实施例中，默认BWP为网络设备的配置信息指示的BWP，BWP为第二下行BWP、SIB配置的第一下行BWP或MIB配置的第一下行BWP中的任一种。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在一些实施例中，该第一定时器为BWP-InactivityTimer；或是其他任何恰当的定时器。
需要说明的是，上述实施例提供的装置，在实现其功能时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置与方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图5示出了本申请一个示例性实施例提供的BWP回退装置的框图，参见图5，该装置包括：
确定模块501，被配置为响应于对应于第一类型终端的定时器超时，网络设备确定第一类型终端的默认BWP，默认BWP为网络设备从当前所监测的BWP 切换至的目标BWP。
在本公开实施例中，如图5所示的装置应用于网络设备。
其中，默认BWP根据预设规则、通信协议中的至少之一确定。
在一些实施例中，预设规则包括以下至少一项信息：
第一上行BWP与第一类型终端支持带宽之间的关系、第一下行BWP与第一类型终端支持带宽之间的关系以及第二下行BWP的作用；
其中，第一下行BWP支持第一类型终端和第二类型终端使用，第二下行BWP支持第一类型终端使用，第一类型终端的能力小于第二类型终端的能力。
在一些实施例中，默认BWP为网络设备通过终端专属信令配置的默认BWP。
在一些实施例中，在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为SIB配置的第一下行BWP。
在一些实施例中，在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为MIB配置的第一下行BWP。
在一些实施例中，在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为第二下行BWP。
在一些实施例中，在网络设备未通过终端专属信令配置默认BWP的情况下，默认BWP为网络设备配置的公共BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备通过终端专属信令配置的默认BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为MIB配置的第一下行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为MIB配置的第一下行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，默认BWP为MIB配置的第一下行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，默认BWP为MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在一些实施例中，在SIB配置的下行BWP大于第一类型终端支持带宽、上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，默认BWP为第二下行BWP。
在一些实施例中，默认BWP为网络设备的配置信息指示的BWP，BWP为第二下行BWP、SIB配置的第一下行BWP或MIB配置的第一下行BWP中的任一种。
在一些实施例中，在第一下行BWP小于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP小于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在一些实施例中，在SIB配置的第一下行BWP大于第一类型终端支持带宽、第一上行BWP大于第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，默认BWP为网络设备配置的公共BWP。
在一些实施例中，该定时器可以为BWP-InactivityTimer；或是其他任何恰当的定时器。
需要说明的是，上述实施例提供的装置，在实现其功能时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置与方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图6示出了本申请一个示例性实施例提供的通信设备的结构示意图，该通信设备包括：处理器601、接收器602、发射器603、存储器604和总线605。
处理器601包括一个或者一个以上处理核心，处理器601通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器602和发射器603可以实现为一个通信组件，该通信组件可以是一块通信芯片。
存储器604通过总线605与处理器601相连。
存储器604可用于存储至少一个程序代码，处理器601用于执行该至少一个程序代码，以实现上述方法实施例中的各个步骤。
此外，通信设备可以为终端或网络设备。存储器604可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，静态随时存取存储器(SRAM)，只读存储器(ROM)，磁存储器，快闪存储器，可编程只读存储器(PROM)。
在示例性实施例中，还提供了一种计算机可读存储介质，所述可读存储介质中存储有可执行程序代码，所述可执行程序代码由处理器加载并执行以实现上述各个方法实施例提供的由通信设备执行的BWP回退方法。
在示例性实施例中，提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片在终端或网络设备上运行时，用于实现如各个方法实施例提供的BWP回退方法。
在示例性实施例中，提供了计算机程序产品，当所述计算机程序产品被终端或网络设备的处理器执行时，其用于实现上述各个方法实施例提供的BWP回退方法。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (34)

  1. 一种BWP回退方法，其特征在于，所述方法由第一类型终端执行，所述方法包括：
    响应于与当前所监测的BWP的第一定时器超时，第一类型终端确定默认BWP；
    其中，所述默认BWP为所述终端从当前所监测的BWP切换至的目标BWP，所述默认BWP根据以下的至少一种方式确定：
    预设规则，
    网络设备的指示信息，以及，
    通信协议。
  2. 根据权利要求1所述的方法，其特征在于，所述预设规则包括以下至少一项信息：
    第一上行BWP与所述第一类型终端支持带宽之间的关系、第一下行BWP与所述第一类型终端支持带宽之间的关系以及第二下行BWP的作用；
    其中，所述第一下行BWP支持第一类型终端和第二类型终端使用，所述第二下行BWP支持所述第一类型终端使用，所述第一类型终端的能力小于第二类型终端的能力。
  3. 根据权利要求1或2所述的方法，其特征在于，所述默认BWP为网络设备通过终端专属信令配置的默认BWP。
  4. 根据权利要求1或2所述的方法，其特征在于，在所述网络设备未通过终端专属信令配置默认BWP的情况下，所述默认BWP为系统信息块SIB配置的第一下行BWP；
    或者，
    在所述网络设备未通过终端专属信令配置默认BWP的情况下，所述默认BWP为主信息块MIB配置的第一下行BWP。
  5. 根据权利要求1或2所述的方法，其特征在于，在所述网络设备未通过终端专属信令配置默认BWP的情况下，所述默认BWP为第二下行BWP。
  6. 根据权利要求1或2所述的方法，其特征在于，在所述网络设备未通过终端专属信令配置默认BWP的情况下，所述默认BWP为所述网络设备配置的公共BWP。
  7. 根据权利要求1或2所述的方法，其特征在于，所述默认BWP为所述网络设备的配置信息指示的BWP，所述BWP为第二下行BWP、SIB配置的第一下行BWP或MIB配置的第一下行BWP中的任一种。
  8. 根据权利要求3所述的方法，其特征在于，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为网络设备通过终端专属信令配置的默认BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为网络设备通过终端专属信令配置的默认BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为网络设备通过终端专属信令配置的默认BWP。
  9. 根据权利要求4所述的方法，其特征在于，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP；
    或者，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所 述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP；
    或者，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
  10. 根据权利要求9所述的方法，其特征在于，在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP；
    或者，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
  11. 根据权利要求4所述的方法，其特征在于，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为MIB配置的第一下行BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为MIB配置的第一下行BWP。
  12. 根据权利要求11所述的方法，其特征在于，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，所述默认BWP为MIB配置的第一下行BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，所述默认BWP为MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
  13. 根据权利要求5所述的方法，其特征在于，在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为所述第二下行BWP；
    或者，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为所述第二下行BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为所述第二下行BWP；
    或者，
    在SIB配置的所述下行BWP大于所述终端支持带宽、所述上行BWP大于所述终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为所述第二下行BWP。
  14. 根据权利要求6所述的方法，其特征在于，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为所述网络设备配置的公共BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为所述网络设备配置的公共BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为所述网络设备配置的公共BWP。
  15. 一种BWP回退方法，其特征在于，所述方法由网络设备执行，所述方法包括：
    响应于对应于第一类型终端的定时器超时，网络设备确定与第一类型终端进行通信的默认BWP，默认BWP为网络设备从当前BWP切换至的目标BWP；
    其中，所述默认BWP根据以下至少一种方式确定：
    预设规则，以及，
    通信协议。
  16. 根据权利要求15所述的方法，其特征在于，所述预设规则包括以下至少一项信息：
    第一上行BWP与所述第一类型终端支持带宽之间的关系、第一下行BWP与所述第一类型终端支持带宽之间的关系以及第二下行BWP的作用；
    其中，所述第一下行BWP支持第一类型终端和第二类型终端使用，所述第二下行BWP支持所述第一类型终端使用，所述第一类型终端的能力小于第二类型终端的能力。
  17. 根据权利要求15或16所述的方法，其特征在于，所述默认BWP为网络设备通过终端专属信令配置的默认BWP。
  18. 根据权利要求15或16所述的方法，其特征在于，在所述网络设备未通过终端专属信令配置默认BWP的情况下，所述默认BWP为SIB配置的第一下行BWP；
    或者，
    在所述网络设备未通过终端专属信令配置默认BWP的情况下，所述默认BWP为MIB配置的第一下行BWP。
  19. 根据权利要求15或16所述的方法，其特征在于，在所述网络设备未通过终端专属信令配置默认BWP的情况下，所述默认BWP为第二下行BWP。
  20. 根据权利要求15或16所述的方法，其特征在于，在所述网络设备未通过终端专属信令配置默认BWP的情况下，所述默认BWP为所述网络设备配置的公共BWP。
  21. 根据权利要求15或16所述的方法，其特征在于，所述默认BWP为所述网络设备的配置信息指示的BWP，所述BWP为第二下行BWP、SIB配置的第一下行BWP或MIB配置的第一下行BWP中的任一种。
  22. 根据权利要求17所述的方法，其特征在于，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为网络设备通过终端专属信令配置的默认BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为网络设备通过终端专属信令配置的默认BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为网络设备通过终端专属信令配置的默认BWP。
  23. 根据权利要求18所述的方法，其特征在于，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP；
    或者，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP；
    或者，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP。
  24. 根据权利要求23所述的方法，其特征在于，在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于频分双工模式，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP；
    或者，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，所述默认BWP为SIB配置的第一下行BWP或MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
  25. 根据权利要求18所述的方法，其特征在于，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为MIB配置的第一下行BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为MIB配置的第一下行BWP。
  26. 根据权利要求25所述的方法，其特征在于，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或 寻呼的情况下，对于频分双工模式，所述默认BWP为MIB配置的第一下行BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，对于时分双工模式，所述默认BWP为MIB配置的第一下行BWP，配置与第一下行BWP对应的上行BWP。
  27. 根据权利要求19所述的方法，其特征在于，在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为所述第二下行BWP；
    或者，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为所述第二下行BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为所述第二下行BWP；
    或者，
    在SIB配置的所述下行BWP大于所述第一类型终端支持带宽、所述上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于连接态的情况下，所述默认BWP为所述第二下行BWP。
  28. 根据权利要求20所述的方法，其特征在于，
    在第一下行BWP小于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为所述网络设备配置的公共BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP小于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或 寻呼的情况下，所述默认BWP为所述网络设备配置的公共BWP；
    或者，
    在SIB配置的第一下行BWP大于所述第一类型终端支持带宽、第一上行BWP大于所述第一类型终端支持带宽，且第二下行BWP至少用于随机接入或寻呼的情况下，所述默认BWP为所述网络设备配置的公共BWP。
  29. 一种BWP回退装置，其特征在于，所述装置包括：
    确定模块，被配置为响应于与当前所监测的BWP的第一定时器超时，第一类型终端确定默认BWP；
    其中，所述默认BWP为所述终端从当前所监测的BWP切换至的目标BWP，所述默认BWP根据以下的至少一种方式确定：
    预设规则，
    网络设备的指示信息，以及，
    通信协议。
  30. 一种BWP回退装置，其特征在于，所述装置包括：
    确定模块，被配置为响应于对应于第一类型终端的定时器超时，网络设备确定与第一类型终端进行通信的默认BWP，默认BWP为网络设备从当前BWP切换至的目标BWP；
    其中，所述默认BWP根据以下至少一种方式确定：
    预设规则，以及，
    通信协议。
  31. 一种终端，其特征在于，所述终端包括：
    处理器；
    与所述处理器相连的收发器；
    其中，所述处理器被配置为加载并执行可执行指令以实现如权利要求1至14任一所述的BWP回退方法。
  32. 一种网络设备，其特征在于，所述网络设备包括：
    处理器；
    与所述处理器相连的收发器；
    其中，所述处理器被配置为加载并执行可执行指令以实现如权利要求15至28任一所述的BWP回退方法。
  33. 一种计算机可读存储介质，其特征在于，所述可读存储介质中存储有可执行程序代码，所述可执行程序代码由处理器加载并执行以实现如权利要求1至28任一所述的BWP回退方法。
  34. 一种计算机程序产品，其特征在于，所述算机程序产品被终端或网络设备的处理器执行时，用于实现如权利要求1至28任一所述的BWP回退方法。
PCT/CN2021/129121 2021-11-05 2021-11-05 Bwp回退方法、装置、设备及存储介质 WO2023077466A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/129121 WO2023077466A1 (zh) 2021-11-05 2021-11-05 Bwp回退方法、装置、设备及存储介质
CN202180003789.4A CN114175724A (zh) 2021-11-05 2021-11-05 Bwp回退方法、装置、设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/129121 WO2023077466A1 (zh) 2021-11-05 2021-11-05 Bwp回退方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023077466A1 true WO2023077466A1 (zh) 2023-05-11

Family

ID=80489989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/129121 WO2023077466A1 (zh) 2021-11-05 2021-11-05 Bwp回退方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN114175724A (zh)
WO (1) WO2023077466A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10334525B1 (en) * 2016-12-06 2019-06-25 Mbit Wireless, Inc. Method and apparatus for collaborative paging information transmission
CN111132278A (zh) * 2018-10-31 2020-05-08 华为技术有限公司 Bwp的分配方法及装置
CN111436085A (zh) * 2019-01-11 2020-07-21 华为技术有限公司 通信方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10334525B1 (en) * 2016-12-06 2019-06-25 Mbit Wireless, Inc. Method and apparatus for collaborative paging information transmission
CN111132278A (zh) * 2018-10-31 2020-05-08 华为技术有限公司 Bwp的分配方法及装置
CN111436085A (zh) * 2019-01-11 2020-07-21 华为技术有限公司 通信方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "Summary of Bandwidth Part Operation", 3GPP TSG RAN WG1 MEETING 91, R1-1721504, 29 November 2017 (2017-11-29), XP051364019 *

Also Published As

Publication number Publication date
CN114175724A (zh) 2022-03-11

Similar Documents

Publication Publication Date Title
EP3836687A1 (en) Information transmission method and apparatus
US20210168810A1 (en) Resource Configuration Method and Apparatus
US12004157B2 (en) Method and apparatus for operating DRX timer, device and storage medium
CN111356230B (zh) 一种通信方法及装置
CN114424482B (zh) 通信方法及装置
CN114424629B (zh) 一种唤醒信号的检测方法及装置
RU2699408C1 (ru) Поисковый вызов в расширенном покрытии
CN112469025B (zh) 一种通信方法及装置
US20220150869A1 (en) Assignment of a second ue identity to adjust paging timing for ue for wireless network
WO2021103026A1 (zh) 在带宽部分上进行通信的方法
WO2023051336A1 (zh) 一种通信方法、通信装置及计算机可读存储介质
JP2023512807A (ja) 無線通信において、低減した能力のデバイスをサポートする方法及び装置
US11570633B2 (en) Network configuration method, apparatus, network element, and system
WO2023077466A1 (zh) Bwp回退方法、装置、设备及存储介质
CN114616870B (zh) 非连续接收周期期间的唤醒信令
KR20230130015A (ko) 사이드링크 송신 및 수신을 수행하기 위한 방법 및디바이스
CN115136718A (zh) 通信设备和方法
WO2023108497A1 (zh) 能力指示方法、装置、设备及存储介质
WO2024077510A1 (zh) 信号接收、发送方法及装置
US20230069465A1 (en) Receiving Data Without Monitoring Control Channel
EP4369797A1 (en) Drx configuration method and apparatus, terminal device, and network device
US20240089821A1 (en) Method for service switching between terminal devices
WO2021063031A1 (zh) 节能信息传输方法、终端和网络侧设备
CN117015009A (zh) 一种设备唤醒方法及装置
CN117956596A (zh) 载波配置方法、装置及存储介质

Legal Events

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

Ref document number: 21962979

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2021962979

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021962979

Country of ref document: EP

Effective date: 20240605