WO2023179743A1 - 随机接入方法及装置、计算机可读存储介质 - Google Patents

随机接入方法及装置、计算机可读存储介质 Download PDF

Info

Publication number
WO2023179743A1
WO2023179743A1 PCT/CN2023/083557 CN2023083557W WO2023179743A1 WO 2023179743 A1 WO2023179743 A1 WO 2023179743A1 CN 2023083557 W CN2023083557 W CN 2023083557W WO 2023179743 A1 WO2023179743 A1 WO 2023179743A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
random access
information
access method
type
Prior art date
Application number
PCT/CN2023/083557
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 展讯通信（上海）有限公司
Publication of WO2023179743A1 publication Critical patent/WO2023179743A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present invention relates to the field of wireless communication technology, and in particular, to a random access method and device, and a computer-readable storage medium.
  • the fifth generation mobile communication system defines three major application scenarios, including enhanced mobile broadband (eMBB) and ultra-reliable and low latency communication (URLLC). and massive machine type communications (mMTC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low latency communication
  • mMTC massive machine type communications
  • new services and new terminal types in actual applications that do not belong to these three major application scenarios. They have certain transmission rate requirements, but they are far less than eMBB. Their impact on latency The requirements are lower than URLLC but may be higher than eMBB. They also have business attributes of machine type communication.
  • a new terminal type is defined for this new service (new scenario), which is called a reduced capability (ReducedCapability, RedCap) terminal.
  • the access network equipment base station
  • the access network equipment cannot learn the terminal type, so the RedCap terminal may not be able to successfully access the network.
  • the embodiments of the present invention solve the technical problem that the access network equipment does not know the terminal type, causing the RedCap terminal to be unable to successfully access the network.
  • embodiments of the present invention provide a random access method, which includes: reporting terminal information during the random access process, where the terminal information includes terminal type and/or terminal capability information.
  • the reporting of terminal information includes: when performing uplink transmission, information carried by the uplink indicates the terminal information.
  • the reporting of terminal information includes: when sending a random access preamble, the random access preamble or the resources used by the random access preamble are used to indicate the terminal information; or, When sending a random access preamble, the random access preamble or the resources used by the random access preamble are used to indicate the terminal type, and carry the terminal capability information in Msg3.
  • the terminal type includes at least a first type of terminal and a second type of terminal with different processing capabilities.
  • the processing capability of the terminal includes at least one of the following: a supported maximum transport block size, a supported maximum number of HARQs, a supported processing time requirement, and a supported cache size.
  • the reporting of terminal information includes: carrying the terminal information through feedback information when feeding back the physical downlink shared channel containing the terminal contention resolution identifier.
  • the random access method further includes: detecting that the downlink control information scrambled by the temporary cell wireless network temporary identifier schedules the downlink control data shared channel, and fails to successfully decode the downlink control data shared channel or the downlink control data shared channel.
  • the terminal information is carried through feedback information.
  • carrying the terminal information through feedback information includes: indicating different terminal information through different feedback resources.
  • carrying the terminal information through feedback information further includes: indicating different terminal information through different code points indicated by the feedback information.
  • Embodiments of the present invention also provide a random access method, which includes: obtaining terminal information, where the terminal information includes terminal type and/or terminal capability information; adjusting the load size carried by Msg4 according to the terminal information; and re- Pass the Msg4 after payload size adjustment.
  • the obtaining terminal information includes: receiving a random access preamble, the random access preamble or the resources used by the random access preamble are used to indicate the terminal information; or, receiving a random access preamble. Enter a preamble and Msg3, the random access preamble or the resource used by the random access preamble is used to indicate the terminal type, and the Msg3 carries the terminal capability information.
  • the terminal type includes a first type of terminal and a second type of terminal with different processing capabilities.
  • the obtaining terminal information includes: receiving feedback information, where the feedback information is used to carry the terminal information.
  • different feedback resources in the feedback information indicate different terminal information.
  • different code points in the feedback information indicate different terminal information.
  • Embodiments of the present invention also provide a computer-readable storage medium.
  • the computer-readable storage medium is a non-volatile storage medium or a non-transitory storage medium, and a computer program is stored thereon.
  • the computer program is processed by a processor. The steps of any of the above random access methods are executed during runtime.
  • An embodiment of the present invention also provides another random access device, including a memory and a processor.
  • the memory stores a computer program that can be run on the processor.
  • the processor runs the computer program, it executes Any of the above random access methods A step of.
  • the terminal reports terminal information, so that the access network device learns the terminal information corresponding to the terminal.
  • the access network device determines the information carried in the delivered Msg4 based on the terminal information. Therefore, corresponding Msg4 is issued for different terminal information, thereby ensuring that RedCap terminals can access normally without affecting the access efficiency of general terminals.
  • Figure 1 is a flow chart of a random access method in an embodiment of the present invention
  • Figure 2 is a flow chart of another random access method in an embodiment of the present invention.
  • Figure 3 is a schematic structural diagram of a random access device in an embodiment of the present invention.
  • Figure 4 is a schematic structural diagram of another random access device in an embodiment of the present invention.
  • Universal terminals can be eMBB terminals, URLLC terminals, mMTC terminals, etc.
  • the access network equipment does not know the terminal type when performing access scheduling.
  • the RedCap terminal may not be able to successfully receive Msg4, causing the RedCap terminal to be unable to successfully access the cell; if scheduling is based on the capabilities of the RedCap terminal, due to the large amount of information corresponding to the RRC configuration information in Msg4, Then the RRC configuration message cannot be carried in Msg4, which will affect the initial access efficiency of the general terminal.
  • the terminal reports terminal information, so that the access network device learns the terminal information corresponding to the terminal.
  • the access network equipment is based on the terminal Information, determine the information carried in the Msg4 issued. Therefore, corresponding Msg4 is issued for different terminal information, thereby ensuring that RedCap terminals can access normally without affecting the access efficiency of general terminals.
  • the terminal described in the embodiment of the present invention is a device with wireless communication functions, which can be called user equipment (User Equipment, UE), mobile station (MS), mobile terminal (mobile terminal, MT), interface Input terminal equipment, vehicle-mounted terminal equipment, industrial control terminal equipment, UE unit, UE station, mobile station, remote station, remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE agent or UE device, etc.
  • User equipment can be fixed or mobile. It should be noted that the user equipment can support at least one wireless communication technology, such as LTE, new radio (NR), etc.
  • the user equipment can be a mobile phone, a tablet, a desktop, a laptop, an all-in-one machine, a vehicle terminal, a virtual reality (VR) user equipment, an augmented reality (AR) user Equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grid, transportation security Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless Wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, future mobile communications User equipment in the network or user equipment in the future evolved public land mobile network (PLMN), etc.
  • the user equipment may also be a device with transceiver functions, such as a chip system.
  • the chip system may include chips and may also include other discrete devices.
  • the access network device is a device that provides wireless communication functions for terminals.
  • the equipment can also be called wireless access network (radio access network, RAN) equipment, or access network elements.
  • the access network equipment may support at least one wireless communication technology, such as LTE, NR, etc.
  • access network equipment includes but is not limited to: next-generation base station (generation nodeB, gNB), evolved node B (evolved node B, eNB), wireless Network controller (radio network controller, RNC), node B (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved node B, or home node B (HNB), baseband unit (BBU), receiving point (transmitting and receiving point, TRP), transmitting point (TP), mobile switching center, etc.
  • generation nodeB generation nodeB, gNB
  • evolved node B evolved node B
  • eNB evolved node B
  • RNC wireless Network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • HNB home evolved node B
  • BBU baseband unit
  • TRP transmitting and receiving point
  • TP transmitting point
  • mobile switching center etc.
  • the network device may also be a wireless controller, a centralized unit (CU), and/or a distributed unit (DU) in a cloud radio access network (CRAN) scenario, or an access network
  • the equipment can be relay stations, access points, vehicle-mounted equipment, terminal equipment, wearable equipment, and access network equipment in future mobile communications or access network equipment in future evolved PLMNs, etc.
  • the access network device may also be a device with a wireless communication function for the terminal device, such as a chip system.
  • the chip system may include a chip, and may also include other discrete devices.
  • the access network device can also communicate with an Internet Protocol (Internet Protocol, IP) network, such as the Internet, a private IP network, or other data networks.
  • IP Internet Protocol
  • An embodiment of the present invention provides a random access method. Referring to Figure 1, detailed description will be given below through specific steps.
  • the random access method provided in the following steps S101 to S102 may be executed by the terminal.
  • the random access method provided in the following steps S101 to S102 can be executed by a chip with data processing capabilities in the terminal, or by a chip module including a data processing chip in the terminal.
  • Step S101 During the process of performing random access, terminal information is reported.
  • the terminal can report its corresponding terminal information.
  • the terminal information may include any one of terminal type and terminal capability information, or the terminal information may include both terminal type and terminal capability information.
  • Terminal types include first-type terminals and second-type terminals, and first-type terminals and second-type terminals correspond to different processing capabilities.
  • the first type of terminal may be a general terminal, and the second type of terminal may be a RedCap terminal. Furthermore, the terminal type may also include a third type of terminal, and the third type of terminal is a low-capability RedCap terminal.
  • the terminal capability information may include at least one of the following: a supported maximum transport block size, a supported maximum number of HARQs, a supported processing time requirement, and a supported cache size.
  • the access network device can receive the terminal information reported by the terminal, and then learn that the terminal is a general terminal, a RedCap terminal, or a low-capability RedCap terminal. If the terminal information only includes terminal capability information, the access network device can learn whether the terminal is a normal-capability RedCap terminal or a low-capability RedCap terminal. If the terminal information includes terminal type and terminal capability information, the access network device can learn whether the terminal is a general terminal or a RedCap terminal, and whether the terminal is a low-capability RedCap terminal.
  • the random access process may include a four-step random access process, specifically including the following steps:
  • the terminal sends a Random Access Preamble transmission (Msg1) to the access network device.
  • Msg1 Random Access Preamble transmission
  • the access network device sends a Random Access Response (RAR) (Msg2) to the terminal.
  • RAR Random Access Response
  • the access network device After receiving the random access preamble, the access network device sends an RA response through PDSCH.
  • the RA response includes the RA preamble identifier, timing adjustment information, initial uplink scheduling and temporary C-RNTI.
  • One PDSCH can carry RA responses to multiple terminals. After the terminal sends the random access preamble, it monitors the PDCCH and waits for the RA response within the RA response window.
  • the terminal receives a response with an RA preamble identifier, the identifier contains If the RA preamble identifier sent is the same, the response is successful and the terminal sends uplink scheduling information.
  • the response fails if the terminal does not receive a response within the RA response window or fails to verify the response. In this case, if the number of RA attempts is less than the upper limit (such as 10 times), the terminal retries RA; otherwise, RA fails.
  • the upper limit such as 10 times
  • the third step is to schedule uplink transmission (Msg3).
  • the terminal sends uplink scheduling information through PUSCH.
  • the fourth step is competition resolution (Msg4).
  • the contention resolution timer starts counting.
  • the access network equipment uses the C-RNTI on the PDCCH or the UE contention resolution identifier (IE) on the PDSCH to help the terminal resolve contention.
  • the terminal returns a positive answer after correctly decoding Msg4.
  • the terminal continues to listen to the PDCCH before the contention resolution timer expires.
  • the specific process of the above four-step random access process can refer to the existing protocol.
  • the terminal may report terminal information when sending the random access preamble.
  • terminal information can be carried through a random access preamble.
  • the terminal may indicate the terminal information through the resources used by the random access preamble.
  • the terminal may indicate the terminal type through the random access preamble, or may indicate the terminal type through the resources used by the random access preamble.
  • the terminal may also indicate the terminal capability information through the random access preamble, or indicate the terminal capability information through the resources used by the random access preamble.
  • the terminal indicates that the terminal type is a universal terminal or a RedCap terminal through a random access preamble.
  • the terminal can also report terminal capability information when scheduling uplink transmission (Msg3).
  • the terminal capability information can be used to indicate whether the RedCap terminal has restricted scheduled data. Amount of low-capability RedCap terminals.
  • the terminal information when the terminal schedules uplink transmission, the terminal information may be indicated by the information carried on the uplink.
  • the information carried on the uplink may be uplink scheduling information.
  • identification information is added to the uplink scheduling information, and the identification information indicates whether the RedCap terminal is a normal RedCap terminal or a low-capability RedCap terminal with limited scheduling data amount.
  • the uplink scheduling information when sending Msg1, it indicates whether the terminal type is a RedCap terminal. Further, after Msg1 indicates that it is a RedCap terminal, if the terminal is a normal RedCap terminal, the uplink scheduling information carries Msg3 normal LCID, indicating that the RedCap terminal is a normal RedCap terminal; if the uplink scheduling information carries Msg3 new LCID indicates that the RedCap terminal is a low-capability RedCap terminal that limits the amount of scheduled data.
  • the terminal may not report terminal information when sending the random access preamble.
  • the terminal can report the terminal information as the terminal type when scheduling uplink transmission, thereby indicating whether the terminal is a universal terminal or a RedCap terminal.
  • the terminal when the terminal sends uplink scheduling information through PUSCH, the terminal adds identification information to the uplink scheduling information, and uses the identification information to indicate whether the terminal is a universal terminal or a RedCap terminal.
  • the uplink scheduling information carries Msg3 normal LCID, indicating that the terminal is a general terminal; if the uplink scheduling information carries Msg3 new LCID, it indicates that the terminal is RedCap terminal.
  • the terminal may also report terminal information when receiving Msg4.
  • the terminal after detecting that the contention resolution is successful, the terminal carries the terminal information through the feedback information when feeding back the physical downlink shared channel containing the terminal contention resolution identifier.
  • a general terminal after receiving Msg4, feedback information is sent on the common PUCCH configured in the SIB.
  • the downlink control data shared channel is scheduled for the downlink control information scrambled by the temporary cell wireless network temporary identifier, and the downlink control data shared channel fails to be decoded successfully or the data of the downlink control data shared channel does not match the terminal type or exceeds the terminal type.
  • the terminal information is carried through feedback information.
  • a special (special) PUCCH can be configured in the SIB and NACK can be sent on the special PUCCH resource.
  • the terminal may indicate different terminal information through different feedback resources.
  • the terminal can also add terminal information to the feedback information, so that the content corresponding to the feedback information is related to the terminal information.
  • the terminal can extend the feedback information of Msg4.
  • the Msg4 feedback information is extended to 2 bits, and the 4 code points corresponding to the 2 bits correspond to different terminal types and decoding states. It is understandable that the feedback information of Msg4 can also be extended to more bits.
  • the feedback information is 2 bits.
  • the 2-bit value is 00
  • the feedback information is the NACK corresponding to the universal terminal
  • the 2-bit value is 01
  • the feedback information is the NACK corresponding to the RedCap terminal
  • the 2-bit value is 10
  • the feedback information is the NACK corresponding to the universal terminal
  • the corresponding ACK when the 2-bit value is 11, the feedback information is the ACK corresponding to the RedCap terminal.
  • Step S102 Receive the retransmitted Msg4.
  • the access network device can adjust Msg4.
  • the access network device if it receives a NACK on the special PUCCH resource, it indicates that the terminal is a RedCap terminal.
  • Msg4 contention resolution information
  • the access network device can adjust the load size in Msg4 so that the RedCap terminal can successfully decode Msg4 and successfully access the cell, thereby avoiding limiting the access failure of the RedCap terminal. This initiates the random access process.
  • the access network equipment does not adjust the load size in Msg4, it may result in the RedCap terminal being unable to access the cell.
  • the access network device After receiving the Msg4 feedback information, the access network device learns the 2-bit information corresponding to the feedback information.
  • the access network device adjusts the load size in Msg4 so that the RedCap terminal can successfully access the cell.
  • the feedback information received by the access network device is "00", it indicates that the terminal is a universal terminal.
  • Msg4 there is no need to adjust the payload size in Msg4, so there will be no impact on the access efficiency of general terminals.
  • the terminal can use feedback information to indicate terminal capability information.
  • the terminal may also use feedback information to indicate terminal capability information.
  • a special (special) PUCCH can be configured in the SIB, and the feedback information sent on the special PUCCH resource is NACK.
  • the feedback information indicates that the RedCap terminal is a low-capability RedCap terminal.
  • the terminal can also add terminal capability information to the feedback information.
  • the terminal can expand the feedback information of Msg4.
  • the feedback information of Msg4 is extended to 2 bits, and the 4 code points corresponding to 2 bits correspond to different terminal types. type and decoding status. It is understandable that the feedback information of Msg4 can also be extended to more bits.
  • the feedback information is 2 bits.
  • the 2-bit value is 00
  • the feedback information is the NACK corresponding to the normal RedCap terminal
  • the 2-bit value is 01
  • the feedback information is the NACK corresponding to the RedCap terminal with reduced capabilities
  • the 2-bit value is 10
  • the feedback information It is the ACK corresponding to normal RedCap
  • the value of 2 bits is 11, the feedback information is the ACK corresponding to the RedCap terminal with reduced capability.
  • the embodiment of the present invention also provides another random access method. Referring to Figure 2, detailed description will be given below through specific steps.
  • the random access method provided in the following steps S201 to S203 may be executed by the access network device.
  • the random access method provided in the following steps S201 to S203 can be executed by a chip with data processing capabilities in the access network equipment, or by a chip module including a data processing chip in the access network equipment. .
  • Step S201 Obtain terminal information.
  • the terminal can report its corresponding terminal information.
  • the terminal information may include any one of terminal type and terminal capability information, or the terminal information may include both terminal type and terminal capability information.
  • Terminal types include first-type terminals and second-type terminals, and first-type terminals and second-type terminals correspond to different processing capabilities.
  • the first type of terminal may be a general terminal, and the second type of terminal may be a RedCap terminal. Furthermore, the terminal type may also include a third type of terminal, and the third type of terminal is a low-capability RedCap terminal.
  • the terminal capability information may include at least one of the following: a supported maximum transport block size, a supported maximum number of HARQs, a supported processing time requirement, and a supported cache size.
  • the access network device can receive the terminal information reported by the terminal, and then learn that the terminal is a general terminal, a RedCap terminal, or a low-capability RedCap terminal. terminal. If the terminal information only includes terminal capability information, the access network device can learn whether the terminal is a normal-capability RedCap terminal or a low-capability RedCap terminal. If the terminal information includes terminal type and terminal capability information, the access network device can learn whether the terminal is a general terminal or a RedCap terminal, and whether the terminal is a low-capability RedCap terminal.
  • the terminal may report terminal information when sending the random access preamble.
  • terminal information can be carried through a random access preamble.
  • the terminal may indicate the terminal information through the resources used by the random access preamble.
  • the terminal may indicate the terminal type through the random access preamble, or may indicate the terminal type through the resources used by the random access preamble.
  • the terminal may also indicate the terminal capability information through the random access preamble, or indicate the terminal capability information through the resources used by the random access preamble.
  • the terminal indicates that the terminal type is a universal terminal or a RedCap terminal through a random access preamble.
  • the terminal can also report terminal capability information when scheduling uplink transmission (Msg3).
  • the terminal capability information can be used to indicate whether the RedCap terminal has restricted scheduled data. Amount of low-capability RedCap terminals.
  • the terminal information when the terminal schedules uplink transmission, the terminal information may be indicated by the information carried on the uplink.
  • the information carried on the uplink may be uplink scheduling information.
  • identification information is added to the uplink scheduling information, and the identification information indicates whether the RedCap terminal is a normal RedCap terminal or a low-capability RedCap terminal with limited scheduling data amount.
  • the uplink scheduling information carries Msg3normal LCID, indicating that the RedCap terminal is a normal RedCap terminal; if the uplink scheduling information, Carrying Msg3 new LCID indicates that the RedCap terminal is a low-capability RedCap terminal that limits the amount of scheduled data.
  • the terminal may not report terminal information when sending the random access preamble.
  • the terminal can report the terminal information as the terminal type when scheduling uplink transmission, thereby indicating whether the terminal is a universal terminal or a RedCap terminal.
  • the terminal when the terminal sends uplink scheduling information through PUSCH, the terminal adds identification information to the uplink scheduling information, and uses the identification information to indicate whether the terminal is a universal terminal or a RedCap terminal.
  • the uplink scheduling information carries Msg3 normal LCID, indicating that the terminal is a general terminal; if the uplink scheduling information carries Msg3 new LCID, it indicates that the terminal is RedCap terminal.
  • the terminal may also report terminal information when receiving Msg4.
  • the terminal after detecting that the contention resolution is successful, the terminal carries the terminal information through the feedback information when feeding back the physical downlink shared channel containing the terminal contention resolution identifier.
  • the terminal information is carried through feedback information.
  • a special (special) PUCCH can be configured in the SIB and NACK can be sent on the special PUCCH resource.
  • the terminal may indicate different terminal information through different feedback resources.
  • the terminal can also add terminal information to the feedback information, so that the content corresponding to the feedback information is related to the terminal information.
  • the terminal can extend the feedback information of Msg4.
  • the Msg4 feedback information is extended to 2 bits, and the 4 code points corresponding to the 2 bits correspond to different terminal types and decoding states. It is understandable that the feedback information of Msg4 can also be extended to more bits.
  • the feedback information is 2 bits.
  • the 2-bit value is 00
  • the feedback information is the NACK corresponding to the universal terminal
  • the 2-bit value is 01
  • the feedback information is the NACK corresponding to the RedCap terminal
  • the 2-bit value is 10
  • the feedback information is the NACK corresponding to the universal terminal
  • the corresponding ACK when the 2-bit value is 11, the feedback information is the ACK corresponding to the RedCap terminal.
  • Step S202 Adjust the load size carried by Msg4 according to the terminal type.
  • the access network device can adjust Msg4.
  • the access network device if the access network device receives a NACK on the special PUCCH resource, it indicates that the terminal is a RedCap terminal.
  • Msg4 contention resolution information
  • the access network device can adjust the load size in Msg4 so that the RedCap terminal can successfully decode Msg4 and successfully access the cell, thereby avoiding limiting the access failure of the RedCap terminal. This initiates the random access process.
  • the access network device adjusts the load size in Msg4 so that the RedCap terminal can successfully access the cell.
  • the feedback information received by the access network device is "00", it indicates that the terminal is a universal terminal.
  • Msg4 there is no need to adjust the payload size in Msg4, so there will be no impact on the access efficiency of general terminals.
  • Step S203 Retransmit Msg4 after load size adjustment.
  • the access network equipment after adjusting the load size in Msg4, the access network equipment
  • the device can re-deliver Msg4 after load size adjustment.
  • the terminal receives the Msg4 after the load size has been adjusted, so that it can correctly decode the Msg4 and successfully access the cell.
  • the access network device obtains the terminal type of the terminal and determines the information carried in the delivered Msg4 based on the terminal type. Therefore, corresponding Msg4 is issued for different terminal types (RedCap terminals and universal terminals), thereby ensuring that RedCap terminals can access normally without affecting the access efficiency of universal terminals.
  • an embodiment of the present invention also provides a random access device 30, including: a reporting unit configured to report terminal information during the process of performing random access.
  • the terminal information includes terminal type and/or terminal information. Capability information.
  • the random access device 30 may further include: a receiving unit 302, configured to receive the retransmitted Msg4 with the load size adjusted.
  • the above-mentioned reporting unit 301 and the receiving unit 302 may refer to the above-mentioned steps S101 to S102 correspondingly, which will not be described again here.
  • the above-mentioned random access device 30 may correspond to a chip with a data processing function in the terminal; or correspond to a chip module in the terminal including a chip with a data processing function, or correspond to the terminal.
  • FIG. 4 another random access device 40 in an embodiment of the present invention is shown, including: an acquisition unit 401, an adjustment unit 402 and a retransmission unit 403, wherein:
  • Obtaining unit 401 is used to obtain terminal information, where the terminal information includes terminal type and/or terminal capability information;
  • the adjustment unit 402 is configured to adjust the load size carried by Msg4 according to the terminal information
  • the retransmission unit 403 is used to retransmit Msg4 after load size adjustment.
  • the above-mentioned acquisition unit 401, adjustment unit 402 and retransmission unit 403 may refer to the above-mentioned steps S201 to S203 correspondingly, and will not be described again here.
  • the above-mentioned random access device 40 may correspond to the access network equipment A chip with a data processing function in the chip; or corresponding to a chip module including a chip with a data processing function in the access network equipment, or corresponding to the access network equipment.
  • each module/unit included in each device and product described in the above embodiments may be a software module/unit or a hardware module/unit, or it may be partly a software module/unit and partly is a hardware module/unit.
  • each module/unit included therein can be implemented in the form of hardware such as circuits, or at least some of the modules/units can be implemented in the form of a software program.
  • the software program Running on the processor integrated inside the chip, the remaining (if any) modules/units can be implemented using circuits and other hardware methods; for various devices and products applied to or integrated into the chip module, each module/unit included in it can They are all implemented in the form of hardware such as circuits.
  • Different modules/units can be located in the same component of the chip module (such as chips, circuit modules, etc.) or in different components. Alternatively, at least some modules/units can be implemented in the form of software programs.
  • the software program runs on the processor integrated inside the chip module, and the remaining (if any) modules/units can be implemented using circuits and other hardware methods; for each device or product that is applied to or integrated into the terminal, each module it contains /Units can all be implemented in the form of hardware such as circuits, and different modules/units can be located in the same component (for example, chip, circuit module, etc.) or in different components within the terminal, or at least some of the modules/units can be implemented in the form of software programs.
  • the software program runs on the processor integrated inside the terminal, and the remaining (if any) modules/units can be implemented using circuits and other hardware methods.
  • Embodiments of the present invention also provide a computer-readable storage medium.
  • the computer-readable storage medium is a non-volatile storage medium or a non-transitory storage medium, and a computer program is stored thereon.
  • the computer program is processed by a processor. During runtime, the steps of the random access method provided in steps S101 to S102 are executed, or the steps of the random access method provided in steps S201 to S203 are executed.
  • An embodiment of the present invention also provides a random access device, including a memory and a processor.
  • the memory stores a computer program that can be run on the processor.
  • the processor executes steps when running the computer program.
  • the program can be stored in a computer-readable storage medium.
  • the storage medium can include: ROM, RAM, magnetic disk or CD, etc.

Landscapes

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

Abstract

一种随机接入方法及装置、计算机可读存储介质，所述随机接入方法包括：在执行随机接入的过程中，上报终端信息，终端信息包括终端类型和/或终端能力信息。采用上述方案，能够实现在不影响通用终端接入效率的情况下，确保RedCap终端能够正常接入。

Description

随机接入方法及装置、计算机可读存储介质
本申请要求于2022年3月24日提交中国专利局、申请号为202210297059.6、发明名称为“随机接入方法及装置、计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术领域，尤其涉及一种随机接入方法及装置、计算机可读存储介质。
背景技术
第五代移动通信(5thgeneration communication system)系统定义了三大应用场景，包括增强型移动宽带(enhanced mobile broadband，eMBB)，超高可靠超低时延通信(ultra-reliable and low latency communication，URLLC)和海量机器类通信(massive machine type communications，mMTC)。
除以上场景之外,研究人员发现实际应用中还存在一些不属于这三大应用场景的新业务和新的终端类型，它们有着一定的、但远小于eMBB的传输速率需求，它们对时延的要求比URLLC要低但可能又比eMBB要高，它们还有着机器类通信的业务属性。针对这种新业务(新场景)定义了一种新的终端类型，这种终端类型被称为能力降低(ReducedCapability,RedCap)终端。
在同一个小区中，可能会同时存在通用终端和降低处理能力的RedCap终端。接入网设备(基站)在进行终端接入调度时，接入网设备无法获知终端类型，导致RedCap终端可能无法成功接入网络。
发明内容
本发明实施例解决的是接入网设备不知道终端类型，导致RedCap终端无法成功接入网络的技术问题。
为解决上述技术问题，本发明实施例提供一种随机接入方法，包括：在随机接入的过程中，上报终端信息，所述终端信息包括终端类型和/或终端能力信息。
可选的，所述上报终端信息，包括：在执行上行传输时，由上行链路承载的信息指示所述终端信息。
可选的，所述上报终端信息，包括：在发送随机接入前导码时，所述随机接入前导码或所述随机接入前导码所使用的资源用于指示所述终端信息；或，在发送随机接入前导码时，所述随机接入前导码或所述随机接入前导码所使用的资源用于指示所述终端类型，并在Msg3中承载所述终端能力信息。
可选的，所述终端类型至少包括不同处理能力的第一类终端和第二类终端。
可选的，所述终端的处理能力包括以下至少一种：支持的最大传输块尺寸、支持的最大HARQ数、支持的处理时间要求、支持的缓存大小。
可选的，所述上报终端信息，包括：在对包含有终端竞争解决标识的物理下行共享信道进行反馈时，通过反馈信息承载所述终端信息。
可选的，所述随机接入方法还包括：在检测到由临时小区无线网络临时标识加扰的下行控制信息调度了下行控制数据共享信道，且未能成功解码该下行控制数据共享信道或该下行控制数据共享信道的数据不与终端类型匹配或超出终端能力时，通过反馈信息承载所述终端信息。
可选的，所述通过反馈信息承载所述终端信息，其特征在于，包括：通过不同的反馈资源指示不同的所述终端信息。
可选的，所述通过反馈信息承载所述终端信息，其特征在于，还包括：通过反馈信息指示的不同码点指示不同的所述终端信息。
本发明实施例还提供了一种随机接入方法，包括：获取终端信息，所述终端信息包括终端类型和/或终端能力信息；根据所述终端信息，对Msg4承载的负载大小进行调整；重传经过负载大小调整后的Msg4。
可选的，所述获取终端信息，包括：接收随机接入前导码，所述随机接入前导码或所述随机接入前导码使用的资源用于指示所述终端信息；或，接收随机接入前导码以及Msg3，所述随机接入前导码或所述随机接入前导码使用的资源用于指示所述终端类型，所述Msg3承载所述终端能力信息。
可选的，所述终端类型包括不同处理能力的第一类终端以及第二类终端。
可选的，所述获取终端信息，包括：接收反馈信息，所述反馈信息用于承载所述终端信息。
可选的，所述反馈信息中不同的反馈资源指示不同的终端信息。
可选的，所述反馈信息中的不同码点指示不同的终端信息。
本发明实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行上述任一种所述的随机接入方法的步骤。
本发明实施例还提供了另一种随机接入装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述任一种所述的随机接入方法 的步骤。
与现有技术相比，本发明实施例的技术方案具有以下有益效果：
在本发明实施例中，在执行随机接入的过程中，终端上报终端信息，使得接入网设备获知终端对应的终端信息。接入网设备根据终端信息，确定下发的Msg4中携带的信息。因此，针对不同的终端信息，下发对应的Msg4，从而实现在不影响通用终端接入效率的情况下，确保RedCap终端能够正常接入。
附图说明
图1是本发明实施例中的一种随机接入方法的流程图；
图2是本发明实施例中的另一种随机接入方法的流程图；
图3是本发明实施例中的一种随机接入装置的结构示意图；
图4是本发明实施例中的另一种随机接入装置的结构示意图。
具体实施方式
如上述背景技术中所述，同一个小区中，可能会同时存在通用终端和降低处理能力的RedCap终端。通用终端可以为eMBB终端、URLLC终端、mMTC终端等。接入网设备在进行接入调度时，并不知道终端类型。
若基于通用终端的能力进行调度，则RedCap终端可能无法成功接收Msg4，导致RedCap终端无法成功接入小区；若基于RedCap终端的能力进行调度，由于Msg4中的RRC配置信息对应的信息量较大，则在Msg4中不能携带RRC配置消息，进而导致通用终端的初始接入效率会被影响。
在本发明实施例中，在执行随机接入的过程中，终端上报终端信息，使得接入网设备获知终端对应的终端信息。接入网设备根据终端 信息，确定下发的Msg4中携带的信息。因此，针对不同的终端信息，下发对应的Msg4，从而实现在不影响通用终端接入效率的情况下，确保RedCap终端能够正常接入。
为使本发明的上述目的、特征和有益效果能够更为明显易懂，下面结合附图对本发明的具体实施例做详细的说明。
本发明实施例中所述的终端是一种具有无线通信功能的设备，可以称为用户设备(User Equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、接入终端设备、车载终端设备、工业控制终端设备、UE单元、UE站、移动站、远方站、远程终端设备、移动设备、UE终端设备、无线通信设备、UE代理或UE装置等。用户设备可以是固定的或者移动的。需要说明的是，用户设备可以支持至少一种无线通信技术，例如LTE、新空口(new radio，NR)等。例如，用户设备可以是手机(mobile phone)、平板电脑(pad)、台式机、笔记本电脑、一体机、车载终端、虚拟现实(virtual reality，VR)用户设备、增强现实(augmented reality，AR)用户设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、可穿戴设备、未来移动通信网络中的用户设备或者未来演进的公共移动陆地网络(public land mobile network，PLMN)中的用户设备等。在本申请的一些实施例中，用户设备还可以是具有收发功能的装置，例如芯片系统。其中，芯片系统可以包括芯片，还可以包括其它分立器件。
在本发明实施例中，接入网设备是一种为终端提供无线通信功能 的设备，也可称之为无线接入网(radio access network，RAN)设备、或接入网网元等。其中，接入网设备可以支持至少一种无线通信技术，例如LTE、NR等。示例的，接入网设备包括但不限于：第五代移动通信系统(5th-generation，5G)中的下一代基站(generation nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站接收台(base transceiver station，BTS)、家庭基站(例如，home evolved node B、或home node B，HNB)、基带单元(baseband unit，BBU)、接收点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)、和/或分布单元(distributed unit，DU)，或者接入网设备可以为中继站、接入点、车载设备、终端设备、可穿戴设备以及未来移动通信中的接入网设备或者未来演进的PLMN中的接入网设备等。在一些实施例中，接入网设备还可以为具有为终端设备提供无线通信功能的装置，例如芯片系统。示例的，芯片系统可以包括芯片，还可以包括其它分立器件。
在一些实施例中，接入网设备还可以与互联网协议(Internet Protocol，IP)网络进行通信，例如因特网(internet)，私有的IP网，或其他数据网等。
本发明实施例提供了一种随机接入方法，参照图1，以下通过具体步骤进行详细说明。
在本发明实施例中，下述步骤S101～步骤S102所提供的随机接入方法可以由终端所执行。具体的，下述步骤S101～步骤S102所提供的随机接入方法可以由终端中具有数据处理能力的芯片所执行，或者由终端中包含数据处理芯片的芯片模组所执行。
步骤S101，在执行随机接入的过程中，上报终端信息。
在具体实施中，终端可以上报自身对应的终端信息。终端信息可以包括终端类型与终端能力信息中的任一种，或者，终端信息可以同时包括终端类型以及终端能力信息。终端类型包括第一类终端以及第二类终端，第一类终端与第二类终端对应不同的处理能力。
在本发明实施例中，第一类终端可以为通用终端，第二类终端可以为RedCap终端。进一步，终端类型还可以包括第三类终端，第三类终端为低能力RedCap终端。
在本发明实施例中，终端能力信息可以包括以下至少一种：支持的最大传输块尺寸、支持的最大HARQ数、支持的处理时间要求、支持的缓存大小。
若终端信息仅包括终端类型，则接入网设备可以接收终端上报的终端信息，进而获知终端为通用终端、RedCap终端、低能力RedCap终端。若终端信息仅包括终端能力信息，则接入网设备可以获知终端为正常能力的RedCap终端还是低能力的RedCap终端。若终端信息包括终端类型以及终端能力信息，则接入网设备可以获知终端为通用终端还是RedCap终端，以及，终端是否为低能力RedCap终端。
在现有技术中，随机接入过程可以包括四步随机接入过程，具体包括如下步骤：
第一步，终端向接入网设备发送随机接入前导码(Random Access Preamble)传输(Msg1)。
第二步，接入网设备向终端发送随机接入响应(RAR)(Msg2)。
在接收到随机接入前导码后，接入网设备通过PDSCH发送RA响应。RA响应包括RA前导码标识符、时间调整信息、初始上行链路调度和临时C-RNTI。一个PDSCH可以携带RA响应至多个终端。在终端发送随机接入前导码之后，监听PDCCH并在RA响应窗口内等待RA响应。
如果终端接收到RA preamble标识符的响应，该标识符与包含所 发送的RA preamble标识符相同，则响应成功，终端发送上行链路调度信息。
如果终端没有在RA响应窗口内接收到响应或未能验证响应，则响应失败。在这种情况下，如果RA尝试次数小于上限(如10次)，则终端重试RA；否则，RA失败。
第三步，调度上行传输(Msg3)。
终端通过PUSCH发送上行链路调度信息。
第四步，竞争解决(Msg4)。
终端在发送Msg3之后，竞争解决计时器开始计时。接入网设备使用PDCCH上的C-RNTI或PDSCH上的UE竞争解决标识(IE)来帮助终端进行竞争解决。终端在正确解码Msg4之后反馈肯定回答。终端在竞争解决计时器过期之前继续监听PDCCH。
上述四步随机接入过程的具体过程可以对应参照现有协议。
在具体实施中，终端可以在发送随机接入前导码时，上报终端信息。具体而言，可以通过随机接入前导码承载终端信息。或者，终端可以通过随机接入前导码所使用的资源来指示终端信息。
在本发明实施例中，终端可以通过随机接入前导码指示终端类型，或者，通过随机接入前导码使用的资源指示终端类型。
终端也可以通过随机接入前导码指示终端能力信息，或者，通过随机接入前导码使用的资源指示终端能力信息。
在本发明实施例中，终端通过随机接入前导码指示终端类型为通用终端或者RedCap终端。
若终端通过随机接入前导码指示终端类型为RedCap终端，则终端在调度上行传输(Msg3)时，还可以上报终端能力信息，该终端能力信息可以用于指示该RedCap终端是否为限制了调度数据量的低能力RedCap终端。
在本发明实施例中，终端可以在调度上行传输时，可以由上行链路承载的信息指示终端信息。具体而言，上行链路承载的信息可以为上行链路调度信息。
在本发明一实施例中，在上行链路调度信息中增加标识信息，通过该标识信息指示RedCap终端为正常RedCap终端还是限制了调度数据量的低能力RedCap终端。
具体而言，在发送Msg1的时候指示终端类型是否为RedCap终端。进一步的在Msg1指示了是RedCap终端之后，若终端为正常RedCap终端，则在上行链路调度信息中，携带Msg3 normal LCID，指示该RedCap终端为正常RedCap终端；若上行链路调度信息中，携带Msg3 new LCID，则指示该RedCap终端为限制了调度数据量的低能力RedCap终端。
在具体实施中，终端在发送随机接入前导码时，可能并未上报终端信息。终端可以在调度上行传输时，上报终端终端信息为终端类型，因此来指示终端为通用终端还是RedCap终端。
具体而言，终端在通过PUSCH发送上行链路调度信息时，在上行链路调度信息中增加标识信息，通过该标识信息指示终端为通用终端还是RedCap终端。
具体而言，若终端为通用终端，则在上行链路调度信息中，携带Msg3 normal LCID，指示该终端为通用终端；若上行链路调度信息中，携带Msg3 new LCID，则指示该终端为RedCap终端。
在具体实施中，终端也可以在接收Msg4时，上报终端信息。
在本发明实施例中，终端在检测到竞争解决成功后，在对包含有终端竞争解决标识的物理下行共享信道进行反馈时，通过反馈信息承载终端信息。
具体而言，对于通用终端，在接收完成Msg4后，在SIB配置的公共(common)PUCCH发送反馈信息。对于RedCap终端，在检测 到由临时小区无线网络临时标识加扰的下行控制信息调度了下行控制数据共享信道，且未能成功解码该下行控制数据共享信道或该下行控制数据共享信道的数据不与终端类型匹配或超出终端能力时，通过反馈信息承载所述终端信息。
具体而言，对于RedCap终端，其在解码PDCCH时，若Msg4的负载大小(payload size)超出终端承载能力，则可以在SIB中配置特殊(special)PUCCH，并在special PUCCH资源上发送NACK。
在具体实施中，终端可以通过不同的反馈资源指示不同的终端信息。终端还可以在反馈信息中增加终端信息，使得反馈信息对应的内容与终端信息相关。
在本发明实施例中，终端可以对Msg4的反馈信息进行扩展。例如，将Msg4的反馈信息扩展至2比特，2比特对应的4个码点对应不同的终端类型以及解码状态。可以理解的是，也可以将Msg4的反馈信息扩展至更多比特。
在本发明一实施例中，反馈信息为2比特。当2比特取值为00时，反馈信息为通用终端对应的NACK；当2比特取值为01时，反馈信息为RedCap终端对应的NACK；当2比特取值为10时，反馈信息为通用终端对应的ACK；当2比特取值为11时，反馈信息为RedCap终端对应的ACK。
步骤S102，接收重传的Msg4。
在具体实施中，接入网设备在获知终端信息之后，若终端为RedCap终端，则接入网设备可以对Msg4进行调整。
在本发明实施例中，若接入网设备在special PUCCH资源上收到NACK，则表示该终端为RedCap终端。在重传Msg4(竞争解决信息)时，接入网设备可以对Msg4中的负载大小进行调整，以使得RedCap终端能够成功解码Msg4并成功接入小区，从而避免限制了RedCap终端接入失败而在此发起随机接入过程。
并且，若接入网设备不对Msg4中的负载大小进行调整，则可能会导致RedCap终端始终无法接入到小区。
接入网设备在接收到Msg4的反馈信息后，获知反馈信息对应的2比特信息。
在本发明实施例中，若将Msg4的反馈信息扩展至2比特，接入网设备接收到的反馈信息为“01”，则表征该终端为RedCap终端。在重传Msg4时，接入网设备对Msg4中的负载大小进行调整，使得RedCap终端能够成功接入小区。
若接入网设备接收到的反馈信息为“00”，则表征该终端为通用终端。在重传Msg4时，无需对Msg4中的负载大小进行调整，由此，不会对通用终端的接入效率产生影响。
需要说明的是，上述2比特的反馈信息中不同码点承载的信息仅为示例性说明。在具体应用中，可以根据具体的应用场景来设定不同码点承载的信息。
在具体实施中，若终端在发送随机接入前导码时，指示终端类型为RedCap终端，且终端没有在Msg3上上报终端能力信息，则终端可以使用反馈信息来指示终端能力信息。或者，终端在调度上行传输时，指示终端为RedCap终端，则终端也可以使用反馈信息来指示终端能力信息。
在本发明实施例中，对于低能力的RedCap终端，可以在SIB中配置特殊(special)PUCCH，并在special PUCCH资源上发送的反馈信息为NACK。由此，通过反馈信息指示该RedCap终端为低能力RedCap终端。
在本发明实施例中，终端还可以在反馈信息中增加终端能力信息。
此时，终端可以对Msg4的反馈信息进行扩展。例如，将Msg4的反馈信息扩展至2比特，2比特对应的4个码点对应不同的终端类 型以及解码状态。可以理解的是，也可以将Msg4的反馈信息扩展至更多比特。
在本发明一实施例中，反馈信息为2比特。当2比特取值为00时，反馈信息为正常RedCap终端对应的NACK；当2比特取值为01时，反馈信息为能力降低RedCap终端对应的NACK；当2比特取值为10时，反馈信息为正常RedCap对应的ACK；当2比特取值为11时，反馈信息为能力降低RedCap终端对应的ACK。
本发明实施例还提供了另一种随机接入方法，参照图2，以下通过具体步骤进行详细说明。
在本发明实施例中，下述步骤S201～步骤S203所提供的随机接入方法可以由接入网设备所执行。具体的，下述步骤S201～步骤S203所提供的随机接入方法可以由接入网设备中具有数据处理能力的芯片所执行，或者由接入网设备中包含数据处理芯片的芯片模组所执行。
步骤S201，获取终端信息。
在具体实施中，终端可以上报自身对应的终端信息。终端信息可以包括终端类型与终端能力信息中的任一种，或者，终端信息可以同时包括终端类型以及终端能力信息。终端类型包括第一类终端以及第二类终端，第一类终端与第二类终端对应不同的处理能力。
在本发明实施例中，第一类终端可以为通用终端，第二类终端可以为RedCap终端。进一步，终端类型还可以包括第三类终端，第三类终端为低能力RedCap终端。
在本发明实施例中，终端能力信息可以包括以下至少一种：支持的最大传输块尺寸、支持的最大HARQ数、支持的处理时间要求、支持的缓存大小。
若终端信息仅包括终端类型，则接入网设备可以接收终端上报的终端信息，进而获知终端为通用终端、RedCap终端、低能力RedCap 终端。若终端信息仅包括终端能力信息，则接入网设备可以获知终端为正常能力的RedCap终端还是低能力的RedCap终端。若终端信息包括终端类型以及终端能力信息，则接入网设备可以获知终端为通用终端还是RedCap终端，以及，终端是否为低能力RedCap终端。
在具体实施中，终端可以在发送随机接入前导码时，上报终端信息。具体而言，可以通过随机接入前导码承载终端信息。或者，终端可以通过随机接入前导码所使用的资源来指示终端信息。
在本发明实施例中，终端可以通过随机接入前导码指示终端类型，或者，通过随机接入前导码使用的资源指示终端类型。
终端也可以通过随机接入前导码指示终端能力信息，或者，通过随机接入前导码使用的资源指示终端能力信息。
在本发明实施例中，终端通过随机接入前导码指示终端类型为通用终端或者RedCap终端。
若终端通过随机接入前导码指示终端类型为RedCap终端，则终端在调度上行传输(Msg3)时，还可以上报终端能力信息，该终端能力信息可以用于指示该RedCap终端是否为限制了调度数据量的低能力RedCap终端。
在本发明实施例中，终端可以在调度上行传输时，可以由上行链路承载的信息指示终端信息。具体而言，上行链路承载的信息可以为上行链路调度信息。
在本发明一实施例中，在上行链路调度信息中增加标识信息，通过该标识信息指示RedCap终端为正常RedCap终端还是限制了调度数据量的低能力RedCap终端。
具体而言，在发送Msg1的时候指示终端类型是否为RedCap终端。进一步的在Msg1指示了是RedCap终端之后，若终端为正常RedCap终端，则在上行链路调度信息中，携带Msg3normal LCID，指示该RedCap终端为正常RedCap终端；若上行链路调度信息中， 携带Msg3 new LCID，则指示该RedCap终端为限制了调度数据量的低能力RedCap终端。
在具体实施中，终端在发送随机接入前导码时，可能并未上报终端信息。终端可以在调度上行传输时，上报终端终端信息为终端类型，因此来指示终端为通用终端还是RedCap终端。
具体而言，终端在通过PUSCH发送上行链路调度信息时，在上行链路调度信息中增加标识信息，通过该标识信息指示终端为通用终端还是RedCap终端。
具体而言，若终端为通用终端，则在上行链路调度信息中，携带Msg3 normal LCID，指示该终端为通用终端；若上行链路调度信息中，携带Msg3 new LCID，则指示该终端为RedCap终端。
在具体实施中，终端也可以在接收Msg4时，上报终端信息。
在本发明实施例中，终端在检测到竞争解决成功后，在对包含有终端竞争解决标识的物理下行共享信道进行反馈时，通过反馈信息承载终端信息。
具体而言，对于通用终端，在接收完成Msg4后，在SIB配置的公共(common)PUCCH发送反馈信息。对于RedCap终端，在检测到由临时小区无线网络临时标识加扰的下行控制信息调度了下行控制数据共享信道，且未能成功解码该下行控制数据共享信道或该下行控制数据共享信道的数据不与终端类型匹配或超出终端能力时，通过反馈信息承载所述终端信息。
具体而言，对于RedCap终端，其在解码PDCCH时，若Msg4的负载大小(payload size)超出终端承载能力，则可以在SIB中配置特殊(special)PUCCH，并在special PUCCH资源上发送NACK。
在具体实施中，终端可以通过不同的反馈资源指示不同的终端信息。终端还可以在反馈信息中增加终端信息，使得反馈信息对应的内容与终端信息相关。
在本发明实施例中，终端可以对Msg4的反馈信息进行扩展。例如，将Msg4的反馈信息扩展至2比特，2比特对应的4个码点对应不同的终端类型以及解码状态。可以理解的是，也可以将Msg4的反馈信息扩展至更多比特。
在本发明一实施例中，反馈信息为2比特。当2比特取值为00时，反馈信息为通用终端对应的NACK；当2比特取值为01时，反馈信息为RedCap终端对应的NACK；当2比特取值为10时，反馈信息为通用终端对应的ACK；当2比特取值为11时，反馈信息为RedCap终端对应的ACK。
步骤S202，根据所述终端类型，对Msg4承载的负载大小进行调整。
在具体实施中，接入网设备在获知终端类型之后，若终端为RedCap终端，则接入网设备可以对Msg4进行调整。
在本发明实施例中，若接入网设备在special PUCCH资源上收到NACK，则表示该终端为RedCap终端。在重传Msg4(竞争解决信息)时，接入网设备可以对Msg4中的负载大小进行调整，以使得RedCap终端能够成功解码Msg4并成功接入小区，从而避免限制了RedCap终端接入失败而在此发起随机接入过程。
在本发明实施例中，若将Msg4的反馈信息扩展至2比特，接入网设备接收到的反馈信息为“01”，则表征该终端为RedCap终端。在重传Msg4时，接入网设备对Msg4中的负载大小进行调整，使得RedCap终端能够成功接入小区。
若接入网设备接收到的反馈信息为“00”，则表征该终端为通用终端。在重传Msg4时，无需对Msg4中的负载大小进行调整，由此，不会对通用终端的接入效率产生影响。
步骤S203，重传经过负载大小调整后的Msg4。
在具体实施中，在对Msg4中的负载大小进行调整后，接入网设 备可以重新下发经过负载大小调整后的Msg4。终端接收经过负载大小调整后的Msg4，从而可以正确解码Msg4，并成功接入小区。
由此可见，接入网设备获取终端的终端类型，根据终端类型，确定下发的Msg4中携带的信息。因此，针对不同的终端类型(RedCap终端与通用终端)，下发对应的Msg4，从而实现在不影响通用终端接入效率的情况下，确保RedCap终端能够正常接入。
参照图3，本发明实施例还提供了一种随机接入装置30，包括：上报单元，用于在执行随机接入的过程中，上报终端信息，所述终端信息包括终端类型和/或终端能力信息。
在具体实施中，随机接入装置30还可以包括：接收单元302，用于接收重传的经过负载大小调整的Msg4。
在具体实施中，上述的上报单元301以及接收单元302可以对应参照上述步骤S101～步骤S102，此处不做赘述。
在具体实施中，上述的随机接入装置30可以对应于终端中具有数据处理功能的芯片；或者对应于终端中包括具有数据处理功能的芯片的芯片模组，或者对应于终端。
参照图4，给出了本发明实施例中的另一种随机接入装置40，包括：获取单元401、调整单元402以及重传单元403，其中：
获取单元401，用于获取终端信息，所述终端信息包括终端类型和/或终端能力信息；
调整单元402，用于根据所述终端信息，对Msg4承载的负载大小进行调整；
重传单元403，用于重传经过负载大小调整后的Msg4。
在具体实施中，上述的获取单元401、调整单元402以及重传单元403可以对应参照上述步骤S201～步骤S203，此处不做赘述。
在具体实施中，上述的随机接入装置40可以对应于接入网设备 中具有数据处理功能的芯片；或者对应于接入网设备中包括具有数据处理功能的芯片的芯片模组，或者对应于接入网设备。
在具体实施中，关于上述实施例中描述的各个装置、产品包含的各个模块/单元，其可以是软件模块/单元，也可以是硬件模块/单元，或者也可以部分是软件模块/单元，部分是硬件模块/单元。
例如，对于应用于或集成于芯片的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于芯片模组的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于芯片模组的同一组件(例如芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片模组内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于终端的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于终端内同一组件(例如，芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于终端内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现。
本发明实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行步骤S101～步骤S102所提供的随机接入方法的步骤，或者执行步骤S201～步骤S203所提供的随机接入方法的步骤。
本发明实施例还提供了一种随机接入装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行步骤S101～步骤S102所提供的随 机接入方法的步骤，或者执行步骤S201～步骤S203所提供的随机接入方法的步骤。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指示相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：ROM、RAM、磁盘或光盘等。
虽然本发明披露如上，但本发明并非限定于此。任何本领域技术人员，在不脱离本发明的精神和范围内，均可作各种更动与修改，因此本发明的保护范围应当以权利要求所限定的范围为准。

Claims (19)

  1. 一种随机接入方法，其特征在于，包括：
    在随机接入的过程中，上报终端信息，所述终端信息包括终端类型和/或终端能力信息。
  2. 如权利要求1所述的随机接入方法，其特征在于，所述上报终端信息，包括：
    在执行上行传输时，由上行链路承载的信息指示所述终端信息。
  3. 如权利要求1所述的随机接入方法，其特征在于，所述上报终端信息，包括：
    在发送随机接入前导码时，所述随机接入前导码或所述随机接入前导码所使用的资源用于指示所述终端信息；
    或，
    在发送随机接入前导码时，所述随机接入前导码或所述随机接入前导码所使用的资源用于指示所述终端类型，并在Msg3中承载所述终端能力信息。
  4. 如权利要求3所述的随机接入方法，其特征在于，所述终端类型至少包括不同处理能力的第一类终端和第二类终端
  5. 如权利要求3所述的随机接入方法，其特征在于，所述终端能力信息包括以下至少一种：支持的最大传输块尺寸、支持的最大HARQ数、支持的处理时间要求、支持的缓存大小。
  6. 如权利要求1所述的随机接入方法，其特征在于，所述上报终端信息，包括：
    在对包含有终端竞争解决标识的物理下行共享信道进行反馈时，通过反馈信息承载所述终端信息。
  7. 如权利要求6所述的随机接入方法，其特征在于，还包括：
    在检测到由临时小区无线网络临时标识加扰的下行控制信息调度了下行控制数据共享信道，且未能成功解码该下行控制数据共享信道或该下行控制数据共享信道的数据不与终端类型匹配或超出终端能力时，通过反馈信息承载所述终端信息。
  8. 如权利要求7所述的随机接入方法，所述通过反馈信息承载所述终端信息，其特征在于，包括：
    通过不同的反馈资源指示不同的所述终端信息。
  9. 如权利要求7所述的随机接入方法，所述通过反馈信息承载所述终端信息，其特征在于，还包括：
    通过反馈信息指示的不同码点指示不同的所述终端信息。
  10. 一种随机接入方法，其特征在于，包括：
    获取终端信息，所述终端信息包括终端类型和/或终端能力信息；
    根据所述终端信息，对Msg4承载的负载大小进行调整；
    重传经过负载大小调整后的Msg4。
  11. 如权利要求10所述的随机接入方法，其特征在于，所述获取终端信息，包括：接收随机接入前导码，所述随机接入前导码或所述随机接入前导码使用的资源用于指示所述终端信息；
    或，
    接收随机接入前导码以及Msg3，所述随机接入前导码或所述随机接入前导码使用的资源用于指示所述终端类型，所述Msg3承载所述终端能力信息。
  12. 如权利要求10所述的随机接入方法，其特征在于，所述终端类型包括不同处理能力的第一类终端以及第二类终端。
  13. 如权利要求10所述的随机接入方法，其特征在于，所述获取终端信息，包括：接收反馈信息，所述反馈信息用于承载所述终端信息。
  14. 如权利要求13所述的随机接入方法，其特征在于，所述反馈信息中不同的反馈资源指示不同的终端信息。
  15. 如权利要求13所述的随机接入方法，其特征在于，所述反馈信息中的不同码点指示不同的终端信息。
  16. 一种随机接入装置，其特征在于，包括：
    上报单元，用于在执行随机接入的过程中，上报终端信息，所述终端信息包括终端类型和/或终端能力信息。
  17. 一种随机接入装置，其特征在于，包括：
    获取单元，用于获取终端信息，所述终端信息包括终端类型和/或终端能力信息；
    调整单元，用于根据所述终端信息，对Msg4承载的负载大小进行调整；
    重传单元，用于重传经过负载大小调整后的Msg4。
  18. 一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器运行时执行权利要求1～17任一项所述的随机接入方法的步骤。
  19. 一种随机接入装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，其特征在于，所述处理器运行所述计算机程序时执行权利要求1～9任一项所述的随机接入方法的步骤，或者，执行权利要求10～17任一项所述的随机接入方法的步骤。
PCT/CN2023/083557 2022-03-24 2023-03-24 随机接入方法及装置、计算机可读存储介质 WO2023179743A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210297059.6A CN116847471A (zh) 2022-03-24 2022-03-24 随机接入方法及装置、计算机可读存储介质
CN202210297059.6 2022-03-24

Publications (1)

Publication Number Publication Date
WO2023179743A1 true WO2023179743A1 (zh) 2023-09-28

Family

ID=88100077

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/083557 WO2023179743A1 (zh) 2022-03-24 2023-03-24 随机接入方法及装置、计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN116847471A (zh)
WO (1) WO2023179743A1 (zh)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113316218A (zh) * 2020-02-27 2021-08-27 华为技术有限公司 接入方法及装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113316218A (zh) * 2020-02-27 2021-08-27 华为技术有限公司 接入方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "TP for UE identification and access restriction", 3GPP TSG RAN WG2 #113E, R2-2100985, 15 January 2021 (2021-01-15), XP051974028 *
OPPO: "Other considerations for reduced UE capability", 3GPP TSG RAN WG1 #104E, R1-2100167, 18 January 2021 (2021-01-18), XP051970285 *

Also Published As

Publication number Publication date
CN116847471A (zh) 2023-10-03

Similar Documents

Publication Publication Date Title
US11984989B2 (en) Transmission method and apparatus
US8428066B2 (en) Method and apparatus for reporting carrier status
EP3557776B1 (en) Data transmission method, communication device and data transmission system
US10931334B2 (en) Beam recovery method and apparatus
JP2010045790A (ja) Ｔｔｉバンドルの再送を処理する方法及び通信装置
WO2021022408A1 (zh) 随机接入消息发送方法、装置及存储介质
JP7509805B2 (ja) ランダムアクセス方法、端末デバイス及びネットワークデバイス
US9843420B2 (en) Cross carrier scheduling method and apparatus
CN114071776A (zh) 通信方法、用户设备、网络设备及电子设备
EP3364583A1 (en) Information transmission method, terminal and base station
WO2022006914A1 (zh) 混合自动重传请求应答harq-ack的反馈方法和终端设备
US20240032028A1 (en) Cg resource processing method, terminal device, and network device
EP4030666A1 (en) Method for processing hybrid automatic repeat request, and communication apparatus
EP3570607B1 (en) Reducing the transmission delay and improving the reliability of uplink data
WO2018086707A1 (en) Feedback based flexible transmission scheme for contention-based urllc transmission
US20220140957A1 (en) HARQ Feedback Technique for Communication Systems
WO2023179743A1 (zh) 随机接入方法及装置、计算机可读存储介质
CN108702691B (zh) 一种发送通信消息的方法和装置
WO2022001893A1 (zh) 确定数据传输方式的方法及装置
KR20220165755A (ko) 사이드링크 피드백 정보를 송신 및 수신하기 위한 방법 및 장치
CN108924965B (zh) 一种非连续传输检测的方法、装置、基站及终端
JP2023515755A (ja) 情報フィードバック方法及び関連デバイス
WO2024017290A1 (zh) 通信方法及装置、计算机可读存储介质
CN110831228B (zh) 一种通信方法及装置
US20230232466A1 (en) Access method and related device

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: 23773988

Country of ref document: EP

Kind code of ref document: A1