WO2022151052A1 - 一种随机接入参数配置方法、装置及存储介质 - Google Patents

一种随机接入参数配置方法、装置及存储介质 Download PDF

Info

Publication number
WO2022151052A1
WO2022151052A1 PCT/CN2021/071506 CN2021071506W WO2022151052A1 WO 2022151052 A1 WO2022151052 A1 WO 2022151052A1 CN 2021071506 W CN2021071506 W CN 2021071506W WO 2022151052 A1 WO2022151052 A1 WO 2022151052A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
control channel
uplink control
physical uplink
type
Prior art date
Application number
PCT/CN2021/071506
Other languages
English (en)
French (fr)
Inventor
牟勤
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to US18/260,968 priority Critical patent/US20240057171A1/en
Priority to CN202180000224.0A priority patent/CN115088375A/zh
Priority to EP21918268.0A priority patent/EP4280785A1/en
Priority to JP2023541699A priority patent/JP2024505394A/ja
Priority to KR1020237026201A priority patent/KR20230125831A/ko
Priority to PCT/CN2021/071506 priority patent/WO2022151052A1/zh
Publication of WO2022151052A1 publication Critical patent/WO2022151052A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • H04W74/0833Random access procedures, e.g. with 4-step access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency
    • H04L5/0007Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/0012Hopping in multicarrier systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signaling for the administration of the divided path
    • H04L5/0094Indication of how sub-channels of the path are allocated
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/21Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/002Transmission of channel access control information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055Physical resource allocation for ACK/NACK
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a random access parameter configuration method, device, and storage medium.
  • Redcap terminals With the introduction of Redcap terminals, the capabilities of terminals have been differentiated. For example, compared with normal terminals (normal UEs), Redcap terminals have limited transmission and reception bandwidth. Therefore, the existing random access parameter configuration methods cannot meet the needs of differentiated terminals. need.
  • the present disclosure provides a random access parameter configuration method, device and storage medium.
  • a random access parameter configuration method which is applied to a network device.
  • the random access parameter configuration method includes: determining a physical uplink control channel configuration parameter, the physical uplink control channel configuration
  • the parameters include configuration parameters for the automatic mixed retransmission request feedback of message 4 in the random access process for terminals of the first type and terminals of the second type, where the capabilities of the terminals of the first type and the terminals of the second type are different.
  • the physical uplink control channel configuration parameters include a first physical uplink control channel configuration parameter and a second physical uplink control channel configuration parameter; the first physical uplink control channel configuration parameter and the second physical uplink At least part of the control channel configuration parameters are different; the first physical uplink control channel configuration parameter corresponds to the first type of terminal, and the second physical uplink control channel configuration parameter corresponds to the second type of terminal.
  • the first physical uplink control channel configuration parameter and the second physical uplink control channel configuration parameter are different in at least one of the following parameters:
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal;
  • the first physical uplink control channel configuration parameters include configuration parameters that support frequency hopping, and the second physical uplink control channel configuration parameters include configuration parameters that do not support frequency hopping; and/or the first physical uplink control channel
  • the frequency hopping width configured in the configuration parameter is larger than the frequency hopping width configured in the second physical uplink control channel configuration parameter.
  • the physical uplink control channel configuration parameters include physical uplink control channel configuration parameters shared by the first type of terminal and the second type of terminal.
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal;
  • the physical uplink control channel configuration parameters include one or a combination of the following parameters:
  • the physical uplink control channel does not support frequency hopping; the physical uplink control channel supports frequency hopping, and the frequency hopping width is within the bandwidth range supported by the second type of terminal.
  • the random access parameter configuration method further includes: sending the physical uplink control channel configuration parameter.
  • the physical uplink control channel configuration parameter is carried in the remaining minimum system message RMSI.
  • the random access parameter configuration method further includes:
  • the terminal capability indicates that the terminal is a first-type terminal or a second-type terminal; according to the terminal capability, determine the resource for the terminal to perform message 4 automatic mixed retransmission request feedback.
  • a random access parameter configuration method which is applied to a terminal.
  • the random access parameter configuration method includes: determining a physical uplink control channel configuration parameter, where the physical uplink control channel configuration parameter includes Regarding the configuration parameters that the first type terminal and the second type terminal perform the automatic mixed retransmission request feedback of message 4 in the random access process, the capabilities of the first type terminal and the second type terminal are different; according to the physical The uplink control channel configuration parameter determines the resources for the automatic mixed retransmission request feedback of message 4 in the random access process.
  • the determining the physical uplink control channel configuration parameters includes:
  • the physical uplink control channel configuration parameters include first physical uplink control channel configuration parameters and second physical uplink control channel configuration parameters; the first physical uplink control channel configuration parameters and the second physical uplink control channel configuration parameters at least part of the parameters different; the first physical uplink control channel configuration parameter corresponds to the first type of terminal, and the second physical uplink control channel configuration parameter corresponds to the second type of terminal.
  • At least one of the following parameters of the first physical uplink control channel configuration parameter and the second physical uplink control channel configuration parameter is different from at least one of the following parameters:
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal;
  • the first physical uplink control channel configuration parameters include configuration parameters that support frequency hopping, and the second physical uplink control channel configuration parameters include configuration parameters that do not support frequency hopping; and/or the first physical uplink control channel
  • the frequency hopping width configured in the configuration parameter is larger than the frequency hopping width configured in the second physical uplink control channel configuration parameter.
  • the physical uplink control channel configuration parameters include physical uplink control channel configuration parameters shared by the first type of terminal and the second type of terminal.
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal;
  • the physical uplink control channel configuration parameters include one or a combination of the following parameters: the physical uplink control channel does not support frequency hopping; the physical uplink control channel supports frequency hopping, and the frequency hopping width is within the bandwidth range supported by the second type of terminal .
  • the determining the physical uplink control channel configuration parameters includes:
  • the physical uplink control channel configuration parameter is carried in the remaining minimum system message RMSI.
  • the random access parameter configuration method further includes: reporting a terminal capability of the terminal, where the terminal capability indicates that the terminal type is a first type terminal or a second type terminal.
  • an apparatus for configuring random access parameters characterized in that, when applied to network equipment, the apparatus for configuring random access parameters includes:
  • the processing unit is configured to determine a physical uplink control channel configuration parameter, the physical uplink control channel configuration parameter includes a configuration for the first type terminal and the second type terminal to perform message 4 automatic hybrid retransmission request feedback in the random access process parameter, the capabilities of the terminal of the first type and the terminal of the second type are different.
  • the physical uplink control channel configuration parameters include a first physical uplink control channel configuration parameter and a second physical uplink control channel configuration parameter; the first physical uplink control channel configuration parameter and the second physical uplink At least part of the control channel configuration parameters are different; the first physical uplink control channel configuration parameter corresponds to the first type of terminal, and the second physical uplink control channel configuration parameter corresponds to the second type of terminal.
  • the physical uplink control channel configuration parameters include physical uplink control channel configuration parameters shared by the first type of terminal and the second type of terminal.
  • At least one of the following parameters of the first physical uplink control channel configuration parameter and the second physical uplink control channel configuration parameter is different from at least one of the following parameters:
  • the first physical uplink control channel configuration parameters include configuration parameters that support frequency hopping, and the second physical uplink control channel configuration parameters include configuration parameters that do not support frequency hopping; and/or the first physical uplink control channel
  • the frequency hopping width configured in the configuration parameter is larger than the frequency hopping width configured in the second physical uplink control channel configuration parameter.
  • the physical uplink control channel configuration parameters include physical uplink control channel configuration parameters shared by the first type of terminal and the second type of terminal.
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal;
  • the physical uplink control channel configuration parameters include one or a combination of the following parameters:
  • the physical uplink control channel does not support frequency hopping; the physical uplink control channel supports frequency hopping, and the frequency hopping width is within the bandwidth range supported by the second type of terminal.
  • the random access parameter configuration apparatus further includes: a sending unit configured to send the physical uplink control channel configuration parameter.
  • the physical uplink control channel configuration parameter is carried in the remaining minimum system message RMSI.
  • the random access parameter configuration apparatus further includes a receiving unit, and the receiving unit is configured to: receive the terminal capability reported by the terminal, where the terminal capability indicates that the terminal is a first type terminal or a second type terminal. Type of terminal; the processing unit is configured to determine, according to the capabilities of the terminal, the resources for the terminal to feed back the message 4 automatic hybrid retransmission request.
  • an apparatus for configuring random access parameters which is applied to a terminal
  • the apparatus for configuring random access parameters includes: a processing unit configured to determine physical uplink control channel configuration parameters,
  • the physical uplink control channel configuration parameter determines the resources for the automatic mixed retransmission request feedback of message 4 in the random access process, and the physical uplink control channel configuration parameter includes the first type terminal and the second type terminal in the random access process.
  • the configuration parameters of the automatic mixed retransmission request feedback of message 4 are performed, and the capabilities of the first type terminal and the second type terminal are different.
  • the processing unit is configured to determine the physical uplink control channel configuration parameter in the following manner: determine a terminal type, where the terminal type is a first type terminal or a second type terminal, the first type terminal and The capabilities of the second type of terminals are different; a physical uplink control channel configuration parameter is determined according to the terminal type; the physical uplink control channel configuration parameter includes a first physical uplink control channel configuration parameter and a second physical uplink control channel configuration parameter; The first physical uplink control channel configuration parameter and the second physical uplink control channel configuration parameter are at least partially different; the first physical uplink control channel configuration parameter corresponds to the first type of terminal, and the second physical uplink The control channel configuration parameter corresponds to the second type of terminal.
  • At least one of the following parameters of the first physical uplink control channel configuration parameter and the second physical uplink control channel configuration parameter is different from at least one of the following parameters:
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal;
  • the first physical uplink control channel configuration parameters include configuration parameters that support frequency hopping, and the second physical uplink control channel configuration parameters include configuration parameters that do not support frequency hopping; and/or the first physical uplink control channel
  • the frequency hopping width configured in the configuration parameter is larger than the frequency hopping width configured in the second physical uplink control channel configuration parameter.
  • the physical uplink control channel configuration parameters include physical uplink control channel configuration parameters shared by the first type of terminal and the second type of terminal.
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal;
  • the physical uplink control channel configuration parameters include one or a combination of the following parameters: the physical uplink control channel does not support frequency hopping; the physical uplink control channel supports frequency hopping, and the frequency hopping width is within the bandwidth range supported by the second type of terminal .
  • the random access parameter configuration apparatus further includes a receiving unit, and the receiving unit is configured to receive the physical uplink control channel configuration parameters sent by the network device.
  • the processing unit is configured to determine the physical uplink control channel configuration parameter based on the physical uplink control channel configuration parameter received by the receiving unit.
  • the physical uplink control channel configuration parameter is carried in the remaining minimum system message RMSI.
  • the random access parameter configuration apparatus further includes a sending unit, the sending unit is configured to report the terminal capability of the terminal, and the terminal capability indicates that the terminal type is the first type terminal or the first type terminal. Two types of terminals.
  • an apparatus for configuring random access parameters including:
  • processor ; memory for storing processor-executable instructions;
  • the processor is configured to: execute the first aspect or the random access parameter configuration method described in any implementation manner of the first aspect.
  • an apparatus for configuring random access parameters including:
  • processor ; memory for storing processor-executable instructions;
  • the processor is configured to: execute the second aspect or the random access parameter configuration method described in any implementation manner of the second aspect.
  • a non-transitory computer-readable storage medium when instructions in the storage medium are executed by a processor of a network device, the network device can execute the first aspect or the first aspect The random access parameter configuration method described in any one of the embodiments.
  • a non-transitory computer-readable storage medium which enables the mobile terminal to execute the second aspect or the second aspect when instructions in the storage medium are executed by a processor of a mobile terminal.
  • the technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects: by determining that the first-type terminal and the second-type terminal with different capabilities perform physical uplink control of message 4 automatic hybrid retransmission request feedback capability in the random access process
  • the channel configuration parameters can realize the configuration of physical uplink control channel configuration parameters for terminals with different capabilities, so as to meet the communication capabilities of terminals with different capabilities.
  • FIG. 1 is a schematic diagram of a wireless communication system according to an exemplary embodiment.
  • FIG. 2 shows a schematic diagram of a frequency hopping range beyond the receiving frequency band range of a Redcap terminal.
  • Fig. 3 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • Fig. 4 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • FIG. 5 shows a schematic diagram of configuring PUCCH configuration parameters with different frequency hopping widths for a normal UE and a Redcap terminal, respectively, according to an exemplary embodiment of the present disclosure.
  • Fig. 6 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • Fig. 7 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • Fig. 8 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • Fig. 9 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • Fig. 10 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • Fig. 11 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • Fig. 12 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment.
  • Fig. 13 is a block diagram of an apparatus for configuring random access parameters according to an exemplary embodiment.
  • Fig. 14 is a block diagram of an apparatus for configuring random access parameters according to an exemplary embodiment.
  • Fig. 15 is a block diagram of an apparatus for configuring random access parameters according to an exemplary embodiment.
  • Fig. 16 is a block diagram of an apparatus for configuring random access parameters according to an exemplary embodiment.
  • the wireless communication system includes a terminal and a network device. Information is sent and received between the terminal and the network device through wireless resources.
  • the wireless communication system shown in FIG. 1 is only a schematic illustration, and the wireless communication system may further include other network devices, for example, may also include core network devices, wireless relay devices, and wireless backhaul devices, etc. Not shown in Figure 1.
  • the embodiments of the present disclosure do not limit the number of network devices and the number of terminals included in the wireless communication system.
  • the wireless communication system is a network that provides a wireless communication function.
  • Wireless communication systems can use different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division multiple access (TDMA) , frequency division multiple access (frequency division multiple access, FDMA), orthogonal frequency division multiple access (orthogonal frequency-division multiple access, OFDMA), single carrier frequency division multiple access (single Carrier FDMA, SC-FDMA), carrier sense Carrier Sense Multiple Access with Collision Avoidance.
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • single carrier frequency division multiple access single Carrier FDMA, SC-FDMA
  • carrier sense Carrier Sense Multiple Access with Collision Avoidance CDMA
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal
  • the network can be divided into 2G (English: generation) network, 3G network, 4G network or future evolution network, such as 5G network, 5G network can also be called a new wireless network ( New Radio, NR).
  • 2G International: generation
  • 3G network 4G network or future evolution network, such as 5G network
  • 5G network can also be called a new wireless network ( New Radio, NR).
  • New Radio New Radio
  • the present disclosure will sometimes refer to a wireless communication network simply as a network.
  • the wireless access network device may be: a base station, an evolved node B (base station), a home base station, an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay A node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc., can also be a gNB in an NR system, or can also be a component or part of a device that constitutes a base station Wait.
  • the network device may also be an in-vehicle device.
  • V2X vehicle-to-everything
  • the terminal involved in the present disclosure may also be referred to as terminal equipment, user equipment (User Equipment, UE), mobile station (Mobile Station, MS), mobile terminal (Mobile Terminal, MT), etc.
  • a device that provides voice and/or data connectivity for example, a terminal may be a handheld device with wireless connectivity, a vehicle-mounted device, or the like.
  • some examples of terminals are: Smartphone (Mobile Phone), Pocket Personal Computer (PPC), PDA, Personal Digital Assistant (PDA), notebook computer, tablet computer, wearable device, or Vehicle equipment, etc.
  • the terminal device may also be an in-vehicle device. It should be understood that the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal.
  • the terminal involved in the embodiments of the present disclosure can be understood as a new type of terminal designed in 5G NR: Reduced capability UE or simply referred to as NR-lite or Redcap terminal.
  • the new terminal is referred to as a Redcap terminal.
  • Redcap terminals Similar to the Internet of Things (IoT) devices in Long Term Evolution (LTE), Redcap terminals usually need to meet the following requirements:
  • the sending and receiving bandwidth of the Redcap terminal matches the capability of the terminal. Compared with the normal UE, the sending and receiving bandwidth is limited. For example, the maximum bandwidth (max UE BW) during the initial access phase is limited. Typically, the bandwidth in frequency band 1 (FR1) is 20MHz, and the bandwidth in FR2 is 40MHz.
  • the configuration of the physical uplink control channel (PUCCH) needs to be performed in the initial access phase, for example, the configuration of bearer message 4 (Msg.4) in the random access channel (Random Access Channel, RACH) configuration phase PUCCH format (format) of Hybrid Automatic Repeat Request (HARQ).
  • the PUCCH formats that carry Msg.4HARQ feedback are PUCCH format 0 and PUCCH format 1.
  • format 0 is a short PUCCH (short PUCCH), does not support frequency hopping (frequency hopping, FH) of an intra-slot, and its length can be 1-2 OFDM symbols (OFDM symbol).
  • Format1 is long PUCCH (long PUCCH), supports FH, and its length can be 4-14 OFDM symbols.
  • the network device when configuring the PUCCH, the network device usually broadcasts the configuration parameters of the PUCCH in a broadcast manner. For example, in the System Information Block (SIB), the network device will broadcast the configuration parameters of the secondary PUCCH, including the format, physical resource block (Physical Resource Block, PRB) location, whether to support frequency hopping, etc.
  • SIB System Information Block
  • the PUCCH configuration parameters broadcast by the network device may not meet the Redcap terminal capabilities. For example, when the Redcap terminal shares the uplink BWP (UL BWP) with the normal UE, if the PUCCH configuration parameters include using intra-slot frequency hopping for Msg.4HARQ, the frequency hopping range at this time may exceed the receiving frequency band range of the Redcap terminal.
  • UL BWP uplink BWP
  • Figure 2 shows a schematic diagram of a frequency hopping range beyond the receiving frequency band of a Redcap terminal.
  • both the Redcap terminal and the normal UE received the intra-slot frequency hopping range broadcast by the terminal on the UL BWP shared at the initial stage.
  • the intra-slot frequency hopping range exceeds the receiving bandwidth range of the Redcap terminal and cannot meet the The capability of the Redcap terminal to Msg.4 HARQ during random access.
  • the embodiment of the present disclosure provides a random access parameter configuration method.
  • the configuration parameters of the PUCCH are enhanced, so that the configuration parameters of the PUCCH can meet the terminal capabilities of the Redcap terminal.
  • the PUCCH configuration parameters in the initial UL BWP are configured to meet the capability of terminals with different types of terminal capabilities to perform Msg.4 HARQ in the random access process.
  • any two different types of terminals among different types of terminals are referred to as a first type terminal and a second type terminal.
  • the capabilities of the first type of terminal and the second type of terminal are different.
  • the first type of terminal may be a normal UE, and the second type of terminal may be a Redcap terminal.
  • the configuration parameters of the PUCCH are configured, and the configuration parameters of the PUCCH satisfy the capability of the first type terminal and the second type terminal to perform Msg.4 HARQ in the random access process, and the capability of the first type terminal and the second type terminal. different.
  • Fig. 3 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment. As shown in Fig. 3 , the method for configuring random access parameters is used in a network device, and includes the following steps.
  • step S11 the configuration parameters of the PUCCH are determined.
  • the PUCCH configuration parameters determined by the network device include configuration parameters for performing Msg.4 HARQ in the random access process for the first type terminal and the second type terminal.
  • the configuration parameters determined by the network device to perform Msg.4 HARQ in the random access process for the first type terminal and the second type terminal meet the requirements of the first type terminal and the second type terminal in the random access process. Capability to perform Msg.4 HARQ.
  • the capabilities of the first type of terminal are different from the capabilities of the second type of terminal.
  • the terminal of the first type and the terminal of the second type may have different capabilities.
  • the capabilities of the terminal may include at least one of: transmission bandwidth (eg, receive bandwidth and/or transmit bandwidth), number of transmit antennas (eg, receive antennas and/or transmit antennas), maximum number of bits in a transport block, and processing time delay Wait.
  • the different capabilities of the terminals may be one or more of the transceiving bandwidth, the number of transceiving antennas, the maximum number of bits of the transport block, and the processing time delay.
  • different PUCCH configuration parameters may be configured for terminals with different capabilities, so as to satisfy the capability of the first type terminal and the second type terminal to perform Msg.4 HARQ in the random access process.
  • the first PUCCH configuration parameter is configured for the first type terminal
  • the second PUCCH configuration parameter is configured for the second type terminal.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are different at least in some parameters or all parameters are different.
  • Fig. 4 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment. As shown in Fig. 4 , the method for configuring random access parameters is used in a network device and includes the following steps.
  • step S21 the first PUCCH configuration parameter and the second PUCCH configuration parameter are determined.
  • the configured PUCCH parameters include a first PUCCH configuration parameter and a second PUCCH configuration parameter.
  • the first PUCCH configuration parameter corresponds to the first type of terminal
  • the second PUCCH parameter corresponds to the second type of terminal.
  • the first PUCCH configuration parameter corresponding to the first type of terminal may be understood as the first PUCCH configuration parameter that satisfies the capability of the first type of terminal to perform Msg.4 HARQ in the random access process, or may also be understood as the first PUCCH configuration parameter Including the configuration of the PUCCH for carrying the Msg.4 HARQ feedback during the random access process of the first type terminal.
  • the second PUCCH configuration parameter corresponding to the second type of terminal can be understood as the second PUCCH configuration parameter that satisfies the capability of the second type of terminal to perform Msg.4 HARQ in the random access process, or it can also be understood as the second PUCCH configuration parameter Including the configuration of the PUCCH for carrying the Msg.4 HARQ feedback during the random access process of the second type terminal.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are at least partially different.
  • the configuration related to the first PUCCH and the configuration of the second PUCCH are included in the initial UL BWP.
  • the PUCCH configuration includes the configuration of the PUCCH that is fed back to Msg.4 HARQ in the process of carrying the random access.
  • the configuration of the first PUCCH is different from the configuration of the second PUCCH.
  • the configuration of the first PUCCH is used by the terminal of the first type, and the configuration of the second PUCCH is used by the terminal of the second type.
  • the terminal capabilities of the first type terminal and the second type terminal are different.
  • the terminal capability includes the transmission and reception bandwidth of the terminal.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are at least partially different, and may include at least one of the following parameters: different PRBs where the PUCCH is located, different PUCCH formats, Whether the frequency hopping is supported is different, the PRB positions that the PUCCH supports frequency hopping are different, and the frequency hopping width of the PUCCH supporting frequency hopping is different.
  • the capability of the first type terminal is stronger than that of the second type terminal.
  • the first type terminal may be a normal UE, and the second type terminal may be Redcap terminal.
  • the transmission and reception bandwidth supported by the UE is greater than the transmission and reception bandwidth supported by the Redcap terminal.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are at least partially different, for example, the first PUCCH configuration parameter may include a configuration parameter that supports frequency hopping, and the second PUCCH configuration parameter includes a configuration parameter that does not support frequency hopping; and/ Or the frequency hopping width configured in the first PUCCH configuration parameter is larger than the frequency hopping width configured in the second PUCCH configuration parameter.
  • FIG. 5 shows a schematic diagram of configuring PUCCH configuration parameters with different frequency hopping widths for a normal UE and a Redcap terminal, respectively, according to an exemplary embodiment of the present disclosure.
  • the frequency hopping width configured in the first PUCCH configuration parameter used by the normal UE is greater than the frequency hopping width configured in the second PUCCH configuration parameter used by the Redcap terminal.
  • the frequency hopping width configured in the first PUCCH configuration parameter matches the transmission and reception bandwidth of the normal UE, and the frequency hopping will not exceed the transmission and reception bandwidth of the normal UE.
  • the frequency hopping width configured in the second PUCCH configuration parameter matches the sending and receiving bandwidth of the Redcap terminal, and the frequency hopping will not exceed the sending and receiving bandwidth of the Redcap terminal.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter respectively satisfy the capability of the first type terminal and the second type terminal to perform Msg.4 HARQ in the random access process.
  • PUCCH configuration parameters of terminals meeting different capabilities may be configured to meet the capabilities of the first type terminal and the second type terminal to perform Msg.4 HARQ in the random access process. That is, the configured PUCCH configuration parameters include PUCCH configuration parameters shared by the terminals of the first type and the terminals of the second type.
  • Fig. 6 is a flowchart of a random access parameter configuration method according to an exemplary embodiment. As shown in Fig. 6 , the random access parameter configuration method is used in a network device, and includes the following steps.
  • step S31 a PUCCH configuration parameter shared by the first type terminal and the second type terminal is configured.
  • the capability of the first type terminal is stronger than that of the second type terminal.
  • the first type terminal may be a normal UE, and the second type terminal may be a Redcap terminal.
  • the PUCCH configuration parameters shared by the first type terminal and the second type terminal may include at least the following parameters or a combination of multiple parameters: PUCCH does not support frequency hopping; or PUCCH supports frequency hopping, and the frequency hopping width is within the bandwidth supported by the second type terminal within the range.
  • the PUCCH configuration parameters shared by the terminals of the first type and the terminals of the second type satisfy the capabilities of the terminals of the second type, that is, the capabilities of the terminals of the first type and the terminals of the second type are simultaneously satisfied.
  • the network device configures one set of PUCCH configuration parameters to satisfy the capability of the first type terminal and the second type terminal to perform Msg.4 HARQ in the random access process.
  • the configured PUCCH does not use frequency hopping, or the configured PUCCH frequency hopping width is within the capability range of the second type of terminal; at this time, the first type of terminal and the second type of terminal share the same PUCCH configuration.
  • the network device after the network device determines the PUCCH configuration parameters that satisfy the Msg.4 HARQ capability of the first type terminal and the second type terminal in the random access process, it can send the determined PUCCH configuration parameters to the terminal, and the terminal can send the determined PUCCH configuration parameters to the terminal based on the
  • the terminal type determines the corresponding PUCCH configuration, and determines specific PUCCH resources according to the PUCCH configuration.
  • the terminal transmits the HARQ of Msg.4 on the determined PUCCH resource.
  • Fig. 7 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment. As shown in Fig. 7 , the method for configuring random access parameters is used in a network device, and includes the following steps.
  • step S41 the configuration parameters of the PUCCH are determined.
  • the PUCCH configuration parameters include configuration parameters for performing Msg.4 HARQ in the random access process for the first type terminal and the second type terminal.
  • the configuration parameters for the first type terminal and the second type terminal to perform Msg.4HARQ in the random access process meet the requirements for the first type terminal and the second type terminal to perform Msg.4HARQ in the random access process.
  • capabilities, the capabilities of the first type of terminals and the capabilities of the second type of terminals are different.
  • the configuration parameters of the PUCCH may include configuration parameters of the first PUCCH and configuration parameters of the second PUCCH.
  • the configuration parameters of the PUCCH may include PUCCH configuration parameters shared by the terminals of the first type and the terminals of the second type.
  • step S42 the configuration parameters of the PUCCH are sent.
  • the configuration parameter of the PUCCH sent by the network device may be sent by broadcasting.
  • the network device may carry the configuration parameters of the PUCCH in a Remaining Minimum System Information (RMSI) for sending.
  • RMSI Remaining Minimum System Information
  • the configuration parameters of the first PUCCH and the configuration parameters of the second PUCCH are both carried in the RMSI.
  • the PUCCH configuration parameters shared by the terminals of the first type and the terminals of the second type are carried in the RMSI.
  • the network device can receive the terminal capability reported by the terminal, and the terminal capability represents that the terminal is a first type terminal or a second type terminal.
  • the network device can determine the resources for the terminal to feed back HARQ through the terminal capability, and then can receive the HARQ feedback according to the determined resources.
  • Fig. 8 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment. As shown in Fig. 8 , the method for configuring random access parameters is used in a network device, and includes the following steps.
  • step S51 the terminal capability reported by the terminal is received, and the terminal capability indicates that the terminal is a first type terminal or a second type terminal.
  • step S52 according to the terminal capability, determine the resources for the terminal to perform Msg.4 HARQ.
  • the network device determines the resource for the terminal to perform Msg.4 HARQ according to the terminal capability, for example, on the one hand, the resource may be the resource corresponding to the configuration parameter of the first PUCCH, or the resource corresponding to the configuration parameter of the second PUCCH.
  • the network device determines resources for the terminal to perform Msg.4HARQ according to the terminal capability, for example, the resources corresponding to the PUCCH configuration parameters shared by the first type terminal and the second type terminal may be included.
  • the PUCCH configuration parameter determined by the network device satisfies the capability of the first type terminal and the second type terminal to perform Msg.4 HARQ in the random access process, and the PUCCH configuration parameter is enhanced. , so that the configuration parameters of the PUCCH can meet the terminal capabilities of the Redcap terminal.
  • Fig. 9 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment. As shown in Fig. 9 , the method for configuring random access parameters is used in a terminal, and includes the following steps.
  • step S61 the configuration parameters of the PUCCH are determined.
  • step S62 according to the determined PUCCH configuration parameters, resources for performing Msg.4 HARQ in the random access process are determined.
  • the PUCCH configuration parameter includes configuration parameters for performing Msg.4 HARQ in the random access process for the first type terminal and the second type terminal.
  • the configuration parameters for the first type terminal and the second type terminal to perform Msg.4HARQ in the random access process meet the requirements that the first type terminal and the second type terminal perform Msg.4HARQ in the random access process.
  • capabilities, the capabilities of the first type of terminals and the capabilities of the second type of terminals are different.
  • the terminal of the first type and the terminal of the second type may have different capabilities.
  • the capability of the terminal may be the transceiving bandwidth, the number of transceiving antennas, the maximum number of bits of the transport block, and the processing time delay.
  • the different capabilities of the terminals may be one or more of the transceiving bandwidth, the number of transceiving antennas, the maximum number of bits of the transport block, and the processing time delay.
  • the configuration parameter of the PUCCH corresponding to the type of the terminal may be determined based on the type of the terminal, and the PUCCH resource may be determined according to the determined configuration parameter of the PUCCH.
  • the terminal transmits the HARQ of Msg.4 on the determined PUCCH resource.
  • Fig. 10 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment. As shown in Fig. 10 , the method for configuring random access parameters is used in a terminal, and includes the following steps.
  • step S71 the terminal type is determined, the terminal type is a first type terminal or a second type terminal, and the capabilities of the first type terminal and the second type terminal are different.
  • step S72 PUCCH configuration parameters are determined according to the terminal type.
  • the PUCCH configuration parameter includes a first PUCCH configuration parameter and a second PUCCH configuration parameter.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are at least partially different.
  • the first PUCCH configuration parameter corresponds to the first type of terminal, and the second PUCCH configuration parameter corresponds to the second type of terminal.
  • the PUCCH configuration parameters determined by the terminal include the first PUCCH configuration parameters, and the first PUCCH configuration parameters satisfy the ability of the first type terminal to perform Msg.4HARQ in the random access process
  • the first PUCCH configuration parameter includes the configuration of the PUCCH that bears the Msg.4 HARQ feedback during the random access process of the first type terminal.
  • the PUCCH configuration parameter determined by the terminal includes the second PUCCH configuration parameter, and the second PUCCH configuration parameter satisfies the capability of the second type terminal to perform Msg.4 HARQ in the random access process, or also It can be understood that the second PUCCH configuration parameter includes the configuration of the PUCCH that bears the Msg.4 HARQ feedback during the random access process of the second type terminal.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are at least partially different, and may include one or more of the following parameters: different PRBs where the PUCCH is located, PUCCH The format of the PUCCH is different, the frequency hopping is supported or not, the PRB position of the PUCCH supporting frequency hopping is different, and the frequency hopping width of the PUCCH supporting frequency hopping is different.
  • the capability of the first type terminal is stronger than that of the second type terminal.
  • the first type terminal may be a normal UE, and the second type terminal may be Redcap terminal.
  • the transmission and reception bandwidth supported by the UE is greater than the transmission and reception bandwidth supported by the Redcap terminal.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are at least partially different, for example, the first PUCCH configuration parameter includes a configuration parameter that supports frequency hopping, and the second PUCCH configuration parameter includes a configuration parameter that does not support frequency hopping; and/or
  • the frequency hopping width configured in the first PUCCH configuration parameter is larger than the frequency hopping width configured in the second PUCCH configuration parameter.
  • the PUCCH configuration parameter includes a PUCCH configuration parameter shared by the first type of terminal and the second type of terminal.
  • the terminal may directly determine the PUCCH resource based on the configured PUCCH configuration parameter without distinguishing the terminal type, and transmit the HARQ of Msg.4 on the determined PUCCH resource.
  • the capability of the first type terminal is stronger than that of the second type terminal.
  • the first type terminal may be a normal UE, and the second type terminal may be a Redcap terminal.
  • the PUCCH configuration parameter shared by the first type terminal and the second type terminal may include one or a combination of the following parameters: PUCCH does not support frequency hopping. Or the PUCCH supports frequency hopping, and the frequency hopping width is within the bandwidth range supported by the terminal of the second type.
  • the PUCCH configuration parameters shared by the first-type terminal and the second-type terminal satisfy the capabilities of the second-type terminal, that is, the capabilities of the first-type terminal and the second-type terminal can be satisfied.
  • Fig. 11 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment. As shown in Fig. 9 , the method for configuring random access parameters is used in a terminal, and includes the following steps.
  • step S81 the configuration parameters of the PUCCH sent by the network device are received.
  • the PUCCH configuration parameters include configuration parameters for performing Msg.4 HARQ in the random access process for the first type terminal and the second type terminal.
  • the configuration parameters for the first type terminal and the second type terminal to perform Msg.4HARQ in the random access process meet the requirements that the first type terminal and the second type terminal perform Msg.4HARQ in the random access process.
  • capabilities, the capabilities of the first type of terminals and the capabilities of the second type of terminals are different.
  • the configuration parameters of the PUCCH may include the configuration parameters of the first PUCCH and the configuration parameters of the first PUCCH.
  • the configuration parameters of the PUCCH may include PUCCH configuration parameters shared by the terminals of the first type and the terminals of the second type.
  • the configuration parameters of the PUCCH in the embodiment of the present disclosure are carried in the RMSI, and the terminal may determine the configuration parameters of the PUCCH based on the received RMSI.
  • the terminal may determine the configuration parameters of the first PUCCH and the configuration parameters of the second PUCCH based on the received RMSI.
  • the terminal may determine the PUCCH configuration parameter shared by the first type terminal and the second type terminal based on the received RMSI.
  • the terminal capability that the terminal can report and the terminal capability table indicates that the terminal is the first type terminal or the second type terminal, so that the network device can determine the HARQ feedback information of the terminal through the terminal capability. resources, and then the HARQ feedback can be received according to the determined resources.
  • Fig. 12 is a flowchart showing a method for configuring random access parameters according to an exemplary embodiment. As shown in Fig. 12 , the method for configuring random access parameters is used in a terminal, and includes the following steps.
  • step S91 the terminal capability is reported, and the terminal capability indicates that the terminal is the first type terminal or the second type terminal.
  • the terminal reports the terminal capability, so that the network device determines the resources for the terminal to perform Msg.4 HARQ according to the terminal capability.
  • the resource for the terminal to perform Msg.4 HARQ determined by the network device according to the terminal capability may be the resource corresponding to the configuration parameter of the first PUCCH, or the resource corresponding to the configuration parameter of the second PUCCH.
  • the network device determines resources for the terminal to perform Msg.4HARQ according to the terminal capability, for example, the resources corresponding to the PUCCH configuration parameters shared by the first type terminal and the second type terminal may be included.
  • the terminal determines the PUCCH configuration parameter according to the terminal type, and determines the PUCCH resource for performing Msg.4 HARQ in the random access process according to the determined PUCCH parameter, which can satisfy the PUCCH matching the terminal type.
  • the configuration parameters of the device can meet the terminal capabilities of different types of terminals.
  • the random access parameter configuration method provided by the embodiment of the present disclosure is applicable to the process of implementing random access parameter configuration during the interaction between the network device and the terminal.
  • the process of implementing random access parameter configuration through interaction between the network device and the terminal will not be described in detail in this embodiment of the present disclosure.
  • the embodiment of the present disclosure also provides an apparatus for configuring random access parameters.
  • the random access parameter configuration apparatus includes corresponding hardware structures and/or software modules for executing each function.
  • the embodiments of the present disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of the embodiments of the present disclosure.
  • Fig. 13 is a block diagram of an apparatus for configuring random access parameters according to an exemplary embodiment.
  • the random access parameter configuration apparatus 100 is applied to a network device, and includes a processing unit 101 .
  • the processing unit 101 is configured to determine a PUCCH configuration parameter, where the PUCCH configuration parameter includes configuration parameters for performing Msg.4 HARQ in the random access process for the first type terminal and the second type terminal, the first type terminal and the second type terminal. different abilities.
  • the PUCCH configuration parameters include a first PUCCH configuration parameter and a second PUCCH configuration parameter.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are at least partially different.
  • the first PUCCH configuration parameter corresponds to the first type of terminal, and the second PUCCH configuration parameter corresponds to the second type of terminal.
  • the PUCCH configuration parameters include PUCCH configuration parameters shared by the first type of terminal and the second type of terminal.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are different in at least one of the following parameters: the physical resource block where the PUCCH is located, the format of the PUCCH, the PUCCH supports frequency hopping or the PUCCH does not support frequency hopping, The physical resource block position of the PUCCH supporting frequency hopping, and the frequency hopping width of the PUCCH supporting frequency hopping.
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal.
  • the first PUCCH configuration parameters include configuration parameters that support frequency hopping
  • the second PUCCH configuration parameters include configuration parameters that do not support frequency hopping.
  • the frequency hopping width configured in the first PUCCH configuration parameter is larger than the frequency hopping width configured in the second PUCCH configuration parameter.
  • the PUCCH configuration parameters include PUCCH configuration parameters shared by the first type of terminal and the second type of terminal.
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal.
  • the PUCCH configuration parameters include one or a combination of the following parameters:
  • the PUCCH does not support frequency hopping.
  • the PUCCH supports frequency hopping, and the frequency hopping width is within the bandwidth range supported by the second type of terminal.
  • the random access parameter configuration apparatus 100 further includes a sending unit 102 .
  • the sending unit 102 is configured to send PUCCH configuration parameters.
  • the PUCCH configuration parameters are carried in the RMSI.
  • the random access parameter configuration apparatus 100 further includes a receiving unit 103 .
  • the receiving unit 103 is configured to: receive the terminal capability reported by the terminal, where the terminal capability indicates that the terminal is a first type terminal or a second type terminal.
  • the processing unit 101 is configured to determine resources for the terminal to perform Msg.4 HARQ according to the terminal capability.
  • Fig. 14 is a block diagram of an apparatus for configuring random access parameters according to an exemplary embodiment.
  • the random access parameter configuration apparatus 200 is applied to a terminal, and the random access parameter configuration apparatus 200 includes a processing unit 201 .
  • the processing unit 201 is configured to determine PUCCH configuration parameters, and determine resources for performing Msg.4 HARQ in the random access process according to the PUCCH configuration parameters.
  • the PUCCH configuration parameters include the random access
  • the configuration parameters of Msg.4HARQ are carried out in the process.
  • the processing unit 201 is configured to determine the PUCCH configuration parameters in the following manner: determine the terminal type, the terminal type is the first type terminal or the second type terminal, and the capabilities of the first type terminal and the second type terminal are different.
  • the PUCCH configuration parameters are determined according to the terminal type.
  • the PUCCH configuration parameters include a first PUCCH configuration parameter and a second PUCCH configuration parameter.
  • the first PUCCH configuration parameter and the second PUCCH configuration parameter are at least partially different.
  • the first PUCCH configuration parameter corresponds to the first type of terminal
  • the second PUCCH configuration parameter corresponds to the second type of terminal.
  • At least one of the following parameters of the first PUCCH configuration parameter and the second PUCCH configuration parameter is different:
  • the physical resource block where the PUCCH is located the format of the PUCCH, whether the PUCCH supports frequency hopping or the PUCCH does not support frequency hopping, the location of the physical resource block where the PUCCH supports frequency hopping, and the frequency hopping width of the PUCCH that supports frequency hopping.
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal.
  • the first PUCCH configuration parameters include configuration parameters that support frequency hopping
  • the second PUCCH configuration parameters include configuration parameters that do not support frequency hopping.
  • the frequency hopping width configured in the first PUCCH configuration parameter is larger than the frequency hopping width configured in the second PUCCH configuration parameter.
  • the PUCCH configuration parameters include PUCCH configuration parameters shared by the first type of terminal and the second type of terminal.
  • the capabilities of the first type of terminal are stronger than the capabilities of the second type of terminal.
  • the PUCCH configuration parameters include one or a combination of the following parameters: PUCCH does not support frequency hopping.
  • PUCCH supports frequency hopping, and the frequency hopping width is within the bandwidth range supported by the second type of terminal.
  • the random access parameter configuration apparatus 200 further includes a receiving unit 202 .
  • the receiving unit 202 is configured to receive the PUCCH configuration parameter sent by the network device.
  • the processing unit 201 is configured to determine the PUCCH configuration parameters based on the PUCCH configuration parameters received by the receiving unit.
  • the PUCCH configuration parameters are carried in the RMSI.
  • the random access parameter configuration apparatus 200 further includes a sending unit 203 .
  • the sending unit 203 is configured to report the terminal capability of the terminal, and the terminal capability indicates that the terminal type is the first type terminal or the second type terminal.
  • Fig. 15 is a block diagram of an apparatus for configuring random access parameters according to an exemplary embodiment.
  • apparatus 300 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, and the like.
  • apparatus 300 may include one or more of the following components: processing component 302, memory 304, power component 306, multimedia component 308, audio component 310, input/output (I/O) interface 312, sensor component 314, and Communication component 316 .
  • the processing component 302 generally controls the overall operation of the device 300, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 302 may include one or more processors 320 to execute instructions to perform all or some of the steps of the methods described above. Additionally, processing component 302 may include one or more modules that facilitate interaction between processing component 302 and other components. For example, processing component 302 may include a multimedia module to facilitate interaction between multimedia component 308 and processing component 302 .
  • Memory 304 is configured to store various types of data to support operations at device 300 . Examples of such data include instructions for any application or method operating on device 300, contact data, phonebook data, messages, pictures, videos, and the like. Memory 304 may be implemented by any type of volatile or nonvolatile storage device or combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Magnetic Disk Magnetic Disk or Optical Disk.
  • Power component 306 provides power to various components of device 300 .
  • Power components 306 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to device 300 .
  • Multimedia component 308 includes screens that provide an output interface between the device 300 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user.
  • the touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.
  • the multimedia component 308 includes a front-facing camera and/or a rear-facing camera. When the apparatus 300 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each of the front and rear cameras can be a fixed optical lens system or have focal length and optical zoom capability.
  • Audio component 310 is configured to output and/or input audio signals.
  • audio component 310 includes a microphone (MIC) that is configured to receive external audio signals when device 300 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signal may be further stored in memory 304 or transmitted via communication component 316 .
  • audio component 310 also includes a speaker for outputting audio signals.
  • the I/O interface 312 provides an interface between the processing component 302 and a peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to: home button, volume buttons, start button, and lock button.
  • Sensor assembly 314 includes one or more sensors for providing status assessment of various aspects of device 300 .
  • the sensor assembly 314 can detect the open/closed state of the device 300, the relative positioning of components, such as the display and keypad of the device 300, and the sensor assembly 314 can also detect a change in the position of the device 300 or a component of the device 300 , the presence or absence of user contact with the device 300 , the orientation or acceleration/deceleration of the device 300 and the temperature change of the device 300 .
  • Sensor assembly 314 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact.
  • Sensor assembly 314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 316 is configured to facilitate wired or wireless communication between apparatus 300 and other devices.
  • Device 300 may access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 316 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 316 also includes a near field communication (NFC) module to facilitate short-range communication.
  • NFC near field communication
  • the NFC module may be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • apparatus 300 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation is used to perform the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor or other electronic component implementation is used to perform the above method.
  • non-transitory computer-readable storage medium including instructions, such as a memory 304 including instructions, executable by the processor 320 of the apparatus 300 to perform the method described above.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
  • Fig. 16 is a block diagram of an apparatus for configuring random access parameters according to an exemplary embodiment.
  • the apparatus 400 may be provided as a server.
  • apparatus 400 includes a processing component 422, which further includes one or more processors, and a memory resource represented by memory 432 for storing instructions executable by processing component 422, such as an application program.
  • An application program stored in memory 432 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 422 is configured to execute instructions to perform the above-described methods.
  • Device 400 may also include a power supply assembly 426 configured to perform power management of device 400 , a wired or wireless network interface 450 configured to connect device 400 to a network, and an input output (I/O) interface 458 .
  • Device 400 may operate based on an operating system stored in memory 432, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.
  • a non-transitory computer-readable storage medium including instructions such as a memory 432 including instructions, executable by the processing component 422 of the apparatus 400 to perform the method described above is also provided.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
  • first, second, etc. are used to describe various information, but the information should not be limited to these terms. These terms are only used to distinguish the same type of information from one another, and do not imply a particular order or level of importance. In fact, the expressions “first”, “second” etc. are used completely interchangeably.
  • the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information, without departing from the scope of the present disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

本公开是关于一种随机接入参数配置方法、装置及存储介质。随机接入参数配置方法,其特征在于,应用于网络设备,包括:确定物理上行控制信道配置参数,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同。通过本公开能够实现针对不同能力的终端进行物理上行控制信道配置参数的配置,满足不同能力的终端的通信能力。

Description

一种随机接入参数配置方法、装置及存储介质 技术领域
本公开涉及通信技术领域,尤其涉及一种随机接入参数配置方法、装置及存储介质。
背景技术
随着物联网业务的不断发展,比如视频监控,智能家居,可穿戴设备和工业传感监测等业务的普及。这些业务通常要求几十到100M的速率,同时对时延也有相对较高的要求,因此相关技术中的机器类通信(Machine Type Communication,MTC),窄带物联网(Narrow band Internet of thing,NB-IoT)技术很难满足要求。故,提出了在5G新空口(New Radio,NR)中再设计一种新的类型终端用以来覆盖中端物联网设备的要求。在目前的3GPP标准化中,这种新的类型终端叫做Reduced capability UE,或者简称为NR-lite或Redcap终端。
随着Redcap终端的引入,使得终端的能力发生了差异化,例如Redcap终端相对正常终端(normal UE)而言,收发带宽受限,故,已有随机接入参数配置方式不能满足差异化的终端需求。
发明内容
为克服相关技术中存在的问题,本公开提供一种随机接入参数配置方法、装置及存储介质。
根据本公开实施例的第一方面,提供一种随机接入参数配置方法,应用于网络设备,所述随机接入参数配置方法包括:确定物理上行控制信道配置参数,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同。
一种实施方式中,所述物理上行控制信道配置参数包括第一物理上行控制信道配置参数和第二物理上行控制信道配置参数;所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数至少部分参数不同;所述第一物理上行控制信道配置参数对应所述第一类型终端,所述第二物理上行控制信道配置参数对应所述第二类型终端。
一种实施方式中,所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数的以下至少一个参数不同:
物理上行控制信道所在的物理资源块;物理上行控制信道的格式;物理上行控制信道支持跳频或物理上行控制信道不支持跳频;物理上行控制信道支持跳频的物理资源块位置;以及物理上行控制信道支持跳频的跳频宽度。
一种实施方式中,所述第一类型终端的能力强于所述第二类型终端的能力;
所述第一物理上行控制信道配置参数中包括支持跳频的配置参数,所述第二物理上行控制信道配置参数中包括不支持跳频的配置参数;和/或所述第一物理上行控制信道配置参数中配置的跳频宽度大于所述第二物理上行控制信道配置参数中配置的跳频宽度。
一种实施方式中,所述物理上行控制信道配置参数包括所述第一类型终端和所述第二类型终端共用的物理上行控制信道配置参数。
一种实施方式中,所述第一类型终端的能力强于所述第二类型终端的能力;
所述物理上行控制信道配置参数中包括如下参数之一或组合:
物理上行控制信道不支持跳频;物理上行控制信道支持跳频,且跳频宽度在所述第二类型终端支持的带宽范围内。
一种实施方式中,所述随机接入参数配置方法还包括:发送所述物理上行控制信道配置参数。
一种实施方式中,所述物理上行控制信道配置参数承载在剩余最少系统消息RMSI中。
一种实施方式中,所述随机接入参数配置方法还包括:
接收终端上报的终端能力,所述终端能力表征所述终端为第一类型终端或第二类型终端;根据所述终端能力,确定所述终端进行消息4自动混合重传请求反馈的资源。
根据本公开实施例第二方面,提供一种随机接入参数配置方法,应用于终端,所述随机接入参数配置方法包括:确定物理上行控制信道配置参数,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同;根据所述物理上行控制信道配置参数确定随机接入过程中进行消息4自动混合重传请求反馈的资源。
一种实施方式中,所述确定物理上行控制信道配置参数,包括:
确定终端类型,所述终端类型为第一类型终端或第二类型终端,所述第一类型终端和所述第二类型终端的能力不同;根据所述终端类型确定物理上行控制信道配置参数;所述物理上行控制信道配置参数包括第一物理上行控制信道配置参数和第二物理上行控制信道配置参数;所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数至少部分参数不同;所述第一物理上行控制信道配置参数对应所述第一类型终端,所述第二物理上行控制信道配置参数对应所述第二类型终端。
一种实施方式中,所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数的如下参数中的以下至少一个参数不同:
物理上行控制信道所在的物理资源块;物理上行控制信道的格式;物理上行控制信道 支持跳频或物理上行控制信道不支持跳频;物理上行控制信道支持跳频的物理资源块位置;以及物理上行控制信道支持跳频的跳频宽度。
一种实施方式中,所述第一类型终端的能力强于所述第二类型终端的能力;
所述第一物理上行控制信道配置参数中包括支持跳频的配置参数,所述第二物理上行控制信道配置参数中包括不支持跳频的配置参数;和/或所述第一物理上行控制信道配置参数中配置的跳频宽度大于所述第二物理上行控制信道配置参数中配置的跳频宽度。
一种实施方式中,所述物理上行控制信道配置参数包括第一类型终端和第二类型终端共用的物理上行控制信道配置参数。
一种实施方式中,所述第一类型终端的能力强于所述第二类型终端的能力;
所述物理上行控制信道配置参数中包括如下参数之一或组合:物理上行控制信道不支持跳频;物理上行控制信道支持跳频,且跳频宽度在所述第二类型终端支持的带宽范围内。
一种实施方式中,所述确定物理上行控制信道配置参数,包括:
接收网络设备发送的物理上行控制信道配置参数。
一种实施方式中,所述物理上行控制信道配置参数承载在剩余最少系统消息RMSI中。
一种实施方式中,所述随机接入参数配置方法还包括:上报所述终端的终端能力,所述终端能力表征所述终端类型为第一类型终端或第二类型终端。
根据本公开实施例第三方面,提供一种随机接入参数配置装置,其特征在于,应用于网络设备,所述随机接入参数配置装置包括:
处理单元,被配置为确定物理上行控制信道配置参数,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同。
一种实施方式中,所述物理上行控制信道配置参数包括第一物理上行控制信道配置参数和第二物理上行控制信道配置参数;所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数至少部分参数不同;所述第一物理上行控制信道配置参数对应所述第一类型终端,所述第二物理上行控制信道配置参数对应所述第二类型终端。
一种实施方式中,所述物理上行控制信道配置参数包括所述第一类型终端和所述第二类型终端共用的物理上行控制信道配置参数。
一种实施方式中,所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数的如下参数中以下至少一个参数不同:
物理上行控制信道所在的物理资源块;物理上行控制信道的格式;物理上行控制信道 支持跳频或物理上行控制信道不支持跳频;物理上行控制信道支持跳频的物理资源块位置;以及物理上行控制信道支持跳频的跳频宽度。
一种实施方式中,所述第一类型终端的能力强于所述第二类型终端的能力;
所述第一物理上行控制信道配置参数中包括支持跳频的配置参数,所述第二物理上行控制信道配置参数中包括不支持跳频的配置参数;和/或所述第一物理上行控制信道配置参数中配置的跳频宽度大于所述第二物理上行控制信道配置参数中配置的跳频宽度。
一种实施方式中,所述物理上行控制信道配置参数包括所述第一类型终端和所述第二类型终端共用的物理上行控制信道配置参数。
一种实施方式中,所述第一类型终端的能力强于所述第二类型终端的能力;
所述物理上行控制信道配置参数中包括如下参数之一或组合:
物理上行控制信道不支持跳频;物理上行控制信道支持跳频,且跳频宽度在所述第二类型终端支持的带宽范围内。
一种实施方式中,所述随机接入参数配置装置还包括:发送单元,被配置为发送所述物理上行控制信道配置参数。
一种实施方式中,所述物理上行控制信道配置参数承载在剩余最少系统消息RMSI中。
一种实施方式中,所述随机接入参数配置装置还包括接收单元,所述接收单元被配置为:接收终端上报的终端能力,所述终端能力表征所述终端为第一类型终端或第二类型终端;所述处理单元被配置为根据所述终端能力,确定所述终端进行消息4自动混合重传请求反馈的资源。
根据本公开实施例第四方面,提供一种随机接入参数配置装置,应用于终端,所述随机接入参数配置装置包括:处理单元,被配置为确定物理上行控制信道配置参数,并根据所述物理上行控制信道配置参数确定随机接入过程中进行消息4自动混合重传请求反馈的资源,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同。
一种实施方式中,所述处理单元被配置为采用如下方式确定物理上行控制信道配置参数:确定终端类型,所述终端类型为第一类型终端或第二类型终端,所述第一类型终端和所述第二类型终端的能力不同;根据所述终端类型确定物理上行控制信道配置参数;所述物理上行控制信道配置参数包括第一物理上行控制信道配置参数和第二物理上行控制信道配置参数;所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数至少部分参数不同;所述第一物理上行控制信道配置参数对应所述第一类型终端,所述第 二物理上行控制信道配置参数对应所述第二类型终端。
一种实施方式中,所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数的如下参数中的以下至少一个参数不同:
物理上行控制信道所在的物理资源块;物理上行控制信道的格式;物理上行控制信道支持跳频或物理上行控制信道不支持跳频;物理上行控制信道支持跳频的物理资源块位置;以及物理上行控制信道支持跳频的跳频宽度。
一种实施方式中,所述第一类型终端的能力强于所述第二类型终端的能力;
所述第一物理上行控制信道配置参数中包括支持跳频的配置参数,所述第二物理上行控制信道配置参数中包括不支持跳频的配置参数;和/或所述第一物理上行控制信道配置参数中配置的跳频宽度大于所述第二物理上行控制信道配置参数中配置的跳频宽度。
一种实施方式中,所述物理上行控制信道配置参数包括第一类型终端和第二类型终端共用的物理上行控制信道配置参数。
一种实施方式中,所述第一类型终端的能力强于所述第二类型终端的能力;
所述物理上行控制信道配置参数中包括如下参数之一或组合:物理上行控制信道不支持跳频;物理上行控制信道支持跳频,且跳频宽度在所述第二类型终端支持的带宽范围内。
一种实施方式中,所述随机接入参数配置装置还包括接收单元,所述接收单元用于接收网络设备发送的物理上行控制信道配置参数。所述处理单元被配置为基于所述接收单元接收的物理上行控制信道配置参数,确定物理上行控制信道配置参数。
一种实施方式中,所述物理上行控制信道配置参数承载在剩余最少系统消息RMSI中。
一种实施方式中,所述随机接入参数配置装置还包括发送单元,所述发送单元被配置为上报所述终端的终端能力,所述终端能力表征所述终端类型为第一类型终端或第二类型终端。
根据本公开实施例第五方面,提供一种随机接入参数配置装置,包括:
处理器;用于存储处理器可执行指令的存储器;
其中,所述处理器被配置为:执行第一方面或者第一方面任意一种实施方式中所述的随机接入参数配置方法。
根据本公开实施例第六方面,提供一种随机接入参数配置装置,包括:
处理器;用于存储处理器可执行指令的存储器;
其中,所述处理器被配置为:执行第二方面或者第二方面任意一种实施方式中所述的随机接入参数配置方法。
根据本公开实施例第七方面,提供一种非临时性计算机可读存储介质,当所述存储介 质中的指令由网络设备的处理器执行时,使得网络设备能够执行第一方面或者第一方面任意一种实施方式中所述的随机接入参数配置方法。
根据本公开实施例第八方面,提供一种非临时性计算机可读存储介质,当所述存储介质中的指令由移动终端的处理器执行时,使得移动终端能够执行第二方面或者第二方面任意一种实施方式中所述的随机接入参数配置方法。
本公开的实施例提供的技术方案可以包括以下有益效果:通过确定满足能力不同的第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈能力的物理上行控制信道配置参数,能够实现针对不同能力的终端进行物理上行控制信道配置参数的配置,满足不同能力的终端的通信能力。
应当理解的是,以上的一般描述和后文的细节描述仅是示例性和解释性的,并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分,示出了符合本公开的实施例,并与说明书一起用于解释本公开的原理。
图1是根据一示例性实施例示出的一种无线通信系统示意图。
图2示出了一种跳频范围超出Redcap终端接收频带范围的示意图。
图3是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图4是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图5示出了本公开一示例性实施例中为normal UE和Redcap终端分别配置不同跳频宽度的PUCCH配置参数的示意图。
图6是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图7是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图8是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图9是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图10是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图11是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图12是根据一示例性实施例示出的一种随机接入参数配置方法的流程图。
图13是根据一示例性实施例示出的一种随机接入参数配置装置框图。
图14是根据一示例性实施例示出的一种随机接入参数配置装置框图。
图15是根据一示例性实施例示出的一种用于随机接入参数配置的装置的框图。
图16是根据一示例性实施例示出的一种用于随机接入参数配置的装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明,其示例表示在附图中。下面的描述涉及附图时,除非另有表示,不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反,它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
本公开实施例提供的随机接入参数配置方法可应用于图1所示的无线通信系统中。参阅图1所示,该无线通信系统中包括终端和网络设备。终端和网络设备之间通过无线资源进行信息的发送与接收。
可以理解的是,图1所示的无线通信系统仅是进行示意性说明,无线通信系统中还可包括其它网络设备,例如还可以包括核心网络设备、无线中继设备和无线回传设备等,在图1中未画出。本公开实施例对该无线通信系统中包括的网络设备数量和终端数量不做限定。
进一步可以理解的是,本公开实施例的无线通信系统,是一种提供无线通信功能的网络。无线通信系统可以采用不同的通信技术,例如码分多址(code division multiple access,CDMA)、宽带码分多址(wideband code division multiple access,WCDMA)、时分多址(time division multiple access,TDMA)、频分多址(frequency division multiple access,FDMA)、正交频分多址(orthogonal frequency-division multiple access,OFDMA)、单载波频分多址(single Carrier FDMA,SC-FDMA)、载波侦听多路访问/冲突避免(Carrier Sense Multiple Access with Collision Avoidance)。根据不同网络的容量、速率、时延等因素可以将网络分为2G(英文:generation)网络、3G网络、4G网络或者未来演进网络,如5G网络,5G网络也可称为是新无线网络(New Radio,NR)。为了方便描述,本公开有时会将无线通信网络简称为网络。
进一步的,本公开中涉及的网络设备也可以称为无线接入网络设备。该无线接入网络设备可以是:基站、演进型基站(evolved node B,基站)、家庭基站、无线保真(wireless fidelity,WIFI)系统中的接入点(access point,AP)、无线中继节点、无线回传节点、传输点(transmission point,TP)或者发送接收点(transmission and reception point,TRP)等,还可以为NR系统中的gNB,或者,还可以是构成基站的组件或一部分设备等。当为车联网(V2X)通信系统时,网络设备还可以是车载设备。应理解,本公开的实施例中,对网络设备所采用的具体技术和具体设备形态不做限定。
进一步的,本公开中涉及的终端,也可以称为终端设备、用户设备(User Equipment,UE)、移动台(Mobile Station,MS)、移动终端(Mobile Terminal,MT)等,是一种向用 户提供语音和/或数据连通性的设备,例如,终端可以是具有无线连接功能的手持式设备、车载设备等。目前,一些终端的举例为:智能手机(Mobile Phone)、口袋计算机(Pocket Personal Computer,PPC)、掌上电脑、个人数字助理(Personal Digital Assistant,PDA)、笔记本电脑、平板电脑、可穿戴设备、或者车载设备等。此外,当为车联网(V2X)通信系统时,终端设备还可以是车载设备。应理解,本公开实施例对终端所采用的具体技术和具体设备形态不做限定。
本公开实施例涉及的终端可以理解为是在5G NR中设计的新的类型终端:Reduced capability UE或者简称为NR-lite或Redcap终端。本公开实施例中,将该新的终端称为Redcap终端。
同长期演进(Long Term Evolution,LTE)中的物联网(Internet of Thing,IoT)设备类似,Redcap终端通常需要满足如下要求:
-低造价,低复杂度
-一定程度的覆盖增强
-功率节省
相关技术中,Redcap终端的收发带宽与终端的能力匹配,相对normal UE而言,收发带宽受限。例如,在初始接入(initial access)阶段的最大带宽(max UE BW)受限。通常,在频段1(FR1)下的带宽是20MHz,在FR2下的带宽是40MHz。然而,相关技术中在initial access阶段需要进行物理上行控制信道(physical uplink control channel,PUCCH)的配置,例如在随机接入信道(Random Access Channel,RACH)配置阶段配置承载消息4(Msg.4)混合自动重传请求(Hybrid Automatic Repeat Request,HARQ)的PUCCH格式(format)。其中,承载Msg.4HARQ反馈的PUCCH format是PUCCH format0和PUCCH format 1。其中,format 0是短PUCCH(short PUCCH),不支持同时隙(intra-slot)的跳频(frequency hopping,FH),其长度可以为1-2个OFDM符号(OFDM symbol)。Format1是长PUCCH(long PUCCH),支持FH,其长度可以为4-14个OFDM symbol。
相关技术中,进行PUCCH配置时,网络设备通常是采用广播的方式广播PUCCH的配置参数,比如,在系统信息块(System Information Block,SIB)中网络设备会广播次PUCCH的配置参数,包括PUCCH的format,物理资源模块(Physical Resource Block,PRB)位置,是否支持跳频等。然而,网络设备广播的PUCCH配置参数,很可能出现不能满足Redcap终端能力的情况。例如,在Redcap终端与normal UE共享上行BWP(UL BWP)时,若PUCCH的配置参数包括针对Msg.4HARQ使用intra-slot跳频,此时的跳频范围可能会超过Redcap终端的接收频带范围。图2示出了一种跳频范围超出Redcap终端接收 频带范围的示意图。参阅图2所示,Redcap终端和normal UE在初始阶段共享的UL BWP上均接收到了终端广播的intra-slot跳频范围,该intra-slot跳频范围超出了Redcap终端的接收带宽范围,不能满足Redcap终端在随机接入过程中对Msg.4HARQ的能力。
本公开实施例提供一种随机接入参数配置方法,在该随机接入参数配置方法中,对PUCCH的配置参数进行增强,使PUCCH的配置参数能够满足Redcap终端的终端能力。
一种实施方式中,配置initial UL BWP中的PUCCH配置参数,满足不同类型终端能力的终端在随机接入过程中进行Msg.4HARQ的能力。
其中,本公开实施例中为描述方便,将不同类型终端中任意两种不同类型的终端称为第一类型终端和第二类型终端。第一类型终端和第二类型终端的能力不同。一示例中,第一类型终端可以是normal UE,第二类型终端可以是Redcap终端。
本公开实施例中,配置PUCCH的配置参数,PUCCH的配置参数满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力,第一类型终端和第二类型终端的能力不同。
图3是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图3所示,随机接入参数配置方法用于网络设备中,包括以下步骤。
在步骤S11中,确定PUCCH的配置参数。
其中,网络设备确定的PUCCH配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的配置参数。
一种方式中,网络设备确定的针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4 HARQ的配置参数,满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4 HARQ的能力。其中,第一类型终端的能力和第二类型终端的能力不同。
本公开实施例中第一类型终端和第二类型终端可以是具有不同的能力。例如终端的能力可以包括以下的至少一项:传输带宽(例如接收带宽和/或发送带宽)、传输天线数量(例如接收天线和/或发送天线)、传输块的最大比特数、以及处理时间延迟等。终端的能力不同可以是收发带宽、收发天线数量、传输块的最大比特数、以及处理时间延迟中的一项或多项不同。
本公开实施例一种实施方式中,可以针对不同能力的终端分别配置不同的PUCCH配置参数,以满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力。例如,为第一类型终端配置第一PUCCH配置参数,为第二类型终端配置第二PUCCH配置参数。其中,第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同或所有参数不同。
图4是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图4所示,随机接入参数配置方法用于网络设备中,包括以下步骤。
在步骤S21中,确定第一PUCCH配置参数和第二PUCCH配置参数。
其中,本公开实施例提供的随机接入参数配置方法中,配置的PUCCH参数中包括第一PUCCH配置参数和第二PUCCH配置参数。第一PUCCH配置参数对应第一类型终端,第二PUCCH参数对应第二类型终端。其中,第一PUCCH配置参数对应第一类型终端可以理解为是第一PUCCH配置参数满足第一类型终端在随机接入过程中进行Msg.4HARQ的能力,或者也可以理解为是第一PUCCH配置参数包括承载第一类型终端随机接入过程中对Msg.4HARQ反馈PUCCH的配置。其中,第二PUCCH配置参数对应第二类型终端可以理解为是第二PUCCH配置参数满足第二类型终端在随机接入过程中进行Msg.4HARQ的能力,或者也可以理解为是第二PUCCH配置参数包括承载第二类型终端随机接入过程中对Msg.4HARQ反馈PUCCH的配置。
本公开实施例提供的随机接入参数配置方法中,第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同。
一示例中,在initial UL BWP中包括相关于第一PUCCH的配置和第二PUCCH的配置。其中,PUCCH配置包括承载随机接入过程中对Msg.4HARQ反馈PUCCH的配置。第一PUCCH的配置与第二PUCCH的配置不同。第一PUCCH的配置供第一类型终端使用,第二PUCCH的配置供第二类型终端使用。其中,第一类型终端与第二类型终端的终端能力不同。其中所述终端能力包括终端的收发带宽。
本公开实施例提供的随机接入参数配置方法中,第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同,可以是包括以下至少一个参数不同:PUCCH所在的PRB不同、PUCCH的格式不同、是否支持跳频不同、PUCCH支持跳频的PRB位置不同,以及PUCCH支持跳频的跳频宽度不同。
本公开实施例提供的随机接入参数配置方法的一示例中,第一类型终端的能力强于第二类型终端的能力,例如,第一类型终端可以是normal UE,第二类型终端可以是Redcap终端。normal UE支持的收发带宽大于Redcap终端支持的收发带宽。第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同,例如可以是第一PUCCH配置参数中包括支持跳频的配置参数,第二PUCCH配置参数中包括不支持跳频的配置参数;和/或第一PUCCH配置参数中配置的跳频宽度大于第二PUCCH配置参数中配置的跳频宽度。
图5示出了本公开一示例性实施例中为normal UE和Redcap终端分别配置不同跳频宽度的PUCCH配置参数的示意图。参阅图5所示,normal UE使用的第一PUCCH配置参数 中配置的跳频宽度,大于Redcap终端使用的第二PUCCH配置参数中配置的跳频宽度。第一PUCCH配置参数中配置的跳频宽度匹配normal UE的收发带宽,跳频时不会超出normal UE的收发带宽。第二PUCCH配置参数中配置的跳频宽度匹配Redcap终端的收发带宽,跳频时不会超出Redcap终端的收发带宽。第一PUCCH配置参数和第二PUCCH配置参数分别满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力。
本公开实施例一种实施方式中,可以配置满足不同能力的终端的PUCCH配置参数,以满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力。即,配置的PUCCH配置参数包括第一类型终端和第二类型终端共用的PUCCH配置参数。
图6是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图6所示,随机接入参数配置方法用于网络设备中,包括以下步骤。
在步骤S31中,配置第一类型终端和第二类型终端共用的PUCCH配置参数。
一种实施方式中,第一类型终端的能力强于第二类型终端的能力,例如,第一类型终端可以是normal UE,第二类型终端可以是Redcap终端。第一类型终端和第二类型终端共用的PUCCH配置参数可以是包括以下至少参数或多个参数组合:PUCCH不支持跳频;或者PUCCH支持跳频,且跳频宽度在第二类型终端支持的带宽范围内。换言之,第一类型终端和第二类型终端共用的PUCCH配置参数满足第二类型终端的能力,即可同事满足第一类型终端和第二类型终端的能力。
一示例中,网络设备配置1套PUCCH的配置参数,满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力。比如所配置的PUCCH不使用跳频,或所配置的PUCCH跳频宽度在第二类终端的能力范围内;此时第一类终端和第二类终端共用相同的PUCCH配置。
本公开实施例中网络设备确定了满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ能力的PUCCH配置参数后,可以将确定的PUCCH配置参数发送给终端,终端基于根据终端类型确定对应的PUCCH配置,并根据PUCCH配置确定具体的PUCCH资源。终端在确定的PUCCH资源上传输Msg.4的HARQ。
图7是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图7所示,随机接入参数配置方法用于网络设备中,包括以下步骤。
在步骤S41中,确定PUCCH的配置参数。
本公开实施例中,PUCCH配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的配置参数。
一种方式中,针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ 的配置参数,满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力,第一类型终端的能力和第二类型终端的能力不同。一方面,PUCCH的配置参数可以包括第一PUCCH的配置参数和第二PUCCH的配置参数。另一方面,PUCCH的配置参数可以包括第一类型终端和第二类型终端共用的PUCCH配置参数。
在步骤S42中,发送PUCCH的配置参数。
本公开实施例提供的随机接入参数配置方法中,网络设备发送PUCCH的配置参数可以是通过广播的方式发送。
一种实施方式中,本公开实施例中网络设备可以将PUCCH的配置参数承载在剩余最少系统消息(Remaining Minimum System Information,RMSI)中发送。例如,第一PUCCH的配置参数和第二PUCCH的配置参数都承载在RMSI中。再例如,第一类型终端和第二类型终端共用的PUCCH配置参数承载在RMSI中。
本公开实施例提供的随机接入参数配置方法中,网络设备可以接收终端上报的终端能力,终端能力表征述终端为第一类型终端或第二类型终端。网络设备通过终端能力可以确定终端反馈HARQ的资源,进而可按照确定的资源进行HARQ反馈的接收。
图8是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图8所示,随机接入参数配置方法用于网络设备中,包括以下步骤。
在步骤S51中,接收终端上报的终端能力,终端能力表征终端为第一类型终端或第二类型终端。
在步骤S52中,根据终端能力,确定终端进行Msg.4HARQ的资源。
其中,本公开实施例中网络设备根据终端能力确定终端进行Msg.4HARQ的资源例如一方面可以是,第一PUCCH的配置参数对应的资源,或者第二PUCCH的配置参数对应的资源。另一方面网络设备根据终端能力确定终端进行Msg.4HARQ的资源例如可以包括第一类型终端和第二类型终端共用的PUCCH配置参数对应的资源。
本公开实施例提供的随机接入参数配置方法,网络设备确定的PUCCH配置参数满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力,对PUCCH的配置参数进行增强,使PUCCH的配置参数能够满足Redcap终端的终端能力。
图9是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图9所示,随机接入参数配置方法用于终端中,包括以下步骤。
在步骤S61中,确定PUCCH的配置参数。
在步骤S62中,根据确定的PUCCH配置参数,确定随机接入过程中进行Msg.4HARQ的资源。
本公开实施例提供的随机接入参数配置方法中,PUCCH配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的配置参数。
一种方式中,针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的配置参数,满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力,第一类型终端的能力和第二类型终端的能力不同。
本公开实施例中第一类型终端和第二类型终端可以是具有不同的能力。例如终端的能力可以是收发带宽、收发天线数量、传输块的最大比特数、以及处理时间延迟等。终端的能力不同可以是收发带宽、收发天线数量、传输块的最大比特数、以及处理时间延迟中的一项或多项不同。
其中,终端确定PUCCH的配置参数时可以基于终端的类型确定与终端类型对应的PUCCH的配置参数,并根据确定的PUCCH配置参数确定PUCCH资源。终端在确定的PUCCH资源上传输Msg.4的HARQ。
图10是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图10所示,随机接入参数配置方法用于终端中,包括以下步骤。
在步骤S71中,确定终端类型,终端类型为第一类型终端或第二类型终端,第一类型终端和第二类型终端的能力不同。
在步骤S72中,根据终端类型确定PUCCH配置参数。
本公开实施例提供的随机接入参数配置方法中,一种实施方式中,PUCCH配置参数包括第一PUCCH配置参数和第二PUCCH配置参数。其中,第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同。第一PUCCH配置参数对应第一类型终端,第二PUCCH配置参数对应第二类型终端。换言之,若确定的终端类型为第一类型终端,则终端确定的PUCCH配置参数包括第一PUCCH配置参数,第一PUCCH配置参数满足第一类型终端在随机接入过程中进行Msg.4HARQ的能力,或者也可以理解为是第一PUCCH配置参数包括承载第一类型终端随机接入过程中对Msg.4HARQ反馈PUCCH的配置。若确定的终端类型为第二类型终端,则终端确定的PUCCH配置参数包括第二PUCCH配置参数,第二PUCCH配置参数满足第二类型终端在随机接入过程中进行Msg.4HARQ的能力,或者也可以理解为是第二PUCCH配置参数包括承载第二类型终端随机接入过程中对Msg.4HARQ反馈PUCCH的配置。
本公开实施例提供的随机接入参数配置方法中,第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同,可以是包括如下参数中的一个或多个不同:PUCCH所在的PRB不同、PUCCH的格式不同、是否支持跳频不同、PUCCH支持跳频的PRB位置不同, 以及PUCCH支持跳频的跳频宽度不同。
本公开实施例提供的随机接入参数配置方法的一示例中,第一类型终端的能力强于第二类型终端的能力,例如,第一类型终端可以是normal UE,第二类型终端可以是Redcap终端。normal UE支持的收发带宽大于Redcap终端支持的收发带宽。第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同例如可以是第一PUCCH配置参数中包括支持跳频的配置参数,第二PUCCH配置参数中包括不支持跳频的配置参数;和/或第一PUCCH配置参数中配置的跳频宽度大于第二PUCCH配置参数中配置的跳频宽度。
本公开实施例提供的随机接入参数配置方法中,另一种实施方式中,PUCCH配置参数包括第一类型终端和第二类型终端共用的PUCCH配置参数。终端则可以不区分终端类型,直接基于配置的PUCCH配置参数确定PUCCH资源,并在确定的PUCCH资源上传输Msg.4的HARQ。
其中,本公开实施例中,第一类型终端的能力强于第二类型终端的能力,例如,第一类型终端可以是normal UE,第二类型终端可以是Redcap终端。第一类型终端和第二类型终端共用的PUCCH配置参数可以是包括如下参数之一或组合:PUCCH不支持跳频。或者PUCCH支持跳频,且跳频宽度在第二类型终端支持的带宽范围内。换言之,第一类型终端和第二类型终端共用的PUCCH配置参数满足第二类型终端的能力,即可满足第一类型终端和第二类型终端的能力。
图11是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图9所示,随机接入参数配置方法用于终端中,包括以下步骤。
在步骤S81中,接收网络设备发送的PUCCH的配置参数。
本公开实施例中,本公开实施例中,PUCCH配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的配置参数。
一种方式中,针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的配置参数,满足第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的能力,第一类型终端的能力和第二类型终端的能力不同。一方面,PUCCH的配置参数可以包括第一PUCCH的配置参数和第一PUCCH的配置参数。另一方面,PUCCH的配置参数可以包括第一类型终端和第二类型终端共用的PUCCH配置参数。
一种实施方式中,本公开实施例中PUCCH的配置参数承载在RMSI中,则终端可以基于接收的RMSI,确定PUCCH的配置参数。例如,终端基于接收的RMSI可以确定第一PUCCH的配置参数和第二PUCCH的配置参数。再例如,终端基于接收的RMSI可以确定第一类型终端和第二类型终端共用的PUCCH配置参数。
本公开实施例提供的随机接入参数配置方法中,终端可以上报的终端能力,终端能力表征述终端为第一类型终端或第二类型终端,以使网络设备通过终端能力可以确定终端反馈HARQ的资源,进而可按照确定的资源进行HARQ反馈的接收。
图12是根据一示例性实施例示出的一种随机接入参数配置方法的流程图,如图12所示,随机接入参数配置方法用于终端中,包括以下步骤。
在步骤S91中,上报终端能力,终端能力表征终端为第一类型终端或第二类型终端。
本公开实施例中,终端上报终端能力,使得网络设备根据终端能力确定终端进行Msg.4HARQ的资源。一方面,网络设备根据终端能力确定终端进行Msg.4HARQ的资源可以是第一PUCCH的配置参数对应的资源,或者第二PUCCH的配置参数对应的资源。另一方面网络设备根据终端能力确定终端进行Msg.4HARQ的资源例如可以包括第一类型终端和第二类型终端共用的PUCCH配置参数对应的资源。
本公开实施例提供的随机接入参数配置方法,终端根据终端类型确定PUCCH配置参数,并根据确定的PUCCH参数确定在随机接入过程中进行Msg.4HARQ的PUCCH资源,能够满足匹配终端类型的PUCCH的配置参数,进而能够满足不同类型终端的终端能力。
可以理解的是,本公开实施例提供的随机接入参数配置方法适用于网络设备与终端交互过程实现随机接入参数配置的过程。其中,对于网络设备与终端之间进行交互实现随机接入参数配置的过程,本公开实施例不再详述。
需要说明的是,本领域内技术人员可以理解,本公开实施例上述涉及的各种实施方式/实施例中可以配合前述的实施例使用,也可以是独立使用。无论是单独使用还是配合前述的实施例一起使用,其实现原理类似。本公开实施中,部分实施例中是以一起使用的实施方式进行说明的;当然,本领域内技术人员可以理解,这样的举例说明并非对本公开实施例的限定。
基于相同的构思,本公开实施例还提供一种随机接入参数配置装置。
可以理解的是,本公开实施例提供的随机接入参数配置装置为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。结合本公开实施例中所公开的各示例的单元及算法步骤,本公开实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能,但是这种实现不应认为超出本公开实施例的技术方案的范围。
图13是根据一示例性实施例示出的一种随机接入参数配置装置框图。参照图13,该随机接入参数配置装置100应用于网络设备,包括处理单元101。
处理单元101,被配置为确定PUCCH配置参数,PUCCH配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的配置参数,第一类型终端和第二类型终端的能力不同。
一种实施方式中,PUCCH配置参数包括第一PUCCH配置参数和第二PUCCH配置参数。第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同。第一PUCCH配置参数对应第一类型终端,第二PUCCH配置参数对应第二类型终端。
一种实施方式中,PUCCH配置参数包括第一类型终端和第二类型终端共用的PUCCH配置参数。
一种实施方式中,第一PUCCH配置参数和第二PUCCH配置参数的如下参数中的以下至少一个参数不同:PUCCH所在的物理资源块、PUCCH的格式、PUCCH支持跳频或PUCCH不支持跳频、PUCCH支持跳频的物理资源块位置、以及PUCCH支持跳频的跳频宽度。
一种实施方式中,第一类型终端的能力强于第二类型终端的能力。
第一PUCCH配置参数中包括支持跳频的配置参数,第二PUCCH配置参数中包括不支持跳频的配置参数。和/或,第一PUCCH配置参数中配置的跳频宽度大于第二PUCCH配置参数中配置的跳频宽度。
一种实施方式中,PUCCH配置参数包括第一类型终端和第二类型终端共用的PUCCH配置参数。
一种实施方式中,第一类型终端的能力强于第二类型终端的能力。
PUCCH配置参数中包括如下参数之一或组合:
PUCCH不支持跳频。PUCCH支持跳频,且跳频宽度在第二类型终端支持的带宽范围内。
一种实施方式中,随机接入参数配置装置100还包括发送单元102。发送单元102,被配置为发送PUCCH配置参数。
一种实施方式中,PUCCH配置参数承载在RMSI中。
一种实施方式中,随机接入参数配置装置100还包括接收单元103。接收单元103被配置为:接收终端上报的终端能力,终端能力表征终端为第一类型终端或第二类型终端。处理单元101被配置为根据终端能力,确定终端进行Msg.4HARQ的资源。
图14是根据一示例性实施例示出的一种随机接入参数配置装置框图。参照图14,该随机接入参数配置装置200应用于终端,随机接入参数配置装置200包括处理单元201。
其中,处理单元201,被配置为确定PUCCH配置参数,并根据PUCCH配置参数确定 随机接入过程中进行Msg.4HARQ的资源,PUCCH配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行Msg.4HARQ的配置参数。
一种实施方式中,处理单元201被配置为采用如下方式确定PUCCH配置参数:确定终端类型,终端类型为第一类型终端或第二类型终端,第一类型终端和第二类型终端的能力不同。根据终端类型确定PUCCH配置参数。PUCCH配置参数包括第一PUCCH配置参数和第二PUCCH配置参数。第一PUCCH配置参数和第二PUCCH配置参数至少部分参数不同。第一PUCCH配置参数对应第一类型终端,第二PUCCH配置参数对应第二类型终端。
一种实施方式中,第一PUCCH配置参数和第二PUCCH配置参数的如下参数中的以下至少一个参数不同:
PUCCH所在的物理资源块、PUCCH的格式、PUCCH支持跳频或PUCCH不支持跳频、PUCCH支持跳频的物理资源块位置、以及PUCCH支持跳频的跳频宽度。
一种实施方式中,第一类型终端的能力强于第二类型终端的能力。
第一PUCCH配置参数中包括支持跳频的配置参数,第二PUCCH配置参数中包括不支持跳频的配置参数。和/或第一PUCCH配置参数中配置的跳频宽度大于第二PUCCH配置参数中配置的跳频宽度。
一种实施方式中,PUCCH配置参数包括第一类型终端和第二类型终端共用的PUCCH配置参数。
一种实施方式中,第一类型终端的能力强于第二类型终端的能力。
PUCCH配置参数中包括如下参数之一或组合:PUCCH不支持跳频。PUCCH支持跳频,且跳频宽度在第二类型终端支持的带宽范围内。
一种实施方式中,随机接入参数配置装置200还包括接收单元202。接收单元202被配置为接收网络设备发送的PUCCH配置参数。处理单元201被配置为基于接收单元接收的PUCCH配置参数,确定PUCCH配置参数。
一种实施方式中,PUCCH配置参数承载在RMSI中。
一种实施方式中,随机接入参数配置装置200还包括发送单元203。发送单元203被配置为上报终端的终端能力,终端能力表征终端类型为第一类型终端或第二类型终端。
关于上述实施例中的装置,其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述,此处将不做详细阐述说明。
图15是根据一示例性实施例示出的一种用于随机接入参数配置的装置的框图。例如,装置300可以是移动电话,计算机,数字广播终端,消息收发设备,游戏控制台,平板设 备,医疗设备,健身设备,个人数字助理等。
参照图15,装置300可以包括以下一个或多个组件:处理组件302,存储器304,电力组件306,多媒体组件308,音频组件310,输入/输出(I/O)接口312,传感器组件314,以及通信组件316。
处理组件302通常控制装置300的整体操作,诸如与显示,电话呼叫,数据通信,相机操作和记录操作相关联的操作。处理组件302可以包括一个或多个处理器320来执行指令,以完成上述的方法的全部或部分步骤。此外,处理组件302可以包括一个或多个模块,便于处理组件302和其他组件之间的交互。例如,处理组件302可以包括多媒体模块,以方便多媒体组件308和处理组件302之间的交互。
存储器304被配置为存储各种类型的数据以支持在装置300的操作。这些数据的示例包括用于在装置300上操作的任何应用程序或方法的指令,联系人数据,电话簿数据,消息,图片,视频等。存储器304可以由任何类型的易失性或非易失性存储设备或者它们的组合实现,如静态随机存取存储器(SRAM),电可擦除可编程只读存储器(EEPROM),可擦除可编程只读存储器(EPROM),可编程只读存储器(PROM),只读存储器(ROM),磁存储器,快闪存储器,磁盘或光盘。
电力组件306为装置300的各种组件提供电力。电力组件306可以包括电源管理系统,一个或多个电源,及其他与为装置300生成、管理和分配电力相关联的组件。
多媒体组件308包括在所述装置300和用户之间的提供一个输出接口的屏幕。在一些实施例中,屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板,屏幕可以被实现为触摸屏,以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界,而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中,多媒体组件308包括一个前置摄像头和/或后置摄像头。当装置300处于操作模式,如拍摄模式或视频模式时,前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件310被配置为输出和/或输入音频信号。例如,音频组件310包括一个麦克风(MIC),当装置300处于操作模式,如呼叫模式、记录模式和语音识别模式时,麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器304或经由通信组件316发送。在一些实施例中,音频组件310还包括一个扬声器,用于输出音频信号。
I/O接口312为处理组件302和外围接口模块之间提供接口,上述外围接口模块可以是键盘,点击轮,按钮等。这些按钮可包括但不限于:主页按钮、音量按钮、启动按钮和 锁定按钮。
传感器组件314包括一个或多个传感器,用于为装置300提供各个方面的状态评估。例如,传感器组件314可以检测到装置300的打开/关闭状态,组件的相对定位,例如所述组件为装置300的显示器和小键盘,传感器组件314还可以检测装置300或装置300一个组件的位置改变,用户与装置300接触的存在或不存在,装置300方位或加速/减速和装置300的温度变化。传感器组件314可以包括接近传感器,被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件314还可以包括光传感器,如CMOS或CCD图像传感器,用于在成像应用中使用。在一些实施例中,该传感器组件314还可以包括加速度传感器,陀螺仪传感器,磁传感器,压力传感器或温度传感器。
通信组件316被配置为便于装置300和其他设备之间有线或无线方式的通信。装置300可以接入基于通信标准的无线网络,如WiFi,2G或3G,或它们的组合。在一个示例性实施例中,通信组件316经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中,所述通信组件316还包括近场通信(NFC)模块,以促进短程通信。例如,在NFC模块可基于射频识别(RFID)技术,红外数据协会(IrDA)技术,超宽带(UWB)技术,蓝牙(BT)技术和其他技术来实现。
在示例性实施例中,装置300可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现,用于执行上述方法。
在示例性实施例中,还提供了一种包括指令的非临时性计算机可读存储介质,例如包括指令的存储器304,上述指令可由装置300的处理器320执行以完成上述方法。例如,所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
图16是根据一示例性实施例示出的一种用于随机接入参数配置的装置的框图。例如,装置400可以被提供为一服务器。参照图16,装置400包括处理组件422,其进一步包括一个或多个处理器,以及由存储器432所代表的存储器资源,用于存储可由处理组件422的执行的指令,例如应用程序。存储器432中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外,处理组件422被配置为执行指令,以执行上述方法。
装置400还可以包括一个电源组件426被配置为执行装置400的电源管理,一个有线或无线网络接口450被配置为将装置400连接到网络,和一个输入输出(I/O)接口458。装置400可以操作基于存储在存储器432的操作系统,例如Windows ServerTM,Mac OS XTM,UnixTM,LinuxTM,FreeBSDTM或类似。
在示例性实施例中,还提供了一种包括指令的非临时性计算机可读存储介质,例如包括指令的存储器432,上述指令可由装置400的处理组件422执行以完成上述方法。例如,所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
进一步可以理解的是,本公开中“多个”是指两个或两个以上,其它量词与之类似。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。单数形式的“一种”、“所述”和“该”也旨在包括多数形式,除非上下文清楚地表示其他含义。
进一步可以理解的是,术语“第一”、“第二”等用于描述各种信息,但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开,并不表示特定的顺序或者重要程度。实际上,“第一”、“第二”等表述完全可以互换使用。例如,在不脱离本公开范围的情况下,第一信息也可以被称为第二信息,类似地,第二信息也可以被称为第一信息。
进一步可以理解的是,本公开实施例中尽管在附图中以特定的顺序描述操作,但是不应将其理解为要求按照所示的特定顺序或是串行顺序来执行这些操作,或是要求执行全部所示的操作以得到期望的结果。在特定环境中,多任务和并行处理可能是有利的。
本领域技术人员在考虑说明书及实践这里公开的发明后,将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本公开的真正范围和精神由下面的权利要求指出。
应当理解的是,本公开并不局限于上面已经描述并在附图中示出的精确结构,并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (24)

  1. 一种随机接入参数配置方法,其特征在于,应用于网络设备,所述随机接入参数配置方法包括:
    确定物理上行控制信道配置参数,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同。
  2. 根据权利要求1所述的随机接入参数配置方法,其特征在于,所述物理上行控制信道配置参数包括第一物理上行控制信道配置参数和第二物理上行控制信道配置参数;
    所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数至少部分参数不同;
    所述第一物理上行控制信道配置参数对应所述第一类型终端,所述第二物理上行控制信道配置参数对应所述第二类型终端。
  3. 根据权利要求2所述的随机接入参数配置方法,其特征在于,所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数的如下参数中的以下至少一个参数不同:
    物理上行控制信道所在的物理资源块;
    物理上行控制信道的格式;
    物理上行控制信道支持跳频或物理上行控制信道不支持跳频;
    物理上行控制信道支持跳频的物理资源块位置;以及
    物理上行控制信道支持跳频的跳频宽度。
  4. 根据权利要求2或3所述的随机接入参数配置方法,其特征在于,所述第一类型终端的能力强于所述第二类型终端的能力;
    所述第一物理上行控制信道配置参数中包括支持跳频的配置参数,所述第二物理上行控制信道配置参数中包括不支持跳频的配置参数;和/或
    所述第一物理上行控制信道配置参数中配置的跳频宽度大于所述第二物理上行控制信道配置参数中配置的跳频宽度。
  5. 根据权利要求1所述的随机接入参数配置方法,其特征在于,所述物理上行控制信道配置参数包括所述第一类型终端和所述第二类型终端共用的物理上行控制信道配置参数。
  6. 根据权利要求5所述的随机接入参数配置方法,其特征在于,所述第一类型终端 的能力强于所述第二类型终端的能力;
    所述物理上行控制信道配置参数中包括如下参数之一或组合:
    物理上行控制信道不支持跳频;
    物理上行控制信道支持跳频,且跳频宽度在所述第二类型终端支持的带宽范围内。
  7. 根据权利要求1至6中任意一项所述的随机接入参数配置方法,其特征在于,所述随机接入参数配置方法还包括:
    发送所述物理上行控制信道配置参数。
  8. 根据权利要求7所述的随机接入参数配置方法,其特征在于,所述物理上行控制信道配置参数承载在剩余最少系统消息RMSI中。
  9. 根据权利要求1所述的随机接入参数配置方法,其特征在于,所述随机接入参数配置方法还包括:
    接收终端上报的终端能力,所述终端能力表征所述终端为第一类型终端或第二类型终端;
    根据所述终端能力,确定所述终端进行消息4自动混合重传请求反馈的资源。
  10. 一种随机接入参数配置方法,其特征在于,应用于终端,所述随机接入参数配置方法包括:
    确定物理上行控制信道配置参数,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同;
    根据所述物理上行控制信道配置参数确定随机接入过程中进行消息4自动混合重传请求反馈的资源。
  11. 根据权利要求10所述的随机接入参数配置方法,其特征在于,所述确定物理上行控制信道配置参数,包括:
    确定终端类型,所述终端类型为第一类型终端或第二类型终端,所述第一类型终端和所述第二类型终端的能力不同;
    根据所述终端类型确定物理上行控制信道配置参数;
    所述物理上行控制信道配置参数包括第一物理上行控制信道配置参数和第二物理上行控制信道配置参数;
    所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数至少部分参数不同;
    所述第一物理上行控制信道配置参数对应所述第一类型终端,所述第二物理上行控制 信道配置参数对应所述第二类型终端。
  12. 根据权利要求11所述的随机接入参数配置方法,其特征在于,所述第一物理上行控制信道配置参数和所述第二物理上行控制信道配置参数的如下参数中的以下至少一个参数不同:
    物理上行控制信道所在的物理资源块;
    物理上行控制信道的格式;
    物理上行控制信道支持跳频或物理上行控制信道不支持跳频;
    物理上行控制信道支持跳频的物理资源块位置;以及
    物理上行控制信道支持跳频的跳频宽度。
  13. 根据权利要求11或12所述的随机接入参数配置方法,其特征在于,所述第一类型终端的能力强于所述第二类型终端的能力;
    所述第一物理上行控制信道配置参数中包括支持跳频的配置参数,所述第二物理上行控制信道配置参数中包括不支持跳频的配置参数;和/或
    所述第一物理上行控制信道配置参数中配置的跳频宽度大于所述第二物理上行控制信道配置参数中配置的跳频宽度。
  14. 根据权利要求10所述的随机接入参数配置方法,其特征在于,所述物理上行控制信道配置参数包括第一类型终端和第二类型终端共用的物理上行控制信道配置参数。
  15. 根据权利要求14所述的随机接入参数配置方法,其特征在于,所述第一类型终端的能力强于所述第二类型终端的能力;
    所述物理上行控制信道配置参数中包括如下参数之一或组合:
    物理上行控制信道不支持跳频;
    物理上行控制信道支持跳频,且跳频宽度在所述第二类型终端支持的带宽范围内。
  16. 根据权利要求10至15中任意一项所述的随机接入参数配置方法,其特征在于,所述确定物理上行控制信道配置参数,包括:
    接收网络设备发送的物理上行控制信道配置参数。
  17. 根据权利要求16所述的随机接入参数配置方法,其特征在于,所述物理上行控制信道配置参数承载在剩余最少系统消息RMSI中。
  18. 根据权利要求10所述的随机接入参数配置方法,其特征在于,所述随机接入参数配置方法还包括:
    上报所述终端的终端能力,所述终端能力表征所述终端类型为第一类型终端或第二类型终端。
  19. 一种随机接入参数配置装置,其特征在于,应用于网络设备,所述随机接入参数配置装置包括:
    处理单元,被配置为确定物理上行控制信道配置参数,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同。
  20. 一种随机接入参数配置装置,其特征在于,应用于终端,所述随机接入参数配置装置包括:
    处理单元,被配置为确定物理上行控制信道配置参数,并根据所述物理上行控制信道配置参数确定随机接入过程中进行消息4自动混合重传请求反馈的资源,所述物理上行控制信道配置参数包含针对第一类型终端和第二类型终端在随机接入过程中进行消息4自动混合重传请求反馈的配置参数,所述第一类型终端和所述第二类型终端的能力不同。
  21. 一种随机接入参数配置装置,其特征在于,包括:
    处理器;
    用于存储处理器可执行指令的存储器;
    其中,所述处理器被配置为:执行权利要求1至9中任意一项所述的随机接入参数配置方法。
  22. 一种随机接入参数配置装置,其特征在于,包括:
    处理器;
    用于存储处理器可执行指令的存储器;
    其中,所述处理器被配置为:执行权利要求10至18中任意一项所述的随机接入参数配置方法。
  23. 一种非临时性计算机可读存储介质,当所述存储介质中的指令由网络设备的处理器执行时,使得网络设备能够执行权利要求1至9中任意一项所述的随机接入参数配置方法。
  24. 一种非临时性计算机可读存储介质,当所述存储介质中的指令由移动终端的处理器执行时,使得移动终端能够执行权利要求10至18中任意一项所述的随机接入参数配置方法。
PCT/CN2021/071506 2021-01-13 2021-01-13 一种随机接入参数配置方法、装置及存储介质 WO2022151052A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US18/260,968 US20240057171A1 (en) 2021-01-13 2021-01-13 Method and apparatus for configuring random access parameter, and storage medium
CN202180000224.0A CN115088375A (zh) 2021-01-13 2021-01-13 一种随机接入参数配置方法、装置及存储介质
EP21918268.0A EP4280785A1 (en) 2021-01-13 2021-01-13 Method and apparatus for configuring random access parameter, and storage medium
JP2023541699A JP2024505394A (ja) 2021-01-13 2021-01-13 ランダムアクセスパラメータ設定方法、装置及び記憶媒体
KR1020237026201A KR20230125831A (ko) 2021-01-13 2021-01-13 랜덤 액세스 파라미터 설정 방법, 장치 및 저장 매체
PCT/CN2021/071506 WO2022151052A1 (zh) 2021-01-13 2021-01-13 一种随机接入参数配置方法、装置及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071506 WO2022151052A1 (zh) 2021-01-13 2021-01-13 一种随机接入参数配置方法、装置及存储介质

Publications (1)

Publication Number Publication Date
WO2022151052A1 true WO2022151052A1 (zh) 2022-07-21

Family

ID=82447716

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/071506 WO2022151052A1 (zh) 2021-01-13 2021-01-13 一种随机接入参数配置方法、装置及存储介质

Country Status (6)

Country Link
US (1) US20240057171A1 (zh)
EP (1) EP4280785A1 (zh)
JP (1) JP2024505394A (zh)
KR (1) KR20230125831A (zh)
CN (1) CN115088375A (zh)
WO (1) WO2022151052A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017135455A1 (ja) * 2016-02-04 2017-08-10 株式会社Nttドコモ ユーザ装置、及びランダムアクセス方法
CN110291745A (zh) * 2017-01-05 2019-09-27 夏普株式会社 用于第五代(5g)新无线电(nr)的短物理上行链路控制信道(pucch)设计
CN111492716A (zh) * 2020-03-23 2020-08-04 北京小米移动软件有限公司 用于随机接入的通信方法、装置及计算机可读存储介质
CN111567126A (zh) * 2020-04-08 2020-08-21 北京小米移动软件有限公司 配置信息传输方法及装置、通信设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017135455A1 (ja) * 2016-02-04 2017-08-10 株式会社Nttドコモ ユーザ装置、及びランダムアクセス方法
CN110291745A (zh) * 2017-01-05 2019-09-27 夏普株式会社 用于第五代(5g)新无线电(nr)的短物理上行链路控制信道(pucch)设计
CN111492716A (zh) * 2020-03-23 2020-08-04 北京小米移动软件有限公司 用于随机接入的通信方法、装置及计算机可读存储介质
CN111567126A (zh) * 2020-04-08 2020-08-21 北京小米移动软件有限公司 配置信息传输方法及装置、通信设备及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Identification and access restriction of RedCap UE", 3GPP DRAFT; R2-2009934, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051942704 *
NOKIA, NOKIA SHANGHAI BELL: "Cell access for REDCAP UE with reduced bandwidth", 3GPP DRAFT; R2-2009800, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20201102 - 20201113, 22 October 2020 (2020-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051941432 *

Also Published As

Publication number Publication date
KR20230125831A (ko) 2023-08-29
JP2024505394A (ja) 2024-02-06
CN115088375A (zh) 2022-09-20
EP4280785A1 (en) 2023-11-22
US20240057171A1 (en) 2024-02-15

Similar Documents

Publication Publication Date Title
WO2022193195A1 (zh) 一种带宽部分配置方法、带宽部分配置装置及存储介质
WO2022151488A1 (zh) 一种带宽部分确定方法、带宽部分确定装置及存储介质
WO2022141074A1 (zh) 波束指示方法、波束指示装置及存储介质
WO2022165856A1 (zh) 一种信息上报方法、信息上报装置及存储介质
WO2022027496A1 (zh) 资源配置方法、装置、通信设备和存储介质
WO2023279297A1 (zh) 随机接入方法、装置及存储介质
WO2022051948A1 (zh) 下行传输方法、下行传输装置及存储介质
WO2023050354A1 (zh) 一种sdt传输方法、装置及存储介质
WO2022193194A1 (zh) 一种带宽部分配置方法、带宽部分配置装置及存储介质
WO2022120535A1 (zh) 资源确定方法、资源确定装置及存储介质
WO2023201730A1 (zh) 一种传输用户设备能力的方法、装置及可读存储介质
WO2023133901A1 (zh) 一种资源冲突处理方法、装置及可读存储介质
WO2022126555A1 (zh) 一种传输方法、传输装置及存储介质
WO2022233057A1 (zh) 信道状态信息测量方法、装置及存储介质
WO2022151052A1 (zh) 一种随机接入参数配置方法、装置及存储介质
WO2022027323A1 (zh) 用于寻呼信息处理的方法、装置及存储介质
CN113796110A (zh) 一种执行小数据包传输和确定随机接入消息传输方式的方法、装置、设备及存储介质
WO2022150988A1 (zh) 一种接入资源确定方法、接入资源确定装置及存储介质
WO2022006722A1 (zh) 随机接入资源配置方法、装置及存储介质
WO2022217428A1 (zh) 一种波束管理方法、波束管理装置及存储介质
WO2022077234A1 (zh) 下行控制信息调度方法、装置及存储介质
WO2022032595A1 (zh) 一种频率切换方法、频率切换装置及存储介质
WO2022151490A1 (zh) 一种信道状态信息确定方法、装置及存储介质
WO2022032593A1 (zh) 一种跳频配置方法、跳频配置装置及存储介质
WO2022011703A1 (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: 21918268

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023541699

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 18260968

Country of ref document: US

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023013974

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20237026201

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021918268

Country of ref document: EP

Effective date: 20230814

WWE Wipo information: entry into national phase

Ref document number: 11202305322T

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 112023013974

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20230712