Wireless communication method and apparatus, device, chip, and storage medium

Abstract

A wireless communication method and apparatus, a device, a chip, and a storage medium, relating to the technical field of communications. The method comprises: a terminal device receives a first message on the basis of a first RNTI, wherein a plurality of terminal devices reuse the same first message. In the method, a plurality of terminal devices reuse a same first message, thereby being conducive to improving the transmission efficiency of the first message and reducing signaling overhead.

Description

Wireless communication methods, devices, equipment, chips and storage media Technical Field

[0001] This application relates to the field of communication technology, and in particular to a wireless communication method, apparatus, device, chip, and storage medium. Background Technology

[0002] EDT (Early Data Transmission) technology saves device power consumption by transmitting data during random access.

[0003] To reduce uplink and downlink signaling overhead and improve system uplink capacity, plans are underway to further enhance EDT features, such as introducing CB-Msg3 EDT (contention-based-msg3 EDT), which is contention-based direct transmission of Msg3. This scheme skips the Msg1 / Msg2 process and transmits Msg3 directly. Furthermore, for Msg4 or RRC Early Data Complete (RRC) messages, further research is needed to develop efficient transmission schemes to reduce signaling overhead. Summary of the Invention

[0004] This application provides a wireless communication method, apparatus, device, chip, and storage medium. The technical solutions provided by this application are as follows.

[0005] According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being executed by a terminal device, the method comprising:

[0006] A first message is received based on a first RNTI (Radio Network Temporary Identity), wherein multiple terminal devices reuse the same first message.

[0007] According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being performed by a network device, the method comprising:

[0008] A first message is sent based on a first RNTI, wherein multiple terminal devices reuse the same first message.

[0009] According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising:

[0010] The receiving module is used to receive a first message based on a first RNTI, wherein multiple terminal devices reuse the same first message.

[0011] According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising:

[0012] The sending module is used to send a first message based on a first RNTI, wherein multiple terminal devices reuse the same first message.

[0013] According to one aspect of the embodiments of this application, a communication device is provided, the communication device including a processor and a memory, the memory storing a computer program, the processor executing the computer program to implement the wireless communication method on the terminal device side or the wireless communication method on the network device side.

[0014] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, the storage medium storing a computer program, the computer program being executed by a processor to implement the wireless communication method on the terminal device side or the wireless communication method on the network device side described above.

[0015] According to one aspect of the embodiments of this application, a chip is provided, the chip including programmable logic circuits and / or program instructions, which, when the chip is running, are used to implement the wireless communication method on the terminal device side or the wireless communication method on the network device side.

[0016] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, wherein a processor reads from the computer-readable storage medium and executes the computer instructions to implement the wireless communication method on the terminal device side or the wireless communication method on the network device side described above.

[0017] The technical solutions provided in this application embodiment may have the following beneficial effects:

[0018] Reusing the same first message across multiple terminal devices helps improve the transmission efficiency of the first message and reduce signaling overhead. Attached Figure Description

[0019] Figure 1 is a schematic diagram of a network architecture provided in one embodiment of this application;

[0020] Figure 2 is a schematic diagram of a contention-based random access method provided in an embodiment of this application;

[0021] Figure 3 is a schematic diagram of a non-contention-based random access method provided in an embodiment of this application;

[0022] Figure 4 is a flowchart of the EDT under the user plane transport scheme provided in an embodiment of this application;

[0023] Figure 5 is a flowchart of a wireless communication method provided in an embodiment of this application;

[0024] Figure 6 is a schematic diagram of the first message provided in an embodiment of this application;

[0025] Figure 7 is a schematic diagram of the first message provided in another embodiment of this application;

[0026] Figure 8 is a flowchart of a wireless communication method provided in another embodiment of this application;

[0027] Figure 9 is a flowchart of a wireless communication method provided in another embodiment of this application;

[0028] Figure 10 is a flowchart of a wireless communication method provided in another embodiment of this application;

[0029] Figure 11 is a flowchart of a wireless communication method provided in another embodiment of this application;

[0030] Figure 12 is a block diagram of a wireless communication device provided in an embodiment of this application;

[0031] Figure 13 is a block diagram of a wireless communication device provided in another embodiment of this application;

[0032] Figure 14 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0033] Figure 15 is a schematic diagram of the structure of a network device provided in one embodiment of this application. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0035] The network 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.

[0036] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), 5th-Generation (5G) systems, B5G (Beyound 5G) systems, 6th-Generation (6G) systems, or other communication systems.

[0037] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0038] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0039] The communication system in this application embodiment can be applied to unlicensed spectrum, wherein unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, wherein licensed spectrum can also be considered as non-shared spectrum.

[0040] The embodiments of this application can be applied to both non-terrestrial networks (NTN) and terrestrial networks (TN). NTN typically uses satellite communication to provide communication services to terrestrial users. Currently, NTN systems include NR-NTN and IoT-NTN systems, and other NTN systems may be included in the future.

[0041] Please refer to Figure 1, which shows a schematic diagram of a network architecture 100 provided in one embodiment of this application. The network architecture 100 may include: a terminal device 10, an access network device 20, and a core network element 30.

[0042] Terminal device 10 can refer to UE (User Equipment), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent, or user equipment. In some embodiments, terminal device 10 can also be a cellular phone, cordless phone, SIP (Session Initiation Protocol) phone, WLL (Wireless Local Loop) station, PDA (Personal Digital Assistant), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in 5GS (5th Generation System), or terminal device in the future evolved PLMN (Public Land Mobile Network), etc., and this application embodiment is not limited thereto. For ease of description, the devices mentioned above are collectively referred to as terminal devices. The number of terminal devices 10 is usually multiple, and one or more terminal devices 10 can be distributed within the cell managed by each access network device 20. Terminal equipment can also be simply referred to as terminal or UE, the meaning of which can be understood by those skilled in the art.

[0043] Access network device 20 is a device deployed in an access network to provide wireless communication functionality to terminal device 10. Access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the name of the device with access network device functionality may differ; for example, in a 5G NR system, it is called gNodeB or gNB. As communication technologies evolve, the name "access network device" may change. For ease of description, in this embodiment, the aforementioned devices providing wireless communication functionality to terminal device 10 are collectively referred to as access network devices. In some embodiments, a communication relationship can be established between terminal device 10 and core network element 30 through access network device 20. For example, in an LTE (Long Term Evolution) system, access network device 20 may be one or more eNodeBs in an EUTRAN (Evolved Universal Terrestrial Radio Access Network) or EUTRAN; in a 5G NR system, access network device 20 may be one or more gNBs in a RAN (Radio Access Network). In the embodiments of this application, unless otherwise specified, the term "network device" refers to access network device 20, such as a base station.

[0044] Core network element 30 is a network element deployed in the core network. Its main functions are to provide user connectivity, manage users, and bear services, serving as an interface to external networks. For example, core network elements in a 5G NR system may include AMF (Access and Mobility Management Function) entities, UPF (User Plane Function) entities, and SMF (Session Management Function) entities.

[0045] In some embodiments, the access network device 20 and the core network element 30 communicate with each other via some air interface technology, such as the NG interface in a 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via some air interface technology, such as the Uu interface.

[0046] The "5G NR system" in this application embodiment can also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in this application embodiment can be applied to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems (such as B5G (Beyond 5G, a fifth-generation mobile communication technology) systems, 6G systems (6th Generation System, a sixth-generation mobile communication system)), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems. This application does not limit these applications.

[0047] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0048] Before introducing the technical solution of this application, some related technical knowledge involved in this application will be introduced and explained. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0049] 1. LTE Random Access Procedure

[0050] In LTE, the random access process is mainly triggered by the following events (or scenarios):

[0051] 1. Establishing a radio connection during initial UE access: The UE transitions from the RRC (Radio Resource Control)_IDLE state (idle state) to the RRC_CONNECTED state (connected state);

[0052] 2. RRC connection reconstruction process: to enable the UE to rebuild the radio connection after the radio link fails;

[0053] 3. Handover: The UE needs to establish uplink synchronization with the new cell;

[0054] 4. In the RRC_CONNECTED state, DL (DownLink) data arrives, and UL is out of sync at this time;

[0055] 5. In the RRC_CONNECTED state, UL (UpLink) data arrives. At this time, the UL is out of sync or does not have PUCCH resources for sending SR (Scheduling Request).

[0056] 6. SR failed;

[0057] 7. Synchronous reconfiguration request from RRC.

[0058] In LTE, two main random access methods are supported: contention-based random access and contention-free random access. These two methods are applicable to different scenarios. In contention-based random access, the RACH (Random Access Channel) is a resource pool available to the terminal device, and different terminal devices can use the same resources, leading to resource contention. In contention-free random access, specific resources are reserved and allocated to a specific terminal device at a given time.

[0059] Figure 2 illustrates a contention-based random access method, characterized by code resource sharing and a four-step access process, including access request, access response, connection request, and contention resolution (also known as conflict resolution). This process comprises steps Step 1 through Step 4. It is important to note that the interaction messages in each step of the contention-based random access method are referred to as Msg1 through Msg4.

[0060] Step 1: Access Request (Msg1)

[0061] The terminal device selects a PRACH (Physical Random Access Channel) resource (including time-frequency resources and code domain resources) and transmits the selected preamble on the selected PRACH time-frequency resource. Based on the preamble, the network device can estimate the uplink timing and the grant size required for the terminal device to transmit Msg3.

[0062] Step 2: Access Response (Msg2)

[0063] After receiving the preamble from the terminal device, the network device sends a RAR (Random Access Response) to the terminal device. After sending Msg1, the terminal device opens a RAR window and monitors the PDCCH (Physical Downlink Control Channel) scrambled with RA-RNTI (Random Access-Radio Network Temporary Identifier).

[0064] In LTE systems, RA-RNTI is calculated as follows:

[0065] RA-RNTI = 1 + t_id + 10 * f_id

[0066] Where t_id is the index of the first subframe of PRACH transmission (0≤t_id<10), and f_id is the frequency domain index of the corresponding PRACH in that subframe (0≤f_id<6). The PRACH resources are numbered sequentially in the frequency domain from low to high.

[0067] In the NR system, RA-RNTI is calculated as follows:

[0068] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0069] Wherein, s_id is the index of the first OFDM (Orthogonal Frequency Division Multiplexing) symbol of the PRACH timing (0≤s_id≤14), t_id is the index of the first slot of the PRACH timing in the system frame (0≤t_id≤80), f_id is the index of the PRACH timing in the frequency domain (0≤f_id≤8), and ul_carrier_id is the UL (Uplink) carrier used for random access preamble transmission (0 indicates NUL (Normal Uplink) carrier, and 1 indicates SUL (Supplementary Uplink) carrier).

[0070] For eMTC (enhanced Machine-Type Communication) UEs, RA-RNTI is calculated as follows:

[0071] RA-RNTI=1+t_id+10*f_id+60*(SFN_id mod(Wmax / 10))

[0072] Where t_id is the index of the first subframe of PRACH transmission (0≤t_id<10), f_id is the frequency domain index of the corresponding PRACH in that subframe (0≤f_id<6), and PRACH resources are numbered sequentially in the frequency domain from low to high. SFN_id is the index of the first SFN (system frame) of PRACH transmission, and Wmax is the maximum RAR window length supported by eMTC, which is 400 subframes.

[0073] For NB-IoT UEs, RA-RNTI is calculated as follows:

[0074] RA-RNTI=1+floor(SFN_id / 4)+256*carrier_id

[0075] Here, SFN_id is the index of the first SFN transmitted via PRACH, and carrier_id is the index of the UL carrier corresponding to the PRACH transmission. The carrier_id corresponding to the Anchor carrier is 0.

[0076] For NB-IoT UEs in TDD (Time Division Duplexing) mode, RA-RNTI is calculated as follows:

[0077] RA-RNTI=1+floor(SFN_id / 4)+256*(H-SFN mod 2)

[0078] Wherein, SFN_id is the index of the first SFN transmitted by PRACH, and H-SFN is the index of the first H-SFN (superframe) transmitted by PRACH.

[0079] As can be seen from the calculation formula of RA-RNTI above, RA-RNTI is related to the PRACH time and frequency resources used by the terminal device to send Msg1.

[0080] After the terminal device successfully receives the RA-RNTI scrambled PDCCH, it can obtain the PDSCH (Physical Downlink Shared Channel) scheduled by the PDCCH, which contains RAR.

[0081] The RAR subheader contains a BI (Backoff Indicator), which indicates the backoff time for retransmitting Msg1.

[0082] The RAR subheader also contains RAPID (Random Access Preamble ID), which indicates the preamble index received by the network.

[0083] The RAR payload contains a TAC (Timing Advance Command), which is used to adjust the uplink timing.

[0084] The RAR payload also includes a UL grant (uplink grant), used to indicate or schedule uplink resources for the Msg3 transmission. Because the terminal device has not yet established an RRC connection with the network device or performed uplink synchronization, it cannot request uplink grants from the network device for uplink transmission via a Scheduling Request. Instead, it can only send the first uplink message, Msg3 (RRC Setup Request), by including uplink grant information in the RAR message. The UL-Grant field indicates the resources used for uplink transmission. The UL-Grant field is 20 bits long, and Msg3 is actually sent using these resources.

[0085] The RAR payload also includes Temporary C-RNTI, or TC-RNTI (Temporary Cell-RNTI, Temporary Cell-Radio Network Temporary Identifier), which is used to scramble Msg4's PDCCH.

[0086] If the terminal device receives a RA-RNTI scrambled PDCCH and the RAR contains its own preamble index, the terminal considers it to have successfully received the random access response.

[0087] For non-contention-based random access, the random access process ends after the terminal successfully receives Msg2. For contention-based random access, after the terminal device successfully receives Msg2, it still needs to transmit Msg3 and receive Msg4.

[0088] Step 3: Connection Request (Msg3)

[0089] Msg3 is primarily used to inform network devices what event triggered the RACH procedure. For example, if it's an initial access random procedure, Msg3 will carry the UE ID (such as S-TMSI, randomValue) and establishment cause; if it's an RRC reconstruction, it will carry the connected-state UE identifier (such as C-RNTI, PCI, shortMAC-I) and reestablishment cause. Simultaneously, the ID carried in Msg3 allows contention to be resolved in Step 4.

[0090] Step 4: Competition Resolution (Msg4)

[0091] Msg4 has two functions: first, it is used for contention resolution, and second, it is used to transmit RRC configuration messages to the terminal device.

[0092] There are two ways to resolve contention: Method 1: If the terminal device carries a C-RNTI in Msg3, then Msg4 is scheduled using a PDCCH scrambled with the C-RNTI. Method 2: If the terminal device does not carry a C-RNTI in Msg3, such as during initial access, then Msg4 is scheduled using a PDCCH scrambled with the TC-RNTI. Conflict resolution is achieved by the terminal device receiving the PDSCH carrying Msg4 and matching the CCCH (Common Control Channel) SDU (Service Data Unit) in the PDSCH with the contention resolution ID in its own Msg3.

[0093] Figure 3 illustrates a non-contention-based random access method, characterized by exclusive code resources and a three-step access process: preamble allocation, access request, and access response. This process includes the following steps: Step 0 to Step 2. It's important to note that the interaction messages in each step of this non-contention-based random access method are referred to as Msg0 to Msg2, respectively.

[0094] Step 0: Leader assignment (Msg0)

[0095] Network devices assign random access preambles to terminal devices and send them using RRC messages or DCI (Downlink Control Information).

[0096] Step 1: Access Request (Msg1)

[0097] Step 2: Access Response (Msg2)

[0098] For explanations of Msg1 and Msg2, please refer to the above text; they will not be repeated here.

[0099] As can be seen from the above random access process, the main purpose of random access is for the terminal device to achieve uplink synchronization with the cell. During the random access process, the network device can know the time when the terminal device sends the preamble based on the RACH time-frequency resources used by the preamble received from the terminal device. Therefore, it determines the initial TA (Timing Advance) of the terminal device based on the transmission and reception times of the preamble, and informs the terminal through the RAR.

[0100] 2. EDT (Early Data Transmission)

[0101] In traditional LTE systems, if a terminal device in RRC IDLE state needs to transmit uplink data, it must first initiate an RRC connection establishment process through a random access procedure. Only after establishing an RRC connection with the network device can it transmit data. To reduce signaling interactions between the terminal device and the network device during data transmission and to save terminal power consumption, the EDT mechanism is introduced for NB-IoT and eMTC. This feature allows a terminal device in RRC IDLE state to transmit UL data via Msg3 during the random access procedure. Upon receiving a successful reception response from the network device, the random access procedure terminates, and the terminal device remains in RRC IDLE state without entering RRC connected state. The network device configures a separate PRACH resource for EDT. When the amount of UL data to be transmitted by the terminal device does not exceed the data limit configured by the network device, the terminal device can send Msg1 on the separate PRACH resource for EDT to request Msg3 authorization from the network device for EDT. Figure 4.400 shows the flowchart of EDT under the user plane transport scheme. In Figure 4, MME refers to Mobility Management Entity and S-GW refers to Serving Gateway.

[0102] 3. PUR (Preconfigured Uplink Resources)

[0103] To further reduce signaling overhead and terminal power consumption on top of EDT, the PUR feature was introduced for NB-IoT and eMTC. This feature allows the base station to configure PUR resources for the UE while releasing it to RRC IDLE state. The UE can then use these PUR resources for uplink transmission in RRC IDLE state without initiating a random access procedure. When configuring the PUR for the UE, the network can also simultaneously configure a DMRS (Demodulation Reference Signal) cyclic shift, allowing up to two UEs to share the same PUSCH (Physical Uplink Shared Channel) resource (distinguished by the DMRS). By skipping the random access procedure, uplink transmission efficiency and terminal power consumption can be further improved.

[0104] Before performing a PUR transmission, the UE needs to verify the validity of the TA. The validity of the TA is determined based on one or more of the following conditions:

[0105] a) Has the service area changed?

[0106] b) Has the TAT timed out?

[0107] c) Changes in UE RSRP (Reference Signal Receiving Power).

[0108] To reduce uplink and downlink signaling overhead and improve system uplink capacity, IoT NTN plans to further enhance EDT features, such as introducing RACH-less EDT, i.e., direct transmission of Msg3, which transmits Msg3 directly without going through the Msg1 / Msg2 process. The research objectives for this feature are as follows: Study and specify, if beneficial, the following enhancements to reduce the necessary uplink and downlink signaling to complete an EDT transaction [RAN2]: Msg3 transmission without msg1 / RAR; Efficient delivery (reduced overhead) of msg4 / RRC early Data Complete.

[0109] In traditional EDT, the base station allocates PUSCH resources for the initial transmission of Msg3 to the UE via Msg2. In traditional PUR (Preconfigured UL resources), the base station provides PUR configuration information to the UE via an RRC connection release message when releasing the UE to the RRC IDLE state. Regarding PUSCH resources used for Msg3 transmission in RACH-less EDT, RAN2#126 reached the following conclusion: RAN2 focuses the study on contention-based Msg3 transmission to complete an EDT-like transaction (FFS on the details of Msg3, FFS on the procedural steps, e.g., how much we reuse of EDT and PUR procedures, FFS on resource allocation).

[0110] Based on the above conclusions, in RACH-less EDT, if multiple UEs select the same PUSCH resource to transmit Msg3 (i.e., multiple UEs experience Msg3 conflict), the base station can only successfully receive Msg3 from one UE at most. However, in most cases, the base station cannot correctly receive Msg3 from all these conflicting UEs. Thus, UEs that fail to resolve contention need to retry Msg3 transmission. Similarly, for CBRA (contention-based Random Access), for UEs that select the same RO (RACH Occasion) and the same preamble to send Msg1, the success of contention resolution can only be determined after Msg4 is received. UEs that fail to resolve contention need to retry Msg1. Msg3 conflicts in RACH-less EDT and Msg1 conflicts in CBRA waste system PUSCH and PRACH resources and increase the latency for UE data transmission or access, thus affecting user experience.

[0111] Therefore, in order to further improve the system capacity, the following two features have been agreed upon after discussion:

[0112] (1) DSA technology

[0113] In some current satellite communication standards, DSA (Diversity Slotted Aloha) or CRDSA (Contention Resolution Diversity Slotted Aloha) are used to effectively improve the utilization of random access resources and reduce the probability of collisions between different UEs for random access. Taking RACH-less EDT as an example, the basic idea of ​​DSA is that the UE sends multiple Msg3 replicas using different Msg3 transmissions. As long as the base station can successfully receive one of the Msg3s, the UE can consider the EDT to be successful. Therefore, DSA increases the probability of the UE's Msg3 being successfully received by the base station by increasing the opportunities for Msg3 transmission, thereby improving system capacity.

[0114] (2) OCC (Orthogonal Cover Code) technology

[0115] Taking CB-Msg3 based EDT (Contention Based-Msg3 based EDT) as an example, OCC technology is used during Msg3PUSCH transmission, enabling multiple UEs to reuse the same PUSCH time domain resources for transmission, and different UEs are distinguished by OCC.

[0116] Please refer to Figure 5, which shows a flowchart of a wireless communication method provided in one embodiment of this application. This method can be applied to the network architecture shown in Figure 1. The method may include the following step 510.

[0117] Step 510: The terminal device receives the first message based on the first RNTI, wherein multiple terminal devices reuse the same first message.

[0118] In some embodiments, a network device sends a first message based on a first RNTI, wherein multiple terminal devices reuse the same first message.

[0119] In some embodiments, the first message is Msg4. In this application embodiment, the first message is a multi-user multiplexed first message, therefore the first message can be called Multi-UE Msg4.

[0120] In addition, multiple terminal devices reusing the same first message can also be understood as multiple terminal devices sharing the same RNTI (i.e., the first RNTI) to receive the first message, or as the first message including the message content corresponding to multiple terminal devices, such as the Msg4 content.

[0121] In some embodiments, after sending the second message, the terminal device receives the first message based on the first RNTI. The second message is Msg3, and the first message is Multi-UE Msg4.

[0122] Optionally, for CB-msg3 based EDT, the second message is CB-Msg3 and the first message is Multi-UE Msg4.

[0123] Optionally, for traditional EDT, the second message is Msg3 and the first message is Multi-UE Msg4.

[0124] Optionally, when the terminal device uses DSA technology to send a second message, the terminal device will send multiple second messages, which are also referred to as multiple copies of the second message. For example, when the terminal device uses DSA technology to send CB-Msg3, the terminal device will send multiple identical CB-Msg3s, which are also referred to as multiple copies of CB-Msg3.

[0125] Optionally, the second message carries uplink data. Optionally, in an EDT scenario, the second message carries the EDT's uplink data. For example, for a CB-Msg3 based EDT, the second message is CB-Msg3, and CB-Msg3 carries the EDT's uplink data. For example, for a traditional EDT, the second message is Msg3, and Msg3 carries the EDT's uplink data.

[0126] In some embodiments, the first RNTI is used to receive the first PDCCH and / or the first PDSCH, the first PDCCH is used to schedule the reception of the first message, and the first PDSCH is used to carry the first message. Wherein, the first RNTI is used to receive the first PDCCH, which can be understood as the first PDCCH being scrambled using the first RNTI; the network device scrambles the first PDCCH using the first RNTI when sending it, and the terminal device descrambles it using the first RNTI when receiving it. The first RNTI is also used to receive the first PDSCH, which can be understood as the first PDSCH being scrambled using the first RNTI; the network device scrambles the first PDSCH using the first RNTI when sending it, and the terminal device descrambles it using the first RNTI when receiving it.

[0127] When the first RNTI is used to receive the first PDCCH, the network device sends the first PDCCH based on the first RNTI. The above step 510 is: the terminal device receives the first PDCCH based on the first RNTI. The first PDCCH is used to schedule the reception of the first message, wherein multiple terminal devices reuse the same first message.

[0128] When the first RNTI is used to receive the first PDSCH, the network device sends the first PDSCH based on the first RNTI. The above step 510 is: the terminal device receives the first PDSCH based on the first RNTI. The first PDSCH is used to carry the first message, wherein multiple terminal devices reuse the same first message.

[0129] When the first RNTI is used to receive the first PDCCH and the first PDSCH, the network device sends the first PDCCH and the first PDSCH based on the first RNTI. The above step 510 is as follows: the terminal device receives the first PDCCH based on the first RNTI, and the first PDCCH is used to schedule the reception of the first message; the terminal device receives the first PDSCH based on the first RNTI, and the first PDSCH is used to carry the first message; wherein, multiple terminal devices reuse the same first message.

[0130] In the prior art, one first message (such as Msg4) corresponds to one terminal device. Unlike the prior art, in this embodiment, multiple terminal devices reuse the same first message (such as Multi-UE Msg4). This single first message includes feedback information from the network device regarding second messages (such as Msg3 or CB-Msg3) sent to the multiple terminal devices.

[0131] In some embodiments, the first message is used for contention resolution and / or to schedule the retransmission of the second message. The terminal device, based on the received first message, either resolves the contention or retransmits the second message. Details of this process can be found in the descriptions in the embodiments below.

[0132] The technical solution provided in this application embodiment helps to improve the transmission efficiency of the first message and reduce signaling overhead by reusing the same first message by multiple terminal devices.

[0133] This application provides a scheme for how a terminal device receives a multi-user multiplexed first message when multiple terminal devices reuse the same first message. The terminal device receives the first message based on a determined first RNTI. The method for determining the first RNTI is described below.

[0134] In some embodiments, the first RNTI is determined based on first resource information, which is related to the second message sent by the terminal device. For example, the first resource information is related to the transmission resources corresponding to the second message sent by the terminal device, and the transmission resources include at least one of time-domain resources, frequency-domain resources, and code-domain resources. For example, the first resource information is related to the transmission resources used by the terminal device to send the second message.

[0135] In some embodiments, the first resource information includes at least one of the following:

[0136] (1) Index of the time-domain resource corresponding to the second message;

[0137] (2) Index of the frequency domain resources corresponding to the second message;

[0138] (3) Index of the code field resource corresponding to the second message;

[0139] (4) First timer, the first timer is a timer started by the terminal device in response to sending the second message;

[0140] (5) First cycle, the first cycle is the cycle of the transmission resources used to transmit the second message.

[0141] Regarding (1) above, the temporal resource corresponding to the second message can be understood as the temporal resource used to transmit the second message. The index of the temporal resource is used to indicate the location of the temporal resource, and different temporal resources can be distinguished by different indices. For example, the index of the temporal resource can be subframe id, SFN id, H-SFN id, etc. Optionally, in the case of temporal repetition of the second message, the index of the temporal resource corresponding to the second message can be: the index of the first temporal resource corresponding to the PUSCH transmission carrying the second message.

[0142] Regarding (2) above, the frequency domain resources corresponding to the second message can be understood as the frequency domain resources used to transmit the second message. The index of the frequency domain resources is used to indicate the location of the frequency domain resources, and different frequency domain resources can be distinguished by different indexes. For example, the index of the frequency domain resources can be a subcarrier index, a carrier index, a PRB (Physical Resource Block) index, etc. Optionally, the indexes of the frequency domain resources are numbered sequentially in ascending order of frequency domain. If the transmission of the second message occupies multiple consecutive frequency domain resources at the same time, the index of the frequency domain resources corresponding to the second message can be: the index of the resource with the lowest or highest frequency domain position among the frequency domain resources occupied by this transmission.

[0143] Regarding (3) above, the code domain resource corresponding to the second message can be understood as the code domain resource used to transmit the second message. The index of the code domain resource is used to indicate the location of the code domain resource, and different code domain resources can be distinguished by different indices. For example, the index of the code domain resource can be the OCC index, which is the OCC index used for the transmission of the second message. The OCC can be numbered based on certain rules, or the index (or number) corresponding to each OCC can be determined by network configuration.

[0144] Regarding (4) above, the first timer is a timer started by the terminal device in response to sending the second message. During the operation of the first timer, the terminal device listens for the first PDCCH indicating retransmission of the second message or feedback from the network device. Optionally, the time to start the first timer is the time when the second message is sent, or the time after the time when the second message is sent, after a first duration. Wherein, the first time is configured by the network device, or pre-configured, or specified by the standard, or depends on the implementation of the terminal device; or, the first duration is determined based on the round-trip delay between the terminal device and the network device; or, the first duration is determined based on the round-trip delay and processing time between the terminal device and the network device, wherein the processing time is configured by the network device, or pre-configured, or specified by the standard, or depends on the implementation of the terminal device. Optionally, the first timer is a mac-ContentionResolutionTimer. Optionally, the first resource information includes the duration of the first timer. The duration of the first timer can be denoted as T_length, where T_length is the maximum length supported by the first timer (configurable by the network device), or the actual length configured by the network device.

[0145] Regarding (5) above, the first period can also be called the SPS (Semi-Persistent Scheduling) period, which can be represented by T_SPS. T_SPS is the minimum period (configurable by the network device) that the transmission resources for transmitting the second message can support, or the period actually configured by the network device.

[0146] In some embodiments, the first resource information is a subset of the second resource information, which is used to determine the second RNTI.

[0147] In some embodiments, the second RNTI is the RNTI used by the terminal device to send the second message.

[0148] In some embodiments, the second resource information used to determine the second RNTI includes at least one of the following:

[0149] (1) Index of the time-domain resource corresponding to the second message;

[0150] (2) Index of the frequency domain resources corresponding to the second message;

[0151] (3) Index of the code field resource corresponding to the second message;

[0152] (4) First timer, the first timer is a timer started by the terminal device in response to sending the second message;

[0153] (5) First cycle, the first cycle is the cycle of the transmission resources used to transmit the second message.

[0154] For example, the terminal device determines the second RNTI based on the time-domain resources and frequency-domain resources used to send the second message. That is, the second RNTI = f(time index, freq index), where the time index represents the index of the time-domain resources used to send the second message, and the freq index represents the index of the frequency-domain resources used to send the second message.

[0155] For example:

[0156] The second RNTI = N0 + K1*s_id + K2*f_id; or,

[0157] The second RNTI = N0 + K1*s_id + K2*f_id + K3*(SFN_id mod(T_length / 10)); or,

[0158] Second RNTI=N0+K1*s_id+K2*f_id+K3*(SFN_id mod(T_length / 10))+K4*(H-SFN mod M);

[0159] Where N0, K1, K2, K3, and K4 are predefined values; s_id is the first subframe ID occupied by the PUSCH transmission of the second message; SFN_id is the first SFN ID occupied by the PUSCH transmission of the second message; f_id is the index of the lowest or highest PRB or subcarrier in the frequency domain occupied by the PUSCH transmission of the second message; T_length is in subframe or ms. H-SFN is the first H-SFN ID occupied by the PUSCH transmission of the second message, M = ceiling(T_length / 10240). ceiling represents rounding up, and mod represents modulo operation.

[0160] For example, the terminal device determines the second RNTI based on the time-domain resources, frequency-domain resources, and code-domain resources used to send the second message. That is, the second RNTI = f(time index, freq index, OCC index), where the time index represents the index of the time-domain resources used to send the second message, the freq index represents the index of the frequency-domain resources used to send the second message, and the OCC index represents the index of the OCC used to send the second message.

[0161] For example:

[0162] Second RNTI=f(time index, freq index)+Kx*OCC_index;

[0163] Where f(time index, freq index) can be found in the example above, and Kx is a predefined value.

[0164] For example, if the first resource information is a subset of the second resource information, and the second resource information includes the index of the time-domain resource corresponding to the second message and the index of the frequency-domain resource corresponding to the second message, then the first resource information includes the index of the time-domain resource corresponding to the second message, or the first resource information includes the index of the frequency-domain resource corresponding to the second message.

[0165] For example, if the second RNTI = f(time index, freq index), then the first RNTI = f(time index), or the first RNTI = f(freq index).

[0166] For example, if the first resource information is a subset of the second resource information, and the second resource information includes the index of the time domain resource corresponding to the second message, the index of the frequency domain resource corresponding to the second message, and the index of the code domain resource corresponding to the second message, then the first resource information includes any one or two of the following: the index of the time domain resource corresponding to the second message, the index of the frequency domain resource corresponding to the second message, and the index of the code domain resource corresponding to the second message.

[0167] For example, if the second RNTI = f(time index, freq index, OCC index), then the first RNTI = f(time index, freq index), or the first RNTI = f(freq index, OCC index), or the first RNTI = f(time index, OCC index).

[0168] In some embodiments, there may be multiple time indexes and / or frequency indexes. For example, a time index may include a subframe id, an SFN id, and an H-SFN id; while a frequency index may include a subcarrier index, a carrier index, and a PRB index. In one implementation, if it is determined that the second resource information used by the second RNTI includes multiple time-domain resource indices and / or multiple frequency-domain resource indices, then it is determined that the first resource information used by the first RNTI includes a portion of the multiple time-domain resource indices and / or a portion of the multiple frequency-domain resource indices.

[0169] For example, if the second RNTI = f(time index_1, time index_2, freq index_1, freq index_2, freq index_3), then the first RNTI = f(time index_1, freq index_1, freq index_2).

[0170] For example, the second RNTI = N0 + K1*s_id + K2*f_id + K3*OCC_index, and the first RNTI = N0 + K1*s_id + K2*f_id. Thus, the first RNTI of terminal devices from different OCCs may be common.

[0171] For example, the second RNTI = N0 + K1*s_id + K2*f_id + K3*(SFN_id mod(T_length / 10)), and the first RNTI = N0 + K1*s_id + K3*(SFN_id mod(T_length / 10)). Thus, the first RNTI at different frequency domain locations may be common.

[0172] For example, the second RNTI = N0 + K1*s_id + K2*f_id + K3*(SFN_id mod(T_length / 10)), and the first RNTI = N0 + K2*f_id + K3*(SFN_id mod(T_length / 10)). Thus, the first RNTI at different subframe positions may be common.

[0173] Thus, since there is more information / factors available to determine the second RNTI, multiple terminal devices can determine different second RNTIs based on different dimensions of information / factors of the transmission resources selected for transmitting the second message. However, since there is less information / factors for their first RNTIs, it is possible that multiple terminal devices select the same transmission resource information / factors for transmitting the second message, and therefore the first RNTIs determined are the same.

[0174] In some embodiments, the first RNTI and the second RNTI are the same.

[0175] For example, the second RNTI = f(time index, freq index) does not take the code domain OCC into account. Multiple terminal devices transmit CB-Msg3 using different OCCs on the same time-frequency resources. These multiple terminal devices transmit CB-Msg3 based on the same second RNTI. The network device distinguishes multiple terminal devices with the same second RNTI from the code domain through the OCC.

[0176] The first RNTI is equal to the second RNTI. The terminal device uses the first RNTI to receive the first message. Since the second RNTI is multi-user multiplexed, even if the first RNTI is equal to the second RNTI, the first message is still multi-user multiplexed. In some embodiments, the first RNTI is determined based on a quantity N, where N is an integer greater than 1.

[0177] In one possible scenario, the number N represents the number of terminal devices that reuse the same first message. For example, if N terminal devices reuse the same first message, these N terminal devices share the same RNTI (i.e., the first RNTI) to receive the first message, and the first message includes the message content corresponding to these N terminal devices.

[0178] In another possible scenario, the number N represents the number of second RNTIs that reuse the same first RNTI. For example, in a DSA scenario, a terminal device sends multiple copies of the second message at different transmission times, and because of these different transmission times, the second RNTIs are also different.

[0179] In some embodiments, the first RNTI is determined based on the quantity N and the second RNTI described above. Optionally, the second RNTI may be determined based on the second resource information described above, or the second RNTI may be indicated by the network device. Exemplarily, the second RNTI is the TC-RNTI indicated by the network device in the RAR (i.e., Msg2).

[0180] For example, the first RNTI = Floor[Second RNTI / N], where Floor represents rounding down, and N represents the number of terminal devices reusing the same first message, or the number of second RNTIs reusing the same first RNTI. The value of N can be configured by the network device. Alternatively, the first RNTI = ceiling[Second RNTI / N], where ceiling represents rounding up, and N represents the number of terminal devices reusing the same first message, or the number of second RNTIs reusing the same first RNTI. The value of N can be configured by the network device. In this way, the first RNTI is common to every N consecutive second RNTIs.

[0181] When the second RNTI is determined based on the second resource information, and multiple different terminal devices select different transmission resources to transmit the second message, although the second RNTIs are different, the first RNTI may be common. Conversely, when the second RNTI is indicated by the network device, although the second RNTIs of different terminal devices are different, the first RNTI may be common. In this way, the network device can send the feedback information from these terminal devices in a single first message, and these terminal devices can collectively receive this multi-user multiplexed first message through the first RNTI.

[0182] The following section describes the content of the first message used by multiple users.

[0183] In some embodiments, the first message includes M sub-messages, where M is a positive integer. Optionally, the first message may include multiple sub-messages.

[0184] In some embodiments, for each sub-message, the sub-message is used to indicate that the contention conflict has been successfully resolved; or, the sub-message is used to schedule the retransmission of the second message.

[0185] Optionally, each sub-message includes at least one of the following: a MAC layer message (such as a MAC CE), an RRC message, or downlink data. The MAC layer message may be a Contention Resolution MAC CE, used to indicate whether contention resolution was successful. For example, if the Contention Resolution Identity indicated by the Contention Resolution MAC CE matches the CCCH SDU carried in the second message sent by the terminal device, the contention resolution is successful; otherwise, the contention resolution fails. If the contention resolution is successful, the terminal device further reads the RRC message and / or downlink data. The RRC message may be an RRCEarlyDataComplete message, an RRCConnectionRelease message, etc. Additionally, when a sub-message is used to schedule the retransmission of the second message, the sub-message may include a MAC layer message (such as a MAC CE), which is used to schedule the retransmission of the second message corresponding to that sub-message.

[0186] The above M sub-messages belonging to the same first message can have the following two possible scenarios.

[0187] Case 1: There is a one-to-one correspondence between M sub-messages and M terminal devices.

[0188] Scenario 2: There is a one-to-one correspondence between M sub-messages and M second RNTIs, or a one-to-one correspondence between M sub-messages and M transmission opportunities. The M second RNTIs include the RNTI used by the terminal device to send the second message. The transmission opportunities are used to send the second message.

[0189] When the terminal device sends the second message using SA (Standalone), or when the terminal device does not send the second message using DSA (Distributed Subsystem for Administration), Cases 1 and 2 above are equivalent. For example, consider three terminal devices: terminal device #1, terminal device #2, and terminal device #3. Each of these three terminal devices sends a second message to the network device. Terminal device #1 sends second message #1, which is scrambled using second RNTI #1. Terminal device #2 sends second message #2, which is scrambled using second RNTI #2. Terminal device #3 sends second message #3, which is scrambled using second RNTI #3. In this case, the three terminal devices correspond to three second RNTIs, and Cases 1 and 2 above are equivalent.

[0190] When a terminal device uses DSA to send a second message, there is a difference between Case 1 and Case 2 above. For example, a terminal device sends multiple copies of the second message at different transmission times. Due to the different transmission times, the second RNTI is also different. However, the content of the multiple copies of the second message of the terminal device is actually consistent, so the content of the response message (i.e., the first message) for any copy of the second message of the same terminal device is also consistent. The terminal device can complete the contention-based first message sending process, such as the CB-Msg3 EDT process, by receiving any first message. For example, for a terminal device #1, suppose it sends three copies of the second message at three different transmission times, denoted as copy #1-1, copy #1-2, and copy #1-3. Since the transmission times of these three copies of the second message are different, the second RNTI used for scrambling is also different. Suppose that copy #1-1 is scrambled using second RNTI #1-1, copy #1-2 is scrambled using second RNTI #1-2, and copy #1-3 is scrambled using second RNTI #1-3. In this scenario, for case 1 above, the network device only sends back one sub-message for terminal device #1, without needing to send a separate sub-message for each different second message copy. For case 2 above, for terminal device #1, since it sent three second message copies using three different second RNTIs, the network device sends back three sub-messages for terminal device #1, and these three sub-messages correspond one-to-one with the three second RNTIs (or three second message copies).

[0191] For multiple copies of the second message sent by the same terminal device, if the first RNTI of the multiple copies of the second message is the same, then the response message (i.e. the first message) of these copies of the second message can be carried by the same first message. We can call this first message the first message of multi-user multiplexing.

[0192] According to scenario 2, the first message of the multi-user multiplexing needs to contain multiple sub-messages, each sub-message corresponding to a second RNTI or transmission timing, even if they are the same or duplicate sub-messages.

[0193] Based on scenario 1, it is sufficient to include only one sub-message corresponding to the terminal device in the first message of the multi-user multiplexing, which helps to save signaling overhead.

[0194] Since both the second RNTI and the first RNTI are determined based on the transmission timing selected by the terminal device, and both the terminal device and the network device determine the second RNTI and the first RNTI according to predefined calculation formulas, the network device and the terminal device have a consistent understanding of the correlation between the second RNTI, the first RNTI, and the transmission timing selected by the terminal device, and there will be no inconsistencies in their understanding. Furthermore, by sending sub-messages corresponding to multiple terminal devices within the same first message, information transmission efficiency is improved.

[0195] In some embodiments, when a sub-message is used to indicate successful contention resolution, for case 1, if M sub-messages correspond one-to-one with M terminal devices, it can be understood that the sub-message is used to indicate that the contention conflict of the terminal device corresponding to the sub-message has been successfully resolved, or it can also be understood that the sub-message is used to indicate that the contention conflict of the second message sent by the terminal device corresponding to the sub-message has been successfully resolved; for case 2, if M sub-messages correspond one-to-one with M second RNTIs, or M sub-messages correspond one-to-one with M transmission opportunities, it can be understood that the sub-message is used to indicate that the contention conflict of the second message scrambled by the second RNTI corresponding to the sub-message has been successfully resolved, or the contention conflict of the second message sent by the transmission opportunity corresponding to the sub-message has been successfully resolved.

[0196] In some embodiments, when a sub-message is used to schedule the retransmission of a second message, for case 1, if M sub-messages correspond one-to-one with M terminal devices, it can be understood that the sub-message is used to schedule the retransmission of the second message sent by the terminal device corresponding to the sub-message; for case 2, if M sub-messages correspond one-to-one with M second RNTIs, or M sub-messages correspond one-to-one with M transmission opportunities, it can be understood that the sub-message is used to schedule the retransmission of the second message scrambled by the second RNTI corresponding to the sub-message, or the retransmission of the second message sent by the transmission opportunity corresponding to the sub-message.

[0197] In some embodiments, the first message further includes index information corresponding to M sub-messages, wherein the index information corresponding to the sub-messages is used to indicate the terminal device, the second RNTI, or the transmission timing corresponding to the sub-message. This index information can indicate the association between multiple sub-messages that reuse the same first message transmission and the terminal device, the second RNTI, or the transmission timing.

[0198] Optionally, the index information corresponding to the sub-message includes first index information, which determines whether the second RNTI is used and whether the first RNTI is not used. Optionally, the index information corresponding to the sub-message is carried by a MAC CE (Media Access Control Element).

[0199] For example, the first RNTI = Floor[second RNTI / N]. Thus, the above index information is the second RNTI mod N.

[0200] For example, the second RNTI = N0 + K1*s_id + K2*f_id + K3*OCC_index, and the first RNTI = N0 + K1*s_id + K2*f_id. Thus, the index information mentioned above is OCC_index.

[0201] For example, the second RNTI = N0 + K1*s_id + K2*f_id + K3*(SFN_id mod(T_length / 10)), and the first RNTI = N0 + K1*s_id + K3*(SFN_id mod(T_length / 10)). Thus, the above index information is the index of the frequency domain resource, i.e., f_id.

[0202] For example, the second RNTI = N0 + K1 * s_id + K2 * f_id + K3 * (SFN_id mod(T_length / 10)), and the first RNTI = N0 + K2 * f_id + K3 * (SFN_id mod(T_length / 10)). Thus, the above index information is the subframe index, i.e., s_id.

[0203] Based on the additional index information, the terminal device can determine which sub-message in the first message of multi-user multiplexing is the one it needs to identify. For example, it can determine which contention resolution MAC CE in Multi-UE Msg4 is the one it needs to identify and execute. If the contention resolution is successful, it can then proceed to read RRC messages and / or downlink data.

[0204] In some embodiments, the first message is sent in the form of a MAC PDU (Protocol Data Unit). The index information corresponding to the M sub-messages included in the first message can be located at the very beginning of the MAC PDU. Optionally, the index information corresponding to the M sub-messages is represented in the form of a bitmap. As shown in Figure 6, the first message includes M = 3 sub-messages, denoted as sub-message 1, sub-message 3, and sub-message 4. N = 8 indicates that the number of terminal devices multiplexing the same first message is 8. The sub-message index information (including the index information corresponding to the M sub-messages) is located at the very beginning of the MAC PDU.

[0205] In Figure 6, the sub-message index information is represented by an 8-bit bitmap, used to indicate whether a sub-message corresponding to each of the N terminal devices exists. Here it is 10110000, indicating that among the 8 terminal devices, sub-message 1 corresponding to terminal device #1, sub-message 3 corresponding to terminal device #3, and sub-message 4 corresponding to terminal device #4 exist.

[0206] Optionally, the first message may also include length information or start position information corresponding to each of the M sub-messages. The length information of each sub-message indicates its length, such as the number of bits or bytes it contains. The start position information of each sub-message indicates its starting position within the first message, or it can be understood as the position of the first bit or first byte of the sub-message within the first message.

[0207] Optionally, the sub-message index information includes index information corresponding to each of the M sub-messages, and length information or start position information corresponding to each of the M sub-messages. Optionally, the sub-message index information is located at the very beginning of the MAC PDU.

[0208] As shown in Figure 6, the sub-message index information also includes the length information or starting position of each of the three existing sub-messages. The length information or starting position information for sub-message 1 indicates the length or starting position of sub-message 1. The length information or starting position information for sub-message 2 indicates the length or starting position of sub-message 2. The length information or starting position information for sub-message 3 indicates the length or starting position of sub-message 3.

[0209] By placing the sub-message index information at the very beginning of the MAC PDU, the terminal device can directly read the sub-message index information from the very beginning after receiving the MAC PDU. Then, based on the index information and length information (or start position information) of each sub-message contained therein, it can directly find the sub-message that the terminal device needs to read, without having to traverse every sub-message, which helps to reduce terminal complexity.

[0210] In some embodiments, the first message includes M sub-messages, where N represents the number of terminal devices that reuse the same first message, and M is less than or equal to N.

[0211] As introduced above, sub-messages can include two types. One type is used to indicate successful contention resolution when the second message is successfully received. It includes at least one of MAC layer messages (such as MAC CE), RRC messages, and downlink data. The other type is used to schedule the retransmission of the second message when the second message is not successfully received. It only includes MAC layer messages (such as MAC CE) and is used for the retransmission scheduling of the second message that was not successfully received.

[0212] When a sub-message is used to indicate successful contention resolution, the MAC layer message (such as MAC CE) within that sub-message is similar to "successRAR" for 2-step RACH MsgB, used for contention resolution after Msg3 success, and carries the following information:

[0213] (1) CCCH SDU / UE Contention Resolution Identity, used for contention conflict resolution;

[0214] (2) C-RNTI (Cell-RNTI, Cell-Radio Network Temporary Identifier): If the sub-message does not carry an RRC message (such as RRCEarlyDataComplete message or RRCConnectionRelease message), the terminal device needs to continue listening to the PDCCH to receive subsequent RRC messages. This C-RNTI is used.

[0215] (3) An indication exists in the RRC message or downlink data, indicating that it carries an RRC message (such as the RRCEarlyDataComplete message or the RRCConnectionRelease message) and / or downlink data.

[0216] In addition, when a sub-message is used to indicate that a contention conflict has been successfully resolved, the information carried by the MAC layer message contained in the sub-message can be in the MAC subheader or the MAC payload, and this application does not limit this.

[0217] When a sub-message is used to schedule the retransmission of the second message, the MAC layer message (such as MAC CE) in this sub-message is similar to the "fallbackRAR" used for 2-step RACH MsgB, used for scheduling Msg3 retransmissions when Msg3 reception fails. There are two possible implementations:

[0218] (1) It can carry a BI (Backoff Indicator) similar to Msg2 RAR in the prior art, so that Msg3 retransmission is still CB-Msg3, and the terminal device still needs to use CB-Msg3 resources to retransmit Msg3 based on contention.

[0219] The Backoff Point (BI) reflects the current load of contention for resources in the cell and indicates the waiting time for the terminal device to attempt its next attempt. When the terminal device receives the BI, it calculates the specific waiting time based on the BI value and a scaling factor (SCALING_FACTOR_BI) configured in the network. Specifically, the terminal device sets PREMBLE_BACKOFF to equal BI multiplied by SCALING_FACTOR_BI, and then selects a random value as the backoff time (i.e., the waiting time) from a random range evenly distributed between 0 and PREMBLE_BACKOFF.

[0220] (2) It can also carry a UL grant (uplink grant) similar to Msg2 RAR, so that Msg3 retransmission is scheduled using traditional dynamically scheduled Msg3 retransmission resources. In addition to the UL grant, it may also include TAC and / or TC-RNTI.

[0221] The above two Msg3 retransmission scheduling instructions are indicated through the MAC layer, which is different from the Msg3 retransmission scheduling indicated by PDCCH (DCI).

[0222] In addition, when a sub-message is used to schedule the retransmission of the second message, the information carried by the MAC layer message contained in the sub-message can also be in the MAC subheader or MAC payload, and this application does not limit this.

[0223] Alternatively, when a sub-message is used to schedule the retransmission of a second message, the sub-message must also allow different terminal devices to distinguish whether the sub-message is specific to them; therefore, it needs to indicate the index information corresponding to the sub-message. However, when a sub-message is used to indicate successful contention resolution, the index information corresponding to the sub-message may not be required because the CCCH SDU / UE Contention Resolution Identity allows the terminal device to determine whether the sub-message is specific to it.

[0224] Based on this, the embodiments of this application provide the following possible implementation methods:

[0225] Implementation method 1-1: This implementation method is the sub-message index information located at the very beginning of the MAC PDU, as mentioned above. It can be in the form of a bitmap. The association relationship is already carried in the sub-message index information located at the very beginning of the MAC PDU. In this way, each sub-message used to schedule the retransmission of the second message does not need additional indication. It can also be combined with the length information to allow the terminal device to read only its own related sub-messages.

[0226] Implementation Method 1-2: In the absence of sub-message index information at the very beginning of the MAC PDU as described above, alternatively, for each sub-message used to schedule the retransmission of the second message, the index information is carried within that sub-message (instead of being outside the sub-message and at the very beginning of all sub-messages). For example, the sub-message could contain BI + index information, or UL grant + index information. The advantage of this is that the index information only needs to be indicated for the sub-message used to schedule the retransmission of the second message. However, in extreme cases, the terminal device may need to read the first message from beginning to end.

[0227] Alternatively, when a sub-message is used to schedule the retransmission of a second message, the sub-message may not distinguish between different terminal devices or second RNTIs or transmission opportunities, and therefore does not need to indicate the index information corresponding to the sub-message.

[0228] Based on this, the embodiments of this application provide a possible implementation:

[0229] Implementation Method 2: In this method, without the sub-message index information located at the very beginning of the MAC PDU as described above, the sub-message used to schedule the second message retransmission may not be associated with a specific terminal device, second RNTI, or transmission opportunity. That is, the sub-message used to schedule the second message retransmission does not distinguish between different terminal devices, second RNTIs, or transmission opportunities. For example, the sub-message may contain a BI or UL grant without carrying index information. In this way, the sub-message used to schedule the second message retransmission is for multiple terminal devices, second RNTIs, or transmission opportunities. The terminal device checks all sub-messages included in the first message. If it determines that contention resolution is unsuccessful, it reads the content of the sub-message used to schedule the second message retransmission and executes the second message retransmission. In this case, there can be exactly one sub-message used to schedule the second message retransmission; that is, all terminal devices that failed to resolve the contention share this same sub-message used to schedule the second message retransmission.

[0230] Assuming M=3, N=8, the first message includes 3 sub-messages, and the number of terminal devices reusing the same first message is 8. As shown in Figure 7, which exemplarily illustrates a schematic diagram of the first message, the first message includes: sub-message index information (optional), and 3 sub-messages including sub-message 1, sub-message 3, and sub-message 4.

[0231] Each MAC subPDU consists of a MAC subheader and / or a MAC payload. The information carried by the MAC layer message in the sub-message can be in the subheader or the payload, and this application does not limit this.

[0232] Sub-message 1 is a sub-message used to schedule the retransmission of the second message, and can also be understood as a sub-message that Msg3 was not successfully received.

[0233] In this example, if the terminal device selects an OCC based on the OCC resource pool to send the second message, and the second RNTI of the second message is equal to f(time, freq), and the first RNTI of the first message is equal to the second RNTI of the second message, then the sub-message index information is actually the OCC index. The terminal device knows which OCC it is using, so it can confirm that the sub-message used to schedule the retransmission of the second message is its own. As mentioned earlier, the OCC index can be at the very beginning of the first message, as in implementation 1-1; it can also be only in sub-message 1, as in implementation 1-2; or it can be omitted, as in implementation 2.

[0234] Sub-message 3 is a sub-message used to indicate that the contention conflict has been successfully resolved. It can also be understood as a sub-message that Msg3 has been successfully received. It contains only MAC layer messages, but does not carry DL data or RRC messages (such as RRCEarlyDataComplete message or RRCConnectionRelease message).

[0235] Sub-message 4 is a sub-message used to indicate that the contention conflict has been successfully resolved. It can also be understood as a sub-message that Msg3 has been successfully received. It includes the MAC layer message successRAR, as well as DL data and / or RRC messages (such as RRCEarlyDataComplete message and RRCConnectionRelease message), and is carried by one or more subsequent MAC subPDUs (MAC SDUs).

[0236] In some embodiments, when the first PDCCH is used to schedule the retransmission of the second message, the information carried by the first PDCCH includes the aforementioned index information.

[0237] If the terminal device receives a first PDCCH scrambled with a first RNTI, and the first PDCCH indicates that the second message should be retransmitted, the terminal device decides whether to retransmit the second message based on the index information carried in the first PDCCH. For example, if the index information carried in the first PDCCH corresponds to the second RNTI or the transmission timing used by the terminal device when sending the second message, the terminal device decides to retransmit the second message; otherwise, the terminal device decides not to retransmit the second message.

[0238] For example, taking the second RNTI as TC-RNTI, the terminal device determines the TC-RNTI corresponding to the Msg3 retransmission indication based on the index information carried in the first PDCCH. If the TC-RNTI is consistent with the TC-RNTI indicated in Msg2, the terminal device performs Msg3 retransmission on the PUSCH resource indicated by the first PDCCH.

[0239] The following describes how the terminal device resolves contention conflicts after receiving the first message from the multi-user multiplexing service.

[0240] In some embodiments, as shown in FIG8, step 510 is followed by step 520.

[0241] Step 520: If the first message includes a first sub-message, the terminal device determines that the contention resolution was successful; wherein the contention resolution identifier indicated in the first sub-message matches the CCCH SDU carried in the second message sent by the terminal device.

[0242] In some embodiments, the first message includes M sub-messages, where M is a positive integer. The first sub-message is a sub-message determined from the M sub-messages based on the index information corresponding to each of the M sub-messages. The index information corresponding to the sub-message is used to indicate the terminal device, the second RNTI, or the transmission timing corresponding to the sub-message.

[0243] In extreme cases, if the index information corresponding to each sub-message is not included in the first message, the terminal device needs to check all the sub-messages included in the first message in order to determine that the contention has been resolved successfully.

[0244] However, if the first message includes index information corresponding to each sub-message, after receiving the first message, the terminal device can find the sub-message related to itself from multiple sub-messages based on itself or the second RNTI or transmission timing used to send the second message. The terminal device can determine whether the competition has been successfully resolved based on the sub-message related to itself, without needing to check all the sub-messages included in the first message. This helps to reduce the complexity of the terminal device.

[0245] The following describes the configuration process for the transmission resources of the second message.

[0246] In some embodiments, as shown in FIG9, at least one of the following steps 502 to 506 is included before step 510.

[0247] Step 502: The terminal device receives first configuration information, which is used to configure the transmission resources of the second message, and the second message carries uplink data.

[0248] In some embodiments, the second message carries uplink data of the EDT.

[0249] In some embodiments, the network device sends first configuration information, and the terminal device receives the first configuration information sent by the network device. Optionally, the first configuration information is carried in a broadcast message. For example, the broadcast message may be a system message, such as any one of MIB (Master Information Block), SIB1 (System Information Block), and SIBx.

[0250] In some embodiments, when the second message is CB-Msg3, the network device configures the Msg3 PUSCH transmission resources for CB-Msg3EDT using the first configuration information.

[0251] In some embodiments, the first configuration information is used to determine at least one of the following:

[0252] (1) At least one resource pool, wherein the transmission resources in the resource pool are used to transmit the second message;

[0253] (2) At least one SA or DSA configuration corresponding to each coverage enhancement level;

[0254] (3) Power control parameters for the second message;

[0255] (4) Second configuration information, used to receive the first message;

[0256] (5) TA verification parameters.

[0257] Regarding (1) above, the resource pool can be a time-frequency resource pool or a time-frequency code resource pool. When the resource pool is a time-frequency resource pool, it may include time-domain and / or frequency-domain resource indication information for transmitting the second message. When the resource pool is a time-frequency code resource pool, in addition to including time-domain and / or frequency-domain resource indication information for transmitting the second message, it also includes code-domain resource indication information, such as a set of code-domain resources available for transmitting the second message, such as an OCC set.

[0258] In some embodiments, the at least one resource pool includes: at least one first-type resource pool, and / or, at least one second-type resource pool; wherein the first-type resource pool includes time-domain resources, frequency-domain resources, and code-domain resources, and the second-type resource pool includes time-domain resources and frequency-domain resources. Optionally, the first-type resource pool is a resource pool based on OCC transmission, and the second-type resource pool is a resource pool not based on OCC transmission. The resource pool based on OCC transmission is a time-frequency code resource pool, which, in addition to including time-domain and / or frequency-domain resource indication information for transmitting the second message, also includes a set of OCCs available for transmitting the second message. The resource pool not based on OCC transmission is a time-frequency resource pool, which includes time-domain and / or frequency-domain resource indication information for transmitting the second message.

[0259] In some embodiments, the configuration of the resource pool is related to at least one of the following: Coverage Enhancement Level (CE level), carrier type, subcarrier spacing, uplink transmission mode, and TBS (Transport Block Size).

[0260] Optionally, the above resource pools are configured based on CE level, that is, each resource pool corresponds to a CE level.

[0261] Optionally, for each CE level, resource pools are configured on anchor carriers (carriers used to transmit specific signals) and / or non-anchor carriers, respectively, that is, each resource pool corresponds to an anchor carrier or one of the non-anchor carriers.

[0262] Optionally, resource pools can be configured for different subcarrier intervals (e.g., 15kHz subcarrier interval and 3.75kHz subcarrier interval), with each resource pool corresponding to one subcarrier interval.

[0263] Optionally, for a 15kHz subcarrier spacing, resource pools are configured separately for single-tone and multi-tone. That is, each resource pool corresponding to a 15kHz subcarrier spacing corresponds to either single-tone or multi-tone. Furthermore, if it corresponds to multi-tone, it further corresponds to a number of tones (number of carriers).

[0264] Optionally, the resource pool supports different TBSs. Specifically, this can be achieved as follows: each resource pool corresponds to a maximum TBS (i.e., the resource size or number is fixed, and it also corresponds to a maximum MCS (Modulation and Coding Scheme)). The terminal device can adjust the actual TBS according to the number of bits to be transmitted, but the resource size or number remains unchanged, and the actual MCS is lower than the maximum MCS.

[0265] For (2) above, the network device can configure SA or DSA for each CE level. For example, the number of replicas of the second message can be configured as 1 (SA), 2, 3, or 4.

[0266] Regarding (3) above, the power control parameters of the second message are used to control the transmission power of the second message.

[0267] Regarding (4) above, the second configuration information may include at least one of the following: PDCCH-related configuration information and the duration of the first timer. The PDCCH-related configuration information includes the PDCCH search space and the maximum number of PDCCH repetitions. Optionally, the PDCCH configuration information can be configured separately based on the CE level. The first timer can also be called a contention resolution timer. Optionally, the duration of the first timer can be configured separately based on the CE level.

[0268] For (5) above, the TA verification parameters may include at least one of the following: the duration of the TA timer, and the RSRP change threshold of the terminal device on the serving cell. Both of these pieces of information are used by the terminal device to evaluate the validity of the TA when it is in a disconnected state. Optionally, for 15kHz SCS NB-IoT and eMTC CE mode B, the network device configures the terminal device-specific TA verification parameters through dedicated signaling, such as through the RRRCRelease message.

[0269] Step 504: The terminal device sends a second message based on the first configuration information.

[0270] In some embodiments, when the terminal device is in a disconnected state, such as when the terminal device is in an RRC IDLE state, a CB-Msg3 EDT is initiated, and the PUSCH transmission resource of CB-Msg3 is selected based on the first configuration information mentioned above.

[0271] For SA, the terminal device randomly selects one CB-Msg3 PUSCH transmission opportunity within the time window configured by the network device; for DSA, the terminal device randomly selects multiple CB-Msg3 PUSCH transmission opportunities within the time window configured by the network device.

[0272] Within the configured time window, the terminal device will randomly select different time domain locations to transmit multiple replicas. For each time domain location, the terminal device will randomly select a frequency domain resource.

[0273] In some embodiments, when multiple identical second messages are sent using DSA, the multiple identical second messages use the same code domain resource (such as OCC), or the multiple identical second messages use different code domain resources (such as OCC).

[0274] For the time-frequency code resource pool, the terminal device randomly selects a first OCC from the set of OCCs available for CB-Msg3 PUSCH transmission. Optionally, for DSA, there is only one first OCC, used for multiple Msg3 copies of DSA (i.e., multiple selected CB-Msg3 PUSCH transmission opportunities); or, there are multiple first OCCs, each used for multiple Msg3 copies of DSA (i.e., multiple selected CB-Msg3 PUSCH transmission opportunities).

[0275] During one or more selected CB-Msg3 PUSCH transmission opportunities, the terminal device transmits Msg3 or a copy of Msg3, wherein Msg3 or a copy of Msg3 contains the terminal device's uplink data and / or RRC messages (such as RRC Early Data Request, RRC Connection Request, RRC Connection Resume Request, etc.).

[0276] In addition, the terminal device uses a second RNTI to scramble the CB-Msg3 PUSCH transmission. The second RNTI can be determined by the terminal device according to the method described above.

[0277] Step 506: In response to sending the second message, the terminal device starts the first timer.

[0278] In response to sending Msg3 or a copy of Msg3, the terminal device starts the first timer. During the execution of the first timer, the terminal device listens for the first PDCCH and receives Multi-UE Msg4. The timing of starting the first timer is explained above and will not be repeated here.

[0279] The above methods enable the configuration of CB-Msg3 transmission resources and the transmission of CB-Msg3.

[0280] The technical solution of this application will be described below using different embodiments for CB-msg3 based EDT and traditional EDT.

[0281] 1: CB-msg3 based EDT+Multi-UE Msg4

[0282] 1-1. The terminal device determines the second RNTI for scrambling CB-msg3 PUSCH based on at least one of the time domain, frequency domain, and code domain positions of the PUSCH resources transmitted by CB-Msg3 EDT.

[0283] 1-2. Based on at least one of the time-domain, frequency-domain, and code-domain locations of the PUSCH resources transmitted via CB-Msg3 EDT, the terminal device determines a first RNTI common to multiple terminal devices. This RNTI is used to schedule the scrambling of the PDCCH received by Msg4 and for the scrambling of the Msg4 PDSCH. The terminal device listens to the Msg4 PDCCH and receives the Msg4 PDSCH based on the first RNTI. The Msg4 PDSCH is a common Msg4 shared by multiple terminal devices.

[0284] For example, as shown in FIG10, the method provided in this embodiment may include at least one of the following steps S1 to S5.

[0285] Step S1: The terminal device receives first configuration information from the network device for configuring Msg3 PUSCH transmission resources in CB-Msg3 EDT.

[0286] In step S2, the terminal device in RRC IDLE state initiates CB-Msg3 EDT and selects the PUSCH transmission resource for CB-Msg3.

[0287] In step S3, the terminal device transmits Msg3 or a copy of Msg3 at one or more selected CB-Msg3 PUSCH transmission times. Msg3 or a copy of Msg3 contains the terminal device's uplink data and / or RRC messages. The terminal device scrambles the CB-Msg3 PUSCH transmission using a second RNTI, which is determined by the terminal device based on one or more information / factors from time-domain, frequency-domain, and code-domain resources.

[0288] In step S4, after transmitting Msg3 or a copy of Msg3, the terminal device starts a first timer. During the operation of the first timer, the terminal device listens to the PDCCH and receives Multi-UE Msg4. Specifically, the PDCCH and / or PDSCH of Multi-UE Msg4 are scrambled by a first RNTI. The first RNTI is a common RNTI for multiple terminal devices, or the first RNTI corresponds to multiple second RNTIs. Multi-UE Msg4 contains one or more Msg4 messages (i.e., the "sub-messages" mentioned above).

[0289] Step S5: The terminal device resolves the contention conflict based on Multi-UE Msg 4.

[0290] 2: Traditional EDT + Multi-UE Msg4

[0291] 2-1. The terminal equipment uses the TC-RNTI indicated in Msg2 RAR to scramble the PUSCH of the initial and retransmission of Msg3 EDT.

[0292] 2-2. The terminal device determines a common first RNTI for multiple terminal devices based on the TC-RNTI. This RNTI is used to schedule the scrambling of the PDCCH for Msg4 reception and Msg3 retransmission, and to scramble the Msg4 PDSCH. The terminal device listens to the PDCCH and receives the Msg4 PDSCH based on the first RNTI. The Msg4 PDSCH is a common Msg4 for multiple terminal devices.

[0293] For example, as shown in FIG11, the method provided in this embodiment may include at least one of the following steps S1 to S7.

[0294] Step S1: The terminal device receives first configuration information from the network device for EDT transmission resource configuration.

[0295] In step S2, the terminal device in RRC IDLE state selects transmission resources and initiates EDT transmission based on the first configuration information.

[0296] Step S3: The terminal device sends Msg1.

[0297] Step S4: The terminal device receives Msg2 sent by the network device, which carries the uplink authorization for the transmission of TC-RNTI and Msg3.

[0298] Step S5, the terminal device sends Msg3, which carries the uplink data of EDT and is scrambled using TC-RNTI.

[0299] Step S6: After transmitting Msg3, the terminal device starts a first timer. During the operation of the first timer, the terminal device listens to the PDCCH and receives retransmissions of Multi-UE Msg4 or Msg3. Specifically, the PDCCH and / or PDSCH of Multi-UE Msg4 are scrambled by a first RNTI. The first RNTI is a common RNTI for multiple terminal devices, or the first RNTI corresponds to multiple TC-RNTIs. Multi-UE Msg4 contains one or more Msg4 messages (i.e., the "sub-messages" mentioned above).

[0300] Step S7: The terminal device resolves the contention conflict based on Multi-UE Msg 4.

[0301] It should be noted that, in the above method embodiments, the steps executed by the terminal device can be implemented independently as a wireless communication method on the terminal device side, and the steps executed by the network device can be implemented independently as a wireless communication method on the network device side. Furthermore, the various embodiments of this application can be arbitrarily combined to form new embodiments, all of which are within the protection scope of this application.

[0302] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0303] Please refer to Figure 12, which shows a block diagram of a wireless communication device according to an embodiment of this application. This device has the function of implementing the wireless communication method described above on the terminal device side. This function can be implemented in hardware or by hardware executing corresponding software. The device can be the terminal device described above, or it can be disposed within a terminal device. As shown in Figure 12, the device 1000 may include a receiving module 1010.

[0304] The receiving module 1010 is used to receive a first message based on a first RNTI, wherein multiple terminal devices reuse the same first message.

[0305] In some embodiments, the first RNTI is used to receive a first PDCCH and / or a first PDSCH, the first PDCCH is used to schedule the reception of the first message, and the first PDSCH is used to carry the first message.

[0306] In some embodiments, the first RNTI is determined based on first resource information, which is related to a second message sent by the terminal device.

[0307] In some embodiments, the first resource information includes at least one of the following: an index of the time-domain resource corresponding to the second message; an index of the frequency-domain resource corresponding to the second message; an index of the code-domain resource corresponding to the second message; a first timer, which is a timer started by the terminal device in response to sending the second message; and a first period, which is a period for transmitting the transmission resources for transmitting the second message.

[0308] In some embodiments, the first resource information is a subset of the second resource information, the second resource information being used to determine the second RNTI, the second RNTI being the RNTI used by the terminal device to send the second message.

[0309] In some embodiments, the first RNTI is determined based on a quantity N, where N is an integer greater than 1; the quantity N is the number of terminal devices that reuse the same first message; or, the quantity N is the number of second RNTIs that reuse the same first RNTI, where the second RNTI is the RNTI used by the terminal device to send the second message.

[0310] In some embodiments, the first RNTI is determined based on the quantity N and the second RNTI, where the second RNTI is the RNTI used by the terminal device to send the second message.

[0311] In some embodiments, the second resource information for determining the second RNTI includes at least one of the following: an index of the time-domain resource corresponding to the second message; an index of the frequency-domain resource corresponding to the second message; an index of the code-domain resource corresponding to the second message; a first timer, wherein the first timer is a timer started by the terminal device in response to sending the second message; and a first period, wherein the first period is the period for transmitting the transmission resources for transmitting the second message.

[0312] In some embodiments, the second message is CB-Msg3.

[0313] In some embodiments, the receiving module 1010 is further configured to receive first configuration information, the first configuration information being used to configure the transmission resources of a second message, the second message carrying uplink data of an EDT.

[0314] In some embodiments, the first configuration information is used to determine at least one of the following: at least one resource pool, wherein the transmission resources in the resource pool are used to transmit the second message; at least one SA or DSA configuration corresponding to a coverage enhancement level; power control parameters of the second message; second configuration information for receiving the first message; and TA verification parameters.

[0315] In some embodiments, the at least one resource pool includes: at least one first type of resource pool, and / or, at least one second type of resource pool; wherein the first type of resource pool includes time-domain resources, frequency-domain resources, and code-domain resources, and the second type of resource pool includes time-domain resources and frequency-domain resources.

[0316] In some embodiments, the configuration of the resource pool relates to at least one of the following: coverage enhancement level, carrier type, subcarrier spacing, uplink transmission mode, and TBS.

[0317] In some embodiments, the first message is used for contention resolution and / or for scheduling the retransmission of the second message.

[0318] In some embodiments, the first message includes M sub-messages, where M is a positive integer; the M sub-messages correspond one-to-one with M terminal devices; or, the M sub-messages correspond one-to-one with M second RNTIs, where the M second RNTIs include the RNTIs used by the terminal devices to send the second message; or, the M sub-messages correspond one-to-one with M transmission opportunities, where the transmission opportunities are used to send the second message.

[0319] In some embodiments, the sub-message is used to indicate that the contention conflict has been successfully resolved; or, the sub-message is used to schedule the retransmission of the second message.

[0320] In some embodiments, the first message further includes index information corresponding to the M sub-messages, wherein the index information corresponding to the sub-messages is used to indicate the terminal device or second RNTI or transmission timing corresponding to the sub-message.

[0321] In some embodiments, the index information corresponding to the sub-message includes first index information, which is information for determining whether the second RNTI is used and whether the first RNTI is not used.

[0322] In some embodiments, the index information corresponding to the sub-message is carried by MAC CE.

[0323] In some embodiments, when the first PDCCH is used to schedule the retransmission of the second message, the information carried by the first PDCCH includes the index information.

[0324] In some embodiments, the first message may further include length information or starting position information corresponding to the M sub-messages respectively.

[0325] In some embodiments, as shown in FIG12, the device 1000 further includes a processing module 1020, configured to determine that contention resolution was successful when the first message includes a first sub-message. The contention resolution identifier indicated in the first sub-message matches the CCCH SDU carried in the second message sent by the terminal device.

[0326] In some embodiments, the first message includes M sub-messages, where M is a positive integer; the first sub-message is a sub-message determined from the M sub-messages based on the index information corresponding to each of the M sub-messages, wherein the index information corresponding to the sub-message is used to indicate the terminal device or second RNTI or transmission timing corresponding to the sub-message.

[0327] In some embodiments, when multiple identical second messages are sent using DSA, the multiple identical second messages use the same code field resource, or the multiple identical second messages use different code field resources.

[0328] In some embodiments, the first message is Msg4.

[0329] Please refer to Figure 13, which shows a block diagram of a wireless communication device according to another embodiment of this application. This device has the function of implementing the wireless communication method on the network device side described above. This function can be implemented in hardware or by hardware executing corresponding software. The device can be the network device described above, or it can be disposed within a network device. As shown in Figure 13, the device 1100 may include a transmitting module 1110.

[0330] The sending module 1110 is used to send a first message based on a first RNTI, wherein multiple terminal devices reuse the same first message.

[0331] In some embodiments, the first RNTI is used to receive a first PDCCH and / or a first PDSCH, the first PDCCH is used to schedule the reception of the first message, and the first PDSCH is used to carry the first message.

[0332] In some embodiments, the first RNTI is determined based on first resource information, which is related to a second message sent by the terminal device.

[0333] In some embodiments, the first resource information includes at least one of the following: an index of the time-domain resource corresponding to the second message; an index of the frequency-domain resource corresponding to the second message; an index of the code-domain resource corresponding to the second message; a first timer, which is a timer started by the terminal device in response to sending the second message; and a first period, which is a period for transmitting the transmission resources for transmitting the second message.

[0334] In some embodiments, the first resource information is a subset of the second resource information, the second resource information being used to determine the second RNTI, the second RNTI being the RNTI used by the terminal device to send the second message.

[0335] In some embodiments, the first RNTI is determined based on a quantity N, where N is an integer greater than 1; the quantity N is the number of terminal devices that reuse the same first message; or, the quantity N is the number of second RNTIs that reuse the same first RNTI, where the second RNTI is the RNTI used by the terminal device to send the second message.

[0336] In some embodiments, the first RNTI is determined based on the quantity N and the second RNTI, where the second RNTI is the RNTI used by the terminal device to send the second message.

[0337] In some embodiments, the second resource information for determining the second RNTI includes at least one of the following: an index of the time-domain resource corresponding to the second message; an index of the frequency-domain resource corresponding to the second message; an index of the code-domain resource corresponding to the second message; a first timer, wherein the first timer is a timer started by the terminal device in response to sending the second message; and a first period, wherein the first period is the period for transmitting the transmission resources for transmitting the second message.

[0338] In some embodiments, the second message is CB-Msg3.

[0339] In some embodiments, the sending module 1110 is further configured to send first configuration information, the first configuration information being used to configure the transmission resources of the second message, the second message carrying uplink data of EDT.

[0340] In some embodiments, the first configuration information is used to determine at least one of the following: at least one resource pool, wherein the transmission resources in the resource pool are used to transmit the second message; at least one SA or DSA configuration corresponding to a coverage enhancement level; power control parameters of the second message; second configuration information for receiving the first message; and TA verification parameters.

[0341] In some embodiments, the at least one resource pool includes: at least one first type of resource pool, and / or, at least one second type of resource pool; wherein the first type of resource pool includes time-domain resources, frequency-domain resources, and code-domain resources, and the second type of resource pool includes time-domain resources and frequency-domain resources.

[0342] In some embodiments, the configuration of the resource pool relates to at least one of the following: coverage enhancement level, carrier type, subcarrier spacing, uplink transmission mode, and TBS.

[0343] In some embodiments, the first message is used for contention resolution and / or for scheduling the retransmission of the second message.

[0344] In some embodiments, the first message includes M sub-messages, where M is a positive integer; the M sub-messages correspond one-to-one with M terminal devices; or, the M sub-messages correspond one-to-one with M second RNTIs, where the M second RNTIs include the RNTIs used by the terminal devices to send the second message; or, the M sub-messages correspond one-to-one with M transmission opportunities, where the transmission opportunities are used to send the second message.

[0345] In some embodiments, the sub-message is used to indicate that the contention conflict has been successfully resolved; or, the sub-message is used to schedule the retransmission of the second message.

[0346] In some embodiments, the first message further includes index information corresponding to the M sub-messages, wherein the index information corresponding to the sub-messages is used to indicate the terminal device or second RNTI or transmission timing corresponding to the sub-message.

[0347] In some embodiments, the index information corresponding to the sub-message includes first index information, which is information for determining whether the second RNTI is used and whether the first RNTI is not used.

[0348] In some embodiments, the index information corresponding to the sub-message is carried by MAC CE.

[0349] In some embodiments, when the first PDCCH is used to schedule the retransmission of the second message, the information carried by the first PDCCH includes the index information.

[0350] In some embodiments, the first message may further include length information or starting position information corresponding to the M sub-messages respectively.

[0351] In some embodiments, when multiple identical second messages are sent using DSA, the multiple identical second messages use the same code field resource, or the multiple identical second messages use different code field resources.

[0352] In some embodiments, the first message is Msg4.

[0353] It should be noted that the above embodiments only illustrate the division of the above functional modules when implementing the device. In actual applications, the above functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0354] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here. For details not described in detail in the apparatus embodiments, please refer to the above method embodiments.

[0355] Please refer to 14, which shows a schematic diagram of a terminal device provided in one embodiment of this application. The terminal device 1200 may include a processor 1201, a transceiver 1202, and a memory 1203. The processor 1201 is used to implement various processing functions of the terminal device 1200, such as generating information to be sent, processing received information, controlling transmission and / or reception, etc., thus implementing the functions of the aforementioned processing module. The transceiver 1202 is used to implement transmission and / or reception functions, thus implementing the functions of the aforementioned receiving module.

[0356] The processor 1201 includes one or more processing cores. The processor 1201 executes various functional applications and information processing by running software programs and modules.

[0357] The transceiver 1202 may include a receiver and a transmitter. For example, the receiver and transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0358] The memory 1203 can be connected to the processor 1201 and the transceiver 1202.

[0359] The memory 1203 can be used to store a computer program executed by the processor, and the processor 1201 is used to execute the computer program to implement the various steps in the above method embodiments.

[0360] In some embodiments, transceiver 1202 is used to receive a first message based on a first RNTI, wherein multiple terminal devices multiplex the same first message.

[0361] For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

[0362] Furthermore, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, statically accessible memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0363] Please refer to Figure 15, which shows a schematic diagram of a network device provided in one embodiment of this application. The network device 1300 may include a processor 1301, a transceiver 1302, and a memory 1303. The processor 1301 can be used to implement various processing functions of the network device 1300, such as generating information to be sent, processing received information, and controlling transmission and / or reception. The transceiver 1302 is used to implement transmission and / or reception functions, such as implementing the functions of the aforementioned transmission module.

[0364] The processor 1301 includes one or more processing cores. The processor 1301 executes various functional applications and information processing by running software programs and modules.

[0365] Transceiver 1302 may include a receiver and a transmitter. For example, transceiver 1302 may include a wired communication component, which may include a wired communication chip and a wired interface (such as a fiber optic interface). Optionally, transceiver 1302 may also include a wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0366] The memory 1303 can be connected to the processor 1301 and the transceiver 1302.

[0367] The memory 1303 can be used to store a computer program executed by the processor, and the processor 1301 is used to execute the computer program to implement the various steps performed by the network device in the above method embodiment.

[0368] In some embodiments, transceiver 1302 is used to send a first message based on a first RNTI, wherein multiple terminal devices reuse the same first message.

[0369] For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

[0370] Furthermore, the memory 1303 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static on-demand memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0371] This application also provides a computer-readable storage medium storing a computer program for execution by a processor to implement the aforementioned wireless communication method on the terminal device side or the aforementioned wireless communication method on the network device side. In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0372] This application also provides a chip, which includes programmable logic circuits and / or program instructions. When the chip is running, it is used to implement the wireless communication method on the terminal device side described above.

[0373] This application also provides a chip, which includes programmable logic circuitry and / or program instructions. When the chip is running in a terminal device, it is used to: receive a first message based on a first RNTI, wherein multiple terminal devices multiplex the same first message. When the chip is running in a terminal device, it is also used to implement other steps executed by the terminal device as described in the above embodiments, which will not be repeated here.

[0374] This application also provides a chip, which includes programmable logic circuits and / or program instructions, and when the chip is running, it is used to implement the wireless communication method on the network device side described above.

[0375] This application also provides a chip, which includes programmable logic circuitry and / or program instructions. When the chip is running in a network device, it is used to: send a first message based on a first RNTI, wherein multiple terminal devices multiplex the same first message. When the chip is running in the network device, it is also used to implement other steps executed by the network device as described in the above embodiments, which will not be repeated here.

[0376] This application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the wireless communication method on the terminal device side or the wireless communication method on the network device side.

[0377] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0378] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0379] In some embodiments of this application, "predefined" can be achieved by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0380] In some embodiments of this application, the term "protocol" may refer to standard protocols in the field of communications, such as BLE protocol, Wi-Fi protocol, and related protocols applied in future communication systems. This application does not limit the scope of these protocols.

[0381] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0382] In this article, "greater than or equal to" can mean greater than or equal to, and "less than or equal to" can mean less than or equal to.

[0383] Furthermore, the step numbers described herein are merely illustrative of one possible execution order between steps. In some other embodiments, the steps may not be executed in the order of their numbers, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0384] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0385] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A wireless communication method, characterized in that, The method is executed by a terminal device, and the method includes: A first message is received based on a first wireless network temporary identifier (RNTI), wherein multiple terminal devices reuse the same first message.

2. The method according to claim 1, characterized in that, The first RNTI is used to receive the first physical downlink control channel PDCCH and / or the first physical downlink shared channel PDSCH. The first PDCCH is used to schedule the reception of the first message, and the first PDSCH is used to carry the first message.

3. The method according to claim 1 or 2, characterized in that, The first RNTI is determined based on first resource information, which is related to the second message sent by the terminal device.

4. The method according to claim 3, characterized in that, The first resource information includes at least one of the following: The index of the time-domain resource corresponding to the second message; The index of the frequency domain resource corresponding to the second message; The index of the code field resource corresponding to the second message; A first timer, wherein the first timer is a timer started by the terminal device in response to sending the second message; The first cycle is the cycle of transmission resources used to transmit the second message.

5. The method according to claim 3 or 4, characterized in that, The first resource information is a subset of the second resource information, which is used to determine the second RNTI, which is the RNTI used by the terminal device to send the second message.

6. The method according to any one of claims 1 to 5, characterized in that, The first RNTI is determined based on a quantity N, where N is an integer greater than 1; The quantity N is the number of terminal devices that reuse the same first message; or... The number N is the number of second RNTIs that reuse the same first RNTI, where the second RNTI is the RNTI used by the terminal device to send the second message.

7. The method according to claim 6, characterized in that, The first RNTI is determined based on the quantity N and the second RNTI, which is the RNTI used by the terminal device to send the second message.

8. The method according to claim 5 or 7, characterized in that, The second resource information used to determine the second RNTI includes at least one of the following: The index of the time-domain resource corresponding to the second message; The index of the frequency domain resource corresponding to the second message; The index of the code field resource corresponding to the second message; A first timer, wherein the first timer is a timer started by the terminal device in response to sending the second message; The first cycle is the cycle of transmission resources used to transmit the second message.

9. The method according to any one of claims 3 to 5 and 7 to 8, characterized in that, The second message is a competition-based message 3CB-Msg3.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: Receive first configuration information, which is used to configure the transmission resources of the second message, and the second message carries uplink data of Early Data Transmission (EDT).

11. The method according to claim 10, characterized in that, The first configuration information is used to determine at least one of the following: At least one resource pool, wherein the transmission resources in the resource pool are used to transmit the second message; At least one SA or DSA configuration corresponding to each coverage enhancement level; The power control parameters of the second message; The second configuration information is used to receive the first message; TA verification parameters are performed in advance on a scheduled basis.

12. The method according to claim 11, characterized in that, The at least one resource pool includes: at least one first type of resource pool, and / or, at least one second type of resource pool; wherein, the first type of resource pool includes time-domain resources, frequency-domain resources and code-domain resources, and the second type of resource pool includes time-domain resources and frequency-domain resources.

13. The method according to claim 11 or 12, characterized in that, The configuration of the resource pool is related to at least one of the following: coverage enhancement level, carrier type, subcarrier spacing, uplink transmission mode, and transport block size (TBS).

14. The method according to any one of claims 1 to 13, characterized in that, The first message is used for contention resolution and / or for scheduling the retransmission of the second message.

15. The method according to any one of claims 1 to 14, characterized in that, The first message includes M sub-messages, where M is a positive integer; The M sub-messages and M terminal devices correspond one-to-one; or, The M sub-messages and M second RNTIs correspond one-to-one, and the M second RNTIs include the RNTI used by the terminal device to send the second message; or... The M sub-messages and M transmission opportunities correspond one-to-one, and the transmission opportunities are used to send the second message.

16. The method according to claim 15, characterized in that, The sub-message is used to indicate that the contention conflict has been successfully resolved; or, the sub-message is used to schedule the retransmission of the second message.

17. The method according to claim 15 or 16, characterized in that, The first message also includes index information corresponding to the M sub-messages, wherein the index information corresponding to the sub-messages is used to indicate the terminal device, the second RNTI, or the transmission timing corresponding to the sub-message.

18. The method according to claim 17, characterized in that, The index information corresponding to the sub-message includes first index information, which is information for determining whether the second RNTI is used and whether the first RNTI is not used.

19. The method according to claim 17 or 18, characterized in that, The index information corresponding to the sub-message is carried by the Media Access Control (MAC) CE control element.

20. The method according to any one of claims 17 to 19, characterized in that, When the first PDCCH is used to schedule the retransmission of the second message, the information carried by the first PDCCH includes the index information.

21. The method according to any one of claims 15 to 20, characterized in that, The first message also includes the length information or starting position information corresponding to the M sub-messages respectively.

22. The method according to any one of claims 1 to 21, characterized in that, The method further includes: If the first message includes the first sub-message, the race condition is determined to have been successfully resolved. The contention resolution identifier indicated in the first sub-message matches the Common Control Channel (CCCH) Service Data Unit (SDU) carried in the second message sent by the terminal device.

23. The method according to claim 22, characterized in that, The first message includes M sub-messages, where M is a positive integer; The first sub-message is a sub-message determined from the M sub-messages based on the index information corresponding to each of the M sub-messages. The index information corresponding to the sub-message is used to indicate the terminal device, the second RNTI, or the transmission timing corresponding to the sub-message.

24. The method according to any one of claims 1 to 23, characterized in that, When multiple identical second messages are sent using DSA, the multiple identical second messages may use the same code field resource, or the multiple identical second messages may use different code field resources.

25. The method according to any one of claims 1 to 24, characterized in that, The first message is message 4Msg4.

26. A wireless communication method, characterized in that, The method is performed by a network device, and the method includes: A first message is sent based on a first wireless network temporary identifier (RNTI), wherein multiple terminal devices reuse the same first message.

27. The method according to claim 26, characterized in that, The first RNTI is used to receive the first physical downlink control channel PDCCH and / or the first physical downlink shared channel PDSCH. The first PDCCH is used to schedule the reception of the first message, and the first PDSCH is used to carry the first message.

28. The method according to claim 26 or 27, characterized in that, The first RNTI is determined based on first resource information, which is related to the second message sent by the terminal device.

29. The method according to claim 28, characterized in that, The first resource information includes at least one of the following: The index of the time-domain resource corresponding to the second message; The index of the frequency domain resource corresponding to the second message; The index of the code field resource corresponding to the second message; A first timer, wherein the first timer is a timer started by the terminal device in response to sending the second message; The first cycle is the cycle of transmission resources used to transmit the second message.

30. The method according to claim 28 or 29, characterized in that, The first resource information is a subset of the second resource information, which is used to determine the second RNTI, which is the RNTI used by the terminal device to send the second message.

31. The method according to any one of claims 26 to 30, characterized in that, The first RNTI is determined based on a quantity N, where N is an integer greater than 1; The quantity N is the number of terminal devices that reuse the same first message; or... The number N is the number of second RNTIs that reuse the same first RNTI, where the second RNTI is the RNTI used by the terminal device to send the second message.

32. The method according to claim 31, characterized in that, The first RNTI is determined based on the quantity N and the second RNTI, which is the RNTI used by the terminal device to send the second message.

33. The method according to claim 30 or 32, characterized in that, The second resource information used to determine the second RNTI includes at least one of the following: The index of the time-domain resource corresponding to the second message; The index of the frequency domain resource corresponding to the second message; The index of the code field resource corresponding to the second message; A first timer, wherein the first timer is a timer started by the terminal device in response to sending the second message; The first cycle is the cycle of transmission resources used to transmit the second message.

34. The method according to any one of claims 28 to 30 and 32 to 33, characterized in that, The second message is a competition-based message 3CB-Msg3.

35. The method according to any one of claims 26 to 34, characterized in that, The method further includes: Send first configuration information, which is used to configure the transmission resources of the second message, and the second message carries uplink data of Early Data Transmission (EDT).

36. The method according to claim 35, characterized in that, The first configuration information is used to determine at least one of the following: At least one resource pool, wherein the transmission resources in the resource pool are used to transmit the second message; At least one SA or DSA configuration corresponding to each coverage enhancement level; The power control parameters of the second message; The second configuration information is used to receive the first message; TA verification parameters are performed in advance on a scheduled basis.

37. The method according to claim 36, characterized in that, The at least one resource pool includes: at least one first type of resource pool, and / or, at least one second type of resource pool; wherein, the first type of resource pool includes time-domain resources, frequency-domain resources and code-domain resources, and the second type of resource pool includes time-domain resources and frequency-domain resources.

38. The method according to claim 36 or 37, characterized in that, The configuration of the resource pool is related to at least one of the following: coverage enhancement level, carrier type, subcarrier spacing, uplink transmission mode, and transport block size (TBS).

39. The method according to any one of claims 26 to 38, characterized in that, The first message is used for contention resolution and / or for scheduling the retransmission of the second message.

40. The method according to any one of claims 26 to 39, characterized in that, The first message includes M sub-messages, where M is a positive integer; The M sub-messages and M terminal devices correspond one-to-one; or, The M sub-messages and M second RNTIs correspond one-to-one, and the M second RNTIs include the RNTI used by the terminal device to send the second message; or... The M sub-messages and M transmission opportunities correspond one-to-one, and the transmission opportunities are used to send the second message.

41. The method according to claim 40, characterized in that, The sub-message is used to indicate that the contention conflict has been successfully resolved; or, the sub-message is used to schedule the retransmission of the second message.

42. The method according to claim 40 or 41, characterized in that, The first message also includes index information corresponding to the M sub-messages, wherein the index information corresponding to the sub-messages is used to indicate the terminal device, the second RNTI, or the transmission timing corresponding to the sub-message.

43. The method according to claim 42, characterized in that, The index information corresponding to the sub-message includes first index information, which is information for determining whether the second RNTI is used and whether the first RNTI is not used.

44. The method according to claim 42 or 43, characterized in that, The index information corresponding to the sub-message is carried by the Media Access Control (MAC) CE control element.

45. The method according to any one of claims 42 to 44, characterized in that, When the first PDCCH is used to schedule the retransmission of the second message, the information carried by the first PDCCH includes the index information.

46. ​​The method according to any one of claims 40 to 45, characterized in that, The first message also includes the length information or starting position information corresponding to the M sub-messages respectively.

47. The method according to any one of claims 26 to 46, characterized in that, When multiple identical second messages are sent using DSA, the multiple identical second messages may use the same code field resource, or the multiple identical second messages may use different code field resources.

48. The method according to any one of claims 26 to 47, characterized in that, The first message is message 4Msg4.

49. A wireless communication device, characterized in that, The device includes: The receiving module is configured to receive a first message based on a first wireless network temporary identifier (RNTI), wherein multiple terminal devices reuse the same first message.

50. A wireless communication device, characterized in that, The device includes: The sending module is used to send a first message based on a first wireless network temporary identifier (RNTI), wherein multiple terminal devices reuse the same first message.

51. A communication device, characterized in that, The communication device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program to implement the method as claimed in any one of claims 1 to 25, or to implement the method as claimed in any one of claims 26 to 48.

52. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that is executed by a processor to implement the method as described in any one of claims 1 to 25, or the method as described in any one of claims 26 to 48.

53. A chip, characterized in that, The chip includes programmable logic circuitry and / or program instructions, which, when the chip is running, are used to implement the method as described in any one of claims 1 to 25, or to implement the method as described in any one of claims 26 to 48.

54. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, which a processor reads from and executes to implement the method as claimed in any one of claims 1 to 25, or the method as claimed in any one of claims 26 to 48.

Images