WO2018157732A1 - 一种数据传输方法及装置 - Google Patents

一种数据传输方法及装置 Download PDF

Info

Publication number
WO2018157732A1
WO2018157732A1 PCT/CN2018/076295 CN2018076295W WO2018157732A1 WO 2018157732 A1 WO2018157732 A1 WO 2018157732A1 CN 2018076295 W CN2018076295 W CN 2018076295W WO 2018157732 A1 WO2018157732 A1 WO 2018157732A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
resource
information
data transmission
uplink data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/076295
Other languages
English (en)
French (fr)
Inventor
杜白
张鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP18760766.8A priority Critical patent/EP3579644B1/en
Priority to BR112019017420A priority patent/BR112019017420A2/pt
Publication of WO2018157732A1 publication Critical patent/WO2018157732A1/zh
Priority to US16/552,371 priority patent/US11083004B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information

Definitions

  • the present application relates to the field of wireless communications technologies, and in particular, to a data transmission method and apparatus.
  • Enhanced Mobile Broadband eMBB
  • Ultra-Reliable and Low-Latency Communication URLLC
  • massive machine-like communication Massive Machine Type Communications, mMTC
  • the URLLC service requires a very high transmission delay.
  • the transmission delay of the URLLC service is required to be within 0.5 ms without requiring reliability.
  • the transmission delay of the URLLC service is required when the reliability is required to be 99.999%.
  • the request is still within 1ms. For this reason, data can be transmitted using a shorter transmission interval, such as Short Transmission Time Interval (sTTI) or mini-slot mini-slot.
  • Typical URLLC services include industrial control in the Internet of Things, automatic control in driverless cars, and the like.
  • Typical eMBB services include Ultra HD video, Virtual Reality (VR), and Augmented Reality (AR).
  • the URLLC terminal Since the TTI for transmitting the eMBB service is long, when the URLLC terminal needs to perform the data transmission of the URLLC service, if the URL LC service data is sent to the base station after waiting for the eMBB service data transmission that is currently being scheduled, the URLLC service is transmitted. The delay is too long to meet the transmission delay requirement of the URLLC service. Furthermore, in order to ensure that the transmission delay of the URLLC service is within the target range, the URLLC terminal can directly transmit the URLLC service data by using the uplink resource that is transmitting the eMBB service data.
  • the eMBB terminal will continue to use the uplink resource to send the eMBB service data to the base station, and the eMBB terminal and the URLLC terminal simultaneously send data on the same resource.
  • the eMBB terminal and the URLLC terminal simultaneously send data on the same resource.
  • the embodiment of the present application provides a data transmission method and apparatus to solve the problem of interference between an eMBB service and a URLLC service caused by uplink resource preemption in the prior art.
  • the embodiment of the present application provides a data transmission method, including: a first terminal sends first information to a second terminal, where the first information is used to indicate that the second terminal stops using the first resource to send uplink data, and then the first The terminal uses the first resource to send uplink data. It can be seen that when the first terminal needs to use the first resource of the second terminal to send data, the second terminal is notified to stop using the first resource to send uplink data, so that the first terminal and the second terminal do not use the same uplink resource at the same time. The data is transmitted, thereby solving the problem of mutual interference between the eMBB service and the URLLC service.
  • the second information from the second terminal may be received, where the second information includes the second resource used by the second terminal for uplink data transmission. information. It can be seen that, before the first terminal sends the uplink data, the second information of the second terminal is obtained, so that when the first terminal needs to send the uplink data, it is more convenient and quick to determine the first resource that needs to be preempted according to the second resource, and reduce the first resource.
  • the transmission delay of the service supported by the first terminal, and the second terminal corresponding to the first resource is determined in time, and the second terminal is notified to stop using the first resource to send uplink data, thereby avoiding the first terminal and the second terminal. Business interference between.
  • the first terminal may send third information, and the third information is used to request to acquire information about the second resource used by the second terminal for uplink data transmission.
  • the first terminal determines, according to the second resource, the first resource used by the first terminal for uplink data transmission, and the first resource may be part or all of the second resource. It can be seen that the first terminal can directly determine the first resource for uplink data transmission according to the second resource received in advance, instead of performing information interaction with the second terminal to determine the first resource when the service needs to be performed, so that The time for determining the first resource is reduced, and the transmission delay of the service supported by the first terminal is reduced.
  • an embodiment of the present application provides a data transmission method, including: receiving, by a second terminal, first information from a first terminal, where the first information is used to indicate that the second terminal stops using the first resource to send uplink data, and then The second terminal stops using the first resource to send uplink data. It can be seen that the second terminal stops using the first resource to send uplink data, and the base station does not receive the data sent by the two terminals on the first resource at the same time, thereby avoiding service interference between the two terminals.
  • the second terminal before the second terminal receives the first information from the first terminal, the second terminal needs to send the second information to the first terminal, where the second information includes the second terminal used for uplink data transmission.
  • Information on two resources The second terminal sends the information of the second resource for the uplink data transmission to the first resource, which may be convenient for the first terminal to determine the first resource according to the second resource, and notify the second terminal that the second terminal needs to be preempted.
  • the first resource reduces the transmission delay of the service supported by the first terminal and avoids the service interference between the first terminal and the second terminal.
  • the second terminal receives third information from the first terminal, and the third information is used to request to acquire information of the second resource used by the second terminal for uplink data transmission.
  • the first terminal in the first aspect and the second aspect is a high-reliability low-latency communication URLLC service terminal, and the second terminal is a mobile broadband enhanced eMBB service terminal.
  • an embodiment of the present application provides a data transmission apparatus, where the apparatus can implement the functions performed by the first terminal in the foregoing first aspect, and the functions may be implemented by using hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the apparatus includes a processor and a transceiver configured to support the apparatus to perform the corresponding functions of the above methods.
  • the transceiver is used to support communication between the device and other network elements.
  • the apparatus can also include a memory for coupling with the processor that retains the program instructions and data necessary for the apparatus.
  • an embodiment of the present application provides a data transmission apparatus, where the apparatus can implement the functions performed by the second terminal in the foregoing second aspect, and the functions can be implemented by using hardware or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the apparatus includes a processor and a transceiver configured to support the apparatus to perform the corresponding functions of the above methods.
  • the transceiver is used to support communication between the device and other network elements.
  • the apparatus can also include a memory for coupling with the processor that retains the program instructions and data necessary for the apparatus.
  • an embodiment of the present application provides a data transmission system, including a base station and the first terminal and the second terminal in the foregoing aspect.
  • an embodiment of the present application provides a computer storage medium for storing computer software instructions for use in the first terminal, including a program designed to perform the above aspects.
  • an embodiment of the present application provides a computer storage medium for storing computer software instructions for use in the second terminal, including a program designed to perform the above aspects.
  • the resource of the eMBB terminal is directly preempted, so that the URLLC terminal and the eMBB terminal use the same uplink resource to send data, which causes a service interference.
  • the first terminal needs to use the first resource to send the uplink data
  • the first terminal notifies the second terminal to stop using the first resource to send the uplink data, so that the first terminal and the second terminal do not simultaneously use the same uplink resource to send data
  • the base station Only the uplink data sent by the first terminal is received on the first resource, and the problem of mutual interference between the eMBB service and the URLLC service is solved while reducing the service transmission delay of the first terminal.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 3 is an exemplary schematic diagram of a data transmission method according to an embodiment of the present application.
  • FIG. 4 is a flowchart of another data transmission method according to an embodiment of the present application.
  • FIG. 5 is a flowchart of another data transmission method according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a logical structure of a first terminal according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a logical structure of a second terminal according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a logical structure of another first terminal according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a logical structure of another second terminal according to an embodiment of the present application.
  • the terminal in the embodiment of the present application may be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal device, and an augmented reality (AR) terminal device.
  • wireless terminal in industrial control wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, transportation security Wireless terminal in safety), wireless terminal in smart city, wireless terminal in smart home, and the like.
  • the embodiment of the present application does not limit the application scenario.
  • the data transmission method provided by the embodiment of the present application is applied to a communication system, as shown in FIG. 1 , which is a schematic diagram of a system architecture applied by a data transmission method provided by an embodiment of the present application, where the communication system includes at least The base station, the first terminal, and the second terminal, the first terminal and the second terminal may communicate by means of a device-to-device (D2D), and when the communication is performed by using a D2D mode, the communication link between the terminals It is called a sidelink.
  • D2D device-to-device
  • the first terminal may be a URLLC service terminal
  • the second terminal may be an eMBB service terminal, but the application does not limit this.
  • the eMBB service terminal refers to the terminal that carries the eMBB service
  • the URLLC service terminal refers to the terminal that carries the URLLC service. It should be noted that the same terminal may carry different services in different time periods, and the terminal is carrying the eMBB service.
  • the time period is called an eMBB service terminal, and is called a URLLC service terminal in a time period in which the URLLC service is carried. Because the URLLC service has a high transmission delay requirement, when the URLLC service terminal needs to perform the URLLC service, it directly performs data interaction with the eMBB service terminal (for example, data exchange through the sidelink), thereby occupying the uplink of the eMBB service data being transmitted. Resources to transfer URLLC business data.
  • the embodiment of the present application provides a data transmission method. As shown in FIG. 2 , the method includes:
  • the first terminal sends the first information to the second terminal, where the first information is used to indicate that the second terminal stops using the first resource to send the uplink data.
  • the first terminal and the second terminal are used to indicate the terminal that performs the different services.
  • the service performed by the first terminal has a high requirement on the transmission delay, and the sTTI needs to be used to support the service of the first terminal, and the service performed by the second terminal.
  • the scheduling time is longer and the transmission delay is lower, for example, 1 ms TTI can be used.
  • the first terminal is a URLLC service terminal
  • the second terminal is an eMBB service terminal
  • the type of the first terminal and the second terminal are not limited in this application.
  • the first resource may be selected from the second resource used by the eMBB service terminal for uplink data transmission.
  • the eMBB service terminal needs to be sent to the eMBB service terminal. a message.
  • the first resource may be an uplink resource used by the eMBB service terminal for uplink data transmission, or may be a partial uplink resource used by the eMBB service terminal for uplink data transmission, and the URLLC service terminal may select the most suitable uplink resource according to the service requirement.
  • the first resource for example, may select the best uplink resource of the channel quality indicator (CQI) as the first resource, but the application is not limited thereto, and the first resource may be selected according to other principles.
  • CQI channel quality indicator
  • the first information may also be used to notify the second terminal to stop sending uplink data. For example, when the second terminal receives the first information, the uplink data currently being transmitted is stopped. Or, the first information includes the first time, when the second terminal receives the first information, if the time domain range of a scheduled uplink transmission of the second terminal includes the first time, stopping sending the transmission Upstream data after the first time.
  • the communication process between the first terminal and the second terminal may be performed in whole or in part through the sidelink, but the communication method between the first terminal and the second terminal is not performed in this application. limited.
  • the second terminal stops using the first resource to send uplink data according to the first information.
  • the first terminal sends the uplink data by using the first resource.
  • the eMBB service terminal is transmitting uplink data to the base station by using the second resource shown in FIG. 3.
  • the URLLC service terminal needs to perform the URLLC service, but the URLLC service terminal waits for the eMBB service terminal.
  • the URLLC service cannot meet the transmission delay requirement.
  • the direct occupation of the eMBB service resource causes the eMBB service terminal and the URLLC service terminal to simultaneously use the same resource to send uplink data to generate services. interference.
  • the URLLC service terminal may notify the eMBB service terminal to stop transmitting uplink data on the first resource when the URLLC service needs to be performed, and then the URLLC service terminal may use the first resource to send uplink data to the base station, as shown in FIG. It can be seen that the URLLC service terminal uses the first resource in the second resource to send the uplink data, which can reduce the transmission delay of the URLLC service, after waiting for the eMBB service terminal to use the second resource to complete the uplink data transmission and then perform the URLLC service.
  • the data transmission method provided by the embodiment of the present application directly captures the resources of the eMBB service terminal when the URLLC service terminal needs to perform the URLLC service, so that the URLLC service terminal and the eMBB service terminal use the same uplink resource to send data, resulting in the appearance of the data.
  • the first terminal when the first terminal needs to use the first resource to send the uplink data, the first terminal notifies the second terminal to stop using the first resource to send the uplink data, so that the first terminal and the first terminal
  • the second terminal does not use the same uplink resource to transmit data at the same time, and the base station only receives the uplink data sent by the first terminal on the first resource, and solves the eMBB service while reducing the service transmission delay of the first terminal.
  • the first terminal Before the first terminal preempts the uplink resource of the second terminal to send the uplink data, the first resource needs to be determined first. To facilitate the first terminal to quickly determine the first resource, the first terminal may know the second terminal for uplink data transmission in advance. Based on the information of the second resource, in another implementation manner provided by the embodiment of the present application, as shown in FIG. 4, before performing the method flow shown in FIG. 2, the following steps may also be performed:
  • the first terminal sends the third information, where the third information is used to request to obtain information about the second resource used by the second terminal for uplink data transmission.
  • the first terminal may send a detection signal to discover the surrounding second terminal. After receiving the detection signal, the second terminal returns a response message to the first terminal, and then the first terminal returns a second response message to the first terminal. The terminal sends the third information to request to acquire the second resource information used by the second terminal that returns the response message for the uplink data transmission.
  • the third information is a broadcast message, or the third information may be carried in the detection signal sent by the first terminal.
  • the second terminal receives the message carrying the third information, the second terminal directly returns to the uplink data transmission. Second resource information.
  • the detection signal may be sent by the second terminal, and the first terminal may receive the detection signals sent by the multiple second terminals, and then send the third information to each second terminal respectively. And obtaining the second resource information used by the surrounding second terminal for uplink data transmission.
  • the second terminal sends the second information to the first resource, where the second information includes information about the second resource used by the second terminal for uplink data transmission.
  • the information about the second resource used by the second terminal for uplink data transmission may be the location information of the second resource allocated by the base station for the second terminal for uplink data transmission.
  • the information about the second resource used by the second terminal for the uplink data transmission included in the second information may be information about all the second resources used by the second terminal for uplink data transmission, or may be used by the second terminal for uplink data transmission. Information about some of the second resources.
  • the second terminal may return the second information to the first terminal, or the second terminal may also actively move to the nearby A terminal sends the second information. It can be understood that if the second terminal actively sends the second information to the first terminal, step 401 need not be performed.
  • the first terminal stores information about a second resource used by the second terminal for uplink data transmission.
  • the first terminal may establish a second terminal resource group, where the second terminal resource group includes information about the second resource for uplink data transmission of each second terminal received by the first terminal.
  • the second terminal needs to maintain and update the information of the second resource for the uplink data transmission of each second terminal in the second terminal resource group in real time, because the second resource of the second terminal is used for the uplink data transmission. .
  • step 501 can also be performed.
  • the first terminal determines, according to the second resource, a first resource used by the first terminal for uplink data transmission.
  • the first resource may be selected from the second terminal resource group, and then the second terminal to which the first resource belongs is determined, and then the first resource is sent to the first resource.
  • the associated second terminal sends the first information; or, when the first terminal needs to send the uplink data, the second terminal may be selected from the second terminal resource group, and then the first resource is selected from the selected uplink resources of the second terminal. And sending the first information to the selected second terminal, to instruct the second terminal to stop using the first resource to send the uplink data.
  • the first terminal may select the first resource from the second resources of the same second terminal in the second terminal resource group.
  • the first resource may be selected from the multiple second terminals in the second terminal resource group, and the first information is sent to each selected second terminal respectively to indicate that the resource is The selected second terminal stops using the first resource to send uplink data or stops sending uplink data.
  • the base station may reserve a part of uplink resources for the first terminal, when the first terminal does not select the first resource from the second terminal resource group, or select the first resource.
  • the first terminal may use the selected first resource and the reserved resource to send uplink data, or when the selected first resource is insufficient, the first terminal may also use the reserved resource instead of using the first resource. Upstream data.
  • the base station may reserve a part of the uplink resource for the URLLC service terminal. If there is no eMBB service terminal around the URLLC service terminal, or the eMBB service terminal around the URLLC service terminal is not allocated the uplink resource, the eMBB service terminal resource group will be The information of the second resource is such that the URLLC service terminal does not have the first resource that can be selected; or when there is not enough second resource in the eMBB service terminal resource group, the URLLC service terminal cannot select enough first resources.
  • the reserved resource may be directly used to send uplink data, or when the URLLC service terminal does not select enough first resources from the eMBB service terminal resource group, the uplink data may be sent by using the selected first resource and the reserved resource.
  • the base station may allocate the reserved resource to the eMBB service terminal with insufficient resources, or when there is idle reserved resource, the base station may directly reserve the reserved resource. It is allocated to the eMBB service terminal in the eMBB service terminal resource group.
  • the reserved resource has been allocated to the eMBB service terminal by the base station, when the URLLC service terminal needs to use the reserved resource, the first information is sent to the eMBB service terminal that is using the reserved resource to indicate the eMBB.
  • the service terminal stops using the reserved resources to send uplink data to avoid service interference.
  • the data transmission method provided by the embodiment of the present application directly captures the resources of the eMBB service terminal when the URLLC service terminal needs to perform the URLLC service, so that the URLLC service terminal and the eMBB service terminal use the same uplink resource to send data, resulting in the appearance of the data.
  • the preemption eMBB service terminal is first sent a preemption instruction to notify the preempted eMBB service terminal to stop using the preempted eMBB service resource.
  • Uplink data so that the base station only receives the uplink data sent by the URLLC service terminal on the preempted eMBB service resource, and solves the problem of mutual interference between the eMBB service and the URLLC service while reducing the transmission delay of the URLLC service. .
  • the solution provided by the embodiment of the present application is mainly introduced from the perspectives of the first terminal and the second terminal. It can be understood that the first terminal and the second terminal comprise corresponding hardware structures and/or software modules for performing respective functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may perform the division of the function modules on the first terminal and the second terminal according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one process.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • the embodiment of the present application further provides a data transmission device, which may be the first terminal in the foregoing embodiment.
  • FIG. 6 shows a possible structural diagram of the first terminal involved in the foregoing embodiment.
  • the first terminal includes a sending module 601, a receiving module 602, and a determining module 603.
  • the sending module 601 is configured to support the first terminal to perform steps 201 and 203 in FIG. 2 and step 401 in FIG. 4, and the receiving module 602 is configured to support the first terminal to receive the second information sent by the second terminal, and determine the module. 603.
  • the method is used to support the first terminal to perform step 501 in FIG. 5. All the related content of the steps involved in the foregoing method embodiments may be referred to the functional description of the corresponding functional modules, and details are not described herein again.
  • the embodiment of the present application further provides another data transmission device, which may be the second terminal in the foregoing embodiment, as shown in FIG. 7, and FIG. 7 shows one of the second terminals involved in the foregoing embodiment.
  • the second terminal includes: a receiving module 701, and a sending module 702.
  • the receiving module 701 is configured to support the second terminal to receive the first information and the third information from the first terminal
  • the sending module 702 is configured to support the second terminal to perform step 402 in FIG. 4 . All the related content of the steps involved in the foregoing method embodiments may be referred to the functional description of the corresponding functional modules, and details are not described herein again.
  • FIG. 8 is a schematic diagram showing another possible structure of the first terminal involved in the foregoing embodiment.
  • the first terminal includes: a processor 802, a transceiver 803, a memory 801, and a bus 804.
  • the transceiver 803, the processor 802, and the memory 801 are connected to each other through a bus 804.
  • the bus 804 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. .
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • the memory 801 is configured to store program codes and data of the first terminal.
  • the transceiver 803 is configured to support communication between the first terminal and other network entities, for example, to support the first terminal to perform step 201 and step 203 in FIG. 2, and step 401 in FIG.
  • the processor 803 is configured to control the action of the first terminal, for example, to support the first terminal to perform step 501 in FIG. 5, and/or other processes for the techniques described herein.
  • FIG. 9 is a schematic diagram showing another possible structure of the second terminal involved in the foregoing embodiment.
  • the second terminal includes: a processor 902, a transceiver 903, a memory 901, and a bus 904.
  • the transceiver 903, the processor 902, and the memory 901 are connected to each other through a bus 904.
  • the bus 904 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. .
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • the memory 901 is configured to store program codes and data of the second terminal.
  • the transceiver 903 is configured to support communication between the second terminal and other network entities, for example, to support the second terminal to perform step 402 in FIG.
  • the processor 803 is configured to control the action of the second terminal, for example, to support the second terminal to perform step 202 in FIG. 2, and/or other processes for the techniques described herein.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions can be from a website site, computer, server or data center to another website site by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Transfer from a computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the present application can be implemented by means of software plus necessary general hardware, and of course, by hardware, but in many cases, the former is a better implementation. .
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer.
  • a hard disk or optical disk, etc. includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请的实施例公开一种数据传输方法及装置，涉及无线通信技术领域，可以解决现有技术中由于进行资源抢占导致的eMBB业务和URLLC业务之间出现干扰的问题。本申请的实施例通过第一终端向第二终端发送第一信息，第一信息用于指示第二终端停止使用第一资源发送上行数据，然后第一终端使用第一资源发送上行数据。本申请的实施例提供的方案适于进行资源抢占时采用。

Description

一种数据传输方法及装置
本申请要求于2017年02月28日提交中国专利局、申请号为201710114720.4、申请名称为“一种数据传输方法及装置的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种数据传输方法及装置。
背景技术
目前，国际电信联盟定义了5G的三类业务，分别为移动宽带增强(Enhanced Mobile Broadband，eMBB)，低时延高可靠通信(Ultra-Reliable and Low-Latency Communication，URLLC)，海量机器类通信(Massive Machine Type Communications,mMTC)。其中，URLLC业务对传输时延要求极高，在不要求可靠性的情况下，URLLC业务的传输时延要求在0.5ms以内，在要求99.999％的可靠性的情况下，URLLC业务的传输时延要求仍在1ms之内，为此，可以使用更短的传输间隔来传输数据，例如短传输时间间隔(Short Transmission Time Interval，sTTI)或者微时隙mini-slot。典型的URLLC业务包括物联网中的工业控制、无人驾驶汽车中的自动控制等。典型的eMBB业务包括超高清视频、虚拟现实(Virtual Reality，VR)和增强现实(Augmented Reality，AR)等。
而由于传输eMBB业务的TTI较长，当URLLC终端需要进行URLLC业务的数据传输时，如果等待当前正在被调度的eMBB业务数据传输完成之后再向基站发送URLLC业务数据，会使得URLLC业务的传输时延过长，不能满足URLLC业务对传输时延的要求。进而，为了保证URLLC业务的传输时延在目标范围之内，URLLC终端可以直接使用正在传输eMBB业务数据的上行资源来传输URLLC业务数据。
然而，当URLLC业务数据使用正在传输eMBB业务数据的上行资源后，eMBB终端仍然会继续使用该上行资源向基站发送eMBB业务数据，会出现eMBB终端和URLLC终端同时在相同的资源上发送数据的情况，导致eMBB业务和URLLC业务之间出现干扰。
发明内容
本申请的实施例提供一种数据传输方法及装置，以解决现有技术中由于进行上行资源抢占导致的eMBB业务和URLLC业务之间出现干扰的问题。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，本申请实施例提供一种数据传输方法，包括：第一终端向第二终端发送第一信息，第一信息用于指示第二终端停止使用第一资源发送上行数据，然后第一终端使用第一资源发送上行数据。可见，在第一终端需使用第二终端的第一资源发送数据时，会事先通知第二终端停止使用第一资源发送上行数据，使得第一终端和第二 终端不会同时使用相同的上行资源发送数据，进而解决了eMBB业务和URLLC业务之间互相干扰的问题。
在一种可能的设计中，在第一终端向第二终端发送第一信息之前，可以接收来自第二终端的第二信息，第二信息包括第二终端用于上行数据传输的第二资源的信息。可见，在第一终端发送上行数据之前，先获取第二终端的第二信息，可以使得当第一终端需要发送上行数据时，更加方便快捷地根据第二资源确定需要抢占的第一资源，降低了第一终端所支持的业务的传输时延，且能够及时确定第一资源对应的第二终端，并通知该第二终端停止使用第一资源发送上行数据，避免了第一终端和第二终端之间的业务干扰。
在一种可能的设计中，第一终端可以发送第三信息，第三信息用于请求获取第二终端用于上行数据传输的第二资源的信息。
在一种可能的设计中，第一终端根据第二资源确定第一终端用于上行数据传输的第一资源，第一资源可以是第二资源中的一部分或全部。可见，第一终端可以直接根据事先接收到的第二资源来确定用于上行数据传输的第一资源，而不是当需要执行业务时才去与第二终端进行信息交互以确定第一资源，这样就减少了确定第一资源的时间，减小了第一终端所支持业务的传输时延。
第二方面，本申请的实施例提供一种数据传输方法，包括：第二终端接收来自第一终端的第一信息，第一信息用于指示第二终端停止使用第一资源发送上行数据，然后第二终端停止使用第一资源发送上行数据。可见，第二终端停止使用第一资源发送上行数据，基站就不会同时在第一资源上接收到两个终端发送的数据，避免了两个终端之间的业务干扰。
在一种可能的设计中，在第二终端接收来自第一终端的第一信息之前，第二终端需向第一终端发送第二信息，第二信息包括第二终端用于上行数据传输的第二资源的信息。第二终端将用于上行数据传输的第二资源的信息发送给第一资源，可以方便第一终端需要发送上行数据时，直接根据第二资源来确定第一资源，并通知第二终端需要抢占第一资源，既降低了第一终端所支持的业务的传输时延，又避免了第一终端与第二终端之间的业务干扰。
在一种可能的设计中，第二终端接收来自第一终端的第三信息，第三信息用于请求获取第二终端用于上行数据传输的第二资源的信息。
在一种可能的设计中，上述第一方面和第二方面中的第一终端为高可靠低时延通信URLLC业务终端，第二终端为移动宽带增强eMBB业务终端。
第三方面，本申请的实施例提供一种数据传输装置，该装置可以实现上述第一方面中第一终端所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的设计中，该装置的结构中包括处理器和收发器，该处理器被配置为支持该装置执行上述方法中相应的功能。该收发器用于支持该装置与其他网元之间的通信。该装置还可以包括存储器，该存储器用于与处理器耦合，其保存该装置必要的程序指令和数据。
第四方面，本申请的实施例提供一种数据传输装置，该装置可以实现上述第二方 面中第二终端所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的设计中，该装置的结构中包括处理器和收发器，该处理器被配置为支持该装置执行上述方法中相应的功能。该收发器用于支持该装置与其他网元之间的通信。该装置还可以包括存储器，该存储器用于与处理器耦合，其保存该装置必要的程序指令和数据。
第五方面，本申请的实施例提供一种数据传输系统，包括基站以及上述方面中所述的第一终端和第二终端。
第六方面，本申请的实施例提供了一种计算机存储介质，用于储存为上述第一终端所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第七方面，本申请的实施例提供了一种计算机存储介质，用于储存为上述第二终端所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
与现有技术中URLLC终端需要执行URLLC业务时直接抢占eMBB终端的资源，使得URLLC终端和eMBB终端使用相同的上行资源发送数据，导致出现业务干扰的现象相比，本申请的实施例中，当第一终端需要使用第一资源发送上行数据时，第一终端通知第二终端停止使用第一资源发送上行数据，从而使得第一终端和第二终端不会同时使用相同的上行资源发送数据，基站在第一资源上只会接收到第一终端发送的上行数据，在降低了第一终端的业务传输时延的同时，解决了eMBB业务和URLLC业务之间互相干扰的问题。
附图说明
图1为本申请的实施例提供的一种通信系统的结构示意图；
图2为本申请的实施例提供的一种数据传输方法的流程图；
图3为本申请的实施例提供的一种数据传输方法的示例性示意图；
图4为本申请的实施例提供的另一种数据传输方法的流程图；
图5为本申请的实施例提供的另一种数据传输方法的流程图；
图6为本申请的实施例提供的一种第一终端的逻辑结构示意图；
图7为本申请的实施例提供的一种第二终端的逻辑结构示意图；
图8为本申请的实施例提供的另一种第一终端的逻辑结构示意图；
图9为本申请的实施例提供的另一种第二终端的逻辑结构示意图。
具体实施方式
本申请描述的系统架构以及业务场景是为了更加清楚的说明本申请的技术方案，并不构成对于本申请提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
需要说明的是，本申请中“的(英文：of)”，相应的“(英文corresponding， relevant)”和“对应的(英文：corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。
本申请的实施例中的终端可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请的实施例对应用场景不做限定。
本申请的实施例提供的数据传输方法应用于通信系统中，如图1所示，其示出了本申请的实施例提供的一种数据传输方法所应用的系统架构示意图，通信系统中至少包括基站、第一终端和第二终端，第一终端可以和第二终端可以通过设备到设备(Device-to-Device，D2D)的方式进行通信，采用D2D的方式通信时，终端间的通信链路称为侧向链路(sidelink)。
在本申请的实施例中，第一终端可以为URLLC业务终端，第二终端可以为eMBB业务终端，但本申请对此并不作限定。
其中，eMBB业务终端是指承载eMBB业务的终端，URLLC业务终端是指承载URLLC业务的终端，需要说明的是，同一个终端在不同的时间段可能承载不同的业务，则该终端在承载eMBB业务的时间段内被称为eMBB业务终端，在承载URLLC业务的时间段内被称为URLLC业务终端。由于URLLC业务对传输时延要求较高，所以，当URLLC业务终端需要进行URLLC业务时，会直接与eMBB业务终端进行数据交互(例如通过sidelink进行数据交互)，从而占用正在传输eMBB业务数据的上行资源来传输URLLC业务数据。
结合图1所示的通信系统，为了避免资源抢占导致的eMBB业务和URLLC业务之间的干扰，本申请的实施例提供一种数据传输方法，如图2所示，该方法包括：
201、第一终端向第二终端发送第一信息，第一信息用于指示第二终端停止使用第一资源发送上行数据。
其中，第一终端和第二终端用于表示执行不同业务的终端，第一终端执行的业务对传输时延要求较高，需要使用sTTI来支持第一终端的业务，而第二终端执行的业务调度时间较长，对传输时延要求较低，例如可以使用1ms TTI。
作为一种可能的实现方式，本申请的实施例中以第一终端为URLLC业务终端、第二终端为eMBB业务终端为例，但本申请对第一终端和第二终端的类型不做限定。
当URLLC业务终端需要进行URLLC业务时，可以从eMBB业务终端用于上行数据传输的第二资源中选取第一资源，为了避免该eMBB业务终端继续使用第一资源，需向该eMBB业务终端发送第一信息。
其中，第一资源可以为eMBB业务终端用于上行数据传输的全部上行资源，也可以为eMBB业务终端用于上行数据传输的部分上行资源，URLLC业务终端可以根据业务需求选取最合适的上行资源作为第一资源，例如，可以选取信道质量(Channel Quality Indicator，CQI)最好的上行资源作为第一资源，但本申请不限制于此，也可 以根据其他原则来选取第一资源。
可选地，第一信息也可以用于通知第二终端停止发送上行数据。例如，当第二终端收到第一信息时，停止当前正在传输的上行数据。或者，第一信息包含第一时间，当第二终端收到第一信息后，若第二终端的某个已调度的上行传输的时域范围包含第一时间，则停止发送此次传输过程中在第一时间后的上行数据。
还需说明的是，本申请的实施例中第一终端与第二终端之间的通信过程可以全部或者部分通过sidelink进行，但本申请对第一终端和第二终端之间的通信方式不做限定。
202、第二终端根据第一信息停止使用第一资源发送上行数据。
203、第一终端使用第一资源发送上行数据。
具体可以参照图3，在t1时刻，eMBB业务终端正在使用图3中示出的第二资源向基站发送上行数据，此时，URLLC业务终端需要执行URLLC业务，但是URLLC业务终端如果等待eMBB业务终端的业务数据传输完毕再向基站发送URLLC业务数据就无法满足URLLC业务对传输时延的要求，而直接抢占eMBB业务资源会导致eMBB业务终端和URLLC业务终端同时使用相同的资源发送上行数据，产生业务干扰。为了解决这些问题，URLLC业务终端可以在需要执行URLLC业务时，通知eMBB业务终端停止在第一资源上发送上行数据，然后URLLC业务终端可以使用第一资源来向基站发送上行数据，从图3中可以看出，相比于等待eMBB业务终端使用第二资源完成上行数据发送之后再执行URLLC业务，URLLC业务终端使用第二资源中的第一资源发送上行数据可以降低URLLC业务的传输时延。
本申请的实施例提供的数据传输方法，与现有技术中URLLC业务终端需要执行URLLC业务时直接抢占eMBB业务终端的资源，使得URLLC业务终端和eMBB业务终端使用相同的上行资源发送数据，导致出现业务干扰的现象相比，本申请的实施例中，当第一终端需要使用第一资源发送上行数据时，第一终端通知第二终端停止使用第一资源发送上行数据，从而使得第一终端和第二终端不会同时使用相同的上行资源发送数据，基站在第一资源上只会接收到第一终端发送的上行数据，在降低了第一终端的业务传输时延的同时，解决了eMBB业务和URLLC业务之间互相干扰的问题。
在第一终端抢占第二终端的上行资源发送上行数据之前，需先确定第一资源，为了方便第一终端快速地确定第一资源，第一终端可以提前获知第二终端用于上行数据传输的第二资源的信息，基于此，在本申请的实施例提供的另一种实现方式中，如图4所示，在执行图2所示的方法流程之前，还可以执行以下步骤：
401、第一终端发送第三信息，第三信息用于请求获取第二终端用于上行数据传输的第二资源的信息。
其中，第一终端可以发送侦测信号，以发现周围的第二终端，第二终端接收到侦测信号后，会向第一终端返回响应消息，进而第一终端向这些返回响应消息的第二终端发送第三信息，以请求获取这些返回响应消息的第二终端用于上行数据传输的第二资源信息。
或者，第三信息为广播消息，或者可以在第一终端发送的侦测信号中携带第三信息，当第二终端接收到携带第三信息的消息之后，就直接返回自身用于上行数据传输 的第二资源信息。
在另一种可能的实现方式中，可以由第二终端发送侦测信号，第一终端可能会接收到多个第二终端发送的侦测信号，然后分别向每个第二终端发送第三信息，以获知周围的第二终端用于上行数据传输的第二资源信息。
402第二终端向第一资源发送第二信息，第二信息包括第二终端用于上行数据传输的第二资源的信息。
其中，第二终端用于上行数据传输的第二资源的信息可以为基站为第二终端分配的用于上行数据传输的第二资源的位置信息。
第二信息中包含的第二终端用于上行数据传输的第二资源的信息可以为第二终端用于上行数据传输的全部第二资源的信息，或者可以为第二终端用于上行数据传输的部分第二资源的信息。
需要说明的是，第二终端可以在接收到步骤401中，第一终端向第二终端发送的第三信息后，向第一终端返回第二信息，或者第二终端也可以主动向附近的第一终端发送第二信息，可以理解的是，如果第二终端主动向第一终端发送第二信息，则无需执行步骤401。
403、第一终端存储第二终端用于上行数据传输的第二资源的信息。
其中，第一终端可以建立第二终端资源组，第二终端资源组中包含第一终端接收到的每个第二终端的用于上行数据传输的第二资源的信息。由于第二终端用于上行数据传输的第二资源会发生变化，所以第一终端还需实时维护和更新第二终端资源组中的各第二终端的用于上行数据传输的第二资源的信息。
可以理解的是，在第一终端存储了第二终端用于上行数据传输的第二资源的信息之后，当第一终端需要传输上行数据时，即可从第二终端用于上行数据传输的第二资源的信息中选取第一资源，所以，在执行上述步骤201之前，还可以执行步骤501。
501、第一终端根据第二资源确定第一终端用于上行数据传输的第一资源。
其中，在创建第二终端资源组之后，当第一终端需要发送上行数据时，可以从第二终端资源组中选取第一资源，然后确定第一资源所属的第二终端，进而向第一资源所属的第二终端发送第一信息；或者，当第一终端需要发送上行数据时，可以从第二终端资源组中选取第二终端，然后从选取的第二终端的上行资源中选取第一资源，进而向选取的第二终端中发送第一信息，以指示第二终端停止使用第一资源发送上行数据。
需要说明的是，为了尽量减少受影响的第二终端的数量，第一终端可以尽量从第二终端资源组中的同一个第二终端的第二资源中选取第一资源。当从一个第二终端选取的资源不够时，可以从第二终端资源组中的多个第二终端中选取第一资源，并分别向选取的每个第二终端发送第一信息，以指示被选取的第二终端停止使用第一资源发送上行数据或者停止发送上行数据。
在本申请的实施例提供的另一种实现方式中，基站可以为第一终端预留一部分上行资源，当第一终端未从第二终端资源组中选取到第一资源，或者选取的第一资源不足时，第一终端可以使用选取到的第一资源以及预留资源发送上行数据，或者当选取的第一资源不足时，第一终端也可以不使用第一资源，直接使用预留资源发送上行数 据。
具体的，基站可以为URLLC业务终端预留一部分上行资源，如果URLLC业务终端周围没有任何eMBB业务终端，或者URLLC业务终端周围的eMBB业务终端都没有被分配上行资源，则eMBB业务终端资源组中将没有第二资源的信息，使得URLLC业务终端没有可选取的第一资源；或者当eMBB业务终端资源组中没有足够的第二资源，会导致URLLC业务终端选取不到足够的第一资源。为了保证URLLC业务的顺利执行，当URLLC业务终端未从eMBB业务终端资源组中选取到第一资源时，或者未选取到足够的第一资源时，可以直接使用预留资源发送上行数据，或者当URLLC业务终端未从eMBB业务终端资源组中选取到足够的第一资源时，可以使用选取到的第一资源以及预留资源发送上行数据。
另外，由于URLLC业务终端在未执行URLLC业务的情况下，预留资源是空闲的，或者URLLC业务终端执行业务时可能未占用全部的预留资源，所以当存在空闲的预留资源时，且eMBB业务终端资源组中存在上行资源不足的eMBB业务终端时，基站可以将预留资源分配给资源不足的eMBB业务终端使用，或者当存在空闲的预留资源时，基站可以直接将空闲的预留资源分配给eMBB业务终端资源组中的eMBB业务终端使用。
需要说明的是，如果预留资源已经被基站分配给eMBB业务终端使用，当URLLC业务终端需要使用预留资源时，需向正在使用预留资源的eMBB业务终端发送第一信息，以指示该eMBB业务终端停止使用预留资源发送上行数据，避免出现业务干扰。
本申请的实施例提供的数据传输方法，与现有技术中URLLC业务终端需要执行URLLC业务时直接抢占eMBB业务终端的资源，使得URLLC业务终端和eMBB业务终端使用相同的上行资源发送数据，导致出现业务干扰的现象相比，本申请的实施例中，当URLLC业务终端需要执行URLLC业务时，先向被抢占eMBB业务终端发送抢占指令，以通知被抢占eMBB业务终端停止使用被抢占eMBB业务资源发送上行数据，从而使得基站在被抢占eMBB业务资源上只会接收到URLLC业务终端发送的上行数据，在降低了URLLC业务的传输时延的同时，解决了eMBB业务和URLLC业务之间互相干扰的问题。
上述主要从第一终端和第二终端的角度对本申请的实施例提供的方案进行了介绍。可以理解的是，第一终端和第二终端包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请的实施例可以根据上述方法示例对第一终端和第二终端进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请的实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
本申请的实施例还提供一种数据传输装置，该装置可以为上述实施例中的第一终端。如图6所示，图6示出了上述实施例中所涉及的第一终端的一种可能的结构示意图。该第一终端包括发送模块601，接收模块602，确定模块603。其中，发送模块601用于支持第一终端执行图2中的步骤201、203和图4中的步骤401，接收模块602，用于支持第一终端接收第二终端发送的第二信息，确定模块603，用于支持第一终端执行图5中的步骤501。其中，上述方法实施例涉及的各步骤的所有相关内容均可援引到对应功能模块的功能描述，在此不再赘述。
本申请的实施例还提供另一种数据传输装置，该装置可以为上述实施例中的第二终端，如图7所示，图7示出了上述实施例中所涉及的第二终端的一种可能的结构示意图。该第二终端包括：接收模块701，发送模块702。其中，接收模块701，用于支持第二终端接收来自第一终端的第一信息和第三信息，发送模块702，用于支持第二终端执行图4中的步骤402。其中，上述方法实施例涉及的各步骤的所有相关内容均可援引到对应功能模块的功能描述，在此不再赘述。
图8示出了上述实施例所涉及的第一终端的另一种可能的结构示意图，如图8所示，该第一终端包括：处理器802，收发器803，存储器801以及总线804.其中，收发器803、处理器802以及存储器801通过总线804相互连接；总线804可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图8中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
其中，存储器801用于存储第一终端的程序代码和数据。收发器803，用于支持第一终端与其他网络实体间的通信，例如用于支持第一终端执行图2中的步骤201和步骤203，以及图4中的步骤401。处理器803，用于对第一终端的动作进行控制，例如用于支持第一终端执行图5中的步骤501，和/或用于本文所描述的技术的其它过程。
图9示出了上述实施例所涉及的第二终端的另一种可能的结构示意图，如图9所示，该第二终端包括：处理器902，收发器903，存储器901以及总线904.其中，收发器903、处理器902以及存储器901通过总线904相互连接；总线904可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图8中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
其中，存储器901用于存储第二终端的程序代码和数据。收发器903，用于支持第二终端与其他网络实体间的通信，例如用于支持第二终端执行图4中的步骤402。处理器803，用于对第二终端的动作进行控制，例如用于支持第二终端执行图2中的步骤202，和/或用于本文所描述的技术的其它过程。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable  ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘，硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (18)

  1. 一种数据传输方法，其特征在于，包括：
    第一终端向第二终端发送第一信息，所述第一信息用于指示所述第二终端停止使用第一资源发送上行数据；
    所述第一终端使用所述第一资源发送上行数据。
  2. 根据权利要求1所述的数据传输方法，其特征在于，在所述第一终端向第二终端发送第一信息之前，所述方法还包括：
    所述第一终端接收来自所述第二终端的第二信息，所述第二信息包括所述第二终端用于上行数据传输的第二资源的信息。
  3. 根据权利要求2所述的数据传输方法，其特征在于，所述方法还包括：
    所述第一终端发送第三信息，所述第三信息用于请求获取所述第二终端用于上行数据传输的第二资源的信息。
  4. 根据权利要求2或3所述的数据传输方法，其特征在于，所述方法还包括：
    所述第一终端根据所述第二资源确定所述第一终端用于上行数据传输的所述第一资源，所述第一资源为所述第二资源中的一部分或全部。
  5. 根据权利要求1至4任一项所述的数据传输方法，其特征在于，所述第一终端为高可靠低时延通信URLLC业务终端，所述第二终端为移动宽带增强eMBB业务终端。
  6. 一种数据传输方法，其特征在于，包括：
    第二终端接收来自第一终端的第一信息，所述第一信息用于指示所述第二终端停止使用第一资源发送上行数据；
    所述第二终端停止使用所述第一资源发送上行数据。
  7. 根据权利要求6所述的数据传输方法，其特征在于，在所述第二终端接收来自第一终端的第一信息之前，所述方法还包括：
    所述第二终端向所述第一终端发送第二信息，所述第二信息包括所述第二终端用于上行数据传输的第二资源的信息。
  8. 根据权利要求7所述的数据传输方法，其特征在于，所述方法还包括：
    所述第二终端接收来自所述第一终端的第三信息，所述第三信息用于请求获取所述第二终端用于上行数据传输的第二资源的信息。
  9. 根据权利要求6至8任一项所述的数据传输方法，其特征在于，所述第一终端为高可靠低时延通信URLLC业务终端，所述第二终端为移动宽带增强eMBB业务终端。
  10. 一种数据传输装置，其特征在于，包括：
    确定模块，用于确定第一信息，所述第一信息用于指示第二终端停止使用第一资源发送上行数据；
    发送模块，用于向所述第二终端发送第一信息以及使用所述第一资源发送上行数据。
  11. 根据权利要求10所述的数据传输装置，其特征在于，所述装置还包括：
    接收模块，用于接收来自所述第二终端的第二信息，所述第二信息包括所述第二 终端用于上行数据传输的第二资源的信息。
  12. 根据权利要求11所述的数据传输装置，其特征在于，
    所述发送模块，还用于发送第三信息，所述第三信息用于请求获取所述第二终端用于上行数据传输的第二资源的信息。
  13. 根据权利要求11或12所述的数据传输装置，其特征在于，所述装置还包括：
    确定模块，用于根据所述第二资源确定所述发送模块用于上行数据传输的所述第一资源，所述第一资源为所述第二资源中的一部分或全部。
  14. 根据权利要求10至13任一项所述的数据传输装置，其特征在于，所述数据传输装置为高可靠低时延通信URLLC业务终端，所述第二终端为移动宽带增强eMBB业务终端。
  15. 一种数据传输装置，其特征在于，包括：
    接收模块，用于接收来自第一终端的第一信息，所述第一信息用于指示第二终端停止使用所述第一资源发送上行数据；
    发送模块，用于使用第二资源中除所述第一资源之外的资源发送上行数据。
  16. 根据权利要求15所述的数据传输装置，其特征在于，
    所述发送模块，还用于向所述第一终端发送第二信息，所述第二信息包括所述发送模块用于上行数据传输的第二资源的信息。
  17. 根据权利要求16所述的数据传输装置，其特征在于，
    所述接收模块，还用于接收来自所述第一终端的第三信息，所述第三信息用于请求获取所述发送模块用于上行数据传输的第二资源的信息。
  18. 根据权利要求15至17任一项所述的数据传输装置，其特征在于，所述第一终端为高可靠低时延通信URLLC业务终端，所述数据传输装置为移动宽带增强eMBB业务终端。
PCT/CN2018/076295 2017-02-28 2018-02-11 一种数据传输方法及装置 Ceased WO2018157732A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18760766.8A EP3579644B1 (en) 2017-02-28 2018-02-11 Data transmission method and apparatus
BR112019017420A BR112019017420A2 (pt) 2017-02-28 2018-02-11 método e aparelho para transmissão de dados e sistema de comunicação
US16/552,371 US11083004B2 (en) 2017-02-28 2019-08-27 Data transmission method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710114720.4 2017-02-28
CN201710114720.4A CN108513358A (zh) 2017-02-28 2017-02-28 一种数据传输方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/552,371 Continuation US11083004B2 (en) 2017-02-28 2019-08-27 Data transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2018157732A1 true WO2018157732A1 (zh) 2018-09-07

Family

ID=63369752

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076295 Ceased WO2018157732A1 (zh) 2017-02-28 2018-02-11 一种数据传输方法及装置

Country Status (5)

Country Link
US (1) US11083004B2 (zh)
EP (1) EP3579644B1 (zh)
CN (1) CN108513358A (zh)
BR (1) BR112019017420A2 (zh)
WO (1) WO2018157732A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020034429A1 (en) * 2018-11-02 2020-02-20 Zte Corporation Methods, apparatus and systems for indicating uplink transmission resources related to various services

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109804657B (zh) 2016-09-28 2022-09-06 Idac控股公司 针对灵活无线电服务的5g nr数据传送
US11172471B2 (en) * 2017-01-05 2021-11-09 Motorola Mobility Llc Resource reservation
EP3635887B1 (en) * 2017-05-03 2021-10-20 Convida Wireless, LLC Infrastructure equipment, mobile terminal, computer software and methods
EP3827630A1 (en) * 2018-07-25 2021-06-02 Sony Corporation Base station, user equipment, circuitry, mobile telecommunications system and method
WO2020056782A1 (en) 2018-09-22 2020-03-26 Qualcomm Incorporated Preemption indication for dl multiplexing of embb and urllc with non-coherent joint transmission
CN111510872B (zh) * 2019-01-11 2022-01-18 中国信息通信研究院 一种车联网通信信道预占用通知方法、装置和系统
WO2020215192A1 (zh) * 2019-04-22 2020-10-29 Oppo广东移动通信有限公司 用于无线通信的方法和设备
CN110278614B (zh) * 2019-06-24 2020-12-18 西安理工大学 一种数据信道的传输方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104919878A (zh) * 2013-01-09 2015-09-16 夏普株式会社 终端装置以及基站装置
CN104955156A (zh) * 2014-03-26 2015-09-30 华为技术有限公司 一种数据发送方法、装置、基站及用户设备
CN105338635A (zh) * 2014-08-06 2016-02-17 电信科学技术研究院 一种业务传输的方法和设备
US20160352551A1 (en) * 2015-06-01 2016-12-01 Liqing Zhang System and scheme of scalable ofdm numerology
GB2558564A (en) * 2017-01-05 2018-07-18 Tcl Communication Ltd Methods and devices for downlink resource sharing between URLLC and eMBB transmissions in wireless communication systems

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8744465B2 (en) 2005-06-16 2014-06-03 Qualcomm Incorporated Resource allocation method in a communication system
US8830947B2 (en) 2011-08-30 2014-09-09 Broadcom Corporation Channel sensing in uplink transmission
US10021536B2 (en) * 2013-09-27 2018-07-10 Kyocera Corporation Communication control method and user terminal for selecting a D2D synchronization reference
WO2015135214A1 (zh) * 2014-03-14 2015-09-17 华为技术有限公司 数据传输方法、用户设备及基站

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104919878A (zh) * 2013-01-09 2015-09-16 夏普株式会社 终端装置以及基站装置
CN104955156A (zh) * 2014-03-26 2015-09-30 华为技术有限公司 一种数据发送方法、装置、基站及用户设备
CN105338635A (zh) * 2014-08-06 2016-02-17 电信科学技术研究院 一种业务传输的方法和设备
US20160352551A1 (en) * 2015-06-01 2016-12-01 Liqing Zhang System and scheme of scalable ofdm numerology
GB2558564A (en) * 2017-01-05 2018-07-18 Tcl Communication Ltd Methods and devices for downlink resource sharing between URLLC and eMBB transmissions in wireless communication systems

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3579644A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020034429A1 (en) * 2018-11-02 2020-02-20 Zte Corporation Methods, apparatus and systems for indicating uplink transmission resources related to various services
US11997688B2 (en) 2018-11-02 2024-05-28 Zte Corporation Methods, apparatus and systems for indicating uplink transmission resources related to various services

Also Published As

Publication number Publication date
EP3579644A4 (en) 2020-01-22
EP3579644A1 (en) 2019-12-11
EP3579644B1 (en) 2023-05-24
US20190387538A1 (en) 2019-12-19
CN108513358A (zh) 2018-09-07
US11083004B2 (en) 2021-08-03
BR112019017420A2 (pt) 2020-04-07

Similar Documents

Publication Publication Date Title
US11083004B2 (en) Data transmission method and apparatus
CN114726829B (zh) 通信方法、用户面网关及通信系统
CN109542614B (zh) 资源配置方法、装置、终端及存储介质
WO2019084714A1 (zh) 系统信息发送方法、装置、计算机设备及存储介质
CN112491978B (zh) 一种调度方法和设备
WO2017113130A1 (zh) 一种资源请求方法、设备、网络侧节点及系统
CN113301513A (zh) 基于VoLTE的彩铃业务处理方法、设备和存储介质
CN109640289A (zh) 一种通信方法及设备、通信系统
CN112867156A (zh) 信道占用时间确定方法、装置、第一通信节点及存储介质
KR102329095B1 (ko) 네트워크 접속 방법, 관련 기기 및 시스템
CN107249194A (zh) 管理无线网络连接的方法、装置及设备
CN110113781A (zh) 缓冲区状态报告的上报、资源分配方法、终端及网络设备
CN110959300B (zh) 数据传输方法、装置、设备、系统及存储介质
JP2017531336A (ja) トランキング通信サービス処理方法、コアネットワーク装置、及びｕｅ、記憶媒体
CN111131846A (zh) 视频播放方法、多媒体播放设备、边缘服务器和核心网
CN115720367A (zh) 直连链路通信方法、装置、设备及存储介质
US20210377972A1 (en) Transmission configuration method and apparatus, device, system, and storage medium
CN111148171B (zh) 通话切换方法及服务器
CN113170350B (zh) 资源确定方法及相关设备
US12177883B2 (en) Signal transmission method and apparatus, mobile terminal, and storage medium
US12309779B2 (en) Resource configuration method and apparatus, terminal, and non-volatile storage medium
WO2018049627A1 (zh) 一种集群组呼处理方法、相关设备和系统
CN106413123B (zh) 数据传输方法及装置
CN110944305A (zh) 一种v2x双模终端的数据传输方法、4g基站及终端
WO2017177822A1 (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: 18760766

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019017420

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2018760766

Country of ref document: EP

Effective date: 20190902

ENP Entry into the national phase

Ref document number: 112019017420

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190821