Communication method and apparatus, user equipment, network device, and medium

Abstract

The present application discloses a communication method and apparatus, a user equipment (UE), a network device, and a medium. Specifically, a UE receives configuration information. The configuration information is used for enabling a device in a first cell to directly execute a contention-based MO-EDT data sending operation. The device of the first cell comprises the user equipment. The UE sends a target request message on the basis of the configuration information and trigger information of the UE. The target request message is a message carrying user data of the UE, or the target request message is a message multiplexed with the user data, and the trigger information is used for determining whether the UE can execute the contention-based MO-EDT data sending operation. The procedure does not require sending msg1 and msg2, and thus helps reduce the overhead of uplink signaling and downlink signaling during the EDT procedure and increase the utilization rate of uplink resources and downlink resources, thereby improving the effect of uplink capacity.

Description

A communication method, apparatus, user equipment, network equipment, and medium

[0001] This application claims priority to Chinese Patent Application No. 202411605319.7, filed on November 8, 2024, entitled "A Communication Method, Apparatus, User Equipment, Network Equipment and Medium", 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 communication method, apparatus, user equipment, network equipment and medium. Background Technology

[0003] The Random Access Procedure (RAP) refers to the key steps in establishing and re-establishing a connection between a User Equipment (UE) and a base station. RAP mainly includes the following four steps:

[0004] S1: The UE sends the first message (msg1) to the base station. That is, the UE sends the Random Access Preamble to the base station to help the base station identify the UE.

[0005] S2: The base station sends a second message (msg 2) to the UE. The base station sends a Random Access Response (RAR) to the UE via msg 2, which is used for the UE's subsequent uplink transmission.

[0006] S3: The UE sends a third message (i.e., msg 3) to the base station. The UE sends a connection request to the base station through msg 3.

[0007] S4: The base station sends a fourth message (msg 4) to the UE. The base station uses msg 4 to send a contention resolution identifier back to the UE, and the UE determines whether the contention was successful based on the contention resolution identifier.

[0008] In recent years, to reduce connection establishment latency and improve data transmission efficiency, Mobile-Originating Early Data Transmission (MO-EDT) has been introduced. MO-EDT allows the UE to directly send its user data in msg 3 of the RAP (Random Access Preamble) without waiting for the complete connection establishment process, thus reducing connection establishment latency. However, before sending user data using msg 3, the base station and UE still need to transmit the Random Access Preamble (RAR) sequence. This increases uplink and downlink signaling overhead, affecting the utilization of uplink and downlink resources. Summary of the Invention

[0009] This application provides a communication method, apparatus, user equipment, network equipment, and medium that can directly send UE user data using msg3 messages without sending random access preamble and RAR, thus reducing uplink and downlink signaling overhead and improving the utilization of uplink and downlink resources.

[0010] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0011] In a first aspect, embodiments of this application provide a communication method, specifically, a UE receives configuration information. The configuration information is used to enable devices in a first cell to directly perform contention-based MO-EDT data transmission operations, wherein the devices in the first cell include user equipment. The UE sends a target request message based on the configuration information and its own triggering information. The target request message is either a message carrying the UE's user data, or a message multiplexed with user data, and the triggering information is used to determine whether the UE can perform contention-based MO-EDT data transmission operations.

[0012] For example, in a communication system including network equipment and a UE, the network equipment covers a first cell, and the UE is located in the first cell. The network equipment can send configuration information to the equipment in the first cell via System Information Block (SIB) or Narrowband System Information Block (SIB-NB) messages, specifically SIB2 or SIB2-NB messages, using a broadcast method. After receiving the configuration information via broadcast, the UE can send a msg3 message based on the configuration information and its own triggering information. Alternatively, the UE can also send the above configuration information to the equipment in the first cell via dedicated signaling. This process does not require sending msg1 and msg2, thus helping to reduce uplink and downlink signaling overhead during EDT, improving the utilization of uplink and downlink resources, and further enhancing uplink capacity.

[0013] The triggering information includes one or more of the following: whether the upper layer initiates a request to establish a Radio Resource Control (RRC) connection or an RRC connection recovery request; whether contention-based MO-EDT is supported; whether the received broadcast message carries target indication information and whether there is a pre-compensated timing advance; and whether the target indication information indicates whether the network device sending the broadcast message allows the execution of contention-based MO-EDT.

[0014] In one specific implementation, the broadcast message carries a first indication information and / or a second indication information, wherein the first indication information indicates that the network device allows the execution of user plane-based MO-EDT, and the second indication information indicates that the network device allows the execution of control plane-based MO-EDT.

[0015] Specifically, if the broadcast message carries first indication information and the user equipment supports contention-based user plane MO-EDT, a first target request message is sent based on the configuration information. The first target request message is a connection restoration request message multiplexed with user data. If the broadcast message carries second indication information and the user equipment supports contention-based control plane MO-EDT, a second target request message is sent based on the configuration information. The second target request message is a connection establishment request message carrying user data.

[0016] The configuration information includes: configuration information for sending target request messages, or configuration information for sending target request messages according to coverage level.

[0017] Furthermore, the configuration information for sending the target request message includes one or more of the following: resource information for sending the target request message, contention resolution window length, contention resolution timer, and number of transmissions of the target request message.

[0018] If the configuration information for sending target request messages is configured according to the coverage level, the configuration information for sending target request messages includes one or more of the following: resource information for sending target request messages, contention resolution window length, contention resolution timer, number of transmissions of target request messages, and number of repetitions of sending target request messages.

[0019] In another specific implementation, a contention resolution window or contention resolution timer is started, and a target response message is received within the contention resolution window or contention resolution timer. The target response message carries a contention resolution identifier, which is used to identify the device that successfully competed in the first cell. If the target response message is obtained and the contention resolution identifier is consistent with the user identifier used by the user equipment, it is determined that the competition was successful.

[0020] In one specific implementation, after the target request message is sent, and after N subframes of time plus the round-trip time between the user equipment and the network device, a contention resolution window or a contention resolution timer is started, where N is a positive integer. This allows the UE sufficient buffer time for the network device to process the target request message, thereby improving the accuracy and efficiency of obtaining the target response message.

[0021] In another specific implementation, the contention failure is determined based on the number of transmissions and contention failure conditions. The contention failure conditions include not obtaining the target response message, or obtaining the target response message but the contention resolution identifier is inconsistent with the user identifier used by the user equipment. If the number of transmissions is less than the number of transmissions for sending the target request message, and the contention failure conditions are met, the contention failure is determined. The target request message is resent, and the count of the number of transmissions of the target request message is incremented. The steps for determining whether the contention failure has occurred continue until a preset stopping condition is reached. The preset stopping condition is that the total number of transmissions is greater than or equal to the number of transmissions for sending the target request message, or the contention is determined to be successful.

[0022] In another specific implementation, if the configuration information also includes the number of transmissions of the target request message corresponding to the coverage level; obtain the number of transmissions of the target request message under the current coverage level; determine whether the contention has failed based on the number of transmissions under the current coverage level and the contention failure conditions; the contention failure conditions include not obtaining the target response message, or obtaining the target response message but the contention resolution identifier is inconsistent with the user identifier used by the user equipment; if the number of transmissions is less than or equal to the number of transmissions corresponding to the current coverage level and the contention failure conditions are met, determine that the contention has failed; resend the target request message, increment the transmission count counter, and continue to execute the steps to determine whether the contention has failed until a preset stop condition is reached, the preset stop condition being that the number of transmissions is greater than or equal to the number of transmissions of the target request message corresponding to the target coverage level, or that the contention has succeeded; if the number of transmissions is greater than or equal to the number of transmissions corresponding to the current coverage level, jump to the next coverage level, the next coverage level is higher than the current coverage level, and adjust the number of transmissions of the target request message under the adjusted coverage level to the initial value.

[0023] The configuration information also includes DSA configuration information, which includes: configuration information for configuring the transmission of target request message copies, or configuration information for configuring the transmission of target request message copies according to coverage level. This application embodiment performs contention-based MO-EDT according to coverage level. Different coverage levels correspond to different transmission parameters and resource configurations, thus better adapting to various coverage conditions and improving transmission reliability. Furthermore, allocating resources according to coverage level allows for more efficient use of radio resources, avoiding resource waste and improving resource utilization.

[0024] In another specific implementation, the configuration information for sending a copy of the target request message includes one or more of the following: resource information for sending the copy of the target request message, the number of copies, and the mapping relationship between the resources of the copy and the resources of the target request message; if the configuration information for sending the copy of the target request message is configured according to the coverage level, the configuration information for sending the copy of the target request message includes one or more of the following: resource information for the configuration information of the copy of the target request message, the number of copies, the number of duplicate copies, and the mapping relationship between the resources of the copy and the resources of the target request message.

[0025] In another specific implementation, based on DSA configuration information and the user equipment's support for contention-based MO-EDT with DSA, a copy of the target request message is sent, or a copy of the target request message is sent according to the coverage level. In this embodiment, the UE can further increase the probability of successful contention by sending a copy of the target request message after sending the target request message.

[0026] In another specific implementation, after sending a copy of the target request message, a contention resolution window or contention resolution timer is started after the last copy is sent. Alternatively, if the target request message copies are sent according to coverage level, a contention resolution window or contention resolution timer is started after the last duplicate of the last copy is sent. Within the contention resolution window or contention resolution timer, a target response message is received. If a target response message is obtained, and the contention resolution identifier carried in the target response information matches the user identifier sent by the user equipment, the contention is considered successful. This reduces the number of times windows or timers are started, thus improving processing efficiency.

[0027] In another specific implementation, the radio network identifier is calculated based on the time-frequency resources of the target request message, or based on the time-frequency resources of a copy of the target request message; using the calculated radio network identifier, downlink messages are monitored and the target response message is received.

[0028] In another specific implementation, after the last copy is sent, and after N subframes and the RTT between the user equipment and the network equipment, a contention resolution window or a contention resolution timer is started, where N is a positive integer; if the target request message copy is sent according to the coverage level, after the last duplicate of the last copy is sent, and after N subframes and the RTT between the user equipment and the network equipment, a contention resolution window or a contention resolution timer is started.

[0029] In another specific implementation, after the first copy is sent, a contention resolution window or contention resolution timer is started. If no target response message is received within the contention resolution window or contention resolution timer, or if a target response message is received but the contention resolution identifier in the target response message is inconsistent with the user identifier used by the user equipment, a second copy is sent. Alternatively, if the target request message copy is sent according to the coverage level, after the last duplicate of the first copy is sent, a contention resolution window or contention resolution timer is started. If no target response message is received within the contention resolution window or contention resolution timer, or if a target response message is received but the contention resolution identifier in the target response message is inconsistent with the user identifier used by the user equipment, a second copy is sent.

[0030] In another specific implementation, after the first copy is sent, a contention resolution window or a contention resolution timer is started, and the time domain and / or frequency domain resources for sending the second copy are selected. After the second copy is sent, a contention resolution window or a contention resolution timer is started, and the contention resolution window or timer corresponding to the first copy is stopped. If the target request message copy is sent according to the coverage level, after the last duplicate of the last copy is sent, a contention resolution window or a contention resolution timer is started, and the second copy is selected to be sent. After the second copy is sent, a contention resolution window or a contention resolution timer is started, and the contention resolution window or timer corresponding to the first copy is stopped.

[0031] It should be noted that this explanation only considers a scenario with two replicas, including the first and second replicas. This method can also be applied to scenarios with more than two replicas, such as three or more replicas.

[0032] In another specific implementation, the contention resolution identifier being consistent with the user identifier sent by the user equipment specifically includes: the contention resolution identifier being completely identical to the user identifier sent by the user equipment, or the contention resolution identifier being identical to the first X bits of the user identifier used by the user equipment, where X is an integer greater than 1.

[0033] Secondly, embodiments of this application provide a communication method applied to a network device, the network device covering a first cell, the method comprising:

[0034] The system sends configuration information to enable multiple devices in the first cell to directly perform contention-based MO-EDT data transmission operations; based on the configuration information and the triggering information of the user equipment, the user equipment in the first cell sends a target request message; multiple devices, including the user equipment, receive the target request message, which is a message carrying the user equipment's user data, or a message multiplexed with user data; the system parses the target request message to obtain the user data.

[0035] In another specific implementation, the triggering information of the user equipment includes one or more of the following: the upper layer initiates a request to establish a Radio Resource Control (RRC) connection, supports contention-based MO-EDT, and the received broadcast message carries target indication information and pre-compensated timing advance, with the target indication information instructing the network device to allow the execution of contention-based MO-EDT.

[0036] In another specific implementation, a broadcast message is sent; if the broadcast message carries first indication information, a first target request message is received, the first indication information instructs the network device to allow the execution of user plane-based MO-EDT, and the first target request message is a connection restoration request message multiplexed with user data.

[0037] If the broadcast information carries a second indication information, a second target request message is received. The second indication information instructs the network device to allow the execution of MO-EDT based on the control plane. The second target request message is a connection establishment request message carrying user data.

[0038] In another specific implementation, the configuration information includes: configuration information for the device in the first cell to send target request messages, or configuration information for the device in the first cell to send target request messages according to the coverage level.

[0039] In yet another specific implementation, the configuration information for sending the target request message includes one or more of the following:

[0040] Resource information for sending the target request message, contention resolution window length, contention resolution timer, and number of transmissions for sending the target request message.

[0041] If the configuration information for sending target request messages by the device in the first cell is configured according to the coverage level, the configuration information for sending target request messages includes one or more of the following:

[0042] Resource information for sending the target request message, contention resolution window length, contention resolution timer, number of transmissions of the target request message, and number of repetitions of the target request message.

[0043] In another specific implementation, after sending the target request message, a target response message is sent. The target response message carries a contention resolution identifier, which is used to identify the device that has successfully competed in the first cell. If the user equipment receives the target response message within the contention resolution window or the contention resolution timer, and the contention resolution identifier is consistent with the user identifier used by the user equipment, it is determined that the user equipment has successfully competed.

[0044] In another specific implementation, the configuration information also includes data sequence allocation (DSA) configuration information, which includes: configuration information for configuring the device in the first cell to send a copy of the target request message, or configuration information for configuring the device in the first cell to send a copy of the target request message according to the coverage level.

[0045] In another specific implementation, the configuration information for sending a copy of the target request message includes one or more of the following: resource information for the configuration information of the copy of the target request message, the number of copies, and the mapping relationship between the resources for sending the copies and the resources for sending the target request message.

[0046] If the configuration information for sending target request message replicas is configured according to the coverage level, the configuration information for sending target request message replicas includes one or more of the following: resource information for the configuration information of sending target request message replicas, number of replicas, number of replicas to be repeatedly sent, and mapping relationship between the resources for sending replicas and the resources for sending target request messages.

[0047] In another specific implementation, a copy of the target request message is received based on the DSA configuration information, or a copy of the target request message is received according to the coverage level.

[0048] In another specific implementation, the contention resolution identifier being consistent with the user identifier sent by the user equipment specifically includes: the contention resolution identifier being completely identical to the user identifier sent by the user equipment, or the contention resolution identifier being identical to the first X bits of the user identifier used by the user equipment, where X is an integer greater than 1.

[0049] Thirdly, embodiments of this application provide a communication device applied to a user equipment in a first cell. The communication device includes:

[0050] The first receiving unit is used to receive configuration information, which enables multiple devices in the first cell to directly perform contention-based mobile calling party advance data transmission (MO-EDT) data transmission operations, including user equipment.

[0051] The first sending unit is used to send a target request message according to the configuration information and the trigger information of the user equipment. The target request message is a message carrying user data of the user equipment, or the target request message is a message multiplexed with user data. The trigger information is used to determine whether the user equipment can perform the operation of contention-based MO-EDT data transmission.

[0052] Fourthly, embodiments of this application provide a communication device applied to a network device covering a first cell. The communication device includes:

[0053] The second sending unit is used to send configuration information, which enables multiple devices in the first cell to directly perform contention-based MO-EDT data transmission operations; based on the configuration information and the triggering information of the user equipment, it enables the user equipment in the first cell to send a target request message; the multiple devices include user equipment.

[0054] The second receiving unit is used to receive a target request message, which is a message carrying user data of the user equipment, or a message multiplexed with user data.

[0055] The parsing unit is used to parse the target request message and obtain user data.

[0056] Fifthly, embodiments of this application provide a user equipment, which includes a memory and a processor;

[0057] The memory is used to store the executable program;

[0058] The processor is used to execute programs stored in memory, performing communication methods such as those described in the first aspect.

[0059] Sixthly, embodiments of this application provide a network device, which includes a memory and a processor;

[0060] The memory is used to store the executable program;

[0061] The processor is used to execute programs stored in memory, and to perform communication methods such as those described in the second aspect.

[0062] In a seventh aspect, embodiments of this application provide a communication system, characterized in that it includes a network device and a user device; the network device performs a communication method as described in any of the second aspects, and the user device performs a communication method as described in any of the first aspects.

[0063] Eighthly, embodiments of this application provide a computer storage medium for storing a computer program, which, when executed, implements a communication method as described in either the first or second aspect. Attached Figure Description

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

[0065] Figure 2 is an interaction diagram of a random access procedure provided in an embodiment of this application;

[0066] Figure 3 is an interaction diagram of an implementation method of MO-EDT-CP provided in an embodiment of this application;

[0067] Figure 4 is an interaction diagram of another MO-EDT-CP implementation method provided in the embodiments of this application;

[0068] Figure 5 is an interaction diagram of an implementation method of MO-EDT-UP provided in an embodiment of this application;

[0069] Figure 6 is an interaction diagram of a communication method provided in an embodiment of this application;

[0070] Figure 7 is an interaction diagram of the competition-based MO-EDT-UP implementation method provided in the embodiments of this application;

[0071] Figure 8A is a flowchart of a method for performing a competition-based MO-EDT according to an embodiment of this application;

[0072] Figure 8B is a flowchart of a method for performing a competition-based MO-EDT according to an embodiment of this application;

[0073] Figure 9A is a flowchart of another method for performing competition-based MO-EDT provided in an embodiment of this application;

[0074] Figure 9B is a schematic diagram of a competition resolution window provided in an embodiment of this application;

[0075] Figure 10A is an interaction diagram of another competition-based MO-EDT implementation method provided in the embodiments of this application;

[0076] Figure 10B is a schematic diagram of a competition resolution window provided in an embodiment of this application;

[0077] Figure 11A is an interaction diagram of another competition-based MO-EDT implementation method provided in the embodiments of this application;

[0078] Figure 11B is a schematic diagram of another way to start a contention resolution window according to an embodiment of this application;

[0079] Figure 12A is an interaction diagram of another implementation method based on MO-EDT provided in the embodiments of this application;

[0080] Figure 12B is a schematic diagram of a race condition resolution window provided in an embodiment of this application;

[0081] Figure 13A is a schematic diagram of a coverage level provided in an embodiment of this application;

[0082] Figure 13B is a flowchart of another method for performing competition-based MO-EDT provided in an embodiment of this application;

[0083] Figure 14 is a flowchart of another method for performing competition-based MO-EDT provided in an embodiment of this application;

[0084] Figure 15 is an interaction diagram of another competition-based MO-EDT implementation method provided in the embodiments of this application;

[0085] Figure 16 is a schematic diagram of the hardware structure of a network device provided by the present application.

[0086] Figure 17 is a component example diagram of the UE provided in the embodiments of this application. Detailed Implementation

[0087] This application provides a communication system, which can be a fifth-generation (5G) communication system, a 5G New Radio (5G NR) system, or other new communication systems that will emerge in the future development of communication. The communication system includes multiple devices, and these devices can exchange signals to achieve data interaction.

[0088] An example of a communication system is shown in Figure 1, which includes a core network, network devices, and n UEs, UE1 to UEn. As shown in Figure 1, n is an integer greater than 1. The core network is responsible for processing data requests and providing functions such as user connection, user management, and service carrying.

[0089] In this application embodiment, the network device can be any device located on the network side and having wireless transceiver capabilities, including but not limited to: satellites or aircraft in Non-Terrestrial Networks (NTN) or Internet of Things-Non-Terrestrial Networks (IoT-NTN), or other possible satellite network devices, base stations (gNodeB or gNB) or Transmission Receiving Points / Transmission Reception Points (TRPs) in New Radio (NR), etc., which are not specifically limited in this application embodiment. The network device can communicate with user equipment or communicate with user equipment through relay stations. User equipment can communicate with multiple base stations of different technologies. For example, user equipment can communicate with base stations supporting LTE networks, base stations supporting 5G networks, and can also establish dual connections with base stations supporting both LTE and 5G networks.

[0090] In a communication system, a User Equipment (UE), such as UE1, can take various forms. For example, a UE can be a mobile phone, tablet, computer with wireless transceiver capabilities, virtual reality (VR) user equipment, augmented reality (AR) user equipment, a wireless terminal in industrial control, vehicle-mounted user equipment, a wireless terminal in self-driving vehicles, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, wearable user equipment, and so on. A UE can also be referred to as user equipment, access user equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote user equipment, mobile device, UE user equipment, user equipment, wireless communication equipment, UE agent, or UE device, etc. A UE can also be a fixed terminal or a mobile terminal.

[0091] The core network may include one or more network elements, such as access and mobility management function (AMF) network elements, user plane function (UPF) network elements, or session management function (SMF) network elements. Examples include mobility management entity (MME) network elements and serving gateway (S-GW) network elements. This application embodiment is not specifically limited. In this application embodiment, the core network receives target request messages initiated by the UE through network devices, processes the target request messages, and ensures that the UE successfully accesses the network and maintains the connection.

[0092] The above description uses a communication system including terminal devices and network devices as an example. In other possible implementations, the communication system may include multiple terminal devices or multiple network devices. Alternatively, in other possible implementations, the network devices in the communication system may be replaced with other types of network elements, and this is not limited. For ease of understanding, the following description will still use the interaction between terminal devices and network devices as an example.

[0093] In practical applications, the key steps for establishing and restoring the initial connection between the UE and the network device are called RAP (Random Access Procedure). Figure 2 is an interaction diagram of a random access procedure provided in an embodiment of this application. Specifically, it includes the following four steps:

[0094] S21. The UE sends a random access preamble to the network device.

[0095] The UE sends a random access preamble sequence to the network device via msg1.

[0096] In one specific implementation, the network device sends System Information Block (SIB) messages via the Broadcast Channel (BCH) or the Physical Downlink Control Channel (PDCCH). The SIB message carries preamble sequence configuration resources. The UE randomly selects a preamble sequence (i.e., a random access preamble sequence), configures the preamble sequence resources, and sends the random access preamble sequence to the network device via the uplink Random Access Channel (RACH) to request network access.

[0097] S22. The network device returns a Random Access Response (RAR) to the UE.

[0098] In this process, the network device sends the RAR to the UE via msg2.

[0099] In one specific implementation, after receiving the random access preamble sequence, the network device obtains the Random Access Radio Network Temporary Identifier (RA-RNTI) based on the time-frequency resource location of the preamble sequence sent by the UE. The RA-RNTI is used to uniquely identify the UE in the RAR.

[0100] Since multiple UEs choose the same time-frequency resources to send the preamble sequence, a competition is required to determine which UE successfully wins the competition and accesses the network. As shown in Figure 1, if UE1, UE2, and UE3 choose the same time-frequency resources to send the preamble sequence, it is necessary to determine which UE successfully wins the competition and accesses the network.

[0101] Within the random access response window, the network device sends the RAR to the UE via the Physical Downlink Shared Channel (PDSCH) or the Narrowband Physical Downlink Shared Channel (NPDSCH). The UE needs to decode the scheduling resources of the PDSCH or NPDSCH using RA-RNTI within the random access response window, and then decode the channel content of the PDSCH or NPDSCH to obtain the RAR.

[0102] The random access window is activated after the UE sends the preamble sequence, following a period of 4 or 41 subframes, plus the round-trip time between the UE and the network device. The window size is configured by the network device. This activation method helps ensure that the network device has sufficient time to process the preamble sequence, improving the success rate of the UE receiving the RAR.

[0103] RAR includes a preamble sequence, backoff parameters, uplink grant (UL-grant) for scheduling msg3, temporary cell-radio network temporary identifier (TC-RNTI), and timing advance (TA).

[0104] The fallback parameter is used to prevent multiple UEs from attempting random access multiple times at the same time, which helps reduce conflicts.

[0105] UL-grant is the uplink resource allocated by the network device to the UE for sending msg3.

[0106] TC-RNTI is a temporary identifier assigned by the network device in the RAP, used to uniquely identify the UE in the RAP so that the UE can identify itself in subsequent communications.

[0107] TA is used to compensate for propagation delay between the UE and network devices, ensuring that the UE's uplink signal is correctly aligned at the network device. TA values ​​are typically expressed in units of time.

[0108] The UE determines whether the RAR corresponds to the random access preamble sequence it sent based on the preamble sequence in the RAR. However, since there may be scenarios where multiple UEs choose the same time-frequency resources to send preamble sequences to the network device, although the network device can identify these preamble sequences, the identical preamble sequences may lead to the RAR content generated by the network device being the same or similar. As a result, the UE cannot determine whether the RAR was sent to it individually based on the content of the RAR.

[0109] S23. The UE sends a Schedule Transmission message to the network device.

[0110] After receiving the RAR, the UE uses the UL-grant provided by the RAR to send msg3. The UE then sends a connection request to the network device via msg3.

[0111] msg3 includes a Radio Resource Control (RRC) Connection Request (also known as an RRC Connection Request).

[0112] It should be noted that if the UE is a Narrowband Internet of Things (NBIOT) terminal, the RRC message will carry the suffix -NB in ​​the command, for example, the RRC connection request is RRC Connection Request-NB.

[0113] If the UE is another user equipment, the RRC message command will not have the suffix "-NB". For ease of explanation, subsequent RRC messages will not have the suffix, but they actually refer to the RRC messages corresponding to the NB-IoT terminal, as well as the RRC messages corresponding to other terminals.

[0114] Furthermore, the msg3 message supports Hybrid Automatic Repeat Request (HARQ) retransmission, with retransmission resources scheduled via Downlink Control Information (DCI). The msg3 message carries a Short Temporary Mobile Subscriber Identity (S-TMSI) to uniquely identify the UE in the RAP. The msg3 message also carries the establishment reason, such as emergency call or high-priority access. Network devices can process access requests based on the establishment reason, ensuring timely processing of critical services.

[0115] S24. The network device sends a contention resolution message to the UE.

[0116] In this process, network devices and UEs use msg4 messages to carry RRC Early Data Complete (RRC) information to complete the contention resolution process.

[0117] Specifically, the msg4 message carries a contention resolution identifier. In one example, the network device uses a TC-RNTI-scrambled PDCCH to send downlink control information, including scheduling information and resource allocation information, to the UE in msg4, ensuring that only a designated UE can decode and receive msg4. The PDSCH is used to transmit user data and control information in msg4, including the MAC PDU in msg4. The MAC PDU on the PDSCH carries a contention resolution identifier to help the UE determine whether it has successfully acquired resources. The UE decodes the TC-RNTI-scrambled PDCCH to obtain the resource allocation information. Based on the resource allocation information of the PDCCH, the UE receives the PDSCH in the specified time slot and frequency band, and obtains the contention resolution identifier carried in the MAC PDU in the PDSCH channel.

[0118] The UE compares the contention resolution identifier with the user identifier it is using. If they match, the contention is successful and the UE successfully accesses the network. If they do not match, the contention has failed. The contention resolution identifier is carried in the Media Access Control Protocol Data Unit (MAC PDU) within the msg4 message.

[0119] The user identifier used by the UE is S-TMSI.

[0120] The contention resolution identifier being identical to the user identifier means that the contention resolution identifier is exactly the same as the S-TMSI, or that the first X of the contention resolution identifier is the same as the S-TMSI, where X is an integer greater than 1, for example, X = 48.

[0121] Therefore, through the above four steps, an RRC connection has been successfully established between the UE and the network device, and the UE enters the RRC connection state, where data transmission can be performed.

[0122] In recent years, MO-EDT has been introduced to reduce connection establishment latency and improve data transmission efficiency. MO-EDT allows the UE to directly send part of its user data in msg3 of RAP without waiting for the complete connection establishment process, thus reducing connection establishment latency.

[0123] The user data includes, but is not limited to, the following: UE sensor data, such as environmental monitoring data like temperature, humidity, and light intensity; UE status reports, such as battery level or device status; short messages, such as short text messages; alarm information, such as smoke alarms and intrusion alarms; control commands, such as system restart commands and parameter configuration commands; and location information, such as the UE's indoor location and latitude and longitude coordinates. For ease of description, the user data sent by msg3 will be referred to as "user data" in the following text.

[0124] MO-EDT includes two implementation schemes: MO-EDT based on the control plane (CP) (MO-EDT-CP for short) and MO-EDT based on the user plane (UP) (MO-EDT-UP for short).

[0125] MO-EDT-CP refers to the UE encapsulating user data in a Non-Access Stratum Protocol Data Unit (NAS PDU) and sending it to the network device by obtaining an RRC advance data request message with the encapsulated NAS PDU.

[0126] MO-EDT-UP refers to the UE placing user data on a dedicated traffic channel (DTCH), multiplexing it with an RRC connection recovery request message, and sending it to the network equipment. The DTCH is primarily used for transmitting user plane data, such as voice, video, and file transfers.

[0127] The two implementation schemes will be described in detail below with reference to Figures 3 to 5.

[0128] For example, Figure 3 is an interactive diagram of an MO-EDT-CP implementation method. In the MO-EDT-CP implementation method shown in Figure 3, the UE accesses the 4G core network. The network elements of the 4G core network include the MME and S-GW. The method specifically includes the following steps:

[0129] S31. The UE sends a random access preamble sequence to the network device.

[0130] S32, The network device returns a RAR to the UE.

[0131] S33, the UE sends a msg3 message to the network device.

[0132] The msg3 message is an RRC connection establishment request (RRC Early Data Request) message. This message includes the S-TMSI, the reason for establishment, and Non-Access Stratum (NAS) information.

[0133] Subsequently, the network device initiates the S1-AP process, which includes initial connection establishment, connection reconfiguration, and connection release, as shown in S34 to S310.

[0134] S34. The network device sends an Initial UE Message to the MME.

[0135] The initial UE message is a NAS message. This message carries an encapsulated NAS PDU. An encapsulated NAS PDU is a NAS PDU containing the S-TMSI, establishment reason, and dedicated NAS information. The network device transmits the encapsulated NAS PDU to the MME to establish an RRC connection.

[0136] S35 and MME send a bearer modification request to S-GW.

[0137] A bearer modification request, also known as a "Modify Bearer" request, is used to instruct the S-GW to modify the bearer to meet the requirements of MO-EDT. The bearer modification request carries the parameters required to modify the bearer.

[0138] S36, MME sends uplink data messages to S-GW.

[0139] Uplink data messages are also known as “Uplink data” messages.

[0140] The MME sends an uplink data message to the S-GW to inform the S-GW that it is ready to receive uplink data from the UE. In one example, the uplink data message carries the UE identifier and the uplink data.

[0141] Optionally, the S37 and S-GW send downlink data messages to the MME.

[0142] If the network device needs to send downlink data to the UE, the S-GW sends a downlink data message to the MME.

[0143] S38, the MME sends a NAS message carrying downlink data to the network device or an instruction message instructing the network device to establish an RRC connection with the UE.

[0144] S39. The network device sends a msg4 message to the UE.

[0145] It should be noted that if the network device puts the UE into connected state, the msg4 message carries Radio Resource Control (RRC) Connection Setup information, which is used to establish a connection between the UE and the network device. If the network device wants the UE to complete the MO-EDT procedure, the msg4 message carries an RRC advance data completion response to complete the MO-EDT procedure.

[0146] S310, Network device releases connection with MME.

[0147] Specifically, the following release process is executed:

[0148] Step 1: When the network device detects that the S1-AP connection with the MME needs to be released, the network device generates a connection release request. This connection release request carries information related to releasing the S1-AP connection.

[0149] Step 2: The network device sends a connection release request to the MME through the S1 interface.

[0150] Step 3: After receiving the connection release request, the MME processes the request and releases the connection with the network device.

[0151] As a result, the network device releases its connection to the MME.

[0152] S311, MME release and S-GW bearing.

[0153] Specifically, when the MME needs to release a bearer, the MME generates a bearer modification request. The MME sends the bearer modification request to the S-GW. After receiving the bearer modification request, the S-GW performs the operation of releasing the specified bearer.

[0154] For example, Figure 4 is an interactive diagram of another MO-EDT-CP implementation method. In the MO-EDT-CP implementation method shown in Figure 4, the UE accesses the 5G core network. The network elements of the 5G core network include AMF and SMF or UPF. The method specifically includes the following steps:

[0155] S41. The UE sends a random access preamble sequence to the network device.

[0156] S42. The network device returns a RAR to the UE.

[0157] S43, the UE sends a msg3 message to the network device.

[0158] The msg3 message is an RRC connection establishment request message. This message includes the S-TMSI, the reason for establishment, and Non-Access Stratum (NAS) information.

[0159] Subsequently, the network device initiates the NG-AP process, which includes initial connection establishment, connection reconfiguration, and connection release, as shown in S44 to S410.

[0160] S44. The network device sends the initial UE message to the AMF.

[0161] The initial UE message includes a PDU session ID and data. The PDU session ID is used to identify the PDU session requested by the UE.

[0162] S45, AMF parses the PDU session identifier from the initial UE message.

[0163] AMF identifies the specific PDU session by parsing the PDU session identifier.

[0164] S46, AMF sends PDU sessions and data to SMF / UPF.

[0165] Optionally, S47 and SMF / UPF send PDU sessions and data to AMF.

[0166] The SMF / UPF sends PDU sessions and data to the AMF to confirm that the PDU sessions and data have been successfully processed.

[0167] S48, the MME sends a NAS message carrying downlink data to the network device or an instruction message instructing the network device to establish an RRC connection with the UE.

[0168] S49. The network device sends a msg4 message to the UE.

[0169] It should be noted that if the network device puts the UE into connected state, the msg4 message carries Radio Resource Control (RRC) Connection Setup information, which is used to establish a connection between the UE and the network device. If the network device wants the UE to complete the MO-EDT procedure, the msg4 message carries an RRC advance data completion response to complete the MO-EDT procedure.

[0170] S410, Network device releases connection with AMF.

[0171] Specifically, the following release process is executed:

[0172] Step 1: When the network device detects that the NG-AP connection with the AMF needs to be released, the network device generates a connection release request. This connection release request carries information related to releasing the NG-AP connection.

[0173] Step 2: The network device sends a connection release request to the AMF.

[0174] Step 3: After receiving the connection release request, AMF processes the request and releases the connection with the network device.

[0175] As a result, the network device releases its connection to the AMF.

[0176] S411, AMF releases the connection with SMF / UPF.

[0177] The AMF releases its connection to the SMF / UPF, and the specific steps are as follows:

[0178] Step 11: AMF generates a connection release request, carrying information related to releasing the connection with SMF / UPF.

[0179] Step 12: The AMF sends a connection release request to the SMF / UPF.

[0180] Step 13: After receiving the connection release request, the SMF / UPF processes the request and releases the connection with the AMF.

[0181] It should be noted that S410 and S411 can be executed simultaneously, or S410 can be executed first and then S411, or S411 can be executed first and then S410. This application embodiment does not specifically limit the execution of these two methods.

[0182] For example, Figure 5 is an interaction diagram of an MO-EDT-UP implementation method. This method is an implementation method for UE access to the 4G core network. The method includes the following steps:

[0183] S51, the UE sends a random access preamble sequence to the base station.

[0184] S52, The base station returns RAR to the UE.

[0185] S53, the UE sends an RRC Connection Resume Request message to the base station.

[0186] The RRC connection establishment request carries user data. In addition, the RRC connection establishment request also carries:

[0187] The recovery process includes a resume identifier (resumeID), a resume reason (resumeCause), and a short resume message authentication code integrity check (shortResumeMAC-I). The resume identifier is a unique identifier used to identify the UE in the RRC idle state. When the UE reactivates the connection from the RRC idle state, it uses the resumeID to request connection restoration. The resume reason indicates the specific reason why the UE requests connection restoration. The short resume message authentication code integrity check is a short message authentication code value used to verify the integrity of the RRC resume request, ensuring that the resume request has not been tampered with during transmission.

[0188] Subsequently, the network device initiates the S1-AP process, which includes initial connection establishment, connection reconfiguration, and connection release, as shown in S54 to S510.

[0189] S54. The network device sends an RRC connection restoration request message to the MME.

[0190] The UE connection restoration request message, also known as the UE Context Resume request message, is used to request the restoration of the S1-AP connection. The UE connection restoration request carries a restoration identifier, a restoration reason, and a short restoration message authentication code integrity check, etc.

[0191] Bearer modifications between S55, MME, and S-GW.

[0192] Specifically, the MME sends a bearer modification request to the S-GW, the S-GW modifies the bearer, and sends a bearer modification response to the MME. The MME can determine whether the bearer modification is complete based on the bearer modification response.

[0193] S56, MME sends a recovery request response to the network device.

[0194] The MME acknowledges the UE's request to restore the connection and sends a response to the network device, indicating the status of the restored connection.

[0195] S57, Network devices send user data to S-GW.

[0196] Optionally, the S58 and S-GW send downlink data to network devices.

[0197] S59. The network device sends a msg4 message to the UE.

[0198] If there is no data to transmit, the network device will initiate an S1 connection suspension and send a release RRC connection request message to the UE, so that the UE is released to the idle state.

[0199] In addition, the Release RRC Connection Request message carries the release reason, recovery identifier, and parameters for key updates, such as the Next Hop Chaining Count. The UE obtains and saves the release reason, recovery identifier, and parameters for key updates.

[0200] S510, Network Equipment Suspension and MME Procedures.

[0201] The network device generates a pause request, requesting to pause the process with the MME. The network device sends the pause request to the MME, and the MME pauses the process with the network device.

[0202] S511, MME release and S-GW bearing.

[0203] It should be noted that the implementation steps of S59, S510 and S511 are not limited in this application embodiment. For example, S59, S510 and S511 can be executed in sequence, or S510, S511 and S59 can be executed in sequence, or S511, S510 and S59 can be executed in sequence, or S59, S511 and S510 can be executed simultaneously.

[0204] MO-EDT sends UE data via the msg3 message of RAP. However, before sending data using msg3, the network device and the UE need to transmit the random access preamble sequence and RAR, which increases uplink and downlink signaling overhead and affects the utilization of uplink and downlink resources.

[0205] In view of this, embodiments of this application provide a communication method that, by configuring shared resources, directly utilizes the target request message in the random access process to complete the transmission of user data. This eliminates the need for the base station and UE to transmit the random access preamble sequence and RAR, reducing uplink and downlink signaling overhead during MO-EDT, improving uplink and downlink capacity, and thus helping to improve the utilization rate of uplink and downlink resources.

[0206] To better illustrate the communication method provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings. It should be noted that the msg3 message, RRC connection recovery request message, and RRC connection establishment request message provided in the embodiments of this application are all illustrative. In actual use, the msg3 message can be adjusted to msgX as needed, and the RRC connection recovery request message and RRC connection request message can also be other RRC messages.

[0207] Example 1

[0208] Figure 6 is an interaction diagram of a communication method provided in an embodiment of this application. The method includes the following:

[0209] S610, network devices send configuration information.

[0210] The configuration information is used to enable devices in the first cell to directly perform contention-based MO-EDT data transmission. For example, the configuration information includes resource information and the number of transmissions required for contention-based MO-EDT transmission.

[0211] In this context, the first cell is the cell covered by the network device. For example, as shown in Figure 1, the first cell is a cell, and the devices in the first cell are UE1 to UEn. The configuration information sent by the network device is used to enable UE1 to UEn to directly perform contention-based MO-EDT data transmission operations.

[0212] In one specific implementation, network devices can send configuration information via System Information Block (SIB) messages using a broadcast method. For example, a network device can send configuration information via an SIB2 message.

[0213] S620: Based on its own triggering information, the UE determines whether it can execute a contention-based MO-EDT. If yes, proceed to S630; otherwise, proceed to S640.

[0214] Triggering information is used to determine whether the UE can perform contention-based MO-EDT data transmission. In this embodiment, triggering information includes, but is not limited to, the following: whether the upper layer initiates a request to establish an RRC connection or an RRC connection recovery request; whether the UE supports contention-based MO-EDT; whether there is a pre-compensation timing advance (Pre-TA); and whether the broadcast message received by the UE carries target indication information.

[0215] Before initiating a contention-based MO-EDT, the UE checks whether its Upper layer has already initiated a request to establish an RRC connection. If the Upper layer has initiated such a request, data transmission is only performed after the RRC connection is established. This avoids unnecessary waste of resources by repeatedly using MO-EDT when an RRC connection request has already been initiated.

[0216] Not all UEs support contention-based MO-EDT. Therefore, it is necessary to determine whether the UE supports contention-based MO-EDT before initiating it. Initiating MO-EDT only when the UE supports it helps reduce unnecessary signaling overhead and increases the probability of successful transmission.

[0217] Pre-TA refers to the UE adjusting its transmission time in advance before sending data to compensate for signal propagation delay. During random access, when transmitting user data via msg3, Pre-TA can help the UE avoid time deviations when sending MSG3.

[0218] The target indication information indicates whether the network device allows contention-based MO-EDT. The UE can determine whether to perform contention-based MO-EDT based on the target indication information. For example, the target indication information can be a Boolean value (True or False). If the target indication information is True, the UE determines that the network device allows contention-based MO-EDT; if the target indication information is False, the UE determines that the network device does not allow contention-based MO-EDT. Therefore, by using the target indication information to determine whether to initiate contention-based MO-EDT, the UE further helps to improve the probability of successful transmission.

[0219] In this embodiment, the UE obtains target indication information through broadcast messages. Broadcast messages are messages sent by the network device to all UEs within the covered cell. Broadcast messages provide network configuration information, system parameters, etc., to help the UE correctly access and use the network. In this embodiment, the broadcast message carries target indication information. Sending configuration information via broadcast helps improve the speed of obtaining target indication information.

[0220] In one example, if the UE determines that the Upper layer has not initiated a request to establish an RRC connection, supports contention-based MO-EDT, and the received broadcast message carries target indication information indicating that contention-based MO-EDT is permitted, and a Pre-TA exists, then the UE is determined to be able to execute contention-based MO-EDT. Otherwise, the UE is determined not to be able to execute contention-based MO-EDT, and the initiation of contention-based MO-EDT is stopped.

[0221] Furthermore, MO-EDT includes two schemes: MO-EDT-CP and MO-EDT-UP. The UE can also determine whether to execute MO-EDT-CP, MO-EDT-UP, or neither based on its own triggering information.

[0222] The triggering information also includes whether the UE supports contention-based MO-EDT-UP and contention-based MO-EDT-CP. The broadcast message received by the UE carries target indication information, which is further subdivided into indicating whether the network device allows the execution of contention-based MO-EDT-UP and indicating whether the network device allows the execution of contention-based MO-EDT-CP. For ease of description, the indication that the network device allows the execution of contention-based MO-EDT-UP is referred to as the first indication message, and the indication that the network device allows the execution of contention-based MO-EDT-CP is referred to as the second indication message.

[0223] If the UE supports MO-EDT-UP and the broadcast information received by the UE carries a first indication message, a contention-based MO-EDT-UP is initiated. If the UE supports MO-EDT-CP and the broadcast information received by the UE carries a second indication message, a contention-based MO-EDT-CP is initiated.

[0224] Based on the configuration information, the S630 and UE send a target request message to the network device.

[0225] The target request message is initiated by the UE to establish a network connection with the network device. The target request message includes information such as the UE's random access identifier and access parameters. Upon receiving the target request message, the network device establishes a network connection with the base station based on the random access identifier and access parameters.

[0226] In this embodiment, the target request message can be the msg3 message in the RAP. Furthermore, the target request message is a message carrying UE user data, or a message multiplexed with user data.

[0227] For example, if a UE initiates a contention-based MO-EDT-UP procedure, the target request message is a first target request message, which is a connection restoration request message multiplexed with user data. For instance, the UE places user data in the DTCH, multiplexes it with the RRC connection restoration request message, and sends it to the network device. Further, if the core network is a 4G core network, the procedures shown in Figure 5 (S54-S510) can be executed. If the core network is a 5G core network, the procedure shown in Figure 7 can be executed.

[0228] Figure 7 is an interaction diagram of the contention-based MO-EDT-UP implementation method provided in this application embodiment. The core network of this method is a 5G core network. After the UE multiplexes the user data and the RRC connection restoration request message together and sends them to the network device, the method continues to execute the following steps:

[0229] S711, The network device sends a UE connection restoration request message to the AMF.

[0230] The UE Reconnection Request message is used to restore the UE's connection with network devices. The UE Reconnection Request message includes a PDU session ID and data. The PDU session ID identifies the PDU session requested by the UE.

[0231] S712, AMF identifies the PDU session identifier from the UE connection recovery request message.

[0232] PDU sessions and data changes between S713, AMF, and SMF / UPF.

[0233] S714 and AMF send a recovery request response to the network device.

[0234] S715, network devices send user data to SMF / UPF.

[0235] Optionally, the S716 and SMF / UPF send downlink data to the network device.

[0236] S717, The network device sends a msg4 message to the UE.

[0237] S718, Network Device Release and Subsequent Procedures for AMF and SMF / UPF.

[0238] If the UE initiates a contention-based MO-EDT-CP procedure, the target request message is a second target request message, which is a connection establishment request carrying user data. For example, the UE encapsulates the user data in a NAS PDU and sends it to the network device via an RRC connection establishment request message. Further, if the core network is a 4G core network, steps S34 to S310 as shown in Figure 3 can be executed. If the core network is a 5G core network, steps S44 to S410 as shown in Figure 4 can be executed.

[0239] S640 and UE send user equipment data based on a preset procedure.

[0240] For example, the preset process can be a traditional MO-EDT process or a random access process. In addition, the preset process can also be other preset processes. This application embodiment does not specifically limit the process.

[0241] In summary, in a communication system including network equipment and a UE, the network equipment covers the first cell, and the UE is located in the first cell. After receiving the configuration information via broadcast, the UE sends a msg3 message based on its own triggering information. This process, by configuring shared resources, can directly utilize the target request message to send user data. This process does not require sending msg1 and msg2, thus helping to reduce uplink and downlink signaling overhead during EDT, improving the utilization of uplink and downlink resources, and thereby enhancing uplink capacity.

[0242] Example 2

[0243] This application embodiment can determine whether the UE has successfully established a connection with the network device by starting a contention resolution window or starting a contention resolution timer and obtaining target response information within the contention resolution window or contention resolution timer.

[0244] The configuration information provided in this application embodiment is the configuration information for configuring target request messages. This configuration information includes resource information for sending target request messages, contention resolution window length (or contention resolution timer), and the number of transmissions required to send target request messages.

[0245] The resource information for sending the target request message is used to ensure that the UE sends the target request message within a defined time period using defined transmission resources, without conflicting with transmissions from other UEs in the first cell. The resource information for sending the target request message includes frequency bands, subcarriers, and time slots.

[0246] The contention resolution window is a time window configured by the network device for the UE, and its length is the contention resolution window length. Within the contention resolution window, the UE can monitor the response messages of the target request message to determine whether the UE has successfully won the contention. The contention resolution window length can be in the form of n PDCCH cycles or a time unit, such as s or ms. For example, the contention resolution window length is 10ms. n ≥ 1, and n is an integer.

[0247] The contention resolution timer is a timer configured by the network device for the UE, causing the UE to wait for the network device to send a contention resolution message after sending a target request message. For example, if the UE starts the contention resolution timer after sending Msg3, and does not receive Msg4 within 20ms of waiting for the contention resolution timer, it considers the contention resolution to have failed, and the UE needs to retry the random access procedure.

[0248] The number of times a target request message is transmitted refers to the maximum number of times a UE attempts to send a target request message in a single RAP.

[0249] In this embodiment of the application, the UE sends msg3 to the network device based on the resource information for sending the target request message.

[0250] Simultaneously, the UE initiates a contention resolution window and receives the target response message within the contention resolution window. In this embodiment, the network device can set a reasonable contention resolution window for the UE based on empirical values ​​or other methods to avoid the contention resolution window being too short, which could lead to failure to receive the response in a timely manner or waste of resources during the contention resolution window process.

[0251] Furthermore, after msg3 is sent, the UE can initiate a contention resolution window after N subframes and the round-trip time between the UE and the network device. Here, N ≥ 1, and N is an integer. For example, N = 4 or N = 41. This allows the UE sufficient buffer time for the network device to process the msg3 message, thereby improving the accuracy and efficiency of obtaining the target response message.

[0252] It should be noted that since the contention resolution window and the contention resolution timer are implemented in the same way and on the same principle, and serve the same function, this application will use the contention resolution window as an example for ease of explanation. In actual use, all contention resolution windows can be equivalently replaced by the contention resolution timer.

[0253] A target response message is a response message sent by a network device to another network device after receiving a target request message. In RAP, the target response message is msg4. The target response message is used to notify the UE that the target request message has been received and processed. In this embodiment, the target response message carries a contention resolution identifier.

[0254] The contention resolution identifier is used to identify the device that successfully competed for contention in the first cell. For the msg4 message, the contention resolution identifier is carried in the MAC PDU of the msg4 message. If the contention resolution identifier matches the user identifier used by the UE (e.g., S-TMSI), the UE is determined to have successfully competed for contention; otherwise, the UE is identified as having failed to compete for contention.

[0255] The contention resolution identifier is consistent with the identifier used by the UE, including: the contention resolution identifier is exactly the same as the identifier used by the UE, or the first X preset bits of the contention resolution identifier are the same as the contention resolution identifier used by the UE. X > 1, and X is an integer, for example, X is 48.

[0256] Furthermore, for step S630, this application embodiment provides another implementation method.

[0257] Figure 8A is a flowchart illustrating a method for performing a contention-based MO-EDT according to an embodiment of this application. The executor of this method is the UE. The method specifically includes:

[0258] S830-1, UE sends msg3 message.

[0259] S830-2, UE starts contention resolution window.

[0260] S830-3, The UE calculates the radio network identifier based on the time-frequency resources based on the sent msg3 message.

[0261] In this embodiment, after the UE sends the msg3 message, it can calculate the radio network identifier based on the time-frequency resources used to send the msg3 message. This radio network identifier is used for scheduling information of the scrambling target response message. For example, after the UE sends the msg3 message, it calculates the RA-RNTI based on the time-frequency resources of the msg3 message.

[0262] It should be noted that S830-2 and S830-3 can be executed simultaneously, or S830-2 can be executed first and then S830-3, or S830-3 can be executed first and then S830-2. This application embodiment does not specifically limit the execution of these two methods.

[0263] S830-4: The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0264] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0265] S830-5: The UE determines whether the contention failed. If yes, proceed to S830-6. If no, proceed to S830-7.

[0266] The UE determines whether the competition failure condition is met. If it is met, the competition is determined to have failed; otherwise, the competition is determined to have succeeded.

[0267] The contention failure condition is that no target response message is received within the contention resolution window, or the target response message is received but the contention resolution identifier carried by the target effect message is inconsistent with the user identifier used by the UE.

[0268] S830-6: The UE determines whether the number of transmissions is less than the configured number of transmissions for sending the target request message. If yes, execute S830-1; otherwise, execute S640.

[0269] Increment the transmission count of mg3 and retrieve the transmission count of msg3. Note that the transmission count of msg3 has an initial value, for example, 0. Sending a msg3 message increments the transmission count by one.

[0270] S830-7, Stop executing the MO-EDT process.

[0271] To better illustrate the embodiments of this application, the target message is defined as the msg3 message, but it can also be msgX or a specific message name; the naming of the message has no actual referential meaning. For example, as shown in Figure 8B, which is a schematic diagram of starting a contention resolution window according to an embodiment of this application, the first sent msg3 message is called msg3-1, the second sent msg3 message is called msg3-2, and the third sent msg3 message is called msg3-3. The contention resolution window corresponding to the msg3-1 message is window 1, the contention resolution window corresponding to the msg3-2 message is window 2, and the contention resolution window corresponding to the msg3-3 message is window 3.

[0272] After the UE sends the msg3-1 message, it starts window 1 to receive the target response message. If the contention fails, it sends the msg3-2 message, starts window 2 to receive the target response message, and stops sending if the contention succeeds. If the contention fails, it sends the msg3-3 message and starts window 3 to receive the target response message.

[0273] In this embodiment of the application, the UE can increase the probability of successful contention by repeatedly sending the target request message.

[0274] Example 3

[0275] In this embodiment, the target request message sent is a target request message based on Diversity Slotted ALOHA (DSA). DSA is a technique used to enhance the reliability and performance of wireless communication systems. It improves the robustness and anti-interference capability of data transmission by sending duplicate data in different time slots.

[0276] In this embodiment of the application, the configuration information includes resource information for sending target request messages, DSA configuration information, contention resolution window length, and the number of transmissions for sending target request messages.

[0277] The DSA configuration information includes, but is not limited to, the following: resource information for sending a replica of the target request message (referred to as a replica), the number of replicas, and the mapping relationship between the resources for sending the replica and the resources for sending the target request message. The resource information for sending the replica includes, but is not limited to, the replica's frequency band, subcarrier, time slot, and symbol information.

[0278] The mapping relationship between the resources for sending a replica and the resources for sending a target request message refers to the resource mapping relationship between the target request message and the replica. In the embodiments of this application, after sending the target request message, the replica corresponding to the target request message can be accurately sent based on this mapping relationship.

[0279] It should be noted that the mapping relationship between the resources for sending the replica and the resources for sending the target request message can be a fixed mapping relationship or a dynamic mapping relationship, such as dynamically selecting the replica resources based on the current network conditions and load. This application does not specifically limit this.

[0280] In this embodiment, the UE sends msg3 to the network device based on the resource information for sending the target request message. After sending the msg3 message, the UE can send a copy of the msg3 message based on a preset time interval T1. The time interval between two adjacent copies of the msg3 message is a preset time interval T2, which may be the same as or different from T1; this application does not specifically limit this.

[0281] To improve the accuracy of receiving target response messages, both T1 and T2 provided in this application embodiment are smaller than the contention resolution window length. A detailed description follows.

[0282] It should be noted that, for ease of explanation, the following illustration uses two replicas, Re1 and Re2, as an example. It should also be noted that the number of replicas can also be less than two, such as three or four, but since the implementation method is the same as that for two replicas, it will not be discussed further here.

[0283] Figure 9A is a flowchart illustrating another method for implementing a contention-based MO-EDT according to an embodiment of this application. The executor of this method is the UE. The method specifically includes:

[0284] S930-1, UE sends msg3 message.

[0285] S930-2, UE initiates contention resolution window.

[0286] After the UE sends the msg3 message, it initiates the contention resolution window after N subframes and the round-trip time between the UE and the network device.

[0287] S930-3, The UE calculates the radio network identifier based on the time-frequency resources in the msg3 message.

[0288] In this embodiment, after the UE sends a target request message, it can calculate the radio network identifier based on the time-frequency resources of the target request message. This radio network identifier is used for scrambling and scheduling target response messages. For example, after the UE sends a msg3 message, it calculates the RA-RNTI based on the time-frequency resources of the msg3 message.

[0289] It should be noted that S930-2 and S930-3 can be executed simultaneously, or S930-2 can be executed first and then S930-3, or S930-3 can be executed first and then S930-2. This application embodiment does not specifically limit the execution of these two methods.

[0290] S930-4: Based on the wireless network identifier, the UE receives the target response message within the startup resolution window.

[0291] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0292] S931-2, UE sends the copy Re1 corresponding to the msg3 message.

[0293] It should be noted that S931-2 and S930-2 can be executed simultaneously, or S931-2 can be executed first and then S930-2, or S930-2 can be executed first and then S931-2. This application embodiment does not specifically limit the execution.

[0294] S931-3, UE initiates contention resolution window.

[0295] In this embodiment, the UE initiates a contention resolution window after Re1 transmission is completed. Specifically, the UE initiates the contention resolution window after N subframes and the round-trip time between the UE and the network device have elapsed since Re1 transmission was completed.

[0296] S931-4. The UE calculates the radio network identifier based on the time-frequency resources of the sent msg3 message or Rel.

[0297] In this embodiment, the UE can calculate the radio network identifier based on the msg3 message, the time-frequency resources of the Rel, or other resource information of the Rel. This radio network identifier is used for scheduling information in scrambling target response messages.

[0298] It should be noted that S931-3 and S931-4 can be executed simultaneously, or S931-3 can be executed first and then S931-4, or S931-4 can be executed first and then S931-3. This application embodiment does not specifically limit the execution of these two methods.

[0299] S931-5. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0300] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0301] S932-2, UE sends the copy Re2 corresponding to the msg3 message.

[0302] It should be noted that S932-2 and S930-2 can be executed simultaneously, or S932-2 can be executed first and then S930-2, or S930-2 can be executed first and then S932-2. This application embodiment does not specifically limit the execution of S932-2.

[0303] S932-3, UE initiates contention resolution window.

[0304] In this embodiment, the UE initiates a contention resolution window after Re2 transmission is completed. Specifically, the UE initiates the contention resolution window after N subframes and the round-trip time between the UE and the network device have elapsed since the Re2 transmission was completed.

[0305] S932-4. The UE calculates the radio network identifier based on the time-frequency resources of the msg3 message or Re2 message.

[0306] After the UE sends a copy, it can calculate the radio network identifier based on the time-frequency resources of Re2, or it can calculate the radio network identifier based on the time-frequency resources of MSG3. Furthermore, embodiments of this application can also calculate the radio network identifier based on sending the msg3 message or other resources of Re2; this embodiment of the application is not specifically limited. The radio network identifier is used for scheduling information of the scrambling target response message.

[0307] It should be noted that S932-3 and S932-4 can be executed simultaneously, or S932-3 can be executed first and then S932-4, or S932-4 can be executed first and then S932-3. This application embodiment does not specifically limit the execution of these two methods.

[0308] S932-5, the UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0309] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0310] S930-6: The UE determines whether the contention failed. If yes, proceed to S930-7. If no, proceed to S930-8.

[0311] The UE determines whether the contention failure condition is met. If the condition is met, the contention failure is determined. If the condition is not met, the contention success is determined.

[0312] The contention failure condition is that no target response message is received within any of the above contention resolution windows, or that a target response message is received but the contention resolution identifier carried by the target effect message is inconsistent with the user identifier used by the UE.

[0313] S930-7: The UE determines whether the number of transmissions is less than the configured number of transmissions for sending the target request message. If yes, proceed to S930-1; otherwise, proceed to S640.

[0314] S930-8, Stop executing the MO-EDT process.

[0315] As illustrated in Figure 9B, this is a schematic diagram of another method for initiating a contention resolution window according to an embodiment of this application. The message msg3 is sent, followed by its corresponding copies Re1 and Re2. After sending msg3, the contention resolution window is window 1. After sending Re1, window 2 is initiated, and after sending Re2, window 3 is initiated. When msg4 is received in any of the three windows, and the contention resolution identifier carried in msg4 matches the UE's usage identifier, the contention is determined to be successful, and subsequent listening windows and subsequent copy transmissions are stopped.

[0316] For example, as shown in Figure 9B, after the competition in window 2 is successful, subsequent Re2 transmissions and window 3 are stopped.

[0317] In this embodiment of the application, the UE can further increase the probability of successful contention by sending a copy of the target request message after sending the target request message.

[0318] Example 4

[0319] In this embodiment, compared to Embodiment 3, after sending the target request message, and if no target response message is received, or if a target response message is received but the contention resolution identifier carried in the target response message is inconsistent with the UE's usage identifier, a copy of the target request message is then sent. For different copies, if no target response message is received, or if a target response message is received but the contention resolution identifier carried in the target response message is inconsistent with the UE's usage identifier, other copies are sent.

[0320] It should be noted that, for ease of explanation, the following illustration uses two replicas, Re1 and Re2, as an example. It should also be noted that the number of replicas can also be less than two, such as three or four, but since the implementation method is the same as that for two replicas, it will not be discussed further here.

[0321] Figure 10A is an interaction diagram of another competition-based MO-EDT implementation method provided in an embodiment of this application. The method includes the following:

[0322] S1030-1, UE sends msg3 message.

[0323] S1030-2, UE initiates contention resolution window.

[0324] After the UE completes the msg3 message transmission, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0325] S1030-3, The UE calculates the radio network identifier based on the time-frequency resources of the sent msg3 message.

[0326] In this embodiment, after the UE sends a target request message, it can calculate the radio network identifier based on the time-frequency resources of the target request message. This radio network identifier is used for scrambling and scheduling target response messages. For example, after the UE sends a msg3 message, it calculates the RA-RNTI based on the time-frequency resources of the msg3 message.

[0327] It should be noted that S1030-2 and S1030-3 can be executed simultaneously, or S1030-2 can be executed first and then S1030-3, or S1030-3 can be executed first and then S1030-2. This application embodiment does not specifically limit the execution of S1030-2.

[0328] S1030-4. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0329] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0330] S1030-5. Determine if the competition failed. If yes, proceed to S1031-2. If no, proceed to S1030-7.

[0331] S1031-2, The UE sends the copy Re1 corresponding to the msg3 message.

[0332] S1031-3, UE initiates contention resolution window.

[0333] After the UE completes the Re1 message transmission, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0334] S1031-4. The UE calculates the radio network identifier based on the time-frequency resources of the Re1 message or msg3 message.

[0335] It should be noted that S1031-3 and S1031-4 can be executed simultaneously, or S1031-3 can be executed first and then S1031-4, or S1031-4 can be executed first and then S1031-3. This application embodiment does not specifically limit the execution of these two methods.

[0336] S1031-5. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0337] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0338] S103-6. Determine if the competition failed. If yes, proceed to S1032-2. If no, proceed to S1030-7.

[0339] S1032-2, The UE sends the copy Re2 corresponding to the msg3 message.

[0340] S1032-3, UE initiates contention resolution window.

[0341] After the UE completes the Re2 message transmission, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0342] S1032-4. The UE calculates the radio network identifier based on the time-frequency resources of the Re2 or msg3 message sent.

[0343] It should be noted that S1032-3 and S1032-4 can be executed simultaneously, or S1032-3 can be executed first and then S1032-4, or S1032-4 can be executed first and then S1032-3. This application embodiment does not specifically limit the execution of these two methods.

[0344] S1032-5. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0345] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0346] S1032-6, UE determines whether the contention failed. If yes, proceed to S1030-6. If no, proceed to S1030-7.

[0347] The UE determines whether the competition failure condition is met. If it is met, the competition is determined to have failed; otherwise, the competition is determined to have succeeded.

[0348] The contention failure condition is that no target response message is received within any of the above contention resolution windows, or that a target response message is received but the contention resolution identifier carried by the target effect message is inconsistent with the user identifier used by the UE.

[0349] S1030-6, The UE determines whether the number of transmissions is less than the configured number of transmissions for sending the target request message. If yes, proceed to S1030-1; otherwise, proceed to S640.

[0350] S1030-7, Stop executing the MO-EDT process.

[0351] As illustrated in Figure 10B, this is a schematic diagram of a contention resolution window activation method provided in an embodiment of this application. After sending the msg3 message, window 1 is activated. If contention failure is determined, Re1 is sent, and window 2 is activated. If contention failure is determined, Re2 is sent, and window 3 is activated, and so on.

[0352] In summary, compared with Embodiment 3, the embodiments of this application can further increase the probability of UE success in contention by sending a copy of the target request message, while reducing the number of times copies or target request messages are sent. Therefore, it helps to reduce the waste of transmission resources and improve transmission efficiency.

[0353] Example 5

[0354] Compared to Embodiment 4, this embodiment of the application, after sending the target request message and if no target response message is received, or if the target response message is received but the contention fails, then sends a copy corresponding to the target request message. The time interval between sending different copies is a preset interval T2, and after the last copy is sent, a contention resolution window or a contention resolution timer is started to monitor the target response message.

[0355] It should be noted that, for ease of explanation, the following illustration uses two replicas, Re1 and Re2, as an example. It should also be noted that the number of replicas can also be less than two, such as three or four, but since the implementation method is the same as that for two replicas, it will not be discussed further here.

[0356] Figure 11A is an interaction diagram of another competition-based MO-EDT implementation method provided in an embodiment of this application. The method includes the following:

[0357] S1130-1, UE sends msg3 message.

[0358] S1130-2, UE initiates contention resolution window.

[0359] After the UE sends the msg3 message, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0360] S1130-3, The UE calculates the radio network identifier based on the time-frequency resources of the sent msg3 message.

[0361] In this embodiment, after the UE sends a target request message, it can calculate the radio network identifier based on the time-frequency resources of the target request message. This radio network identifier is used for scrambling and scheduling target response messages. For example, after the UE sends a msg3 message, it calculates the RA-RNTI based on the time-frequency resources of the msg3 message.

[0362] It should be noted that S1130-2 and S1130-3 can be executed simultaneously, or S1130-2 can be executed first and then S1130-3, or S1130-3 can be executed first and then S1130-2. This application embodiment does not specifically limit the execution of these two methods.

[0363] S1130-4. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0364] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0365] S1130-5. Determine if the competition failed. If yes, proceed to S1131-2. If no, proceed to S1130-7.

[0366] S1131-2, The UE sends the replicas Re1 and Re2 corresponding to the msg3 message.

[0367] S1131-3, UE initiates contention resolution window.

[0368] After the UE sends the last copy, i.e., Re2, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0369] S1131-4. The UE calculates the radio network identifier based on the time-frequency resources of the Re2 or msg3 message sent.

[0370] It should be noted that S1131-3 and S1131-4 can be executed simultaneously, or S1131-3 can be executed first and then S1131-4, or S1131-4 can be executed first and then S1131-3. This application embodiment does not specifically limit the execution of these two methods.

[0371] S1131-5. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0372] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0373] S1131-6. Determine if the competition failed. If yes, proceed to S1132-6. If no, proceed to S1130-7.

[0374] S1130-6: The UE determines whether the number of transmissions is less than the configured number of transmissions for sending the target request message. If yes, proceed to S1130-1; otherwise, proceed to S640.

[0375] S1130-7, Stop executing the MO-EDT process.

[0376] As illustrated in Figure 11B, this is a schematic diagram of another method for initiating a contention resolution window according to an embodiment of this application. After sending the msg3 message, window 1 is initiated. If contention is determined to have failed, Re1 and Re2 are sent sequentially, initiating the window corresponding to Re2, and so on.

[0377] Compared to Embodiment 4, the embodiments of this application can reduce the number of times the window is launched and improve processing efficiency.

[0378] Example 6

[0379] Compared to Embodiment 5, this embodiment of the application, after sending the target request message, sends a copy of the target request message based on a time interval T1. A copy is sent once based on a time interval T2, and after the last copy is sent, a contention resolution window is initiated to monitor the target response message.

[0380] It should be noted that, for ease of explanation, the following illustration uses two replicas, Re1 and Re2, as an example. It should also be noted that the number of replicas can also be less than two, such as three or four, but since the implementation method is the same as that for two replicas, it will not be discussed further here.

[0381] Figure 12A is an interaction diagram of another implementation method based on MO-EDT provided in an embodiment of this application. This method includes the following:

[0382] S1230-1, UE sends msg3 message.

[0383] S1231-2, The UE sends the replicas Re1 and Re2 corresponding to the msg3 message.

[0384] S1231-3, UE initiates contention resolution window.

[0385] After the UE sends the last copy, i.e., Re2, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0386] S1231-4. The UE calculates the radio network identifier based on the time and frequency resources of Re2.

[0387] It should be noted that S1231-3 and S1231-4 can be executed simultaneously, or S1231-3 can be executed first and then S1231-4, or S1231-4 can be executed first and then S1231-3. This application embodiment does not specifically limit the execution of these two methods.

[0388] S1231-5. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0389] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0390] S1232-6. The UE determines whether the contention failed. If yes, proceed to S1230-6. If no, proceed to S1230-7.

[0391] The UE determines whether the competition failure condition is met. If it is met, the competition is determined to have failed; otherwise, the competition is determined to have succeeded.

[0392] The contention failure condition is that no target response message is received within any of the above contention resolution windows, or that a target response message is received but the contention resolution identifier carried by the target effect message is inconsistent with the user identifier used by the UE.

[0393] S1230-6: The UE determines whether the number of transmissions is less than the configured number of transmissions for sending the target request message. If yes, proceed to S1230-1; otherwise, proceed to S640.

[0394] S1230-7, Stop executing the MO-EDT process.

[0395] As illustrated in Figure 12B, this is another schematic diagram of launching a contention resolution window according to an embodiment of this application. After sending the msg3 message, Re1 and Re2 are sent, launching the window corresponding to Re2, and so on.

[0396] Therefore, the embodiments of this application can further reduce the number of times the contention resolution window is initiated, and further improve processing efficiency.

[0397] Example 7

[0398] The configuration information provided in this application embodiment is the configuration information for sending target request messages according to the coverage level. In one specific implementation, the coverage level of network devices is currently divided into three levels: coverage level 0, coverage level 1, and coverage level 2.

[0399] Figure 13A is a schematic diagram of a coverage level provided in an embodiment of this application. The coverage area corresponding to coverage level 0 is called range 1, the coverage area corresponding to coverage level 1 is called range 2, and the coverage area corresponding to coverage level 2 is called range 3. The Reference Signal Received Power (RSRP) within range 1 is greater than the RSRP within range 2, and the RSRP within range 2 is greater than the RSRP within range 3.

[0400] In this embodiment, the network device can configure a threshold value for the Reference Signal Received Power (RSRP) for each coverage level. The UE can determine the range where the UE is located, and thus the coverage level, by measuring the RSRP and the threshold values ​​for each range.

[0401] In this embodiment, the configuration information further includes resource information for sending target request messages according to coverage level, contention resolution window length (or contention resolution timer), and the number of transmissions for sending target request messages according to coverage level. For example, resource information 1 corresponds to coverage level 0, and the number of transmissions is M1; resource information 2 corresponds to coverage level 1, and the number of transmissions is M2; resource information 3 corresponds to coverage level 2, and the number of transmissions is M3. Wherein, M1, M2, and M3 are all positive integers.

[0402] It should be noted that the configuration information can be configured separately according to the coverage level, or the configuration can be allocated to each coverage level at the same time. This application embodiment does not specifically limit this.

[0403] After a UE initiates a contention-based MO-EDT, it first determines the current coverage level and selects the resource corresponding to the target request message according to the coverage level, then sends the target request message. For example, the resource information corresponding to coverage level 0 is resource information 1; the resource information corresponding to coverage level 1 is resource information 2; and the resource information corresponding to coverage level 2 is resource information 3. The UE determines that the current coverage level is coverage level 2, and the UE first obtains resource information 3 corresponding to coverage level 2, then uses resource information 3 to send the target request message.

[0404] Figure 13B is a flowchart of another method for performing contention-based MO-EDT provided in an embodiment of this application. The executor of this method is the UE. This method is illustrated using coverage levels including coverage level 0, coverage level 1, and coverage level 2 as examples. Specifically, coverage level 0 corresponds to M1 transmissions, coverage level 1 corresponds to M2 transmissions, and coverage level 2 corresponds to M3 transmissions, as illustrated in the example.

[0405] The method specifically includes:

[0406] S1330-1, UE sends msg3 message.

[0407] S1330-2, UE initiates contention resolution window.

[0408] After the UE completes the last msg3 message transmission, and after N subframes and the round-trip time between the user equipment and the network equipment, the contention resolution window is initiated.

[0409] S1330-3, The UE calculates the radio network identifier based on the time-frequency resources of the last msg3 message sent.

[0410] In this embodiment of the application, after the UE sends a target request message, it can calculate the radio network identifier based on the time-frequency resources of the target request message.

[0411] It should be noted that S1330-2 and S1330-3 can be executed simultaneously, or S1330-2 can be executed first and then S1330-3, or S1330-3 can be executed first and then S1330-2. This application embodiment does not specifically limit the execution of S1330-2.

[0412] S1330-4. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0413] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0414] S1330-5. The UE determines whether the contention failed. If yes, proceed to S1330-6. If no, proceed to S1330-8.

[0415] S1330-6: The UE determines whether the number of transmissions is less than the configured number of transmissions for sending the target request message. If yes, proceed to S1330-1; otherwise, proceed to S1330-7.

[0416] Increment the transmission count of msg3 to obtain the total number of transmissions of msg3 under the current coverage level.

[0417] It should be noted that in this embodiment, the UE repeatedly sends the msg3 message, and after the last transmission, it increments the count of msg3 transmissions to obtain the total number of msg3 transmissions under the current coverage level. For example, if the UE repeatedly sends the msg3 message 6 times, after the 6th transmission, the UE increments the count of msg3 transmissions to obtain the total number of msg3 transmissions under the current coverage level.

[0418] It should be noted that the number of times the UE can repeatedly send the msg3 message can be configured by the network device.

[0419] In this embodiment, the total number of msg3 transmissions before the first transmission of the msg3 message under each coverage level is a preset initial value, such as 0. That is, when the coverage level is adjusted from one coverage level to another, the total number of transmissions is recalculated, thereby ensuring the probability of successful calculation.

[0420] For example, if the current coverage level is 0, the total number of transmissions is M1, and the total number of transmissions is not less than the number of transmissions of the target request message under coverage level 0, then execute S1330-7.

[0421] S1330-7: The UE determines whether the current coverage level is the highest coverage level. If yes, execute S640; otherwise, adjust to the next coverage level and execute S1330-1.

[0422] The highest coverage level is the weakest coverage level of RSRP. For Figure 13A, the highest coverage level is coverage level 2. In this embodiment, "adjusted from the current coverage level to another coverage level" means adjusted from a low coverage level to a high coverage level, such as from coverage level 0 to coverage level 1, or from coverage level 1 to coverage level 2.

[0423] S1330-8, Stop executing the MO-EDT process.

[0424] This application's embodiments perform contention-based MO-EDT according to coverage levels. Different coverage levels correspond to different transmission parameters and resource configurations, thus better adapting to various coverage conditions and improving transmission reliability. Furthermore, allocating resources according to coverage levels allows for more efficient use of wireless resources, avoiding resource waste and improving resource utilization.

[0425] Example 8

[0426] Compared to Embodiment Seven, this embodiment of the application further includes DSA configuration information configured according to coverage level. Specifically, the configuration information includes resource information for sending target request messages according to coverage level, DSA configuration information according to coverage level, contention resolution window length, and the number of transmissions of target request messages according to coverage level.

[0427] The DSA configuration information includes, but is not limited to, the following: resource information for sending target request message replicas, the number of replicas N2, and the mapping relationship between the resources for sending replicas and the resources for sending target request messages.

[0428] The resource information for sending a copy includes the copy's frequency band, subcarrier, time slot, and symbol.

[0429] The mapping relationship between the resources for sending a replica and the resources for sending a target request message refers to the resource mapping relationship between the target request message and the replica. In the embodiments of this application, after sending the target request message, the replica corresponding to the target request message can be accurately sent based on this mapping relationship.

[0430] It should be noted that the mapping relationship between the resources for sending the replica and the resources for sending the target request message can be a fixed mapping relationship or a dynamic mapping relationship, such as dynamically selecting the replica resources based on the current network conditions and load. This application does not specifically limit this.

[0431] In addition, the configuration information includes the number of identical repeated transmissions per replica (N1) and the number of distinct repeated transmissions per replica (N2). Both N1 and N2 are positive integers. The number of identical repeated transmissions per replica (N1) refers to the number of times each replica transmits on the same resource. For example, the UE can choose to transmit Re1 on resource 1, sending it N1 times. The number of distinct repeated transmissions per replica (N2) refers to the number of times each replica transmits on N2 resources. For example, if the replica is Rel, the UE can choose to transmit Re1 on resource 1, Re1 on resource 2, and so on, transmitting Re1 on resource N2.

[0432] By configuring the number of identical and distinct duplicate transmissions for each replica, the reliability and anti-interference capability of data transmission can be further improved. The UE transmits the same replica multiple times on the same resource and multiple times on different resources, utilizing diversity techniques to enhance transmission robustness. This helps ensure the success of the random access procedure and improves the overall performance and reliability of the system.

[0433] In this embodiment, the UE determines the current coverage level and sends msg3 to the network device based on the resource information for sending a target request message corresponding to the current coverage level. In this embodiment, after sending the msg3 message, the UE can send a copy of the msg3 message based on a preset time interval T1. The time interval between two adjacent copies of the msg3 message is a preset time interval T2, which may be the same as or different from T1; this application does not specifically limit this.

[0434] To improve the accuracy of receiving target response messages, both T1 and T2 provided in this application embodiment are smaller than the contention resolution window length. A detailed description follows.

[0435] It should be noted that, for ease of explanation, the following illustration uses two replicas, Re1 and Re2, as an example. It should also be noted that the number of replicas can also be less than two, such as three or four, but since the implementation method is the same as that for two replicas, it will not be discussed further here.

[0436] Figure 14 is a flowchart of another method for performing contention-based MO-EDT provided in an embodiment of this application. The executor of this method is the UE. The method specifically includes:

[0437] S1430-1, UE sends msg3 message.

[0438] S14302, UE starts the contention resolution window.

[0439] After the UE completes the last transmission of the msg3 message, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0440] S1430-3, The UE calculates the radio network identifier based on the time-frequency resources of the last msg3 message sent.

[0441] It should be noted that S1430-2 and S1430-3 can be executed simultaneously, or S1430-2 can be executed first and then S1430-3, or S1430-3 can be executed first and then S1430-2. This application embodiment does not specifically limit the execution of these two methods.

[0442] S1430-4. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0443] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0444] S1431-2, The UE sends a copy of the msg3 message.

[0445] Specifically, the UE retransmits Re1 based on the number of identical retransmissions and the number of different retransmissions of Re1. For example, if the number of identical retransmissions of Re1 is 2 and the number of different retransmissions is 3, then the UE will retransmit Re1 6 times.

[0446] It should be noted that S1431-2 and S1430-2 can be executed simultaneously, or S1431-2 can be executed first and then S1430-2, or S1430-2 can be executed first and then S1431-2. This application embodiment does not specifically limit the execution of S1431-2.

[0447] S1431-3, UE initiates contention resolution window.

[0448] In this embodiment, the UE initiates a contention resolution window after the last copy is sent. For example, the UE retransmits Re1 6 times, and the last copy is the 6th Re1 transmission.

[0449] S1430-4. The UE calculates the radio network identifier based on the time-frequency resources of the last Re1 or the last msg3 message sent.

[0450] It should be noted that S1430-3 and S1430-4 can be executed simultaneously, or S1430-3 can be executed first and then S1430-4, or S1430-4 can be executed first and then S1430-3. This application embodiment does not specifically limit the execution of S1430-3.

[0451] S1430-5. Based on the wireless network identifier, the UE receives the target response message within the startup resolution window.

[0452] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0453] S1432-2, The UE sends the copy Re2 corresponding to the msg3 message.

[0454] Specifically, the UE retransmits Re2 based on the number of identical retransmissions and the number of different retransmissions of Re2. For example, if the number of identical retransmissions of Re2 is 2 and the number of different retransmissions is 3, then the UE will retransmit Re2 6 times.

[0455] It should be noted that S1432-2 and S1430-2 can be executed simultaneously, or S1432-2 can be executed first and then S1430-2, or S1430-2 can be executed first and then S1432-2. This application embodiment does not specifically limit the execution.

[0456] S1432-3, UE initiates contention resolution window.

[0457] In this embodiment of the application, after the UE completes the last Re2 transmission, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0458] S1432-4. The UE calculates the radio network identifier based on the time-frequency resources of the last Re2 or the last msg3 message sent.

[0459] After the UE sends a copy, it can calculate the radio network identifier based on the time-frequency resources of Re2 or msg3. This radio network identifier is used for scheduling information in scrambling target response messages.

[0460] It should be noted that S1432-3 and S1432-4 can be executed simultaneously, or S1432-3 can be executed first and then S1432-4, or S1432-4 can be executed first and then S1432-3. This application embodiment does not specifically limit the execution of S1432-3.

[0461] S1432-5. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0462] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0463] S1430-5. The UE determines whether the contention failed. If yes, proceed to S1430-6. If no, proceed to S1430-8.

[0464] The UE determines whether the competition failure condition is met. If it is met, the competition is determined to have failed; otherwise, the competition is determined to have succeeded.

[0465] The contention failure condition is that no target response message is received within any of the above contention resolution windows, or that a target response message is received but the contention resolution identifier carried by the target effect message is inconsistent with the user identifier used by the UE.

[0466] S1430-6: The UE determines whether the number of transmissions is less than the configured number of transmissions for sending the target request message. If yes, proceed to S1430-1; otherwise, proceed to S1430-7.

[0467] Increment the transmission count of msg3 to obtain the total number of transmissions of msg3 under the current coverage level.

[0468] It should be noted that in this embodiment, the UE repeatedly sends the msg3 message, and after the last transmission, it increments the count of msg3 transmissions to obtain the total number of msg3 transmissions under the current coverage level. For example, if the UE repeatedly sends the msg3 message 6 times, after the 6th transmission, the UE increments the count of msg3 transmissions to obtain the total number of msg3 transmissions under the current coverage level.

[0469] It should be noted that the number of times the UE can repeatedly send the msg3 message can be configured by the network device.

[0470] In this embodiment, the total number of msg3 transmissions before the first transmission of the msg3 message under each coverage level is a preset initial value, such as 0. That is, when the coverage level is adjusted from one coverage level to another, the total number of transmissions is recalculated, thereby ensuring the probability of successful calculation.

[0471] For example, if the current coverage level is 0, the total number of transmissions is M1, and the total number of transmissions is not less than the number of transmissions of the target request message under coverage level 0, then execute S1430-7.

[0472] S1430-7. The UE determines whether the current coverage level is the highest coverage level. If yes, execute S640. If no, adjust to the next coverage level and execute S1430-1.

[0473] The highest coverage level is the weakest coverage level of RSRP. For Figure 13A, the highest coverage level is coverage level 2. In this embodiment, "adjusted from the current coverage level to another coverage level" means adjusted from a low coverage level to a high coverage level, such as from coverage level 0 to coverage level 1, or from coverage level 1 to coverage level 2.

[0474] S1430-8, Stop executing the MO-EDT process.

[0475] In this embodiment of the application, performing contention-based MO-EDT with DSA according to the coverage level can improve the contention success rate while improving resource utilization and reliability.

[0476] Example 9

[0477] In this embodiment of the application, after sending the target request message, and if no target response message is received, or if a target response message is received but the contention resolution identifier carried in the target response message is inconsistent with the UE's usage identifier, a copy of the target request message is then sent. For different copies, if no target response message is received, or if a target response message is received but the contention resolution identifier carried in the target response message is inconsistent with the UE's usage identifier, other copies are sent.

[0478] It should be noted that, for ease of explanation, the following illustration uses two replicas, Re1 and Re2, as an example. It should also be noted that the number of replicas can also be less than two, such as three or four, but since the implementation method is the same as that for two replicas, it will not be discussed further here.

[0479] Figure 15 is an interaction diagram of another competition-based MO-EDT implementation method provided in an embodiment of this application. The method includes the following:

[0480] S1530-1, UE sends msg3 message.

[0481] S1530-2, UE initiates contention resolution window.

[0482] After the UE completes the last msg3 message transmission, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0483] S1530-3, The UE calculates the radio network identifier based on the time-frequency resources of the last msg3 message sent.

[0484] It should be noted that S1530-3 and S1530-4 can be executed simultaneously, or S1530-3 can be executed first and then S1530-4, or S1530-4 can be executed first and then S1530-3. This application embodiment does not specifically limit the execution of S1530-3.

[0485] S1530-4. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0486] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0487] S1530-5. Determine if the competition failed. If yes, proceed to S1531-2. If no, proceed to S1530-8.

[0488] S1531-2, The UE sends the copy Re1 corresponding to the msg3 message.

[0489] Specifically, the UE retransmits Re1 based on the number of identical retransmissions and the number of different retransmissions of Re1. For example, if the number of identical retransmissions of Re1 is 2 and the number of different retransmissions is 3, then the UE will retransmit Re1 6 times.

[0490] S1531-3, UE initiates contention resolution window.

[0491] In this embodiment, the UE initiates a contention resolution window after the last copy is sent. For example, the UE retransmits Re1 6 times, and the last copy is the 6th Re1 transmission.

[0492] S1531-4. The UE calculates the radio network identifier based on the time-frequency resources of the last Rel or the last msg3 message sent.

[0493] It should be noted that S1531-3 and S1531-4 can be executed simultaneously, or S1531-3 can be executed first and then S1531-4, or S1531-4 can be executed first and then S1531-3. This application embodiment does not specifically limit the execution of these two methods.

[0494] S1531-5. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0495] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0496] S153-6. Determine if the competition failed. If yes, proceed to S1532-2. If no, proceed to S1530-7.

[0497] S1532-2, The UE sends the copy Re2 corresponding to the msg3 message.

[0498] Specifically, the UE retransmits Re2 based on the number of identical retransmissions and the number of different retransmissions of Re2. For example, if the number of identical retransmissions of Re2 is 2 and the number of different retransmissions is 3, then the UE will retransmit Re2 6 times.

[0499] S1532-3, UE initiates contention resolution window.

[0500] In this embodiment of the application, after the UE completes the last Re2 transmission, and after N subframes and the round-trip time between the UE and the network device, the contention resolution window is initiated.

[0501] S1532-4. The UE calculates the radio network identifier based on the time-frequency resources of the last msg3 message sent or the last Re2 message sent.

[0502] It should be noted that S1532-3 and S1532-4 can be executed simultaneously, or S1532-3 can be executed first and then S1532-4, or S1532-4 can be executed first and then S1532-3. This application embodiment does not specifically limit the execution of these two methods.

[0503] S1532-5. The UE receives the target response message within the startup resolution window based on the wireless network identifier.

[0504] For example, the UE listens for downlink messages based on RA-RNTI to receive the target response message.

[0505] S1532-6, UE determines whether the contention failed. If yes, proceed to S1530-1. If no, proceed to S1530-8.

[0506] The UE determines whether the competition failure condition is met. If it is met, the competition is determined to have failed; otherwise, the competition is determined to have succeeded.

[0507] The contention failure condition is that no target response message is received within any of the above contention resolution windows, or that a target response message is received but the contention resolution identifier carried by the target effect message is inconsistent with the user identifier used by the UE.

[0508] S1530-6: The UE determines whether the number of transmissions is less than the configured number of transmissions for sending the target request message. If yes, proceed to S1530-1; otherwise, proceed to S1530-7.

[0509] Increment the transmission count of msg3 to obtain the total number of transmissions of msg3 under the current coverage level.

[0510] It should be noted that in this embodiment, the UE repeatedly sends the msg3 message, and after the last transmission, it increments the count of msg3 transmissions to obtain the total number of msg3 transmissions under the current coverage level. For example, if the UE repeatedly sends the msg3 message 6 times, after the 6th transmission, the UE increments the count of msg3 transmissions to obtain the total number of msg3 transmissions under the current coverage level.

[0511] It should be noted that the number of times the UE can repeatedly send the msg3 message can be configured by the network device.

[0512] In this embodiment, the total number of msg3 transmissions before the first transmission of the msg3 message under each coverage level is a preset initial value, such as 0. That is, when the coverage level is adjusted from one coverage level to another, the total number of transmissions is recalculated, thereby ensuring the probability of successful calculation.

[0513] For example, if the current coverage level is 0, the total number of transmissions is M1, and the total number of transmissions is not less than the number of transmissions of the target request message under coverage level 0, then execute S1530-7.

[0514] S1530-7. The UE determines whether the current coverage level is the highest coverage level. If yes, execute S640. If no, adjust to the next coverage level and execute S1530-1.

[0515] The highest coverage level is the weakest coverage level of RSRP. For Figure 13A, the highest coverage level is coverage level 2. In this embodiment, "adjusted from the current coverage level to another coverage level" means adjusted from a low coverage level to a high coverage level, such as from coverage level 0 to coverage level 1, or from coverage level 1 to coverage level 2.

[0516] S1530-8, Stop executing the MO-EDT process.

[0517] In summary, the embodiments of this application, which perform contention-based MO-EDT with DSA according to coverage level, can reduce the number of times copies or target request messages are sent while improving resource utilization and reliability. Therefore, it helps to reduce transmission resource waste and improve transmission efficiency.

[0518] Alternatively, it can be executed after sending the target request message, and if no target response message is received, or if the target response message is received but contention fails, to send the replica corresponding to the target request message. The time interval between sending different replicas is a preset interval T2, and after the last replica is sent, a contention resolution window or contention resolution timer is started to monitor the target response message.

[0519] Furthermore, after sending the target request message, a replica corresponding to the target request message is sent based on a time interval T1. A replica is sent once based on a time interval T2, and after the last replica is sent, a contention resolution window is initiated to monitor the target response message.

[0520] In addition, other methods can be implemented in the embodiments of this application, and the embodiments of this application are not specifically limited.

[0521] The hardware implementation of network devices and UEs will be further described below with reference to Figures 16 and 17.

[0522] Referring to Figure 16, a schematic diagram of the hardware structure of a network device is shown. This network device can be used to execute methods performed by the network device. The network device shown in Figure 16 includes at least one processor 111, at least one memory 112, at least one transceiver 113, at least one network interface 114, and one or more antennas 115. The processor 111, memory 112, transceiver 113, and network interface 114 are connected, for example, via a bus. In this embodiment, the connection may include various interfaces, transmission lines, or buses, etc., and this embodiment is not limited thereto. The antenna 115 is connected to the transceiver 113. The network interface 114 is used to enable the network device to connect with other communication devices through a communication link. For example, the network interface 114 may include a network interface between a satellite network device and a network device in the core network, such as an S1 interface. The network interface may also include a network interface between the network device and other network devices, such as an X2 or Xn interface.

[0523] Specifically, the processor 111 shown in Figure 16 can perform the network device processing actions in the above method, the memory 112 can perform the storage actions in the above method, the transceiver 113 and the antenna 115 can perform the air interface transmission and reception actions in the above method, and the network interface 114 can perform the interaction actions with the network device or other network devices / network elements in the above method.

[0524] The processor in this application embodiment, such as processor 111, may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., which are various computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing. The processor may be a separate semiconductor chip or integrated with other circuits into a single semiconductor chip. For example, it may form a SoC (System-on-a-Chip) with other circuits (such as encoding / decoding circuits, hardware acceleration circuits, or various bus and interface circuits), or it may be integrated as a built-in processor in an ASIC. The ASIC with the integrated processor may be packaged separately or packaged together with other circuits. In addition to including cores for executing software instructions to perform calculations or processing, the processor may further include necessary hardware accelerators, such as FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), or logic circuits that implement dedicated logic operations.

[0525] The memory in the embodiments of this application may include at least one of the following types: read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; or electrically erasable programmable-only memory (EEPROM). In some scenarios, the memory may also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto.

[0526] The memory 112 can exist independently and be connected to the processor 111. Optionally, the memory 112 can be integrated with the processor 111, for example, integrated into a single chip. The memory 112 can store program code that executes the technical solutions of the embodiments of this application, and its execution is controlled by the processor 111. The various types of computer program code being executed can also be considered as drivers for the processor 111. For example, the processor 111 executes the computer program code stored in the memory 112 to implement the technical solutions of the embodiments of this application.

[0527] Transceiver 113 can be used to support the reception or transmission of radio frequency (RF) signals between network devices and other devices. Transceiver 113 can be connected to antenna 115. Transceiver 113 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 115 can receive RF signals. The receiver Rx of transceiver 113 is used to receive the RF signals from the antennas, convert the RF signals into digital baseband signals or digital intermediate frequency (IF) signals, and provide the digital baseband signals or IF signals to the processor 111 so that the processor 111 can perform further processing on the digital baseband signals or IF signals, such as demodulation and decoding. In addition, the transmitter Tx in transceiver 113 is also used to receive modulated digital baseband signals or IF signals from processor 111, convert the modulated digital baseband signals or IF signals into RF signals, and transmit the RF signals through one or more antennas 115. Specifically, the receiver Rx can selectively perform one or more stages of downmixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency (IF) signal. The order of the downmixing and IF conversion processes is adjustable. The transmitter Tx can selectively perform one or more stages of upmixing and digital-to-analog conversion on the modulated digital baseband signal or digital IF signal to obtain a radio frequency signal. The order of the upmixing and IF conversion processes is also adjustable. The digital baseband signal and the digital IF signal can be collectively referred to as digital signals.

[0528] Figure 17 shows an example of the composition of a UE provided in an embodiment of this application. The UE may be, for example, a mobile phone, a smart wearable device (such as a smartwatch), etc. Taking a mobile phone as an example, the UE may include a processor 310, an external memory interface 320, an internal memory 321, a display screen 330, a camera 340, an antenna 1, an antenna 2, a mobile communication module 350, and a wireless communication module 360, etc.

[0529] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the UE. In other embodiments, the UE 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.

[0530] Processor 310 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, time-frequency codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0531] 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 UE. In other embodiments of this application, the UE may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0532] The external memory interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the UE's storage capacity. The external memory card communicates with the processor 310 through the external memory interface 320 to perform data storage functions. For example, music, time and frequency files can be saved on the external memory card.

[0533] Internal memory 321 can be used to store computer executable program code, including instructions. Processor 310 executes various functional applications and data processing of the UE by running the instructions stored in internal memory 321. Internal memory 321 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc. The data storage area may store data created by the UE during use (such as time-frequency stream data), etc. In addition, internal memory 321 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 310 executes various functions and data processing of the UE by running instructions stored in internal memory 321 and / or instructions stored in memory disposed in the processor.

[0534] The UE's wireless communication function can be implemented through antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, modem processor, and baseband processor.

[0535] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the UE can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0536] The mobile communication module 350 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G on the UE. The mobile communication module 350 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 350 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 350 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 350 may be housed in the processor 310. In some embodiments, at least some functional modules of the mobile communication module 350 and at least some modules of the processor 310 may be housed in the same device.

[0537] In some embodiments, the UE sends a request via the mobile communication module 350 and the antenna 1.

[0538] 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 any of the UE components described above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0539] Furthermore, embodiments of this application also provide a computer-readable storage medium storing instructions that, when executed on one or more computing devices, cause the one or more computing devices to perform the communication method described in the above embodiments.

[0540] Furthermore, this application also provides a computer program product, which, when executed by one or more computing devices, allows the computing devices to execute any of the aforementioned communication methods. The computer program product can be a software installation package; when any of the aforementioned communication methods is required, the computer program product can be downloaded and executed on a computer.

[0541] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0542] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0543] The computer program product includes one or more computer instructions. When the computer program 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. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0544] The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

Claims

1. A communication method, characterized in that, Applied to a user equipment in a first cell, the method includes: Receive configuration information, the configuration information being used to enable multiple devices in the first cell to directly perform the operation of contention-based mobile calling party advance data transmission (MO-EDT) to send data, the multiple devices including the user equipment; Based on the configuration information and the triggering information of the user equipment, a target request message is sent. The target request message is a message carrying user data of the user equipment, or the target request message is a message multiplexed with the user data. The triggering information is used to determine whether the user equipment can perform a contention-based MO-EDT data transmission operation.

2. The method according to claim 1, characterized in that, The triggering information includes one or more of the following: Whether the upper layer initiates a request to establish a Radio Resource Control (RRC) connection or an RRC connection recovery request, whether contention-based MO-EDT is supported, whether the received broadcast message carries target indication information and whether there is a pre-compensated timing advance, and whether the target indication information indicates whether the network device sending the broadcast message allows the execution of contention-based MO-EDT.

3. The method according to claim 2, characterized in that, The target indication message includes a first indication message and / or a second indication message, wherein the first indication message indicates that the network device allows the execution of user plane-based MO-EDT; and the second indication message indicates that the network device allows the execution of control plane-based MO-EDT.

4. The method according to claim 2 or 3, characterized in that, Sending a target request message based on the configuration information and the triggering information of the user equipment includes: If the broadcast message carries first indication information and the user equipment supports contention-based user plane MO-EDT, a first target request message is sent based on the configuration information. The first target request message is a connection restoration request message multiplexed with the user data. If the broadcast message carries second indication information, and the user equipment supports contention-based control plane MO-EDT, a second target request message is sent based on the configuration information. The second target request message is a connection establishment request message carrying the user data.

5. The method according to any one of claims 1-4, characterized in that, The configuration information includes: configuration information for sending target request messages, or configuration information for sending target request messages according to coverage level.

6. The method according to claim 5, characterized in that, The configuration information for sending the target request message includes one or more of the following: Resource information for sending the target request message, contention resolution window length, contention resolution timer, and number of transmissions for sending the target request message.

7. The method according to claim 5 or 6, characterized in that, The method further includes: Initiate a contention resolution window or a contention resolution timer, and within the contention resolution window or the contention resolution timer, receive a target response message; the target response message carries a contention resolution identifier, which is used to identify the device that successfully competed in the first cell; If the target response message is obtained, and the contention resolution identifier is consistent with the user identifier used by the user equipment, the contention is determined to be successful.

8. The method according to claim 6, characterized in that, The specific methods for starting the race resolution window or starting the race resolution timer include: After the target request message is sent, and after N subframes and the round-trip time between the user equipment and the network equipment, the contention resolution window or the contention resolution timer is started, where N is a positive integer.

9. The method according to claim 7 or 8, characterized in that, The method further includes: Based on the total number of transmissions and the contention failure conditions, it is determined whether the contention has failed; the contention failure conditions include not obtaining the target response message, or obtaining the target response message, and the contention resolution identifier is inconsistent with the user identifier used by the user equipment; If the total number of transmissions is less than the number of transmissions of the target request message, and the contention failure condition is met, the contention failure is determined. The target request message is resent, and the count of the number of transmissions of the target request message is incremented. The process of determining whether the contention has failed continues until a preset stopping condition is met. The preset stopping condition is that the total number of transmissions is greater than or equal to the number of transmissions of the target request message, or the contention is determined to be successful.

10. The method according to claim 4, characterized in that, If the configuration information also includes the number of times the target request message is sent corresponding to the coverage level; Obtain the number of transmissions of the target request message under the current coverage level; Based on the total number of transmissions under the current coverage level and the contention failure conditions, it is determined whether the contention has failed; the contention failure conditions include not obtaining the target response message, or obtaining the target response message and the contention resolution identifier being inconsistent with the user identifier used by the user equipment; If the number of transmissions is less than or equal to the number of transmissions corresponding to the current coverage level, and the contention failure condition is met, then the contention failure is determined. The target request message is resent, the transmission count counter is incremented, and the step of determining whether the contention has failed is continued until a preset stopping condition is met. The preset stopping condition is that the number of transmissions is greater than or equal to the number of transmissions of the target request message corresponding to the target coverage level, or the contention is determined to be successful. If the number of transmissions is greater than or equal to the number of transmissions corresponding to the current coverage level, the system jumps to the next coverage level, which is higher than the current coverage level, and the number of transmissions of the target request sent under the adjusted coverage level is adjusted back to the initial value.

11. The method according to claim 1, characterized in that, The configuration information also includes diversity slot DSA configuration information, which includes: configuration information for configuring the sending of target request message replicas, or configuration information for configuring the sending of target request message replicas according to coverage level.

12. The method according to claim 11, characterized in that, The configuration information for sending a copy of the target request message includes one or more of the following: resource information of the copy of the target request message, the number of copies, and the mapping relationship between the resources of the copy and the resources of the target request message. If the configuration information for sending the target request message copy is configured according to the coverage level, the configuration information for sending the target request message copy includes one or more of the following: resource information for the configuration information of sending the target request message copy, number of copies, number of duplicate copies, and mapping relationship between the resources for sending copies and the resources for sending the target request message.

13. The method according to claim 11 or 12, characterized in that, The method further includes: Based on the DSA configuration information and the fact that the user equipment supports contention-based MO-EDT with DSA, a copy of the target request message is sent, or a copy of the target request message is sent according to the coverage level.

14. The method according to claim 13, characterized in that, After sending the copy of the target request message, the method further includes: After the last copy is sent, a contention resolution window or a contention resolution timer is started; or, if the target request message copies are sent according to the coverage level, a contention resolution window or a contention resolution timer is started after the last duplicate of the last copy is sent. Within the contention resolution window or the contention resolution timer, receive the target response message; If the target response message is obtained, and the contention resolution identifier carried in the target response information is consistent with the user identifier sent by the user equipment, the contention is determined to be successful.

15. The method according to claim 14, characterized in that, The receiving of the target response message includes: The radio network identifier is calculated based on the time-frequency resources of the target request message, or the radio network identifier is calculated based on the time-frequency resources of a copy of the target request message. Using the calculated wireless network identifier, downlink messages are monitored to obtain the target response message.

16. The method according to claim 14, characterized in that, The step of starting a contention resolution window or a contention resolution timer after the last copy has been sent includes: After the last copy is sent, and after N subframes and the RTT time between the user equipment and the network equipment, the contention resolution window or the contention resolution timer is started, where N is a positive integer. If the target request message replicas are sent according to the coverage level, after the last duplicate of the last replica has been sent, a contention resolution window or contention resolution timer is started, including: If the target request message copy is sent according to the coverage level, after the last duplicate of the last copy is sent, and after N subframes and the RTT time of the user equipment and network equipment, a contention resolution window or contention resolution timer is started.

17. The method according to any one of claims 14-16, characterized in that, The method further includes: After the first copy is sent, the contention resolution window or the contention resolution timer is started. If the target response message is not received within the contention resolution window or the contention resolution timer, or if the target response message is received but the contention resolution identifier in the target response message is inconsistent with the user identifier used by the user equipment, the second copy is sent. Alternatively, if the target request message copy is sent according to the coverage level, after the last duplicate of the first copy is sent, the contention resolution window or the contention resolution timer is started. If the target response message is not obtained within the contention resolution window or the contention resolution timer, or if the target response message is obtained but the contention resolution identifier in the target response message is inconsistent with the user identifier used by the user equipment, a second copy is sent.

18. The method according to any one of claims 14-16, characterized in that, The step of starting a contention resolution window or a contention resolution timer after the last copy has been sent includes: After the first copy is sent, start the contention resolution window or start the contention resolution timer, select to send the second copy, start the contention resolution window or start the contention resolution timer after the second copy is sent, and stop the contention resolution window or contention resolution timer corresponding to the first copy; If the target request message copy is sent according to the coverage level, after the last duplicate of the last copy is sent, the contention resolution window or the contention resolution timer is started, the second copy is selected to be sent, and after the second copy is sent, the contention resolution window or the contention resolution timer is started, and the contention resolution window or the contention resolution timer corresponding to the first copy is stopped.

19. The method according to any one of claims 10-18, characterized in that, The contention resolution identifier being identical to the user identifier sent by the user equipment specifically includes: The contention resolution identifier is exactly the same as the user identifier sent by the user equipment, or the contention resolution identifier is the same as the first X bits of the user identifier used by the user equipment, where X is an integer greater than 1.

20. A communication method, characterized in that, Applied to a network device that covers a first cell, the method includes: Send configuration information, which enables multiple devices in the first cell to directly perform contention-based MO-EDT data transmission operations; based on the configuration information and the triggering information of the user equipment, enable the user equipment in the first cell to send a target request message; the multiple devices include the user equipment. Receive the target request message, wherein the target request message is a message carrying data of the user equipment, or a message multiplexed with the data; Parse the target request message to obtain the data.

21. The method according to claim 20, characterized in that, The triggering information of the user equipment includes one or more of the following: a request from the upper layer to establish a Radio Resource Control (RRC) connection, support for contention-based MO-EDT, and a received broadcast message carrying target indication information and pre-compensated timing advance, wherein the target indication information indicates that the network device allows the execution of contention-based MO-EDT.

22. The method according to claim 20, characterized in that, The method further includes: Send a broadcast message; The broadcast message carries first indication information, which instructs the network device to allow the user equipment of the first cell to perform user plane-based MO-EDT. And / or the broadcast information carries a second indication information, the second indication information indicating that the network device allows the user equipment to perform a control plane-based MO-EDT.

23. The method according to claim 20, characterized in that, The configuration information includes: configuration information for the device in the first cell to send the target request message, or configuration information for the device in the first cell to send the target request message according to the coverage level.

24. The method according to claim 22, characterized in that, The configuration information for sending the target request message includes one or more of the following: Resource information for sending the target request message, contention resolution window length, contention resolution timer, and number of transmissions for sending the target request message; If the configuration information for sending the target request message is configured according to the coverage level, the configuration information for sending the target request message includes one or more of the following: Resource information for sending the target request message, contention resolution window length, contention resolution timer, number of transmissions of the target request message, and number of repetitions of the target request message.

25. The method according to claim 20, characterized in that, After receiving the target request message, the method further includes: A target response message is sent, which carries a contention resolution identifier, used to identify the device that successfully competed in the first cell.

26. The method according to claim 20, characterized in that, The configuration information also includes diversity slot DSA configuration information, which includes: configuration information for configuring the device in the first cell to send a copy of the target request message, or configuration information for configuring the device in the first cell to send a copy of the target request message according to the coverage level.

27. The method according to claim 26, characterized in that, The configuration information for sending a copy of the target request message includes one or more of the following: resource information for the configuration information of the copy of the target request message, the number of copies, and the mapping relationship between the resources of the copy and the resources of the target request message. If the configuration information for sending the target request message copy is configured according to the coverage level, the configuration information for sending the target request message copy includes one or more of the following: resource information for the configuration information of sending the target request message copy, number of copies, number of duplicate copies, and mapping relationship between the resources for sending copies and the resources for sending the target request message.

28. The method according to claim 26 or 27, characterized in that, The method further includes: Based on the DSA configuration information, a copy of the target request message is received.

29. The method according to any one of claims 24-27, characterized in that, The contention resolution identifier being identical to the user identifier sent by the user equipment specifically includes: The contention resolution identifier is exactly the same as the user identifier sent by the user equipment, or the contention resolution identifier is the same as the first X bits of the user identifier used by the user equipment, where X is an integer greater than 1.

30. A communication device, characterized in that, The communication equipment is applied to a user equipment in a first cell, and includes: The first receiving unit is configured to receive configuration information, which enables multiple devices in the first cell to directly perform contention-based Mobile Caller Advance Data Transmission (MO-EDT) to send data, and the multiple devices include the user equipment. The first sending unit is configured to send a target request message according to the configuration information and the trigger information of the user equipment. The target request message is a message carrying user data of the user equipment, or the target request message is a message multiplexed with the user data. The trigger information is used to determine whether the user equipment can perform a contention-based MO-EDT data transmission operation.

31. A communication device, characterized in that, Applied to network equipment, the network equipment covering a first cell, the communication equipment includes: The second sending unit is used to send configuration information, which enables multiple devices in the first cell to directly perform contention-based MO-EDT data transmission operations; based on the configuration information and the triggering information of the user equipment, the user equipment in the first cell is enabled to send a target request message; the multiple devices include the user equipment. The second receiving unit is configured to receive the target request message, wherein the target request message is a message carrying data of the user equipment, or a message multiplexed with the data; The parsing unit is used to parse the target request message and obtain the data.

32. A user equipment, characterized in that, The user equipment includes a memory and a processor; The memory is used to store the executable program; The processor is used to execute the communication method as described in any one of claims 1-18 based on the executable program stored in the memory.

33. A network device, characterized in that, The network device includes a memory and a processor; The memory is used to store the executable program; The processor is configured to execute the communication method as described in any one of claims 19-29 based on the executable program stored in the memory.

34. A communication system, characterized in that, This includes network equipment and user equipment; The network device performs the communication method as described in any one of claims 19-29, and the user equipment performs the communication method as described in any one of claims 1-18.

35. A computer storage medium for storing a computer program, which, when executed, implements the communication method according to any one of claims 1-29.

Images