[go: up one dir, main page]

WO2025156230A1 - Procédé pour un nouveau type de transmission de données dans un réseau sans fil - Google Patents

Procédé pour un nouveau type de transmission de données dans un réseau sans fil

Info

Publication number
WO2025156230A1
WO2025156230A1 PCT/CN2024/074125 CN2024074125W WO2025156230A1 WO 2025156230 A1 WO2025156230 A1 WO 2025156230A1 CN 2024074125 W CN2024074125 W CN 2024074125W WO 2025156230 A1 WO2025156230 A1 WO 2025156230A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
transmission
mac
grant
assignment
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/074125
Other languages
English (en)
Inventor
Fei DONG
He Huang
Jing Liu
Nan Zhang
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2024/074125 priority Critical patent/WO2025156230A1/fr
Publication of WO2025156230A1 publication Critical patent/WO2025156230A1/fr
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/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS

Definitions

  • This disclosure is directed generally to wireless communication networks and particularly to network architectures for effectuating a new type data transmission or communication in the wireless communication networks.
  • Legacy wireless communication systems are suitable for faithfully transmitting source information in forms of a collection of physical bits or symbols through various network protocol levels, error correction mechanisms, and transmission and retransmission schemes. For some source information, its faithful transmission may not be necessary.
  • a new type data transmission or communication methodology may be adopted for transmitting such error-tolerant information. For example, such a new type data transmission may be implemented to communicate such source information semantically.
  • This disclosure is directed generally to wireless communication networks and particularly to network architectures for effectuating a new type data transmission or communication for information with transmission error-tolerance, such as semantic communication.
  • a new type data transmission or communication for information with transmission error-tolerance, such as semantic communication.
  • several aspects in wireless network architecture and signaling are disclosed for realizing the new type data transmission between a wireless terminal and a wireless network.
  • Modification to legacy wireless systems are implemented in order to accommodate source encoder/decoder models, their management, and their activation/deactivation based on model performances and network channel conditions.
  • Data within such a new type data communication may be bifurcated into error-free data and error-tolerant data which may be processed distinctively by the modified wireless network.
  • a method performed by a wireless terminal in communication with a wireless network may include receiving a configuration signaling from the wireless network for a data communication comprising one of an uplink (UL) data transmission or a downlink (DL) data reception; receiving a resource configuration comprising one of a UL grant or a DL assignment for the data communication; determining a data communication type of the data communication based on the at least one of the resource configuration or the configuration signaling; and performing the data communication according to the data communication type.
  • UL uplink
  • DL downlink
  • the data communication type comprises one of guaranteed communication type or non-guaranteed communication type.
  • the data communication type is determine based on the configuration signaling according to at least one of following information items of the configuration signaling: a first indication configured for a logical channel, a radio bearer, or a QoS flow for indicating whether data from the logical channel, the radio bearer, or the QoS flow is for the guaranteed communication type or the non-guaranteed communication type; a second indication configured for a serving cell for the wireless terminal for indicating whether the UL grant or the DL assignment for the serving cell is for the guaranteed communication type or the non-guaranteed communication type; a third indication configured for a PDCCH timing or frequency location associated with the UL grant or the DL assignment for indicating whether the UL grant or the DL assignment is for the guaranteed communication type or the non-guaranteed communication type; a fifth indication configured for a HARQ process associated with the UL grant or the DL assignment for indicating whether the UL grant or the DL assignment for the HARQ process is for associated with the UL
  • the data communication type is determined based on the UL grant or the DL assignment according to at least one of: a serving cell and/or Bandwidth Part (BWP) which the UL grant or DL assignment is for; a specific cell defined UE identity (CRNTI) that addresses the UL grant or the DL assignment; a specific timing location or frequency location of a PDCCH in which the UL grant or the DL assignment is received; an indication in a PDCCH for the UL grant or the DL assignment for indicating the data communication type; or a Hybrid Automatic Repeat Request (HARQ) process associated with the UL grant or the DL assignment implicitly indicating that the UL grant or the DL assignment is to be considered by the wireless terminal as indicating the data communication type.
  • BWP Bandwidth Part
  • CNTI cell defined UE identity
  • HARQ Hybrid Automatic Repeat Request
  • performing the UL data transmission according to the data communication type comprises: determining a restriction factor of a logic channel for the UL data transmission based on the data communication type; and multiplexing UL data of the logic channel according to the restriction factor.
  • performing the DL data reception according to the data communication type comprises: performing at least one Cyclic Redundancy Check (CRC) of the DL data reception when the data communication type is of the guaranteed communication type; and performing no CRC of the DL data reception when the data communication type is of the non-guaranteed communication type.
  • CRC Cyclic Redundancy Check
  • the data communication type comprises one of a new data transmission or a data re-transmission.
  • the data communication comprises the UL data transmission
  • performing the UL data transmission comprises: composing a MAC PDU for transmission when the UL data transmission is of the data communication type of new transmission; or performing a re-transmission when the UL data transmission is of the data communication type of re-transmission and a non-acknowledgement (NACK) for a HARQ process identifier associated with the UL grant is received.
  • NACK non-acknowledgement
  • the NACK is indicated via at least one of a PDCCH or a PDSCH.
  • the MAC PDU comprises multiple MAC subPDUs and wherein: at least one of the multiple MAC subPDUs has CRC information; and at least one of the multiple MAC subPDUs has no CRC information.
  • the at least one of the multiple MAC subPDUs that has CRC information comprises at least one of: a MAC CE; a MAC subSDU associated with an LCH that is associated with a Signal Radio Bearer (SRB) or a Data Radio Bearer (DRB) allowing for only guaranteed transmission; or a MAC subSDU corresponding to a control signaling from an upper layer.
  • a MAC CE a MAC subSDU associated with an LCH that is associated with a Signal Radio Bearer (SRB) or a Data Radio Bearer (DRB) allowing for only guaranteed transmission
  • SRB Signal Radio Bearer
  • DRB Data Radio Bearer
  • At least one bit in a subheader of the MAC subSDU is included to indicate whether the CRC information is attached; or the CRC information is included in a sub-header to each MAC subSDU that requires CRC.
  • the data communication comprises the UL data transmission and the data communication type comprises data re-transmission; and performing the data re-transmission comprises: re-transmitting a MAC PDU, a MAC SDU, a MAC CE, or a MAC subPDU where CRC information is attached; re-transmitting the MAC PDU, a MAC SDU, a MAC CE, or a MAC subPDU when indicated by a NACK; or re-transmitting an entire MAC PDU when receiving a NACK.
  • the data communication comprises the UL data transmission;
  • the resource configuration comprises the UL grant;
  • determining the data communication type comprises: determining whether the data communication is a semantic communication; and when the data communication is a semantic communication, determining whether the data communication is a new transmission or a re-transmission; when the data communication is a semantic communication and is a new transmission, generating at least one MAC PDUs for the UL data transmission and deliver a Transport Block (TB) associated with the at least one MAC PDU to a HARQ process for semantic transmission; and when the data communication is a re-transmission, delivering the UL grant and HARQ information for the TB to the HARQ process for re-transmission.
  • TB Transport Block
  • the at least one MAC PDUs comprises one MAC PDU that is separated into at least two sub-TBs, a first sub-TB of the at least two sub-TBs is transmitted error-free whereas a second sub-TB is transmitted with error-tolerance.
  • the first sub-TB contains communication protocol headers and the second sub-TB contains data blocks.
  • the at least one MAC PDUs comprises one MAC PDU that is separated into at least two MAC subSDUs, a first MAC subSDU containing communication protocol headers whereas a second MAC subSDU containing data blocks.
  • the at least one MAC PDUs comprises one MAC PDU, a header portion of the one MAC PDU is transmitted error-free whereas a payload portion of the MAC PDU is transmitted with error-tolerance.
  • the data communication comprises the DL data reception; the resource configuration comprises the DL assignment; determining the data communication type comprises determining whether the data communication is a semantic communication; and when the data communication is a semantic communication, receiving communication header information of the data communication via an error-free decoding process and receiving data information of the data communication via an error-tolerant decoding process.
  • the data communication type is performed by a MAC entity in the wireless terminal.
  • a method performed by a network node in communication with a wireless terminal in a wireless network may include transmitting a configuration signaling from for a data communication comprising one of an uplink (UL) data transmission or a downlink (DL) data reception to the wireless terminal; transmitting a resource configuration comprising one of a UL grant or a DL assignment for the data communication to the wireless terminal to enable the wireless terminal to determine a data communication type of the data communication based on the at least one of the resource configuration or the configuration signaling; and performing the data communication with the wireless terminal according to the data communication type.
  • UL uplink
  • DL downlink
  • the data communication type comprises one of guaranteed communication type or non-guaranteed communication type.
  • the data communication type is determine based on the configuration signaling according to at least one of following information items of the configuration signaling: a first indication configured for a logical channel, a radio bearer, or a QoS flow for indicating whether data from the logical channel, the radio bearer, or the QoS flow is for the guaranteed communication type or the non-guaranteed communication type; a second indication configured for a serving cell for the wireless terminal for indicating whether the UL grant or the DL assignment for the serving cell is for the guaranteed communication type or the non-guaranteed communication type; a third indication configured for a PDCCH timing or frequency location associated with the UL grant or the DL assignment for indicating whether the UL grant or the DL assignment is for the guaranteed communication type or the non-guaranteed communication type; a fifth indication configured for a HARQ process associated with the UL grant or the DL assignment for indicating whether the UL grant or the DL assignment for the HARQ process is for associated with the UL
  • the data communication type is determined based on the UL grant or the DL assignment according to at least one of: a serving cell and/or Bandwidth Part (BWP) which the UL grant or DL assignment is for; a specific cell defined UE identity (CRNTI) that addresses the UL grant or the DL assignment; a specific timing location or frequency location of a PDCCH in which the UL grant or the DL assignment is received; an indication in a PDCCH for the UL grant or the DL assignment for indicating the data communication type; or a Hybrid Automatic Repeat Request (HARQ) process associated with the UL grant or the DL assignment implicitly indicating that the UL grant or the DL assignment is to be considered by the wireless terminal as indicating the data communication type.
  • BWP Bandwidth Part
  • CNTI cell defined UE identity
  • HARQ Hybrid Automatic Repeat Request
  • performing the DL data reception according to the data communication type comprises: performing at least one Cyclic Redundancy Check (CRC) of the DL data reception when the data communication type is of the guaranteed communication type; and performing no CRC of the DL data reception when the data communication type is of the non-guaranteed communication type.
  • CRC Cyclic Redundancy Check
  • the data communication type comprises one of a new data transmission or a data re-transmission.
  • the data communication comprises the DL data reception; the resource configuration comprises the DL assignment; determining the data communication type comprises determining whether the data communication is a semantic communication; and when the data communication is a semantic communication, receiving communication header information of the data communication via an error-free decoding process and receiving data information of the data communication via an error-tolerant decoding process.
  • the wireless terminal or network node of any one of the methods above is disclosed.
  • the wireless terminal or network node may include a processor and a memory, wherein the processor is configured to read computer code from the memory to cause the wireless terminal or network node to perform the method of any one of the methods above.
  • a non-transitory computer-readable program medium with computer code stored thereupon is further disclosed.
  • the computer code when executed by a processor of the wireless terminal or network node of any one of the methods above, is configured to cause the processor to implement any one of the methods above.
  • FIG. 1 illustrates an example wireless communication network including a wireless access network, a core network, and data networks.
  • FIG. 2 illustrates an example wireless access network including a plurality of mobile stations/terminals or User Equipments (UEs) and a wireless access network node in communication with one another via an over-the-air radio communication interface.
  • UEs User Equipments
  • FIG. 3 shows an example radio access network (RAN) architecture.
  • RAN radio access network
  • FIG. 4 shows an example communication protocol stack in a wireless access network node or wireless terminal device including various network layers.
  • FIG. 5 illustrates an example architecture for wireless semantic communication.
  • FIG. 6 illustrates another example architecture for wireless semantic communication.
  • FIG. 7 illustrates an example procedure for configuring and managing semantic models for wireless semantic communication.
  • FIG. 8 illustrates another example procedure for configuring and managing semantic models for wireless semantic communication.
  • FIG. 9 illustrates another example architecture for wireless semantic communication.
  • FIG. 10 illustrates another example procedure for configuring and managing semantic models for wireless semantic communication.
  • FIG. 11 illustrates another example procedure for configuring and managing semantic models for wireless semantic communication.
  • FIG. 12 illustrates an example procedure for data flow control for semantic communication.
  • FIG. 13 illustrates another example procedure for data flow control for semantic communication.
  • FIG. 14 illustrates an example procedure for uplink and downlink semantic transmission.
  • FIG. 15 illustrates an example protocol header configuration
  • FIG. 16 illustrates an example Media Access Control (MAC) Protocol Date Unit (PDU) for semantic configuration.
  • MAC Media Access Control
  • PDU Protocol Date Unit
  • FIG. 17 illustrates an example switching between semantic communication and legacy communication as controlled by the network side.
  • FIG. 18 illustrates an example switching between semantic communication and legacy communication as controlled by the terminal side.
  • terms, such as “a”, “an” , or “the” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
  • This disclosure is directed generally to wireless communication networks and particularly to network architectures for effectuating a new type data transmission or communication for information with transmission error-tolerance, such as semantic communication.
  • a new type data transmission or communication for information with transmission error-tolerance, such as semantic communication.
  • several aspects in wireless network architecture and signaling are disclosed for realizing the new type data transmission between a wireless terminal and a wireless network.
  • Modification to legacy wireless systems are implemented in order to accommodate source encoder/decoder models, their management, and their activation/deactivation based on model performances and network channel conditions.
  • Data within such a new type data communication may be bifurcated into error-free data and error-tolerant data which may be processed distinctively by the modified wireless network.
  • An example wireless communication network may include wireless terminal devices or user equipment (UE) 110, 111, and 112, a carrier network 102, various service applications 140, and other data networks 150.
  • the wireless terminal devices or UEs may be alternatively referred to as wireless terminals.
  • the carrier network 102 may include access network nodes 120 and 121, and a core network 130.
  • the carrier network 110 may be configured to transmit voice, data, and other information (collectively referred to as data traffic) among UEs 110, 111, and 112, between the UEs and the service applications 140, or between the UEs and the other data networks 150.
  • the access network nodes 120 and 121 may be configured as various wireless access network nodes (WANNs, alternatively referred to as wireless base stations) to interact with the UEs on one side of a communication session and the core network 130 on the other.
  • WANNs wireless access network nodes
  • the term “access network” may be used more broadly to refer a combination of the wireless terminal devices 110, 111, and 112 and the access network nodes 120 and 121.
  • a wireless access network may be alternatively referred to as Radio Access Network (RAN) .
  • the core network 130 may include various network nodes configured to control communication sessions and perform network access management and traffic routing.
  • the service applications 140 may be hosted by various application servers deployed outside of but connected to the core network 130.
  • the other data networks 150 may also be connected to the core network 130.
  • the UEs may communicate with one another via the wireless access network.
  • UE 110 and 112 may be connected to and communicate via the same access network node 120.
  • the UEs may communicate with one another via both the access networks and the core network.
  • UE 110 may be connected to the access network node 120 whereas UE 111 may be connected to the access network node 121, and as such, the UE 110 and UE 111 may communicate to one another via the access network nodes 120 and 121, and the core network 130.
  • the UEs may further communicate with the service applications 140 and the data networks 150 via the core network 130. Further, the UEs may communicate to one another directly via side link communications, as shown by 113.
  • FIG. 2 further shows an example system diagram of the wireless access network 120 including a WANN 202 serving UEs 110 and 112 via the over-the-air interface 204.
  • the wireless transmission resources for the over-the-air interface 204 include a combination of frequency, time, and/or spatial resource.
  • Each of the UEs 110 and 112 may be a mobile or fixed terminal device installed with mobile access units such as SIM/USIM modules for accessing the wireless communication network 100.
  • the UEs 110 and 112 may each be implemented as a terminal device including but not limited to a mobile phone, a smartphone, a tablet, a laptop computer, a vehicle on-board communication equipment, a roadside communication equipment, a sensor device, a smart appliance (such as a television, a refrigerator, and an oven) , or other devices that are capable of communicating wirelessly over a network.
  • each of the UEs such as UE 112 may include transceiver circuitry 206 coupled to one or more antennas 208 to effectuate wireless communication with the WANN 120 or with another UE such as UE 110.
  • the transceiver circuitry 206 may also be coupled to a processor 210, which may also be coupled to a memory 212 or other storage devices.
  • the memory 212 may be transitory or non-transitory and may store therein computer instructions or code which, when read and executed by the processor 210, cause the processor 210 to implement various ones of the methods described herein.
  • the WANN 120 may include a wireless base station or other wireless network access point capable of communicating wirelessly via the over-the-air interface 204 with one or more UEs and communicating with the core network 130.
  • the WANN 120 may be implemented, without being limited, in the form of a 2G base station, a 3G nodeB, an LTE eNB, a 4G LTE base station, a 5G NR base station of a 5G gNB, a 5G central-unit base station, a 5G distributed-unit base station, a 6G base station, another type of secular base station, or cell-free access points.
  • Each type of these WANNs may be configured to perform a corresponding set of wireless network functions.
  • the WANN 202 may include transceiver circuitry 214 coupled to one or more antennas 216, which may include an antenna tower 218 in various forms, to effectuate wireless communications with the UEs 110 and 112.
  • the transceiver circuitry 214 may be coupled to one or more processors 220, which may further be coupled to a memory 222 or other storage devices.
  • the memory 222 may be transitory or non-transitory and may store therein instructions or code that, when read and executed by the one or more processors 220, cause the one or more processors 220 to implement various functions of the WANN 120 described herein.
  • Data packets in a wireless access network may be transmitted as protocol data units (PDUs) .
  • the data included therein may be packaged as PDUs at various network layers wrapped with nested and/or hierarchical protocol headers.
  • the PDUs may be communicated between a transmitting device or transmitting end (these two terms are used interchangeably) and a receiving device or receiving end (these two terms are also used interchangeably) once a connection (e.g., a radio link control (RRC) connection) is established between the transmitting and receiving ends.
  • RRC radio link control
  • Any of the transmitting device or receiving device may be either a wireless terminal device such as device 110 and 120 of FIG. 2 or a wireless access network node such as node 202 of FIG. 2. Each device may both be a transmitting device and receiving device for bi-directional communications.
  • the core network 130 of FIG. 1 may include various network nodes geographically distributed and interconnected to provide network coverage of a service region of the carrier network 102. These network nodes may be implemented as dedicated hardware network nodes. Alternatively, these network nodes may be virtualized and implemented as virtual machines or as software entities. These network nodes may each be configured with one or more types of network functions which collectively provide the provisioning and routing functionalities of the core network 130.
  • FIG. 3 illustrates an example RAN 340 in communication with a core network 310 and wireless terminals UE1 to UE7.
  • the RAN 340 may include one or more various types of wireless base station or WANNs 320 and 321 which may include but are not limited to gNB, eNodeB, NodeB, or other type of base stations.
  • the RAN 340 may be backhauled to the core network 310.
  • the WANNs 320 may further include multiple separate access network nodes in the form of a Central Unit (CU) 322 and one or more Distributed Unit (DU) 324 and 326.
  • CU Central Unit
  • DU Distributed Unit
  • the CU 322 is connected with DU1 324 and DU2 326 via various interfaces, for example, an F1 interface.
  • the F1 interface may further include an F1-C interface and an F1-U interface, which may be used to carry control plane information and user plane data, respectively.
  • the CU may be a gNB Central Unit (gNB-CU)
  • the DU may be a gNB Distributed Unit (gNB-DU) .
  • gNB-CU gNB Central Unit
  • gNB-DU gNB Distributed Unit
  • the UEs may be connected to the network via the WANNs 320 over an air interface.
  • the UEs may be served by at least one cell. Each cell is associated with a coverage area. These cells may be alternatively referred to as serving cells. The coverage areas between cells may partially overlap.
  • Each UE may be actively communicating with at least one cell while may be potentially connected or connectable to more than one cell.
  • UE1, UE2, and UE3 may be served by cell1 330 of the DU1
  • UE4 and UE5 may be served by cell2 332 of the DU1
  • UE6 and UE7 may be served by cell3 associated with DU2.
  • a UE may be served simultaneously by two or more cells.
  • Each of the UE may be mobile and the signal strength and quality from the various cells at the UE may depend on the UE location and mobility.
  • the cells shown in FIG. 3 may be alternatively referred to as serving cells.
  • the serving cells may be grouped into serving cell groups (CGs) .
  • a serving cell group may be either a Master CG (MCG) or Secondary CG (SCG) .
  • MCG Master CG
  • SCG Secondary CG
  • a primary cell in a MSG for example, may be referred to as a PCell
  • PScell Primary cell in a SCG
  • Secondary cells in either an MCG or an SCG may be all referred to as SCell.
  • the primary cells including PCell and PScell may be collectively referred to as spCell (special Cell) .
  • serving cells may be referred to as serving cells or cells.
  • the term “cell” and “serving cell” may be used interchangeably in a general manner unless specifically differentiated.
  • the term “serving cell” may refer to a cell that is serving, will serve, or may serve the UE. In other words, a “serving cell” may not be currently serving the UE. While the various embodiment described below may at times be referred to one of the types of serving cells above, the underlying principles apply to all types of serving cells in both types of serving cell groups.
  • FIG. 4 further illustrates a simplified view of the various network layers involved in transmitting user-plane PDUs from a transmitting device 402 to a receiving device 404 in the example wireless access network of FIGs. 1-3.
  • FIG. 4 is not intended to be inclusive of all essential device components or network layers for handling the transmission of the PDUs.
  • FIG. 4 illustrates that the data packaged by upper network layers 420 at the transmitting device 402 may be transmitted to corresponding upper layer 430 (such as radio resource control or RRC layer) at the receiving device 304 via Packet Data Convergence Protocol layer (PDCP layer, not shown in FIG.
  • PDCP layer Packet Data Convergence Protocol layer
  • Radio link control (RLC) layer 422 and of the transmitting device the physical (PHY) layers of the transmitting and receiving devices and the radio interface, as shown as 406, and the media access control (MAC) layer 434 and RLC layer 432 of the receiving device.
  • Various network entities in each of these layers may be configured to handle the transmission and retransmission of the PDUs.
  • the upper layers 420 may be referred as layer-3 or L3, whereas the intermediate layers such as the RLC layer and/or the MAC layer and/or the PDCP layer (not shown in FIG. 4) may be collectively referred to as layer-2, or L2, and the term layer-1 is used to refer to layers such as the physical layer and the radio interface-associated layers.
  • the term “low layer” may be used to refer to a collection of L1 and L2, whereas the term “high layer” may be used to refer to layer-3.
  • the term “lower layer” may be used to refer to a layer among L1, L2, and L3 that are lower than a current reference layer.
  • Control signaling may be initiated and triggered at each of L1 through L3 and within the various network layers therein. These signaling messages may be encapsulated and cascaded into lower layer packages and transmitted via allocated control or data over-the-air radio resources and interfaces.
  • the term “layer” generally includes various corresponding entities thereof.
  • a MAC layer encompasses corresponding MAC entities that may be created.
  • the layer-1 for example, encompasses PHY entities.
  • the layer-2 for another example encompasses MAC layers/entities, RLC layers/entities, service data adaptation protocol (SDAP) layers and/or PDCP layers/entities.
  • SDAP service data adaptation protocol
  • the various system components above for the various wireless communication networks may be, for example, adopted, enhanced, or modified to realize the example communication system for a new type data transmission, such as semantic communication, as detailed below.
  • the wireless communication systems described above are suitable for transmitting source information in form of a collection of physical bits or symbols through the various network protocol levels, error detection/correction mechanisms, and transmission/retransmission schemes from an origin network node to a destination network node.
  • Such a communication system may be referred to as a level 1 transmission system.
  • information processing and communications systems may be characterized as solving problems that may be categorized into the following three levels:
  • Level 1 solutions to physical information transport for handling transmission of source bits or symbols with a certain level of accuracy.
  • Level 2 solutions to semantic information transport for transmission of source semantics with a certain level of accuracy.
  • Level 3 Solutions related to transport efficiency issue (e.g., how efficiently does the received meaning affect conduct in the desired way) .
  • the current wireless communication protocol described above is aiming to handle the Leve 1 issues or problems, namely, bit/symbol level transmission with certainly level of accuracy (e.g., error-free) .
  • level of accuracy e.g., error-free
  • Level-2 error-tolerant transmission for example, semantic communications, may help achieve improved overall information transmission via semantic encoding of the source information at a transmitting end and semantic decoding of received semantic information at the receiving end.
  • the semantic encoding and decoding may be closely related to the evolving artificial intelligence (AI) and/or machine learning (ML) technologies related to, merely as an example, natural language processing (e.g., NLP) for encoding textual information.
  • AI artificial intelligence
  • ML machine learning
  • NLP natural language processing
  • a two-sided AI/ML model architecture may be considered, one side for encoding/compressing the original information into semantic information, and the other side for decoding /decompressing semantic information into original information.
  • AI/ML based encoding/decoding may be referred to as source/destination encoding/decoding, or semantic encoding/decoding.
  • semantic encoding/decoding mainly aims to generate fewer bits and less symbol information to transfer
  • the channel encoding/decoding technology is aimed at improving the robustness of the information transfer by adding redundant information to the original
  • a joint semantic and channel encoding/decoding may be designed to provide more benefits from the overall semantic communication.
  • one or more of the following options regarding locations of source coding/decoding module in the wireless communication network may be considered:
  • the semantic source encoder may be located at the NW side, and the semantic source decoder may be located at the UE side.
  • the semantic source encoder may be located at the UE side, and the semantic source decoder is located at the NW side.
  • the semantic source encoder may function as an AI/ML model for processing the source data
  • the input of the AI/ML model may be the original data
  • the output of the AI/ML model may be the encoded or compressed data of the original data
  • the semantic source decoder may function as an AI/ML model for processing input data comprising data as comprised by an AI/ML encoder and as transmitted by the wireless network, and an output of the AI/ML model may represent data decompressed from the compressed input data.
  • the source data can be drastically compressed by semantic encoder, thereby reducing the channel resources consumption for user plane (UP) data.
  • UP user plane
  • semantic encoder For another example, there may be no need to perform the guaranteed error-free transmission for semantic communication since the semantically compressed data can be resumed at the receiving point even though some compressed data may be lost or incorrectly transmitted due to a poor channel state, as a result of a potential error recovery capability of AI/ML based semantic decoders.
  • the various embodiments below for semantic communication implementations particular concern aspects for enhancing the current wireless communication protocols (e.g., the 3GPP protocols) including but not limited to (1) mechanisms for AI/ML model management, and (2) switching mechanism between a new type of communications and legacy communications, in order to maximally leverage the advantage of new type of communication.
  • the new type of communications for example, may refer to semantic communications.
  • AL/ML models may be data specific (e.g., textual data, image data, speech data, etc. ) , in terms of either or both of model architecture and trained model parameters. These AI/ML models may be trained for coding/compression and decoding/decompression of the source data of deferent types. The AI/ML models as trained may be deployed at different locations or network nodes or network levels in the wireless network for effectuating semantic communications. Examples for architecture and deployment of AI/ML models in the communication network are shown in FIGs. 5-6 and 9.
  • the AI/ML models for semantic source encoding may be deployed at application layer 502 on the UE side 501 and correspondingly in an application server 504 on the network side 503. Management of the models may be performed between the application layer 502 and application server 504. Such management may be implementation dependent and may thus be transparent to the other lower network layers, including the NAS layer 510 and the AS layer 512 on the UE side, the wireless access network 522 and core network 520 on the network side, and the transmission physical channels 530.
  • the AI/ML models for semantic source coding may be deployed at the NAS layer 610 on the UE side 601 and the core network (CN) 620 on the network side 603.
  • Management of the models may be performed between the NAS layer 610 and the core network 620 via NAS signaling exchanges.
  • Such management may be implemented by network service providers via the wireless network rather than user devices and application server (and thus can be centralized and shared by different application providers) and may thus be transparent to the lower network layers, including the AS layer 612 on the UE side, the wireless access network 620 on the network side, and the transmission physical channels 630.
  • FIG. 7 An example implementation for managing the AI/ML models between the NAS layer 610 and the CN 920 in the architecture of FIG. 6 is shown in FIG. 7, including the following example steps:
  • ⁇ STEP 1 The CN may send a configuration for model management to the UE.
  • ⁇ STEP 2 The CN may send to the UE a control signaling to activate an AI/ML model for the new transmission type.
  • ⁇ STEP 3 The CN may send to the UE a reference data and/or a request for performance monitoring of the new transmission type.
  • ⁇ STEP 4 The UE may perform the performance monitoring and calculate the performance metrics according to the configuration and received reference data.
  • ⁇ STEP 5 The UE may send the calculated performance metrics and/or model control request (s) to the CN.
  • ⁇ STEP 6 The CN may make a model management determination according to the received performance metrics and/or control request (s) .
  • ⁇ STEP 7 The CN may send to the UE the model control signaling to adjust the model status.
  • FIG. 8 Another example implementation alternative to FIG. 7 for managing the AI/ML models between the NAS layer 610 and the CN 620 in the architecture of FIG. 6 is shown in FIG. 8, including the following example steps:
  • ⁇ STEP 1 The CN may send the configuration for model management to the UE.
  • ⁇ STEP 2 the CN may send a control signaling to activate the AI/ML model for the new transmission type (e.g., semantic communication) .
  • ⁇ STEP 3 The UE may send CN the reference data and/or request for performance monitoring of the new transmission type.
  • ⁇ STEP 4 The CN may calculate the performance metrics and make a model management decision according to the calculated metrics, if needed.
  • ⁇ STEP 5 The CN may send to the UE the model control signaling to adjust the model status.
  • the difference between the example implementations of FIG. 7 and FIG. 8 mainly concerns which network entity (the UE or the CN) provides reference data for performance monitoring and which entity performs the performance monitoring for the new transmission type.
  • the signaling may be sent via a protocol tunnel (e.g., NTTP, representing New Type Transmission Protocol) between a logical function (e.g., Semantic Communication Management Function, or SCMF) residing at the CN and the NAS layer of UE.
  • a protocol tunnel e.g., NTTP, representing New Type Transmission Protocol
  • SCMF Semantic Communication Management Function
  • the above protocol tunnel may be transparent to the base station of the wireless communication network (e.g., 622 of FIG. 6) .
  • the SCMF above may have an interface connecting to an SMF and/or UPF and/or AMF described above with respect to the example core network of various generations.
  • the function of SCMF above may contain at least one of the following:
  • control signaling may be sent by the AMF from CN.
  • the AMF may be provided with an interface to the SCMF, and the AMF may be configured to support at least one of the following functions for new type data transmission:
  • the reference data signaling may be an NTTP protocol signaling.
  • the reference data may be retrieved from a database for test or from a real transmission for determining a prediction validity or accuracy of the deployed AI/ML model.
  • the reference data may contain a set of benchmark data or benchmark data pairs (e.g., benchmark input data and benchmark output data) . Such benchmark data may be from a database for the model evaluation/test and/or performance monitoring. If reference data is a benchmark data, the reference data may be the input of the compressed part of the two-sided models.
  • reference data is a data pair
  • one of the data pair may be an input of either the UE part of two-sided model or the NW part of two-sided model that needs to be tested for validity or prediction accuracy.
  • the other one of the data pair may be an output of either the UE part of two-sided model or the NW part of two-sided model that needs to be tested for validity or prediction accuracy.
  • the reference data may include data from real transmissions. In other words, the source/resumed data would be sent to the UE/CN by CN/UE for the performance monitoring.
  • the performance metrics can be obtained from a comparison between the benchmark reference output data and the output of either the UE part of two-side model or the NW part of the two-side model.
  • the output of either the UE part of two-side model or the NW part of two-side model may be obtained from the reference input data along with the AI/ML model that needs performance monitoring.
  • the performance metrics can be obtained from a comparison between the reference data and the output of the decompressing/decoding part of AI/ML model.
  • the UE may be assumed to have compressing/encoding part of the two-side model for DL transmission.
  • the UE may be assumed that it possesses decompressing/decoding portion of two-side model for UL transmission, and the CN may be assumed to have decompressing/decoding portion of two-side model for DL transmission.
  • the CN may be assumed to have compressing/encoding part of two-side model for UL transmission.
  • one peer may send one NTTP protocol signaling to request the other peer (e.g., UE and/or CN) to trigger a performance metrics calculation
  • the NTTP protocol signaling may indicate at least one of the following information: 1) the reference data (pair) which is used for the performance metric calculation, 2) an indication to acquire the feedback of the decompressed/resumed and/or source data, 3) an indication to acquire the feedback of the performance metrics, 4) a threshold value to determine the model control behavior.
  • format of the NTTP protocol signaling it may be a NTTP protocol control element. In some other example implementation of format of the NTTP protocol signaling, it may be a subheader to a NTTP protocol data unit.
  • it may include a quantification semantic difference. In some example implementations, it may include a Euclidean Distance.
  • control signaling may be an NTTP protocol signaling which is described as above.
  • the model control signaling may include a model activation/deactivation/switch/fallback.
  • the AI/ML models for semantic source encoding may be deployed at the AS layer 912 on the UE side 901 and the access network (base station, e.g., NodeB) 922 on the network side 903.
  • Management of the model may be performed between the AS layer 912 and the access network 922 via AS signaling exchanges.
  • Such management may be implemented by network service providers via the wireless network rather than user devices and application server (and thus can be centralized and shared by different application providers) and because it is the closest to the physical channel 930, it provides model management with smallest delays.
  • FIG. 10 An example implementation for managing the AI/ML models between the AS layer 912 and the access network (e.g., NodeB) 922 in the architecture of FIG. 9 is shown in FIG. 10, including the following example steps:
  • the NodeB may send the configuration for model management to the UE.
  • ⁇ STEP 2 The NodeB may send the control signaling to activate an AI/ML model for new type data transmission.
  • the NodeB may send UE the reference data and/or request for performance monitoring of the new type data transmission.
  • ⁇ STEP 4 The UE may implement the performance monitoring and calculate the performance metrics based on configuration and received reference data.
  • ⁇ STEP 5 The UE may send the calculated performance metrics and/or model management request to the NodeB.
  • the NodeB may determine a model management, if needed.
  • ⁇ STEP 7 The NodeB may send to the UE the model control signaling to adjust the model status.
  • FIG. 10 Another example implementation alternative to FIG. 10 for managing the AI/ML models between the AS layer 912 and the base station (nodeB) 922 in the architecture of FIG. 9 is shown in FIG. 11, including the following example steps:
  • the NodeB may send the configuration for model monitoring to the UE.
  • ⁇ STEP 2 The NodeB may send the control signaling to activate an AI/ML model for new type data transmission (e.g., semantic communication) .
  • ⁇ STEP 3 The UE may send to the NodeB the reference data and/or request for performance monitoring for new type data transmission.
  • ⁇ STEP 4 The NodeB may calculate the performance metrics and make a model management decision according to the calculated metrics.
  • ⁇ STEP 5 The NodeB may send to the UE the model control signaling to adjust the model status.
  • the difference between the example implementations of FIG. 10 and FIG. 11 mainly with respect which network entity (the UE or the NodeB) provides reference data for performance monitoring and which entity performs the performance monitoring for the new type data transmission.
  • an RRC signaling may be used.
  • the RRC signaling may indicate the timing point or event to trigger UE and/or NW to report the calculated performance metrics and/or the reference data for calculating performance metrics.
  • Such triggering time point or event may include but is not limited to at least one of: applying a timer may be applied; applying a COUNTER with a predefined maximum value; upon a reception of a control PDU; or by a threshold value for triggering the performance metrics report as indicated by the RRC signaling.
  • control signaling of FIG. 10 and FIG. 11 may be an RRC signaling, a PDCP control PDU, an RLC Control PDU, a MAC CE, or a PHY Control Signaling (e.g., PUCCH and/or PDCCH) , or one logical layer control PDU the logical layer is an access stratum layer.
  • the control signaling may contain/indicate at least one of the following information: a model identity; a model description Information; a service type; a knowledge base identity (for the knowledge base indicated in FIG.
  • a PDU session ID a QoS (Quality of Service) flow ID; a Logical Channel (LCH) ID; or a Data Radio Bearer (DRB) ID; an indication of model control (e.g., activation/deactivation/switch/fallback) .
  • QoS Quality of Service
  • LCH Logical Channel
  • DRB Data Radio Bearer
  • the performance metrics signaling in FIG. 10 and FIG. 11 may be an RRC signaling, a PDCP control PDU, an RLC Control PDU, a MAC CE, or PHY Control Signaling (e.g., PUCCH and/or PDCCH) .
  • the performance metrics may be a quantification of semantic difference between the input of the encoder and output of the decoder.
  • the performance metrics may be a quantification semantic difference between the output of the model and the received reference data.
  • the performance metrics may be a Euclidean Distance between the output of the model and the received reference data.
  • the performance metrics may be a Euclidean Distance between the input of the encoder and output of the decoder.
  • the reference data signaling may be a PDCP Control PDU, an RLC Control PDU, a MAC CE, a PUCCH/PDCCH, and the like.
  • the reference data may be retrieved from a database for test or from a real transmission for determining a prediction validity or accuracy of the deployed AI/ML model.
  • the reference data may contain one benchmark data or a benchmark data pair (e.g., benchmark input data and benchmark output data) .
  • the benchmark data may be from a database for the model evaluation/test and/or performance monitoring.
  • reference data may be the input of the compressed part of two-sided model. If reference data is a data pair, one of the data pair may be an input of either UE part of the two-sided model or NW part of the two-sided model that needs to be tested for validity or prediction accuracy. The other one of the data pair may be an output of either UE part of the two-sided model or NW part of the two-sided model that needs to be tested for validity or prediction accuracy.
  • the reference data may include data from real transmission. In other words, the source/resumed data would be sent to the UE/NodeB by NodeB/UE for the performance monitoring.
  • the performance metrics can be obtained from a comparison between the benchmark reference output data and the output of either UE part of the two-side model or NW part of the two-side model.
  • An output of either UE part of the two-side model or NW part of the two-side model is obtained from the reference input data with the AI/ML model that needs performance monitoring.
  • the performance metrics can be obtained from a comparison between the reference data and the output of the decompressing/decoding part of the AI/ML model.
  • the UE may be assumed to have compressing/encoding part of two two-side model for UL transmission.
  • the UE may be further assumed to have decompressing/decoding part of the two-side model for DL transmission.
  • the CN may be assumed to have decompressing/decoding part of the two-side model for UL transmission, CN may be assumed to have compressing/encoding part of the two-side model for DL transmission.
  • the request signaling may be a PDCP Control PDU, an RLC Control PDU, a MAC CE, a PUCCH/PDCCH, and one logical layer protocol control PDU.
  • the Request signaling may indicate at least one of the following information: 1) an indication of reference data (pair) which is used for performance metric calculation, 2) an indication to acquire the feedback of the decompressed/resumed and/or the source data, 3) an indication to acquire the feedback of the performance metrics, 4) a threshold value to determine the model control behavior.
  • it may include a quantification semantic difference. In some example implementations, it may include a Euclidean Distance.
  • control signaling may be an NTTP protocol signaling which is described as above.
  • the model control signaling may include a model activation/deactivation/switch/fallback.
  • the new type data transmission (e.g., semantic communications) and legacy source symbol-based communications may co-exist.
  • the new type data transmission for a communication session may be activated or deactivated.
  • the network thus may need to be designed, configured, and adapted to handle such activation and deactivation of the new type data transmission, and such activation and deactivation may impact the data transmission requirement and process on the various inter-node interfaces.
  • the various network nodes involved in the communication procedure may need to be informed of various configuration related to semantic communication. For example, in the model management architecture of FIGs. 5 and 6, the semantic communication may be transparent to the RAN (gNB, or NodeB) . Yet, they may need to be notified of the activation and deactivation of the new type data transmission that may require resource changes.
  • data flows for both the new type transmission and symbol-based (e.g., legacy) transmission may be established when establishing the PDU sessions for a service. Then activation/deactivation may of the new type transmission may be requested from either the UE or the data network service provider.
  • Each of the data flow may be established for handling either the new type transmission or the legacy transmission. Only the handling of the new type transmission would involve the AI/ML encoding/compression and decoding/decompression models.
  • one or more, or multiple service flows may be associated with a service.
  • One of the multiple service flows may be mapped to the new type data transmission while another service flow for the same service may be mapped the legacy symbol-based transmission.
  • the service flow associated with the new type data transmission may be activated or deactivated by request, or may be switched between a service flow for new type data transmission and a service flow for legacy symbol-based transmission.
  • the deactivation of one service flow means that the service flow is suspended rather than released, and the activation of one service flow means a resumption of the service flow from a suspended state.
  • a switch of service flows for one service between the new type data transmission and symbol-based transmission may be applied.
  • a service flow switch for example, at least one service flow is deactivated and at least one other service flow is activated simultaneously for the service.
  • a service flow may be PDU session, or a QoS flow.
  • the NW or the UE may effectuate such a switch, activation or deactivation by the following example steps for the example case where the AI/ML models for the new type data transmission are located in the CN/NAS as shown in FIG. 6 or in the application server/App layer as shown in FIG. 5:
  • ⁇ STEP 1 The UE may send a request message A to the CN for requesting the PDU session activation/deactivation.
  • ⁇ STEP 2 The CN may send a message B to the NodeB regarding a service flow activation/deactivation.
  • ⁇ STEP 3 The NodeB may send a message C to the UE according to the received signaling regarding the service flow activation/deactivation.
  • ⁇ STEP 4 The UE may execute the related operation according to the message C, and may send a response to message C to the NodeB.
  • NodeB may send the CN the response to the message B regarding the service flow activation/deactivation.
  • the message A may be a NAS signaling terminated between NAS layer of the UE and the CN.
  • the message A may include/indicate at lease one of the following information: 1) a PDU session Id to indicate the PDU session which need to be activated/deactivated, 2) activation/deactivation indication to indicate the behavior for the indicated PDU session (e.g., activate or deactivate) , 3) the deactivation/activation request of the AI/ML model/functionality/feature regarding the new type data transmission, 4) an AI/ML model/functionality indication to indicate the AI/ML model/functionalities that are requested to be activated/deactivated.
  • Message B above may be a signaling terminated between the CN and the NodeB.
  • Message B may include/indicate at least one of the following information: 1) a PDU session Id to indicate the PDU sessions which need to be activated/deactivated, 2) an activation/deactivation indication to indicate the behavior for the indicated PDU session (e.g., activate or deactivate) , 3) an indication of deactivation/activation of the AI/ML model/functionality/feature regarding the new type data transmission, 4) an AI/ML model/functionality indication to indicate the AI/ML model/functionalities that are activated/deactivated.
  • message C above may be a resource control signaling (e.g., RRCReconfiguration) , or an AS logical layer control PDU (e.g., SDAP control PDU, PDCP control PDU, MAC Control element) .
  • RRCReconfiguration e.g., RRCReconfiguration
  • AS logical layer control PDU e.g., SDAP control PDU, PDCP control PDU, MAC Control element
  • message C may include/indicate at least one of the following information: 1) a PDU session Id to indicate the PDU sessions which need to be activated/deactivated, 2) an activation/deactivation indication to indicate the behavior for the indicated PDU session (e.g., activate or deactivate) , 3) an indication of deactivation/activation of the AI/ML model/functionality/feature regarding new type data transmission, 4) an AI/ML model/functionality indication to indicate the AI/ML model/functionalities that are activated/deactivated.
  • At least one of the following operation may be executed when the signaling indicates a deactivation of a PDU session: 1) for UL transmission, the logical layer (s) associated with the related data radio bearer (s) for the indicated PDU session may transfer all the data units in its buffer to a lower layer, and the data units may be ACKed data units or non-ACKed units; and/or 2) Reset all timers and counters in each AS logical layer associated with the related data radio bearer; and/or 3) for UL transmission, the logical layer associated with the indicated PDU session generates an end mark data unit if there is no more data unit left in the buffer or if an indication of deactivation of related PDU session is received, and/or; 4) for DL transmission, the logical layer (s) associated with the related data radio bearer (s) may transfer all the data units in the buffer to an upper layer, and these data units may be considered ACKed, and/or 5) for DL transmission, the
  • At least one of the following operations may be executed when the signaling indicates an activation of a PDU session: 1) the radio bearer (s) associated with the indicated PDU session is considered as resumed; 2) reset all the timers/counters of each AS logical layer that is associated with the PDU session and/or all the related radio bearers.
  • one or more radio bearer of the air-interface e.g., the interface between UE and nodeB
  • the response message may be an RRC signaling (e.g., RRCReconfigurationComplete Message) , or an AS logical layer control data unit.
  • the AS logical layer may be a SDAP layer, a PDCP layer, an RLC layer, a MAC layer, a PHY layer, and the like, or the AS logical layer may be a logical layer associated with the indicated PDU session.
  • the response message may be an end mark control PDU generated by an AS logical layer associated with the indicated PDU session.
  • the response message may be a signaling terminated between NodeB and CN, and may indicate/include the following information: 1) an indication for successfully activated PDU sessions; 2) an indication for a failure of activation of PDU session and associated failure causes; 3) an indication for successfully deactivated PDU sessions; 4) an indication for a failure of deactivation of PDU session and associated failure causes.
  • one or more or multiple service flows for air-interface may be associated with one or more PDU sessions or one or more QoS flows for new type data transmission.
  • one service flow associated with the new type data transmission may be activated or deactivated by request, or service flow may be switched between a service flow for the new type data transmission and a service flow for legacy symbol-based transmission.
  • the deactivation of a service flow means that the service flow is suspended rather than released.
  • An activation of one service flow means a resumption of the suspended service flow.
  • the switching of service flows between the service flows for new type data transmission and those for symbol-based transmission may be applied.
  • a service flow switch means at least one service flow is deactivated and at least one another service flow is activated simultaneously.
  • the NW or the UE may effectuate such switch, activation or deactivation of the service flow associated with the new type data transmission or the symbol-based transmission by the following example steps:
  • ⁇ STEP 1 The UE may send a request message A to the RAN Node.
  • ⁇ STEP 2 The RAN Node may send a message B to UE regarding the activation/deactivation of a service flow.
  • ⁇ STEP 3 The UE may execute some operations regarding the activation/deactivation of a service flow.
  • the request message A may be a UL RRC signaling, an SDAP control data unit, a PDCP control data unit, an RLC control data unit, a MAC control element, a PHY control signaling (e.g., PUCCH/PDCCH) .
  • the signaling may indicate/include at least one of the following information:
  • An AI/ML model/functionality index the AI/ML models/functionalities for new type data transmission which is requested to be deactivated/activated or switched.
  • a Radio bearer Index or Logical Channel Index to indicate the service flows for new type data transmission that are requested to be activated/deactivated/switched.
  • An activation/deactivation/switch of service flow flag to indicate the activation/deactivation/switch the above indicated service flows.
  • a performance metrics indication to indicate the performance metrics from performance monitoring at UE side.
  • the service flow may be the radio bearer which is terminated between UE and RAN Node.
  • the message B may be a response message to the message A.
  • the message B may be the activation/deactivation control signaling for AI/ML models/functionalities of the new type data transmission.
  • the message B may indicate/include at least one of the following information:
  • An AI/ML model/functionality index the AI/ML models/functionalities for new type data transmission which is deactivated/activated.
  • a Radio bearer Index or Logical Channel Index to indicate the service flows for new type data transmission those are requested to be activated/deactivated/switched.
  • a performance metrics indication to indicate the performance metrics from performance monitoring at NW side.
  • the UE operation for deactivating a service flow may contain at least one of the following:
  • the logical layer where the control signaling message B is received may indicate to a logical layer (e.g., the SDAP layer) to stop mapping a PDU session and/or QoS flow to one service flow (e.g., radio bearer) .
  • a logical layer e.g., the SDAP layer
  • QoS flow e.g., radio bearer
  • the logical layer (e.g., SDAP layer) may generate an end mark control data unit for the deactivated service flow and send it to a lower layer.
  • the end mark control PDU may indicate that this control data unit is the last data unit for such service flow which is deactivated.
  • the logical layers (e.g., PDCP layer, RLC layer) associated with the deactivated service flow may be considered as reestablished after receiving the end mark control PDU or successfully transmitting the end mark control PDU.
  • each logical layer may send all stored PDUs and/or SDUs that are not ACKed by lower/upper layers to the lower/upper layers, and each logical layer may then discard all stored PDUs and/or SDUs, and reset all timers, variables, counters.
  • the logical layers e.g., PDCP layer, RLC layer
  • the logical layers may be considered as suspended after receiving the end mark control PDU or successfully transmitting the end mark control PDU.
  • suspension of one logical layer may contain: 1) discarding all stored data units in the buffer; 2) initializing all the timers, counters, and/or variables.
  • the UE operation for activating a service flow may contain at least one of the following:
  • One logical layer may map the PDU session and/or QoS flows to the activated service flow.
  • Each logical layer (e.g., the PDCP layer or RLC layer) associated with the activated service flow may be reset.
  • resetting of one logical layer may contain 1) discarding all stored data units in the buffer; 2) initializing all the timers, counters, variables.
  • CP control plane
  • One example CP procedure is shown in FIG. 12, and may include:
  • UE/Database/Application server may request the NW for an establishment and/or modification of a service data flow.
  • ⁇ STEP 2 The NW may send a response to the request for establishment and/or modification of a service data flow.
  • the NW may be a core network.
  • the NW may be a base station or RAN (e.g., NodeB) .
  • the service data flow may be one or more PDU sessions, one or more QoS flows, one or more radio bearers, or any combinations thereof.
  • the PDU session for example, may be a tunnel connected between the UE and the CN.
  • a QoS flow for example, may be a sub-tunnel to the PDU session.
  • the sub-tunnel may be configured with a quality of service configuration connected between UE and CN.
  • a data radio bearer for example, may be a tunnel connected between UE and base station.
  • the request may include and/or may indicate at least one of the following information items:
  • a data flow type indicator to indicate the type for which the data flow is request to be established or modified among, for example, an error-free data flow, an error-tolerance data flow, and the like.
  • a quantification indicator to indicate the scenario where such request data flow may be allowed/applied, for instance, range of the value of SINR, the value of RSRQ, the value of RSRP, the transmission failure ratio (e.g., including the PDU transmission failure of each layer) .
  • a data flow quality of service indicator to indicate the data flow QoS requirement, for example, level 5QI.
  • the response may be a NAS signaling terminated between the UE and the CN, or may be a radio resource control signaling, or may be a message combing the RRC message and/or NAS signaling which may indicate at least one of the following information items:
  • Data flow ID to indicate the data flow identifier which is configured to UE.
  • a quantification configuration to indicate the scenario where the error-tolerance transmission (new type data transmission) for such data flow can be allowed, enabled, and the like, e.g., the value of SINR, the value of RSRQ, the value of RSRP, the transmission failure ratio (e.g., including the PDU transmission failure of each layer) .
  • the new type transmission may be allowed/enabled if channel state’s SINR is greater than one certain SINR value in a quantification configuration.
  • the new type transmission may be allowed/enabled if the channel state’s RSRP is greater than one certain RSRP value in the quantification configuration.
  • the new type transmission may be allowed and/or enabled if the channel state’s RSRQ is greater than one certain RSRQ value in the quantification configuration.
  • the new type transmission may be disallowed and/or disabled if the new type transmission failure ratio is greater than one certain threshold value in the quantification configuration.
  • FIG. 13 Another example CP procedure is shown in FIG. 13 (where a base station is split into different function units) , and may include:
  • a first unit of the base station may request the data flow establishment and/or modification for new type transmission.
  • a second unit may generate the response message to the request.
  • the first unit may include a centric unit of a base station.
  • the second unit of the base station may represent a distributed unit of the base station.
  • a communication interface between the first unit and the second unit of the base station e.g., CU and DU
  • STEP 1 may be associated with the UE context modification/establishment procedure.
  • the request in STEP 1 above may include and/or indicate at least one of the following information items:
  • An air-interface data flow (e.g., DRB) to be set up for the request data flow for new type transmission.
  • An SCell (Secondary Cell) to be set up for the request data flow for new type transmission.
  • a quantification indicator for the request data flow for new type transmission e.g., one SINR value, one RSRP value, one RSRQ value, or transmission failure ratio, and the like.
  • a quality indication of the data flow for example, level 5QI.
  • the response may include and/or indicate at least one of the following information items:
  • An air-interface data flow (e.g., DRB (list) ) which is request to be set up for the data flow of new type transmission.
  • An SCell (list) which is request to be set up for the data flow of new type transmission.
  • the new type transmission such as the semantic communication does not need an error-free transmission.
  • the AI/ML based semantic communication have an ability of recovering the semantics of the data through the AI/ML models even some of them may be lost or incorrectly transferred due to the poor channel quality.
  • a UP data transmission may adopt a non-guarantee transmission in order to reduce delays and save resources consumption caused by the potential re-transmission.
  • PDU based transmission in the 3GPP system need non-error transmission of header information for each protocol layer and/or control signaling. Otherwise, the PDU would be discarded due to the error detection of the header information, and the CP related procedure would be considered as failed due to the control signaling error. For at least this reason, the PDU based solution in the current symbol based communication systems would need to be modified when being used for the new type transmission.
  • CP date may be undergone error-free transmission
  • semantic UP (User Plane) data with protocol headers may be undergo a mix of error free transmission and error tolerant transmission, where the protocol headers may undergo error free transmission and the payload may under go error tolerance transmission.
  • the protocol headers for downlink (DL) data may include SDAP header, PDCP header, RLC header, and MAC header, and the like.
  • the protocol headers for uplink (UL) data for example, may include the SDAP header, the PDCP header, the RLC header, the MAC header, and the like.
  • the error tolerance level of the non-header UP data payload may depend on the capability of the AI/ML models and the error levels at the same time may depend on the quality of the underlying physical transmission channels and may be adaptively adjusted by including a controllable level of, for example, Cyclic Redundancy Check (CRC) , HARQ operation, etc.
  • CRC Cyclic Redundancy Check
  • a modified protocol system for the PDU would preferably achieve one or more of the follow targets:
  • ⁇ Target 1 to support both the data flow for error-free transmission and the data flow for error-tolerance transmission.
  • ⁇ Target 2 to support both error-free transmission of header information and error-tolerant transmission of the UP data.
  • Target 3 the CRC operation for the new type transmission may need be controllable in order to adapt to the various change of the channel state. Which can be considered as the target 3 in this disclosure.
  • the separation of the data flow with guaranteed transmission from data flow with data tolerance may be implemented using UL grant or DL assignment.
  • An example is shown in FIG. 14, including the following example steps:
  • ⁇ STEP 1 an RRC configuration signaling for new type transmission operation may be received from by the UE from the NW.
  • ⁇ STEP 2 a UL grant and/or DL assignment may be received by the UE from NW.
  • ⁇ STEP 3a the UE perform UL grant processing if the UL grant is received in STEP 2.
  • STEP 3b alternative to STEP 3a: the UE performs DL assignment processing if the DL assignment is received in STEP 2.
  • ⁇ STEP 4a the UE generates the UL transmission to the NW according to the UL grant.
  • STEP 4b alternative to STEP 4a: the UE performs DL reception operation according the DL assignment.
  • UE may send the ACK/NACK to the NW according to the DL operation in step 4b.
  • the RRC configuration may indicate or include at least one the following information items regarding the transmission operation:
  • Such an indication may indicate the transmission type for the data from such logical channel, radio bearer, QoS flow.
  • the transmission type for a logical channel, or radio bearer, or QoS flow may depend on transmission type for the HARQ processes that are associated with the LCH, or the radio bearer, or the QoS flow. For example, if one HARQ process with a HARQ process Id is indicated for TYPE 1 transmission, the associated LCH and/or radio bearer and/or QoS flow may be for TYPE 1 transmission as well. Otherwise, the associated LCH and/or radio bearer and/or QoS flow may be for TYPE 2 transmission.
  • An indication configured for a serving cell/BWP may indicate the transmission type (e.g., TYPE 1 transmission/TYPE 2 transmission) of the transmission on the serving cell/BWP.
  • An indication configured for a PDCCH timing location (e.g., search space) .
  • Such an indication may indicate the transmission type of a transmission scheduled by a UL grant/DL assignment received from such PDCCH timing location.
  • An indication configured for a PDCCH frequency location (e.g., CORESET) .
  • Such an indication may indicate the transmission type of a transmission scheduled by a UL grant/DL assignment received from such PDCCH frequency location.
  • a specific cell radio network temporary identifier may indicate type 1 transmission. Comparatively, the UL grant/DL assignment addressed by a cell radio network temporary identifier other than the specific cell radio network temporary identifier may indicate type 2 transmission.
  • An indication configured for a HARQ process may indicate the transmission type for the transmission corresponding to the HARQ process.
  • the HARQ process configuration may include/indicate at least one of the following information:
  • a transmission type may include but is not limited to:
  • the transmission may be an error-tolerant transmission, or the transmission may contain both the for error-tolerant transmission and error-free transmission.
  • the transmission may require error-tolerant transmission which does not require HARQ related operations.
  • a part of the data for transmission may require error-free transmission which needs HARQ related operation.
  • the transmission type may be an error-free transmission. For example, all the data for transmission may need HARQ related operation.
  • the TYPE 2 transmission may be a symbol-based transmission which is broadly used in LTE and NR.
  • TYPE 1 transmission and TYPE 2 transmission appeared in this specification may have the same definition.
  • the terms of ‘HARQ operation’ or ‘HARQ related operation’a ppeared in this specification may include a couple of operation for implementing the error-free transmission.
  • a transmitting side may encode a data block with some redundant/checking bits (e.g., encoding the data block with a certain redundancy check method, for example, using CRC, LDPC, Pola, or Turbo code) , and may perform a re-transmission if NACK is received, whereas a receiving side may check whether the data block is correctly received with the redundant/checking bits added by a transmitting side (e.g., decoding the data block with a certain redundancy check method, for example, using CRC, LDPC, Polar, or Turbo code) , and may generate ACK/NACK regarding the received data block after checking.
  • some redundant/checking bits e.g., encoding the data block with a certain redundancy check method, for example, using CRC, LDPC, Pola, or Turbo code
  • the UE may decide the transmission type for a UL grant/DL assignment in the following example manners:
  • the UL grant/DL assignment addressed by a specific cell defined UE identity may be considered by the UE as the corresponding scheduling transmission type (e.g., TYPE 1, or TYPE 2) .
  • the UL grant/DL assignment received in a PDCCH with a specific timing location may be considered by the UE as the corresponding scheduling transmission type.
  • the UL grant/DL assignment received in a PDCCH with a specific frequency location may be considered by the UE as the corresponding scheduling transmission type.
  • the UL grant/DL assignment may contain one indication to indicate the scheduling transmission type and the UE may decide the transmission type according to such indication.
  • the UL grant and DL assignment for a HARQ process which may implicitly indicate a transmission type that the UL grant/DL assignment is for through the transmission type configured for the HARQ process.
  • the UL grant /DL assignment may be for Type 1 transmission if the scheduling HARQ process is configured for Type 1 transmission. Otherwise, the UL grant /DL assignment may be for Type 2 transmission.
  • the MAC package data unit and/or TB should be generated.
  • a LCH restriction factor may be introduced, the LCH restriction factor may be used for MAC entity to determine the LCH where the data can be multiplexed into MAC package data unit/TB for the UL transmission scheduled by UL grant.
  • the LCH restriction factor above may be an allowed serving cell (list) and/or BWP (list) which means that the data from the LCH can be multiplexed and assembled for such UL transmission on those serving cells/UL BWPs.
  • the LCH restriction factor above may be an allowed HARQ process Id (list) which means that the data from the corresponding LCH can be multiplexed and assembled only for the UL grant for the allowed HARQ process Ids.
  • step 4a the MAC PDU generation for TYPE 1 transmission, are further described in the below embodiments (e.g., the embodiments described in the section entitled: Separation of the Header/Control Information from the Source Data Block/Padding) .
  • the received Transport Block (TB) or the part of the received TB may not need the HARQ related operation and/or generate the HARQ feedback (e.g., ACK/NACK) according to the received DL assignment if the received DL assignment indicates the scheduling transmission is a TYPE 1 transmission.
  • the received TB may need the HARQ related operation and/or generate the corresponding HARQ feedback (e.g., ACK/NACK) according to the received DL assignment if the received DL assignment indicates the scheduling transmission is TYPE 2 transmission.
  • step 4b and 5b the DL reception for TYPE 1 transmission is further described in the disclosure below (e.g., Separation of the Header/Control Information from the Source Data Block/Padding) .
  • the HARQ related operations may be handled by higher layers, e.g., one or more MAC entities for UL and DL transmissions.
  • higher layers e.g., one or more MAC entities for UL and DL transmissions.
  • HARQ operation handling may include the following steps:
  • ⁇ STEP 0 a UL grant may be received from NW.
  • the UE may determine the transmission type for the UL grant (e.g., new transmission or retransmission) .
  • ⁇ STEP 2 if the UL grant is for new transmission.
  • the UE perform a multiplexing of the MAC SDU and MAC CE into a MAC PDU for the UL grant, and indicate the lower layer to perform a UL transmission.
  • ⁇ STEP 3 if the UL grant is for the re-transmission to a HARQ process ID and/or a NACK to the HARQ process ID of a UL transmission has been received, then the MAC entity may generate a re-transmission for the MAC PDU.
  • the MAC entity may be responsible for composing a MAC PDU, and the MAC PDU may comprise of one or more MAC subPDUs.
  • the MAC entity may attach the HARQ related information to one or more MAC subPDUs.
  • the MAC subPDU may contain a MAC SDU or MAC Control element and a corresponding subHeader information.
  • at least one of the following MAC subPDU may need to be attached with the HARQ related information:
  • a service flow e.g., radio bearer
  • MAC subPDU corresponding to a MAC SDU being a Control signaling from upper layers (e.g., SDAP/PDCP/RLC) .
  • upper layers e.g., SDAP/PDCP/RLC
  • MAC subPDU corresponding to a MAC SDU that contains one or more header information of upper layers (e.g., the logical layers above the MAC layer) for one payload data unit.
  • At least one of the following operations may be performed by the MAC entity:
  • one or more MAC subPDUs can be grouped together for HARQ related operation, and hence at least one of the following operations may be performed by MAC entity:
  • Grouping MAC subPDUs into multiple groups in one MAC PDU In one example implementation of this grouping/apart mechanism, the MAC subPDUs needing the HARQ operation are allocated into one or more groups, whereas the MAC subPDUs that do not need the HARQ operation are allocated into other group (s) .
  • the HARQ header may include the HARQ related information which may include the bit length indication for the group that corresponds to the HARQ related information.
  • the NACK indication to a UL transmission may be of at least one of the below formats:
  • the PDCCH may be used to indicate UL grant for scheduling re-transmission to the HARQ process ID for which the UL transmission is associated.
  • the PDCCH may include at least one of the following information:
  • a HARQ process ID to indicate the HARQ process the re-transmission is scheduled for.
  • a group Indication to indicate the groups of MAC subPDUs the retransmission is scheduled for.
  • a MAC sub-PDU indication to indicate the MAC sub-PDUs the retransmission is scheduled for.
  • one DL MAC CE may be used for indicating the NACK.
  • the DL MAC CE may include/indicate the at least one of the following information:
  • a HARQ Process ID to indicate the HARQ process that the MAC PDU is associated with.
  • a MAC Sub-PDU indication to indicate the MAC sub-PDU of the MAC PDU that are ACKed or NACKed.
  • a group Indication to indicate the groups of MAC subPDUs those are ACKed or NACKed.
  • An ACK/NACK indication to indicate the ACK/NACK for each indicated MAC PDU/MAC SubPDU/MAC subPDU group.
  • the MAC SDUs/MAC CEs or MAC sub-PDU (group) where the HARQ related information is attached may be retransmitted when receiving the NACK.
  • the MAC entity may push the MAC PDU into multiplexing and assembly entity to re-generate a MAC PDU for retransmission where the MAC sub-PDU without HARQ information attached is eliminated.
  • the MAC SDUs/MAC CEs or MAC subPDU (group) indicated by NACK may be retransmitted when receiving the NACK.
  • the MAC entity may push the MAC PDU into multiplexing and assembly entity to re-generate the MAC PDU for retransmission where the MAC sub-PDU with ACK indication is eliminated.
  • the whole MAC PDU may be retransmitted when receiving the NACK.
  • one example HARQ operation handling by higher layers may include the following steps:
  • a DL assignment may be received for a HARQ process by the UE.
  • a MAC entity may process the DL assignment and determine whether the DL reception is a new transmission or a re-transmission and send the information to the HARQ entity.
  • ⁇ STEP 3 the MAC entity may allocate a TB received from lower layer and associate a HARQ process ID to the HARQ process.
  • the MAC entity may decode the TB to MAC PDU and parse the MAC PDU into the MAC sub-PDUs for the HARQ process.
  • MAC entity may forward each MAC subPDU to the upper layer by removing the subheader/header that is added in MAC layer.
  • the MAC entity may generate the NACK/ACK information to the HARQ process and indicate it to lower layer for transmission of the NACK/ACK indication.
  • the PDCCH for DL assignment may include/indicate at least one of the following information:
  • ⁇ HARQ Process ID to indicate the HARQ Process the retransmission is for. In one example implementation, it indicates all MAC subPDUs and/or MAC subPDU groups that have been indicated as NACK for which HARQ process ID are transmitted by such DL assignment.
  • Transmission type indication to indicate the transmission type (e.g., Retransmission/New Transmission) .
  • the transmission type e.g., Retransmission/New Transmission
  • it may be an indication of NDI value which is used for comparing the previous NDI value for the same HARQ process Id.
  • ⁇ MAC sub-PDU indication to indicate the MAC Sub-PDUs that are associated with the indicated HARQ process ID and are re-transmitted by such DL assignment.
  • ⁇ MAC subPDU group indication to indicate the MAC sub-PDU group that are associated with the indicated HARQ process Id and are re-transmitted by such DL assignment.
  • the MAC entity may consider the MAC subPDU as failed to be received if the HARQ related information is attached and the HARQ is failed. In some other example implementation of decoding and parsing TB/MAC PDU in STEP 4, the MAC entity may consider all MAC subPDUs with HARQ related information attached to be failed if at least one MAC subPDU is not successful with respect to HARQ operation.
  • the MAC entity may consider all MAC subPDUs in one group as failed to be received if at lease one or more than N MAC subPDUs in the group is not successful with respect to HARQ operation.
  • value of N can be configurable in RRC configuration or hard coded in the specification.
  • the MAC entity may consider the MAC PDU as failed to be received if at least one or more than N MAC subPDUs are not successful with respect to HARQ operation.
  • value of N can be configurable in RRC configuration or hard coded in the specification.
  • At least one of the following MAC subPDU may be forwarded to the upper layer:
  • ⁇ MAC subPDUs (Group) those are considered as successful reception upon the HARQ related operation in the MAC entity.
  • the NACK/ACK indication to a received MAC PDU can be either UL MAC CE or PUCCH signaling, which may contain or indicate at least one of the following information:
  • a HARQ Process ID to indicate HARQ Process ID the ACK/NACK information is for.
  • MAC subPDU indication to indicate the MAC subPDUs those have failed and/or Succeeded in HARQ operation.
  • a MAC subPDU group indication to indicate the MAC subPDU (group) those have failed and/or succeeded in the HARQ operation.
  • a NACK/ACK indication to indicate the reception failure/success for each indicated HARQ process Id, MAC subPDU, MAC subPDU group.
  • each higher layer in the communication protocol stack e.g., SDAP, PDCP, RLC
  • the new type transmission e.g., semantic transmission
  • the MAC layer may be responsible to compose those headers from upper layer and itself with corresponding source data block in a MAC PDU.
  • a MAC entity may have two example ways to multiplex and assemble the headers and payload into a MAC PDU.
  • the MAC PDU may be separated into two part. The first part may contain the headers and/or control information, whereas the second part may contain source data block or payload data block, as shown in FIG. 16.
  • the source data block in such a MAC PDU may follow the header/control information part, as shown in the upper panel of FIG. 16.
  • the source data block in such a MAC PDU may proceed the header/control information part, as shown in the lower panel of FIG. 16.
  • the MAC entity may generate one MAC PDU and/or TB that comprises both headers information and source data block received from upper layer.
  • header part of MAC PDU may need the HARQ operation, whereas the source data part of MAC PDU may not need the HARQ operation.
  • the MAC entity may generate two separate MAC PDUs and/or TBs to respectively include the header information and payload received from upper layer.
  • the MAC PDU of header information generated by each upper layer may need HARQ operation, but the MAC PDU of source data may not need HARQ operation.
  • the HARQ operations may be located at one logical layer which hosts a function for re-transmission.
  • the HARQ operations may be located at the PHY layer.
  • the HARQ operation may be located at MAC layer.
  • each higher layer may perform the HARQ operation for the corresponding header and/or control signaling.
  • the HARQ operations may be located at each higher layer for the corresponding header information and/or control information.
  • the HARQ operations for source data block may be located at lower layer (e.g., PHY layer) , or may be located at a higher layer, for example, the SDAP layer.
  • the handling of a PDU or subPDU received for the data transmission may follow the following example steps:
  • an AS logical layer of a UE may perform the HARQ operation on a subPDU or PDU when receiving the subPDU or PDU from a lower layer or from the NW.
  • the AS logical layer may transfer the subPDU or PDU by removing the header information to the upper layer when the HARQ operation is considered as successful.
  • STEP 2b alternative to STEP 2a: the AS logical layer may perform an operation on the subPDU or PDU when HARQ operation is considered as failed.
  • the AS logical layer may be one of PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, or may be a layer mixed with multiple layers of PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer.
  • subPDU or PDU may be a block of data
  • one subPDU or PDU may contain the header part and/or payload part.
  • the UE may perform the HARQ operation on only header part of the subPDU or PDU.
  • the UE may consider the subPDU or PDU (e.g., including both header and payload part) as being received successfully if the HARQ operation of header part is successful.
  • the UE may perform the HARQ operation on both header part and the payload part. For example, the UE may consider the subPDU or PDU as being successfully received if the header part of the subPDU or PDU is successfully decoded, although the transmission of the payload may be considered as failed. For another example, a number of retransmissions of the header part of a subPDU or PDU reaching a predefined maximum number may be considered as indicating a transmission failure of payload part of the subPDU or PDU.
  • the operation performed on the subPDU or PDU may include at least one of the following:
  • ⁇ generating a HARQ feedback for the subPDU or PDU, and/or indicating the lower layer to send the HARQ feedback indication to a peer.
  • ⁇ generating the ARQ feedback for the subPDU or PDU, and/or indicating the lower layer to send the ARQ feedback to a peer.
  • the HARQ operation if needed, may be performed at the PHY layer.
  • a UL transmission may be implemented in the following example steps:
  • the MAC entity of a UE may determine whether the UL grant is for TYPE 1 transmission upon receiving a UL grant from lower layer. If the UL grant is for TYPE 1 transmission, go to STEP 2 below. Otherwise, end the procedure.
  • ⁇ STEP 2 the MAC entity of the UE may determine the transmission is new transmission or re-transmission for the TYPE 1 transmission.
  • ⁇ STEP 3a if the MAC entity of the UE determines that the UL transmission is a new transmission, it may perform a multiplexing and assembling of a MAC PDU, and generate and deliver the TB to the HARQ process (es) .
  • MAC entity of the UE may deliver the UL grant and HARQ information for the TB to the HARQ process for retransmission.
  • ⁇ STEP 4 the MAC entity may instruct the lower layer to initiate a UL transmission (e.g., new transmission or retransmission) .
  • a UL transmission e.g., new transmission or retransmission
  • the UL grant may be identified as UL grant for TYPE 1 transmission by the MAC entity by at least one of the following:
  • the serving cell and/or BWP that the UL grant is for may be configured with an indication to indicate such serving cell/BWP to be for TYPE 1 transmission.
  • the PDCCH timing position where the UL grant is received (e.g., the PDCCH search space) .
  • the PDCCH timing position may be configured for scheduling TYPE 1 transmission where the UL grant is received.
  • the PDCCH frequency position where the UL grant is received (e.g., the PDCCH CORESET) .
  • the PDCCH frequency position may be configured for scheduling TYPE 1 transmission where the UL grant is received.
  • the HARQ Process Id which is indicated in the UL grant.
  • the HARQ process indicated by such HARQ process Id is configured for TYPE 1 transmission.
  • UL grant can be determined implicitly as the UL grant for the TYPE 1 transmission by at least one of the following methods:
  • the UL grant for the mapped serving cells/BWPs may be determined as UL grant for TYPE 1 transmission.
  • the UL grant for the mapped HARQ processes may be determined as UL grant for TYPE 1 transmission.
  • the MAC PDU may be separated into at least two sub-TBs for one TB in for PHY layer transmission. At least one of the two sub-TBs may be generated for header and/or control information part of the MAC PDU, whereas another one of the two sub-TBs may be generated for the source data block part of the MAC PDU.
  • two or more sub-TBs may be delivered by the MAC entity to a HARQ process.
  • a buffer of the HARQ process may be split into at least two parts.
  • One of the at least two parts may be configured for storing the header and/or control information, whereas another part of the at least two parts may be configured for storing the source data block.
  • the two or more sub-TBs may be delivered to different HARQ processes.
  • the HARQ process for sub-TBs associated with the header/control information may support HARQ operations, whereas the HARQ process for sub-TBs associated with the source data block may not support HARQ operation.
  • one HARQ process supporting HARQ operation maybe from a HARQ entity, whereas one HARQ process not supporting HARQ operation may be from another HARQ entity.
  • a serving cell or cell group may be configured with at least two HARQ entities.
  • two sub-TBs from one MAC entity may be sent to two HARQ processes with the same HARQ process Id in different HARQ entities.
  • 2N HARQ processes may be operated in one HARQ entity, among which the first/second half HARQ process Ids may be used for the transmission that needs HARQ operation, whereas the second/first half HARQ process Ids may be used for the transmission that does not needs HARQ operation.
  • N HARQ processes may be allocated to at least two groups for one HARQ entity, where the first group of HARQ processes in one HARQ entity may support the HARQ operation, whereas the second group of HARQ processes in one HARQ entity may not support the HARQ operation.
  • the MAC layer may instruct lower layer which sub-TB in the HARQ process buffer needs the HARQ Operation.
  • the MAC layer may deliver different sub-TBs for source data block to different HARQ processes, and among such HARQ processes, the HARQ process for the sub-TBs associated with the control and/or header information may need HARQ operations, whereas the HARQ process for the sub-TBs associated with the source data block may not need HARQ operations.
  • the UE may need to notify the NW of the size of each sub-TB in one TB.
  • the sub-TB size information may be indicated in a PUSCH.
  • the sub-TB size of the first Part of a MAC PDU may be indicated in the front of the corresponding MAC PDU.
  • the MAC layer may indicate to a lower layer which sub-TB shall be re-transmitted and needs HARQ operation for a HARQ process. For example, a bitmap with at least two bits for a HARQ process ID in the UL grant to indicate which sub-TB is for retransmission (e.g., header, control information, or source data block) .
  • the sub-TB for retransmission may be indicated by HARQ ID in the UL grant for retransmission.
  • the HARQ operation if needed, may be performed at the PHY layer.
  • a DL transmission may be implemented in the following example steps:
  • ⁇ STEP 1 it is determined by the UE whether a DL assignment for TYPE 1 transmission. If the DL assignment for TYPE 1 transmission is received, continue with STEP 2. Otherwise, end the procedure.
  • ⁇ STEP 2 the MAC entity of the UE may process the DL assignment, and try to receive the TB or sub-TBs from lower layer.
  • ⁇ STEP 3 the MAC entity of the UE may allocate TB (s) or sub-TB (s) received from lower layer to the HARQ processes.
  • ⁇ STEP 4 the MAC entity of the UE attempt to decode the received TB (s) or sub-TB (s) .
  • ⁇ STEP 5a if the received TB (s) or sub-TB (s) is not decodable, the MAC layer of the UE may instruct lower layer to generate a NACK signaling for the received TB or sub-TB (s) .
  • MAC entity of the UE may deliver the decoded MAC PDU to a disassembly and de-multiplexing entity and instruct the lower layer to generate an ACK signaling.
  • the DL assignment may be identified as for TYPE 1 transmission via at least one of the below manners:
  • the serving cell and/or BWP that the DL assignment is for may be configured with an indication to indicate such serving cell/BWP to be for TYPE 1 transmission.
  • the PDCCH timing position where the DL assignment is received (e.g., the PDCCH search space) .
  • the PDCCH timing position may be configured for scheduling TYPE 1 transmission where the DL assignment is received.
  • the PDCCH frequency position where the DL assignment is received (e.g., the PDCCH CORESET) .
  • the PDCCH frequency position is configured for scheduling TYPE 1 transmission where the DL assignment is received.
  • the HARQ Process Id which is indicated in the DL assignment.
  • the HARQ process indicated by such HARQ process Id may be configured for TYPE 1 transmission.
  • DL assignment can be determined implicitly as the UL grant for the TYPE 1 transmission by at least one of the following methods:
  • the UL grant for the mapped serving cells/BWPs may be s determined as UL grant for TYPE 1 transmission.
  • the UL grant for the mapped HARQ processes may be determined as UL grant for TYPE 1 transmission.
  • only HARQ process ID may be indicated for both header/control information and source data block.
  • more than 1 HARQ process IDs may be indicated for header/control information and source data block respectively.
  • the TB may be split into at least two sub-TBs, where at least one sub-TB may need the HARQ related operation, whereas at least one sub-TB may not need the HARQ related operation.
  • the MAC entity may allocate all sub-TBs of one TB to one HARQ process.
  • one HARQ process may have at least two independent HARQ buffers to accommodate every sub-TB received from lower layer.
  • the MAC entity may allocate each sub-TBs of one TB to a diverse HARQ process.
  • HARQ process grouping may be introduced, where one HARQ entity may have more than one HARQ process groups, and at least one HARQ process group have the HARQ related operation, whereas at least one HARQ process group do not have the HARQ related operation.
  • one HARQ process having HARQ related operation may be from a HARQ entity, whereas one HARQ process not having HARQ related operation may be from another HARQ entity.
  • a serving cell or cell group may be configured with at least two HARQ entities, where two sub-TBs received by MAC entity may be sent to two HARQ processes with a same HARQ process Id in different HARQ entities.
  • 2N HARQ processes may be operated in one HARQ entity, among which the first/second half HARQ process Ids may be used for the transmission that needs HARQ related operation, whereas the second/first half HARQ process Ids may be used for the transmission that does not need HARQ related operation.
  • the size each sub-TB may be indicated in the PDCCH. In some other example implementations, the size of first sub-TB in a TB may be indicated in the front of the MAC PDU associated with the TB.
  • a TB containing multiple sub-TBs may be considered as successfully decoded if and only if all sub-TBs and/or HARQ processes related to the TB are successfully decoded.
  • a TB containing multiple sub-TBs may be considered as successful decoded if the sub-TBs that need HARQ related operation are decoded successfully.
  • the TB are considered as not successfully decoded if retransmission times of one sub-TB of the TB has reached a pre-defined or pre-configured maximum number.
  • the ACK/NACK signaling above may include or indicate one or more of the following information items:
  • ⁇ a sub-TB indication to indicate which sub-TB is ACKed or NACKed.
  • CBG Code Block Group
  • the HARQ related operation if needed, may be performed at the MAC layer.
  • a UL transmission may be implemented in the following example steps:
  • the MAC entity of a UE may determine whether the UL grant is for TYPE 1 transmission upon the UL grant being received from lower layer. If it is determined that the UL grant is for TYPE 1 transmission, continue to STEP 2. Otherwise, the procedure ends.
  • ⁇ STEP 2 the MAC entity of the UE may determine the transmission is an initial transmission or a re-transmission) .
  • ⁇ STEP 3a if the transmission type is a new transmission, the MAC entity of the UE may perform a multiplexing and assembling of a MAC PDU, and then generate and deliver the TB for the MAC PDU to the HARQ process indicated in UL grant.
  • ⁇ STEP 3b if the transmission type is a re-transmission, the MAC entity of the UE may deliver the UL grant and HARQ information for the TB to the HARQ process for retransmission.
  • ⁇ STEP 4 the MAC entity may instruct a lower layer to initiate a UL transmission (e.g., initial transmission or retransmission) .
  • a UL transmission e.g., initial transmission or retransmission
  • the UL grant may be identified as UL grant for TYPE 1 transmission by at least one of the below solutions:
  • the serving cell and/or BWP that the UL grant is for may be configured with an indication to indicate such serving cell/BWP to be for TYPE 1 transmission.
  • the PDCCH timing position where the UL grant is received (e.g., the PDCCH search space) .
  • the PDCCH timing position may be configured for scheduling TYPE 1 transmission where the UL grant is received.
  • the PDCCH frequency position where the UL grant is received (e.g., the PDCCH CORESET) .
  • the PDCCH frequency position may be configured for scheduling TYPE 1 transmission where the UL grant is received.
  • the HARQ Process Id which is indicated in the UL grant.
  • the HARQ process indicated by such HARQ process Id may be configured for TYPE 1 transmission.
  • UL grant can be determined implicitly as the UL grant for the TYPE 1 transmission by at least one of the following methods:
  • the UL grant for the mapped serving cells/BWPs may be determined as UL grant for TYPE 1 transmission.
  • the UL grant for the mapped HARQ processes may be determined as UL grant for TYPE 1 transmission.
  • the PDCCH to which the UL grant is addressed to may contain the indications to indicate a retransmission, the indication may be at least one of the following information:
  • a HARQ process Indication to indicate which HARQ process to be scheduled as retransmission.
  • a Retransmission granularity level indication to indicate the retransmission granularity level.
  • the retransmission may be for the part of the MAC PDU that needs HARQ operation, or the retransmission may be for the part of the MAC PDU that does not need HARQ related operation, or the retransmission may be for the whole MAC PDU.
  • a HARQ group indication to indicate which HARQ Group of the part of MAC PDU that needs HARQ operation to be scheduled as retransmission.
  • a Retransmission indication to indicate such UL grant is for retransmission associated the indicated HARQ process Id and/or HARQ group.
  • the retransmission indication may be a toggled NDI value compare to the NDI value received from the previous UL grant for the indicated HARQ process Id.
  • the HARQ related information (e.g., HARQ header) for a MAC PDU may be attached to the front of header or control information part of a MAC PDU.
  • the HARQ related information above (e.g., HARQ header) for the MAC PDU may include the at least one of the following information items:
  • the size of the part of a MAC PDU that needs HARQ related information (e.g., the header or control information part) .
  • the header or control information part of a MAC PDU may be grouped/split into multiple groups (e.g., HARQ groups) .
  • the HARQ related information e.g., HARQ header
  • the re-transmission may be for the part of the MAC PDU (e.g., the header or control signaling part) that needs HARQ related operation, or for the part of the MAC PDU (e.g., the payload or source data block) that does not need HARQ related operation, or the whole MAC PDU upon the indication from the UL grant.
  • the part of the MAC PDU e.g., the header or control signaling part
  • the part of the MAC PDU e.g., the payload or source data block
  • the MAC PDU stored in the HARQ process buffer may be pushed into multiplexed and assembly entity and may regenerate a MAC PDU by eliminating the part that does not need HARQ related operation and/or the part that has been ACKed.
  • the HARQ related operation if needed, may be performed at the MAC layer.
  • a DL transmission may be implemented in the following example steps:
  • ⁇ STEP 1 The UE may determine whether the received DL assignment is for TYPE 1 transmission or not. If it is determined that the DL assignment is for TYPE 1 transmission, continue to STEP 2. Otherwise, the procedure ends.
  • ⁇ STEP 2 The MAC entity of the UE may process the DL assignment, and determine the transmission type (e.g., initial transmission or re-transmission) .
  • the transmission type e.g., initial transmission or re-transmission
  • ⁇ STEP 3 The MAC entity of the UE may allocate the TB (s) received from a lower layer to the HARQ processes.
  • ⁇ STEP 4 The MAC entity of the UE may attempt to decode the received TB (s) , and check the MAC PDU with the attached HARQ related information.
  • ⁇ STEP 5a If the received TB (s) is not decodable and/or the HARQ operation for the MAC PDU fails, the MAC layer of the UE may instruct the lower layer to generate a NACK signaling for the received TB.
  • ⁇ STEP 5b If the received TB (s) is successfully decoded, and the MAC PDU has successfully passed the HARQ operation, the MAC entity of the UE may deliver the decoded MAC PDU to a disassembling and de-multiplexing entity and instruct the lower layer to generate an ACK signaling.
  • the identification of the DL assignment for TYPE 1 transmission may be implemented in at least one of the below manners:
  • the PDCCH timing position where the DL assignment is received (e.g., the PDCCH search space) , the PDCCH timing position is configured for scheduling TYPE 1 transmission where the DL assignment is received.
  • the PDCCH frequency position where the DL assignment is received (e.g., the PDCCH CORESET) , the PDCCH frequency position is configured for scheduling TYPE 1 transmission where the DL assignment is received.
  • the HARQ Process Id which is indicated in the DL assignment, the HARQ process indicated by such HARQ process Id is configured for TYPE 1 transmission.
  • DL assignment can be determined implicitly as the UL grant for the TYPE 1 transmission by at least one of the following methods:
  • the UL grant for the mapped serving cells/BWPs may be determined as UL grant for TYPE 1 transmission.
  • the UL grant for the mapped HARQ processes may be determined as UL grant for TYPE 1 transmission.
  • the retransmission may be either a retransmission of the part of the MAC PDU that needs the HARQ related operation (e.g., the header information and/or control information) , or a retransmission of the part of the MAC PDU that does not need the HARQ related operation (e.g., the source data block or payload) , or a retransmission of the whole MAC PDU (e.g., both the part with HARQ related operation and the part without HARQ related operation) .
  • the part of the MAC PDU that needs the HARQ related operation e.g., the header information and/or control information
  • a retransmission of the part of the MAC PDU that does not need the HARQ related operation e.g., the source data block or payload
  • a retransmission of the whole MAC PDU e.g., both the part with HARQ related operation and the part without HARQ related operation
  • the PDCCH to which the DL assignment may be addressed to may contain the indications to indicate a retransmission, the indication may be at least one of the following information:
  • a HARQ process Indication to indicate which HARQ process to be scheduled as retransmission.
  • a Retransmission granularity level indication to indicate the retransmission granularity level.
  • the retransmission may be for the part of the MAC PDU that needs HARQ operation, or the retransmission may be for the part of the MAC PDU that does not need HARQ related operation, or the retransmission may be for the whole MAC PDU.
  • a CBG indication to indicate that the CBGs of the part of MAC PDU that needs HARQ operation to be scheduled as retransmission.
  • the CBG indication is optionally present in PDCCH, it may be only present in PDCCH when the retransmission is for the part of the MAC PDU that needs HARQ operation.
  • a Retransmission indication to indicate such DL assignment is for retransmission associated with the indicated HARQ process Id.
  • the retransmission indication may be a toggled NDI value compare to the NDI value received from the previous UL grant for the indicated HARQ process Id.
  • the NACK signaling format may be implemented as one of:
  • Such signaling format may contain at least one of the following information items:
  • the part of MAC PDU indication to indicate which part of MAC PDU has failed to be received, e.g., the part with HARQ related operation, or the part without HARQ related operation, or both.
  • a switch between the new transmission type (e.g., semantic transmission) and the legacy transmission type (e.g., symbol based transmission) may be implemented on the network side including the following example steps, as shown in FIG. 17:
  • ⁇ STEP 1 The control signaling to activate/deactivate the HARQ operation for the new type transmission may be received from the NW side.
  • ⁇ STEP 2 The UE may perform an activation/deactivation of the HARQ operation for the new type transmission according to the received control signaling.
  • the control signaling may be implemented as a lower layer signaling, e.g., a PDCCH signaling containing an indication to indicate whether the HARQ operation is activated for the scheduled HARQ process Id by such PDCCH.
  • a PDCCH signaling containing an indication to indicate whether the HARQ operation is activated for the scheduled HARQ process Id by such PDCCH.
  • the indication one bit in the PDCCH may be used, the value ‘1’ of such bit means the HARQ operation may be activated for this transmission schedule by the PDCCH, while the value ‘0’ of such bit means the HARQ operation may be deactivated for this transmission schedule by the PDCCH.
  • control signaling may be a high layer signaling, e.g., a MAC CE, an SDAP/PDCP/RLC control PDU.
  • control signaling may indicate or include at least one of the following information items:
  • a logical path indication to indicate one or more logical paths from which the new type data transmission is activated or deactivated.
  • the logical path may be a radio bearer.
  • the logical path may be logical channel.
  • the logical path may be an RLC entity, PDCP entity, or SDAP entity, or mix of any of them.
  • an activation/deactivate indication to indicate an activation/deactivation of the HARQ operation for the indicated logical paths in the same control signaling.
  • a serving cell/BWP indication to indicate one or more serving cells where the new type transmission is activated or deactivated.
  • a lower layer may deactivate HARQ related operation for the data block or TB corresponding to a HARQ process if the received PDCCH indicating that the new type transmission is deactivated for the indicated HARQ process. Otherwise, the lower layer may activate the HARQ related operation for the data block or TB corresponding to the indicated HARQ process.
  • a higher layer may deactivate the HARQ related operation for the data transmission for which the data from the indicated logical path if a received control signaling indicating that the new type transmission is deactivated for the indicated logical path. Otherwise, the higher layer may activate the HARQ related operation for the data block or TB from the indicated logical path.
  • the activation/deactivation of HARQ operation may be performed by switching of the transmission type (e.g., switch from TYPE 1 transmission to TYPE 2 transmission, or switch from TYPE 2 transmission to TYPE 1 transmission) .
  • the activation of HARQ operation may be associated with a switch from TYPE 1 transmission to TYPE 2 transmission, whereas the deactivation of HARQ operation may be associated with a switch from TYPE 2 transmission to TYPE 1 transmission.
  • the TYPE 1 transmission and TYPE 2 transmission have been defined above.
  • a switch between the new transmission type (e.g., semantic transmission) and the legacy transmission type (e.g., symbol based transmission) may be implemented on the UE side including the following example steps, as shown in FIG. 18:
  • a configuration (e.g., an RRC configuration) may be received for the new type transmission by the UE from the NW.
  • ⁇ STEP 2 The UE may start performing the measurement (s) with respect to the new type transmission and calculate transmission metrics.
  • ⁇ STEP 3a The UE may send a request of activation/deactivation of the new type transmission to the NW.
  • STEP 3b (alternative to STEP 3a) : The UE may send a notification of activation/deactivation of the new type transmission to the NW.
  • ⁇ STEP 4 The UE may receive a response to the notification/request in STEP 3 from the NW.
  • the RRC configuration for the new type transmission may indicate or include at least one of the following information items:
  • a benchmark for the UE to determine the activation/deactivation of the new type transmission which may include one of a threshold/benchmark value of SINR, a threshold/benchmark value of RSRP, a threshold/benchmark value of RSRQ, or a threshold/benchmark value of transmission failure ratio/transmission failure times.
  • ⁇ A period for the UE to perform the measurement to determine the activation/deactivation of the new type transmission which may include at least one of a COUNTER with a maximum number value or a time period for a measurement.
  • the reference signaling (e.g., CSI-RS, SSB, and the like) used for the measurement (s) .
  • the UE may perform the measurement (s) on reference signals for the new type transmission. In case that the new transmission type is activated, if the measurement result is lower than a threshold in a certain period, the UE may determine that the new type transmission for the HARQ process/logical path needs to be deactivated.
  • the UE may perform the calculation of the transmission failure times/ratios in a period of time to determine the activation/deactivation of the NW type transmission for a HARQ process and/or logical path.
  • the transmission failure times/ratios may be calculated based on the header information/control information.
  • the UE may determine to deactivate the new type transmission for the HARQ process or the logical path.
  • a counter to track the number of transmission failures may be included, and the timer period described above may be predetermined and defined.
  • the UE may determine to deactivate the new type transmission for the HARQ process or the logical path.
  • two counters to count the number of transmission failures may be included.
  • One of the counters for example, may be configured for the total number of transmission times, whereas the other one of the counters may be configured for tracking the total number of transmission failure times.
  • the timer period above may be predetermined and defined.
  • the UE may perform the measurement (s) on reference signals for the new type transmission. In case that the new transmission type has been deactivated, if the measurement result is higher than a threshold in a certain period, the UE may determine that the new type transmission for the HARQ process/logical path can be activated.
  • the request/notification message may be of at least one of the following formats:
  • Higher layer signaling including a UL RRC signaling for, e.g., the UE assistance information, or a UL MAC CE, an SDAP/PDCP/RLC Control PDU.
  • Lower layer signaling include a PUCCH signaling, a PUSCH signaling, or the like.
  • the request/notification message may indicate and/or include at least one of the following information items:
  • An activation/deactivation indication to indicate the activation/deactivation of the new type transmission for the indicated HARQ process and/or logical path.
  • the response message from the NW may be a control signaling to activate/deactivate the new type transmission to the HARQ process and/or logical path.
  • terms, such as “a, ” “an, ” or “the, ” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

Landscapes

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

Abstract

La présente divulgation concerne de manière générale des réseaux de communication sans fil et, en particulier, des architectures de réseau pour effectuer une transmission ou une communication de données de nouveau type pour des informations avec une tolérance d'erreur de transmission, telle qu'une communication sémantique. En particulier, plusieurs aspects dans l'architecture et la signalisation de réseau sans fil sont divulgués pour réaliser la transmission de données de nouveau type entre un terminal sans fil et un réseau sans fil. La modification des systèmes sans fil existants est mise en œuvre afin de s'adapter à des modèles de codeur/décodeur de source, à leur gestion et à leur activation/désactivation sur la base de performances de modèle et de conditions de canal de réseau. Les données dans une telle communication de données de nouveau type peuvent être bifurquées en données sans erreur et en données tolérantes aux erreurs qui peuvent être traitées distinctement par le réseau sans fil modifié.
PCT/CN2024/074125 2024-01-25 2024-01-25 Procédé pour un nouveau type de transmission de données dans un réseau sans fil Pending WO2025156230A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/074125 WO2025156230A1 (fr) 2024-01-25 2024-01-25 Procédé pour un nouveau type de transmission de données dans un réseau sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/074125 WO2025156230A1 (fr) 2024-01-25 2024-01-25 Procédé pour un nouveau type de transmission de données dans un réseau sans fil

Publications (1)

Publication Number Publication Date
WO2025156230A1 true WO2025156230A1 (fr) 2025-07-31

Family

ID=96544115

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/074125 Pending WO2025156230A1 (fr) 2024-01-25 2024-01-25 Procédé pour un nouveau type de transmission de données dans un réseau sans fil

Country Status (1)

Country Link
WO (1) WO2025156230A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180295651A1 (en) * 2017-04-06 2018-10-11 Huawei Technologies Co., Ltd. Flexible Grant-Free Resource Configuration Signaling
US20210376963A1 (en) * 2018-11-08 2021-12-02 Nec Corporation Method and devices for hybrid automatic repeat request
US20220069950A1 (en) * 2019-01-09 2022-03-03 Panasonic Intellectual Property Corporation Of America Base station, terminal, and communication method
US20220070938A1 (en) * 2019-01-17 2022-03-03 Samsung Electronics Co., Ltd. Method and apparatus for performing communication in wireless communication system
CN116746268A (zh) * 2021-01-15 2023-09-12 中兴通讯股份有限公司 无线网络中传输资源或传输参数更新的方法、设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180295651A1 (en) * 2017-04-06 2018-10-11 Huawei Technologies Co., Ltd. Flexible Grant-Free Resource Configuration Signaling
US20210376963A1 (en) * 2018-11-08 2021-12-02 Nec Corporation Method and devices for hybrid automatic repeat request
US20220069950A1 (en) * 2019-01-09 2022-03-03 Panasonic Intellectual Property Corporation Of America Base station, terminal, and communication method
US20220070938A1 (en) * 2019-01-17 2022-03-03 Samsung Electronics Co., Ltd. Method and apparatus for performing communication in wireless communication system
CN116746268A (zh) * 2021-01-15 2023-09-12 中兴通讯股份有限公司 无线网络中传输资源或传输参数更新的方法、设备及系统

Similar Documents

Publication Publication Date Title
US12047807B2 (en) Method for processing data in consideration of TCP/IP
US11445403B2 (en) Method for processing data in consideration of TCP/IP
US11096241B2 (en) Reducing layer-2 protocol overhead by improving layer processing efficiency
CN115765943B (zh) 一种被用于无线通信的节点中的方法和装置
JP5215413B2 (ja) 再送プロトコルのためのステータス報告
EP3566353B1 (fr) Procédés et appareils dans un système de communication sans fil
US10420134B2 (en) System and method to facilitate subframe scheduling in a split medium access control radio access network environment
US9467892B2 (en) Method and apparatus for transmitting data packet
US11943053B2 (en) Code block header for fast RLC PDU deliveries in 5G NR
JP2011530943A (ja) 無線通信システムのデータ再伝送資源割り当て方法及び装置
CN115699631B (zh) 用于配置网络编码和控制网络编码启用的方法和设备
CN113796057A (zh) 无线通信系统中防止数据丢失的用户数据压缩方法和装置
US20250184047A1 (en) Infrastructure equipment, mobile terminal, computer software and methods
US20220263606A1 (en) Ntn-based data transmission method and apparatus and storage medium
US20190356422A1 (en) Wireless communication system, base station device, terminal device, and wireless communication method
KR20190097963A (ko) 무선 통신 시스템에서 데이터 송수신 방법 및 장치
EP3682575B1 (fr) Communication radio d'unités de données de paquets critiques
WO2017220855A1 (fr) Procédé et appareil pour réaliser une duplication de paquets dans un scénario à connectivité multiple
US12003331B2 (en) Wireless data transmission apparatus, wireless data reception apparatus and methods
JP7500746B2 (ja) ネットワークコーディング動作の中断及び再開をシグナリングする方法及び装置
WO2025156230A1 (fr) Procédé pour un nouveau type de transmission de données dans un réseau sans fil
WO2025156229A1 (fr) Procédé pour un nouveau type de transmission de données dans un réseau sans fil
WO2025156232A1 (fr) Procédé pour un nouveau type de transmission de données dans un réseau sans fil
US9307419B1 (en) Data transmission throughput for a wireless access node
US20240146462A1 (en) Relay-assisted retransmission

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: 24919339

Country of ref document: EP

Kind code of ref document: A1