WO2023010362A1 - 收发信号的方法、装置和通信系统 - Google Patents

收发信号的方法、装置和通信系统 Download PDF

Info

Publication number
WO2023010362A1
WO2023010362A1 PCT/CN2021/110680 CN2021110680W WO2023010362A1 WO 2023010362 A1 WO2023010362 A1 WO 2023010362A1 CN 2021110680 W CN2021110680 W CN 2021110680W WO 2023010362 A1 WO2023010362 A1 WO 2023010362A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
downlink bwp
initial
initial downlink
bwp
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2021/110680
Other languages
English (en)
French (fr)
Inventor
李国荣
贾美艺
张磊
王昕�
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
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 Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to JP2024506564A priority Critical patent/JP7850796B2/ja
Priority to CN202180101190.4A priority patent/CN117813883A/zh
Priority to PCT/CN2021/110680 priority patent/WO2023010362A1/zh
Publication of WO2023010362A1 publication Critical patent/WO2023010362A1/zh
Priority to US18/430,057 priority patent/US20240224338A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0457—Variable allocation of band or rate
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA

Definitions

  • the embodiment of the present application relates to the technical field of communications.
  • a terminal device for example, UE performs the following operations during initial network access:
  • Operation 1) obtain the master information block (MIB) by searching the PBCH/synchronization signal block (CD-SSB, Cell Defining SSB (Synchronization Signal Block)) at the cell level, and obtain the system information block type 1 (SIB1) for scheduling the cell Physical downlink control channel (PDCCH) configuration, the configuration includes control resource set 0 (control resource set 0, CORESET#0) configuration and search space 0 (Search space 0, SS#0) configuration.
  • MIB master information block
  • CD-SSB PBCH/synchronization signal block
  • SIB1 System information block type 1
  • the configuration includes control resource set 0 (control resource set 0, CORESET#0) configuration and search space 0 (Search space 0, SS#0) configuration.
  • SIB1 includes information such as initial DL BWP configuration, initial UL BWP configuration, random access configuration, and other public configurations of the cell.
  • UE adopts the relevant configuration of random access in the initial UL BWP configuration, and initiates the random access process.
  • UE receives RAR and Msg4 on CORESET#0.
  • RedCap UE reduced capability terminal equipment
  • the main application scenarios of RedCap UE include: industrial wireless sensors, surveillance cameras and wearable devices.
  • RedCap UE is characterized by lower device cost and complexity than Release 15/Release 16 (R15/R16) high-end Enhanced Mobile Broadband (eMBB) and Low Latency Highly Reliable Communication (URLLC) devices, and has a smaller size, The business rate requirement is not high, and some devices need to have a long battery life.
  • R15/R16 Release 15/Release 16
  • eMBB Enhanced Mobile Broadband
  • URLLC Low Latency Highly Reliable Communication
  • the inventors of the present application found that if the initial DL BWP configured separately for RedCap UE can be used during the initial access process or before the initial access process, then the initial downlink BWP or CORESET, etc. need to have a consistent understanding: for example, when the RedCap UE starts working in the initial DL BWP configured separately for the RedCap UE or when it starts to monitor the control resource set (Control Resource) in the initial DL BWP configured separately for the RedCap UE Set, CORESET) and/or Common Search Space (Common Search Space, CSS); another example, RedCap UE is in the idle (idle) state, inactive (inactive) state, or random in the radio resource control (RRC) connection re-establishment Before the access process, which bandwidth to work on, etc.
  • RRC radio resource control
  • the initial DL BWP configured separately for the RedCap UE can be used during the initial access process or before the initial access process, the initial downlink BWP or CORESET of the network device and the RedCap UE working on the RedCap UE, etc.
  • the initial downlink BWP or CORESET of the network device and the RedCap UE working on the RedCap UE etc.
  • a terminal device with reduced capabilities uses the first configured separately for the RedCap UE.
  • An initial downlink BWP receives the signal, so that the network device and the RedCap UE can have a consistent understanding of the initial downlink BWP or CORESET of the RedCap UE's work.
  • an apparatus for transmitting and receiving signals which is applied to a terminal equipment with reduced capabilities (Redcap UE), the apparatus includes a first transceiver unit, and the first transceiver unit is configured such that:
  • the terminal device with reduced capability obtains the configuration of a first initial downlink BWP, and the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals before the random access is completed.
  • an apparatus for sending and receiving signals which is applied to network equipment, and the apparatus includes a second transceiver unit configured to make the network equipment:
  • an apparatus for transmitting and receiving signals which is applied to a terminal equipment with reduced capabilities (Redcap UE), the apparatus includes a third transceiver unit, and the third transceiver unit is configured such that:
  • the terminal device with reduced capability obtains the configuration of a first initial downlink BWP, and the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • the terminal device with reduced capabilities operates in a bandwidth when it is in an idle state, in an inactive state, or before a random access procedure for radio resource control (RRC) connection re-establishment, the one bandwidth being One of at least one candidate bandwidth.
  • RRC radio resource control
  • an apparatus for sending and receiving signals which is applied to network equipment, and the apparatus includes a fourth transceiver unit configured to make the network equipment:
  • the one bandwidth is one of at least one candidate bandwidth.
  • an apparatus for sending and receiving signals which is applied to network equipment, and the apparatus includes a fifth transceiver unit configured to make the network equipment:
  • an apparatus for transmitting and receiving signals which is applied to a terminal device with reduced capabilities, the apparatus includes a sixth transceiver unit, and the sixth transceiver unit is configured such that:
  • the terminal device with reduced capability obtains the configuration of a first initial downlink BWP, and the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • the terminal equipment with reduced capability uses the first initial downlink BWP configured separately for the RedCap UE to receive signals, thus, the network equipment and the RedCap UE
  • the UE can have a consistent understanding of the initial downlink BWP or CORESET of the RedCap UE's work.
  • FIG. 1 is a schematic diagram of a method for sending and receiving signals in an embodiment of the first aspect of the present application
  • Figure 2 is a schematic diagram of non-RedCap UE using initial DL BWP and RedCap UE using the first initial DL BWP;
  • FIG. 3 is a schematic diagram of a method for sending and receiving signals in an embodiment of the first aspect of the present application
  • Fig. 4 is a schematic diagram of a method for sending and receiving signals according to an embodiment of the third aspect
  • Fig. 5 is a schematic diagram of a method for sending and receiving signals in an embodiment of the fourth aspect of the present application.
  • Figure 6 is a schematic diagram of non-RedCap UE using initial DL BWP and RedCap UE using the first initial DL BWP;
  • Fig. 7 is a schematic diagram of a method for sending and receiving signals according to an embodiment of the fifth aspect
  • Fig. 8 is a schematic diagram of a method for sending and receiving signals according to an embodiment of the sixth aspect
  • Fig. 9 is a schematic diagram of a device for sending and receiving signals in an embodiment of the seventh aspect.
  • Fig. 10 is another schematic diagram of the device for sending and receiving signals in the embodiment of the seventh aspect
  • Fig. 11 is another schematic diagram of the device for sending and receiving signals in the embodiment of the seventh aspect
  • Fig. 12 is a schematic diagram of the device for sending and receiving signals in the embodiment of the eighth aspect
  • Fig. 13 is another schematic diagram of the device for sending and receiving signals in the embodiment of the eighth aspect
  • Fig. 14 is another schematic diagram of the device for sending and receiving signals in the embodiment of the eighth aspect.
  • Fig. 15 is a schematic diagram of a terminal device in an embodiment of the ninth aspect.
  • Fig. 16 is a schematic diagram of a network device of an embodiment of the ninth aspect.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or time order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having” and the like refer to the presence of stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term “communication network” or “wireless communication network” may refer to a network conforming to any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), Enhanced Long-term evolution (LTE-A, LTE-Advanced), wideband code division multiple access (WCDMA, Wideband Code Division Multiple Access), high-speed packet access (HSPA, High-Speed Packet Access), etc.
  • NR New Radio
  • New Radio Long Term Evolution
  • LTE-A Long-term evolution
  • LTE-A Long-term evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocols, such as but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G , New Radio (NR, New Radio), etc., and/or other communication protocols that are currently known or will be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network equipment may include but not limited to the following equipment: integrated access and backhaul node (IAB-node), base station (BS, Base Station), access point (AP, Access Point), sending and receiving point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), etc.
  • IAB-node integrated access and backhaul node
  • BS Base Station
  • AP access point
  • TRP Transmission Reception Point
  • MME mobile management entity
  • MME Mobile Management Entity
  • gateway server
  • RNC Radio Network Controller
  • BSC Base Station Controller
  • the base station may include but not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include Remote Radio Head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low-power nodes (such as femeto, pico, etc.).
  • Node B Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power nodes such as femeto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
  • the term "cell” can refer to a base station and/or its coverage area depending on the context in which the term is used.
  • the term "User Equipment” (UE, User Equipment) or “terminal equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
  • a terminal device may be fixed or mobile, and may also be called a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, etc.
  • the terminal equipment may include but not limited to the following equipment: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld equipment, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication equipment
  • handheld equipment machine-type communication equipment
  • laptop computer Cordless phones
  • Cordless phones smartphones, smart watches, digital cameras, and more.
  • the terminal device can also be a machine or device for monitoring or measurement, such as but not limited to: a machine type communication (MTC, Machine Type Communication) terminal, Vehicle communication terminal, device to device (D2D, Device to Device) terminal, machine to machine (M2M, Machine to Machine) terminal, etc.
  • MTC Machine Type Communication
  • Vehicle communication terminal device to device (D2D, Device to Device) terminal
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station, or may include one or more network devices as above.
  • user side or “terminal side” or “terminal device side” refers to a side of a user or a terminal, which may be a certain UE, or may include one or more terminal devices as above.
  • uplink control signal and “uplink control information (UCI, Uplink Control Information)” or “physical uplink control channel (PUCCH, Physical Uplink Control Channel)” can be used interchangeably without causing confusion.
  • uplink data signal and “uplink data information” or “physical uplink shared channel (PUSCH, Physical Uplink Shared Channel)” can be interchanged;
  • downlink control signal and “downlink control information (DCI, Downlink Control Information)” or “physical downlink control channel (PDCCH, Physical Downlink Control Channel)” are interchangeable, and the terms “downlink data signal” and “downlink data information” Or “Physical Downlink Shared Channel (PDSCH, Physical Downlink Shared Channel)” can be interchanged.
  • DCI Downlink Control Information
  • PDCCH Physical Downlink Control Channel
  • sending or receiving PUSCH can be understood as sending or receiving uplink data carried by PUSCH
  • sending or receiving PUCCH can be understood as sending or receiving uplink information carried by PUCCH
  • sending or receiving PRACH can be understood as sending or receiving information carried by PRACH.
  • the uplink signal may include uplink data signal and/or uplink control signal, etc., and may also be called uplink transmission (UL transmission) or uplink information or uplink channel.
  • Sending the uplink transmission on the uplink resource may be understood as sending the uplink transmission using the uplink resource.
  • downlink data/signals/channels/information can be understood accordingly.
  • the high-level signaling may be, for example, radio resource control (RRC) signaling; for example, it is called an RRC message (RRC message), for example, it includes MIB, system information (system information), and a dedicated RRC message; or it is called RRC IE (RRC information element).
  • RRC radio resource control
  • the high-level signaling may also be, for example, MAC (Medium Access Control) signaling; or called MAC CE (MAC control element). But the present application is not limited thereto.
  • RedCap UE After initial access (for example, after RRC setup, RRC Resume, or RRC Reestablishment), RedCap UE is not expected to use an initial downlink BWP (initial DL BWP) wider than the maximum RedCap UE bandwidth.
  • the initial DL BWP for RedCap UEs (not exceeding the maximum RedCap UE bandwidth) can be optionally configured/defined separately from the initial DL BWP for non-RedCap UEs.
  • the initial DL BWP of an individual RedCap UE can be used at least after initial access (for example, after RRC setup, RRC Resume, or RRC Reestablishment) .
  • the embodiment of the first aspect provides a method for sending and receiving signals, which is applied to a terminal device with reduced capabilities (Redcap UE).
  • Fig. 1 is a schematic diagram of a method for sending and receiving signals in an embodiment of the first aspect of the present application. As shown in Fig. 1, the method includes:
  • the terminal device with reduced capability obtains the configuration of a first initial downlink BWP (initial DL BWP), and the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • Operation 102 The terminal device with reduced capability uses the first initial downlink BWP to receive a signal before random access is completed.
  • the network side and the RedCap UE side have a consistent understanding of the downlink working BWP to avoid loss or error in downlink transmission.
  • the RedCap UE can obtain the configuration of the first initial downlink BWP from the network device.
  • the SIB1 or other system information sent by a network device may include the configuration of initial DL BWP configured for non-reduced capability terminal equipment (non-RedCap UE) and the initial DL configured or defined separately for RedCap UE
  • RedCap UE can ignore the configuration of initial DL BWP configured for non-RedCap UE, and use the initial DL BWP configured separately for RedCap UE as its own initial DL BWP or the configuration of initial DL BWP configured for RedCap UE alone
  • the initial DL BWP has a BWP-id of 0; or, RedCap UE can also configure the initial DL BWP for non-RedCap UE and the initial DL BWP configured separately for RedCap UE as Its own initial DL BWP, these two initial DL BWPs can be distinguished by different BWP-ids, for example, the
  • the initial DL BWP configuration sent by the network device for the RedCap UE's separate configuration or definition may include configuration of at least one CORESET (hereinafter referred to as the first CORESET) and/or at least one CSS (hereinafter referred to as the first CORESET) - CSS) configuration for the RedCap UE to receive system information (may be system information including SIB1 or system information not including SIB1) and/or paging and/or random access response (or random access message 2).
  • system information may be system information including SIB1 or system information not including SIB1
  • random access response or random access message 2.
  • the initial DL BWP configured/defined separately for the RedCap UE may not include the complete CORESET#0, that is, the initial DL BWP configured/defined separately for the RedCap UE may partially overlap with or not include the CORESET#0 of the cell overlapping.
  • the first CORESET may or may not partially overlap with CORESET #0 of the cell.
  • the first CSS may or may not partially overlap with SS#0 of the cell.
  • Figure 2 is a schematic diagram of non-RedCap UE using initial DL BWP and RedCap UE using the first initial DL BWP.
  • Figure 2 shows the situation that the initial DL BWP configured/defined separately for RedCap UE (that is, the first initial DL BWP) does not overlap with CORESET#0 and the first CORESET does not overlap with the CORESET#0 of the cell, but the present application Not limited thereto, the first initial DL BWP and CORESET#0 may also at least partially overlap.
  • the Separated initial DL BWP for RedCap in Figure 2 is the first initial DL BWP, and the CORESET in the dashed box is the first CORESET.
  • RedCap UEs can use system information (such as SIB1 or other The SIB) configured is the initial DL BWP (ie, the first initial DL BWP) configured/defined separately for the RedCap UE.
  • SIB1 system information
  • the SIB configured is the initial DL BWP (ie, the first initial DL BWP) configured/defined separately for the RedCap UE.
  • receiving a signal using the initial DL BWP configured/defined separately for the RedCap UE may include: receiving a signal in the initial DL BWP configured/defined separately for the RedCap UE, the received signal is, for example, a physical downlink shared channel (PDSCH) and/or channel state information reference signal (CSI-RS) and/or physical downlink control channel (PDCCH); or, the bandwidth of the initial DL BWP configured/defined separately for RedCap UE as the receiving bandwidth; Or, listen to PDCCH in CORESET and/or CSS in the initial DL BWP configured separately for RedCap UE; or, RedCap UE will keep or switch or adjust the bandwidth to the initial DL BWP configured/defined separately for RedCap UE, etc. .
  • the meaning of "receiving a signal using the first initial DL BWP" in this application is not limited thereto.
  • the reduced capability terminal equipment uses the first initial downlink BWP before the initial access procedure or before the random access procedure.
  • the terminal device with reduced capability may reside in the first initial downlink BWP before the initial access procedure or before the random access procedure.
  • the RedCap UE is in an idle (idle) state, an inactive (inactive) state, or resides in the first initial downlink BWP before the random access procedure of radio resource control (RRC) connection reestablishment.
  • RRC radio resource control
  • the terminal equipment with reduced capability may reside in the first initial downlink BWP after selecting a suitable cell or before initializing the random access procedure.
  • the terminal device with reduced capabilities may use the first initial downlink BWP to receive signals when receiving the configuration of the first initial downlink BWP or after receiving the configuration of the first initial downlink BWP.
  • “when the configuration of the first initial downlink BWP is received or after the configuration of the first initial downlink BWP is received" is an example of "before the random access procedure".
  • the RedCap UE receives the configuration of the first initial downlink BWP in SIB1 or other system information, and uses the first initial downlink BWP when or after receiving the configuration. Modifications as shown in Table 1 can be made to TS38.331, where the underlined part is newly added content.
  • the RedCap UE receives the configuration of the first initial downlink BWP in the RRC Release or RRC Release with suspend indication message, and uses the first initial downlink BWP when or after receiving the configuration.
  • the reduced-capability terminal equipment uses the first initial downlink BWP to receive signals during the initial access process or the random access process.
  • Embodiment 2 may include the following specific implementation modes 1-5.
  • the terminal device with reduced capabilities uses the first initial downlink BWP to receive signals, wherein, "received the first initial downlink BWP configuration or after receiving the configuration of the first initial downlink BWP" is an example of "in the initial access process".
  • the RedCap UE receives the configuration of the first initial downlink BWP in SIB1 or other system information, and uses the first initial downlink BWP when or after receiving the configuration.
  • the terminal equipment with reduced capabilities uses the first initial downlink BWP to receive signals during or after the initialization of the random access procedure.
  • the initial uplink BWP (initial UL BWP) configured separately for the RedCap UE is used, that is, when the terminal equipment with reduced capabilities uses the first initial uplink BWP, use the first initial uplink BWP.
  • An initial downlink BWP receives a signal, and the first initial uplink BWP is an initial uplink BWP configured or defined separately for the terminal device with reduced capability.
  • the first initial downlink BWP of the terminal device with reduced capabilities has a predetermined identifier (BWP-id), where the predetermined identifier is, for example, BWP-id being 0.
  • RedCap UE thinks that the initial DL BWP configured separately for RedCap UE has a BWP-id of 0, there is no need to modify the BWP operation in section 5.15 of the MAC specification, but it needs to be explained that RedCap UE uses the initial DL BWP configured separately for RedCap UE , that is, the RedCap UE can ignore the configuration of the initial DL BWP configured for the non-RedCap UE, and will use the initial DL BWP configured separately for the RedCap UE as its own initial DL BWP, and the BWP-id is 0.
  • the first initial downlink BWP of the terminal device with reduced capability corresponds to the first initial uplink BWP.
  • RedCap UE thinks that the BWP-id of the initial DL BWP configured separately for RedCap UE is not 0, then modify the BWP operation in Section 5.15 of the MAC specification, for example, modify it to the following Table 2; That is, the DL BWP corresponding to the initial UL BWP is the initial DL BWP configured separately for the RedCap UE, that is, the first initial downlink BWP corresponds to the first initial uplink BWP.
  • the RedCap UE may set the random access preamble power parameter, or after selecting the carrier for random access, or after setting the type of the random access procedure (for example, the type is two After one-step random access or four-step random access), or after initializing random access type-specific variables, the downlink BWP is converted to the first initial downlink BWP, or the receiving bandwidth is adjusted to the first initial downlink BWP.
  • the RedCap UE may switch the downlink BWP to the first initial downlink BWP or adjust the receiving bandwidth to the first initial downlink BWP before performing the random access resource selection process.
  • the network device may send an additional SSB (additional SSB) in the first initial downlink BWP, and the RedCap UE may receive the additional SSB in the first initial downlink BWP.
  • additional SSB may be shown as additional SSB in FIG. 2 .
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals during or after the random access resource selection process.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals; more specifically, during the random access resource selection process, the terminal device with reduced capability starts from the SSB defined by the cell or from the SSB defined for After the SSB is selected from the SSBs in the initial downlink BWP of the non-RedCap configuration, use the first initial downlink BWP to receive signals.
  • a terminal device with reduced capabilities selects a random access preamble group (Group A or Group B), or after selecting a random access preamble, or after determining the next available random access opportunity (PRACH occasion), Use the first initial downlink BWP to receive signals.
  • a random access preamble group Group A or Group B
  • PRACH occasion Use the first initial downlink BWP to receive signals.
  • the terminal device with reduced capability Before receiving a random access response (Random Access Response) or when receiving a random access response, the terminal device with reduced capability uses the first initial downlink BWP to receive signals.
  • Random Access Response Random Access Response
  • the random access response before receiving the random access response, it includes: after sending the random access message 1 (Msg1, preamble) or the random access message A (preamble+PUSCH), for example, after sending the first random access message 1 ( Msg1, preamble) or random access message A (preamble+PUSCH).
  • When receiving the random access response it includes when starting the random access response window (ra-ResponseWindow), for example, when starting the random access response window for the first time.
  • ra-ResponseWindow when starting the random access response window for the first time.
  • random access message 1 indicates the type of terminal equipment with reduced capability, that is, indicates that the terminal equipment is a RedCap UE , and/or indicate the number of receiving antennas of the terminal device with reduced capabilities, such as 1Rx or 2Rx, so that the network device can determine the initial DL BWP corresponding to the RedCap UE, so as to send Msg2 and/or Msg4 in the correct BWP.
  • the RedCap UE uses the first initial downlink BWP to receive the signal.
  • Msg4 may be sent in the initial DL BWP configured separately for the Redcap UE, and Msg2 may not be sent in the initial DL BWP configured separately for the Redcap UE.
  • random access message 1 Msg1, preamble
  • random access message A preamble+PUSCH
  • random access message 3 indicates the type of the terminal device with reduced capability, that is, indicates that the terminal device is RedCap UE, and/or indicate the number of receiving antennas of the terminal equipment with reduced capabilities, such as 1Rx or 2Rx, so that the network device can determine the initial DL BWP corresponding to the RedCap UE, so as to send Msg4 in the correct BWP.
  • the network device may not send additional SSBs in the first initial DL BWP, and the RedCap UE may not receive additional SSBs in the first initial DL BWP.
  • the terminal device with reduced capability can use the related configuration of random access in the initial uplink BWP configuration configured for non-RedCap, or use the configuration in the initial uplink BWP configured or defined separately for RedCap UE
  • the related configuration of random access if the initial uplink BWP is configured or defined for the RedCap UE, the related configuration of random access may include at least one parameter in the RACH-ConfigCommon IE.
  • the RedCap UE uses the first initial DL BWP to receive the signal before the random access is completed, so that the network side and the UE side have a consistent understanding of the downlink working BWP, avoiding downlink transmission loss or mistake.
  • the embodiment of the second aspect of the present application provides a method for sending and receiving signals, which is applied to a network device.
  • the method for sending and receiving signals in the embodiment of the second aspect corresponds to the method for sending and receiving signals in the embodiment of the first aspect.
  • the methods for sending and receiving signals include:
  • Operation 301 Send the configuration of a first initial downlink BWP to the terminal device with reduced capability, where the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability; and
  • Operation 302. Before the random access of the terminal device with reduced capability is completed, send a signal to the terminal device with reduced capability using the first initial downlink BWP.
  • the configuration of the first initial downlink BWP sent to the terminal device with reduced capabilities includes: configuration of at least one control resource set (CORESET) (hereinafter referred to as the first CORESET) and/or at least one common search Configuration of space (CSS) (hereinafter referred to as first CSS).
  • CORESET control resource set
  • CSS common search Configuration of space
  • the control resource set (CORESET) and/or the common search space (CSS) are used for the terminal device with reduced capability to receive system information (which may be system information including SIB1 or system information not including SIB1) and/or search call and/or random access response (or random access message 2).
  • the configuration of the first initial downlink BWP is sent to the terminal device with reduced capabilities through system information or RRC dedicated signaling.
  • the first initial downlink BWP is used to send a signal.
  • the first initial downlink BWP is used to send a signal.
  • Embodiment 2 may include the following specific implementation modes 1-5.
  • the first initial downlink BWP is used to send a signal.
  • the first initial downlink BWP is used to send a signal.
  • the first initial downlink BWP is used to send a signal, where the first initial uplink BWP is an initial uplink BWP configured or defined separately for the terminal device with reduced capability.
  • the first initial downlink BWP of the terminal device with reduced capabilities has a predetermined identifier (BWP-id), for example, the predetermined identifier is that BWP-id is equal to 0.
  • the first initial downlink BWP of the terminal device with reduced capability corresponds to the first initial uplink BWP, where the first initial uplink BWP is configured separately for the terminal device with reduced capability or Defined initial uplink BWP.
  • the network device may also use the first initial downlink BWP to send an additional SSB to the terminal device with reduced capability.
  • the network device sends a signal using the first initial downlink BWP.
  • the network device uses the first initial downlink BWP to send a signal. More specifically, in the random access resource selection process, after a terminal device with reduced capabilities selects an SSB from the cell-defined SSBs or from the SSBs in the initial downlink BWP configured for non-RedCap, the network device uses the first The initial downlink BWP sends a signal.
  • a terminal device with reduced capabilities selects a random access preamble group (Group A or Group B), or after selecting a random access preamble, or after determining the next available random access opportunity (PRACH occasion),
  • the network device sends a signal using the first initial downlink BWP.
  • the network device Before or when sending the random access response to the terminal device with reduced capability, the network device sends a signal using the first initial downlink BWP.
  • ra-ResponseWindow When sending a random access response, it includes when the terminal device with reduced capabilities starts a random access response window (ra-ResponseWindow), for example, when starting a random access response window for the first time.
  • the random access message 1 indicates the type of terminal equipment with reduced capabilities, that is, indicates that the terminal equipment RedCap UE , and/or indicate the number of receiving antennas of the terminal device with reduced capabilities, such as 1Rx or 2Rx, so that the network device can determine the initial DL BWP corresponding to the RedCap UE, so as to send Msg2 and/or Msg4 in the correct BWP.
  • the network device When receiving the random access message 3 (Msg3) or after receiving the random access message 3 (Msg3), the network device sends a signal using the first initial downlink BWP.
  • random access message 1 (Msg1, preamble), random access message A (preamble+PUSCH) or random access message 3 indicates the type of terminal equipment with reduced capability, and/or indicates the type of terminal device with reduced capability
  • the number of receiving antennas of the terminal device such as 1Rx or 2Rx, so that the network device can determine the initial DL BWP corresponding to the RedCap UE, so as to send Msg4 in the correct BWP.
  • the network device may not send additional SSBs in the first initial DL BWP, and the RedCap UE may not receive additional SSBs in the first initial DL BWP.
  • the RedCap UE uses the first initial DL BWP to send a signal before the random access is completed, so that the network side and the UE side have a consistent understanding of the downlink working BWP, avoiding downlink transmission loss or mistake.
  • the embodiment of the third aspect provides a method for sending and receiving signals, which is applied to a terminal device with reduced capabilities (Redcap UE).
  • Fig. 4 is a schematic diagram of a method for sending and receiving signals according to an embodiment of the third aspect. As shown in Fig. 4, the method for sending and receiving signals includes:
  • the terminal device with reduced capability obtains the configuration of a first initial downlink BWP, where the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • the terminal device with reduced capability works in a bandwidth when it is in an idle (idle) state, an inactive (inactive) state, or before a random access procedure of radio resource control (RRC) connection re-establishment, and the bandwidth is One of at least one candidate bandwidth.
  • RRC radio resource control
  • an idle state refers to an RRC_IDLE state
  • an inactive state refers to an RRC_INACTIVE state
  • RRC radio resource control
  • the RedCap UE works in a bandwidth, and "working in a bandwidth” here can also be understood as including “camp on (camp on) a bandwidth”, “keep a bandwidth”, “use a Bandwidth”, “receiving PDCCH and/or PDSCH and/or reference signal in a bandwidth”, “switching to a bandwidth” or “retuning (retuning) radio frequency to a bandwidth” and other meanings.
  • At least one candidate bandwidth in the above operation 402 includes:
  • Control resource set 0 (CORESET#0); the initial downlink BWP corresponding to the non-reduced capability terminal equipment (non-RedCap UE); and, the first initial downlink BWP or the first initial downlink BWP is used to receive system information and/or Control resource set (CORESET) for paging and/or random access response.
  • the RedCap UE can reside in CORESET#0, that is, the RedCap UE can reside in CORESET#0 together with the non-RedCap UE;
  • the RedCap UE may reside in the initial DL BWP corresponding to the non-RedCap UE, wherein "the initial DL BWP corresponding to the non-RedCap UE” may refer to "the initial DL BWP configured for the non-RedCap UE” , and, "initial DL BWP configured for non-RedCap UE” is the initial downlink BWP (initial DL BWP) configured by the cell in SIB1, RedCap UE can work in this initial DL BWP, for example, when the bandwidth of the BWP is not greater than that of RedCap When the maximum bandwidth supported by the UE;
  • the RedCap UE can reside in the initial DL BWP (that is, the first initial DL BWP) configured/defined separately for the RedCap UE, and can also work in the initial DL BWP for receiving system information and /or in the CORESET of paging.
  • the method for sending and receiving signals in FIG. 4 may further include:
  • the terminal device with reduced capability obtains a master information block (MIB);
  • MIB master information block
  • Operation 404 obtain system information block type 1 (SIB1);
  • Operation 405 Switch to the first initial downlink BWP when it is judged that the cell can be selected.
  • Embodiment 3 when the terminal equipment enters RRC_IDLE or enters RRC_INACTIVE state or needs to perform RRC reconstruction (except for special cases such as inter-RAT cell reselection), it needs to perform cell selection, and the MIB and SIB1.
  • New Radio for a cell (cell), only one CD-SSB is configured for terminal equipment, so RedCap UE needs to read CD-SSB to obtain MIB, and monitor PDCCH from CORESET#0 to obtain SIB1 to select a cell .
  • RedCap UE can first read CD-SSB to obtain MIB, and monitor PDCCH in CORESET#0 and/or SS#0 to obtain SIB1, judge A cell can be selected, i.e. the cell is a suitable cell, and then switched to/working on the initial DL BWP configured/defined for the RedCap UE.
  • the terminal device with reduced capability may determine the one bandwidth to work in the above at least one candidate bandwidth, for example, the one bandwidth may be determined according to preset conditions, thus, the network device side may also The one bandwidth can be determined according to the preset condition, so as to have the same understanding as the RedCap UE on the one working bandwidth.
  • the RedCap UE may also determine the one bandwidth according to the indication information of the network device.
  • the indication information may be sent through the following information or messages: system information (such as SIB1 or other SIBs), radio resource control release/radio resource control release with suspend indication (RRC release/RRC release with suspend indication) message, wireless A resource control rejection (RRC reject) message or a radio resource control reconfiguration (RRC reconfiguration) message, etc.
  • the network side and the terminal side can clarify the idle or inactive state or the bandwidth or BWP of the RedCap UE that needs to perform RRC reconstruction, so that the network side can have the same bandwidth or BWP as the RedCap UE.
  • the embodiment of the third aspect can be combined with the embodiment of the first aspect, so that when the RedCap UE is configured with the first initial DL BWP, the network side and the terminal side can determine when the RedCap UE uses the first initial DL BWP.
  • the initial DL BWP, and which bandwidth the RedCap UE resides in have a consistent understanding, so as to avoid downlink transmission loss or error.
  • the embodiment of the fourth aspect of the present application provides a method for sending and receiving signals, which is applied to a network device.
  • the method for sending and receiving signals in the embodiment of the fourth aspect corresponds to the method for sending and receiving signals in the embodiment of the third aspect.
  • the methods for sending and receiving signals include:
  • Operation 501 Send the configuration of a first initial downlink BWP to the terminal device with reduced capability, where the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability; and
  • Operation 502 Instruct the terminal device with reduced capability to work in a bandwidth when it is in an idle (idle) state, an inactive (inactive) state, or before a random access procedure of radio resource control (RRC) connection re-establishment, the one
  • the bandwidth is one of at least one candidate bandwidth.
  • the idle (idle) state refers to the RRC_IDLE state
  • the inactive (inactive) state refers to the RRC_INACTIVE state
  • RRC radio resource control
  • RedCap UE works in a bandwidth
  • “working in a bandwidth” here can also be understood as including “camp on (camp on) a bandwidth”, “maintain a bandwidth”, “use a Bandwidth”, “receiving PDCCH and/or PDSCH and/or reference signal in a bandwidth”, “switching to a bandwidth” or “retuning (retuning) radio frequency to a bandwidth” and other meanings.
  • the at least one candidate bandwidth includes:
  • Control resource set 0 (CORESET#0);
  • the initial downlink BWP for non-reduced capability UEs The initial downlink BWP for non-reduced capability UEs.
  • CORESET control resource set
  • the indication information is sent through the following information or message:
  • System information e.g. SIB1 or other SIBs
  • RRC release/RRC release with suspend indication message e.g. RRC reject message or RRC reconfiguration (RRC reconfiguration) message.
  • the network device can determine the one bandwidth according to the preset condition, and the RedCap UE can also determine the one bandwidth according to the preset condition, thus, the network device and the RedCap UE can pair The one bandwidth that resides has the same understanding. In this case, operation 502 may be omitted.
  • the network side and the terminal side can clarify the idle/inactive state or the bandwidth or BWP of the RedCap UE that needs to perform RRC reconstruction, so that the network side can have the same bandwidth or BWP as the RedCap UE.
  • the embodiment of the fourth aspect can be combined with the embodiment of the second aspect, thus, when the RedCap UE is configured with the first initial DL BWP, the network side and the terminal side can determine when the RedCap UE uses the first initial DL BWP.
  • the initial DL BWP, and which bandwidth the RedCap UE resides in have a consistent understanding, so as to avoid downlink transmission loss or error.
  • the embodiment of the fifth aspect of the present application provides a method for sending and receiving signals, which is applied to a network device.
  • the network device is represented as gNB.
  • the initial DL BWP (i.e., the first initial DL BWP) configured or defined separately for the RedCap UE may not include the complete CORESET#0, i.e., for the RedCap UE
  • the initial DL BWP configured/defined by the UE alone may partially overlap or not overlap with the CORESET#0 of the cell.
  • the network device eg, gNB
  • the network device needs to determine in which bandwidth or BWP or CORESET to send the paging message.
  • Figure 6 is a schematic diagram of the non-RedCap UE using the initial DL BWP and the RedCap UE using the first initial DL BWP.
  • the initial DL BWP ie, the first initial DL BWP
  • the initial DL BWP configured/defined separately for RedCap UE does not overlap with CORESET#0.
  • the gNB For the paging initiated by the radio access network (RAN), because the gNB has the context of the UE, it knows whether the paging message is for the RedCap UE, so the gNB can be in the BW where the RedCap UE in the RRC_INACTIVE state resides (refer to the second Embodiments of aspects) send the paging message.
  • RAN radio access network
  • the current gNB cannot obtain information about whether the paging message is for the RedCap UE from the paging message sent by the core network. Therefore, there is a problem that the gNB cannot determine which bandwidth or BWP or CORESET to send The problem with the paging message.
  • the embodiment of the fifth aspect of the present application provides a method for sending and receiving signals.
  • Fig. 7 is a schematic diagram of a method for sending and receiving signals according to an embodiment of the fifth aspect. As shown in Fig. 7, the method includes:
  • Operation 701. Send a configuration of a first initial downlink BWP to the terminal device with reduced capability, where the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • Operation 702 receiving a paging (paging) message from the core network
  • Operation 703. Determine at least the bandwidth used for sending the paging message to the terminal device with reduced capability.
  • the network device may send a paging message to the terminal device with reduced capabilities according to the bandwidth determined in operation 703.
  • the terminal equipment with reduced capability may be in RRC_IDLE state or RRC_INACTIVE state.
  • operation 703 may be implemented by any one of Embodiments 1 to 3 described below.
  • the bandwidth determined in operation 703 includes:
  • Non-RedCap UE control resource set 0 (CORESET#0) or the additional control resource set (additional CORESET) in the initial downlink BWP of a non-reduced capability terminal device.
  • the network device can send a paging message in the initial DL BWP of the non-RedCap UE or in CORESET#0 or in the additional CORESET in the initial DL BWP of the non-RedCap UE.
  • the RedCap UE may need to retuning (retuning) the radio frequency (RF) to CORESET#0 according to its corresponding paging occasions (PO), so as to receive the paging message.
  • a RedCap UE in the RRC_IDLE or RRC_INACTIVE state resides in the initial DL BWP configured or defined separately for the RedCap UE, and the initial DL BWP does not contain a complete CORESET#0 or does not contain a complete initial DL corresponding to a non-RedCap UE In the case of CORESET used for paging messages in BWP.
  • the bandwidth determined in operation 703 includes:
  • the initial downlink BWP of the non-reduced capability terminal device, the control resource set 0 (CORESET#0) or the additional control resource set (additional CORESET) in the initial downlink BWP of the non-reduced capability terminal device, and the terminal with the reduced capability The initial downlink BWP configured or defined separately by the device or the control resource set (CORESET) configured or defined separately for the terminal device with reduced capability.
  • the network device can be in the initial DL BWP of non-RedCap UE or in CORESET#0 or in the additional CORESET in the initial DL BWP of non-RedCap UE, and in the initial DL BWP configured/defined separately for redcap UE or In the CORESET configured/defined separately for redcap UE, paging messages are sent.
  • both the initial downlink BWP of the non-capability-reduced terminal device and the initial downlink BWP of the reduced-capability terminal device include control resource set 0 (CORESET#0) or an additional control resource set for paging ( CORESET), the network device may send to the terminal device with reduced capability and the terminal device with non-reduced capability in control resource set 0 (CORESET#0) or additional control resource set for paging (CORESET) paging message.
  • CORESET#0 control resource set 0
  • CORESET additional control resource set for paging
  • At least one of the initial downlink BWP of the non-reduced capability terminal device and the initial downlink BWP of the reduced capability terminal device does not contain control resource set 0 (CORESET#0) or non-RedCap UE
  • the network device uses the initial downlink BWP of the terminal device with non-reduced capabilities, control resource set 0 (CORESET#0) or non-reduced capabilities
  • the additional control resource set (additional CORESET) in the initial downlink BWP of the terminal device, and the initial downlink BWP configured or defined separately for the terminal device with reduced capability or the control resource set (CORESET) configured or defined separately for the terminal device with reduced capability ) send a paging message.
  • both initial DL BWPs contain CORESET#0 or an additional CORESET for paging
  • paging messages for redcap UE and non-RedCap UE can be sent in CORESET#0 or in an additional CORESET for paging be sent; otherwise, the paging message needs to be sent in both initial DL BWPs or CORESETs (CORESET#0 or an additional CORESET for paging) in both initial DL BWPs.
  • the bandwidth determined in operation 703 includes:
  • An initial downlink BWP configured or defined separately for the terminal device with reduced capability or a control resource set (CORESET) configured or defined separately for the terminal device with reduced capability.
  • CORESET control resource set
  • the network device sends a paging message in the initial DL BWP configured/defined separately for Redcap UE or in the CORESET configured/defined separately for Redcap UE.
  • the network device can also use the initial downlink BWP configured or defined separately for the non-reduced capability terminal device (non-RedCap) or a separate BWP for the non-reduced capability terminal device (non-RedCap)
  • a configured or defined control resource set (CORESET) sends paging messages for the non-reduced capability terminal device (non-RedCap).
  • the network device may receive an indication from the core network, where the indication is used to indicate whether the paging message is a paging message for a terminal device with reduced capability. Therefore, the complete CORESET#0 or the complete set of additional control resources for paging (additional CORESET for paging), the network device can determine whether the paging message is for the RedCap UE through the indication message.
  • the paging message sent by the core network for paging the RedCap UE is different from the paging message for paging the non-RedCap UE, and/or has a different structure, and/or contains different information elements (information element, IE). .
  • the core network can send the paging message for paging RedCap UE and the paging message for paging non-RedCap UE to the network device (for example, gNB) separately through different messages; or, the core network can pass the paging message Different structures or IEs in different structures or IEs, etc., to distinguish between paging messages for paging RedCap UEs and paging messages for paging non-RedCap UEs.
  • an indicator for example, the indicator can be 1bit, used to indicate The paging message is a paging message for RedCap UE, or, the indicator can be used to indicate that a paging record is a paging record for RedCap UE.
  • the network device After receiving a paging message, the network device (gNB) can determine whether the paging message is used for paging RedCap UE or non-RedCap UE according to the receiving time and/or structure and/or IE contained in the paging message, or Which paging records in the paging message are used for paging the RedCap UE, and the paging message for paging the RedCap UE is sent to the RedCap UE at the paging occasion corresponding to the RedCap UE.
  • the indication can be sent through the F1 interface message
  • the network device can include a centralized unit (CU) and a distributed unit (DU), the The CU sends the indication to the DU through the F1 interface message.
  • CU centralized unit
  • DU distributed unit
  • the network device is able to determine in which bandwidth or BWP or CORESET to send the paging message sent by the core network for the terminal device with reduced capability.
  • the embodiment of the sixth aspect of the present application provides a method for sending and receiving signals, which is applied to a terminal device (RedCap UE) with reduced capabilities.
  • the method for sending and receiving signals in the embodiment of the sixth aspect is the same as the method for sending and receiving signals in the embodiment of the fifth aspect. The method corresponds.
  • Fig. 8 is a schematic diagram of a method for sending and receiving signals according to an embodiment of the sixth aspect. As shown in Fig. 8, the method includes:
  • the terminal device with reduced capability obtains the configuration of a first initial downlink BWP, where the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability; and
  • Operation 802. Receive a paging message from a network device.
  • the terminal equipment with reduced capability may be in RRC_IDLE state or RRC_INACTIVE state.
  • the paging message in operation 802 is, for example, a paging (paging) message sent by the core network to the network device (eg, gNB) and forwarded by the network device to the RedCap UE.
  • the network device eg, gNB
  • the bandwidth for receiving the paging message includes: the initial downlink BWP of the non-reduced capability terminal device, control resource set 0 (CORESET#0) or the initial downlink BWP of the non-reduced capability terminal device Additional control resource set (additional CORESET).
  • the terminal device with reduced capability may also readjust (retuning) the radio frequency (RF) to the initial downlink BWP of the terminal device with reduced capability according to the corresponding paging occasions (PO). or CORESET#0 or an additional control resource set (additional CORESET) in the initial downlink BWP of the non-reduced capability terminal equipment to receive the paging message.
  • RF radio frequency
  • a RedCap UE in the RRC_IDLE or RRC_INACTIVE state resides in the initial DL BWP configured or defined separately for the RedCap UE, and the initial DL BWP does not contain a complete CORESET#0 or does not contain a complete initial DL corresponding to a non-RedCap UE In the case of CORESET used for paging messages in BWP.
  • the bandwidth for receiving the paging message includes: the initial downlink BWP of the non-reduced capability terminal device, control resource set 0 (CORESET#0) or the initial downlink BWP of the non-reduced capability terminal device An additional control resource set (additional CORESET); and an initial downlink BWP configured or defined separately for the terminal device with reduced capability or a control resource set (CORESET) configured or defined separately for the terminal device with reduced capability.
  • the bandwidth for receiving the paging message includes: the initial downlink BWP configured or defined separately for the terminal device with reduced capability or the control resource set (CORESET) configured or defined separately for the terminal device with reduced capability ).
  • CORESET control resource set
  • the terminal device can determine in which bandwidth or BWP or CORESET the paging message sent by the core network for the terminal device with reduced capabilities is received.
  • An embodiment of the present application provides an apparatus for sending and receiving signals, which is applied to a terminal device with reduced capabilities (Redcap UE).
  • Fig. 9 is a schematic diagram of a device for transmitting and receiving signals in an embodiment of the seventh aspect.
  • the device for transmitting and receiving signals 900 includes a first transceiving unit 901, and the first transceiving unit 901 is configured such that:
  • the terminal device with reduced capability is configured with a first initial downlink BWP, where the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals before the random access is completed.
  • the device 900 for sending and receiving signals reference may be made to the embodiment of the first aspect.
  • Fig. 10 is another schematic diagram of the device for transmitting and receiving signals in the embodiment of the seventh aspect.
  • the device for transmitting and receiving signals 1000 includes a third transceiver unit 1001, and the third transceiver unit 1001 is configured such that:
  • the terminal device with reduced capability obtains a configuration of a first initial downlink BWP, where the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • a terminal device with reduced capabilities operates in a bandwidth that is at least one One of the candidate bandwidths.
  • FIG. 11 is another schematic diagram of the device for transmitting and receiving signals in the embodiment of the seventh aspect.
  • the device for transmitting and receiving signals 1100 includes a sixth transceiver unit 1101, and the sixth transceiver unit 1101 is configured such that:
  • the terminal device with reduced capability obtains a configuration of a first initial downlink BWP, where the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • An embodiment of the present application provides an apparatus for sending and receiving signals, which is applied to a network device, such as a gNB.
  • Fig. 12 is a schematic diagram of an apparatus for sending and receiving signals in an embodiment of the eighth aspect.
  • the apparatus 1200 for sending and receiving signals includes a second transceiver unit 1201, and the second transceiver unit 1201 is configured such that the network device:
  • Fig. 13 is another schematic diagram of the device for transmitting and receiving signals in the embodiment of the eighth aspect.
  • the device for transmitting and receiving signals 1300 includes a fourth transceiving unit 1301, and the fourth transceiving unit 1301 is configured such that the network device:
  • the one bandwidth is one of at least one candidate bandwidth.
  • Fig. 14 is another schematic diagram of the device for sending and receiving signals in the embodiment of the eighth aspect.
  • the device 1400 for sending and receiving signals includes a fifth transceiver unit 1401, and the fifth transceiver unit 1401 is configured to make the network device:
  • An embodiment of the present application also provides a communication system, where the communication system may include a terminal device and a network device with reduced capabilities.
  • Fig. 15 is a schematic diagram of a terminal device in an embodiment of the ninth aspect.
  • the terminal device 1500 may include a processor 1510 and a memory 1520 ; the memory 1520 stores data and programs, and is coupled to the processor 1510 . It is worth noting that this figure is exemplary; other types of structures may also be used in addition to or instead of this structure to implement telecommunications functions or other functions.
  • Terminal device 1500 may be a reduced capability terminal device.
  • the processor 1510 may be configured to execute a program to implement the methods described in the first, third, and sixth embodiments.
  • the terminal device 1500 may further include: a communication module 1530 , an input unit 1540 , a display 1550 , and a power supply 1560 .
  • a communication module 1530 the terminal device 1500 may further include: a communication module 1530 , an input unit 1540 , a display 1550 , and a power supply 1560 .
  • the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the terminal device 1500 does not necessarily include all the components shown in FIG. have technology.
  • Fig. 16 is a schematic diagram of a network device of an embodiment of the ninth aspect.
  • a network device 1600 may include: a processor 1610 (such as a central processing unit CPU) and a memory 1620 ; the memory 1620 is coupled to the processor 1610 .
  • the memory 1620 can store various data; in addition, it also stores a program 1630 for information processing, and executes the program 1630 under the control of the processor 1610 .
  • the processor 1610 may be configured to execute a program to realize the method described in the embodiment of the second aspect, the fourth aspect or the fifth aspect.
  • the network device 1600 may further include: a transceiver 1640 and an antenna 1650 ; where the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the network device 1600 does not necessarily include all the components shown in FIG. 16 ; in addition, the network device 1600 may also include components not shown in FIG. 16 , and reference may be made to the prior art.
  • An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the methods described in the first, third, and sixth embodiments.
  • the embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program causes the terminal device to execute the methods described in the first, third, and sixth embodiments.
  • An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the methods described in the second, fourth, and fifth embodiments.
  • the embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables the network device to execute the methods described in the second, fourth, and fifth embodiments.
  • the above devices and methods in this application can be implemented by hardware, or by combining hardware and software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to realize the above-mentioned device or constituent component, or enables the logic component to realize the above-mentioned various methods or steps.
  • the present application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, and the like.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams shown in the figure and/or one or more combinations of the functional block diagrams may correspond to each software module or each hardware module of the computer program flow.
  • These software modules may respectively correspond to the steps shown in the figure.
  • These hardware modules for example, can be realized by solidifying these software modules by using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium, or it can be an integral part of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or large-capacity flash memory device.
  • One or more of the functional blocks described in the accompanying drawings and/or one or more combinations of the functional blocks can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • One or more of the functional blocks described in the drawings and/or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors processor, one or more microprocessors in communication with a DSP, or any other such configuration.
  • a method for sending and receiving signals, applied to a terminal equipment (Redcap UE) that reduces capability comprising:
  • the terminal device with reduced capability obtains the configuration of a first initial downlink BWP, and the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals before the random access is completed.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals before the initial access procedure or before the random access procedure.
  • the terminal device with reduced capability resides in the first initial downlink BWP before the initial access procedure or before the random access procedure.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals during an initial access process or a random access process.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals when receiving the configuration of the first initial downlink BWP or after receiving the configuration of the first initial downlink BWP.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals during or after the initialization of the random access procedure.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals when the first initial uplink BWP is used,
  • the first initial uplink BWP is an initial uplink BWP configured or defined separately for the terminal device with reduced capability.
  • the first initial downlink BWP of the reduced capability terminal device has a predetermined identifier (BWP-id).
  • the first initial downlink BWP of the reduced capability terminal device corresponds to the first initial uplink BWP
  • the first initial uplink BWP is an initial uplink BWP configured or defined separately for the terminal device with reduced capabilities.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive an additional SSB.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive signals during or after the random access resource selection process.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive a signal.
  • the terminal device with reduced capability uses the first initial downlink BWP to receive a signal before receiving the random access response or when receiving the random access response.
  • Random access message 1 (Msg1, preamble) or random access message A (preamble+PUSCH) indicates the type of the terminal device with reduced capability.
  • the first initial downlink BWP is used to receive signals.
  • Random access message 1 (Msg1, preamble), random access message A (preamble+PUSCH) or random access message 3 indicates the type of the terminal device with reduced capabilities.
  • the first initial downlink BWP partially overlaps or does not overlap with control resource set zero (CORESET#0).
  • the terminal device with reduced capabilities operates in a bandwidth when it is in an idle state, in an inactive state, or before a random access procedure for radio resource control (RRC) connection re-establishment, the one bandwidth being One of at least one candidate bandwidth.
  • RRC radio resource control
  • the at least one candidate bandwidth includes:
  • Control resource set 0 (CORESET#0);
  • the initial downlink BWP for non-reduced capability UEs The initial downlink BWP for non-reduced capability UEs.
  • CORESET control resource set
  • the terminal device with reduced capability works in the first initial downlink BWP or the control resource set (CORESET) used by the first initial downlink BWP for receiving system information and/or paging,
  • the method also includes:
  • said reduced-capability terminal device obtains a master information block (MIB);
  • SIB1 System Information Block 1
  • the terminal device with reduced capabilities is in an idle (idle) state, an inactive (inactive) state, or before a random access procedure of radio resource control (RRC) connection re-establishment,
  • RRC radio resource control
  • the terminal device with reduced capability uses the one bandwidth in the at least one candidate bandwidth, or determines the one bandwidth according to instruction information of the network device.
  • the instruction information is sent through the following information or message:
  • Radio resource control release/radio resource control release RRC release/RRC release with suspend indication
  • radio resource control rejection RRC reject
  • RRC reconfiguration radio resource control reconfiguration
  • a method for sending and receiving signals, applied to network equipment comprising:
  • the configuration of the first initial downlink BWP sent to the terminal device with reduced capabilities includes: configuration of at least one control resource set (CORESET) and/or configuration of at least one common search space (CSS).
  • CORESET control resource set
  • CSS common search space
  • the control resource set (CORESET) and/or the common search space (CSS) are used for the reduced capability terminal device to receive system information and/or paging and/or random access responses.
  • the first initial downlink BWP is used to send a signal before the initial access procedure of the terminal device with reduced capabilities or before the random access procedure.
  • the first initial downlink BWP is used to send a signal.
  • the first initial downlink BWP is used to send a signal.
  • the first initial uplink BWP is an initial uplink BWP configured or defined separately for the terminal device with reduced capability.
  • the first initial downlink BWP of the reduced capability terminal device has a predetermined identifier (BWP-id).
  • the first initial downlink BWP of the reduced capability terminal device corresponds to the first initial uplink BWP
  • the first initial uplink BWP is an initial uplink BWP configured or defined separately for the terminal device with reduced capabilities.
  • the terminal device with reduced capability uses the first initial downlink BWP to send a signal.
  • the first initial downlink BWP is used to send a signal.
  • Random access message 1 (Msg1, preamble) or random access message A (preamble+PUSCH) indicates the type of the terminal device with reduced capabilities.
  • Random access message 1 (Msg1, preamble), random access message A (preamble+PUSCH) or random access message 3 indicates the type of the terminal device with reduced capability.
  • the one bandwidth is one of at least one candidate bandwidth.
  • the at least one candidate bandwidth includes:
  • Control resource set 0 (CORESET#0);
  • the initial downlink BWP for non-reduced capability UEs The initial downlink BWP for non-reduced capability UEs.
  • CORESET control resource set
  • the instruction information is sent through the following information or message:
  • Radio resource control release/radio resource control release RRC release/RRC release with suspend indication
  • radio resource control rejection RRC reject
  • RRC reconfiguration radio resource control reconfiguration
  • a method for sending and receiving signals, applied to network equipment comprising:
  • Said bandwidth includes:
  • the initial downlink BWP of the non-reduced capability terminal device control resource set 0 (CORESET#0) or the additional control resource set (additional CORESET) in the initial downlink BWP of the non-reduced capability terminal device.
  • Said bandwidth includes:
  • control resource set 0 CORESET#0
  • additional control resource set additional CORESET
  • An initial downlink BWP configured or defined separately for the terminal device with reduced capability or a control resource set (CORESET) configured or defined separately for the terminal device with reduced capability.
  • CORESET control resource set
  • the initial downlink BWP of the non-reduced capability terminal device and the initial downlink BWP of the reduced capability terminal device both contain control resource set 0 (CORESET#0) or an additional control resource set for paging (CORESET),
  • the network device sends a paging message to the reduced-capability terminal device and the non-reduced-capability terminal device on a control resource set 0 (CORESET#0) or an additional control resource set for paging (CORESET).
  • CORESET#0 control resource set 0
  • CORESET#0 additional control resource set for paging
  • At least one of the initial downlink BWP of the non-reduced capability terminal device and the initial downlink BWP of the reduced capability terminal device does not contain control resource set 0 (CORESET#0) or additional control resource set for paging (CORESET) in the case of,
  • the network device uses the initial downlink BWP of the terminal device with non-reduced capability, control resource set 0 (CORESET#0) or an additional control resource set (additional CORESET) in the initial downlink BWP of the terminal device with non-reduced capability, and the The initial downlink BWP configured or defined separately by the terminal device with reduced capability or the control resource set (CORESET) configured or defined separately for the terminal device with reduced capability is used to send a paging message.
  • control resource set 0 CORESET#0
  • additional CORESET additional control resource set
  • Said bandwidth includes:
  • An initial downlink BWP configured or defined separately for the terminal device with reduced capability or a control resource set (CORESET) configured or defined separately for the terminal device with reduced capability.
  • CORESET control resource set
  • the network device uses the initial downlink BWP configured or defined separately for the terminal device with reduced capability or the control resource set (CORESET) configured or defined for the terminal device with reduced capability to send the terminal with reduced capability
  • CORESET control resource set
  • An indication is received from a core network, the indication being used to indicate whether the paging message is a paging message for the reduced capability terminal device.
  • the paging message for paging RedCap UE is different from the paging message for paging non-RedCap UE, or the paging message structure or IE is different.
  • the network device includes a centralized unit (CU) and a distributed unit (DU), and the CU sends the indication to the DU through an F1 interface message.
  • CU centralized unit
  • DU distributed unit
  • a method for sending and receiving signals, applied to a terminal device with reduced capabilities comprising:
  • the terminal device with reduced capability obtains the configuration of a first initial downlink BWP, and the first initial downlink BWP is an initial downlink BWP configured or defined separately for the terminal device with reduced capability;
  • Bandwidth for receiving paging messages includes:
  • the initial downlink BWP of the non-reduced capability terminal device control resource set 0 (CORESET#0) or the additional control resource set (additional CORESET) in the initial downlink BWP of the non-reduced capability terminal device.
  • the method also includes:
  • the terminal device with reduced capability retunes (retuning) the radio frequency (RF) to the initial downlink BWP or CORESET#0 of the terminal device with reduced capability or the terminal with reduced capability according to the corresponding paging occasions (PO).
  • Bandwidth for receiving paging messages includes:
  • control resource set 0 CORESET#0
  • additional control resource set additional CORESET
  • An initial downlink BWP configured or defined separately for the terminal device with reduced capability or a control resource set (CORESET) configured or defined separately for the terminal device with reduced capability.
  • CORESET control resource set
  • Bandwidth for receiving paging messages includes:
  • An initial downlink BWP configured or defined separately for the terminal device with reduced capability or a control resource set (CORESET) configured or defined separately for the terminal device with reduced capability.
  • CORESET control resource set

Landscapes

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

Abstract

本申请实施例提供一种收发信号的装置，应用于减少能力的终端设备(Redcap UE)，所述装置包括，第一收发单元，该第一收发单元被配置为使得：所述减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及所述减少能力的终端设备在随机接入完成之前，使用所述第一初始下行BWP接收信号。

Description

收发信号的方法、装置和通信系统 技术领域
本申请实施例涉及通信技术领域。
背景技术
目前的3GPP标准中，终端设备(例如，UE)在初始接入网络过程中，进行下面的操作：
操作1)、通过搜索小区级别的PBCH/同步信号块(CD-SSB，Cell Defining SSB(Synchronization Signal Block))获得主信息块(MIB)，从中获得调度本小区系统信息块类型1(SIB1)的物理下行控制信道(PDCCH)的配置，该配置包括控制资源集合0(control resource set 0，CORESET#0)配置和搜索空间0(Search space 0，SS#0)配置。
操作2)、UE根据CORESET#0/SS#0的配置，监听PDCCH从而获取SIB1。SIB1中包含initial DL BWP的配置和initial UL BWP的配置、随机接入的配置、以及小区的其它公共配置等信息。
操作3)、UE采用initial UL BWP配置中的随机接入的相关配置，发起随机接入过程。在随机接入过程中，UE在CORESET#0上接收RAR和Msg4。
操作4)、在随机接入过程之后(例如，UE收到RRC setup、RRC Resume、或RRC Reestablishment之后)，UE工作在SIB1中指示的初始下行部分带宽(initial DL BWP)中。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
在5G版本17(Release 17，R17)中，开始研究减少能力的终端设备(Reduced Capability UE，RedCap UE)。RedCap UE的主要应用场景(use case)包括：工业无线传感器、监控摄像头和可穿戴设备。RedCap UE的特点是，设备成本和复杂度比版 本15/版本16(R15/R16)的高端增强移动宽带(eMBB)和低时延高可靠通信(URLLC)设备低，并且具有较小的尺寸，业务速率要求不高，有些设备需要具有较长的电池寿命。
本申请的发明人发现，如果为RedCap UE单独配置的initial DL BWP可以在初始接入过程中或者在初始接入过程之前被使用，那么，网络设备与RedCap UE对RedCap UE工作的初始下行BWP或CORESET等需要有一致的理解：例如，RedCap UE什么时候开始在为该RedCap UE单独配置的initial DL BWP中工作或者什么时候开始监听为RedCap UE单独配置的initial DL BWP中的控制资源集合(Control Resource Set，CORESET)和/或公共搜索空间(Common Search Space，CSS)；又例如，RedCap UE在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，工作在哪个带宽等。
现有技术中，针对为RedCap UE单独配置的initial DL BWP可以在初始接入过程中或者在初始接入过程之前被使用的情况，网络设备与RedCap UE对RedCap UE工作的初始下行BWP或CORESET等没有一致的理解，因此，会发生下行传输丢失或错误。
针对上述问题的至少之一，本申请实施例提供一种收发信号的方法、装置和通信系统，减少能力的终端设备(RedCap UE)在随机接入完成之前，使用为该RedCap UE单独配置的第一初始下行BWP接收信号，由此，网络设备与RedCap UE对RedCap UE工作的初始下行BWP或CORESET等能够有一致的理解。
根据本申请实施例的一个方面，提供一种收发信号的装置，应用于减少能力的终端设备(Redcap UE)，所述装置包括，第一收发单元，该第一收发单元被配置为使得：
所述减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
所述减少能力的终端设备在随机接入完成之前，使用所述第一初始下行BWP接收信号。
根据本申请实施例的另一个方面，提供一种收发信号的装置，应用于网络设备，所述装置包括，第二收发单元，该第二收发单元被配置为使得所述网络设备：
向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
在所述减少能力的终端设备随机接入完成之前，使用所述第一初始下行BWP向所述减少能力的终端设备发送信号。
根据本申请实施例的另一个方面，提供一种收发信号的装置，应用于减少能力的终端设备(Redcap UE)，所述装置包括，第三收发单元，该第三收发单元被配置为使得：
所述减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
所述减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，所述一个带宽是至少一个候选带宽中的一者。
根据本申请实施例的另一个方面，提供一种收发信号的装置，应用于网络设备，所述装置包括，第四收发单元，该第四收发单元被配置为使得所述网络设备：
向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
指示所述减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，所述一个带宽是至少一个候选带宽中的一者。
根据本申请实施例的另一个方面，提供一种收发信号的装置，应用于网络设备，所述装置包括，第五收发单元，该第五收发单元被配置为使得所述网络设备：
向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；
从核心网接收寻呼(paging)消息；以及
确定向所述减少能力的终端设备发送寻呼消息所使用的至少带宽。
根据本申请实施例的另一个方面，提供一种收发信号的装置，应用于减少能力的终端设备，所述装置包括第六收发单元，所述第六收发单元被配置为使得：
所述减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
从网络设备接收寻呼消息。
本申请实施例的有益效果之一在于：减少能力的终端设备(RedCap UE)在随机 接入完成之前，使用为该RedCap UE单独配置的第一初始下行BWP接收信号，由此，网络设备与RedCap UE对RedCap UE工作的初始下行BWP或CORESET等能够有一致的理解。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是本申请第一方面的实施例中收发信号的方法的一个示意图；
图2是non-RedCap UE使用initial DL BWP和RedCap UE使用第一initial DL BWP的一个示意图；
图3是本申请第一方面的实施例中收发信号的方法的一个示意图；
图4是第三方面的实施例的收发信号的方法的一个示意图；
图5是本申请第四方面的实施例中收发信号的方法的一个示意图；
图6是non-RedCap UE使用initial DL BWP和RedCap UE使用第一initial DL BWP的一个示意图；
图7是第五方面的实施例的收发信号的方法的一个示意图；
图8是第六方面的实施例的收发信号的方法的一个示意图；
图9是第七方面的实施例中收发信号的装置的一个示意图；
图10是第七方面的实施例中收发信号的装置的另一个示意图；
图11是第七方面的实施例中收发信号的装置的另一个示意图；
图12是第八方面的实施例中收发信号的装置的一个示意图；
图13是第八方面的实施例中收发信号的装置的另一个示意图；
图14是第八方面的实施例中收发信号的装置的另一个示意图；
图15是第九方面的实施例的终端设备的示意图；
图16是第九方面的实施例的网络设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：集成的接入和回传节点(IAB-node)、基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。
在以下的说明中，在不引起混淆的情况下，术语“上行控制信号”和“上行控制信 息(UCI，Uplink Control Information)”或“物理上行控制信道(PUCCH，Physical Uplink Control Channel)”可以互换，术语“上行数据信号”和“上行数据信息”或“物理上行共享信道(PUSCH，Physical Uplink Shared Channel)”可以互换；
术语“下行控制信号”和“下行控制信息(DCI，Downlink Control Information)”或“物理下行控制信道(PDCCH，Physical Downlink Control Channel)”可以互换，术语“下行数据信号”和“下行数据信息”或“物理下行共享信道(PDSCH，Physical Downlink Shared Channel)”可以互换。
另外，发送或接收PUSCH可以理解为发送或接收由PUSCH承载的上行数据，发送或接收PUCCH可以理解为发送或接收由PUCCH承载的上行信息，发送或接收PRACH可以理解为发送或接收由PRACH承载的preamble；上行信号可以包括上行数据信号和/或上行控制信号等，也可以称为上行传输(UL transmission)或上行信息或上行信道。在上行资源上发送上行传输可以理解为使用该上行资源发送该上行传输。类似地，可以相应地理解下行数据/信号/信道/信息。
在本申请实施例中，高层信令例如可以是无线资源控制(RRC)信令；例如称为RRC消息(RRC message)，例如包括MIB、系统信息(system information)、专用RRC消息；或者称为RRC IE(RRC information element)。高层信令例如还可以是MAC(Medium Access Control)信令；或者称为MAC CE(MAC control element)。但本申请不限于此。
在本申请的实施例中，对初始下行BWP(initial DL BWP)，可以有如下的前提：
·在初始接入(initial access)之后(例如，在RRC setup、RRC Resume、或RRC Reestablishment之后)，RedCap UE不被预期采用比最大RedCap UE带宽更宽的初始下行BWP(initial DL BWP)。
·最少对TDD，RedCap UE的initial DL BWP(不超过最大RedCap UE带宽)可以被可选地配置/定义，与非RedCap UE的initial DL BWP分开。
其中，如果单独的RedCap UE的initial DL BWP被配置/定义，那么这个单独的RedCap UE的initial DL BWP可以至少在初始接入之后被使用(例如，在RRC setup、RRC Resume、或RRC Reestablishment之后)。
第一方面的实施例
第一方面的实施例提供一种收发信号的方法，应用于减少能力的终端设备(Redcap UE)。
图1是本申请第一方面的实施例中收发信号的方法的一个示意图，如图1所示，该方法包括：
操作101、减少能力的终端设备(RedCap UE)得到第一初始下行BWP(initial DL BWP)的配置，该第一初始下行BWP是为该减少能力的终端设备单独配置或定义的初始下行BWP；以及
操作102、该减少能力的终端设备在随机接入完成之前，使用该第一初始下行BWP接收信号。
根据第一方面的实施例，能够明确：RedCap UE什么时候开始在为该Redcap UE单独配置或定义的initial DL BWP中工作。由此，网络侧与RedCap UE侧对下行的工作BWP有一致的理解，避免下行传输丢失或错误。
在上述操作101中，RedCap UE可以从网络设备得到该第一初始下行BWP的配置。
例如，网络设备(例如，gNB)发送的SIB1或其他系统信息中可以包括为非减少能力的终端设备(non-RedCap UE)配置的initial DL BWP的配置以及为RedCap UE单独配置或定义的initial DL BWP的配置，RedCap UE可以忽略为non-RedCap UE配置的initial DL BWP的配置，将为RedCap UE单独配置的initial DL BWP作为自己的initial DL BWP或将为RedCap UE单独配置的initial DL BWP的配置作为自己的initial DL BWP的配置，例如该initial DL BWP具有BWP-id为0；或者，RedCap UE也可以将为non-RedCap UE配置的initial DL BWP和为RedCap UE单独配置的initial DL BWP都作为自己的initial DL BWP，这2个initial DL BWP可以采用不同的BWP-id进行区分，例如为non-RedCap UE配置的initial DL BWP具有BWP-id为0，为RedCap UE单独配置的initial DL BWP具有BWP-id为5或其他值(该值可以是预定义的或者由网络设备配置)，或者为RedCap UE单独配置的initial DL BWP具有BWP-id为0，为RedCap UE单独配置的initial DL BWP具有BWP-id为5或其他值(该值可以是预定义的或者由网络设备配置)，等等。
在至少一个实施例中，网络设备发送的为RedCap UE单独配置或定义的initial DL BWP的配置可以包括至少一个CORESET(以下称为第一CORESET)的配置和/或至 少一个CSS(以下称为第一CSS)的配置，用于RedCap UE接收系统信息(可以是包括SIB1的系统信息或不包括SIB1的系统信息)和/或寻呼和/或随机接入响应(或随机接入消息2)。
对于卸载(offloading)目的，为RedCap UE单独配置/定义的initial DL BWP可能不包括完整的CORESET#0，即为RedCap UE单独配置/定义的initial DL BWP可能与小区的CORESET#0部分重叠或者不重叠。此外，第一CORESET可以与小区的CORESET#0部分重叠或者不重叠。第一CSS可以与小区的SS#0部分重叠或者不重叠。
图2是non-RedCap UE使用initial DL BWP和RedCap UE使用第一initial DL BWP的一个示意图。图2示出了为RedCap UE单独配置/定义的initial DL BWP(即，第一initial DL BWP)与CORESET#0不重叠以及第一CORESET与小区的CORESET#0不重叠的情况，但是，本申请不限于此，第一initial DL BWP与CORESET#0也可以至少部分重叠。
图2中的Separated initial DL BWP for RedCap即为第一initial DL BWP，虚线框的CORESET为第一CORESET。
根据上述的操作102，与non-RedCap UE不同，RedCap UE可以在随机接入完成之前(例如，在随机接入过程之前或者随机接入过程中)使用系统信息(该系统信息例如是SIB1或其他SIB)配置的为RedCap UE单独配置/定义的initial DL BWP(即，第一initial DL BWP)。
在上述操作102中，使用为RedCap UE单独配置/定义的initial DL BWP接收信号可以包括：在为RedCap UE单独配置/定义的initial DL BWP中接收信号，该接收的信号例如是物理下行共享信道(PDSCH)和/或信道状态信息参考信号(CSI-RS)等下行参考信号和/或物理下行控制信道(PDCCH)；或者，将为RedCap UE单独配置/定义的initial DL BWP的带宽作为接收带宽；或者，在为RedCap UE单独配置的initial DL BWP中的CORESET和/或CSS中监听PDCCH；或者，RedCap UE将带宽保持或切换或调节到在为RedCap UE单独配置/定义的initial DL BWP，等等。此外，本申请中“使用第一initial DL BWP接收信号”的含义不限于此。
下面，通过实施方式1和实施方式2来说明RedCap UE使用第一initial DL BWP的时刻。
实施方式1
减少能力的终端设备(RedCap UE)在初始接入过程之前或随机接入过程之前，使用第一初始下行BWP。
其中，该减少能力的终端设备在初始接入过程之前或随机接入过程之前，可以驻留在第一初始下行BWP中。例如，RedCap UE处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，驻留在第一初始下行BWP中。
减少能力的终端设备可以在选择到合适的小区后或者在随机接入过程初始化之前，驻留在第一初始下行BWP中。
此外，减少能力的终端设备可以在收到第一初始下行BWP的配置时或收到第一初始下行BWP的配置之后，使用该第一初始下行BWP接收信号。其中，“收到第一初始下行BWP的配置时或收到第一初始下行BWP的配置之后”是“随机接入过程之前”的一个例子。
例如，RedCap UE在SIB1或其他系统信息中收到第一初始下行BWP的配置，并且，在收到该配置时或之后，使用该第一初始下行BWP。可以对TS38.331做出如表1所示的修改，其中，下划线部分为新增内容。
表1
Figure PCTCN2021110680-appb-000001
再例如，RedCap UE在RRC Release或RRC Release with suspend indication消息中收到第一初始下行BWP的配置，并且，在收到该配置时或之后，使用该第一初始下行BWP。
实施方式2
减少能力的终端设备(RedCap UE)在初始接入过程中或随机接入过程中，使用第一初始下行BWP接收信号。
实施方式2可以包括如下具体实现方式1～5。
具体实现方式1：
减少能力的终端设备在收到第一初始下行BWP的配置时或收到第一初始下行BWP的配置之后，使用该第一初始下行BWP接收信号，其中，“收到第一初始下行BWP的配置时或收到第一初始下行BWP的配置之后”是“初始接入过程中”的一个例子。例如，RedCap UE在SIB1或其他系统信息中收到第一初始下行BWP的配置，并且，在收到该配置时或之后，使用该第一初始下行BWP。
在具体实现方式1中，可以对TS38.331做出如上述表1所示的修改，其中，下划线部分为新增内容。
具体实现方式2：
减少能力的终端设备在随机接入过程的初始化过程中或初始化过程之后，使用第一初始下行BWP接收信号。
例如，随机接入过程的初始化过程中，可以是当为RedCap UE单独配置的初始上行BWP(initial UL BWP)被使用时，即，减少能力的终端设备在使用第一初始上行BWP时，使用第一初始下行BWP接收信号，该第一初始上行BWP是为该减少能力的终端设备单独配置或定义的初始上行BWP。
在具体实现方式2的一个实施例中，减少能力的终端设备的第一初始下行BWP具有预定的标识(BWP-id)，该预定的标识例如是BWP-id为0。
例如，如果RedCap UE认为为RedCap UE单独配置的initial DL BWP具有BWP-id为0，则不用修改MAC规范中5.15节BWP operation，但需要说明RedCap UE使用的是为RedCap UE单独配置的initial DL BWP，即，RedCap UE可以忽略为non-RedCap UE配置的initial DL BWP的配置，将为RedCap UE单独配置的initial DL BWP作为自己的initial DL BWP，BWP-id为0。
在具体实现方式2的另一个实施例中，减少能力的终端设备的第一初始下行BWP与第一初始上行BWP对应。
例如：如果RedCap UE认为为RedCap UE单独配置的initial DL BWP具有的BWP-id不为0，则修改MAC规范中5.15节BWP operation，例如修改为如下的表2；此外，需要规定对RedCap UE来说，与initial UL BWP对应的DL BWP是为RedCap UE单独配置的initial DL BWP，即，第一初始下行BWP与第一初始上行BWP对应。
表2
Figure PCTCN2021110680-appb-000002
再例如，在随机接入过程的初始化过程中，RedCap UE可以在设置随机接入preamble功率参数后，或者在选择随机接入的载波后，或者在设置随机接入过程的类型(例如类型为两步随机接入或四步随机接入)后，或者在初始化随机接入类型特定的变量之后，将下行BWP转换到第一初始下行BWP，或者调节接收带宽到第一初始下行BWP。
再例如，在随机接入过程的初始化过程之后，RedCap UE可以在执行随机接入资源选择过程之前，将下行BWP转换到第一初始下行BWP，或者调节接收带宽到第一初始下行BWP。
在具体实现方式1和具体实现方式2中，网络设备可以在第一初始下行BWP中发送额外的SSB(additional SSB)，RedCap UE可以在第一初始下行BWP中接收该额外的SSB。由此，减少能力的终端设备在随机接入过程中的随机接入资源选择过程中能够通过对第一初始下行BWP中的SSB的测量结果来选择SSB。其中，该额外的SSB可以如图2的additional SSB所示。
具体实现方式3：
减少能力的终端设备在随机接入资源选择过程中或随机接入资源选择过程之后，使用第一初始下行BWP接收信号。
例如，减少能力的终端设备在SSB被选择之后，使用第一初始下行BWP接收信 号；更具体地，在随机接入资源选择过程中，在减少能力的终端设备从小区定义的SSB中或者从为non-RedCap配置的初始下行BWP中的SSB中选择了SSB之后，使用第一初始下行BWP接收信号。
再例如，减少能力的终端设备在选择随机接入preamble组(Group A或Group B)之后，或者在选择随机接入preamble之后，或者在确定下一个可用的随机接入时机(PRACH occasion)之后，使用第一初始下行BWP接收信号。
具体实现方式4：
减少能力的终端设备在接收随机接入响应(Random Access Response)之前或接收随机接入响应时，使用第一初始下行BWP接收信号。
其中，在接收随机接入响应之前，包括：在发送了随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)后，例如在发送第一条随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)后。
在接收随机接入响应时，包括在启动随机接入响应窗口(ra-ResponseWindow)时，例如在第一次启动随机接入响应窗口时。
在具体实现方式1～具体实现方式4中，随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)指示减少能力的终端设备的类型，即指示该终端设备是RedCap UE，和/或指示减少能力的终端设备的接收天线个数，例如1Rx或2Rx，由此，网络设备可以确定该RedCap UE对应的initial DL BWP，从而在正确的BWP中发送Msg2和/或Msg4。
具体实现方式5：
在随机接入消息3(Msg3)被发送时或随机接入消息3(Msg3)被发送之后，RedCap UE使用第一初始下行BWP接收信号。
在具体实现方式5中，Msg4可以在为Redcap UE单独配置的initial DL BWP中被发送，Msg2可以不在为Redcap UE单独配置的initial DL BWP中被发送。
在具体实现方式5中，随机接入消息1(Msg1，preamble)、随机接入消息A(preamble+PUSCH)或随机接入消息3指示该减少能力的终端设备的类型，即指示该终端设备是RedCap UE，和/或指示减少能力的终端设备的接收天线个数，例如1Rx或2Rx，由此，网络设备可以确定该RedCap UE对应的initial DL BWP，从而在正确的BWP中发送Msg4。
在具体实现方式3～具体实现方式5中，网络设备可以不在第一initial DL BWP中发送额外的SSB，RedCap UE可以不在第一initial DL BWP中接收额外的SSB。
在第一方面的实施例中，减少能力的终端设备可以使用为non-RedCap配置的初始上行BWP配置中的随机接入的相关配置，或者使用为RedCap UE单独配置或定义的初始上行BWP中的随机接入的相关配置，如果其中为RedCap UE单独配置或定义了初始上行BWP的话，随机接入的相关配置可以包括RACH-ConfigCommon IE中的至少一个参数。
在第一方面的实施例中，RedCap UE在随机接入完成之前，使用第一initial DL BWP接收信号，由此，网络侧与UE侧对下行的工作BWP有一致的理解，避免下行传输丢失或错误。
第二方面的实施例
至少针对与第一方面的实施例相同的问题，本申请第二方面的实施例提供一种收发信号的方法，应用于网络设备。第二方面的实施例的收发信号的方法与第一方面的实施例的收发信号的方法对应。
如图3所示，收发信号的方法包括：
操作301、向减少能力的终端设备发送第一初始下行BWP的配置，该第一初始下行BWP是为该减少能力的终端设备单独配置或定义的初始下行BWP；以及
操作302、在减少能力的终端设备随机接入完成之前，使用第一初始下行BWP向减少能力的终端设备发送信号。
在至少一个实施例中，向减少能力的终端设备发送的第一初始下行BWP的配置中包括：至少一个控制资源集合(CORESET)(以下称为第一CORESET)的配置和/或至少一个公共搜索空间(CSS)(以下称为第一CSS)的配置。其中，该控制资源集合(CORESET)和/或该公共搜索空间(CSS)用于该减少能力的终端设备接收系统信息(可以是包括SIB1的系统信息或不包括SIB1的系统信息)和/或寻呼和/或随机接入响应(或随机接入消息2)。
在操作301中，通过系统信息或RRC专用信令向所述减少能力的终端设备发送所述第一初始下行BWP的配置。
下面，通过实施方式1和实施方式2来说明网络设备使用第一initial DL BWP向 RedCap UE发送信号的时刻。
实施方式1：
在减少能力的终端设备初始接入过程之前或随机接入过程之前，使用第一初始下行BWP发送信号。
实施方式2：
在减少能力的终端设备的初始接入过程中或随机接入过程中，使用第一初始下行BWP发送信号。
实施方式2可以包括如下具体实现方式1～5。
具体实现方式1：
在向减少能力的终端设备发送第一初始下行BWP的配置时或之后，使用第一初始下行BWP发送信号。
具体实现方式2：
在该减少能力的终端设备随机接入过程的初始化过程中或初始化过程之后，使用所述第一初始下行BWP发送信号。
例如，在减少能力的终端设备使用第一初始上行BWP时，使用第一初始下行BWP发送信号，其中，该第一初始上行BWP是为该减少能力的终端设备单独配置或定义的初始上行BWP。
在具体实现方式2的一个实施例中，减少能力的终端设备的第一初始下行BWP具有预定的标识(BWP-id)，例如，该预定的标识为BWP-id等于0。
在具体实现方式2的另一个实施例中，减少能力的终端设备的第一初始下行BWP与第一初始上行BWP对应，其中，该第一初始上行BWP是为该减少能力的终端设备单独配置或定义的初始上行BWP。
在具体实现方式1和具体实现方式2中，网络设备还可以使用第一初始下行BWP向减少能力的终端设备 发送额外的SSB。
具体实现方式3：
在减少能力的终端设备在随机接入资源选择过程中或随机接入资源选择过程之后，网络设备使用第一初始下行BWP发送信号。
例如，在随机接入资源选择过程中，在减少能力的终端设备从小区定义的SSB中选择了SSB之后，网络设备使用第一初始下行BWP发送信号。更具体地，在随机 接入资源选择过程中，在减少能力的终端设备从小区定义的SSB中或者从为non-RedCap配置的初始下行BWP中的SSB中选择了SSB之后，网络设备使用第一初始下行BWP发送信号。
再例如，减少能力的终端设备在选择随机接入preamble组(Group A或Group B)之后，或者在选择随机接入preamble之后，或者在确定下一个可用的随机接入时机(PRACH occasion)之后，网络设备使用第一初始下行BWP发送信号。
具体实现方式4：
在向减少能力的终端设备发送随机接入响应之前或发送随机接入响应时，网络设备使用第一初始下行BWP发送信号。
其中，在发送随机接入响应之前，包括：
在接收了随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)后，例如在接收第一条随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)后。
在发送随机接入响应时，包括在所述减少能力的终端设备启动随机接入响应窗口(ra-ResponseWindow)时，例如在第一次启动随机接入响应窗口时。
在具体实现方式1～具体实现方式4中，随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)指示减少能力的终端设备的类型，即，指示该终端设备RedCap UE，和/或指示减少能力的终端设备的接收天线个数，例如1Rx或2Rx，由此，网络设备可以确定该RedCap UE对应的initial DL BWP，从而在正确的BWP中发送Msg2和/或Msg4。
具体实现方式5：
在接收到随机接入消息3(Msg3)时或接收到随机接入消息3(Msg3)之后，网络设备使用第一初始下行BWP发送信号。
在具体实现方式5中，随机接入消息1(Msg1，preamble)、随机接入消息A(preamble+PUSCH)或随机接入消息3指示减少能力的终端设备的类型，和/或指示减少能力的终端设备的接收天线个数，例如1Rx或2Rx，由此，网络设备可以确定该RedCap UE对应的initial DL BWP，从而在正确的BWP中发送Msg4。
在具体实现方式3～具体实现方式5中，网络设备可以不在第一initial DL BWP中发送额外的SSB，RedCap UE可以不在第一initial DL BWP中接收额外的SSB。
在第二方面的实施例中，RedCap UE在随机接入完成之前，使用第一initial DL BWP发送信号，由此，网络侧与UE侧对下行的工作BWP有一致的理解，避免下行传输丢失或错误。
第三方面的实施例
第三方面的实施例提供一种收发信号的方法，应用于减少能力的终端设备(Redcap UE)。
图4是第三方面的实施例的收发信号的方法的一个示意图，如图4所示，该收发信号的方法包括：
操作401、减少能力的终端设备得到第一初始下行BWP的配置，第一初始下行BWP是为减少能力的终端设备单独配置或定义的初始下行BWP；以及
操作402、减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，该一个带宽是至少一个候选带宽中的一者。
在操作402中，空闲(idle)状态是指RRC_IDLE状态，未激活(inactive)状态是指RRC_INACTIVE状态。
在操作402中，在无线资源控制(RRC)连接重建的随机接入过程之前，例如是下面的至少一个：RRC连接重建过程被发起过程中，定时器T311运行期间，小区选择过程中，选择一个合适的小区时，随机接入(RA)过程被初始化之前等。
在操作402中，RedCap UE工作在一个带宽中，这里的“工作在一个带宽中”也可以被理解为包括“驻留在(camp on)一个带宽中”、“保持一个带宽”、“使用一个带宽”、“在一个带宽中接收PDCCH和/或PDSCH和/或参考信号”、“切换到一个带宽”或“重调节(retuning)射频到一个带宽”等含义。
在至少一个实施例中，上述操作402中的至少一个候选带宽包括：
控制资源集合0(CORESET#0)；非减少能力的终端设备(non-RedCap UE)对应的初始下行BWP；以及，第一初始下行BWP或第一初始下行BWP中用于接收系统信息和/或寻呼和/或随机接入响应的控制资源集合(CORESET)。
也就是说：
在实施例1中，RedCap UE可以驻留在CORESET#0中，即RedCap UE可以与 non-RedCap UE一起驻留在CORESET#0中；
在实施例2中，RedCap UE可以驻留在non-RedCap UE对应的initial DL BWP中，其中，“non-RedCap UE对应的initial DL BWP”可以指“为non-RedCap UE配置的initial DL BWP”，并且，“为non-RedCap UE配置的initial DL BWP”是小区在SIB1中配置的初始下行BWP(initial DL BWP)，RedCap UE可以工作在该initial DL BWP，例如当该BWP的带宽不大于RedCap UE支持的最大带宽时；
在实施例3中，RedCap UE可以驻留在为RedCap UE单独配置/定义的initial DL BWP(即，第一initial DL BWP)中，也可以工作在该initial DL BWP中的用于接收系统信息和/或寻呼的CORESET中。
其中，在实施例3中，图4的收发信号的方法还可以包括：
操作403、减少能力的终端设备获得主信息块(MIB)；
操作404、获得系统信息块类型1(SIB1)；以及
操作405、在判断小区可以被选择的情况下，切换到第一初始下行BWP。
例如，在实施例3中，终端设备在进入RRC_IDLE或者进入RRC_INACTIVE状态或者要进行RRC重建时(除了inter-RAT小区重选等特殊情况)需要进行小区选择，而小区选择过程中要读取MIB和SIB1。在新无线(NR)中，对于一个小区(cell)，只为终端设备配置一个CD-SSB，因此RedCap UE需要读取CD-SSB获得MIB、并从CORESET#0监听PDCCH获取SIB1，来选择小区。如果为RedCap UE配置/定义的initial DL BWP不包括完整的CORESET#0，那么RedCap UE可以先读取CD-SSB获得MIB、并在CORESET#0和/或SS#0中监听PDCCH获取SIB1，判断小区可以被选择，例如小区是一个合适的小区，然后再切换到/工作在为RedCap UE配置/定义的initial DL BWP。
在至少一个实施例中，减少能力的终端设备可以在上述的至少一个候选带宽中确定工作的该一个带宽，例如，可以根据预先设定的条件来确定该一个带宽，由此，网络设备侧也可以根据该预先设定的条件确定该一个带宽，从而与RedCap UE对工作的该一个带宽具有相同的理解。
或者，在至少另一个实施例中，RedCap UE也可以根据网络设备的指示信息确定该一个带宽。其中，该指示信息可以通过如下的信息或消息发送：系统信息(例如SIB1或其他SIB)，无线资源控制释放/具有暂停指示的无线资源控制释放(RRC  release/RRC release with suspend indication)消息，无线资源控制拒绝(RRC reject)消息或无线资源控制重配置(RRC reconfiguration)消息等。
通过第三方面的实施例，网络侧和终端侧能够明确idle或inactive状态或要进行RRC重建的RedCap UE所工作的带宽或BWP，从而有利于网络侧对RedCap UE工作的带宽或BWP具有与UE侧一致的理解，正确将RedCap UE需要接收的下行消息和信息发送给RedCap UE。
此外，第三方面的实施例能够与第一方面的实施例结合，由此，在RedCap UE被配置了第一initial DL BWP的情况下，网络侧和终端侧能够对RedCap UE何时使用第一initial DL BWP，以及RedCap UE驻留在哪个带宽等都具有一致的理解，从而避免下行传输丢失或错误。
第四方面的实施例
至少针对与第三方面的实施例相同的问题，本申请第四方面的实施例提供一种收发信号的方法，应用于网络设备。第四方面的实施例的收发信号的方法与第三方面的实施例的收发信号的方法对应。
如图5所示，收发信号的方法包括：
操作501、向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
操作502、指示该减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，该一个带宽是至少一个候选带宽中的一者。
在操作502中，空闲(idle)状态是指RRC_IDLE状态，未激活(inactive)状态是指RRC_INACTIVE状态。
在操作502中，在无线资源控制(RRC)连接重建的随机接入过程之前，例如是下面的至少一个：RRC连接重建过程被发起过程中，定时器T311运行期间，小区选择过程中，选择一个合适的小区时，随机接入(RA)过程被初始化之前等。
在本申请中，RedCap UE工作在一个带宽中，这里的“工作在一个带宽中”也可以被理解为包括“驻留在(camp on)一个带宽中”、“保持一个带宽”、“使用一个带宽”、“在一个带宽中接收PDCCH和/或PDSCH和/或参考信号”、“切换到一个带宽”或“重 调节(retuning)射频到一个带宽”等含义。
在操作502中，该至少一个候选带宽包括：
控制资源集合0(CORESET#0)；
非减少能力的终端设备对应的初始下行BWP；以及
第一初始下行BWP或所述第一初始下行BWP用于接收系统信息和/或寻呼和/或随机接入响应的控制资源集合(CORESET)。
在操作502中，该指示信息通过如下的信息或消息发送：
系统信息(例如SIB1或其他SIB)，无线资源控制释放/具有暂停指示的无线资源控制释放(RRC release/RRC release with suspend indication)消息，无线资源控制拒绝(RRC reject)消息或无线资源控制重配置(RRC reconfiguration)消息。
此外，在至少一个实施例中，网络设备可以根据该预先设定的条件确定该一个带宽，而RedCap UE也可以根据该预先设定的条件确定该一个带宽，由此，网络设备与RedCap UE对驻留的该一个带宽具有相同的理解。在这种情况下，操作502可以被省略。
通过第四方面的实施例，网络侧和终端侧能够明确idle/inactive状态或要进行RRC重建的RedCap UE所工作的带宽或BWP，从而有利于网络侧对RedCap UE工作的带宽或BWP具有与UE侧一致的理解，正确将RedCap UE需要接收的下行消息和信息发送给RedCap UE。
此外，第四方面的实施例能够与第二方面的实施例结合，由此，在RedCap UE被配置了第一initial DL BWP的情况下，网络侧和终端侧能够对RedCap UE何时使用第一initial DL BWP，以及RedCap UE驻留在哪个带宽等都具有一致的理解，从而避免下行传输丢失或错误。
第五方面的实施例
本申请第五方面的实施例提供一种收发信号的方法，应用于网络设备，在第五方面的实施例中，网络设备被表示为gNB。
如第一方面的实施例的说明，对于卸载(offloading)目的，为RedCap UE单独配置或定义的initial DL BWP(即，第一initial DL BWP)可能不包括完整的CORESET#0，即，为RedCap UE单独配置/定义的initial DL BWP可能与小区的 CORESET#0部分重叠或者不重叠。这种情况下，当核心网有寻呼(paging)消息下发到网络设备(例如，gNB)时，网络设备(例如，gNB)需要确定在哪个带宽或BWP或CORESET中发送该paging消息。如图6所示，图6是non-RedCap UE使用initial DL BWP和RedCap UE使用第一initial DL BWP的一个示意图。在图6中，为RedCap UE单独配置/定义的initial DL BWP(即，第一initial DL BWP)与CORESET#0不重叠的情况。
对于无线接入网(RAN)发起的寻呼，由于gNB具有UE的上下文，从而知道paging消息是否是对于RedCap UE，因此gNB可以在RRC_INACTIVE状态的RedCap UE所驻留的BW中(可以参考第二方面的实施例)发送该paging消息。
然而，对于核心网(CN)发起的寻呼，当前gNB从核心网发送的paging消息中无法获得paging消息是否是对于RedCap UE的信息，因此，存在gNB无法确定在哪个带宽或BWP或CORESET中发送该paging消息的问题。
为了解决上述问题，本申请第五方面的实施例提供了一种收发信号的方法。
图7是第五方面的实施例的收发信号的方法的一个示意图，如图7所示，该方法包括：
操作701、向减少能力的终端设备发送第一初始下行BWP的配置，该第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；
操作702、从核心网接收寻呼(paging)消息；以及
操作703、确定向减少能力的终端设备发送寻呼消息所使用的至少带宽。
在操作703之后，网络设备可以根据操作703中确定的带宽向向减少能力的终端设备发送寻呼消息。
在本实施例中，减少能力的终端设备可能处于RRC_IDLE状态或RRC_INACTIVE状态。
在本申请中，可以通过下述的实施方式1～实施方式3中的任一者来实现操作703。
实施方式1：
在实施方式1中，操作703所确定的带宽包括：
非减少能力的终端设备(non-RedCap UE)的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)。
例如，网络设备可以在non-RedCap UE的initial DL BWP中或CORESET#0中或non-RedCap UE的initial DL BWP中的additional CORESET中发送paging消息。
其中，RedCap UE可能需要根据自己对应的寻呼时刻(paging occasions，PO)，重新调节(retuning)射频(RF)到CORESET#0，以接收paging消息。例如在RRC_IDLE或RRC_INACTIVE状态的RedCap UE驻留在为RedCap UE单独配置或定义的initial DL BWP中、且该initial DL BWP不包含完整的CORESET#0或者不包含完整的non-RedCap UE对应的initial DL BWP中用于paging消息的CORESET的情况下。
实施方式2：
在实施方式2中，操作703所确定的带宽包括：
非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)，以及为所述减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)。
例如，网络设备可以在non-RedCap UE的initial DL BWP中或CORESET#0中或non-RedCap UE的initial DL BWP中的additional CORESET中、以及在为redcap UE单独配置/定义的initial DL BWP中或为redcap UE单独配置/定义的CORESET中，发送paging消息。
在至少一个实施例中，在非减少能力的终端设备的初始下行BWP和减少能力的终端设备的初始下行BWP都包含控制资源集合0(CORESET#0)或用于寻呼的额外控制资源集合(CORESET)的情况下，该网络设备可以在控制资源集合0(CORESET#0)或用于寻呼的额外控制资源集合(CORESET)中向所述减少能力的终端设备和非减少能力的终端设备发送寻呼消息。
在至少另一个实施例中，在非减少能力的终端设备的初始下行BWP和减少能力的终端设备的初始下行BWP中的至少一者不包含控制资源集合0(CORESET#0)或non-RedCap UE的初始下行BWP中用于寻呼的额外控制资源集合(CORESET)的情况下，该网络设备使用非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)，以及减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)，发送寻 呼消息。
例如：如果在2个initial DL BWP中都包含CORESET#0或用于paging的额外CORESET，那么为redcap UE和non-RedCap UE的paging消息可以在CORESET#0中被发送或者在paging的额外CORESET中被发送；否则，paging消息需要在2个initial DL BWP或者2个initial DL BWP中的CORESET(CORESET#0或用于paging的额外CORESET)中都被发送。
实施方式3：
在实施方式3中，操作703所确定的带宽包括：
为所述减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)。
例如，网络设备在为Redcap UE单独配置/定义的initial DL BWP中或为Redcap UE单独配置/定义的CORESET中，发送paging消息。
此外，在实施方式3的情况下，网络设备还可以使用为非减少能力的终端设备(non-RedCap)单独配置或定义的初始下行BWP或为该非减少能力的终端设备(non-RedCap)单独配置或定义的控制资源集合(CORESET)，发送用于该非减少能力的终端设备(non-RedCap)的寻呼消息。
在实施方式3的情况下，网络设备可以从核心网接收指示，该指示用于指示该寻呼消息是否为用于减少能力的终端设备的寻呼消息。由此，在为Redcap UE单独配置/定义的initial DL BWP(即，第一initial DL BWP)中不包括完整的CORESET#0或者不包括完整的用于寻呼的额外控制资源集(additional CORESET for paging)的情况下，网络设备可以通过该指示消息确定该paging消息是否是对于RedCap UE。
在一个具体实例中，核心网发送的寻呼RedCap UE的paging消息和寻呼non-RedCap UE的paging消息时间不同，和/或结构不同，和/或包含的信息元素(information element，IE)不同。
例如，核心网(CN)可以将寻呼RedCap UE的paging消息和寻呼non-RedCap UE的paging消息通过不同的消息分开发送给网络设备(例如，gNB)；又或者，核心网可以通过paging消息中的不同结构或IE等，区分寻呼RedCap UE的paging消息和寻呼non-RedCap UE的paging消息，例如，可以通过核心网寻呼消息(CN paging message)中包含的RedCap UE特定的寻呼辅助信息(paging assistant information)和 /或RedCap UE特定寻呼非连续接收(specific paging DRX)信息等；又或者，核心网可以采用一个指示(indicator)，例如，该indicator可以是1bit，用于指示该paging消息是针对RedCap UE的paging消息，或者，该indicator可以用于指示一个paging record是针对RedCap UE的paging record。网络设备(gNB)在收到一条paging消息后，可以根据该paging消息的接收时间和/或结构和/或包含的IE，确定该paging消息是用于寻呼RedCap UE还是non-RedCap UE、或者该paging消息中哪些paging record是用于寻呼RedCap UE，并在RedCap UE对应的寻呼时刻(paging occasion)将用于寻呼RedCap UE的paging消息发送给RedCap UE。
在集中式单元和分布式单元分离(CU-DU split)的场景中，可以通过F1接口消息来发送该指示，例如，网络设备可以包括集中式单元(CU)和分布式单元(DU)，该CU通过F1接口消息将指示发送到该DU。
根据第五方面的实施例，网络设备能够确定在哪个带宽或BWP或CORESET中发送由核心网针对减少能力的终端设备发送的paging消息。
第六方面的实施例
本申请第六方面的实施例提供一种收发信号的方法，应用于减少能力的终端设备(RedCap UE)，第六方面的实施例的收发信号的方法与第五方面的实施例的收发信号的方法对应。
图8是第六方面的实施例的收发信号的方法的一个示意图，如图8所示，该方法包括：
操作801、减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
操作802、从网络设备接收寻呼消息。
在本实施例中，减少能力的终端设备可能处于RRC_IDLE状态或RRC_INACTIVE状态。
在至少一个实施例中，操作802中的寻呼消息例如是核心网发送给网络设备(例如，gNB)，并由网络设备转发给RedCap UE的寻呼(paging)消息。
在操作802的实施方式1中，接收寻呼消息的带宽包括：非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始 下行BWP中的额外控制资源集合(additional CORESET)。
在操作802的实施方式1中，该减少能力的终端设备还可以根据对应的寻呼时刻(paging occasions，PO)，重新调节(retuning)射频(RF)到非减少能力的终端设备的初始下行BWP或CORESET#0或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)，以接收该寻呼消息。例如在RRC_IDLE或RRC_INACTIVE状态的RedCap UE驻留在为RedCap UE单独配置或定义的initial DL BWP中、且该initial DL BWP不包含完整的CORESET#0或者不包含完整的non-RedCap UE对应的initial DL BWP中用于paging消息的CORESET的情况下。
在操作802的实施方式2中，接收寻呼消息的带宽包括：非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)；以及为该减少能力的终端设备单独配置或定义的初始下行BWP或为该减少能力的终端设备单独配置或定义的控制资源集合(CORESET)。
在操作802的实施方式3中，接收寻呼消息的带宽包括：为该减少能力的终端设备单独配置或定义的初始下行BWP或为该减少能力的终端设备单独配置或定义的控制资源集合(CORESET)。
根据第六方面的实施例，终端设备能够确定在哪个带宽或BWP或CORESET中接收由核心网针对该减少能力的终端设备发送的paging消息。
第七方面的实施例
本申请实施例提供一种收发信号的装置，应用于减少能力的终端设备(Redcap UE)。
图9是第七方面的实施例中收发信号的装置的一个示意图，如图9所示，该收发信号的装置900包括第一收发单元901，第一收发单元901被配置为使得：
该减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
该减少能力的终端设备在随机接入完成之前，使用所述第一初始下行BWP接收信号。
关于收发信号的装置900的说明可以参考第一方面的实施例。
图10是第七方面的实施例中收发信号的装置的另一个示意图，如图10所示，该收发信号的装置1000包括第三收发单元1001，第三收发单元1001被配置为使得：
减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，所述一个带宽是至少一个候选带宽中的一者。
关于收发信号的装置1000的说明可以参考第三方面的实施例。
图11是第七方面的实施例中收发信号的装置的另一个示意图，如图11所示，该收发信号的装置1100包括第六收发单元1101，第六收发单元1101被配置为使得：
减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
从网络设备接收寻呼消息。
关于收发信号的装置1100的说明可以参考第六方面的实施例。
第八方面的实施例
本申请实施例提供一种收发信号的装置，应用于网络设备，例如，gNB。
图12是第八方面的实施例中收发信号的装置的一个示意图，如图12所示，该收发信号的装置1200包括第二收发单元1201，第二收发单元1201被配置为使得网络设备：
向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
在所述减少能力的终端设备随机接入完成之前，使用所述第一初始下行BWP向所述减少能力的终端设备发送信号。
关于收发信号的装置1200的说明可以参考第二方面的实施例。
图13是第八方面的实施例中收发信号的装置的另一个示意图，如图13所示，该收发信号的装置1300包括第四收发单元1301，第四收发单元1301被配置为使得网络设备：
向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP 是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
指示所述减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，所述一个带宽是至少一个候选带宽中的一者。
关于收发信号的装置1300的说明可以参考第四方面的实施例。
图14是第八方面的实施例中收发信号的装置的另一个示意图，如图14所示，该收发信号的装置1400包括第五收发单元1401，第五收发单元1401被配置为使得网络设备：
向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；
从核心网接收寻呼(paging)消息；以及
确定向所述减少能力的终端设备发送寻呼消息所使用的至少带宽。
关于收发信号的装置1400的说明可以参考第五方面的实施例。
第九方面的实施例
本申请实施例还提供一种通信系统，该通信系统可以包括减少能力的终端设备和网络设备。
图15是第九方面的实施例的终端设备的示意图。如图15所示，该终端设备1500可以包括处理器1510和存储器1520；存储器1520存储有数据和程序，并耦合到处理器1510。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。终端设备1500可以是减少能力的终端设备。
例如，处理器1510可以被配置为执行程序而实现如第一、三、六方面的实施例所述的方法。
如图15所示，该终端设备1500还可以包括：通信模块1530、输入单元1540、显示器1550、电源1560。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1500也并不是必须要包括图15中所示的所有部件，上述部件并不是必需的；此外，终端设备1500还可以包括图15中没有示出的部件，可以参考现有技术。
图16是第九方面的实施例的网络设备的示意图。如图16所示，网络设备1600可以包括：处理器1610(例如中央处理器CPU)和存储器1620；存储器1620耦合到处理器1610。其中该存储器1620可存储各种数据；此外还存储信息处理的程序1630，并且在处理器1610的控制下执行该程序1630。
例如，处理器1610可以被配置为执行程序而实现如第二方面、第四方面或第五方面的实施例所述的方法。
此外，如图16所示，网络设备1600还可以包括：收发机1640和天线1650等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1600也并不是必须要包括图16中所示的所有部件；此外，网络设备1600还可以包括图16中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端设备中执行所述程序时，所述程序使得所述终端设备执行第一、三、六方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得终端设备执行第一、三、六方面的实施例所述的方法。
本申请实施例还提供一种计算机程序，其中当在网络设备中执行所述程序时，所述程序使得所述网络设备执行第二、四、五方面的实施例所述的方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得网络设备执行第二、四、五方面的实施例所述的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM 存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
(第一组附记)
1.一种收发信号的方法，应用于减少能力的终端设备(Redcap UE)，所述方法包括：
所述减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
所述减少能力的终端设备在随机接入完成之前，使用所述第一初始下行BWP接收信号。
2.如附记1所述的方法，其中，
所述减少能力的终端设备在初始接入过程之前或随机接入过程之前，使用所述第一初始下行BWP接收信号。
3.如附记2所述的方法，其中，
所述减少能力的终端设备在初始接入过程之前或随机接入过程之前，驻留在所述第一初始下行BWP中。
4.如附记1所述的方法，其中，
所述减少能力的终端设备在初始接入过程中或随机接入过程中，使用所述第一初始下行BWP接收信号。
5.如附记2或附记4所述的方法，其中，
所述减少能力的终端设备在收到所述第一初始下行BWP的配置时或收到所述第一初始下行BWP的配置之后，使用所述第一初始下行BWP接收信号。
6.如附记4所述的方法，其中，
所述减少能力的终端设备在随机接入过程的初始化过程中或初始化过程之后，使用所述第一初始下行BWP接收信号。
7.如附记6所述的方法，其中，
所述减少能力的终端设备在第一初始上行BWP被使用时，使用所述第一初始下行BWP接收信号，
其中，所述第一初始上行BWP是为所述减少能力的终端设备单独配置或定义的初始上行BWP。
8.如附记6所述的方法，其中，
所述减少能力的终端设备的所述第一初始下行BWP具有预定的标识(BWP-id)。
9.如附记6所述的方法，其中，
所述减少能力的终端设备的所述第一初始下行BWP与第一初始上行BWP对应，
其中，所述第一初始上行BWP是为所述减少能力的终端设备单独配置或定义的初始上行BWP。
10.如附记5～10中的任一项所述的方法，其中，所述方法还包括：
所述减少能力的终端设备使用所述第一初始下行BWP接收额外的SSB。
11.如附记4所述的方法，其中，
所述减少能力的终端设备在随机接入资源选择过程中或随机接入资源选择过程之后，使用所述第一初始下行BWP接收信号。
12.如附记11所述的方法，其中，
在随机接入资源选择过程中，在所述减少能力的终端设备从小区定义的SSB中选择了SSB之后，使用所述第一初始下行BWP接收信号。
13.如附记4所述的方法，其中，
所述减少能力的终端设备在接收随机接入响应之前或者在接收随机接入响应时，使用所述第一初始下行BWP接收信号。
14.如附记13所述的方法，其中，
在接收随机接入响应之前，包括：
在发送了随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)后，
在接收随机接入响应时，包括：
在启动随机接入响应窗口(ra-ResponseWindow)时。
15.如附记5～14中任一项所述的方法，其中，
随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)指示所述减少能力的终端设备的类型。
16.如附记4所述的方法，其中，
在随机接入消息3(Msg3)被发送时或随机接入消息3(Msg3)被发送之后，使用所述第一初始下行BWP接收信号。
17.如附记16所述的方法，其中，
随机接入消息1(Msg1，preamble)、随机接入消息A(preamble+PUSCH)或随机接入消息3指示所述减少能力的终端设备的类型。
18.如附记1～17中任一项所述的方法，其中，
所述第一初始下行BWP与控制资源集合零(CORESET#0)部分重叠或者不重叠。
19.如附记1～18中任一项所述的方法，其中，
所述减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，所述一个带宽是至少一个候选带宽中的一者。
20.如附记19所述的方法，其中，
所述至少一个候选带宽包括：
控制资源集合0(CORESET#0)；
非减少能力的终端设备对应的初始下行BWP；以及
所述第一初始下行BWP或所述第一初始下行BWP中用于接收系统信息和/或寻呼和/或随机接入响应的控制资源集合(CORESET)。
21.如附记20所述的方法，其中，
所述减少能力的终端设备，在所述第一初始下行BWP或所述第一初始下行BWP用于接收系统信息和/或寻呼的控制资源集合(CORESET)中工作的情况下，
所述方法还包括：
所述减少能力的终端设备获得主信息块(MIB)；
获得系统信息块1(SIB1)；以及
在判断小区可以被选择的情况下，切换到所述第一初始下行BWP。
22.如附记20所述的方法，其中，
所述减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，
所述减少能力的终端设备使用所述至少一个候选带宽中的所述一个带宽，或者根据网络设备的指示信息确定所述一个带宽。
23.如附记22所述的方法，其中，
所述指示信息通过如下的信息或消息发送：
系统信息，无线资源控制释放/具有暂停指示的无线资源控制释放(RRC release/RRC release with suspend indication)消息，无线资源控制拒绝(RRC reject)消息或无线资源控制重配置(RRC reconfiguration)消息。
(第二组附记)
1.一种收发信号的方法，应用于网络设备，所述方法包括：
向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
在所述减少能力的终端设备随机接入完成之前，使用所述第一初始下行BWP向所述减少能力的终端设备发送信号。
2.如附记1所述的方法，其中，
向所述减少能力的终端设备发送的第一初始下行BWP的配置中包括：至少一个 控制资源集合(CORESET)的配置和/或至少一个公共搜索空间(CSS)的配置。
3.如附记2所述的方法，其中，
所述控制资源集合(CORESET)和/或所述公共搜索空间(CSS)用于所述减少能力的终端设备接收系统信息和/或寻呼和/或随机接入响应。
4.如附记1所述的方法，其中，
通过系统信息或RRC专用信令向所述减少能力的终端设备发送所述第一初始下行BWP的配置。
5.如附记1所述的方法，其中，
在所述减少能力的终端设备初始接入过程之前或随机接入过程之前，使用所述第一初始下行BWP发送信号。
6.如附记1所述的方法，其中，
在所述减少能力的终端设备的初始接入过程中或随机接入过程中，使用所述第一初始下行BWP发送信号。
7.如附记6所述的方法，其中，
在向所述减少能力的终端设备发送所述第一初始下行BWP的配置时或之后，使用所述第一初始下行BWP发送信号。
8.如附记6所述的方法，其中，
在所述减少能力的终端设备随机接入过程的初始化过程中或初始化过程之后，使用所述第一初始下行BWP发送信号。
9.如附记8所述的方法，其中，
在所述减少能力的终端设备的第一初始上行BWP被使用时，使用所述第一初始下行BWP发送信号，
其中，所述第一初始上行BWP是为所述减少能力的终端设备单独配置或定义的初始上行BWP。
10.如附记8所述的方法，其中，
所述减少能力的终端设备的所述第一初始下行BWP具有预定的标识(BWP-id)。
11.如附记8所述的方法，其中，
所述减少能力的终端设备的所述第一初始下行BWP与第一初始上行BWP对应，
其中，所述第一初始上行BWP是为所述减少能力的终端设备单独配置或定义的 初始上行BWP。
12.如附记7～11中的任一项所述的方法，其中，所述方法还包括：
使用所述第一初始下行BWP向所述减少能力的终端设备发送额外的SSB。
13.如附记6所述的方法，其中，
在所述减少能力的终端设备在随机接入资源选择过程中或随机接入资源选择过程之后，
使用所述第一初始下行BWP发送信号。
14.如附记13所述的方法，其中，
在随机接入资源选择过程中，在所述减少能力的终端设备从小区定义的SSB中选择了SSB之后，使用所述第一初始下行BWP发送信号。
15.如附记6所述的方法，其中，
在向所述减少能力的终端设备发送随机接入响应之前或者发送随机接入响应时，使用所述第一初始下行BWP发送信号。
16.如附记15所述的方法，其中，
在发送随机接入响应之前，包括：
在接收了随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)后，
在发送随机接入响应时，包括：
在所述减少能力的终端设备启动随机接入响应窗口(ra-ResponseWindow)时。
17.如附记7～16中任一项所述的方法，其中，
随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)指示所述减少能力的终端设备的类型。
18.如附记6所述的方法，其中，
在接收到随机接入消息3(Msg3)时或接收到随机接入消息3(Msg3)之后，使用所述第一初始下行BWP发送信号。
19.如附记18所述的方法，其中，
随机接入消息1(Msg1，preamble)、随机接入消息A(preamble+PUSCH)或随机接入消息3指示所述减少能力的终端设备的类型。
20.如附记1～19中的任一项所述的方法，其中，所述方法还包括：
指示所述减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，所述一个带宽是至少一个候选带宽中的一者。
21.如附记20所述的方法，其中，
所述至少一个候选带宽包括：
控制资源集合0(CORESET#0)；
非减少能力的终端设备对应的初始下行BWP；以及
所述第一初始下行BWP或所述第一初始下行BWP用于接收系统信息和/或寻呼和/或随机接入响应的控制资源集合(CORESET)。
22.如附记20所述的方法，其中，
所述指示信息通过如下的信息或消息发送：
系统信息，无线资源控制释放/具有暂停指示的无线资源控制释放(RRC release/RRC release with suspend indication)消息，无线资源控制拒绝(RRC reject)消息或无线资源控制重配置(RRC reconfiguration)消息。
(第三组附记)
1.一种收发信号的方法，应用于网络设备，所述方法包括：
向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；
从核心网接收寻呼(paging)消息；以及
确定向所述减少能力的终端设备发送寻呼消息所使用的至少带宽。
2.如附记1所述的方法，其中，
所述带宽包括：
非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)。
3.如附记1所述的方法，其中，
所述带宽包括：
非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)； 以及
为所述减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)。
4.如附记3所述的方法，其中，
在非减少能力的终端设备的初始下行BWP和减少能力的终端设备的初始下行BWP都包含控制资源集合0(CORESET#0)或用于寻呼的额外控制资源集合(CORESET)的情况下，
所述网络设备在控制资源集合0(CORESET#0)或用于寻呼的额外控制资源集合(CORESET)向所述减少能力的终端设备和非减少能力的终端设备发送寻呼消息。
5.如附记3所述的方法，其中，
在非减少能力的终端设备的初始下行BWP和减少能力的终端设备的初始下行BWP中的至少一者不包含控制资源集合0(CORESET#0)或用于寻呼的额外控制资源集合(CORESET)的情况下，
所述网络设备使用非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)，以及所述减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)，发送寻呼消息。
6.如附记1所述的方法，其中，
所述带宽包括：
为所述减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)。
7.如附记6所述的方法，其中，所述方法还包括：
所述网络设备使用所述减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)，发送用于所述减少能力的终端设备的寻呼消息。
8.如附记7所述的方法，其中，所述方法还包括：
从核心网接收指示，所述指示用于指示所述寻呼消息是否为用于所述减少能力的终端设备的寻呼消息。
9.如附记8所述的方法，其中，
寻呼RedCap UE的paging消息和寻呼non-RedCap UE的paging消息的接收时间不同，或者paging消息的结构不同或IE不同。
10.如附记8所述的方法，其中，
所述网络设备包括集中式单元(CU)和分布式单元(DU)，所述CU通过F1接口消息将所述指示发送到所述DU。
(第四组附记)
1.一种收发信号的方法，应用于减少能力的终端设备，所述方法包括：
所述减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
从网络设备接收寻呼消息。
2.如附记1所述的方法，其中，
接收寻呼消息的带宽包括：
非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)。
3.如附记2所述的方法，其中，
所述方法还包括：
所述减少能力的终端设备根据对应的寻呼时刻(paging occasions，PO)，重新调节(retuning)射频(RF)到非减少能力的终端设备的初始下行BWP或CORESET#0或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)，以接收所述寻呼消息。
4.如附记1所述的方法，其中，
接收寻呼消息的带宽包括：
非减少能力的终端设备的初始下行BWP，控制资源集合0(CORESET#0)或非减少能力的终端设备的初始下行BWP中的额外控制资源集合(additional CORESET)；以及
为所述减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)。
5.如附记1所述的方法，其中，
接收寻呼消息的带宽包括：
为所述减少能力的终端设备单独配置或定义的初始下行BWP或为所述减少能力的终端设备单独配置或定义的控制资源集合(CORESET)。

Claims (20)

  1. 一种收发信号的装置，应用于减少能力的终端设备(Redcap UE)，所述装置包括，第一收发单元，该第一收发单元被配置为使得：
    所述减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
    所述减少能力的终端设备在随机接入完成之前，使用所述第一初始下行BWP接收信号。
  2. 如权利要求1所述的装置，其中，
    所述减少能力的终端设备在初始接入过程之前或随机接入过程之前，使用所述第一初始下行BWP接收信号。
  3. 如权利要求2所述的装置，其中，
    所述减少能力的终端设备在收到所述第一初始下行BWP的配置时或收到所述第一初始下行BWP的配置之后，使用所述第一初始下行BWP接收信号。
  4. 如权利要求1所述的装置，其中，
    所述减少能力的终端设备在初始接入过程中或随机接入过程中，使用所述第一初始下行BWP接收信号。
  5. 如权利要求4所述的装置，其中，
    所述减少能力的终端设备在收到所述第一初始下行BWP的配置时或收到所述第一初始下行BWP的配置之后，使用所述第一初始下行BWP接收信号。
  6. 如权利要求4所述的装置，其中，
    所述减少能力的终端设备在随机接入过程的初始化过程中或初始化过程之后，使用所述第一初始下行BWP接收信号。
  7. 如权利要求6所述的装置，其中，
    所述减少能力的终端设备在第一初始上行BWP被使用时，使用所述第一初始下行BWP接收信号，
    其中，所述第一初始上行BWP是为所述减少能力的终端设备单独配置或定义的初始上行BWP。
  8. 如权利要求3所述的装置，其中，
    所述减少能力的终端设备在随机接入资源选择过程中或随机接入资源选择过程之后，使用所述第一初始下行BWP接收信号。
  9. 如权利要求8所述的装置，其中，
    在随机接入资源选择过程中，在所述减少能力的终端设备从小区定义的SSB中选择了SSB之后，使用所述第一初始下行BWP接收信号。
  10. 如权利要求3所述的装置，其中，
    所述减少能力的终端设备在接收随机接入响应之前或接收随机接入响应(RAR)时，使用所述第一初始下行BWP接收信号。
  11. 如权利要求10所述的装置，其中，
    在接收RAR之前，包括：
    在发送了随机接入消息1(Msg1，preamble)或随机接入消息A(preamble+PUSCH)后，或者在启动随机接入响应窗口(ra-ResponseWindow)时。
  12. 如权利要求3所述的装置，其中，
    在随机接入消息3(Msg3)被发送时或随机接入消息3(Msg3)被发送之后，使用所述第一初始下行BWP接收信号。
  13. 如权利要求1所述的装置，其中，
    所述第一初始下行BWP与控制资源集合零(CORESET#0)部分重叠或者不重叠。
  14. 一种收发信号的装置，应用于网络设备，所述装置包括，第二收发单元，该第二收发单元被配置为使得所述网络设备：
    向减少能力的终端设备发送第一初始下行BWP的配置，所述第一初始下行BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
    在所述减少能力的终端设备随机接入完成之前，使用所述第一初始下行BWP向所述减少能力的终端设备发送信号。
  15. 如权利要求14所述的装置，其中，
    向所述减少能力的终端设备发送的第一初始下行BWP的配置中包括：至少一个控制资源集合(CORESET)的配置和/或至少一个公共搜索空间(CSS)的配置。
  16. 一种收发信号的装置，应用于减少能力的终端设备(Redcap UE)，所述装置包括，第三收发单元，该第三收发单元被配置为使得：
    所述减少能力的终端设备得到第一初始下行BWP的配置，所述第一初始下行 BWP是为所述减少能力的终端设备单独配置或定义的初始下行BWP；以及
    所述减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，在一个带宽中工作，所述一个带宽是至少一个候选带宽中的一者。
  17. 如权利要求16所述的装置，其中，
    所述至少一个候选带宽包括：
    控制资源集合0(CORESET#0)；
    非减少能力的终端设备对应的初始下行BWP；以及
    所述第一初始下行BWP或所述第一初始下行BWP中用于接收系统信息和/或寻呼和/或随机接入响应的控制资源集合(CORESET)。
  18. 如权利要求17所述的装置，其中，
    所述减少能力的终端设备，在所述第一初始下行BWP或所述第一初始下行BWP用于接收系统信息和/或寻呼的控制资源集合(CORESET)中工作的情况下，
    所述装置还包括：
    所述减少能力的终端设备获得主信息块(MIB)；
    获得系统信息块1(SIB1)；以及
    在判断小区可以被选择的情况下，切换到所述第一初始下行BWP。
  19. 如权利要求16所述的装置，其中，
    所述减少能力的终端设备在处于空闲(idle)状态、未激活(inactive)状态、或者在无线资源控制(RRC)连接重建的随机接入过程之前，
    所述减少能力的终端设备使用所述至少一个候选带宽中的所述一个带宽，或者根据网络设备的指示信息确定所述一个带宽。
  20. 如权利要求19所述的装置，其中，
    所述指示信息通过如下的信息或消息发送：
    系统信息，无线资源控制释放/具有暂停指示的无线资源控制释放(RRC release/RRC release with suspend indication)消息，无线资源控制拒绝(RRC reject)消息或无线资源控制重配置(RRC reconfiguration)消息。
PCT/CN2021/110680 2021-08-04 2021-08-04 收发信号的方法、装置和通信系统 Ceased WO2023010362A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2024506564A JP7850796B2 (ja) 2021-08-04 2021-08-04 信号送受信の方法と装置及び通信システム
CN202180101190.4A CN117813883A (zh) 2021-08-04 2021-08-04 收发信号的方法、装置和通信系统
PCT/CN2021/110680 WO2023010362A1 (zh) 2021-08-04 2021-08-04 收发信号的方法、装置和通信系统
US18/430,057 US20240224338A1 (en) 2021-08-04 2024-02-01 Method and apparatus for transreceiving signal, and communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/110680 WO2023010362A1 (zh) 2021-08-04 2021-08-04 收发信号的方法、装置和通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/430,057 Continuation US20240224338A1 (en) 2021-08-04 2024-02-01 Method and apparatus for transreceiving signal, and communication system

Publications (1)

Publication Number Publication Date
WO2023010362A1 true WO2023010362A1 (zh) 2023-02-09

Family

ID=85154936

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/110680 Ceased WO2023010362A1 (zh) 2021-08-04 2021-08-04 收发信号的方法、装置和通信系统

Country Status (4)

Country Link
US (1) US20240224338A1 (zh)
JP (1) JP7850796B2 (zh)
CN (1) CN117813883A (zh)
WO (1) WO2023010362A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116156599A (zh) * 2023-04-18 2023-05-23 翱捷科技股份有限公司 一种RedCap终端接入5G小区的方法及装置
WO2024169819A1 (zh) * 2023-02-17 2024-08-22 维沃移动通信有限公司 配置方法、装置、设备及可读存储介质
WO2025097983A1 (zh) * 2023-11-07 2025-05-15 华为技术有限公司 一种通信方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240388999A1 (en) * 2021-09-17 2024-11-21 Beijing Xiaomi Mobile Software Co., Ltd. System information transmission method and apparatus
WO2023097682A1 (en) * 2021-12-03 2023-06-08 Qualcomm Incorporated Synchronization for rach and sdt in ssb-less dl bwp
US20230224130A1 (en) * 2022-01-07 2023-07-13 Qualcomm Incorporated Control resource set type configurations
US12363656B2 (en) * 2022-04-29 2025-07-15 Qualcomm Incorporated Techniques for configuring bandwidth parts and synchronization signal blocks

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111567126A (zh) * 2020-04-08 2020-08-21 北京小米移动软件有限公司 配置信息传输方法及装置、通信设备及存储介质
CN111757393A (zh) * 2018-03-30 2020-10-09 Oppo广东移动通信有限公司 用于随机接入的方法和设备
US20210037573A1 (en) * 2019-07-31 2021-02-04 Qualcomm Incorporated Two-step rach procedure for nr reduced capability ue
CN113170475A (zh) * 2021-03-17 2021-07-23 北京小米移动软件有限公司 一种带宽部分配置方法、带宽部分配置装置及存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7001307B2 (ja) * 2017-06-22 2022-01-19 ホアウェイ・テクノロジーズ・カンパニー・リミテッド 通信方法、端末デバイス、ネットワークデバイス、プログラム、および通信システム
WO2021146998A1 (zh) * 2020-01-22 2021-07-29 华为技术有限公司 一种确定初始带宽部分bwp的方法、装置及存储介质
CN115604830A (zh) * 2021-07-09 2023-01-13 维沃移动通信有限公司（Cn） 初始带宽部分配置的获取方法、终端及网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757393A (zh) * 2018-03-30 2020-10-09 Oppo广东移动通信有限公司 用于随机接入的方法和设备
US20210037573A1 (en) * 2019-07-31 2021-02-04 Qualcomm Incorporated Two-step rach procedure for nr reduced capability ue
CN111567126A (zh) * 2020-04-08 2020-08-21 北京小米移动软件有限公司 配置信息传输方法及装置、通信设备及存储介质
CN113170475A (zh) * 2021-03-17 2021-07-23 北京小米移动软件有限公司 一种带宽部分配置方法、带宽部分配置装置及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Addressing ENs on SMF obtaining DNS information from AF", 3GPP DRAFT; S2-2102493, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20210412 - 20210416, 6 April 2021 (2021-04-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051993869 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024169819A1 (zh) * 2023-02-17 2024-08-22 维沃移动通信有限公司 配置方法、装置、设备及可读存储介质
CN116156599A (zh) * 2023-04-18 2023-05-23 翱捷科技股份有限公司 一种RedCap终端接入5G小区的方法及装置
CN116156599B (zh) * 2023-04-18 2023-08-01 翱捷科技股份有限公司 一种RedCap终端接入5G小区的方法及装置
WO2025097983A1 (zh) * 2023-11-07 2025-05-15 华为技术有限公司 一种通信方法及装置

Also Published As

Publication number Publication date
JP7850796B2 (ja) 2026-04-23
US20240224338A1 (en) 2024-07-04
JP2024528187A (ja) 2024-07-26
CN117813883A (zh) 2024-04-02

Similar Documents

Publication Publication Date Title
US11039368B2 (en) Dynamic coverage mode switching and communication bandwidth adjustment
US11582661B2 (en) Terminal measurement method and apparatus, and terminal
EP4277399A1 (en) Ue capability information processing method and apparatus, device, and storage medium
US10973076B2 (en) Fast switching between control channels during radio resource control connection
EP3583728B1 (en) Methods and apparatus for associating carriers in a wireless communication network
WO2023010362A1 (zh) 收发信号的方法、装置和通信系统
CN113133032A (zh) 无线通信方法、终端设备和网络设备
US12550054B2 (en) Mobility for small data transmission procedure
WO2023010368A1 (zh) 收发信号的方法、装置和通信系统
WO2019096213A1 (en) Methods and devices for load balancing across band-width parts
WO2025166634A1 (zh) 信息接收方法和信息发送方法、装置及通信系统
WO2024026898A1 (zh) 信息处理方法、信息收发方法和装置
WO2023124823A1 (zh) 一种通信方法及装置
WO2024026897A1 (zh) 信息处理方法、信息发送方法和装置
WO2026044728A1 (zh) 信息传输方法、终端设备、第一网络设备和第二网络设备
WO2025152118A1 (zh) 数据发送方法、接收方法、装置及通信系统
WO2025065634A1 (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: 21952262

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2024506564

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202180101190.4

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21952262

Country of ref document: EP

Kind code of ref document: A1