Counting method and communication device

Abstract

The invention provides a counting method and a communication device, and relates to the technical field of communication, and the method comprises the steps that terminal equipment counts the transmission times of a first message. And the terminal equipment receives a second message, the second message is used for indicating to send a third message within the time T, and when the processing time of scheduling the third message by the terminal equipment is greater than the time T, the counting rule is adjusted. According to the invention, waste of access opportunities in a random access process can be reduced.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a counting method and a communication device. Background Art

[0002] In the R17 (release 17) and R18 (release 18) versions of wireless communication technology of the third generation partnership project (3GPP), reduced capability (RedCap) type and enhanced reduced capability (eRedCap) type terminal devices were introduced. Compared with conventional NR terminals, RedCap and eRedCap terminals have lower cost and complexity, smaller form factor and longer battery life, but are more restricted in processing power and time and frequency resources. For RedCap and eRedCap terminals, how to reduce the waste of access opportunities during random access is a key issue currently faced. Summary of the invention

[0003] The present application provides a counting method and a communication device, which are beneficial to reducing the waste of access opportunities during random access.

[0004] In the first aspect, the present application provides a counting method. The method provided in the first aspect can be executed by a terminal device, or by a module applied to the terminal device (such as a processor, chip, or chip system, etc.), or by a logical node, logical module or software that can implement all or part of the terminal device functions. The present application does not limit this.

[0005] Specifically, the method can be used in a random access process of a terminal device, including: the terminal device counts the number of transmissions of a first message. The first message is used to indicate the reception of a second message. The terminal device receives the second message, and the second message is used to indicate the transmission of a third message within a time T. When the processing time of the third message scheduled by the terminal device is greater than the time T, the counting rule is adjusted. Or the terminal device receives a fourth message, and when the bandwidth that the terminal device can process is less than the transmission bandwidth of the fourth message, the counting rule is adjusted, wherein the first message, the second message, the third message, and the fourth message are used in the random access process of the terminal device.

[0006] Based on the above technical solution, after the terminal device receives the second message indicating to send the third message within time T, when the processing time of the third message scheduled by the terminal device is greater than time T, by adjusting the counting rule, the terminal device can reduce the waste of random access opportunities caused by processing capacity limitation. On the other hand, when the bandwidth that the terminal device can process is less than the transmission bandwidth of the fourth message, by adjusting the counting rule, the terminal device can reduce the waste of random access opportunities caused by processing bandwidth limitation.

[0007] In an embodiment of the present application, the first message is message 1 in the random access process, wherein message 1 includes a random access preamble code, the second message is message 2, the third message is message 3, and the fourth message is message 4.

[0008] In combination with the first aspect, in some implementations of the first aspect, adjusting the counting rule includes not counting the next time the terminal device sends the first message, or increasing the maximum number of times the first message is sent.

[0009] Based on the above technical solution, by instructing the counter not to count the next time the terminal device sends the first message, or increasing the maximum number of times the first message is sent in the counter, the terminal device can obtain more random access opportunities, thereby avoiding the waste of random access opportunities caused by random access failure.

[0010] In combination with the first aspect, in some implementations of the first aspect, the terminal device sends a third message, where the third message is used to indicate reception of a fourth message.

[0011] Optionally, the first message or the third message further includes identification information of the terminal device, where the identification information is used to indicate the type of the terminal device.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the terminal device receives a fifth message, and the fifth message is used to indicate that no counting is performed when the terminal device sends the first message next time, or the maximum number of times the first message is sent is increased.

[0013] Based on the above technical solution, the embodiment of the present application indicates the counting rule of the counter through the fifth message, thereby improving processing efficiency and avoiding waste of resources of the terminal device.

[0014] In combination with the first aspect, in some implementations of the first aspect, the terminal device includes a reduced-capability RedCap type terminal device and an enhanced reduced-capability eRedCap type terminal device.

[0015] On the second aspect, the present application provides a counting method. The method provided in the second aspect can be executed by a network device, or by a module applied to the network device (such as a processor, chip, or chip system, etc.), or by a logical node, logical module or software that can realize all or part of the functions of the network device. The present application does not limit this.

[0016] Specifically, the method can be used in a random access process of a network device, including: the network device counts the number of transmissions of a first message. The first message is used to indicate the sending of a second message. The network device sends the second message, and the second message is used to indicate the receiving of a third message within a time T. When the network device does not receive the third message within the time T, the counting rule is adjusted. The first message, the second message, and the third message are used in a random access process of a terminal device.

[0017] In this embodiment of the present application, the first message is message 1 in the random access process, the second message is message 2, and the third message is message 3.

[0018] In combination with the second aspect, in some implementations of the second aspect, adjusting the counting rule includes not counting the next time the network device receives the first message, or increasing the maximum number of times the first message is received.

[0019] In combination with the second aspect, in certain implementations of the second aspect, when it is determined that the processing time of the third message scheduled by the terminal device is greater than time T, a fifth message is sent, and the fifth message is used to instruct the terminal device not to count the next time it sends the first message, or to increase the maximum number of times the first message is sent.

[0020] In combination with the second aspect, in certain implementations of the second aspect, the network device receives a third message, the third message is used to determine a fourth message, and when it is determined that the bandwidth that the terminal device can process is less than the transmission bandwidth of the fourth message, a fifth message is sent, wherein the fourth message is used for a random access process of the terminal device.

[0021] Optionally, the first message or the third message further includes information of the terminal device, where the information of the terminal device includes at least one of the type of the terminal device, supported bandwidth, and processing capability.

[0022] In combination with the second aspect, in some implementations of the second aspect, the terminal device includes a reduced-capability RedCap type terminal device and an enhanced reduced-capability eRedCap type terminal device.

[0023] According to a third aspect, a communication device is provided, which may include a unit for implementing the method in the first aspect or any possible implementation manner of the first aspect.

[0024] According to a fourth aspect, a communication device is provided, which may include a unit for implementing the method in the second aspect or any possible implementation manner of the second aspect.

[0025] In a fifth aspect, a communication device is provided, comprising a processor. The processor may be used to execute the instructions involved, so that the device performs the method in the first aspect or any possible implementation of the first aspect. Optionally, the device may also include a memory, the memory is coupled to the processor, and the memory stores the instructions involved. Optionally, the device may also include an interface circuit, the interface circuit is coupled to the processor.

[0026] In a sixth aspect, a communication device is provided, comprising a processor. The processor may be used to execute the instructions involved, so that the device performs the method in the second aspect or any possible implementation of the second aspect. Optionally, the device may also include a memory, the memory is coupled to the processor, and the memory stores the instructions involved. Optionally, the device may also include an interface circuit, the interface circuit is coupled to the processor.

[0027] In a seventh aspect, a chip system is provided, comprising a processor, wherein the processor comprises: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation of the first to sixth aspects or the first to sixth aspects.

[0028] In the specific implementation process, the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits. The input signal received by the input circuit can be received and input by, for example but not limited to, a receiver, and the signal output by the output circuit can be, for example but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be the same circuit, which is used as an input circuit and an output circuit at different times. The embodiment of the present application does not limit the specific implementation method of the processor and various circuits.

[0029] In the specific implementation process, the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading software codes stored in a memory. The memory can be integrated in the processor or located outside the processor and exist independently.

[0030] Optionally, the system may also include a memory, and the processor is used to read the program or instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in the first to sixth aspects or any possible implementation of the first to sixth aspects.

[0031] In a feasible design, the number of the processors is one or more, and the number of the memories is one or more.

[0032] In a feasible design, the memory may be integrated with the processor, or the memory may be separately provided from the processor.

[0033] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips respectively. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0034] In an eighth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute the method in the above-mentioned first and second aspects and any possible implementation of the first and second aspects.

[0035] In the ninth aspect, a computer-readable medium is provided, which stores a computer program (also referred to as code, or instructions) which, when executed on a computer, enables the computer to execute the method in the above-mentioned first and second aspects and any possible implementation of the first and second aspects.

[0036] In a tenth aspect, a communication system is provided, comprising an apparatus corresponding to a method for implementing any possible implementation of the above-mentioned first aspect and second aspect or any possible implementation manner of the first aspect and second aspect.

[0037] In one possible design, the communication system may also include other devices that interact with the communication device in the solution provided in the embodiment of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a schematic diagram of a communication system provided by the present application.

[0039] Figure 2 It is a schematic diagram of another communication system provided by the present application.

[0040] Figure 3 This is a schematic diagram of a random access process provided by this application.

[0041] Figure 4 This is another schematic diagram of a random access process provided by this application.

[0042] Figure 5 It is a schematic flow chart of method 500 provided in an embodiment of the present application.

[0043] Figure 6 It is a schematic flow chart of method 600 provided in an embodiment of the present application.

[0044] Figure 7 It is a schematic flow chart of method 700 provided in an embodiment of the present application.

[0045] Figure 8 It is a schematic block diagram of the device 800 provided in this application.

[0046] Fig. 9 It is a schematic block diagram of the device 900 provided in this application. DETAILED DESCRIPTION

[0047] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0048] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, fifth generation (5G) system, new radio (NR) or other communication systems that may appear in the future.

[0049] Figure 1 1 shows an architecture diagram of a system 100 that can be applied to the present application. Figure 1 As shown, the system 100 may include one or more of the following devices: terminal device 101, access network equipment 102, user plane network element 103, data network 104, access and mobility management network element 105, session management network element 106, policy control network element 107, application network element 108, unified data management network element 109 and network open network element 110.

[0050] Terminal device 101: can be user equipment (UE), user, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. For example, it can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Terminal device 101 can also be a device or circuit structure set in the above-mentioned various devices, such as a chip or a chip system.

[0051] The terminal device in the present application may refer to, for example, a terminal device with reduced capabilities such as the eRedCap type in R18, the RedCap type in R17, or a low-capability terminal device, a reduced-capability terminal device, a RedCap UE, a ReducedCapacity UE, a narrowband NR (narrow-band NR, NB-NR) UE, etc. It may also be a Regular UE (or normal UE, non-RedCap UE, etc.), such as an enhanced mobile broadband (enhanced mobile broadbande, eMBB) UE. Of course, with the development of wireless communication technology, terminal devices with reduced capabilities may also include other types of devices, and corresponding terminal devices with non-reduced capabilities may also include other types of devices, which is not specifically limited in the embodiments of the present disclosure.

[0052] Optionally, the terminal device in the present application has one or more of the following features:

[0053] Bandwidth, number of supported or configured resources, number of transmit antenna ports and / or number of receive antenna ports, number of RF channels, number of hybrid automatic repeat request (HARQ) processes, supported peak rate, application scenarios, latency requirements, processing capabilities, protocol version, duplex mode, services, etc. The first feature is described in detail below.

[0054] 1. Bandwidth capability. Bandwidth capability can be expressed by the maximum bandwidth processing capability of the baseband. For example, the bandwidth supported by the terminal device in this application is not greater than 40 MHz. Specifically, it can be 20 MHz, 10 MHz, or 5 MHz.

[0055] 2. Number of receiving and transmitting antennas. For example, the terminal device in the present application may support 2 receiving and 1 transmitting (2 receiving antennas and 1 transmitting antenna), or 1 receiving and 1 transmitting (1 receiving antenna and 1 transmitting antenna).

[0056] 3. Maximum uplink transmission power. For example, the maximum uplink transmission power of the terminal device in this application can be 4 decibel milliwatts (dBm). A value in .

[0057] 4. Protocol version. The terminal device in the present application may be a terminal device in NR version 17 (Rele-17) or a later version of NR Rel-17.

[0058] 5. Carrier aggregation capability. For example, the terminal device in the present application does not support carrier aggregation, or supports carrier aggregation, but the maximum number of carrier aggregations supported simultaneously is less than the maximum number of carrier aggregations supported simultaneously by a terminal device with legacy capability, normal capability, or high capability (also referred to as a legacy terminal device or a normal terminal device).

[0059] 6. Duplex capability: For example, the terminal device in the present application supports half-duplex frequency division duplexing (FDD).

[0060] 7. Data processing time capability. For example, the minimum delay between the terminal device in the present application receiving downlink data and sending feedback on the downlink data is greater than the minimum delay between the terminal device with traditional capabilities, normal capabilities, or high capabilities receiving downlink data and sending feedback on the downlink data; and / or, the minimum delay between the terminal device in the present application sending uplink data and receiving feedback on the uplink data is greater than the minimum delay between the terminal device with traditional capabilities, normal capabilities, or high capabilities sending uplink data and receiving feedback on the uplink data.

[0061] 8. Processing capability (ability / capability). For example, the baseband processing capability of the terminal device in the present application is lower than the baseband processing capability of the terminal device with traditional capability, normal capability or high capability. Among them, the baseband processing capability may include at least one of the following: the maximum number of multiple input multiple output (MIMO) layers supported by the terminal device when performing data transmission, the number of hybrid automatic repeat request (HARQ) processes supported by the terminal device, and the maximum transmission block size (TBS) supported by the terminal device.

[0062] 9. Uplink and / or downlink transmission peak rate. The transmission peak rate refers to the maximum data transmission rate that the terminal device can achieve in a unit of time (for example, per second). The uplink peak rate supported by the terminal device in this application may be lower than the uplink peak rate supported by the terminal device with traditional capabilities, normal capabilities, or high capabilities, and / or the downlink peak rate supported by the terminal device in this application may be lower than the downlink peak rate supported by the terminal device with traditional capabilities, normal capabilities, or high capabilities.

[0063] 10. Buffer size: Buffer can be understood as the total size of the Layer 2 (L2) buffer, or the total number of soft channel bits that can be used for HARQ processing.

[0064] 11. The number of resources supported or configured. The number of resources may be a resource block (RB), a resource element (RE), a subcarrier, an RB group, a resource element group bundle (REG bundle), a control channel element, a subframe, a radio frame, a time slot, a mini-time slot and / or the number of symbols. The number of resources supported or configured by the first type of device and the second type of device is different. For example, the number of resources supported by the first type of device is 48 RBs, and the number of resources supported by the second type of device is 96 RBs.

[0065] It should be understood that other types or future new types of terminal devices that also support the technical solution of the present application are also within the protection scope of the present application.

[0066] Access network equipment 102: capable of managing wireless resources, providing access services for terminal devices, and completing the forwarding of control signals and user data between the terminal devices and the core network.

[0067] Access network equipment is also called network equipment. Access network equipment can be a transmission reception point (TRP), an evolved NodeB (eNB or eNodeB) in an LTE system, a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), a wireless controller in a cloud radio access network (CRAN) scenario, a relay station, an access point, a vehicle-mounted device, a wearable device, a next generation NodeB (gNB) in a 5G mobile communication system, an access network device in a future evolved public land mobile network (PLMN), an access point (AP), etc. It can also be a module or unit that completes some functions of a base station. For example, a gNB can include a centralized unit (CU) and a distributed unit (DU). A gNB can also include an active antenna unit (AAU). The CU here completes the functions of the radio resource control protocol and the packet data convergence layer protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the functions of part of the physical layer or all of the physical layer. The AAU implements some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or, it is converted from the information of the PHY layer, therefore, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or, sent by the DU+AAU. It can be understood that the network device can be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into a network device in the access network (radio access network, RAN), and the CU can also be divided into a network device in the core network (core network, CN), and this application does not limit this.For a detailed description of each of the above-mentioned protocol layers, reference may be made to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The wireless access network device may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device. For ease of description, the following description takes a base station as an example of a wireless access network device.

[0068] User plane network element 103: mainly responsible for data packet routing and forwarding.

[0069] Data network 104: can be operator services, Internet access or third-party services, such as IP Multimedia Service (IMS), Internet, etc. The data network may include an application server (AS), which is a software framework that provides an environment for application running and is used to provide security, data, transaction support, load balancing, large distributed system management and other services for the application. The terminal device obtains application messages by communicating with the AS.

[0070] Access and mobility management network element 105: mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user switching, etc.

[0071] Session management network element 106: mainly responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions include allocating IP addresses to users and selecting user plane network elements that provide message forwarding functions.

[0072] Policy control network element 107: responsible for providing policies such as quality of service (QoS) policy and slice selection policy to access and mobility management network elements and session management network elements.

[0073] Application network element 108: responsible for providing services to the 3GPP network, interacting with the policy control network element to perform policy control, etc.

[0074] Unified data management network element 109: used to store user data, such as contract information, authentication / authorization information.

[0075] Network open network element 110: provides the framework, authentication and interface related to network capability opening, and transmits information between 5G system network functions and other network functions.

[0076] It should be understood that the above-mentioned devices or network elements may be devices with corresponding functions, or may be software / hardware modules (such as chips) inside the device, etc. It should also be understood that any device or network element involved in the present application may be implemented in the form of software or a combination of software and hardware.

[0077] In one example, Figure 1 The system 100 shown may be Figure 2 It should be understood that the system 100 may also be a 4G system or other systems, which is not limited in this application.

[0078] Figure 2 This is a schematic diagram of a 5G system architecture. Figure 1 The network elements with the same reference numerals are Figure 1 The naming of the corresponding network elements in the current 5G system. Figure 2 The 5G system architecture may include one or more of the following network elements: UE 101, (radio) access network ((R)AN) 102, user plane function (UPF) 103, data network (DN) 104, access and mobility management function (AMF) 105, session management function (SMF) 106, policy control function (PCF) 107, application function (AF) 108, unified data management (UDM) 109 and network exposure function 110.

[0079] It should be understood that Figure 2 The names of the network elements shown are just names, and the names do not limit the functions of the network elements themselves. In different networks, the above network elements may also have other names, which are not specifically limited in the embodiments of the present application. For example, in a 6G network, some or all of the above network elements may use the terminology used in 5G, or may be named in other ways. Similarly, Figure 2 The interface between the network elements shown is only an example. In 5G networks and other future networks, the interface between network elements may not be the interface shown in the figure, and this application does not limit this.

[0080] It should also be understood that the embodiments of the present application are not limited to Figure 2For example, the communication system to which the present application can be applied may include more or fewer network elements or devices. Figure 2 The equipment or network element in the network can be hardware, functionally divided software, or a combination of the two. Figure 2 Devices or network elements in a network can communicate through other devices or network elements.

[0081] The technical solution provided in the embodiment of the present application can be applied to wireless communication between communication devices. Wireless communication between communication devices may include: wireless communication between network devices and terminals, wireless communication between network devices and network devices, and wireless communication between terminal devices and terminal devices. In the embodiment of the present application, the term "wireless communication" can also be referred to as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0082] In order to facilitate understanding of the solutions of the embodiments of the present application, the relevant concepts are explained.

[0083] 1. Random access:

[0084] Random access is the process of establishing a wireless link connection between a terminal device and a network device. Only after random access is completed can the network device and the terminal device perform data interoperation normally. According to the different service triggering methods, random access can be divided into contention based random access procedure and non-contention based random access procedure. The main process of contention based random access includes the following steps (implementation process steps as follows Figure 3 shown):

[0085] S301, UE sends a random access (RA) preamble to a network device.

[0086] The random access preamble may also be referred to as message 1 (Msg1) or a random access request. The function of the random access preamble is to notify the network device that there is a random access request. The network device can estimate the transmission delay between it and the terminal device and the size of the uplink resource required for message 3 in step S303 based on message 1.

[0087] S302: After detecting the random access preamble, the network device sends a random access response (RAR) to the UE.

[0088] The random access response may also be referred to as message 2 (Msg2). The random access response includes the scheduling information of message 3 (Msg3), namely, the RAR uplink (UL) grant information. The random access response may also include other information, such as the timing advance TA (TA) and the temporary cell radio network temporary identity (TC-RNTI).

[0089] After the terminal device sends message 1, it can monitor the physical downlink control channel (PDCCH) scrambled by the random access radio network temporary identity (RA-RNTI) in the RAR window to receive the physical downlink shared channel (PDSCH) scheduled by the PDCCH. The RAR message is carried in the PDSCH. Among them, the RAR message can be scheduled using the downlink control information (DCI) format 1-0.

[0090] If the terminal device does not receive a RAR message from the network device in the RAR window, the random access is considered to have failed. If the terminal device successfully detects a RAR message in the RAR window, and the index of the preamble carried in the RAR message is the same as the index of the preamble in Message 1, the terminal device can stop detecting the RAR message. The terminal device can use RA-RNTI to descramble the RAR message. RA-RNTI is related to the PRACH used by the terminal device to send Msg1.

[0091] S303, the UE receives a random access response, and sends a message 3 in the time-frequency resources scheduled by the scheduling information in the random access response.

[0092] After receiving the RAR message, the terminal device determines whether the RAR message belongs to itself. For example, the terminal device can use the preamble code index to check. After determining that it is the RAR message belonging to itself, the terminal device generates message 3 at the RRC layer and sends message 3 to the network device, which can carry the identifier of the terminal device, etc. Message 3 is carried by the physical uplink shared channel (PUSCH).

[0093] After sending message 3, the UE starts a contention resolution timer (ra-ContentionResolutionTimer) (the contention resolution timer duration is 64 ms), and then monitors the PDCCH within the time window of the timer.

[0094] S304, the network device receives message 3 from the UE, and returns a conflict resolution message, also called message 4 (message 4, Msg4), to the UE that has successfully accessed.

[0095] The terminal device receives message 4 to complete contention resolution. During the RRC connection establishment process, message 4 may carry an RRC connection establishment message.

[0096] If message 3 carries the unique identifier of the terminal device, such as C-RNTI or identification information from the core network (such as S-TMSI or a random number), message 4 will carry the unique identifier of the terminal device to specify the terminal device that wins the competition, and the PDCCH used to schedule message 4 can be encrypted with C-RNTI.

[0097] The terminal device that wins the contention resolution establishes uplink synchronization with the NR cell and obtains uplink resources.

[0098] If the number of random access attempts of the terminal device that did not win the contention resolution is less than the maximum number of attempts, a random access attempt is made again, otherwise the random access process fails.

[0099] The main process of non-contention-based random access includes the following steps (the implementation process steps are as follows Figure 4 shown):

[0100] S401, the network device sends message 0 (message 0, Msg0) to the UE and allocates an RA preamble code.

[0101] Specifically, the base station determines the system configuration information and sends it to the user equipment. The system configuration information includes: a random access preamble retransmission mechanism and random access preamble retransmission configuration information. In an embodiment of the present invention, the system configuration information may also include: a format of a random access preamble and configuration information of random access resources. The random preamble retransmission mechanism and random access preamble retransmission configuration information may include a maximum number of random access times for a preamble code (Preamble TransMax).

[0102] The base station allocates a dedicated preamble for non-contention random access and PRACH resources used for random access to the UE through message 0. Non-contention random access dedicated resources are allocated through RRC signaling (such as handover or SCG (Secondary Cell Group) addition, BFR) or physical layer signaling PDCCH.

[0103] S402, the UE sends a designated dedicated preamble, ie, message 1, to the base station on a designated PRACH resource according to the instruction of message 0.

[0104] The UE obtains the physical random access channel PRACH configuration from the system information block SIB1 message. The UE obtains the time-frequency domain position of the RA preamble it sends through the PRACH configuration. After receiving message 1, the base station calculates the uplink timing advance TA based on message 1.

[0105] S403, the UE receives a random access response.

[0106] The information carried in the RA response includes timing alignment information (TAI), uplink authorization, etc.

[0107] S404, the UE sends message 3 at the determined sending time based on the timing alignment information carried in the RA response.

[0108] For the embodiment of the present invention, the above-mentioned random access failure includes at least one of the following situations:

[0109] (1) The user equipment does not receive the random access response information sent by the base station within the random access response receiving time window.

[0110] (2) The user equipment receives random access response information sent by the base station within the random access response receiving time window, but the identifier of the preamble sequence carried in the random access response information is different from the identifier corresponding to the preamble sequence sent by the user equipment to the base station.

[0111] (3) The user equipment receives random access response information sent by the base station within the random access response reception time window, and the identifier of the preamble sequence carried in the random access response information is the same as the identifier corresponding to the preamble sequence sent by the user equipment to the base station, but the identifier of the user equipment carried in the conflict resolution information received by the user equipment is different from the identifier corresponding to the preamble sequence.

[0112] (4) Message 3 times out.

[0113] Specifically, the UL grant carried in the RA response includes the time domain resource allocation table (TDMA) of message 3, which is used to indicate the time required for the user equipment to receive the RA response and send message 3. If the time is less than the minimum scheduling delay of the user equipment for Msg3, the user equipment cannot successfully send message 3, resulting in a timeout of message 3.

[0114] (5) The user equipment does not receive message 4 after sending message 3.

[0115] Specifically, when the transmission bandwidth of message 4 is greater than the processing bandwidth capability of the user equipment, the user equipment cannot parse message 4, and thus cannot determine whether it wins in contention resolution, which leads to random access failure. For example, the bandwidth supported by the user equipment is 20 MHz, and the bandwidth of message 4 is 40 MHz.

[0116] It should be understood that when the terminal device fails in random access, it will continue to initiate the next random access attempt until the random access succeeds, or it is determined that a random access problem occurs after reaching the maximum random access number of the preamble code. Usually, according to the count value of the preamble code transmission counter (PREAMBLE_TRANSMISSION_COUNTER), by increasing the first count value each time a preamble code is sent, for example, by adding 1 (the specific increase amount can be set as needed), it is determined whether the count value reaches the set upper limit, and when the count value reaches the set upper limit, the MAC needs to indicate to the upper layer (upper layer) (for example, the RRC layer) that a random access problem has occurred. After receiving the indication, the upper layer can determine that a radio link failure (RLF) has occurred, and then the RRC connection re-establishment process can be triggered, and the preamble code is stopped from being sent to the base station, thereby avoiding the user equipment from continuously resending the preamble code to the base station when it is determined that the random access to the base station has failed successfully, causing resource consumption of the user equipment and the base station.

[0117] 2. Preamble transmission times counter

[0118] The UE establishes a wireless link with the network side through a random access process, which can be based on a non-competitive RA or a RA based on contention conflict resolution. During the random access process, the number of preamble transmission times counter (hereinafter referred to as the counter) is used to count the number of preamble transmissions during the random access process. Specifically, the specific process related to the counter during the random access process may include:

[0119] Step 1: Start the counter: When the random access process is initialized / triggered, the value of the counter is set to 0 or 1. The following description assumes that the initial value of the counter is 1.

[0120] Step 2: Count the number of times the preamble is sent during the random access process: When random access fails, for example, when the UE does not receive a response to the UE within a time window, and when the contention conflict resolution is unsuccessful (for example, when the contention conflict resolution timer times out), the value of the counter is increased by 1, or after the terminal device sends message 1 once, the value recorded by the counter is increased by 1. Exemplarily, after the terminal device sends message 1 once, the value recorded by the counter is 2; after the terminal device sends message 1 N times, the value recorded by the counter is N+1.

[0121] Step 3: Determine whether the value of the counter is equal to the maximum number of transmission times plus 1.

[0122] - If the value of the counter is not equal to the maximum number of transmissions plus 1, the UE may continue to send the preamble, i.e., message 1, and may also continue to perform step 2;

[0123] - If the value of the counter is equal to the maximum number of transmissions plus 1, the MAC layer indicates to the upper layer of the UE that a random access problem has occurred or indicates to the upper layer of the UE that a problem has occurred, and the problem is a random access problem, which is collectively referred to as indicating a random access problem here and below. After receiving the indication, the upper layer can determine that a radio link random access failure has occurred, and then the RRC connection re-establishment process can be triggered.

[0124] It should be understood that judging whether the value of the counter is equal to the maximum number of transmissions plus 1 is equivalent to judging whether the value of the counter exceeds (is greater than) the predetermined maximum number of transmissions. If the initial value of the counter is 0, the judgment here can be to judge whether the value of the counter is equal to the predetermined maximum number of transmissions. The network device can configure the value of the maximum number of transmissions.

[0125] 3. System information (SI)

[0126] System information is a message sent by the base station, which contains information required for UE initialization and related information of some other functions / features. System information is divided into minimum system information (Minimum SI) and other system information (Other SI).

[0127] The minimum system information consists of the master information block (MIB) and system information block 1 (SIB1), which is also called the remaining minimum system information (RMSI). The MIB is broadcast periodically on the broadcast channel (BCH). SIB1 is broadcast periodically on the downlink shared channel (DL-SCH) or sent to the RRC_CONNECTED UE through dedicated signaling.

[0128] Other system information consists of other SIBs, such as SIB2 to SIB9, etc. Other SIBs are broadcast on DL-SCH periodically, or on-demand (i.e., when a UE in RRC idle state (RRC_IDLE) or RRC inactive state (RRC_INACTIVE) requests a certain SIB, the network broadcasts the SIB, otherwise the SIB is not sent), or sent to RRC connected UEs by dedicated signaling.

[0129] From the above, we can see that compared with conventional NR terminals, RedCap and eRedCap terminals have lower cost and complexity, smaller form factor and longer battery life, but are more limited in processing power and time-frequency resources. For RedCap and eRedCap terminals, random access failures (such as the above-mentioned random access failure situations (4) and (5)) may occur due to limited processing power and time-frequency resources, thereby wasting access opportunities. Therefore, how to reduce the waste of access opportunities during random access is a key issue currently faced.

[0130] In view of the above technical problems, the present application provides a counting method and a communication device, which are beneficial to reducing the waste of access opportunities during random access.

[0131] The counting method and the communication device according to the embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0132] like Figure 5 As shown, Figure 5 is a flow chart of a method 500 according to an embodiment of the present application. The method 500 includes:

[0133] Optionally, S501, the terminal device sends a preamble code via message 1.

[0134] In the present application, the terminal device can send a preamble code through message 1 in various scenarios. Message 1 can be actively sent by the terminal device to the network device, or sent by the network device to the terminal device after receiving a request from the terminal device. An example is given below. It should be understood that message 1 can be an example of the first message.

[0135] Method 1

[0136] The terminal device may send message 1 during a contention-based random access process.

[0137] Method 2

[0138] The terminal device can send message 1 on the designated PRACH resource according to the instruction of message 0 sent by the network device during the non-contention-based random access process.

[0139] The specific process can be referred to the above description and will not be repeated here.

[0140] The following takes the process of method 1 as an example for detailed description.

[0141] S502: The terminal device counts the number of transmissions of message 1.

[0142] It should be understood that the above step S502 can be performed before S501, or when the terminal device determines that random access fails, and this application does not limit this.

[0143] In some embodiments, the network device counts the number of transmissions of Message 1.

[0144] Specifically, after receiving the message 1, the network device may count the number of transmissions of the message 1.

[0145] S503, the terminal device receives message 2.

[0146] Message 2 is used to indicate that message 3 is sent within time T.

[0147] Specifically, after sending message 1, the terminal device can monitor the RA-RNTI encrypted PDCCH in the RAR window to receive the PDSCH scheduled by the PDCCH, wherein message 2 is carried in the PDSCH. Message 2 includes scheduling information of message 3, i.e., RAR uplink authorization information, and the uplink authorization information includes the time domain resource allocation table of message 3. The time domain resource allocation table is used to indicate the time T required from the terminal device receiving message 2 to sending message 3. It should be understood that message 2 can be an example of the second message, and message 3 can be an example of the third message.

[0148] It should be understood that the terminal device in the embodiment of the present application may be a low-capability terminal device. The low-capability terminal device has a lower data processing capability than the traditional terminal device, and it can be considered that it takes longer to process the same data. For example, the minimum delay between the low-capability terminal device receiving downlink data and sending feedback on the downlink data is greater than the minimum delay between the traditional terminal device receiving downlink data and sending feedback on the downlink data. Among them, the delay of receiving and processing PDSCH of RedCap type terminal devices is increased compared with traditional terminal devices. The delay of receiving and processing PDSCH of eRedCap type terminal devices is increased compared with RedCap type terminal devices.

[0149] In some embodiments, the low-capability terminal device may be a terminal device with reduced capabilities, such as an eRedCap type in R18 or a RedCap type in R17.

[0150] In some embodiments, the network device sends message 2.

[0151] In the embodiments of the present application, Figure 5 As shown in , the random access scenario also includes traditional terminal devices.

[0152] Specifically, in step S504, the traditional terminal device receives message 2, and performs step S505 within time T, and the traditional terminal device sends message 3. However, since the terminal device in this scenario has a lower data processing capability than the traditional terminal device, it can be considered that the PDSCH reception and processing delay of the terminal device is increased compared with the traditional terminal device, resulting in the time T indicated in the uplink authorization information being less than the minimum scheduling delay of the terminal device, that is, the processing time of the terminal device scheduling message 3 is greater than the time T indicated by message 2, and the random access process of the terminal device fails.

[0153] It should be understood that message 2 can be sent to multiple terminal devices on one PDSCH at the same time, and the above-mentioned multiple terminal devices may include traditional terminal devices, eRedCap type, RedCap type and other terminal devices with reduced capabilities. Low capability only represents a relative concept, which depends on the time T indicated in message 2 and the processing capability of the receiving device. When the random access scenario includes terminal devices with reduced capabilities such as eRedCap type and RedCap type and traditional terminal devices, if the processing time of the traditional terminal device scheduling message 3 is less than time T, and the processing time of the eRedCap type and RedCap type terminal devices scheduling message 3 is greater than time T, then the terminal device in the embodiment of the present application may be an eRedCap type or RedCap type terminal device; if the processing time of the traditional terminal device and the RedCap type terminal device scheduling message 3 is less than time T, and the processing time of the eRedCap type terminal device scheduling message 3 is greater than time T, then the terminal device in the embodiment of the present application may be an eRedCap type terminal device. The above example only illustrates the process in which the time T indicated in the uplink authorization information is less than the minimum scheduling delay of the terminal device. The time T may be specified by the protocol.

[0154] Exemplarily, when multiple terminal devices include eRedCap type and RedCap type terminal devices, if time T is the minimum scheduling delay of the RedCap type terminal device, that is, T = (NT, 1) + (NT, 2) + 0.5, where (NT, 1) is the scheduling delay of message 1, and (NT, 2) is the scheduling delay of message 2. Since the PDSCH delay of the eRedCap type terminal device is longer, for example, the delay T' of the eRedCap type terminal device is T' = (NT, 1) + (NT, 2) + 0.5 + X milliseconds, where X is the delay of scheduling message 3 added by the eRedCap type terminal device, that is, T'>T, at this time, the processing time of the eRedCap type terminal device scheduling message 3 is greater than the time T indicated by message 2, that is, in this scenario, the eRedCap type terminal device cannot successfully send message 3, and the random access process fails.

[0155] After the random access process of the terminal device fails, proceed to step S506.

[0156] S506, the terminal device adjusts the counting rule.

[0157] Optionally, after the terminal device adjusts the counting rule, the terminal device re-initiates random access.

[0158] Specifically, when the processing time of the terminal device scheduling message 3 is greater than the time T indicated by the message 2, the terminal device adjusts the counting rule and re-initiates random access.

[0159] It should be understood that during the random access process, the terminal device can use the preamble sending counter to count the number of times the preamble is sent during the random access process, that is, the number of times the message 1 is transmitted. For details, please refer to the above description.

[0160] In the embodiment of the present application, adjusting the counting rule includes not counting when the terminal device sends the first message next time, or increasing the maximum number of times the first message is sent.

[0161] It should be understood that in a normal random access process, when the terminal device fails to perform random access, the value of the counter is increased by 1 the next time the terminal device sends message 1. In the embodiment of the present application, the adjusted counting rule is that the next time the terminal device sends message 1, no counting is performed, or the maximum number of times message 1 is sent is increased. Specifically, the next time message 1 is sent, no counting is performed, which can be "not increment PREAMBLE_TRANSMISSION_COUNTER by 1" in the protocol, and increasing the maximum number of times message 1 is sent can increase the configured "preambleTransMax" total number, for example, by 1.

[0162] S507, the network device adjusts counting rules.

[0163] Correspondingly, when the network device does not receive message 3 within time T, the counting rule is adjusted so that the counting of the network device and the terminal device is synchronized. Specifically, adjusting the counting rule includes not counting the next time the network device receives the first message, or increasing the maximum number of receptions of the first message, for example, increasing the maximum number of receptions by 1.

[0164] S508, the terminal device sends message 1.

[0165] It should be understood that the process of the terminal device sending message 1 in S508 is the next sending process of the terminal device sending message 1 in S501. After the counting rule is adjusted in S506, after the terminal device sends message 1 in S508, according to the adjusted counting rule, the counter does not count or increases the maximum number of sending times of message 1.

[0166] In this way, after the terminal device receives the second message indicating that the third message is to be sent within time T, when the terminal device schedules the processing time of the third message to be greater than time T, the terminal device can reduce the waste of random access opportunities due to processing capacity limitations by adjusting the counting rules.

[0167] In some embodiments, the terminal device receives the fourth message, and when the bandwidth that the terminal device can process is less than the transmission bandwidth of the fourth message, the counting rule is adjusted. Optionally, the fourth message is message 2 or message 4, and the following is a detailed description taking message 4 as an example.

[0168] Figure 6 600 is a schematic flow chart of the method 600 provided in the embodiment of the present application. Figure 6 As shown, the method 600 includes:

[0169] S601, the terminal device sends message 1.

[0170] S602, the terminal device receives message 2.

[0171] S603, the terminal device sends message 3.

[0172] Among them, message 3 is used to determine message 4. It should be understood that message 4 can be an example of the fourth message.

[0173] Steps S601 to S603 are the same as S301 to S303 , and the description of S301 to S303 may be referred to, and will not be repeated here.

[0174] S604, the terminal device receives message 4.

[0175] It should be understood that message 4 can be sent to multiple terminal devices on one PDSCH at the same time, where the multiple terminal devices may include traditional terminal devices and terminal devices with reduced capabilities such as eRedCap type and RedCap type. Since the bandwidth capability of low-capability terminal devices is limited, for example, the bandwidth supported by traditional terminal devices is greater than 40MHz, the bandwidth supported by RedCap type terminal devices is 20MHz, and the bandwidth supported by eRedCap type terminal devices is 5MHz. When the transmission bandwidth of message 4 sent by the network device is 20MHz, the bandwidth that the eRedCap type terminal device can process is less than the transmission bandwidth of message 4, that is, it cannot receive and process message 4 with a large bandwidth, resulting in the failure of the random access process of the eRedCap type terminal device.

[0176] That is, when the bandwidth that the terminal device can process is smaller than the transmission bandwidth of message 4, that is, the random access process of the terminal device fails, the process goes to step S605.

[0177] S605, when the bandwidth that the terminal device can process is smaller than the transmission bandwidth of message 4, the counting rule is adjusted and random access is re-initiated.

[0178] Specifically, adjusting the counting rule includes not counting when the terminal device sends the first message next time, or increasing the maximum number of times the first message is sent.

[0179] S606, the terminal device sends message 1.

[0180] Steps S605 to S606 are the same as S505 to S506, and the description of S505 to S506 may be referred to, which will not be repeated here.

[0181] In this way, when the bandwidth that the terminal device can process is smaller than the transmission bandwidth of the fourth message, by adjusting the counting rule, the terminal device can reduce the waste of random access opportunities caused by processing bandwidth limitation.

[0182] In some embodiments, the first message or the third message contains information of the terminal device, and the information of the terminal device includes at least one of the type of the terminal device, supported bandwidth, and processing capability.

[0183] This allows the network device to determine the type of the terminal device. The following is an example in which message 1 includes information about the terminal device.

[0184] Combine the following Figure 7 This section describes the method for counting terminal devices when the network device is able to determine the type of the terminal device.

[0185] like Figure 7 As shown, Figure 7 700 is a flowchart of a method 700 of an embodiment of the present application. The method 700 includes:

[0186] S701. The terminal device sends a preamble code via message 1.

[0187] In some embodiments, the message 1 also includes information about the terminal device. For example, the information about the terminal device includes at least one of the type of the terminal device, supported bandwidth, and processing capability. Optionally, the information about the terminal device may also include other information so that the network device can distinguish the type of the terminal device.

[0188] Exemplarily, the types of terminal devices include traditional terminal devices, RedCap type terminal devices, eRedCap type terminal devices, etc., which are not limited in this application.

[0189] Specifically, the UE capability information may be used to indicate the UE's processing capability for PDSCH channels carrying system information block 1 (SIB1), other system information (OSI), paging, random access response, and message 4. Furthermore, the UE capability information may be used to indicate the UE's processing capability for all PDSCH channels.

[0190] S704: The network device determines a fifth message according to the information of the terminal device.

[0191] In some embodiments, the network device can determine the information of the terminal device through message 1. When the network device determines that the processing time of the terminal device scheduling message 3 is greater than the time T indicated by message 2, or the bandwidth that the terminal device can process is less than the transmission bandwidth of message 4, the fifth message is determined, wherein the fifth message is used to instruct the terminal device to adjust the counting rule. Specifically, the terminal device does not count the next time it sends the first message, or increases the maximum number of times the first message is sent. The first message is message 1.

[0192] Optionally, the fifth message is a system message SIB.

[0193] S705, the network device sends the fifth message, and the terminal device receives the fifth message.

[0194] Among them, the fifth message is used to instruct the terminal device not to count the next time it sends message 1, or to increase the maximum number of times message 1 is sent.

[0195] S706: The terminal device adjusts the counting rule according to the fifth message and re-initiates random access.

[0196] S707, the network device adjusts counting rules.

[0197] In the embodiment of the present application, when the network device determines, based on the information of the terminal device, that the processing time of the scheduled message 3 of the terminal device is greater than the time T indicated by the message 2, or that the bandwidth that the terminal device can process is less than the transmission bandwidth of the message 4, the fifth message is sent, and the counting rule of the network device is adjusted so that the counting of the network device and the terminal device is synchronized. Specifically, adjusting the counting rule includes not counting the next time the network device receives the first message, or increasing the maximum number of receptions of the first message, for example, increasing the maximum number of receptions by 1.

[0198] In some embodiments, S707 precedes S705.

[0199] S708, the terminal device sends message 1.

[0200] Steps S706 to S708 are similar to steps S505 to S507, and reference may be made to the description of S505 to S507, which will not be repeated here.

[0201] In some embodiments, the terminal device sends information of the terminal device via message 3.

[0202] The method 700 further includes,

[0203] S702, the network device sends message 2, and the terminal device receives message 2.

[0204] In some embodiments, the network device sends a message 2, where the message 2 is used to indicate that a message 3 is received within a time T. When the network device does not receive the message 3 within the time T, the counting rule of the network device is adjusted.

[0205] It should be understood that when the network device does not obtain the information of the terminal device, the terminal device may not send message 3 within time T due to capability limitation. At this time, the network device can maintain consistency with the terminal device count by adjusting the counting rule.

[0206] S703, the terminal device sends message 3, and the network device receives message 3.

[0207] Message 3 is used to determine message 4. Message 3 also includes information about the terminal device, and the information about the terminal device includes at least one of the type of the terminal device, the supported bandwidth, and the processing capability. Optionally, the information about the terminal device may also include other information so that the network device can distinguish the type of the terminal device. When the network device determines, based on the information about the terminal device, that the bandwidth that the terminal device can process is less than the transmission bandwidth of message 4, the counting rule of the network device is adjusted, and a fifth message is sent.

[0208] In some embodiments, when the network device determines that the terminal device wins the contention resolution, and determines based on the information of the terminal device that the bandwidth that the terminal device can process is less than the transmission bandwidth of message 4, the counting rule of the network device is adjusted and the fifth message is sent.

[0209] For example, when the network device determines that UE1 wins when performing contention resolution between UE1 and UE2, and the network device determines, based on the information of UE1, that the bandwidth that UE1 can process is less than the transmission bandwidth of message 4, the network device adjusts the counting rule of the network device and broadcasts it to the terminal through the fifth message, wherein the fifth message is used to instruct UE1 to adjust the counting rule. Specifically, the next time UE1 sends message 1, no counting is performed, or the maximum number of times message 1 is sent is increased.

[0210] In some embodiments, when the transmission bandwidth of message 4 is greater than the bandwidth that any terminal device can process, the network device sends the fifth message.

[0211] It should be understood that multiple terminal devices may send message 3 to the network device, that is, the network device may send message 4 to multiple terminal devices at the same time, wherein the multiple terminal devices may include traditional terminal devices and terminal devices with reduced capabilities such as eRedCap type and RedCap type. Since the bandwidth capability of low-capability terminal devices is limited, for example, the bandwidth supported by traditional terminal devices is greater than 40MHz, the bandwidth supported by RedCap type terminal devices is 20MHz, and the bandwidth supported by eRedCap type terminal devices is 5MHz, when the transmission bandwidth of message 4 sent by the network device is 20MHz, the traditional terminal devices and RedCap type terminal devices among the multiple terminal devices can process message 4, while the eRedCap type terminal devices cannot receive and process message 4 because the bandwidth that can be processed is less than the transmission bandwidth of message 4, resulting in the failure of the random access process of the eRedCap type terminal device.

[0212] That is, when the network device determines, based on the information of the terminal device, that the bandwidth that the terminal device can process is smaller than the transmission bandwidth of message 4, the fifth message is sent.

[0213] Steps S702 to S703 are the same as S302 to S303 , and the description of S302 to S303 may be referred to, and will not be repeated here.

[0214] In some embodiments, the terminal device may send the information of the terminal device in other ways, which are described below with examples.

[0215] Method 1

[0216] The terminal device can carry the information of the terminal device in the RRC message sent to the access network device.

[0217] Exemplarily, the RRC message is an RRC connection establishment request message.

[0218] Method 2

[0219] The terminal device may send the wireless capability information of the terminal device to the access network device, and the access network device may determine the information of the terminal device based on the wireless capability information. For example, the wireless capability information may carry the information of the terminal device. Alternatively, the access network device may determine the information of the terminal device based on the parameters in the wireless capability information. For example, the access network device may determine the REDCAP information used by the terminal device based on the corresponding access frequency and other parameters in the wireless capability information, and use it as the information of the terminal device.

[0220] Exemplarily, this method can be applied to the case where the terminal device is powered on and registered for the first time.

[0221] Above, combined Figures 5 to 7 The method provided by the embodiment of the present application is described in detail. Hereinafter, the device provided by the present application is described below. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, and therefore, the content not described in detail can be referred to the method embodiment above, and for the sake of brevity, it will not be repeated here.

[0222] Figure 8 An apparatus 800 for sending information provided by an embodiment of the present application is shown. In one design, the apparatus 800 may be a terminal device or a chip in a terminal device. In another design, the apparatus 800 may be a network device or a chip in a network device. The apparatus 800 includes: an interface unit 810 and a processing unit 820. The interface unit 810 may implement corresponding communication functions, and the processing unit 820 is used for data processing. The interface unit 810 may also be referred to as a communication interface or a communication unit.

[0223] Optionally, the apparatus 800 may further include a storage unit, which may be used to store instructions and / or data. The processing unit 820 may read the instructions and / or data in the storage unit so that the communication apparatus implements the aforementioned method embodiment.

[0224] Optionally, the interface unit 810 may include a sending unit and a receiving unit. The sending unit is used to perform the sending operation in the above method embodiment. The receiving unit is used to perform the receiving operation in the above method embodiment.

[0225] In a possible implementation, the apparatus 800 is used to execute various processes and steps corresponding to the terminal device in the above method embodiment.

[0226] The interface unit 810 is used to receive a second message, where the second message is used to instruct to send a third message within a time T.

[0227] The processing unit 820 is used to count the number of transmissions of the first message, wherein the first message is used to indicate reception of the second message.

[0228] The processing unit 820 is further configured to: when the processing time of the third message scheduled by the interface unit 810 is greater than the time T, adjust the counting rule.

[0229] Optionally, the interface unit 810 is used to: receive a fourth message.

[0230] The processing unit 820 is further configured to: when the bandwidth that can be processed by the processing unit 820 is smaller than the transmission bandwidth of the fourth message, adjust the counting rule.

[0231] Among them, the first message, the second message, the third message and the fourth message are used for the random access process of the terminal device.

[0232] Optionally, adjusting the counting rule includes that the processing unit 820 does not count when the interface unit 810 sends the first message next time, or increases the maximum number of times the first message is sent.

[0233] Optionally, the interface unit 810 is used to: send a third message, where the third message is used to indicate receiving a fourth message.

[0234] Optionally, the first message or the third message further includes identification information of the device 800 , where the identification information is used to indicate the type of the device 800 .

[0235] Optionally, the interface unit 810 is used to: receive a fifth message, where the fifth message is used to instruct the processing unit 820 not to count when the interface unit 810 sends the first message next time, or to increase the maximum number of times the first message is sent.

[0236] Optionally, the apparatus 800 includes a reduced capability RedCap type terminal device and an enhanced reduced capability eRedCap type terminal device.

[0237] In another possible implementation, the apparatus 800 is used to execute various processes and steps corresponding to the network device in the above method embodiment.

[0238] The interface unit 810 is used to send a second message, where the second message is used to indicate receiving a third message within a time T.

[0239] The processing unit 820 is used to adjust the counting rule when the interface unit 810 does not receive the third message within the time T. The first message, the second message and the third message are used in the random access process of the terminal device.

[0240] Optionally, adjusting the counting rule includes that the processing unit 820 does not count when the interface unit 810 receives the first message next time, or increases the maximum number of times the first message is received.

[0241] Optionally, when it is determined that the processing time of the third message scheduled by the terminal device is greater than time T, the interface unit 810 is used to: send a fifth message, wherein the fifth message is used to instruct the terminal device not to count the next time it sends the first message, or to increase the maximum number of times the first message is sent.

[0242] Optionally, the interface unit 810 is used to: receive a third message, the third message is used to determine a fourth message, and when it is determined that the bandwidth that the terminal device can process is less than the transmission bandwidth of the fourth message, the interface unit 810 is used to: send a fifth message, wherein the fourth message is used for a random access process of the terminal device.

[0243] Optionally, the first message or the third message further includes information of the terminal device, where the information of the terminal device includes at least one of the type of the terminal device, supported bandwidth, and processing capability.

[0244] Optionally, the terminal device includes a reduced-capability RedCap type terminal device and an enhanced reduced-capability eRedCap type terminal device.

[0245] It should be understood that the device 800 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the device 800 can be specifically a terminal device or a network device in the above-mentioned embodiment, and the device 800 can be used to execute the various processes and / or steps corresponding to the terminal device or the network device in the above-mentioned method embodiment. To avoid repetition, it will not be repeated here.

[0246] The device 800 of each of the above schemes has the function of implementing the corresponding steps performed by the terminal device or network device in the above method; the above function can be implemented by hardware, or by hardware executing the corresponding software. The hardware or software includes one or more modules corresponding to the above function. For example, the above interface unit 810 may include a sending unit and a receiving unit, the sending unit can be used to implement the various steps and / or processes for performing the sending action corresponding to the above interface unit, and the receiving unit can be used to implement the various steps and / or processes for performing the receiving action corresponding to the above interface unit. The sending unit can be replaced by a transmitter, and the receiving unit can be replaced by a receiver, respectively performing the sending and receiving operations and related processing operations in each method embodiment.

[0247] In the embodiments of the present application, Figure 8 The device 800 in the embodiment may also be a chip or a chip system, such as a system on chip (SoC). Correspondingly, the interface unit 810 may be a transceiver circuit of the chip, which is not limited here.

[0248] Fig. 9Another information transmission device 900 provided by an embodiment of the present application is shown. The device 900 includes a processor 910, a communication interface 920, and a memory 930. The processor 910, the communication interface 920, and the memory 930 communicate with each other through an internal connection path, the memory 930 is used to store instructions, and the processor 910 is used to execute the instructions stored in the memory 930 to control the communication interface 920 to send and / or receive signals.

[0249] In a possible implementation, the device 900 is used to perform the above Figure 5-Figure 7 The various processes and steps corresponding to the terminal devices in the diagram.

[0250] The communication interface 920 is used to receive a second message, the second message is used to indicate that a third message is sent within a time T. The processor 910 is used to count the number of transmissions of the first message. When the communication interface 920 schedules the processing time of the third message to be greater than the time T, the counting rule is adjusted.

[0251] Optionally, the communication interface 920 is used to receive a fourth message; and the processor 910 is used to count the number of transmissions of the first message. When the bandwidth that the processor 910 can process is smaller than the transmission bandwidth of the fourth message, the counting rule is adjusted.

[0252] In another possible implementation, the device 900 is used to perform the above Figure 5-Figure 7 The various processes and steps corresponding to the network devices in the diagram.

[0253] The communication interface 920 is used to send a second message indicating that a third message is received within a time T. The processor 910 is used to count the number of transmissions of the first message. When the communication interface 1020 does not receive the third message within the time T, the counting rule is adjusted.

[0254] It should be understood that the device 900 can be specifically a terminal device or a network device in the above embodiment, and can be used to execute the various steps and / or processes corresponding to the terminal device or the network device in the above method embodiment. Optionally, the memory 930 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A part of the memory may also include a non-volatile random access memory. For example, the memory may also store information about the device type. The processor 910 may be used to execute instructions stored in the memory, and when the processor 910 executes the instructions stored in the memory, the processor 910 is used to execute the various steps and / or processes of the above method embodiment corresponding to the terminal device or the network device. The communication interface 920 may include a transmitter and a receiver, the transmitter may be used to implement the various steps and / or processes corresponding to the above communication interface for performing the sending action, and the receiver may be used to implement the various steps and / or processes corresponding to the above communication interface for performing the receiving action.

[0255] It should be understood that in the embodiments of the present application, the processor of the above-mentioned device may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0256] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0257] The present application also provides another chip, including: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is used to execute the code in the memory, and when the code is executed, the processor is used to execute the method in each of the above examples. Optionally, the chip also includes a memory, and the memory is used to store computer programs or codes.

[0258] The present application also provides a processor, which is coupled to a memory and is used to execute the methods and functions involving a network device or a terminal device in any of the above-mentioned embodiments.

[0259] In another embodiment of the present application, a computer program product including instructions is provided. When the computer program product is run on a computer, the method of the above embodiment is implemented.

[0260] The present application also provides a computer program. When the computer program is executed in a computer, the method of the above embodiment is implemented.

[0261] In another embodiment of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the method described in the above embodiment is implemented.

[0262] The present application also provides a communication system, which may include the above Figure 8 or Fig. 9 The terminal device shown (device 800 or device 900 is embodied as a terminal device), and the above Figure 8 or Fig. 9 The network device shown (device 800 or device 900 is embodied as a network device).

[0263] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software units in a processor for execution. The software unit can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor executes the instructions in the memory, and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0264] Those of ordinary skill in the art will appreciate that the various method steps and units described in the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those of ordinary skill in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0265] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0266] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0267] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0268] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0269] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0270] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0271] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0272] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A counting method, characterized in that: include: The terminal device counts the number of transmissions of the first message; The terminal device receives a second message, where the second message is used to indicate that a third message is to be sent within a time T, and when the processing time of the third message scheduled by the terminal device is greater than the time T, the counting rule is adjusted; or The terminal device receives a fourth message, and when the bandwidth that the terminal device can process is less than the transmission bandwidth of the fourth message, adjusts the counting rule, wherein the first message, the second message, the third message and the fourth message are used for the random access process of the terminal device.

2. The method according to claim 1, characterized in that The adjustment counting rules include: The next time the terminal device sends the first message, no counting is performed, or the maximum number of times the first message is sent is increased.

3. The method according to claim 1 or 2, characterized in that: After the terminal device receives the second message, the method further includes: The terminal device sends the third message, where the third message is used to indicate reception of the fourth message.

4. The method according to any one of claims 1 to 3, characterized in that The method comprises, The terminal device receives a fifth message, where the fifth message is used to indicate that no counting will be performed when the terminal device sends the first message next time, or that a maximum number of times the first message is sent will be increased.

5. The method according to any one of claims 1 to 4, characterized in that The terminal devices include reduced capability RedCap type terminal devices and enhanced reduced capability eRedCap type terminal devices.

6. A counting method, characterized in that: include: The network device counts the number of transmissions of the first message; The network device sends a second message, where the second message is used to indicate that a third message is received within time T. When the network device does not receive the third message within the time T, the counting rule is adjusted, wherein the first message, the second message and the third message are used for a random access process of a terminal device.

7. The method according to claim 6, characterized in that The adjustment counting rules include: The next time the network device receives the first message, no counting is performed, or a maximum number of reception times of the first message is increased.

8. The method according to claim 6 or 7, characterized in that: When it is determined that the processing time of the third message scheduled by the terminal device is greater than the time T, a fifth message is sent, wherein the fifth message is used to instruct the terminal device not to count when sending the first message next time, or to increase the maximum number of times the first message is sent.

9. The method according to claim 8, characterized in that After the network device sends the second message, the method further includes: The network device receives the third message, and the third message is used to determine the fourth message. When it is determined that the bandwidth that the terminal device can process is less than the transmission bandwidth of the fourth message, the fifth message is sent, wherein the fourth message is used for the random access process of the terminal device.

10. The method according to any one of claims 6 to 9, characterized in that: The terminal devices include reduced capability RedCap type terminal devices and enhanced reduced capability eRedCap type terminal devices.

11. A communication device, characterized in that: The method comprises means for implementing the method according to any one of claims 1 to 5.

12. A communication device, characterized in that: The method comprises means for implementing the method as claimed in any one of claims 6 to 10.

13. A communication device, characterized in that: include: A processor, wherein the processor is coupled to a memory, wherein the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the device executes the method according to any one of claims 1 to 5.

14. A communication device, characterized in that: include: A processor, wherein the processor is coupled to a memory, wherein the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the device executes the method according to any one of claims 6 to 10.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed, the computer is enabled to execute the method according to any one of claims 1 to 10.

16. A chip system, characterized in that: include: A processor, configured to call and run a computer program from a memory so that a device equipped with the chip system executes a method as described in any one of claims 1 to 10.

Images