WO2022267948A1 - 数据传输方法、装置及终端 - Google Patents
数据传输方法、装置及终端 Download PDFInfo
- Publication number
- WO2022267948A1 WO2022267948A1 PCT/CN2022/098897 CN2022098897W WO2022267948A1 WO 2022267948 A1 WO2022267948 A1 WO 2022267948A1 CN 2022098897 W CN2022098897 W CN 2022098897W WO 2022267948 A1 WO2022267948 A1 WO 2022267948A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- drx
- receiving end
- duration
- service
- activation time
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 135
- 230000005540 biological transmission Effects 0.000 title claims abstract description 81
- 230000006854 communication Effects 0.000 claims abstract description 179
- 238000004891 communication Methods 0.000 claims abstract description 178
- 230000004913 activation Effects 0.000 claims description 119
- 230000011664 signaling Effects 0.000 claims description 27
- 230000004044 response Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 6
- 238000001994 activation Methods 0.000 description 81
- 230000008569 process Effects 0.000 description 40
- 238000007726 management method Methods 0.000 description 28
- 230000006870 function Effects 0.000 description 18
- 230000000694 effects Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 12
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 8
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 8
- 230000007704 transition Effects 0.000 description 7
- 230000008859 change Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 239000003795 chemical substances by application Substances 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000002360 preparation method Methods 0.000 description 2
- 241000699670 Mus sp. Species 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present application belongs to the communication field, and in particular relates to a data transmission method, device and terminal.
- the parameters can be configured through the quality of service (Quality of Service, QoS) profile (Profile) required by different services, and the DRX offset (Offset) parameter can be configured through the service-related destination layer 2 identification (Destination L2 ID) to configure. Therefore, the broadcast or multicast side link interface (PC5) DRX configuration is implemented through the combination of QoS Profile and Destination L2 ID.
- QoS Quality of Service
- Profile Quality of Service
- Offset service-related destination layer 2 identification
- the broadcast or multicast receiving terminal (Receive UE, Rx UE) cannot pre-acquire the "on-going" (that is, "on-going") service of the surrounding sending terminal (Transmit UE, Tx UE) QoS Profile information, so the Rx UE can only implement DRX operations through the QoS Profile information of the service it is "interested in”.
- user equipment User Equipment, UE, also known as terminal
- UE can receive default side link interface discontinuous reception (Default PC5 DRX) configuration information from the access and mobility management function (Access and Mobility Management Function, AMF)
- AMF Access and Mobility Management Function
- the UE can receive PQI-related special side link interface discontinuous reception (Specific PC5 DRX) configuration information from the application function (Application Function, AF)/policy control function (Policy Control function, PCF).
- the vehicle to everything (V2X) layer provides this information to the access layer (Access Stratum, AS), and the AS can combine these PC5 DRX configurations to determine the final DRX configuration. Therefore, it becomes very important for the AS layer to effectively configure the PC5 DRX cycle according to its own business nature/characteristics/time. This requires effective coordination between the Default PC5 DRX configuration and the Specific PC5 DRX configuration in different situations.
- the pre-configured Default PC5 DRX can be associated with the PC5 RAT type, or can also increase the configuration granularity, for example, associated with the V2X service type or PQI. If the V2X service applies its own, independent, and uncoordinated Default PC5 DRX configuration, this will cause the UE to run multiple services at the same time, which will greatly increase the receiving duration of the UE and fail to achieve energy saving effects.
- each UE In multicast or broadcast, there is no corresponding coordination mechanism between UEs at the AS layer, and each UE must determine the final DRX configuration through pre-configuration (outside network coverage) or base station configuration (inside network coverage), which greatly The effect of UE energy saving is reduced. In particular, before the service starts, the UE must determine DRX configuration parameters through the service of interest to receive multicast or broadcast service data packets.
- Embodiments of the present application provide a data transmission method, device, and terminal, which can solve the problem of PC5 DRX parameter configuration in the prior art, which causes high power consumption of the terminal and is not conducive to energy saving of the terminal.
- a data transmission method including:
- the receiving end determines the parameter configuration of the discontinuous reception DRX according to the period of the service
- the receiving end receives the target communication data
- the target communication includes: broadcast communication or multicast communication.
- a data transmission device including:
- the configuration module is used to determine the parameter configuration of discontinuous reception DRX according to the time period of the service
- the first receiving module is configured to receive target communication data according to the parameter configuration
- the target communication includes: broadcast communication or multicast communication.
- a data transmission method including:
- the sending end obtains the discontinuous reception DRX parameter configuration of the receiving end, and the parameter configuration is determined by the period of the service;
- the sending end sends the target communication data
- the target communication includes: broadcast communication or multicast communication.
- a data transmission device including:
- the obtaining module is used to obtain the parameter configuration of the discontinuous reception DRX of the receiving end, and the parameter configuration is determined by the period of the service;
- a first sending module configured to send target communication data according to the parameter configuration
- the target communication includes: broadcast communication or multicast communication.
- a terminal is provided, the terminal is a receiving end, and the terminal includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor, the program or instruction When executed by the processor, the steps of the method according to the first aspect are realized.
- a terminal is provided, the terminal is a receiving end, and includes a processor and a communication interface, wherein the processor is used to determine the parameter configuration of discontinuous reception DRX according to the time period of the service;
- the communication interface is used to receive target communication data according to the parameter configuration
- the target communication includes: broadcast communication or multicast communication.
- a terminal is provided.
- the terminal is a sending end, and includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor.
- the program or instruction is executed by the The steps of the method described in the third aspect are implemented when the processor executes.
- a terminal is provided, the terminal is a sending end, and includes a processor and a communication interface, wherein the processor is used to obtain the discontinuous reception DRX parameter configuration of the receiving end, and the parameter configuration is determined by the The time period is determined; the communication interface is used to send target communication data according to the parameter configuration;
- the target communication includes: broadcast communication or multicast communication.
- a readable storage medium is provided, and programs or instructions are stored on the readable storage medium, and when the programs or instructions are executed by a processor, the steps of the method described in the first aspect are realized, or the steps of the method described in the first aspect are realized, or The steps of the method described in the third aspect.
- a chip in a tenth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions, so as to implement the first aspect or the third aspect The steps of the method.
- a computer program/program product is provided, the computer program/program product is stored in a non-volatile storage medium, and the program/program product is executed by at least one processor to implement the first Aspect or the step of the method described in the third aspect.
- FIG. 1 is a schematic flow diagram of a data transmission method applied to a receiving end according to an embodiment of the present application
- Figure 2 is a schematic diagram of the stage division of the business from the beginning to the end;
- FIG. 3 is a schematic diagram of the DRX activation time set by the receiving end after receiving the data packet from the sending end;
- FIG. 4 is a schematic diagram of the DRX activation time of the sending end and the receiving end in the broadcast communication mode
- Fig. 5 is a schematic diagram of the evolution process of sending and receiving data packets at the sending end and the receiving end;
- Fig. 6 is a schematic diagram of the use process of the data packet receiving timer
- FIG. 7 is a schematic diagram of DRX activation time when a terminal leaves and joins a group in a multicast communication mode
- Fig. 8 is one of the module schematic diagrams of the data transmission device of the embodiment of the present application.
- FIG. 9 is a structural block diagram of a terminal according to an embodiment of the present application.
- FIG. 10 is a schematic flowchart of a data transmission method applied to a sending end according to an embodiment of the present application.
- FIG. 11 is the second schematic diagram of the modules of the data transmission device according to the embodiment of the present application.
- Fig. 12 is a structural block diagram of a communication device according to an embodiment of the present application.
- first, second and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and “second” distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects.
- “and/or” in the description and claims means at least one of the connected objects, and the character “/” generally means that the related objects are an "or” relationship.
- LTE Long Term Evolution
- LTE-Advanced LTE-Advanced
- LTE-A Long Term Evolution-Advanced
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single-carrier Frequency-Division Multiple Access
- system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned system and radio technology, and can also be used for other systems and radio technologies.
- the following description describes the New Radio (New Radio, NR) system for example purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th Generation (6th Generation , 6G) communication system.
- 6th Generation 6th Generation
- the embodiment of the present application provides a data transmission method, including:
- Step 101 the receiving end configures parameters of discontinuous reception DRX according to the time period of the service
- Step 102 receiving target communication data according to the parameter configuration
- the target communication includes: broadcast communication or multicast communication.
- the business mentioned in the embodiment of the present application mainly refers to the V2X business.
- the elapsed time from the beginning to the end of the business can be divided into three stages; ), business continuation period (Service Ongoing) and business completion period (Service Completion).
- the business initiation period can be further subdivided into a preparation period (Preparation) and a transition period (Transition); and the business completion period can be further subdivided into a transition period (Transition) and a termination period (Termination).
- the transition period is to deal with some uncertainties, and the transition period occurs before or after the business continuation period.
- Tx UE the party that sends the service data packet
- Rx UE the party that receives the service data packet
- Tx UE the party that sends the service data packet
- Tx UE the party that receives the service data packet
- Rx UE the party that receives the service data packet
- step 101 includes at least one of the following:
- PC5 DRX it mainly includes: Default PC5 DRX (default PC5 DRX) and Specific PC5 DRX (special PC5 DRX), of course there are other types of DRX, and the embodiment of this application
- the first DRX can refer to Default PC5 DRX
- the second DRX can refer to Specific PC5 DRX.
- the first DRX can also be Sidelink DRX (SL DRX), Specific PC5 DRX or other types of DRX
- the second DRX can also be Default PC5 DRX, SL DRX or other types of DRX, as long as the first DRX and the second DRX Not the same kind of DRX.
- 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 Default PC5 DRX can be configured based on geographic location, that is, when the terminal enters the corresponding geographic location, it will determine the corresponding Default PC5 DRX parameters according to its own geographic location. This method is more effective.
- the network side device can configure the Default PC5 DRX parameters related to the geographical location in advance according to the geographical situation. For example, in the park and its vicinity, the terminal can configure the corresponding Default PC5 DRX parameters so that it can sleep for a long time and only have relatively sparse DRX activation time, so as to effectively achieve the purpose of energy saving.
- the parameters of the first DRX are pre-configured
- the Default PC5 DRX parameters can be fixed and preconfigured, that is, the Default PC5 DRX parameters do not depend on any other factors.
- This method is relatively simple, but the pre-configured DRX parameters must consider the worst case, for example, the DRX Cycle length should be smaller than the minimum packet delay budget (Packet Delay Budget).
- the parameters of the first DRX are configured by the network side device
- the network side device for example, base station
- the network side device configures the parameters of Default PC5 DRX.
- the base station provides Default PC5 DRX parameters to the terminal by broadcasting a System Information Block (SIB).
- SIB System Information Block
- the terminal will always run a configured Default PC5 DRX. Unless Default PC5 DRX is reconfigured, the terminal will use the new Default PC5 DRX configuration. For example, the configuration of Default PC5 DRX parameters is determined according to the geographic location. When the terminal changes from one geographic location to another, it will select the Default PC5 DRX parameters related to the new geographic location for DRX configuration.
- the receiving end since the receiving end does not know when the sending end starts 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 only needs to be awakened to receive upper layer signaling information at a minimum.
- an implementation method for performing DRX configuration is:
- the receiving end receives the first data packet
- the receiving end obtains service quality (QoS) configuration information of the service
- the receiving end 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 a DRX parameter corresponding to the QoS configuration information.
- the above QoS configuration information mainly refers to the QoS Profile
- the second DRX parameters are mainly associated with the QoS Profile, that is to say, different QoS Profiles correspond to different second DRX parameters, here DRX
- the parameters can mainly include: side link discontinuous reception duration timer (sl-drx-onDurationTimer), which is the duration at the beginning of the DRX cycle, and its size depends on how many Tx UEs need to transmit data packets, in other words, It depends on the congestion rate (Channel Occupancy Ratio, CR) value; the side link discontinuous reception cycle (sl-drx-Cycle), which depends on the smallest PDB in the QoS Profile configuration file group; the side link discontinuous reception start deviation Shift (sl-drx-StartOffset), which determines the start time of sl-drx-onDuration.
- side link discontinuous reception duration timer sl-drx-onDurationTimer
- the receiving end after the receiving end obtains its own data packet sent by the sending end, it analyzes the QoS Profile in the data packet, obtains the DRX parameters of the second DRX that need to be configured according to the QoS Profile, and sets the duration of the first DRX and The duration of the second DRX indicated by the DRX parameter corresponding to the QoS Profile is used as the DRX activation time, so as to realize the configuration of DRX.
- the application layer of the receiving end decides whether to use the DRX mode. Once the receiving end enters the DRX mode, it will always run Default PC5 DRX. Only after the receiving end obtains the corresponding service QoS information, the receiving end will use both Default PC5 DRX and Special PC5 DRX to implement related V2X services.
- the sending end will send the first data packet (including high-level signaling, etc.) during the duration (On-duration) configured by the Default PC5 DRX of the receiving end. And only when the receiving end receives the first data packet, and then directly or indirectly obtains the QoS Profile information of the corresponding service, the receiving end will start the corresponding Special PC5 DRX. For the receiving end, the process of starting the Special PC5 DRX must be completed within the service start period.
- the direct acquisition of the QoS Profile information of the corresponding service mentioned above refers to: the sending end directly notifies the QoS Profile used by the receiving end through high-level signaling;
- the indirect acquisition of the QoS Profile information of the corresponding service refers to: The sending end determines the QoS Profile, the sending end sends data packets according to the determined QoS Profile, and the receiving end receives the data packets, and then derives the QoS Profile information by receiving the data packet information.
- the receiving end merges the two independent On-durations as the DRX activation time (Merged DRX Active Time). Only at the combined DRX activation time, the sending end will send data packets, and the receiving end will receive data packets.
- PC2 DRX can be configured as Default PC5 DRX and Specific PC5 DRX. Since Default PC5 DRX will always be run, the On-duration time in Default PC5 DRX and Specific PC5 DRX will overlap.
- the receiving end merges two independent On-durations as the DRX activation time (Merged DRX Active Time). Only at the combined DRX activation time, the sending end will send data packets, and the receiving end will receive data packets.
- the receiving end will combine two independent On-durations as the DRX activation time.
- the first case at time t1, if the sender starts the service, the sender will send the first data packet in Default PC5 DRX, and the receiver will obtain the corresponding QoS Profile directly or indirectly after receiving the data packet, and then the receiver will obtain the corresponding QoS Profile according to QoS Profile determines the parameters corresponding to Specific PC5 DRX.
- the receiving end combines the On-duration of Default PC5 DRX and Specific PC5 DRX as the DRX activation time.
- the second case at time t1, if the new member receives the data packet sent by the sender in Default PC5 DRX On-duration, and judges that he is interested in receiving data packets, and decides to join the group as a new member.
- the receiving end of the new member After receiving the data packet, the receiving end of the new member obtains the corresponding QoS Profile information directly or indirectly, and then the receiving end determines the parameters corresponding to Specific PC5 DRX according to the QoS Profile. Finally, the receiver combines the On-duration of Default PC5 DRX and Specific PC5 DRX as the DRX activation time.
- the On-duration time of Default PC5 DRX is much shorter than that of Special PC5 DRX.
- different broadcast and multicast V2X communication processes are also different, so the operation of Default PC5 DRX also needs to be considered separately.
- the broadcast mode between terminals is determined by the application layer.
- the establishment of the broadcast mode and the sending and receiving of data packets consist of the following three steps:
- Step 1 The application layer at the receiving end must first determine the destination L2 ID for broadcast reception, and then the application layer at the receiving end will pass the destination L2 ID information to the AS layer at the receiving end through the V2X layer.
- Step 2 The application layer at the sending end provides the data unit to the V2X layer, and at the same time provides the QoS Profile requirements of the data unit.
- the sender uses the self-allocation method to determine the destination L2 ID for broadcast, and then the sender determines the PC5 QoS Profile of the broadcast service.
- Step 3 The sender uses the source L2 ID (Source L2 ID) and the destination L2 ID to send the V2X service data packet. After receiving the data packet, the receiving end will confirm the destination L2 ID. If the destination L2 ID matches the destination L2 ID received by its own broadcast, the receiving end believes that the received data packet is the data packet it needs.
- Source L2 ID Source L2 ID
- the receiving end After receiving the data packet, the receiving end will confirm the destination L2 ID. If the destination L2 ID matches the destination L2 ID received by its own broadcast, the receiving end believes that the received data packet is the data packet it needs.
- Each receiving end can have multiple interested destination L2 IDs for broadcast reception, while the sending end only relies on one or several destination L2 IDs for broadcast service during a certain period of time when the service occurs.
- the receiving end enters DRX mode, if the PC5 DRX parameters of the receiving end only depend on the pre-configured QoS Profile and destination L2 ID, most of the receiving work will be meaningless, and the power consumption of the receiving end will definitely become a problem.
- this application considers the following method: once the sending end starts the service, the sending end first uses the Default PC5 DRX configuration to generate data packets during the service start cycle.
- the implementation of receiving the first data packet includes at least one of the following:
- the receiving end receives at least one first data packet
- the first data packet is sent by the sending end within the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached;
- the V2X layer or AS layer of the sending end determines the maximum number of transmission opportunities, and before reaching the maximum number of transmission opportunities, the sending end continuously broadcasts data packets to the receiving end within the time of Default PC5 DRX On-duration.
- the receiver After receiving the data packet sent by the sender, the receiver confirms the destination L2 ID, and obtains the QoS Profile information directly or indirectly.
- the receiving end determines the Specific PC5 DRX parameters corresponding to the relevant service, and then the receiving end combines Default PC5 DRX On-duration and Specific PC5 DRX On-duration as the DRX activation time.
- the advantage of this implementation is that the window of the V2X service start-up period is constant, and the sender defaults that all receivers have obtained the destination L2 ID and QoS Profile information of the corresponding service during the service start-up period. Entering the business continuation period, the sending end does not need to consider the specific PC5 DRX configuration of the receiving end. So the overall is relatively simple. However, the sending end is constantly moving, and the receiving end that needs to receive the broadcast service is also constantly changing with time. Therefore, this method is relatively poor in adapting to changes in the broadcast service.
- the new receiving end When the new receiving end is close to the sending end, since the new receiving end will receive data packets during Default PC5 DRX On-duration, the new receiving end can only start when the sending end sends data packets during Default PC5 DRX On-duration A data packet of a broadcast service is received.
- the receiving end receives at least one first data packet within each DRX activation time of the first DRX;
- the sender when the sender initiates a new broadcast service, in order to ensure that the new receiver can access the broadcast service initiated by the sender at any time, the sender sets each Default PC5 DRX On-duration Data packets must be sent during this period, so that as long as the receiver is awakened in Default PC5 DRX On-duration, the receiver can have the opportunity to join the broadcast service initiated by the sender.
- the sender must send data packets during DRX On-duration.
- the first case is: according to the PDB requirements of the data packets, the sender arranges to send data packets during Default PC5 DRX On-duration ;
- the second case is: according to the PDB requirements of the data packet, the sender must send the data packet before the Default PC5 DRX On-duration. Therefore, in order for the new receiving end to have the opportunity to join the broadcast service initiated by the sending end, the sending end repeatedly sends the same data packet during Default PC5 DRX On-duration.
- the advantages of the above-mentioned two ways of sending data packets are: the integrity of the broadcast service will be better, and the performance of broadcast service reception will not be affected due to the mobility of the sender and receiver. Since this method does not clearly distinguish between the service startup period and the service continuation period, the sender must always pay attention to the integrity of the broadcast service, and the burden on the V2X layer or AS layer at the sender is correspondingly relatively large.
- the sending end should enhance the transmission mechanism in Default PC5 DRX On-duration and improve the corresponding transmission performance.
- the sender can consider repeatedly transmitting the same data packet multiple times in Default PC5 DRX On-duration, which helps the receiver quickly and accurately obtain service-related data packets, and directly or indirectly obtain the relevant QoS Profile information.
- the main implementation method of DRX parameter configuration is:
- the first condition includes at least one of the following:
- the receiving end receives first indication information sent by the sending end, where the first indication information is used to instruct the receiving end to stop using the second DRX;
- the receiving end receives the first indication information sent by the sending end, including the following item:
- the receiving end receives the first indication information sent by the sending end through high-layer signaling;
- high-level information is used to send the first indication information.
- the specific implementation process of this situation is: once the application layer of the sending end stops the broadcast service, the sending end notifies the receiving end to stop the Specific PC5 DRX configuration and use through high-level signaling. In this case, the receiver stops Specific PC5 DRX, but Default PC5 DRX will continue to run.
- the disadvantage of this first indication information notification method is: if the receiving end fails to receive or successfully decode the first indication information, the receiving end will not be able to stop Specific PC5 DRX configuration and use.
- the receiving end receives the first indication information sent by the sending end through medium access control layer control element (MAC-CE) signaling;
- MAC-CE medium access control layer control element
- MAC-CE signaling is used to send the first indication information.
- the specific implementation process of this situation is: once the application layer of the sending end stops the broadcast service, the sending end notifies the receiving end to stop the Specific PC5 DRX configuration and use by using the MAC-CE signaling of SL DRX. In this case, the receiver stops Specific PC5 DRX, but Default PC5 DRX will continue to run.
- the disadvantage of this first indication information notification method is: the receiving end fails to receive or successfully decode the MAC-CE signaling carrying the first indication information, and the receiving end will not be able to stop Specific PC5 DRX configuration and use.
- the first timer is started when the receiving end receives a new data packet (when the first timer is not started before, when the receiving end receives a new data packet, start the first timer a timer) or restart (before the first timer has been started, when the receiving end receives a new data packet, the first timer needs to be restarted (restarted)).
- the first timer in the embodiment of the present application is a data packet receiving timer.
- the receiving end uses the data packet receiving timer to stop Specific PC5 DRX configuration and use.
- the specific method is that if the receiving end receives a new data packet from the sending end, the receiving end restarts or starts a data packet receiving 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 at the first time slot after the DRX activation time. If the data packet receiving timer expires, it means that the application layer has no data packets to send, and the receiving end disables Specific PC5 DRX, but Default PC5 DRX will continue to run.
- the advantage of this method is that as long as the sender stops sending new data packets, the receiver will stop using the Specific PC5 DRX configuration. Therefore, this method can realize the energy saving effect at the receiving end.
- V2X application layer (VAE layer and SEAL layer).
- the following information is provided by the V2X application layer to the V2X layer, and then provided by the V2X layer to the AS layer.
- the V2X application layer can provide group identification information (that is, the V2X group identification of the application layer, V2X Group Identifier).
- the V2X application layer can provide V2X application requirements, for example, PC5 QoS Profile parameters. However, if the V2X application layer does not provide corresponding requirements, the V2X layer determines the PC5 QoS Profile parameters by itself.
- the V2X application layer can provide the group size and associated member IDs.
- NAS Non-Access Stratum
- the relevant transmission must be performed in Default PC5 DRX On-duration.
- the receiving end receives the information, that is to say, the relevant communication of the NAS layer at this time can only be carried out by broadcasting, that is to say, in the group (also called the group If the broadcast group) is not established, the receiving end receives the group configuration information sent by the sending end in a broadcast manner within the duration of the first DRX.
- the receiving end when the receiving end joins the group, receives the first data packet from the sending end within the target duration; according to the first data packet, obtain the service quality of the service (QoS) configuration information; configuration uses the duration of 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.
- QoS service quality of the service
- the target duration is the duration of the first DRX closest to the first moment, and the first moment is the moment when the receiving end joins the group.
- the rest of the process is basically the same as that performed by the sender and receiver in the broadcast communication.
- the receiving end receives the initial transmission data packet, the receiving end obtains the relevant QoS Profile directly or indirectly, determines the Specific PC5 DRX configuration parameters, and then merges the On-duration time between Default PC5 DRX and Specific PC5 DRX.
- the application layer of the sending end stops the broadcast service, the sending end uses D11 or D12 in the broadcast communication to stop the Specific PC5 DRX configuration. But Default PC5 DRX will continue to work.
- multicast requires group management.
- multicast mode communication is supported.
- the receiving end only needs to wake up to receive data packets in the On-duration associated with Default PC5 DRX, and its behavior is basically the same as that performed by the sending end and receiving end of broadcast communication;
- the only difference is that the receiving end in multicast needs to check the communication range with the sending end (that is, Communication Range), and the receiving end detects the physical side link control channel (PSCCH) sent from the sending end, that is, the first stage SCI (1st Stage SCI) and physical side link shared channel (PSSCH), that is, the second stage SCI (2nd Stage SCI).
- PSCCH physical side link control channel
- PSSCH physical side link shared channel
- the receiving end will first determine whether the destination L2 ID matches; if they match, the receiving end needs to determine whether the sending end is within the communication range.
- the receiving end Only when the sending end is within the communication range, the receiving end will determine that the received data packet is what it wants data pack. Then, the receiving end will directly or indirectly obtain the relevant QoS Profile information according to the data packet, and then activate the Specific PC5 DRX configuration. Finally, the receiver combines Default PC5 DRX On-duration and Specific PC5 DRX On-duration as the DRX activation time.
- the sender needs to initiate the multicast service, but the sender also needs to stop the multicast service.
- the sender can use D11 or D12 in the above broadcast communication to stop Specific PC5 DRX configuration.
- the V2X application layer provides the group size and related member IDs, and the V2X layer passes them to the AS layer for multicast service.
- the AS layer receives the multicast control information (group size and member ID)
- the new group member will activate the On-duration associated with Specific PC5 DRX.
- the sender sends NAS information related to new members during Default PC5 DRX On-duration. In other words, the sender must complete the exchange of NAS information related to new members joining the group during Default PC5 DRX On-duration.
- the group members can use the new group member information to perform the HARQ feedback process.
- the group update information sent by the transmitting end is received within the DRX activation time.
- the sender can transmit at any time of the On-Duration of Default PC5 DRX or Specific PC5 DRX Group management information related to group membership. It is worth noting that in this case, the AS layer does not need to know whether the transmitted information belongs to control information or data information.
- NR-V2X For multicast communication, in NR-V2X, the determination of data packet retransmission depends on the HARQ feedback type, and NR-V2X supports two HARQ feedback processes:
- the receiving end fails to decode the corresponding transmission block (Transmission Block, TB) after decoding the relevant PSCCH, the receiving end sends hybrid automatic retransmission on the physical side link feedback channel (Physical Sidelink Feedback Channel, PSFCH) Request non-acknowledgement (HARQ-NACK); otherwise the receiver will not transmit the signal on PSFCH.
- TCH Physical Sidelink Feedback Channel
- HARQ-NACK Request non-acknowledgement
- the receiving end If the receiving end successfully decodes the corresponding TB, the receiving end sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) on PSFCH; if the receiving end does not successfully decode the corresponding TB, the receiving end sends HARQ-NACK on PSFCH . Therefore, the sending end must know the group membership information to judge whether the sent data packet is correctly received by all receiving ends.
- HARQ-ACK Hybrid Automatic Repeat Request Acknowledgment
- the HARQ feedback type of option 1 is for the application layer connectionless group
- the HARQ feedback type of option 2 is for the application layer management group.
- the embodiment of the present application also considers further limiting the HARQ feedback type of option 2 in the case of the application layer management group.
- the HARQ feedback process at the receiving end is associated with the status of the group management.
- the application layer at the sending end should regularly or irregularly update group change information to all group members (new terminals enter the multicast service, or existing terminals leave the multicast service).
- group members use existing group information (ie, group member number and group member ID) to perform the HARQ process of option 2.
- the V2X layer will update the The group information is notified to the AS layer, and the group members use the new group information (ie, the number of group members and the group member ID) to perform the HARQ process of option 2.
- the sender sends the data packet at the nearest On-Duration of Default PC5 DRX.
- the new group member receives the data packet according to the configured Default PC5 DRX On-Duration, directly or indirectly obtains the corresponding QoS Profile information, and then the receiving end combines the Default PC5 DRX On-duration and Specific PC5 DRX On-duration as the DRX activation time .
- the receiving end uses high-level information (such as VAE or SEAL layer information) to notify all group members, and the receiving end completes the process of joining the group for the group members who wish to join the group.
- the AS layer does not know whether the transmitted information belongs to control information or data information. All information exchange is done at the NAS layer.
- At least one of the following is further included:
- the receiving end before the receiving end completes the process of joining the group (that is, during the group management time period), it receives the data packet sent from the sending end, but the receiving end cannot feed back ACK/NACK to the sending end; only the receiving end After using other broadcast destination L2 IDs to exchange group information with group members through broadcast, HARQ feedback can still be performed normally.
- the receiving end receives the data packet sent from the sending end, although the receiving end has processed the received data packet Not interested, but the receiving end is obliged to feed back ACK/NACK to the sending end to complete the HARQ process.
- the Tx UE sends data packets at time t1 (time t1 is in the On-duration of Default PC5 DRX).
- Rx UE-2 did not successfully decode PSCCH and/or PSSCH due to reasons such as poor channel. But other Rx UEs receive the initial data packet, successfully decode the data packet information, and obtain the corresponding QoS Profile information directly or indirectly. Except for Rx UE-2, other Rx UEs determine the configuration of Specific PC5 DRX, and then combine the On-duration of Default PC5 DRX and Specific PC5 DRX as the DRX activation time.
- Rx UE-2 Since Rx UE-2 fails to receive the initial data packet (for example, does not decode SCI correctly), Rx UE-2 will continue to sleep until the next On-duration time associated with the Default PC5 DRX configuration arrives. Rx UE-2 successfully receives the data packet at the On-duration time t6 of Default PC5 DRX, and obtains the corresponding QoS Profile information directly or indirectly. Rx UE-2 determines the configuration of Specific PC5 DRX, and then combines the On-duration of Default PC5 DRX and Specific PC5 DRX as the DRX activation time.
- Rx UE-2 since Rx UE-2 has not decoded the data packet within the first On-duration time, during the interval between time t1 and time t6, Rx UE-2 cannot use the configuration of Specific PC5 DRX to receive data packets , during which some packets will be lost.
- the evolution process of sending and receiving data packets of Tx UE and Rx UE, the UE actions from time t1 to time t6 are respectively:
- the Tx UE application layer data packet arrives, and a new multicast or broadcast service starts.
- the V2X layer in the Tx UE determines the PC5 QoS Profile parameters, assigns the PC5 QoS flow identifier (PC5Flow ID, PQI), and provides the PFI and associated PC5 QoS Profile parameters to the AS layer.
- PC5Flow ID PC5Flow ID, PQI
- the Tx UE transmits the initial data packet within the On-duration of the Default PC5 DRX configuration.
- the Rx UE successfully decodes the initial data packet within the On-duration of the Default PC5 DRX configuration.
- the Rx UE directly or indirectly acquires information about the QoS Profile and determines the Specific PC5 DRX configuration.
- Rx UE combines the On-duration of Default PC5 DRX and Specific PC5 DRX as the DRX activation time and uses it to receive the remaining data packets. It is worth noting that the configuration of Specific PC5 DRX depends on the PC5 QoS Profile parameters, and the PC5 QoS Profile parameters are determined by the AS layer.
- Rx UE-2 receives the data packet of this service within the On-duration of Default PC5 DRX, and Rx UE-2 directly or indirectly obtains the relevant information of QoS Profile, and determines the configuration of Specific PC5 DRX.
- Rx UE-2 combines the On-duration of Default PC5 DRX and Specific PC5 DRX as the DRX activation time and uses it to receive the remaining data packets.
- the implementation of D11 and D12 can be considered by the Rx UE.
- the Rx UE uses the start packet reception timer to stop the Specific PC5 DRX configuration usage. The specific method is that if the Rx UE receives a new data packet from the Tx UE, the Rx UE will (re)start the data packet reception timer.
- the last service data packet arrives at the Tx UE application layer.
- the Tx UE passes the final service data packet to the AS layer through the V2X layer, and the MAC layer of the Tx UE sends the final service data packet at time t8.
- the Rx UE receives the data packet and restarts the data packet reception timer at time t9 (that is, the first time slot after On-duration).
- the Rx UE does not receive any data packets during the running of the data packet receiving timer (that is, the application layer has no data packets to send), and the data packet receiving timer expires at time t10.
- the Rx UE stops the packet reception timer at time t10 and stops the Specific PC5 DRX configuration. But Default PC5 DRX will continue to work.
- the HARQ feedback process of the Rx UE is associated with the group management status.
- the Tx UE application layer shall periodically or aperiodically update group change information (i.e., new UEs join the multicast service, or existing UEs leave the multicast service) to all group members.
- group members use existing group information (ie, group member number and group member ID) to perform the HARQ process of option 2.
- the V2X layer When the group management information changes, and after the Tx UE application layer finishes updating the group change information to all group members (that is, a new UE enters the multicast service, or an existing UE leaves the multicast service), the V2X layer will The updated group information is notified to the AS layer, and the group members use the new group information (ie, the number of group members and the group member ID) to perform the HARQ process of option 2.
- 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. After that, Tx UE-1 sends a data packet to Rx UE-2, and Rx UE-2 will feed back ACK/NACK to Tx UE-1 after receiving the data packet.
- UE-1 is used as Tx UE.
- UE-2 can also be used as Tx UE. In this case, UE-1 will feed back ACK/NACK to UE-2.
- Rx UE-3 receives the data packet sent by Tx UE-1, and successfully decodes PSCCH and PSSCH. Rx UE-3 judges that it is interested in the data packet and decides to join the group. Rx UE-3 obtains QoS Profile information directly or indirectly, determines Specific PC5 DRX configuration, and combines Default PC5 DRX On-duration and Specific PC5 DRX On-duration as DRX activation time. Rx UE-3 exchanges group information with Tx UE-1/Rx UE-2 during the DRX activation time, and completes the whole process of joining the group at time t13. After that, Tx UE-1 sends a data packet, and Rx UE-2 and Rx UE-3 will feed back ACK/NACK to Tx UE-1 after receiving the data packet.
- Rx UE-3 may extend the On-duration time after time t12 to complete exchanging group information with Tx UE-1/Rx UE-2.
- Rx UE-3 receives the data packet sent from Tx UE-1, but Rx UE-3 It is impossible to feed back ACK/NACK to Tx UE-1.
- Rx UE-3 needs to exchange group information with Tx UE-1/Rx UE-2 using other broadcasted destination L2 IDs.
- Rx UE-2 decides to leave the group.
- Rx UE-2 exchanges information about leaving the group with Tx UE-1/Rx UE-3 during the DRX activation time, and completes the entire process of leaving the group at time t15.
- Tx UE-1 sends a data packet, and Rx UE-3 will feed back ACK/NACK to Tx UE-1 after receiving the data packet.
- Rx UE-2 receives the data packet sent from Tx UE-1, although Rx UE-2 Already not interested in the received data packets, but Rx UE-3 is obliged to feed back ACK/NACK to Tx UE-1.
- Rx UE-2 receives the data packet sent 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 feed back ACK to Tx UE-1, and Rx UE-2 does not need to continue decoding the data information specified by SCI.
- the characteristics of different time periods of the service are used to effectively divide the service initiation period, service continuation period and service completion period, and flexibly control the PC5 DRX parameters.
- the energy-saving UE Before the service starts, the energy-saving UE only uses the Default PC5 DRX with sparse DRX activation time to improve the energy-saving effect of the UE; once the service starts, the energy-saving UE will combine Default PC5 DRX On-duration and Specific PC5 DRX On-duration as DRX activation time to improve broadcast and multicast communication performance.
- the energy-saving UE will stop using the Specific PC5 DRX On-duration, leaving only the Default PC5 DRX, and return to the UE's more energy-efficient Default PC5 DRX mode, so as to realize energy saving of the terminal.
- the data transmission method provided in the embodiment of the present application may be executed by a data transmission device, or a control module in the data transmission device for executing the data transmission method.
- the data transmission device provided in the embodiment of the present application is described by taking the execution of the data transmission method by the data transmission device as an example.
- the embodiment of the present application provides a data transmission device 800, which is applied to the receiving end, including:
- Configuration module 801 configured to determine the parameter configuration of discontinuous reception DRX according to the time period of the service
- the first receiving module 802 is configured to receive target communication data according to the parameter configuration
- the target communication includes: broadcast communication or multicast communication.
- the configuration module 801 includes at least one of the following:
- the first determining unit is configured to determine to use the duration of the first DRX as the DRX activation time before the service starts;
- the second determination unit is configured to determine to use the duration of the first DRX and the duration of the second DRX as the DRX activation time during the service startup period;
- the third determining unit is configured to determine to stop using the configured second DRX duration as the DRX activation time after the service is completed, and determine to use the first DRX duration as the DRX activation time.
- 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.
- the second determination unit includes:
- the receiving subunit is configured to receive the first data packet during the service startup period
- An acquisition subunit configured to acquire service quality QoS configuration information of the service according to the first data packet
- the configuration subunit 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 a DRX parameter corresponding to the QoS configuration information.
- the receiving subunit is configured to implement at least one of the following:
- the receiving subunit is configured to:
- the target duration is the duration of the first DRX closest to the first moment, and the first moment is the moment when the receiving end joins the group.
- the third determining unit is configured to:
- the first condition includes at least one of the following:
- the first timer expires.
- the implementation of receiving the first indication information sent by the sending end includes the following one:
- the first indication information sent by the sending end through the MAC-CE signaling of the media access control layer control unit is received.
- the first timer is started or restarted.
- the device when the target communication is multicast communication, the device further includes at least one of the following:
- the second receiving module is configured to receive group configuration information sent by the sending end in a broadcast mode within the duration of the first DRX when the group is not established;
- the third receiving module is configured to receive group update information sent by the sending end within the DRX activation time after the group is established.
- the device when the target communication is multicast communication, after the first receiving module receives the data of the target communication, the device further includes at least one of the following:
- a first determining module configured to determine not to feed back a response message for the data to the sending end when the receiving end has not joined the group
- the second determining module is configured to determine to feed back a response message for the data to the sending end when the receiving end does not leave the group.
- the dynamic configuration of DRX can be realized, thereby ensuring that the savings can be saved as much as possible. terminal power consumption.
- the data transmission device in the embodiment of the present application may be a device, a device with an operating system or an electronic device, or may be a component, an integrated circuit, or a chip in a terminal.
- the apparatus or electronic equipment may be a mobile terminal or a non-mobile terminal.
- the mobile terminal may include but not limited to the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machines or self-service machines, etc., are not specifically limited in this embodiment of the present application.
- the data transmission device provided by the embodiment of the present application can realize each process realized by the method embodiment in FIG. 1 and achieve the same technical effect. To avoid repetition, details are not repeated here.
- the embodiment of the present application also provides a terminal, the terminal is a receiving end, including a processor and a communication interface, the processor is used to determine the parameter configuration of discontinuous reception DRX according to the time period of the service; the communication interface is used to Configure, receive target communication data;
- the target communication includes: broadcast communication or multicast communication.
- FIG. 9 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
- the terminal 900 is a receiving end, including but not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909, and a processing At least some components in the device 910 and the like.
- the terminal 900 can also include a power supply (such as a battery) for supplying power to various components, and the power supply can be logically connected to the processor 910 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions.
- a power supply such as a battery
- the terminal structure shown in FIG. 9 does not constitute a limitation on the terminal.
- the terminal may include more or fewer components than shown in the figure, or combine some components, or arrange different components, which will not be repeated here.
- the input unit 904 may include a graphics processor (Graphics Processing Unit, GPU) 9041 and a microphone 9042, and the graphics processor 9041 is used for the image capture device (such as the image data of the still picture or video obtained by the camera) for processing.
- the display unit 906 may include a display panel 9061, and the display panel 9061 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 two parts, 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 keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
- the radio frequency unit 901 receives the downlink data from the network side device, and processes it to the processor 910; in addition, sends the uplink data to the network side device.
- 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, and the like.
- the memory 909 can be used to store software programs or instructions as well as various data.
- the memory 909 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instructions required by at least one function (such as a sound playback function, an image playback function, etc.) and the like.
- the memory 909 may include a high-speed random access memory, and may also include a nonvolatile memory, wherein the nonvolatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
- ROM Read-Only Memory
- PROM programmable read-only memory
- PROM erasable programmable read-only memory
- Erasable PROM Erasable PROM
- EPROM electrically erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device.
- the processor 910 may include one or more processing units; optionally, the processor 910 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly handle wireless communications, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 910 .
- the processor 910 is used to implement: according to the time period of the service, determine the parameter configuration of the discontinuous reception DRX;
- the radio frequency unit 901 is configured to receive target communication data according to the parameter configuration
- the target communication includes: broadcast communication or multicast communication.
- the terminal in the embodiment of the present application configures DRX parameters according to the time period of the service, and receives broadcast communication or multicast communication data according to the DRX parameter configuration, so as to realize dynamic configuration of DRX, thereby ensuring that the DRX can be configured as much as possible. Save terminal power consumption.
- processor 910 is configured to implement at least one of the following:
- the service After the service is completed, it is determined to stop using the configured second DRX duration as the DRX activation time, and it is determined to use the first DRX duration as the DRX activation time.
- 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.
- the radio frequency unit 901 is used to receive the first data packet
- processor 910 is configured to implement:
- the duration of the second DRX is indicated by a DRX parameter corresponding to the QoS configuration information.
- the radio frequency unit 901 is configured to implement at least one of the following:
- the radio frequency unit 901 is configured to:
- the target duration is the duration of the first DRX closest to the first moment, and the first moment is the moment when the receiving end joins the group.
- processor 910 is configured to implement:
- the first condition includes at least one of the following:
- the first timer expires.
- the radio frequency unit 901 is configured to implement one of the following:
- the first indication information sent by the sending end through the MAC-CE signaling of the media access control layer control unit is received.
- the first timer is started or restarted.
- the processor 910 is further configured to implement at least one of the following:
- the receiving end receives the group configuration information sent by the sending end in a broadcast manner within the duration of the first DRX;
- the group update information sent by the sending end is received within the DRX activation time.
- the processor 910 is further configured to implement at least one of the following:
- the embodiment of the present application also provides a terminal, the terminal is a receiving end, including a processor, a memory, a program or an instruction stored in the memory and operable on the processor, and the program or instruction is processed
- a terminal is a receiving end, including a processor, a memory, a program or an instruction stored in the memory and operable on the processor, and the program or instruction is processed
- the embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by the processor, each process of the embodiment of the data transmission method is realized, and the same technical effect can be achieved , to avoid repetition, it will not be repeated here.
- the computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk, and the like.
- the embodiment of the present application also provides a data transmission method, which is applied to the sending end, including:
- Step 1001 the sending end obtains the discontinuous reception DRX parameter configuration of the receiving end, and the parameter configuration is determined by the time period of the service;
- Step 1002 according to the parameter configuration, the sender sends the target communication data
- the target communication includes: broadcast communication or multicast communication.
- the parameter configuration satisfies at least one of the following:
- the parameter is configured to use the duration of the first DRX as the DRX activation time
- 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 parameters are configured to stop using the configured second DRX duration as the DRX activation time, and use the first DRX duration as the DRX activation time.
- 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.
- the sending target communication data according to the DRX configuration includes at least one of the following:
- the sending end determines the maximum number of transmission opportunities, and sends at least one first data packet to the receiving end within the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached;
- the sending end sends at least one first data packet to the receiving end within each DRX activation time of the first DRX;
- the first data packet is used to assist the receiving end to configure DRX parameters during the service start-up period.
- the method further includes:
- the sending end sends a first data packet to the receiving end within a target duration
- 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
- the first data packet is used to assist the receiving end in DRX parameter configuration is performed during the service start-up period.
- the method 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.
- the sending the first indication information to the receiving end includes at least one of the following:
- the sending end sends the first indication information to the receiving end through high-layer signaling
- the sending end sends the first indication information to the receiving end through a medium access control layer control unit MAC-CE signaling.
- the method further includes at least one of the following:
- the sending end sends group configuration information to each receiving end in the group by broadcasting within the duration of the first DRX;
- the sending end After the group is established, the sending end sends group update information to each receiving end in the group within the DRX activation time.
- the embodiment of the present application also provides a data transmission device 1100, including:
- the obtaining module 1101 is used to obtain the parameter configuration of the discontinuous reception DRX of the receiving end, and the parameter configuration is determined by the period of the service;
- the first sending module 1102 is configured to send target communication data according to the parameter configuration
- the target communication includes: broadcast communication or multicast communication.
- the parameter configuration satisfies at least one of the following:
- the parameter is configured to use the duration of the first DRX as the DRX activation time
- 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 parameters are configured to stop using the configured second DRX duration as the DRX activation time, and use the first DRX duration as the DRX activation time.
- 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.
- the first sending module 1102 includes at least one of the following:
- the first sending unit is configured to determine the maximum number of transmission opportunities during the service startup period, and send at least one first data packet to the receiving end within the DRX activation time of the first DRX before the maximum number of transmission opportunities is reached;
- the second sending unit is configured to send at least one first data packet to the receiving end during each DRX activation time of the first DRX during the service startup period;
- the first data packet is used to assist the receiving end in configuring DRX parameters during the service start-up period.
- the data transmission apparatus 1100 further includes:
- the second sending module is configured to send the first data packet to the receiving end within a target duration when the receiving end joins the group during the service start-up period;
- 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
- the first data packet is used to assist the receiving end in DRX parameter configuration is performed during the service start-up period.
- the data transmission device 1100 further includes:
- a third sending module configured to send first indication information to the receiving end
- the first indication information is used to instruct the receiving end to stop using the second DRX.
- the third sending module is configured to implement at least one of the following:
- the data transmission apparatus 1100 further includes at least one of the following:
- the fourth sending module is configured to send group configuration information to each receiving end in the group by broadcasting within the duration of the first DRX when the group is not established;
- the fifth sending module is configured to send group update information to each receiving end in the group within the DRX activation time after the group is established.
- this device embodiment is a device corresponding to the above-mentioned method embodiment one by one, and all the implementation methods of the above-mentioned method embodiment are applicable to this device embodiment, and can also achieve the same technical effect. This will not be repeated here.
- the embodiment of the present application also provides a terminal, the terminal is a sending end, including a processor, a memory, a program or instruction stored in the memory and operable on the processor, the program or instruction is processed
- a sending end including a processor, a memory, a program or instruction stored in the memory and operable on the processor, the program or instruction is processed
- each process of the embodiment of the data transmission method applied to the sender side can be implemented, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
- the embodiment of the present application also provides a readable storage medium, on which a computer-readable storage medium stores a program or an instruction, and when the program or instruction is executed by a processor, each process of the embodiment of the data transmission method applied to the sending end is implemented, And can achieve the same technical effect, in order to avoid repetition, no more details here.
- the computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk, and the like.
- ROM Read-Only Memory
- RAM Random Access Memory
- the embodiment of the present application also provides a terminal, the terminal is a sending end, including a processor and a communication interface, and the processor is used to obtain the parameter configuration of the discontinuous reception DRX of the receiving end, and the parameter configuration is determined by the period of the service; the communication The interface is used to send target communication data according to the parameter configuration;
- the target communication includes: broadcast communication or multicast communication.
- This terminal embodiment corresponds to the above-mentioned embodiment of the data transmission method on the sending end side, and each implementation process and implementation mode of the above-mentioned method embodiments can be applied to this terminal embodiment, and can achieve the same technical effect.
- the embodiment of the present application also provides a terminal, where the terminal is a sending end.
- the structure of the sending end is similar to the structure of the receiving end shown in FIG. 9 , which will not be repeated here.
- processors are used to implement:
- the parameter configuration is determined by the period of the service
- the radio frequency unit is configured to transmit target communication data according to the parameter configuration
- the target communication includes: broadcast communication or multicast communication.
- the parameter configuration satisfies at least one of the following:
- the parameter is configured to use the duration of the first DRX as the DRX activation time
- 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 parameters are configured to stop using the configured second DRX duration as the DRX activation time, and use the first DRX duration as the DRX activation time.
- 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.
- the radio frequency unit is configured to implement at least one of the following:
- the first data packet is used to assist the receiving end to configure DRX parameters during the service start-up period.
- the radio frequency unit is further configured to:
- 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
- the first data packet is used to assist the receiving end in DRX parameter configuration is performed during the service start-up period.
- the radio frequency unit is also used for:
- the first indication information is used to instruct the receiving end to stop using the second DRX.
- the radio frequency unit is also used to implement at least one of the following:
- the radio frequency unit is also implemented in at least one of the following:
- the information transmission devices applied to the sending end and the receiving end mentioned in the embodiments of the present 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 .
- this embodiment of the present application further provides a communication device 1200, including a processor 1201, a memory 1202, and programs or instructions stored in the memory 1202 and operable on the processor 1201,
- a communication device 1200 including a processor 1201, a memory 1202, and programs or instructions stored in the memory 1202 and operable on the processor 1201
- the communication device 1200 is the receiving end
- the program or instruction is executed by the processor 1201
- the various processes of the above embodiments of the data transmission method applied to the receiving end can be realized, and the same technical effect can be achieved.
- the communication device 1200 is the sending end
- the program or instruction is executed by the processor 1201
- each process of the above-mentioned embodiment of the data transmission method applied to the sending end can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not repeated here. .
- the terminal involved in this embodiment of the present application may be a device that provides voice and/or data connectivity to users, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
- the name of the terminal equipment may be different.
- the terminal equipment may be called User Equipment (User Equipment, UE).
- the wireless terminal equipment can communicate with one or more core networks (Core Network, CN) via the radio access network (Radio Access Network, RAN), and the wireless terminal equipment can be a mobile terminal equipment, such as a mobile phone (or called a "cellular "telephones) and computers with mobile terminal equipment, such as portable, pocket, hand-held, computer built-in or vehicle-mounted mobile devices, which exchange language and/or data with the radio access network.
- a mobile terminal equipment such as a mobile phone (or called a "cellular "telephones) and computers with mobile terminal equipment, such as portable, pocket, hand-held, computer built-in or vehicle-mounted mobile devices, which exchange language and/or data with the radio access network.
- PCS Personal Communication Service
- SIP Session Initiated Protocol
- WLL Wireless Local Loop
- PDA Personal Digital Assistant
- Wireless terminal equipment may also be called system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point , remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), and user device (user device), which are not limited in this embodiment of the application.
- the network side device involved in the embodiment of the present application may be a Base Transceiver Station (BTS for short) in Global System of Mobile communication (GSM for short) or Code Division Multiple Access (CDMA for short), It can also be a base station (NodeB, NB for short) in Wideband Code Division Multiple Access (WCDMA for short), or an evolved base station (Evolutional Node B, eNB or eNodeB for short) in LTE, or a relay station Or an access point, or a base station in a future 5G network, etc., are not limited here.
- BTS Base Transceiver Station
- GSM Global System of Mobile communication
- CDMA Code Division Multiple Access
- NodeB, NB base station
- WCDMA Wideband Code Division Multiple Access
- Evolutional Node B, eNB or eNodeB for short in LTE
- a relay station Or an access point or a base station in a future 5G network, etc.
- MIMO transmission can be single user MIMO (Single User MIMO, SU-MIMO) or multi user MIMO (Multiple User MIMO, MU-MIMO).
- MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or diversity transmission, precoding transmission, or beamforming transmission, etc.
- the embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the above data transmission method embodiment
- the chip 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 above data transmission method embodiment
- chips mentioned in the embodiments of the present application may also be called system-on-chip, system-on-chip, system-on-a-chip, or system-on-a-chip.
- the embodiment of the present application also provides a computer program product, the computer program product is stored in a non-volatile storage medium, and when the computer program product is executed by at least one processor, each process of the above data transmission method embodiment is implemented , and can achieve the same technical effect, in order to avoid repetition, it will not be repeated here.
- the term “comprising”, “comprising” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase “comprising a " does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element.
- the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
- the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
- the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to enable a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in various embodiments of the present application.
- a terminal which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种数据传输方法、装置及终端,属于通信技术领域,本申请实施例的数据传输方法包括:接收端根据业务所处时期,确定非连续接收DRX的参数配置;根据所述参数配置,所述接收端接收目标通信的数据;其中,所述目标通信包括:广播通信或组播通信。
Description
相关申请的交叉引用
本申请主张在2021年06月22日在中国提交的中国专利申请No.202110694229.X的优先权,其全部内容通过引用包含于此。
本申请属于通信领域,特别涉及一种数据传输方法、装置及终端。
新空口(New Radio,NR)侧链路(Sidelink,SL,也称直通链路、直接通信链路、副链路等)广播或组播的非连续接收(Discontinuous Reception,DRX)周期(Cycle)参数可以通过不同的业务所需的服务质量(Quality of Service,QoS)配置文件(Profile)来进行配置,而DRX偏移(Offset)参数可以通过业务相关的目的地层2标识(Destination L2 ID)来进行配置。因此,广播或组播的侧链路接口(PC5)DRX配置是通过QoS Profile和Destination L2 ID的组合来实现的。
但是在业务初始阶段,广播或组播的接收终端(Receive UE,Rx UE)是无法预先获取周围发送终端(Transmit UE,Tx UE)的“正在进行”的(即,“on-going”)业务QoS Profile信息,因此Rx UE只能通过自己“感兴趣”的业务QoS Profile信息来实现DRX的操作。
一般情况下,用户设备(User Equipment,UE,也称终端)可以从接入和移动管理功能(Access and Mobility Management Function,AMF)收到默认侧链路接口非连续接收(Default PC5 DRX)配置信息,而UE可以从应用功能(Application Funtion,AF)/策略控制功能(Policy Control function,PCF)收到PQI相关的特殊侧链路接口非连续接收(Specific PC5 DRX)配置信息。车到万物(vehicle to everything,V2X)层将这些信息提供给接入层(Access Stratum,AS),AS可以结合这些PC5 DRX配置来决定最终的DRX配置。因 此AS层如何根据自己的业务性质/特点/时间有效结合相应的配置PC5 DRX周期就变得非常重要。这需要在不同的情况下对Default PC5 DRX配置和Specific PC5 DRX配置之间进行有效协调。
预配置Default PC5 DRX可以与PC5 RAT类型相关联,或者也可以提高配置粒度,例如,与V2X业务类型或PQI相关联。如果V2X业务应用自己的、独立的、非协调的Default PC5 DRX配置,这会导致UE同时运行多种业务,而使得UE接收持续时间大幅增加,无法达到节能效果。
在组播或广播中,UE间在AS层没有相应的协调机制,每个UE必须通过预配置(网络覆盖外)或基站配置(网络覆盖内)的方法来决定最终的DRX配置,这就大大的降低了UE节能的效果。特别是,UE在业务还没有开始的时间,就必须通过感兴趣的业务确定DRX配置参数来接收组播或广播业务数据包。
发明内容
本申请实施例提供一种数据传输方法、装置及终端,能够解决现有技术中的PC5 DRX参数配置,导致终端功耗较大,不利于终端节能的问题。
第一方面,提供了一种数据传输方法,包括:
接收端根据业务所处时期,确定非连续接收DRX的参数配置;
根据所述参数配置,所述接收端接收目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
第二方面,提供了一种数据传输装置,包括:
配置模块,用于根据业务所处时期,确定非连续接收DRX的参数配置;
第一接收模块,用于根据所述参数配置,接收目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
第三方面,提供了一种数据传输方法,包括:
发送端获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;
根据所述参数配置,所述发送端发送目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
第四方面,提供了一种数据传输装置,包括:
获取模块,用于获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;
第一发送模块,用于根据所述参数配置,发送目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
第五方面,提供了一种终端,所述终端为接收端,该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面,提供了一种终端,所述终端为接收端,包括处理器及通信接口,其中,所述处理器用于根据业务所处时期,确定非连续接收DRX的参数配置;
所述通信接口用于根据所述参数配置,接收目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
第七方面,提供了一种终端,所述终端为发送端,包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第八方面,提供了一种终端,所述终端为发送端,包括处理器及通信接口,其中,所述处理器用于获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;所述通信接口用于根据所述参数配置,发送目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
第九方面,提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤,或者实现如第三方面所述的方法的步骤。
第十方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如第一方 面或第三方面所述的方法的步骤。
第十一方面,提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在非易失的存储介质中,所述程序/程序产品被至少一个处理器执行以实现如第一方面或第三方面所述的方法的步骤。
在本申请实施例中,通过依据业务所处时期,进行DRX的参数配置,并依据DRX的参数配置,接收广播通信或组播通信的数据,以此能够实现DRX的动态配置,进而保证能够尽可能节省终端功耗。
图1是本申请实施例应用于接收端的数据传输方法的流程示意图;
图2是业务从初始到结束的阶段划分示意图;
图3是接收端在接收到发送端的数据包之后,设置的DRX激活时间的示意图;
图4是广播通信方式下,发送端以及接收端的DRX激活时间的示意图;
图5是发送端和接收端的发送和接收数据包的演变过程示意图;
图6是数据包接收计时器的使用过程示意图;
图7是组播通信方式下,终端离开与加入组的情况下的DRX激活时间的示意图;
图8是本申请实施例的数据传输装置的模块示意图之一;
图9是本申请实施例的终端的结构框图;
图10是本申请实施例的应用于发送端的数据传输方法的流程示意图;
图11是本申请实施例的数据传输装置的模块示意图之二;
图12是本申请实施例的通信设备的结构框图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施 例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)系统,还可用于其他无线通信系统,诸如码分多址(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)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用,所描述的技术既可用于以上提及的系统和无线电技术,也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio,NR)系统,并且在以下大部分描述中使用NR术语,但是这些技术也可应用于NR系统应用以外的应用,如第6代(6th Generation,6G)通信系统。
下面结合附图,通过一些实施例及其应用场景对本申请实施例提供的数据传输方法、装置及终端进行详细地说明。
如图1所示,本申请实施例提供一种数据传输方法,包括:
步骤101,接收端根据业务所处时期,进行非连续接收DRX的参数配置;
步骤102,根据所述参数配置,接收目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
需要说明的是,本申请实施例中所说的业务主要指的是V2X业务,如图2所示,业务从初始到结束,经过的时间可以分为三个阶段;即业务启动期(Service Initiation)、业务持续期(Service Ongoing)和业务完成期(Service Completion)。业务启动期可以更细分为准备期(Preparation)和过渡期(Transition);而业务完成期又可细分为过渡期(Transition)和终止期(Termination)。值得注意的是,过渡期是为了处理一些不确定性,过渡期是发生在业务持续期之前或之后。
这里需要说明的是,在终端间进行V2X业务时,发送业务数据包的一方称为发送终端(Tx UE,也可以称为发送端),接收业务数据包的一方称为接收终端(Rx UE,也可以称为接收端)。
需要说明的是,因在业务持续期间以外,由于NR V2X固有特性,PC5 DRX的参数的有效配置还没有成熟解决方案。本申请便是针对广播通信和组播通信在业务启动期和业务完成期如何进行DRX配置提供的解决方案。
可选地,所述步骤101的具体实现包括以下至少一项:
A11、在业务未开始之前,确定使用第一DRX的持续时间作为DRX激活时间;
A12、在业务启动期,确定使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;
A13、在业务完成后,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间。
首先需要说明的是,针对于PC5 DRX,其主要包括:Default PC5 DRX(默认PC5 DRX)和Specific PC5 DRX(特殊PC5 DRX),当然还存在其他类型的DRX,而本申请实施例中所说的第一DRX可以指的是Default PC5 DRX,第二DRX可以指的是Specific PC5 DRX。当然,第一DRX还可以是Sidelink DRX(SL DRX)、Specific PC5 DRX或其他类型的DRX,第二DRX也可以是Default PC5 DRX、SL DRX或其他类型的DRX,只要第一DRX和第二DRX不是同一种DRX即可。
以第一DRX指的是Default PC5 DRX,第二DRX指的是Specific PC5 DRX为例,进一步地,所述第一DRX的参数满足以下至少一项:
B11、所述第一DRX的参数由所述接收端所处的位置确定;
需要说明的是,Default PC5 DRX的参数可以基于地理位置来配置,即当终端进入相应的地理位置,其便会根据自己的地理位置来决定相应的Default PC5 DRX的参数。这种方法比较有效,网络侧设备可以预先根据地理情况,配置与地理位置相关的Default PC5 DRX的参数。例如,在公园里及其附近,终端可以配置相应Default PC5 DRX的参数,使其能够长时间的睡眠,只拥有比较稀疏的DRX激活时间,从而有效的达到节能目的。
B12、所述第一DRX的参数为预配置;
可选地,Default PC5 DRX参数可以被固定预配置,即,Default PC5 DRX参数不依赖其它任何因素。这种方法比较简单,但是被预配置DRX参数必须考虑最坏的情况,例如,DRX Cycle长度要小于最小的数据包延迟预算(Packet Delay Budget)。
B13、所述第一DRX的参数由网络侧设备配置;
可选地,在空闲模式(Idle Mode)或非激活模式(Inactive Mode)的情况下,网络侧设备(例如,基站)配置Default PC5 DRX的参数。例如,基站利用系统信息块(System Information Block,SIB)广播的方式提供Default PC5 DRX的参数给终端。
还需要说明的是,一般情况下,终端会一直运行一种所配置的Default PC5 DRX。除非Default PC5 DRX被重新配置,终端才会使用新的Default PC5 DRX配置。比如,Default PC5 DRX的参数的配置是根据地理位置决定,当终端从一个地理位置改变到另一个地理位置,便会选择和新的地理位置相关的Default PC5 DRX的参数进行DRX配置。
在业务启动期间,由于接收端并不知道发送端何时启动业务,所以接收端既没有相关业务的QoS Profile配置信息,也没有目的地L2 ID,在这种情况下,接收端会被配置Default PC5 DRX,只需要最小限度的被唤醒接收上层信令信息即可。
值得注意的是,接收端必须通过解码每个数据包中的侧链路控制信息(Sidelink Control Information,SCI)来得到目的地L2 ID信息,然后判断接 收的数据包是否属于自己的。如果解码到的目的地L2 ID和自己感兴趣的业务的目的地L2 ID吻合,接收端会继续解码数据包中的数据,从而得到自己所需的信息。可选地,针对于业务启动期,进行DRX配置的一种可以采用的实现方式为:
在业务启动期,所述接收端接收第一数据包;
根据所述第一数据包,所述接收端获取业务的服务质量(QoS)配置信息;
所述接收端配置使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间。
需要说明的是,所述第二DRX的持续时间由与所述QoS配置信息对应的DRX参数所指示。
需要说明的是,上述的QoS配置信息主要指的是QoS Profile,因第二DRX参数主要是与QoS Profile相关联的,也就是说,不同的QoS Profile对应不同的第二DRX参数,这里的DRX参数可以主要包括:侧链路非连续接收持续时间定时器(sl-drx-onDurationTimer),为DRX周期开始时的持续时间,它的大小取决于多少个Tx UE需要传输数据包,换句话说,它取决于拥塞率(Channel Occupancy Ratio,CR)值;侧链路非连续接收周期(sl-drx-Cycle),其取决于QoS Profile配置文件组中最小的PDB;侧链路非连续接收开始偏移(sl-drx-StartOffset),其决定sl-drx-onDuration的开始时间。
本申请实施例中,接收端获取发送端发送的属于自己的数据包后,解析数据包中的QoS Profile,依据QoS Profile获取需要配置的第二DRX的DRX参数,将第一DRX的持续时间以及QoS Profile对应的DRX参数所指示的第二DRX的持续时间作为DRX激活时间,以此实现对DRX的配置。
需要说明的是,接收端的应用层决定是否使用DRX模式,一旦接收端进入DRX模式,便会始终运行Default PC5 DRX。只有在接收端得到相应的业务QoS信息后,接收端会同时使用Default PC5 DRX和Special PC5 DRX来实现相关的V2X业务。发送端会在接收端的Default PC5 DRX配置的持续 时间(On-duration)中发送第一个数据包(包括高层信令等)。而只有在接收端接收到第一个数据包,然后直接或间接获取相应业务的QoS Profile信息,接收端才会启动相应的Special PC5 DRX。对接收端来说,启动Special PC5 DRX的过程必须在业务启动期内完成。
需要说明的是,上述提到的直接获取相应业务的QoS Profile信息指的是:发送端通过高层信令,直接通知接收端所使用的QoS Profile;间接获取相应业务的QoS Profile信息指的是:发送端确定QoS Profile,发送端根据确定的QoS Profile发送数据包,而接收端接收数据包,然后通过接收数据包信息推导出QoS Profile信息。
值得注意的是,由于Default PC5 DRX始终会被运行,因此Default PC5 DRX的On-duration和Special PC5 DRX的On-duration在时间上会重叠。在这种情况下,接收端将两个独立的On-duration合并作为DRX激活时间(Merged DRX Active Time)。只有在合并DRX激活时间,发送端会发送数据包,接收端会接收数据包。
具体应用情况一、
PC2 DRX可以被配置为Default PC5 DRX和Specific PC5 DRX。由于Default PC5 DRX始终会被运行,因此Default PC5 DRX和Specific PC5 DRX中的On-duration时间会重叠。接收端将两个独立的On-duration合并作为DRX激活时间(Merged DRX Active Time)。只有在合并DRX激活时间,发送端会发送数据包,接收端会接收数据包。
如图3所示,针对以下两种情况,接收端会将两个独立的On-duration合并作为DRX激活时间。
第一种情况:在时间t1,如果发送端启动业务,发送端会在Default PC5 DRX发送第一个数据包,接收端接收数据包后直接或间接地获取相应的QoS Profile,然后接收端会根据QoS Profile确定Specific PC5 DRX对应的参数。接收端将Default PC5 DRX和Specific PC5 DRX的On-duration合并作为DRX激活时间。
第二种情况:在时间t1,如果新成员在Default PC5 DRX On-duration接收到发送端发送的数据包,并判断自己对接收数据包业务感兴趣,并决定作为新成员加入组。新成员接收端接收数据包后直接或间接地获取相应的QoS Profile信息,然后接收端会根据QoS Profile确定Specific PC5 DRX对应的参数。最后接收端将Default PC5 DRX和Specific PC5 DRX的On-duration合并作为DRX激活时间。
一般情况下,Default PC5 DRX的On-duration时间比Special PC5 DRX的On-duration时间短很多。另外PC5侧链路上,不同的广播和组播V2X通信过程也有所不同,因此Default PC5 DRX的操作也需要相应分开考虑。
一、针对广播通信
终端间的广播模式是由应用层决定建立的,广播模式的建立和数据包的发送接收由以下三个步骤组成:
步骤一,接收端的应用层首先要确定用于广播接收的目的地L2 ID,然后接收端的应用层会把目的地L2 ID信息通过V2X层传递到接收端的AS层。
步骤二,发送端的应用层向V2X层提供数据单元,并同时提供数据单元QoS Profile需求。发送端利用自分配方法,确定用于广播的目的地L2 ID,然后发送端确定此广播业务的PC5 QoS Profile。
步骤三,发送端使用源L2 ID(Source L2 ID)和目的地L 2 ID发送V2X业务数据包。接收端接收到数据包后会确认目的地L2 ID,如果目的地L2 ID和自己的广播接收的目的地L2 ID相吻合,接收端认为接收到数据包是自己所需的数据包。
每个接收端可以有多个感兴趣的目的地L2 ID用于广播接收,而发送端在业务发生的某一段时间里仅依赖于一个或其中几个目的地L2 ID来进行广播业务。当接收端进入DRX模式,如果接收端的PC5 DRX的参数仅依赖于预配置的QoS Profile和目的地L2 ID的话,则大多数时间的接收工作将没有意义,接收端的功耗必将成为问题。为了有效解决接收端的功耗问题,本申请考虑以下方法:一旦发送端启动业务,发送端就在业务启动周期首先使用 Default PC5 DRX配置发生数据包。为了确保接收端在Default PC5 DRX On-duration期间接收到数据包,获取业务相关的QoS Profile信息,所述接收第一数据包的实现方式包括以下至少一项:
C11、在所述第一DRX的DRX激活时间内,所述接收端接收至少一个第一数据包;
其中,所述第一数据包是由所述发送端在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送的;
也就是说,此种情况下,发送端的V2X层或AS层确定最大传输时机数,在达到最大传输时机数之前,发送端在Default PC5 DRX On-duration的时间内不断向接收端广播数据包。接收端在接收到发送端发来的数据包后,确认目的地L2 ID,并直接或间接的获取QoS Profile信息。根据数据包的业务类型,接收端确定与相关业务对应的Specific PC5 DRX的参数,然后接收端合并Default PC5 DRX On-duration和Specific PC5 DRX On-duration作为DRX激活时间。
需要说明的是,此种实现方式的好处是,V2X业务启动期的窗口是恒定的,发送端默认为所有的接收端在业务启动期已经获取相应业务的目的地L2 ID和QoS Profile信息,一旦进入业务持续期,发送端就不需要再考虑接收端的Specific PC5 DRX配置问题。因此整体比较简单。但是,发送端是在不断移动的,需要接收广播业务的接收端随着时间也在不断的改变,因此,此种方式在广播业务适应变化能力方面相应比较差。当新的接收端接近发送端的时候,由于新的接收端在Default PC5 DRX On-duration才会接收数据包,只有当发送端在Default PC5 DRX On-duration期间发送数据包,新的接收端才能开始接收到广播业务的数据包。
C12、所述接收端在所述第一DRX的每个DRX激活时间内接收至少一个第一数据包;
也就是说,此种情况下,当发送端发起新的广播业务后,发送端为了确保任何时候新的接收端能够接入发送端发起的广播业务,发送端在每个 Default PC5 DRX On-duration期间必须发送数据包,这样接收端只要在Default PC5 DRX On-duration被唤醒,接收端就能有机会加入发送端发起的广播业务。
值得注意的是,发送端在DRX On-duration期间必须发送数据包的情况有两种,第一种情况是:根据数据包的PDB要求,发送端在Default PC5 DRX On-duration期间安排发送数据包;第二种情况是:根据数据包的PDB要求,发送端在Default PC5 DRX On-duration之前必须发送数据包。因此为了让新接收端有机会加入发送端发起的广播业务,发送端在Default PC5 DRX On-duration期间重复发送相同的数据包。
需要说明的是,上述所提到的两种发送数据包的方式的优点是:广播业务的完整性会比较好,不会因为发送端和接收端移动性,而影响广播业务接收性能。由于这种方法不明显区分业务启动期和业务持续期,发送端必须时刻关注广播业务完整性,对发送端V2X层或AS层的负担相应比较大。
可选地,为了提高接收端在Default PC5 DRX On-duration中的数据包检测成功率,发送端应该增强Default PC5 DRX On-duration中的传输机制,并提高相应的传输性能。例如,发送端可以考虑在Default PC5 DRX On-duration中重复多次传输相同的数据包,这样有助于接收端快速和准确地获取业务相关的数据包,并直接或间接地获取QoS Profile的相关信息。
可选地,在业务完成期,DRX的参数配置的主要实现方式为:
在满足第一条件的情况下,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间;
其中,所述第一条件包括以下至少一项:
D11、所述接收端接收到发送端发送的第一指示信息,所述第一指示信息用于指示接收端停止使用所述第二DRX;
可选地,所述接收端接收到发送端发送的第一指示信息,包括以下一项:
D111、所述接收端接收到发送端通过高层信令发送的第一指示信息;
需要说明的是,此种情况下是利用高层信息进行第一指示信息的发送。 此种情况的具体实现过程为:一旦发送端应用层停止广播业务,发送端通过高层信令通知接收端去停止Specific PC5 DRX配置使用。这种情况下,接收端停止Specific PC5 DRX,但是Default PC5 DRX还将继续运行。此种第一指示信息通知方式的缺点是:如果接收端没能接收或没能成功解码到第一指示信息,接收端将无法停止Specific PC5 DRX配置使用。
D112、所述接收端接收到发送端通过媒体接入控制层控制单元(MAC-CE)信令发送的第一指示信息;
需要说明的是,此种情况下是利用MAC-CE信令进行第一指示信息的发送。此种情况的具体实现过程为:一旦发送端的应用层停止广播业务,发送端通过使用SL DRX的MAC-CE信令通知接收端去停止Specific PC5 DRX配置使用。这种情况下,接收端停止Specific PC5 DRX,但是Default PC5 DRX还将继续运行。此种第一指示信息通知方式的缺点是:接收端没能接收或没能成功解码到承载第一指示信息的MAC-CE信令,接收端将无法停止Specific PC5 DRX配置使用。
D12、第一计时器超时;
需要说明的是,所述第一计时器在所述接收端接收到新数据包的情况下,启动(在第一计时器之前未启动时,在接收端接收到新数据包时,启动该第一计时器)或重启(在第一计时器之前已经启动,在接收端接收到新数据包时,需要重新启动(重启)该第一计时器)。
本申请实施例中的第一计时器为数据包接收计时器,在此种情况下,接收端利用数据包接收计时器来停止Specific PC5 DRX配置使用。具体方法是,如果接收端收到来自发送端的新数据包,接收端重启或启动数据包接收计时器。更准确地说,一旦接收端收到来自发送端的新数据包,数据包接收定时器将在DRX激活时间之后的第一个时隙被重启或启动。如果数据包接收计时器到期,说明应用层已经没有数据包可发,则接收端停用Specific PC5 DRX,但是Default PC5 DRX还将继续运行。此种方式的优点是:只要发送端停止发送新数据包,接收端就会停止使用Specific PC5 DRX配置。因此,这种方 法能够实现接收端的节能效果。
二、针对组播通信
由于组播业务中的组管理是在V2X应用层(VAE层和SEAL层)进行的。以下信息由V2X应用层提供给V2X层,然后由V2X层提供给AS层。
第一,V2X应用层可以提供组标识信息(即,应用层的V2X组标识,V2X Group Identifier)。
第二,V2X应用层可以提供V2X应用需求,例如,PC5 QoS Profile参数。但如果V2X应用层没有提供相应的需求,则V2X层自己确定PC5 QoS Profile参数。
第三,V2X应用层可以提供组大小和相关成员ID。
值得注意的是,这些信息需要在非接入层(Non-Access Stratum,NAS)进行通信,也就是意味着,相关传输必须在Default PC5 DRX On-duration中进行。因为接收端在接收到这些信息以前,组播还没有被组建,也就是说,这个时候的NAS层的相关通信,只能采用广播的方式进行,也就是说,在组(也可以称为组播组)未建立的情况下,接收端在所述第一DRX的持续时间内,接收所述发送端通过广播方式发送的组配置信息。
可选地,在此种情况下,在所述接收端加入组时,所述接收端在目标持续时间内接收来自发送端的第一数据包;根据所述第一数据包,获取业务的服务质量(QoS)配置信息;配置使用第一DRX的持续时间以及与所述QoS配置信息对应的DRX参数所指示的第二DRX的持续时间作为DRX激活时间。
需要说明的是,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻。
进一步需要说明的是,一旦组播被组建后,剩下的流程与广播通信中的发送端和接收端执行的过程基本相同。当接收端接收到初始传输数据包后,接收端直接或间接地获取相关的QoS Profile,决定Specific PC5 DRX配置参数,然后合并Default PC5 DRX和Specific PC5 DRX之间的On-duration时间。 当发送端应用层停止广播业务,发送端利用与广播通信中的D11或D12来停止Specific PC5 DRX配置使用,需要说明的是,这种情况下,和广播通信一样,接收端停止Specific PC5 DRX,但是Default PC5 DRX还将继续运行。
这里需要说明的是,组播通信在业务启动期和业务完成期的具体操作与广播通信的具体实现过程完全相同。二者的主要区别在于组播需要组的管理,基于NR V2X支持组播模式通信,组播管理有两种形式,即应用层无连接组管理(Application Layer Connection-less Group)和应用层管理组管理(Application Layer Managed Group),针对不同类型的组播管理形式,应该分别考虑Default PC5 DRX操作。
可选地,在应用层无连接组的情况下,接收端只需要在Default PC5 DRX关联的On-duration中唤醒接收数据包,其行为与广播通信的发送端和接收端执行的行为基本相同;唯一不同的是,组播中的接收端需要查看和发送端之间的通讯范围(即,Communication Range),接收端检测从发送端发送的物理侧链路控制信道(PSCCH),即第一阶段SCI(1st Stage SCI)和物理侧链路共享信道(PSSCH),即第二阶段SCI(2nd Stage SCI)。接收端首先会判断目的地L2 ID是否吻合;如果吻合,接收端需要判断发送端是否在通信范围内,只有发送端是在通信范围内,接收端才会判断接收到的数据包是自己希望的数据包。然后,接收端会根据数据包直接或间接地获取相关的QoS Profile信息,然后激活Specific PC5 DRX配置。最后,接收端合并Default PC5 DRX On-duration和Specific PC5 DRX On-duration作为DRX激活时间。
同样地,发送端需要发起组播业务,但发送端也需要停止组播业务,当发送端应用层停止组播业务的时候,发送端可以使用上述广播通信中的D11或D12来停止Specific PC5 DRX配置。
可选地,在应用层管理组的情况下,V2X应用层提供组大小和相关成员ID,V2X层将它们传递给AS层进行组播业务。在AS层接收到组播控制信息(组大小和成员ID)后,如果有新的组成员加了组播业务,新的组成员将执行与Specific PC5 DRX相关联的On-duration的激活。为了确保在激活过程 中新的组成员也能收到组播控制信息,发送端在Default PC5 DRX On-duration期间发送于新成员相关的NAS信息。也就是说,发送端必须在Default PC5 DRX On-duration期间完成交换与加入组的新成员相关的NAS信息。在确保发送端更新所需要的组信息后,组成员才能使用新组成员信息,来进行HARQ的反馈过程。
可选地,在组建立之后,在所述DRX激活时间内接收发送端发送的组更新信息。
也就是说,当现有的组成员决定离开组时,并且组成员或一部分组成员被配置PC5 DRX的情况下,发送端可以在Default PC5 DRX或Specific PC5 DRX的On-Duration的任意时机,传输组成员相关的组管理信息。值得注意的是,在这种情况下,AS层无需知道传输的信息属于控制信息还是数据信息的。
进一步还需要说明的是,针对于组播通信,在NR-V2X中,数据包重传的确定取决于HARQ反馈类型,NR-V2X支持两个选项的HARQ反馈过程:
选项1、如果接收端在解码相关PSCCH后未能解码相应的传输块(Transmission Block,即TB),则接收端在物理侧链路反馈信道(Physical Sidelink Feedback Channel,PSFCH)上发送混合自动重传请求非确认(HARQ-NACK);否则接收端不会在PSFCH上传输信号。
选项2、如果接收端成功解码相应的TB,接收端在PSFCH上发送混合自动重传请求确认(HARQ-ACK);如果接收端没有成功解码相应的TB,则接收端在PSFCH上发送HARQ-NACK。因此,发送端必须知道组成员信息才能判断发送的数据包是否被所有的接收端正确接收。
值得注意的是,在组播业务中,选项1的HARQ反馈类型是针对应用层无连接组的情况的,而选项2的HARQ反馈类型是针对应用层管理组的情况的。本申请实施例还考虑在应用层管理组的情况下,针对选项2的HARQ反馈类型进行进一步地限定。
接收端的HARQ反馈过程和组管理现状相关联。在组管理期间,发送端 应用层应该向所有组成员定期或不定期更新组变化信息(新的终端进入组播业务,或现有的终端离开组播业务)。在组管理信息没有变化的情况下,组成员使用现存的组信息(即,组成员数和组成员ID)来执行选项2的HARQ过程。在组管理信息发生变化的情况下,并且发送端应用层完成向所有组成员更新组变化信息后(新的终端进入组播业务,或现有的终端离开组播业务),V2X层将更新的组信息通知给AS层,组成员使用新的组信息(即,组成员数和组成员ID)执行选项2的HARQ过程。
可选地,当新的组成员决定加入组时,并且组成员或一部分组成员被配置PC5 DRX的情况下,发送端在最近的Default PC5 DRX的On-Duration时机发送数据包。新组成员根据配置的Default PC5 DRX的On-Duration接收到数据包,直接或间接地获取相应的QoS Profile信息,然后接收端合并Default PC5 DRX On-duration和Specific PC5 DRX On-duration作为DRX激活时间。接收端利用高层信息(如VAE或SEAL层信息)通知所有的组成员,接收端为希望加入组的组成员完成加入组的过程。值得注意的是,在这种情况下,AS层是不知道传输的信息属于控制信息还是数据信息的。所有的信息交互是在NAS层完成的。
可选地,在所述接收发送端发送的目标通信的数据之后,还包括以下至少一项:
E11、在所述接收端未加入组的情况下,确定不反馈针对所述数据的应答消息给所述发送端;
也就是说,接收端在没有完成加入组过程前(即,在组管理时间段),收到从发送端发来的数据包,但是接收端是无法反馈ACK/NACK给发送端的;只有接收端使用其它广播的目的地L2 ID通过广播方式和组成员交换组信息之后,还能正常的进行HARQ反馈。
E12、在所述接收端未离开组的情况下,确定反馈针对所述数据的应答消息给发送端;
也就是说,值得注意的是,接收端在没有完成离开组过程前(即,在组 管理时间段),接收端收到从发送端发来的数据包,虽然接收端已经对接收的数据包不感兴趣,但是接收端有义务反馈ACK/NACK给发送端,从而完成HARQ过程。
下面对本申请的几种应用情况进行举例说明如下。
具体应用情况二、
如图4所示,Tx UE在时间t1中发送数据包(时间t1是在Default PC5 DRX的On-duration中)。Rx UE-2由于信道不良等原因没有成功解码PSCCH和/或PSSCH。但其它Rx UE接收到初始数据包,成功解码数据包信息,并直接或间接地获取相应的QoS Profile信息。除Rx UE-2以外,其它Rx UE决定Specific PC5 DRX的配置,然后将Default PC5 DRX和Specific PC5 DRX的On-duration合并作为DRX激活时间。
由于Rx UE-2初始数据包接收失败(例如,没有正确解码SCI),Rx UE-2将继续保持休眠,一直到Default PC5 DRX配置相关联的下一个On-duration时间到来。Rx UE-2在Default PC5 DRX的On-duration时间t6成功接收到数据包,并直接或间接地获取相应的QoS Profile信息。Rx UE-2决定Specific PC5 DRX的配置,然后将Default PC5 DRX和Specific PC5 DRX的On-duration合并作为DRX激活时间。
值得注意的是,由于Rx UE-2没有解码到第一个On-duration时间内的数据包,所有在时间t1和时间t6间隔中,Rx UE-2无法使用Specific PC5 DRX的配置来接收数据包,在此期间,有一部分数据包将会丢失。
如图5所示,Tx UE和Rx UE的发送和接收数据包的演变过程,从时间t1到时间t6的UE动作分别为:
在时间t1,Tx UE应用层数据包到达,新的组播或广播业务开始。
在时间t2,Tx UE中的V2X层确定PC5 QoS Profile参数,分配PC5 QoS流标识(PC5Flow ID,PQI),并将PFI和关联的PC5 QoS Profile参数提供给AS层。
在时间t3,Tx UE在Default PC5 DRX配置的On-duration内传输初始数 据包。
在时间t4,Rx UE在Default PC5 DRX配置的On-duration内成功解码初始数据包。
在时间t5,Rx UE直接或间接地获取QoS Profile相关信息,并决定Specific PC5 DRX配置。Rx UE将Default PC5 DRX和Specific PC5 DRX的On-duration合并作为DRX激活时间,并用于接收剩余数据包。值得注意的是,Specific PC5 DRX的配置是依赖于PC5 QoS Profile参数,而PC5 QoS Profile参数是由AS层决定的。
在时间t6,Rx UE-2在Default PC5 DRX的On-duration内接收到本业务的数据包,Rx UE-2直接或间接地获取QoS Profile相关信息,并决定Specific PC5 DRX配置。Rx UE-2将Default PC5 DRX和Specific PC5 DRX的On-duration合并作为DRX激活时间,并用于接收剩余数据包。
具体应用情况三、
当Tx UE应用层停止广播或组播业务时,D11、D12的实现方式可以被Rx UE考虑。对于D12,Rx UE利用启动数据包接收计时器来停止Specific PC5 DRX配置使用。具体方法是,如果Rx UE收到来自Tx UE的新数据包,Rx UE会(重新)启动数据包接收计时器。
如图6所示,在时间t7,最后的业务数据包到达Tx UE应用层。Tx UE通过V2X层把最后的业务数据包传递给AS层,Tx UE的MAC层在时间t8,发送最后的业务数据包。Rx UE接收数据包,并在时间t9(即,On-duration后的第一个时隙),重新启动数据包接收定时器。Rx UE在数据包接收定时器定时器运行期间没有收到任何数据包(即,应用层已经没有数据包可发),并在时间t10数据包接收定时器到期。Rx UE在时间t10停止数据包接收定时器,并停止Specific PC5 DRX配置。但是Default PC5 DRX还将继续运行。
值得注意的是,从最后的业务数据包到达Tx UE应用层时间t7,到停止数据包接收定时器时间t10,被考虑为业务停止过渡期,而从时间t10开始考虑为业务终止期。
具体应用情况四、
Rx UE的HARQ反馈过程和组管理现状相关联。在组管理期间,Tx UE应用层应该向所有组成员定期或非定期更新组变化信息(即,新的UE加入组播业务,或现有的UE离开组播业务)。在组管理信息没有变化的情况下,组成员使用现存的组信息(即,组成员数和组成员ID)来执行选项2的HARQ过程。在组管理信息发生变化的情况下,并且Tx UE应用层完成向所有组成员更新组变化信息后(即,新的UE进入组播业务,或现有的UE离开组播业务),V2X层将更新的组信息通知给AS层,组成员使用新的组信息(即,组成员数和组成员ID)执行选项2的HARQ过程。
如图7所示,首先在时间t11,Tx UE-1应用层组建由Tx UE-1和Rx UE-2的组,并且通过V2X层通知AS层。之后,Tx UE-1发送数据包给Rx UE-2,Rx UE-2接收到数据包后会反馈ACK/NACK给Tx UE-1。
值得注意的是,本实施例中,UE-1被作为Tx UE。同样地,UE-2也可以被作为Tx UE。这种情况下,UE-1将反馈ACK/NACK给UE-2。
在时间t12,Rx UE-3接收到Tx UE-1发来的数据包,并成功解码了PSCCH和PSSCH。Rx UE-3判断对数据包感兴趣,并决定加入组。Rx UE-3直接或间接地获取QoS Profile信息,决定Specific PC5 DRX配置,并且合并Default PC5 DRX On-duration和Specific PC5 DRX On-duration作为DRX激活时间。Rx UE-3在DRX激活时间内和Tx UE-1/Rx UE-2交互组信息,在时间t13完成加入组的全部过程。之后,Tx UE-1发送数据包,Rx UE-2和Rx UE-3接收到数据包后会反馈ACK/NACK给Tx UE-1。
可选地,Rx UE-3在时间t12后可以延长On-duration时间来完成和Tx UE-1/Rx UE-2交换组信息。
值得注意的是,Rx UE-3在没有完成加入组过程前(即,t12和t13组管理时间段),Rx UE-3收到从Tx UE-1发来的数据包,但是Rx UE-3是无法反馈ACK/NACK给Tx UE-1的。另外,Rx UE-3需要使用其它广播的目的地L2 ID和Tx UE-1/Rx UE-2交换组信息。
在时间t14,Rx UE-2决定离开组。Rx UE-2在DRX激活时间内和Tx UE-1/Rx UE-3交换离开组相关信息,在时间t15完成离开组的全部过程。之后,Tx UE-1发送数据包,Rx UE-3接收到数据包后会反馈ACK/NACK给Tx UE-1。
值得注意的是,Rx UE-2在没有完成离开组过程前(即,t14和t15组管理时间段),Rx UE-2收到从Tx UE-1发来的数据包,虽然Rx UE-2已经对接收的数据包不感兴趣,但是Rx UE-3有义务反馈ACK/NACK给Tx UE-1的。
可选地,t14和t15组管理时间段,Rx UE-2收到从Tx UE-1发来的数据包,Rx UE-2解码SCI,并得知收到的是属于该组播的数据包,Rx UE-2仅需要反馈ACK给Tx UE-1就可以,Rx UE-2没有必要继续解码由SCI指定的数据信息。
需要说明的是,本申请实施例,利用业务的不同时间段的特性,有效地划分业务启动期、业务持续期和业务完成期,并对PC5 DRX参数进行灵活控制。在业务没有开始之前,节能UE仅使用DRX激活时间比较稀疏的Default PC5 DRX,来提高UE的节能效果;而一旦业务开始,节能UE会合并Default PC5 DRX On-duration和Specific PC5 DRX On-duration作为DRX激活时间,来提高广播和组播通信性能。最后当业务完成后,节能UE会停止使用Specific PC5 DRX On-duration,仅残留Default PC5 DRX,重新回到UE更节能的Default PC5 DRX模式,以此能够实现终端的节能。
需要说明的是,本申请实施例提供的数据传输方法,执行主体可以为数据传输装置,或者,该数据传输装置中的用于执行数据传输方法的控制模块。本申请实施例中以数据传输装置执行数据传输方法为例,说明本申请实施例提供的数据传输装置。
如图8所示,本申请实施例提供一种数据传输装置800,应用于接收端,包括:
配置模块801,用于根据业务所处时期,确定非连续接收DRX的参数配置;
第一接收模块802,用于根据所述参数配置,接收目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
可选地,所述配置模块801,包括以下至少一项:
第一确定单元,用于在业务未开始之前,确定使用第一DRX的持续时间作为DRX激活时间;
第二确定单元,用于在业务启动期,确定使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;
第三确定单元,用于在业务完成后,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间。
可选地,所述第一DRX的参数满足以下至少一项:
所述第一DRX的参数由所述接收端所处的位置确定;
所述第一DRX的参数为预配置;
所述第一DRX的参数由网络侧设备配置。
可选地,所述第二确定单元,包括:
接收子单元,用于在业务启动期,接收第一数据包;
获取子单元,用于根据所述第一数据包,获取业务的服务质量QoS配置信息;
配置子单元,用于配置使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;
其中,所述第二DRX的持续时间由与所述QoS配置信息对应的DRX参数所指示。
可选地,所述接收子单元,用于实现以下至少一项:
在所述第一DRX的DRX激活时间内,接收至少一个第一数据包,所述第一数据包是发送端在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送的;
在所述第一DRX的每个DRX激活时间内接收至少一个第一数据包。
可选地,在所述目标通信为组播通信的情况下,所述接收子单元,用于:
在所述接收端加入组时,在目标持续时间内接收来自发送端的第一数据 包;
其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻。
可选地,所述第三确定单元,用于:
在满足第一条件的情况下,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间;
其中,所述第一条件包括以下至少一项:
接收到发送端发送的第一指示信息,所述第一指示信息用于指示所述接收端停止使用所述第二DRX;
第一计时器超时。
可选地,所述接收到发送端发送的第一指示信息的实现方式,包括以下一项:
接收到发送端通过高层信令发送的第一指示信息;
接收到发送端通过媒体接入控制层控制单元MAC-CE信令发送的第一指示信息。
可选地,在所述接收端接收到新数据包的情况下,所述第一计时器启动或重启。
可选地,在所述目标通信为组播通信的情况下,所述装置,还包括以下至少一项:
第二接收模块,用于在组未建立的情况下,在所述第一DRX的持续时间内,接收所述发送端通过广播方式发送的组配置信息;
第三接收模块,用于在组建立之后,在所述DRX激活时间内接收发送端发送的组更新信息。组组
可选地,在所述目标通信为组播通信的情况下,在所述第一接收模块接收目标通信的数据之后,所述装置还包括以下至少一项:
第一确定模块,用于在所述接收端未加入组的情况下,确定不向所述发送端反馈针对所述数据的应答消息;
第二确定模块,用于在所述接收端未离开组的情况下,确定向所述发送端反馈针对所述数据的应答消息。
需要说明的是,通过依据业务所处时期,进行DRX的参数配置,并依据DRX的参数配置,接收广播通信或组播通信的数据,以此能够实现DRX的动态配置,进而保证能够尽可能节省终端功耗。
本申请实施例中的数据传输装置可以是装置,具有操作系统的装置或电子设备,也可以是终端中的部件、集成电路、或芯片。该装置或电子设备可以是移动终端,也可以为非移动终端。示例性的,移动终端可以包括但不限于上述所列举的终端11的类型,非移动终端可以为服务器、网络附属存储器(Network Attached Storage,NAS)、个人计算机(personal computer,PC)、电视机(television,TV)、柜员机或者自助机等,本申请实施例不作具体限定。
本申请实施例提供的数据传输装置能够实现图1的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种终端,所述终端为接收端,包括处理器和通信接口,处理器用于根据业务所处时期,确定非连续接收DRX的参数配置;通信接口用于根据所述参数配置,接收目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
该终端实施例是与上述应用于接收端侧的方法实施例对应的,上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中,且能达到相同的技术效果。具体地,图9为实现本申请实施例的一种终端的硬件结构示意图。
该终端900为接收端,包括但不限于:射频单元901、网络模块902、音频输出单元903、输入单元904、传感器905、显示单元906、用户输入单元907、接口单元908、存储器909、以及处理器910等中的至少部分部件。
本领域技术人员可以理解,终端900还可以包括给各个部件供电的电源(比如电池),电源可以通过电源管理系统与处理器910逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图9中示出的终端结构并不构成对终端的限定,终端可以包括比图示更多或更少的部件,或 者组合某些部件,或者不同的部件布置,在此不再赘述。
应理解的是,本申请实施例中,输入单元904可以包括图形处理器(Graphics Processing Unit,GPU)9041和麦克风9042,图形处理器9041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元906可包括显示面板9061,可以采用液晶显示器、有机发光二极管等形式来配置显示面板9061。用户输入单元907包括触控面板9071以及其他输入设备9072。触控面板9071,也称为触摸屏。触控面板9071可包括触摸检测装置和触摸控制器两个部分。其他输入设备9072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆,在此不再赘述。
本申请实施例中,射频单元901将来自网络侧设备的下行数据接收后,给处理器910处理;另外,将上行的数据发送给网络侧设备。通常,射频单元901包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器909可用于存储软件程序或指令以及各种数据。存储器909可主要包括存储程序或指令区和存储数据区,其中,存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外,存储器909可以包括高速随机存取存储器,还可以包括非易失性存储器,其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器910可包括一个或多个处理单元;可选的,处理器910可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序或指令等,调制解调处理器主要处理无线通信,如基带处理器。可以理解的是,上述调制解调处理器也可以不集成到处理器910中。
其中,处理器910用于实现:根据业务所处时期,确定非连续接收DRX的参数配置;
射频单元901用于实现根据所述参数配置,接收目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
本申请实施例的终端通过依据业务所处时期,进行DRX的参数配置,并依据DRX的参数配置,接收广播通信或组播通信的数据,以此能够实现DRX的动态配置,进而保证能够尽可能节省终端功耗。
可选地,处理器910用于实现以下至少一项:
在业务未开始之前,确定使用第一DRX的持续时间作为DRX激活时间;
在业务启动期,确定使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;
在业务完成后,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间。
可选地,所述第一DRX的参数满足以下至少一项:
所述第一DRX的参数由所述接收端所处的位置确定;
所述第一DRX的参数为预配置;
所述第一DRX的参数由网络侧设备配置。
可选地,在业务启动期,通过射频单元901用于接收第一数据包;
可选地,处理器910,用于实现:
根据所述第一数据包,获取业务的服务质量QoS配置信息;
配置使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;
其中,所述第二DRX的持续时间由与所述QoS配置信息对应的DRX参数所指示。
可选地,射频单元901用于实现以下至少一项:
在所述第一DRX的DRX激活时间内,接收至少一个第一数据包,所述第一数据包是发送端在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送的;
在所述第一DRX的每个DRX激活时间内接收至少一个第一数据包。
可选地,在所述目标通信为组播通信的情况下,射频单元901用于:
在所述接收端加入组时,在目标持续时间内接收来自发送端的第一数据包;
其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻。
可选地,处理器910,用于实现:
在满足第一条件的情况下,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间;
其中,所述第一条件包括以下至少一项:
接收到发送端发送的第一指示信息,所述第一指示信息用于指示所述接收端停止使用所述第二DRX;
第一计时器超时。
可选地,所述射频单元901,用于实现以下一项:
接收到发送端通过高层信令发送的第一指示信息;
接收到发送端通过媒体接入控制层控制单元MAC-CE信令发送的第一指示信息。
可选地,在所述接收端接收到新数据包的情况下,所述第一计时器启动或重启。
可选地,在所述目标通信为组播通信的情况下,所述处理器910,还用于实现以下至少一项:
在组未建立的情况下,接收端在所述第一DRX的持续时间内,接收所述发送端通过广播方式发送的组配置信息;
在组建立之后,在所述DRX激活时间内接收发送端发送的组更新信息。
可选地,在所述目标通信为组播通信的情况下,在所述射频单元901接收目标通信的数据之后,所述处理器910,还用于实现以下至少一项:
在所述接收端未加入组的情况下,确定不向所述发送端反馈针对所述数据的应答消息;
在所述接收端未离开组的情况下,确定向所述发送端反馈针对所述数据的应答消息。
优选的,本申请实施例还提供一种终端,所述终端为接收端,包括处理器,存储器,存储在存储器上并可在所述处理器上运行的程序或指令,该程序或指令被处理器执行时实现数据传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种可读存储介质,可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现数据传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。其中,所述的计算机可读存储介质,如只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等。
如图10所示,为了配合接收端的接收,本申请实施例还提供一种数据传输方法,应用于发送端,包括:
步骤1001,发送端获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;
步骤1002,根据所述参数配置,所述发送端发送目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
可选地,所述参数配置满足以下至少一项:
在业务未开始之前,所述参数配置为使用第一DRX的持续时间作为DRX激活时间;
在业务启动期,所述参数配置为使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;
在业务完成后,所述参数配置为停止使用被配置的第二DRX的持续时间作为DRX激活时间,使用第一DRX的持续时间作为DRX激活时间。
可选地,所述第一DRX的参数满足以下至少一项:
所述第一DRX的参数由所述接收端所处的位置确定;
所述第一DRX的参数为预配置;
所述第一DRX的参数由网络侧设备配置。
可选地,所述根据所述DRX配置,发送目标通信的数据,包括以下至少一项:
在业务启动期,所述发送端确定最大传输时机数,在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送至少一个第一数据包给接收端;
在业务启动期,所述发送端在所述第一DRX的每个DRX激活时间内发送至少一个第一数据包给接收端;
其中,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
可选地,在所述目标通信为组播通信的情况下,所述方法,还包括:
在业务启动期,在所述接收端加入组时,所述发送端在目标持续时间内发送第一数据包给所述接收端;
其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
可选地,所述方法,还包括:
所述发送端发送第一指示信息给所述接收端;
其中,所述第一指示信息用于指示所述接收端停止使用所述第二DRX。
可选地,所述发送第一指示信息给所述接收端,包括以下至少一项:
所述发送端通过高层信令发送第一指示信息给所述接收端;
所述发送端通过媒体接入控制层控制单元MAC-CE信令发送第一指示信息给所述接收端。
可选地,在所述目标通信为组播通信的情况下,所述方法,还包括以下至少一项:
在组未建立的情况下,所述发送端在所述第一DRX的持续时间内,通过广播方式发送组配置信息给所述组中的每个接收端;
在组建立之后,所述发送端在所述DRX激活时间内发送组更新信息给所 述组中的每个接收端。
需要说明的是,上述实施例中所有关于发送端的描述均适用于应用于发送端的数据传输方法的实施例中,也能达到与之相同的技术效果,在此不再赘述。
如图11所示,本申请实施例还提供一种数据传输装置1100,包括:
获取模块1101,用于获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;
第一发送模块1102,用于根据所述参数配置,发送目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
可选地,所述参数配置满足以下至少一项:
在业务未开始之前,所述参数配置为使用第一DRX的持续时间作为DRX激活时间;
在业务启动期,所述参数配置为使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;
在业务完成后,所述参数配置为停止使用被配置的第二DRX的持续时间作为DRX激活时间,使用第一DRX的持续时间作为DRX激活时间。
可选地,所述第一DRX的参数满足以下至少一项:
所述第一DRX的参数由所述接收端所处的位置确定;
所述第一DRX的参数为预配置;
所述第一DRX的参数由网络侧设备配置。
可选地,所述第一发送模块1102,包括以下至少一项:
第一发送单元,用于在业务启动期,确定最大传输时机数,在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送至少一个第一数据包给接收端;
第二发送单元,用于在业务启动期,在所述第一DRX的每个DRX激活时间内发送至少一个第一数据包给接收端;
其中,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参 数配置。
可选地,在所述目标通信为组播通信的情况下,所述数据传输装置1100,还包括:
第二发送模块,用于在业务启动期,在所述接收端加入组时,在目标持续时间内发送第一数据包给所述接收端;
其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
可选地,所述数据传输装置1100,还包括:
第三发送模块,用于发送第一指示信息给所述接收端;
其中,所述第一指示信息用于指示所述接收端停止使用所述第二DRX。
可选地,所述第三发送模块,用于实现以下至少一项:
通过高层信令发送第一指示信息给所述接收端;
通过媒体接入控制层控制单元MAC-CE信令发送第一指示信息给所述接收端。
可选地,在所述目标通信为组播通信的情况下,所述数据传输装置1100,还包括以下至少一项:
第四发送模块,用于在组未建立的情况下,在所述第一DRX的持续时间内,通过广播方式发送组配置信息给所述组中的每个接收端;
第五发送模块,用于在组建立之后,在所述DRX激活时间内发送组更新信息给所述组中的每个接收端。
组组组组需要说明的是,本装置实施例是与上述方法实施例一一对应的装置,上述方法实施例的所有实现方式均适用于该装置实施例,也能达到相同的技术效果,在此不再赘述。
优选的,本申请实施例还提供一种终端,所述终端为发送端,包括处理器,存储器,存储在存储器上并可在所述处理器上运行的程序或指令,该程序或指令被处理器执行时实现应用于发送端侧的数据传输方法实施例的各个 过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种可读存储介质,计算机可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现应用于发送端侧的数据传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述的计算机可读存储介质,如只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等。
本申请实施例还提供一种终端,所述终端为发送端,包括处理器和通信接口,处理器用于获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;通信接口用于根据所述参数配置,发送目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
该终端实施例是与上述发送端侧的数据传输方法实施例对应的,上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中,且能达到相同的技术效果。
具体地,本申请实施例还提供了一种终端,所述终端为发送端。具体地,该发送端的结构与图9所示的接收端的结构类似,在此不再赘述。
可选地,处理器用于实现:
获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;
射频单元用于实现根据所述参数配置,发送目标通信的数据;
其中,所述目标通信包括:广播通信或组播通信。
可选地,所述参数配置满足以下至少一项:
在业务未开始之前,所述参数配置为使用第一DRX的持续时间作为DRX激活时间;
在业务启动期,所述参数配置为使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;
在业务完成后,所述参数配置为停止使用被配置的第二DRX的持续时间作为DRX激活时间,使用第一DRX的持续时间作为DRX激活时间。
可选地,所述第一DRX的参数满足以下至少一项:
所述第一DRX的参数由所述接收端所处的位置确定;
所述第一DRX的参数为预配置;
所述第一DRX的参数由网络侧设备配置。
可选地,射频单元,用于实现以下至少一项:
在业务启动期,确定最大传输时机数,在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送至少一个第一数据包给接收端;
在业务启动期,在所述第一DRX的每个DRX激活时间内发送至少一个第一数据包给接收端;
其中,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
可选地,在所述目标通信为组播通信的情况下,射频单元,还用于:
在业务启动期,在所述接收端加入组时,在目标持续时间内发送第一数据包给所述接收端;
其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
可选地,射频单元,还用于:
发送第一指示信息给所述接收端;
其中,所述第一指示信息用于指示所述接收端停止使用所述第二DRX。
可选地,射频单元,还用于实现以下至少一项:
通过高层信令发送第一指示信息给所述接收端;
通过媒体接入控制层控制单元MAC-CE信令发送第一指示信息给所述接收端。
可选地,在所述目标通信为组播通信的情况下,所述射频单元,还用实 现于以下至少一项:
在组未建立的情况下,在所述第一DRX的持续时间内,通过广播方式发送组配置信息给所述组中的每个接收端;
在组建立之后,在所述DRX激活时间内发送组更新信息给所述组中的每个接收端。
需要说明的是,本申请实施例中所说的应用于发送端和接收端的信息传输装置可以设置在同一设备中,也就是说,该设备既可以实现信息的发送功能也可以实现信息的接收功能。
可选的,如图12所示,本申请实施例还提供一种通信设备1200,包括处理器1201,存储器1202,存储在存储器1202上并可在所述处理器1201上运行的程序或指令,例如,该通信设备1200为接收端时,该程序或指令被处理器1201执行时实现上述应用于接收端的数据传输方法实施例的各个过程,且能达到相同的技术效果。该通信设备1200为发送端时,该程序或指令被处理器1201执行时实现上述应用于发送端的数据传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例涉及的终端,可以是指向用户提供语音和/或数据连通性的设备,具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备等。在不同的系统中,终端设备的名称可能也不相同,例如在5G系统中,终端设备可以称为用户设备(User Equipment,UE)。无线终端设备可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网(Core Network,CN)进行通信,无线终端设备可以是移动终端设备,如移动电话(或称为“蜂窝”电话)和具有移动终端设备的计算机,例如,可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置,它们与无线接入网交换语言和/或数据。例如,个人通信业务(Personal Communication Service,PCS)电话、无绳电话、会话发起协议(Session Initiated Protocol,SIP)话机、无线本地环路(Wireless Local Loop,WLL)站、个人数字助理(Personal Digital Assistant,PDA)等设备。无线终端设备也可以称为系统、订户单元(subscriber unit)、订户站(subscriber station),移动站(mobile station)、移动台(mobile)、 远程站(remote station)、接入点(access point)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、用户装置(user device),本申请实施例中并不限定。
本申请实施例涉及的网络侧设备可以是全球移动通讯(Global System of Mobile communication,简称GSM)或码分多址(Code Division Multiple Access,简称CDMA)中的基站(Base Transceiver Station,简称BTS),也可以是宽带码分多址(Wideband Code Division Multiple Access,简称WCDMA)中的基站(NodeB,简称NB),还可以是LTE中的演进型基站(Evolutional Node B,简称eNB或eNodeB),或者中继站或接入点,或者未来5G网络中的基站等,在此并不限定。
网络侧设备与终端之间可以各自使用一或多根天线进行多输入多输出(Multi Input Multi Output,MIMO)传输,MIMO传输可以是单用户MIMO(Single User MIMO,SU-MIMO)或多用户MIMO(Multiple User MIMO,MU-MIMO)。根据根天线组合的形态和数量,MIMO传输可以是2D-MIMO、3D-MIMO、FD-MIMO或massive-MIMO,也可以是分集传输或预编码传输或波束赋形传输等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现上述数据传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
本申请实施例还提供一种计算机程序产品,所述计算机程序产品被存储在非易失的存储介质中,所述计算机程序产品被至少一个处理器执行时实现上述数据传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还 包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。
Claims (43)
- 一种数据传输方法,包括:接收端根据业务所处时期,确定非连续接收DRX的参数配置;根据所述参数配置,所述接收端接收目标通信的数据;其中,所述目标通信包括:广播通信或组播通信。
- 根据权利要求1所述的方法,其中,所述接收端根据业务所处时期,确定非连续接收DRX的参数配置,包括以下至少一项:在业务未开始之前,确定使用第一DRX的持续时间作为DRX激活时间;在业务启动期,确定使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;在业务完成后,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间。
- 根据权利要求2所述的方法,其中,所述第一DRX的参数满足以下至少一项:所述第一DRX的参数由所述接收端所处的位置确定;所述第一DRX的参数为预配置;所述第一DRX的参数由网络侧设备配置。
- 根据权利要求2所述的方法,其中,在业务启动期,确定使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间,包括:在业务启动期,所述接收端接收第一数据包;根据所述第一数据包,所述接收端获取业务的服务质量QoS配置信息;所述接收端配置使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;其中,所述第二DRX的持续时间由与所述QoS配置信息对应的DRX参数所指示。
- 根据权利要求4所述的方法,其中,所述接收端接收第一数据包,包 括以下至少一项:在所述第一DRX的DRX激活时间内,所述接收端接收至少一个第一数据包,所述第一数据包是发送端在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送的;所述接收端在所述第一DRX的每个DRX激活时间内接收至少一个第一数据包。
- 根据权利要求4所述的方法,其中,在所述目标通信为组播通信的情况下,所述接收端接收第一数据包,包括:在所述接收端加入组时,所述接收端在目标持续时间内接收来自发送端的第一数据包;其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻。
- 根据权利要求2所述的方法,其中,所述在业务完成后,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间,包括:在满足第一条件的情况下,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间;其中,所述第一条件包括以下至少一项:所述接收端接收到发送端发送的第一指示信息,所述第一指示信息用于指示所述接收端停止使用所述第二DRX;第一计时器超时。
- 根据权利要求7所述的方法,其中,所述接收端接收到发送端发送的第一指示信息,包括以下一项:所述接收端接收到发送端通过高层信令发送的第一指示信息;所述接收端接收到发送端通过媒体接入控制层控制单元MAC-CE信令发送的第一指示信息。
- 根据权利要求7所述的方法,其中,在所述接收端接收到新数据包的 情况下,所述第一计时器启动或重启。
- 根据权利要求2所述的方法,其中,在所述目标通信为组播通信的情况下,所述方法,还包括以下至少一项:在组未建立的情况下,接收端在所述第一DRX的持续时间内,接收所述发送端通过广播方式发送的组配置信息;在组建立之后,在所述DRX激活时间内所述接收端接收发送端发送的组更新信息。
- 根据权利要求1所述的方法,其中,在所述目标通信为组播通信的情况下,在所述接收端接收目标通信的数据之后,所述方法,还包括以下至少一项:在所述接收端未加入组的情况下,所述接收端确定不向所述发送端反馈针对所述数据的应答消息;在所述接收端未离开组的情况下,所述接收端确定向所述发送端反馈针对所述数据的应答消息。
- 一种数据传输方法,包括:发送端获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;根据所述参数配置,所述发送端发送目标通信的数据;其中,所述目标通信包括:广播通信或组播通信。
- 根据权利要求12所述的方法,其中,所述参数配置满足以下至少一项:在业务未开始之前,所述参数配置为使用第一DRX的持续时间作为DRX激活时间;在业务启动期,所述参数配置为使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;在业务完成后,所述参数配置为停止使用被配置的第二DRX的持续时间作为DRX激活时间,使用第一DRX的持续时间作为DRX激活时间。
- 根据权利要求13所述的方法,其中,所述第一DRX的参数满足以下至少一项:所述第一DRX的参数由所述接收端所处的位置确定;所述第一DRX的参数为预配置;所述第一DRX的参数由网络侧设备配置。
- 根据权利要求13所述的方法,其中,所述根据所述参数配置,发送目标通信的数据,包括以下至少一项:在业务启动期,所述发送端确定最大传输时机数,在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送至少一个第一数据包给接收端;在业务启动期,所述发送端在所述第一DRX的每个DRX激活时间内发送至少一个第一数据包给接收端;其中,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
- 根据权利要求13所述的方法,其中,在所述目标通信为组播通信的情况下,所述方法,还包括:在业务启动期,在所述接收端加入组时,所述发送端在目标持续时间内发送第一数据包给所述接收端;其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
- 根据权利要求13所述的方法,其中,还包括:所述发送端发送第一指示信息给所述接收端;其中,所述第一指示信息用于指示所述接收端停止使用所述第二DRX。
- 根据权利要求17所述的方法,其中,所述发送端发送第一指示信息给所述接收端,包括以下至少一项:所述发送端通过高层信令发送第一指示信息给所述接收端;所述发送端通过媒体接入控制层控制单元MAC-CE信令发送第一指示信息给所述接收端。
- 根据权利要求13所述的方法,其中,在所述目标通信为组播通信的情况下,所述方法,还包括以下至少一项:在组未建立的情况下,所述发送端在所述第一DRX的持续时间内,通过广播方式发送组配置信息给所述组中的每个接收端;在组建立之后,所述发送端在所述DRX激活时间内发送组更新信息给所述组中的每个接收端。
- 一种数据传输装置,应用于接收端,包括:配置模块,用于根据业务所处时期,确定非连续接收DRX的参数配置;第一接收模块,用于根据所述参数配置,接收目标通信的数据;其中,所述目标通信包括:广播通信或组播通信。
- 根据权利要求20所述的装置,其中,所述配置模块,包括以下至少一项:第一确定单元,用于在业务未开始之前,确定使用第一DRX的持续时间作为DRX激活时间;第二确定单元,用于在业务启动期,确定使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;第三确定单元,用于在业务完成后,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间。
- 根据权利要求21所述的装置,其中,所述第一DRX的参数满足以下至少一项:所述第一DRX的参数由所述接收端所处的位置确定;所述第一DRX的参数为预配置;所述第一DRX的参数由网络侧设备配置。
- 根据权利要求21所述的装置,其中,所述第二确定单元,包括:接收子单元,用于在业务启动期,接收第一数据包;获取子单元,用于根据所述第一数据包,获取业务的服务质量QoS配置信息;配置子单元,用于配置使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;其中,所述第二DRX的持续时间由与所述QoS配置信息对应的DRX参数所指示。
- 根据权利要求23所述的装置,其中,所述接收子单元,用于实现以下至少一项:在所述第一DRX的DRX激活时间内,接收至少一个第一数据包,所述第一数据包是发送端在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送的;在所述第一DRX的每个DRX激活时间内接收至少一个第一数据包。
- 根据权利要求23所述的装置,其中,在所述目标通信为组播通信的情况下,所述接收子单元,用于:在所述接收端加入组时,在目标持续时间内接收来自发送端的第一数据包;其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻。
- 根据权利要求21所述的装置,其中,所述第三确定单元,用于:在满足第一条件的情况下,确定停止使用被配置的第二DRX的持续时间作为DRX激活时间,并确定使用第一DRX的持续时间作为DRX激活时间;其中,所述第一条件包括以下至少一项:接收到发送端发送的第一指示信息,所述第一指示信息用于指示所述接收端停止使用所述第二DRX;第一计时器超时。
- 根据权利要求26所述的装置,其中,所述接收到发送端发送的第一 指示信息的实现方式,包括以下一项:接收到发送端通过高层信令发送的第一指示信息;接收到发送端通过媒体接入控制层控制单元MAC-CE信令发送的第一指示信息。
- 根据权利要求26所述的装置,其中,在所述接收端接收到新数据包的情况下,所述第一计时器启动或重启。
- 根据权利要求21所述的装置,其中,在所述目标通信为组播通信的情况下,所述装置,还包括以下至少一项:第二接收模块,用于在组未建立的情况下,在所述第一DRX的持续时间内,接收所述发送端通过广播方式发送的组配置信息;第三接收模块,用于在组建立之后,在所述DRX激活时间内接收发送端发送的组更新信息。
- 根据权利要求20所述的装置,其中,在所述目标通信为组播通信的情况下,在所述第一接收模块接收目标通信的数据之后,所述装置还包括以下至少一项:第一确定模块,用于在所述接收端未加入组的情况下,确定不向所述发送端反馈针对所述数据的应答消息;第二确定模块,用于在所述接收端未离开组的情况下,确定向所述发送端反馈针对所述数据的应答消息。
- 一种数据传输装置,应用于发送端,包括:获取模块,用于获取接收端的非连续接收DRX的参数配置,所述参数配置由业务所处时期确定;第一发送模块,用于根据所述参数配置,发送目标通信的数据;其中,所述目标通信包括:广播通信或组播通信。
- 根据权利要求31所述的装置,其中,所述参数配置满足以下至少一项:在业务未开始之前,所述参数配置为使用第一DRX的持续时间作为DRX 激活时间;在业务启动期,所述参数配置为使用第一DRX的持续时间以及第二DRX的持续时间作为DRX激活时间;在业务完成后,所述参数配置为停止使用被配置的第二DRX的持续时间作为DRX激活时间,使用第一DRX的持续时间作为DRX激活时间。
- 根据权利要求32所述的装置,其中,所述第一DRX的参数满足以下至少一项:所述第一DRX的参数由所述接收端所处的位置确定;所述第一DRX的参数为预配置;所述第一DRX的参数由网络侧设备配置。
- 根据权利要求32所述的装置,其中,所述第一发送模块,包括以下至少一项:第一发送单元,用于在业务启动期,确定最大传输时机数,在未达到最大传输时机数之前,在第一DRX的DRX激活时间内发送至少一个第一数据包给接收端;第二发送单元,用于在业务启动期,在所述第一DRX的每个DRX激活时间内发送至少一个第一数据包给接收端;其中,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
- 根据权利要求32所述的装置,其中,在所述目标通信为组播通信的情况下,所述装置,还包括:第二发送模块,用于在业务启动期,在所述接收端加入组时,在目标持续时间内发送第一数据包给所述接收端;其中,所述目标持续时间为距离第一时刻最近的第一DRX的持续时间,所述第一时刻为所述接收端加入组的时刻,所述第一数据包用于辅助所述接收端在业务启动期进行DRX的参数配置。
- 根据权利要求32所述的装置,其中,还包括:第三发送模块,用于发送第一指示信息给所述接收端;其中,所述第一指示信息用于指示所述接收端停止使用所述第二DRX。
- 根据权利要求36所述的装置,其中,所述第三发送模块,用于实现以下至少一项:通过高层信令发送第一指示信息给所述接收端;通过媒体接入控制层控制单元MAC-CE信令发送第一指示信息给所述接收端。
- 根据权利要求32所述的装置,其中,在所述目标通信为组播通信的情况下,所述装置,还包括以下至少一项:第四发送模块,用于在组未建立的情况下,在所述第一DRX的持续时间内,通过广播方式发送组配置信息给所述组中的每个接收端;第五发送模块,用于在组建立之后,在所述DRX激活时间内发送组更新信息给所述组中的每个接收端。
- 一种终端,所述终端为接收端,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至11任一项所述的数据传输方法的步骤。
- 一种终端,所述终端为发送端,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求12至19任一项所述的数据传输方法的步骤。
- 一种可读存储介质,其中,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如权利要求1-19任一项所述的数据传输方法的步骤。
- 一种芯片,包括处理器和通信接口,其中,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如权利要求1至11中任一项所述的数据传输方法的步骤,或者实现如权利要求12至19中任一项所述的数据传输方法的步骤。
- 一种计算机程序产品,其中,所述程序产品被存储在非易失的存储 介质中,所述程序产品被至少一个处理器执行以实现如权利要求1至11中任一项所述的数据传输方法的步骤,或者实现如权利要求12至19中任一项所述的数据传输方法的步骤。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110694229.XA CN115515258A (zh) | 2021-06-22 | 2021-06-22 | 数据传输方法、装置及终端 |
CN202110694229.X | 2021-06-22 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022267948A1 true WO2022267948A1 (zh) | 2022-12-29 |
Family
ID=84499833
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/098897 WO2022267948A1 (zh) | 2021-06-22 | 2022-06-15 | 数据传输方法、装置及终端 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN115515258A (zh) |
WO (1) | WO2022267948A1 (zh) |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102014103A (zh) * | 2009-09-07 | 2011-04-13 | 华为技术有限公司 | 机器类型通讯方法及终端 |
US20160219443A1 (en) * | 2013-09-15 | 2016-07-28 | Lg Electronics Inc. | Discontinuous reception supporting method in wireless communication system supporting change of usage of radio resource and apparatus therefor |
CN107241786A (zh) * | 2016-03-28 | 2017-10-10 | 电信科学技术研究院 | 一种进行通信配置的方法和设备 |
CN111800764A (zh) * | 2019-08-22 | 2020-10-20 | 维沃移动通信有限公司 | 边链路drx参数配置方法、装置及终端设备 |
CN112543442A (zh) * | 2019-09-20 | 2021-03-23 | 维沃移动通信有限公司 | 非连续接收参数配置方法及设备 |
WO2021093202A1 (en) * | 2020-02-13 | 2021-05-20 | Zte Corporation | Method and device for sidelink communication |
CN112867176A (zh) * | 2021-01-15 | 2021-05-28 | 中兴通讯股份有限公司 | 通信方法、设备和存储介质 |
-
2021
- 2021-06-22 CN CN202110694229.XA patent/CN115515258A/zh active Pending
-
2022
- 2022-06-15 WO PCT/CN2022/098897 patent/WO2022267948A1/zh active Application Filing
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102014103A (zh) * | 2009-09-07 | 2011-04-13 | 华为技术有限公司 | 机器类型通讯方法及终端 |
US20160219443A1 (en) * | 2013-09-15 | 2016-07-28 | Lg Electronics Inc. | Discontinuous reception supporting method in wireless communication system supporting change of usage of radio resource and apparatus therefor |
CN107241786A (zh) * | 2016-03-28 | 2017-10-10 | 电信科学技术研究院 | 一种进行通信配置的方法和设备 |
CN111800764A (zh) * | 2019-08-22 | 2020-10-20 | 维沃移动通信有限公司 | 边链路drx参数配置方法、装置及终端设备 |
CN112543442A (zh) * | 2019-09-20 | 2021-03-23 | 维沃移动通信有限公司 | 非连续接收参数配置方法及设备 |
WO2021093202A1 (en) * | 2020-02-13 | 2021-05-20 | Zte Corporation | Method and device for sidelink communication |
CN112867176A (zh) * | 2021-01-15 | 2021-05-28 | 中兴通讯股份有限公司 | 通信方法、设备和存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN115515258A (zh) | 2022-12-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11064559B2 (en) | Method of sharing a UE receiver between D2D and cellular operations based on activity | |
JP2013051719A (ja) | 不連続受信とタイミングをとるチャネル品質指標伝送 | |
US20240049342A1 (en) | Drx configuration method and apparatus, communication device and storage medium | |
WO2023274141A1 (zh) | 非激活定时器的控制方法、装置及终端 | |
WO2022056806A1 (zh) | 一种mbs业务的管理方法及装置、终端设备、网络设备 | |
WO2022017481A1 (zh) | 业务传输资源的更新方法、终端及网络侧设备 | |
CN115396823B (zh) | 一种传输业务数据的方法和通信装置 | |
WO2023280014A1 (zh) | 单播侧链路通信方法、装置及终端 | |
US8824348B2 (en) | Method for controlling power saving mode in group communication | |
WO2022267948A1 (zh) | 数据传输方法、装置及终端 | |
WO2022068679A1 (zh) | 广播多播业务的拥塞控制方法、装置和设备 | |
WO2022213982A1 (zh) | 配置方法、装置及设备 | |
US20230239901A1 (en) | Method for receiving multicast service data, terminal device, and non-transitory computer-readable storage medium | |
WO2022188771A1 (zh) | 副链路的非连续接收配置方法、装置、设备及可读存储介质 | |
WO2022183980A1 (zh) | Sl csi报告的处理方法、装置及设备 | |
WO2022184045A1 (zh) | 多播业务的接收方法、装置及电子设备 | |
WO2024216502A1 (zh) | 一种传输下行信道的方法、装置以及可读存储介质 | |
WO2023001144A1 (zh) | 多播广播业务的接收方法、发送方法、装置及设备 | |
WO2023072149A1 (zh) | 接入方法、驻留方法、装置、用户设备及存储介质 | |
WO2024098300A1 (zh) | 一种传输配置信息的方法、装置及可读存储介质 | |
WO2023280101A1 (zh) | Sl处理方法、装置、终端及可读存储介质 | |
US20230362886A1 (en) | Data transmission method and apparatus | |
WO2024159360A1 (zh) | 一种监听或发送方法、设备、装置及可读存储介质 | |
WO2024103358A1 (zh) | 一种传输指示信息的方法、装置及可读存储介质 | |
WO2024187431A1 (zh) | 一种通信方法、装置以及可读存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22827443 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 22827443 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 23/04/2024) |