Communication method and system

Abstract

The invention discloses a communication method and system. The method comprises the following steps: a base station receives an MSG3 message sent by terminal equipment, and the base station starts a first mechanism in response to the MSG3 message; the base station starts a second mechanism after receiving the MSG5 message sent by the terminal equipment; based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device through a physical downlink control channel (PDCCH); the base station receives uplink data sent by the terminal equipment; and based on the target mechanism, the base station sends a DCI-N1 scheduling instruction to the terminal equipment through a narrowband PDCCH, and after a preset duration of sending the DCI-N1 scheduling instruction is completed, the base station sends downlink data to the terminal equipment for multiple times through a narrowband PUSCH. The technical problem that the non-ground internet of things does not support real-time voice communication is solved.

Description

Technical Field

[0001] The present application relates to the field of satellite communication technology, and in particular to a communication method and system. Background Art

[0002] Traditional satellite voice communication requires the use of dedicated communication protocols and frequency bands. This requires customized mobile phones, such as the common satellite phones with gooseneck antennas. In addition, dedicated satellite phones have larger antennas and higher transmission power, and are usually used in special fields. If applied to mass smartphones, due to the limitations of satellite capabilities and the size and power consumption of mobile phones, they can generally only support text messages and voice intercoms, and it is difficult to support real-time voice communications.

[0003] For low-cost, low-speed IoT, R17 has developed the Internet of Things-Non-Terrestrial Network (IOT-NTN) standard based on satellite communications. Compared with the terrestrial narrowband Internet of Things (NB-IOT) standard, IOT-NTN has made enhancements in terms of time-frequency synchronization, transmission timing relationship, and mobility management to adapt to the characteristics of satellite communication such as large transmission delay, large Doppler frequency shift, and fast satellite beam movement, laying the foundation for satellite-to-ground interconnection.

[0004] Currently, IOT-NTN mainly focuses on low-speed and poorly real-time IoT services, short message services, and voice intercom services, and cannot support real-time voice communications. Its standard uplink and downlink data scheduling process is as follows:

[0005] 1. The scheduling process of downlink data in the Physical Downlink Shared Channel (PDSCH) is as follows. In IOT-NTN, the timing of PDSCH reception is based on the timing of the downlink alone and is not affected by the misalignment of the uplink and downlink frame timing on the User Equipment (UE) side. Figure 1 As shown, the specific scheduling process is as follows:

[0006] (1) At time t1, the network sends DCI-N1 carrying downlink scheduling information on the narrowband physical downlink control channel (NPDCCH);

[0007] (2) At time t2, the network sends downlink data on the narrowband physical downlink shared channel (NPDSCH);

[0008] (3) DCI N1 in step (1) reaches the UE at time t3 after a spatial propagation delay of round trip time (RTT) / 2;

[0009] (4) The data in the NPDSCH in step (2) arrives at the UE side at time t4 after a spatial propagation delay of RTT / 2.

[0010] (5) After receiving the data in NPDSCH, the UE sends the corresponding Hybrid Automatic Repeat-reQuest (HARQ) information in step (4) using NPUSCH format 2 at time t5 after a processing delay of K1 time.

[0011] (6) The HARQ information in step (5) arrives at the network side at time t6 after spatial propagation delay.

[0012] 2. Uplink data scheduling process, such as Figure 2 As shown, the specific steps include the following steps.

[0013] (1) The network sends DCI N0 carrying uplink scheduling information at time t1;

[0014] (2) After a spatial propagation delay of RTT / 2, the DCI N0 reaches the UE at time t2;

[0015] (3) According to the network instruction, the UE undergoes a processing delay K2 similar to that of the terrestrial network and then at time t3 (UE UL time slot n+K offset +K2) sends the scheduled physical uplink shared channel (Physical Uplink Shared Channel, PUSCH);

[0016] (4) After a spatial propagation delay of RTT / 2, the data in the PUSCH arrives at the network side at time t4.

[0017] 3. The scheduling and HARQ of cellular network NB-IOT include the following contents.

[0018] In order to reduce the complexity of the terminal, the protocol allows longer UE decoding time for NPDCCH and NPDSCH. The specific requirements are as follows: Figure 3 shown.

[0019] (1) For scheduling downlink data, the precise time offset between the NPDCCH and the associated NPDSCH is indicated in the DCI.

[0020] (2) After receiving the NPDSCH, the terminal needs to feedback the HARQ confirmation using NPUSCH Format 2. The DCI indicates the resources of the NPUSCH that carries the HARQ confirmation message.

[0021] (3) For uplink scheduling and HARQ operations, the time offset between the end of the NPDCCH and the start of the associated NPUSCH is at least 8 ms.

[0022] In summary, IOT-NTN cannot currently support real-time voice communication. Summary of the invention

[0023] The embodiments of the present application provide a communication method and system to at least solve the technical problem that non-terrestrial network Internet of Things does not support real-time voice communication.

[0024] According to one aspect of an embodiment of the present application, a communication method is provided, including: a base station receives a MSG3 message sent by a terminal device, and the base station responds to the MSG3 message and enables a first mechanism, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off confirmation messages ACK and non-confirmation messages NACK; after receiving the MSG5 message sent by the terminal device, the base station enables a second mechanism, wherein the second mechanism is used to instruct the base station to use a non-confirmation mode in a wireless link control protocol; based on a target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device via a physical downlink control channel PDCCH, wherein the target mechanism includes: the first mechanism and the second mechanism, and the DCI-N0 scheduling instruction is used to instruct the terminal device to send uplink data to the base station multiple times via a physical uplink shared channel PUSCH; the base station receives the uplink data sent by the terminal device; based on the target mechanism, the base station sends a DCI-N1 scheduling instruction to the terminal device via a narrowband PDCCH, and after completing a preset duration for sending the DCI-N1 scheduling instruction, the base station sends downlink data to the terminal device multiple times via a narrowband PUSCH.

[0025] Optionally, the base station receives uplink data sent by the terminal device, including: the base station receives the uplink data sent by the terminal device through PUSCH, wherein the terminal device is used to send uplink data to the base station through PUSCH for multiple times after receiving the first preset duration of the DCI-N0 scheduling instruction, and the first preset duration includes: 8ms.

[0026] Optionally, after the base station receives the MSG3 message sent by the terminal device, the method further includes: using the confirmation mode in the wireless link control protocol to authenticate the terminal device, and receiving the MSG5 message sent by the terminal device if the terminal device is authenticated.

[0027] Optionally, the base station receives uplink data sent by the terminal device, including: after completing the second preset time length for receiving the uplink data, based on the target mechanism, continuing to send DCI-N0 scheduling instructions to the terminal device to schedule the terminal device to continue sending uplink data, wherein the second preset time length includes: 3ms.

[0028] Optionally, based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device through the physical downlink control channel PDCCH, including: the base station determines the minimum time interval between the downlink control information and the physical downlink shared channel PDSCH scheduled by the downlink control information according to the network configuration information and time-frequency resource allocation information of the terminal device, and based on the target mechanism, sends the DCI-N0 scheduling instruction to the terminal device through PDCCH, wherein the DCI-N0 scheduling instruction includes: the minimum time interval.

[0029] Optionally, the base station sends downlink data to the terminal device multiple times via the narrowband PUSCH, including: after completing the third preset duration for sending the downlink data, the base station continues to send DCI-N1 scheduling instructions to the terminal device via the narrowband PDCCH based on the target mechanism, and after completing the preset duration for sending the DCI-N1 scheduling instructions, the base station sends downlink data to the terminal device multiple times via the narrowband PUSCH, wherein the third preset duration includes: 12ms, and the preset duration includes: 4ms.

[0030] According to another aspect of the embodiment of the present application, a communication system is also provided, including: a base station and a terminal device, wherein the base station is communicatively connected with the terminal device, the base station is used to receive a MSG3 message sent by the terminal device, the base station responds to the MSG3 message and enables a first mechanism, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off confirmation messages ACK and non-confirmation messages NACK; the base station is also used to enable a second mechanism after receiving a MSG5 message sent by the terminal device, wherein the second mechanism is used to instruct the base station to use a non-confirmation mode in a wireless link control protocol; the terminal device is used to receive a message sent by the base station based on a target machine The target mechanism comprises: a first mechanism and a second mechanism; the terminal device is used to respond to the DCI-N0 scheduling instruction and send the uplink data indicated by the DCI-N0 scheduling instruction to the base station through the physical uplink shared channel PUSCH for multiple times; the base station is used to receive the uplink data sent by the terminal device; the terminal device is also used to receive the DCI-N1 scheduling instruction sent by the base station through the narrowband PDCCH based on the target mechanism, and receive the downlink data sent by the base station through the narrowband PUSCH for multiple times after completing the preset duration of sending the DCI-N1 scheduling instruction.

[0031] According to another aspect of the embodiments of the present application, a non-volatile storage medium is provided, the storage medium includes a stored program, wherein when the program is executed, the device where the storage medium is located is controlled to execute the above communication method.

[0032] According to another aspect of the embodiments of the present application, there is further provided an electronic device, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the above communication method is executed when the program is run.

[0033] According to yet another aspect of the embodiments of the present application, a computer program is further provided, wherein the above communication method is implemented when the computer program is executed by a processor.

[0034] According to another aspect of the embodiments of the present application, a computer program product is provided, which includes a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above communication method is implemented.

[0035] In an embodiment of the present application, a base station receives a MSG3 message sent by a terminal device, and the base station responds to the MSG3 message and enables a first mechanism, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off confirmation messages ACK and non-confirmation messages NACK; after receiving the MSG5 message sent by the terminal device, the base station enables a second mechanism, wherein the second mechanism is used to instruct the base station to use a non-confirmation mode in a radio link control protocol; based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device via a physical downlink control channel PDCCH, wherein the target mechanism includes: the first mechanism and the second mechanism, DC The I-N0 scheduling instruction is used to instruct the terminal device to send uplink data to the base station multiple times through the physical uplink shared channel PUSCH; the base station receives the uplink data sent by the terminal device; based on the target mechanism, the base station sends the DCI-N1 scheduling instruction to the terminal device through the narrowband PDCCH. After completing the preset duration of sending the DCI-N1 scheduling instruction, the base station sends downlink data to the terminal device multiple times through the narrowband PUSCH, thereby achieving the purpose of supporting real-time voice communication in the non-terrestrial network Internet of Things, thereby achieving the technical effect of improving the communication efficiency of the non-terrestrial network Internet of Things, and then solving the technical problem that the non-terrestrial network Internet of Things does not support real-time voice communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0037] Figure 1 A flowchart of IOT-NTN downlink data scheduling is shown;

[0038] Figure 2 shows a flowchart of IOT-NTN uplink data scheduling;

[0039] Figure 3 A schematic diagram showing a DCI scheduling time interval is shown;

[0040] Figure 4 is a flow chart of a communication method according to an embodiment of the present application;

[0041] Figure 5 is a flow chart of data scheduling according to an embodiment of the present application;

[0042] Figure 6 is a flow chart of another communication method according to an embodiment of the present application;

[0043] Figure 7 is a flow chart of another communication method according to an embodiment of the present application;

[0044] Figure 8 is a structural diagram of a communication system according to an embodiment of the present application;

[0045] Fig. 9 It is a hardware structure block diagram of a computer terminal according to a communication method of an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0047] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0048] According to an embodiment of the present application, a method embodiment of a communication method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0049] Figure 4 is a flow chart of a communication method according to an embodiment of the present application, such as Figure 4 As shown, the method comprises the following steps:

[0050] Step S401, the base station receives a MSG3 message sent by a terminal device, and in response to the MSG3 message, the base station activates a first mechanism, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off confirmation messages ACK and non-confirmation messages NACK.

[0051] The MSG3 message is the third control message sent by the terminal equipment (UE) to the base station (eNodeB, eNB) during the random access process in the wireless communication system.

[0052] MSG3 plays a key role in the random access process. It is not only used to establish a connection, but also to transmit necessary configuration information and identifiers. Since its content and purpose vary depending on the UE status and application scenario, MSG3 can flexibly adapt to different network conditions and user needs. This flexibility makes MSG3 a very important message type in wireless communications. In this embodiment, the UE indicates that the service type is a voice service by adding a special identifier in MSG3. For example, the "voice link establishment" type is added to the service type in MSG3. When the base station recognizes the "voice link establishment" type, the above-mentioned first mechanism is enabled.

[0053] ACK is the abbreviation of "Acknowledgment", which means confirmation or response. ACK is a signal or message used to confirm the receipt of data. When a node (base station or terminal device) sends data to another node (terminal device or base station), the receiver will send an ACK signal to confirm the successful reception of the data. During a general voice call, the base station will continuously send voice data packets to the terminal device. After successfully receiving these data packets, the terminal device will send an ACK signal to the base station to confirm the receipt of the data. NACK is the abbreviation of "Negative Acknowledgment", which means negative response or non-response.

[0054] NACK is a message used to notify the sender that the data was not successfully received. Indication of data loss or error: When the receiver detects data loss or error, it sends a NACK signal to the sender so that the sender can take appropriate remedial measures, such as retransmitting the lost data packet. During a voice call, if the terminal device fails to successfully receive the voice data packet sent by the base station, it will send a NACK signal to the base station. For services with high real-time requirements (such as real-time voice services), turning off ACK and NACK can reduce the delay caused by confirming messages and improve user experience.

[0055] It can be understood that, in the case where the base station turns off the confirmation message ACK and the non-confirmation message NACK, the terminal does not need to enable or disable ACK / NACK.

[0056] For example, the terminal device is in an idle state and is ready to initiate a voice service. The terminal device detects that the user has triggered a voice communication operation, and then establishes a preliminary connection with the base station through a random access preamble. After completing the random access response, the terminal device adds a service type indication in the MSG3 message, clearly identifying it as "voice service." The MSG3 message is sent to the base station via PUCCH or PUSCH. The base station receives the MSG3 message sent by the terminal device and parses the service type indication therein. After confirming that the service type is a voice service, the base station immediately activates the first mechanism to indicate the closure of the feedback channel for confirmation messages (ACK) and non-confirmation messages (NACK). Preferably, the first mechanism also involves modifying the DCI format and deleting the part indicating ACK / NACK to reduce processing overhead and improve network efficiency.

[0057] Step S402: After receiving the MSG5 message sent by the terminal device, the base station activates the second mechanism, wherein the second mechanism is used to instruct the base station to use the non-confirmation mode in the radio link control protocol.

[0058] The MSG5 message is part of the random access process in the 5G network. The MSG5 message is an important signaling sent by the UE to the base station through the RRC SetupComplete message. In the 5G access process, MSG5 marks the completion of the establishment of the RRC connection, and the Signaling Radio Bearer 1 (SRB1) is also established at this time. Subsequent RRC reconfiguration messages will be transmitted on SRB1.

[0059] It is worth noting that the base station uses the non-acknowledgement mode in the radio link control protocol in order to provide a certain degree of data integrity verification while ensuring data transmission efficiency.

[0060] The Radio Link Control (RLC) protocol is an important part of the data link layer in wireless communication systems such as LTE. Located between the Media Access Control (MAC) layer and the Packet Data Convergence Control (PDCP) layer, it is responsible for data segmentation, concatenation and reassembly, as well as error correction through automatic repeat request (ARQ). The RLC protocol provides three working modes: transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM).

[0061] In the non-confirmation mode, the RLC layer will not retransmit the sent data packets. This means that if the data is lost or erroneous during the transmission process, the receiving end will not be able to obtain the retransmitted data. The data transmission in this mode does not require the receiving end's confirmation information, thereby reducing the handshake process and the transmission delay. Since the data is not retransmitted in the non-confirmation mode, its transmission efficiency is higher than that in the confirmation mode (AM). In this mode, the RLC layer simply adds the necessary header information to the PDU from the PDCP layer and sends it directly to the MAC layer, without the need for a complex retransmission mechanism and confirmation process. This simplified processing flow makes the non-confirmation mode particularly suitable for data transmission with high real-time requirements, such as real-time voice services.

[0062] Step S403, based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device through the physical downlink control channel PDCCH, wherein the target mechanism includes: a first mechanism and a second mechanism, and the DCI-N0 scheduling instruction is used to instruct the terminal device to send uplink data to the base station multiple times through the physical uplink shared channel PUSCH.

[0063] In real-time voice communication, latency is one of the key indicators. By optimizing the DCI-N0 scheduling instructions and reducing the scheduling delay, it can ensure that uplink data (such as voice packets) can be quickly received and processed by the base station. In addition, the mechanism of multiple data transmissions can be pre-scheduled to reduce waiting time and further reduce end-to-end communication delay. In addition, by completing multiple data transmissions in one scheduling, the limited resources of satellite communications can be used more efficiently, the waste of channel resources can be reduced, and the throughput and capacity of the entire system can be improved.

[0064] For example, DCI-N0 includes the following information: 1. Resource allocation information: indicates the specific location of the terminal device on the spectrum, that is, on which subcarriers it should receive data. 2. Modulation and Coding Scheme (MCS): tells the terminal device which modulation method and coding rate to use to decode the received data. 3. Transmission time interval: indicates the time interval for data transmission. 4. Control information: such as Hybrid Automatic Repeat Request (HARQ) information, which is used to process retransmission requests in data transmission.

[0065] PDCCH carries scheduling and other control information, including transmission format, resource allocation, uplink scheduling permission, power control, uplink retransmission information, etc. PDCCH is a set of physical resource elements that carry uplink and downlink control information. According to its different scopes, it can be divided into public control information and dedicated control information.

[0066] Step S404: the base station receives uplink data sent by the terminal device.

[0067] For example, the terminal device receives a DCI-N0 scheduling instruction sent by the base station, which is transmitted via the PDCCH. The DCI-N0 scheduling instruction instructs the terminal device to send uplink data via the PUSCH in a preset time slot. Based on the target mechanism, i.e., the first mechanism and the second mechanism, the terminal device does not wait for ACK / NACK confirmation and directly sends uplink data in the specified time slot. The base station receives the uplink data, and because the unconfirmed mode (UM) is used under the target mechanism, ACK / NACK feedback is no longer sent, which can improve the real-time and smoothness of voice calls.

[0068] In summary, by enabling the first and second mechanisms, the entire end-to-end voice communication link is optimized, unnecessary delays and processing steps are reduced, and voice communication is made more real-time and reliable. The data transmission between the base station and the terminal device follows the optimized scheduling process, achieving efficient real-time voice communication and meeting the user's demand for voice call quality.

[0069] According to some optional embodiments of the present application, step S404 can be implemented by the following method: the base station receives the uplink data sent by the terminal device through PUSCH, wherein the terminal device is used to send uplink data to the base station through PUSCH for multiple times after receiving the first preset duration of the DCI-N0 scheduling instruction, and the first preset duration includes: 8ms.

[0070] Preferably, after completing the second preset duration of receiving uplink data, the base station continues to send DCI-N0 scheduling instructions to the terminal device based on the target mechanism to schedule the terminal device to continue sending uplink data, wherein the second preset duration is 3ms.

[0071] For example, at a certain moment (denoted as T0), the network side sends DCI N0 through the PDCCH channel to instruct the terminal device to perform uplink data transmission, where DCI N0 contains parameters such as the time, frequency resources, and modulation and coding scheme for PUSCH transmission. The DCI N0 signal reaches the terminal device side after the spatial propagation delay (denoted as T1) of the satellite link. Assume that the spatial propagation delay is 200ms. After receiving DCI N0, the terminal device starts to process the uplink data after a minimum processing delay of 8ms (denoted as T2) and prepares to transmit on the designated PUSCH. At T0+T1+T2, the terminal device sends uplink data to the base station through PUSCH. Assuming that the uplink data needs to be transmitted repeatedly once, and each transmission takes 80ms, the entire uplink data transmission will be completed at T0+T1+T2+80ms. After the base station receives the uplink data, it can schedule the next uplink data transmission 3ms after the reception confirmation is completed (denoted as T3) to ensure the continuity and real-time nature of data transmission.

[0072] Figure 5 is a flow chart of data scheduling according to an embodiment of the present application. Figure 6 is a flow chart of another communication method according to an embodiment of the present application, comprising Figure 5 and Figure 6 It can be seen that data scheduling includes: uplink scheduling process enhancement, downlink scheduling process enhancement, RLC protocol layer enhancement and DCI scheduling enhancement. Figure 5 and Figure 6 , the communication method proposed in this application is described in detail.

[0073] It should be noted that Figure 5 The two consecutive PDCCHs (DCI N0) at t1 and t5 in the uplink scheduling diagram can be the consecutive scheduling of the same user or the scheduling of different users. In the uplink scheduling process enhancement, the NTN user scheduling parameters are set as follows: PDCCH: repeated twice, one scheduling requires 2 valid subframes, a total of about 2ms. The scheduling delay between PDCCH and PUSCH is minimized: k0=0, that is, the scheduling interval (first preset duration) t3-t2=8ms. The TBS of PUSCH is 680 bits, repeated once, and one scheduling is about 80ms. If the data is repeated n times, a total of 80*n (ms) is required. The scheduling interval (second preset duration) between the PUSCH and the next PDCCH is set to the minimum: t5-t4=3ms. In summary, the total interval time of an uplink scheduling is:

[0074] ΔT up =2+8+80*n+3+K-offset=13+80*n+K-offset(ms)

[0075] PUSCH format 1 is designed for uplink channel data on UL-SCH and uses the same Turbo code error correction as LTE. Its resource block size is much lower than LTE and is no more than 1000 bits. The maximum physical layer rate of a subcarrier is:

[0076]

[0077] The uplink system physical layer (12 subcarriers) rate is:

[0078]

[0079] The uplink transmission delay is:

[0080] ΔT up_delay =2+8+80*n+K-offset=10+80*n+K-offset(ms)

[0081] In short, the uplink data transmission process is as follows: 1. The base station (network side) sends DCI N0 carrying uplink scheduling information on the PDCCH channel. 2. The DCI N0 is transmitted via 3. According to the network instruction, the UE sends the uplink data on the designated PUSCH after a minimum processing delay of 8ms, which is similar to that of the terrestrial network. 4. The base station receives the scheduled uplink data. 5. 3ms after step 4 is completed, the base station performs the next uplink data transmission process.

[0082] Step S405, based on the target mechanism, the base station sends a DCI-N1 scheduling instruction to the terminal device via the narrowband PDCCH. After completing the preset duration of sending the DCI-N1 scheduling instruction, the base station sends downlink data to the terminal device multiple times via the narrowband PUSCH.

[0083] Compared with the traditional method of waiting for the ACK / NACK feedback from the terminal after each transmission, removing the ACK feedback channel and sending data multiple times can continuously utilize satellite resources, reduce resource waste caused by waiting for feedback, and improve the communication efficiency of the link. In addition, real-time voice communication usually requires continuous data stream transmission. Sending data multiple times can ensure the continuity of the voice stream and maintain high-quality voice communication even when the satellite link is unstable or the terminal is moving.

[0084] In some optional embodiments of the present application, sending downlink data to a terminal device via a narrowband PUSCH can be achieved by the following method: after completing the third preset duration for sending the downlink data, the base station continues to send the DCI-N1 scheduling instruction to the terminal device via the narrowband PDCCH based on the target mechanism, and after completing the preset duration for sending the DCI-N1 scheduling instruction, the base station sends downlink data to the terminal device via the narrowband PUSCH for multiple times, wherein the third preset duration includes: 12ms, and the preset duration includes: 4ms.

[0085] like Figure 5 and Figure 6 As shown, the downlink scheduling process enhancement includes: removing the HARQ feedback channel during downlink scheduling. Figure 5 The two consecutive PDCCHs (DCI N1) at t1 and t5 in the downlink scheduling diagram can be the continuous scheduling of one user or the scheduling of different users. Specifically, the NTN user scheduling parameters are set as follows: PDCCH: repeated 2 times, one scheduling requires 2 valid subframes, a total of about 2ms. The scheduling delay between PDCCH and PDSCH takes the minimum k0=0, that is, the scheduling interval t2-t1=4ms. PDSCH: The maximum transmission block size (TBS) is 680 bits, repeated n times, one scheduling requires 20*n valid subframes, and the time is about 20*n (ms). The scheduling interval between the next PDCCH after PDSCH (the third preset duration): 12ms, which is the processing time of the terminal for PDSCH, and the minimum time interval between PDSCH and HARQ is evaluated according to the existing standards. In summary, considering that the overhead of the downlink common channel configuration is about 30%, the remaining 70% is available, and a standard valid subframe is about 1ms.

[0086] Furthermore, the downlink scheduling interval is:

[0087]

[0088] It is understandable that in order to reduce terminal complexity, all downlink channels of NB-NTN use LTE's TBCC code. In addition, the TBS of NPDSCH is 680 bits, and the maximum transmission rate of the physical layer of the downlink system is:

[0089]

[0090] The downlink transmission delay is:

[0091]

[0092] In short, the downlink data transmission process is as follows: 1. The base station sends DCI N1 carrying downlink scheduling information on the NPDCCH channel. 2. The base station sends downlink data on the NPDSCH channel 4ms later. 3. The DCI N1 in step 1 is transmitted through After the spatial propagation delay of , it is received by the UE. 4. The NPDSCH data in step 2 passes through 5. The base station performs the next downlink data transmission process 12ms after step 2 is completed.

[0093] Preferably, in the uplink data transmission and downlink data transmission processes, the random access channel scheduling process remains unchanged, and the connection state between the terminal device and the base station changes from an idle state (RRC_IDLE) to a connected state (RRC_CONNECTED).

[0094] Preferably, after receiving the MSG3 message sent by the terminal device, the base station performs the following steps: using the confirmation mode in the radio link control protocol to authenticate the terminal device, and receiving the MSG5 message sent by the terminal device when the terminal device is authenticated.

[0095] It is understandable that the base station still uses the confirmation mode during the authentication of the terminal device, and only during the voice data transmission does the RLC protocol layer use the non-confirmation mode. The base station uses the confirmation mode when authenticating the terminal device, which means that any errors or packet loss during the data transmission process will be detected and retransmitted to ensure the integrity and correctness of the data. Specifically, the confirmation mode provides error correction function at the RLC layer, and ensures the correct transmission of data through an automatic retransmission request mechanism. When a data packet fails to successfully reach the receiving end, the sending end will resend the lost packet to ensure reliable data transmission. For services with high real-time requirements, such as voice data transmission, waiting for error correction for a long time will introduce unacceptable delays. In this case, the RLC protocol layer uses the non-confirmation mode.

[0096] Specifically, when the terminal device detects that a real-time voice communication connection needs to be established, it actively initiates a random access process and sends a MSG1 message to the network side to request access to the network. After receiving the MSG1 message, the network side allocates random access resources to the terminal device through the MSG2 message and instructs the terminal device to make subsequent authentication preparations. After receiving MSG2, the terminal device reports the authentication information and service type in MSG3 according to the instructions of the network side, and the service type is indicated as "voice link establishment". After receiving MSG3, the network side authenticates the terminal device. The confirmation mode of the RLC protocol layer is used in the authentication process to verify the identity of the terminal device. After the authentication is passed, the network side no longer requires the terminal device to send ACK / NACK feedback to reduce link delay, and then the network side completes the random access process through MSG4. After receiving MSG4, the terminal device sends a MSG5 message to confirm that the random access process has been completed and is ready for real-time voice communication. After receiving the MSG5 message, the network side determines that the terminal device has successfully accessed and starts to use the optimized scheduling scheme, that is, the target mechanism, to support real-time voice services.

[0097] Preferably, after receiving the MSG5 message sent by the terminal equipment or the attach completion message, the base station will not send a downlink hybrid automatic repeat request.

[0098] Preferably, based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device through the physical downlink control channel PDCCH, which can be achieved by the following method: the base station determines the minimum time interval between the downlink control information and the physical downlink shared channel PDSCH scheduled by the downlink control information according to the network configuration information and time-frequency resource allocation information of the terminal device, and based on the target mechanism, sends a DCI-N0 scheduling instruction to the terminal device through PDCCH, wherein the DCI-N0 scheduling instruction includes: the minimum time interval.

[0099] It is understood that in the uplink data transmission and downlink data transmission processes, the base station can indicate to the terminal device the minimum applicable time slot offset, i.e., minimum k0, wherein the use of parameter k0 allows a time offset between the DCI sent by the base station on the PDCCH and its corresponding PDSCH transmission, and this offset can be 0 to 32 time slots, depending on the network configuration. When k0 is set to 0, it means that the DCI and PDSCH are in the same time slot; when k0 is greater than 0, it means that the PDSCH will be received in the k0th time slot in the future. This scheduling method can provide the system with greater flexibility to adapt to different business needs. For low-latency services such as real-time voice communication, a smaller k0 value can be used.

[0100] It should be further explained that the RLC protocol layer enhancement includes: since the service plane only has confirmation mode and unconfirmation mode but no transparent mode at the RLC layer, the three transmission modes are distributed as follows: transparent mode, direct transparent transmission without adding additional information to the upper layer PDU, the main services are broadcast system messages, paging messages, etc.; unconfirmation mode, adding additional information, the transmitted information does not need to be confirmed by the peer entity, mainly for services with high real-time requirements such as VOIP and video; confirmation mode, adding additional information, the transmitted information needs to be confirmed by the peer entity, mainly for error-sensitive services such as FTP and Web browsing. It is worth noting that supporting real-time voice calls requires that both the network side and the terminal side support the unconfirmation mode working mode at the RLC protocol layer. DCI scheduling enhancement includes: each uplink / downlink DCI schedules 2 or more data transmissions on the terminal side in the future. In the downlink scheduling process, one NPDCCH (DCI N1) schedules more than 2 NPDSCH transmissions. In the uplink scheduling process, one NPDCCH (DCI N0) schedules more than 2 NPUSCH transmissions.

[0101] Combine the following Figure 6 The communication method proposed in this application is summarized and explained.

[0102] Step S601: The terminal device initiates a random access process and completes the network stationing. The terminal indicates the voice service type in the MSG3 service type report, and the network side decides to use disable ACK / NACK.

[0103] Step S602: When the current service is a voice service, the base station starts a new scheduling scheme after receiving the MSG5 message, cancels ACK, and uses the RLC UM mode.

[0104] Step S603, executing the uplink data transmission process.

[0105] Step S6031: The network side sends DCI N0 carrying uplink scheduling information on the PDCCH channel.

[0106] Step S6032: The DCI N0 reaches the UE side after spatial propagation of RTT / 2.

[0107] Step S6033: The UE sends uplink data on the designated PUSCH according to the network instruction after a minimum processing delay of 6 ms similar to that of the terrestrial network.

[0108] Step S6034: the network side receives the scheduled uplink data.

[0109] Step S6035: 3 ms after step S6034 is completed, the network side performs the next uplink data transmission process.

[0110] Step S604, executing the downlink data transmission process.

[0111] Step S6041, the network side sends DCI N1 carrying downlink scheduling information on the NPDCCH channel;

[0112] Step S6042, the network side sends downlink data on the NPDSCH channel after 4 ms;

[0113] Step S6043: DCI N1 in step S6041 is received by the UE after a spatial propagation delay of RTT / 2.

[0114] Step S6044: The NPDSCH data in step S6042 is received by the UE after a spatial propagation delay of RTT / 2.

[0115] Step S6045: 12 ms after step S6042 is completed, the network side performs the next downlink data transmission process.

[0116] Through the above steps, a base station receives a MSG3 message sent by a terminal device, and the base station responds to the MSG3 message and enables a first mechanism, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off confirmation messages ACK and non-confirmation messages NACK; after receiving the MSG5 message sent by the terminal device, the base station enables a second mechanism, wherein the second mechanism is used to instruct the base station to use a non-confirmation mode in the radio link control protocol; based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device through a physical downlink control channel PDCCH, wherein the target mechanism includes: a first Mechanism and the second mechanism, the terminal device responds to the DCI-N0 scheduling instruction, and sends the uplink data indicated by the DCI-N0 scheduling instruction to the base station through the physical uplink shared channel PUSCH; the base station receives the uplink data sent by the terminal device; based on the target mechanism, the base station sends the DCI-N1 scheduling instruction to the terminal device through the narrowband PDCCH, and after completing the preset time for sending the DCI-N1 scheduling instruction, the downlink data is sent to the terminal device through the narrowband PUSCH, thereby achieving the purpose of supporting real-time voice communication in the non-terrestrial network Internet of Things, thereby achieving the technical effect of improving the communication efficiency of the non-terrestrial network Internet of Things.

[0117] Figure 7 is a flow chart of another communication method according to an embodiment of the present application. Figure 7 As shown, the method comprises the following steps:

[0118] In step S701, the terminal device sends a MSG3 message to the base station, wherein the base station is used to enable a first mechanism in response to the MSG3 message, the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off confirmation messages ACK and non-confirmation messages NACK; the base station is also used to enable a second mechanism after receiving a MSG5 message sent by the terminal device, wherein the second mechanism is used to instruct the base station to use a non-confirmation mode in the wireless link control protocol.

[0119] Step S702, the terminal device receives a DCI-N0 scheduling instruction sent by the base station through the physical downlink control channel PDCCH based on a target mechanism, wherein the target mechanism includes: a first mechanism and a second mechanism.

[0120] Step S703, the terminal device responds to the DCI-N0 scheduling instruction and sends the uplink data indicated by the DCI-N0 scheduling instruction to the base station through the physical uplink shared channel PUSCH for multiple times, wherein the base station is used to receive the uplink data sent by the terminal device.

[0121] Step S704, the terminal device receives the DCI-N1 scheduling instruction sent by the base station through the narrowband PDCCH based on the target mechanism, and accepts the downlink data sent multiple times by the base station through the narrowband PUSCH after the preset duration of sending the DCI-N1 scheduling instruction is completed.

[0122] It should be noted that Figure 7 The preferred implementation of the illustrated embodiment can be found in Figure 4 The relevant description of the illustrated embodiment will not be repeated here.

[0123] Figure 8 is a structural diagram of a communication system according to an embodiment of the present application, such as Figure 8 As shown, the system includes: a base station 81 and a terminal device 82, wherein:

[0124] Base station 81 is communicatively connected with terminal device 82, and base station 81 is used to receive MSG3 message sent by terminal device 82. Base station 81 responds to MSG3 message and enables the first mechanism, wherein MSG3 message is used to indicate that the service type is voice service, and the first mechanism is used to instruct base station 81 to turn off confirmation message ACK and non-confirmation message NACK.

[0125] The base station 81 is further configured to enable a second mechanism after receiving the MSG5 message sent by the terminal device 82, wherein the second mechanism is configured to instruct the base station 81 to use a non-acknowledgement mode in the radio link control protocol.

[0126] The terminal device 82 is used to receive the DCI-N0 scheduling instruction sent by the base station 81 through the physical downlink control channel PDCCH based on the target mechanism, wherein the target mechanism includes: a first mechanism and a second mechanism.

[0127] The terminal device 82 is used to respond to the DCI-N0 scheduling instruction and send the uplink data indicated by the DCI-N0 scheduling instruction to the base station 81 through the physical uplink shared channel PUSCH for multiple times.

[0128] The base station 81 is used to receive uplink data sent by the terminal device 82.

[0129] The terminal device 82 is also used to receive the DCI-N1 scheduling instruction sent by the base station 81 through the narrowband PDCCH based on the target mechanism, and receive the downlink data sent multiple times by the base station 81 through the narrowband PUSCH after the preset duration of sending the DCI-N1 scheduling instruction is completed.

[0130] Optionally, after receiving the MSG3 message sent by the terminal device 82, the base station 81 may also perform the following steps: use the confirmation mode in the wireless link control protocol to authenticate the terminal device 82, and if the terminal device 82 is authenticated, receive the MSG5 message sent by the terminal device 82.

[0131] Optionally, the base station 81 is also used to receive uplink data sent by the terminal device 82 by the following method: after completing the second preset time duration for receiving the uplink data, based on the target mechanism, continue to send DCI-N0 scheduling instructions to the terminal device 82 to schedule the terminal device 82 to continue sending uplink data, wherein the second preset time duration includes: 3ms.

[0132] Optionally, the base station 81 is also used to perform the following steps: determine the minimum time interval between the downlink control information and the physical downlink shared channel PDSCH scheduled by the downlink control information according to the network configuration information and time-frequency resource allocation information of the terminal device 82, and based on the target mechanism, send a DCI-N0 scheduling instruction to the terminal device 82 through the PDCCH, wherein the DCI-N0 scheduling instruction includes: the minimum time interval.

[0133] Optionally, the base station 81 is also used to perform the following steps: after completing the third preset duration for sending downlink data, continue to send DCI-N1 scheduling instructions to the terminal device 82 through the narrowband PDCCH based on the target mechanism, and after completing the preset duration for sending the DCI-N1 scheduling instructions, the base station 81 sends downlink data to the terminal device 82 through the narrowband PUSCH multiple times, wherein the third preset duration includes: 12ms, and the preset duration includes: 4ms.

[0134] It should be noted that Figure 8 The preferred implementation of the illustrated embodiment can be found in Figure 4 The relevant description of the illustrated embodiment will not be repeated here.

[0135] Fig. 9 FIG. 1 shows a hardware structure block diagram of a computer terminal for implementing a communication method. Fig. 9 As shown, the computer terminal 90 may include one or more (902a, 902b, ..., 902n are used to illustrate) processors 902 (the processor 902 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 904 for storing data, and a transmission module 906 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Fig. 9 The structure shown is only for illustration and does not limit the structure of the above electronic device. Fig. 9 More or fewer components as shown, or with Fig. 9 Different configurations are shown.

[0136] It should be noted that the one or more processors 902 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 90. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0137] The memory 904 can be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the communication method in the embodiment of the present application. The processor 902 executes various functional applications and data processing by running the software programs and modules stored in the memory 904, that is, realizing the above-mentioned communication method. The memory 904 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 904 may further include a memory remotely arranged relative to the processor 902, and these remote memories may be connected to the computer terminal 90 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0138] The transmission module 906 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 90. In one example, the transmission module 906 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission module 906 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0139] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 90 .

[0140] It should be noted that, in some optional embodiments, the above Fig. 9 The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Fig. 9 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0141] It should be noted that Fig. 9 The computer terminal shown is used to execute Figure 4 The communication method shown, therefore the relevant explanations in the execution method of the above command are also applicable to the electronic device and will not be repeated here.

[0142] An embodiment of the present application further provides a non-volatile storage medium, which includes a stored program, wherein when the program is executed, the device where the storage medium is located is controlled to execute the above communication method.

[0143] A program for executing the following functions on a non-volatile storage medium: a base station receives a MSG3 message sent by a terminal device, and the base station responds to the MSG3 message and enables a first mechanism, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off confirmation messages ACK and non-confirmation messages NACK; after receiving a MSG5 message sent by the terminal device, the base station enables a second mechanism, wherein the second mechanism is used to instruct the base station to use a non-confirmation mode in a wireless link control protocol; based on a target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device via a physical downlink control channel PDCCH, wherein the target mechanism includes: the first mechanism and the second mechanism, and the DCI-N0 scheduling instruction is used to instruct the terminal device to send uplink data to the base station multiple times via a physical uplink shared channel PUSCH; the base station receives the uplink data sent by the terminal device; based on the target mechanism, the base station sends a DCI-N1 scheduling instruction to the terminal device via a narrowband PDCCH, and after completing a preset duration for sending the DCI-N1 scheduling instruction, the base station sends downlink data to the terminal device multiple times via a narrowband PUSCH.

[0144] An embodiment of the present application further provides an electronic device, including: a memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the above communication method is executed when the program is run.

[0145] The processor is used to run a program that performs the following functions: the base station receives a MSG3 message sent by a terminal device, and the base station responds to the MSG3 message and enables a first mechanism, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off confirmation messages ACK and non-confirmation messages NACK; after receiving the MSG5 message sent by the terminal device, the base station enables a second mechanism, wherein the second mechanism is used to instruct the base station to use the non-confirmation mode in the wireless link control protocol; based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device through a physical downlink control channel PDCCH, wherein the target mechanism includes: the first mechanism and the second mechanism, and the DCI-N0 scheduling instruction is used to instruct the terminal device to send uplink data to the base station multiple times through a physical uplink shared channel PUSCH; the base station receives the uplink data sent by the terminal device; based on the target mechanism, the base station sends a DCI-N1 scheduling instruction to the terminal device through a narrowband PDCCH, and after completing a preset duration for sending the DCI-N1 scheduling instruction, the base station sends downlink data to the terminal device multiple times through a narrowband PUSCH.

[0146] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0147] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0148] In the above-mentioned embodiments of the present application, the collected information is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary protection measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

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

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

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

[0152] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0153] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A communication method, characterized in that: include: The base station receives a MSG3 message sent by the terminal device, and the base station activates a first mechanism in response to the MSG3 message, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off an acknowledgment message ACK and a non-acknowledgment message NACK; After receiving the MSG5 message sent by the terminal device, the base station enables a second mechanism, wherein the second mechanism is used to instruct the base station to use a non-confirmation mode in a radio link control protocol; Based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device through a physical downlink control channel PDCCH, wherein the target mechanism includes: the first mechanism and the second mechanism, and the DCI-N0 scheduling instruction is used to instruct the terminal device to send uplink data to the base station multiple times through a physical uplink shared channel PUSCH; The base station receives the uplink data sent by the terminal device; Based on the target mechanism, the base station sends a DCI-N1 scheduling instruction to the terminal device via a narrowband PDCCH. After completing a preset duration for sending the DCI-N1 scheduling instruction, the base station sends downlink data to the terminal device multiple times via a narrowband PUSCH.

2. The method according to claim 1, characterized in that The base station receives the uplink data sent by the terminal device, including: The base station receives the uplink data sent by the terminal device through the PUSCH, wherein the terminal device is used to send the uplink data to the base station through the PUSCH multiple times after receiving the first preset duration of the DCI-N0 scheduling instruction, and the first preset duration includes: 8ms.

3. The method according to claim 1, characterized in that After the base station receives the MSG3 message sent by the terminal device, the method further includes: The terminal device is authenticated using the confirmation mode in the radio link control protocol, and when the terminal device is authenticated, the MSG5 message sent by the terminal device is received.

4. The method according to claim 1, characterized in that The base station receives the uplink data sent by the terminal device, including: After completing the second preset duration of receiving the uplink data, based on the target mechanism, continue to send DCI-N0 scheduling instructions to the terminal device to schedule the terminal device to continue sending uplink data, wherein the second preset duration includes: 3ms.

5. The method according to claim 1, characterized in that Based on the target mechanism, the base station sends a DCI-N0 scheduling instruction to the terminal device through a physical downlink control channel PDCCH, including: The base station determines the minimum time interval between the downlink control information and the physical downlink shared channel PDSCH scheduled by the downlink control information according to the network configuration information and time-frequency resource allocation information of the terminal device, and based on the target mechanism, sends a DCI-N0 scheduling instruction to the terminal device through the PDCCH, wherein the DCI-N0 scheduling instruction includes: the minimum time interval.

6. The method according to claim 1, characterized in that The base station sends downlink data to the terminal device multiple times through the narrowband PUSCH, including: After completing the third preset duration of sending the downlink data, the base station continues to send the DCI-N1 scheduling instruction to the terminal device through the narrowband PDCCH based on the target mechanism, and after completing the preset duration of sending the DCI-N1 scheduling instruction, the base station sends downlink data to the terminal device through the narrowband PUSCH multiple times, wherein the third preset duration includes: 12ms, and the preset duration includes: 4ms.

7. A communication system, characterized in that: include: Base station and terminal equipment, wherein, The base station is in communication connection with the terminal device, the base station is used to receive a MSG3 message sent by the terminal device, and the base station activates a first mechanism in response to the MSG3 message, wherein the MSG3 message is used to indicate that the service type is a voice service, and the first mechanism is used to instruct the base station to turn off an acknowledgment message ACK and a non-acknowledgment message NACK; The base station is further configured to enable a second mechanism after receiving the MSG5 message sent by the terminal device, wherein the second mechanism is configured to instruct the base station to use a non-confirmation mode in a radio link control protocol; The terminal device is used to receive a DCI-N0 scheduling instruction sent by the base station through a physical downlink control channel PDCCH based on a target mechanism, wherein the target mechanism includes: the first mechanism and the second mechanism; The terminal device is used to respond to the DCI-N0 scheduling instruction and send the uplink data indicated by the DCI-N0 scheduling instruction to the base station through a physical uplink shared channel PUSCH for multiple times; The base station is used to receive the uplink data sent by the terminal device; The terminal device is also used to receive the DCI-N1 scheduling instruction sent by the base station through the narrowband PDCCH based on the target mechanism, and receive downlink data sent multiple times by the base station through the narrowband PUSCH after completing the preset duration of sending the DCI-N1 scheduling instruction.

8. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored program, wherein when the program is executed, the device where the non-volatile storage medium is located is controlled to execute the communication method according to any one of claims 1 to 6.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program executes the communication method according to any one of claims 1 to 6 when running.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the communication method according to any one of claims 1 to 6 is implemented.

Images