Random access method and apparatus, and storage medium, program product and chip

Abstract

Provided in the embodiments of the present application are a random access method and apparatus, and a storage medium, a program product and a chip, which aim to solve the problem of contention collision. The method comprises: sending to a network device a first message transmitted by using a shared resource; and receiving a second message sent by the network device, wherein the second message comprises a medium access control protocol data unit, which comprises one or more sub-units, and the sub-unit is used for indicating a random access response result. Therefore, upon receiving a second message, a terminal device can determine a random access response result on the basis of the second message, thereby enabling the terminal device to determine whether the terminal device itself has succeeded in contention, such that the terminal device smoothly performs a service.

Description

A random access method, apparatus, storage medium, program product, and chip

[0001] This application claims priority to Chinese Patent Application No. 202510379417.1, filed with the State Intellectual Property Office of China on March 26, 2025, entitled "A Random Access Method, Apparatus, Storage Medium, Program Product and Chip", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a random access method, apparatus, storage medium, program product, and chip. Background Technology

[0003] In non-terrestrial (NTN) networks, base station configuration includes radio resource control (RRC) messages and uplink data transmission resources. Multiple terminal devices randomly select resources from the configured resources to send RRC messages and uplink data. Since the resources configured by the base station are shared resources used by multiple terminal devices, contention occurs when multiple terminal devices select the same resource, preventing normal service processing between the terminal devices and network equipment. Therefore, resolving this contention is a crucial technical problem that needs to be addressed. Summary of the Invention

[0004] This application provides a random access method, apparatus, storage medium, program product, and chip, with the aim of solving the problem of how to resolve race conditions.

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] The first aspect of this application provides a random access method, which can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. For example, the method is applied to a terminal device, but this application does not limit its application. The following description uses a terminal device as an example. The method includes:

[0007] Send the first message to the network device using shared resources;

[0008] The network device receives a second message; the second message includes a Media Access Control (MAC) protocol data unit; the MAC protocol data unit includes one or more sub-units; the sub-units are used to indicate the random access response result.

[0009] The first message can be an RRC connection request message, an RRC early data request message, an RRC connection resume request message, an RRC connection release request message, or other types of RRC messages, which are not limited here. The first message can also carry uplink data. The uplink data can be placed in a non-access stratum protocol data unit (NAS-PDU), and the first message carries this NAS-PDU. The uplink data can also be multiplexed with the first message and sent together.

[0010] The second message can be a Media Access Control (MAC) protocol data unit message, or a message multiplexed with an RRC message; the RRC message can be an RRC connection setup message, an RRC early data complete message, an RRC connection resume message, an RRC connection release message, or other types of RRC messages, which are not limited here.

[0011] In the above scheme, since the second message contains a sub-unit for indicating the random access response result, the terminal device can determine the random access response result based on the second message after receiving the second message, thereby enabling the terminal device to determine whether it has successfully competed for access, so that the terminal device can smoothly carry out its services.

[0012] The random access response is the response to the first message sent by the terminal.

[0013] In some possible implementations, the sub-unit includes: a media access control layer sub-header and a response entity for successful random access; or, the sub-unit includes the media access control layer sub-header and a response entity for random access rollback; or, the sub-unit includes a media access control layer sub-header for indicating rollback.

[0014] The response entity for successful random access is the same as the response entity for successful contention. It resolves the conflict caused by the first message sent by the terminal device and indicates the terminal that won the contention through the response entity for successful random access.

[0015] The response entity for random access rollback is the rollback response entity. It handles the contention caused by the first message sent by the terminal device and indicates the rollback operation through the response entity for random access rollback.

[0016] In the above scheme, since the sub-unit can contain a response entity for successful random access, or a response entity for random access rollback, or a media access control layer sub-header for indicating rollback, the sub-unit can feed back the response result of successful random access or the response result of random access rollback to the terminal, so that the terminal device can determine whether it has successfully competed for access, thereby avoiding the inability of the terminal device to process services normally due to competition conflicts.

[0017] In some possible implementations, the response entity for successful random access includes a first bit field; the first bit field is used to indicate whether the response entity for successful random access includes a temporary identifier of the cell radio network, or indicates the receipt of a third message and / or downlink data, or indicates that the terminal device has entered a connected state.

[0018] In the above scheme, the first bit field in the response entity of successful random access indicates whether the response entity of successful random access includes a temporary identifier of the cell radio network, or indicates the receipt of a third message and / or downlink data, or indicates that the terminal device enters the connected state. This enables the terminal device to determine whether the current contention is successful, or the action to be performed after the contention is successful, based on whether the indication includes a temporary identifier of the cell radio network, or whether the indication allows the terminal device to continue receiving a third message and / or downlink data, or whether the indication allows the terminal device to enter the connected state. This allows the terminal device to process services normally.

[0019] In some possible implementations, where the subunit includes a media access control layer subheader and a successful random access response entity, the media access control layer subheader includes a second bit field; the second bit field is used to indicate the length of the successful random access response entity.

[0020] To further illustrate with examples: the second bit field, used to indicate the length of the response entity for successful random access, can be 48 bits (6 bytes) or 64 bits (8 bytes). If the length of the response entity for successful random access is 48 bits (6 bytes), then the response entity includes the UE contention resolution identity. If the length of the response entity for successful random access is 64 bits (8 bytes), then the response entity includes: the UE contention resolution identity and the cell-radio network temporary identifier (C-RNTI).

[0021] The second bit field, used to indicate a successful random access response entity, can also be 64 bits (8 bytes) or 80 bits (10 bytes) long. If the length of the successful random access response entity is 64 bits, it includes: a terminal contention resolution identifier, and indication information for hybrid automatic repeat request (HARQ) feedback (indication information for HARQ feedback on the second message, which at least includes indication information for the resources used for HARQ feedback). If the length of the successful random access response entity is 80 bits, it includes: a UE contention resolution identifier, HARQ feedback indication information, and a C-RNTI.

[0022] In some possible implementations, where the sub-unit includes a Media Access Control (MAC) layer sub-header and a successful random access response entity, the MAC layer sub-header includes a third bit field; the third bit field is used to indicate whether the successful random access response entity includes a cell radio network temporary identifier.

[0023] If the response entity used in the third bit field to indicate successful random access includes the temporary identifier of the cell's wireless network, the terminal device receives a third message and / or downlink data, or enters a connected state.

[0024] In the above scheme, the third bit field in the Media Access Control layer subheader indicates whether the terminal device includes a temporary identifier for the cell network, so that the terminal device can determine whether the contention is successful or the action to be performed after the contention is successful based on whether the temporary identifier for the cell network is included, so that the terminal device can process services normally.

[0025] In some possible implementations, where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes a fourth bit field; the fourth bit field is used to indicate whether the successful random access response entity includes indication information indicating that the terminal device receives a third message and / or downlink data, or indicating entry into a connection state.

[0026] In the above scheme, the fourth bit field in the media access control layer subheader indicates whether the response entity for a successful random access instructs the terminal device to continue receiving the third message and / or downlink data, or indicates the connection status, so that the terminal device can determine whether the contention is successful or the action to be performed after the contention is successful based on the information indicated in the fourth bit field, so that the terminal device can process the service normally.

[0027] In some possible implementations, where the subunit includes a Media Access Control (MAC) layer subheader and a response entity for successful random access, the MAC layer subheader includes a fifth bit field; the fifth bit field is used to indicate that the terminal device has received a third message and / or downlink data, or to indicate that it has entered a connection state.

[0028] In the above scheme, the terminal device determines whether to continue receiving the third message and / or downlink data, or to enter the connection state, through the fifth bit field in the media access control layer subheader. This enables the terminal device to determine the action to be taken after the contention is successful, allowing the terminal device to process services normally.

[0029] In some possible implementations, where the subunit includes a Media Access Control (MAC) subheader for indicating fallback, or a MAC subheader and a random access fallback response entity, the MAC subheader for indicating fallback or the random access fallback response entity includes first information; the first information includes at least one of carrier information, physical resource block information, and frequency domain location information.

[0030] To further illustrate with examples: Carrier information can be a carrier identifier ID or a carrier index; physical resource block information can be a physical resource block identifier ID or a physical resource block index; frequency domain location information can be a frequency domain identifier location ID or a frequency domain location index. The UE determines whether the sub-unit (e.g., the media access control layer sub-header used to indicate backoff, or the media access control layer sub-header and the response entity for random access backoff) is related to itself based on the resources used to send the first message, such as the carrier identifier ID (or carrier index) or the identifier ID (or physical resource block index) or the frequency domain identifier location ID (or frequency domain location index).

[0031] If the information indicated in the Media Access Control (MAC) subheader or the response entity for random access backoff in the first message is different from the carrier identifier ID (or carrier index), physical resource block information identifier ID (or physical resource block index), or frequency domain location (or frequency domain location index) resource used to send the first message, then the UE considers that the sub-unit to be irrelevant to itself. If the information indicated in the MAC subheader or the response entity for random access backoff in the first message is the same as the carrier identifier ID (or carrier index), physical resource block information identifier ID (or physical resource block index), or frequency domain location ID (or frequency domain location index) used to send the first message, then the UE considers that the sub-unit to be relevant to itself, and the UE will perform a backoff operation according to the backoff instruction.

[0032] In some possible implementations, if the resource information used by the terminal device to send the first message matches the first information, then the second message is used to instruct the terminal device to roll back.

[0033] In the above scheme, when the resource information used by the first message matches the first information, the terminal device is instructed to roll back, thereby enabling rollback operations to be performed on some terminals in the terminal contention conflict, reducing network load.

[0034] In some possible implementations, the media access control layer subheader for indicating rollback or the response entity for random access rollback includes a bitmap; the bitmap is used to indicate whether to perform a rollback operation according to the obtained modulo result after obtaining a modulo result on the terminal device identifier, wherein N represents the number of bits included in the bitmap and N is a positive integer.

[0035] In the above scheme, the result of a modulo N operation on the bitmap and the terminal device identifier is compared to determine whether the terminal device should back off. This allows for backoff operations to be performed on some terminals involved in terminal contention, reducing network load. N is a positive integer greater than 1, and the number of bits occupied by the bitmap can be 1 bit, 2 bits, 3 bits, or 4 bits, without limitation.

[0036] To further illustrate with an example: If the bitmap is 0110 (assuming a bit value of "1" indicates a rollback, meaning terminals with a modulo result of 1 or 2 will execute a rollback), and N = 4, the modulo result can be 0, 1, 2, or 3. If a bit value of "1" indicates a rollback, then terminals with a modulo result of 1 or 2 will execute a rollback. If a bit value of "0" indicates a rollback, then terminals with a modulo result of 0 or 3 will execute a rollback.

[0037] When the 3-bit bitmap is 011, where 1 indicates a rollback operation, N is 6, and the modulo result is 0, 1, 2, 3, 4, or 5. When the terminal device's modulo result is 0 or 1, the terminal device executes the operation corresponding to the first bit in the bitmap. When the terminal device's modulo result is 2 or 3, the terminal device executes the operation corresponding to the second bit in the bitmap. When the terminal device's modulo result is 4 or 5, the terminal device executes the operation corresponding to the third bit in the bitmap. This mapping is predefined and not limited here.

[0038] In some possible implementations, the media access control layer subheader for indicating rollback or the response entity for random access rollback includes first threshold information; the first threshold information is used to indicate that if the delayed access time of the terminal device exceeds the first threshold information, the terminal device performs a rollback operation.

[0039] To further illustrate with an example: the first threshold information can be a threshold value for the index of the delayed access time, and there is a preset correspondence between the index of the delayed access time and the delayed access time. When the index value corresponding to the delayed access time of the terminal device exceeds the threshold value of the delayed access time index indicated by the first threshold information, the terminal device performs a rollback operation. For example, if the index value corresponding to a delayed access time of 100 milliseconds is 5, and the index value corresponding to a delayed access time of 150 milliseconds is 6, then when the first threshold information is 5, if the index value of the terminal device is 6, the terminal device performs a rollback operation.

[0040] The first threshold information can also be a threshold for delayed access time. When the delayed access time of the terminal device exceeds this threshold, a rollback operation is performed. For example, if the first threshold information is 200 milliseconds and the delayed access time of the terminal device is 230 milliseconds, then the delayed access time of the terminal device exceeds the first threshold information, and the terminal device performs a rollback operation.

[0041] In the above scheme, by judging the first threshold information of the terminal device's delayed access time, the terminal device can determine whether to back off, thereby realizing the back-off operation for some terminals in the terminal contention conflict and reducing network load.

[0042] In some possible implementations, where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes third information; the third information includes at least one of carrier information, physical resource block information, and frequency domain location information; the successful random access response entity includes a sixth bit field; the sixth bit field includes a terminal contention resolution identifier; the third information and / or the sixth bit field are used to determine whether the terminal device has successfully contented.

[0043] To further illustrate with an example: the carrier information can be the carrier identifier ID, and the physical resource block information can be the physical resource block information identifier ID. The UE determines whether the sub-unit (including the medium access control layer sub-header and the random access success response entity) is related to itself based on the resources used to send the first message, such as the carrier identifier ID or the physical resource block information identifier ID or the frequency domain location.

[0044] If the information indicated by the Media Access Control (MAC) subheader or the random access fallback response entity in the first message is different from the carrier identifier ID (or carrier index), physical resource block information identifier ID (or physical resource block index), or frequency domain location (or frequency domain location index) used to send the first message, then the UE considers that the sub-unit to be irrelevant to itself. If the information indicated by the MAC subheader or the random access fallback response entity in the first message is the same as the carrier identifier ID (or carrier index), physical resource block information identifier ID (or physical resource block index), or frequency domain location (or frequency domain location index) used to send the first message, the UE determines whether it has successfully competed based on the terminal contention resolution identifier in the random access success response entity. If the terminal contention resolution identifier in that entity matches the UE identifier used in the first message sent by the UE, then the UE has successfully competed.

[0045] A second aspect of this application provides a random access method, which may be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit the scope of the method. The following description uses a network device as an example. The method includes:

[0046] The receiving terminal device transmits the first message using shared resources;

[0047] A second message is sent to the terminal device; the second message includes a Media Access Control Layer Protocol (MAC) data unit; the MAC data unit includes one or more sub-units; the sub-units are used to indicate the random access response result.

[0048] The first message can be an RRC connection request, an RRC early data request, an RRC connection resume request, or other types of RRC messages; this is not limited to these. The first message can also carry uplink data. This uplink data can be placed in a non-access stratum protocol data unit (NAS-PDU), and the first message carries this NAS-PDU. The uplink data can also be multiplexed and sent together with the first message.

[0049] The second message can be a Media Access Control (MAC) Data Unit (DATA) message, or a message multiplexed with an RRC message. The RRC message can be an RRC connection setup message, an RRC early data complete message, an RRC connection resume message, an RRC connection release message, or other types of RRC messages; this is not limited to these specific types. The random access response is the response to the first message sent by the terminal.

[0050] In the above scheme, since the second message contains a sub-unit for indicating the random access response result, the terminal device can determine the random access response result based on the second message after receiving the second message, thereby enabling the terminal device to determine whether it has successfully competed for access, so that the terminal device can smoothly carry out its services.

[0051] In some possible implementations, the sub-unit includes: a media access control layer sub-header and a response entity for successful random access; or, the sub-unit includes: the media access control layer sub-header and a response entity for random access rollback; or, the sub-unit includes: a media access control layer sub-header for indicating rollback.

[0052] The response entity for successful random access is the same as the response entity for successful contention. It resolves the conflict caused by the first message sent by the terminal device and indicates the terminal that won the contention through the response entity for successful random access.

[0053] The response entity for random access rollback is the rollback response entity. It handles the contention caused by the first message sent by the terminal device and indicates the rollback operation through the response entity for random access rollback.

[0054] In the above scheme, since the sub-unit can contain a response entity for successful random access, or a response entity for random access rollback, or a media access control layer sub-header for indicating rollback, the sub-unit can feed back the response result of successful random access or the response result of random access rollback to the terminal, so that the terminal device can determine whether it has successfully competed for access, thereby avoiding the inability of the terminal device to process services normally due to competition conflicts.

[0055] In some possible implementations, the response entity for successful random access includes a first bit field; the first bit field is used to indicate whether the response entity for successful random access includes a temporary identifier of the cell radio network, or indicates the receipt of a third message and / or downlink data, or indicates that the terminal device has entered a connected state.

[0056] In the above scheme, the first bit field in the response entity of successful random access indicates whether the response entity of successful random access includes a temporary identifier of the cell radio network, or indicates the receipt of a third message and / or downlink data, or indicates that the terminal device enters the connected state. This enables the terminal device to determine whether the current contention is successful, or the action to be performed after the contention is successful, based on whether the indication includes a temporary identifier of the cell radio network, or whether the indication allows the terminal device to continue receiving a third message and / or downlink data, or whether the indication allows the terminal device to enter the connected state. This allows the terminal device to process services normally.

[0057] In some possible implementations, where the subunit includes a media access control layer subheader and a successful random access response entity, the media access control layer subheader includes a second bit field; the second bit field is used to indicate the length of the successful random access response entity.

[0058] To further illustrate with examples: the second bit field, used to indicate the length of the response entity for successful random access, can be 48 bits (6 bytes) or 64 bits (8 bytes). If the length of the response entity for successful random access is 48 bits (6 bytes), then the response entity includes the UE contention resolution identity. If the length of the response entity for successful random access is 64 bits (8 bytes), then the response entity includes: the UE contention resolution identity and the cell-radio network temporary identifier (C-RNTI).

[0059] The second bit field, used to indicate a successful random access response entity, can also be 64 bits (8 bytes) or 80 bits (10 bytes) long. If the length of the successful random access response entity is 64 bits, it includes: a terminal contention resolution identifier, and indication information for hybrid automatic repeat request (HARQ) feedback (indication information for HARQ feedback on the second message, which at least includes indication information for the resources used for HARQ feedback). If the length of the successful random access response entity is 80 bits, it includes: a UE contention resolution identifier, HARQ feedback indication information, and a C-RNTI.

[0060] In some possible implementations, where the sub-unit includes a Media Access Control (MAC) layer sub-header and a successful random access response entity, the MAC layer sub-header includes a third bit field; the third bit field is used to indicate whether the successful random access response entity includes a cell radio network temporary identifier.

[0061] If the response entity used in the third bit field to indicate successful random access includes the temporary identifier of the cell's wireless network, the terminal device receives a third message and / or downlink data, or enters a connected state.

[0062] In the above scheme, the third bit field in the Media Access Control layer subheader indicates whether the terminal device includes a temporary identifier for the cell network, so that the terminal device can determine whether the contention is successful or the action to be performed after the contention is successful based on whether the temporary identifier for the cell network is included, so that the terminal device can process services normally.

[0063] In some possible implementations, where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes a fourth bit field; the fourth bit field is used to indicate whether the successful random access response entity includes indication information indicating that the terminal device receives a third message and / or downlink data, or indicating entry into a connection state.

[0064] In the above scheme, the fourth bit field in the media access control layer subheader indicates whether the response entity for a successful random access instructs the terminal device to continue receiving the third message and / or downlink data, or indicates the connection status, so that the terminal device can determine whether the contention is successful or the action to be performed after the contention is successful based on the information indicated in the fourth bit field, so that the terminal device can process the service normally.

[0065] In some possible implementations, where the sub-unit includes a Media Access Control (MAC) layer sub-header and a random access success response entity, the MAC layer sub-header includes a fifth bit field; the fifth bit field is used to indicate that the terminal device receives a Radio Resource Control (RRC) message and / or downlink data, or to indicate entering a connection state.

[0066] In the above scheme, the terminal device determines whether to continue receiving the third message and / or downlink data, or to enter the connection state, through the fifth bit field in the media access control layer subheader. This enables the terminal device to determine the action to be taken after the contention is successful, allowing the terminal device to process services normally.

[0067] In some possible implementations, where the subunit includes a Media Access Control (MAC) subheader for indicating fallback, or a MAC subheader and a random access fallback response entity, the MAC subheader for indicating fallback or the random access fallback response entity includes first information; the first information includes at least one of carrier information, physical resource block information, and frequency domain location information.

[0068] To further illustrate with examples: Carrier information can be a carrier identifier ID or a carrier index; physical resource block information can be a physical resource block identifier ID or a physical resource block index; frequency domain location information can be a frequency domain identifier location ID or a frequency domain location index. The UE determines whether the sub-unit (such as a media access control layer sub-header used to indicate backoff, or a media access control layer sub-header and a random access backoff response entity) is related to itself based on the resources used to send the first message, such as the carrier identifier ID (or carrier index) or the physical resource block identifier ID (or physical resource block index) or the frequency domain location (or frequency domain location index).

[0069] If the information indicated by the Media Access Control (MAC) subheader or the random access backoff response entity in the first message is different from the carrier identifier ID (or carrier index), physical resource block information identifier ID (or physical resource block index), or frequency domain location (or frequency domain location index) resource used to send the first message, then the UE considers that the sub-unit is irrelevant to itself. If the information indicated by the MAC subheader or the random access backoff response entity in the first message is the same as the carrier identifier ID (or carrier index), physical resource block information identifier ID (or physical resource block index), or frequency domain location (or frequency domain location index) used to send the first message, then the UE considers that the sub-unit is relevant to itself, and the UE will perform a backoff operation according to the backoff instruction.

[0070] In some possible implementations, if the resource information used by the terminal device to send the first message matches the first information, then the second message is used to instruct the terminal device to roll back.

[0071] In the above scheme, when the resource information used by the first message matches the first information, the terminal device is instructed to roll back, thereby enabling rollback operations to be performed on some terminals in the terminal contention conflict, reducing network load.

[0072] In some possible implementations, the media access control layer subheader for indicating rollback or the response entity for random access rollback includes a bitmap; the bitmap is used to indicate whether to perform a rollback operation according to the modulo result after obtaining the modulo result of the terminal device identifier modulo N, where N represents the number of bits included in the bitmap and N is a positive integer.

[0073] In the above scheme, the result of a modulo N operation on the bitmap and the terminal device identifier is compared to determine whether the terminal device should back off. This allows for backoff operations to be performed on some terminals involved in terminal contention, reducing network load. N is a positive integer greater than 1, and the number of bits occupied by the bitmap can be 1 bit, 2 bits, 3 bits, or 4 bits, without limitation.

[0074] To further illustrate with an example: If the bitmap is 0110 (assuming a bit value of "1" indicates a rollback, meaning terminals with a modulo result of 1 or 2 will execute a rollback), and N = 4, the modulo result can be 0, 1, 2, or 3. If a bit value of "1" indicates a rollback, then terminals with a modulo result of 1 or 2 will execute a rollback. If a bit value of "0" indicates a rollback, then terminals with a modulo result of 0 or 3 will execute a rollback.

[0075] When the 3-bit bitmap is 011, where 1 indicates a rollback operation, N is 6, and the modulo result is 0, 1, 2, 3, 4, or 5. When the terminal device's modulo result is 0 or 1, the terminal device executes the operation corresponding to the first bit in the bitmap. When the terminal device's modulo result is 2 or 3, the terminal device executes the operation corresponding to the second bit in the bitmap. When the terminal device's modulo result is 4 or 5, the terminal device executes the operation corresponding to the third bit in the bitmap. This mapping is predefined and not limited here.

[0076] In some possible implementations, the media access control layer subheader for indicating rollback or the response entity for random access rollback includes first threshold information; the first threshold information is used to indicate that if the delayed access time of the terminal device exceeds the first threshold information, the terminal device performs a rollback operation.

[0077] To further illustrate with an example: the first threshold information can be a threshold value for the index of the delayed access time, and there is a preset correspondence between the index of the delayed access time and the delayed access time. When the index value corresponding to the delayed access time of the terminal device exceeds the threshold value of the delayed access time index indicated by the first threshold information, the terminal device performs a rollback operation. For example, if the index value corresponding to a delayed access time of 100 milliseconds is 5, and the index value corresponding to a delayed access time of 150 milliseconds is 6, then when the first threshold information is 5, if the index value of the terminal device is 6, the terminal device performs a rollback operation.

[0078] The first threshold information can also be a threshold for delayed access time. When the delayed access time of the terminal device exceeds this threshold, a rollback operation is performed. For example, if the first threshold information is 200 milliseconds and the delayed access time of the terminal device is 230 milliseconds, then the delayed access time of the terminal device exceeds the first threshold information, and the terminal device performs a rollback operation.

[0079] In the above scheme, by judging the first threshold information of the terminal device's delayed access time, the terminal device can determine whether to back off, thereby realizing the back-off operation for some terminals in the terminal contention conflict and reducing network load.

[0080] In some possible implementations, where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes third information; the third information includes at least one of carrier information, physical resource block information, and frequency domain location information; the successful random access response entity includes a sixth bit field; the sixth bit field includes a terminal contention resolution identifier; the third information and / or the sixth bit field are used to determine whether the terminal device has successfully contented.

[0081] To further illustrate with an example: the carrier information can be the carrier identifier ID, and the physical resource block information can be the physical resource block information identifier ID. The UE determines whether the sub-unit (including the medium access control layer sub-header and the random access success response entity) is related to itself based on the resources used to send the first message, such as the carrier identifier ID or the physical resource block information identifier ID or the frequency domain location.

[0082] If the information indicated by the Media Access Control (MAC) subheader or the response entity for random access fallback in the first message is different from the carrier identifier ID (or carrier index), physical resource block information identifier ID (or, physical resource block index), or frequency domain location (or, frequency domain location index) used to send the first message, then the UE considers that the sub-unit to be irrelevant to itself. If the information indicated by the MAC subheader or the response entity for random access fallback in the first message is the same as the carrier identifier ID (or carrier index), physical resource block information identifier ID (or, physical resource block index), or frequency domain location (or, frequency domain location index) used to send the first message, the UE determines whether it has successfully competed for the sub-unit based on the terminal contention resolution identifier in the response entity for successful random access. If the terminal contention resolution identifier in this entity matches the UE identifier used in the first message sent by the UE, then the UE has successfully competed for the sub-unit.

[0083] A third aspect of this application provides a communication device, including a module for performing the method provided in the first aspect, or a module for performing the method provided in the second aspect.

[0084] A fourth aspect of this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device, implement the method provided in the first aspect or the method provided in the second aspect.

[0085] The fifth aspect of this application provides a computer program product including instructions that, when executed, cause the method provided in the first aspect or the method provided in the second aspect to be implemented.

[0086] A sixth aspect of this application provides a chip including a processor coupled to a memory for executing a computer program or instructions stored in the memory, such that the chip implements the method provided in the first aspect or the method provided in the second aspect.

[0087] The seventh aspect of this application provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices and transmit them to the processor, or to send signals from the processor to other communication devices. The processor is used to implement the method provided in the first aspect or the method provided in the second aspect through logic circuits or executing code instructions. Attached Figure Description

[0088] Figure 1 is a schematic diagram of the system architecture of the communication system provided in an embodiment of this application;

[0089] Figure 2 is a schematic diagram of the interaction process between a terminal device and a network device provided in an embodiment of this application;

[0090] Figure 3 is a schematic diagram of the structure of a media access control layer protocol data unit provided in an embodiment of this application;

[0091] Figure 4 is a schematic diagram of the structure of a 10-byte random access success response entity provided in an embodiment of this application;

[0092] Figure 5 is a schematic diagram of the structure of a successful random access response entity with 8 octets provided in an embodiment of this application;

[0093] Figure 6 is a schematic diagram of another response entity with 8 octets for successful random access provided in an embodiment of this application;

[0094] Figure 7 is a schematic diagram of the structure of a successful random access response entity with 6 octets provided in an embodiment of this application;

[0095] Figure 8 is a schematic diagram of another media access control layer protocol data unit provided in an embodiment of this application;

[0096] Figure 9 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0097] Figure 10 is a structural example diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0098] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0099] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0100] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.

[0101] The embodiments of this application are applied to communication systems, which can be second-generation (2G) communication systems, third-generation (3G) communication systems, LTE systems, fifth-generation (5G) communication systems, LTE and 5G hybrid architectures, 5G new radio (5G NR) systems, and new communication systems that will emerge in the future development of communication.

[0102] The communication system includes a first device and a second device. The first device can be a network-side device used to provide network communication functions; in some cases, it is also called a network device or network element. The network device can typically be a base station (including functional units of a base station, or a combination of functional units of base stations) or a core network unit. The core network unit can be a functional unit within the core network, including but not limited to access and mobility management function (AMF) units or session management function (SMF) units. The second device can be a device accessing the network, typically a terminal. An example of a communication system is shown in Figure 1, which includes base station 1 and terminal 2.

[0103] In the embodiments provided in this application, the base station can be any device with wireless transceiver capabilities, including but not limited to: evolved Node B (NodeB, eNB, or e-NodeB) in Long Term Evolution (LTE), base station (gNodeB or gNB) or transmission receiving point / transmission reception point (TRP) in New Radio (NR), base stations in subsequent 3GPP evolutions, access nodes in Wi-Fi systems, wireless relay nodes, wireless backhaul nodes, etc. The base station can be: satellite base station, macro base station, micro base station, pico base station, small cell, relay station, or balloon station, etc. The base station can include one or more co-located or non-co-located transmission reception points (TRPs). The base station can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. The base station can communicate with the terminal, or it can communicate with the terminal through a relay station. The terminal can communicate with multiple base stations using different technologies. For example, the terminal can communicate with base stations that support LTE networks, base stations that support 5G networks, and can also establish dual connections with both LTE and 5G base stations.

[0104] In the embodiments provided in this application, the terminal can take various forms, such as a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, vehicle-mounted terminal device, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, wearable terminal device, etc. The terminal may also be referred to as terminal equipment, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, UE terminal equipment, terminal equipment, wireless communication equipment, UE agent, or UE device, etc. The terminal can also be a fixed terminal or a mobile terminal.

[0105] Specifically, in non-terrestrial networks, base stations are configured with shared resources for multiple terminal devices to use. These shared resources include RRC messages, which can carry uplink data. However, when multiple terminal devices attempt random access, if multiple devices initiate random access requests on the same resource, the limited resources prevent simultaneous access, leading to contention and preventing normal service processing. Therefore, this application provides a random access method, apparatus, storage medium, program product, and chip to enable terminal devices to determine whether they have successfully competed for access, resolve contention conflicts, and facilitate smooth service processing.

[0106] To make the technical solution of this application clearer and easier to understand, the following description, in conjunction with the accompanying drawings, introduces a random access method, apparatus, storage medium, program product, and chip provided in the embodiments of this application.

[0107] Referring to Figure 2, a flowchart of a random access method is shown. The method includes:

[0108] S201: The terminal device sends a first message to the network device for transmission using shared resources. Correspondingly, the network device receives the first message.

[0109] The first message is a message transmitted using shared resources, which can be a non-access stratum message, a data radio bearer message, an RRC message, or other messages transmitted using shared resources. This application will use an RRC message as an example for subsequent explanation.

[0110] The first message carries the payload of the Physical Uplink Shared Channel (PUSCH). RRC messages are specifically RRC-type messages, such as RRC Connection Request messages, RRC Advance Data Request messages, RRC Connection Resumption Request messages, RRC Connection Release Request messages, or other types of RRC messages.

[0111] The first message can also carry uplink data, which can be placed in a non-access stratum protocol data unit (NAS). The first message carries this NAS. The uplink data can also be multiplexed and sent together with the first message.

[0112] S202: The terminal device receives a second message sent by the network device; the second message includes a Media Access Control (MAC) data unit; the MAC data unit includes one or more sub-units; the sub-units are used to indicate the random access response result. Accordingly, the network device sends the second message to the terminal device.

[0113] The second message can be a response or indication message to the first message. Specifically, it can be a Media Access Control (MAC) Data Unit (DATA) message, or a message multiplexed with an RRC message. The RRC message can be an RRC connection establishment message, an RRC advance data completion message, an RRC connection restoration message, an RRC connection release message, or other types of RRC messages; this is not limited here. For example, when the first message is an RRC connection request message, the second message is an RRC connection establishment message or an RRC connection release message. When the first message is an RRC advance data request message, the second message is an RRC advance data completion message, an RRC connection release message, or an RRC connection establishment message. When the first message is an RRC connection restoration request message, the second message is an RRC connection restoration message, an RRC connection release message, or an RRC connection establishment message.

[0114] The Media Access Control Protocol Data Unit (MAC PDU) in the second message includes one or more sub-units, specifically Media Access Control Sub-Protocol Data Units (MAC subPDUs). The MAC PDU may also include optional padding. The random access response is the network device's response to the first message sent by the terminal device, and the random access response result includes successful random access or a fallback.

[0115] Specifically, when a MAC PDU includes a sub-unit, the sub-unit includes: a MAC subheader and a success random access response; or, the sub-unit includes: a MAC subheader and a fallback random access response; or, the sub-unit includes: a MAC subheader with a fallback indicator only.

[0116] If the subunit includes a Media Access Control (MAC) subheader and a response entity indicating successful random access, the subunit is used to indicate that the terminal device has successfully accessed the network. If the subunit includes a MAC subheader and a response entity indicating random access rollback, or a MAC subheader indicating rollback, the subunit is used to indicate that the terminal device has rolled back. It should be noted that the MAC subheader in a subunit including both a MAC subheader and a response entity indicating successful random access can have the same structure as the MAC subheader in a subunit including both a MAC subheader and a response entity indicating random access rollback, or they can have different structures; this is not limited here.

[0117] When a MAC PDU comprises multiple sub-units, at least one sub-unit includes: a Media Access Control (MAC) subheader and a response entity for successful random access; or, at least one sub-unit includes: a MAC subheader and a response entity for random access fallback; or, at least one sub-unit includes: a MAC subheader for indicating fallback. In addition to the sub-units including a MAC subheader and a response entity for successful random access, the sub-units including a MAC subheader and a response entity for random access fallback, and the sub-units including a MAC subheader for indicating fallback, the multiple sub-units may also be at least one of the following: a MAC subheader with a backoff indicator only, or a MAC subheader and a MAC service data unit for a common control channel, a dedicated control channel, or a dedicated traffic channel, or a MAC subheader and padding.

[0118] To make it easier to understand, the following example is provided:

[0119] Taking a Media Access Control (MAC) subheader containing 8 bits as an example, the MAC subheader used to indicate rollback can include any one of the X, Y, and Z fields. Specifically:

[0120] The number of bits occupied by the X field can be selected based on actual needs. For example, the X field can be a 2-bit field, indicating the carrier identifier ID, and / or the physical resource block information identifier ID, and / or the frequency domain position. In this case, the Media Access Control (MAC) subheader can be represented as X / R / R / R / R / R / R. The number of bits occupied by the Y field can be selected based on actual needs. For example, the Y field can be a 4-bit field, indicating the bitmap. In this case, the MAC subheader can be represented as Y / R / R / R / R. The number of bits occupied by the Z field can be selected based on actual needs. For example, the Z field can be a 2-bit field, used to indicate the threshold information for delayed access. In this case, the MAC subheader can be represented as Z / R / R / R / R / R / R.

[0121] When the subunit includes a media access control layer subheader and a successful random access response entity, the media access control layer subheader may include any one of the G, H, E, and I fields, specifically:

[0122] The number of bits occupied by the G field can be selected based on actual needs. For example, if the G field occupies 2 bits, it indicates the length of the response entity for successful random access. In this case, the Media Access Control (MAC) subheader can be represented as G / R / R / R / R / R / R. The number of bits occupied by the H field can be selected based on actual needs. For example, if the H field occupies 1 bit, it indicates whether the response entity for successful random access includes the cell radio network temporary identifier. In this case, the MAC subheader can be represented as H / R / R / R / R. The number of bits occupied by the E field can be selected based on actual needs. For example, if the E field occupies 1 bit, it indicates whether the response entity for successful random access includes information instructing the terminal device to receive a third message and / or downlink data, or indicating entry into a connected state. In this case, the MAC subheader can be represented as E / R / R / R / R / R / R. The number of bits occupied by the I field can be selected based on actual needs. For example, the I field can be a 1-bit field used to indicate that the terminal device is receiving a third message and / or downlink data, or to indicate that it has entered a connection state. In this case, the Media Access Control (MAC) subheader can be represented as I / R / R / R / R / R / R / R. In this invention, the R field can be a reserved field or a field used for other indication information or information content, and there is no limitation on this.

[0123] To further illustrate with an example, as shown in Figure 3, when a MAC PDU includes multiple sub-units, the structure of the MAC PDU can be as shown in Figure 3. The MAC PDU includes a MAC subPDU for carrying a backoff indicator (BI) access indication, a MAC subPDU for indicating backoff, a MAC subPDU for indicating successful random access, a MAC subPDU including a service data unit (SDU), and padding.

[0124] A MAC subPDU carrying a backoff indicator (BI) may include a 4-bit BI field header. A MAC subPDU indicating fallback includes a 4-bit Y field (or X field, or Z field) and a fallback random access response (fallback RAR). A MAC subPDU indicating successful random access includes a 1-bit H field (or G field, or E field, or I field) and a success random access response (success RAR). A MAC subPDU including a Service Data Unit includes an 8-bit header (illustrated herein as an R field, but could be other fields) and a Service Data Unit. The R field may be used to contain specific control information or status indication information (tu) or may be a reserved field. In this invention, the terms "field" and "domain" have the same meaning.

[0125] It should be noted that each MAC subPDU has 8 bits. When the number of bits occupied by a field in the MAC subPDU is less than 8 bits, it can be filled by the R field or other fields.

[0126] Furthermore, after receiving the second information, if the sub-unit includes a response entity indicating successful random access, and the terminal contention resolution identifier in the response entity matches the terminal identifier used in the first information, then the terminal device determines that the second information is related to itself. Since the second information includes a response entity indicating successful random access, the terminal device confirms that it has successfully competed for the second information.

[0127] The terminal contention resolution identifier includes at least the identifiers of terminal devices that the network device allows to access. If the identifier of a terminal device that the network device allows to access is the same as the terminal identifier used in the first information, then the terminal contention resolution identifier matches the terminal identifier used in the first information. In this embodiment, after the terminal device receives the second information, it matches the terminal contention resolution identifier in the second information with the terminal identifier used when the terminal sent the first information, so that the terminal device can determine whether the contention was successful.

[0128] Furthermore, the second information can also be used to indicate the actions to be taken by the terminal device after it has successfully competed for access. For example, the actions to be taken by the terminal device can be indicated through the medium access control layer subheader in the sub-unit or the response entity for successful random access. These actions could include continuing to receive radio resource control messages (RRC msg) or continuing to receive downlink data (DL data), etc.

[0129] In an optional embodiment, when the subunit includes a media access control layer subheader and a random access success response entity, the random access success response entity includes a first bit field; the first bit field is used to indicate whether the random access success response entity includes a cell radio network temporary identifier, or indicates the receipt of a third message and / or downlink data, or indicates that the terminal device has entered a connected state.

[0130] The first bit field occupies 1 bit in the response entity for successful random access, such as the K field in Figures 4 and 5. The value of the first bit field indicates whether the response entity for successful random access includes the cell radio network temporary identifier, indicates receipt of a third message and / or downlink data, or indicates that the terminal device has entered the connected state. For example, when the value of the first bit field is 1, it indicates that the response entity for successful random access includes the C-RNTI, or indicates receipt of a third message and / or downlink data, or indicates that the terminal device has entered the connected state. When the value of the first bit field is 0, it indicates that the response entity for successful random access does not include the C-RNTI, or indicates that the terminal device has stopped the random access procedure, or indicates that the terminal device has not entered the connected state.

[0131] When the first bit field is used to indicate whether the response entity for successful random access includes the Cell Radio Network Temporary Identifier (C-RNTI), the terminal device can determine the action to perform based on whether the response entity for successful random access includes the C-RNTI. For example, if the first bit field indicates that the response entity for successful random access includes the C-RNTI, the terminal device continues to receive the third message and / or downlink data after determining that the contention was successful. If the first bit field indicates that the response entity for successful random access does not include the C-RNTI, the terminal device stops the random access procedure after determining that the contention was successful.

[0132] In an alternative embodiment, where the subunit includes a media access control layer subheader and a successful random access response entity, the media access control layer subheader includes a second bit field; the second bit field is used to indicate the length of the successful random access response entity.

[0133] The second bit field, occupying 1 bit in the MAC header (e.g., the G field), indicates the length of the response entity for successful random access. For example, when the value of the second bit field is 1, it indicates that the length of the response entity for successful random access is A bits / B octets; when the value of the second bit field is 0, it indicates that the length of the response entity for successful random access is C bits / D octets.

[0134] Since the response entity for successful random access has different lengths when it has a C-RNTI and when it does not, this embodiment of the application can determine whether the response entity for successful random access has a C-RNTI by the length of the response entity for successful random access indicated by the second bit field, so as to indicate the action to be performed by the terminal device after successful contention. For example, taking the length of the response entity for successful random access with a C-RNTI as 80 bits / 10 octets and the length of the response entity for successful random access without a C-RNTI as 64 bits / 8 octets, when the second bit field indicates that the length of the response entity for successful random access is 80 bits / 10 octets, the response entity for successful random access is as shown in Figure 4, which includes at least one of the following: UE contention resolution identifier, HARQ feedback indication information, and C-RNTI. The terminal device determines that the response entity for successful random access has a C-RNTI, and the terminal device continues to receive the third message and / or downlink data. When the length of the response entity indicating successful random access in the second bit field is 64 bits / 8 octets, the response entity indicating successful random access is as shown in Figure 5. It includes at least one of the following: UE contention resolution identifier and HARQ feedback indication information. The response entity indicating successful random access does not have C-RNTI. After the terminal device determines that the contention is successful, it stops the random access procedure.

[0135] Taking the length of the successful random access response entity as 64 bits / 8 octets when it has a C-RNTI and 48 bits / 6 octets when it does not have a C-RNTI as an example, when the second bit field indicates that the length of the successful random access response entity is 64 bits / 8 octets, the successful random access response entity is as shown in Figure 6, and includes at least one of the following: UE contention resolution identifier and C-RNTI. The terminal device determines that the successful random access response entity has a C-RNTI, and the terminal device continues to receive the third message and / or downlink data. When the second bit field indicates that the length of the successful random access response entity is 48 bits / 6 octets, the successful random access response entity is as shown in Figure 7, and includes a terminal contention resolution identifier. The terminal device determines that the successful random access response entity does not have a C-RNTI, and the terminal device stops the random access procedure after determining that the contention is successful.

[0136] It should be noted that the response entity for successful random access includes at least a terminal contention resolution identifier, and may also include a field containing HARQ feedback indication information. The HARQ feedback indication information may include one or more of the following: channel access type - cyclic prefix (CP), channel access-cpex, transmission power control (TPC), HARQ feederback timing, and physical uplink control channel resource indicator (PUCCH resource indicator). The HARQ feedback indication information can be 8 bits or other lengths, which are not limited here.

[0137] In an optional embodiment, when the sub-unit includes a Media Access Control (MAC) layer sub-header and a random access success response entity, the MAC layer sub-header includes a third bit field; the third bit field is used to indicate whether the random access success response entity includes a cell radio network temporary identifier.

[0138] In cases where the response entity used in the third bit field to indicate successful random access includes a temporary identifier for the cell's wireless network, the terminal device receives a third message and / or downlink data, or enters a connected state.

[0139] The third bit field, occupying 1 bit in the MAC header (e.g., the H field), indicates whether the response entity for successful random access includes the C-RNTI. For example, when the third bit field is 1, it indicates that the response entity for successful random access includes the C-RNTI, and the terminal device receives the third message and / or downlink data, or enters the connected state. When the third bit field is 0, it indicates that the response entity for successful random access does not include the C-RNTI, and the terminal device stops the random access procedure after determining that the contention was successful, or the terminal device does not enter the connected state.

[0140] In an optional embodiment, when the subunit includes a media access control layer subheader and a response entity for successful random access, the media access control layer subheader includes a fourth bit field; the fourth bit field is used to indicate whether the response entity for successful random access includes indication information indicating that the terminal device receives a third message and / or downlink data, or indication information indicating entry into a connection state.

[0141] The fourth bit field, occupying 1 bit in the MAC subheader (e.g., the E field), indicates whether the response entity for successful random access includes instructions to the terminal device to continue receiving third messages and / or downlink data. For example, when the fourth bit field is 1, it indicates that the response entity for successful random access includes instructions to the terminal device to receive third messages and / or downlink data, or instructions to the terminal device to enter a connected state. When the fourth bit field is 0, it indicates that the response entity for successful random access does not include instructions to the terminal device to receive third messages and / or downlink data, or instructions to the terminal device to enter a connected state.

[0142] In an optional embodiment, where the subunit includes a Media Access Control (MAC) layer subheader and a response entity indicating successful random access, the MAC layer subheader includes a fifth bit field; the fifth bit field is used to indicate that the terminal device has received a third message and / or downlink data, or to indicate that it has entered a connection state.

[0143] The fifth bit field, occupying 1 bit in the MAC subheader (e.g., the I field), indicates whether the terminal device should continue receiving third messages and / or downlink data, or whether it should enter a connected state. For example, a value of 1 indicates that the terminal device should receive third messages and / or downlink data, or that it should enter a connected state. A value of 0 indicates that the terminal device should terminate the random access procedure, or that it should not enter a connected state.

[0144] In an optional embodiment, when the subunit includes a media access control layer subheader and a random access success response entity, the media access control layer subheader includes third information; the third information includes at least one of carrier information, physical resource block information, and frequency domain location information; the random access success response entity includes at least a sixth bit field; the sixth bit field includes a terminal contention resolution identifier; the third information and / or the sixth bit field are used to determine whether the terminal device has successfully contented.

[0145] The carrier information in the third information can be a carrier identifier (ID) or a carrier index, and the frequency domain location information can be a physical resource block identifier (ID) or a physical resource block index. In the case where the sub-unit includes a Media Access Control (MAC) layer sub-header and a successful random access response entity, if the information indicated by the MAC layer sub-header in the third information does not match the carrier identifier (ID) (or carrier index), physical resource block identifier (ID) (or physical resource block index), or frequency domain location identifier (ID) (or frequency domain location index) used by the terminal device when sending the first message, then the terminal device determines that the sub-unit is unrelated to itself. If the information indicated by the MAC layer sub-header in the third information matches the carrier identifier (ID) (or carrier index), physical resource block identifier (ID) (or physical resource block index), or frequency domain location identifier (ID) (or frequency domain location index) used by the terminal device when sending the first message, then the terminal device determines that the sub-unit is related to itself, and the terminal device determines that it has successfully competed for the sub-unit. If, after the terminal device determines that the sub-unit is related to itself, the response entity for successful random access also includes a sixth bit field, the terminal device further determines whether it has successfully competed for access based on whether the terminal contention resolution identifier in the sixth bit field is the same as the terminal device identifier used by the terminal device when sending the first message. If the terminal contention resolution identifier in the sixth bit field is the same as the terminal device identifier used by the terminal device when sending the first message, the terminal device stops the second message response window, successfully completes the random access procedure, thereby improving the processing efficiency of the second message and avoiding signaling congestion.

[0146] When the Media Access Control (MAC) layer subheader includes third information, the MAC PDU can indicate the third information through the J field. The structure of the MAC PDU can then be as shown in Figure 8. The MAC PDU includes a MAC subPDU for carrying a delayed access indication, a MAC subPDU for indicating a fallback, a MAC subPDU for indicating successful random access, a MAC subPDU including a Service Data Unit, and padding. The J field indicating the third information can be a 1-bit field, or a 2-bit or 4-bit field; no limitation is made here.

[0147] Furthermore, after receiving the second information, if the sub-unit is used to instruct the terminal device to roll back, then at least one sub-unit in the second information includes a MAC sub-header for instructing rollback, or a MAC sub-header and a response entity for random access rollback. The terminal device determines whether to perform a rollback operation based on the first information in the MAC sub-header or the response entity for random access rollback, and / or the bitmap, and / or the first threshold information.

[0148] Specifically, when the subunit includes a Media Access Control (MAC) subheader for indicating backoff, or a MAC subheader and a response entity for random access backoff, the MAC subheader for indicating backoff or the response entity for random access backoff includes first information; the first information includes at least one of carrier information, physical resource block information, and frequency domain location information. The carrier information can be a carrier identifier ID, the physical resource block information can be a physical resource block identifier ID, and the frequency domain location information can be a frequency domain identifier location ID.

[0149] When the subunit includes a Media Access Control (MAC) subheader for indicating rollback, the MAC subheader for indicating rollback includes first information. When the subunit includes a MAC subheader and a random access rollback response entity, either the MAC subheader or the random access rollback response entity includes the first information.

[0150] In an optional embodiment, if the sub-unit's instruction to the terminal device to roll back, the MAC header in the second information, or the response entity for random access rollback includes the first information, then it is determined whether the resources used by the terminal device to send the first message match the first information. If the resources used to send the first message are exactly the same as the information of the same category included in the first information, it is determined that the resources used by the terminal device to send the first message match the first information. If the resources used to send the first message are exactly the same as the information included in the first information, it is determined that the resources used by the terminal device to send the first message do not match the first information. If the resource information used by the terminal device to send the first message matches the first information, then the second message is used to instruct the terminal device to roll back, thereby instructing some terminal devices to perform rollback operations during the contention process, reducing network load.

[0151] To further illustrate with an example: Carrier information can be carrier identifier ID, physical resource block information can be physical resource block information identifier ID, and frequency domain location information can be frequency domain identifier location ID. The UE determines whether the sub-unit (the medium access control layer sub-header used to indicate backoff, or the medium access control layer sub-header and the response entity for random access backoff) is related to itself based on the resources used to send the first message, such as carrier identifier ID, physical resource block information identifier ID, or frequency domain identifier location ID.

[0152] If the carrier identifier ID, physical resource block information identifier ID, or frequency domain identifier location ID included in the first information is different from the carrier identifier ID, physical resource block information identifier ID, or frequency domain identifier location ID used to send the first message, then the UE considers the sub-unit to be unrelated to itself. If the carrier identifier ID, physical resource block information identifier ID, or frequency domain identifier location ID included in the first information is the same as the carrier identifier ID, physical resource block information identifier ID, or frequency domain identifier location ID used to send the first message, then the UE considers the sub-unit to be related to itself, and the UE will perform a backoff operation according to the backoff instruction.

[0153] For example, when the resources used by the terminal device to send the first message include carrier information X1, physical resource block information X2, and frequency domain location information X3, and the first information includes carrier information X1 and physical resource block information Y1, since the carrier information in both the first message and the first information is X1, the carrier information in the first message and the first information is the same. However, the physical resource block information in the first message is X2, which is different from the physical resource block information in the second information, which is Y1. Therefore, the resources used when sending the first message are not completely the same as the information of the same category included in the first information, and the resources used by the terminal device to send the first message do not match the first information.

[0154] In one optional embodiment, the media access control layer subheader or random access rollback response entity used to indicate rollback includes a bitmap; the bitmap is used to indicate whether to perform a rollback operation according to the modulo result after obtaining the modulo result of the terminal device identifier modulo N, where N represents the number of bits included in the bitmap and N is a positive integer.

[0155] When the response entity of the subunit used to indicate terminal device rollback, MAC subheader in the second message, or random access rollback includes the first information and a bitmap, the second message includes a bitmap of N bits. The bitmap includes execution operations corresponding to N modulo results or M modulo results, where N is an integer greater than or equal to 1, and M is an integer greater than N. If the bitmap includes N modulo results, the execution operations corresponding to the N modulo results correspond one-to-one with the execution operations corresponding to the N bits in the bitmap. For example, the execution operation corresponding to the modulo result of N-1 is the execution operation corresponding to the value of the Nth bit in the bitmap. If the bitmap includes M modulo results, the M modulo results are divided into N parts, and the execution operation corresponding to each part of the modulo results corresponds one-to-one with the execution operations corresponding to the N bits in the bitmap. For example, when N is 2 and M is 4, the operation corresponding to the value of the first bit in the bit diagram is executed when the modulo result is 0 or 1, and the operation corresponding to the value of the second bit in the bit diagram is executed when the modulo result is 2 or 3. The operation corresponding to the value of the bit in the bit diagram can be set according to actual needs and is not limited here. For example, when the modulo result is 0, the operation corresponding to the modulo result is executed when the modulo result is 0, and the operation corresponding to the value of the first bit in the bit diagram is executed when the modulo result is 1.

[0156] After receiving the second message, the terminal device performs a modulo-N operation to obtain the modulo result. It then queries the bitmap to find the corresponding execution operation. For example, if the bit value corresponding to the modulo result in the bitmap is 1, the execution operation is a rollback operation. If the found execution operation is a rollback operation, the terminal device considers the second message successfully received and executes the rollback operation. This instructs some terminal devices to execute rollback operations during contention, reducing network load.

[0157] To facilitate understanding, the following examples will be provided:

[0158] When the 3-bit bitmap is 011, where 1 indicates a rollback operation, N is 3, and the modulo result is 0, 1, or 2. When the terminal device's modulo result is 0, the terminal device executes the operation corresponding to the first bit in the bitmap. When the terminal device's modulo result is 1, the terminal device executes the operation corresponding to the second bit in the bitmap. Since the second bit in the bitmap is 1, the operation corresponding to the second bit in the bitmap is a rollback operation. When the terminal device's modulo result is 3, the terminal device executes the operation corresponding to the third bit in the bitmap. Since the third bit in the bitmap is 1, the operation corresponding to the third bit in the bitmap is a rollback operation.

[0159] When the 3-bit bitmap is 011, where 1 indicates a rollback operation, N is 6, and the modulo result is 0, 1, 2, 3, 4, or 5. When the terminal device's modulo result is 0 or 1, the terminal device executes the operation corresponding to the first bit in the bitmap. When the terminal device's modulo result is 2 or 3, the terminal device executes the operation corresponding to the second bit in the bitmap. When the terminal device's modulo result is 4 or 5, the terminal device executes the operation corresponding to the third bit in the bitmap. This mapping is predefined and not limited here.

[0160] In one optional embodiment, the Media Access Control Layer subheader or the response entity for indicating rollback includes first threshold information; the first threshold information is used to indicate that if the terminal device's delayed access time exceeds the first threshold information, the terminal device performs a rollback operation.

[0161] When the response entity in the subunit used to instruct the terminal device to back off, or the MAC header or random access backoff in the second information, includes the first information and the first threshold information, after receiving the second message, the terminal device determines whether its delayed access time is greater than the first threshold information. If it is greater than the first threshold information, the terminal device considers the second message successfully received and performs a backoff operation. This instructs some terminal devices to perform a backoff operation during the contention process, reducing network load. The first threshold information is the threshold information for delayed access BI.

[0162] To further illustrate with an example: the first threshold information can be a threshold value for the index of the delayed access time, and there is a preset correspondence between the index of the delayed access time and the delayed access time. When the index value corresponding to the delayed access time of the terminal device exceeds the threshold value of the delayed access time index indicated by the first threshold information, the terminal device performs a rollback operation. For example, if the index value corresponding to a delayed access time of 100 milliseconds is 5, and the index value corresponding to a delayed access time of 150 milliseconds is 6, then when the first threshold information is 5, if the index value of the terminal device is 6, the terminal device performs a rollback operation.

[0163] The first threshold information can also be a threshold for delayed access time. When the delayed access time of the terminal device exceeds this threshold, a rollback operation is performed. For example, if the first threshold information is 200 milliseconds and the delayed access time of the terminal device is 230 milliseconds, then the delayed access time of the terminal device exceeds the first threshold information, and the terminal device performs a rollback operation.

[0164] In this embodiment, the information carried in the Media Access Control layer subheader of the second information, or in the response entity for successful random access, or in the response entity for random access rollback, instructs the terminal device to continue receiving the third message and / or downlink data, or instructs the terminal device to enter the connection state, so that the terminal device can determine whether the contention is successful, thereby performing a rollback operation on the terminal that cannot access, reducing the network load, and enabling the terminal device that successfully competes to process services smoothly.

[0165] The embodiment also provides a communication device including a module for performing a random access method.

[0166] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device, implement a method for random access.

[0167] This application also provides a computer program product, including instructions that, when executed, enable a random access method.

[0168] This application also provides a chip, including a processor coupled to a memory, for executing computer programs or instructions stored in the memory, thereby enabling the chip to implement a random access method.

[0169] This application also provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices and transmit them to the processor, or to send signals from the processor to other communication devices. The processor is used to implement a random access method through logic circuits or executing code instructions.

[0170] Figure 9 is another schematic block diagram of a communication device 900 provided in an embodiment of this application. The communication device 900 may be a chip, chip system, or processor, etc., used by a terminal device or network device to implement the above-described methods. The communication device 900 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0171] As shown in Figure 9, the communication device 900 may include one or more processors 910, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 910 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 900 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0172] In an alternative design, the processor 910 may also store instructions and / or data that can be executed by the processor 910 to cause the communication device 900 to perform the methods described in the above method embodiments.

[0173] In another alternative design, the communication device 900 may include a communication interface 920 for implementing receiving and transmitting functions. For example, the communication interface 920 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0174] Optionally, the communication device 900 may include one or more memories 930, which may store instructions that can be executed on the processor 910, causing the communication device 900 to perform the methods described in the above method embodiments. Optionally, the memories 930 may also store data. Optionally, the processor 910 may also store instructions and / or data. The processor 910 and the memories 930 may be provided separately or integrated together.

[0175] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0176] In one implementation, the communication device 900 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 910 may be used to execute instructions stored in the memory 930, 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 embodiments corresponding to the terminal device.

[0177] In another implementation, the communication device 900 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 910 may be used to execute instructions stored in the memory 930, 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 embodiments corresponding to the network device.

[0178] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0179] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0180] Figure 10 illustrates an example of the composition of an electronic device provided in this application. This electronic device can be a terminal device, including but not limited to mobile phones, smart wearable devices (such as smartwatches), and other electronic devices. Taking a mobile phone as an example, the electronic device may include a processor 1010, an external memory interface 1020, internal memory 1021, a display screen 1030, a camera 1040, antenna 1, antenna 2, a mobile communication module 1050, and a wireless communication module 1060, etc.

[0181] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0182] It is understood that the interface connection relationships between the modules illustrated in this embodiment are merely illustrative and do not constitute a limitation on the structure of the electronic device. In other embodiments of this application, the electronic device may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0183] The external storage interface 1020 can be used to connect external storage cards, such as Micro SD cards, to expand the storage capacity of electronic devices.

[0184] Internal memory 1021 can be used to store executable program code, which includes instructions. Processor 1010 executes various functional applications and data processing of electronic devices by running the instructions stored in internal memory 1021.

[0185] The wireless communication function of electronic devices can be implemented through antenna 1, antenna 2, mobile communication module 1050, wireless communication module 1060, modem processor, and baseband processor.

[0186] The mobile communication module 1050 can provide solutions for wireless communication applications, including 2G / 3G / 4G / 5G, in electronic devices. The mobile communication module 1050 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc.

[0187] Furthermore, an operating system runs on top of the aforementioned components. Examples include iOS, Android, and Windows operating systems. Applications can be installed and run on this operating system. Those skilled in the art will understand that, for the sake of convenience and brevity, explanations and beneficial effects of the relevant content in any of the above-described electronic devices can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0188] This application also provides a chip system including a processor for supporting terminal devices or network devices in implementing the functions involved in the above aspects, such as transmitting or processing data and / or information involved in the above methods. In one possible design, the chip system further includes a memory for storing necessary program instructions and data for the terminal device or network device. The chip system may be composed of chips or may include chips and other discrete devices.

[0189] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0190] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0191] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0192] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0193] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A random access method, characterized in that, Applied to a terminal device, the method includes: Send the first message to the network device using shared resources; The network device receives a second message; the second message includes a Media Access Control (MAC) protocol data unit; the MAC protocol data unit includes one or more sub-units; the sub-units are used to indicate the random access response result.

2. The method according to claim 1, characterized in that, The sub-unit includes: a media access control layer sub-header and a response entity for successful random access; Alternatively, the sub-unit may include: a media access control layer sub-header and a random access fallback response entity; Alternatively, the sub-unit may include a media access control layer sub-header for indicating rollback.

3. The method according to claim 2, characterized in that, The response entity for successful random access includes a first bit field; the first bit field is used to indicate whether the response entity for successful random access includes a temporary identifier of the cell radio network, or indicates the receipt of a third message and / or downlink data, or indicates that the terminal device has entered a connected state.

4. The method according to claim 2, characterized in that, In the case where the subunit includes a media access control layer subheader and a successful random access response entity, the media access control layer subheader includes a second bit field; the second bit field is used to indicate the length of the successful random access response entity.

5. The method according to claim 2, characterized in that, In the case where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes a third bit field; the third bit field is used to indicate whether the successful random access response entity includes a cell radio network temporary identifier. If the response entity used in the third bit field to indicate successful random access includes the temporary identifier of the cell's wireless network, the terminal device receives a third message and / or downlink data, or enters a connected state.

6. The method according to claim 2, characterized in that, In the case where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes a fourth bit field; the fourth bit field is used to indicate whether the successful random access response entity includes indication information indicating that the terminal device receives a third message and / or downlink data, or indicating that it has entered a connection state.

7. The method according to claim 2, characterized in that, In the case where the subunit includes a Media Access Control (MAC) layer subheader and a response entity for successful random access, the MAC layer subheader includes a fifth bit field; the fifth bit field is used to indicate that the terminal device has received a third message and / or downlink data, or to indicate that it has entered a connection state.

8. The method according to claim 2, characterized in that, When the subunit includes a Media Access Control (MAC) subheader for indicating fallback, or a MAC subheader and a random access fallback response entity, the MAC subheader for indicating fallback or the random access fallback response entity includes first information; the first information includes at least one of carrier information, physical resource block information, and frequency domain location information.

9. The method according to claim 8, characterized in that, If the resource information used by the terminal device to send the first message matches the first information, then the second message is used to instruct the terminal device to roll back.

10. The method according to claim 8, characterized in that, The media access control layer subheader used to indicate rollback or the response entity for random access rollback includes a bitmap; the bitmap is used to indicate whether to perform a rollback operation according to the modulo result after obtaining the modulo result of the terminal device identifier modulo N, where N represents the number of bits included in the bitmap and N is a positive integer.

11. The method according to claim 8, characterized in that, The media access control layer subheader used to indicate rollback or the response entity for random access rollback includes first threshold information; the first threshold information is used to indicate that if the delayed access time of the terminal device exceeds the first threshold information, the terminal device performs a rollback operation.

12. The method according to claim 2, characterized in that, In the case where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes third information; the third information includes at least one of carrier information, physical resource block information, and frequency domain location information; the successful random access response entity includes a sixth bit field; the sixth bit field includes a terminal contention resolution identifier; the third information and / or the sixth bit field are used to determine whether the terminal device has successfully contented.

13. A random access method, characterized in that, Applied to network devices, the method includes: The receiving terminal device transmits the first message using shared resources; A second message is sent to the terminal device; the second message includes a Media Access Control Layer Protocol (MAC) data unit; the MAC data unit includes one or more sub-units; the sub-units are used to indicate the random access response result.

14. The method according to claim 13, characterized in that, The sub-unit includes: a media access control layer sub-header and a response entity for successful random access; Alternatively, the sub-unit may include: the media access control layer sub-header and the random access fallback response entity; Alternatively, the sub-unit may include a media access control layer sub-header for indicating rollback.

15. The method according to claim 14, characterized in that, The response entity for successful random access includes a first bit field; the first bit field is used to indicate whether the response entity for successful random access includes a temporary identifier of the cell radio network, or indicates the receipt of a third message and / or downlink data, or indicates that the terminal device has entered a connected state.

16. The method according to claim 14, characterized in that, In the case where the subunit includes a media access control layer subheader and a successful random access response entity, the media access control layer subheader includes a second bit field; the second bit field is used to indicate the length of the successful random access response entity.

17. The method according to claim 14, characterized in that, In the case where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes a third bit field; the third bit field is used to indicate whether the successful random access response entity includes a cell radio network temporary identifier. If the response entity used in the third bit field to indicate successful random access includes the temporary identifier of the cell's wireless network, the terminal device receives a third message and / or downlink data, or enters a connected state.

18. The method according to claim 14, characterized in that, In the case where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes a fourth bit field; the fourth bit field is used to indicate whether the successful random access response entity includes indication information indicating that the terminal device receives a third message and / or downlink data, or indicating that it has entered a connection state.

19. The method according to claim 14, characterized in that, In the case where the subunit includes a Media Access Control (MAC) layer subheader and a random access success response entity, the MAC layer subheader includes a fifth bit field; the fifth bit field is used to indicate that the terminal device receives a Radio Resource Control (RRC) message and / or downlink data, or to indicate that it has entered a connection state.

20. The method according to claim 14, characterized in that, When the subunit includes a Media Access Control (MAC) subheader for indicating fallback, or a MAC subheader and a random access fallback response entity, the MAC subheader for indicating fallback or the random access fallback response entity includes first information; the first information includes at least one of carrier information, physical resource block information, and frequency domain location information.

21. The method according to claim 20, characterized in that, If the resource information used by the terminal device to send the first message matches the first information, then the second message is used to instruct the terminal device to roll back.

22. The method according to claim 20, characterized in that, The media access control layer subheader used to indicate rollback or the response entity for random access rollback includes a bitmap; the bitmap is used to indicate whether to perform a rollback operation according to the modulo result after obtaining the modulo result of the terminal device identifier modulo N, where N represents the number of bits included in the bitmap and N is a positive integer.

23. The method according to claim 20, characterized in that, The media access control layer subheader used to indicate rollback or the response entity for random access rollback includes first threshold information; the first threshold information is used to indicate that if the delayed access time of the terminal device exceeds the first threshold information, the terminal device performs a rollback operation.

24. The method according to claim 14, characterized in that, In the case where the subunit includes a Media Access Control (MAC) layer subheader and a successful random access response entity, the MAC layer subheader includes third information; the third information includes at least one of carrier information, physical resource block information, and frequency domain location information; the successful random access response entity includes a sixth bit field; the sixth bit field includes a terminal contention resolution identifier; the third information and / or the sixth bit field are used to determine whether the terminal device has successfully contented.

25. A communication device, characterized in that, It includes modules for performing the method as described in any one of claims 1 to 12, or modules for performing the method as described in any one of claims 13 to 24.

26. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 12, or 13 to 24.

27. A computer program product, characterized in that, Includes instructions that, when executed, cause the method as described in any one of claims 1 to 12, or 13 to 24, to be implemented.

28. A chip, characterized in that, The chip includes a processor coupled to a memory for executing a computer program or instructions stored in the memory, such that the chip implements the method of any one of claims 1 to 12, or 13 to 24.

29. A communication device, characterized in that, The device includes a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, the processor being used to implement the method as described in any one of claims 1 to 12, or 13 to 24, through logic circuits or executing code instructions.

Images