Data transmission method, apparatus and terminal

Abstract

The application discloses a data transmission method, device and terminal, and belongs to the technical field of communication. The data transmission method comprises the following steps: a receiving end determines a parameter configuration of discontinuous reception (DRX) according to a time period in which a service is located; and the receiving end receives data of target communication according to the parameter configuration, wherein the target communication comprises broadcast communication or groupcast communication.

Description

Technical Field

[0001] This application belongs to the field of communications, and specifically relates to a data transmission method, apparatus and terminal. Background Technology

[0002] The discontinuous reception (DRX) cycle parameter for New Radio (NR) sidelinks (SL, also known as direct links, direct communication links, secondary links, etc.) broadcast or multicast can be configured using the Quality of Service (QoS) profiles required for different services, while the DRX offset parameter can be configured using the service-related Destination L2 ID. Therefore, the DRX configuration of the broadcast or multicast sidelink interface (PC5) is achieved through a combination of QoS Profile and Destination L2 ID.

[0003] However, in the initial stage of the service, the receiving terminal (Receive UE, Rx UE) of broadcast or multicast cannot obtain the "ongoing" service QoS Profile information of the surrounding transmitting terminals (Transmit UE, Tx UE) in advance. Therefore, the Rx UE can only implement DRX operation through the service QoS Profile information of the service it is "interested in".

[0004] Generally, User Equipment (UE, also known as the terminal) receives default PC5 DRX configuration information from the Access and Mobility Management Function (AMF), while the UE receives specific PC5 DRX configuration information related to PQI from the Application Function (AF) / Policy Control function (PCF). The Vehicle-to-Everything (V2X) layer provides this information to the Access Stratum (AS), which then combines these PC5 DRX configurations to determine the final DRX configuration. Therefore, it is crucial for the AS layer to effectively combine the appropriate PC5 DRX configuration cycle based on its service nature, characteristics, and timeframe. This requires effective coordination between the Default PC5 DRX configuration and the Specific PC5 DRX configuration under different circumstances.

[0005] The pre-configured Default PC5 DRX can be associated with the PC5 RAT type, or the configuration granularity can be increased, for example, by associating it with the V2X service type or PQI. If the V2X service applies its own independent, uncoordinated DefaultPC5 DRX configuration, this will cause the UE to run multiple services simultaneously, resulting in a significant increase in UE reception time and failing to achieve energy-saving effects.

[0006] In multicast or broadcast, there is no corresponding coordination mechanism between UEs at the AS layer. Each UE must determine its final DRX configuration through pre-configuration (outside network coverage) or base station configuration (within network coverage), which greatly reduces the energy-saving effect of UEs. In particular, before the service has even started, the UE must determine the DRX configuration parameters based on the service of interest to receive multicast or broadcast service data packets. Summary of the Invention

[0007] This application provides a data transmission method, apparatus, and terminal that can solve the problem in the prior art where PC5DRX parameter configuration leads to high terminal power consumption, which is not conducive to terminal energy saving.

[0008] Firstly, a data transmission method is provided, including:

[0009] The receiving end determines the parameter configuration for discontinuous DRX reception based on the period in which the service is located;

[0010] According to the parameter configuration, the receiving end receives the target communication data;

[0011] The target communication includes broadcast communication or multicast communication.

[0012] Secondly, a data transmission device is provided, comprising:

[0013] The configuration module is used to determine the parameter configuration for discontinuous DRX reception based on the period in which the service is located.

[0014] The first receiving module is configured to receive data from the target communication according to the parameters.

[0015] The target communication includes broadcast communication or multicast communication.

[0016] Thirdly, a data transmission method is provided, including:

[0017] The sending end obtains the parameter configuration of the non-continuous reception DRX from the receiving end, and the parameter configuration is determined by the period in which the service is located;

[0018] According to the parameter configuration, the sending end sends the target communication data;

[0019] The target communication includes broadcast communication or multicast communication.

[0020] Fourthly, a data transmission device is provided, comprising:

[0021] The acquisition module is used to acquire the parameter configuration of the discontinuous reception DRX at the receiving end, wherein the parameter configuration is determined by the period in which the service is located;

[0022] The first sending module is used to send data for target communication according to the parameter configuration.

[0023] The target communication includes broadcast communication or multicast communication.

[0024] Fifthly, a terminal is provided, the terminal being a receiving end, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0025] In a sixth aspect, a terminal is provided, the terminal being a receiving end, including a processor and a communication interface, wherein the processor is used to determine the parameter configuration for discontinuous reception of DRX according to the period in which the service is located;

[0026] The communication interface is used to receive data from the target communication according to the parameter configuration;

[0027] The target communication includes broadcast communication or multicast communication.

[0028] In a seventh aspect, a terminal is provided, the terminal being a transmitting end, comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the third aspect.

[0029] Eighthly, a terminal is provided, the terminal being a transmitting end, including a processor and a communication interface, wherein the processor is used to acquire parameter configurations for discontinuous reception of DRX at the receiving end, the parameter configurations being determined by the period in which the service is located; the communication interface is used to send data for target communication according to the parameter configurations;

[0030] The target communication includes broadcast communication or multicast communication.

[0031] A ninth aspect provides a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the third aspect.

[0032] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the steps of the method as described in the first or third aspect.

[0033] Eleventhly, a computer program / program product is provided, the computer program / program product being stored in a non-volatile storage medium, the program / program product being executed by at least one processor to implement the steps of the method as described in the first or third aspect.

[0034] In this embodiment of the application, by configuring the parameters of DRX according to the period of the service, and receiving broadcast or multicast communication data according to the DRX parameter configuration, dynamic configuration of DRX can be achieved, thereby ensuring that terminal power consumption can be saved as much as possible. Attached Figure Description

[0035] Figure 1 This is a flowchart illustrating the data transmission method applied to the receiving end according to an embodiment of this application;

[0036] Figure 2 This is a diagram illustrating the stages of a business process from its inception to its conclusion.

[0037] Figure 3 This is a diagram illustrating the DRX activation time set by the receiving end after receiving a data packet from the sending end.

[0038] Figure 4 This is a schematic diagram illustrating the DRX activation time at the sending and receiving ends in broadcast communication mode.

[0039] Figure 5 This is a schematic diagram illustrating the evolution of data packet transmission and reception at the sending and receiving ends.

[0040] Figure 6 This is a schematic diagram illustrating the usage of the data packet receiving timer;

[0041] Figure 7 This is a diagram illustrating the DRX activation time when a terminal leaves or joins a group under multicast communication.

[0042] Figure 8 This is one of the schematic diagrams of a data transmission device according to an embodiment of this application;

[0043] Figure 9 This is a structural block diagram of the terminal according to an embodiment of this application;

[0044] Figure 10 This is a flowchart illustrating a data transmission method applied to the sending end according to an embodiment of this application;

[0045] Figure 11 This is a second schematic diagram of a data transmission device according to an embodiment of this application;

[0046] Figure 12 This is a structural block diagram of a communication device according to an embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0048] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0049] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used not only in the systems and radio technologies mentioned above, but also in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th Generation (6G) communication systems.

[0050] The data transmission method, apparatus, and terminal provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0051] like Figure 1 As shown in the figure, this application provides a data transmission method, including:

[0052] Step 101: The receiving end configures the parameters for discontinuous reception DRX according to the period in which the service is located.

[0053] Step 102: Receive data from the target communication according to the parameter configuration;

[0054] The target communication includes broadcast communication or multicast communication.

[0055] It should be noted that the services mentioned in the embodiments of this application mainly refer to V2X services, such as... Figure 2As shown, the time span of a business operation from initiation to completion can be divided into three phases: Service Initiation, Service Ongoing, and Service Completion. The Service Initiation phase can be further subdivided into Preparation and Transition; while the Service Completion phase can be further subdivided into Transition and Termination. It is worth noting that the Transition phase is designed to handle uncertainties and occurs before or after the Service Ongoing phase.

[0056] It should be noted that when V2X services are performed between terminals, the party that sends the service data packet is called the sending terminal (Tx UE, also known as the sender), and the party that receives the service data packet is called the receiving terminal (Rx UE, also known as the receiver).

[0057] It should be noted that, due to the inherent characteristics of NR V2X, there is no mature solution for effectively configuring PC5 DRX parameters outside of the service duration. This application provides a solution for configuring DRX during the service initiation and completion phases of broadcast and multicast communications.

[0058] Optionally, the specific implementation of step 101 includes at least one of the following:

[0059] A11. Before the business begins, determine the duration of the first DRX as the DRX activation time;

[0060] A12. During the business launch period, determine the duration of the first DRX and the duration of the second DRX as the DRX activation time;

[0061] A13. After the service is completed, determine the duration of the configured second DRX to be stopped as the DRX activation time, and determine the duration of the first DRX to be used as the DRX activation time.

[0062] First, it should be noted that PC5 DRX mainly includes: Default PC5 DRX and Specific PC5 DRX. Other types of DRX also exist. In this embodiment, the first DRX can refer to the Default PC5 DRX, and the second DRX can refer to the Specific PC5 DRX. Of course, the first DRX can also be a Sidelink DRX (SL DRX), a Specific PC5 DRX, or other types of DRX, and the second DRX can also be a Default PC5 DRX, an SL DRX, or other types of DRX, as long as the first DRX and the second DRX are not the same type of DRX.

[0063] Taking the example where the first DRX refers to the Default PC5 DRX and the second DRX refers to the Specific PC5 DRX, further, the parameters of the first DRX satisfy at least one of the following:

[0064] B11. The parameters of the first DRX are determined by the location of the receiving end;

[0065] It's important to note that the parameters of the Default PC5 DRX can be configured based on geographic location. This means that when a terminal enters a specific geographic location, its Default PC5 DRX parameters will be determined accordingly. This method is quite effective, as network-side devices can pre-configure the Default PC5 DRX parameters based on geographic conditions. For example, in or near a park, the terminal can be configured with appropriate Default PC5 DRX parameters, allowing it to remain in sleep mode for extended periods with only sparse DRX activation time, thus effectively achieving energy savings.

[0066] B12. The parameters of the first DRX are pre-configured;

[0067] Alternatively, the Default PC5 DRX parameter can be pre-configured, meaning the Default PC5 DRX parameter does not depend on any other factors. This method is simpler, but the pre-configured DRX parameter must consider the worst-case scenario, such as the DRX Cycle length being less than the minimum packet delay budget.

[0068] B13. The parameters of the first DRX are configured by the network-side device;

[0069] Optionally, in Idle Mode or Inactive Mode, the network-side device (e.g., a base station) configures the parameters of the Default PC5 DRX. For example, the base station provides the parameters of the Default PC5 DRX to the terminal via System Information Block (SIB) broadcast.

[0070] It should also be noted that, generally, the terminal will always run a configured Default PC5 DRX. The terminal will only use the new Default PC5 DRX configuration if the Default PC5 DRX is reconfigured. For example, if the Default PC5 DRX parameters are configured based on geographic location, when the terminal changes from one geographic location to another, it will select the Default PC5 DRX parameters associated with the new geographic location for DRX configuration.

[0071] During service startup, since the receiving end does not know when the sending end will start the service, the receiving end has neither the QoS Profile configuration information of the relevant service nor the destination L2 ID. In this case, the receiving end will be configured with Default PC5 DRX, and only needs to be woken up to receive upper layer signaling information in a minimal manner.

[0072] It is worth noting that the receiving end must obtain the destination L2 ID information by decoding the Sidelink Control Information (SCI) in each data packet, and then determine whether the received data packet belongs to it. If the decoded destination L2 ID matches the destination L2 ID of the service it is interested in, the receiving end will continue to decode the data in the data packet to obtain the information it needs. Optionally, for the service startup phase, one possible implementation method for DRX configuration is as follows:

[0073] During the service startup phase, the receiving end receives the first data packet;

[0074] Based on the first data packet, the receiving end obtains the service quality (QoS) configuration information of the service;

[0075] The receiver is configured to use the duration of the first DRX and the duration of the second DRX as the DRX activation time.

[0076] It should be noted that the duration of the second DRX is indicated by the DRX parameter corresponding to the QoS configuration information.

[0077] It should be noted that the QoS configuration information mentioned above mainly refers to the QoS Profile. Since the second DRX parameter is mainly associated with the QoS Profile, different QoS Profiles correspond to different second DRX parameters. The DRX parameters here can mainly include: the sidelink discontinuous reception duration timer (sl-drx-onDurationTimer), which is the duration at the beginning of the DRX cycle. Its size depends on how many Tx UEs need to transmit data packets. In other words, it depends on the Channel Occupancy Ratio (CR) value; the sidelink discontinuous reception cycle (sl-drx-Cycle), which depends on the minimum PDB in the QoS Profile configuration file group; and the sidelink discontinuous reception start offset (sl-drx-StartOffset), which determines the start time of sl-drx-onDuration.

[0078] In this embodiment of the application, after the receiving end obtains the data packet that belongs to it sent by the sending end, it parses the QoS Profile in the data packet, obtains the DRX parameters of the second DRX that needs to be configured according to the QoS Profile, and uses the duration of the first DRX and the duration of the second DRX indicated by the DRX parameters corresponding to the QoS Profile as the DRX activation time, thereby realizing the configuration of DRX.

[0079] It should be noted that the application layer at the receiving end determines whether to use DRX mode. Once the receiving end enters DRX mode, it will always run Default PC5 DRX. Only after the receiving end obtains the corresponding service QoS information will it use both Default PC5 DRX and Special PC5 DRX to implement the relevant V2X service. The sending end will send the first data packet (including higher-layer signaling, etc.) within the on-duration configured in the receiving end's Default PC5 DRX. Only after the receiving end receives the first data packet and then directly or indirectly obtains the QoS Profile information of the corresponding service will it start the corresponding Special PC5 DRX. For the receiving end, the process of starting Special PC5 DRX must be completed within the service startup period.

[0080] It should be noted that the above-mentioned direct acquisition of the QoS Profile information of the corresponding service refers to the sending end directly notifying the receiving end of the QoS Profile used through higher-layer signaling; the indirect acquisition of the QoS Profile information of the corresponding service refers to the sending end determining the QoS Profile, sending data packets according to the determined QoS Profile, and the receiving end receiving the data packets and then deducing the QoS Profile information from the information of the received data packets.

[0081] It is worth noting that since the Default PC5 DRX is always running, the on-duration of the Default PC5 DRX and the on-duration of the Special PC5 DRX will overlap in time. In this case, the receiver combines the two independent on-durations into a single DRX Active Time. Only when the DRX Active Time is combined will the sender transmit data packets and the receiver receive data packets.

[0082] Specific application scenarios, Part 1

[0083] PC2 DRX can be configured as Default PC5 DRX and Specific PC5 DRX. Since Default PC5 DRX is always running, the on-duration times of Default PC5 DRX and Specific PC5 DRX overlap. The receiver combines the two independent on-duration times into a single DRX Active Time. Only when the DRX Active Time is combined will the sender transmit data packets and the receiver receive them.

[0084] like Figure 3 As shown, in the following two cases, the receiver will combine the two independent on-durations as the DRX activation time.

[0085] Scenario 1: At time t1, if the sending end initiates the service, it will send the first data packet to the Default PC5 DRX. After receiving the data packet, the receiving end will directly or indirectly obtain the corresponding QoS Profile. Then, the receiving end will determine the parameters corresponding to the Specific PC5 DRX based on the QoS Profile. The receiving end will combine the on-duration of the Default PC5 DRX and the Specific PC5 DRX as the DRX activation time.

[0086] The second scenario: At time t1, if a new member receives a data packet from the sender during the Default PC5 DRX On-duration, determines its interest in receiving data packets, and decides to join the group as a new member, the new member's receiver directly or indirectly obtains the corresponding QoS Profile information after receiving the data packet. The receiver then determines the parameters corresponding to the Specific PC5 DRX based on the QoS Profile. Finally, the receiver combines the On-duration times of the Default PC5 DRX and the Specific PC5 DRX as the DRX activation time.

[0087] Generally, the on-duration time of the Default PC5 DRX is much shorter than that of the Special PC5 DRX. Furthermore, the different broadcast and multicast V2X communication processes on the PC5 side link also differ, therefore the operation of the Default PC5 DRX needs to be considered separately accordingly.

[0088] I. Regarding broadcast communications

[0089] The broadcast mode between terminals is determined by the application layer, and the establishment of the broadcast mode and the sending and receiving of data packets consist of the following three steps:

[0090] Step 1: The application layer at the receiving end first determines the destination L2 ID for broadcast reception. Then, the application layer at the receiving end transmits the destination L2 ID information to the AS layer at the receiving end through the V2X layer.

[0091] Step two: The application layer of the sending end provides data units to the V2X layer, along with the QoS Profile requirements for those data units. The sending end uses a self-allocation method to determine the destination L2 ID for broadcasting, and then determines the PC5 QoS Profile for this broadcast service.

[0092] Step 3: The sending end sends V2X service data packets using the source L2 ID and the destination L2 ID. After receiving the data packet, the receiving end will verify the destination L2 ID. If the destination L2 ID matches the destination L2 ID it received in its broadcast, the receiving end considers the received data packet to be the data packet it needs.

[0093] Each receiver can have multiple destination L2 IDs of interest for broadcast reception, while the sender relies on only one or a few destination L2 IDs for broadcast service during a certain period of service occurrence. When the receiver enters DRX mode, if the parameters of the receiver's PC5 DRX only depend on the pre-configured QoS Profile and destination L2 ID, then most of the reception work will be meaningless, and the power consumption of the receiver will inevitably become a problem. To effectively solve the power consumption problem of the receiver, this application considers the following method: Once the sender starts the service, the sender first uses the Default PC5 DRX configuration to send data packets during the service startup cycle. To ensure that the receiver receives data packets and obtains service-related QoS Profile information during the Default PC5 DRX On-duration, the implementation of receiving the first data packet includes at least one of the following:

[0094] C11. During the DRX activation time of the first DRX, the receiving end receives at least one first data packet;

[0095] The first data packet is sent by the sending end during the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached;

[0096] In other words, in this scenario, the V2X layer or AS layer at the sending end determines the maximum number of transmission opportunities. Before reaching this maximum, the sending end continuously broadcasts data packets to the receiving end during the Default PC5 DRX On-duration. Upon receiving the data packets from the sending end, the receiving end confirms the destination L2 ID and directly or indirectly obtains the QoS Profile information. Based on the service type of the data packets, the receiving end determines the parameters of the Specific PC5 DRX corresponding to the relevant service. Then, the receiving end combines the Default PC5 DRX On-duration and the Specific PC5 DRX On-duration as the DRX activation time.

[0097] It's important to note that the advantage of this implementation is that the V2X service startup window is constant. The sending end assumes that all receivers have already obtained the destination L2 ID and QoS Profile information for the corresponding service during the startup period. Once the service duration begins, the sending end no longer needs to consider the receiver's Specific PC5 DRX configuration. Therefore, it's relatively simple overall. However, the sending end is constantly moving, and the receivers that need to receive broadcast services are constantly changing over time. Therefore, this method is relatively poor at adapting to changes in broadcast services. When a new receiver approaches the sending end, it only starts receiving broadcast service data packets during the Default PC5 DRX On-duration period because the new receiver only receives data packets during that period. The new receiver can only begin receiving broadcast service data packets when the sending end sends data packets during the Default PC5 DRX On-duration period.

[0098] C12, the receiving end receives at least one first data packet during each DRX activation time of the first DRX;

[0099] In other words, in this case, when the sender initiates a new broadcast service, in order to ensure that a new receiver can access the broadcast service initiated by the sender at any time, the sender must send data packets during each Default PC5 DRX On-duration. In this way, as long as the receiver is awakened during the Default PC5 DRX On-duration, the receiver will have the opportunity to join the broadcast service initiated by the sender.

[0100] It is worth noting that there are two scenarios where the sender must transmit data packets during DRX On-duration. The first scenario is that, according to the data packet's PDB requirements, the sender schedules the transmission of data packets during Default PC5 DRX On-duration. The second scenario is that, according to the data packet's PDB requirements, the sender must transmit data packets before Default PC5 DRX On-duration. Therefore, to allow new receivers to join the broadcast service initiated by the sender, the sender repeatedly transmits the same data packets during Default PC5 DRX On-duration.

[0101] It should be noted that the advantages of the two data packet sending methods mentioned above are: better integrity of the broadcast service, and the reception performance of the broadcast service will not be affected by the mobility of the sender and receiver. However, because this method does not clearly distinguish between the service initiation period and the service duration, the sender must constantly monitor the integrity of the broadcast service, which places a relatively heavy burden on the sender's V2X layer or AS layer.

[0102] Optionally, to improve the packet detection success rate of the receiver in the Default PC5 DRX On-duration, the sender should enhance the transmission mechanism in the Default PC5 DRX On-duration and improve the corresponding transmission performance. For example, the sender can consider repeatedly transmitting the same data packets multiple times in the Default PC5 DRX On-duration. This helps the receiver quickly and accurately obtain service-related data packets and directly or indirectly obtain relevant information about the QoS Profile.

[0103] Optionally, during the business completion period, the main implementation method for DRX parameter configuration is as follows:

[0104] If the first condition is met, determine the duration of stopping the use of the configured second DRX as the DRX activation time, and determine the duration of using the first DRX as the DRX activation time.

[0105] The first condition includes at least one of the following:

[0106] D11. The receiving end receives a first indication information sent by the sending end, the first indication information being used to instruct the receiving end to stop using the second DRX;

[0107] Optionally, the receiving end receives first indication information sent by the sending end, including one of the following:

[0108] D111, The receiving end receives the first indication information sent by the sending end through higher-layer signaling;

[0109] It should be noted that in this scenario, the first indication information is sent using higher-layer information. The specific implementation process is as follows: once the sending application layer stops broadcasting, the sending end notifies the receiving end to stop configuring and using the Specific PC5 DRX via higher-layer signaling. In this case, the receiving end stops the Specific PC5 DRX, but the Default PC5 DRX will continue to run. The disadvantage of this first indication information notification method is that if the receiving end fails to receive or successfully decode the first indication information, it will be unable to stop configuring and using the Specific PC5 DRX.

[0110] D112, The receiving end receives the first indication information sent by the sending end through the Media Access Control-CE control unit (MAC-CE) signaling;

[0111] It should be noted that in this scenario, the first indication information is sent using MAC-CE signaling. The specific implementation process is as follows: once the application layer at the sending end stops broadcasting, the sending end notifies the receiving end to stop configuring and using the Specific PC5 DRX via MAC-CE signaling of the SL DRX. In this case, the receiving end stops the Specific PC5 DRX, but the Default PC5 DRX will continue to run. The disadvantage of this first indication information notification method is that if the receiving end fails to receive or successfully decode the MAC-CE signaling carrying the first indication information, it will be unable to stop configuring and using the Specific PC5 DRX.

[0112] D12, First timer timed out;

[0113] It should be noted that the first timer is either started (if it was not started before, it is started when the receiving end receives a new data packet) or restarted (if it was already started before, it needs to be restarted when the receiving end receives a new data packet).

[0114] In this embodiment, the first timer is a data packet reception timer. In this case, the receiving end uses the data packet reception timer to stop the use of the Specific PC5 DRX configuration. Specifically, if the receiving end receives a new data packet from the sending end, it restarts or starts the data packet reception timer. More precisely, once the receiving end receives a new data packet from the sending end, the data packet reception timer will be restarted or started in the first time slot after the DRX activation time. If the data packet reception timer expires, it means that the application layer has no more data packets to send, and the receiving end stops using Specific PC5 DRX, but Default PC5 DRX will continue to run. The advantage of this method is that as long as the sending end stops sending new data packets, the receiving end will stop using the Specific PC5 DRX configuration. Therefore, this method can achieve energy saving at the receiving end.

[0115] II. For multicast communication

[0116] Group management in multicast services is performed at the V2X application layer (VAE and SEAL layers). The following information is provided by the V2X application layer to the V2X layer, and then by the V2X layer to the AS layer.

[0117] First, the V2X application layer can provide group identification information (i.e., the V2X group identifier, V2XGroupIdentifier).

[0118] Second, the V2X application layer can provide V2X application requirements, such as PC5 QoS Profile parameters. However, if the V2X application layer does not provide corresponding requirements, the V2X layer determines the PC5 QoS Profile parameters itself.

[0119] Third, the V2X application layer can provide group size and associated member IDs.

[0120] It is important to note that this information needs to be communicated in the Non-Access Stratum (NAS), meaning that the relevant transmissions must occur during the Default PC5 DRX On-duration. Because the multicast group has not yet been established before the receiving end receives this information, the relevant communication at the NAS layer can only be conducted via broadcast. In other words, before the group (also known as a multicast group) is established, the receiving end receives the group configuration information broadcast by the sending end during the duration of the first DRX.

[0121] Optionally, in this case, when the receiving end joins the group, the receiving end receives a first data packet from the sending end within a target duration; obtains the service quality (QoS) configuration information of the service based on the first data packet; and configures the duration of using the first DRX and the duration of the second DRX indicated by the DRX parameter corresponding to the QoS configuration information as the DRX activation time.

[0122] It should be noted that the target duration is the duration of the first DRX closest to the first moment, and the first moment is the moment when the receiver joins the group.

[0123] It should be further noted that once the multicast is established, the remaining process is essentially the same as that performed by the sender and receiver in broadcast communication. When the receiver receives the initial transmission data packet, it directly or indirectly obtains the relevant QoS Profile, determines the Specific PC5 DRX configuration parameters, and then merges the on-duration time between the Default PC5 DRX and the Specific PC5 DRX. When the sender's application layer stops the broadcast service, the sender uses D11 or D12 from the broadcast communication to stop the Specific PC5 DRX configuration. It should be noted that in this case, similar to broadcast communication, the receiver stops the Specific PC5 DRX, but the Default PC5 DRX will continue to run.

[0124] It's important to note that the specific operations of multicast communication during the service initiation and completion phases are exactly the same as those of broadcast communication. The main difference lies in the fact that multicast requires group management. Based on NR V2X's support for multicast communication, there are two forms of multicast management: Application Layer Connection-less Group and Application Layer Managed Group. For each type of multicast management, the Default PC5 DRX operation should be considered separately.

[0125] Optionally, in the case of no connection group at the application layer, the receiver only needs to wake up to receive data packets during the On-duration associated with the Default PC5 DRX. Its behavior is basically the same as that of the sender and receiver in broadcast communication. The only difference is that the receiver in multicast needs to check the communication range between itself and the sender. The receiver detects the Physical Side Link Control Channel (PSCCH) sent from the sender, i.e., the first-stage SCI (1st Stage SCI) and the Physical Side Link Shared Channel (PSSCH), i.e., the second-stage SCI (2nd Stage SCI). The receiver first determines whether the destination L2 ID matches. If they match, the receiver needs to determine whether the sender is within the communication range. Only if the sender is within the communication range will the receiver determine that the received data packet is the desired data packet. Then, the receiver directly or indirectly obtains the relevant QoS Profile information based on the data packet and then activates the Specific PC5 DRX configuration. Finally, the receiver combines the Default PC5 DRX On-duration and the Specific PC5 DRX On-duration as the DRX activation time.

[0126] Similarly, the sending end needs to initiate multicast services, but the sending end also needs to stop multicast services. When the sending end application layer stops multicast services, the sending end can use D11 or D12 in the above broadcast communication to stop the Specific PC5DRX configuration.

[0127] Optionally, in the case of application-layer managed groups, the V2X application layer provides the group size and associated member IDs, which the V2X layer then passes to the AS layer for multicast services. After the AS layer receives the multicast control information (group size and member IDs), if a new group member joins the multicast service, the new member will perform on-duration activation associated with the Specific PC5 DRX. To ensure that the new member also receives multicast control information during activation, the sender transmits NAS information related to the new member during the Default PC5 DRX on-duration. In other words, the sender must complete the exchange of NAS information related to the new member joining the group during the Default PC5 DRX on-duration. Only after ensuring that the sender has updated the necessary group information can the group member use the new member information for the HARQ feedback process.

[0128] Optionally, after the group is established, group update information sent by the sender is received during the DRX activation time.

[0129] In other words, when an existing group member decides to leave the group, and if the group member or a subset of the group members are configured with PC5DRX, the sender can transmit group management information related to the group member at any time during the on-duration of either the Default PC5 DRX or the Specific PC5 DRX. It is worth noting that in this case, the AS layer does not need to know whether the transmitted information is control information or data information.

[0130] It should also be noted that, for multicast communication, in NR-V2X, the determination of packet retransmission depends on the HARQ feedback type. NR-V2X supports two options for the HARQ feedback process:

[0131] Option 1: If the receiver fails to decode the corresponding transmission block (TB) after decoding the relevant PSCCH, the receiver sends a Hybrid Automatic Repeat Request Unacknowledged (HARQ-NACK) on the Physical Sidelink Feedback Channel (PSFCH); otherwise, the receiver will not transmit signals on the PSFCH.

[0132] Option 2: If the receiver successfully decodes the corresponding TB, it sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) on the PSFCH; if the receiver fails to decode the corresponding TB, it sends a HARQ-NACK on the PSFCH. Therefore, the sender must know the group membership information to determine whether the sent data packet has been correctly received by all receivers.

[0133] It is worth noting that in multicast services, the HARQ feedback type of Option 1 is for the case of application-layer connectionless groups, while the HARQ feedback type of Option 2 is for the case of application-layer management groups. This application embodiment also considers further limiting the HARQ feedback type of Option 2 in the case of application-layer management groups.

[0134] The HARQ feedback process at the receiving end is linked to the current group management status. During group management, the sending application layer should periodically or irregularly update group change information (new terminals entering the multicast service, or existing terminals leaving the multicast service) to all group members. If the group management information remains unchanged, group members use the existing group information (i.e., the number of group members and the group member ID) to execute the HARQ process of option 2. If the group management information changes, and the sending application layer has completed updating the group change information to all group members (new terminals entering the multicast service, or existing terminals leaving the multicast service), the V2X layer notifies the AS layer of the updated group information, and group members use the new group information (i.e., the number of group members and the group member ID) to execute the HARQ process of option 2.

[0135] Optionally, when a new group member decides to join the group, and if the group member or a subset of group members are configured with PC5 DRX, the sender transmits data packets at the most recent On-Duration time of the Default PC5 DRX. The new group member receives the data packet based on the configured On-Duration of the Default PC5 DRX, directly or indirectly obtaining the corresponding QoS Profile information. Then, the receiver combines the Default PC5 DRX On-Duration and the Specific PC5 DRX On-Duration as the DRX activation time. The receiver uses higher-layer information (such as VAE or SEAL layer information) to notify all group members, and completes the group joining process for members wishing to join. It is worth noting that in this case, the AS layer does not know whether the transmitted information is control information or data information. All information exchange is completed at the NAS layer.

[0136] Optionally, after the data of the target communication sent by the receiving end, at least one of the following is also included:

[0137] E11. If the receiving end has not joined the group, determine that no response message for the data will be sent back to the sending end;

[0138] In other words, if the receiving end receives a data packet from the sending end before completing the group joining process (i.e., during the group management period), the receiving end cannot send back ACK / NACK. Only after the receiving end uses other broadcast destination L2 IDs to exchange group information with group members via broadcast can it normally send back HARQ feedback.

[0139] E12. If the receiving end has not left the group, determine to send a response message for the data to the sending end;

[0140] In other words, it is worth noting that if the receiving end receives a data packet from the sending end before completing the leave group process (i.e., during the group management period), even though the receiving end is no longer interested in the received data packet, the receiving end is obligated to send an ACK / NACK back to the sending end to complete the HARQ process.

[0141] The following are examples illustrating several applications of this application.

[0142] Specific application scenario II

[0143] like Figure 4 As shown, Tx UE sends data packets at time t1 (time t1 is within the on-duration of the Default PC5 DRX). Rx UE-2 fails to decode the PSCCH and / or PSSCH due to poor channel conditions. However, other Rx UEs receive the initial data packets, successfully decode the data packet information, and directly or indirectly obtain the corresponding QoS Profile information. Except for Rx UE-2, the other Rx UEs determine the configuration of the Specific PC5 DRX, and then combine the on-duration of the Default PC5 DRX and the Specific PC5 DRX as the DRX activation time.

[0144] Since the initial packet reception of Rx UE-2 failed (e.g., SCI was not decoded correctly), Rx UE-2 will remain dormant until the next on-duration time associated with the Default PC5 DRX configuration arrives. Rx UE-2 successfully receives packets during the Default PC5 DRX on-duration time t6 and directly or indirectly obtains the corresponding QoS Profile information. Rx UE-2 determines the Specific PC5 DRX configuration and then combines the on-duration times of the Default PC5 DRX and Specific PC5 DRX as the DRX activation time.

[0145] It is worth noting that because the Rx UE-2 did not decode the data packets during the first on-duration period, it was unable to receive data packets using the Specific PC5 DRX configuration during the time intervals t1 and t6. During this period, some data packets were lost.

[0146] like Figure 5 As shown, the evolution of data packet transmission and reception for Tx UE and Rx UE, and the UE actions from time t1 to time t6 are as follows:

[0147] At time t1, the Tx UE application layer data packet arrives, and a new multicast or broadcast service begins.

[0148] At time t2, the V2X layer in the Tx UE determines the PC5 QoS Profile parameters, assigns the PC5 QoS Flow ID (PQI), and provides the PFI and associated PC5 QoS Profile parameters to the AS layer.

[0149] At time t3, Tx UE transmits the initial data packets within the On-duration of the Default PC5 DRX configuration.

[0150] At time t4, Rx UE successfully decoded the initial data packet within the on-duration of the Default PC5 DRX configuration.

[0151] At time t5, the Rx UE directly or indirectly obtains QoS Profile information and determines the Specific PC5 DRX configuration. The Rx UE combines the on-duration of the Default PC5 DRX and the Specific PC5 DRX as the DRX activation time and uses it to receive the remaining packets. It is worth noting that the Specific PC5 DRX configuration depends on the PC5 QoS Profile parameters, which are determined by the AS layer.

[0152] At time t6, Rx UE-2 receives data packets for this service within the on-duration of the Default PC5 DRX. Rx UE-2 directly or indirectly obtains QoS Profile related information and determines the Specific PC5 DRX configuration. Rx UE-2 combines the on-duration of the Default PC5 DRX and the Specific PC5 DRX as the DRX activation time and uses it to receive the remaining data packets.

[0153] Specific application scenarios, part three.

[0154] When the Tx UE application layer stops broadcast or multicast services, the implementation methods of D11 and D12 can be considered by the Rx UE. For D12, the Rx UE uses the start packet receive timer to stop the use of the Specific PC5 DRX configuration. Specifically, if the Rx UE receives a new packet from the Tx UE, the Rx UE will (re)start the packet receive timer.

[0155] like Figure 6 As shown, at time t7, the last service data packet arrives at the Tx UE application layer. The Tx UE passes the last service data packet to the AS layer through the V2X layer, and the Tx UE's MAC layer sends the last service data packet at time t8. The Rx UE receives the data packet and restarts the data packet reception timer at time t9 (i.e., the first time slot after on-duration). The Rx UE does not receive any data packets during the data packet reception timer's operation (i.e., the application layer has no more data packets to send), and the data packet reception timer expires at time t10. The Rx UE stops the data packet reception timer at time t10 and stops the Specific PC5 DRX configuration. However, the Default PC5 DRX will continue to run.

[0156] It is worth noting that the period from the arrival time of the last service data packet at the Tx UE application layer t7 to the timer time t10 when the data packet reception stops is considered as the service termination transition period, while the period from time t10 onwards is considered as the service termination period.

[0157] Specific application scenarios, Part IV

[0158] The HARQ feedback process for Rx UEs is linked to the current group management status. During group management, the Tx UE application layer should periodically or irregularly update group change information (i.e., a new UE joins the multicast service, or an existing UE leaves the multicast service) to all group members. If the group management information remains unchanged, group members use the existing group information (i.e., the number of group members and the group member ID) to execute the HARQ procedure of option 2. If the group management information changes, and the Tx UE application layer has completed updating the group change information to all group members (i.e., a new UE enters the multicast service, or an existing UE leaves the multicast service), the V2X layer notifies the AS layer of the updated group information, and group members use the new group information (i.e., the number of group members and the group member ID) to execute the HARQ procedure of option 2.

[0159] like Figure 7As shown, first at time t11, the Tx UE-1 application layer forms a group consisting of Tx UE-1 and Rx UE-2, and notifies the AS layer through the V2X layer. Then, Tx UE-1 sends a data packet to Rx UE-2, and Rx UE-2, upon receiving the data packet, sends an ACK / NACK response to Tx UE-1.

[0160] It is worth noting that in this embodiment, UE-1 is used as a Tx UE. Similarly, UE-2 can also be used as a Tx UE. In this case, UE-1 will send an ACK / NACK response to UE-2.

[0161] At time t12, Rx UE-3 receives a data packet from Tx UE-1 and successfully decodes the PSCCH and PSSCH. Rx UE-3 determines it is interested in the data packet and decides to join the group. Rx UE-3 directly or indirectly obtains QoS Profile information, determines the Specific PC5 DRX configuration, and merges the Default PC5DRX On-duration and Specific PC5DRX On-duration as the DRX activation time. During the DRX activation time, Rx UE-3 exchanges group information with Tx UE-1 / Rx UE-2, completing the entire group joining process at time t13. Afterwards, Tx UE-1 sends a data packet, and Rx UE-2 and Rx UE-3, upon receiving the data packet, will send ACK / NACK feedback to Tx UE-1.

[0162] Optionally, Rx UE-3 can extend the on-duration time after time t12 to complete the exchange of group information with Tx UE-1 / Rx UE-2.

[0163] It is worth noting that before Rx UE-3 completes the group joining process (i.e., during the group management periods t12 and t13), Rx UE-3 receives data packets from Tx UE-1, but Rx UE-3 cannot send an ACK / NACK response to Tx UE-1. Additionally, Rx UE-3 needs to use other broadcast destination L2 IDs to exchange group information with Tx UE-1 / Rx UE-2.

[0164] At time t14, Rx UE-2 decides to leave the group. During the DRX activation time, Rx UE-2 exchanges group leaving information with Tx UE-1 / Rx UE-3, and completes the entire group leaving process at time t15. Afterwards, Tx UE-1 sends a data packet, and Rx UE-3, upon receiving the data packet, will send an ACK / NACK response to Tx UE-1.

[0165] It is worth noting that before Rx UE-2 completes the leave group process (i.e., during the t14 and t15 group management periods), Rx UE-2 receives a data packet from Tx UE-1. Although Rx UE-2 is no longer interested in the received data packet, Rx UE-3 is obligated to send an ACK / NACK to Tx UE-1.

[0166] Optionally, during the t14 and t15 group management periods, when Rx UE-2 receives a data packet from Tx UE-1, Rx UE-2 decodes the SCI and learns that the received data packet belongs to the multicast. Rx UE-2 only needs to send an ACK back to Tx UE-1. Rx UE-2 does not need to continue decoding the data information specified by the SCI.

[0167] It should be noted that this embodiment of the application effectively divides the service initiation period, service duration, and service completion period by utilizing the characteristics of different service time periods, and flexibly controls the PC5 DRX parameters. Before the service starts, the energy-saving UE only uses the Default PC5 DRX with relatively sparse DRX activation time to improve the UE's energy-saving effect; once the service starts, the energy-saving UE will combine the Default PC5 DRX On-duration and Specific PC5 DRX On-duration as the DRX activation time to improve broadcast and multicast communication performance. Finally, when the service is completed, the energy-saving UE will stop using the Specific PC5 DRX On-duration, leaving only the Default PC5 DRX, and return to the more energy-efficient Default PC5 DRX mode, thereby achieving terminal energy saving.

[0168] It should be noted that the data transmission method provided in this application can be executed by a data transmission device, or by a control module within that data transmission device for executing the data transmission method. This application uses the execution of the data transmission method by a data transmission device as an example to illustrate the data transmission device provided in this application.

[0169] like Figure 8 As shown, this application embodiment provides a data transmission device 800, applied at a receiving end, including:

[0170] Configuration module 801 is used to determine the parameter configuration for discontinuous DRX reception based on the period in which the service is located.

[0171] The first receiving module 802 is configured to receive data from the target communication according to the parameters configured.

[0172] The target communication includes broadcast communication or multicast communication.

[0173] Optionally, the configuration module 801 includes at least one of the following:

[0174] The first determining unit is used to determine the duration of using the first DRX as the DRX activation time before the service begins.

[0175] The second determining unit is used to determine, during the business launch period, the duration of using the first DRX and the duration of the second DRX as the DRX activation time.

[0176] The third determining unit is used to determine, after the service is completed, the duration for which the configured second DRX is stopped as the DRX activation time, and the duration for which the first DRX is used as the DRX activation time.

[0177] Optionally, the parameters of the first DRX satisfy at least one of the following:

[0178] The parameters of the first DRX are determined by the location of the receiving end;

[0179] The parameters of the first DRX are pre-configured;

[0180] The parameters of the first DRX are configured by the network-side device.

[0181] Optionally, the second determining unit includes:

[0182] The receiving subunit is used to receive the first data packet during the service startup phase;

[0183] The acquisition subunit is used to acquire the QoS configuration information of the service based on the first data packet.

[0184] The configuration subunit is used to configure the duration of using the first DRX and the duration of using the second DRX as the DRX activation time;

[0185] The duration of the second DRX is indicated by the DRX parameter corresponding to the QoS configuration information.

[0186] Optionally, the receiving subunit is configured to implement at least one of the following:

[0187] During the DRX activation time of the first DRX, at least one first data packet is received. The first data packet is sent by the sender during the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached.

[0188] At least one first data packet is received during each DRX activation time of the first DRX.

[0189] Optionally, when the target communication is multicast communication, the receiving subunit is configured to:

[0190] When the receiving end joins the group, it receives the first data packet from the sending end within the target duration;

[0191] The target duration is the duration of the first DRX closest to the first moment, and the first moment is the moment when the receiver joins the group.

[0192] Optionally, the third determining unit is configured to:

[0193] If the first condition is met, determine the duration of stopping the use of the configured second DRX as the DRX activation time, and determine the duration of using the first DRX as the DRX activation time.

[0194] The first condition includes at least one of the following:

[0195] Upon receiving a first indication message from the sending end, the first indication message is used to instruct the receiving end to stop using the second DRX;

[0196] The first timer timed out.

[0197] Optionally, the method of receiving the first indication information sent by the sending end includes one of the following:

[0198] Receive the first indication information sent by the sender via higher-layer signaling;

[0199] The first indication information was received from the transmitting end via the Media Access Control Layer Control Unit (MAC-CE) signaling.

[0200] Optionally, the first timer is started or restarted when the receiving end receives a new data packet.

[0201] Optionally, when the target communication is multicast communication, the apparatus further includes at least one of the following:

[0202] The second receiving module is used to receive group configuration information sent by the sending end via broadcast during the duration of the first DRX if the group has not been established.

[0203] The third receiving module is used to receive group update information sent by the sending end during the DRX activation time after the group is established.

[0204] Optionally, if the target communication is multicast communication, after the first receiving module receives the data of the target communication, the apparatus further includes at least one of the following:

[0205] The first determining module is used to determine, if the receiving end has not joined the group, not to send a response message for the data back to the sending end;

[0206] The second determining module is used to determine, if the receiving end has not left the group, to send a response message for the data to the sending end.

[0207] It should be noted that by configuring the DRX parameters according to the current period of the service, and receiving broadcast or multicast communication data based on the DRX parameter configuration, dynamic configuration of the DRX can be achieved, thereby ensuring that terminal power consumption can be saved as much as possible.

[0208] The data transmission device in this application embodiment can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. The device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not impose specific limitations.

[0209] The data transmission device provided in this application embodiment can achieve... Figure 1 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0210] This application embodiment also provides a terminal, which is a receiving end, including a processor and a communication interface. The processor is used to determine the parameter configuration for discontinuous DRX reception according to the period of the service; the communication interface is used to receive data of the target communication according to the parameter configuration.

[0211] The target communication includes broadcast communication or multicast communication.

[0212] This terminal embodiment corresponds to the method embodiment described above applied to the receiving end. All implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0213] The terminal 900 is a receiver and includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.

[0214] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 910 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0215] It should be understood that, in this embodiment, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042. The GPU 9041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0216] In this embodiment, the radio frequency unit 901 receives downlink data from the network-side device and processes it for the processor 910; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0217] The memory 909 can be used to store software programs or instructions and various data. The memory 909 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 909 may include high-speed random access memory and non-volatile memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0218] Processor 910 may include one or more processing units; optionally, processor 910 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 910.

[0219] The processor 910 is used to: determine the parameter configuration for discontinuous DRX reception based on the period in which the service is located;

[0220] The radio frequency unit 901 is used to receive data from the target communication according to the parameters configured therein;

[0221] The target communication includes broadcast communication or multicast communication.

[0222] The terminal in this application embodiment configures the DRX parameters according to the current service period and receives broadcast or multicast communication data according to the DRX parameter configuration, thereby achieving dynamic DRX configuration and ensuring that terminal power consumption is saved as much as possible.

[0223] Optionally, the processor 910 is used to implement at least one of the following:

[0224] Before the business begins, determine the duration of the first DRX to be used as the DRX activation time;

[0225] During the business launch phase, determine the duration of the first DRX and the duration of the second DRX as the DRX activation time;

[0226] After the service is completed, determine the duration of the configured second DRX to be stopped as the DRX activation time, and determine the duration of the first DRX to be used as the DRX activation time.

[0227] Optionally, the parameters of the first DRX satisfy at least one of the following:

[0228] The parameters of the first DRX are determined by the location of the receiving end;

[0229] The parameters of the first DRX are pre-configured;

[0230] The parameters of the first DRX are configured by the network-side device.

[0231] Optionally, during the service startup phase, the radio frequency unit 901 is used to receive the first data packet;

[0232] Optionally, processor 910 is used to implement:

[0233] Based on the first data packet, obtain the QoS configuration information of the service;

[0234] Configure the use of the duration of the first DRX and the duration of the second DRX as the DRX activation time;

[0235] The duration of the second DRX is indicated by the DRX parameter corresponding to the QoS configuration information.

[0236] Optionally, the radio frequency unit 901 is used to implement at least one of the following:

[0237] During the DRX activation time of the first DRX, at least one first data packet is received. The first data packet is sent by the sender during the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached.

[0238] At least one first data packet is received during each DRX activation time of the first DRX.

[0239] Optionally, when the target communication is multicast communication, the radio frequency unit 901 is used to:

[0240] When the receiving end joins the group, it receives the first data packet from the sending end within the target duration;

[0241] The target duration is the duration of the first DRX closest to the first moment, and the first moment is the moment when the receiver joins the group.

[0242] Optionally, processor 910 is used to implement:

[0243] If the first condition is met, determine the duration of stopping the use of the configured second DRX as the DRX activation time, and determine the duration of using the first DRX as the DRX activation time.

[0244] The first condition includes at least one of the following:

[0245] Upon receiving a first indication message from the sending end, the first indication message is used to instruct the receiving end to stop using the second DRX;

[0246] The first timer timed out.

[0247] Optionally, the radio frequency unit 901 is configured to perform one of the following:

[0248] Receive the first indication information sent by the sender via higher-layer signaling;

[0249] The first indication information was received from the transmitting end via the Media Access Control Layer Control Unit (MAC-CE) signaling.

[0250] Optionally, the first timer is started or restarted when the receiving end receives a new data packet.

[0251] Optionally, if the target communication is multicast communication, the processor 910 is further configured to implement at least one of the following:

[0252] If the group is not established, the receiving end receives the group configuration information sent by the sending end via broadcast during the duration of the first DRX.

[0253] After the group is established, the group update information sent by the sender is received during the DRX activation time.

[0254] Optionally, if the target communication is multicast communication, after the radio frequency unit 901 receives the data of the target communication, the processor 910 is further configured to implement at least one of the following:

[0255] If the receiving end has not joined the group, it is determined not to send a response message for the data to the sending end;

[0256] If the receiving end has not left the group, it is determined to send a response message for the data back to the sending end.

[0257] Preferably, this application embodiment also provides a terminal, which is a receiving end, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the various processes of the data transmission method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0258] This application also provides a readable storage medium storing a program or instructions. When executed by a processor, the program or instructions implement various processes of the data transmission method embodiment and achieve the same technical effect. To avoid repetition, these will not be described again here. The computer-readable storage medium may include read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0259] like Figure 10 As shown, to facilitate reception at the receiving end, this application embodiment also provides a data transmission method applied at the sending end, including:

[0260] Step 1001: The transmitting end obtains the parameter configuration of the non-continuous reception DRX of the receiving end, wherein the parameter configuration is determined by the period in which the service is located;

[0261] Step 1002: According to the parameter configuration, the sending end sends the target communication data;

[0262] The target communication includes broadcast communication or multicast communication.

[0263] Optionally, the parameter configuration satisfies at least one of the following:

[0264] Before the service begins, the parameters are configured to use the duration of the first DRX as the DRX activation time;

[0265] During the service launch phase, the parameters are configured to use the duration of the first DRX and the duration of the second DRX as the DRX activation time;

[0266] After the service is completed, the parameter is configured to stop using the configured duration of the second DRX as the DRX activation time and use the duration of the first DRX as the DRX activation time.

[0267] Optionally, the parameters of the first DRX satisfy at least one of the following:

[0268] The parameters of the first DRX are determined by the location of the receiving end;

[0269] The parameters of the first DRX are pre-configured;

[0270] The parameters of the first DRX are configured by the network-side device.

[0271] Optionally, the data sent for target communication according to the DRX configuration includes at least one of the following:

[0272] During the service launch period, the sending end determines the maximum number of transmission opportunities and sends at least one first data packet to the receiving end before the maximum number of transmission opportunities is reached.

[0273] During the service launch period, the sending end sends at least one first data packet to the receiving end during each DRX activation time of the first DRX;

[0274] The first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

[0275] Optionally, if the target communication is multicast communication, the method further includes:

[0276] During the service launch period, when the receiving end joins the group, the sending end sends a first data packet to the receiving end within the target duration;

[0277] Wherein, the target duration is the duration of the first DRX closest to the first moment, the first moment is the moment when the receiving end joins the group, and the first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

[0278] Optionally, the method further includes:

[0279] The sending end sends first indication information to the receiving end;

[0280] The first indication information is used to instruct the receiving end to stop using the second DRX.

[0281] Optionally, sending the first indication information to the receiving end includes at least one of the following:

[0282] The transmitting end sends a first indication information to the receiving end via higher-layer signaling;

[0283] The transmitting end sends a first indication message to the receiving end via the Media Access Control Layer Control Unit (MAC-CE) signaling.

[0284] Optionally, when the target communication is multicast communication, the method further includes at least one of the following:

[0285] If the group is not established, the sending end will broadcast the group configuration information to each receiving end in the group during the duration of the first DRX.

[0286] After the group is established, the sending end sends group update information to each receiving end in the group during the DRX activation time.

[0287] It should be noted that all descriptions of the sending end in the above embodiments are applicable to the embodiments of the data transmission method applied to the sending end, and can achieve the same technical effect, so they will not be repeated here.

[0288] like Figure 11 As shown, this application embodiment also provides a data transmission device 1100, including:

[0289] The acquisition module 1101 is used to acquire the parameter configuration of the discontinuous reception DRX at the receiving end, wherein the parameter configuration is determined by the period in which the service is located;

[0290] The first sending module 1102 is used to send data for target communication according to the parameter configuration.

[0291] The target communication includes broadcast communication or multicast communication.

[0292] Optionally, the parameter configuration satisfies at least one of the following:

[0293] Before the service begins, the parameters are configured to use the duration of the first DRX as the DRX activation time;

[0294] During the service launch phase, the parameters are configured to use the duration of the first DRX and the duration of the second DRX as the DRX activation time;

[0295] After the service is completed, the parameter is configured to stop using the configured duration of the second DRX as the DRX activation time and use the duration of the first DRX as the DRX activation time.

[0296] Optionally, the parameters of the first DRX satisfy at least one of the following:

[0297] The parameters of the first DRX are determined by the location of the receiving end;

[0298] The parameters of the first DRX are pre-configured;

[0299] The parameters of the first DRX are configured by the network-side device.

[0300] Optionally, the first transmitting module 1102 includes at least one of the following:

[0301] The first sending unit is used to determine the maximum number of transmission opportunities during the service startup period, and to send at least one first data packet to the receiving end during the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached.

[0302] The second sending unit is used to send at least one first data packet to the receiving end during the service startup period and each DRX activation time of the first DRX.

[0303] The first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

[0304] Optionally, if the target communication is multicast communication, the data transmission device 1100 further includes:

[0305] The second sending module is used to send a first data packet to the receiving end during the service startup period when the receiving end joins the group within a target duration.

[0306] Wherein, the target duration is the duration of the first DRX closest to the first moment, the first moment is the moment when the receiving end joins the group, and the first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

[0307] Optionally, the data transmission device 1100 further includes:

[0308] The third sending module is used to send the first indication information to the receiving end;

[0309] The first indication information is used to instruct the receiving end to stop using the second DRX.

[0310] Optionally, the third sending module is configured to implement at least one of the following:

[0311] The first instruction information is sent to the receiving end via higher-level signaling;

[0312] The first indication information is sent to the receiving end via the Media Access Control Layer Control Unit (MAC-CE) signaling.

[0313] Optionally, when the target communication is multicast communication, the data transmission device 1100 further includes at least one of the following:

[0314] The fourth sending module is used to send group configuration information to each receiver in the group via broadcast during the duration of the first DRX if the group has not been established.

[0315] The fifth sending module is used to send group update information to each receiver in the group after the group is established and during the DRX activation time.

[0316] It should be noted that this device embodiment corresponds one-to-one with the above method embodiments. All implementations of the above method embodiments are applicable to this device embodiment and can achieve the same technical effect, so they will not be repeated here.

[0317] Preferably, this application embodiment also provides a terminal, which is a transmitting end, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement various processes of the data transmission method embodiment applied to the transmitting end side and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0318] This application also provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, it implements various processes of the data transmission method embodiment applied to the sending end side and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0319] The computer-readable storage medium mentioned above includes, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0320] This application embodiment also provides a terminal, which is a transmitting end, including a processor and a communication interface. The processor is used to obtain the parameter configuration of the non-continuous reception DRX of the receiving end, and the parameter configuration is determined by the period of the service. The communication interface is used to send the target communication data according to the parameter configuration.

[0321] The target communication includes broadcast communication or multicast communication.

[0322] This terminal embodiment corresponds to the data transmission method embodiment on the sending end side described above. All implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and can achieve the same technical effect.

[0323] Specifically, this application embodiment also provides a terminal, which is a transmitting end. Specifically, the structure of this transmitting end is similar to... Figure 9 The structure of the receiver shown is similar, and will not be described in detail here.

[0324] Optionally, the processor is used to implement:

[0325] Obtain the parameter configuration of the discontinuous reception DRX at the receiving end, wherein the parameter configuration is determined by the period in which the service is located;

[0326] The radio frequency unit is used to transmit target communication data according to the parameters configured therein;

[0327] The target communication includes broadcast communication or multicast communication.

[0328] Optionally, the parameter configuration satisfies at least one of the following:

[0329] Before the service begins, the parameters are configured to use the duration of the first DRX as the DRX activation time;

[0330] During the service launch phase, the parameters are configured to use the duration of the first DRX and the duration of the second DRX as the DRX activation time;

[0331] After the service is completed, the parameter is configured to stop using the configured duration of the second DRX as the DRX activation time and use the duration of the first DRX as the DRX activation time.

[0332] Optionally, the parameters of the first DRX satisfy at least one of the following:

[0333] The parameters of the first DRX are determined by the location of the receiving end;

[0334] The parameters of the first DRX are pre-configured;

[0335] The parameters of the first DRX are configured by the network-side device.

[0336] Optionally, the radio frequency unit is used to implement at least one of the following:

[0337] During the service launch period, determine the maximum number of transmission opportunities, and before the maximum number of transmission opportunities is reached, send at least one first data packet to the receiving end during the DRX activation time of the first DRX.

[0338] During the service launch period, at least one first data packet is sent to the receiving end during each DRX activation time of the first DRX.

[0339] The first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

[0340] Optionally, if the target communication is multicast communication, the radio frequency unit is further configured to:

[0341] During the service launch period, when the receiving end joins the group, a first data packet is sent to the receiving end within the target duration.

[0342] Wherein, the target duration is the duration of the first DRX closest to the first moment, the first moment is the moment when the receiving end joins the group, and the first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

[0343] Optionally, the radio frequency unit is also used for:

[0344] Send the first instruction information to the receiving end;

[0345] The first indication information is used to instruct the receiving end to stop using the second DRX.

[0346] Optionally, the radio frequency unit is also used to implement at least one of the following:

[0347] The first instruction information is sent to the receiving end via higher-level signaling;

[0348] The first indication information is sent to the receiving end via the Media Access Control Layer Control Unit (MAC-CE) signaling.

[0349] Optionally, when the target communication is multicast communication, the radio frequency unit may further be implemented in at least one of the following:

[0350] If the group is not established, during the duration of the first DRX, the group configuration information is broadcast to each receiver in the group;

[0351] After the group is established, group update information is sent to each receiver in the group during the DRX activation time.

[0352] It should be noted that the information transmission device used for the sending end and the receiving end in the embodiments of this application can be set in the same device. That is to say, the device can realize both the function of sending information and the function of receiving information.

[0353] Optional, such as Figure 12 As shown, this application embodiment also provides a communication device 1200, including a processor 1201, a memory 1202, and a program or instructions stored in the memory 1202 and executable on the processor 1201. For example, when the communication device 1200 is a receiving end, the program or instructions executed by the processor 1201 implement the various processes of the data transmission method embodiment applied to the receiving end described above, and achieve the same technical effect. When the communication device 1200 is a sending end, the program or instructions executed by the processor 1201 implement the various processes of the data transmission method embodiment applied to the sending end described above, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0354] The terminal involved in the embodiments of this application can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The name of the terminal device may differ in different systems; for example, in a 5G system, the terminal device can be called a User Equipment (UE). The wireless terminal device can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. These exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0355] The network-side equipment involved in the embodiments of this application can be a base station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a base station in a future 5G network, etc., and is not limited thereto.

[0356] Network-side devices and terminals can each use one or more antennas for Multiple-Input Multiple-Output (MIMO) transmission. MIMO transmission can be Single-User MIMO (SU-MIMO) or Multiple-User MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, pre-coding transmission, or beamforming transmission, etc.

[0357] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0358] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0359] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0360] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0361] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A data transmission method, characterized in that, include: The receiving end determines the parameter configuration for discontinuous DRX reception based on the period in which the service is located; According to the parameter configuration, the receiving end receives the target communication data; The target communication includes: broadcast communication or multicast communication; The receiving end determines the parameter configuration for discontinuous DRX reception based on the current service period, including: Before the business begins, determine the duration of the first DRX to be used as the DRX activation time; During the business launch phase, determine the duration of the first DRX and the duration of the second DRX as the DRX activation time; The first DRX is the default PC5 DRX.

2. The method according to claim 1, characterized in that, The receiving end determines the parameter configuration for discontinuous DRX reception based on the service period, and further includes: After the service is completed, determine the duration of the configured second DRX to be stopped as the DRX activation time, and determine the duration of the first DRX to be used as the DRX activation time.

3. The method according to claim 1, characterized in that, The parameters of the first DRX satisfy at least one of the following: The parameters of the first DRX are determined by the location of the receiving end; The parameters of the first DRX are pre-configured; The parameters of the first DRX are configured by the network-side device.

4. The method according to claim 1, characterized in that, During the business launch phase, determine the duration of the first DRX and the duration of the second DRX as the DRX activation time, including: During the service startup phase, the receiving end receives the first data packet; Based on the first data packet, the receiving end obtains the QoS configuration information of the service; The receiver is configured to use the duration of the first DRX and the duration of the second DRX as the DRX activation time; The duration of the second DRX is indicated by the DRX parameter corresponding to the QoS configuration information.

5. The method according to claim 4, characterized in that, The receiving end receives a first data packet, including at least one of the following: During the DRX activation time of the first DRX, the receiving end receives at least one first data packet, which is sent by the sending end during the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached. The receiving end receives at least one first data packet during each DRX activation time of the first DRX.

6. The method according to claim 4, characterized in that, In the case that the target communication is multicast communication, the receiving end receives the first data packet, including: When the receiving end joins the group, the receiving end receives the first data packet from the sending end within the target duration; The target duration is the duration of the first DRX closest to the first moment, and the first moment is the moment when the receiver joins the group.

7. The method according to claim 2, characterized in that, The step of determining to stop using the configured second DRX duration as the DRX activation time after the service is completed, and determining to use the first DRX duration as the DRX activation time, includes: If the first condition is met, determine the duration of stopping the use of the configured second DRX as the DRX activation time, and determine the duration of using the first DRX as the DRX activation time. The first condition includes at least one of the following: The receiving end receives a first indication information sent by the sending end, the first indication information being used to instruct the receiving end to stop using the second DRX; The first timer timed out.

8. The method according to claim 7, characterized in that, The receiving end receives the first indication information sent by the sending end, including one of the following: The receiving end receives the first indication information sent by the sending end via higher-layer signaling; The receiving end receives the first indication information sent by the sending end through the Media Access Control Layer Control Unit (MAC-CE) signaling.

9. The method according to claim 7, characterized in that, When the receiving end receives a new data packet, the first timer starts or restarts.

10. The method according to claim 1, characterized in that, When the target communication is multicast communication, the method further includes at least one of the following: If the group is not established, the receiving end receives the group configuration information sent by the sending end via broadcast during the duration of the first DRX. After the group is established, the receiving end receives the group update information sent by the sending end during the DRX activation time.

11. The method according to claim 1, characterized in that, When the target communication is multicast communication, after the receiving end receives the data of the target communication, the method further includes at least one of the following: If the receiving end has not joined the group, the receiving end determines not to send a response message for the data to the sending end; If the receiving end does not leave the group, the receiving end determines to send a response message to the sending end regarding the data.

12. A data transmission method, characterized in that, include: The sending end obtains the parameter configuration of the non-continuous reception DRX from the receiving end, and the parameter configuration is determined by the period in which the service is located; According to the parameter configuration, the sending end sends the target communication data; The target communication includes: broadcast communication or multicast communication; The parameter configuration satisfies the following: Before the service begins, the parameters are configured to use the duration of the first DRX as the DRX activation time; During the service launch phase, the parameters are configured to use the duration of the first DRX and the duration of the second DRX as the DRX activation time; The first DRX is the default PC5 DRX.

13. The method according to claim 12, characterized in that, The parameter configuration also satisfies: After the service is completed, the parameter is configured to stop using the configured duration of the second DRX as the DRX activation time and use the duration of the first DRX as the DRX activation time.

14. The method according to claim 12, characterized in that, The parameters of the first DRX satisfy at least one of the following: The parameters of the first DRX are determined by the location of the receiving end; The parameters of the first DRX are pre-configured; The parameters of the first DRX are configured by the network-side device.

15. The method according to claim 12, characterized in that, The data sent for target communication according to the parameter configuration includes at least one of the following: During the service launch period, the sending end determines the maximum number of transmission opportunities and sends at least one first data packet to the receiving end before the maximum number of transmission opportunities is reached. During the service launch period, the sending end sends at least one first data packet to the receiving end during each DRX activation time of the first DRX; The first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

16. The method according to claim 12, characterized in that, When the target communication is multicast communication, the method further includes: During the service launch period, when the receiving end joins the group, the sending end sends a first data packet to the receiving end within the target duration; Wherein, the target duration is the duration of the first DRX closest to the first moment, the first moment is the moment when the receiving end joins the group, and the first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

17. The method according to claim 12, characterized in that, Also includes: The sending end sends first indication information to the receiving end; The first indication information is used to instruct the receiving end to stop using the second DRX.

18. The method according to claim 17, characterized in that, The sending end sends first indication information to the receiving end, including at least one of the following: The transmitting end sends a first indication information to the receiving end via higher-layer signaling; The transmitting end sends a first indication message to the receiving end via the Media Access Control Layer Control Unit (MAC-CE) signaling.

19. The method according to claim 12, characterized in that, When the target communication is multicast communication, the method further includes at least one of the following: If the group is not established, the sending end will broadcast the group configuration information to each receiving end in the group during the duration of the first DRX. After the group is established, the sending end sends group update information to each receiving end in the group during the DRX activation time.

20. A data transmission device, applied at a receiving end, characterized in that, include: The configuration module is used to determine the parameter configuration for discontinuous DRX reception based on the period in which the service is located. The first receiving module is configured to receive data from the target communication according to the parameters. The target communication includes: broadcast communication or multicast communication; The configuration module includes: The first determining unit is used to determine the duration of using the first DRX as the DRX activation time before the service begins. The second determining unit is used to determine, during the business launch period, the duration of using the first DRX and the duration of the second DRX as the DRX activation time. The first DRX is the default PC5 DRX.

21. The apparatus according to claim 20, characterized in that, The configuration module also includes: The third determining unit is used to determine, after the service is completed, the duration for which the configured second DRX is stopped as the DRX activation time, and the duration for which the first DRX is used as the DRX activation time.

22. The apparatus according to claim 20, characterized in that, The parameters of the first DRX satisfy at least one of the following: The parameters of the first DRX are determined by the location of the receiving end; The parameters of the first DRX are pre-configured; The parameters of the first DRX are configured by the network-side device.

23. The apparatus according to claim 20, characterized in that, The second determining unit includes: The receiving subunit is used to receive the first data packet during the service startup phase; The acquisition subunit is used to acquire the QoS configuration information of the service based on the first data packet. The configuration subunit is used to configure the duration of using the first DRX and the duration of using the second DRX as the DRX activation time; The duration of the second DRX is indicated by the DRX parameter corresponding to the QoS configuration information.

24. The apparatus according to claim 23, characterized in that, The receiving subunit is configured to implement at least one of the following: During the DRX activation time of the first DRX, at least one first data packet is received. The first data packet is sent by the sender during the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached. At least one first data packet is received during each DRX activation time of the first DRX.

25. The apparatus according to claim 23, characterized in that, In the case that the target communication is multicast communication, the receiving subunit is configured to: When the receiving end joins the group, it receives the first data packet from the sending end within the target duration; The target duration is the duration of the first DRX closest to the first moment, and the first moment is the moment when the receiver joins the group.

26. The apparatus according to claim 21, characterized in that, The third determining unit is used for: If the first condition is met, determine the duration of stopping the use of the configured second DRX as the DRX activation time, and determine the duration of using the first DRX as the DRX activation time. The first condition includes at least one of the following: Upon receiving a first indication message from the sending end, the first indication message is used to instruct the receiving end to stop using the second DRX; The first timer timed out.

27. The apparatus according to claim 26, characterized in that, The method of receiving the first indication information sent by the sending end includes one of the following: Receive the first indication information sent by the sender via higher-layer signaling; The first indication information was received from the transmitting end via the Media Access Control Layer Control Unit (MAC-CE) signaling.

28. The apparatus according to claim 26, characterized in that, When the receiving end receives a new data packet, the first timer starts or restarts.

29. The apparatus according to claim 20, characterized in that, When the target communication is multicast communication, the apparatus further includes at least one of the following: The second receiving module is used to receive group configuration information sent by the sending end via broadcast during the duration of the first DRX if the group has not been established. The third receiving module is used to receive group update information sent by the sending end during the DRX activation time after the group is established.

30. The apparatus according to claim 20, characterized in that, In the case that the target communication is multicast communication, after the first receiving module receives the data of the target communication, the apparatus further includes at least one of the following: The first determining module is used to determine, if the receiving end has not joined the group, not to send a response message for the data back to the sending end; The second determining module is used to determine, when the receiving end has not left the group, to send a response message for the data back to the sending end.

31. A data transmission device, applied at a transmitting end, characterized in that, include: The acquisition module is used to acquire the parameter configuration of the discontinuous reception DRX at the receiving end, wherein the parameter configuration is determined by the period in which the service is located; The first sending module is used to send data for target communication according to the parameter configuration. The target communication includes: broadcast communication or multicast communication; The parameter configuration satisfies the following: Before the service begins, the parameters are configured to use the duration of the first DRX as the DRX activation time; During the service launch phase, the parameters are configured to use the duration of the first DRX and the duration of the second DRX as the DRX activation time; The first DRX is the default PC5 DRX.

32. The apparatus according to claim 31, characterized in that, The parameter configuration also satisfies: After the service is completed, the parameter is configured to stop using the configured duration of the second DRX as the DRX activation time and use the duration of the first DRX as the DRX activation time.

33. The apparatus according to claim 31, characterized in that, The parameters of the first DRX satisfy at least one of the following: The parameters of the first DRX are determined by the location of the receiving end; The parameters of the first DRX are pre-configured; The parameters of the first DRX are configured by the network-side device.

34. The apparatus according to claim 31, characterized in that, The first transmitting module includes at least one of the following: The first sending unit is used to determine the maximum number of transmission opportunities during the service startup period, and to send at least one first data packet to the receiving end during the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached. The second sending unit is used to send at least one first data packet to the receiving end during the service startup period and each DRX activation time of the first DRX. The first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

35. The apparatus according to claim 31, characterized in that, When the target communication is multicast communication, the apparatus further includes: The second sending module is used to send a first data packet to the receiving end during the service startup period when the receiving end joins the group within a target duration. Wherein, the target duration is the duration of the first DRX closest to the first moment, the first moment is the moment when the receiving end joins the group, and the first data packet is used to assist the receiving end in configuring DRX parameters during the service startup period.

36. The apparatus according to claim 31, characterized in that, Also includes: The third sending module is used to send the first indication information to the receiving end; The first indication information is used to instruct the receiving end to stop using the second DRX.

37. The apparatus according to claim 36, characterized in that, The third sending module is used to implement at least one of the following: The first instruction information is sent to the receiving end via higher-level signaling; The first indication information is sent to the receiving end via the Media Access Control Layer Control Unit (MAC-CE) signaling.

38. The apparatus according to claim 31, characterized in that, When the target communication is multicast communication, the apparatus further includes at least one of the following: The fourth sending module is used to send group configuration information to each receiver in the group via broadcast during the duration of the first DRX if the group has not been established. The fifth sending module is used to send group update information to each receiver in the group after the group is established and during the DRX activation time.

39. A terminal, wherein the terminal is a receiving end, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the data transmission method as described in any one of claims 1 to 11.

40. A terminal, wherein the terminal is a transmitting end, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the data transmission method as described in any one of claims 12 to 19.

41. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the data transmission method as described in any one of claims 1-19.

Images