WO2023184121A1 - 信息传输方法、装置、通信设备和存储介质 - Google Patents

信息传输方法、装置、通信设备和存储介质 Download PDF

Info

Publication number
WO2023184121A1
WO2023184121A1 PCT/CN2022/083507 CN2022083507W WO2023184121A1 WO 2023184121 A1 WO2023184121 A1 WO 2023184121A1 CN 2022083507 W CN2022083507 W CN 2022083507W WO 2023184121 A1 WO2023184121 A1 WO 2023184121A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
initial bwp
type
downlink
ssb
Prior art date
Application number
PCT/CN2022/083507
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/CN2022/083507 priority Critical patent/WO2023184121A1/zh
Priority to CN202280000955.XA priority patent/CN114902730A/zh
Publication of WO2023184121A1 publication Critical patent/WO2023184121A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • 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 wireless communication technology but is not limited to the field of wireless communication technology, and in particular, to information transmission methods, devices, communication equipment and storage media.
  • NR-lite reduced capability user equipment
  • Redcap terminal a new terminal type is proposed called reduced capability user equipment (Reduced capability UE), referred to as NR-lite or Redcap terminal.
  • This type of equipment is similar to IoT equipment in Long Term Evolution (LTE).
  • 5G-based NR-lite usually needs to meet the following requirements:
  • Some terminals are (1 receiving antenna) 1RX, some are (2 receiving antennas) 2RX.
  • embodiments of the present disclosure provide an information transmission method, device, communication device, and storage medium.
  • an information transmission method is provided, and the method is executed by a base station, wherein the method includes:
  • the cell switching command carries BWP configuration information indicating the bandwidth part BWP of the target cell, wherein the BWP of the target cell is determined based on the type of the first type UE of.
  • the BWP corresponding to the first type UE indicated by the BWP configuration information includes at least one of the following:
  • the first one activates the downward initial BWP
  • the first one activates the uplink initial BWP
  • the first activated downlink initial BWP does not have a synchronization signal block SSB;
  • the first activated downstream initial BWP has SSB.
  • the first activated downlink initial BWP indicated by the BWP configuration information has a non-cell-defining synchronization signal block NCD-SSB.
  • the first downstream initial BWP does not have SSB
  • the first downstream initial BWP has SSB within it.
  • the first downlink initial BWP indicated by the BWP configuration information includes NCD-SSB.
  • the method further includes at least one of the following:
  • the first downlink BWP is configured with the third downlink initial BWP.
  • the third downlink initial BWP is determined as the first downlink initial BWP;
  • the target cell In response to the target cell being configured with a third downlink initial BWP for the second type UE, and the bandwidth of the third downlink initial BWP being greater than the bandwidth of the downlink BWP supported by the first type UE, the target cell is configured with a third downlink initial BWP.
  • the fourth downlink initial BWP configured in the cell's corresponding MIB is determined as the first downlink initial BWP;
  • the fifth downlink initial BWP configured in the MIB corresponding to the target cell is determined as the first downlink initial BWP.
  • the method further includes at least one of the following:
  • the first uplink initial BWP is configured with the third uplink initial BWP.
  • the third uplink initial BWP is determined as the first uplink initial BWP.
  • an information transmission method is provided, and the method is executed by a first type user equipment UE, wherein the method includes:
  • the cell switching command carries BWP configuration information indicating the bandwidth part BWP corresponding to the first type UE in the target cell, wherein the BWP of the target cell is the base station based on the Determined by the type of the first type UE.
  • the BWP corresponding to the first type of UE includes at least one of the following:
  • the first one activates the downward initial BWP
  • the first one activates the uplink initial BWP
  • the first activated downlink initial BWP does not have a synchronization signal block SSB;
  • the first activated downstream initial BWP has SSB.
  • the method further includes:
  • the first downstream initial BWP has SSB within it.
  • the method further includes:
  • synchronization and/or wireless signal measurement is performed through the downlink initial BWP having SSB in the target cell.
  • the method further includes:
  • an information transmission device wherein the device includes:
  • the first transceiver module is configured to send a cell switching command to the first type user equipment UE, where the cell switching command carries BWP configuration information indicating the bandwidth part BWP of the target cell, wherein the BWP of the target cell is based on the Determined by the type of the first type UE.
  • the BWP corresponding to the first type UE indicated by the BWP configuration information includes at least one of the following:
  • the first one activates the downward initial BWP
  • the first one activates the uplink initial BWP
  • the first activated downlink initial BWP does not have a synchronization signal block SSB;
  • the first activated downstream initial BWP has SSB.
  • the first activated downlink initial BWP indicated by the BWP configuration information has a non-cell-defining synchronization signal block NCD-SSB.
  • the first downstream initial BWP has SSB within it.
  • the first downlink initial BWP indicated by the BWP configuration information includes a non-cell-defining synchronization signal block NCD-SSB.
  • the device further includes a first processing module configured to be at least one of the following:
  • the first downlink BWP is configured with the third downlink initial BWP.
  • the third downlink initial BWP is determined as the first downlink initial BWP;
  • the target cell In response to the target cell being configured with a third downlink initial BWP for the second type UE, and the bandwidth of the third downlink initial BWP being greater than the bandwidth of the downlink BWP supported by the first type UE, the target cell is configured with a third downlink initial BWP.
  • the fourth downlink initial BWP configured in the cell's corresponding MIB is determined as the first downlink initial BWP;
  • the device further includes a first processing module configured to be at least one of the following:
  • the first uplink initial BWP is configured with the third uplink initial BWP.
  • the third uplink initial BWP is determined as the first uplink initial BWP.
  • an information transmission device wherein the device includes:
  • the second transceiver module is configured to receive a cell switching command from the base station, where the cell switching command carries BWP configuration information indicating the BWP of the bandwidth part corresponding to the first type user equipment UE in the target cell, where the target cell
  • the BWP is determined by the base station based on the type of the first type UE.
  • the BWP corresponding to the first type of UE includes at least one of the following:
  • the first one activates the downward initial BWP
  • the first one activates the uplink initial BWP
  • the first activated downlink initial BWP does not have a synchronization signal block SSB;
  • the first activated downstream initial BWP has SSB.
  • the device further includes a second processing module configured to:
  • the first downstream initial BWP has SSB within it.
  • the device further includes a second processing module configured to:
  • synchronization and/or wireless signal measurement is performed through the downlink initial BWP having SSB in the target cell.
  • the second transceiver module is further configured to:
  • a communication equipment device including a processor, a memory, and an executable program stored on the memory and capable of being run by the processor, wherein the processor runs the executable program.
  • the program When the program is executed, the steps of the information transmission method described in the first aspect or the second aspect are performed.
  • a storage medium on which an executable program is stored, wherein when the executable program is executed by a processor, the information transmission method as described in the first aspect or the second aspect is implemented. A step of.
  • Embodiments of the present disclosure provide information transmission methods, devices, communication equipment and storage media.
  • the information transmission method includes: the base station sends a cell switching command to the first type user equipment UE, wherein the cell switching command carries BWP configuration information indicating the bandwidth part BWP of the target cell, wherein the BWP of the target cell is based on the first A type of UE is determined by its type.
  • the BWP of the target cell for handover is configured for the UE based on the type of the UE, which reduces the situation that the configured BWP cannot be supported by the UE, improves the cell handover success rate, and improves communication reliability.
  • Figure 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment
  • Figure 2 is a schematic flow chart of an information transmission method according to an exemplary embodiment
  • Figure 3 is a schematic flowchart of another information transmission method according to an exemplary embodiment
  • Figure 4 is a schematic flowchart of yet another information transmission method according to an exemplary embodiment
  • Figure 5 is a schematic flowchart of yet another information transmission method according to an exemplary embodiment
  • Figure 6 is a schematic flowchart of yet another information transmission method according to an exemplary embodiment
  • Figure 7 is a schematic flowchart of yet another information transmission method according to an exemplary embodiment
  • Figure 8 is a schematic flowchart of yet another information transmission method according to an exemplary embodiment
  • Figure 9 is a block diagram of an information transmission device according to an exemplary embodiment
  • Figure 10 is a block diagram of another information transmission device according to an exemplary embodiment
  • FIG. 11 is a block diagram of an apparatus for information transmission according to an exemplary embodiment.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • word “if” as used herein may be interpreted as "when” or “when” or “in response to determining.”
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on cellular mobile communication technology.
  • the wireless communication system may include several terminals 11 and several base stations 12 .
  • the terminal 11 may be a device that provides voice and/or data connectivity to the user.
  • Terminal 11 can communicate with one or more core networks via a Radio Access Network (RAN).
  • RAN Radio Access Network
  • Terminal 11 can be an Internet of Things terminal, such as a sensor device, a mobile phone (or "cellular" phone) and a device with The computer of the Internet of Things terminal, for example, can be a fixed, portable, pocket-sized, handheld, computer-built-in or vehicle-mounted device.
  • station STA
  • subscriber unit subscriber unit
  • subscriber station subscriber station
  • mobile station mobile station
  • remote station remote station
  • access terminal remote terminal
  • user terminal user agent, user device, or user equipment (UE).
  • UE user equipment
  • the terminal 11 may be a device of an unmanned aerial vehicle.
  • the terminal 11 may also be a vehicle-mounted device, for example, it may be an on-board computer with a wireless communication function, or a wireless communication device connected to an external on-board computer.
  • the terminal 11 may also be a roadside device, for example, it may be a streetlight, a signal light or other roadside device with wireless communication function.
  • the base station 12 may be a network-side device in a wireless communication system.
  • the wireless communication system can be the 4th generation mobile communication technology (the 4th generation mobile communication, 4G) system, also known as the Long Term Evolution (LTE) system; or the wireless communication system can also be a 5G system, Also called new radio (NR) system or 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network).
  • MTC system New Generation-Radio Access Network
  • the base station 12 may be an evolved base station (eNB) used in the 4G system.
  • the base station 12 may also be a base station (gNB) that adopts a centralized distributed architecture in the 5G system.
  • eNB evolved base station
  • gNB base station
  • the base station 12 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
  • the centralized unit is equipped with a protocol stack including the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control protocol (Radio Link Control, RLC) layer, and the Media Access Control (Media Access Control, MAC) layer; distributed
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • the unit is provided with a physical (Physical, PHY) layer protocol stack, and the embodiment of the present disclosure does not limit the specific implementation of the base station 12.
  • a wireless connection can be established between the base station 12 and the terminal 11 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, such as
  • the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.
  • an E2E (End to End) connection can also be established between terminals 11.
  • V2V vehicle to vehicle, vehicle to vehicle
  • V2I vehicle to infrastructure, vehicle to roadside equipment
  • V2P vehicle to pedestrian, vehicle to person
  • the above-mentioned wireless communication system may also include a network management device 13.
  • the network management device 13 may be a core network device in a wireless communication system.
  • the network management device 13 may be a mobility management entity (Mobility Management Entity) in an evolved packet core network (Evolved Packet Core, EPC). MME).
  • the network management device can also be other core network devices, such as serving gateway (Serving GateWay, SGW), public data network gateway (Public Data Network GateWay, PGW), policy and charging rules functional unit (Policy and Charging Rules) Function, PCRF) or Home Subscriber Server (HSS), etc.
  • serving gateway Serving GateWay, SGW
  • public data network gateway Public Data Network GateWay, PGW
  • Policy and Charging Rules Policy and Charging Rules
  • PCRF Policy and Charging Rules
  • HSS Home Subscriber Server
  • the execution subjects involved in the embodiments of this disclosure include but are not limited to: mobile phone terminals in cellular mobile communication systems, as well as network-side equipment, such as access network equipment such as base stations, and core networks.
  • a downlink initial BWP can be separately configured for Redcap UE in SIB1: Redcap-specific downlink initial BWP configuration (RedCap-specific initial DL BWP configuration), which is used for random access response (RAR, Random Access Response). Receiving; can also be used for paging, etc.
  • Redcap-specific downlink initial BWP configuration (RedCap-specific initial DL BWP configuration), which is used for random access response (RAR, Random Access Response).
  • RAR Random Access Response
  • Receiving can also be used for paging, etc.
  • the dedicated downstream initial BWP can be configured without CD-SSB and CORESET#0.
  • the dedicated downlink initial BWP is configured for random access and not for idle/inactive paging
  • the Redcap UE does not expect the dedicated downlink initial BWP to have SSB/CORESET#0/SIB .
  • the access network (RAN1) considers the Redcap UE to assume that the REDCAP UE performs random access in a dedicated downlink initial BWP and does not need to listen for paging in the BWP containing CORESET#0.
  • this dedicated downstream initial BWP can be configured without CD-SSB.
  • the dedicated downlink initial BWP is configured for random access and not for idle/inactive paging
  • the Redcap UE does not expect the dedicated downlink initial BWP to have SSB/CORESET#0/SIB .
  • the access network (RAN1) considers the Redcap UE to assume that the REDCAP UE performs random access in a dedicated downlink initial BWP and does not need to listen for paging in the BWP containing CORESET#0.
  • a separate upstream initial BWP is also configured in SIB1: Redcap-specific initial UL BWP configuration (RedCap-specific initial UL BWP configuration), which is used for random access.
  • the initial BWP it uses will be issued to the UE by the target base station in the handover command.
  • how to configure the downlink initial BWP for the handover process has not been defined.
  • the initial BWP used by ordinary UE if it is directly configured to Redcap UE, it may not be supported by Redcap UE, because the bandwidth of the initial BWP used by ordinary UE may be within the bandwidth range that Redcap UE can support. In addition, this means that the Redcap UE may not receive the corresponding configuration of the initial BWP.
  • this exemplary embodiment provides an information transmission method, which can be performed by a base station of a cellular mobile communication system, including:
  • Step 201 Send a cell switching command to the first type user equipment UE, where the cell switching command carries BWP configuration information indicating the bandwidth part BWP of the target cell, wherein the BWP of the target cell is based on the first type UE. The type is determined.
  • the base station to which the serving cell belongs can send a handover command to the UE, instructing the UE to switch to the target cell.
  • the serving cell and the target cell may be cells generated by the same base station or cells generated by different base stations.
  • the base station to which the serving cell belongs can apply for and allocate resources from the base station to which the target cell belongs.
  • the first type of UE may be a UE in an RRC connected state.
  • the signal receiving capability of the first type UE is lower than the signal receiving capability of the second type UE. That is to say, the first type UE may have lower signal receiving capability than the second type UE.
  • a first type UE has a smaller number of receive antennas than a second type UE.
  • the first type of UE has weak BWP support capabilities. For example, the bandwidth of BWP supported by the first type of UE is 20M in the FR1 range and 100M in the FR2 range.
  • the bandwidth of the BWP supported by the second type UE is greater than the bandwidth of the BWP supported by the first type UE.
  • the first type of UE may be a Redcap type UE introduced in 3GPP Release 17 (R17).
  • the first type of UE may also be an enhanced Redcap type UE introduced in subsequent 3GPP Release versions; for example, the first type of UE may be a Redcap type UE.
  • the second type of UE may be an eMMB type UE.
  • the BWP of the target cell indicated by the BWP configuration information may be determined by the base station to which the serving cell belongs, or may be determined by the base station to which the target cell belongs.
  • the BWP indicated by the BWP configuration information may include: an initial BWP used to access the target cell, and/or the first activated BWP used to transmit service data, etc.
  • the BWP indicated by the BWP configuration information may be determined by the base station to which the target cell belongs.
  • the base station may determine the BWP applicable to the UE type based on the UE type. For example, when the UE to be handed over is a first type UE, a BWP with a narrower bandwidth can be configured for the first type UE so that the configured BWP can meet the support capabilities of the first type UE; when the UE to be handed over is a second type UE , a BWP with a wider bandwidth can be configured for the second type UE.
  • the UE can report its own UE type.
  • the base station to which the serving cell belongs sends a handover request to the base station to which the target cell belongs, the handover request may carry the UE type.
  • the base station to which the target cell belongs can configure the BWP of the UE based on the type of the UE. For example, the UE can report its UE type to the base station to which the serving cell belongs, and during the handover process, the base station to which the serving cell belongs can indicate the UE type to the base station to which the target cell belongs.
  • the base station to which the target cell belongs After the base station to which the target cell belongs determines the BWP configured for the first type UE, it can send it to the base station to which the serving cell of the first type UE belongs, and then the base station to which the serving cell belongs sends it to the UE.
  • the UE After receiving the BWP configuration information, the UE can perform data transmission based on the BWP of the target cell indicated by the BWP configuration information: such as receiving random access responses, transmitting service data, etc. Since the BWP is configured based on the type of the UE, the UE can support the BWP.
  • the BWP of the target cell for handover is configured for the UE based on the type of the UE, which reduces the situation that the configured BWP cannot be supported by the UE, improves the cell handover success rate, and improves communication reliability.
  • the BWP corresponding to the first type UE indicated by the BWP configuration information includes at least one of the following:
  • the first one activates the downward initial BWP
  • the first one activates the uplink initial BWP
  • the first activated downlink initial BWP can be the first type of UE, such as the initial activated downlink BWP used by Redcap UE when transmitting service data in the target cell.
  • the BWP bandwidth that the second type UE, such as eMMB UE, can support is greater than the BWP bandwidth that the first type UE can support. Therefore, the bandwidth of the first activated downlink initial BWP configured by the base station for the first type UE is less than or equal to the bandwidth configured for the first type UE.
  • the bandwidth of the first activated downlink initial BWP of the second type UE is such that the bandwidth configured for the first activated downlink initial BWP of the first type UE can comply with the support capability of the first type UE.
  • the first activated uplink initial BWP can be the first type of UE, such as the initial activated uplink BWP used by Redcap UE when transmitting service data in the target cell.
  • the BWP bandwidth that the second type UE, such as eMMB UE, can support is greater than the BWP bandwidth that the first type UE can support. Therefore, the bandwidth of the first activated uplink initial BWP configured by the base station for the first type UE is less than or equal to the bandwidth configured for the first type UE.
  • the bandwidth of the first activated uplink initial BWP of the second type UE is such that the bandwidth configured for the first activated uplink initial BWP of the first type UE can comply with the support capability of the first type UE.
  • the first downlink initial BWP may be the BWP for the first type UE to perform random access in the target cell.
  • the first downlink initial BWP may be the first type UE to receive a random access response (RAR, Random) in the target cell. Access Response); the first downlink initial BWP may also be the BWP used by the first type UE to receive paging in the target cell.
  • the first downlink initial BWP may be initialDownlinkBWP-RedCap configured using DownlinkConfigCommon.
  • the base station may configure the bandwidth of the first downlink initial BWP to be less than or equal to the bandwidth of the downlink initial BWP configured for the second type UE, so that the bandwidth of the first downlink initial BWP can comply with the support capability of the first type UE.
  • the first downlink initial BWP may be a Redcap UE-specific downlink initial BWP (RedCap-specific initial DL BWP).
  • the first uplink initial BWP may be the BWP used by the first type UE to perform random access in the target cell.
  • the base station may configure the bandwidth of the first uplink initial BWP to be less than or equal to the bandwidth of the downlink initial BWP configured for the second type UE, so that the bandwidth of the first uplink initial BWP can comply with the support capability of the first type UE.
  • the first uplink initial BWP may be a Redcap UE-specific uplink initial BWP (RedCap-specific initial UL BWP).
  • the BWP of the target cell for handover is configured for the UE based on the type of the UE, which reduces the situation that the configured BWP cannot be supported by the UE, improves the cell handover success rate, and improves communication reliability.
  • the first activated downlink initial BWP does not have a synchronization signal block SSB;
  • the first activated downstream initial BWP has SSB.
  • the first activated downlink initial BWP configured for the first type UE may not have SSB.
  • SSB may include: cell-defining SSB (CD-SSB, cellDefining SSB) or non-cell-defining SSB (NCD-SSB, Non Cell-Defining SSB).
  • CD-SSB has System Information Block 1 (SIB, System Information Block 1), which is the remaining minimum system information (RMSI, remaining system information), which can be used to indicate a cell, and CD-SSB can be used for synchronization or use for signal measurement.
  • SIB System Information Block 1
  • RMSI remaining system information
  • NCD-SSB cannot be used to determine the cell.
  • NCD-SSB can be used for synchronization or for signal measurement.
  • the first type UE in response to the first activated downlink initial BWP having no SSB, performs synchronization and/or wireless signal measurement through the downlink initial BWP having SSB in the target cell.
  • the first activated downlink initial BWP configured for the first type UE does not have SSB, and the first type UE can use the downlink initial BWP with SSB for synchronization.
  • the first type of UE can decode the MIB in the target cell and obtain the downlink initial BWP configured in the MIB for synchronization and/or wireless signal measurement.
  • the dedicated downlink initial BWP configured in the MIB can be used for synchronization and/or measurement;
  • the first type of UE may use the downlink initial BWP used by the second type of UE for synchronization and/or wireless signal measurement.
  • the first activated downlink initial BWP configured for the first type UE may have SSB.
  • SSB may include: CD-SSB or NCD-SSB.
  • the first type UE may complete synchronization and/or radio signal measurement based on the SSB in the first activated downlink initial BWP.
  • Having SSB in the first activated downlink initial BWP may include: having CD-SSB in the first activated downlink initial BWP, or having NCD-SSB in the first activated downlink initial BWP.
  • the first activated downlink initial BWP does not have SSB, synchronization and measurement during the handover process can be accelerated, optimizing performance.
  • the first activated downlink initial BWP indicated by the BWP configuration information has a non-cell-defining synchronization signal block NCD-SSB.
  • the base station may configure the first activated downlink initial BWP with NCD-SSB for the first type UE based on the predetermined capabilities of the first type UE.
  • the predetermined capability may be obtained by the base station to which the target cell belongs (target base station) from the base station to which the serving cell belongs (original base station).
  • the predetermined capabilities of the first type UE may be carried in the handover request sent by the original base station to the target base station.
  • the predetermined capability may be obtained by the base station to which the target cell belongs (target base station) from the core network.
  • the first type of UE may send its predetermined capabilities to the original base station and/or the core network when connecting to the original base station.
  • the predetermined capabilities may include requirements for the first type of UE to be the first to activate the downlink initial BWP.
  • the predetermined capability may be: the first type of UE supports feature group (Feature Group) FG 6-1, but expects the BWP to include NCD-SSB and not include CORESET#0/SIB, etc.
  • the first downstream initial BWP does not have SSB
  • the first downstream initial BWP has SSB within it.
  • the first downstream initial BWP may not have SSB.
  • SSB may include: CD-SSB or NCD-SSB.
  • CD-SSB has System Information Block 1 (SIB, System Information Block1), which is the remaining minimum system information (RMSI, remaining system information), which can be used to indicate a cell, and CD-SSB can be used for synchronization or signal measurement .
  • SIB System Information Block 1
  • RMSI remaining minimum system information
  • NCD-SSB cannot be used to determine the cell.
  • NCD-SSB can be used for synchronization or for signal measurement.
  • the first type UE in response to the first downlink initial BWP having no SSB, performs synchronization and/or wireless signal measurement with the target cell through the downlink initial BWP having SSB in the target cell. .
  • the first downlink initial BWP does not have SSB, and the first type of UE can use the downlink initial BWP with SSB for synchronization.
  • the first type of UE can decode the MIB in the target cell to obtain the downlink initial BWP configured in the MIB for synchronization, for example, synchronize through the dedicated downlink initial BWP configured in the MIB; or, the first type UE can use the second Downlink initial BWP used by class UE for synchronization and/or radio signal measurement.
  • SSB may include: CD-SSB or NCD-SSB.
  • the first type UE may complete synchronization and/or radio signal measurement based on the SSB within the first downlink initial BWP.
  • Having SSB in the first downlink initial BWP may include: having CD-SSB in the first downlink initial BWP, or having NCD-SSB in the first downlink initial BWP.
  • the first downlink initial BWP indicated by the BWP configuration information includes NCD-SSB.
  • the base station may configure the first downlink initial BWP with NCD-SSB for the first type UE based on the predetermined capabilities of the first type UE.
  • the predetermined capability may be obtained by the base station to which the target cell belongs (target base station) from the base station to which the serving cell belongs (original base station).
  • the predetermined capabilities of the first type UE may be carried in the handover request sent by the original base station to the target base station.
  • the predetermined capability may be obtained by the base station to which the target cell belongs (target base station) from the core network.
  • the first type of UE may send its predetermined capabilities to the original base station and/or the core network when connecting to the original base station.
  • the predetermined capabilities may include requirements of the first downlink initial BWP for the first type of UE.
  • the predetermined capability may be: the first type of UE supports FG 6-1, but expects the BWP to include NCD-SSB and not include CORESET#0/SIB, etc.
  • this exemplary embodiment provides an information transmission method that can be performed by a base station of a cellular mobile communication system, including at least one of the following:
  • Step 301a In response to the target cell being configured with a second downlink initial BWP for the first type UE, determine the second downlink initial BWP as the first downlink initial BWP;
  • Step 301b In response to the target cell being configured with a third downlink initial BWP for the second type UE, and the bandwidth of the third downlink initial BWP being less than or equal to the bandwidth of the downlink BWP supported by the first type UE, The third downlink initial BWP is determined as the first downlink initial BWP;
  • Step 301c In response to the target cell being configured with a third downlink initial BWP for the second type UE, and the bandwidth of the third downlink initial BWP being greater than the bandwidth of the downlink BWP supported by the first type UE, The fourth downlink initial BWP configured in the MIB corresponding to the target cell is determined as the first downlink initial BWP;
  • Step 301d In response to the target cell not being configured with the third downlink initial BWP for the second type UE, determine the fifth downlink initial BWP configured in the MIB corresponding to the target cell as the first downlink initial BWP. BWP.
  • Step 301a, step 301b, step 301c, and/or step 301d can be implemented independently or in combination with step 201.
  • a dedicated second downlink initial BWP is configured for the first type of UE in the target cell, for example, a dedicated downlink initial BWP (RedCap-specific initial DL BWP) is configured for the Redcap UE, then the network device directly configures the second downlink initial BWP.
  • the BWP is determined as the first downlink initial BWP, and is indicated to the first type UE through BWP configuration information.
  • the first type UE will use the initial BWP to perform random access during handover.
  • the dedicated downlink initial BWP can be the BWP configured separately for Redcap UE by the base station in SIB1.
  • the dedicated downlink initial BWP can be used for the UE's initial random access and can also be used for the UE's cell handover.
  • the network equipment may include access network equipment and/or core network equipment, etc.
  • a dedicated second downlink initial BWP is not configured for the first type UE, and a third downlink initial BWP is configured for the second type UE, such as EMMB UE, and the bandwidth of the third downlink initial BWP is less than or Equal to the first type of UE, such as the bandwidth supported by Redcap UE (FR1 is 20M, FR2 is 100M)
  • the network device directly determines the third downlink initial BWP as the first downlink initial BWP, and uses the BWP configuration information during cell switching Instruct the first type UE; the first type UE will use the initial BWP to perform random access during handover.
  • the target cell does not configure a dedicated second downlink initial BWP for the first type UE, and if the target cell does not configure a dedicated second downlink initial BWP for the first type UE, and it is a second type UE,
  • eMMB UE is configured with the third downlink initial BWP, and the bandwidth of the third downlink initial BWP is greater than the first type UE.
  • the bandwidth supported by Redcap UE FR1 is 20M, FR2 is 100M
  • the network device directly configures the MIB to the third downlink initial BWP.
  • the fourth downlink initial BWP is determined as the first downlink initial BWP.
  • the BWP configuration information is used to indicate to the first type UE.
  • the first type UE will use this initial BWP to perform random access during handover or can perform random access during cell handover.
  • the fourth downlink initial BWP configured in the MIB is obtained for random access.
  • the network device directly configures the fourth downlink BWP of the MIB configuration.
  • the initial BWP is determined as the first downlink initial BWP.
  • the BWP configuration information is used to indicate to the first type UE.
  • the first type UE will use the initial BWP to perform random access during handover or can perform random access in the target cell.
  • the fifth downlink initial BWP configured in the MIB is obtained for random access.
  • the protocol limits access as soon as possible during the handover process, so SSB can be configured in the first downlink initial BWP.
  • the downlink initial BWP configured for regular users or the downlink initial BWP configured by the MIB can be configured for the terminal for handover access. Because this type of initial BWP usually has CD-SSB
  • the network device directly determines the third downlink initial BWP as the first downlink
  • the initial BWP is executed, and the BWP configuration information is used to instruct the first type UE during cell handover; the first type UE will use the initial BWP to perform random access during handover.
  • the target cell is configured with a dedicated second downlink initial BWP for the first type UE
  • a third downlink initial BWP for the second type UE such as eMMB UE
  • the third downlink initial BWP The bandwidth of BWP is larger than the first type of UE, such as the bandwidth supported by Redcap UE (FR1 is 20M, FR2 is 100M)
  • the network device directly determines the fourth downlink initial BWP configured in the MIB as the first downlink initial BWP, and cell switching
  • the BWP configuration information is used to indicate to the first type UE
  • the first type UE will use the initial BWP to perform random access during handover or can obtain the fourth downlink initial BWP configured by the MIB in the target cell by decoding the MIB. Perform random access.
  • this exemplary embodiment provides an information transmission method that can be executed by a base station of a cellular mobile communication system, including at least one of the following:
  • Step 401a In response to the target cell being configured with a second uplink initial BWP for the first type UE, determine the second uplink initial BWP as the first uplink initial BWP;
  • Step 401b In response to the target cell being configured with a third uplink initial BWP for the second type UE, and the bandwidth of the third uplink initial BWP being less than or equal to the bandwidth of the uplink BWP supported by the first type UE, The third uplink initial BWP is determined as the first uplink initial BWP.
  • Step 401a and/or step 401b can be implemented alone, or can be implemented in combination with step 301a, step 301b, step 301c, step 301d, and/or step 201.
  • a dedicated second uplink initial BWP is configured for the first type of UE in the target cell, for example, a dedicated uplink initial BWP (RedCap-specific initial UL BWP) is configured for the Redcap UE
  • the network device directly configures the second uplink initial BWP.
  • the BWP is determined as the first uplink initial BWP, and is indicated to the first type UE through BWP configuration information.
  • the first type UE will use the initial BWP to perform random access during handover.
  • the target cell is configured with a third uplink initial BWP for a second type UE, such as an EMMB UE, and the bandwidth of the third downlink initial BWP is less than or equal to the bandwidth supported by a first type UE, such as a Redcap UE, the network device directly
  • the third uplink initial BWP is determined as the first uplink initial BWP, and is indicated to the first type UE through the BWP configuration information during cell handover; the first type UE will use the initial BWP to perform random access during handover.
  • this exemplary embodiment provides an information transmission method, which can be performed by a UE of a cellular mobile communication system, including at least one of the following:
  • Step 501 Receive a cell switching command from the base station, where the cell switching command carries BWP configuration information indicating the BWP of the bandwidth part corresponding to the first type UE in the target cell, where the BWP of the target cell is the base station Determined based on the type of the first type UE.
  • the base station to which the serving cell belongs can send a handover command to the UE, instructing the UE to switch to the target cell.
  • the serving cell and the target cell may be cells generated by the same base station or cells generated by different base stations.
  • the base station to which the serving cell belongs can apply for and allocate resources from the base station to which the target cell belongs.
  • the first type of UE may be a UE in an RRC connected state.
  • the signal receiving capability of the first type UE is lower than the signal receiving capability of the second type UE. That is to say, the first type UE may have lower signal receiving capability than the second type UE.
  • a first type UE has a smaller number of receiving antennas than a second type UE.
  • the first type of UE has weak BWP support capability.
  • the bandwidth of BWP supported by the first type of UE is 20M in the FR1 range and 100M in the FR2 range.
  • the bandwidth of the BWP supported by the second type UE is greater than the bandwidth of the BWP supported by the first type UE.
  • the first type of UE may be a Redcap type UE introduced in 3GPP Release 17 (R17).
  • the first type of UE may also be an enhanced Redcap type UE introduced in subsequent 3GPP Release versions; for example, the first type of UE may be a Redcap type UE.
  • the second type of UE may be an eMMB type UE.
  • the BWP of the target cell indicated by the BWP configuration information may be determined by the base station to which the serving cell belongs, or may be determined by the base station to which the target cell belongs.
  • the BWP indicated by the BWP configuration information may include: an initial BWP used to access the target cell, and/or the first activated BWP used to transmit service data, etc.
  • the BWP indicated by the BWP configuration information may be determined by the base station to which the target cell belongs.
  • the base station may determine the BWP applicable to the UE type based on the UE type. For example, when the UE to be handed over is a first type UE, a BWP with a narrower bandwidth can be configured for the first type UE so that the configured BWP can meet the support capabilities of the first type UE; when the UE to be handed over is a second type UE , a BWP with a wider bandwidth can be configured for the second type UE.
  • the UE can report its own UE type.
  • the base station to which the serving cell belongs sends a handover request to the base station to which the target cell belongs, the handover request may carry the UE type.
  • the base station to which the target cell belongs can configure the BWP of the UE based on the type of the UE. For example, the UE can report its UE type to the base station to which the serving cell belongs, and during the handover process, the base station to which the serving cell belongs can indicate the UE type to the base station to which the target cell belongs.
  • the base station to which the target cell belongs After the base station to which the target cell belongs determines the BWP configured for the first type UE, it can send it to the base station to which the serving cell of the first type UE belongs, and then the base station to which the serving cell belongs sends it to the UE.
  • the UE After receiving the BWP configuration information, the UE can perform data transmission based on the BWP of the target cell indicated by the BWP configuration information: such as receiving random access responses, transmitting service data, etc. Since the BWP is configured based on the type of the UE, the UE can support the BWP.
  • the BWP of the target cell for handover is configured for the UE based on the type of the UE, which reduces the situation that the configured BWP cannot be supported by the UE, improves the cell handover success rate, and improves communication reliability.
  • the BWP corresponding to the first type of UE includes at least one of the following:
  • the first one activates the downward initial BWP
  • the first one activates the uplink initial BWP
  • the first activated downlink initial BWP can be the first type of UE, such as the initial activated downlink BWP used by Redcap UE when transmitting service data in the target cell.
  • the BWP bandwidth that the second type UE, such as eMMB UE, can support is greater than the BWP bandwidth that the first type UE can support. Therefore, the bandwidth of the first activated downlink initial BWP configured by the base station for the first type UE is less than or equal to the bandwidth configured for the first type UE.
  • the bandwidth of the first activated downlink initial BWP of the second type UE is such that the bandwidth configured for the first activated downlink initial BWP of the first type UE can comply with the support capability of the first type UE.
  • the first activated uplink initial BWP can be the first type of UE, such as the initial activated uplink BWP used by Redcap UE when transmitting service data in the target cell.
  • the BWP bandwidth that the second type UE, such as eMMB UE, can support is greater than the BWP bandwidth that the first type UE can support. Therefore, the bandwidth of the first activated uplink initial BWP configured by the base station for the first type UE is less than or equal to the bandwidth configured for the first type UE.
  • the bandwidth of the first activated uplink initial BWP of the second type UE is such that the bandwidth configured for the first activated uplink initial BWP of the first type UE can comply with the support capability of the first type UE.
  • the first downlink initial BWP may be the BWP for the first type UE to perform random access in the target cell.
  • the first downlink initial BWP may be the first type UE to receive a random access response (RAR, Random) in the target cell. Access Response); the first downlink initial BWP may also be the BWP used by the first type UE to receive paging in the target cell.
  • the first downlink initial BWP may be initialDownlinkBWP-RedCap configured using DownlinkConfigCommon.
  • the base station may configure the bandwidth of the first downlink initial BWP to be less than or equal to the bandwidth of the downlink initial BWP configured for the second type UE, so that the bandwidth of the first downlink initial BWP can comply with the support capability of the first type UE.
  • the first downlink initial BWP may be a Redcap UE-specific downlink initial BWP (RedCap-specific initial DL BWP).
  • the first uplink initial BWP may be the BWP used by the first type UE to perform random access in the target cell.
  • the base station may configure the bandwidth of the first uplink initial BWP to be less than or equal to the bandwidth of the downlink initial BWP configured for the second type UE, so that the bandwidth of the first uplink initial BWP can comply with the support capability of the first type UE.
  • the first uplink initial BWP may be a Redcap UE-specific uplink initial BWP (RedCap-specific initial UL BWP).
  • the BWP of the target cell for handover is configured for the UE based on the type of the UE, which reduces the situation that the configured BWP cannot be supported by the UE, improves the cell handover success rate, and improves communication reliability.
  • the first activated downlink initial BWP does not have a synchronization signal block SSB;
  • the first activated downstream initial BWP has SSB.
  • the first activated downlink initial BWP configured for the first type UE may not have SSB.
  • SSB may include: cell-defining SSB (CD-SSB, cell-Defining SSB) or non-cell-defining SSB (NCD-SSB, Non Cell-Defining SSB).
  • CD-SSB has system information block 1 (SIB, System Information Block 1), that is, remaining minimum system information (RMSI, remaining system information), which can be used to indicate a cell, and CD-SSB can be used for synchronization or for signal measurement.
  • SIB System Information Block 1
  • RMSI remaining system information
  • NCD-SSB cannot be used to determine the cell, but can be used for synchronization or signal measurement.
  • the first activated downlink initial BWP configured for the first type UE may have SSB.
  • SSB may include: CD-SSB or NCD-SSB.
  • the first type UE may complete synchronization and/or radio signal measurement based on the SSB in the first activated downlink initial BWP. Including SSB will help the terminal complete synchronization and random access as quickly as possible during the handover process.
  • Having SSB in the first activated downlink initial BWP may include: having CD-SSB in the first activated downlink initial BWP, or having NCD-SSB in the first activated downlink initial BWP.
  • this exemplary embodiment provides an information transmission method that can be executed by a UE in a cellular mobile communication system, including:
  • Step 601 In response to the first activated downlink initial BWP having no SSB, perform synchronization and/or wireless signal measurement through the downlink initial BWP having SSB in the target cell.
  • Step 601 can be implemented alone or in combination with step 501.
  • the first activated downlink initial BWP configured for the first type UE does not have SSB, and the first type UE can use the downlink initial BWP with SSB for synchronization.
  • the first type of UE can decode the MIB in the target cell and obtain the downlink initial BWP configured in the MIB for synchronization and/or wireless signal measurement.
  • the dedicated downlink initial BWP configured in the MIB can be used for synchronization and/or measurement;
  • the first type of UE may use the downlink initial BWP used by the second type of UE for synchronization and/or wireless signal measurement.
  • the first activated downlink initial BWP indicated by the BWP configuration information has a non-cell-defining synchronization signal block NCD-SSB. Including NCD-SSB will help the terminal complete synchronization and random access as quickly as possible during the handover process.
  • the base station may configure the first activated downlink initial BWP with NCD-SSB for the first type UE based on the predetermined capabilities of the first type UE.
  • the predetermined capability may be obtained by the base station to which the target cell belongs (target base station) from the base station to which the serving cell belongs (original base station).
  • the predetermined capabilities of the first type UE may be carried in the handover request sent by the original base station to the target base station.
  • the predetermined capability may be obtained by the base station to which the target cell belongs (target base station) from the core network.
  • the first type of UE may send its predetermined capabilities to the original base station and/or the core network when connecting to the original base station.
  • the predetermined capabilities may include requirements for the first type of UE to be the first to activate the downlink initial BWP.
  • the predetermined capability may be: the first type of UE supports FG 6-1, but expects the BWP to include NCD-SSB and not include CORESET#0/SIB, etc.
  • the first downstream initial BWP does not have SSB
  • the first downstream initial BWP has SSB within it.
  • the first downstream initial BWP may not have SSB.
  • SSB may include: CD-SSB or NCD-SSB.
  • CD-SSB has System Information Block 1 (SIB, System Information Block1), which is the remaining minimum system information (RMSI, remaining system information), which can be used to indicate a cell, and CD-SSB can be used for synchronization or signal measurement .
  • SIB System Information Block 1
  • RMSI remaining minimum system information
  • NCD-SSB cannot be used to determine the cell.
  • NCD-SSB can be used for synchronization or for signal measurement.
  • the first downlink initial BWP needs to have SSB.
  • SSB may include: CD-SSB or NCD-SSB.
  • the first type UE may complete synchronization and/or radio signal measurement based on the SSB within the first downlink initial BWP.
  • Having SSB in the first downlink initial BWP may include: having CD-SSB in the first downlink initial BWP, or having NCD-SSB in the first downlink initial BWP.
  • this exemplary embodiment provides an information transmission method that can be executed by a UE in a cellular mobile communication system, including:
  • Step 701 In response to the first downlink initial BWP having no SSB, perform synchronization and/or wireless signal measurement through the downlink initial BWP having SSB in the target cell.
  • Step 701 can be implemented alone or in combination with step 501 and/or step 601.
  • the first downlink initial BWP does not have SSB, and the first type of UE can use the downlink initial BWP with SSB for synchronization.
  • the first type of UE can decode the MIB in the target cell to obtain the downlink initial BWP configured in the MIB for synchronization, for example, synchronize through the dedicated downlink initial BWP configured in the MIB; or, the first type UE can use the second Downlink initial BWP used by class UE for synchronization and/or radio signal measurement.
  • this exemplary embodiment provides an information transmission method that can be executed by a UE in a cellular mobile communication system, including:
  • Step 801 Send indication information indicating whether the first type user equipment UE has preset capabilities to the base station, where the preset capabilities are used for the base station to determine whether to indicate to the first type user equipment UE that it has non-default capabilities.
  • the cell defines the first activated downlink initial BWP of the synchronization signal block NCD-SSB and/or the first downlink initial BWP with NCD-SSB.
  • Step 801 can be implemented alone or in combination with step 501 and/or step 601 and/or step 701.
  • the predetermined capability may be obtained by the base station to which the target cell belongs (target base station) from the base station to which the serving cell belongs (original base station).
  • the predetermined capabilities of the first type UE may be carried in the handover request sent by the original base station to the target base station.
  • the predetermined capability may be obtained by the base station to which the target cell belongs (target base station) from the core network.
  • the first type of UE may send its predetermined capabilities to the original base station and/or the core network when connecting to the original base station.
  • the predetermined capabilities may include requirements of the first type of UE for the first activated downlink initial BWP and/or the first downlink initial BWP.
  • the predetermined capability may be: the first type of UE supports FG 6-1, but expects the first activated downlink initial BWP and/or the first downlink initial BWP to include NCD-SSB and not include CORESET#0/SIB, etc.
  • the specific type of terminal is the Redcap type terminal introduced in R17;
  • the target base station will obtain from the handover request that the user type is a specific type of terminal;
  • the initial downlink BWP specified for the first active time when switching does not need to include SSB (CD-SSB or NCD-SSB):
  • the network device includes the first activation of the downlink initial BWP in the handover command, the downlink initial BWP does not need to be configured with CD-SSB or NCD-SSB;
  • the terminal can use the downlink initial BWP with SSB for synchronization, such as the downlink initial BWP configured by the MIB; or the downlink initial BWP used by normal users;
  • the downlink initial BWP needs to be configured with CD-SSB or NCD-SSB; (that is, if there is no CD-SSB on the BWP, an additional one needs to be configured) NCD-SSB).
  • NCD-SSB can be configured for the initial downlink initial BWP configuration specified for a specific type of terminal when handover.
  • the NCD-SSB needs to be based on the terminal capabilities obtained by the base station.
  • the terminal capabilities can be obtained by the target base station from the original base station. (For example, carried in the handover request) or obtained by the core network.
  • the capability of the terminal can be that the terminal supports FG 6-1, but it is expected that the BWP will contain NCD-SSB but not CORESET#0/SIB.
  • the initial downlink BWP specified when switching is the dedicated downlink initial BWP configured for the specific type of terminal (i.e. initialDownlinkBWP-RedCap in DownlinkConfigCommon, which is different from the first activated initial BWP above). No need to include CD-SSB.
  • a dedicated downlink initial BWP is configured for a specific type of terminal in the target cell
  • the network device is directly configured to configure a dedicated downlink initial BWP for the specific type of terminal; the terminal will use this initial BWP to perform random access during handover. enter;
  • the dedicated downlink initial BWP configured for a specific type of terminal does not necessarily include SSB, so the terminal needs to use other initial BWP (such as the initial BWP for ordinary users) for synchronization and measurement;
  • NCD-SSB can be configured for a dedicated downlink initial BWP for a specific type of terminal; at this time, for example, if there is no SSB, synchronization and measurement during the handover process can be accelerated, optimizing performance.
  • Configuring a dedicated downlink initial BWP for a specific type of terminal requires terminal capabilities.
  • the terminal supports configuring NCD-SSB;
  • the capability of the terminal can be that the terminal supports FG 6-1, but it is expected that the BWP will contain NCD-SSB but not CORESET#0/SIB.
  • a dedicated downlink initial BWP is configured for a specific type of terminal and does not contain SSB
  • the terminal will use the downlink initial BWP with SSB for synchronization and measurement during random access, such as the downlink initial BWP configured in the MIB; or Normal user Downstream initial BWP used;
  • the downlink initial BWP specified when switching i.e., the initialDownlinkBWP in DownlinkConfigCommon
  • SSB CD-SSB
  • the network device directly configures the downlink configured for ordinary users.
  • the initial BWP is configured for a specific type of terminal as the designated downlink initial BWP during handover; the terminal will use this initial BWP to perform random access during handover;
  • the network device directly configures the downlink initial BWP configuration of the MIB configuration Specify the downlink initial BWP for a specific type of terminal during handover; the terminal will use this initial BWP to perform random access during handover;
  • the network device directly configures the downlink initial BWP configured in the MIB to the specific type of terminal as the designated downlink initial BWP during handover; the terminal will use this initial BWP BWP performs random access during handover;
  • the upstream initial BWP specified when switching is a dedicated upstream initial BWP configured for the specific type of terminal [RedCap-specific initial UL BWP configuration];
  • the target base station is not configured to configure a dedicated downlink initial BWP for a specific type of terminal, the uplink initial BWP configured for ordinary users is used; at this time, the target base station supports Redcap, or the target base station is a specific type of terminal.
  • a dedicated downlink initial BWP is configured, or an uplink initial BWP is configured for ordinary users, and its bandwidth is within the bandwidth range of Redcap users.
  • An embodiment of the present invention also provides an information transmission device, as shown in Figure 9, applied in a base station of cellular mobile wireless communication, wherein the device 100 includes:
  • the first transceiver module 110 is configured to send a cell switching command to the first type user equipment UE, where the cell switching command carries BWP configuration information indicating the bandwidth part BWP of the target cell, where the BWP of the target cell is based on the Determined by the type of the first type of UE.
  • the BWP corresponding to the first type UE indicated by the BWP configuration information includes at least one of the following:
  • the first one activates the downward initial BWP
  • the first one activates the uplink initial BWP
  • the first activated downlink initial BWP does not have a synchronization signal block SSB;
  • the first activated downstream initial BWP has SSB.
  • the first activated downlink initial BWP indicated by the BWP configuration information has a non-cell-defining synchronization signal block NCD-SSB.
  • the first downstream initial BWP has SSB within it.
  • the first downlink initial BWP indicated by the BWP configuration information includes a non-cell-defining synchronization signal block NCD-SSB.
  • the device further includes a first processing module 120, and the first processing module 120 is configured to be at least one of the following:
  • the first downlink BWP is configured with the third downlink initial BWP.
  • the third downlink initial BWP is determined as the first downlink initial BWP;
  • the target cell In response to the target cell being configured with a third downlink initial BWP for the second type UE, and the bandwidth of the third downlink initial BWP being greater than the bandwidth of the downlink BWP supported by the first type UE, the target cell is configured with a third downlink initial BWP.
  • the fourth downlink initial BWP configured in the cell's corresponding MIB is determined as the first downlink initial BWP;
  • the fifth downlink initial BWP configured in the MIB corresponding to the target cell is determined as the first downlink initial BWP.
  • the device further includes a first processing module 120, and the first processing module 120 is configured to be at least one of the following:
  • the first uplink initial BWP is configured with the third uplink initial BWP.
  • the third uplink initial BWP is determined as the first uplink initial BWP.
  • An embodiment of the present invention also provides an information transmission device, as shown in Figure 10, applied to UE in cellular mobile wireless communications, wherein the device 200 includes:
  • the second transceiver module 210 is configured to receive a cell switching command from the base station, where the cell switching command carries BWP configuration information indicating the bandwidth part BWP corresponding to the first type user equipment UE in the target cell, where the target The BWP of the cell is determined by the base station based on the type of the first type UE.
  • the BWP corresponding to the first type of UE includes at least one of the following:
  • the first one activates the downward initial BWP
  • the first one activates the uplink initial BWP
  • the first activated downlink initial BWP does not have a synchronization signal block SSB;
  • the first activated downstream initial BWP has SSB.
  • the device further includes a second processing module 220, the second processing module 220 is configured to:
  • the first downstream initial BWP has SSB within it.
  • the device further includes a second processing module 220, the second processing module 220 is configured to:
  • synchronization and/or wireless signal measurement is performed through the downlink initial BWP having SSB in the target cell.
  • the second transceiver module 210 is further configured to:
  • the first transceiver module 110, the first processing module 120, the second transceiver module 210, the second processing module 220, etc. may be processed by one or more central processing units (CPUs, Central Processing Units), graphics GPU, Graphics Processing Unit), Baseband Processor (BP, Baseband Processor), Application Specific Integrated Circuit (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), Complex Programmable Logic Device (CPLD, Complex Programmable Logic Device), Field-Programmable Gate Array (FPGA, Field-Programmable Gate Array), general-purpose processor, controller, microcontroller (MCU, Micro Controller Unit), microprocessor (Microprocessor), or other electronic components for performing the foregoing method.
  • CPUs Central Processing Units
  • graphics GPU Graphics Processing Unit
  • BP Baseband Processor
  • ASIC Application Specific Integrated Circuit
  • DSP Programmable Logic Device
  • PLD Programmable Logic Device
  • CPLD Complex Programmable Logic Device
  • FPGA Field-Pro
  • FIG. 11 is a block diagram of a device 3000 for information transmission according to an exemplary embodiment.
  • the device 3000 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like.
  • device 3000 may include one or more of the following components: processing component 3002, memory 3004, power supply component 3006, multimedia component 3008, audio component 3010, input/output (I/O) interface 3012, sensor component 3014, and Communication Component 3016.
  • Processing component 3002 generally controls the overall operations of device 3000, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 3002 may include one or more processors 3020 to execute instructions to complete all or part of the steps of the above method.
  • processing component 3002 may include one or more modules that facilitate interaction between processing component 3002 and other components.
  • processing component 3002 may include a multimedia module to facilitate interaction between multimedia component 3008 and processing component 3002.
  • Memory 3004 is configured to store various types of data to support operations at device 3000. Examples of such data include instructions for any application or method operating on device 3000, contact data, phonebook data, messages, pictures, videos, etc.
  • Memory 3004 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EEPROM erasable programmable read-only memory
  • EPROM Programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory, magnetic or optical disk.
  • Power supply component 3006 provides power to the various components of device 3000.
  • Power supply components 3006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 3000 .
  • Multimedia component 3008 includes a screen that provides an output interface between device 3000 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. A touch sensor can not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.
  • multimedia component 3008 includes a front-facing camera and/or a rear-facing camera.
  • the front camera and/or the rear camera may receive external multimedia data.
  • Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
  • Audio component 3010 is configured to output and/or input audio signals.
  • audio component 3010 includes a microphone (MIC) configured to receive external audio signals when device 3000 is in operating modes, such as call mode, recording mode, and speech recognition mode. The received audio signals may be further stored in memory 3004 or sent via communications component 3016 .
  • audio component 3010 also includes a speaker for outputting audio signals.
  • the I/O interface 3012 provides an interface between the processing component 3002 and a peripheral interface module.
  • the peripheral interface module may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
  • Sensor component 3014 includes one or more sensors for providing various aspects of status assessment for device 3000 .
  • the sensor component 3014 can detect the open/closed state of the device 3000, the relative positioning of components, such as the display and keypad of the device 3000, the sensor component 3014 can also detect the position change of the device 3000 or a component of the device 3000, the user The presence or absence of contact with device 3000, device 3000 orientation or acceleration/deceleration, and temperature changes of device 3000.
  • Sensor assembly 3014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 3014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 3014 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 3016 is configured to facilitate wired or wireless communication between the apparatus 3000 and other devices.
  • Device 3000 may access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof.
  • the communication component 3016 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • communications component 3016 also includes a near field communications (NFC) module to facilitate short-range communications.
  • NFC near field communications
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • apparatus 3000 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Gate array (FPGA), controller, microcontroller, microprocessor or other electronic components are implemented for executing the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable Gate array
  • controller microcontroller, microprocessor or other electronic components are implemented for executing the above method.
  • non-transitory computer-readable storage medium including instructions, such as a memory 3004 including instructions, which can be executed by the processor 3020 of the device 3000 to complete the above method is also provided.
  • non-transitory computer-readable storage media may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

Landscapes

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

Abstract

本公开实施例是关于信息传输方法、装置、通信设备和存储介质，基站向第一类型用户设备(UE)发送小区切换命令，其中，小区切换命令携带有指示目标小区的带宽部分(BWP)的BWP配置信息，其中，所述目标小区的BWP是基于所述第一类型UE的类型确定的。

Description

信息传输方法、装置、通信设备和存储介质 技术领域
本申请涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及信息传输方法、装置、通信设备和存储介质。
背景技术
在目前的3GPP标准化中，提出了新的终端类型叫做能力消减用户设备(Reduced capability UE)，简称为NR-lite或者Redcap终端。该类型设备同长期演进技术(LTE)中的物联网设备类似，基于5G的NR-lite通常需要满足如下要求：
-低造价，低复杂度
-一定程度的覆盖增强
-功率节省
-有些终端是(1个接收天线)1RX，有些是(两个接收天线)2RX。
发明内容
有鉴于此，本公开实施例提供了一种信息传输方法、装置、通信设备和存储介质。
根据本公开实施例的第一方面，提供一种信息传输方法，所述方法被基站执行，其中，所述方法包括：
向第一类型用户设备UE发送小区切换命令，其中，小区切换命令携带有指示目标小区的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是基于所述第一类型UE的类型确定的。
在一个实施例中，所述BWP配置信息指示的所述第一类型UE对应的 所述BWP，包括以下至少之一：
首个激活下行初始BWP；
首个激活上行初始BWP；
第一下行初始BWP；
第一上行初始BWP。
在一个实施例中，
首个激活下行初始BWP内不具有同步信号块SSB；
或者，
首个激活下行初始BWP内具有SSB。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述首个激活下行初始BWP内具有非小区定义同步信号块NCD-SSB。
在一个实施例中，
第一下行初始BWP内不具有SSB；
或者，
第一下行初始BWP内具有SSB。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述第一下行初始BWP内具有NCD-SSB。
在一个实施例中，所述方法还包括以下至少之一：
响应于所述目标小区配置有用于所述第一类型UE的第二下行初始BWP，将所述第二下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区配置有用于第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽小于或等于所述第一类型UE支持的下行BWP的带宽，将所述第三下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区配置有用于所述第二类型UE的第三下行初始 BWP，并且所述第三下行初始BWP的带宽大于所述第一类型UE支持的下行BWP的带宽，将所述目标小区对应MIB中配置的第四下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区未配置有用于所述第二类型UE的第三下行初始BWP，将所述目标小区对应MIB中配置的第五下行初始BWP确定为所述第一下行初始BWP。
在一个实施例中，所述方法还包括以下至少之一：
响应于所述目标小区配置有用于所述第一类型UE的第二上行初始BWP，将所述第二上行初始BWP确定为所述第一上行初始BWP；
响应于所述目标小区配置有用于第二类型UE的第三上行初始BWP，并且所述第三上行初始BWP的带宽小于或等于所述第一类型UE支持的上行BWP的带宽，将所述第三上行初始BWP确定为所述第一上行初始BWP。
根据本公开实施例的第二方面，提供一种信息传输方法，所述方法被第一类型用户设备UE执行，其中，所述方法包括：
接收来自基站的小区切换命令，其中，小区切换命令携带有指示目标小区中所述第一类型UE对应的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是所述基站基于所述第一类型UE的类型确定的。
在一个实施例中，所示第一类型UE对应的所述BWP，包括以下至少之一：
首个激活下行初始BWP；
首个激活上行初始BWP；
第一下行初始BWP；
第一上行初始BWP。
在一个实施例中，首个激活下行初始BWP内不具有同步信号块SSB；
或者，
首个激活下行初始BWP内具有SSB。
在一个实施例中，所述方法还包括：
响应于所述首个激活下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
在一个实施例中，第一下行初始BWP内不具有SSB；
或者，
第一下行初始BWP内具有SSB。
在一个实施例中，所述方法还包括：
响应于所述第一下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
在一个实施例中，所述方法还包括：
向基站发送指示所述第一类型用户设备UE是否具有预设能力的指示信息，其中，所述预设能力，用于供基站确定是否向所述第一类型用户设备UE指示具有非小区定义同步信号块NCD-SSB的所述首个激活下行初始BWP和/或具有NCD-SSB的第一下行初始BWP。
根据本公开实施例的第三方面，提供一种信息传输装置，其中，所述装置包括：
第一收发模块，配置为向第一类型用户设备UE发送小区切换命令，其中，小区切换命令携带有指示目标小区的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是基于所述第一类型UE的类型确定的。
在一个实施例中，所述BWP配置信息指示的所述第一类型UE对应的所述BWP，包括以下至少之一：
首个激活下行初始BWP；
首个激活上行初始BWP；
第一下行初始BWP；
第一上行初始BWP。
在一个实施例中，首个激活下行初始BWP内不具有同步信号块SSB；
或者，
首个激活下行初始BWP内具有SSB。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述首个激活下行初始BWP内具有非小区定义同步信号块NCD-SSB。
在一个实施例中，第一下行初始BWP内不具有SSB；
或者，
第一下行初始BWP内具有SSB。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述第一下行初始BWP内具有非小区定义同步信号块NCD-SSB。
在一个实施例中，所述装置还包括第一处理模块，所述第一处理模块配置为以下至少之一：
响应于所述目标小区配置有用于所述第一类型UE的第二下行初始BWP，将所述第二下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区配置有用于第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽小于或等于所述第一类型UE支持的下行BWP的带宽，将所述第三下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区配置有用于所述第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽大于所述第一类型UE支持的下行BWP的带宽，将所述目标小区对应MIB中配置的第四下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区未配置有用于所述第二类型UE的第三下行初始 BWP，将所述目标小区对应MIB中配置的第五下行初始BWP确定为所述第一下行初始BWP。
在一个实施例中，所述装置还包括第一处理模块，所述第一处理模块配置为以下至少之一：
响应于所述目标小区配置有用于所述第一类型UE的第二上行初始BWP，将所述第二上行初始BWP确定为所述第一上行初始BWP；
响应于所述目标小区配置有用于第二类型UE的第三上行初始BWP，并且所述第三上行初始BWP的带宽小于或等于所述第一类型UE支持的上行BWP的带宽，将所述第三上行初始BWP确定为所述第一上行初始BWP。
根据本公开实施例的第四方面，提供一种信息传输装置，其中，所述装置包括：
第二收发模块，配置为接收来自基站的小区切换命令，其中，小区切换命令携带有指示目标小区中所述第一类型用户设备UE对应的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是所述基站基于所述第一类型UE的类型确定的。
在一个实施例中，所示第一类型UE对应的所述BWP，包括以下至少之一：
首个激活下行初始BWP；
首个激活上行初始BWP；
第一下行初始BWP；
第一上行初始BWP。
在一个实施例中，首个激活下行初始BWP内不具有同步信号块SSB；
或者，
首个激活下行初始BWP内具有SSB。
在一个实施例中，所述装置还包括第二处理模块，所述第二处理模块 配置为：
响应于所述首个激活下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
在一个实施例中，第一下行初始BWP内不具有SSB；
或者，
第一下行初始BWP内具有SSB。
在一个实施例中，所述装置还包括第二处理模块，所述第二处理模块配置为：
响应于所述第一下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
在一个实施例中，所述第二收发模块，还配置为：
向基站发送指示所述第一类型用户设备UE是否具有预设能力的指示信息，其中，所述预设能力，用于供基站确定是否向所述第一类型用户设备UE指示具有非小区定义同步信号块NCD-SSB的所述首个激活下行初始BWP和/或具有NCD-SSB的第一下行初始BWP。
根据本公开实施例的第五方面，提供一种通信设备装置，包括处理器、存储器及存储在存储器上并能够由所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如第一方面或第二方面所述信息传输方法的步骤。
根据本公开实施例的第六方面，提供一种存储介质，其上存储由可执行程序，其中，所述可执行程序被处理器执行时实现如第一方面或第二方面所述信息传输方法的步骤。
本公开实施例提供的信息传输方法、装置、通信设备和存储介质。信息传输方法包括：基站向第一类型用户设备UE发送小区切换命令，其中，小区切换命令携带有指示目标小区的带宽部分BWP的BWP配置信息，其 中，所述目标小区的BWP是基于所述第一类型UE的类型确定的。如此，基于UE的类型为UE配置切换的目标小区的BWP，减少由于配置的BWP不能被UE所支持的情况，提高小区切换成功率，提高通信可靠性。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开实施例。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明实施例，并与说明书一起用于解释本发明实施例的原理。
图1是根据一示例性实施例示出的一种无线通信***的结构示意图；
图2是根据一示例性实施例示出的一种信息传输方法的流程示意图；
图3是根据一示例性实施例示出的另一种信息传输方法的流程示意图；
图4是根据一示例性实施例示出的又一种信息传输方法的流程示意图；
图5是根据一示例性实施例示出的再一种信息传输方法的流程示意图；
图6是根据一示例性实施例示出的再一种信息传输方法的流程示意图；
图7是根据一示例性实施例示出的再一种信息传输方法的流程示意图；
图8是根据一示例性实施例示出的再一种信息传输方法的流程示意图；
图9是根据一示例性实施例示出的一种信息传输装置的框图；
图10是根据一示例性实施例示出的另一种信息传输装置的框图；
图11是根据一示例性实施例示出的一种用于信息传输的装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述 的、本发明实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用于将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
请参考图1，其示出了本公开实施例提供的一种无线通信***的结构示意图。如图1所示，无线通信***是基于蜂窝移动通信技术的通信***，该无线通信***可以包括：若干个终端11以及若干个基站12。
其中，终端11可以是指向用户提供语音和/或数据连通性的设备。终端11可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，终端11可以是物联网终端，如传感器设备、移动电话(或称为“蜂窝”电话)和具有物联网终端的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)、移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程终端(remote terminal)、接入终端(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户终端(user equipment，UE)。或者，终端11也可以是无人飞行器的设备。或者，终端11也可以是 车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线通信设备。或者，终端11也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
基站12可以是无线通信***中的网络侧设备。其中，该无线通信***可以是***移动通信技术(the 4th generation mobile communication，4G)***，又称长期演进(Long Term Evolution，LTE)***；或者，该无线通信***也可以是5G***，又称新空口(new radio，NR)***或5G NR***。或者，该无线通信***也可以是5G***的再下一代***。其中，5G***中的接入网可以称为NG-RAN(New Generation-Radio Access Network，新一代无线接入网)。或者，MTC***。
其中，基站12可以是4G***中采用的演进型基站(eNB)。或者，基站12也可以是5G***中采用集中分布式架构的基站(gNB)。当基站12采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对基站12的具体实现方式不加以限定。
基站12和终端11之间可以通过无线空口建立无线连接。在不同的实施方式中，该无线空口是基于***移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中，终端11之间还可以建立E2E(End to End，端到端)连接。比如车联网通信(vehicle to everything，V2X)中的V2V(vehicle to  vehicle，车对车)通信、V2I(vehicle to Infrastructure，车对路边设备)通信和V2P(vehicle to pedestrian，车对人)通信等场景。
在一些实施例中，上述无线通信***还可以包含网络管理设备13。
若干个基站12分别与网络管理设备13相连接。其中，网络管理设备13可以是无线通信***中的核心网设备，比如，该网络管理设备13可以是演进的数据分组核心网(Evolved Packet Core，EPC)中的移动性管理实体(Mobility Management Entity，MME)。或者，该网络管理设备也可以是其它的核心网设备，比如服务网关(Serving GateWay，SGW)、公用数据网网关(Public Data Network GateWay，PGW)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)或者归属签约用户服务器(Home Subscriber Server，HSS)等。对于网络管理设备13的实现形态，本公开实施例不做限定。
本公开实施例涉及的执行主体包括但不限于：蜂窝移动通信***中的手机终端，以及网络侧设备，如基站等接入网设备，以及核心网等。
相关技术中，可以为Redcap UE在SIB1中单独配置一个下行初始BWP：Redcap专用的下行初始BWP配置(RedCap-specific initial DL BWP configuration)，其用于随机接入响应(RAR，Random Access Response)的接收；也可以用于寻呼(paging)等。
针对FR1，专用的下行初始BWP可以配置为不具有CD-SSB和CORESET#0。在FR1范围内，如果该专用的下行初始BWP配置为用于随机接入，不用于空闲态/非激活态寻呼，那么Redcap UE不期望该专用的下行初始BWP具有SSB/CORESET#0/SIB。该情况下接入网(RAN1)认为Redcap UE假定REDCAP UE在专用的下行初始BWP中执行随机接入，并且不需要在包含CORESET#0的BWP监听寻呼。
针对FR2，该专用的下行初始BWP可以配置为不具有CD-SSB。在FR2 范围内，如果该专用的下行初始BWP配置为用于随机接入，不用于空闲态/非激活态寻呼，那么Redcap UE不期望该专用的下行初始BWP具有SSB/CORESET#0/SIB。该情况下接入网(RAN1)认为Redcap UE假定REDCAP UE在专用的下行初始BWP中执行随机接入，并且不需要在包含CORESET#0的BWP监听寻呼。
在上行方向上也在SIB1中单独配置一个上行初始BWP：Redcap专用的上行初始BWP配置(RedCap-specific initial UL BWP configuration)，用于随机接入。
但是在Redcap UE进行小区切换的时候，其使用的初始BWP将是目标基站在切换命令中下发给UE的，相关技术中，针对切换过程，如何配置下行初始BWP尚无定义。并且，针对Redcap UE，如果直接将普通UE使用的初始BWP配置给Redcap UE，则可能会出现Redcap UE不能支持的情况，因为，普通UE使用的初始BWP的带宽可能在Redcap UE能支持的带宽范围之外，这意味着该Redcap UE可能无法接收该初始BWP的相应配置。
因此，如何对Redcap UE在切换过程中进行BWP的配置，满足Redcap UE对BWP的需求，提高Redcap UE通信可靠性，是亟待解决的问题。
如图2所示，本示例性实施例提供一种信息传输方法，所述方法可以被蜂窝移动通信***的基站执行，包括：
步骤201：向第一类型用户设备UE发送小区切换命令，其中，小区切换命令携带有指示目标小区的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是基于所述第一类型UE的类型确定的。
在UE从服务小区切换到目标小区过程中，服务小区所属基站可以向UE发送切换命令，指示UE切换到目标小区。服务小区和目标小区可以是同一基站生成的小区，也可以是不同基站生成的小区。服务小区所属基站可以从目标小区所属基站进行资源的申请与分配。
第一类型UE可以是处于RRC连接态的UE。其中，该第一类型UE的信号接收能力低于第二类型UE的信号接收能力，也就是说，第一类型UE相对第二类型UE可以具有较低的信号接收能力。例如，第一类型UE与第二类型UE相比具有较少数量的接收天线。第一类型UE具有较弱的BWP支持能力，例如，第一类型UE支持的BWP的带宽在FR1范围内为20M，在FR2范围内为100M。第二类型UE支持的BWP的带宽大于第一类型UE支持的BWP的带宽。
示例性的，第一类型UE可以是3GPP Release 17(R17)中引入的Redcap类型UE。第一类型UE也可以是后续3GPP Release版本中引入的增强形Redcap类型UE；例如，第一类型的UE可以是Redcap类型UE。第二类型的UE可以是eMMB类型UE。
BWP配置信息所指示的目标小区的BWP可以是由服务小区所属基站确定的，也可以是由目标小区所属基站确定的。BWP配置信息所指示的BWP可以包括：用于接入目标小区的初始BWP，和/或用于传输业务数据的首个激活BWP等。
这里，BWP配置信息指示的BWP可以是目标小区所属基站确定的。基站可以基于UE的类型确定适用于UE类型的BWP。例如，当切换的UE为第一类型UE时，可以为第一类型UE配置带宽较窄的BWP，使得配置的BWP能够符合第一类型UE的支持能力；当切换的UE为第二类型UE时，可以为第二类型UE配置带宽较宽的BWP。
在一个实施例中，UE可以上报自身的UE类型。服务小区所属基站在向目标小区所属基站发送切换请求时，可以在切换请求中携带UE的类型。目标小区所属基站可以基于UE的类型配置该UE的BWP。例如，UE可以向服务小区所属基站上报自身的UE类型，切换过程中服务小区所属基站可以向目标小区所属基站指示UE的类型。
目标小区所属基站确定配置给第一类型UE的BWP后，可以发送给第一类型UE的服务小区所属基站，再由服务小区所属基站发送给UE。
UE接收到BWP配置信息后，可以基于BWP配置信息指示的目标小区的BWP进行数据传输：如接收随机接入响应、传输业务数据等。由于BWP是基于UE的类型配置的，因此，UE可以支持该BWP。
如此，基于UE的类型为UE配置切换的目标小区的BWP，减少由于配置的BWP不能被UE所支持的情况，提高小区切换成功率，提高通信可靠性。
在一个实施例中，
所述BWP配置信息指示的所述第一类型UE对应的所述BWP，包括以下至少之一：
首个激活下行初始BWP；
首个激活上行初始BWP；
第一下行初始BWP；
第一上行初始BWP。
首个激活下行初始BWP可以是第一类型UE，如Redcap UE在目标小区内进行业务数据传输时采用的初始的激活下行BWP。第二类型UE，如eMMB UE能够支持的BWP的带宽大于第一类型UE能够支持的BWP的带宽，因此，基站配置给第一类型UE的首个激活下行初始BWP的带宽，小于或等于配置给第二类型UE的首个激活下行初始BWP的带宽，如此，使得配置给第一类型UE的首个激活下行初始BWP的带宽能够符合第一类型UE的支持能力。
首个激活上行初始BWP可以是第一类型UE，如Redcap UE在目标小区内进行业务数据传输时采用的初始的激活上行BWP。第二类型UE，如eMMB UE能够支持的BWP的带宽大于第一类型UE能够支持的BWP的带 宽，因此，基站配置给第一类型UE的首个激活上行初始BWP的带宽，小于或等于配置给第二类型UE的首个激活上行初始BWP的带宽，如此，使得配置给第一类型UE的首个激活上行初始BWP的带宽能够符合第一类型UE的支持能力。
第一下行初始BWP可以是第一类型UE在目标小区内进行随机接入的BWP，例如，第一下行初始BWP可以是第一类型UE在目标小区内接收随机接入响应(RAR，Random Access Response)的BWP；第一下行初始BWP也可以是第一类型UE在目标小区内接收寻呼(paging)的BWP。例如，第一下行初始BWP可以是采用DownlinkConfigCommon配置的initialDownlinkBWP-RedCap。基站可以将第一下行初始BWP的带宽配置成小于或等于配置给第二类型UE的下行初始BWP的带宽，如此，使得第一下行初始BWP的带宽能够符合第一类型UE的支持能力。
示例性的，第一下行初始BWP可以是Redcap UE专用的下行初始BWP(RedCap-specific initial DL BWP)。
第一上行初始BWP可以是第一类型UE在目标小区内进行随机接入的BWP。基站可以将第一上行初始BWP的带宽配置成小于或等于配置给第二类型UE的下行初始BWP的带宽，如此，使得第一上行初始BWP的带宽能够符合第一类型UE的支持能力。
示例性的，第一上行初始BWP可以是Redcap UE专用的上行初始BWP(RedCap-specific initial UL BWP)。
如此，基于UE的类型为UE配置切换的目标小区的BWP，减少由于配置的BWP不能被UE所支持的情况，提高小区切换成功率，提高通信可靠性。
在一个实施例中，
首个激活下行初始BWP内不具有同步信号块SSB；
或者，
首个激活下行初始BWP内具有SSB。
配置给第一类型UE的首个激活下行初始BWP内可以不具有SSB。这里，SSB可以包括:小区定义SSB(CD-SSB，cellDefining SSB)、或者非小区定义SSB(NCD-SSB，Non Cell-Defining SSB)。其中，CD-SSB具有有***信息块1(SIB，System Information Block 1)，即剩余最小***信息(RMSI，remain system information)，可以用于指示一个小区，并且CD-SSB可以用于同步或用于信号测量。NCD-SSB不能用于确定小区，NCD-SSB可以用于同步或用于信号测量。
在一个实施例中，响应于所述首个激活下行初始BWP内不具有SSB，第一类型UE通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
配置给第一类型UE的首个激活下行初始BWP不具有SSB，第一类UE可以使用具有SSB的下行初始BWP进行同步。例如，第一类UE可以在目标小区内，通过解码MIB，获取MIB配置的下行初始BWP进行同步和/或无线信号测量，例如，通过MIB配置的专用的下行初始BWP进行同步和/或测量；或者，第一类UE可以采用第二类UE使用的下行初始BWP进行同步同步和/或无线信号测量。
配置给第一类型UE的首个激活下行初始BWP内可以具有SSB。这里，SSB可以包括：CD-SSB、或者NCD-SSB。第一类型UE可以基于第一首个激活下行初始BWP内的SSB完成同步和/或无线信号测量。
首个激活下行初始BWP内具有SSB可以包括：首个激活下行初始BWP内具有CD-SSB，或者首个激活下行初始BWP内具有NCD-SSB。
如果首个激活下行初始BWP不具有SSB，则可以加快切换过程中的同步和测量，优化了性能。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述首个激活下行初始BWP内具有非小区定义同步信号块NCD-SSB。
基站可以基于第一类型UE的预定能力，为第一类型UE配置具有NCD-SSB的首个激活下行初始BWP。
在一个实施例中，预定能力可以是目标小区所属基站(目标基站)从服务小区所属基站(原基站)获取的。例如，第一类型UE的预定能力可以携带在原基站发送给目标基站的切换请求中。预定能力可以是目标小区所属基站(目标基站)从核心网获取的。第一类型UE可以在与原基站连接时，向原基站和/或核心网发送自身的预定能力。
预定能力可以包括第一类型UE对首个激活下行初始BWP的要求。例如，预定能力可以是：第一类型UE支持特征组(Feature Group)FG 6-1，但是期待BWP上包含NCD-SSB，并且不包含CORESET#0/SIB等。
在一个实施例中，
第一下行初始BWP内不具有SSB；
或者，
第一下行初始BWP内具有SSB。
第一下行初始BWP内可以不具有SSB。这里，SSB可以包括:CD-SSB、或者NCD-SSB。CD-SSB具有有***信息块1(SIB，System Information Block1)，即剩余最小***信息(RMSI，remain system information)，可以用于指示一个小区，并且CD-SSB可以用于同步或用于信号测量。NCD-SSB不能用于确定小区，NCD-SSB可以用于同步或用于信号测量。
在一个实施例中，响应于所述第一下行初始BWP内不具有SSB，第一类型UE通过所述目标小区内具有SSB的下行初始BWP与所述目标小区进行同步和/或无线信号测量。
这种情况下，需要额外的收发机转化的时长，就会增大切换过程中同步和随机接入的时延。第一下行初始BWP内不具有SSB，可以加快切换过程中的同步和测量，优化了性能。
第一下行初始BWP内不具有SSB，第一类UE可以使用具有SSB的下行初始BWP进行同步。例如，第一类UE可以在目标小区内，通过解码MIB，获取MIB配置的下行初始BWP进行同步，例如，通过MIB配置的专用的下行初始BWP进行同步；或者，第一类UE可以采用第二类UE使用的下行初始BWP进行同步和/或无线信号测量。
第一下行初始BWP内可以具有SSB。这里，SSB可以包括:CD-SSB、或者NCD-SSB。第一类型UE可以基于第一下行初始BWP内的SSB完成同步和/或无线信号测量。
第一下行初始BWP内具有SSB可以包括：第一下行初始BWP内具有CD-SSB，或者第一下行初始BWP内具有NCD-SSB。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述第一下行初始BWP内具有NCD-SSB。
基站可以基于第一类型UE的预定能力，为第一类型UE配置具有NCD-SSB的第一下行初始BWP。
在一个实施例中，预定能力可以是目标小区所属基站(目标基站)从服务小区所属基站(原基站)获取的。例如，第一类型UE的预定能力可以携带在原基站发送给目标基站的切换请求中。预定能力可以是目标小区所属基站(目标基站)从核心网获取的。第一类型UE可以在与原基站连接时，向原基站和/或核心网发送自身的预定能力。
预定能力可以包括第一类型UE对第一下行初始BWP的要求。例如，预定能力可以是：第一类型UE支持FG 6-1，但是期待BWP上包含NCD-SSB，并且不包含CORESET#0/SIB等。
如图3所示，本示例性实施例提供一种信息传输方法，可以被蜂窝移动通信***的基站执行，包括以下至少之一：
步骤301a：响应于所述目标小区配置有用于所述第一类型UE的第二下行初始BWP，将所述第二下行初始BWP确定为所述第一下行初始BWP；
步骤301b：响应于所述目标小区配置有用于第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽小于或等于所述第一类型UE支持的下行BWP的带宽，将所述第三下行初始BWP确定为所述第一下行初始BWP；
步骤301c：响应于所述目标小区配置有用于所述第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽大于所述第一类型UE支持的下行BWP的带宽，将所述目标小区对应MIB中配置的第四下行初始BWP确定为所述第一下行初始BWP；
步骤301d：响应于所述目标小区未配置有用于所述第二类型UE的第三下行初始BWP，将所述目标小区对应MIB中配置的第五下行初始BWP确定为所述第一下行初始BWP。
步骤301a、步骤301b、步骤301c、和/或步骤301d可以单独实施，也可以与步骤201结合实施。
若目标小区中，为第一类型UE配置了专用的第二下行初始BWP，例如，为Redcap UE配置了专用的下行初始BWP(RedCap-specific initial DL BWP)，则网络设备直接将第二下行初始BWP确定为所述第一下行初始BWP，并通过BWP配置信息向第一类型UE进行指示。第一类型UE将利用该初始BWP在切换的时候进行随机接入。这里，专用的下行初始BWP可以是基站在SIB1中单独为Redcap UE配置的BWP。专用的下行初始BWP可以用于UE的初始随机接入，也可以用于UE的小区切换。这里，网络设备可以包括接入网设备和/或核心网设备等。
若目标小区中，没有为第一类型UE配置了专用的第二下行初始BWP，并且为第二类型UE，如EMMB UE等配置有第三下行初始BWP，并且第三下行初始BWP的带宽小于或等于第一类型UE，如Redcap UE支持的带宽(FR1为20M，FR2为100M)，则网络设备直接将第三下行初始BWP确定为所述第一下行初始BWP，小区切换时候通过BWP配置信息向第一类型UE进行指示；第一类型UE将利用该初始BWP在切换的时候进行随机接入。
若此时目标小区中没有为第一类型UE配置了专用的第二下行初始BWP，若目标小区中，没有为第一类型UE配置了专用的第二下行初始BWP，并且为第二类型UE，如eMMB UE等配置有第三下行初始BWP，并且第三下行初始BWP的带宽大于第一类型UE，如Redcap UE支持的带宽(FR1为20M，FR2为100M),网络设备直接将MIB配置的第四下行初始BWP确定为所述第一下行初始BWP，小区切换时候通过BWP配置信息向第一类型UE进行指示，第一类UE将利用该初始BWP在切换的时候进行随机接入或者可以在目标小区内，通过解码MIB，获取MIB配置的第四下行初始BWP进行随机接入。
若目标小区中，为第二类型UE，如eMMB UE等配置有第三下行初始BWP，并且也没为第一类型UE配置专用的下行初始BWP，那么，网络设备直接将MIB配置的第四下行初始BWP确定为所述第一下行初始BWP，小区切换时候通过BWP配置信息向第一类型UE进行指示，第一类UE将利用该初始BWP在切换的时候进行随机接入或者可以在目标小区内，通过解码MIB，获取MIB配置的第五下行初始BWP进行随机接入。
在一个实施例中，协议限定在切换过程中，必须要保证尽快接入，则可以在第一下行初始BWP内配置有SSB。则此时为常规用户配置的下行初始BWP或者MIB配置的下行初始BWP就可以配置给终端作为切换时接 入。因为该类初始BWP通常都具有CD-SSB
在一个实施例中，此时不管目标小区中是否为第一类型UE配置了专用的第二下行初始BWP，若目标小区中，为第二类型UE，如EMMB UE等配置有第三下行初始BWP，并且第三下行初始BWP的带宽小于或等于第一类型UE，如Redcap UE支持的带宽(FR1为20M，FR2为100M)，则网络设备直接将第三下行初始BWP确定为所述第一下行初始BWP，小区切换时候通过BWP配置信息向第一类型UE进行指示；第一类型UE将利用该初始BWP在切换的时候进行随机接入。
此时不管目标小区中是否为第一类型UE配置了专用的第二下行初始BWP，若目标小区中，为第二类型UE，如eMMB UE等配置有第三下行初始BWP，并且第三下行初始BWP的带宽大于第一类型UE，如Redcap UE支持的带宽(FR1为20M，FR2为100M),网络设备直接将MIB配置的第四下行初始BWP确定为所述第一下行初始BWP，小区切换时候通过BWP配置信息向第一类型UE进行指示，第一类UE将利用该初始BWP在切换的时候进行随机接入或者可以在目标小区内，通过解码MIB，获取MIB配置的第四下行初始BWP进行随机接入。
如图4所示，本示例性实施例提供一种信息传输方法，可以被蜂窝移动通信***的基站执行，包括以下至少之一：
步骤401a：响应于所述目标小区配置有用于所述第一类型UE的第二上行初始BWP，将所述第二上行初始BWP确定为所述第一上行初始BWP；
步骤401b：响应于所述目标小区配置有用于第二类型UE的第三上行初始BWP，并且所述第三上行初始BWP的带宽小于或等于所述第一类型UE支持的上行BWP的带宽，将所述第三上行初始BWP确定为所述第一上行初始BWP。
步骤401a和/或步骤401b可以单独实施，也可以与步骤301a、步骤 301b、步骤301c、步骤301d、和/或步骤201结合实施。
若目标小区中，为第一类型UE配置了专用的第二上行初始BWP，例如，为Redcap UE配置了专用的上行初始BWP(RedCap-specific initial UL BWP)，则网络设备直接将第二上行初始BWP确定为所述第一上行初始BWP，并通过BWP配置信息向第一类型UE进行指示。第一类型UE将利用该初始BWP在切换的时候进行随机接入。
若目标小区中，为第二类型UE，如EMMB UE等配置有第三上行初始BWP，并且第三下行初始BWP的带宽小于或等于第一类型UE，如Redcap UE支持的带宽，则网络设备直接将第三上行初始BWP确定为所述第一上行初始BWP，小区切换时候通过BWP配置信息向第一类型UE进行指示；第一类型UE将利用该初始BWP在切换的时候进行随机接入。
如图5所示，本示例性实施例提供一种信息传输方法，所述方法可以被蜂窝移动通信***的UE执行，包括以下至少之一：
步骤501：接收来自基站的小区切换命令，其中，小区切换命令携带有指示目标小区中所述第一类型UE对应的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是所述基站基于所述第一类型UE的类型确定的。
在UE从服务小区切换到目标小区过程中，服务小区所属基站可以向UE发送切换命令，指示UE切换到目标小区。服务小区和目标小区可以是同一基站生成的小区，也可以是不同基站生成的小区。服务小区所属基站可以从目标小区所属基站进行资源的申请与分配。
第一类型UE可以是处于RRC连接态的UE。其中，该第一类型UE的信号接收能力低于第二类型UE的信号接收能力，也就是说，第一类型UE相对第二类型UE可以具有较低的信号接收能力。例如，第一类型UE于第二类型UE相比具有较少数量的接收天线。第一类型UE具有较弱的BWP 支持能力，例如，第一类型UE支持的BWP的带宽在FR1范围内为20M，在FR2范围内为100M。第二类型UE支持的BWP的带宽大于第一类型UE支持的BWP的带宽。
示例性的，第一类型UE可以是3GPP Release 17(R17)中引入的Redcap类型UE。第一类型UE也可以是后续3GPP Release版本中引入的增强形Redcap类型UE；例如，第一类型的UE可以是Redcap类型UE。第二类型的UE可以是eMMB类型UE。
BWP配置信息所指示的目标小区的BWP可以是由服务小区所属基站确定的，也可以是由目标小区所属基站确定的。BWP配置信息所指示的BWP可以包括：用于接入目标小区的初始BWP，和/或用于传输业务数据的首个激活BWP等。
这里，BWP配置信息指示的BWP可以是目标小区所属基站确定的。基站可以基于UE的类型确定适用于UE类型的BWP。例如，当切换的UE为第一类型UE时，可以为第一类型UE配置带宽较窄的BWP，使得配置的BWP能够符合第一类型UE的支持能力；当切换的UE为第二类型UE时，可以为第二类型UE配置带宽较宽的BWP。
在一个实施例中，UE可以上报自身的UE类型。服务小区所属基站在向目标小区所属基站发送切换请求时，可以在切换请求中携带UE的类型。目标小区所属基站可以基于UE的类型配置该UE的BWP。例如，UE可以向服务小区所属基站上报自身的UE类型，切换过程中服务小区所属基站可以向目标小区所属基站指示UE的类型。
目标小区所属基站确定配置给第一类型UE的BWP后，可以发送给第一类型UE的服务小区所属基站，再由服务小区所属基站发送给UE。
UE接收到BWP配置信息后，可以基于BWP配置信息指示的目标小区的BWP进行数据传输：如接收随机接入响应、传输业务数据等。由于 BWP是基于UE的类型配置的，因此，UE可以支持该BWP。
如此，基于UE的类型为UE配置切换的目标小区的BWP，减少由于配置的BWP不能被UE所支持的情况，提高小区切换成功率，提高通信可靠性。
在一个实施例中，所示第一类型UE对应的所述BWP，包括以下至少之一：
首个激活下行初始BWP；
首个激活上行初始BWP；
第一下行初始BWP；
第一上行初始BWP。
首个激活下行初始BWP可以是第一类型UE，如Redcap UE在目标小区内进行业务数据传输时采用的初始的激活下行BWP。第二类型UE，如eMMB UE能够支持的BWP的带宽大于第一类型UE能够支持的BWP的带宽，因此，基站配置给第一类型UE的首个激活下行初始BWP的带宽，小于或等于配置给第二类型UE的首个激活下行初始BWP的带宽，如此，使得配置给第一类型UE的首个激活下行初始BWP的带宽能够符合第一类型UE的支持能力。
首个激活上行初始BWP可以是第一类型UE，如Redcap UE在目标小区内进行业务数据传输时采用的初始的激活上行BWP。第二类型UE，如eMMB UE能够支持的BWP的带宽大于第一类型UE能够支持的BWP的带宽，因此，基站配置给第一类型UE的首个激活上行初始BWP的带宽，小于或等于配置给第二类型UE的首个激活上行初始BWP的带宽，如此，使得配置给第一类型UE的首个激活上行初始BWP的带宽能够符合第一类型UE的支持能力。
第一下行初始BWP可以是第一类型UE在目标小区内进行随机接入的 BWP，例如，第一下行初始BWP可以是第一类型UE在目标小区内接收随机接入响应(RAR，Random Access Response)的BWP；第一下行初始BWP也可以是第一类型UE在目标小区内接收寻呼(paging)的BWP。例如，第一下行初始BWP可以是采用DownlinkConfigCommon配置的initialDownlinkBWP-RedCap。基站可以将第一下行初始BWP的带宽配置成小于或等于配置给第二类型UE的下行初始BWP的带宽，如此，使得第一下行初始BWP的带宽能够符合第一类型UE的支持能力。
示例性的，第一下行初始BWP可以是Redcap UE专用的下行初始BWP(RedCap-specific initial DL BWP)。
第一上行初始BWP可以是第一类型UE在目标小区内进行随机接入的BWP。基站可以将第一上行初始BWP的带宽配置成小于或等于配置给第二类型UE的下行初始BWP的带宽，如此，使得第一上行初始BWP的带宽能够符合第一类型UE的支持能力。
示例性的，第一上行初始BWP可以是Redcap UE专用的上行初始BWP(RedCap-specific initial UL BWP)。
如此，基于UE的类型为UE配置切换的目标小区的BWP，减少由于配置的BWP不能被UE所支持的情况，提高小区切换成功率，提高通信可靠性。
在一个实施例中，
首个激活下行初始BWP内不具有同步信号块SSB；
或者，
首个激活下行初始BWP内具有SSB。
配置给第一类型UE的首个激活下行初始BWP内可以不具有SSB。这里，SSB可以包括:小区定义SSB(CD-SSB，cell-Defining SSB)、或者非小区定义SSB(NCD-SSB，Non Cell-Defining SSB)。其中，CD-SSB，具有有 ***信息块1(SIB，System Information Block 1)，即剩余最小***信息(RMSI，remain system information)，可以用于指示一个小区，并且CD-SSB可以用于同步或用于信号测量。NCD-SSB不能用于确定小区，可以用于同步或用于信号测量。
配置给第一类型UE的首个激活下行初始BWP内可以具有SSB。这里，SSB可以包括：CD-SSB、或者NCD-SSB。第一类型UE可以基于第一首个激活下行初始BWP内的SSB完成同步和/或无线信号测量。包含SSB则有利于终端尽快在切换过程中尽快完成同步和随机接入。
首个激活下行初始BWP内具有SSB可以包括：首个激活下行初始BWP内具有CD-SSB，或者首个激活下行初始BWP内具有NCD-SSB。
如图6所示，本示例性实施例提供一种信息传输方法，可以被蜂窝移动通信***的UE执行，包括：
步骤601：响应于所述首个激活下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
步骤601可以单独实施，也可以和步骤501结合实施。
配置给第一类型UE的首个激活下行初始BWP不具有SSB，第一类UE可以使用具有SSB的下行初始BWP进行同步。例如，第一类UE可以在目标小区内，通过解码MIB，获取MIB配置的下行初始BWP进行同步和/或无线信号测量，例如，通过MIB配置的专用的下行初始BWP进行同步和/或测量；或者，第一类UE可以采用第二类UE使用的下行初始BWP进行同步同步和/或无线信号测量。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述首个激活下行初始BWP内具有非小区定义同步信号块NCD-SSB。包含NCD-SSB则有利于终端尽快在切换过程中尽快完成同步和随机接入。
基站可以基于第一类型UE的预定能力，为第一类型UE配置具有NCD-SSB的首个激活下行初始BWP。
在一个实施例中，预定能力可以是目标小区所属基站(目标基站)从服务小区所属基站(原基站)获取的。例如，第一类型UE的预定能力可以携带在原基站发送给目标基站的切换请求中。预定能力可以是目标小区所属基站(目标基站)从核心网获取的。第一类型UE可以在与原基站连接时，向原基站和/或核心网发送自身的预定能力。
预定能力可以包括第一类型UE对首个激活下行初始BWP的要求。例如，预定能力可以是：第一类型UE支持FG 6-1，但是期待BWP上包含NCD-SSB，并且不包含CORESET#0/SIB等。
在一个实施例中，
第一下行初始BWP内不具有SSB；
或者，
第一下行初始BWP内具有SSB。
第一下行初始BWP内可以不具有SSB。这里，SSB可以包括:CD-SSB、或者NCD-SSB。CD-SSB具有有***信息块1(SIB，System Information Block1)，即剩余最小***信息(RMSI，remain system information)，可以用于指示一个小区，并且CD-SSB可以用于同步或用于信号测量。NCD-SSB不能用于确定小区，NCD-SSB可以用于同步或用于信号测量。
可以限定第一下行初始BWP内需要具有SSB，包含SSB则有利于终端尽快在切换过程中尽快完成同步和随机接入。这里，SSB可以包括:CD-SSB、或者NCD-SSB。第一类型UE可以基于第一下行初始BWP内的SSB完成同步和/或无线信号测量。
第一下行初始BWP内具有SSB可以包括：第一下行初始BWP内具有CD-SSB，或者第一下行初始BWP内具有NCD-SSB。
如图7所示，本示例性实施例提供一种信息传输方法，可以被蜂窝移动通信***的UE执行，包括：
步骤701：响应于所述第一下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
步骤701可以单独实施，也可以与步骤501和/或步骤601结合实施。
第一下行初始BWP内不具有SSB，第一类UE可以使用具有SSB的下行初始BWP进行同步。例如，第一类UE可以在目标小区内，通过解码MIB，获取MIB配置的下行初始BWP进行同步，例如，通过MIB配置的专用的下行初始BWP进行同步；或者，第一类UE可以采用第二类UE使用的下行初始BWP进行同步和/或无线信号测量。
如图8所示，本示例性实施例提供一种信息传输方法，可以被蜂窝移动通信***的UE执行，包括：
步骤801：向基站发送指示所述第一类型用户设备UE是否具有预设能力的指示信息，其中，所述预设能力，用于供基站确定是否向所述第一类型用户设备UE指示具有非小区定义同步信号块NCD-SSB的所述首个激活下行初始BWP和/或具有NCD-SSB的第一下行初始BWP。
步骤801可以单独实施，也可以与步骤501和/或步骤601和/或步骤701结合实施。
在一个实施例中，预定能力可以是目标小区所属基站(目标基站)从服务小区所属基站(原基站)获取的。例如，第一类型UE的预定能力可以携带在原基站发送给目标基站的切换请求中。预定能力可以是目标小区所属基站(目标基站)从核心网获取的。第一类型UE可以在与原基站连接时，向原基站和/或核心网发送自身的预定能力。
预定能力可以包括第一类型UE对首个激活下行初始BWP和/或第一下行初始BWP的要求。例如，预定能力可以是：第一类型UE支持FG 6-1， 但是期待首个激活下行初始BWP和/或第一下行初始BWP上包含NCD-SSB，并且不包含CORESET#0/SIB等。
以下结合上述任意实施例提供一个具体示例：
1、一种为特定类型终端，切换时配置初始BWP的方式；
a)特定类型终端为R17中引入的Redcap类型终端；
b)特定类型终端为后续版本中引入的增强形Redcap类型终端；
c)目标基站将从切换请求中获取到用户的类型是特定类型终端；
2、约定对于特定类型终端的连接态用户，其切换时候指定的首次激活(first active)下行初始BWP可以不需要包含SSB(CD-SSB或者NCD-SSB)：
a)若网络设备在切换命令中包含了首次激活下行初始BWP，该下行初始BWP可以不配置有CD-SSB或者NCD-SSB；
终端可以使用具有SSB的下行初始BWP进行同步，比如MIB配置的下行初始BWP；或者普通(normal)用户使用的下行初始BWP；
3、约定对于特定类型终端的连接态用户，其切换时候指定的首次激活下行初始BWP需要包含SSB(CD-SSB或者NCD-SSB)：
a)若网络设备在切换命令中包含了首次激活下行初始BWP，则需要为该下行初始BWP配置有CD-SSB或者NCD-SSB；(即若该BWP上没有CD-SSB,则需要额外配置一个NCD-SSB)。
b)进一步：可以为为特定类型终端切换时候指定的首次激活下行初始BWP配置NCD-SSB需要基于基站获取到的终端的能力，作为一种实施例，终端的能力可以是目标基站从原基站获取(比如在切换请求中携带)或者核心网获取。
终端(RedCap UE)的能力，可以是终端支持FG 6-1，但是期待BWP上包含NCD-SSB，而不包含CORESET#0/SIB。
4、约定对于特定类型终端的连接态用户，其切换时候指定的下行初始BWP为特定类型终端配置的专用的下行初始BWP(即DownlinkConfigCommon中initialDownlinkBWP-RedCap，区别于以上的首个激活初始BWP)可以不需要包含CD-SSB。
a)若目标小区中，为特定类型终端配置了专用的下行初始BWP存在配置，则网络设备直接配置为特定类型终端配置专用的下行初始BWP；终端将利用该初始BWP在切换的时候进行随机接入；
此时为为特定类型终端配置了专用的下行初始BWP不一定包含SSB，则终端需要使用其他的初始BWP(比如给普通用户的初始BWP)进行同步和测量；
进一步：可以为为特定类型终端配置了专用的下行初始BWP配置NCD-SSB；此时像比如没有SSB的情况，则可以加快切换过程中的同步和测量，优化了性能。
进一步：为特定类型终端配置了专用的下行初始BWP配置NCD-SSB需要基于终端的能力，比如终端支持配置NCD-SSB；
如：终端(RedCap UE)的能力，可以是终端支持FG 6-1，但是期待BWP上包含NCD-SSB，而不包含CORESET#0/SIB。
此时，若为特定类型终端配置了专用的下行初始BWP上不包含SSB，则终端在随机接入时使用具有SSB的下行初始BWP进行同步和测量，比如MIB配置的下行初始BWP；或者Normal用户使用的下行初始BWP；
5、约定对于特定类型终端的连接态用户，其切换时候指定的下行初始BWP(即DownlinkConfigCommon中initialDownlinkBWP)需要包含SSB(CD-SSB)。这么做的目的是保证切换过程中终端可以尽快同步和完成随机接入。
a)若目标小区中，为普通用户配置使用的下行初始BWP存在配置，且其带宽不大于Redcap用户支持的带宽(FR1为20M，FR2为100M)，则网络设备直接配置普通用户配置使用的下行初始BWP配置给特定类型终端作为切换时候指定的下行初始BWP；终端将利用该初始BWP在切换的时候进行随机接入；
b)若目标小区中，为普通用户配置使用的下行初始BWP存在配置，且其带宽大于Redcap用户支持的带宽(FR1为20M，FR2为100M)，则网络设备直接配置MIB配置的下行初始BWP配置给特定类型终端作为切换时候指定的下行初始BWP；终端将利用该初始BWP在切换的时候进行随机接入；
c)若目标小区中，为普通用户配置使用的下行初始BWP不存在配置，则网络设备直接配置MIB配置的下行初始BWP配置给特定类型终端作为切换时候指定的下行初始BWP；终端将利用该初始BWP在切换的时候进行随机接入；
6、约定对于特定类型终端的连接态用户，其切换时候指定的上行初始BWP为为特定类型终端配置了专用的上行初始BWP[RedCap-specific initial UL BWP configuration)；
a)作为一种实施例，若目标基站没有配置为特定类型终端配置了专用的下行初始BWP，则使用为普通用户配置的上行初始BWP；此时目标基站支持Redcap，要么目标基站为特定类型终端配置了专用的下行初始BWP，要么为普通用户配置的上行初始BWP，其带宽是在Redcap用户带宽范围内的。
本发明实施例还提供了一种信息传输装置，如图9所示，应用于蜂窝移动无线通信的基站中，其中，所述装置100包括：
第一收发模块110，配置为向第一类型用户设备UE发送小区切换命令， 其中，小区切换命令携带有指示目标小区的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是基于所述第一类型UE的类型确定的。
在一个实施例中，所述BWP配置信息指示的所述第一类型UE对应的所述BWP，包括以下至少之一：
首个激活下行初始BWP；
首个激活上行初始BWP；
第一下行初始BWP；
第一上行初始BWP。
在一个实施例中，首个激活下行初始BWP内不具有同步信号块SSB；
或者，
首个激活下行初始BWP内具有SSB。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述首个激活下行初始BWP内具有非小区定义同步信号块NCD-SSB。
在一个实施例中，第一下行初始BWP内不具有SSB；
或者，
第一下行初始BWP内具有SSB。
在一个实施例中，响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述第一下行初始BWP内具有非小区定义同步信号块NCD-SSB。
在一个实施例中，所述装置还包括第一处理模块120，所述第一处理模块120配置为以下至少之一：
响应于所述目标小区配置有用于所述第一类型UE的第二下行初始BWP，将所述第二下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区配置有用于第二类型UE的第三下行初始BWP， 并且所述第三下行初始BWP的带宽小于或等于所述第一类型UE支持的下行BWP的带宽，将所述第三下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区配置有用于所述第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽大于所述第一类型UE支持的下行BWP的带宽，将所述目标小区对应MIB中配置的第四下行初始BWP确定为所述第一下行初始BWP；
响应于所述目标小区未配置有用于所述第二类型UE的第三下行初始BWP，将所述目标小区对应MIB中配置的第五下行初始BWP确定为所述第一下行初始BWP。
在一个实施例中，所述装置还包括第一处理模块120，所述第一处理模块配置120为以下至少之一：
响应于所述目标小区配置有用于所述第一类型UE的第二上行初始BWP，将所述第二上行初始BWP确定为所述第一上行初始BWP；
响应于所述目标小区配置有用于第二类型UE的第三上行初始BWP，并且所述第三上行初始BWP的带宽小于或等于所述第一类型UE支持的上行BWP的带宽，将所述第三上行初始BWP确定为所述第一上行初始BWP。
本发明实施例还提供了一种信息传输装置，如图10所示，应用于蜂窝移动无线通信的UE中，其中，所述装置200包括：
第二收发模块210，配置为接收来自基站的小区切换命令，其中，小区切换命令携带有指示目标小区中所述第一类型用户设备UE对应的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是所述基站基于所述第一类型UE的类型确定的。
在一个实施例中，所示第一类型UE对应的所述BWP，包括以下至少之一：
首个激活下行初始BWP；
首个激活上行初始BWP；
第一下行初始BWP；
第一上行初始BWP。
在一个实施例中，首个激活下行初始BWP内不具有同步信号块SSB；
或者，
首个激活下行初始BWP内具有SSB。
在一个实施例中，所述装置还包括第二处理模块220，所述第二处理模块220配置为：
响应于所述首个激活下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
在一个实施例中，第一下行初始BWP内不具有SSB；
或者，
第一下行初始BWP内具有SSB。
在一个实施例中，所述装置还包括第二处理模块220，所述第二处理模块220配置为：
响应于所述第一下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
在一个实施例中，所述第二收发模块210，还配置为：
向基站发送指示所述第一类型用户设备UE是否具有预设能力的指示信息，其中，所述预设能力，用于供基站确定是否向所述第一类型用户设备UE指示具有非小区定义同步信号块NCD-SSB的所述首个激活下行初始BWP和/或具有NCD-SSB的第一下行初始BWP。
在示例性实施例中，第一收发模块110、第一处理模块120、第二收发模块210和第二处理模块220等可以被一个或多个中央处理器(CPU，Central Processing Unit)、图形处理器(GPU，Graphics Processing Unit)、基带处理 器(BP，Baseband Processor)、应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、现场可编程门阵列(FPGA，Field-Programmable Gate Array)、通用处理器、控制器、微控制器(MCU，Micro Controller Unit)、微处理器(Microprocessor)、或其他电子元件实现，用于执行前述方法。
图11是根据一示例性实施例示出的一种用于信息传输的装置3000的框图。例如，装置3000可以是移动电话、计算机、数字广播终端、消息收发设备、游戏控制台、平板设备、医疗设备、健身设备、个人数字助理等。
参照图11，装置3000可以包括以下一个或多个组件：处理组件3002、存储器3004、电源组件3006、多媒体组件3008、音频组件3010、输入/输出(I/O)接口3012、传感器组件3014、以及通信组件3016。
处理组件3002通常控制装置3000的整体操作，诸如与显示、电话呼叫、数据通信、相机操作和记录操作相关联的操作。处理组件3002可以包括一个或多个处理器3020来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件3002可以包括一个或多个模块，便于处理组件3002和其他组件之间的交互。例如，处理组件3002可以包括多媒体模块，以方便多媒体组件3008和处理组件3002之间的交互。
存储器3004被配置为存储各种类型的数据以支持在装置3000的操作。这些数据的示例包括用于在装置3000上操作的任何应用程序或方法的指令、联系人数据、电话簿数据、消息、图片、视频等。存储器3004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)、电可擦除可编程只读存储器(EEPROM)、可擦除可编程只读存储器(EPROM)、可编程只读存储器(PROM)、只读存储器(ROM)、磁存储器、快闪存储器、磁盘或光盘。
电源组件3006为装置3000的各种组件提供电力。电源组件3006可以包括电源管理***、一个或多个电源、及其他与为装置3000生成、管理和分配电力相关联的组件。
多媒体组件3008包括在装置3000和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件3008包括一个前置摄像头和/或后置摄像头。当装置3000处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜***或具有焦距和光学变焦能力。
音频组件3010被配置为输出和/或输入音频信号。例如，音频组件3010包括一个麦克风(MIC)，当装置3000处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器3004或经由通信组件3016发送。在一些实施例中，音频组件3010还包括一个扬声器，用于输出音频信号。
I/O接口3012为处理组件3002和***接口模块之间提供接口，上述***接口模块可以是键盘、点击轮、按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件3014包括一个或多个传感器，用于为装置3000提供各个方面的状态评估。例如，传感器组件3014可以检测到装置3000的打开/关闭状态、组件的相对定位，例如组件为装置3000的显示器和小键盘，传感器组件3014还可以检测装置3000或装置3000一个组件的位置改变、用户 与装置3000接触的存在或不存在、装置3000方位或加速/减速和装置3000的温度变化。传感器组件3014可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件3014还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件3014还可以包括加速度传感器、陀螺仪传感器、磁传感器、压力传感器或温度传感器。
通信组件3016被配置为便于装置3000和其他设备之间有线或无线方式的通信。装置3000可以接入基于通信标准的无线网络，如Wi-Fi、2G或3G，或它们的组合。在一个示例性实施例中，通信组件3016经由广播信道接收来自外部广播管理***的广播信号或广播相关信息。在一个示例性实施例中，通信组件3016还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术、红外数据协会(IrDA)技术、超宽带(UWB)技术、蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置3000可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器3004，上述指令可由装置3000的处理器3020执行以完成上述方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明实施例的其它实施方案。本申请旨在涵盖本发明实施例的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明实施例 的一般性原理并包括本公开实施例未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明实施例的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明实施例并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明实施例的范围仅由所附的权利要求来限制。

Claims (32)

  1. 一种信息传输方法，被基站执行，其中，所述方法包括：
    向第一类型用户设备UE发送小区切换命令，其中，小区切换命令携带有指示目标小区的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是基于所述第一类型UE的类型确定的。
  2. 根据权利要求1所述的方法，其中，
    所述BWP配置信息指示的所述第一类型UE对应的所述BWP，包括以下至少之一：
    首个激活下行初始BWP；
    首个激活上行初始BWP；
    第一下行初始BWP；
    第一上行初始BWP。
  3. 根据权利要求2所述的方法，其中，
    首个激活下行初始BWP内不具有同步信号块SSB；
    或者，
    首个激活下行初始BWP内具有SSB。
  4. 根据权利要求3所述的方法，其中，
    响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述首个激活下行初始BWP内具有非小区定义同步信号块NCD-SSB。
  5. 根据权利要求2所述的方法，其中，
    第一下行初始BWP内不具有SSB；
    或者，
    第一下行初始BWP内具有SSB。
  6. 根据权利要求5所述的方法，其中，
    响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示 的所述第一下行初始BWP内具有NCD-SSB。
  7. 根据权利要求2所述的方法，其中，所述方法还包括以下至少之一：
    响应于所述目标小区配置有用于所述第一类型UE的第二下行初始BWP，将所述第二下行初始BWP确定为所述第一下行初始BWP；
    响应于所述目标小区配置有用于第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽小于或等于所述第一类型UE支持的下行BWP的带宽，将所述第三下行初始BWP确定为所述第一下行初始BWP；
    响应于所述目标小区配置有用于所述第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽大于所述第一类型UE支持的下行BWP的带宽，将所述目标小区对应MIB中配置的第四下行初始BWP确定为所述第一下行初始BWP；
    响应于所述目标小区未配置有用于所述第二类型UE的第三下行初始BWP，将所述目标小区对应MIB中配置的第五下行初始BWP确定为所述第一下行初始BWP。
  8. 根据权利要求2所述的方法，其中，所述方法还包括以下至少之一：
    响应于所述目标小区配置有用于所述第一类型UE的第二上行初始BWP，将所述第二上行初始BWP确定为所述第一上行初始BWP；
    响应于所述目标小区配置有用于第二类型UE的第三上行初始BWP，并且所述第三上行初始BWP的带宽小于或等于所述第一类型UE支持的上行BWP的带宽，将所述第三上行初始BWP确定为所述第一上行初始BWP。
  9. 一种信息传输方法，被第一类型用户设备UE执行，其中，所述方法包括：
    接收来自基站的小区切换命令，其中，小区切换命令携带有指示目标小区中所述第一类型UE对应的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是所述基站基于所述第一类型UE的类型确定的。
  10. 根据权利要求9所述的方法，其中，
    所示第一类型UE对应的所述BWP，包括以下至少之一：
    首个激活下行初始BWP；
    首个激活上行初始BWP；
    第一下行初始BWP；
    第一上行初始BWP。
  11. 根据权利要求10所述的方法，其中，
    首个激活下行初始BWP内不具有同步信号块SSB；
    或者，
    首个激活下行初始BWP内具有SSB。
  12. 根据权利要求11所述的方法，其中，所述方法还包括：
    响应于所述首个激活下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
  13. 根据权利要求10所述的方法，其中，
    第一下行初始BWP内不具有SSB；
    或者，
    第一下行初始BWP内具有SSB。
  14. 根据权利要求13所述的方法，其中，所述方法还包括：
    响应于所述第一下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
  15. 根据权利要求10所述的方法，其中，所述方法还包括：
    向基站发送指示所述第一类型用户设备UE是否具有预设能力的指示信息，其中，所述预设能力，用于供基站确定是否向所述第一类型用户设备UE指示具有非小区定义同步信号块NCD-SSB的所述首个激活下行初始BWP和/或具有NCD-SSB的第一下行初始BWP。
  16. 一种信息传输装置，其中，所述装置包括：
    第一收发模块，配置为向第一类型用户设备UE发送小区切换命令，其中，小区切换命令携带有指示目标小区的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是基于所述第一类型UE的类型确定的。
  17. 根据权利要求16所述的装置，其中，
    所述BWP配置信息指示的所述第一类型UE对应的所述BWP，包括以下至少之一：
    首个激活下行初始BWP；
    首个激活上行初始BWP；
    第一下行初始BWP；
    第一上行初始BWP。
  18. 根据权利要求17所述的装置，其中，
    首个激活下行初始BWP内不具有同步信号块SSB；
    或者，
    首个激活下行初始BWP内具有SSB。
  19. 根据权利要求18所述的装置，其中，
    响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述首个激活下行初始BWP内具有非小区定义同步信号块NCD-SSB。
  20. 根据权利要求17所述的装置，其中，
    第一下行初始BWP内不具有SSB；
    或者，
    第一下行初始BWP内具有SSB。
  21. 根据权利要求20所述的装置，其中，
    响应于确定所述第一类型UE具有预定能力，所述BWP配置信息指示的所述第一下行初始BWP内具有非小区定义同步信号块NCD-SSB。
  22. 根据权利要求17所述的装置，其中，所述装置还包括第一处理模块，所述第一处理模块配置为以下至少之一：
    响应于所述目标小区配置有用于所述第一类型UE的第二下行初始BWP，将所述第二下行初始BWP确定为所述第一下行初始BWP；
    响应于所述目标小区配置有用于第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽小于或等于所述第一类型UE支持的下行BWP的带宽，将所述第三下行初始BWP确定为所述第一下行初始BWP；
    响应于所述目标小区配置有用于所述第二类型UE的第三下行初始BWP，并且所述第三下行初始BWP的带宽大于所述第一类型UE支持的下行BWP的带宽，将所述目标小区对应MIB中配置的第四下行初始BWP确定为所述第一下行初始BWP；
    响应于所述目标小区未配置有用于所述第二类型UE的第三下行初始BWP，将所述目标小区对应MIB中配置的第五下行初始BWP确定为所述第一下行初始BWP。
  23. 根据权利要求17所述的装置，其中，所述装置还包括第一处理模块，所述第一处理模块配置为以下至少之一：
    响应于所述目标小区配置有用于所述第一类型UE的第二上行初始BWP，将所述第二上行初始BWP确定为所述第一上行初始BWP；
    响应于所述目标小区配置有用于第二类型UE的第三上行初始BWP，并且所述第三上行初始BWP的带宽小于或等于所述第一类型UE支持的上行BWP的带宽，将所述第三上行初始BWP确定为所述第一上行初始BWP。
  24. 一种信息传输装置，其中，所述装置包括：
    第二收发模块，配置为接收来自基站的小区切换命令，其中，小区切换命令携带有指示目标小区中所述第一类型用户设备UE对应的带宽部分BWP的BWP配置信息，其中，所述目标小区的BWP是所述基站基于所述 第一类型UE的类型确定的。
  25. 根据权利要求24所述的装置，其中，
    所示第一类型UE对应的所述BWP，包括以下至少之一：
    首个激活下行初始BWP；
    首个激活上行初始BWP；
    第一下行初始BWP；
    第一上行初始BWP。
  26. 根据权利要求25所述的装置，其中，
    首个激活下行初始BWP内不具有同步信号块SSB；
    或者，
    首个激活下行初始BWP内具有SSB。
  27. 根据权利要求26所述的装置，其中，所述装置还包括第二处理模块，所述第二处理模块配置为：
    响应于所述首个激活下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
  28. 根据权利要求25所述的装置，其中，
    第一下行初始BWP内不具有SSB；
    或者，
    第一下行初始BWP内具有SSB。
  29. 根据权利要求28所述的装置，其中，所述装置还包括第二处理模块，所述第二处理模块配置为：
    响应于所述第一下行初始BWP内不具有SSB，通过所述目标小区内具有SSB的下行初始BWP进行同步和/或无线信号测量。
  30. 根据权利要求25所述的装置，其中，所述第二收发模块，还配置为：
    向基站发送指示所述第一类型用户设备UE是否具有预设能力的指示 信息，其中，所述预设能力，用于供基站确定是否向所述第一类型用户设备UE指示具有非小区定义同步信号块NCD-SSB的所述首个激活下行初始BWP和/或具有NCD-SSB的第一下行初始BWP。
  31. 一种通信设备装置，包括处理器、存储器及存储在存储器上并能够由所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如权利要求1至8、或9至15任一项所述信息传输方法的步骤。
  32. 一种存储介质，其上存储由可执行程序，其中，所述可执行程序被处理器执行时实现如权利要求1至8、或9至15任一项所述信息传输方法的步骤。
PCT/CN2022/083507 2022-03-28 2022-03-28 信息传输方法、装置、通信设备和存储介质 WO2023184121A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/083507 WO2023184121A1 (zh) 2022-03-28 2022-03-28 信息传输方法、装置、通信设备和存储介质
CN202280000955.XA CN114902730A (zh) 2022-03-28 2022-03-28 信息传输方法、装置、通信设备和存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/083507 WO2023184121A1 (zh) 2022-03-28 2022-03-28 信息传输方法、装置、通信设备和存储介质

Publications (1)

Publication Number Publication Date
WO2023184121A1 true WO2023184121A1 (zh) 2023-10-05

Family

ID=82729310

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/083507 WO2023184121A1 (zh) 2022-03-28 2022-03-28 信息传输方法、装置、通信设备和存储介质

Country Status (2)

Country Link
CN (1) CN114902730A (zh)
WO (1) WO2023184121A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240147432A1 (en) * 2022-11-01 2024-05-02 Mediatek Inc. Method And Apparatus For Supporting Small Data Transmission On A Bandwidth Part With Non-Cell-Defining Synchronization Signal Block

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111406378A (zh) * 2020-02-25 2020-07-10 北京小米移动软件有限公司 通信方法、装置及计算机存储介质
CN111615162A (zh) * 2019-06-28 2020-09-01 维沃移动通信有限公司 一种带宽部分bwp切换方法及设备
CN112567803A (zh) * 2018-08-09 2021-03-26 高通股份有限公司 无线通信中的带宽配置技术
US20210337511A1 (en) * 2020-04-24 2021-10-28 Qualcomm Incorporated Facilitating bandwidth part selection in wireless communication systems
CN114125998A (zh) * 2021-12-03 2022-03-01 星思连接(上海)半导体有限公司 小区接入方法、信息广播方法、装置及电子设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109803312B (zh) * 2017-11-17 2020-10-30 电信科学技术研究院 切换方法、终端和网络侧设备
EP3528538B1 (en) * 2018-02-15 2021-08-18 Panasonic Intellectual Property Corporation of America Bandwidth part operation during handover procedure
CN110475297B (zh) * 2018-05-10 2022-04-08 ***通信有限公司研究院 基于bwp的处理方法、装置、***、相关设备及存储介质
CN110958179B (zh) * 2019-11-27 2021-10-15 中国联合网络通信集团有限公司 终端部分带宽切换方法、装置及***
CN114071746A (zh) * 2020-08-07 2022-02-18 华为技术有限公司 一种通信方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112567803A (zh) * 2018-08-09 2021-03-26 高通股份有限公司 无线通信中的带宽配置技术
CN111615162A (zh) * 2019-06-28 2020-09-01 维沃移动通信有限公司 一种带宽部分bwp切换方法及设备
CN111406378A (zh) * 2020-02-25 2020-07-10 北京小米移动软件有限公司 通信方法、装置及计算机存储介质
US20210337511A1 (en) * 2020-04-24 2021-10-28 Qualcomm Incorporated Facilitating bandwidth part selection in wireless communication systems
CN114125998A (zh) * 2021-12-03 2022-03-01 星思连接(上海)半导体有限公司 小区接入方法、信息广播方法、装置及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MODERATOR (ERICSSON): "Email discussion summary for [102-e][228] NR_redcap_RRM_1", 3GPP DRAFT; R4-2206771, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG4, no. Electronic Meeting; 20220221 - 20220303, 25 February 2022 (2022-02-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052116951 *

Also Published As

Publication number Publication date
CN114902730A (zh) 2022-08-12

Similar Documents

Publication Publication Date Title
JP2023520478A (ja) 構成情報伝送方法および装置、通信機器および記憶媒体
WO2022056788A1 (zh) 通信方法及装置、网络设备、ue及存储介质
WO2022036649A1 (zh) 扩展非连续接收参数确定方法、通信设备和存储介质
WO2021030974A1 (zh) 寻呼配置方法、装置、通信设备及存储介质
WO2022126345A1 (zh) Drx配置方法及装置、通信设备和存储介质
WO2022052024A1 (zh) 参数配置方法、装置、通信设备和存储介质
WO2022183456A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2022155835A1 (zh) 切换配置确定方法、装置和通信设备装置
WO2022000200A1 (zh) 定位参考信号配置方法及装置、用户设备、存储介质
WO2021196139A1 (zh) 信息传输方法、装置、通信设备及存储介质
WO2022205472A1 (zh) 上行传输时域资源的确定方法及装置、ue、网络设备及存储介质
WO2022006759A1 (zh) 信息传输方法、装置、通信设备和存储介质
CN114128366A (zh) 寻呼参数确定方法、装置、通信设备和存储介质
WO2023184121A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2023201660A1 (zh) Rsrp门限参数确定方法、装置、通信设备及存储介质
WO2023130472A1 (zh) 提早识别的方法、装置、通信设备及存储介质
WO2023050350A1 (zh) Cfr的确定方法、装置、通信设备及存储介质
WO2022205046A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2022222145A1 (zh) 终端能力信息的上报方法、装置、通信设备及存储介质
WO2022021271A1 (zh) 波束切换方法及装置、网络设备、终端及存储介质
WO2021163934A1 (zh) 通信处理方法、装置及计算机存储介质
WO2021077266A1 (zh) 网络接入方法、装置、通信设备及存储介质
US20220408469A1 (en) Downlink control information configuration method and apparatus, and communication device and storage medium
WO2022213330A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2024026758A1 (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: 22933978

Country of ref document: EP

Kind code of ref document: A1