WO2019154039A1 - 一种发送和接收上行数据的方法、装置及系统 - Google Patents

一种发送和接收上行数据的方法、装置及系统 Download PDF

Info

Publication number
WO2019154039A1
WO2019154039A1 PCT/CN2019/072238 CN2019072238W WO2019154039A1 WO 2019154039 A1 WO2019154039 A1 WO 2019154039A1 CN 2019072238 W CN2019072238 W CN 2019072238W WO 2019154039 A1 WO2019154039 A1 WO 2019154039A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
data
time domain
carrier
terminal device
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/CN2019/072238
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 EP19750517.5A priority Critical patent/EP3737191A4/en
Publication of WO2019154039A1 publication Critical patent/WO2019154039A1/zh
Priority to US16/991,291 priority patent/US20200374904A1/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/02—Selection of wireless resources by user or terminal
    • 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/0446—Resources in time domain, e.g. slots or frames
    • 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/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/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, device, and system for transmitting and receiving uplink data.
  • the fifth generation mobile communication (the 5th generation, 5G) new radio (NR) supports the frequency band below 6 gigahertz (GHz) (referred to as sub6G band) to the 60GHz band, when the terminal equipment in NR adopts sub6G
  • GHz gigahertz
  • the high-frequency carrier in the frequency band to the 60 GHz band transmits uplink data
  • the path loss is high due to the large path loss on the high-frequency carrier, but the uplink device is not limited by the cost and power consumption of the terminal device.
  • the transmit power increases the coverage of the uplink. Therefore, when the terminal device uses the high-frequency carrier to transmit the uplink data, if the terminal device is an edge terminal device and is far away from the base station, the base station may not receive the terminal device.
  • the frequency band below 3 GHz (sub3 GHz for short) is supported.
  • the uplink data transmission in the NR can be compared with the uplink data in the LTE.
  • the carrier on the shared sub3GHz frequency band is transmitted.
  • the carrier on the sub3GHz frequency band is a low frequency carrier, and the path loss is small, thereby helping to improve the uplink coverage.
  • the LTE-supported frequency band shared by the NR so the carrier in the sub3 GHz band may be referred to as a supplementary uplink frequency (SUL) carrier, and the carriers in other frequency bands may be referred to as non-SUL carriers.
  • SUL supplementary uplink frequency
  • the embodiments of the present application provide a method, device, and system for transmitting and receiving uplink data, which are helpful for improving the possibility of successful uplink data transmission.
  • the method for sending uplink data in the embodiment of the present application includes:
  • the terminal device receives the control information sent by the network device, where the control information is used to indicate that the terminal device sends the first data on the first resource, where the first resource and the terminal device send the second data
  • the terminal device stops transmitting the first data in the first time domain on the first resource; the first The frequency domain corresponding to the resource belongs to the first carrier, and the frequency domain corresponding to the second resource belongs to the second carrier.
  • the terminal device stops sending the first data in the first time domain on the first resource, which effectively supports The uplink data transmission of the terminal device that simultaneously transmits data on the resources of different carriers is not supported, and further, the uplink data transmission conflict is avoided, and the possibility of uplink data transmission failure is reduced.
  • the frequency of the first carrier is greater than the frequency of the second carrier.
  • the terminal device sends the second data in the first time domain range.
  • the terminal device on the first resource, is in a second time domain range before the first time domain range and/or a third time after the first time domain range. Stop transmitting the first data in a time domain range, wherein a termination time of the second time domain range coincides with a start time of the first time domain range, a termination time of the first time domain range, and the The starting moments of the third time domain range coincide.
  • the length of the second time domain range and/or the length of the third time domain range is predefined; or the length of the second time domain range and/or the The length of the third time domain range is that the network device indicates to the terminal device by using indication information.
  • the second carrier is a supplemental uplink frequency (SUL) carrier
  • the first carrier is a non-SUL carrier
  • the second data is ultra reliable and low latency communications (URLLC) traffic data.
  • URLLC ultra reliable and low latency communications
  • the second aspect, the method for receiving uplink data in the embodiment of the present application includes:
  • Control information sent by the network device to the terminal device where the control information is used to indicate that the terminal device sends the first data on the first resource; if the network device is received on the second resource in the first time domain Determining, by the second data sent by the terminal device, that the terminal device stops transmitting the first data on the first resource, in the first time domain; the second resource and the first A resource overlaps the first time domain in the time domain, the frequency domain corresponding to the first resource belongs to the first carrier, and the frequency domain corresponding to the second resource belongs to the second carrier.
  • the terminal device stops transmitting the first data on the first resource in the first time domain, if the network device is on the first resource, If the third data is received in the first time domain, the third data is not decoded or the like, or the third data is discarded.
  • the frequency of the first carrier is greater than the frequency of the second carrier.
  • the network device determines that, on the first resource, the terminal device is in a second time domain range before the first time domain range and/or the first time domain Stop transmitting the first data in a third time domain range after the range, where a termination time of the second time domain range coincides with a start time of the first time domain range, where the first time domain range The termination time coincides with the start time of the third time domain range.
  • the length of the second time domain range and/or the length of the third time domain range is predefined; or the length of the second time domain range and/or the The length of the third time domain range is that the network device indicates to the terminal device by using indication information.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the second data is URLLC service data.
  • the third aspect, the method for sending uplink data in the embodiment of the present application includes:
  • the terminal device determines a first resource for sending the unscheduled uplink data, where the frequency domain corresponding to the first resource belongs to the first bandwidth portion or the second bandwidth portion, and the first bandwidth portion and the second bandwidth portion Configuring, for the network device, an activated bandwidth portion of the terminal device, and the first bandwidth portion is an activated bandwidth portion on the first carrier, and the second bandwidth portion is an activated bandwidth portion on the second carrier; then, The terminal device sends the unscheduled uplink data to the network device by using the first resource.
  • the scheduling is sent to the network device on the first resource.
  • Uplink data helps to improve the reliability of unscheduled uplink data transmission.
  • the frequency of the second carrier is smaller than the frequency of the first carrier, and the frequency domain range corresponding to the first resource belongs to the second bandwidth portion.
  • the second resource configured to send the unscheduled uplink data is not activated on the first bandwidth portion, or the first bandwidth portion is not configured to send the The second resource of the unscheduled uplink data.
  • another implementation manner of the second bandwidth portion of the frequency domain range data corresponding to the first resource that is used by the terminal device to send the unscheduled uplink data is: The terminal device receives the configuration information sent by the network device, where the configuration information is used to indicate that the frequency domain range corresponding to the resource used by the terminal device to send the unscheduled uplink data belongs to the second bandwidth portion.
  • the frequency domain resource used by the terminal device to send uplink data is the first bandwidth portion
  • the first delay is less than or equal to a preset threshold
  • the first resource corresponds to The frequency domain range belongs to the second bandwidth portion; wherein the first time delay includes a time of switching from the first bandwidth portion to the second bandwidth portion and a time of reaching the first resource.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the unscheduled uplink data is URLLC service data.
  • the method for receiving uplink data in the embodiment of the present application includes:
  • the network device configures the first bandwidth portion and the second bandwidth portion for the terminal device, the first bandwidth portion is an activated bandwidth portion on the first carrier, and the second bandwidth portion is an activated bandwidth portion on the second carrier;
  • the network device receives the unscheduled uplink data sent by the terminal device on the first resource, where the frequency domain range corresponding to the first resource belongs to the first bandwidth portion or the second bandwidth portion.
  • the frequency of the second carrier is smaller than the frequency of the first carrier, and the frequency domain range corresponding to the first resource belongs to the second bandwidth portion.
  • the second resource configured to send the unscheduled uplink data is not activated on the first bandwidth portion, or the first bandwidth portion is not configured to send the The second resource of the unscheduled uplink data.
  • another implementation manner of the second bandwidth portion of the frequency domain range data corresponding to the first resource that is used by the terminal device to send the unscheduled uplink data is: The configuration information sent by the network device to the terminal device, where the configuration information is used to indicate that the frequency domain range corresponding to the resource used by the terminal device to send the unscheduled uplink data belongs to the second bandwidth portion.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the unscheduled uplink data is URLLC service data.
  • the fifth aspect, the method for initial access in the embodiment of the present application includes:
  • the terminal device receives a first system information block indicating a resource location for initial access on the first carrier, and a second system information block, where the second system information block is used to indicate the second carrier a resource location for initial access, where a frequency of the first carrier is greater than a frequency of the second carrier;
  • the terminal device performs initial access through the second carrier when at least one of the following conditions is met;
  • the service type of the data to be sent in the initial access process is a preset type, the data quantity of the data to be transmitted in the initial access process is less than the first threshold, and the signal receiving quality on the first carrier is less than the second threshold.
  • the data of the data to be sent in the initial access process is a preset type, and the data of the data to be sent in the initial access process is satisfied.
  • the initial access by using the second carrier helps improve the reliability of data transmission during the initial access process. .
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the preset type includes the type of URLLC service data.
  • the sixth aspect, the method for initial access in the embodiment of the present application includes:
  • the network device sends a first system information block indicating a resource location for initial access on the first carrier, and a second system information block, where the second system information block is used to indicate the second carrier a resource location for initial access, the frequency of the first carrier is greater than a frequency of the second carrier; and then the network device passes the second when the terminal device meets at least one of the following conditions Receiving, by the carrier, data sent during the initial access process of the terminal device;
  • the service type of the data to be sent by the terminal device in the initial access process is a preset type, the data quantity of the data to be sent by the terminal device in the initial access process is less than a first threshold, and the terminal device is in the first The signal reception quality on one carrier is less than the second threshold.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the preset type includes the type of URLLC service data.
  • the device of the embodiment of the present invention includes a transceiver module and a processing module, where the transceiver module is configured to receive control information sent by a network device, where the control information is used to indicate that the device sends the first resource.
  • First data wherein, when the first resource and the second resource used by the transceiver module to send the second data overlap in the first time domain range in the time domain, on the first resource, the The processing module is configured to trigger the transceiver module to stop sending the first data in the first time domain; the frequency domain corresponding to the first resource belongs to a first carrier, and the frequency domain corresponding to the second resource The range belongs to the second carrier.
  • the frequency of the first carrier is greater than the frequency of the second carrier.
  • the transceiver module is further configured to send the second data on the second resource in the first time domain.
  • the processing module is further configured to: trigger the transceiver module to be on the first resource, in a second time domain range before the first time domain range, and/or the first Stop transmitting the first data in a third time domain range after a time domain range, where a termination time of the second time domain range coincides with a start time of the first time domain range, the first time The termination time of the domain range coincides with the start time of the third time domain range.
  • the length of the second time domain range and/or the length of the third time domain range is predefined; or the transceiver module is further configured to receive the network device to send The indication information is used to indicate the length of the second time domain range and/or the length of the third time domain range.
  • the second carrier is a SUL carrier
  • the first carrier is a non-SUL carrier
  • the second data is URLLC service data.
  • the hardware implementation manner of the transceiver module is a transceiver, and the transceiver includes a receiver and a transmitter, wherein the receiver and the transmitter may be independent hardware units, or may be integrated into one hardware unit.
  • the application embodiment is not limited, and the hardware implementation corresponding to the processing module is a processor.
  • a chip is further provided, wherein the chip is respectively connected to a transceiver and a memory, configured to read and execute a program stored in the memory, and trigger the transceiver to implement the first aspect and the first aspect.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a computer program, where the computer program is executed by the processor, to implement the first aspect and any one of the first aspects The design of the method of sending upstream data.
  • the device of the embodiment of the present application includes a transceiver module and a processing module, where the transceiver module is configured to send control information to the terminal device, where the control information is used to indicate that the terminal device sends the first resource.
  • the first data; the processing module is configured to: if the transceiver module receives the second data sent by the terminal device on the second resource, in the first time domain, determining that the terminal device is in the first Stop transmitting the first data on a resource in the first time domain; the second resource and the first resource are coincident in the first time domain range in a time domain, and the first resource
  • the corresponding frequency domain range belongs to the first carrier, and the frequency domain range corresponding to the second resource belongs to the second carrier.
  • the frequency of the first carrier is greater than the frequency of the second carrier.
  • the processing module is further configured to determine, on the first resource, the terminal device is in a second time domain range before the first time domain range and/or Stop transmitting the first data in a third time domain range after the first time domain range, where a termination time of the second time domain range coincides with a start time of the first time domain range, the first The end time of the time domain range coincides with the start time of the third time domain range.
  • the length of the second time domain range and/or the length of the third time domain range is predefined; or the transceiver module is further configured to send to the terminal device And indication information, where the indication information is used to indicate a length of the second time domain range and/or a length of the third time domain range.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the second data is URLLC service data.
  • the hardware implementation manner of the transceiver module is a transceiver, and the transceiver includes a receiver and a transmitter, wherein the receiver and the transmitter may be independent hardware units, or may be integrated into one hardware unit.
  • the application embodiment is not limited, and the hardware implementation corresponding to the processing module is a processor.
  • a chip is further provided, wherein the chip is respectively connected to a transceiver and a memory, configured to read and execute a program stored in the memory, and trigger the transceiver to implement the second aspect and the second aspect.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a computer program, where the computer program is executed by the processor, to implement the second aspect and any one of the second aspects The method of receiving uplink data.
  • the device of the embodiment of the present application includes a transceiver module and a processing module, where the processing module is configured to determine a first resource for sending the unscheduled uplink data, and the frequency domain range corresponding to the first resource A first bandwidth portion or a second bandwidth portion, the first bandwidth portion and the second bandwidth portion being an activated bandwidth portion configured by the network device to the device, and the first bandwidth portion is on the first carrier And the second bandwidth portion is an activated bandwidth portion on the second carrier; the transceiver module is configured to send the unscheduled uplink data to the network device by using the first resource.
  • the frequency of the second carrier is smaller than the frequency of the first carrier, and the frequency domain range corresponding to the first resource belongs to the second bandwidth portion.
  • the second resource configured to send the unscheduled uplink data is not activated on the first bandwidth portion, or the first bandwidth portion is not configured to send the The second resource of the unscheduled uplink data.
  • the transceiver module is further configured to receive configuration information sent by the network device, where the configuration information is used to indicate, used by the transceiver module, to send the unscheduled uplink data.
  • the frequency domain range corresponding to the resource belongs to the second bandwidth portion.
  • the first delay when the frequency domain resource used by the transceiver module to send uplink data is the first bandwidth portion, if the first delay is less than or equal to a preset threshold, the first resource corresponds to The frequency domain range belongs to the second bandwidth portion; wherein the first time delay includes a time of switching from the first bandwidth portion to the second bandwidth portion and a time of reaching the first resource.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the unscheduled uplink data is URLLC service data.
  • the hardware implementation manner of the transceiver module is a transceiver, and the transceiver includes a receiver and a transmitter, wherein the receiver and the transmitter may be independent hardware units, or may be integrated into one hardware unit.
  • the application embodiment is not limited, and the hardware implementation corresponding to the processing module is a processor.
  • a chip is further provided, wherein the chip is respectively connected to a transceiver and a memory, configured to read and execute a program stored in the memory, and trigger the transceiver to implement the third aspect and the third aspect.
  • the chip is respectively connected to a transceiver and a memory, configured to read and execute a program stored in the memory, and trigger the transceiver to implement the third aspect and the third aspect.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a computer program, where the computer program is executed by the processor, to implement any of the third aspect and the third aspect.
  • the apparatus of the embodiment of the present application includes a transceiver module and a processing module, where the processing module is configured to configure a first bandwidth part and a second bandwidth part, where the first bandwidth part is a first carrier And the second bandwidth portion is an activated bandwidth portion on the second carrier; the transceiver module is configured to receive, on the first resource, the unscheduled uplink data sent by the terminal device, where the first resource corresponds to The frequency domain range belongs to the first bandwidth portion or the second bandwidth portion.
  • the frequency of the second carrier is smaller than the frequency of the first carrier, and the frequency domain range corresponding to the first resource belongs to the second bandwidth portion.
  • the second resource configured to send the unscheduled uplink data is not activated on the first bandwidth portion, or the first bandwidth portion is not configured to send the The second resource of the unscheduled uplink data.
  • the transceiver module is further configured to send configuration information to the terminal device, where the configuration information is used to indicate a resource used by the terminal device to send the unscheduled uplink data.
  • the corresponding frequency domain range belongs to the second bandwidth portion.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the unscheduled uplink data is URLLC service data.
  • the hardware implementation manner of the transceiver module is a transceiver, and the transceiver includes a receiver and a transmitter, wherein the receiver and the transmitter may be independent hardware units, or may be integrated into one hardware unit.
  • the application embodiment is not limited, and the hardware implementation corresponding to the processing module is a processor.
  • a chip is further provided, wherein the chip is respectively connected to a transceiver and a memory, for reading and executing a program stored in the memory, and triggering the transceiver to implement the fourth aspect and the fourth aspect Any of a number of possible designs for receiving upstream data.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a computer program, where the computer program is executed by the processor, to implement any of the fourth aspect and the fourth aspect.
  • the method of receiving uplink data is not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, but not limited to, the embodiment of the present application.
  • the device of the embodiment of the present application includes a transceiver module and a processing module, where the transceiver module is configured to receive a first system information block and a second system information block, where the first system information block indicates the first carrier a resource location for initial access, where the second system information block is used to indicate a resource location for initial access on the second carrier, where a frequency of the first carrier is greater than a frequency of the second carrier;
  • the processing module performs initial access by using the second carrier when at least one of the following conditions is met;
  • the service type of the data to be sent in the initial access process is a preset type, the data quantity of the data to be transmitted in the initial access process is less than the first threshold, and the signal receiving quality on the first carrier is less than the second threshold.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the preset type includes the type of URLLC service data.
  • the hardware implementation manner of the transceiver module is a transceiver, and the transceiver includes a receiver and a transmitter, wherein the receiver and the transmitter may be independent hardware units, or may be integrated into one hardware unit.
  • the application embodiment is not limited, and the hardware implementation corresponding to the processing module is a processor.
  • a chip is further provided, where the chip is respectively connected to a transceiver and a memory, for reading and executing a program stored in the memory, and triggering the transceiver to implement the fifth aspect and the fifth aspect The method of initial access to any of the possible designs.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a computer program, where the computer program is executed by the processor, to implement any of the fifth aspect and the fifth aspect.
  • the method of initial access to the design is not limited to a computer storage medium, wherein the computer storage medium stores a computer program, where the computer program is executed by the processor, to implement any of the fifth aspect and the fifth aspect. The method of initial access to the design.
  • the apparatus of the embodiment of the present application includes a receiving module and a sending module, where the sending module is configured to send a first system information block and a second system information block, where the first system information block indicates the first carrier And a resource location for initial access, where the second system information block is used to indicate a resource location for initial access on the second carrier, where a frequency of the first carrier is greater than a frequency of the second carrier;
  • the receiving module is configured to receive data sent by the terminal device during an initial access process by using the second carrier when the terminal device meets at least one of the following conditions;
  • the service type of the data to be sent by the terminal device in the initial access process is a preset type, the data quantity of the data to be sent by the terminal device in the initial access process is less than a first threshold, and the terminal device is in the first The signal reception quality on one carrier is less than the second threshold.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the preset type includes the type of URLLC service data.
  • the hardware implementation manner of the receiving module is a receiver
  • the hardware implementation manner of the sending module is a transmitter
  • the function of the receiver and the function of the transmitter can be integrated into one hardware module, collectively referred to as a transceiver, and received.
  • the transceiver and transceiver can also be separate hardware units.
  • a chip is further provided, wherein the chip is respectively connected to a transceiver and a memory, configured to read and execute a program stored in the memory, and trigger the transceiver to implement the sixth aspect and the sixth aspect.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a computer program, where the computer program is executed by the processor, to implement any of the sixth aspect and the sixth aspect.
  • the method of initial access to the design
  • the embodiment of the present application further provides a communication system, including the apparatus of any one of the seventh aspect and the seventh aspect, and the apparatus of the eighth aspect and any one of the possible designs of the eighth aspect.
  • the embodiment of the present application further provides a communication system, including the apparatus of any one of the ninth aspect and the ninth aspect, and the apparatus of the tenth aspect and any one of the possible designs of the tenth aspect.
  • the embodiment of the present application further provides a communication system, including the apparatus of any one of the eleventh and eleventh aspects, and the apparatus of the twelfth aspect and any one of the possible designs of the twelfth aspect.
  • FIG. 1 is a schematic structural diagram of a possible mobile communication system to which an embodiment of the present application is applied;
  • FIG. 2 is a schematic flowchart of a method for transmitting uplink data in an embodiment of the present application
  • 3a-3c are schematic diagrams showing a first time domain range according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a first resource and a second resource according to an embodiment of the present application.
  • 5a to 5c are schematic diagrams showing a first resource and a second resource according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a first resource and a second resource according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another method for sending uplink data according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of GF resources of a non-SUL carrier and GF resources of a SUL carrier according to an embodiment of the present application;
  • FIG. 9 is a schematic diagram of GF resources of a non-SUL carrier and GF resources of a SUL carrier according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of GF resources of a non-SUL carrier and GF resources of a SUL carrier according to an embodiment of the present application;
  • FIG. 11 is a schematic flowchart of a method for initial access according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • 15 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • 16 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 20 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • 21 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 22 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • FIG. 23 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • 24 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • 25 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 26 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a possible mobile communication system to which an embodiment of the present application is applied.
  • the mobile communication system shown in FIG. 1 includes a network device and a terminal device. It should be understood that FIG. 1 is only a schematic structural diagram of a mobile communication system.
  • the number of network devices and the number of terminal devices in the mobile communication system are not limited, and the mobile communication system to which the embodiment of the present application is applied is not limited.
  • the device may also include other devices, such as a core network device, a wireless relay device, and a wireless backhaul device.
  • the network device in the embodiment of the present application may integrate all the functions in a single physical device, and may also distribute the functions on multiple independent physical devices, which is not limited in this embodiment.
  • the terminal device in the embodiment of the present application may be connected to the network device by using a wireless manner. It should be noted that the terminal device in the embodiment of the present application may be fixed or movable.
  • the network device in the embodiment of the present application is used to connect the terminal device to the mobile communication system.
  • the network device may be a base station (node B), an evolved base station (evolved node B, eNB), a base station in the 5G,
  • the specific technology and specific device configuration adopted by the network device are not limited in the base station or the access node in the wireless fidelity (WiFi) system in the future mobile communication system.
  • the terminal device in the embodiment of the present application may also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), and the like.
  • the terminal device may be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, and industrial control.
  • the wireless terminal in the wireless terminal, the wireless terminal in the smart city, the wireless terminal in the smart home, and the like are not limited.
  • the network device and the terminal device in the embodiments of the present application may be deployed on land, including indoor or outdoor, handheld or in-vehicle; or may be deployed on the water surface; and may also be deployed on aircraft, balloons, and artificial satellites in the air.
  • the application scenarios of the network device and the terminal device are not limited.
  • the communication between the network device and the terminal device and between the terminal device and the terminal device may be performed through an authorized spectrum, or may be performed through an unlicensed spectrum.
  • the communication between the licensed spectrum and the unlicensed spectrum is not limited.
  • Communication between the radio access network device and the terminal device and between the terminal device and the terminal device may be performed through a spectrum of 6 gigahertz (GHz) or less, or may be communicated through a spectrum of 6 GHz or higher, or may be used below 6 GHz.
  • the spectrum communicates with the spectrum above 6 GHz.
  • the embodiment of the present application does not limit the spectrum resources used between the network device and the terminal device.
  • the carrier may be referred to as a frequency band, a frequency band, a frequency domain range, or the like, and is a frequency domain resource having a certain bandwidth.
  • the carrier may be a SUL carrier or a non-SUL carrier.
  • the SUL carrier can also be referred to as a SUL band and a SUL band, and can be a low frequency frequency domain resource, such as a sub3 GHz band; for example, the SUL carrier can be used to improve the uplink coverage.
  • the non-SUL carrier may also be referred to as a non-SUL carrier, a non-SUL frequency band, a non-SUL frequency band, a non-SUL frequency band, etc., and may be a frequency domain resource having a higher frequency than the SUL carrier, such as a C-band (C-band),
  • the SUL carrier can also be referred to as a UL band.
  • the first carrier involved in the embodiment of the present application may be a non-SUL carrier, and the second carrier may be a SUL carrier.
  • the SUL carrier and the non-SUL carrier may belong to the same cell.
  • the data involved in the embodiments of the present application may be general data, enhanced mobile broadband (eMBB) service data, mass machine type communications (mMTC) service data, and high reliability low latency communication (ultra) Reliable and low latency communications, URLLC), etc.
  • eMBB enhanced mobile broadband
  • mMTC mass machine type communications
  • URLLC high reliability low latency communication
  • Typical eMBB services include: ultra high definition video, augmented reality (AR), virtual reality ( Virtual reality, VR), etc.
  • the main features of mMTC service are huge number of networked devices, small amount of transmitted data, and insensitivity to data transmission delay.
  • Typical mMTC services include: smart grid distribution automation, smart city, etc.; URLLC service
  • the main features are ultra-high reliability, low latency, low transmission data and burstiness.
  • Typical URLLC services include: wireless control in industrial manufacturing or production processes, driverless cars and drones. Motion control and tactile interaction applications such as remote repair and remote surgery.
  • the first data in the embodiment of the present application may be the data of the service type that is not required for the delay, such as the eMBB service data or the mMTC service data.
  • the second data in the embodiment of the present application may be the uplink based on the network device scheduling. Data or non-scheduled uplink data, such as eMBB service data, mMTC service data, URLLC service data, etc., are not limited thereto.
  • the mechanism for scheduling the unscheduled transmission in the embodiment of the present application is: the network device is a terminal device that is semi-statically configured to send the resource of the unscheduled uplink data, and the terminal device can obtain the uplink data without scheduling when the network device needs to send the unscheduled uplink data to the network device.
  • the device sends the unscheduled uplink data on the resource configured by the terminal device for sending the unscheduled uplink data.
  • the uplink device that sends the unscheduled uplink data may be called the grant free uplink transmission or the configured grant uplink transmission.
  • the uplink grant (UL grant) is not required to be sent to the terminal device, and therefore, the network device is configured to send the uplink grant (UL grant).
  • the resource of the uplink data can also be called a GF (grant free) resource.
  • the network device may be semi-static for the terminal device through high layer signaling (such as radio resource control (RRC) signaling) and/or physical layer signaling (such as downlink control information (DCI)). Configure GF resources.
  • RRC radio resource control
  • DCI downlink control information
  • the unscheduled uplink data in the embodiment of the present application is usually data of a service type that requires a higher delay, such as URLLC service data.
  • the bandwidth part in the embodiment of the present application may be referred to as a BWP (bandwidth part), or a carrier bandwidth part, a frequency resource part, a partial frequency resource, or other name.
  • the BWP may be part or all of the frequency domain resources on the carrier, and may be It is a continuous frequency domain resource, and may also be a discontinuous frequency domain resource.
  • the BWP may include multiple consecutive subcarriers.
  • the BWP may include multiple consecutive resource blocks (PRBs) and the like. Continuous frequency domain resources help to reduce the complexity of resource allocation.
  • the terminal device can support multiple BWPs, that is, the network device can configure multiple BWPs for the terminal device.
  • multiple BWPs may or may not overlap.
  • the subcarrier spacing of the frequency domain resources included in different BWPs may be the same or different.
  • the subcarrier spacing is a frequency domain length of a resource element (RE), and the value may include 15 kHz, 30 kHz, or 60 kHz.
  • the terminal device can only use the GF resources activated in the multiple BWPs configured by the network device for the terminal device to send the unscheduled uplink data.
  • the GF resource may also be activated and deactivated.
  • the network device may configure multiple BWPs for the terminal device, configure GF resources on each BWP, and indicate to the terminal devices which GF resources on the BWP are activated, and the terminal device selects to send the GF resources in the activated GF resources.
  • the resource of the uplink data is scheduled; or, in another case, the network device configures the GF resource for the terminal device, and the GF resource is not activated or deactivated during the specific implementation. For example, the network device configures multiple devices for the terminal device. In the BWP, if GF resources are configured on multiple BWPs, the GF resources configured on the BWPs are activated on the terminal device side. In this case, the network devices do not need to send responses to the terminal devices. An indication that the GF resource on the BWP is activated.
  • a method for transmitting uplink data in the embodiment of the present application is specifically described below with reference to FIG.
  • the method for sending uplink data in the embodiment of the present application includes the following steps.
  • Step 201 The network device sends control information to the terminal device, where the control information is used to instruct the terminal device to send the first data on the first resource.
  • control information of the embodiment of the present application may be a DCI, and may be other predefined information and the like, which is not limited thereto.
  • Step 202 After receiving the control information, the terminal device, when the first resource and the second resource for sending the second data by the terminal device overlap in the first time domain range in the time domain, on the first resource, first The first data is stopped in the time domain, and the frequency domain corresponding to the first resource belongs to the first carrier, and the frequency domain corresponding to the second resource belongs to the second carrier.
  • the understanding of the first time domain range in the embodiment of the present application may be as shown in FIG. 3a, as shown in FIG. 3b, or as shown in FIG. 3c; wherein, in FIG. 3a, FIG. 3b and FIG. 3c, time is The domain range 1 is the time domain range of the first resource in the time domain, and the time domain range 2 is the time domain range of the second resource in the time domain, and the first time domain range is the coincidence of the time domain range 1 and the time domain range 2. section.
  • the first data is uplink data scheduled by the network device, and the network device sends the first data to the terminal device by using the control information, where the first data type and the first data are sent.
  • the type of the two data can be different.
  • the first data may be data of a service type that does not require high latency, such as eMBB service data or mMTC service data;
  • the second data may be uplink data scheduled by the network device, or may be uplink data that is not scheduled.
  • the network device indicates, by using the control information, that the second data is sent to the terminal device on the second resource, and if the second data is the unscheduled uplink data, the terminal device determines
  • the second resource may be a GF resource, or may be a GB (grant based) resource, where the GB resource is a resource for the terminal device to send uplink data scheduled by the network device.
  • the second data may be eMBB service data, mMTC service data, URLLC service data, and the like, which are not limited thereto.
  • the uplink data that is not scheduled to be scheduled may be sent on the resource used for sending the unscheduled uplink data, and the uplink data scheduled by the network device is not required to be indicated by the network device by using the control information. Sent on the resource.
  • the terminal device when the first resource and the second resource overlap in the first time domain range in the time domain, the terminal device stops sending the first data in the first time domain on the first resource, and is effective. Uplink data transmission of a terminal device that does not support data transmission on resources on different carriers is supported.
  • the frequency of the first carrier to which the frequency domain corresponding to the first resource belongs and the frequency of the second carrier to which the frequency domain corresponding to the second resource belongs may not be limited.
  • the frequency of the carrier is small, the uplink coverage is large, which helps to improve the reliability of the uplink data transmission. Therefore, in the embodiment of the present application, the frequency of the first carrier is greater than the frequency of the second carrier, for example, The first carrier is a non-SUL carrier, and the second carrier is a SUL carrier.
  • the frequency of the first carrier is greater than the frequency of the second carrier, the coverage of the first carrier is smaller than the coverage of the second carrier, so the second resource is used. Sending the second data helps to improve the reliability of the second data transmission.
  • the first data and the second data when the first data and the second data are not highly reliable or the delay requirement is not high, the first data and the second resource may not be sent in the first time domain range at the same time.
  • the second data when the second data is data of a service type that requires a high latency and reliability, such as a URLLC, the present application is implemented to ensure a service such as a URLLC that has a high latency and high reliability.
  • the examples provide the following specific implementations.
  • the terminal device stops transmitting the first data in the first time domain; on the second resource, the terminal device sends the second data in the first time domain.
  • the resource 1 is the first resource
  • the time domain range 1 is the time domain range in which the resource 1 transmits the first data in the time domain
  • the resource 2 is the second resource
  • the time domain range 2 is the resource 2
  • the time t1 is the start time of transmitting the first data in the time domain range 1
  • the time t2 is the start time of sending the second data in the time domain range 2
  • the time t3 is time
  • the end time of the first data is sent in the domain range 1
  • the time t4 is the end time of the second data in the time domain range 2
  • t1 is less than or equal to t2
  • t3 is greater than or equal to t4.
  • the one-time domain range is the time domain range 2.
  • the terminal device stops transmitting the first data on the resource 1 from the time t2 until the time t4, and sends the second data on the resource 2 from the time t2 until the time t4. Then, after ending the transmission of the second data on the resource 2 at time t4, the first data may be transmitted on the resource 1 from the time t4 until the time t3, or the first data may not be continuously transmitted, or directly from the t4.
  • the first data is sent on the second carrier at the time of the time t3, which is not limited in this embodiment.
  • the time interval is reserved before the second data is sent, and/or the time interval is reserved after the second data is sent, in which the terminal device cannot send the first data on the first resource.
  • the terminal device stops transmitting the first data not only in the first time domain, but also in the second time domain range before the first time domain range and/or the first time domain range.
  • the start time coincides; on the second resource, the terminal device sends the second data in the first time domain.
  • the resource 1 is the first resource
  • the time domain range 1 is the time domain range in which the resource 1 sends the first data in the time domain
  • the resource 2 is the second resource
  • the time domain range 2 is the resource 2
  • the time domain range in which the second data is transmitted in the time domain the time t1 is the start time of transmitting the first data in the time domain range 1
  • the time t2 is the start time of sending the second data in the time domain range 2
  • the time t3 is time
  • the end time of the first data is transmitted in the domain range 1
  • the time t4 is the end time of transmitting the second data in the time domain range 2
  • the time t5 is the start time of stopping the transmission of the first data
  • the time t6 is the stop sending the first data.
  • ⁇ 1 is the second time domain range
  • ⁇ 2 is the third time domain range, where t1 ⁇ t5 ⁇ t2, t4 ⁇ t6 ⁇ t3, in the resource shown in FIG. 5a, the first time domain range is the time domain. Range 2.
  • the terminal device sends the first data on the resource 1 from the time t1 to the time t5, and stops transmitting the first data on the resource 1 from the time t5 until the time t6, starting from the time t2 until the time t4, The second data is sent on the resource 2.
  • the first data may continue to be transmitted on the resource 1 from the time t6 until the time t3, or the first data may not be sent, or the time starts from t4.
  • the first data is sent on the second carrier until the time t3, which is not limited in this embodiment.
  • the resource 1 is the first resource
  • the time domain range 1 is the time domain range in which the resource 1 transmits the first data in the time domain
  • the resource 2 is the second resource
  • the time domain range 2 is the resource 2.
  • Transmitting the time domain range of the second data in the time domain the time t1 is the start time of transmitting the first data in the time domain range 1
  • the time t2 is the start time of sending the second data in the time domain range 2
  • the time t3 is The end time of the first data is transmitted in the time domain range 1
  • the time t4 is the end time of the second data transmission in the time domain range 2
  • the ⁇ 2 is the third time domain range
  • t1 is greater than t2
  • t3 is greater than t4, as shown in FIG.
  • the first time domain range is the time domain range 3.
  • the terminal device sends the second data on the resource 2 from the time t2 until the time t4; stops transmitting the first data on the resource 1 from the time t1 until the time t4, and then starts from the time t5 until the time t3
  • the first data is sent on the resource 1, or the first data is not sent from the time t1 until the time t3, or the first data is sent on the second carrier from the time t4 until the time t3, which is not limited.
  • the resource 1 is the first resource
  • the time domain range 1 is the time domain range in which the resource 1 transmits the first data in the time domain
  • the resource 2 is the second resource
  • the time domain range 2 is the resource 2.
  • Transmitting the time domain range of the second data in the time domain the time t1 is the start time of transmitting the first data in the time domain range 1
  • the time t2 is the start time of sending the second data in the time domain range 2
  • the time t3 is The end time of the first data is transmitted in the time domain range 1
  • the time t4 is the end time of the second data transmission in the time domain range 2
  • ⁇ 1 is the second time domain range
  • t1 is smaller than t2, and t3 is smaller than t4, as shown in FIG.
  • the first time domain range is the time domain range 3.
  • the terminal device sends the first data on the resource 1 from the time t1 to the time t5, and stops transmitting the first data on the resource 1 from the time t5 until the time t3, starting from the time t2 until the time t4, The second data is sent on the resource 2.
  • the length of the second time domain range and/or the length of the third time domain range are predefined; or the length of the second time domain range and/or the The length of the three-time domain range is indicated to the network device by sending the indication information to the terminal device, wherein the indication information is used to indicate the length of the second time domain range and/or the length of the third time domain range.
  • the length of the second time domain range and the length of the third time domain range may be equal to 0 or greater than 0, which is not limited thereto, when the length of the second time domain range and the length of the third time domain range When it can be equal to 0, it is applicable to scenarios that do not consider carrier switching time.
  • the network device in the embodiment of the present application may send the indication information to the terminal device by using physical layer signaling (such as DCI) and/or high layer signaling (such as RRC signaling), or to the terminal device by using predefined signaling.
  • the indication information is sent, which is not limited in this embodiment of the present application.
  • the terminal device stops transmitting the first data in the first time domain; on the first resource, the terminal device sends the second data in the first time domain.
  • the resource consisting of resource 1, resource 2, and resource 3 is the first resource
  • resource 4 is the second resource
  • the time domain range 1 is that the first resource transmits the first data in the time domain.
  • the time domain range, the time domain range 2 is the time domain range in which the second resource transmits the second data in the time domain
  • the time t1 is the start time of transmitting the first data in the time domain range 1
  • the time t2 is the time domain range 2
  • the time t3 is the end time of transmitting the first data in the time domain range 1
  • the time t4 is the end time of transmitting the second data in the time domain range 2, in the resource as shown in FIG.
  • the first time domain range is the time domain range 2.
  • the terminal device sends the first data on the resource 1 from the time t1 until the time t2, and stops sending the first data on the resource 2 and the resource 3 from the time t2 until the time t4, starting from the time t2 until the t4
  • the second data is sent on the resource 2.
  • the terminal device may send the first data on the resource 1 from the time t4 until the time t3, or may directly send the first data on the second carrier, or may not
  • the first data is sent, which is not limited in this embodiment.
  • the terminal device sends the first data and the second data in a first time domain.
  • the resource consisting of resource 1, resource 2, and resource 3 is the first resource
  • resource 4 is the second resource
  • the time domain range 1 is that the first resource transmits the first data in the time domain.
  • the time domain range, the time domain range 2 is the time domain range in which the second resource transmits the second data in the time domain
  • the time t1 is the start time of transmitting the first data in the time domain range 1
  • the time t2 is the time domain range 2
  • the time t3 is the end time of transmitting the first data in the time domain range 1
  • the time t4 is the end time of transmitting the second data in the time domain range 2, in the resource as shown in FIG.
  • the first time domain range is the time domain range 2.
  • the terminal device sends the first data on the resource 1 from the time t1 until the time t2, and sends the first data and the second data on the resource 3 and the resource 2 from the time t2 to the time t4.
  • the terminal device may transmit the first data on the resource 1 from the time t4 until the time t3, or may not send the first data.
  • the terminal device can use the piggyback method to send the first data and The second data is co-encoded and then transmitted only within the time domain range 2 on resource 2 and resource 3.
  • the terminal device stops transmitting the first data on the first resource and the first time domain, and sends the second data on the second resource and in the first time domain, for the network device. If the network device receives the second data on the second resource and the first time domain, the network device determines to stop sending the first data on the first resource and in the first time domain, if the network device is in the first If data is received on a resource or in the first time domain, the data is directly discarded, or the data is not demodulated.
  • the first bandwidth portion and the second bandwidth portion are configured for the terminal device in the network device, and the first bandwidth portion is the bandwidth portion activated on the first carrier, and the second bandwidth portion is combined with the mobile communication system architecture shown in FIG.
  • the bandwidth portion activated on the second carrier a method for transmitting uplink data provided in this embodiment of the present application is described in detail.
  • another method for transmitting uplink data in the embodiment of the present application includes the following steps.
  • Step 701 The terminal device determines a first resource, where the frequency domain corresponding to the first resource belongs to the first bandwidth part or the second bandwidth part, where the first bandwidth part and the second bandwidth part are network devices. The portion of the bandwidth that is configured for activation of the terminal device.
  • Step 702 The terminal device sends the unscheduled uplink data to the network device by using the first resource.
  • the resources used to send the unscheduled uplink data are referred to as GF resources, and the embodiments of the present application are introduced.
  • the unscheduled uplink data is sent by using the GF resource on one of the two bandwidth portions of the activated bandwidth, thereby helping to reduce the exemption An error occurred during scheduled uplink data transmission.
  • the network device receives the More likely.
  • the terminal device determines that the frequency domain corresponding to the first resource is the second bandwidth part, that is, the reliability of the unscheduled data transmission.
  • the terminal device transmits the unscheduled uplink data on the GF resource on the second bandwidth portion.
  • the GF resource on the second bandwidth part sends the unscheduled uplink data: an optional manner is GF resources are not configured on a carrier, and GF resources are only configured on the second carrier.
  • GF resources can be configured on the first bandwidth part, and GF resources can be configured only on the second bandwidth part.
  • the GF resource is configured on the first carrier and the second carrier, only the GF resource on the second carrier is activated, and the GF resource on the first carrier is not activated;
  • the GF resource is configured in part and the second bandwidth part, only the GF resource on the second bandwidth part is activated, and the GF resource on the first bandwidth part is not activated;
  • another optional way is: by the network device
  • the terminal device sends the configuration information, where the configuration information is used to indicate the GF resource on the carrier used by the terminal device to send the unscheduled data, for example, the configuration information is used to indicate that the terminal device uses the sending
  • the frequency domain range corresponding to the GF resource of the uplink data is the second bandwidth part, or the configuration information is used to indicate that the frequency domain range corresponding to the GF resource used by the terminal device to send the unscheduled uplink data is not the first bandwidth part,
  • the configuration information is used to indicate that the frequency domain range corresponding to the GF resource that the terminal device uses to send the unscheduled
  • the GF resource that sends the unscheduled uplink data belongs to the second carrier, or the configuration information is used to indicate that the terminal device preferentially uses the GF resource on the second carrier; and another optional manner is: predefined use in the terminal device
  • the GF resource corresponding carrier that sends the unscheduled uplink data is the second carrier.
  • the frequency domain range corresponding to the predefined GF resource is the second bandwidth part.
  • the first carrier is a non-SUL carrier
  • the second carrier is a SUL carrier.
  • the non-SUL carrier is configured with an activated GF resource
  • the SUL carrier is configured with an activated GF resource
  • the terminal device passes the SUL.
  • the GF resource on the carrier sends the unscheduled uplink data.
  • the terminal device may use the GF resource on the SUL carrier to send the unscheduled uplink data according to the configuration information sent by the network device, where the configuration information is used to indicate that the GF resource used by the terminal device is the GF resource on the SUL carrier; or
  • the terminal device sends the unscheduled uplink data by using the GF resource on the SUL carrier according to the predefined rule.
  • the predefined rule is that when the network device simultaneously activates the GF resource configured on the non-SUL carrier and the GF resource configured on the SUL carrier, the network device preferentially The GF resource configured on the SUL carrier is used.
  • the terminal device that performs the method for sending uplink data as shown in FIG. 7 may also be the first terminal device or the second terminal device, where the first terminal device may also be called As a central terminal device, it is closer to the network device, and the second terminal device can also be called an edge terminal device, which is far away from the network device.
  • the GF resource on the non-SUL carrier is used to send the unscheduled uplink data.
  • the network device can also receive the unscheduled uplink data sent by the terminal device.
  • the network device is far away from the network device. If the GF resource on the non-SUL carrier is used, the network device may not receive the SUL.
  • the non-scheduled uplink data is sent by the GF resource on the carrier. Therefore, in order to ensure the reliability of the edge terminal device to send the uplink data, the terminal device that performs the method for sending the uplink data in the embodiment of the present application is Edge terminal equipment.
  • the frequency band corresponding to the GF resource for transmitting the unscheduled uplink data may be determined as the first bandwidth portion according to the following rules:
  • An MPLS resource is configured on the first carrier, and the GF resource is not configured on the second carrier.
  • the GF resource can be configured on the first bandwidth part, and the GF resource is not configured on the second bandwidth part.
  • the GF resource when the GF resource is configured on the first carrier and the second carrier, only the GF resource on the first carrier is activated, and the GF resource on the second carrier is not activated.
  • the configuration information is used by the network device to send the configuration information to the terminal device, and the configuration information is used to indicate the GF resource on the carrier that the terminal device uses to send the unscheduled data.
  • the configuration information is used to indicate that the terminal device uses the uplink data that is sent without scheduling.
  • the frequency domain range corresponding to the GF resource is not the second bandwidth part, or the configuration information is used to indicate that the terminal device uses the GF resource corresponding to sending the unscheduled uplink data.
  • the frequency domain is in the first bandwidth portion, or the configuration information is used to indicate that the frequency domain corresponding to the GF resource that the terminal device uses to send the unscheduled uplink data is that the second bandwidth portion has a higher priority than the first bandwidth portion, or
  • the configuration information is used to indicate that the GF resource that the terminal device uses to send the unscheduled uplink data belongs to the first carrier, or the configuration information is used to indicate that the terminal device preferentially uses the GF resource on the first carrier;
  • the method is: pre-defining the GF resource corresponding carrier that sends the unscheduled uplink data as the second carrier, for example, the frequency domain range corresponding to the predefined GF resource is the first bandwidth part.
  • the terminal device is a central terminal device or an edge terminal device is determined by the network device.
  • the terminal device when the terminal device sends the uplink data in the first bandwidth part, where the uplink data may be unscheduled uplink data, or may be uplink data scheduled by the network device, the terminal device needs to be in the second The GF resource of the bandwidth part sends the unscheduled uplink data. If the service type corresponding to the unscheduled uplink data sent by the GF resource of the second bandwidth part has a higher delay requirement, the terminal device is first. When the delay is less than or equal to the preset threshold, the unscheduled uplink data is sent on the GF resource of the second bandwidth part; wherein the first delay includes the time of switching from the first bandwidth part to the second bandwidth part and reaching the first resource time.
  • the first carrier is a non-SUL carrier
  • the second carrier is a SUL carrier
  • the GF resource on the non-SUL carrier is a resource on the first carrier for transmitting the unscheduled uplink data, on the SUL carrier.
  • the GF resource is a resource for transmitting the unscheduled uplink data on the second carrier.
  • the terminal device switches from the non-SUL carrier to the SUL carrier, and sends the URLLC service data on the GF resource of the SUL carrier.
  • ( ⁇ t1+ ⁇ t2) is greater than the preset threshold, if the URLLC service data is sent on the GF resource on the non-SUL carrier to ensure the delay of the URLLC service, the GF of the terminal device on the non-SUL carrier The resource sends the URLLC service data.
  • the terminal device needs to send the URLLC service data to the radio access network device in the first time window, because the first time window The inner SUL carrier has no available GF resources, so the terminal device can only send the URLLC service data on the GF resource of the non-SUL carrier.
  • the first resource and the second resource and the figure involved in the method for transmitting uplink data shown in FIG. 2 are independent, and there is no mutual association.
  • the method for transmitting uplink data shown in FIG. 2 and FIG. 7 above is for a connected terminal device.
  • the terminal device When the terminal device is in an idle state, if the terminal device needs to send an unscheduled uplink.
  • the embodiment of the present application further provides a method for initial access.
  • the method for initial access in the embodiment of the present application includes:
  • Step 1101 The terminal device receives the first system information block and the second system information block, where the first system information block indicates a resource location for initial access on the first carrier, and the second system information block is used. Indicates a resource location for initial access on the second carrier, the frequency of the first carrier being greater than the frequency of the second carrier.
  • Step 1102 When at least one of the following conditions is met, the terminal device performs initial access by using the second carrier.
  • the service type of the data to be sent in the initial access process is a preset type, the data quantity of the data to be transmitted in the initial access process is less than the first threshold, and the signal receiving quality on the first carrier is less than the second threshold.
  • the terminal device first receives a synchronous signal block (SSB), where the SSB includes a physical broadcast channel (PBCH) and a primary synchronization signal (primary synchronization signal). Signal, PSS) and secondary synchronization signal (SSS). Then, the terminal device obtains information such as the system bandwidth and the control channel configuration through the PBCH, and further receives the first system information block (SIB) and the second SIB, and obtains the first carrier for initial access by using the first SIB.
  • PBCH physical broadcast channel
  • PSS primary synchronization signal
  • SIB system information block
  • SIB system information block
  • the second SIB is used to obtain a resource location for initial access on the second carrier, where the resource used for initial access may be a physical random access channel (PRACH), when the terminal device
  • the terminal device sends a random access request (preamble) to the network device on the PRACH on the second carrier, and receives a random access response sent by the network device.
  • the MSG 3 is sent on the corresponding uplink time-frequency resource according to the RAR, where the RAR includes uplink time-frequency resource location information for transmitting the msg 3.
  • the uplink frequency domain resource in the embodiment of the present application is a physical resource used for uplink communication in the frequency domain.
  • the frequency domain resource may be a BWP, a resource block, a subband, a narrowband, or the like.
  • a frequency domain resource may also be referred to as a bandwidth resource, a bandwidth portion, a frequency resource portion, a partial frequency resource, or other name.
  • the bandwidth resource is a contiguous resource in the system frequency resource
  • the bandwidth resource may also be referred to as a sub-band, a narrowband, or other name, which is not limited in this embodiment.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the initial access is performed by using the second carrier, that is, the terminal device may send the random access request to the network device by using the frequency domain resource on the second carrier
  • the uplink time-frequency resource location information for transmitting the msg 3 included in the RAR sent by the network device to the terminal device may indicate the frequency domain resource on the second carrier, which helps improve the reliability of the msg3 transmission.
  • step 1202 The following describes each of the conditions in step 1202:
  • the service type of the data to be sent in the initial access process is a preset type.
  • the preset type may include a type of service data requiring a delay less than a certain threshold, and/or a type of high reliability service data, and the like. , for example, the type of URLLC business data.
  • the second carrier is the SUL carrier
  • the data to be sent is the URLLC service data.
  • the preset type includes the type of the URLLC service data.
  • the amount of data to be sent in the initial access process is smaller than the first threshold.
  • the first threshold in the embodiment of the present application may be set according to actual requirements. Specifically, the first threshold may be predefined or may be When the terminal device accesses the network in the last time, the radio access network device indicates to the terminal device, which is not limited in this embodiment.
  • the data to be sent is mMTC service data
  • the data volume of the mMTC service data is less than the first threshold.
  • the terminal device performs initial access through the SUL carrier, and the terminal device is The SUL carrier transmits msg3 to the radio access network device, and the msg3 includes the mMTC service data.
  • the signal receiving quality on the first carrier is smaller than the second threshold.
  • the second threshold in the embodiment of the present application may be correspondingly set according to actual requirements. Specifically, the second threshold may be predefined or may be a terminal device. When the network access device is used for the last time, the radio access network device indicates to the terminal device, which is not limited in this embodiment.
  • the terminal device when the signal reception quality on the first carrier is less than the second threshold, the terminal device performs initial access through the SUL carrier.
  • the signal reception quality may be indicated by reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), and the like.
  • the method provided by the embodiment of the present application is introduced from the perspective of interaction between the network device and the terminal device.
  • the base station and the terminal device may include a hardware structure and/or a software module, and implement the foregoing functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • One of the above functions is performed in a hardware structure, a software module, or a hardware structure plus a software module, depending on the specific application and design constraints of the technical solution.
  • FIG. 12 is a device 1200 provided by the present application.
  • the device 1200 may be a terminal device, or may be a device capable of supporting a terminal device to implement the functions of the terminal device in the method in FIG. 2 .
  • device 1200 can also be a device (such as a chip or chip system) within a terminal device.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices.
  • the device 1200 includes at least one processor 1210 for implementing the function of the terminal device in the method for transmitting uplink data provided by the embodiment of the present application.
  • Apparatus 1200 can also include at least one memory 1220 for storing program instructions and/or data.
  • Memory 1220 is coupled to processor 1210.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in an electrical, mechanical or other form for information interaction between devices, units or modules.
  • Processor 1210 may operate in conjunction with memory 1220.
  • Processor 1210 may execute program instructions stored in memory 1220. At least one of the at least one memory 1220 can be included in the processor 1210.
  • the device 1200 can also include a communication interface 1230 that can communicate with other devices via the communication interface 1230.
  • Communication interface 1230 can be a circuit, bus, transceiver, or any other device that can be used to interact with information.
  • the other device may be another terminal device or a network device.
  • the processor 1210 can transmit and receive data by using the communication interface 1230.
  • the communication interface 1230 is configured to receive control information sent by the network device.
  • connection medium between the above communication interface 1230, the processor 1210, and the memory 1220 is not limited in the embodiment of the present application.
  • the embodiment of the present application is connected by a bus between the memory 1220, the processor 1210, and the communication interface 1230 in FIG. 12, and the bus is indicated by a thick line in FIG. 12, and the connection manner between other components is only schematically illustrated. Not limited to limits.
  • 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 12, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or may be implemented or The methods, steps, and logical block diagrams disclosed in the embodiments of the present application are performed.
  • a general purpose processor can be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or may be a volatile memory, such as Random-access memory (RAM).
  • the memory may also be any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiment of the present application may also be a circuit or any other device capable of implementing a storage function for storing program instructions and/or data.
  • another embodiment of the apparatus provided by the present application may be a terminal device or a device (such as a chip or a chip system) in the terminal device, and may perform any of the foregoing as shown in FIG. 2 .
  • the device includes a transceiver module 1301 and a processing module 1302, wherein the transceiver module 1301 is configured to receive control information sent by the network device, where the control information is used to indicate that the device sends the first data on the first resource; wherein, when the first resource is used
  • the processing module 1302 is configured to trigger the transceiver module 1301 to stop transmitting in the first time domain on the first resource when the second resource that is sent by the transceiver module 1301 to the second data overlaps the first time domain in the time domain.
  • a data range the frequency domain range corresponding to the first resource belongs to the first carrier, and the frequency domain range corresponding to the second resource belongs to the second carrier.
  • the frequency of the first carrier is greater than the frequency of the second carrier.
  • the transceiver module 1301 is further configured to send the second data on the second resource and in the first time domain.
  • the processing module 1302 is further configured to: trigger the transceiver module 1301 to be on the first resource, the second time domain range before the first time domain range, and/or the third time after the first time domain range. Stop transmitting the first data in the time domain, wherein the termination time of the second time domain range coincides with the start time of the first time domain range, and the termination time of the first time domain range coincides with the start time of the third time domain range .
  • the length of the second time domain range and/or the length of the third time domain range are predefined; or the transceiver module 1301 is further configured to receive indication information sent by the network device, where the indication information is used. Indicates the length of the second time domain range and/or the length of the third time domain range.
  • the second carrier is a SUL carrier and the first carrier is a non-SUL carrier.
  • the second data is URLLC service data.
  • the device may be used to implement the steps performed by the terminal device in the method for transmitting uplink data as shown in FIG. 2 in the embodiment of the present application.
  • the device may be used to implement the steps performed by the terminal device in the method for transmitting uplink data as shown in FIG. 2 in the embodiment of the present application.
  • an apparatus 1400 provided by the present application may be a network device, or may be a device capable of supporting a network device to implement the functions of the network device in the method of FIG. 2.
  • device 1400 can be a device (such as a chip or chip system) within a network device.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices.
  • the device 1400 includes at least one processor 1410 for implementing the function of the network device in the method for transmitting uplink data provided by the embodiment of the present application.
  • Apparatus 1400 can also include at least one memory 1420 for storing program instructions and/or data.
  • Memory 1420 is coupled to processor 1410.
  • Processor 1410 may operate in conjunction with memory 1420.
  • Processor 1410 may execute program instructions stored in memory 1420. At least one of the at least one memory 1420 can be included in the processor 1410.
  • the device 1400 can also include a communication interface 1430 that can communicate with other devices via the communication interface 1430.
  • Communication interface 1430 can be a circuit, bus, transceiver, or any other device that can be used to interact with information.
  • the other device may be another terminal device or a network device.
  • the processor 1410 can transmit and receive data using the communication interface 1430.
  • the communication interface 1430 is configured to transmit control information to the terminal device.
  • connection medium between the communication interface 1430, the processor 1410, and the memory 1420 is not limited in the embodiment of the present application.
  • the embodiment of the present application is connected by a bus between the memory 1420, the processor 1410, and the communication interface 1430 in FIG. 14.
  • the bus is shown by a thick line in FIG. 14, and the connection manner between other components is only schematically illustrated. Not limited to limits.
  • 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 14, but it does not mean that there is only one bus or one type of bus.
  • another embodiment of the apparatus provided by the present application may be a network device or a device (such as a chip or a chip system) in a network device, and may perform any of the foregoing as shown in FIG. 2 .
  • the device includes a transceiver module 1501 and a processing module 1502, wherein the transceiver module 1501 is configured to send control information to the terminal device, where the control information is used to instruct the terminal device to send the first data on the first resource; and the processing module 1502 is configured to use
  • the transceiver module 1501 receives the second data sent by the terminal device on the second resource, and determines that the terminal device stops transmitting the first data on the first resource in the first time domain; the second resource and The first resource overlaps the first time domain in the time domain, the frequency domain corresponding to the first resource belongs to the first carrier, and the frequency domain corresponding to the second resource belongs to the second carrier.
  • the frequency of the first carrier is greater than the frequency of the second carrier.
  • the processing module 1502 is further configured to determine, on the first resource, that the terminal device is in the second time domain range before the first time domain range and/or the third time after the first time domain range The first data is stopped in the domain, wherein the termination time of the second time domain range coincides with the start time of the first time domain range, and the termination time of the first time domain range coincides with the start time of the third time domain range.
  • the length of the second time domain range and/or the length of the third time domain range are predefined; or the transceiver module 1501 is further configured to send indication information to the terminal device, where the indication information is used to indicate The length of the second time domain range and/or the length of the third time domain range.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the second data is URLLC service data.
  • the device may be used to implement the steps performed by the network device in the method for transmitting uplink data as shown in FIG. 2 in the embodiment of the present application.
  • the device may be used to implement the steps performed by the network device in the method for transmitting uplink data as shown in FIG. 2 in the embodiment of the present application.
  • FIG. 16 shows an apparatus 1600 provided by the present application.
  • the apparatus 1600 may be a terminal device, or may be a device capable of supporting a terminal device to implement the functions of the terminal device in the method of FIG. 7.
  • device 1600 can also be a device (such as a chip or chip system) within a terminal device.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices.
  • the device 1600 includes at least one processor 1610 for implementing the function of the terminal device in the method for transmitting uplink data provided by the embodiment of the present application.
  • Apparatus 1600 can also include at least one memory 1620 for storing program instructions and/or data.
  • Memory 1620 is coupled to processor 1610.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in an electrical, mechanical or other form for information interaction between devices, units or modules.
  • Processor 1610 may operate in conjunction with memory 1620.
  • Processor 1610 may execute program instructions stored in memory 1620. At least one of the at least one memory 1620 can be included in the processor 1610.
  • Apparatus 1600 can also include a communication interface 1630 that can communicate with other devices via communication interface 1630.
  • Communication interface 1630 can be a circuit, bus, transceiver, or any other device that can be used to interact with information.
  • the other device may be another terminal device or a network device.
  • the processor 1610 can transmit and receive data using the communication interface 1630.
  • the communication interface 1630 is configured to send unscheduled uplink data to the network device on the first resource.
  • connection medium between the communication interface 1630, the processor 1610, and the memory 1620 is not limited in the embodiment of the present application.
  • the embodiment of the present application is connected by a bus between the memory 1620, the processor 1610, and the communication interface 1630 in FIG. 16, and the bus is indicated by a thick line in FIG. 16, and the connection manner between other components is only schematically illustrated. Not limited to limits.
  • 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 16, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or may be implemented or The methods, steps, and logical block diagrams disclosed in the embodiments of the present application are performed.
  • a general purpose processor can be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory such as an HDD or an SSD, or may be a volatile memory such as a RAM.
  • the memory may also be any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiment of the present application may also be a circuit or any other device capable of implementing a storage function for storing program instructions and/or data.
  • another embodiment of the apparatus provided by the present application may be a terminal device or a device (such as a chip or a chip system) in a terminal device, and may perform any of the foregoing as shown in FIG. A method performed by a terminal device in an embodiment.
  • the device includes a transceiver module 1701 and a processing module 1702, where the processing module 1702 is configured to determine a first resource for sending the unscheduled uplink data, where the frequency domain corresponding to the first resource belongs to the first bandwidth portion or the second bandwidth portion.
  • the first bandwidth portion and the second bandwidth portion are portions of the bandwidth that the network device configures to the device, and the first bandwidth portion is an activated bandwidth portion on the first carrier, and the second bandwidth portion is an activated bandwidth portion on the second carrier.
  • the transceiver module 1701 is configured to send the schedule-free uplink data to the network device by using the first resource.
  • the frequency of the second carrier is smaller than the frequency of the first carrier, and the frequency domain range corresponding to the first resource belongs to the second bandwidth portion.
  • the second resource configured to send the unscheduled uplink data is not activated on the first bandwidth portion, or the second bandwidth portion is not configured to send the unscheduled uplink data. Resources.
  • the transceiver module 1701 is further configured to receive configuration information sent by the network device, where the configuration information is used to indicate that the frequency domain range corresponding to the resource used by the transceiver module to send the unscheduled uplink data belongs to the second bandwidth. section.
  • the frequency domain resource used by the transceiver module 1701 to send the uplink data is the first bandwidth portion
  • the first delay is less than or equal to the preset threshold
  • the frequency domain corresponding to the first resource belongs to the first a bandwidth portion; wherein the first time delay includes a time to switch from the first bandwidth portion to the second bandwidth portion and a time to reach the first resource.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the unscheduled uplink data is URLLC service data.
  • the device may be used to implement the steps performed by the terminal device in the method for transmitting uplink data as shown in FIG. 7 in the embodiment of the present application.
  • the device may be used to implement the steps performed by the terminal device in the method for transmitting uplink data as shown in FIG. 7 in the embodiment of the present application.
  • an apparatus 1800 provided by the present application may be a network device, or may be a device capable of supporting a network device to implement the functions of the network device in the method of FIG.
  • device 1800 can be a device (such as a chip or chip system) within a network device.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices.
  • the device 1800 includes at least one processor 1810 for implementing the function of the network device in the method for transmitting uplink data provided by the embodiment of the present application.
  • Apparatus 1800 can also include at least one memory 1820 for storing program instructions and/or data.
  • Memory 1820 is coupled to processor 1810.
  • Processor 1810 may operate in conjunction with memory 1820.
  • Processor 1810 may execute program instructions stored in memory 1820. At least one of the at least one memory 1820 can be included in the processor 1810.
  • a communication interface 1830 can also be included in the device 1800, and the device 1800 can interact with other devices via the communication interface 1830.
  • Communication interface 1830 can be a circuit, bus, transceiver, or any other device that can be used to interact with information.
  • the other device may be another terminal device or a network device.
  • the processor 1810 can use the communication interface 1830 to send and receive data.
  • the communication interface 1830 is configured to receive the unscheduled uplink data sent by the terminal device on the first resource.
  • connection medium between the above communication interface 1830, the processor 1810, and the memory 1820 is not limited in the embodiment of the present application.
  • the embodiment of the present application is connected by a bus between the memory 1820, the processor 1810, and the communication interface 1830 in FIG. 18.
  • the bus is indicated by a thick line in FIG. 18, and the connection manner between other components is only schematically illustrated. Not limited to limits.
  • 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 18, but it does not mean that there is only one bus or one type of bus.
  • another embodiment of the apparatus provided by the present application may be a network device or a device (such as a chip or a chip system) in a network device, and may perform any of the foregoing as shown in FIG. A method performed by a network device in an embodiment.
  • the device includes a transceiver module 1901 and a processing module 1902, wherein the processing module 1902 is configured to configure a first bandwidth portion and a second bandwidth portion for the terminal device, where the first bandwidth portion is an activated bandwidth portion on the first carrier, and the second bandwidth portion The bandwidth portion is activated on the second carrier.
  • the transceiver module 1901 is configured to receive the unscheduled uplink data sent by the terminal device on the first resource, where the frequency domain range corresponding to the first resource belongs to the first bandwidth portion or the second bandwidth portion.
  • the frequency of the second carrier is smaller than the frequency of the first carrier, and the frequency domain range corresponding to the first resource belongs to the second bandwidth portion.
  • the second resource configured to send the unscheduled uplink data is not activated on the first bandwidth portion, or the second bandwidth portion is not configured to send the unscheduled uplink data. Resources.
  • the transceiver module 1901 is further configured to send configuration information to the terminal device, where the configuration information is used to indicate that the frequency domain range corresponding to the resource used by the terminal device to send the unscheduled uplink data belongs to the second bandwidth. section.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the unscheduled uplink data is URLLC service data.
  • the device may be used to implement the steps performed by the network device in the method for transmitting uplink data as shown in FIG. 7 in the embodiment of the present application.
  • the device may be used to implement the steps performed by the network device in the method for transmitting uplink data as shown in FIG. 7 in the embodiment of the present application.
  • FIG. 20 shows an apparatus 2000 provided by the present application.
  • the apparatus 2000 may be a terminal device, or may be a device capable of supporting a terminal device to implement the functions of the terminal device in the method in FIG.
  • device 2000 can also be a device (such as a chip or chip system) within a terminal device.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices.
  • the device 2000 includes at least one processor 2010 for implementing the functions of the terminal device in the method for initial access provided by the embodiment of the present application.
  • the device 2000 can also include at least one memory 2020 for storing program instructions and/or data.
  • Memory 2020 is coupled to processor 2010.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in an electrical, mechanical or other form for information interaction between devices, units or modules.
  • Processor 2010 may operate in conjunction with memory 2020.
  • Processor 2010 may execute program instructions stored in memory 2020. At least one of the at least one memory 2020 can be included in the processor 2010.
  • the device 2000 can also include a communication interface 2030 that can interact with other devices via the communication interface 2030.
  • Communication interface 2030 can be a circuit, bus, transceiver, or any other device that can be used to interact with information.
  • the other device may be another terminal device or a network device.
  • the processor 2010 can transmit and receive data using the communication interface 2030.
  • the communication interface 2030 is configured to receive the first system information block and the second system information block.
  • connection medium between the communication interface 2030, the processor 2010, and the memory 2020 is not limited in the embodiment of the present application.
  • the embodiment of the present application is connected by a bus between the memory 2020, the processor 2010, and the communication interface 2030 in FIG. 20, and the bus is indicated by a thick line in FIG. 20, and the connection manner between other components is only schematically illustrated. Not limited to limits.
  • 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 FIG. 20, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or may be implemented or The methods, steps, and logical block diagrams disclosed in the embodiments of the present application are performed.
  • a general purpose processor can be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory such as an HDD or an SSD, or may be a volatile memory such as a RAM.
  • the memory may also be any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiment of the present application may also be a circuit or any other device capable of implementing a storage function for storing program instructions and/or data.
  • another embodiment of the apparatus provided by the present application may be a terminal device or a device (such as a chip or a chip system) in the terminal device, and may perform any of the foregoing as shown in FIG. A method performed by a terminal device in an embodiment.
  • the device includes a transceiver module 2101 and a processing module 2102, wherein the transceiver module 2101 is configured to receive a first system information block and a second system information block, where the first system information block indicates a resource location for initial access on the first carrier, The second system information block is used to indicate a resource location for the initial access on the second carrier, where the frequency of the first carrier is greater than the frequency of the second carrier; when at least one of the following conditions is met, the processing module 2102 is configured to pass the second The carrier is initially accessed;
  • the service type of the data to be sent in the initial access process is a preset type, the data quantity of the data to be transmitted in the initial access process is less than the first threshold, and the signal receiving quality on the first carrier is less than the second threshold.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the preset type includes the type of URLLC service data.
  • the device may be used to implement the steps performed by the terminal device in the method for initial access as shown in FIG. 11 in the embodiment of the present application.
  • the device may be used to implement the steps performed by the terminal device in the method for initial access as shown in FIG. 11 in the embodiment of the present application.
  • the apparatus 2200 is provided by the present application.
  • the device 2200 may be a network device, or may be a device capable of supporting a network device to implement the functions of the network device in the method in FIG.
  • device 2200 can be a device (such as a chip or chip system) within a network device.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices.
  • the device 2200 includes at least one processor 2210 for implementing the functions of the network device in the method for initial access provided by the embodiment of the present application.
  • Apparatus 2200 can also include at least one memory 2220 for storing program instructions and/or data.
  • Memory 2220 is coupled to processor 2210.
  • Processor 2210 may operate in conjunction with memory 2220.
  • Processor 2210 may execute program instructions stored in memory 2220. At least one of the at least one memory 2220 can be included in the processor 2210.
  • the device 2200 can also include a communication interface 2230 that can communicate with other devices via the communication interface 2230.
  • Communication interface 2230 can be a circuit, bus, transceiver, or any other device that can be used to interact with information.
  • the other device may be another terminal device or a network device.
  • the processor 2210 can transmit and receive data using the communication interface 2230.
  • the communication interface 2230 is used to the first system information block and the second system information block.
  • connection medium between the communication interface 2230, the processor 2210, and the memory 2220 is not limited in the embodiment of the present application.
  • the embodiment of the present application is connected by a bus between the memory 2220, the processor 2210, and the communication interface 2230 in FIG. 22, and the bus is indicated by a thick line in FIG. 22, and the connection manner between other components is only schematically illustrated. Not limited to limits.
  • 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 FIG. 22, but it does not mean that there is only one bus or one type of bus.
  • another embodiment of the apparatus provided by the present application may be a network device or a device (such as a chip or a chip system) in a network device, and may perform any of the foregoing as shown in FIG. A method performed by a network device in an embodiment.
  • the device includes a receiving module 2301 and a sending module 2302, where the sending module 2302 is configured to send a first system information block and a second system information block, where the first system information block indicates a resource location for initial access on the first carrier, The second system information block is used to indicate a resource location for the initial access on the second carrier, where the frequency of the first carrier is greater than the frequency of the second carrier; then, the receiving module 2301 is configured to: when the terminal device meets at least one of the following conditions: Receiving, by using the second carrier, data sent by the terminal device during initial access;
  • the service type of the data to be sent by the terminal device in the initial access process is a preset type, the data volume of the data to be sent by the terminal device in the initial access process is less than the first threshold, and the signal receiving quality of the terminal device on the first carrier is less than Second threshold.
  • the first carrier is a non-SUL carrier and the second carrier is a SUL carrier.
  • the preset type includes the type of URLLC service data.
  • the device may be used to implement the steps performed by the network device in the method for initial access as shown in FIG. 11 in the embodiment of the present application.
  • the device may be used to implement the steps performed by the network device in the method for initial access as shown in FIG. 11 in the embodiment of the present application.
  • the communication system of the embodiment of the present application includes a device 1200 and a device 1400.
  • the communication system of the embodiment of the present application includes a device 1600 and a device 1800.
  • the communication system of the embodiment of the present application includes a device 2000 and a device 2200.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, a network device, a terminal device, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • 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 digital video disc (DVD)), or a semiconductor medium (eg, a Solid State Disk (SSD)). )Wait.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a digital video disc (DVD)
  • DVD digital video disc
  • SSD Solid State Disk
  • embodiments of the present application can be provided as a method, apparatus (device), computer readable storage medium, or computer program product.
  • the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects, which are collectively referred to herein as "module” or "system.”
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本申请涉及通信技术领域，特别涉及一种发送和接收上行数据的方法、装置及系统，其中，该方法包括终端设备接收网络设备发送的控制信息，所述控制信息用于指示所述终端设备在第一资源上发送第一数据；当所述第一资源和用于所述终端设备发送第二数据的第二资源在时域上重合于第一时域范围时，在所述第一资源上，所述终端设备在所述第一时域范围内停止发送所述第一数据；所述第一资源对应的频域范围属于第一载波，所述第二资源对应的频域范围属于第二载波。通过上述技术方案有效的支持了不支持同时在不同载波上的资源发送数据的终端设备的上行数据发送，有助于避免上行数据发送冲突。

Description

一种发送和接收上行数据的方法、装置及系统
本申请中要求在2018年02月12日提交中国专利局、申请号为201810146743.8、申请名称为“一种发送和接收上行数据的方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种发送和接收上行数据的方法、装置及系统。
背景技术
第五代移动通信(the 5th generation，5G)新空口(new radio，NR)中支持从6吉赫兹(gigahertz，GHz)以下的频段(简称sub6G频段)到60GHz频段，当NR中终端设备采用sub6G频段到60GHz频段中的高频载波进行上行数据的发送时，由于高频载波上路径损耗较大，因此覆盖范围受限，但是受终端设备成本、功耗等的限制，无法通过抬升上行数据的发射功率等提升上行的覆盖范围，因而通常情况下，当终端设备采用高频载波进行上行数据的发送时，若终端设备为边缘终端设备，距离基站较远，则基站有可能无法接收到终端设备发送的上行数据。
而长期演进(long term evolution，LTE)中支持3GHz以下的频段(简称sub3GHz)，当LTE支持的频段上的载波上的资源利用率较低时，NR中上行数据发送可以与LTE中上行数据的发送共享sub3GHz频段上的载波，由于NR中当采用sub3GHz频段上的载波发送上行数据时，sub3GHz频段上的载波为低频载波，路径损耗较小，因而有助于提升上行的覆盖范围。其中NR中共享的LTE支持的频段，因此sub3GHz频段上的载波又可称之为增补上行频率(supplementary uplink frequency，SUL)载波，而其它频段上的载波可称之为非SUL载波。
终端设备如何使用合适的通信资源进行数据传输是需要解决的问题。
发明内容
本申请实施例提供一种发送和接收上行数据的方法、装置及系统，有助于提高上行数据发送成功的可能性。
第一方面，本申请实施例发送上行数据的方法，包括：
终端设备接收网络设备发送的控制信息，所述控制信息用于指示所述终端设备在第一资源上发送第一数据；其中，当所述第一资源和用于所述终端设备发送第二数据的第二资源在时域上重合于第一时域范围时，在所述第一资源上，所述终端设备在所述第一时域范围内停止发送所述第一数据；所述第一资源对应的频域范围属于第一载波，所述第二资源对应的频域范围属于第二载波。
本申请实施例中由于当第一资源和第二资源在时域上重合于第一时域范围时，终端设备停止在第一资源上第一时域范围内发送第一数据，有效的支持了不支持同时在不同载波上的资源发送数据的终端设备的上行数据发送，进一步，有助于避免上行数据发送冲突，降低上行数据发送失败的可能性。
在一种可能的设计中，所述第一载波的频率大于所述第二载波的频率。通过上述技术 方案，有助于进一步提高上行数据发送成功的可能性。
在一种可能的设计中，在所述第二资源上，所述终端设备在所述第一时域范围内发送所述第二数据。通过上述技术方案有助于提高第二数据发送成功的可能性。
在一种可能的设计中，在所述第一资源上，所述终端设备在所述第一时域范围前的第二时域范围内和/或所述第一时域范围后的第三时域范围内停止发送所述第一数据，其中所述第二时域范围的终止时刻和所述第一时域范围的起始时刻重合，所述第一时域范围的终止时刻和所述第三时域范围的起始时刻重合。通过上述技术方案有助于进一步提高第二数据发送成功的可能性。
在一种可能的设计中，所述第二时域范围的长度和/或所述第三时域范围的长度为预先定义的；或者，所述第二时域范围的长度和/或所述第三时域范围的长度是所述网络设备通过指示信息指示给所述终端设备的。
在一种可能的设计中，所述第二载波为增补上行频率(supplementary uplink frequency，SUL)载波，所述第一载波为非SUL载波。
在一种可能的设计中，所述第二数据为高可靠低时延通信(ultra reliable and low latency communications，URLLC)业务数据。
第二方面，本申请实施例接收上行数据的方法，包括：
网络设备向终端设备发送的控制信息，所述控制信息用于指示所述终端设备在第一资源上发送第一数据；若在第一时域范围内，所述网络设备在第二资源上接收到所述终端设备发送的第二数据，则确定所述终端设备在所述第一资源上、所述第一时域范围内停止发送所述第一数据；所述第二资源和所述第一资源在时域上重合于所述第一时域范围，所述第一资源对应的频域范围属于第一载波，所述第二资源对应的频域范围属于第二载波。通过上述技术方案，有助于避免上行数据发送冲突，降低上行数据发送失败的可能性。
此外，需要说明的是，所述网络设备在确定所述终端设备在所述第一资源上、所述第一时域范围内停止发送所述第一数据后，若在所述第一资源上、所述第一时域范围内接收到第三数据，则不对所述第三数据进行解码等，或者丢弃所述第三数据。
在一种可能的设计中，所述第一载波的频率大于所述第二载波的频率。通过上述技术方案，有助于进一步提高上行数据发送成功的可能性。
在一种可能的设计中，所述网络设备确定在所述第一资源上，所述终端设备在所述第一时域范围前的第二时域范围内和/或所述第一时域范围后的第三时域范围内停止发送所述第一数据，其中所述第二时域范围的终止时刻和所述第一时域范围的起始时刻重合，所述第一时域范围的终止时刻和所述第三时域范围的起始时刻重合。通过上述技术方案有助于进一步提高第二数据发送成功的可能性。
在一种可能的设计中，所述第二时域范围的长度和/或所述第三时域范围的长度为预先定义的；或者，所述第二时域范围的长度和/或所述第三时域范围的长度是所述网络设备通过指示信息指示给所述终端设备的。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述第二数据为URLLC业务数据。
第三方面，本申请实施例发送上行数据的方法，包括：
终端设备确定用于发送免调度的上行数据的第一资源，所述第一资源对应的频域范围属于第一带宽部分或者第二带宽部分，所述第一带宽部分和所述第二带宽部分为网络设备 配置给所述终端设备的激活的带宽部分，且所述第一带宽部分为第一载波上激活的带宽部分，所述第二带宽部分为第二载波上激活的带宽部分；然后，所述终端设备通过所述第一资源向所述网络设备发送所述免调度的上行数据。
本申请实施例中由于在第一带宽部分为第一载波上激活的带宽部分、第二带宽部分为第二载波上激活的带宽部分的情况下，在第一资源上向网络设备发送免调度的上行数据，有助于提高免调度的上行数据传输的可靠性。
在一种可能的设计中，所述第二载波的频率小于所述第一载波的频率，所述第一资源对应的频域范围属于所述第二带宽部分。通过上述技术方案有助于进一步提高免调度的上行数据传输的可靠性。
在一种可能的设计中，所述第一带宽部分上未激活配置的用于发送所述免调度的上行数据的第二资源，或者，所述第一带宽部分上未配置用于发送所述免调度的上行数据的第二资源。通过上述技术方案，有助于简化使得终端设备确定的用于发送免调度的上行数据的第一资源对应的频域范围属于第二带宽部分的实现方式。
在一种可能的设计中，本申请实施例中另一种使得终端设备确定的用于发送免调度的上行数据的第一资源对应的频域范围数据第二带宽部分的实现方式为：所述终端设备接收所述网络设备发送的配置信息，所述配置信息用于指示所述终端设备使用的用于发送所述免调度的上行数据的资源对应的频域范围属于所述第二带宽部分。
在一种可能的设计中，当所述终端设备用于发送上行数据的频域资源为所述第一带宽部分时，若第一时延小于等于预设阈值，则所述第一资源对应的频域范围属于所述第二带宽部分；其中，所述第一时延包括从所述第一带宽部分切换到所述第二带宽部分的时间和到达所述第一资源的时间。通过上述技术方案，有助于降低免调度的上行数据的传输时延。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述免调度的上行数据为URLLC业务数据。
第四方面，本申请实施例接收上行数据的方法，包括：
网络设备为终端设备配置第一带宽部分和第二带宽部分，所述第一带宽部分为第一载波上激活的带宽部分，所述第二带宽部分为第二载波上激活的带宽部分；然后，所述网络设备在第一资源上接收终端设备发送的免调度的上行数据，所述第一资源对应的频域范围属于所述第一带宽部分或者所述第二带宽部分。通过上述技术方案，有助于提高免调度的上行数据传输的可靠性。
在一种可能的设计中，所述第二载波的频率小于所述第一载波的频率，所述第一资源对应的频域范围属于所述第二带宽部分。通过上述技术方案有助于进一步提高免调度的上行数据传输的可靠性。
在一种可能的设计中，所述第一带宽部分上未激活配置的用于发送所述免调度的上行数据的第二资源，或者，所述第一带宽部分上未配置用于发送所述免调度的上行数据的第二资源。通过上述技术方案，有助于简化使得终端设备确定的用于发送免调度的上行数据的第一资源对应的频域范围属于第二带宽部分的实现方式。
在一种可能的设计中，本申请实施例中另一种使得终端设备确定的用于发送免调度的上行数据的第一资源对应的频域范围数据第二带宽部分的实现方式为：所述网络设备向所述终端设备发送的配置信息，所述配置信息用于指示所述终端设备使用的用于发送所述免调度的上行数据的资源对应的频域范围属于所述第二带宽部分。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述免调度的上行数据为URLLC业务数据。
第五方面，本申请实施例初始接入的方法，包括：
终端设备接收第一系统信息块和第二系统信息块，所述第一系统信息块指示第一载波上用于初始接入的资源位置，所述第二系统信息块用于指示第二载波上用于初始接入的资源位置，所述第一载波的频率大于所述第二载波的频率；
当满足下列条件中的至少一个时，所述终端设备通过所述第二载波进行初始接入；
初始接入过程中待发送数据的业务类型为预设类型、初始接入过程中待发送数据的数据量小于第一阈值和所述第一载波上的信号接收质量小于第二阈值。
本申请实施例中由于在第一载波的频率大于第二载波的频率的情况下，当满足初始接入过程中待发送数据的业务类型为预设类型、初始接入过程中待发送数据的数据量小于第一阈值和所述第一载波上的信号接收质量小于第二阈值中的至少一个条件时，通过第二载波进行初始接入，有助于提高初始接入过程中数据传输的可靠性。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述预设类型包括URLLC业务数据的类型。
第六方面，本申请实施例初始接入的方法，包括：
网络设备发送第一系统信息块和第二系统信息块，所述第一系统信息块指示第一载波上用于初始接入的资源位置，所述第二系统信息块用于指示第二载波上用于初始接入的资源位置，所述第一载波的频率大于所述第二载波的频率；然后，所述网络设备在所述终端设备满足下列条件中的至少一个时，通过所述第二载波接收所述终端设备初始接入过程中发送的数据；
所述终端设备在初始接入过程中待发送数据的业务类型为预设类型、所述终端设备在初始接入过程中待发送数据的数据量小于第一阈值和所述终端设备在所述第一载波上的信号接收质量小于第二阈值。通过上述技术方案有助于提高初始接入过程中数据传输的可靠性。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述预设类型包括URLLC业务数据的类型。
第七方面，本申请实施例的装置，包括收发模块和处理模块，其中，所述收发模块用于接收网络设备发送的控制信息，所述控制信息用于指示所述装置在第一资源上发送第一数据；其中，当所述第一资源和用于所述收发模块发送第二数据的第二资源在时域上重合于第一时域范围时，在所述第一资源上，所述处理模块用于触发所述收发模块在所述第一时域范围内停止发送所述第一数据；所述第一资源对应的频域范围属于第一载波，所述第二资源对应的频域范围属于第二载波。
在一种可能的设计中，所述第一载波的频率大于所述第二载波的频率。
在一种可能的设计中，所述收发模块还用于在所述第二资源上、所述第一时域范围内发送所述第二数据。
在一种可能的设计中，所述处理模块还用于，触发所述收发模块在所述第一资源上、所述第一时域范围前的第二时域范围内和/或所述第一时域范围后的第三时域范围内停止发送所述第一数据，其中所述第二时域范围的终止时刻和所述第一时域范围的起始时刻重合，所述第一时域范围的终止时刻和所述第三时域范围的起始时刻重合。
在一种可能的设计中，所述第二时域范围的长度和/或所述第三时域范围的长度为预先定义的；或者，所述收发模块，还用于接收所述网络设备发送的指示信息，所述指示信息用于指示所述第二时域范围的长度和/或所述第三时域范围的长度。
在一种可能的设计中，所述第二载波为SUL载波，所述第一载波为非SUL载波。
在一种可能的设计中，所述第二数据为URLLC业务数据。
需要说明的是，收发模块对应的硬件实现方式为收发器，收发器包括接收器和发送器，其中接收器和发送器可以为独立的硬件单元，也可以集成在一个硬件单元上，对此本申请实施例不作限定，收处理模块对应的硬件实现方式为处理器。
本申请实施例又一方面，还提供了一种芯片，其中该芯片分别与收发器、存储器相连，用于读取并执行存储器中存储的程序，触发收发器以实现第一方面以及第一方面任意一种可能的设计的发送上行数据的方法。
本申请实施例还一方面，还提供了一种计算机存储介质，其中该计算机存储介质上存储有计算机程序，计算机程序被处理器执行时，用于实现第一方面以及第一方面任意一种可能的设计的发送上行数据的方法。
第八方面，本申请实施例的装置，包括收发模块和处理模块，其中所述收发模块用于向终端设备发送的控制信息，所述控制信息用于指示所述终端设备在第一资源上发送第一数据；所述处理模块用于若在第一时域范围内，所述收发模块在第二资源上接收到所述终端设备发送的第二数据，则确定所述终端设备在所述第一资源上、所述第一时域范围内停止发送所述第一数据；所述第二资源和所述第一资源在时域上重合于所述第一时域范围，所述第一资源对应的频域范围属于第一载波，所述第二资源对应的频域范围属于第二载波。
在一种可能的设计中，所述第一载波的频率大于所述第二载波的频率。
在一种可能的设计中，所述处理模块，还用于确定在所述第一资源上，所述终端设备在所述第一时域范围前的第二时域范围内和/或所述第一时域范围后的第三时域范围内停止发送所述第一数据，其中所述第二时域范围的终止时刻和所述第一时域范围的起始时刻重合，所述第一时域范围的终止时刻和所述第三时域范围的起始时刻重合。
在一种可能的设计中，所述第二时域范围的长度和/或所述第三时域范围的长度为预先定义的；或者，所述收发模块，还用于向所述终端设备发送指示信息，所述指示信息用于指示所述第二时域范围的长度和/或所述第三时域范围的长度。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述第二数据为URLLC业务数据。
需要说明的是，收发模块对应的硬件实现方式为收发器，收发器包括接收器和发送器，其中接收器和发送器可以为独立的硬件单元，也可以集成在一个硬件单元上，对此本申请实施例不作限定，收处理模块对应的硬件实现方式为处理器。
本申请实施例又一方面，还提供了一种芯片，其中该芯片分别与收发器、存储器相连，用于读取并执行存储器中存储的程序，触发收发器以实现第二方面以及第二方面任意一种可能的设计的发送接收上行数据的方法。
本申请实施例还一方面，还提供了一种计算机存储介质，其中该计算机存储介质上存储有计算机程序，计算机程序被处理器执行时，用于实现第二方面以及第二方面任意一种可能的设计的接收上行数据的方法。
第九方面，本申请实施例的装置，包括收发模块和处理模块，其中，所述处理模块用于确定用于发送免调度的上行数据的第一资源，所述第一资源对应的频域范围属于第一带宽部分或者第二带宽部分，所述第一带宽部分和所述第二带宽部分为网络设备配置给所述装置的激活的带宽部分，且所述第一带宽部分为第一载波上激活的带宽部分，所述第二带宽部分为第二载波上激活的带宽部分；所述收发模块，用于通过所述第一资源向所述网络设备发送所述免调度的上行数据。
在一种可能的设计中，所述第二载波的频率小于所述第一载波的频率，所述第一资源对应的频域范围属于所述第二带宽部分。
在一种可能的设计中，所述第一带宽部分上未激活配置的用于发送所述免调度的上行数据的第二资源，或者，所述第一带宽部分上未配置用于发送所述免调度的上行数据的第二资源。
在一种可能的设计中，所述收发模块，还用于接收所述网络设备发送的配置信息，所述配置信息用于指示所述收发模块使用的用于发送所述免调度的上行数据的资源对应的频域范围属于所述第二带宽部分。
在一种可能的设计中，当所述收发模块用于发送上行数据的频域资源为所述第一带宽部分时，若第一时延小于等于预设阈值，则所述第一资源对应的频域范围属于所述第二带宽部分；其中，所述第一时延包括从所述第一带宽部分切换到所述第二带宽部分的时间和到达所述第一资源的时间。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述免调度的上行数据为URLLC业务数据。
需要说明的是，收发模块对应的硬件实现方式为收发器，收发器包括接收器和发送器，其中接收器和发送器可以为独立的硬件单元，也可以集成在一个硬件单元上，对此本申请实施例不作限定，收处理模块对应的硬件实现方式为处理器。
本申请实施例又一方面，还提供了一种芯片，其中该芯片分别与收发器、存储器相连，用于读取并执行存储器中存储的程序，触发收发器以实现第三方面以及第三方面任意一种可能的设计的发送上行数据的方法。
本申请实施例还一方面，还提供了一种计算机存储介质，其中该计算机存储介质上存储有计算机程序，计算机程序被处理器执行时，用于实现第三方面以及第三方面任意一种可能的设计的发送上行数据的方法。
第十方面，本申请实施例的装置，包括收发模块和处理模块，其中，所述处理模块用于为终端设备配置第一带宽部分和第二带宽部分，所述第一带宽部分为第一载波上激活的带宽部分，所述第二带宽部分为第二载波上激活的带宽部分；所述收发模块用于在第一资源上接收终端设备发送的免调度的上行数据，所述第一资源对应的频域范围属于所述第一带宽部分或者所述第二带宽部分。
在一种可能的设计中，所述第二载波的频率小于所述第一载波的频率，所述第一资源对应的频域范围属于所述第二带宽部分。
在一种可能的设计中，所述第一带宽部分上未激活配置的用于发送所述免调度的上行数据的第二资源，或者，所述第一带宽部分上未配置用于发送所述免调度的上行数据的第二资源。
在一种可能的设计中，所述收发模块还用于向所述终端设备发送的配置信息，所述配 置信息用于指示所述终端设备使用的用于发送所述免调度的上行数据的资源对应的频域范围属于所述第二带宽部分。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述免调度的上行数据为URLLC业务数据。
需要说明的是，收发模块对应的硬件实现方式为收发器，收发器包括接收器和发送器，其中接收器和发送器可以为独立的硬件单元，也可以集成在一个硬件单元上，对此本申请实施例不作限定，收处理模块对应的硬件实现方式为处理器。
本申请实施例又一方面，还提供了一种芯片，其中该芯片分别与收发器、存储器相连，用于读取并执行存储器中存储的程序，触发收发器以实现第四方面以及第四方面任意一种可能的设计的接收上行数据的方法。
本申请实施例还一方面，还提供了一种计算机存储介质，其中该计算机存储介质上存储有计算机程序，计算机程序被处理器执行时，用于实现第四方面以及第四方面任意一种可能的设计的接收上行数据的方法。
第十一方面，本申请实施例的装置，包括收发模块和处理模块，其中所述收发模块用于接收第一系统信息块和第二系统信息块，所述第一系统信息块指示第一载波上用于初始接入的资源位置，所述第二系统信息块用于指示第二载波上用于初始接入的资源位置，所述第一载波的频率大于所述第二载波的频率；当满足下列条件中的至少一个时，所述处理模块通过所述第二载波进行初始接入；
初始接入过程中待发送数据的业务类型为预设类型、初始接入过程中待发送数据的数据量小于第一阈值和所述第一载波上的信号接收质量小于第二阈值。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述预设类型包括URLLC业务数据的类型。
需要说明的是，收发模块对应的硬件实现方式为收发器，收发器包括接收器和发送器，其中接收器和发送器可以为独立的硬件单元，也可以集成在一个硬件单元上，对此本申请实施例不作限定，收处理模块对应的硬件实现方式为处理器。
本申请实施例又一方面，还提供了一种芯片，其中该芯片分别与收发器、存储器相连，用于读取并执行存储器中存储的程序，触发收发器以实现第五方面以及第五方面任意一种可能的设计的初始接入的方法。
本申请实施例还一方面，还提供了一种计算机存储介质，其中该计算机存储介质上存储有计算机程序，计算机程序被处理器执行时，用于实现第五方面以及第五方面任意一种可能的设计的初始接入的方法。
第十二方面，本申请实施例的装置，包括接收模块和发送模块，其中所述发送模块用于发送第一系统信息块和第二系统信息块，所述第一系统信息块指示第一载波上用于初始接入的资源位置，所述第二系统信息块用于指示第二载波上用于初始接入的资源位置，所述第一载波的频率大于所述第二载波的频率；然后，所述接收模块用于在所述终端设备满足下列条件中的至少一个时，通过所述第二载波接收所述终端设备初始接入过程中发送的数据；
所述终端设备在初始接入过程中待发送数据的业务类型为预设类型、所述终端设备在初始接入过程中待发送数据的数据量小于第一阈值和所述终端设备在所述第一载波上的信号接收质量小于第二阈值。
在一种可能的设计中，所述第一载波为非SUL载波，所述第二载波为SUL载波。
在一种可能的设计中，所述预设类型包括URLLC业务数据的类型。
需要说明的是，接收模块对应的硬件实现方式为接收器，发送模块对应的硬件实现方式为发送器，其中接收器的功能和发送器功能可以集成在一个硬件模块中，统称为收发器，接收器和收发器也可以分别为独立的硬件单元。
本申请实施例又一方面，还提供了一种芯片，其中该芯片分别与收发器、存储器相连，用于读取并执行存储器中存储的程序，触发收发器以实现第六方面以及第六方面任意一种可能的设计的初始接入的方法。
本申请实施例还一方面，还提供了一种计算机存储介质，其中该计算机存储介质上存储有计算机程序，计算机程序被处理器执行时，用于实现第六方面以及第六方面任意一种可能的设计的初始接入的方法。
本申请实施例还提供了一种通信系统，包括第七方面以及第七方面任意一种可能的设计的装置和第八方面以及第八方面任意一种可能的设计的装置。
本申请实施例还提供了一种通信系统，包括第九方面以及第九方面任意一种可能的设计的装置和第十方面以及第十方面任意一种可能的设计的装置。
本申请实施例还提供了一种通信系统，包括第十一方面以及第十一方面任意一种可能的设计的装置和第十二方面以及第十二方面任意一种可能的设计的装置。
另外，第四方面至第十二方面中任一种可能设计方式所带来的技术效果可参见相应的终端设备侧的方法中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例适用的一种可能的移动通信系统的架构示意图；
图2为本申请实施例中发送上行数据的方法的流程示意图；
图3a～图3c分别为本申请实施例第一时域范围的示意图；
图4为本申请实施例第一资源和第二资源的示意图；
图5a～图5c分别为本申请实施例第一资源和第二资源的示意图；
图6为本申请实施例第一资源和第二资源的示意图；
图7为本申请实施例另一种发送上行数据的方法的流程示意图；
图8为本申请实施例非SUL载波的GF资源和SUL载波的GF资源的示意图；
图9为本申请实施例非SUL载波的GF资源和SUL载波的GF资源的示意图；
图10为本申请实施例非SUL载波的GF资源和SUL载波的GF资源的示意图；
图11为本申请实施例初始接入的方法的流程示意图；
图12为本申请实施例的装置的结构示意图；
图13为本申请实施例的装置的结构示意图；
图14为本申请实施例的装置的结构示意图；
图15为本申请实施例的装置的结构示意图；
图16为本申请实施例的装置的结构示意图；
图17为本申请实施例的装置的结构示意图；
图18为本申请实施例的装置的结构示意图；
图19为本申请实施例的装置的结构示意图；
图20为本申请实施例的装置的结构示意图；
图21为本申请实施例的装置的结构示意图；
图22为本申请实施例的装置的结构示意图；
图23为本申请实施例的装置的结构示意图；
图24为本申请实施例的通信系统的结构示意图；
图25为本申请实施例的通信系统的结构示意图；
图26为本申请实施例的通信系统的结构示意图。
具体实施方式
下面结合说明书附图对本申请实施例进行详细说明。
图1为本申请实施例适用的一种可能的移动通信系统的架构示意图。如图1所示的移动通信系统包括网络设备和终端设备。应理解，图1仅为移动通信系统的一个架构示意图，本申请实施例中对移动通信系统中网络设备的数量、终端设备的数量不作限定，而且本申请实施例所适用的移动通信系统中除了包括网络设备和终端设备以外，还可以包括其它设备，如核心网设备、无线中继设备和无线回传设备等，对此本申请实施例也不作限定。以及，本申请实施例中的网络设备可以将所有的功能集成在一个独立的物理设备，也可以将功能分布在多个独立的物理设备上，对此本申请实施例也不作限定。此外，本申请实施例中的终端设备可以通过无线方式与网络设备连接。还需要说明的是，本申请实施例中的终端设备可以是固定位置的，也可以是可移动的。
本申请实施例中的网络设备用于将终端设备接入到移动通信系统中，具体的，网络设备可以是基站(node B)、演进型基站(evolved node B，eNB)、5G中的基站、未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等，对网络设备所采用的具体技术和具体设备形态不作限定。
本申请实施例中的终端设备也可以称为终端(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。具体的，终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等，对此不作限定。
应理解，本申请实施例中的网络设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上等，对网络设备和终端设备的应用场景不做限定。
应理解，本申请实施例中网络设备和终端设备之间以及终端设备和终端设备之间可以通过授权频谱(licensed spectrum)进行通信，也可以通过免授权频谱(unlicensed spectrum)进行通信，也可以同时通过授权频谱和免授权频谱进行通信，对此不做限定。无线接入网设备和终端设备之间以及终端设备和终端设备之间可以通过6吉兆赫(gigahertz，GHz)以下的频谱进行通信，也可以通过6GHz以上的频谱进行通信，还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请的实施例对网络设备和终端设备之间所使 用的频谱资源不做限定。
首先针对本申请实施例涉及到的部分名词进行解释，以便本领域技术人员理解本申请实施例的技术方案。
1、载波。本申请实施例中载波又可称之为频带、频段、频域范围等，为具有一定带宽的频域资源，例如，载波可以为SUL载波，也可以为非SUL载波。其中，SUL载波又可称之为SUL频带、SUL频段，可以为低频的频域资源，如sub3GHz频段；示例的，可以通过SUL载波来提高上行的覆盖范围。非SUL载波又可称之为non-SUL载波、non-SUL频段、非SUL频带、non-SUL频带等，可以为频率高于SUL载波的频域资源，如C波段(C-band)，非SUL载波也可以称之为UL频带。本申请实施例中涉及到的第一载波可以为非SUL载波，第二载波可以为SUL载波。SUL载波和非SUL载波可以属于同一个小区(cell)。
2、数据。本申请实施例中涉及的数据可以为普通数据、增强型移动宽带(enhanced mobile broadband，eMBB)业务数据、海量机器类通信(massive machine type communications，mMTC)业务数据、高可靠低时延通信(ultra reliable and low latency communications，URLLC)业务数据等，其中eMBB业务的主要特点是传输数据量大、传输速率高，典型的eMBB业务有：超高清视频、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR)等；mMTC业务的主要特点是联网设备数量巨大、传输数据量较小、数据对传输时延不敏感，典型的mMTC业务有：智能电网配电自动化、智慧城市等；URLLC业务的主要特点是超高可靠性、低延时，传输数据量较少以及具有突发性，典型的URLLC业务有：工业制造或生产流程中的无线控制、无人驾驶汽车和无人驾驶飞机的运动控制以及远程修理、远程手术等触觉交互类应用业务。示例的，本申请实施例的第一数据可以为eMBB业务数据、或者mMTC业务数据等对时延要求不高的业务类型的数据，本申请实施例的第二数据可以为基于网络设备调度的上行数据或者免调度的上行数据，例如eMBB业务数据、mMTC业务数据、URLLC业务数据等，对此不作限定。
3、免调度传输。本申请实施例涉及的免调度传输的机制为：网络设备为终端设备半静态配置用于发送免调度的上行数据的资源，终端设备在需要向网络设备发送免调度的上行数据时，可以从网络设备为终端设备配置的用于发送免调度的上行数据的资源上发送免调度的上行数据。由于终端设备在发送免调度的上行数据时，不需要网络设备的上行授权，因此发送免调度的上行数据的方式又可以称之为grant free的上行发送，或者configured grant的上行发送。而且由于在网络设备为终端设备半静态配置给终端设备用于发送免调度的上行数据的资源的过程中，无需向终端设备发送上行授权(uplink grant，UL grant)，因此，用于发送免调度的上行数据的资源又可称之为GF(grant free)资源。示例的，网络设备可以通过高层信令(如无线资源控制(radio resource control，RRC)信令)和/或物理层信令(例如下行控制信息(downlink control information，DCI))为终端设备半静态配置GF资源。而本申请实施例中的免调度的上行数据通常情况下为对时延要求较高的业务类型的数据，例如URLLC业务数据。
4、带宽部分。本申请实施例中的带宽部分又可称之为BWP(bandwidth part)、或者载波带宽部分、频率资源部分、部分频率资源或者其它名称，BWP可以为载波上的部分或全部的频域资源，可以是连续的频域资源，也可以为不连续的频域资源，例如，BWP可以包括多个连续的子载波，再如，BWP可以包括多个连续的资源块(physical resource block， PRB)等。连续的频域资源有利于降低资源分配的复杂度。终端设备可以支持多个BWP，即网络设备可以为终端设备配置多个BWP，当网络设备为终端设备配置多个BWP时，多个BWP之间可以重叠，也可以不重叠。此外，不同的BWP包括的频域资源的子载波间隔可以相同，也可以不同。其中，子载波间隔为资源单元(resource element，RE)的频域长度，取值可以包括15KHz、30KHz、或60KHz等。
5、本申请实施例中终端设备只能使用网络设备为终端设备配置的多个BWP中激活的GF资源来发送免调度的上行数据。在具体实现时，在一种情况中，网络设备给终端设备配置GF资源后，还可以对GF资源进行激活和去激活。此时，网络设备可以为终端设备配置多个BWP，在每个BWP上都配置GF资源，并向终端设备指示哪些BWP上的GF资源被激活，终端设备在激活的GF资源中选择来发送免调度上行数据的资源；或者，在另一种情况中，网络设备给终端设备配置了GF资源，在具体实现时，不对GF资源进行激活和去激活，示例的，网络设备为终端设备配置多个BWP，多个BWP上若均配置有GF资源，则在终端设备侧看来是这些BWP上配置的GF资源是均被激活的，在这种情况下，网络设备无需向终端设备发送响应的哪些BWP上的GF资源被激活的指示信息。
下面结合图1对本申请实施例发送上行数据的方法进行具体介绍。
如图2所示，本申请实施例中发送上行数据的方法，包括以下步骤。
步骤201，网络设备向终端设备发送控制信息，控制信息用于指示终端设备在第一资源上发送第一数据。
应理解，本申请实施例的控制信息可以为DCI，还可以为预定义的其它信息等，对此不作限定。
步骤202，终端设备在接收到控制信息后，当第一资源和用于终端设备发送第二数据的第二资源在时域上重合于第一时域范围时，在第一资源上、第一时域范围内停止发送第一数据，其中第一资源对应的频域范围属于第一载波，第二资源对应的频域范围属于第二载波。
本申请实施例中对第一时域范围的理解可以如图3a所示，也可以如图3b所示，还可以如图3c所示；其中，在图3a、图3b和图3c中，时域范围1为第一资源在时域上的时域范围，时域范围2为第二资源在时域上的时域范围，第一时域范围为时域范围1和时域范围2的重合部分。
应理解，本申请实施例中第一数据为基于网络设备调度的上行数据，由网络设备通过控制信息指示给终端设备第一数据在第一资源上发送，示例的，第一数据的类型和第二数据的类型可以不同。例如，第一数据可以为eMBB业务数据、或者mMTC业务数据等对时延要求不高的业务类型的数据；第二数据可以为基于网络设备调度的上行数据，也可以为免调度的上行数据，若第二数据为基于网络设备调度的上行数据，则由网络设备通过控制信息指示给终端设备第二数据在第二资源上发送，若第二数据为免调度的上行数据则由终端设备决定在第二资源上发送，示例的第二资源可以为GF资源，也可以为GB(grant based)资源，其中GB资源为终端设备发送基于网络设备调度的上行数据的资源。例如，第二数据可以为eMBB业务数据、mMTC业务数据、URLLC业务数据等，对此不作限定。
需要说明的是，本申请实施例中不限定免调度的上行数据必须在用于发送免调度的上行数据的资源上发送，也不限定基于网络设备调度的上行数据必须在网络设备通过控制信息指示的资源上发送。
此外，本申请实施例中由于当第一资源和第二资源在时域上重合于第一时域范围时，终端设备停止在第一资源上第一时域范围内发送第一数据，有效的支持了不支持同时在不同载波上的资源发送数据的终端设备的上行数据发送。
需要说明的是，本申请实施例中可以不限定第一资源对应的频域范围所属的第一载波和第二资源对应的频域范围所属的第二载波的频率的大小，可选的，由于在载波的频率较小时，上行覆盖范围较大，有助于提高上行数据传输的可靠性，因而进一步，可选的，在本申请实施例中第一载波的频率大于第二载波的频率，例如，第一载波为非SUL载波，第二载波为SUL载波，当第一载波的频率大于第二载波的频率时，第一载波的覆盖范围小于第二载波的覆盖范围，因此在第二资源上发送第二数据，有助于提高第二数据传输的可靠性。
在本申请实施例中当第一数据和第二数据为可靠性不高或者时延要求不高的情况下，可以同时不在第一时域范围内第一资源和第二资源上发送第一数据和第二数据，但是当第二数据为如URLLC等对时延和可靠性要求较高的业务类型的数据时，为了保证URLLC等对时延和可靠性较高的业务的要求，本申请实施例提供了以下几种具体实现方式。
方式一：
在第一资源上，终端设备在第一时域范围内停止发送第一数据；在第二资源上，终端设备在第一时域范围内发送第二数据。
例如，如图4所示，资源1为第一资源，时域范围1为资源1在时域上传输第一数据的时域范围，资源2为第二资源，时域范围2为资源2在时域上传输第二数据的时域范围，t1时刻为时域范围1内发送第一数据的起始时刻，t2时刻为时域范围2内发送第二数据的起始时刻，t3时刻为时域范围1内发送第一数据的结束时刻，t4时刻为时域范围2内发送第二数据的结束时刻，且t1小于等于t2，t3大于等于t4，在如图4所示的资源中，第一时域范围为时域范围2。可选的，终端设备从t2时刻开始直至t4时刻，停止在资源1上发送第一数据，从t2时刻开始直至t4时刻，在资源2上发送第二数据。然后，在t4时刻在资源2上结束发送第二数据后，可以继续从t4时刻开始直至t3时刻，在资源1上发送第一数据，或者，不再继续发送第一数据，或者，直接从t4时刻开始直至t3时刻在第二载波上发送第一数据，对此本申请实施例不作限定。
方式二：
考虑到终端设备的载波切换时间、处理能力，为降低第一数据和第二数据间的干扰，提高终端设备在第二资源上第一时域范围内发送第二数据成功的可能性，需要在发送第二数据前预留时间间隔、和/或在发送第二数据后预留时间间隔，在这两段时间间隔内终端设备无法在第一资源上发送第一数据。具体的，在第一资源上，终端设备不仅在第一时域范围内停止发送第一数据，而且终端设备在第一时域范围前的第二时域范围内和/或第一时域范围后的第三时域范围内停止发送第一数据，其中第二时域范围的终止时刻和第一时域范围的起始时刻重合，第一时域范围的终止时刻和第三时域范围的起始时刻重合；在第二资源上，终端设备在第一时域范围内发送第二数据。
例如，如图5a所示，资源1为第一资源，时域范围1为资源1在时域上发送第一数据的时域范围，资源2为第二资源，时域范围2为资源2在时域上发送第二数据的时域范围， t1时刻为时域范围1内发送第一数据的起始时刻，t2时刻为时域范围2内发送第二数据的起始时刻，t3时刻为时域范围1内发送第一数据的结束时刻，t4时刻为时域范围2内发送第二数据的结束时刻，t5时刻为停止发送第一数据的起始时刻，t6时刻为停止发送第一数据的结束时刻，Δ1为第二时域范围，Δ2为第三时域范围，其中t1<t5<t2，t4<t6<t3，在如图5a所示的资源中，第一时域范围为时域范围2。可选的，终端设备从t1时刻开始直至t5时刻，在资源1上发送第一数据，从t5时刻开始直至t6时刻，在资源1上停止发送第一数据，从t2时刻开始直至t4时刻，在资源2上发送第二数据。在t4时刻在资源2上结束发送第二数据后，可以继续从t6时刻开始直至t3时刻，在资源1上继续发送第一数据，或者，不再发送第一数据，或者，直接从t4时刻开始直至t3时刻，在第二载波上发送第一数据，对此本申请实施例不作限定。
再例如，如图5b所示，资源1为第一资源，时域范围1为资源1在时域上传输第一数据的时域范围，资源2为第二资源，时域范围2为资源2在时域上传输第二数据的时域范围，t1时刻为时域范围1内发送第一数据的起始时刻，t2时刻为时域范围2内发送第二数据的起始时刻，t3时刻为时域范围1内发送第一数据的结束时刻，t4时刻为时域范围2内发送第二数据的结束时刻，Δ2为第三时域范围，且t1大于t2，t3大于t4，在如图5b所示的资源中，第一时域范围为时域范围3。可选的，终端设备从t2时刻开始直至t4时刻，在资源2上发送第二数据；从t1时刻开始直至t4时刻，停止在资源1上发送第一数据，然后，从t5时刻开始直至t3时刻在资源1上发送第一数据，或者，从t1时刻开始直至t3时刻均不发送第一数据，或者，从t4时刻开始直至t3时刻在第二载波上发送第一数据，对此不作限定。
再例如，如图5c所示，资源1为第一资源，时域范围1为资源1在时域上传输第一数据的时域范围，资源2为第二资源，时域范围2为资源2在时域上传输第二数据的时域范围，t1时刻为时域范围1内发送第一数据的起始时刻，t2时刻为时域范围2内发送第二数据的起始时刻，t3时刻为时域范围1内发送第一数据的结束时刻，t4时刻为时域范围2内发送第二数据的结束时刻，Δ1为第二时域范围，且t1小于t2，t3小于t4，在如图5c所示的资源中，第一时域范围为时域范围3。可选的，终端设备从t1时刻开始直至t5时刻，在资源1上发送第一数据，从t5时刻开始直至t3时刻，停止在资源1上发送第一数据，从t2时刻开始直至t4时刻，在资源2上发送第二数据。
还需要说明的是，在本申请实施例方式二中，第二时域范围的长度和/或第三时域范围的长度为预先定义的；或者，第二时域范围的长度和/或第三时域范围的长度为网络设备通过向终端设备发送指示信息指示给终端设备的，其中，指示信息用于指示第二时域范围的长度和/或第三时域范围的长度。需要说明的是，第二时域范围的长度和第三时域范围的长度可以等于0，也可以大于0，对此不作限定，当第二时域范围的长度和第三时域范围的长度可以等于0时，适用于不考虑载波切换时间的场景。
具体的，本申请实施例中网络设备可以通过物理层信令(如DCI)和/或高层信令(如RRC信令)向终端设备发送指示信息，再或者通过预定义的信令向终端设备发送指示信息，本申请实施例对此不作限定。
方式三：
在第一资源上，终端设备在第一时域范围内停止发送第一数据；在第一资源上，终端 设备在第一时域范围内发送第二数据。
示例的，如图6所示，由资源1、资源2和资源3所组成的资源为第一资源，资源4为第二资源，时域范围1为第一资源在时域上传输第一数据的时域范围，时域范围2为第二资源在时域上传输第二数据的时域范围，t1时刻为时域范围1内发送第一数据的起始时刻，t2时刻为时域范围2内发送第二数据的起始时刻，t3时刻为时域范围1内发送第一数据的结束时刻，t4时刻为时域范围2内发送第二数据的结束时刻，在如图6所示的资源中，第一时域范围为时域范围2。可选的，终端设备从t1时刻开始直至t2时刻，在资源1上发送第一数据，从t2时刻开始直至t4时刻，停止在资源2和资源3上发送第一数据，从t2时刻开始直至t4时刻，在资源2上发送第二数据。终端设备在t4时刻结束在资源2上发送第二数据后，从t4时刻开始直至t3时刻可以在资源1上发送第一数据，也可以直接在第二载波上发送第一数据，还可以不再发送第一数据，对此本申请实施例不作限定。
方式四：
在第一资源上，终端设备在第一时域范围内发送第一数据和第二数据。
示例的，如图6所示，由资源1、资源2和资源3所组成的资源为第一资源，资源4为第二资源，时域范围1为第一资源在时域上传输第一数据的时域范围，时域范围2为第二资源在时域上传输第二数据的时域范围，t1时刻为时域范围1内发送第一数据的起始时刻，t2时刻为时域范围2内发送第二数据的起始时刻，t3时刻为时域范围1内发送第一数据的结束时刻，t4时刻为时域范围2内发送第二数据的结束时刻，在如图6所示的资源中，第一时域范围为时域范围2。可选的，终端设备从t1时刻开始直至t2时刻，在资源1上发送第一数据，从t2时刻开始直至t4时刻，在资源3和资源2上发送第一数据和第二数据。终端设备在t4时刻结束在资源2和资源3上结束发送第一数据和第二数据后，可以从t4时刻开始直至t3时刻在资源1上发送第一数据，也可以不再发送第一数据。具体的，终端设备从t2时刻开始直至t4，在资源3和资源2上发送第一数据和第二数据的一种具体实现方式为：终端设备可以使用随路(piggyback)方式将第一数据和第二数据共同编码，然后仅在资源2和资源3上时域范围2内进行发送。
此外，本申请实施例中，终端设备在第一资源上、第一时域范围内停止发送第一数据，在第二资源上、第一时域范围内发送第二数据时，对于网络设备而言，网络设备若在第二资源上、第一时域范围内接收到第二数据，则确定终端设备在第一资源上、第一时域范围内停止发送第一数据，如果网络设备在第一资源上、第一时域范围内接收到数据，则直接丢弃该数据，或者不对该数据进行解调等。
下面结合图1所示的移动通信系统架构，对在网络设备为终端设备配置了第一带宽部分和第二带宽部分，且第一带宽部分为第一载波上激活的带宽部分，第二带宽部分为第二载波上激活的带宽部分的情况下，本申请实施例提供的一种上行数据的发送方法进行详细介绍。
如图7所示，本申请实施例另一种发送上行数据的方法包括以下步骤。
步骤701，终端设备确定用于发送免调度的上行数据的第一资源，第一资源对应的频域范围属于第一带宽部分或者第二带宽部分，第一带宽部分和第二带宽部分为网络设备配置给终端设备的激活的带宽部分。
步骤702，终端设备通过第一资源向网络设备发送免调度的上行数据。
下面将用于发送免调度的上行数据的资源称之为GF资源，对本申请实施例进行介绍。
本申请实施例中，由于能够在跨载波同时激活两个带宽部分的情况下，通过激活的两个带宽部分中其中一个带宽部分上的GF资源来发送免调度的上行数据，有助于降低免调度的上行数据发送时出现差错。
应理解，当第二载波的频率小于第一载波的频率的情况下，第二载波的覆盖范围比第一载波的覆盖范围大，因而在第二载波上发送上行数据时，网络设备接收到的可能性更大。
因此，本申请实施例在第二载波的频率小于第一载波的频率的情况下，为了保证免调度数据传输的可靠性，终端设备确定第一资源对应的频域范围为第二带宽部分，即终端设备在第二带宽部分上的GF资源上发送免调度的上行数据。
本申请实施例为了使得终端设备在第二载波的频率小于第一载波的频率的情况下，在第二带宽部分上的GF资源发送免调度的上行数据：一种可选的方式为，在第一载波上不配置GF资源，只在第二载波上配置GF资源，具体实现时，可以在第一带宽部分上不配置GF资源，只在第二带宽部分上配置GF资源；另一种可选的方式为，在第一载波和第二载波同时配置GF资源的情况下，只激活第二载波上的GF资源，而不激活第一载波上的GF资源；具体实现时，可以在第一带宽部分和第二带宽部分同时配置GF资源的情况下，只激活第二带宽部分上的GF资源，而不激活第一带宽部分上的GF资源；再一种可选的方式为：由网络设备向终端设备发送配置信息，该配置信息用于指示终端设备使用哪个载波上的GF资源来发送免调度数据，例如：该配置信息用于指示终端设备使用发送免调度的上行数据的GF资源对应的频域范围为第二带宽部分，或者，该配置信息用于指示终端设备使用发送免调度的上行数据的GF资源对应的频域范围不为第一带宽部分，或者，该配置信息用于指示终端设备使用发送免调度的上行数据的GF资源对应的频域范围为第一带宽部分的优先级高于第二带宽部分，或者，该配置信息用于指示终端设备使用发送免调度的上行数据的GF资源属于第二载波，或者，该配置信息用于指示终端设备优先使用第二载波上的GF资源；又一种可选的方式为：在终端设备预定义使用发送免调度的上行数据的GF资源对应载波为第二载波，例如预定义GF资源对应的频域范围为第二带宽部分。
例如，如图8所示，第一载波为非SUL载波，第二载波为SUL载波，其中非SUL载波上配置有激活的GF资源，SUL载波上配置有激活的GF资源，则终端设备通过SUL载波上的GF资源发送免调度的上行数据。示例的，终端设备可以根据网络设备发送的配置信息来确定使用SUL载波上的GF资源发送免调度的上行数据，配置信息用于指示终端设备使用的GF资源为SUL载波上的GF资源；或者，终端设备根据预定义的规则通过SUL载波上的GF资源发送免调度的上行数据，例如预定义规则为在网络设备同时激活非SUL载波上配置的GF资源和SUL载波上配置的GF资源时，优先使用SUL载波上配置的GF资源。
需要说明的是，本申请实施例中执行如图7所示的发送上行数据的方法的终端设备也可以为第一终端设备，也可以为第二终端设备，其中第一终端设备又可称之为中心终端设备，距离网络设备较近，第二终端设备又可称之为边缘终端设备，距离网络设备较远。
进一步的，由于通常情况下，SUL载波上GF资源的有限性，在具体实现时，由于对于中心终端设备来说，距离基站较近，使用非SUL载波上的GF资源发送免调度的上行数据时，网络设备也能够接收到终端设备发送的免调度的上行数据，而对于边缘终端设备来 说，距离网络设备较远，若使用非SUL载波上的GF资源，网络设备有可能无法接收到使用SUL载波上的GF资源发送的免调度的上行数据，因此为了保证边缘终端设备发送免调度的上行数据的可靠性，本申请实施例中执行如图7所示的发送上行数据的方法的终端设备为边缘终端设备的。
对于中心终端设备来说，可以按照下列规则确定用于发送免调度的上行数据的GF资源对应的频带范围为第一带宽部分：
一种可选的方式为：在第一载波上配置GF资源，不在第二载波上配置GF资源，具体实现时，可以在第一带宽部分上配置GF资源，不在第二带宽部分上配置GF资源，另一种可选的方式为，在第一载波和第二载波同时配置GF资源的情况下，只激活第一载波上的GF资源，而不激活第二载波上的GF资源；具体实现时，可以在第一带宽部分和第二带宽部分同时配置GF资源的情况下，只激活第一带宽部分上的GF资源，而不激活第二带宽部分上的GF资源；再一种可选的方式为：由网络设备向终端设备发送配置信息，该配置信息用于指示终端设备使用哪个载波上的GF资源来发送免调度数据，例如：该配置信息用于指示终端设备使用发送免调度的上行数据的GF资源对应的频域范围不为第二带宽部分，或者，该配置信息用于指示终端设备使用发送免调度的上行数据的GF资源对应的频域范围为第一带宽部分，或者，该配置信息用于指示终端设备使用发送免调度的上行数据的GF资源对应的频域范围为第二带宽部分的优先级高于第一带宽部分，或者，该配置信息用于指示终端设备使用发送免调度的上行数据的GF资源属于第一载波，或者，该配置信息用于指示终端设备优先使用第一载波上的GF资源；又一种可选的方式为：在终端设备预定义使用发送免调度的上行数据的GF资源对应载波为第二载波，例如预定义GF资源对应的频域范围为第一带宽部分。
具体的，终端设备为中心终端设备还是边缘终端设备是由网络设备确定的。
此外，本申请实施例中，当终端设备在第一带宽部分发送上行数据时，其中该上行数据可以为免调度的上行数据，也可为基于网络设备调度的上行数据，终端设备需要在第二带宽部分的GF资源上发送免调度的上行数据，若需要在第二带宽部分的GF资源上发送的免调度的上行数据所对应的业务类型对时延的要求较高，则终端设备在第一时延小于等于预设阈值时，在第二带宽部分的GF资源上发送免调度的上行数据；其中，第一时延包括从第一带宽部分切换到第二带宽部分的时间和到达第一资源的时间。
例如，如图9所示，第一载波为非SUL载波，第二载波为SUL载波，非SUL载波上的GF资源为第一载波上用于发送免调度的上行数据的资源，SUL载波上的GF资源为第二载波上用于发送免调度的上行数据的资源，当终端设备在非SUL载波上发送上行数据的过程中，在T时刻终端设备确定需要在SUL载波的GF资源上发送URLLC业务数据，则若从非SUL载波切换到SUL载波需要的时间为Δt1，切换到SUL载波后到达SUL载波上的GF资源的时间为Δt2，则在(Δt1+Δt2)小于预设阈值的情况下，则终端设备从非SUL载波切换到SUL载波，在SUL载波的GF资源上发送URLLC业务数据。此外，当(Δt1+Δt2)大于预设阈值的情况下，若在非SUL载波上的GF资源上发送URLLC业务数据能够保证URLLC业务对时延的要求，则终端设备在非SUL载波上的GF资源发送URLLC业务数据，但是，当(Δt1+Δt2)大于预设阈值的情况下，若在非SUL载波上的GF资源上发送URLLC业务数据也不能够保证URLLC业务对时延的要求，则终端设备从非SUL载波切换到SUL载波，在SUL载波的GF资源上发送URLLC业务数据。还需要说明的是， 当SUL载波上没有可用的GF资源时，如图10所示，终端设备需要在第一时间窗内向无线接入网设备发送URLLC业务数据的情况下，由于第一时间窗内SUL载波没有可用的GF资源，因此终端设备只能在非SUL载波的GF资源上发送URLLC业务数据。
需要说明的是，在对上述图2和图7所示的发送上行数据的方法的具体介绍中，图2所示的发送上行数据的方法中涉及到的第一资源和第二资源、与图7所示的发送上行数据的方法中涉及到的第一资源和第二资源独立的，不存在相互的关联。
上述图2和图7所示的发送上行数据的方法是针对连接(connected)态的终端设备而言的，当终端设备处于空闲(idle)态的情况下，若终端设备需要发送免调度的上行数据(如URLLC业务数据)或者数据量较小的数据时，为了保证数据传输的可靠性，本申请实施例还提供了一种初始接入的方法。
下面结合如图1所示的移动通信系统架构对本申请实施例进行详细介绍。
如图11所示，本申请实施例初始接入的方法，包括：
步骤1101，终端设备接收第一系统信息块和第二系统信息块，其中，所述第一系统信息块指示第一载波上用于初始接入的资源位置，所述第二系统信息块用于指示第二载波上用于初始接入的资源位置，所述第一载波的频率大于所述第二载波的频率。
步骤1102，当满足下列条件中的至少一个时，终端设备通过第二载波进行初始接入；
初始接入过程中待发送数据的业务类型为预设类型、初始接入过程中待发送数据的数据量小于第一阈值和第一载波上的信号接收质量小于第二阈值。
具体的，在初始接入网络设备的过程中，终端设备首先接收同步信号块(synchronous signal block，SSB)，其中，SSB中包含物理广播信道(physical broadcast channel，PBCH)、主同步信号(primary synchronization signal，PSS)和辅同步信号(secondary synchronization signal，SSS)。然后，终端设备通过PBCH获得系统带宽、控制信道配置等信息，进一步接收第一系统信息块(system information block，SIB)和第二SIB，通过第一SIB来获得第一载波上用于初始接入的资源位置，通过第二SIB来获得第二载波上用于初始接入的资源位置，其中用于初始接入的资源可以为物理随机接入信道(physical random access channel，PRACH)，当终端设备通过第二载波进行初始接入时，则终端设备在第二载波上的PRACH上向网络设备发送随机接入请求(preamble)，并在接收到网络设备的发送的随机接入响应(random access response，RAR)后，根据RAR，在对应的上行时频资源上发送msg 3，其中RAR包含用于发送msg 3的上行时频资源位置信息。
本申请实施例中的上行频域资源为在频域上用于进行上行通信的物理资源，例如频域资源可以为BWP、资源块、子带、窄带等。频域资源还可以称为带宽资源、带宽部分、频率资源部分、部分频率资源或者其它名称。当带宽资源为系统频率资源中的一段连续资源时，带宽资源还可以称为子带、窄带或者其它名称，本申请实施例不做限制。
示例的，第一载波为非SUL载波，第二载波为SUL载波。
本申请实施例中，当终端设备在满足上述条件中的至少一个时，通过第二载波进行初始接入，即终端设备可以使用第二载波上的频域资源向网络设备发送随机接入请求，网络设备向终端设备发送的RAR中包括的用于发送msg 3的上行时频资源位置信息可以指示第 二载波上的频域资源，有助于提高msg3发送的可靠性。
下面对步骤1202中的每个条件作出说明：
初始接入过程中待发送数据的业务类型为预设类型，示例的，预设类型可以包括对要求时延小于某一阈值的业务数据的类型，和/或者高可靠性的业务数据的类型等，例如URLLC业务数据的类型。
以第二载波为SUL载波，待发送数据为URLLC业务数据，预设类型包括URLLC业务数据的类型，当初始接入过程中待发送URLLC业务数据时，终端设备通过SUL载波进行初始接入，则终端设备在SUL载波上向无线接入网设备发送msg3，msg3中包括URLLC业务数据。
初始接入过程中待发送数据的数据量小于第一阈值，其中，本申请实施例中第一阈值可以根据实际需求进行相应的设置，具体的，第一阈值可以为预定义的，也可以为终端设备在最近一次接入网络时，无线接入网设备指示给终端设备的，对此本申请实施例不作限定。
示例的，待发送数据为mMTC业务数据，且mMTC业务数据的数据量小于第一阈值，当初始接入过程中待发送mMTC业务数据时，终端设备通过SUL载波进行初始接入，则终端设备在SUL载波上向无线接入网设备发送msg3，msg3中包括mMTC业务数据。
第一载波上的信号接收质量小于第二阈值，其中，本申请实施例中第二阈值可以根据实际需求进行相应的设置，具体的，第二阈值可以为预定义的，也可以为终端设备在最近一次接入网络时，无线接入网设备指示给终端设备的，对此本申请实施例不作限定。
示例的，当第一载波上的信号接收质量小于第二阈值时，终端设备通过SUL载波进行初始接入。应理解，在具体实现时，信号接收质量可以通过参考信号接收功率(reference signal receiving power，RSRP)、参考信号接收质量(reference signal receiving quality，RSRQ)等来指示。
上述本申请提供的实施例中，分别从网络设备和终端设备之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，基站和终端设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
基于相同的构思，图12所示为本申请提供的一种装置1200，该装置1200可以是终端设备，也可以是能够支持终端设备实现图2涉及的方法中终端设备的功能的装置。示例性地，装置1200还可以是终端设备内的装置(如芯片或芯片系统)。需要说明的是，在本申请实施例中芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
装置1200中包括至少一个处理器1210，用于实现本申请实施例提供的发送上行数据的方法中终端设备的功能。
装置1200中还可以包括至少一个存储器1220，用于存储程序指令和/或数据。存储器1220和处理器1210耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处 理器1210可能和存储器1220协同操作。处理器1210可能执行存储器1220中存储的程序指令。所述至少一个存储器1220中的至少一个可以包括于处理器1210中。
装置1200还可以包括通信接口1230，装置1200可以通过通信接口1230和其它设备进行信息交互。通信接口1230可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。其中，示例性地，该其它设备可以是其它终端设备或网络设备。处理器1210可以利用通信接口1230收发数据，示例的，通信接口1230用于接收网络设备发送的控制信息。
本申请实施例中不限定上述通信接口1230、处理器1210以及存储器1220之间的具体连接介质。本申请实施例在图12中以存储器1220、处理器1210以及通信接口1230之间通过总线连接，总线在图12中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器还可以是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
如图13所示，为本申请提供的装置的另一个实施例，该装置可以是终端设备也可以终端设备中的装置(如芯片或芯片系统)，可执行上述如图2所示的任一实施例中由终端设备执行的方法。
该装置包括收发模块1301和处理模块1302，其中，收发模块1301用于接收网络设备发送的控制信息，控制信息用于指示装置在第一资源上发送第一数据；其中，当第一资源和用于收发模块1301发送第二数据的第二资源在时域上重合于第一时域范围时，在第一资源上，处理模块1302用于触发收发模块1301在第一时域范围内停止发送第一数据；第一资源对应的频域范围属于第一载波，第二资源对应的频域范围属于第二载波。
在一种可能的设计中，第一载波的频率大于第二载波的频率。
在一种可能的设计中，收发模块1301还用于在第二资源上、第一时域范围内发送第二数据。
在一种可能的设计中，处理模块1302还用于，触发收发模块1301在第一资源上、第一时域范围前的第二时域范围内和/或第一时域范围后的第三时域范围内停止发送第一数据，其中第二时域范围的终止时刻和第一时域范围的起始时刻重合，第一时域范围的终止时刻和第三时域范围的起始时刻重合。
在一种可能的设计中，第二时域范围的长度和/或第三时域范围的长度为预先定义的；或者，收发模块1301还用于接收网络设备发送的指示信息，指示信息用于指示第二时域 范围的长度和/或第三时域范围的长度。
在一种可能的设计中，第二载波为SUL载波，第一载波为非SUL载波。
在一种可能的设计中，第二数据为URLLC业务数据。
应理解，该装置可以用于实现本申请实施例的如图2所示的发送上行数据的方法中由终端设备执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的构思，如图14所示，为本申请提供的一种装置1400，该装置1400可以是网络设备，也可以是能够支持网络设备实现图2涉及的方法中网络设备的功能的装置。示例性地，装置1400可以是网络设备内的装置(如芯片或芯片系统)。需要说明的是，在本申请实施例中芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
装置1400中包括至少一个处理器1410，用于实现本申请实施例提供的发送上行数据的方法中网络设备的功能。装置1400还可以包括至少一个存储器1420，用于存储程序指令和/或数据。存储器1420和处理器1410耦合。处理器1410可能和存储器1420协同操作。处理器1410可能执行存储器1420中存储的程序指令。所述至少一个存储器1420中的至少一个可以包括于处理器1410中。
装置1400中还可以包括通信接口1430，装置1400可以通过通信接口1430和其它设备进行信息交互。通信接口1430可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。其中，示例性地，该其它设备可以是其它终端设备或网络设备。处理器1410可以利用通信接口1430收发数据，示例的，通信接口1430用于向终端设备发送控制信息。
本申请实施例中不限定上述通信接口1430、处理器1410以及存储器1420之间的具体连接介质。本申请实施例在图14中以存储器1420、处理器1410以及通信接口1430之间通过总线连接，总线在图14中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
如图15所示，为本申请提供的装置的另一个实施例，该装置可以是网设备也可以网络设备中的装置(如芯片或芯片系统)，可执行上述如图2所示的任一实施例中由网络设备执行的方法。
该装置包括收发模块1501和处理模块1502，其中收发模块1501用于向终端设备发送的控制信息，控制信息用于指示终端设备在第一资源上发送第一数据；处理模块1502用于若在第一时域范围内，收发模块1501在第二资源上接收到终端设备发送的第二数据，则确定终端设备在第一资源上、第一时域范围内停止发送第一数据；第二资源和第一资源在时域上重合于第一时域范围，第一资源对应的频域范围属于第一载波，第二资源对应的频域范围属于第二载波。
在一种可能的设计中，第一载波的频率大于第二载波的频率。
在一种可能的设计中，处理模块1502还用于确定在第一资源上，终端设备在第一时域范围前的第二时域范围内和/或第一时域范围后的第三时域范围内停止发送第一数据，其中第二时域范围的终止时刻和第一时域范围的起始时刻重合，第一时域范围的终止时刻和第三时域范围的起始时刻重合。
在一种可能的设计中，第二时域范围的长度和/或第三时域范围的长度为预先定义的；或者，收发模块1501还用于向终端设备发送指示信息，指示信息用于指示第二时域范围 的长度和/或第三时域范围的长度。
在一种可能的设计中，第一载波为非SUL载波，第二载波为SUL载波。
在一种可能的设计中，第二数据为URLLC业务数据。
应理解，该装置可以用于实现本申请实施例的如图2所示的发送上行数据的方法中由网络设备执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的构思，图16所示为本申请提供的一种装置1600，该装置1600可以是终端设备，也可以是能够支持终端设备实现图7涉及的方法中终端设备的功能的装置。示例性地，装置1600还可以是终端设备内的装置(如芯片或芯片系统)。需要说明的是，在本申请实施例中芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
装置1600中包括至少一个处理器1610，用于实现本申请实施例提供的发送上行数据的方法中终端设备的功能。
装置1600中还可以包括至少一个存储器1620，用于存储程序指令和/或数据。存储器1620和处理器1610耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1610可能和存储器1620协同操作。处理器1610可能执行存储器1620中存储的程序指令。所述至少一个存储器1620中的至少一个可以包括于处理器1610中。
装置1600还可以包括通信接口1630，装置1600可以通过通信接口1630和其它设备进行信息交互。通信接口1630可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。其中，示例性地，该其它设备可以是其它终端设备或网络设备。处理器1610可以利用通信接口1630收发数据，示例的，通信接口1630用于在第一资源上向网络设备发送的免调度的上行数据。
本申请实施例中不限定上述通信接口1630、处理器1610以及存储器1620之间的具体连接介质。本申请实施例在图16中以存储器1620、处理器1610以及通信接口1630之间通过总线连接，总线在图16中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如HDD或SSD等，还可以是易失性存储器，例如RAM。存储器还可以是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
如图17所示，为本申请提供的装置的另一个实施例，该装置可以是终端设备也可以终端设备中的装置(如芯片或芯片系统)，可执行上述如图7所示的任一实施例中由终端设备执行的方法。
该装置包括收发模块1701和处理模块1702，其中，处理模块1702用于确定用于发送 免调度的上行数据的第一资源，第一资源对应的频域范围属于第一带宽部分或者第二带宽部分，第一带宽部分和第二带宽部分为网络设备配置给装置的激活的带宽部分，且第一带宽部分为第一载波上激活的带宽部分，第二带宽部分为第二载波上激活的带宽部分；收发模块1701用于通过第一资源向网络设备发送免调度的上行数据。
在一种可能的设计中，第二载波的频率小于第一载波的频率，第一资源对应的频域范围属于第二带宽部分。
在一种可能的设计中，第一带宽部分上未激活配置的用于发送免调度的上行数据的第二资源，或者，第一带宽部分上未配置用于发送免调度的上行数据的第二资源。
在一种可能的设计中，收发模块1701还用于接收网络设备发送的配置信息，配置信息用于指示收发模块使用的用于发送免调度的上行数据的资源对应的频域范围属于第二带宽部分。
在一种可能的设计中，当收发模块1701用于发送上行数据的频域资源为第一带宽部分时，若第一时延小于等于预设阈值，则第一资源对应的频域范围属于第二带宽部分；其中，第一时延包括从第一带宽部分切换到第二带宽部分的时间和到达第一资源的时间。
在一种可能的设计中，第一载波为非SUL载波，第二载波为SUL载波。
在一种可能的设计中，免调度的上行数据为URLLC业务数据。
应理解，该装置可以用于实现本申请实施例的如图7所示的发送上行数据的方法中由终端设备执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的构思，如图18所示，为本申请提供的一种装置1800，该装置1800可以是网络设备，也可以是能够支持网络设备实现图7涉及的方法中网络设备的功能的装置。示例性地，装置1800可以是网络设备内的装置(如芯片或芯片系统)。需要说明的是，在本申请实施例中芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
装置1800中包括至少一个处理器1810，用于实现本申请实施例提供的发送上行数据的方法中网络设备的功能。装置1800还可以包括至少一个存储器1820，用于存储程序指令和/或数据。存储器1820和处理器1810耦合。处理器1810可能和存储器1820协同操作。处理器1810可能执行存储器1820中存储的程序指令。所述至少一个存储器1820中的至少一个可以包括于处理器1810中。
装置1800中还可以包括通信接口1830，装置1800可以通过通信接口1830和其它设备进行信息交互。通信接口1830可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。其中，示例性地，该其它设备可以是其它终端设备或网络设备。处理器1810可以利用通信接口1830收发数据，示例的，通信接口1830用于在第一资源上接收终端设备发送的免调度的上行数据。
本申请实施例中不限定上述通信接口1830、处理器1810以及存储器1820之间的具体连接介质。本申请实施例在图18中以存储器1820、处理器1810以及通信接口1830之间通过总线连接，总线在图18中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
如图19所示，为本申请提供的装置的另一个实施例，该装置可以是网设备也可以网络设备中的装置(如芯片或芯片系统)，可执行上述如图7所示的任一实施例中由网络设备执行的方法。
该装置包括收发模块1901和处理模块1902，其中，处理模块1902用于为终端设备配置第一带宽部分和第二带宽部分，第一带宽部分为第一载波上激活的带宽部分，第二带宽部分为第二载波上激活的带宽部分；收发模块1901用于在第一资源上接收终端设备发送的免调度的上行数据，第一资源对应的频域范围属于第一带宽部分或者第二带宽部分。
在一种可能的设计中，第二载波的频率小于第一载波的频率，第一资源对应的频域范围属于第二带宽部分。
在一种可能的设计中，第一带宽部分上未激活配置的用于发送免调度的上行数据的第二资源，或者，第一带宽部分上未配置用于发送免调度的上行数据的第二资源。
在一种可能的设计中，收发模块1901还用于向终端设备发送的配置信息，配置信息用于指示终端设备使用的用于发送免调度的上行数据的资源对应的频域范围属于第二带宽部分。
在一种可能的设计中，第一载波为非SUL载波，第二载波为SUL载波。
在一种可能的设计中，免调度的上行数据为URLLC业务数据。
应理解，该装置可以用于实现本申请实施例的如图7所示的发送上行数据的方法中由网络设备执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的构思，图20所示为本申请提供的一种装置2000，该装置2000可以是终端设备，也可以是能够支持终端设备实现图11涉及的方法中终端设备的功能的装置。示例性地，装置2000还可以是终端设备内的装置(如芯片或芯片系统)。需要说明的是，在本申请实施例中芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
装置2000中包括至少一个处理器2010，用于实现本申请实施例提供的初始接入的方法中终端设备的功能。
装置2000中还可以包括至少一个存储器2020，用于存储程序指令和/或数据。存储器2020和处理器2010耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器2010可能和存储器2020协同操作。处理器2010可能执行存储器2020中存储的程序指令。所述至少一个存储器2020中的至少一个可以包括于处理器2010中。
装置2000还可以包括通信接口2030，装置2000可以通过通信接口2030和其它设备进行信息交互。通信接口2030可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。其中，示例性地，该其它设备可以是其它终端设备或网络设备。处理器2010可以利用通信接口2030收发数据，示例的，通信接口2030用于接收第一系统信息块和第二系统信息块。
本申请实施例中不限定上述通信接口2030、处理器2010以及存储器2020之间的具体连接介质。本申请实施例在图20中以存储器2020、处理器2010以及通信接口2030之间通过总线连接，总线在图20中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图20中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现 为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如HDD或SSD等，还可以是易失性存储器，例如RAM。存储器还可以是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
如图21所示，为本申请提供的装置的另一个实施例，该装置可以是终端设备也可以终端设备中的装置(如芯片或芯片系统)，可执行上述如图11所示的任一实施例中由终端设备执行的方法。
该装置包括收发模块2101和处理模块2102，其中收发模块2101用于接收第一系统信息块和第二系统信息块，第一系统信息块指示第一载波上用于初始接入的资源位置，第二系统信息块用于指示第二载波上用于初始接入的资源位置，第一载波的频率大于第二载波的频率；当满足下列条件中的至少一个时，处理模块2102用于通过第二载波进行初始接入；
初始接入过程中待发送数据的业务类型为预设类型、初始接入过程中待发送数据的数据量小于第一阈值和第一载波上的信号接收质量小于第二阈值。
在一种可能的设计中，第一载波为非SUL载波，第二载波为SUL载波。
在一种可能的设计中，预设类型包括URLLC业务数据的类型。
应理解，该装置可以用于实现本申请实施例的如图11所示的初始接入的方法中由终端设备执行的步骤，相关特征可以参照上文，此处不再赘述。
基于相同的构思，如图22所示，为本申请提供的一种装置2200，该装置2200可以是网络设备，也可以是能够支持网络设备实现图11涉及的方法中网络设备的功能的装置。示例性地，装置2200可以是网络设备内的装置(如芯片或芯片系统)。需要说明的是，在本申请实施例中芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
装置2200中包括至少一个处理器2210，用于实现本申请实施例提供的初始接入的方法中网络设备的功能。装置2200还可以包括至少一个存储器2220，用于存储程序指令和/或数据。存储器2220和处理器2210耦合。处理器2210可能和存储器2220协同操作。处理器2210可能执行存储器2220中存储的程序指令。所述至少一个存储器2220中的至少一个可以包括于处理器2210中。
装置2200中还可以包括通信接口2230，装置2200可以通过通信接口2230和其它设备进行信息交互。通信接口2230可以是电路、总线、收发器或者其它任意可以用于进行信息交互的装置。其中，示例性地，该其它设备可以是其它终端设备或网络设备。处理器2210可以利用通信接口2230收发数据，示例的，通信接口2230用于向第一系统信息块和第二系统信息块。
本申请实施例中不限定上述通信接口2230、处理器2210以及存储器2220之间的具体连接介质。本申请实施例在图22中以存储器2220、处理器2210以及通信接口2230之间通过总线连接，总线在图22中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图22中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
如图23所示，为本申请提供的装置的另一个实施例，该装置可以是网设备也可以网 络设备中的装置(如芯片或芯片系统)，可执行上述如图11所示的任一实施例中由网络设备执行的方法。
该装置包括接收模块2301和发送模块2302，其中发送模块2302用于发送第一系统信息块和第二系统信息块，第一系统信息块指示第一载波上用于初始接入的资源位置，第二系统信息块用于指示第二载波上用于初始接入的资源位置，第一载波的频率大于第二载波的频率；然后，接收模块2301用于在终端设备满足下列条件中的至少一个时，通过第二载波接收终端设备初始接入过程中发送的数据；
终端设备在初始接入过程中待发送数据的业务类型为预设类型、终端设备在初始接入过程中待发送数据的数据量小于第一阈值和终端设备在第一载波上的信号接收质量小于第二阈值。
在一种可能的设计中，第一载波为非SUL载波，第二载波为SUL载波。
在一种可能的设计中，预设类型包括URLLC业务数据的类型。
应理解，该装置可以用于实现本申请实施例的如图11所示的初始接入的方法中由网络设备执行的步骤，相关特征可以参照上文，此处不再赘述。
如图24所示，本申请实施例的通信系统包括装置1200和装置1400。
如图25所示，本申请实施例的通信系统包括装置1600和装置1800。
如图26所示，本申请实施例的通信系统包括装置2000和装置2200。
应理解，图13、图15、图17、图19、图21和图23所示的装置为模块划分的方式是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端设备或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD))、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
本领域技术人员应明白，本申请的实施例可提供为方法、装置(设备)、计算机可读存储介质或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或 结合软件和硬件方面的实施例的形式，这里将它们都统称为“模块”或“系统”。
本申请是参照本申请的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (18)

  1. 一种发送上行数据的方法，其特征在于，所述方法包括：
    终端设备接收网络设备发送的控制信息，所述控制信息用于指示所述终端设备在第一资源上发送第一数据；
    当所述第一资源和用于所述终端设备发送第二数据的第二资源在时域上重合于第一时域范围时，在所述第一资源上，所述终端设备在所述第一时域范围内停止发送所述第一数据；
    其中，所述第一资源对应的频域范围属于第一载波，所述第二资源对应的频域范围属于第二载波。
  2. 如权利要求1所述的方法，其特征在于，所述第一载波的频率大于所述第二载波的频率。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    在所述第二资源上，所述终端设备在所述第一时域范围内发送所述第二数据。
  4. 如权利要求1至3任一所述的方法，其特征在于，所述方法还包括：
    在所述第一资源上，所述终端设备在所述第一时域范围前的第二时域范围内和/或所述第一时域范围后的第三时域范围内停止发送所述第一数据，其中所述第二时域范围的终止时刻和所述第一时域范围的起始时刻重合，所述第一时域范围的终止时刻和所述第三时域范围的起始时刻重合。
  5. 如权利要求4所述的方法，其特征在于，所述第二时域范围的长度和/或所述第三时域范围的长度为预先定义的；或者，
    所述方法还包括：
    所述终端设备接收所述网络设备发送的指示信息，所述指示信息用于指示所述第二时域范围的长度和/或所述第三时域范围的长度。
  6. 如权利要求1至5任一所述的方法，其特征在于，所述第一载波为非增补上行频率non-SUL载波，所述第二载波为增补上行频率SUL载波。
  7. 如权利要求1至6任一所述的方法，其特征在于，所述第二数据为高可靠低时延通信URLLC业务数据。
  8. 一种接收上行数据的方法，其特征在于，所述方法包括：
    网络设备向终端设备发送的控制信息，所述控制信息用于指示所述终端设备在第一资源上发送第一数据；
    若在第一时域范围内，所述网络设备在第二资源上接收到所述终端设备发送的第二数据，则确定所述终端设备在所述第一资源上、所述第一时域范围内停止发送所述第一数据；所述第二资源和所述第一资源在时域上重合于所述第一时域范围，所述第一资源对应的频域范围属于第一载波，所述第二资源对应的频域范围属于第二载波。
  9. 如权利要求8所述的方法，其特征在于，所述第一载波的频率大于所述第二载波的频率。
  10. 如权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述网络设备确定在所述第一资源上，所述终端设备在所述第一时域范围前的第二时域范围内和/或所述第一时域范围后的第三时域范围内停止发送所述第一数据，其中所述第 二时域范围的终止时刻和所述第一时域范围的起始时刻重合，所述第一时域范围的终止时刻和所述第三时域范围的起始时刻重合。
  11. 如权利要求10所述的方法，其特征在于，所述第二时域范围的长度和/或所述第三时域范围的长度为预先定义的；或者，
    所述方法还包括：
    所述网络设备向所述终端设备发送的指示信息，所述指示信息用于指示所述第二时域范围的长度和/或所述第三时域范围的长度。
  12. 如权利要求8至11任一所述的方法，其特征在于，所述第一载波为非增补上行频率SUL载波，所述第二载波为SUL载波。
  13. 如权利要求8至11任一所述的方法，其特征在于，所述第二数据为高可靠低时延通信URLLC业务数据。
  14. 一种装置，其特征在于，包括处理器，所述处理器与存储器耦合，并读取所述存储器中的指令，用于执行如权利要求1-7任一所述的方法。
  15. 如权利要求14所述的装置，其特征在于，所述装置为终端设备。
  16. 一种装置，其特征在于，包括处理器，所述处理器与存储器耦合，并读取所述存储器中的指令，用于执行如权利要求8-13任一所述的方法。
  17. 如权利要求16所述的装置，其特征在于，所述装置为网络设备。
  18. 一种计算机存储介质，其特征在于，所述计算机存储介质上存储有程序，所述程序被处理器执行时，用于实现如权利要求1至13任一所述的方法。
PCT/CN2019/072238 2018-02-12 2019-01-17 一种发送和接收上行数据的方法、装置及系统 Ceased WO2019154039A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19750517.5A EP3737191A4 (en) 2018-02-12 2019-01-17 METHOD, DEVICE AND SYSTEM FOR SENDING AND RECEIVING UPLINK DATA
US16/991,291 US20200374904A1 (en) 2018-02-12 2020-08-12 Uplink data sending and receiving method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810146743.8 2018-02-12
CN201810146743.8A CN110167149A (zh) 2018-02-12 2018-02-12 一种发送和接收上行数据的方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/991,291 Continuation US20200374904A1 (en) 2018-02-12 2020-08-12 Uplink data sending and receiving method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2019154039A1 true WO2019154039A1 (zh) 2019-08-15

Family

ID=67549294

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/072238 Ceased WO2019154039A1 (zh) 2018-02-12 2019-01-17 一种发送和接收上行数据的方法、装置及系统

Country Status (4)

Country Link
US (1) US20200374904A1 (zh)
EP (1) EP3737191A4 (zh)
CN (1) CN110167149A (zh)
WO (1) WO2019154039A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114342496A (zh) * 2019-11-20 2022-04-12 Oppo广东移动通信有限公司 一种上行接入方法、电子设备及存储介质
EP4075912A4 (en) * 2019-12-10 2022-11-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method and device, and storage medium

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112584438A (zh) * 2019-09-30 2021-03-30 大唐移动通信设备有限公司 一种业务传输的控制方法、终端和网络设备
CN112996114B (zh) * 2019-12-17 2023-01-31 成都鼎桥通信技术有限公司 资源调度方法、装置、设备及存储介质
CN111130740A (zh) * 2019-12-20 2020-05-08 成都川美新技术股份有限公司 一种缺失信令引导时的bgan上行信号接收方法及设备
CN113810979B (zh) * 2020-06-13 2023-03-24 华为技术有限公司 接入方法、装置、电子设备和可读存储介质
CN114915387B (zh) * 2021-02-09 2024-07-09 华为技术有限公司 数据发送方法、终端设备及计算机可读存储介质
CN112787794B (zh) * 2021-03-08 2021-11-23 深圳市佳贤通信设备有限公司 一种基于sul的urllc业务上行传输方法
CN113573420A (zh) * 2021-07-14 2021-10-29 上海闻泰信息技术有限公司 载波选择方法、装置、终端及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016164140A1 (en) * 2015-04-10 2016-10-13 Motorola Mobility Llc In-device coexistence with other technologies in lte license assisted access operation
CN107210881A (zh) * 2015-01-30 2017-09-26 瑞典爱立信有限公司 配置无线通信资源
CN107466486A (zh) * 2017-07-07 2017-12-12 北京小米移动软件有限公司 干扰协调方法及装置、基站和用户设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0012196D0 (en) * 2000-05-19 2000-07-12 Nokia Networks Oy Control circuitry
WO2017113425A1 (zh) * 2015-12-31 2017-07-06 华为技术有限公司 传输数据的方法和用户设备
CN107295674B (zh) * 2016-04-01 2021-06-08 华为技术有限公司 一种资源分配方法、网络设备及终端设备
CN116528373A (zh) * 2017-11-14 2023-08-01 交互数字专利控股公司 无线系统中的补充上行链路传输

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107210881A (zh) * 2015-01-30 2017-09-26 瑞典爱立信有限公司 配置无线通信资源
WO2016164140A1 (en) * 2015-04-10 2016-10-13 Motorola Mobility Llc In-device coexistence with other technologies in lte license assisted access operation
CN107466486A (zh) * 2017-07-07 2017-12-12 北京小米移动软件有限公司 干扰协调方法及装置、基站和用户设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Impact of SUL on configured grant", 3GPP TSG-RAN2 MEETING #AH-1801 R2-1801038, 26 January 2018 (2018-01-26), XP051386535 *
See also references of EP3737191A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114342496A (zh) * 2019-11-20 2022-04-12 Oppo广东移动通信有限公司 一种上行接入方法、电子设备及存储介质
EP4075912A4 (en) * 2019-12-10 2022-11-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method and device, and storage medium
US12256409B2 (en) 2019-12-10 2025-03-18 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission using uplink carrier switching method

Also Published As

Publication number Publication date
US20200374904A1 (en) 2020-11-26
CN110167149A (zh) 2019-08-23
EP3737191A1 (en) 2020-11-11
EP3737191A4 (en) 2021-01-20

Similar Documents

Publication Publication Date Title
WO2019154039A1 (zh) 一种发送和接收上行数据的方法、装置及系统
CN115699952B (zh) 一种通信方法、通信装置、通信系统以及计算机可读存储介质
EP3706492B1 (en) Method for preempting resources for data transmission
WO2020030051A1 (zh) 一种资源配置方法及装置
CN112737753A (zh) 一种信号传输方法、相关设备及系统
CN109152037B (zh) 带宽资源配置方法、装置和系统
WO2019137319A1 (zh) 一种用于反馈的方法、装置及系统
CN114731645B (zh) 在带宽部分上进行通信的方法
WO2019095940A1 (zh) 一种中继网络中时域资源的指示方法，网络设备及用户设备
CN111756511B (zh) 一种确定跳频频率的方法、设备及系统
CN118574167A (zh) 用于确定资源的方法和设备以及存储介质
US20190124705A1 (en) Identifier management method, apparatus, and system
WO2023143007A1 (zh) 信息传输方法和装置
US20250168921A1 (en) Communication method, apparatus, and device, and storage medium
WO2025044804A1 (zh) 一种载波聚合方法和通信装置
WO2021134572A1 (zh) 通信方法和通信设备
CN118921756A (zh) 一种通信方法、终端设备以及网络设备
WO2026037033A1 (zh) 通信方法、通信装置和计算机可读存储介质
KR20260009871A (ko) 사이드링크 통신을 위한 방법 및 장치
WO2025107171A1 (zh) 无线通信方法以及通信设备
WO2025036170A1 (zh) 一种上行传输方法及相关设备
WO2025036169A1 (zh) 一种小区激活方法及装置
TW202529480A (zh) 通信方法、裝置及儲存介質
WO2024055174A1 (zh) 部分带宽的确定方法、配置方法、装置、介质及程序产品
HK1258893A1 (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: 19750517

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019750517

Country of ref document: EP

Effective date: 20200803