WO2022204999A1 - 存活时间的处理方法和终端设备 - Google Patents
存活时间的处理方法和终端设备 Download PDFInfo
- Publication number
- WO2022204999A1 WO2022204999A1 PCT/CN2021/084137 CN2021084137W WO2022204999A1 WO 2022204999 A1 WO2022204999 A1 WO 2022204999A1 CN 2021084137 W CN2021084137 W CN 2021084137W WO 2022204999 A1 WO2022204999 A1 WO 2022204999A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- time
- live
- transmission
- perform
- timer
- Prior art date
Links
- 230000004083 survival effect Effects 0.000 title claims abstract description 121
- 238000003672 processing method Methods 0.000 title claims abstract description 21
- 238000012545 processing Methods 0.000 claims abstract description 49
- 230000005540 biological transmission Effects 0.000 claims description 337
- 238000000034 method Methods 0.000 claims description 144
- 230000008569 process Effects 0.000 claims description 58
- 238000004590 computer program Methods 0.000 claims description 23
- 230000011664 signaling Effects 0.000 claims description 21
- 238000012546 transfer Methods 0.000 claims description 20
- 238000013507 mapping Methods 0.000 claims description 19
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims description 9
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims description 9
- 230000009471 action Effects 0.000 claims description 9
- 230000003993 interaction Effects 0.000 claims description 7
- 238000013475 authorization Methods 0.000 claims description 4
- 230000003252 repetitive effect Effects 0.000 claims 1
- 230000007246 mechanism Effects 0.000 abstract description 8
- 238000004891 communication Methods 0.000 description 52
- 230000006870 function Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 12
- 238000001228 spectrum Methods 0.000 description 11
- 230000007774 longterm Effects 0.000 description 8
- 230000010076 replication Effects 0.000 description 8
- 238000007726 management method Methods 0.000 description 5
- 238000012913 prioritisation Methods 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 3
- 239000002699 waste material Substances 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 2
- 102100036409 Activated CDC42 kinase 1 Human genes 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/188—Time-out mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1848—Time-out mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0092—Indication of how the channel is divided
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/14—Two-way operation using the same type of signal, i.e. duplex
- H04L5/1469—Two-way operation using the same type of signal, i.e. duplex using time-sharing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
- H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/189—Transmission or retransmission of more than one copy of a message
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0026—Division using four or more dimensions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
Definitions
- the present application relates to the field of communications, and more particularly, to a time-to-live processing method and a terminal device.
- 5G Next Generation of Communication
- eMBB Enhanced Mobile Broadband
- URLLC Ultra Reliability And Low Latency Communication
- mMTC Massive Machine Type Communications
- the R17 URLLC project requires RAN to be enhanced based on survival time. But there is currently no processing mechanism for survival time.
- the embodiments of the present application provide a method and a terminal device for processing the survival time, which can specify the relevant processing mechanism of the survival time.
- An embodiment of the present application provides a method for processing time-to-live, including: a terminal device performs an operation related to time-to-live according to first information, where the first information includes time-to-live related information.
- An embodiment of the present application provides a terminal device, including: a processing unit configured to perform an operation related to the survival time according to first information, where the first information includes information related to the survival time.
- An embodiment of the present application provides a terminal device, including a processor and a memory.
- the memory is used for storing a computer program
- the processor is used for calling and running the computer program stored in the memory, so that the terminal device executes the above-mentioned processing method of the survival time.
- An embodiment of the present application provides a chip, which is used to implement the above-mentioned method for processing the survival time.
- the chip includes: a processor for calling and running a computer program from the memory, so that the device installed with the chip executes the above-mentioned processing method of the survival time.
- An embodiment of the present application provides a computer-readable storage medium for storing a computer program, and when the computer program is run by a device, the device enables the device to execute the above-mentioned processing method of the survival time.
- An embodiment of the present application provides a computer program product, including computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned method for processing the survival time.
- An embodiment of the present application provides a computer program, which, when running on a computer, enables the computer to execute the above-mentioned method for processing the survival time.
- the terminal device performs operations related to the survival time according to the first information, and can specify the processing mechanism related to the survival time.
- FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
- Figure 2 is a schematic diagram of time-to-live usage.
- FIG. 3 is a schematic flowchart of a method for processing time-to-live according to an embodiment of the present application.
- FIG. 4 is a schematic block diagram of a terminal device according to an embodiment of the present application.
- FIG. 5 is a schematic block diagram of a terminal device according to another embodiment of the present application.
- FIG. 6 is a schematic block diagram of a communication device according to an embodiment of the present application.
- FIG. 7 is a schematic block diagram of a chip according to an embodiment of the present application.
- FIG. 8 is a schematic block diagram of a communication system according to an embodiment of the present application.
- GSM Global System of Mobile communication
- CDMA Code Division Multiple Access
- CDMA Wideband Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- LTE-A Advanced Long Term Evolution
- NR New Radio
- NTN Non-Terrestrial Networks
- UMTS Universal Mobile Telecommunication System
- WLAN Wireless Local Area Networks
- Wireless Fidelity Wireless Fidelity
- WiFi fifth-generation communication
- D2D Device to Device
- M2M Machine to Machine
- MTC Machine Type Communication
- V2V Vehicle to Vehicle
- V2X Vehicle to everything
- the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
- Carrier Aggregation, CA Carrier Aggregation, CA
- DC Dual Connectivity
- SA standalone
- the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.
- the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
- user equipment User Equipment, UE
- access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
- the terminal device can be a station (STAION, ST) in the WLAN, can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
- STAION, ST in the WLAN
- SIP Session Initiation Protocol
- WLL Wireless Local Loop
- PDA Personal Digital Assistant
- the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).
- the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
- a mobile phone Mobile Phone
- a tablet computer Pad
- a computer with a wireless transceiver function a virtual reality (Virtual Reality, VR) terminal device
- augmented reality (Augmented Reality, AR) terminal Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
- the terminal device may also be a wearable device.
- Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
- a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
- wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
- the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks
- the network device may have a mobile feature, for example, the network device may be a mobile device.
- the network device may be a satellite or a balloon station.
- the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc.
- the network device may also be a base station set in a location such as land or water.
- a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device (
- the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
- Pico cell Femto cell (Femto cell), etc.
- These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
- FIG. 1 exemplarily shows a communication system 100 .
- the communication system includes one network device 110 and two terminal devices 120 .
- the communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers of terminal devices 120, which are not limited in this embodiment of the present application.
- the communication system 100 may further include a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF) and other network entities, to which the embodiments of the present application Not limited.
- MME Mobility Management Entity
- AMF Access and Mobility Management Function
- the network equipment may further include access network equipment and core network equipment. That is, the wireless communication system further includes a plurality of core networks for communicating with the access network equipment.
- the access network equipment may be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system, or an authorized auxiliary access long-term evolution (authorized auxiliary access long-term evolution, LAA-
- the evolved base station (evolutional node B, may be referred to as eNB or e-NodeB for short) in the LTE) system is a macro base station, a micro base station (also called a "small base station"), a pico base station, an access point (AP), Transmission site (transmission point, TP) or new generation base station (new generation Node B, gNodeB), etc.
- a device having a communication function in the network/system may be referred to as a communication device.
- the communication device may include a network device and a terminal device with a communication function, and the network device and the terminal device may be specific devices in this embodiment of the application, which will not be repeated here; It may include other devices in the communication system, for example, other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
- the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship.
- a indicates B it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
- corresponding may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.
- the survival time (survival time) can be sent to the base station together with time sensitive communication assistance information (TSCAI).
- TSCAI time sensitive communication assistance information
- the time-to-live is specified by the application function (AF), in "time”, with a time scale corresponding to the burst period, or the time-to-live corresponds to the maximum number of consecutive message transmission failures, where a message is a single packet/frame consisting of or a single burst of a set of packets/frames, and a transmission failure occurs when the packet delay budget requirement corresponding to the message is not met.
- AF application function
- time-to-live is represented by continuously transmitting erroneous packets
- a burst corresponds to a message, and a burst includes one or more packets.
- the survival time of some businesses is a multiple of the business cycle. Such as 1 times (representing that there cannot be two consecutive packet losses), 3 times and so on.
- the survival time of some services is 0 (representing no packet loss). Therefore, a time-to-live detection mechanism is required to ensure that the maximum tolerated consecutive packet errors are avoided.
- the peer end may not have time to provide feedback confirmation (ACK).
- PDB packet delay budget
- RTT round-trip time
- ACK feedback confirmation
- the PDB has already timed out, and it is already necessary to perform a more reliable transmission. This may result in redundant transmissions (which would have been correct, but did not receive an ACK in time, resulting in highly reliable retransmissions).
- a schematic diagram is used for the survival time. Included in Figure 2 are the relationships between logical communication links, communication services, and application state (eg, lost messages).
- the application layer considers entering the time-to-live when a packet is lost.
- the so-called survival time is a transition period, after which the application layer transmission is considered to enter the DOWN (disconnected) state.
- the embodiments of the present application can specify the detection and processing mechanism for the survival time. Further, it can be clarified how to reduce redundant transmission and waste of resources under the condition of ensuring strict service transmission requirements of time-to-live.
- FIG. 3 is a schematic flowchart of a method 200 for processing time-to-live according to an embodiment of the present application.
- the method can optionally be applied to the system shown in Figure 1, but is not limited thereto.
- the method includes at least some of the following.
- the terminal device performs an operation related to the survival time according to the first information, where the first information includes the relevant information of the survival time.
- the relevant information of the time-to-live includes at least one of the following: time-to-live, data bearer (Data Radio Bearer, DRB) identifier, quality of service (Quality of Service, QoS) flow (flow) identifier, packet data unit (Packet Data Unit, PDU) session identification, service arrival time, service mode, service cycle, related timer configuration, indication information for using time-to-live related information, and indication information for performing time-to-live related operations.
- data bearer Data Radio Bearer, DRB
- QoS Quality of Service
- flow flow
- PDU packet data unit
- service arrival time service mode
- service cycle service cycle
- related timer configuration indication information for using time-to-live related information
- indication information for performing time-to-live related operations includes at least one of the following: time-to-live, data bearer (Data Radio Bearer, DRB) identifier, quality of service (Quality of Service, QoS) flow (flow) identifier, packet data unit (Packet Data Unit, PDU
- the relevant information of the time-to-live may be configured in the RRC configuration (RRCconfig).
- RRCconfig RRC configuration
- DRBconfig DRB configuration
- CGconfig CG configuration
- LCH configuration LCH configuration
- MAC config serving cell configuration
- BWP config BWP configuration
- the first information is predefined, indicated by the access network network or indicated by the core network.
- the method further includes: the terminal device receives indication signaling from the network device, where the indication signaling is used to indicate whether to perform a time-to-live operation, and/or, which time-to-live operation to perform.
- the terminal device may be enabled to perform operations related to the survival time only after the network instructs it.
- the indication signaling may be different or the same.
- the terminal device can perform the relevant operation of the time-to-live; if the indication signaling does not indicate to perform the relevant operation of the time-to-live , the terminal device does not perform operations related to the time-to-live.
- the terminal device may perform the time-to-live operation indicated in the indication signaling.
- the terminal device may perform a default time-to-live operation.
- the default time-to-live operation is predefined, indicated by the access network network or indicated by the core network.
- the indication signaling includes at least one of radio resource control (Radio Resource Control, RRC), media access control (Media Access Control, MAC), downlink control information (Downlink Control Information, DCI).
- RRC Radio Resource Control
- MAC media access control
- DCI Downlink Control Information
- performing operations related to the time-to-live includes at least one of the following:
- determine whether to enter or start a survival time including at least one of the following:
- PDCP Packet Data Convergence Protocol
- SDU Service Data Unit
- TB Transport Block
- PUSCH Physical Uplink Shared Channel
- a PDCP PDU is considered to be at least one of lost, unsuccessfully received, or transmitted in error, determining the entry or start time-to-live;
- one SDU, one PDU, one TB or one PUSCH is considered to be at least one of lost, unsuccessful reception, transmission error, the entry or start time-to-live is determined.
- the SDU may be PDCP SDU, RLC SDU, MAC SDU, etc.
- PDU may include PDCP PDU, RLC PDU, MAC PDU, etc.
- entering or starting a time-to-live means entering or starting a time-to-live state.
- the action of determining the timer related to the time-to-live includes:
- a first timer is used to determine whether to enter or start the time-to-live.
- the start condition of the first timer includes at least one of the following:
- a packet or a PDCP SDU arrives at the PDCP layer of the sender
- the duration of the first timer is related to a packet delay budget (PDB).
- PDB packet delay budget
- use the first timer to determine whether to enter or start the survival time including:
- NACK non-acknowledgement
- ACK acknowledgment
- ACKs and/or NACKs the following characteristics may be present:
- Hybrid Automatic Repeat-reQuest Hybrid Automatic Repeat-reQuest, HARQ
- an automatic repeat request Automatic Repeat-reQuest, ARQ
- PDCP status report a PDCP status report.
- RLC Radio Link Control
- PDCP Packet Control
- the receiving end can periodically trigger feedback, feedback when a packet is received, feedback when a packet is not received at the location of a specific resource (such as a CG), feedback when the decoding error of a packet received by a specific resource, and feedback when receiving an SN number Feedback on later packs.
- a specific resource such as a CG
- determine whether to leave or end the survival time including at least one of the following:
- leaving or ending a time-to-live means leaving or ending a time-to-live state.
- the action of determining the timer related to the survival time further includes at least one of the following:
- start the second timer In the case of entering or starting the time-to-live, or in the case of entering or starting the time-to-live state, start the second timer;
- the second timer is stopped.
- the terminal device may stop the second timer after performing reporting or performing specific transmission.
- the method also includes at least one of the following:
- performing operations related to the survival time further includes at least one of the following:
- performing operations related to the time-to-live further includes at least one of the following:
- DFI Downlink Feedback Indication
- the terminal device performs operations related to the survival time according to the first information, including:
- the terminal device When the first condition is met, the terminal device performs at least one of the following operations according to the first information:
- the first condition includes at least one of the following: the time-to-live is a specific value, the time-to-live is less than the round-trip time (RTT), the time-to-live is less than Y times the RTT, the PDB is less than the RTT, the PDB is less than the service period or the resource period, the PDB RTT less than X times, not specific subcarrier spacing (subcarrier spacing), time division duplexing (Time Division Duplexing, TDD) working mode or configuration, indication or configuration jitter (jitter), specific jitter value.
- RTT round-trip time
- TDD time division duplexing
- jitter time division duplexing
- X and/or Y can be various, for example, 0 or any integer value (1, 2).
- X, Y can be the same or different.
- the SDU may be at least one of PDCP SDU, RLC SDU, and MAC SDU
- the PDU may include at least one of PDCP PDU, RLC PDU, and MAC PDU.
- perform specific transfers including:
- Different transmissions are performed for initial transmission and retransmission of one SDU, one PDU, one TB or one PUSCH.
- different transmissions are performed for the initial transmission and the retransmission, including at least one of the following:
- the initial transmission of a packet or a PDCP SDU or a MAC PDU performs highly reliable transmission, and the retransmission does not perform highly reliable transmission.
- the initial transmission of one SDU, one PDU, one TB or one PUSCH does not perform highly reliable transmission, and the retransmission performs highly reliable transmission.
- a certain retransmission of a packet or a PDCP SDU or a MAC PDU performs highly reliable transmission, and other retransmissions and initial transmissions do not perform highly reliable transmission.
- performing a specific transmission further comprising:
- the same transmission is performed for the initial transmission and retransmission of one SDU, one PDU, one TB or one PUSCH.
- perform the same transmission for the initial transmission and retransmission including:
- highly reliable transmission is performed for both initial transmission and retransmission of one packet or one PDCP SDU or one MAC PDU.
- highly reliable transmission is performed for both initial transmission and retransmission of one SDU, one PDU, one TB or one PUSCH.
- the terminal device performs operations related to the survival time according to the first information, including:
- the terminal device When the second condition is met, the terminal device performs at least one of the following operations according to the first information:
- the corresponding DFI may include a DFI corresponding to a HARQ process, a DFI corresponding to an LCH, a DFI corresponding to a CG, a DFI corresponding to a time-to-live, and the like.
- the first information also includes at least one of the following correspondences:
- the second condition includes at least one of the following:
- the survival time is bound to the HARQ process
- the terminal device determines, according to the first information, whether to receive or process the corresponding DFI, whether to perform reporting, or whether to perform specific transmission.
- the terminal device determines, according to the first information, whether to receive or process the corresponding DFI, whether to perform reporting, or whether to perform specific transmission.
- the terminal device determines whether to receive or process the corresponding DFI, whether to perform reporting, or whether to perform specific transmission according to the first information.
- DFI feedback is performed on the HARQ process corresponding to the time-to-live, and/or reporting or specific transmission is performed. Specifically, DFI feedback may be performed on the HARQ process corresponding to the lifetime, or reporting may be performed on the HARQ process corresponding to the lifetime, or specific transmission may be performed on the HARQ process corresponding to the lifetime.
- performing reporting or performing specific transmission also includes at least one of the following:
- the DFI feedback of the HARQ process corresponding to the time-to-live or the DFI feedback to the LCH or CG corresponding to the time-to-live, reporting or specific transmission is performed.
- performing the specific transmission includes using subsequent CG resources to perform the specific transmission.
- a specific transmission may be performed using the most recent CG after the feedback was received, or the first available CG, or the available CG that satisfies the minimum DFI feedback time.
- performing the specific transmission includes performing highly reliable transmission.
- the performing highly reliable transmission includes at least one of the following: performing replication transmission, performing repeated transmission, using another set of replication transmission times, using another set of repeated transmission times, using a second set of modulation and coding strategies MCS, Use another resource configuration, use another set of resource configuration parameters, use another set of LCH mapping restrictions, cancel LCH mapping restrictions, use the first set of LCH configuration parameters, use the second set of physical layer transmission parameters, use the second priority Approach.
- the physical layer transmission parameters may include at least one of the following: transmit power, power control parameters, physical layer priority, RV version, filling port, scrambling sequence, precoding and number of layers, etc.
- the priority processing method includes at least one of the following: Rel-15 priority processing method (such as not configured or supported LCH-based priority (LCH-based priority), not configured or supported PHY priority (priority) parameter , is not configured or supports at least one of the second resource priority processing), a processing method based on LCH-based priority, a priority processing method based on PHY priority parameters, and a second resource priority processing method.
- Rel-15 priority processing method such as not configured or supported LCH-based priority (LCH-based priority), not configured or supported PHY priority (priority) parameter , is not configured or supports at least one of the second resource priority processing
- the second resource priority processing method is used for a resource (such as a CG), based on the LCH priority or the priority of the resource corresponding to the HARQ process, to determine whether to select new transmission or retransmission first, and/or determine to select multiple retransmissions which of, and/or, determines which of multiple new passes is selected.
- the second resource priority processing method can be configured/indicated/enabled by a new parameter, or can be configured/indicated/enabled by reusing the LCH-based priority parameter.
- the Rel-15 priority processing method is used during normal transmission, and the LCH-based prioritization method is used during reliable transmission.
- the method based on LCH-based prioritization is used during normal transmission, and the method based on LCH-based prioritization and the second resource priority processing method is used during reliable transmission.
- a method based on LCH-based prioritization and second resource priority processing is used during normal transmission, and a method based on LCH-based prioritization is used during reliable transmission.
- the normally transmitted MCS may be referred to as the first set of MCS
- the highly reliable transmitted MCS may be referred to as the second set of MCS.
- resource configuration for the highly reliable transmission may be referred to as another resource configuration.
- resource configuration parameters For another example, given two sets of resource configuration parameters, one set is for normal transmission or relaxed transmission, and the other set is for highly reliable transmission.
- the resource configuration parameters for the highly reliable transmission may be referred to as another set of resource configuration parameters.
- LCH mapping restriction for the highly reliable transmission may be referred to as another set of LCH mapping restriction.
- the network may preconfigure the above-mentioned parameters, configurations, resources, etc. corresponding to the highly reliable transmission.
- the UE reserves two sets of parameters, configurations, resources, etc., and uses different parameters, configurations, and resources in different situations (another set of parameters, configurations, and resources are deactivated or suspended).
- determining whether to perform reporting or determining whether to perform a specific transmission includes at least one of the following:
- performing the specific transmission also includes:
- the transmission according to a specific rule includes at least one of the following:
- every X packets or PDCP SDUs are transmitted according to the first rule, and every Y packets or PDCP SDUs are transmitted according to the second rule;
- every X SDUs or PDUs or TBs or PUSCHs are transmitted according to the first rule, and every Y packets or SDUs or PDUs or TBs or PUSCHs are transmitted according to the second rule.
- the values of X and Y can be related to the survival time.
- the first rule and the second rule are interactively processed.
- the survival time is 1, which means that one packet follows the first rule, the next packet follows the second rule, and the next packet follows the first rule.
- the method further includes:
- the interaction mode of the first rule and the second rule is determined according to the duration, order or instruction, and/or it is determined whether the first rule or the second rule is used.
- the processing or processing rules of the packet, PDCP SDU, SDU, PDU, TB or PUSCH are performed or determined based on at least one of PDCP, RLC, MAC, and physical layer PHY.
- which rule to process the X-th or Y-th packet according to may be determined by at least one of PDCP, RLC, MAC, and PHY.
- the PDCP layer determines which PDCP PDU is transmitted to the first RLC entity and which PDCP PDU is transmitted to the second RLC entity.
- the first RLC entity and the second RLC entity correspond to different transmissions (such as normal and high reliability, such as different CG resources, such as different carriers, different transmission priorities), or different transmission parameters (such as LCH mapping parameters, different logical channel mapping restrictions).
- the MAC layer decides which transmission to use (such as normal and high reliability, such as different CG resources, such as different carriers, different transmission priorities, and transmission with different transmission parameters).
- the processing or processing rules of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs are determined according to the arrival order and/or number of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs.
- the terminal device may determine which rule to process the packets according to the order and/or the number of packets arriving.
- the order of arrival of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs is represented by a sequence (SN) number, where the SN number includes at least one of a PDCP SN number and an RLC SN number.
- the relationship between the first rule and the second rule includes at least one of the following:
- the first rule is to select the first RLC entity or the first logical channel
- the second rule is to select the second RLC entity
- the first rule is to select normal transmission or relaxed transmission, and the second rule is to select highly reliable transmission;
- the first rule is to select the first parameter
- the second rule is to select the second parameter.
- the first parameter and/or the second parameter may be resource configuration parameters, LCH configuration parameters, or the like.
- the specific transmission rule is further configured to process when the first information is configured or indicated, and/or to process the object corresponding to the first information.
- the object corresponding to the first information may include bearer, LCH, PDCP, PDU session, IP flow, and the like.
- objects that do not correspond to the first information may not be processed.
- the terminal device performs operations related to the survival time according to the first information, and can specify the processing mechanism related to the survival time. Further, states such as the start and end of the survival time can be controlled more accurately. Further, feedback, reporting, specific transmission, etc. can be performed based on the time-to-live to ensure service transmission performance under severe requirements and avoid resource waste.
- the UE acquires first information, where the first information is used to include relevant information about survival time.
- the first information includes at least one of the following: survival time, DRB identifier, QoS flow identifier, PDU session identifier, service arrival time, service pattern (pattern), service period, related timer configuration, and use of survival time related information Indication information, indication information for performing time-to-live related operations.
- the first information is predefined, or indicated by the access network network, or indicated by the core network.
- the UE may receive indication signaling from the network device, where the indication signaling is used to indicate whether to perform a time-to-live operation, and/or which time-to-live operation to perform.
- the UE performs at least one of the following operations according to the first information:
- a time-to-live is considered to enter or begin when at least one of the following:
- a time-to-live is considered to be entered or started
- a PDCP PDU is considered to be at least one of lost, unsuccessfully received, or transmitted in error, determining the entry or start time-to-live;
- one SDU, one PDU, one TB or one PUSCH is considered to be at least one of lost, unsuccessful reception, transmission error, the entry or start time-to-live is determined.
- entering or starting a time-to-live may be characterized as entering or starting a time-to-live state.
- a first timer is introduced to detect the keepalive time, or to measure whether to enter or start the keepalive time.
- An example is as follows:
- the duration of the first timer is related to the PDB (packet delay budget).
- the duration of the first timer is equal to the 5G-AN PDB.
- the leave or end time-to-live can represent the state of leave or end time-to-live.
- introduce a second timer In the event of entering or starting a time-to-live, or entering or starting a time-to-live state, a second timer is started. Upon leaving or ending the time-to-live state, the second timer is stopped.
- a specific transmission such as a higher reliability transmission.
- step 2 of Example 1 can be replaced with at least one of the following scenarios:
- the first timer is started.
- the ACK is received before the first timer expires, and the first timer is restarted.
- the first timer is stopped. Enter or start a time-to-live, and/or start a second timer.
- time-to-live or time-to-live state, or while the second timer is running, a specific transmission is reported or performed.
- the second timer In the time-to-live, or the time-to-live state, or during the running of the second timer, when an ACK is received, the second timer is stopped, and/or the first timer is started.
- time-to-live In the time-to-live, or time-to-live state, or while the second timer is running, always receive a NACK or no ACK or no feedback, leaving or ending the time-to-live state, or when the second timer expires Next, start the first timer, or trigger a link transmission failure reporting, or initiate RRC connection re-establishment.
- This example clarifies the method of judging the entry and exit or ending survival time, and the processing mechanism related to the survival time.
- Example 2 Give a way to guarantee strict time-to-live requirements. Specifically, reporting or specific transmission is performed when a specific condition is met to ensure a specific survival time.
- the UE acquires first information, where the first information is used to include relevant information of survival time. specific:
- the first information includes at least one of the following: survival time, DRB identifier, QoS flow identifier, PDU session identifier, service arrival time, service pattern (pattern), service period, and related timer configuration.
- the first information is predefined, or indicated by the access network network, or indicated by the core network.
- the UE determines whether to report or perform a specific transmission (eg, perform high-reliability transmission, such as UE-based high-reliability transmission) according to the first information.
- a specific transmission eg, perform high-reliability transmission, such as UE-based high-reliability transmission
- the first condition may be at least one of the following: the time-to-live is a specific value (eg, the time-to-live is 0), the time-to-live is less than the RTT, the time-to-live is less than Y times the RTT, the PDB is less than the RTT, the PDB is less than the service period or the resource period (such as CG or SPS), PDB less than X times RTT, not specific subcarrier spacing, TDD working mode or configuration, refer to or configure jitter.
- the time-to-live is a specific value (eg, the time-to-live is 0)
- the time-to-live is less than the RTT
- the time-to-live is less than Y times the RTT
- the PDB is less than the service period or the resource period (such as CG or SPS)
- PDB less than X times RTT not specific subcarrier spacing, TDD working mode or configuration, refer to or configure jitter.
- X and Y can be
- the UE performs highly reliable transmissions such as:
- the highly reliable transmission may be at least one of the following: performing a replication transmission, performing a repeated transmission, using another set of replication transmission times, using another set of repeated transmission times, using a second set of MCS, using another resource configuration, using another One set of resource configuration parameters, use another set of LCH mapping restrictions, cancel LCH mapping restrictions, use the first set of LCH configuration parameters, use the second set of physical layer transmission parameters, and use the second priority processing method.
- This example provides a method to ensure the survival time or avoid reaching the maximum tolerated packet loss time or number in a specific situation, which ensures the service transmission performance under the strict survival time requirement.
- Example 3 A method of guaranteeing the time-to-live for a specific LCH, CG or HARQ is given, so as to avoid waste of resources while guaranteeing the time-to-live.
- the UE obtains first information, where the first information is used to include survival time related information. specific:
- the first information includes at least one of the following: survival time, DRB identifier, QoS flow identifier, PDU session identifier, service arrival time, service pattern, service period, and related timer configuration.
- the first information is predefined, or indicated by the access network network, or indicated by the core network.
- the network is given, or predefined, the correspondence between Survival time and CG/LCH/HARQ.
- the UE performs reporting or performs specific transmission (eg, performing highly reliable transmission, such as UE-based highly reliable transmission) according to the first information.
- the second condition may include at least one of the following:
- the survival time is bound to the HARQ process
- the second step may include at least one of the following:
- survival time is bound to LCH, LCH and CG have a mapping relationship, and CG is related to HARQ process.
- the terminal device may only perform DFI feedback on the HARQ process corresponding to the time-to-live, and/or report or perform specific transmission. For example, during the running of the second timer or after the CGT times out or the CGRT times out, the reporting is performed or the specific transmission is performed.
- survival time is bound to the HARQ process, and only DFI feedback is performed on the corresponding HARQ process, and/or, specific transmission is reported or performed. For example, during the running of the second timer or after the CGT times out or the CGRT times out, the reporting is performed or the specific transmission is performed.
- the Survival time is bound to the CG, and only DFI feedback is performed on the HARQ process corresponding to the CG, and/or, specific transmission is reported or performed. For example, during the running of the second timer or after the CGT times out or the CGRT times out, the reporting is performed or the specific transmission is performed.
- the UE uses subsequent CG resources, such as the first available CG, to perform specific transmission.
- the UE performs reporting or performs specific transmission for the HARQ process whose DFI is NACK or the corresponding LCH or CG.
- the UE uses subsequent CG resources, such as the first available CG, to perform specific transmissions.
- the highly reliable transmission may include at least one of the following: performing a replication transmission, performing a repetition transmission, using another set of replication transmission times, using another set of repeated transmission times, using a second set of MCS, using another Resource configuration, use another set of resource configuration parameters, use another set of LCH mapping restrictions, cancel LCH mapping restrictions, use the first set of LCH configuration parameters, use the second set of physical layer transmission parameters, and use the second priority processing method.
- This example provides a method to ensure the time-to-live while avoiding wasting resources, which ensures the service transmission performance under strict time-to-live requirements, and avoids excessive occupation of air interface resources.
- performing a specific transmission further includes: transmitting according to a specific rule.
- transmitting according to a specific rule includes at least one of the following:
- every X packets or PDCP SDUs are transmitted according to the first rule, and every Y packets or PDCP SDUs are transmitted according to the second rule;
- every X SDUs or PDUs or TBs or PUSCHs are transmitted according to the first rule, and every Y packets or SDUs or PDUs or TBs or PUSCHs are transmitted according to the second rule.
- the first rule and the second rule are processed interactively.
- the interaction mode of the first rule and the second rule may be determined according to the duration, order or instruction, and/or it may be determined whether to use the first rule or the second rule.
- the processing or processing rule of the packet, PDCP SDU, SDU, PDU, TB or PUSCH is performed or determined based on at least one of PDCP, radio link control RLC, MAC, and physical layer PHY.
- the processing rules of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs are determined according to the order and/or number of arrivals of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs.
- the order of arrival of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs is represented by a sequence SN number, where the SN number includes at least one of a PDCP SN number and an RLC SN number.
- the relationship between the first rule and the second rule includes at least one of the following:
- the first rule is to select the first RLC entity or the first logical channel
- the second rule is to select the second RLC entity
- the first rule is to select normal transmission or relaxed relaxation transmission, and the second rule is to select highly reliable transmission;
- the first rule is to select the first parameter
- the second rule is to select the second parameter
- the specific transmission rule is further configured to process when the first information is configured or indicated, and/or to process the object corresponding to the first information.
- FIG. 4 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application.
- the terminal device 400 may include:
- the processing unit 410 is configured to perform an operation related to the survival time according to the first information, where the first information includes relevant information of the survival time.
- the relevant information of the survival time includes at least one of the following: survival time, data bearer DRB identification, quality of service flow QoS flow identification, packet data unit session PDU session identification, service arrival time, service mode, service period, related Timer configuration, indication information for using time-to-live related information, and indication information for performing operations related to time-to-live.
- the first information is predefined, indicated by the access network network or indicated by the core network.
- the terminal device further includes: a receiving unit 420, configured to receive an indication signaling from a network device, where the indication signaling is used to indicate whether to perform a time-to-live related operation, and/or, Which time-to-live operation to perform.
- a receiving unit 420 configured to receive an indication signaling from a network device, where the indication signaling is used to indicate whether to perform a time-to-live related operation, and/or, Which time-to-live operation to perform.
- the indication signaling includes at least one of radio resource control (RRC), medium access control (MAC), and downlink control information (DCI).
- RRC radio resource control
- MAC medium access control
- DCI downlink control information
- performing operations related to the time-to-live includes at least one of the following:
- determine whether to enter or start a survival time including at least one of the following:
- PDCP Service Data Unit SDU
- SDU Packet Data Convergence Protocol
- a PDCP PDU is considered to be at least one of lost, unsuccessfully received, or transmitted in error, determining the entry or start time-to-live;
- one SDU, one PDU, one TB or one PUSCH is considered to be at least one of lost, unsuccessful reception, transmission error, the entry or start time-to-live is determined.
- entering or starting a time-to-live means entering or starting a time-to-live state.
- the action of determining the timer related to the time-to-live includes:
- a first timer is used to determine whether to enter or start the time-to-live.
- the start condition of the first timer includes at least one of the following:
- a packet or a PDCP SDU arrives at the PDCP layer of the sender
- one packet or one PDCP SDU corresponds to one first timer.
- one SDU, one PDU, one TB or one PUSCH corresponds to one first timer.
- all packets or all PDCP SDUs correspond to a first timer.
- all SDUs, all PDUs, all TBs or all PUSCHs correspond to a first timer.
- all packets of the same object correspond to a first timer.
- each packet of the same object corresponds to a first timer.
- the duration of the first timer is related to a packet delay budget (PDB).
- PDB packet delay budget
- use the first timer to determine whether to enter or start the survival time including:
- NACK non-acknowledgement
- ACK acknowledgment
- determine whether to leave or end the survival time including at least one of the following:
- leaving or ending a time-to-live means leaving or ending a time-to-live state.
- the action of determining the timer related to the survival time further includes at least one of the following:
- start the second timer In the case of entering or starting the time-to-live, or in the case of entering or starting the time-to-live state, start the second timer;
- the second timer is stopped.
- processing unit is further configured to perform at least one of the following steps:
- performing operations related to the survival time further includes at least one of the following:
- performing operations related to the time-to-live further includes at least one of the following:
- the processing unit performs operations related to the survival time, including:
- the terminal device When the first condition is met, the terminal device performs at least one of the following operations according to the first information:
- the first condition includes at least one of the following: the time-to-live is a specific value, the time-to-live is less than the round-trip time RTT, the time-to-live is less than Y times the RTT, the PDB is less than the RTT, the PDB is less than the service period or the resource period, and the PDB is less than X times RTT, not specific subcarrier spacing, TDD operating mode or configuration, indicating or configuring jitter jitter, specific jitter value.
- perform specific transfers including:
- Different transmissions are performed for initial transmission and retransmission of one SDU, one PDU, one TB or one PUSCH.
- different transmissions are performed for the initial transmission and the retransmission, including at least one of the following:
- performing a specific transmission further comprising:
- the same transmission is performed for the initial transmission and retransmission of one SDU, one PDU, one TB or one PUSCH.
- perform the same transmission for the initial transmission and retransmission including:
- the processing unit performs operations related to the survival time, including:
- the terminal device When the second condition is met, the terminal device performs at least one of the following operations according to the first information:
- the first information also includes at least one of the following correspondences:
- the second condition includes at least one of the following:
- the survival time is bound to the HARQ process
- DFI feedback is performed on the HARQ process corresponding to the time-to-live, and/or reporting or specific transmission is performed.
- performing reporting or performing specific transmission also includes at least one of the following:
- the DFI feedback of the HARQ process corresponding to the time-to-live or the DFI feedback to the LCH or CG corresponding to the time-to-live, reporting or specific transmission is performed.
- performing a specific transfer includes:
- a specific transmission is performed using subsequent CG resources.
- performing a specific transfer includes:
- the performing highly reliable transmission includes at least one of the following: performing replication transmission, performing repeated transmission, using another set of replication transmission times, using another set of repeated transmission times, using a second set of modulation and coding strategies MCS, Use another resource configuration, use another set of resource configuration parameters, use another set of LCH mapping restrictions, cancel LCH mapping restrictions, use the first set of LCH configuration parameters, use the second set of physical layer transmission parameters, use the second priority Approach.
- determining whether to perform reporting or determining whether to perform a specific transmission includes at least one of the following:
- performing the specific transmission also includes:
- the transmission according to a specific rule includes at least one of the following:
- every X packets or PDCP SDUs are transmitted according to the first rule, and every Y packets or PDCP SDUs are transmitted according to the second rule;
- every X SDUs or PDUs or TBs or PUSCHs are transmitted according to the first rule, and every Y packets or SDUs or PDUs or TBs or PUSCHs are transmitted according to the second rule.
- the first rule and the second rule are interactively processed.
- processing unit further includes:
- the processing or processing rule of the packet, PDCP SDU, SDU, PDU, TB or PUSCH is performed or determined based on at least one of PDCP, radio link control RLC, MAC, and physical layer PHY.
- the processing or processing rules of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs are determined according to the arrival order and/or number of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs.
- the order of arrival of packets, PDCP SDUs, SDUs, PDUs, TBs or PUSCHs is represented by a sequence SN number, where the SN number includes at least one of a PDCP SN number and an RLC SN number.
- the relationship between the first rule and the second rule includes at least one of the following:
- the first rule is to select the first RLC entity or the first logical channel
- the second rule is to select the second RLC entity
- the first rule is to select normal transmission or relaxed relaxation transmission, and the second rule is to select highly reliable transmission;
- the first rule is to select the first parameter
- the second rule is to select the second parameter
- the specific transmission rule is further configured to process when the first information is configured or indicated, and/or to process the object corresponding to the first information.
- the terminal device 400 in this embodiment of the present application can implement the corresponding functions of the terminal device in the foregoing method embodiments.
- each module (submodule, unit, or component, etc.) in the terminal device 400 reference may be made to the corresponding descriptions in the foregoing method embodiments, which are not repeated here.
- the functions described by each module (submodule, unit, or component, etc.) in the terminal device 400 of the application embodiment may be implemented by different modules (submodule, unit, or component, etc.), or may be implemented by the same module Module (submodule, unit or component, etc.) implementation.
- FIG. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.
- the communication device 600 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so that the communication device 600 implements the methods in the embodiments of the present application.
- the communication device 600 may also include a memory 620 .
- the processor 610 may call and run a computer program from the memory 620, so that the communication device 600 implements the methods in the embodiments of the present application.
- the memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .
- the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices .
- the transceiver 630 may include a transmitter and a receiver.
- the transceiver 630 may further include antennas, and the number of the antennas may be one or more.
- the communication device 600 may be the network device of this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
- the communication device 600 may be a terminal device in this embodiment of the present application, and the communication device 600 may implement corresponding processes implemented by the terminal device in each method in the embodiment of the present application, which is not repeated here for brevity.
- FIG. 7 is a schematic structural diagram of a chip 700 according to an embodiment of the present application.
- the chip 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiments of the present application.
- the chip 700 may further include a memory 720 .
- the processor 710 may call and run a computer program from the memory 720 to implement the method executed by the terminal device or the network device in the embodiment of the present application.
- the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
- the chip 700 may further include an input interface 730 .
- the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
- the chip 700 may further include an output interface 740 .
- the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
- the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
- the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which is not repeated here for brevity.
- Chips applied to network equipment and terminal equipment can be the same chip or different chips.
- the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
- the processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
- DSP digital signal processor
- FPGA field programmable gate array
- ASIC application specific integrated circuit
- the general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.
- the memory mentioned above may be either volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
- Volatile memory may be random access memory (RAM).
- the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
- FIG. 8 is a schematic block diagram of a communication system 800 according to an embodiment of the present application.
- the communication system 800 includes a terminal device 810 and a network device 820 .
- the terminal device 810 is configured to perform an operation related to the time-to-live according to the first information, where the first information includes related information of the time-to-live.
- the network device 820 may send the first information to the terminal device.
- the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method
- the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here.
- the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
- software it can be implemented in whole or in part in the form of a computer program product.
- the computer program product includes one or more computer instructions.
- the computer program instructions When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part.
- the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
- the computer instructions may be stored on or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted over a wire from a website site, computer, server or data center (eg coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to another website site, computer, server or data center.
- the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated.
- the available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)), and the like.
- a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
- an optical medium eg, a DVD
- a semiconductor medium eg, a Solid State Disk (SSD)
- the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (89)
- 一种存活时间的处理方法,包括:终端设备根据第一信息,执行存活时间的相关操作,其中,所述第一信息包括存活时间的相关信息。
- 根据权利要求1所述的方法,其中,所述存活时间的相关信息包括以下至少之一:存活时间、数据承载DRB标识、服务质量流QoS flow标识、分组数据单元会话PDU session标识、业务到达时间、业务模式、业务周期、相关定时器配置、使用存活时间相关信息的指示信息、执行存活时间相关操作的指示信息。
- 根据权利要求1或2所述的方法,其中,所述第一信息为预定义的、接入网网络指示的或核心网指示的。
- 根据权利要求1至3中任一项所述的方法,其中,所述方法还包括:所述终端设备接收来自网络设备的指示信令,所述指示信令用于指示是否执行存活时间的相关操作,和/或,执行哪种存活时间操作。
- 根据权利要求4所述的方法,其中,所述指示信令包括无线资源控制RRC、媒体接入控制MAC、下行控制信息DCI的至少之一。
- 根据权利要求1至5中任一项所述的方法,其中,执行存活时间的相关操作包括以下至少之一:确定是否进入或开始存活时间;确定是否离开或结束存活时间;确定存活时间状态;确定存活时间相关的定时器的动作。
- 根据权利要求6所述的方法,其中,确定是否进入或开始存活时间,包括以下至少之一:在一个包或一个分组数据汇聚协议PDCP业务数据单元SDU被认为丢失、未成功接收、传输错误中的至少之一的情况下,确定进入或开始存活时间;在一个包或一个PDCP SDU到达发送端PDCP层的情况下,确定进入或开始存活时间;在一个包或一个PDCP SDU离开发送端PDCP层的情况下,确定进入或开始存活时间;发送一个包或一个PDCP SDU,确定进入或开始存活时间;发送一个SDU、一个PDU、一个TB或一个PUSCH,确定进入或开始存活时间;在一个PDCP PDU被认为丢失、未成功接收、传输错误中的至少之一的情况下,确定进入或开始存活时间;在一个SDU、一个PDU、一个TB或一个PUSCH被认为丢失、未成功接收、传输错误中的至少之一的情况下,确定进入或开始存活时间。
- 根据权利要求7所述的方法,其中,进入或开始存活时间表示进入或开始存活时间状态。
- 根据权利要求6至8中任一项所述的方法,其中,确定存活时间相关的定时器的动作,包括:利用第一定时器确定是否进入或开始存活时间。
- 根据权利要求9所述的方法,其中,所述第一定时器的开启条件包括以下至少之一:一个包或一个PDCP SDU到达发送端PDCP层;一个包或一个PDCP SDU或一个PDCP PDU离开发送端PDCP层;发送一个包或一个PDCP SDU;发送一个SDU、一个PDU、一个TB或一个PUSCH。
- 根据权利要求9或10所述的方法,其中,所述第一定时器的时长与包时延预算PDB相关。
- 根据权利要求9至11中任一项所述的方法,其中,利用第一定时器确定是否进入或开始存活时间,包括:若在所述第一定时器超时前收到非确认NACK反馈,或,在第一定时器超时前未收到确认ACK反馈,或,在第一定时器超时前未收到反馈,或,在第一定时器超时后,进入或开始存活时间。
- 根据权利要求6所述的方法,其中,确定是否离开或结束存活时间,包括以下至少之一:在进入或开始存活时间或维持在存活时间状态的情况下,若一个包或一个PDCP SDU成功传输,则确定离开或结束存活时间;在进入或开始存活时间或维持在存活时间状态的情况下,若一个SDU、一个PDU、一个TB或一个PUSCH成功传输,则确定离开或结束存活时间;在进入或开始存活时间或维持在存活时间状态的情况下,若收到至少一个包或至少一个PDCP SDU的ACK反馈,则确定离开或结束存活时间;在进入或开始存活时间或维持在存活时间状态的情况下,若收到至少一个SDU、至少一个PDU、至少一个TB或至少一个PUSCH的ACK反馈,则确定离开或结束存活时间。
- 根据权利要求13所述的方法,其中,离开或结束存活时间表示离开或结束存活时间状态。
- 根据权利要求6所述的方法,其中,确定存活时间相关的定时器的动作,还包括以下至少之一:在进入或开始存活时间的情况下,或在进入或开始存活时间状态的情况下,开启第二定时器;在离开或结束存活时间的情况下,或在离开或结束存活时间状态的情况下,停止第二定时器。
- 根据权利要求15所述的方法,其中,所述方法还包括以下至少之一:在第二定时器超时后,或第二定时器超时前没有执行上报或特定传输,则向高层上报问题或触发链路传输失败上报或发起RRC连接重建;在第二定时器超时后,离开或结束存活时间;在第二定时器超时前,若一个包或一个PDCP SDU成功传输,离开或结束存活时间;在第二定时器超时前,若一个SDU、一个PDU、一个TB或一个PUSCH成功传输,离开或结束存活时间;在第二定时器超时前,若收到至少一个包或至少一个PDCP SDU的ACK反馈,离开或结束存活时间;在第二定时器超时前,若收到至少一个SDU、至少一个PDU、至少一个TB或至少一个PUSCH的ACK反馈,离开或结束存活时间。
- 根据权利要求1至16中任一项所述的方法,其中,执行存活时间的相关操作,还包括以下至少之一:在收到ACK反馈的情况下,开启第一定时器;在第一定时器超时前收到ACK反馈,重启第一定时器;在第一定时器超时前未收到ACK反馈或收到NACK反馈或未收到反馈,停止第一定时器,进入或开始存活时间,和/或,开始第二定时器;在第一定时器超时后,进入或开始存活时间,和/或,开始第二定时器;在进入或开始存活时间、维持在存活时间状态下或在第二定时器运行期间,收到ACK反馈,停止第二定时器,和/或,开启第一定时器;在存活时间、存活时间状态下或在第二定时器运行期间,始终收到NACK反馈或未收到ACK反馈或未收到反馈,在离开或结束存活时间状态或在第二定时器超时情况下,开启第一定时器或触发链路传输失败上报或发起RRC连接重建或触发问题上报。
- 根据权利要求1至17中任一项所述的方法,其中,执行存活时间的相关操作还包括以下至少之一:确定是否接收或处理对应的下行反馈指示DFI;确定是否执行上报;确定是否执行特定传输。
- 根据权利要求1至17中任一项所述的方法,其中,终端设备根据第一信息,执行存活时间的相关操作,包括:在满足第一条件的情况下,终端设备根据所述第一信息,执行以下操作的至少之一:确定是否执行上报;确定是否执行特定传输。
- 根据权利要求19所述的方法,其中,所述第一条件包括以下至少之一:存活时间为特定值、存活时间小于往返时间RTT、存活时间小于Y倍的RTT、PDB小于RTT、PDB小于业务周期或资源周期、PDB小于X倍的RTT、不是特定子载波间隔subcarrier spacing、时分双工TDD工作模式或配置、指示或配置抖动jitter、特定jitter值。
- 根据权利要求19或20所述的方法,其中,执行特定传输,包括:对一个包或一个PDCP SDU或一个MAC PDU的初传和重传执行不同的传输;或者对一个SDU、一个PDU、一个TB或一个PUSCH的初传和重传执行不同的传输。
- 根据权利要求21所述的方法,其中,对初传和重传执行不同的传输,包括以下至少之一:对初传和重传至少之一执行高可靠的传输;对至少一次重传执行高可靠的传输;对初传执行高可靠的传输。
- 根据权利要求19或20所述的方法,其中,执行特定传输,还包括:对一个包或一个PDCP SDU或一个MAC PDU的初传和重传执行相同的传输;或者,对一个SDU、一个PDU、一个TB或一个PUSCH的初传和重传执行相同的传输。
- 根据权利要求23所述的方法,其中,对初传和重传执行相同的传输,包括:对初传和重传执行高可靠的传输。
- 根据权利要求1至17中任一项所述的方法,其中,终端设备根据第一信息,执行存活时间的相关操作,包括:在满足第二条件的情况下,终端设备根据所述第一信息,执行以下操作的至少之一:确定是否接收或处理对应的DFI;确定是否执行上报;确定是否执行特定传输。
- 根据权利要求25所述的方法,其中,所述第一信息还包括以下对应关系的至少之一:存活时间与逻辑信道LCH的对应关系;存活时间与混合自动重传请求HARQ的对应关系;存活时间与配置授权CG的对应关系。
- 根据权利要求25或26所述的方法,其中,所述第二条件包括以下至少之一:存活时间和LCH绑定;存活时间和HARQ进程绑定;存活时间和CG绑定。
- 根据权利要求25至27中任一项所述的方法,其中,执行上报或执行特定传输,包括:对存活时间对应的HARQ进程进行DFI反馈,和/或,执行上报或执行特定传输。
- 根据权利要求25至28中任一项所述的方法,其中,执行上报或执行特定传输,还包括以下至少之一:在接收到DFI的情况下,对DFI为NACK的HARQ进程或对应的LCH或CG,执行上报或执行特定传输;对存活时间对应的HARQ进程的DFI反馈或对存活时间对应的LCH或CG的DFI反馈,执行上报或执行特定传输。
- 根据权利要求25至29中任一项所述的方法,其中,执行特定传输包括:使用后续CG资源执行特定传输。
- 根据权利要求25至30中任一项所述的方法,其中,执行特定传输包括:执行高可靠的传输。
- 根据权利要求22、24或31所述的方法,其中,所述执行高可靠的传输包括以下至少之一:执行复制传输、执行重复传输、使用另一套复制传输次数、使用另一套重复传输次数、使用第二套调制与编码策略MCS、使用另一个资源配置、使用另一套资源配置参数、使用另一套LCH映射限制、取消LCH映射限制、使用第一套LCH配置参数、使用第二套物理层传输参数、使用第二种优先级处理方法。
- 根据权利要求18至32中任一项所述的方法,其中,确定是否执行上报或确定是否执行特定传输,包括以下至少之一:在进入或开始存活时间的情况下,执行上报或执行特定传输;在第二定时器超时前,执行上报或执行特定传输;在进入或开始存活时间,执行上报或执行特定传输;在维持在存活时间状态下,执行上报或执行特定传输;在第二定时器运行期间,执行上报或执行特定传输。
- 根据权利要求18至33中任一项所述的方法,其中,执行特定传输还包括:按照特定规则传输。
- 根据权利要求34所述的方法,其中,按照特定规则传输包括以下至少之一:对一个对象,每X个包或PDCP SDU按照第一规则传输,每Y个包或PDCP SDU按照第二规则传输;对一个对象,每X个SDU或PDU或TB或PUSCH按照第一规则传输,每Y个包或SDU或PDU或TB或PUSCH按照第二规则传输。
- 根据权利要求35所述的方法,其中,所述第一规则和第二规则是交互处理的。
- 根据权利要求36所述的方法,其中,所述方法还包括:按照时长、顺序或指示,确定所述第一规则和第二规则的交互方式,和/或,确定使用第一规则还是第二规则。
- 根据权利要求35至37中任一项所述的方法,其中,包、PDCP SDU、SDU、PDU、TB或PUSCH的处理或处理规则,基于PDCP、无线链路控制RLC、MAC、物理层PHY的至少之一执行或确定。
- 根据权利要求35至37中任一项所述的方法,其中,包、PDCP SDU、SDU、PDU、TB或PUSCH的处理或处理规则,按照包、PDCP SDU、SDU、PDU、TB或PUSCH到达的顺序和/或个数确定。
- 根据权利要求35至39中任一项所述的方法,其中,包、PDCP SDU、SDU、PDU、TB或PUSCH到达的顺序采用序列SN号来表示,所述SN号包括PDCP SN号、RLC SN号的至少之一。
- 根据权利要求35至40中任一项所述的方法,其中,所述第一规则和所述第二规则的关系包括以下至少之一:所述第一规则为选第一RLC实体或第一逻辑信道,所述第二规则为选第二RLC实体;所述第一规则为选正常传输或放松relax传输,所述第二规则为选高可靠的传输;所述第一规则为选第一参数,所述第二规则为选第二参数。
- 根据权利要求35至40中任一项所述的方法,其中,所述特定传输规则还用于在配置或指示所述第一信息的情况下处理,和/或,对所述第一信息对应的对象进行处理。
- 一种终端设备,包括:处理单元,用于根据第一信息,执行存活时间的相关操作,其中,所述第一信息包括存活时间的相关信息。
- 根据权利要求43所述的终端设备,其中,所述存活时间的相关信息包括以下至少之一:存活时间、数据承载DRB标识、服务质量流QoS flow标识、分组数据单元会话PDU session标识、业务到达时间、业务模式、业务周期、相关定时器配置、使用存活时间相关信息的指示信息、执行存活时间相关操作的指示信息。
- 根据权利要求43或44所述的终端设备,其中,所述第一信息为预定义的、接入网网络指示的或核心网指示的。
- 根据权利要求43至45中任一项所述的终端设备,其中,所述终端设备还包括:接收单元,用于接收来自网络设备的指示信令,所述指示信令用于指示是否执行存活时间的相关操作,和/或,执行哪种存活时间操作。
- 根据权利要求46所述的终端设备,其中,所述指示信令包括无线资源控制RRC、媒体接入控制MAC、下行控制信息DCI的至少之一。
- 根据权利要求43至47中任一项所述的终端设备,其中,执行存活时间的相关操作包括以下至少之一:确定是否进入或开始存活时间;确定是否离开或结束存活时间;确定存活时间状态;确定存活时间相关的定时器的动作。
- 根据权利要求48所述的终端设备,其中,确定是否进入或开始存活时间,包括以下至少之一:在一个包或一个分组数据汇聚协议PDCP业务数据单元SDU被认为丢失、未成功接收、传输错误中的至少之一的情况下,确定进入或开始存活时间;在一个包或一个PDCP SDU到达发送端PDCP层的情况下,确定进入或开始存活时间;在一个包或一个PDCP SDU离开发送端PDCP层的情况下,确定进入或开始存活时间;发送一个包或一个PDCP SDU,确定进入或开始存活时间;发送一个SDU、一个PDU、一个TB或一个PUSCH,确定进入或开始存活时间;在一个PDCP PDU被认为丢失、未成功接收、传输错误中的至少之一的情况下,确定进入或开始存活时间;在一个SDU、一个PDU、一个TB或一个PUSCH被认为丢失、未成功接收、传输错误中的至少之一的情况下,确定进入或开始存活时间。
- 根据权利要求49所述的终端设备,其中,进入或开始存活时间表示进入或开始存活时间状态。
- 根据权利要求48至50中任一项所述的终端设备,其中,确定存活时间相关的定时器的动作,包括:利用第一定时器确定是否进入或开始存活时间。
- 根据权利要求51所述的终端设备,其中,所述第一定时器的开启条件包括以下至少之一:一个包或一个PDCP SDU到达发送端PDCP层;一个包或一个PDCP SDU或一个PDCP PDU离开发送端PDCP层;发送一个包或一个PDCP SDU;发送一个SDU、一个PDU、一个TB或一个PUSCH。
- 根据权利要求51或52所述的终端设备,其中,所述第一定时器的时长与包时延预算PDB相关。
- 根据权利要求51至53中任一项所述的终端设备,其中,利用第一定时器确定是否进入或开始存活时间,包括:若在所述第一定时器超时前收到非确认NACK反馈,或,在第一定时器超时前未收到确认ACK反馈,或,在第一定时器超时前未收到反馈,或,在第一定时器超时后,进入或开始存活时间。
- 根据权利要求48所述的终端设备,其中,确定是否离开或结束存活时间,包括以下至少之一:在进入或开始存活时间或维持在存活时间状态的情况下,若一个包或一个PDCP SDU成功传输,则确定离开或结束存活时间;在进入或开始存活时间或维持在存活时间状态的情况下,若一个SDU、一个PDU、一个TB或一个PUSCH成功传输,则确定离开或结束存活时间;在进入或开始存活时间或维持在存活时间状态的情况下,若收到至少一个包或至少一个PDCP SDU的ACK反馈,则确定离开或结束存活时间;在进入或开始存活时间或维持在存活时间状态的情况下,若收到至少一个SDU、至少一个PDU、至少一个TB或至少一个PUSCH的ACK反馈,则确定离开或结束存活时间。
- 根据权利要求55所述的终端设备,其中,离开或结束存活时间表示离开或结束存活时间状态。
- 根据权利要求48所述的终端设备,其中,确定存活时间相关的定时器的动作,还包括以下至少之一:在进入或开始存活时间的情况下,或在进入或开始存活时间状态的情况下,开启第二定时器;在离开或结束存活时间的情况下,或在离开或结束存活时间状态的情况下,停止第二定时器。
- 根据权利要求57所述的终端设备,其中,所述处理单元还用于执行以下步骤的至少之一:在第二定时器超时后,或第二定时器超时前没有执行上报或特定传输,则向高层上报问题或触发链路传输失败上报或发起RRC连接重建;在第二定时器超时后,离开或结束存活时间;在第二定时器超时前,若一个包或一个PDCP SDU成功传输,离开或结束存活时间;在第二定时器超时前,若一个SDU、一个PDU、一个TB或一个PUSCH成功传输,离开或结束存活时间;在第二定时器超时前,若收到至少一个包或至少一个PDCP SDU的ACK反馈,离开或结束存活时间;在第二定时器超时前,若收到至少一个SDU、至少一个PDU、至少一个TB或至少一个PUSCH的ACK反馈,离开或结束存活时间。
- 根据权利要求43至58中任一项所述的终端设备,其中,执行存活时间的相关操作,还包括以下至少之一:在收到ACK反馈的情况下,开启第一定时器;在第一定时器超时前收到ACK反馈,重启第一定时器;在第一定时器超时前未收到ACK反馈或收到NACK反馈或未收到反馈,停止第一定时器,进入或开始存活时间,和/或,开始第二定时器;在第一定时器超时后,进入或开始存活时间,和/或,开始第二定时器;在进入或开始存活时间、维持在存活时间状态下或在第二定时器运行期间,收到ACK反馈,停止第二定时器,和/或,开启第一定时器;在存活时间、存活时间状态下或在第二定时器运行期间,始终收到NACK反馈或未收到ACK反馈或未收到反馈,在离开或结束存活时间状态或在第二定时器超时情况下,开启第一定时器或触发链路传输失败上报或发起RRC连接重建或触发问题上报。
- 根据权利要求43至59中任一项所述的终端设备,其中,执行存活时间的相关操作还包括以下至少之一:确定是否接收或处理对应的下行反馈指示DFI;确定是否执行上报;确定是否执行特定传输。
- 根据权利要求43至59中任一项所述的终端设备,其中,所述处理单元根据第一信息,执行存活时间的相关操作,包括:在满足第一条件的情况下,终端设备根据所述第一信息,执行以下操作的至少之一:确定是否执行上报;确定是否执行特定传输。
- 根据权利要求61所述的终端设备,其中,所述第一条件包括以下至少之一:存活时间为特定值、存活时间小于往返时间RTT、存活时间小于Y倍的RTT、PDB小于RTT、PDB小于业务周期或资源周期、PDB小于X倍的RTT、不是特定子载波间隔subcarrier spacing、TDD工作模式或配置、指示或配置抖动jitter、特定jitter值。
- 根据权利要求61或62所述的终端设备,其中,执行特定传输,包括:对一个包或一个PDCP SDU或一个MAC PDU的初传和重传执行不同的传输;或者对一个SDU、一个PDU、一个TB或一个PUSCH的初传和重传执行不同的传输。
- 根据权利要求63所述的终端设备,其中,对初传和重传执行不同的传输,包括以下至少之一:对初传和重传至少之一执行高可靠的传输;对至少一次重传执行高可靠的传输;对初传执行高可靠的传输。
- 根据权利要求61或62所述的终端设备,其中,执行特定传输,还包括:对一个包或一个PDCP SDU或一个MAC PDU的初传和重传执行相同的传输;或者,对一个SDU、一个PDU、一个TB或一个PUSCH的初传和重传执行相同的传输。
- 根据权利要求65所述的终端设备,其中,对初传和重传执行相同的传输,包括:对初传和重传执行高可靠的传输。
- 根据权利要求43至59中任一项所述的终端设备,其中,所述处理单元根据第一信息,执行存活时间的相关操作,包括:在满足第二条件的情况下,终端设备根据所述第一信息,执行以下操作的至少之一:确定是否接收或处理对应的DFI;确定是否执行上报;确定是否执行特定传输。
- 根据权利要求67所述的终端设备,其中,所述第一信息还包括以下对应关系的至少之一:存活时间与逻辑信道LCH的对应关系;存活时间与混合自动重传请求HARQ的对应关系;存活时间与配置授权CG的对应关系。
- 根据权利要求67或68所述的终端设备,其中,所述第二条件包括以下至少之一:存活时间和LCH绑定;存活时间和HARQ进程绑定;存活时间和CG绑定。
- 根据权利要求67至69中任一项所述的终端设备,其中,执行上报或执行特定传输,包括:对存活时间对应的HARQ进程进行DFI反馈,和/或,执行上报或执行特定传输。
- 根据权利要求67至70中任一项所述的终端设备,其中,执行上报或执行特定传输,还包括以下至少之一:在接收到DFI的情况下,对DFI为NACK的HARQ进程或对应的LCH或CG,执行上报或执行特定传输;对存活时间对应的HARQ进程的DFI反馈或对存活时间对应的LCH或CG的DFI反馈,执行上报 或执行特定传输。
- 根据权利要求67至71中任一项所述的终端设备,其中,执行特定传输包括:使用后续CG资源执行特定传输。
- 根据权利要求67至72中任一项所述的终端设备,其中,执行特定传输包括:执行高可靠的传输。
- 根据权利要求64、66或73所述的终端设备,其中,所述执行高可靠的传输包括以下至少之一:执行复制传输、执行重复传输、使用另一套复制传输次数、使用另一套重复传输次数、使用第二套调制与编码策略MCS、使用另一个资源配置、使用另一套资源配置参数、使用另一套LCH映射限制、取消LCH映射限制、使用第一套LCH配置参数、使用第二套物理层传输参数、使用第二种优先级处理方法。
- 根据权利要求60至74中任一项所述的终端设备,其中,确定是否执行上报或确定是否执行特定传输,包括以下至少之一:在进入或开始存活时间的情况下,执行上报或执行特定传输;在第二定时器超时前,执行上报或执行特定传输;在进入或开始存活时间,执行上报或执行特定传输;在维持在存活时间状态下,执行上报或执行特定传输;在第二定时器运行期间,执行上报或执行特定传输。
- 根据权利要求60至75中任一项所述的终端设备,其中,执行特定传输还包括:按照特定规则传输。
- 根据权利要求76所述的终端设备,其中,按照特定规则传输包括以下至少之一:对一个对象,每X个包或PDCP SDU按照第一规则传输,每Y个包或PDCP SDU按照第二规则传输;对一个对象,每X个SDU或PDU或TB或PUSCH按照第一规则传输,每Y个包或SDU或PDU或TB或PUSCH按照第二规则传输。
- 根据权利要求77所述的终端设备,其中,所述第一规则和第二规则是交互处理的。
- 根据权利要求78所述的终端设备,其中,还包括:按照时长、顺序或指示,确定所述第一规则和第二规则的交互方式,和/或,确定使用第一规则还是第二规则。
- 根据权利要求77至79中任一项所述的终端设备,其中,包、PDCP SDU、SDU、PDU、TB或PUSCH的处理或处理规则,基于PDCP、无线链路控制RLC、MAC、物理层PHY的至少之一执行或确定。
- 根据权利要求77至79中任一项所述的终端设备,其中,包、PDCP SDU、SDU、PDU、TB或PUSCH的处理或处理规则,按照包、PDCP SDU、SDU、PDU、TB或PUSCH到达的顺序和/或个数确定。
- 根据权利要求77至81中任一项所述的终端设备,其中,包、PDCP SDU、SDU、PDU、TB或PUSCH到达的顺序采用序列SN号来表示,所述SN号包括PDCP SN号、RLC SN号的至少之一。
- 根据权利要求77至82中任一项所述的终端设备,其中,所述第一规则和所述第二规则的关系包括以下至少之一:所述第一规则为选第一RLC实体或第一逻辑信道,所述第二规则为选第二RLC实体;所述第一规则为选正常传输或放松relax传输,所述第二规则为选高可靠的传输;所述第一规则为选第一参数,所述第二规则为选第二参数。
- 根据权利要求77至82中任一项所述的终端设备,其中,所述特定传输规则还用于在配置或指示所述第一信息的情况下处理,和/或,对所述第一信息对应的对象进行处理。
- 一种终端设备,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,以使所述终端设备执行如权利要求1至42中任一项所述的方法。
- 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至42中任一项所述的方法。
- 一种计算机可读存储介质,用于存储计算机程序,当所述计算机程序被设备运行时使得所述设备执行如权利要求1至42中任一项所述的方法。
- 一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至42中任一项所述的方法。
- 一种计算机程序,所述计算机程序使得计算机执行如权利要求1至42中任一项所述的方法。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP21933679.9A EP4290794A4 (en) | 2021-03-30 | 2021-03-30 | SURVIVAL TIME PROCESSING METHOD AND TERMINAL DEVICE |
PCT/CN2021/084137 WO2022204999A1 (zh) | 2021-03-30 | 2021-03-30 | 存活时间的处理方法和终端设备 |
CN202180093304.5A CN116868530A (zh) | 2021-03-30 | 2021-03-30 | 存活时间的处理方法和终端设备 |
CN202311386751.7A CN117222056A (zh) | 2021-03-30 | 2021-03-30 | 存活时间的处理方法和终端设备 |
US18/243,886 US20230421312A1 (en) | 2021-03-30 | 2023-09-08 | Survival time processing method, and terminal device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2021/084137 WO2022204999A1 (zh) | 2021-03-30 | 2021-03-30 | 存活时间的处理方法和终端设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/243,886 Continuation US20230421312A1 (en) | 2021-03-30 | 2023-09-08 | Survival time processing method, and terminal device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022204999A1 true WO2022204999A1 (zh) | 2022-10-06 |
Family
ID=83455421
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/084137 WO2022204999A1 (zh) | 2021-03-30 | 2021-03-30 | 存活时间的处理方法和终端设备 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20230421312A1 (zh) |
EP (1) | EP4290794A4 (zh) |
CN (2) | CN116868530A (zh) |
WO (1) | WO2022204999A1 (zh) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111327404A (zh) * | 2018-12-13 | 2020-06-23 | 电信科学技术研究院有限公司 | 业务生存期处理方法及装置 |
WO2021002873A1 (en) * | 2019-07-03 | 2021-01-07 | Nokia Technologies Oy | Selective packet duplication or alternative packet transmission based on survival time |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111432440B (zh) * | 2019-01-10 | 2022-12-13 | 华为技术有限公司 | 实现业务连续性的方法、装置及系统 |
-
2021
- 2021-03-30 CN CN202180093304.5A patent/CN116868530A/zh active Pending
- 2021-03-30 EP EP21933679.9A patent/EP4290794A4/en active Pending
- 2021-03-30 WO PCT/CN2021/084137 patent/WO2022204999A1/zh active Application Filing
- 2021-03-30 CN CN202311386751.7A patent/CN117222056A/zh active Pending
-
2023
- 2023-09-08 US US18/243,886 patent/US20230421312A1/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111327404A (zh) * | 2018-12-13 | 2020-06-23 | 电信科学技术研究院有限公司 | 业务生存期处理方法及装置 |
WO2021002873A1 (en) * | 2019-07-03 | 2021-01-07 | Nokia Technologies Oy | Selective packet duplication or alternative packet transmission based on survival time |
Non-Patent Citations (4)
Title |
---|
LENOVO, MOTOROLA MOBILITY: "Details of Selective Duplication Procedure", 3GPP DRAFT; R2-1906731, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 2 May 2019 (2019-05-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051711037 * |
See also references of EP4290794A4 * |
VIVO: "Discussion on RAN enhancement to support survival time", 3GPP DRAFT; R2-2100831, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973928 * |
ZTE CORPORATION, SANECHIPS, CHINA SOUTHERN POWER GRID CO., LTD: "Further considerations on new QoS", 3GPP DRAFT; R2-2100328, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-meeting; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973520 * |
Also Published As
Publication number | Publication date |
---|---|
CN117222056A (zh) | 2023-12-12 |
CN116868530A (zh) | 2023-10-10 |
US20230421312A1 (en) | 2023-12-28 |
EP4290794A4 (en) | 2024-04-10 |
EP4290794A1 (en) | 2023-12-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107113291B (zh) | 演进的数据压缩方案信令 | |
US9867146B2 (en) | Systems and methods for dual-connectivity operation | |
US10433205B2 (en) | Network node, method therein, computer program, and carrier comprising the computer program for retransmitting an RLC PDU | |
EP3295735B1 (en) | Method and apparatus for control information transmission | |
WO2016127666A1 (zh) | 一种rlc数据包分流方法及基站 | |
WO2019137641A1 (en) | Submitting a pdcp pdu for transmission | |
WO2022006914A1 (zh) | 混合自动重传请求应答harq-ack的反馈方法和终端设备 | |
US20240154715A1 (en) | Wireless communication method and apparatus | |
CN114788204B (zh) | Harq进程的状态确定方法、装置及设备 | |
WO2022021007A1 (zh) | 无线通信方法、终端设备和网络设备 | |
US20230261801A1 (en) | Communication method and device | |
TW201347587A (zh) | 處理分時雙工系統中資源配置的方法及其通訊裝置 | |
WO2024103798A1 (zh) | 无线通信的方法及装置 | |
US20210298123A1 (en) | Wireless communication system, transmission and reception method, recording medium, wireless communication base station device, control circuit, and control method | |
WO2022204999A1 (zh) | 存活时间的处理方法和终端设备 | |
WO2022155821A1 (zh) | 无线通信的方法及设备 | |
WO2022099555A1 (zh) | 无线通信的方法、终端设备和网络设备 | |
WO2022006724A1 (zh) | 用于关闭harq重传的处理方法、终端设备和网络设备 | |
CN110891326B (zh) | 一种控制面连接重建方法、通信设备、目标基站及源基站 | |
TW202131740A (zh) | 用於處理實體上鏈路控制通道碰撞的裝置及方法 | |
WO2021068224A1 (zh) | 无线通信方法、终端设备和网络设备 | |
CN116711247A (zh) | 数据传输方法及通信装置 | |
WO2022021021A1 (zh) | 无线通信方法、终端设备和网络设备 | |
CN115277608B (zh) | 无线通信的方法及设备 | |
WO2022041125A1 (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: 21933679 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180093304.5 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021933679 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2021933679 Country of ref document: EP Effective date: 20230908 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |