WO2025166555A1 - 一种通信方法及设备、通信系统、通信设备、存储介质 - Google Patents

一种通信方法及设备、通信系统、通信设备、存储介质

Info

Publication number
WO2025166555A1
WO2025166555A1 PCT/CN2024/076403 CN2024076403W WO2025166555A1 WO 2025166555 A1 WO2025166555 A1 WO 2025166555A1 CN 2024076403 W CN2024076403 W CN 2024076403W WO 2025166555 A1 WO2025166555 A1 WO 2025166555A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
uplink
signaling
time window
network 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.)
Pending
Application number
PCT/CN2024/076403
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.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software 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 Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN202480026642.0A priority Critical patent/CN121040174A/zh
Priority to PCT/CN2024/076403 priority patent/WO2025166555A1/zh
Publication of WO2025166555A1 publication Critical patent/WO2025166555A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a communication method and device, a communication system, a communication device, and a storage medium.
  • the embodiments of the present disclosure provide a communication method and device, a communication system, a communication device, and a storage medium, which can be used in the field of communication technology to solve the bottleneck problem of system capacity in the EDT process.
  • a communication method is proposed, which is executed by a terminal, including: sending uplink data and/or uplink signaling to a network device; starting a response time window, the response time window being used to wait for receiving a response message sent by the network device, the response message including downlink data and/or downlink signaling; and receiving the response message within the response time window.
  • a terminal comprising a transceiver module and a processing module, wherein the transceiver module is used to send uplink data and/or uplink signaling to a network device; the processing module is used to start a response time window, and the response time window is used to wait for receiving a response message sent by the network device, the response message including downlink data and/or downlink signaling; the transceiver module is also used to receive a response message within the response time window.
  • a storage medium stores instructions.
  • the instructions When the instructions are executed on a communication device, the communication device executes any one of the methods of the first and second aspects.
  • FIG3A is a schematic flow chart of a communication method for a terminal according to an embodiment of the present disclosure
  • FIG4B is a flow chart of a communication method for a network device according to an embodiment of the present disclosure.
  • FIG5 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.
  • FIG6A is a schematic structural diagram of a terminal provided according to an embodiment of the present disclosure.
  • FIG6B is a schematic diagram of the structure of a network device provided according to an embodiment of the present disclosure.
  • FIG7A is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure.
  • FIG7B is a schematic diagram of the structure of a chip according to an embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a communication method and device, a communication system, a communication device, and a storage medium.
  • an embodiment of the present disclosure provides a communication method, which is executed by a terminal and includes: sending uplink data and/or uplink signaling to a network device; starting a response time window, where the response time window is used to wait for receiving a response message sent by the network device, where the response message includes downlink data and/or downlink signaling; and receiving the response message within the response time window.
  • the terminal achieves the purpose of communication between the terminal and the network device by sending an uplink message to the network device and waiting to receive a response message from the network device within a response time window.
  • the uplink signaling includes at least one of the following: message 1 Msg1 and/or message 3 Msg3 for a first early data transmission EDT process, the first EDT process is a random access channel RACH EDT process, and the first EDT process includes Msg1, Msg2, Msg3, and Msg4; Msg3 for a second EDT process, the second EDT process is a Msg1-less EDT process, and the second EDT process includes Msg3 and Msg4; the downlink signaling includes at least one of the following: message 2 Msg2 and/or message 4 Msg4 for the first early data transmission EDT process; Msg4 for the second EDT process.
  • sending uplink data and/or uplink signaling to the network device includes: sending uplink signaling based on the control plane, the uplink signaling carrying uplink data.
  • sending uplink data and/or uplink signaling to the network device includes: sending uplink data based on the user plane and sending uplink signaling based on the control plane in a multiplexed manner.
  • the terminal may send uplink data and/or uplink signaling in different ways, such as sending signaling via the control plane, or sending data and/or signaling in a multiplexed manner by combining the control plane and the user plane.
  • starting the response time window includes waiting for a first period of time after the subframe for sending uplink data and/or uplink signaling ends, and starting the response time window.
  • the first duration includes at least one of the following: a round-trip time RTT between the terminal and the network device; and a time offset.
  • the delay may be RTT, or time offset, or include RTT and time offset.
  • the method further includes: under the first condition, stopping the response time window.
  • the method further includes: performing a first operation when the response time window times out.
  • the first operation includes at least one of the following: falling back from the second EDT process to the first EDT process; retrying to execute the second EDT process when the number of attempts to execute the second EDT process is less than or equal to a preset threshold, otherwise falling back to the first EDT process; terminating the second EDT process.
  • the length of the response time window is predefined by a protocol or configured by a network device.
  • an embodiment of the present disclosure provides a communication method, which is executed by a network device, including: receiving uplink data and/or uplink signaling sent by a terminal; determining a response time window, the response time window being used for the terminal to wait for receiving a response message sent by the network device, the response message including downlink data and/or downlink signaling; and sending a response message to the terminal within the response time window.
  • the network device can determine a response time window for sending a response message to the terminal within the response time window, thereby achieving the purpose of communicating with the terminal within the response time window.
  • the uplink signaling includes at least one of the following: message 1 Msg1 and/or message 3 Msg3 for a first early data transmission EDT process, the first EDT process is a random access channel RACH EDT process, and the first EDT process includes Msg1, Msg2, Msg3, and Msg4; Msg3 for a second EDT process, the second EDT process is a Msg1-less EDT process, and the second EDT process includes Msg3 and Msg4; the downlink signaling includes at least one of the following: message 2 Msg2 and/or message 4 Msg4 for the first early data transmission EDT process; Msg4 for the second EDT process.
  • receiving uplink data and/or uplink signaling sent by the terminal includes: receiving uplink signaling based on the control plane, the uplink signaling carrying uplink data.
  • receiving uplink data and/or uplink signaling sent by the terminal includes: receiving uplink data based on the user plane and receiving uplink signaling based on the control plane in a multiplexing manner.
  • the first duration includes at least one of the following: a round-trip time RTT between the terminal and the network device; and a time offset.
  • the subframe at which the terminal ends sending uplink data and/or uplink signaling includes at least one of the following: the end subframe of the last transmission of uplink data and/or uplink signaling repeatedly sent multiple times by the terminal in one physical uplink shared channel PUSCH transmission; the end subframe of the last transmission of uplink data and/or uplink signaling repeatedly sent multiple times in each PUSCH transmission in which the terminal retransmits PUSCH.
  • the first condition includes at least one of the following: the terminal uses competitive resources to send uplink data and/or uplink signaling, and the response message received by the terminal includes the terminal identifier; the terminal uses competitive resources to send uplink data and/or uplink signaling, and the physical downlink control channel PDCCH of the response message received by the terminal includes a first resource identifier, and the first resource identifier is a demodulation reference signal DMRS resource identifier and/or an orthogonal cover code OCC resource identifier used by the terminal to send uplink data and/or uplink signaling; the terminal uses competitive resources to send uplink data and/or uplink signaling.
  • the PDCCH of the response message received by the terminal is identified by the first network identifier, and the first network identifier is the radio network temporary identifier RNTI corresponding to the uplink data and/or uplink signaling sent by the terminal; the terminal uses non-competitive resources to send uplink data and/or uplink signaling, and the response message received by the terminal includes layer 1 feedback L1-ACK; the response message received by the terminal includes a fallback indication, and the fallback indication is used to instruct the terminal to fall back to the RACH EDT process; the terminal receives the PDCCH, the PDCCH is identified by the RNTI configured for the terminal, and the media access control protocol data unit MAC PDU is successfully decoded.
  • the first network identifier is the radio network temporary identifier RNTI corresponding to the uplink data and/or uplink signaling sent by the terminal
  • the terminal uses non-competitive resources to send uplink data and/or uplink signaling, and the response message received by the terminal includes layer 1 feedback L1-ACK
  • the first operation includes at least one of the following: falling back from the second EDT process to the first EDT process; retrying to execute the second EDT process when the number of attempts to execute the second EDT process is less than or equal to a preset threshold, otherwise falling back to the first EDT process; terminating the second EDT process.
  • an embodiment of the present disclosure provides a terminal, comprising a transceiver module and a processing module, wherein the transceiver module is used to send uplink data and/or uplink signaling to a network device; the processing module is used to start a response time window, and the response time window is used to wait for receiving a response message sent by the network device, and the response message includes downlink data and/or downlink signaling; the transceiver module is also used to receive a response message within the response time window.
  • an embodiment of the present disclosure provides a communication device, comprising: one or more processors; wherein the one or more processors are used to call instructions so that the communication device executes the method described in any one of the embodiments of the first and second aspects.
  • an embodiment of the present disclosure provides a communication system, comprising: a terminal and a network device, wherein the terminal is used to execute the method described in any one of the embodiments in the first aspect of the present disclosure; the network device is used to execute the method described in any one of the embodiments in the second aspect of the present disclosure.
  • the terminal is at least one of the following: a non-terrestrial network NTN terminal; a reduced bandwidth and low complexity BL terminal; an enhanced coverage terminal; or a narrowband Internet of Things NB-IoT terminal.
  • an embodiment of the present disclosure provides a storage medium storing instructions.
  • the instructions When the instructions are executed on a communication device, the communication device executes the method described in any one of the embodiments of the first and second aspects of the present disclosure.
  • an embodiment of the present disclosure proposes a program product.
  • the program product is executed by a communication device
  • the communication device executes the method described in the optional implementation of the first and second aspects.
  • an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.
  • an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.
  • the present disclosure provides a communication method and device, a communication system, a communication device, and a storage medium.
  • the terms communication method and information processing method are interchangeable, the terms terminal, network device, information processing device, and communication device are interchangeable, and the terms information processing system and communication system are interchangeable.
  • each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined.
  • a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged.
  • the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
  • plurality refers to two or more.
  • the terms “at least one of,” “at least one of,” “at least one of,” “one or more,” “a plurality of,” “multiple,” etc. may be used interchangeably.
  • descriptions such as “at least one of A, B, C...”, “A and/or B and/or C...”, etc. include the situation where any one of A, B, C... exists alone, and also include any combination of any multiple of A, B, C..., and each situation can exist alone; for example, “at least one of A, B, C” includes the situation where A exists alone, B exists alone, C exists alone, the combination of A and B, the combination of A and C, the combination of B and C, and the combination of A, B, and C; for example, A and/or B includes the situation where A exists alone, B exists alone, and the combination of A and B.
  • descriptions such as "in one case A, in another case B,” or “in response to one case A, in response to another case B,” may include the following technical solutions depending on the situation: executing A independently of B (in some embodiments, A); executing B independently of A (in some embodiments, B); selectively executing A and B (in some embodiments, selecting between A and B); and executing both A and B (in some embodiments, A and B).
  • executing A independently of B in some embodiments, A
  • executing B independently of A in some embodiments, B
  • selectively executing A and B in some embodiments, selecting between A and B
  • executing both A and B in some embodiments, A and B.
  • prefixes such as “first” and “second” in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects.
  • the description object please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes.
  • the description object is a "field”
  • the ordinal number before the "field” in the "first field” and the "second field” does not limit the position or order between the "fields”.
  • “First” and “second” do not limit whether the "fields” they modify are in the same message, nor do they limit the order of the "first field” and the "second field”.
  • the description object is a "level”
  • the ordinal number before the "level” in the “first level” and the “second level” does not limit the priority between the "levels”.
  • the number of description objects is not limited by the ordinal number and can be one or more. Taking “first device” as an example, the number of "devices" can be one or more.
  • the objects modified by different prefixes can be the same or different.
  • the description object is "device”
  • the "first device” and the “second device” can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information”, then the "first information” and the “second information” can be the same information or different information, and their contents can be the same or different.
  • “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • time/frequency and time/frequency domain refer to the time domain and/or the frequency domain.
  • terms such as “in response to", “in response to determining", “in the case of", “at the time of", “when!, “if", “if", etc. can be used interchangeably.
  • terms such as “greater than”, “greater than or equal to”, “not less than”, “more than”, “more than or equal to”, “not less than”, “higher than”, “higher than or equal to”, “not less than”, and “above” can be replaced with each other, and terms such as “less than”, “less than or equal to”, “not greater than”, “less than”, “less than or equal to”, “not more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments.
  • Terms such as “device”, “equipment”, “device”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.
  • network can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).
  • the terms “access network device (AN device)”, “radio access network device (RAN device)”, “base station (BS)”, “radio base station”, “fixed station”, “node”, “access point”, “transmission point (TP)”, “reception point (RP)”, “transmission/reception point (TRP)”, “panel”, “antenna panel”, “antenna array”, “cell”, “macro cell”, “small cell”, “femto cell”, “pico cell”, “sector”, “cell group”, “carrier”, “component carrier”, “bandwidth part (BWP)” and the like may be used interchangeably.
  • terminal “terminal”, “terminal device”, “user equipment (UE)”, “user terminal”, “mobile station (MS)”, “mobile terminal (MT)”, subscriber station
  • subscriber station mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client and the like are used interchangeably.
  • the access network device, the core network device, or the network device can be replaced by a terminal.
  • the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.).
  • D2D device-to-device
  • V2X vehicle-to-everything
  • terms such as "uplink” and “downlink” can also be replaced by terms corresponding to communication between terminals (for example, "side”).
  • uplink channels, downlink channels, etc. can be replaced by side channels
  • uplinks, downlinks, etc. can be replaced by side links.
  • the terminal may be replaced by an access network device, a core network device, or a network device.
  • the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.
  • data, information, etc. may be obtained with the user's consent.
  • CIOT Cellular Internet of Things
  • MO-EDT Mobile Originated Early Data Transmission
  • Early Data Transmission can also be early data transmission, and early data transmission and early data transmission can be used interchangeably.
  • DMRS Demodulation Reference Signal
  • Random Access Channel RACH
  • PRACH Physical Random Access Channel
  • Evolved Packet System E-UTRAN + EPC collectively referred to as EPS
  • MME Mobile Management Entity
  • MME is the key control node of the 3GPP protocol LTE access network. It is responsible for the positioning of UE (User Equipment) in idle mode, paging process, including relay. It is involved in the bearer activation/deactivation process, and selects an S-GW (Serving GateWay) for the UE when it is initialized and connected. A user is authenticated by interacting with the HSS and a temporary ID is assigned to the user. MME also supports interception and monitoring within the scope permitted by law. MME provides a control function interface for 2G/3G access networks through the S3 interface. For roaming UEs, the S6a interface is also provided for the HSS.
  • UE User Equipment
  • S-GW Serving GateWay
  • S-GW Serving Gateway
  • the main functions of this device include: acting as a local anchor point during inter-eNodeB handover and assisting in the eNodeB reordering function; acting as a mobility anchor point during handover between different 3GPP access systems (terminating at the S4 interface, implementing service routing between the 2G/3G system and the P-GW), and also having a reordering function; performing lawful interception; routing and forwarding data packets; performing packet marking at the uplink and downlink transport layers; in idle state, buffering downlink packets and initiating network-triggered service requests; and being used for inter-operator billing, etc.
  • Radio Network Temporary Identity (RNTI)
  • PUSCH Physical Uplink Shared Channel
  • NTN Non-terrestrial network
  • Protocol Data Unit (PDU): MAC layer protocol data unit
  • MO-EDT allows one uplink data transmission followed by one downlink data transmission during the random access procedure.
  • MO-EDT is triggered when upper layers request the establishment or resumption of a Radio Resource Control (RRC) connection for mobile early data (i.e., non-signaling or SMS) and the uplink data size is less than or equal to the terabyte size indicated in the system information.
  • RRC Radio Resource Control
  • MO-EDT is not used for control plane data.
  • MO-EDT is only applicable to Basic IoT, Enhanced Coverage IoT, and Cellular-based Narrowband IoT users.
  • uplink user data is transmitted as NAS message in UL RRC Early Data Request message connected on CCCH; downlink user data can be optionally transmitted in NAS message in DL RRC Early Data Request message connected on CCCH; there is no transition to RRC connection.
  • the existing EDT process is based on the random access process.
  • the random access process includes: (1) a two-step random access process: the terminal sends MsgA; the network feeds back MsgB; the terminal matches MsgB with MsgA to determine whether the contention is resolved. (2) a four-step random access process: the terminal sends Msg1; the network feeds back Msg2; the terminal sends Msg3 based on the UL grant of Msg2; the network feeds back Msg4; the terminal matches Msg3 with Msg4 to determine whether the contention is resolved.
  • this disclosure proposes an EDT method without Msg1/Msg2, namely, only Msg3 and Msg4, hereinafter referred to as Msg1-Less EDT.
  • Msg3 is sent directly without Msg1 and Msg2, while Msg4 is transmitted efficiently to increase its capacity.
  • Msg4 is transmitted efficiently to increase its capacity.
  • the method proposed in the present disclosure is applicable to various communication systems, including but not limited to 4G, 5G, 5G-advance and subsequent communication technologies (such as 6G, etc.).
  • FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
  • a communication system 100 may include a terminal 101 and a network device 102 .
  • terminal 101 may be a device that sends uplink data and/or uplink signaling.
  • terminal 101 may be a device that initiates a response window.
  • terminal 101 may be a device that receives a response message.
  • terminal 101 may be a device that performs the first operation.
  • terminal 101 may be a device for determining the first condition.
  • terminal 101 may be a device that performs the first EDT process.
  • terminal 101 may be a device that performs the second EDT process.
  • the terminal 101 may be a non-terrestrial network (NTN) terminal.
  • NTN non-terrestrial network
  • terminal 101 may be a BL terminal.
  • terminal 101 may be an enhanced coverage terminal.
  • terminal 101 may be a NB-IoT terminal.
  • the name of the terminal 101 is not limited, and it can be, for example, "a device for sending uplink data", “a device for sending uplink signaling", “a device for receiving response messages”, or "a device for performing the first operation”.
  • the network device 102 may be a device that receives uplink data.
  • the network device 102 may be a device that receives uplink signaling.
  • network device 102 may be the device that sends the response message.
  • network device 102 may be a device that determines a response time window.
  • the name of the network device 102 is not limited, and it can be, for example, "a receiving device for uplink data”, “a sending device for response messages”, “a receiving device for uplink signaling”, “a determining device for response time windows”, etc.
  • the terminal may include at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home, but is not limited thereto.
  • a mobile phone a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless
  • the access network equipment may include at least one of an evolved Node B (eNB), a next generation eNB (ng-eNB), a next generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.
  • eNB evolved Node B
  • ng-eNB next generation Node B
  • gNB next generation Node B
  • gNB next generation Node B
  • NB node B
  • HNB home node B
  • HeNB home evolved node B
  • BBU
  • the technical solution of the present disclosure may be applicable to the Open RAN architecture.
  • the interfaces between or within the access network devices involved in the embodiments of the present disclosure may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.
  • the access network device may be composed of a centralized unit (CU) and a distributed unit (DU), where the CU may also be called a control unit.
  • the CU-DU structure may be used to split the protocol layers of the access network device, with some functions of the protocol layers centrally controlled by the CU, and the remaining functions of some or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.
  • a core network device may be a single device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements.
  • a network element may be virtual or physical.
  • the core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure.
  • Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.
  • the following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto.
  • the entities shown in Figure 1 are illustrative only.
  • the communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1.
  • the number and form of the entities may be arbitrary.
  • the connection relationship between the entities is illustrative only.
  • the entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 5G new radio NR
  • future radio access FAA
  • new radio access technology RAT
  • NR new radio
  • NX new radio access
  • FAA future generation radio access
  • GSM Global System for Mobile communications
  • CDMA2000 Global System for Mobile communications
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB)
  • Bluetooth registered trademark
  • PLMN Public Land Mobile Network
  • D2D Device-to-Device
  • M2M Machine-to-Machine
  • IoT Internet of Things
  • V2X Vehicle-to-Everything
  • systems using other user plane path establishment methods and next-generation systems extended based on them.
  • multiple systems can also be combined (for example, a combination of LTE or LTE-A with 5G, etc.) for application.
  • FIG. 2 is a schematic diagram of an interaction method provided by an embodiment of the present disclosure.
  • an embodiment of the present disclosure relates to a communication method that can be executed by a communication system, such as the communication system 100 shown in Figure 1.
  • the communication system includes a terminal and a network device.
  • the interaction method may include the following steps:
  • Step 2101 The terminal sends uplink data and/or uplink signaling to the network device.
  • the uplink signaling includes at least one of the following: message 1 Msg1 and/or message 3 Msg3 for a first early data transmission EDT process, the first EDT process is a random access channel RACH EDT process, and the first EDT process includes Msg1, Msg2, Msg3, and Msg4; Msg3 for a second EDT process, the second EDT process is a Msg1-less EDT process, and the second EDT process includes Msg3 and Msg4.
  • the first early data transmission and the first advance data transmission may be used interchangeably.
  • the uplink data and/or uplink signaling sent by the terminal to the network device can be based on RACHEDT or Msg1-less EDT.
  • the uplink signaling in the RACHEDT process can be Msg1 or Msg3
  • the uplink signaling in the Msg1-less EDT process can be Msg3.
  • the resource used by the terminal to send uplink signaling may be a competitive resource or a non-competitive resource.
  • the resources sent by Msg3 for Msg1-Less EDT can be competitive resources or non-competitive resources.
  • it can be a PUR resource that contains a UE-specific OCC resource configuration.
  • the UE is not configured with a unique OCC/DMRS resource.
  • the UE needs to select an OCC/DMRS resource from the OCC/DMRS resource pool.
  • Competitive resources can be sent to the UE through system messages or dedicated signaling, and non-competitive resources are sent to the UE through dedicated signaling.
  • the terminal sending uplink data and/or uplink signaling to the network device can be based on sending uplink signaling on the control plane, and the uplink signaling carries uplink data.
  • the terminal may send uplink data and/or uplink signaling to the network device in a multiplexed manner, sending uplink data based on the user plane and sending uplink signaling based on the control plane.
  • the terminal may send uplink data and/or uplink signaling to the network device based on the above two methods.
  • Msg3 of Msg1-Less EDT includes one or more of the following: UL RRC early data request information based on the control plane CIOT EPS/5GS; uplink user data transmission of the user plane CIOT EPS/5GS and UL RRC connection recovery request message on the control plane CCCH are sent in a multiplexed manner.
  • the terminal sending uplink data and/or uplink signaling to the network device also includes requesting the network device to configure a response time window.
  • Step 2102 The network device determines a response time window.
  • determining the response time window may be that the network device determines the length, the start node, and/or the end node of the response time window.
  • the network device determining the response time window may be that the network device determines the length of the response time window and configures the length of the response time window for the terminal.
  • the network device determines a response time window for the network device to send a response message to the terminal within the response time window.
  • Step 2103 The terminal starts a response time window.
  • the terminal initiating the response time window may be determining the length, the start node and/or the end node of the response time window.
  • the length of the response time window is configured by the network device.
  • the terminal may determine the response time window by configuring the length of the response time window based on a length predefined by a protocol.
  • the length of the response time window is configured by the network, or the length of the response time window may be configured by the CE level.
  • the terminal determines a response time window for the terminal to receive a response message sent by the network device within the response time window.
  • starting the response time window may be used for the terminal to receive a response message within the response time window. In other words, if the response time window is not started, the terminal cannot receive a response message sent by the network device.
  • starting the response time window may be starting the response time window by waiting for a first time period after the subframe in which uplink data and/or uplink signaling is finished being sent.
  • the subframe at which uplink data and/or uplink signaling ends being sent may be the subframe at which the last uplink data and/or uplink signaling is repeatedly sent multiple times in one physical uplink shared channel PUSCH transmission.
  • the terminal may send a PUSCH to the network device once, and repeatedly send uplink data and/or uplink signaling multiple times in one PUSCH. Each repeated transmission may be called a repetition.
  • the subframe that ends sending the uplink data and/or uplink signaling may be the end subframe of the last repetition, that is, the end position of the last repetition.
  • the first duration may be a round-trip time (RTT) between the terminal and the network device.
  • RTT round-trip time
  • the start time of the terminal response time window is the duration of waiting for an RTT after the subframe of the PUSCH transmission end position
  • the PUSCH transmission end position is the end position of the last repeatedly sent Msg3 of the PUSCH
  • the terminal is an NTN terminal.
  • the time offset may be the processing delay of the terminal in determining whether to open the response time window or the length of a subframe added to ensure normal reception of resources.
  • the time offset may be multiple subframes.
  • the time offset may be 0, 1, 2, 3, or 4 subframes.
  • the start time of the terminal response time window is the duration of waiting for a time offset after the subframe of the PUSCH transmission end position
  • the PUSCH transmission end position is the end position of the last repeated Msg3 sent by PUSCH
  • the terminal is an NB-IoT terminal or a BL terminal or a CE terminal.
  • the first duration may be the RTT and time offset between the terminal and the network device.
  • the start time of the terminal response time window is the duration of waiting for an RTT plus a time offset after the subframe of the PUSCH transmission end position
  • the PUSCH transmission end position is the end position of the last repeated Msg3 sent by PUSCH
  • the terminal is an NTN terminal.
  • the subframe at which uplink data and/or uplink signaling ends being sent may be the end subframe of the last transmission of uplink data and/or uplink signaling that is repeatedly sent multiple times in each PUSCH transmission of the retransmitted PUSCH.
  • the terminal may repeatedly send PUSCH to the network device one or more times, and repeatedly send uplink data and/or uplink signaling multiple times in each PUSCH sent.
  • Each repeated sending of uplink data and/or uplink signaling can be called a repetition, and the subframe that ends sending uplink data and/or uplink signaling can be the end subframe of the last repetition, that is, the position of the last repetition.
  • the first duration may be a round-trip time (RTT) between the terminal and the network device.
  • RTT round-trip time
  • the terminal may restart the response time window by waiting for an RTT after the subframe at the end of the retransmission, where the subframe at the end of the retransmission is the end position of the last repeated Msg3 of the retransmission PUSCH.
  • the terminal is an NTN terminal.
  • the first duration may be a time offset.
  • the terminal can restart the response time window, and the time for restarting the response time window is the length of time to wait for a time offset after the subframe at the end of the retransmission position, where the subframe at the end of the retransmission position is the end position of the last repeated Msg3 of the retransmission PUSCH.
  • the terminal is an NB-IoT terminal, a BL terminal, or a CE terminal.
  • the first duration may be a round-trip time (RTT) and a time offset between the terminal and the network device.
  • RTT round-trip time
  • the terminal can restart the response time window by waiting for an RTT plus the time offset after the subframe at the end of the retransmission.
  • the subframe at the end of the retransmission is the end position of the last repeated Msg3 of the retransmission PUSCH.
  • the terminal is an NTN terminal.
  • Step 2104 The network device sends a response message to the terminal.
  • the network device sending the response message to the terminal may be sending Msg to the terminal through downlink signaling.
  • the response message sent by the network device is sent based on uplink data and/or uplink signaling sent by the terminal.
  • the downlink signaling includes at least one of the following: message 2 Msg2 and/or message 4 Msg4 for the first early data transmission EDT process; Msg4 for the second EDT process.
  • the terminal sends Msg1 to the network device.
  • the network device After receiving Msg1, the network device sends Msg2 to the terminal within the response time window.
  • the terminal sends Msg3 to the network device.
  • the network device After receiving Msg3, the network device sends Msg4 to the terminal within the response time window.
  • the terminal sends Msg3 to the network device.
  • the network device After receiving Msg3, the network device sends Msg4 to the terminal within the response time window.
  • the network device sends a response message to the terminal within a response time window.
  • the network device sends Msg4 to the terminal within the response time window.
  • the network device sends a response message Msg4 including the terminal identifier to the terminal within the response time window.
  • the network device sends Msg4 to the terminal within the response time window, wherein the PDCCH of Msg4 includes the DMRS resource ID and/or OCC resource ID used by the terminal when sending Msg3.
  • the network device sends Msg4 to the terminal within the response time window, wherein the PDCCH of Msg4 is identified by the RNTI corresponding to Msg3 sent by the terminal.
  • the network device sends Msg4 including L1-ACK to the terminal within the response time window.
  • the network device sends Msg4 containing a Fallback indication to the terminal within the response time window.
  • the network device sends Msg4 to the terminal within the response time window, and the PDCCH of Msg4 is identified by the RNTI configured for the terminal.
  • Step 2105 The terminal stops responding to the time window.
  • the terminal stops responding to the time window under the first condition.
  • the terminal after the terminal stops responding to the time window, it no longer sends uplink data and/or uplink signaling to the network device, and accordingly, no longer receives a response message sent by the network device.
  • the first condition may be that the terminal uses competitive resources to transmit uplink data and/or uplink signaling, and the response message received by the terminal includes the terminal's identifier.
  • the terminal uses competitive resources to transmit uplink data and/or uplink signaling
  • the response message received by the terminal includes the terminal's identifier.
  • the terminal uses competitive resources to send Msg3 of the Msg1-Less EDT process.
  • the terminal receives the response message Msg4 containing the terminal identifier, the terminal stops the response window.
  • the terminal uses competitive resources to send Msg1 or Msg3 of the RACHEDT process.
  • the terminal receives the response message Msg2 or Msg4 containing the terminal identifier, the terminal stops the response window.
  • the first condition may be that the terminal uses competitive resources to send uplink data and/or uplink signaling
  • the physical downlink control channel PDCCH of the terminal receiving the response message includes a first resource identifier
  • the first resource identifier is the demodulation reference signal DMRS resource identifier and/or orthogonal cover code OCC resource identifier used by the terminal to send uplink data and/or uplink signaling.
  • the terminal uses competitive resources to send Msg3 of the Msg1-Less EDT process.
  • the PDCCH of Msg4 received by the terminal includes the DMRS resource ID and/or OCC resource ID used by the terminal when sending Msg3, and the terminal stops responding to the window.
  • the terminal uses competitive resources to send Msg1 or Msg3 of the RACH EDT process, and the PDCCH of Msg2 or Msg4 received by the terminal includes the DMRS resource ID and/or OCC resource ID used by the terminal when sending Msg1 or Msg3, and the terminal stops responding to the window.
  • the first condition may be that the terminal uses competitive resources to send uplink data and/or uplink signaling, the response message received by the terminal contains the terminal identifier, and the physical downlink control channel PDCCH of the response message includes a first resource identifier, and the first resource identifier is the demodulation reference signal DMRS resource identifier and/or orthogonal cover code OCC resource identifier used by the terminal to send uplink data and/or uplink signaling.
  • the terminal uses contention resources to send Msg1 or Msg3 of the RACH EDT process.
  • the terminal receives the PDCCH of Msg2 or Msg4 including the terminal identifier and the DMRS resource ID and/or OCC resource ID used by the terminal when sending Msg1 or Msg3, and the terminal stops responding to the window.
  • the terminal uses competitive resources to send Msg3 of the Msg1-Less EDT process.
  • the terminal receives Msg4 which contains the terminal's identification, and the PDCCH of Msg4 includes the DMRS resource ID and/or OCC resource ID used by the terminal when sending Msg3.
  • the terminal stops responding to the window.
  • the first condition may be that the terminal uses competitive resources to send uplink data and/or uplink signaling, and the PDCCH on which the terminal receives the response message is identified by a first network identifier, which is the wireless network temporary identifier RNTI corresponding to the terminal sending uplink data and/or uplink signaling.
  • a first network identifier which is the wireless network temporary identifier RNTI corresponding to the terminal sending uplink data and/or uplink signaling.
  • the terminal uses competitive resources to send Msg3 of the Msg1-Less EDT process.
  • the UE receives the PDCCH of Msg4 and identifies it through the RNTI corresponding to the Msg3 sent by the terminal, and the terminal stops responding to the window.
  • the terminal uses competitive resources to send Msg1 or Msg3 of the RACH EDT process.
  • the UE receives the PDCCH of Msg2 or Msg4 and identifies it through the RNTI corresponding to the Msg1 or Msg3 sent by the terminal, and the terminal stops the response window.
  • the first condition may be that the terminal uses competitive resources to send uplink data and/or uplink signaling, the response message received by the terminal contains the terminal's identifier, and the PDCCH of the response message is identified by the first network identifier, which is the wireless network temporary identifier RNTI corresponding to the terminal sending uplink data and/or uplink signaling.
  • the terminal uses competitive resources to send Msg3 of the Msg1-Less EDT process.
  • the UE receives Msg4 containing the terminal's identification, and the PDCCH of Msg4 is identified by the RNTI corresponding to Msg3 sent by the terminal, and the terminal stops responding to the window.
  • the terminal uses competitive resources to send Msg1 or Msg3 of the RACH EDT process, the UE receives Msg2 or Msg4 containing the terminal identification, and the PDCCH of Msg2 or Msg4 is identified by the RNTI corresponding to Msg1 or Msg3 sent by the terminal, and the terminal stops responding to the window.
  • the first condition may be that the terminal uses competitive resources to transmit uplink data and/or uplink signaling
  • the response message received by the terminal includes an identifier of the terminal
  • a physical downlink control channel (PDCCH) of the response message includes a first resource identifier, where the first resource identifier is a demodulation reference signal (DMRS) resource identifier and/or an orthogonal cover code (OCC) resource identifier used by the terminal to transmit uplink data and/or uplink signaling.
  • the PDCCH of the response message is identified by a first network identifier, where the first network identifier is a radio network temporary identifier (RNTI) corresponding to the uplink data and/or uplink signaling transmitted by the terminal.
  • RNTI radio network temporary identifier
  • the terminal uses competitive resources to send Msg3 of the Msg1-Less EDT process.
  • the UE receives Msg4 which contains the terminal's identifier, and the PDCCH of Msg4 includes the terminal's identifier and the DMRS resource ID and/or OCC resource ID used by the terminal when sending Msg1 or Msg3.
  • the PDCCH is identified by the RNTI corresponding to the Msg3 sent by the terminal, and the terminal stops responding to the window.
  • the terminal uses competitive resources to send Msg1 or Msg3 of the RACH EDT process
  • the UE receives Msg2 or Msg4 containing the terminal identifier
  • the PDCCH of Msg2 or Msg4 includes the terminal identifier and the DMRS resource ID and/or OCC resource ID used by the terminal when sending Msg1 or Msg3
  • the PDCCH is identified by the RNTI corresponding to the Msg1 or Msg3 sent by the terminal, and the terminal stops the response window.
  • the first condition may be that the terminal uses non-competitive resources to send uplink data and/or uplink signaling, and the response message received by the terminal includes layer 1 feedback L1-ACK.
  • the terminal uses non-competitive resources to send Msg3 of the Msg1-Less EDT process. If the terminal receives Msg4 containing L1-ACK, the UE stops the response window.
  • the terminal uses non-competitive resources to send Msg1 or Msg3 of the RACH EDT process. If the terminal receives Msg2 or Msg4 containing L1-ACK, the UE stops the response window.
  • the first condition may be that the response message received by the terminal includes a fallback indication, and the fallback indication is used to instruct the terminal to fall back to the RACH EDT process.
  • the terminal uses competitive resources or non-competitive resources to send Msg3 of the Msg1-Less EDT process. If the terminal receives Msg4 containing a Fallback indication, the UE stops responding to the window.
  • the terminal uses competitive resources or non-competitive resources to send Msg1 or Msg3 of the RACH EDT process. If the terminal receives Msg2 or Msg4 containing a Fallback indication, the UE stops the response window.
  • the first condition may be that the terminal receives a PDCCH, the PDCCH is identified by an RNTI configured for the terminal, and the medium access control protocol data unit MAC PDU is successfully decoded.
  • the first condition may be that the terminal receives a PDCCH identified by the RNTI configured for the terminal and the media access control protocol data unit MAC PDU is successfully decoded.
  • the terminal uses competitive resources or non-competitive resources to send Msg3 of the Msg1-Less EDT process. If the terminal receives a PDCCH identified by the RNTI configured for the terminal and the MAC PDU is successfully decoded, the terminal stops the response window.
  • the terminal uses competitive resources or non-competitive resources to send Msg1 or Msg3 of the RACH EDT process. If the terminal receives the PDCCH identified by the RNTI configured for the terminal and the MAC PDU is successfully decoded, the terminal stops the response window.
  • the first condition for the terminal to stop responding to the time window may be a combination of one or more of the above embodiments, which is not limited in the present disclosure.
  • the terminal determines whether to end the response time window based on the received response message.
  • the purpose of controlling the terminal receiving window is achieved by setting different conditions for the terminal to end the response time window.
  • Step 2106 The terminal performs the first operation.
  • the terminal performs a first operation when the response time window times out.
  • the first operation may be to fall back from the second EDT process to the first EDT process.
  • the terminal falls back from the Msg1-Less EDT process to the RACH-based EDT process.
  • the first operation may be to retry executing the second EDT process when the number of attempts to execute the second EDT process is less than or equal to a preset threshold, and otherwise fall back to the first EDT process.
  • the preset threshold may be a threshold configured by the network device.
  • the terminal retries Msg1-Less EDT. Otherwise, it falls back to RACH-based EDT or terminates Msg1-Less EDT.
  • the first operation may be to terminate the second EDT process.
  • the terminal terminates Msg1-Less EDT.
  • the terminal when the response time window times out, if the number of attempts to send Msg1-Less EDT is less than or equal to the threshold, the terminal will retry the Msg1-Less EDT. Otherwise, the terminal will terminate the Msg1-Less EDT.
  • the terminal may perform any of the above first operations, continue to send uplink data and/or uplink signaling in step 2101, or fall back to the RACH-based EDT process, or terminate the EDT process.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps 2101 to 2106.
  • step 2101 can be implemented as an independent embodiment
  • step 2102 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.
  • Steps 2101+2102, step 2101+2102+2103, step 2101+2102+2103+2104, step 2101+2102+2103+2104+2105, step 2101+2102+2103+2105, step 2101+2102+2103+2105+2106, and step 2101+2102+2103+2104+2105+2106 can be implemented as independent embodiments, but the present invention is not limited thereto.
  • step 2104 and step 2106 are optional, and all or part of these steps may be omitted or replaced in different embodiments.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • FIG3A is a flow chart of a communication method of a terminal according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 3101 Send uplink data and/or uplink signaling to a network device.
  • step 3101 can refer to the optional implementation of step 2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
  • Step 3102 start the response time window.
  • step 3102 For optional implementations of step 3102, reference may be made to the optional implementations of step 2103 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step 3103 Receive a response message sent by the network device.
  • step 3103 please refer to the optional implementations of step 2104 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step 3104 stop the response time window.
  • step 3104 please refer to the optional implementations of step 2105 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step 3105 perform the first operation.
  • step 3105 please refer to the optional implementations of step 2106 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps 3101 to 3105.
  • step 3101 can be implemented as an independent embodiment
  • step 3102 can be implemented as an independent embodiment. And so on, but the present invention is not limited to this.
  • Steps 3101+3102, steps 3101+3102+3103, steps 3101+3102+3103+3104, steps 3101+3102+3104+3105, and steps 3101+3102+3103+3104+3105 can be implemented as independent embodiments, but the present invention is not limited to this.
  • Figure 3B is a flow chart of a communication method for a terminal according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 3201 Send uplink data and/or uplink signaling to the network device.
  • step 3201 can be found in step 2101 of FIG. 2 , optional implementations of step 3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.
  • Step 3202 Start a response time window.
  • the response time window is used to wait for a response message sent by a network device, where the response message includes downlink data and/or downlink signaling.
  • Step 3203 Receive a response message within the response time window.
  • step 3203 can be found in step 2104 of FIG. 2 , the optional implementation of step 3103 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.
  • step 3201 may be combined with step 3102 in FIG. 3A
  • step 3203 may be combined with step 3104 in FIG. 3A .
  • FIG4A is a flow chart of a communication method for a network device according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 4101 Receive uplink data and/or uplink signaling sent by the terminal.
  • step 4101 can refer to the optional implementation of step 2101 in Figure 2, step 3101 in Figure 3A, step 3201 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.
  • Step 4102 Determine the response time window.
  • step 4102 can refer to the optional implementation of step 2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
  • Step 4103 Send a response message to the terminal.
  • step 4103 can refer to the optional implementation of step 2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps 4101 to 4103.
  • step 4101 can be implemented as an independent embodiment
  • step 4102 can be implemented as an independent embodiment. And so on, but the present invention is not limited thereto.
  • Steps 4101 + 4103 and steps 4101 + 4102 + 4103 can be implemented as independent embodiments, but the present invention is not limited thereto.
  • FIG4B is a flow chart of a communication method for a network device according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which includes:
  • Step 4201 Receive uplink data and/or uplink signaling sent by the terminal.
  • step 4201 can be found in step 2101 of Figure 2, step 3101 of Figure 3A, step 3201 of Figure 3B, the optional implementation of step 4101 of Figure 4A, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 4A, which will not be repeated here.
  • Step 4202 determine the response time window.
  • the response time window is used for the terminal to wait for receiving a response message sent by the network device, where the response message includes downlink data and/or downlink signaling.
  • step 4202 can be found in step 2102 of FIG. 2 , optional implementations of step 4102 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.
  • Step 4203 Send a response message to the terminal within the response time window.
  • step 4203 can be found in step 2104 of FIG. 2 , the optional implementation of step 4103 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.
  • step 4201 may be combined with step 4102 in FIG. 4A .
  • FIG5 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG5 , an embodiment of the present disclosure relates to a communication method, and the method includes:
  • Step 5101 The terminal sends uplink data and/or uplink signaling to the network device.
  • step 5101 can be found in step 2101 of Figure 2, step 3101 of Figure 3A, step 3201 of Figure 3B, step 4101 of Figure 4A, and step 4201 of Figure 4B, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, and 4B, which will not be repeated here.
  • Step 5102 start the response time window.
  • the response time window is used to wait for a response message sent by a network device, where the response message includes downlink data and/or downlink signaling;
  • step 5102 can refer to the optional implementation of step 2103 in Figure 2, step 3103 in Figure 3A, step 3202 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.
  • Step 5103 Receive a response message within the response time window.
  • step 5103 please refer to step 2104 of Figure 2, step 3103 of Figure 3A, step 3203 of Figure 3B, step 4103 of Figure 4A, and step 4203 of Figure 4B, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, and 4B, which will not be repeated here.
  • the above method may include the method described in the above terminal side, network device side, etc. embodiments, which will not be repeated here.
  • each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.
  • the communication method proposed in this disclosure includes sending uplink data and/or uplink signaling to a network device via a terminal; initiating a response window, which is used to wait for a response message sent by the network device, the response message including downlink data and/or downlink signaling; and receiving the response message within the response window.
  • the terminal sends uplink data and/or uplink signaling to the network device
  • the response window is initiated and the response message is waited for within the response window, thereby achieving the purpose of sending data or signaling between the terminal and the network device.
  • the UE can send Msg3 in the following two ways:
  • the resources sent in Msg3 for Msg1-Less EDT can be either competitive or non-competitive resources.
  • Non-competitive resources can be PUR resources that contain a UE-specific OCC resource configuration.
  • the UE is not configured with a unique OCC/DMRS resource.
  • the UE must select an OCC/DMRS resource from the OCC/DMRS resource pool.
  • Competitive resources can be sent to the UE via system messages or dedicated signaling, while non-competitive resources are sent to the UE via dedicated signaling.
  • Msg3 of Msg1-Less EDT includes one or more of the following: UL RRC early data request information based on the control plane CIOT EPS/5GS; uplink user data transmission of the user plane CIOT EPS/5GS and UL RRC connection recovery request message on CCCH are sent in a multiplexed manner.
  • Msg1-Less EDT may be the second EDT process.
  • step 1 can refer to the optional implementation of step 2101 of Figure 2, step 3101 of Figure 3A, step 3201 of Figure 3B, step 4101 of Figure 4A, step 4201 of Figure 4B, and step 5101 of Figure 5, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, 4B, and 5, which will not be repeated here.
  • the response window can be replaced with a response time window.
  • the start time of the UE response window is the subframe containing the end position of the PUSCH transmission + UE-gNB RTT + X.
  • the RTT round trip time is determined by two propagation delays, one from the UE to the satellite and the other from the satellite to the base station.
  • X is 0, 1, 2, 3, or 4 subframes.
  • X may be a time offset
  • the end position of PUSCH transmission is the end position of the last repetition of PUSCH.
  • the UE is an NTN UE.
  • the UE restarts the response window at the subframe where the retransmission ends + UE-gNB RTT + X.
  • X is 0, 1, 2, 3, or 4 subframes.
  • X may be a time offset
  • the retransmission end position is the end position of the last repetition of the retransmitted PUSCH.
  • the UE is an NTN UE.
  • the UE stops responding to the window.
  • condition for stopping the response window may be the first condition.
  • the UE receives the PDCCH of Msg4 and identifies it through the RNTI corresponding to the Msg3 sent by the UE, and the UE stops the response window.
  • step 4.1 can be combined with step 4.1.1 as a condition for stopping the response window.
  • step 4.1 can be combined with step 4.1.2 as a condition for stopping the response window.
  • step 4.1 can be combined with steps 4.1.1 and 4.1.2 as conditions for stopping the response window.
  • the UE uses non-competitive resources to send Msg3 of Msg1-Less EDT. If the UE receives Msg4 containing L1-ACK, the UE stops the response window.
  • the UE stops the response window.
  • each embodiment in step 4 can be independent or combined.
  • step 4 can refer to the optional implementation of step 2104, step 2105 in Figure 2, step 3103, step 3104 in Figure 3A, step 4102 in Figure 4A, step 4202 in Figure 4B, and step 5103 in Figure 5, as well as other related parts in the embodiments involved in Figures 2, 3A, 4A, 4B, and 5, which will not be repeated here.
  • the UE performs any of the following operations:
  • RACH-based EDT may be the first EDT process.
  • the UE If the number of times the UE attempts Msg1-Less EDT is less than or equal to the threshold, the UE retries Msg1-Less EDT. Otherwise, the UE falls back to RACH-based EDT or terminates Msg1-Less EDT.
  • the threshold value may be a preset threshold value, and the network device configures the maximum number of times the terminal attempts the second EDT process.
  • UE terminates Msg1-Less EDT.
  • step 5 can refer to the optional implementation of step 2106 in Figure 2, step 3105 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps 1 to 5.
  • step 1 can be implemented as an independent embodiment
  • step 2 can be implemented as an independent embodiment
  • step 3 can be implemented as an independent embodiment, and so on, without limitation thereto.
  • step 1+2 can be implemented as an independent embodiment
  • step 1+3 can be implemented as an independent embodiment
  • step 1+2+4 can be implemented as an independent embodiment
  • step 1+3+4 can be implemented as an independent embodiment
  • step 1+2+4+5 can be implemented as an independent embodiment
  • step 1+3+4+5 can be implemented as an independent embodiment
  • step 1+2+3+4+5 can be implemented as an independent embodiment, but without limitation thereto.
  • the embodiments of the present disclosure further provide an apparatus for implementing any of the above methods.
  • an apparatus comprising units or modules for implementing each step performed by a terminal in any of the above methods.
  • another apparatus comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.
  • a network device e.g., an access network device, a core network function node, a core network device, etc.
  • the division of the various units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated.
  • the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory.
  • the processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device.
  • CPU central processing unit
  • microprocessor a microprocessor
  • the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be implemented by designing the hardware circuits.
  • the above-mentioned hardware circuits may be understood as one or more processors.
  • the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above-mentioned units or modules may be implemented by designing the logical relationship between the components in the circuit.
  • ASIC application-specific integrated circuit
  • the above-mentioned hardware circuit may be implemented by a programmable logic device (PLD).
  • PLD programmable logic device
  • FPGA field programmable gate array
  • it may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured through a configuration file, thereby implementing the functions of some or all of the above-mentioned units or modules. All units or modules of the above-mentioned devices may be implemented entirely by the processor calling software, or entirely by hardware circuits, or partially by the processor calling software, and the remaining part by hardware circuits.
  • the processor is a circuit with signal processing capabilities.
  • the processor may be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP).
  • the processor may implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable.
  • the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules.
  • it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as the Neural Network Processing Unit (NPU), the Tensor Processing Unit (TPU), the Deep Learning Processing Unit (DPU), etc.
  • Figure 6A is a structural diagram of a terminal provided according to an embodiment of the present disclosure.
  • the terminal 6100 includes a transceiver module 6101 and a processing module 6102.
  • the transceiver module 6101 is used to send uplink data and/or uplink signaling to the network device and receive a response message within a response time window.
  • the processing module 6102 is used to wait for a response message sent by the network device, and the response message includes downlink data and/or downlink signaling.
  • the transceiver module is used to execute at least one of the communication steps such as sending and/or receiving (for example, step 2101, step 2104, step 3101, step 3103, step 3201, step 3203, but not limited thereto) performed by the terminal 6100 in any of the above methods
  • the processing module is used to execute at least one of the other steps (such as step 2103, step 2105, step 2106, step 3102, step 3104, step 3105, step 3203, but not limited thereto), which will not be described in detail here.
  • FIG. 6B is a schematic diagram of the structure of a network device 6200 provided according to an embodiment of the present disclosure.
  • network device 6200 may include a transceiver module 6201 and a processing module 6202.
  • transceiver module 6201 is configured to receive uplink data and/or uplink signaling sent by a terminal;
  • processing module 6202 is configured to determine a response time window, which is a time window during which the terminal waits to receive a response message from the network device, the response message including downlink data and/or downlink signaling; and the transceiver module is further configured to send a response message to the terminal within the response time window.
  • the transceiver module is configured to execute at least one of the communication steps (e.g., steps 2101, 2104, 4101, 4103, 4201, and 4203, but not limited thereto) performed by the network device 6200 in any of the above methods, which are not described in detail here.
  • the processing module is configured to execute at least some of the other steps (e.g., steps 2102, 4102, and 4202, but not limited thereto), which are not described in detail here.
  • the transceiver module may include a transmitting module and/or a receiving module, and the transmitting module and the receiving module may be separate or integrated.
  • the transceiver module may be interchangeable with the transceiver.
  • FIG. 7A is a schematic diagram of the structure of a communication device 7100 provided according to an embodiment of the present disclosure.
  • Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user device, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods.
  • Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.
  • the communication device 7100 includes one or more processors 7101.
  • the processor 7101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit.
  • the baseband processor can be used to process the communication protocol and communication data
  • the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data.
  • the communication device 7100 is used to perform any of the above methods.
  • one or more processors 7101 are used to call instructions to enable the communication device 7100 to perform any of the above methods.
  • the communication device 7100 further includes one or more transceivers 7102.
  • the transceiver 7102 performs at least one of the communication steps (e.g., steps 2101, 2104, 3101, 3103, 3201, 3203, 4101, 4103, 4201, 4203, 5101, and 5103) of the above method
  • the processor 7101 performs at least one of the other steps (e.g., steps 2102, 2103, 2105, 2106, 3102, 3104, 3105, 4102, 4202, and 5102, but not limited thereto).
  • the transceiver may include a receiver and/or a transmitter, and the receiver and transmitter may be separate or integrated.
  • terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.
  • the communication device 7100 further includes one or more memories 7103 for storing data. Alternatively, all or part of the memories 7103 may be located outside the communication device 7100.
  • the communication device 7100 may include one or more interface circuits 7104.
  • the interface circuits 7104 are connected to the memory 7102 and may be configured to receive data from the memory 7102 or other devices, or to send data to the memory 7102 or other devices. For example, the interface circuits 7104 may read data stored in the memory 7102 and send the data to the processor 7101.
  • processor 8101 may store a computer program 7105.
  • the computer program 7105 when executed on processor 7101, enables communication device 7000 to perform the methods described in the above method embodiments.
  • the computer program 7105 may be embedded in processor 7101, in which case processor 7101 may be implemented by hardware.
  • the communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7A.
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
  • FIG. 7B is a schematic diagram of the structure of a chip 7200 proposed in an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present disclosure is not limited thereto.
  • the chip 7200 includes one or more processors 7201.
  • the chip 7200 is configured to execute any of the above methods.
  • chip 7200 further includes one or more interface circuits 7202. Alternatively, terms such as interface circuit, interface, and transceiver pins may be used interchangeably.
  • chip 7200 further includes one or more memories 7203 for storing data. Alternatively, all or part of memory 7203 may be located external to chip 7200.
  • interface circuit 7202 is connected to memory 7203 and may be used to receive data from memory 7203 or other devices, or may be used to send data to memory 7203 or other devices. For example, interface circuit 7202 may read data stored in memory 7203 and send the data to processor 7201.
  • the interface circuit 7202 performs at least one of the communication steps (e.g., steps 2101, 2104, 3101, 3103, 3201, 3203, 4101, 4103, 4201, 4203, 5101, and 5103) in the above-described method.
  • the interface circuit 7202 performing the communication steps e.g., steps 2101, 2104, 3101, 3103, 3201, 3203, 4101, 4103, 4201, 4203, 5101, and 5103) in the above-described method, for example, means that the interface circuit 7202 performs data exchange between the processor 7201, the chip 7200, the memory 7203, or the transceiver device.
  • the processor 7201 performs at least one of the other steps (e.g., steps 2102, 2103, 2105, 2106, 3102, 3104, 3105, 4102, 4202, and 5102, but not limited thereto).
  • modules and/or devices described in various embodiments can be arbitrarily combined or separated according to circumstances.
  • some or all steps can also be performed collaboratively by multiple modules and/or devices, which is not limited here.
  • the present disclosure also proposes a storage medium having instructions stored thereon.
  • the storage medium is an electronic storage medium.
  • the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices.
  • the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.
  • the present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods.
  • the program product is a computer program product.
  • the present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Landscapes

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

Abstract

本公开涉及一种通信方法及设备、通信系统、通信设备、存储介质，属于通信技术领域。该方法包括：终端向网络设备发送上行数据和/或上行信令；启动响应时间窗，响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；在响应时间窗内接收响应消息。通过终端向网络设备发送上行数据和/或上行信令后，启动响应窗口，在响应窗口中等待接收响应消息，实现终端与网络设备之间发送数据或信令的目的。

Description

一种通信方法及设备、通信系统、通信设备、存储介质 技术领域
本公开涉及通信技术领域，尤其涉及一种通信方法及设备、通信系统、通信设备、存储介质。
背景技术
在随机接入过程中，终端发起的早期数据传输(Mobile Originated Early Data Transmission，MO-EDT)允许终端在单个上行链路数据包和单个上行链路随后单个下行链路数据包情况下发送用户数据。
发明内容
本公开实施例提出了一种通信方法及设备、通信系统、通信设备、存储介质，可用于通信技术领域中，用于解决EDT流程中系统容量的瓶颈问题。
根据本公开实施例的第一方面，提出了一种通信方法，由终端执行，包括：向网络设备发送上行数据和/或上行信令；启动响应时间窗，响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；在响应时间窗内接收响应消息。
根据本公开实施例的第二方面，提出了一种通信方法，该方法由网络设备执行，包括：接收终端发送的上行数据和/或上行信令；确定响应时间窗，响应时间窗用于终端等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；在响应时间窗内，向终端发送响应消息。
根据本公开实施例的第三方面，提出了一种终端，包括收发模块和处理模块，收发模块，用于向网络设备发送上行数据和/或上行信令；处理模块，用于启动响应时间窗，响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；收发模块还用于在响应时间窗内接收响应消息。
根据本公开实施例的第四方面，提出了一种网络设备，包括收发模块和处理模块，收发模块，用于接收终端发送的上行数据和/或上行信令；处理模块，用于确定响应时间窗，响应时间窗用于终端等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；收发模块还用于在响应时间窗内，向终端发送响应消息。
根据本公开实施例的第五方面，提出了一种通信设备，包括一个或多个处理器；其中，一个或多个处理器用于调用指令以使得通信设备执行第一方面和第二方面中任一项所描述的方法。
根据本公开实施例的第六方面，提出了一种通信系统，包括终端和网络设备，其中，终端被配置为实现第一方面的通信方法，网络设备被配置为实现第二方面的通信方法。
根据本公开实施例的第七方面，提出了一种存储介质，存储介质存储有指令，当指令在通信设备上运行时，使得通信设备执行第一方面和第二方面中任一项所述的方法。
根据本公开提出的通信方法，终端向网络设备发送上行数据和/或上行信令；启动响应时间窗，响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；在响应时间窗内接收响应消息。通过终端向网络设备发送上行数据和/或上行信令后，启动响应窗口，在响应窗口中等待接收响应消息，实现终端与网络设备之间发送数据或信令的目的。
附图说明
为了更清楚地说明本公开实施例中的技术方案，以下对实施例描述所需的附图进行介绍，以下附图仅仅是本公开的一些实施例，不对本公开的保护范围造成具体限制。
图1是根据本公开实施例提供的通信系统的架构示意图；
图2是根据本公开实施例提供的通信方法的交互示意图；
图3A根据本公开实施例提供的终端的通信方法流程示意图；
图3B根据本公开实施例提供的终端的通信方法流程示意图；
图4A根据本公开实施例提供的网络设备的通信方法流程示意图；
图4B根据本公开实施例提供的网络设备的通信方法流程示意图；
图5是根据本公开实施例提供的通信方法的交互示意图；
图6A是根据本公开实施例提供的终端的结构示意图；
图6B是根据本公开实施例提供的网络设备的结构示意图；
图7A是根据本公开实施例提供的通信设备的结构示意图；
图7B是根据本公开实施例提出的芯片的结构示意图。
具体实施方式
本公开实施例提出了一种通信方法及设备、通信系统、通信设备、存储介质。
第一方面，本公开实施例提供一种通信方法，该方法由终端执行，包括：向网络设备发送上行数据和/或上行信令；启动响应时间窗，响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；在响应时间窗内接收响应消息。
在上述实施例中，终端通过向网络设备发送上行消息，并在响应时间窗内等待接收网络设备的响应消息，实现终端与网络设备之间通信的目的。
结合第一方面的一些实施例，在一些实施例中，上行信令包括以下至少一项：用于第一早期数据传输EDT过程的消息1Msg1和/或消息3Msg3，第一EDT过程为随机接入信道RACH EDT过程，第一EDT过程包括Msg1、Msg2、Msg3、Msg4；用于第二EDT过程的Msg3，第二EDT过程为Msg1-less EDT过程，第二EDT过程包括Msg3、Msg4；下行信令包括一下至少一项：用于第一早期数据传输EDT过程的消息2Msg2和/或消息4Msg4；用于第二EDT过程的Msg4。
结合第一方面的一些实施例，在一些实施例中，向网络设备发送上行数据和/或上行信令包括：基于控制面发送上行信令，上行信令中携带上行数据。
结合第一方面的一些实施例，在一些实施例中，向网络设备发送上行数据和/或上行信令包括：以复用的方式，基于用户面发送上行数据并基于控制面发送上行信令。
在上述实施例中，终端发送上行数据和/或上行信令可以是不同方式，可以是控制面发送信令，或者，以复用的方式，结合控制面和用户面实现数据和/或信令的发送。
结合第一方面的一些实施例，在一些实施例中，启动响应时间窗包括在结束发送上行数据和/或上行信令的子帧之后等待第一时长，启动响应时间窗。
在上述实施例中，通过在结束发送数据或信令的子帧之后等待第一时长再启动响应时间窗，可以给终端一定的反应。
结合第一方面的一些实施例，在一些实施例中，第一时长包括以下至少一项：终端与网络设备之间的往返时间RTT；时间偏移。
在上述实施例中，在不同的终端的情况下，时延可能是RTT，也可能是时间偏移，或者包括RTT和时间偏移。
结合第一方面的一些实施例，在一些实施例中，结束发送上行数据和/或上行信令的子帧包括以下至少一项：在一次物理上行共享信道PUSCH发送中重复发送多次上行数据和/或上行信令的最后一次发送的结束子帧；重传PUSCH的每次PUSCH发送中重复发送多次上行数据和/或上行信令的最后一次发送的结束子帧。
结合第一方面的一些实施例，在一些实施例中，该方法还包括：在第一条件下，停止响应时间窗。
结合第一方面的一些实施例，在一些实施例中，第一条件包括以下至少一项：终端采用竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息中包含终端的标识；终端采用竞争性资源发送上行数据和/或上行信令，终端接收响应消息的物理下行控制信道PDCCH中包括第一资源标识，第一资源标识为终端发送上行数据和/或上行信令所使用的解调参考信号DMRS资源标识和/或正交覆盖码OCC资源标识；终端采用竞争性资源发送上行数据和/或上行信令，终端接收响应消息的PDCCH由第一网络标识标识，第一网络标识为终端发送上行数据和/或上行信令所对应的无线网络临时标识RNTI；终端采用非竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息包括层1反馈L1-ACK；终端接收到的响应消息包括回退指示，回退指示用于指示终端回退至RACH EDT过程；终端接收到PDCCH，PDCCH由配置给终端的RNTI标识，且媒体访问控制协议数据单元MAC PDU成功译码。
在上述实施例中，通过设定停止响应时间窗的不同条件，实现对响应时间窗的维护，同时实现在响应时间窗内接收响应消息的目的。
结合第一方面的一些实施例，在一些实施例中，该方法还包括：在响应时间窗超时的情况下，执行第一操作。
结合第一方面的一些实施例，在一些实施例中，第一操作包括以下至少一项：由第二EDT过程回退至第一EDT过程；尝试执行第二EDT过程的次数小于或等于预设阈值时，重新尝试执行第二EDT过程，否则回退至第一EDT过程；终止第二EDT过程。
结合第一方面的一些实施例，在一些实施例中，响应时间窗的长度由协议预定义或由网络设备配置。
第二方面，本公开实施例提供一种通信方法，该方法由网络设备执行，包括：接收终端发送的上行数据和/或上行信令；确定响应时间窗，响应时间窗用于终端等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；在响应时间窗内，向终端发送响应消息。
在上述实施例中，网络设备在接收到终端发送的数据和/或信令后，可以确定响应时间窗，用于在响应时间窗内向终端发送响应消息，实现在响应时间窗内与终端进行通信的目的。
结合第二方面的一些实施例，在一些实施例中，上行信令包括以下至少一项：用于第一早期数据传输EDT过程的消息1Msg1和/或消息3Msg3，第一EDT过程为随机接入信道RACH EDT过程，第一EDT过程包括Msg1、Msg2、Msg3、Msg4；用于第二EDT过程的Msg3，第二EDT过程为Msg1-less EDT过程，第二EDT过程包括Msg3、Msg4；下行信令包括一下至少一项：用于第一早期数据传输EDT过程的消息2Msg2和/或消息4Msg4；用于第二EDT过程的Msg4。
结合第二方面的一些实施例，在一些实施例中，接收终端发送的上行数据和/或上行信令包括：基于控制面接收上行信令，上行信令中携带上行数据。
结合第二方面的一些实施例，在一些实施例中，接收终端发送的上行数据和/或上行信令包括：以复用的方式，基于用户面接收上行数据并基于控制面接收上行信令。
在上述实施例中，网络设备接收终端发送的上行数据和/或上行信令可以是不同方式，可以是控制面发送的信令，或者，以复用的方式，接收控制面发送的信令和用户面发送的数据。
结合第二方面的一些实施例，在一些实施例中，响应时间窗的开始时间为：在终端结束发送上行数据和/或上行信令的子帧之后等待第一时长。
结合第二方面的一些实施例，在一些实施例中，第一时长包括以下至少一项：终端与网络设备之间的往返时间RTT；时间偏移。
结合第二方面的一些实施例，在一些实施例中，终端结束发送上行数据和/或上行信令的子帧包括以下至少一项：终端在一次物理上行共享信道PUSCH发送中重复发送多次上行数据和/或上行信令的最后一次发送的结束子帧；终端重传PUSCH的每次PUSCH发送中重复发送多次上行数据和/或上行信令的最后一次发送的结束子帧。
结合第二方面的一些实施例，在一些实施例中，响应时间窗在第一条件下停止。
结合第二方面的一些实施例，在一些实施例中，第一条件包括以下至少一项：终端采用竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息中包含终端的标识；终端采用竞争性资源发送上行数据和/或上行信令，终端接收响应消息的物理下行控制信道PDCCH中包括第一资源标识，第一资源标识为终端发送上行数据和/或上行信令所使用的解调参考信号DMRS资源标识和/或正交覆盖码OCC资源标识；终端采用竞争性资源发送上行数据和/或上行信令，终端接收响应消息的PDCCH由第一网络标识标识，第一网络标识为终端发送上行数据和/或上行信令所对应的无线网络临时标识RNTI；终端采用非竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息包括层1反馈L1-ACK；终端接收到的响应消息包括回退指示，回退指示用于指示终端回退至RACH EDT过程；终端接收到PDCCH，PDCCH由配置给终端的RNTI标识，且媒体访问控制协议数据单元MAC PDU成功译码。
结合第二方面的一些实施例，在一些实施例中，该方法还包括：在响应时间窗超时的情况下，执行第一操作。
结合第二方面的一些实施例，在一些实施例中，第一操作包括以下至少一项：由第二EDT过程回退至第一EDT过程；尝试执行第二EDT过程的次数小于或等于预设阈值时，重新尝试执行第二EDT过程，否则回退至第一EDT过程；终止第二EDT过程。
在上述实施例中，网络设备接收终端发送的上行数据和/或上行信令后，通过确定响应时间窗，在响应时间窗内向终端发送响应消息，实现终端与网络设备之间进行通信的目的。
第三方面，本公开实施例提供一种终端，包括收发模块和处理模块，收发模块，用于向网络设备发送上行数据和/或上行信令；处理模块，用于启动响应时间窗，响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；收发模块还用于在响应时间窗内接收响应消息。
第四方面，本公开实施例提供一种网络设备，包括收发模块和处理模块，收发模块，用于接收终端发送的上行数据和/或上行信令；处理模块，用于确定响应时间窗，响应时间窗用于终端等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；收发模块还用于在响应时间窗内，向终端发送响应消息。
第五方面，本公开实施例提供一种通信设备，包括：一个或多个处理器；其中，一个或多个处理器用于调用指令以使得通信设备执行第一方面和第二方面中任一项实施例描述的方法。
第六方面，本公开实施例提供一种通信系统，包括：终端和网络设备，其中，终端用于执行本公开第一方面中任一项实施例描述的方法；网络设备用于执行本公开第二方面中任一项实施例描述的方法。
结合第六方面的一些实施例，在一些实施例中，终端为以下至少一项：非地面网络NTN终端；带宽降低及低复杂性BL终端；增强覆盖型终端；窄带物联网NB-IoT终端。
第七方面，本公开实施例提供一种存储介质，存储介质存储有指令，当指令在通信设备上运行时，使得通信设备执行本公开第一方面和第二方面中任一项实施例描述的方法。
第八方面，本公开实施例提出了程序产品，上述程序产品被通信设备执行时，使得上述通信设备执行如第一方面和第二方面的可选实现方式所描述的方法。
第九方面，本公开实施例提出了计算机程序，当其在计算机上运行时，使得计算机执行如第一方面和第二方面的可选实现方式所描述的方法。
第十方面，本公开实施例提供了一种芯片或芯片系统。该芯片或芯片系统包括处理电路，被配置为执行根据上述第一方面和第二方面的可选实现方式所描述的方法。
可以理解地，上述终端、网络设备、通信系统、存储介质、程序产品、计算机程序、芯片或芯片系统均用于执行本公开实施例所提出的方法。因此，其所能达到的有益效果可以参考对应方法中的有益效果，此处不再赘述。
本公开实施例提出了一种通信方法及设备、通信系统、通信设备、存储介质。在一些实施例中，通信方法与信息处理方法等术语可以相互替换，终端、网络设备与信息处理装置、通信装置等术语可以相互替换，信息处理系统、通信系统等术语可以相互替换。
本公开实施例并非穷举，仅为部分实施例的示意，不作为对本公开保护范围的具体限制。在不矛盾的情况下，某一实施例中的每个步骤均可以作为独立实施例来实施，且各步骤之间可以任意组合，例如，在某一实施例中去除部分步骤后的方案也可以作为独立实施例来实施，且在某一实施例中各步骤的顺序可以任意交换，另外，某一实施例中的可选实现方式可以任意组合；此外，各实施例之间可以任意组合，例如，不同实施例的部分或全部步骤可以任意组合，某一实施例可以与其他实施例的可选实现方式任意组合。
在各本公开实施例中，如果没有特殊说明以及逻辑冲突，各实施例之间的术语和/或描述具有一致性，且可以互相引用，不同实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本公开实施例中所使用的术语只是为了描述特定实施例的目的，而并非作为对本公开的限制。
在本公开实施例中，除非另有说明，以单数形式表示的元素，如“一个”、“一种”、“该”、“上述”、“前述”、“这一”等，可以表示“一个且只有一个”，也可以表示“一个或多个”、“至少一个”等。例如，在翻译中使用如英语中的“a”、“an”、“the”等冠词(article)的情况下，冠词之后的名词可以理解为单数表达形式，也可以理解为复数表达形式。
在本公开实施例中，“多个”是指两个或两个以上。
在一些实施例中，“至少一者(at least one of)”、“至少一项(at least one of)”、“至少一个(at least one of)”、“一个或多个(one or more)”、“多个(a plurality of)”、“多个(multiple)等术语可以相互替换。
本公开实施例中的如“A、B、C……中的至少一者”、“A和/或B和/或C……”等描述方式，包括了A、B、C……中任意一个单独存在的情况，也包括了A、B、C……中任意多个的任意组合情况，每种情况可以单独存在；例如，“A、B、C中的至少一者”包括单独A、单独B、单独C、A和B组合、A和C组合、B和C组合、A和B和C组合的情况；例如，A和/或B包括单独A、单独B、A和B的组合的情况。
在一些实施例中，“在一情况下A，在另一情况下B”、“响应于一情况A，响应于另一情况B”等记载方式，根据情况可以包括以下技术方案：与B无关地执行A，即，在一些实施例中A；与A无关地执行B，即，在一些实施例中B；A和B被选择性执行，即，在一些实施例中从A与B中选择执行；A和B都被执行，即，在一些实施例中A和B。当有A、B、C等更多分支时也类似上述。
本公开实施例中的“第一”、“第二”等前缀词，仅仅为了区分不同的描述对象，不对描述对象的位置、顺序、优先级、数量或内容等构成限制，对描述对象的陈述参见权利要求或实施例中上下文的描述，不应因为使用前缀词而构成多余的限制。例如，描述对象为“字段”，则“第一字段”和“第二字段”中“字段”之前的序数词并不限制“字段”之间的位置或顺序，“第一”和“第二”并不限制其修饰的“字段”是否在同一个消息中，也不限制“第一字段”和“第二字段”的先后顺序。再如，描述对象为“等级”，则“第一等级”和“第二等级”中“等级”之前的序数词并不限制“等级”之间的优先级。再如，描述对象的数量并不受序数词的限制，可以是一个或者多个，以“第一装置”为例，其中“装置”的数量可以是一个或者多个。此外，不同前缀词修饰的对象可以相同或不同，例如，描述对象为“装置”，则“第一装置”和“第二装置”可以是相同的装置或者不同的装置，其类型可以相同或不同；再如，描述对象为“信息”，则“第一信息”和“第二信息”可以是相同的信息或者不同的信息，其内容可以相同或不同。
在一些实施例中，“包括A”、“包含A”、“用于指示A”、“携带A”，可以解释为直接携带A，也可以解释为间接指示A。
在一些实施例中，“时频(time/frequency)”、“时频域”等术语是指时域和/或频域。
在一些实施例中，“响应于……”、“响应于确定……”、“在……的情况下”、“在……时”、“当……时”、“若……”、“如果……”等术语可以相互替换。
在一些实施例中，“大于”、“大于或等于”、“不小于”、“多于”、“多于或等于”、“不少于”、“高于”、“高于或等于”、“不低于”、“以上”等术语可以相互替换，“小于”、“小于或等于”、“不大于”、“少于”、“少于或等于”、“不多于”、“低于”、“低于或等于”、“不高于”、“以下”等术语可以相互替换。
在一些实施例中，装置等可以解释为实体的、也可以解释为虚拟的，其名称不限定于实施例中所记载的名称，“装置”、“设备(equipment)”、“设备(device)”、“电路”、“网元”、“节点”、“功能”、“单元”、“部件(section)”、“系统”、“网络”、“芯片”、“芯片系统”、“实体”、“主体”等术语可以相互替换。
在一些实施例中，“网络”可以解释为网络中包含的装置(例如，接入网设备、核心网设备等)。
在一些实施例中，“接入网设备(access network device，AN device)”、“无线接入网设备(radio access network device，RAN device)”、“基站(base station，BS)”、“无线基站(radio base station)”、“固定台(fixed station)”、“节点(node)”、“接入点(access point)”、“发送点(transmission point，TP)”、“接收点(reception point，RP)”、“发送接收点(transmission/reception point，TRP)”、“面板(panel)”、“天线面板(antenna panel)”、“天线阵列(antenna array)”、“小区(cell)”、“宏小区(macro cell)”、“小型小区(small cell)”、“毫微微小区(femto cell)”、“微微小区(pico cell)”、“扇区(sector)”、“小区组(cell group)”、“载波(carrier)”、“分量载波(component carrier)”、“带宽部分(bandwidth part，BWP)”等术语可以相互替换。
在一些实施例中，“终端(terminal)”、“终端设备(terminal device)”、“用户设备(user equipment，UE)”、“用户终端(user terminal)”、“移动台(mobile station，MS)”、“移动终端(mobile terminal，MT)”、订户站 (subscriber station)、移动单元(mobile unit)、订户单元(subscriber unit)、无线单元(wireless unit)、远程单元(remote unit)、移动设备(mobile device)、无线设备(wireless device)、无线通信设备(wireless communication device)、远程设备(remote device)、移动订户站(mobile subscriber station)、接入终端(access terminal)、移动终端(mobile terminal)、无线终端(wireless terminal)、远程终端(remote terminal)、手持设备(handset)、用户代理(user agent)、移动客户端(mobile client)、客户端(client)等术语可以相互替换。
在一些实施例中，接入网设备、核心网设备、或网络设备可以被替换为终端。例如，针对将接入网设备、核心网设备、或网络设备以及终端间的通信置换为多个终端间的通信(例如，设备对设备(device-to-device，D2D)、车联网(vehicle-to-everything，V2X)等)的结构，也可以应用本公开的各实施例。在该情况下，也可以设为终端具有接入网设备所具有的全部或部分功能的结构。此外，“上行”、“下行”等术语也可以被替换为与终端间通信对应的术语(例如，“侧行(side)”)。例如，上行信道、下行信道等可以被替换为侧行信道，上行链路、下行链路等可以被替换为侧行链路。
在一些实施例中，终端可以被替换为接入网设备、核心网设备、或网络设备。在该情况下，也可以设为接入网设备、核心网设备、或网络设备具有终端所具有的全部或部分功能的结构。
在一些实施例中，获取数据、信息等可以遵照所在地国家的法律法规。
在一些实施例中，可以在得到用户同意后获取数据、信息等。
此外，本公开实施例的表格中的每一元素、每一行、或每一列均可以作为独立实施例来实施，任意元素、任意行、任意列的组合也可以作为独立实施例来实施。
首先对本申请中的相关词语进行简单介绍：
1、蜂窝物联网(Cellular Internet of Things，CIOT)
2、终端发起的早期数据传输(Mobile Originated Early Data Transmission，MO-EDT)
在本公开的方案中，Early Data Transmission也可以是提前数据传输，早期数据传输和提前数据传输可以相互替换使用。
3、正交覆盖码(Orthogonal Cover Code，OCC)
4、解调参考信号(Demodulation Reference Signal，DMRS)
5、无线资源控制协议(Radio Resource Control，RRC)
6、公共/通用控制信道(Common Control Channel，CCCH)
7、随机接入信道(Random Access Channel，RACH)
8、非接入层(Non-Access Stratum，NAS)
9、物理随机接入信道(Physical Random Access Channel，PRACH)
10、演进分组系统(E-UTRAN+EPC合称EPS)(Evolved Packet System，EPS)
11、移动管理实体(Mobile Managenment Entity，MME)
MME是3GPP协议LTE接入网络的关键控制节点，它负责空闲模式的UE(User Equipment)的定位，传呼过程，包括中继。它涉及到bearer激活/关闭过程，并且当一个UE初始化并且连接到时为这个UE选择一个S-GW(Serving GateWay)。通过和HSS交互认证一个用户，为一个用户分配一个临时ID。MME同时支持在法律许可的范围内，进行拦截、监听。MME为2G/3G接入网络提供了控制函数接口，通过S3接口。为漫游UEs，面向HSS同样提供了S6a接口。
12、服务网关(Serving GateWay，S-GW)
是终止于E-UTRAN接口的网关，该设备的主要功能包括：进行eNodeB间切换时，可以作为本地锚定点，并协助完成eNodeB的重排序功能；在3GPP不同接入系统间切换时，作为移动性锚点(终结在S4接口，在2G/3G系统和P-GW间实现业务路由)，同样具有重排序功能；执行合法侦听功能；进行数据包的路由和前转；在上行和下行传输层进行分组标记；空闲状态下，下行分组缓冲和发起网络触发的服务请求功能；用于运营商间的计费等。
13、增强覆盖型(Coverage Enhancement，CE)
14、窄带低复杂度终端(Bandwidthreduced Low complexityUE，BLUE)
15、无线网络临时标识符(Radio Network Temporary Identity，RNTI)
16、下行链路(Down Link，DL)
17、上行链路资源(Preconfigured Uplink(ul)Resources，PUR)
18、往返时间(Round Trip Time，RTT)
19、物理上行链路共享信道(Physical Uplink Shared Channel，PUSCH)
20、非地面网络(non-terrestrial network，NTN)
21、协议数据单元(Protocol Data Unit，PDU)：MAC层协议数据单元
在随机接入程序中，MO-EDT允许一个上行链路数据传输后跟一个下行链路数据传输。当上层请求建立或恢复无线资源控制协议(Radio Resource Control，RRC)连接，用于移动早期数据(即非信令或短信)并且上行数据大小小于或等于系统信息中指示的TB大小时，MO-EDT就被触发。使用用户平面CIOT EPS/5GS优化时，MO-EDT不用于控制平面上的数据。MO-EDT仅适用于基本物联网用户、增强覆盖范围内的物联网用户和基于蜂窝的窄带物联网用户。
使用用户平面CIOT EPS/5GS优化时的MO-EDT特征如下:上行用户数据以连接在CCCH上的UL RRC早期数据请求消息中的NAS消息传输；可选择将下行用户数据传输到连接在CCCH上的DL RRC早期数据请求消息中的NAS消息中；没有过渡到RRC连接。
现有的EDT流程基于随机接入流程，UE要发一个上行数据必须至少经历4步：发送Msg1；接收Msg2；发送Msg3；接收Msg4。其中随机接入过程包括：(1)2步随机接入过程：终端发送MsgA；网络反馈MsgB；终端将MsgB和MsgA进行匹配，判断是否竞争解决。(2)4步随机接入过程:终端发送Msg1；网络反馈Msg2；终端根据Msg2的UL grant发送Msg3；网络反馈Msg4；终端将Msg3和Msg4进行匹配，判断是否竞争解决。单PRACH传输是指UE向网络设备一次性发送一个前导码(preamble)，或言之，UE向网络设备一次性发送一个消息1(Msg1)。类似地，多PRACH传输是指UE向网络设备一次性发送多个前导码，或言之，UE向网络设备一次性发送多个Msg1。目前，通过OCC来提升上行容量，但是上行容量提升只能提升Msg1和Msg3的容量，Msg2和Msg4则会变成制约系统容量的瓶颈。
为了解决上述问题，本公开提出一种没有Msg1/Msg2的EDT方法，也即只有Msg3和Msg4，下文中将其称为Msg1-Less EDT。Msg3是在没有Msg1和Msg2的情况下直接发送Msg3，Msg4是通过高效传输来提升Msg4的容量。当UE发送了Msg1-Less EDT的Msg3后，UE需要启动接收窗口来等待接收Msg4。
因此，本公开提出了一种通信方法及设备、通信系统、通信设备、存储介质，通过终端向网络设备发送上行数据和/或上行信令；启动响应时间窗，响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；在响应时间窗内接收响应消息。通过终端向网络设备发送上行数据和/或上行信令后，启动响应窗口，在响应窗口中等待接收响应消息，实现终端向网络设备发送数据或信令的目的。
本公开所提出的方法适用于各种通信系统，包括但不限于4G、5G、5G-advance及其后续通信技术(如6G等)。
图1是根据本公开实施例示出的通信系统的架构示意图。如图1所示，通信系统100可以包括终端101、网络设备102。
在一些实施例中，终端101可以是发送上行数据和/或上行信令的设备。
在一些实施例中，终端101可以是启动响应窗口的设备。
在一些实施例中，终端101可以是接收响应消息的设备。
在一些实施例中，终端101可以是执行第一操作的设备。
在一些实施例中，终端101可以是判断第一条件的设备。
在一些实施例中，终端101可以是执行第一EDT过程的设备。
在一些实施例中，终端101可以是执行第二EDT过程的设备。
在一些实施例中，终端101可以是非地面网络NTN终端。
在一些实施例中，终端101可以是BL终端。
在一些实施例中，终端101可以是增强覆盖型终端。
在一些实施例中，终端101可以是NB-IoT终端。
在一些实施例中，终端101的名称不予限制，其例如是“上行数据的发送设备”、“上行信令的发送设备”、“响应消息的接收设备”、“执行第一操作的设备”。
在一些实施例中，网络设备102可以是接收上行数据的设备。
在一些实施例中，网络设备102可以是接收上行信令的设备。
在一些实施例中，网络设备102可以是发送响应消息的设备。
在一些实施例中，网络设备102可以是确定响应时间窗的设备。
在一些实施例中，网络设备102的名称不予限制，其例如是“上行数据的接收设备”、“响应消息的发送设备”、“上行信令的接收设备”、“响应时间窗的确定设备”等。
在一些实施例中，终端可以包括手机(mobile phone)、可穿戴设备、物联网设备、具备通信功能的汽车、智能汽车、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备中的至少一者，但不限于此。
在一些实施例中，接入网设备可以包括5G通信系统中的演进节点B(evolved NodeB，eNB)、下一代演进节点B(next generation eNB，ng-eNB)、下一代节点B(next generation NodeB，gNB)、节点B(node B，NB)、家庭节点B(home node B，HNB)、家庭演进节点B(home evolved nodeB，HeNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、基带单元(base band unit，BBU)、移动交换中心、6G通信系统中的基站、开放型基站(Open RAN)、云基站(Cloud RAN)、其他通信系统中的基站、Wi-Fi系统中的接入节点中的至少一者，但不限于此。
在一些实施例中，本公开的技术方案可适用于Open RAN架构，此时，本公开实施例所涉及的接入网设备间或者接入网设备内的接口可变为Open RAN的内部接口，这些内部接口之间的流程和信息交互可以通过软件或者程序实现。
在一些实施例中，接入网设备可以由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将接入网设备的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU，但不限于此。
在一些实施例中，核心网设备可以是一个设备，包括一个或多个网元，也可以是多个设备或设备群，分别包括上述一个或多个网元中的全部或部分。网元可以是虚拟的，也可以是实体的。核心网例如包括演进分组核心(Evolved Packet Core，EPC)、5G核心网络(5G Core Network，5GCN)、下一代核心(Next Generation Core，NGC)中的至少一者。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提出的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提出的技术方案对于类似的技术问题同样适用。
下述本公开实施例可以应用于图1所示的通信系统100、或部分主体，但不限于此。图1所示的各主体是例示，通信系统可以包括图1中的全部或部分主体，也可以包括图1以外的其他主体，各主体数量和形态为任意，各主体之间的连接关系是例示，各主体之间可以不连接也可以连接，其连接可以是任意方式，可以是直接连接也可以是间接连接，可以是有线连接也可以是无线连接。
本公开各实施例可以应用于长期演进(Long Term Evolution，LTE)、LTE-Advanced(LTE-A)、LTE-Beyond(LTE-B)、SUPER 3G、IMT-Advanced、第四代移动通信系统(4th generation mobile communication system，4G)、第五代移动通信系统(5th generation mobile communication system，5G)、5G新空口(new radio，NR)、未来无线接入(Future Radio Access，FRA)、新无线接入技术(New-Radio Access Technology，RAT)、新无线(New Radio，NR)、新无线接入(New radio access，NX)、未来一代无线接入(Future generation radio access， FX)、Global System for Mobile communications(GSM(注册商标))、CDMA2000、超移动宽带(Ultra Mobile Broadband，UMB)、IEEE 802.11(Wi-Fi(注册商标))、IEEE 802.16(WiMAX(注册商标))、IEEE 802.20、超宽带(Ultra-WideBand，UWB)、蓝牙(Bluetooth(注册商标))、陆上公用移动通信网(Public Land Mobile Network，PLMN)网络、设备到设备(Device-to-Device，D2D)系统、机器到机器(Machine to Machine，M2M)系统、物联网(Internet of Things，IoT)系统、车联网(Vehicle-to-Everything，V2X)、利用其他用户面路径建立方法的系统、基于它们而扩展的下一代系统等。此外，也可以将多个系统组合(例如，LTE或者LTE-A与5G的组合等)应用。
图2为本公开实施例所提供的一种通信方法的交互示意图。如图2所示，本公开实施例涉及一种通信方法，该方法可以由通信系统执行，例如由图1所示的通信系统100执行。通信系统中包括终端、网络设备。该交互方法可以包括以下步骤：
步骤2101，终端向网络设备发送上行数据和/或上行信令。
在一些实施例中，上行信令包括以下至少一项：用于第一早期数据传输EDT过程的消息1Msg1和/或消息3Msg3第一EDT过程为随机接入信道RACH EDT过程，第一EDT过程包括Msg1、Msg2、Msg3、Msg4；用于第二EDT过程的Msg3，第二EDT过程为Msg1-less EDT过程，第二EDT过程包括Msg3、Msg4。
在一些实施例中，第一早期数据传输和第一提前数据传输可以相互替换使用。
在一些实施例中，终端向网络设备发送上行数据和/或上行信令可以是基于RACHEDT，也可以是Msg1-lessEDT。其中RACHEDT过程中的上行信令可以是Msg1或Msg3，Msg1-less EDT过程中的上行信令可以是Msg3。
在一些实施例中，终端发送上行信令的资源可以是竞争性资源，也可以是非竞争性资源。
示例地，用于Msg1-Less EDT的Msg3发送的资源可以为竞争性资源，也可以为非竞争性资源。对非竞争性资源，可以为包含一个UE特定的OCC资源配置的PUR资源。对竞争性资源，UE没有被配置唯一的OCC/DMRS资源，UE在使用竞争性资源时，需要自己从OCC/DMRS资源池中选择一个OCC/DMRS资源。竞争性资源可以通过系统消息或专用信令发送给UE，非竞争性资源通过专用信令发送给UE。在一些实施例中，终端向网络设备发送上行数据和/或上行信令可以是基于控制面发送上行信令，上行信令中携带上行数据。
在一些实施例中，终端向网络设备发送上行数据和/或上行信令可以是以复用的方式，基于用户面发送上行数据并基于控制面板发送上行信令。
在一些实施例中，终端向网络设备发送上行数据和/或上行信令可以是基于以上两种方式。
示例地，Msg1-Less EDT的Msg3包括以下一种或多种：基于控制面CIOT EPS/5GS的UL RRC早期数据请求信息；用户面CIOT EPS/5GS的上行用户数据传输和在控制面CCCH上的UL RRC连接恢复请求消息的复用方式发送。
在一些实施例中，终端向网络设备发送上行数据和/或上行信令也包括向网络设备请求配置响应时间窗。
步骤2102，网络设备确定响应时间窗。
在一些实施例中，确定响应时间窗可以是网络设备确定响应时间窗的长度、开始节点和/或终止节点。
在一些实施例中，网络设备确定响应时间窗可以是网络设备确定响应时间窗的长度，并向终端配置响应时间窗的长度。
在一些实施例中，网络设备确定响应时间窗用于网络设备在响应时间窗内向终端发送响应消息。
步骤2103，终端启动响应时间窗。
在一些实施例中，终端启动响应时间窗可以是确定响应时间窗的长度、开始节点和/或终止节点。
在一些实施例中，响应时间窗的长度由网络设备配置。
在一些实施例中，终端确定响应时间窗可以是基于协议预定义的长度配置响应时间窗的长度。
示例地，响应时间窗的长度由网络配置，或者响应时间窗的长度可以由CE等级配置。
在一些实施例中，终端确定响应时间窗用于终端在响应时间窗内接收网络设备发送的响应消息。
在一些实施例中，启动响应时间窗可以是用于终端在响应时间窗内接收响应消息。换言之，如果不启动响应时间窗，终端无法接收网络设备发送的响应消息。
在一些实施例中，启动响应时间窗可以是在结束发送上行数据和/或上行信令的子帧之后等待第一时长，启动响应时间窗。
在一些实施例中，结束发送上行数据和/或上行信令的子帧可以是在一次物理上行共享信道PUSCH发送中重复发送多次上行数据和/或上行信令的最后一次发送的结束子帧。
在一些实施例中，终端可以向网络设备发送一次PUSCH，在一次PUSCH中重复发送多次上行数据和/或上行信令，每次重复发送可以称为一次重复(repetition)，结束发送上行数据和/或上行信令的子帧可以是最后一次重复的结束子帧，即最后一次重复的结束位置。
在一些实施例中，第一时长可以是终端与网络设备之间的往返时间RTT。
在一些实施例中，RTT的大小可以是由NTN网络传播时延决定的，网络传播时延可以包括从终端到卫星的传播时延和从卫星到基站的传播时延。
示例地，终端响应时间窗口的启动时间为PUSCH传输结束位置的子帧之后等待一个RTT的时长，PUSCH传输结束位置为PUSCH最后一个重复发送的Msg3的结束位置，该终端为NTN终端。
在一些实施例中，第一时长可以是时间偏移。
在一些实施例中，时间偏移可以是终端在判断是否开启响应时间窗的处理时延或是为了保证能够正常接收资源，增加的一段子帧的时长，时间偏移可以是多个子帧。
示例地，时间偏移可以是0、1、2、3、4个子帧。
示例地，终端响应时间窗口的启动时间为PUSCH传输结束位置的子帧之后等待一个时间偏移的时长，PUSCH传输结束位置为PUSCH最后一个重复发送的Msg3的结束位置，该终端为NB-IoT终端或BL终端或CE终端。
在一些实施例中，第一时长可以是终端与网络设备之间的RTT和时间偏移。
示例地，终端响应时间窗口的启动时间为PUSCH传输结束位置的子帧之后等待一个RTT加时间偏移的时长，PUSCH传输结束位置为PUSCH最后一个重复发送的Msg3的结束位置，该终端为NTN终端。
在一些实施例中，结束发送上行数据和/或上行信令的子帧可以是重传PUSCH的每次PUSCH发送中重复发送多次上行数据和/或上行信令的最后一次发送的结束子帧。
在一些实施例中，终端可以向网络设备重复发送一次或多次PUSCH，在每次发送的PUSCH中重复发送多次上行数据和/或上行信令，每次重复发送上行数据和/或上行信令可以称为一次重复(repetition)，结束发送上行数据和/或上行信令的子帧可以是最后一次重复的结束子帧，即最后一次重复的位置。
在一些实施例中，第一时长可以是终端与网络设备之间的往返时间RTT。
示例地，终端可以重新启动响应时间窗口，重新启动响应时间窗口的时间为重传结束位置的子帧之后等待一个RTT的时长，重传结束位置的子帧为重传PUSCH最后一个重复发送Msg3的结束位置。该终端为NTN终端。
在一些实施例中，第一时长可以是时间偏移。
示例地，终端可以重新启动响应时间窗口，重新启动响应时间窗口的时间为重传结束位置的子帧之后等待一个时间偏移的时长，重传结束位置的子帧为重传PUSCH最后一个重复发送Msg3的结束位置。该终端为NB-IoT终端或BL终端或CE终端。
在一些实施例中，第一时长可以是终端与网络设备之间的往返时间RTT和时间偏移。
示例地，终端可以重新启动响应时间窗口，重新启动响应时间窗口的时间为重传结束位置的子帧之后等待一个RTT加时间偏移的时长，重传结束位置的子帧为重传PUSCH最后一个重复发送Msg3的结束位置。该终端为NTN终端。
在上述实施例中，终端启动响应时间窗，用于接收网络设备发送的响应消息。
步骤2104，网络设备向终端发送响应消息。
在一些实施例中，网络设备向终端发送响应消息可以是通过下行信令向终端发送Msg。
在一些实施例中，网络设备发送响应消息是基于终端发送的上行数据和/或上行信令发送的。
在一些实施例中，下行信令包括以下至少一项：用于第一早期数据传输EDT过程的消息2Msg2和/或消息4Msg4；用于第二EDT过程的Msg4。
示例地，在RACHEDT过程中，终端向网络设备发送Msg1，网络设备接收到Msg1后，在响应时间窗内向终端发送Msg2。
示例地，在RACHEDT过程中，终端向网络设备发送Msg3，网络设备接收到Msg3后，在响应时间窗内向终端发送Msg4。
示例地，在Msg1-Less EDT过程中，终端向网络设备发送Msg3，网络设备接收到Msg3后，在响应时间窗内向终端发送Msg4。
在一些实施例中，网络设备在响应时间窗内，向终端发送响应消息。
示例地，网络设备在响应时间窗内向终端发送Msg4。
示例地，网络设备在响应时间窗内向终端发送包含终端标识的响应消息Msg4。
示例地，网络设备在响应时间窗内向终端发送Msg4，其中Msg4的PDCCH中包括终端发送Msg3时所使用的DMRS资源ID和/或OCC资源ID。
示例地，网络设备在响应时间窗内向终端发送Msg4，其中，Msg4的PDCCH通过终端发送Msg3所对应的RNTI来标识。
示例地，网络设备在响应时间窗内向终端发送包含L1-ACK的Msg4。
示例地，网络设备在响应时间窗内向终端发送包含Fallback指示的Msg4。
示例地，网络设备在响应时间窗内向终端发送的Msg4，且Msg4的PDCCH通过配置给该终端的RNTI标识。
步骤2105，终端停止响应时间窗。
在一些实施例中，终端在第一条件下，停止响应时间窗。
在一些实施例中，终端停止响应时间窗后，不再向网络设备发送上行数据和/或上行信令，相应地，也不再接收网络设备发送的响应消息。
在一些实施例中，第一条件可以是终端采用竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息中包含终端的标识。换言之，终端接收到包含其自身标识的消息，表示当前的响应消息是发给这个终端的，那么终端不需要再等待响应消息，则停止响应时间窗。
示例地，终端采用竞争性资源发送Msg1-Less EDT过程的Msg3，当终端接收到包含终端标识的响应消息Msg4，则终端停止响应窗口。
示例地，终端采用竞争性资源发送RACHEDT过程的Msg1或Msg3，当终端接收到包含终端标识的响应消息Msg2或Msg4，则终端停止响应窗口。
在一些实施例中，第一条件可以是终端采用竞争性资源发送上行数据和/或上行信令，终端接收响应消息的物理下行控制信道PDCCH中包括第一资源标识，第一资源标识为终端发送上行数据和/或上行信令所使用的解调参考信号DMRS资源标识和/或正交覆盖码OCC资源标识。
示例地，终端采用竞争性资源发送Msg1-Less EDT过程的Msg3，终端接收Msg4的PDCCH中包括终端发送Msg3时所使用的DMRS资源ID和/或OCC资源ID，终端停止响应窗口。
示例地，终端采用竞争性资源发送RACH EDT过程的Msg1或Msg3，终端接收Msg2或Msg4的PDCCH中包括终端发送Msg1或Msg3时所使用的DMRS资源ID和/或OCC资源ID，终端停止响应窗口。
在一些实施例中，第一条件可以是终端采用竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息中包含终端的标识，且响应消息的物理下行控制信道PDCCH中包括第一资源标识，第一资源标识为终端发送上行数据和/或上行信令所使用的解调参考信号DMRS资源标识和/或正交覆盖码OCC资源标识。
示例地，终端采用竞争性资源发送RACH EDT过程的Msg1或Msg3，终端接收Msg2或Msg4的PDCCH中包括终端的标识和终端发送Msg1或Msg3时所使用的DMRS资源ID和/或OCC资源ID，终端停止响应窗口。
示例地，终端采用竞争性资源发送Msg1-Less EDT过程的Msg3，终端接收Msg4中包含终端的标识，且Msg4的PDCCH中包括终端发送Msg3时所使用的DMRS资源ID和/或OCC资源ID，终端停止响应窗口。
在一些实施例中，第一条件可以是终端采用竞争性资源发送上行数据和/或上行信令，终端接收响应消息的PDCCH由第一网络标识标识，第一网络标识为终端发送上行数据和/或上行信令所对应的无线网络临时标识RNTI。
示例地，终端采用竞争性资源发送Msg1-Less EDT过程的Msg3，UE接收Msg4的PDCCH通过终端发送Msg3所对应的RNTI来标识，终端停止响应窗口。
示例地，终端采用竞争性资源发送RACH EDT过程的Msg1或Msg3，UE接收Msg2或Msg4的PDCCH通过终端发送Msg1或Msg3所对应的RNTI来标识，终端停止响应窗口。
在一些实施例中，第一条件可以是终端采用竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息中包含终端的标识，且响应消息的PDCCH由第一网络标识标识，第一网络标识为终端发送上行数据和/或上行信令所对应的无线网络临时标识RNTI。
示例地，终端采用竞争性资源发送Msg1-Less EDT过程的Msg3，UE接收Msg4中包含终端的标识，且Msg4的PDCCH通过终端发送Msg3所对应的RNTI来标识，终端停止响应窗口。
示例地，终端采用竞争性资源发送RACH EDT过程的Msg1或Msg3，UE接收Msg2或Msg4中包含终端的标识，且Msg2或Msg4的PDCCH通过终端发送Msg1或Msg3所对应的RNTI来标识，终端停止响应窗口。
在一些实施例中，第一条件可以是终端采用竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息中包含终端的标识，且响应消息的物理下行控制信道PDCCH中包括第一资源标识，第一资源标识为终端发送上行数据和/或上行信令所使用的解调参考信号DMRS资源标识和/或正交覆盖码OCC资源标识。，响应消息的PDCCH由第一网络标识标识，第一网络标识为终端发送上行数据和/或上行信令所对应的无线网络临时标识RNTI。
示例地，终端采用竞争性资源发送Msg1-Less EDT过程的Msg3，UE接收Msg4中包含终端的标识，且Msg4的PDCCH中包括终端的标识和终端发送Msg1或Msg3时所使用的DMRS资源ID和/或OCC资源ID，PDCCH通过终端发送Msg3所对应的RNTI来标识，终端停止响应窗口。
示例地，终端采用竞争性资源发送RACH EDT过程的Msg1或Msg3，UE接收Msg2或Msg4中包含终端的标识，且Msg2或Msg4的PDCCH中包括终端的标识和终端发送Msg1或Msg3时所使用的DMRS资源ID和/或OCC资源ID，PDCCH通过终端发送Msg1或Msg3所对应的RNTI来标识，终端停止响应窗口。
在一些实施例中，第一条件可以是终端采用非竞争性资源发送上行数据和/或上行信令，终端接收到的响应消息包括层1反馈L1-ACK。
示例地，终端采用非竞争性资源发送Msg1-Less EDT过程的Msg3，如果终端接收到包含L1-ACK的Msg4，UE停止响应窗口。
示例地，终端采用非竞争性资源发送RACH EDT过程的Msg1或Msg3，如果终端接收到包含L1-ACK的Msg2或Msg4，UE停止响应窗口。
在一些实施例中，第一条件可以是终端接收到的响应消息包括回退指示，回退指示用于指示终端回退至RACH EDT过程。
示例地，终端采用竞争性资源或非竞争性资源发送Msg1-Less EDT过程的Msg3，如果终端接收到包含Fallback指示的Msg4，UE停止响应窗口。
示例地，终端采用竞争性资源或非竞争性资源发送RACH EDT过程的Msg1或Msg3，如果终端接收到包含Fallback指示的Msg2或Msg4，UE停止响应窗口。
在一些实施例中，第一条件可以是终端接收到PDCCH，PDCCH由配置给终端的RNTI标识，且媒体访问控制协议数据单元MAC PDU成功译码。
在一些实施例中，第一条件可以是终端接收到通过配置给终端的RNTI标识的PDCCH，且媒体访问控制协议数据单元MAC PDU成功译码。
示例地，终端采用竞争性资源或非竞争性资源发送Msg1-Less EDT过程的Msg3，如果终端接收到通过配置给该终端的RNTI标识的PDCCH，且MAC PDU成功译码，终端停止响应窗口。
示例地，终端采用竞争性资源或非竞争性资源发送RACH EDT过程的Msg1或Msg3，如果终端接收到通过配置给该终端的RNTI标识的PDCCH，且MAC PDU成功译码，终端停止响应窗口。
在上述实施例中，终端停止响应时间窗的第一条件可以是以上几种实施例的一种或多种的组合，对此本公开不予限制。
在上述实施例中，终端基于接收到的响应消息判断是否结束响应时间窗。
上述实施例中，通过设置终端结束响应时间窗的不同条件，达到控制终端接收窗口的目的。
步骤2106，终端执行第一操作。
在一些实施例中，终端在响应时间窗超时的情况下，执行第一操作。
在一些实施例中，第一操作可以是由第二EDT过程回退至第一EDT过程。
示例地，终端在响应时间窗超时的情况下，由Msg1-Less EDT过程回退到基于RACH的EDT过程。
在一些实施例中，第一操作可以是尝试执行第二EDT过程的次数小于或等于预设阈值时，重新尝试执行第二EDT过程，否则回退至第一EDT过程。
在一些实施例中，预设阈值可以是网络设备配置的阈值。
示例地，终端在响应时间窗超时的情况下，尝试Msg1-Less EDT的次数小于或小于等于门限值，重新尝试Msg1-Less EDT。否则，回退到基于RACH的EDT或终止Msg1-Less EDT。
在一些实施例中，第一操作可以是终止第二EDT过程。
示例地，终端在响应时间窗超时的情况下，终端终止Msg1-Less EDT。
示例地，终端在响应时间窗超时的情况下，尝试Msg1-Less EDT的次数小于或小于等于门限值，重新尝试Msg1-Less EDT。否则，终止Msg1-Less EDT。
在上述实施例中，终端基于响应时间窗超时，可以是执行以上任一种第一操作，继续进行步骤2101的上行数据和/或上行信令的发送，或回退到基于RACH的EDT过程，或终止EDT过程。。
本公开实施例所涉及的通信方法可以包括步骤2101～2106中的至少一者。例如，步骤2101可以作为独立实施例来试试，步骤2102可以作为独立实施例来实施，以此类推，但不限于此。步骤2101+2102、步骤2101+2102+2103、步骤2101+2102+2103+2104、步骤2101+2102+2103+2104+2105、步骤2101+2102+2103+2105、步骤2101+2102+2103+2105+2106、步骤2101+2102+2103+2104+2105+2106可以作为独立实施例来实施，但不限于此。
在一些实施例中，步骤2104、步骤2106是可选的，在不同实施例中可以对这些步骤中的全部或部分进行省略或替代。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
图3A是根据本公开实施例提供的终端的通信方法的流程示意图。本公开实施例涉及通信方法，上述方法包括：
步骤3101，向网络设备发送上行数据和/或上行信令。
步骤3101的可选实现方式可以参见图2的步骤2101的可选实现方式、及图2所涉及的实施例中其它关联部分，此处不再赘述。
步骤3102，启动响应时间窗。
步骤3102可选实现方式可以参见图2的步骤2103的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤3103，接收网络设备发送的响应消息。
步骤3103可选实现方式可以参见图2的步骤2104的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤3104，停止响应时间窗。
步骤3104可选实现方式可以参见图2的步骤2105的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤3105，执行第一操作。
步骤3105可选实现方式可以参见图2的步骤2106的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
本公开实施例所涉及的通信方法可以包括步骤3101～步骤3105中的至少一者。例如，步骤3101可以作为独立实施例来实施，步骤3102可以作为独立实施例来实施。以此类推，但不限于此。步骤3101+3102、步骤3101+3102+3103、步骤3101+3102+3103+3104、步骤3101+3102+3104+3105、步骤3101+3102+3103+3104+3105可以作为独立实施例来实施，但不限于此。
图3B是根据本公开实施例提供的终端的通信方法的流程示意图。本公开实施例涉及通信方法，上述方法包括：
步骤3201，向网络设备发送上行数据和/或上行信令。
步骤3201的可选实现方式可以参见图2的步骤2101、图3A的步骤3101的可选实现方式、及图2、图3A所涉及的实施例中其他关联部分，此处不再赘述。
步骤3202，启动响应时间窗。响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令。
步骤3202的可选实现方式可以参见图2的步骤2103、图3A的步骤3102的可选实现方式、及图2、图3A所涉及的实施例中其他关联部分，此处不再赘述。
步骤3203，在响应时间窗内接收响应消息。
步骤3203的可选实现方式可以参见图2的步骤2104、图3A的步骤3103的可选实现方式、及图2、图3A所涉及的实施例中其他关联部分，此处不再赘述。
在本公开的实施例中，步骤3201可以与图3A中的步骤3102组合，步骤3203可以与图3A中的步骤3104组合。
图4A是根据本公开实施例提供的网络设备的通信方法的流程示意图。本公开实施例涉及通信方法，上述方法包括：
步骤4101，接收终端发送的上行数据和/或上行信令。
步骤4101的可选实现方式可以参见图2的步骤2101、图3A的步骤3101、图3B的步骤3201的可选实现方式、及图2、图3A、图3B所涉及的实施例中其他关联部分，此处不再赘述。
步骤4102，确定响应时间窗。
步骤4102的可选实现方式可以参见图2的步骤2102的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
步骤4103，向终端发送响应消息。
步骤4103的可选实现方式可以参见图2的步骤2104的可选实现方式、及图2所涉及的实施例中其他关联部分，此处不再赘述。
本公开实施例所涉及的通信法可以包括步骤4101～4103中的至少一者。例如，步骤4101可以作为独立实施例来实施，步骤4102可以作为独立实施例来实施。以此类推，但不限于此。步骤4101+4103、步骤4101+4102+4103可以作为独立实施例来实施，但不限于此。
图4B是根据本公开实施例提供的网络设备的通信方法的流程示意图。本公开实施例涉及通信方法，上述方法包括：
步骤4201，接收终端发送的上行数据和/或上行信令。
步骤4201的可选实现方式可以参见图2的步骤2101、图3A的步骤3101、图3B的步骤3201、图4A的步骤4101的可选实现方式、及图2、图3A、图3B、图4A所涉及的实施例中其他关联部分，此处不再赘述。
步骤4202，确定响应时间窗。
响应时间窗用于终端等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令。
步骤4202的可选实现方式可以参见图2的步骤2102、图4A的步骤4102的可选实现方式、及图2、图4A所涉及的实施例中其他关联部分，此处不再赘述。
步骤4203，在响应时间窗内，向终端发送响应消息。
步骤4203的可选实现方式可以参见图2的步骤2104、图4A的步骤4103的可选实现方式、及图2、图4A所涉及的实施例中其他关联部分，此处不再赘述。
在本公开的实施例中，步骤4201可以与图4A中的步骤4102组合。
图5是根据本公开实施例提供的通信方法的交互示意图。如图5所示，本公开实施例涉及通信方法，上述方法包括：
步骤5101，终端向网络设备发送上行数据和/或上行信令。
步骤5101的可选实现方式可以参见图2的步骤2101、图3A的步骤3101、图3B的步骤3201、图4A的步骤4101、图4B的步骤4201的可选实现方式，及图2、图3A、图3B、图4A、图4B所涉及的实施例中其他关联部分，此处不再赘述。
步骤5102，启动响应时间窗。
响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；
步骤5102的可选实现方式可以参见图2的步骤2103、图3A的步骤3103、图3B的步骤3202的可选实现方式，及图2、图3A、图3B所涉及的实施例中其他关联部分，此处不再赘述。
步骤5103，在响应时间窗内接收响应消息。
步骤5103的可选实现方式可以参见图2的步骤2104、图3A的步骤3103、图3B的步骤3203、图4A的步骤4103、图4B的步骤4203的可选实现方式，及图2、图3A、图3B、图4A、图4B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，上述方法可以包括上述终端侧、网络设备侧等的实施例所述的方法，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或其他实施例的任意步骤之间进行任意组合。
综上，本公开提出的通信方法，通过终端向网络设备发送上行数据和/或上行信令；启动响应时间窗，响应时间窗用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；在响应时间窗内接收响应消息。通过终端向网络设备发送上行数据和/或上行信令后，启动响应窗口，在响应窗口中等待接收响应消息，实现终端与网络设备之间发送数据或信令的目的。
以下介绍本公开实施例提供的一种通信方法，该方法包括以下步骤：
1、发送Msg1-Less EDT的Msg3。UE发送Msg3的方式可以有以下两种：
1.1、用于Msg1-Less EDT的Msg3发送的资源可以为竞争性资源，也可以为非竞争性资源。对非竞争性资源，可以为包含一个UE特定的OCC资源配置的PUR资源。对竞争性资源，UE没有被配置唯一的OCC/DMRS资源，UE在使用竞争性资源时，需要自己从OCC/DMRS资源池中选择一个OCC/DMRS资源。竞争性资源可以通过系统消息或专用信令发送给UE，非竞争性资源通过专用信令发送给UE。
1.2、Msg1-Less EDT的Msg3包括以下一种或多种：基于控制面CIOT EPS/5GS的UL RRC早期数据请求信息；用户面CIOT EPS/5GS的上行用户数据传输和在CCCH上的UL RRC连接恢复请求消息的复用方式发送。
可选地，Msg1-Less EDT可以是第二EDT过程。
可选地，步骤1的可选实现方式可以参见图2的步骤2101、图3A的步骤3101、图3B的步骤3201、图4A的步骤4101、图4B的步骤4201、图5的步骤5101的可选实现方式，及图2、图3A、图3B、图4A、图4B、图5所涉及的实施例中其他关联部分，此处不再赘述。
2、启动响应窗口。
可选地，响应窗口可以与响应时间窗口替换。
UE响应窗口的启动时间为包含PUSCH传输结束位置的子帧+UE-gNB RTT+X。
可选地，RTT往返时间的大小由两段传播时延决定，一种是从UE到卫星，另一段是从卫星到基站。
2.1、X为0,1,2,3,4个子帧。
可选地，X可以是时间偏移。
2.2、PUSCH传输结束位置为PUSCH最后一个重复的结束位置。
可选地，响应窗口的长度由网络配置，或者，响应窗口长度可以由CE等级配置。
在上述实施例中，UE为NTN UE。
3、重新启动响应窗口。
如果UE在响应窗口接收到重传调度，UE在重传结束位置的子帧+UE-gNB RTT+X重启响应窗口。
3.1、X为0,1,2,3,4个子帧。
可选地，X可以是时间偏移。
3.2、重传结束位置为重传PUSCH最后一个重复的结束位置。
在上述实施例中，UE为NTN UE。
可选地，步骤2和步骤3的可选实现方式可以参见图2的步骤2102、步骤2103、图3A的步骤3102、图3B的步骤3202、图4A的步骤4102、图4B的步骤4202、图5的步骤5102的可选实现方式，及图2、图3A、图3B、图4A、图4B、图5所涉及的实施例中其他关联部分，此处不再赘述。
4、UE停止响应窗口。
可选地，停止响应窗口的条件可以是第一条件。
4.1、如果UE采用竞争性资源发送Msg1-Less EDT的Msg3，如果UE接收到包含UE标识的响应消息，UE停止响应窗口。
4.1.1、UE接收Msg4的PDCCH中包括UE发送Msg3时所使用的DMRS资源ID和/或OCC资源ID，UE停止响应窗口。
4.1.2、UE接收Msg4的PDCCH通过UE发送Msg3所对应的RNTI来标识，UE停止响应窗口。
可选地，步骤4.1可以与步骤4.1.1结合在一起作为停止响应窗口的条件。
可选地，步骤4.1可以与步骤4.1.2结合在一起作为停止响应窗口的条件。
可选地，步骤4.1可以与步骤4.1.1和4.1.2结合在一起作为停止响应窗口的条件。
4.2、UE采用非竞争性资源发送Msg1-Less EDT的Msg3，如果UE接收到包含L1-ACK的Msg4，UE停止响应窗口。
4.3、如果UE接收到包含回退指示的Msg4，UE停止响应窗口。
4.4、如果UE接收到通过配置给该UE的RNTI标识的PDCCH，且MAC PDU成功译码，UE停止响应窗口。
可选地，步骤4中各实施例的条件可以独立或组合。
可选地，步骤4的可选实现方式可以参见图2的步骤2104、步骤2105、图3A的步骤3103、步骤3104、图4A的步骤4102、图4B的步骤4202、图5的步骤5103的可选实现方式，及图2、图3A、图4A、图4B、图5所涉及的实施例中其他关联部分，此处不再赘述。
5、UE在响应窗口超时的情况下，执行以下任一操作：
5.1、UE回退到基于RACH的EDT。
可选地，基于RACH的EDT可以是第一EDT过程。
5.2、UE尝试Msg1-Less EDT的次数小于或小于等于门限值，UE重新尝试Msg1-Less EDT。否则，UE回退到基于RACH的EDT或终止Msg1-Less EDT。
可选地，门限值可以是预设阈值，由网络设备配置终端尝试第二EDT过程次数的最大值。
5.3、UE终止Msg1-Less EDT。
可选地，步骤5的可选实现方式可以参见图2的步骤2106、图3A的步骤3105的可选实现方式，及图2、图3A所涉及的实施例中其他关联部分，此处不再赘述。
本公开实施例所涉及的通信方法可以包括步骤1～步骤5中的至少一者。例如，步骤1可以作为独立实施例来实施，步骤2可以作为独立实施例来实施，步骤3可以作为独立实施例来实施，以此类推，不限于此。步骤1+2可以作为独立实施例来实施，步骤1+3可以作为独立实施例来实施，步骤1+2+4可以作为独立实施例来实施，步骤1+3+4可以作为独立实施例来实施，步骤1+2+4+5可以作为独立实施例来实施，步骤1+3+4+5可以作为独立实施例来实施，步骤1+2+3+4+5可以作为独立实施例来实施，但不限于此。
在本公开实施例中，部分或全部步骤、其可选实现方式可以与其他实施例中的部分或全部步骤任意组合，也可以与其他实施例的可选实现方式任意组合。
本公开实施例还提出用于实现以上任一方法的装置，例如，提出一装置，上述装置包括用以实现以上任一方法中终端所执行的各步骤的单元或模块。再如，还提出另一装置，包括用以实现以上任一方法中网络设备(例如接入网设备、核心网功能节点、核心网设备等)所执行的各步骤的单元或模块。
应理解以上装置中各单元或模块的划分仅是一种逻辑功能的划分，在实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。此外，装置中的单元或模块可以以处理器调用软件的形式实现：例如装置包括处理器，处理器与存储器连接，存储器中存储有指令，处理器调用存储器中存储的指令，以实现以上任一方法或实现上述装置各单元或模块的功能，其中处理器例如为通用处理器，例如中央处理单元(Central Processing Unit，CPU)或微处理器，存储器为装置内的存储器或装置外的存储器。或者，装置中的单元或模块可以以硬件电路的形式实现，可以通过对硬件电路的设计实现部分或全部单元或模块的功能，上述硬件电路可以理解为一个或多个处理器；例如，在一种实现中，上述硬件电路为专用集成电路(application-specific integrated circuit，ASIC)，通过对电路内元件逻辑关系的设计，实现以上部分或全部单元或模块的功能；再如，在另一种实现中，上述硬件电路为可以通过可编程逻辑器件(programmable logic device，PLD)实现，以现场可编程门阵列(Field Programmable Gate Array，FPGA)为例，其可以包括大量逻辑门电路，通过配置文件来配置逻辑门电路之间的连接关系，从而实现以上部分或全部单元或模块的功能。以上装置的所有单元或模块可以全部通过处理器调用软件的形式实现，或全部通过硬件电路的形式实现，或部分通过处理器调用软件的形式实现，剩余部分通过硬件电路的形式实现。
在本公开实施例中，处理器是具有信号处理能力的电路，在一种实现中，处理器可以是具有指令读取与运行能力的电路，例如中央处理单元(Central Processing Unit，CPU)、微处理器、图形处理器(graphics processing unit，GPU)(可以理解为微处理器)、或数字信号处理器(digital signal processor，DSP)等；在另一种实现中，处理器可以通过硬件电路的逻辑关系实现一定功能，上述硬件电路的逻辑关系是固定的或可以重构的，例如处理器为专用集成电路(application-specific integrated circuit，ASIC)或可编程逻辑器件(programmable logic device，PLD)实现的硬件电路，例如FPGA。在可重构的硬件电路中，处理器加载配置文档，实现硬件电路配置的过程，可以理解为处理器加载指令，以实现以上部分或全部单元或模块的功能的过程。此外，还可以是针对人工智能设计的硬件电路，其可以理解为ASIC，例如神经网络处理单元(Neural Network Processing Unit，NPU)、张量处理单元(Tensor Processing Unit，TPU)、深度学习处理单元(Deep learning Processing Unit，DPU)等。
图6A是根据本公开实施例提供的终端的结构示意图。如图6A所示，终端6100包括收发模块6101和处理模块6102。在一些实施例中，上述收发模块6101用于向网络设备发送上行数据和/或上行信令和在响应时间窗内接收响应消息。处理模块6102用于等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令。可选地，上述收发模块用于执行以上任一方法中终端6100执行的发送和/或接收等通信步骤(例如步骤2101、步骤2104、步骤3101、步骤3103、步骤3201、步骤3203，但不限于此)中的至少一者， 此处不再赘述。处理模块用于执行其他步骤(例如步骤2103、步骤2105、步骤2106、步骤3102、步骤3104、步骤3105、步骤3203，但不限于此)中的至少一者，此处不再赘述。
图6B是根据本公开实施例提供的网络设备6200的结构示意图。如图6B所示，网络设备6200可以包括收发模块6201和处理模块6202。在一些实施例中，上述收发模块6201用于接收终端发送的上行数据和/或上行信令；处理模块6202用于确定响应时间窗，响应时间窗用于终端等待接收网络设备发送的响应消息，响应消息包括下行数据和/或下行信令；收发模块还用于在响应时间窗内，向终端发送响应消息。
可选地，上述收发模块用于执行以上任一方法中网络设备6200执行的发送和/或接收等通信步骤(例如步骤2101、步骤2104、步骤4101、步骤4103、步骤4201、步骤4203，但不限于此)中的至少一者，此处不再赘述。处理模块用于执行其他步骤(例如步骤2102、步骤4102、步骤4202，但不限于此)中的至少一些，此处不再赘述。
在一些实施例中，收发模块可以包括发送模块和/或接收模块，发送模块和接收模块可以是分离的，也可以集成在一起。可选地，收发模块可以与收发器相互替换。
图7A根据本公开实施例提供的通信设备7100的结构示意图。通信设备7100可以是网络设备(例如接入网设备、核心网设备等)，也可以是终端(例如用户设备等)，也可以是支持网络设备实现以上任一方法的芯片、芯片系统、或处理器等，还可以是支持终端实现以上任一方法的芯片、芯片系统、或处理器等。通信设备7100可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
如图7A所示，通信设备7100包括一个或多个处理器7101。处理器7101可以是通用处理器或者专用处理器等，例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行程序，处理程序的数据。可选地，通信设备7100用于执行以上任一方法。可选地，一个或多个处理器7101用于调用指令以使得通信设备7100执行以上任一方法。
在一些实施例中，通信设备7100还包括一个或多个收发器7102。在通信设备7100包括一个或多个收发器7102时，收发器7102执行上述方法中的发送和/或接收等通信步骤(例如步骤2101、步骤2104、步骤3101、步骤3103、步骤3201、步骤3203、步骤4101、步骤4103、步骤4201、步骤4203、步骤5101、步骤5103，但不限于此)中的至少一者，处理器7101执行其他步骤(例如步骤2102、步骤2103、步骤2105、步骤2106、步骤3102、步骤3104、步骤3105、步骤4102、步骤4202、步骤5102，但不限于此)中的至少一者。在可选的实施例中，收发器可以包括接收器和/或发送器，接收器和发送器可以是分离的，也可以集成在一起。可选地，收发器、收发单元、收发机、收发电路、接口电路、接口等术语可以相互替换，发送器、发送单元、发送机、发送电路等术语可以相互替换，接收器、接收单元、接收机、接收电路等术语可以相互替换。
在一些实施例中，通信设备7100还包括用于存储数据的一个或多个存储器7103。可选地，全部或部分存储器7103也可以处于通信设备7100之外。在可选的实施例中，通信设备7100可以包括一个或多个接口电路7104。可选地，接口电路7104与存储器7102连接，接口电路7104可用于从存储器7102或其他装置接收数据，可用于向存储器7102或其他装置发送数据。例如，接口电路7104可读取存储器7102中存储的数据，并将该数据发送给处理器7101。
在一些实施例中，处理器8101可以存有计算机程序7105，计算机程序7105在处理器7101上运行，可使得通信装置7000执行上述方法实施例中描述的方法。计算机程序7105可能固化在处理器7101中，该种情况下，处理器7101可能由硬件实现。
以上实施例描述中的通信设备7100可以是网络设备或者终端，但本公开中描述的通信设备7100的范围并不限于此，通信设备7100的结构可以不受图7A的限制。通信设备可以是独立的设备或者可以是较大设备的一部分。例如所述通信设备可以是：1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选地，上述IC集合也可以包括用于存储数据，程序的存储部件；(3)ASIC，例如调制解调器(Modem)；(4)可嵌入在其他设备内的模块；(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；(6)其他等等。
图7B是本公开实施例提出的芯片7200的结构示意图。对于通信设备7100可以是芯片或芯片系统的情况，可以参见图7B所示的芯片7200的结构示意图，但不限于此。
芯片7200包括一个或多个处理器7201。芯片7200用于执行以上任一方法。
在一些实施例中，芯片7200还包括一个或多个接口电路7202。可选地，接口电路、接口、收发管脚等术语可以相互替换。在一些实施例中，芯片7200还包括用于存储数据的一个或多个存储器7203。可选地，全部或部分存储器7203可以处于芯片7200之外。可选地，接口电路7202与存储器7203连接，接口电路7202可以用于从存储器7203或其他装置接收数据，接口电路7202可用于向存储器7203或其他装置发送数据。例如，接口电路7202可读取存储器7203中存储的数据，并将该数据发送给处理器7201。
在一些实施例中，接口电路7202执行上述方法中的发送和/或接收等通信步骤(例如步骤2101、步骤2104、步骤3101、步骤3103、步骤3201、步骤3203、步骤4101、步骤4103、步骤4201、步骤4203、步骤5101、步骤5103，但不限于此)中的至少一者。接口电路7202执行上述方法中的发送和/或接收等通信步骤例如是指：接口电路7202执行处理器7201、芯片7200、存储器7203或收发器件之间的数据交互。在一些实施例中，处理器7201执行其他步骤(例如步骤2102、步骤2103、步骤2105、步骤2106、步骤3102、步骤3104、步骤3105、步骤4102、步骤4202、步骤5102，但不限于此)中的至少一者。
虚拟装置、实体装置、芯片等各实施例中所描述的各模块和/或器件可以根据情况任意组合或者分离。可选地，部分或全部步骤也可以由多个模块和/或器件协作执行，此处不做限定。
本公开还提出存储介质，上述存储介质上存储有指令，当上述指令在通信设备7100上运行时，使得通信设备7100执行以上任一方法。可选地，上述存储介质是电子存储介质。可选地，上述存储介质是计算机可读存储介质，但不限于此，其也可以是其他装置可读的存储介质。可选地，上述存储介质可以是非暂时性(non-transitory)存储介质，但不限于此，其也可以是暂时性存储介质。
本公开还提出程序产品，上述程序产品被通信设备7100执行时，使得通信设备7100执行以上任一方法。可选地，上述程序产品是计算机程序产品。
本公开还提出计算机程序，当其在计算机上运行时，使得计算机执行以上任一方法。

Claims (29)

  1. 一种通信方法，其特征在于，所述方法由终端执行，所述方法包括：
    向网络设备发送上行数据和/或上行信令；
    启动响应时间窗，所述响应时间窗用于等待接收所述网络设备发送的响应消息，所述响应消息包括下行数据和/或下行信令；
    在所述响应时间窗内接收所述响应消息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述上行信令包括以下至少一项：
    用于第一早期数据传输EDT过程的消息1 Msg1和/或消息3 Msg3，所述第一EDT过程为随机接入信道RACH EDT过程，所述第一EDT过程包括Msg1、Msg2、Msg3、Msg4；
    用于第二EDT过程的Msg3，所述第二EDT过程为Msg1-less EDT过程，所述第二EDT过程包括Msg3、Msg4；
    所述下行信令包括以下至少一项：
    用于所述第一早期数据传输EDT过程的消息2 Msg2和/或消息4 Msg4；
    用于所述第二EDT过程的Msg4。
  3. 根据权利要求1或2所述的方法，其特征在于，所述向网络设备发送上行数据和/或上行信令包括：
    基于控制面发送所述上行信令，所述上行信令中携带所述上行数据。
  4. 根据权利要求1或2所述的方法，其特征在于，所述向网络设备发送上行数据和/或上行信令包括：
    以复用的方式，基于用户面发送所述上行数据并基于控制面发送所述上行信令。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述启动响应时间窗包括：
    在结束发送所述上行数据和/或所述上行信令的子帧之后等待第一时长，启动所述响应时间窗。
  6. 根据权利要求5所述的方法，其特征在于，所述第一时长包括以下至少一项：
    所述终端与所述网络设备之间的往返时间RTT；
    时间偏移。
  7. 根据权利要求5或6所述的方法，其特征在于，所述结束发送所述上行数据和/或所述上行信令的子帧包括以下至少一项：
    在一次物理上行共享信道PUSCH发送中重复发送多次所述上行数据和/或所述上行信令的最后一次发送的结束子帧；
    重传PUSCH的每次PUSCH发送中重复发送多次所述上行数据和/或所述上行信令的最后一次发送的结束子帧。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    在第一条件下，停止所述响应时间窗。
  9. 根据权利要求8所述的方法，其特征在于，所述第一条件包括以下至少一项：
    所述终端采用竞争性资源发送所述上行数据和/或所述上行信令，所述终端接收到的响应消息中包含所述终端的标识；
    所述终端采用竞争性资源发送所述上行数据和/或所述上行信令，所述终端接收所述响应消息的物理下行控制信道PDCCH中包括第一资源标识，所述第一资源标识为所述终端发送所述上行数据和/或所述上行信令所使用的解调参考信号DMRS资源标识和/或正交覆盖码OCC资源标识；
    所述终端采用竞争性资源发送所述上行数据和/或所述上行信令，所述终端接收所述响应消息的PDCCH由第一网络标识标识，所述第一网络标识为所述终端发送所述上行数据和/或所述上行信令所对应的无线网络临时标识RNTI；
    所述终端采用非竞争性资源发送所述上行数据和/或所述上行信令，所述终端接收到的所述响应消息包括层1反馈L1-ACK；
    所述终端接收到的所述响应消息包括回退指示，所述回退指示用于指示所述终端回退至RACH EDT过程；
    所述终端接收到PDCCH，所述PDCCH由配置给所述终端的RNTI标识，且媒体访问控制协议数据单元MAC PDU成功译码。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述方法还包括：
    在所述响应时间窗超时的情况下，执行第一操作。
  11. 根据权利要求10所述的方法，其特征在于，所述第一操作包括以下至少一项：
    由第二EDT过程回退至第一EDT过程；
    尝试执行所述第二EDT过程的次数小于或等于预设阈值时，重新尝试执行所述第二EDT过程，否则回退至所述第一EDT过程；
    终止所述第二EDT过程。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述响应时间窗的长度由协议预定义或由所述网络设备配置。
  13. 一种通信方法，其特征在于，所述方法由网络设备执行，所述方法包括：
    接收终端发送的上行数据和/或上行信令；
    确定响应时间窗，所述响应时间窗用于所述终端等待接收所述网络设备发送的响应消息，所述响应消息包括下行数据和/或下行信令；
    在所述响应时间窗内，向所述终端发送所述响应消息。
  14. 根据权利要求13所述的方法，其特征在于，
    所述上行信令包括以下至少一项：
    用于第一早期数据传输EDT过程的消息1 Msg1和/或消息3 Msg3，所述第一EDT过程为随机接入信道RACH EDT过程，所述第一EDT过程包括Msg1、Msg2、Msg3、Msg4；
    用于第二EDT过程的Msg3，所述第二EDT过程为Msg1-less EDT过程，所述第二EDT过程包括Msg3、Msg4；
    所述下行信令包括一下至少一项：
    用于所述第一早期数据传输EDT过程的消息2 Msg2和/或消息4 Msg4；
    用于所述第二EDT过程的Msg4。
  15. 根据权利要求13或14所述的方法，其特征在于，所述接收终端发送的上行数据和/或上行信令包括：
    基于控制面接收所述上行信令，所述上行信令中携带所述上行数据。
  16. 根据权利要求13或14所述的方法，其特征在于，所述接收终端发送的上行数据和/或上行信令包括：
    以复用的方式，基于用户面接收所述上行数据并基于控制面接收所述上行信令。
  17. 根据权利要求13至16中任一项所述的方法，其特征在于，所述响应时间窗的开始时间为：
    在所述终端结束发送所述上行数据和/或所述上行信令的子帧之后等待第一时长。
  18. 根据权利要求17所述的方法，其特征在于，所述第一时长包括以下至少一项：
    所述终端与所述网络设备之间的往返时间RTT；
    时间偏移。
  19. 根据权利要求17或18所述的方法，其特征在于，所述终端结束发送所述上行数据和/或所述上行信令的子帧包括以下至少一项：
    所述终端在一次物理上行共享信道PUSCH发送中重复发送多次所述上行数据和/或所述上行信令的最后一次发送的结束子帧；
    所述终端重传PUSCH的每次PUSCH发送中重复发送多次所述上行数据和/或所述上行信令的最后一次发送的结束子帧。
  20. 根据权利要求13至19中任一项所述的方法，其特征在于，所述响应时间窗在第一条件下停止。
  21. 根据权利要求20所述的方法，其特征在于，所述第一条件包括以下至少一项：
    所述终端采用竞争性资源发送所述上行数据和/或所述上行信令，所述响应消息中包含所述终端的标识；
    所述终端采用竞争性资源发送所述上行数据和/或所述上行信令，所述响应消息的物理下行控制信道PDCCH中包括第一资源标识，所述第一资源标识为所述终端发送所述上行数据和/或所述上行信令所使用的解调参考信号DMRS资源标识和/或正交覆盖码OCC资源标识；
    所述终端采用竞争性资源发送所述上行数据和/或所述上行信令，所述响应消息的PDCCH由第一网络标识标识，所述第一网络标识为所述终端发送所述上行数据和/或所述上行信令所对应的无线网络临时标识RNTI；
    所述终端采用非竞争性资源发送所述上行数据和/或所述上行信令，所述终响应消息包括层1反馈L1-ACK；
    所述响应消息包括回退指示，所述回退指示用于指示所述终端回退至RACH EDT过程；
    所述终端接收到PDCCH，所述PDCCH由配置给所述终端的RNTI标识，且媒体访问控制协议数据单元MAC PDU成功译码。
  22. 根据权利要求13至21中任一项所述的方法，其特征在于，所述方法还包括：
    在所述响应时间窗超时的情况下，执行第一操作。
  23. 根据权利要求22所述的方法，其特征在于，所述第一操作包括以下至少一项：
    由第二EDT过程回退至第一EDT过程；
    尝试执行所述第二EDT过程的次数小于或等于预设阈值时，重新尝试执行所述第二EDT过程，否则回退至所述第一EDT过程；
    终止所述第二EDT过程。
  24. 一种终端，其特征在于，包括：
    收发模块，用于向网络设备发送上行数据和/或上行信令；
    处理模块，用于启动响应时间窗，所述响应时间窗用于等待接收所述网络设备发送的响应消息，所述响应消息包括下行数据和/或下行信令；
    所述收发模块还用于在所述响应时间窗内接收所述响应消息。
  25. 一种网络设备，其特征在于，包括：
    收发模块，用于接收终端发送的上行数据和/或上行信令；
    处理模块，用于确定响应时间窗，所述响应时间窗用于所述终端等待接收所述网络设备发送的响应消息，所述响应消息包括下行数据和/或下行信令；
    所述收发模块还用于在所述响应时间窗内，向所述终端发送所述响应消息。
  26. 一种通信设备，其中，包括：收发器；存储器；处理器，分别与所述收发器及所述存储器连接，配置为通过执行所述存储器上的计算机可执行指令，控制所述收发器的无线信号收发，并能够实现权利要求1-23中任一项所述的方法。
  27. 一种计算机存储介质，其中，所述计算机存储介质存储有计算机可执行指令；所述计算机可执行指令被处理器执行后，能够实现权利要求1-23中任一项所述的方法。
  28. 一种通信系统，其特征在于，包括：终端和网络设备，其中，所述终端用于执行如权利要求1至12中任一项所述的方法；所述网络设备用于执行如权利要求13至23中任一项所述的方法。
  29. 根据权利要求28所述的系统，其特征在于，所述终端为以下至少一项：
    非地面网络NTN终端；
    带宽降低及低复杂性BL终端；
    增强覆盖型终端；
    窄带物联网NB-IoT终端。
PCT/CN2024/076403 2024-02-06 2024-02-06 一种通信方法及设备、通信系统、通信设备、存储介质 Pending WO2025166555A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202480026642.0A CN121040174A (zh) 2024-02-06 2024-02-06 一种通信方法及设备、通信系统、通信设备、存储介质
PCT/CN2024/076403 WO2025166555A1 (zh) 2024-02-06 2024-02-06 一种通信方法及设备、通信系统、通信设备、存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/076403 WO2025166555A1 (zh) 2024-02-06 2024-02-06 一种通信方法及设备、通信系统、通信设备、存储介质

Publications (1)

Publication Number Publication Date
WO2025166555A1 true WO2025166555A1 (zh) 2025-08-14

Family

ID=96698743

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/076403 Pending WO2025166555A1 (zh) 2024-02-06 2024-02-06 一种通信方法及设备、通信系统、通信设备、存储介质

Country Status (2)

Country Link
CN (1) CN121040174A (zh)
WO (1) WO2025166555A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111885737A (zh) * 2019-05-03 2020-11-03 华为技术有限公司 随机接入的方法和装置
US20210014899A1 (en) * 2019-07-09 2021-01-14 Asustek Computer Inc. Method and apparatus for carrier selection and early data transmission (edt) in a wireless communication system
CN113498628A (zh) * 2019-07-26 2021-10-12 Oppo广东移动通信有限公司 监听随机接入响应的方法、终端设备、网络设备及存储介质
CN113574958A (zh) * 2019-03-29 2021-10-29 富士通株式会社 随机接入响应的接收方法、装置和通信系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113574958A (zh) * 2019-03-29 2021-10-29 富士通株式会社 随机接入响应的接收方法、装置和通信系统
CN111885737A (zh) * 2019-05-03 2020-11-03 华为技术有限公司 随机接入的方法和装置
US20210014899A1 (en) * 2019-07-09 2021-01-14 Asustek Computer Inc. Method and apparatus for carrier selection and early data transmission (edt) in a wireless communication system
CN113498628A (zh) * 2019-07-26 2021-10-12 Oppo广东移动通信有限公司 监听随机接入响应的方法、终端设备、网络设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Email discussion report: [99#45][NB-IoT/MTC] Early data transmission", 3GPP DRAFT; R2-1710888 EMAIL DISC REPORT [99#45] EARLY DATA TRANSMISSION, vol. RAN WG2, 28 September 2017 (2017-09-28), Prague, Czechia, pages 1 - 42, XP051354600 *

Also Published As

Publication number Publication date
CN121040174A (zh) 2025-11-28

Similar Documents

Publication Publication Date Title
US12323833B2 (en) Enhancement for monitoring PC5 to radio resource control (RRC) configuration procedure in new radio (NR) sidelink (SL)
US20230189349A1 (en) Data transmission method and terminal device
WO2025015611A1 (zh) 信息处理方法、终端、网络设备以及存储介质
WO2025091376A1 (zh) 发送接收指示信息的方法、终端、网络设备、系统及介质
US20240334359A1 (en) Method for timing advance maintenance in uplink synchronization, terminal device, and chip
CN118451772A (zh) 通信方法和设备
WO2024221472A1 (zh) 信息处理方法及装置、通信设备、通信系统、存储介质
US12349105B2 (en) Method and apparatus for absence time request
WO2025152246A1 (zh) 通信方法、终端、网络设备、系统及存储介质
JP7697597B2 (ja) 端末装置、通信装置及び端末装置の方法
CN115843464B (zh) 无线通信方法、终端设备和网络设备
CN117596705B (zh) 通信方法、终端、网络设备、通信系统及存储介质
WO2025166774A1 (zh) Pdcch监听方法、装置
WO2025091445A1 (zh) 通信方法、终端和存储介质
WO2025166555A1 (zh) 一种通信方法及设备、通信系统、通信设备、存储介质
WO2025025182A1 (zh) 用于配置定时器的方法及装置、存储介质
WO2025086042A1 (zh) 信息发送、接收方法、终端、网络节点和存储介质
WO2025091408A1 (zh) 信道接入方法、通信方法、终端和存储介质
WO2025208540A1 (zh) 信息处理方法、终端、网络设备、通信系统及存储介质
WO2025166775A1 (zh) 响应消息接收方法、装置
WO2025166668A1 (zh) 基于配置资源发送数据和/或信令的方法、终端设备、网络设备及存储介质
CN121444578A (zh) 通信方法、通信设备、通信系统、存储介质及程序产品
WO2025200028A1 (zh) 信息接收、发送方法和装置、终端、网络设备和存储介质
WO2025208306A1 (zh) 信息的传输方法、终端、网络设备及存储介质
WO2026091114A1 (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: 24922798

Country of ref document: EP

Kind code of ref document: A1