Method and signaling to enable semantic communications in wireless networks

Abstract

Described herein is a method and signaling for data transmission in a communication network, wherein semantic communication is admitted by the communication network, upon receiving a request for semantic communication service. Subsequently resource elements, RE, of the physical, PHY, layer and / or the media access control, MAC, layer of the standard protocol are selected for semantic communication and overloaded for semantic communication. The selected RE are associated to a semantic-data radio bearer, S-DRB. Therefore, the effects on the system can be limited while at the same time semantic communication can be achieved. Semantic communications therefore overloads (or substitutes) some of the standard functionalities while at the same time preserving compatibility with legacy services.

Description

METHOD AND SIGNALING TO ENABLE SEMANTIC COMMUNICATIONS IN WIRELESS NETWORKSTECHNOLOGY

[0001] The present disclosure relates to semantic communications in wireless networks, in particular to methods and signaling to overload at least some of the standard functionalities of e.g. the modulation and coding schemes, MCS, for allowing semantic communication.BACKGROUND

[0002] Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field.

[0003] In “The mathematical theory of communication”, by Shannon and Weaver (Vol. 517. Champaign IL: University of Illinois Press 1964), three types of problems in the field of communications were identified: Procedural problem: How accurately can the symbols of communication be transmitted?; Semantic problem: How precisely do the transmitted symbols convey the desired meaning? Effectiveness problem: How effectively does the received meaning affect conduct in the desired way?

[0004] In legacy communications systems these problems are solved by systems designed based on Shannon’s classical work, which independently optimize the communications system and set aside the intention of the task. However, for the more ambitious use cases such as metaverse and holograms in 5G and beyond, such independent communication and application processes (e.g., application feature extraction, source coding, channel coding, adaptive modulation and coding etc.) may lead to highly redundant information and extra computational effort. Current trends in wireless communication systems therefore suggestconcepts for further reducing redundant information and reducing the computational effort by using semantic communication.

[0005] However, known concepts neglect a key enabler for the semantic and effective communication system. Specifically, common concepts currently do not provide the opportunity to extend the existing standard functionalities and at the same time enable an end-to-end communication taking the indicated semantic and effectiveness problem into account.

[0006] Thus, there is a need to extend current standard functionalities to enable semantic communications and guaranteeing compatibility with the standard protocols in wireless networks, mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems.SUMMARY

[0007] To solve the problems the features of the independent claims are suggested. Further preferred developments are in the dependent claims.

[0008] In accordance with an aspect of the present disclosure, there is provided a method for data transmission in a communication system, more specifically, a method for overloading wireless network functionalities in the communication system. In one implementation the communication system may be a wireless network, mobile or wireless telecommunication system, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications system. The method may include the step of, admitting upon request for semantic communication service, semantic communication (or preferably accepting a quality of service, QoS, requirement for semanticcommunication (for example, the QoS requirement as transmitted from a network element to a base station) and admitting semantic communication by the communication system (or base station)). Therefore, the system may allow semantic communication upon acceptance of a request for semantic communication so that semantic communication is admitted together with legacy communication services (preferably in a system for legacy communication). Moreover, resource elements, RE, (and / or resource blocks) of the physical, PHY, layer and / or the media access control, MAC, layer may be selected for semantic communication and the selected RE may be associated to a special bearer type designed for semantic communications, hereafter called semantic data radio bearer (S-DRB); (preferably the generated signal may then be transmitted). Accordingly, overloading of the standard protocol by mapping the semantic data on the S-DRB may be performed so as to transmit with the physical layer, PHY, and / or the media access control layer, MAC, information for semantic communication. These steps may be performed by a first network element which may be a user equipment, UE, or a base station, a core network entity or a network management entity. Accordingly, a concept is provided to extend the existing standard functionalities to enable an end-to-end communication for semantic and effective communication. It is proposed to integrate semantic communications into the standard communication protocols while at the same time assuring compatibility with existing network standards.

[0009] In some examples, the method for data transmission in a communication system, further includes, for generating a signal to be transmitted, overloading (= substituting one existing functionality in legacy standards with a new functionality) at least a part of a standard protocol of the communication system by occupying the selected RE for semantic communication and transmitting the generated signal, while at the same time preservingcompatibility with legacy services. In other words, overloading may be considered as substitution of an existing functionality in legacy standard with a new functionality, or executing the task of the overloaded legacy functionality in a different way.

[0010] In some examples, overloading of a standard protocol includes overloading at least a part of the modulation and coding schemes, MCS, for semantic communication.

[0011] In some further examples, the method comprises, receiving at a base station a request for semantic communication including QoS requirements for semantic communication and / or a configuration for overloading parametrization.

[0012] In some examples, the RE are scheduled by semi persistent scheduling, SPS, persistent scheduling, PS, or by dynamic scheduling, DS.

[0013] In some examples, the method further comprises: receiving a scheduling request from a user equipment, UE, allocating resources in accordance with the received scheduling request by function overloading at least part of the PHY layer and / or MAC layer procedure to enable semantic communication. Accordingly, in contrast to legacy communication, where the system assigns resources based on its own scheduling algorithm, for semantic communication according to the present disclosure, the system provides exactly the resource elements (REs) that a semantic communication (or semantic application) requires.

[0014] In some examples the QoS requirements for semantic communication include a specific (or fixed) number of required RE or physical resource blocks, PRB.

[0015] In some examples, the QoS requirements for semantic communication indicates an adaptive amount of required RE or physical resource blocks, PRB, depending on channel feedback. In this relation channel feedback may be performed with any known technique such as CSI feedback, UL channel estimation with SRS, etc.

[0016] In some examples, based on a parameter in the QoS requirements for semantic communication, the semantic communication is set to be a dynamic communication requiring to be triggered or a periodic communication.

[0017] In some examples, an expected inter-arrival time of the requests is defined in the QoS requirements for semantic communication to set the required period of allocations or an average value thereof.

[0018] In some examples, an overloading type (for example a first or second overloading type) is defined in the QoS requirements for semantic communication to determine the accepted type of overloading for the semantic communication.

[0019] In some examples, for overloading the standard protocol, selected one or more PRBs are associated to the S-DRB (i.e. a special bearer type designed for semantic communications) while maintaining at least one of the numerologies, the frame structure, the pilots, the control channel and the RE mapping in order to remain compatible with the standard frame structure. Moreover, the S-DRB may be defined as a DRB (or logical channel) associated to semantic communications, with their own QoS definition (instead of legacy QoS paradigms such as 5QI for data). For instance, a feature associated to S-DRB may be the overloading requirement, optionally number of RE, update rate, etc. In one further preferable aspect the scheduling operations concerning S-DRB are defined to be different than legacy scheduling operation.

[0020] In some examples, at least a part of the demodulation reference signal, DMRS, is assigned for semantic communication and overloaded, wherein the downlink control information, DCI, indicates that the PRB are allocated to semantic communication and overloaded. Moreover, the in a preferable development the DCI (for semantic communication) can include an extension for indicating the overloading type. Moreover awarning may be included, so that in case the demodulation reference signal, DMRS, is either partially or completely overloaded where PRBs are allocated to semantic communications, UEs can be properly warned not to use the corresponding REs to estimate the channel. Accordingly, in a preferable development, overloading includes the feature of substituting one existing functionality in legacy standards with a new functionality and additionally changing how the transmitted signal is generated (and mapped to each resource element). Preferably a standardized encoding is performed, then M-QAM modulation (M-ary Quadrature Amplitude Modulation) translates everything in complex symbols allocated. Accordingly, in this further development overloading allows semantic communications to determine these complex symbols on its own, thereby skipping standard encoding and modulation steps. Accordingly, a concept is provided to extend the existing standard functionalities to enable an end-to-end communication for semantic and effective communication. It is proposed to integrate semantic communications into the standard communication protocols while at the same time assuring compatibility with existing network standards.

[0021] In some examples, for assuring that the transmission matches required transmission requirements, a power control mechanism is included in the semantic communication,,, in the way used by semantic communications to determine the transmitted signal. Preferably, at least one of a power control or beamforming or waveform shaping mechanism can be included in the semantic communication. As the decoder of the semantic communication takes the received symbols directly as inputs to compute the goal-oriented outputs, the quality of the received symbol (e.g., symbol error rate) is critical for the end-to- end performance, unlike the legacy communication that focuses more on the bit error rate.Thus, the corresponding power control / beamforming / waveform shaping mechanisms can be included to improve the end-to-end performance.

[0022] In some examples, at least a part of the control resource set, CORESET, resources are assigned for semantic communication and overloaded.

[0023] In some examples, for a full-slot overloaded type, an entire bandwidth part or the full bandwidth in the carrier is assigned for semantic communication and overloaded.

[0024] In some examples, for the full-slot overloaded type the MCS and a part of the control channel is overloaded.

[0025] In some examples, for the full-slot overloaded type, and in case of a downlink,DL, SPS, the entire slot is overloaded and a power control mechanism is included in the semantic communication.

[0026] In some examples, for the full-slot overloaded type, and in case of DL, the method includes an initial transmission of a standard compliant symbol indicating that the current slot is fully overloaded for a given S-DRB (a special bearer type designed for semantic communications).

[0027] A method for data transmission in a communication system, may comprise: transmitting to a base station a request for semantic communication services. Preferably the request includes QoS requirements for semantic communication and / or a configuration for overloading parametrization. Specifically in one implementation the gNB is configured to decide if the semantic communication is admitted. After semantic communication has been admitted, receiving or transmitting a signal in which at least a part of a standard protocol is overloaded by occupying selected resource elements, RE, of the physical, PHY, layer and / or the media access control, MAC, layer for semantic communication.

[0028] In some examples, the RE are scheduled by semi persistent scheduling, SPS, persistent scheduling, PS, or by dynamic scheduling, DS.

[0029] In some examples, the method further comprises: transmitting a scheduling request from a user equipment, UE, allocating resources in accordance with the transmitted scheduling request by function overloading at least part of the PHY layer and / or MAC layer procedure to enable semantic communication.

[0030] In some examples, an apparatus comprises at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: admit semantic communication if a request for semantic communication service is received and / or a quality of service, QoS, requirement for semantic communication is fulfilled; select resource elements, RE, of a physical, PHY, layer and / or a media access control, MAC, layer for semantic communication and associate the selected RE to a semantic-data radio bearer, S-DRB while at the same time preserving compatibility with legacy services.

[0031] In some examples, the apparatus is further caused to, for generating a signal to be transmitted, overload at least a part of a standard protocol of the communication system by occupying the selected RE for semantic communication and transmitting the generated signal, wherein overloading of a standard protocol includes overloading at least a part of the modulation and coding schemes, MCS, for semantic communication while at the same time preserving compatibility with legacy services. The apparatus may thereby be a base station or in a further implementation a semantic UE (or network element) which is a UE (or network element) for semantic communication.

[0032] In some examples, the resource elements for semantic communication are allocated based on a predefined required number of resource elements, which is a fixednumber of required resource elements per S-DRB. Moreover, the resource elements for semantic communication may be allocated based on a channel feedback to determine a number of required resource elements. In addition, using DS and SPS the radio resource (such as resource elements or resource blocks) are allocated by the scheduler for semantic communication. Moreover, in a further preferrable development a joint scheduler is provided that co-schedules legacy communications with semantic communications.

[0033] In addition, according to some other example embodiments, there is provided, for example, a computer program product for a wireless communication device comprising at least one processor, including software code portions for performing the respective steps disclosed in the present disclosure, when said product is run on the device. The computer program product may include a computer-readable medium on which said software code portions are stored. Furthermore, the computer program product may be directly loadable into the internal memory of the computer and / or transmittable via a network by means of at least one of upload, download and push procedures.

[0034] While some example embodiments will be described herein with particular reference to the above application, it will be appreciated that the present disclosure is not limited to such a field of use, and is applicable in broader contexts. Moreover, a computer program may be provided comprising instructions for causing an apparatus to perform the method as described above. In addition, a memory storing computer readable instructions for causing an apparatus to perform the method as described, may be provided.

[0035] Notably, it is understood that methods according to the present disclosure relate to methods of operating the apparatuses according to the above example embodiments and variations thereof, and that respective statements made with regard to the apparatuseslikewise apply to the corresponding methods, and vice versa, such that similar description may be omitted for the sake of conciseness. In addition, the above aspects may be combined in many ways, even if not explicitly disclosed. The skilled person will understand that these combinations of aspects and features / steps are possible unless it creates a contradiction which is explicitly excluded.

[0036] Implementations of the disclosed apparatuses may include using, but not limited to, one or more processor, one or more application specific integrated circuit (ASIC) and / or one or more field programmable gate array (FPGA). Implementations of the apparatus may also include using other conventional and / or customized hardware such as software programmable processors, such as graphics processing unit (GPU) processors.

[0037] Other and further example embodiments of the present disclosure will become apparent during the course of the following discussion and by reference to the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0038] For a more complete understanding of example embodiments of the present disclosure, reference is now made to the following description taken in connection with the accompanying drawings in which:

[0039] Figure 1 schematically illustrates an example of a sequence of processes required by a standard communication system;

[0040] Figure 2 schematically illustrates an example of a signaling / messaging diagram according to an example embodiment of the present disclosure;

[0041] Figures 3 schematically illustrate a further example of a signaling / messaging diagram according to an example embodiment of the present disclosure using dynamic scheduling;

[0042] Figure 4 schematically illustrates a further example of a signaling / messaging diagram according to an example embodiment of the present disclosure using semi-persistent scheduling; and

[0043] Figures 5a to 5d schematically illustrate allocation of physical resource blocks according to example embodiments of the present disclosure.DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

[0044] References are made to the figures and it is to be noted that identical or like reference numbers used in the figures of the present disclosure may, unless indicated otherwise, indicate identical or like elements, such that repeated description thereof may be omitted for reasons of conciseness.

[0045] In the following, different exemplifying embodiments will be described using, as an example of a communication network to which examples of embodiments may be applied, a communication network architecture based on 3GPP standards for a communication network, such as a 5G / NR, without restricting the embodiments to such an architecture, however. It is apparent for a person skilled in the art that the embodiments may also be applied to other kinds of communication networks where mobile communication principles are integrated with a D2D (device-to-device) or V2X (vehicle to everything) configuration, such as SL (side link), e.g. Wi-Fi, worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, mobile ad-hoc networks (MANETs), wired access, etc. Furthermore, without loss of generality, the description of some examples of embodiments is related to a mobile communication network, but principles of the disclosure can be extended and applied to any other type of communication network, such as a wired communication network.

[0046] The following examples and embodiments are to be understood only as illustrative examples. Although the specification may refer to “an”, “one”, or “some” example(s) or embodiment(s) in several locations, this does not necessarily mean that each such reference is related to the same example(s) or embodiment(s), or that the feature only applies to a single example or embodiment. Single features of different embodiments may also be combined to provide other embodiments. Furthermore, terms like “comprising” and “including” should be understood as not limiting the described embodiments to consist of only those features that have been mentioned; such examples and embodiments may also contain features, structures, units, modules, etc., that have not been specifically mentioned.

[0047] A basic system architecture of a (tele)communication network including a mobile communication system where some examples of embodiments are applicable may include an architecture of one or more communication networks including wireless access network subsystem(s) and core network(s). Such an architecture may include one or more communication network control elements or functions, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point (AP), a NodeB (NB), an eNB or a gNB, a distributed unit (DU) or a centralized / central unit (CU), which controls a respective coverage area or cell(s) and with which one or more communication stations such as communication elements or functions, like user devices or terminal devices, like a user equipment (UE), or anotherdevice having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a station, an element, a function or an application capable of conducting a communication, such as a UE, an element or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of conducting a communication, or the like, are capable to communicate via one or more channels via one or more communication beams for transmitting several types of data in a plurality of access domains. Furthermore, core network elements or network functions, such as gateway network elements / functions, mobility management entities, a mobile switching center, servers, databases and the like may be included.

[0048] The following description may provide further details of alternatives, modifications and variances: a gNB comprises e.g., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC, e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2 incorporated by reference.

[0049] A gNB Central Unit (gNB-CU) comprises e.g., a logical node hosting e.g., RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the Fl interface connected with the gNB-DU.

[0050] A gNB Distributed Unit (gNB-DU) comprises e.g., a logical node hosting e.g., RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU.

[0051] A gNB-CU-Control Plane (gNB-CU-CP) comprises e.g., a logical node hosting e.g., the RRC and the control plane part of the PDCP protocol of the gNB-CU for an en-gNB or a gNB. The gNB-CU-CP terminates the El interface connected with the gNB-CU-UP and the Fl-C interface connected with the gNB-DU.

[0052] A gNB-CU-User Plane (gNB-CU-UP) comprises e.g., a logical node hosting e.g., the user plane part of the PDCP protocol of the gNB-CU for an en-gNB, and the user plane part of the PDCP protocol and the SDAP protocol of the gNB-CU for a gNB. The gNB-CU- UP terminates the El interface connected with the gNB-CU-CP and the Fl-U interface connected with the gNB-DU, e.g., according to 3GPP TS 38.401 V16.6.0 (2021-07) section 3.1 incorporated by reference.

[0053] Different functional splits between the central and distributed unit are possible, e.g., called options:

[0054] Option 1 (lA-like split):

[0055] • The function split in this option is similar to the 1A architecture in DC. RRC is in the central unit. PDCP, RLC, MAC, physical layer and RF are in the distributed unit.

[0056] Option 2 (3C-like split):

[0057] • The function split in this option is similar to the 3C architecture in DC. RRC and PDCP are in the central unit. REC, MAC, physical layer and RF are in the distributed unit.

[0058] Option 3 (intra REC split):

[0059] • Eow REC (partial function of RLC), MAC, physical layer and RF are in the distributed unit. PDCP and high RLC (the other partial function of RLC) are in the central unit.

[0060] Option 4 (RLC-MAC split):

[0061] • MAC, physical layer and RF are in the distributed unit. PDCP and RLC are in the central unit.

[0062] Or else, e.g., according to 3GPP TR 38.801 V14.0.0 (2017-03) section 11 incorporated by reference.

[0063] A gNB supports different protocol layers, e.g., Layer 1 (LI) - physical layer.

[0064] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where e.g.:

[0065] • The physical layer offers to the MAC sublayer transport channels;

[0066] • The MAC sublayer offers to the RLC sublayer logical channels;

[0067] • The RLC sublayer offers to the PDCP sublayer RLC channels;

[0068] • The PDCP sublayer offers to the SDAP sublayer radio bearers;

[0069] • The SDAP sublayer offers to 5GC QoS flows;

[0070] • Comp, refers to header compression and Segm. To segmentation;

[0071] • Control channels include (BCCH, PCCH).

[0072] Layer 3 (L3) includes e.g., Radio Resource Control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6 incorporated by reference.

[0073] A RAN (Radio Access Network) node or network node like e.g. a gNB, base station, gNB CU or gNB DU or parts thereof may be implemented using e.g. an apparatus with at least one processor and / or at least one memory (with computer-readable instructions (computer program)) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (Radio Access Network), e.g. layer 2 and / or layer 3.

[0074] The gNB CU and gNB DU parts may e.g., be co-located or physically separated. The gNB DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A Central Unit (CU) may also be called BBU / REC / RCC / C-RAN / V-RAN, O-RAN, or part thereof. A Distributed Unit (DU) may also be called RRH / RRU / RE / RU, or part thereof. Hereinafter, in various example embodiments of the present disclosure, the CU-CP (or more generically, the CU) may also be referred to as a (first) network node that supports at least one of central unit control plane functionality or a layer 3 protocol of a radio access network; and similarly, the DU may be referred to as a (second) network node that supports at least one of distributed unit functionality or the layer 2 protocol of the radio access network.

[0075] A gNB-DU supports one or multiple cells, and could thus serve as e.g., a serving cell for a user equipment (UE).

[0076] A user equipment (UE) may include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (Radio Access Network), a smartphone, an in- vehicle apparatus, an loT device, a M2M device, or else. Such UE or apparatus may comprise: at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, like e.g. RRC connection to the RAN. A UE is e.g., configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). A UE may generate and transmit and receive RRC messages containing one or more RRC PDUs (Packet Data Units).

[0077] The UE may have different states (e.g., according to 3GPP TS 38.331 V16.5.0 (2021-06) sections 42.1 and 4.4, incorporated by reference).

[0078] A UE is e.g., either in RRC_CONNECTED state or in RRCJNACTIVE state when an RRC connection has been established.

[0079] In RRC_CONNECTED state a UE may:

[0080] • store the AS context;

[0081] • transfer unicast data to / from the UE;

[0082] • monitor control channels associated with the shared data channel to determine if data is scheduled for the data channel;

[0083] • provide channel quality and feedback information;

[0084] • perform neighboring cell measurements and measurement reporting.

[0085] The RRC protocol includes e.g. the following main functions:

[0086] • RRC connection control;

[0087] • measurement configuration and reporting;

[0088] • establishment / modification / release of measurement configuration (e.g. intrafrequency, inter- frequency and inter-RAT measurements);

[0089] • setup and release of measurement gaps;

[0090] • measurement reporting.

[0091] The general functions and interconnections of the described elements and functions, which also depend on the actual network type, are known to those skilled in the art and described in corresponding specifications, so that a detailed description thereof may omitted herein for the sake of conciseness. However, it is to be noted that several additional network elements and signaling links may be employed for a communication to or from an element, function or application, like a communication endpoint, a communication network control element, such as a server, a gateway, a radio network controller, and other elements of the same or other communication networks besides those described in detail herein below.

[0092] A communication network architecture as being considered in examples of embodiments may also be able to communicate with other networks, such as a public switched telephone network or the Internet. The communication network may also be able to support the usage of cloud services for virtual network elements or functions thereof, wherein it is to be noted that the virtual network part of the telecommunication network can also be provided by non-cloud resources, e.g. an internal network or the like. It should be appreciated that network elements of an access system, of a core network etc., and / or respective functionalities may be implemented by using any node, host, server, access node or entity etc. being suitable for such a usage. Generally, a network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0093] Furthermore, a network element, such as communication elements, like a UE, a terminal device, control elements or functions, such as access network elements, like a base station / BS, a gNB, a radio network controller, a core network control element or function, such as a gateway element, or other network elements or functions, as described herein, and any other elements, functions or applications may be implemented by software, e.g., by a computer program product for a computer, and / or by hardware. For executing their respective processing, correspondingly used devices, nodes, functions or network elements may include several means, modules, units, components, etc. (not shown) which are required for control, processing and / or communication / signaling functionality. Such means, modules, units and components may include, for example, one or more processors or processor units including one or more processing portions for executing instructions and / or programs and / or for processing data, storage or memory units or means for storing instructions, programsand / or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and / or connections under the control of the processor unit or portion (e.g. wired and wireless interface means, radio interface means including e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also located on a remote site (e.g. a radio head or a radio station etc.). It is to be noted that in the present specification processing portions should not be only considered to represent physical portions of one or more processors, but may also be considered as a logical division of the referred processing tasks performed by one or more processors. It should be appreciated that according to some examples, a so-called “liquid” or flexible network concept may be employed where the operations and functionalities of a network element, a network function, or of another entity of the network, may be performed in different entities or functions, such as in a node, host or server, in a flexible manner. In other words, a “division of labor” between involved network elements, functions or entities may vary case by case.

[0094] As illustrated above, the present disclosure generally seeks to provide a concept to extend the existing standard functionalities to enable an end-to-end communication for the semantic and effective communication. For that matter it is proposed to integrate semantic communications into the standard communication protocols while at the same time assuring compatibility with existing network standards.

[0095] Semantic communication relates to the transmission of semantic information conveyed by a source rather than the accurate reception of each single symbol regardless of its meaning. Although current concepts also consider the challenges of semantic and effective communication, conventional proposals merely provide general concepts of semantic communication and effectiveness communication. However, despite these concepts and architecture design, these proposals neglect a key enabler for the semantic and effectiveness communication system, namely, how to extend the existing standard functionalities and enable an end-to-end communication for the semantic and effectiveness problem. Moreover, up to now it was not considered in common communication schemes to implement a resource allocation in terms of physical resource blocks (PRBs) / frame and also the coexistence of traditional and semantic users in the network system.

[0096] In order to fully grasp the concept of the present disclosure, basics of a semantic / effective communication scheme need to be considered. For example, in the architecture of training a joint source and channel coding (JSCC) scheme for wireless image retrieval, the JSCC solution directly encodes the desired feature for image retrieval to the channel symbols and provides them to the communications system to transmit. In other words, joint source and channel coding can be summarized as the encoding of a redundant information source for transmission over a (noisy) channel, and the corresponding decoding, using a single code instead of the conventional steps of source coding followed by channel coding etc. However, with the current standard communications protocols, this cannot be generally implemented. Specifically, the standard communications system follows a sequence of strict processes, which may be summarized as follows: “source to source encoder to channel encoder to modulator to transmitter (transmitter antenna) to channel to receiver (receiver antenna) to demodulator to channel decoder to source decoder todestination”, as shown in Figure 1. Figure 1 consequently shows a digital communications system block diagram of a standard communications system. In particular, the modulation and coding schemes (MCSs) used in the standard define a precise way to encode the information and transmit it over the air with the standardized waveform, that in 5G is CP- OFDM (orthogonal frequency division multiplexing, OFDM, a technique using cyclic prefixes, CP, instead of null guards, protecting OFDM signals from intersymbol interference, ISI). Such a digital communications system expects the application to encode its desired information into binary bits, and the communications system is responsible for optimizing the conversion between digital bits and symbols, guaranteeing that the provided information bits are accurately transmitted and received.

[0097] In contrast, in the semantic / effective communication scheme, the application and communication system may collaborate to encode the required features directly into symbols to transmit, and, to decode the received symbols directly to the desired goals (e.g., predicted outputs or control actions).

[0098] Therefore, it is suggested that standard protocols of source coding, channel coding and modulation may be overloaded (in the programming sense, i.e., defining a different implementation / working mode for the same entity). Moreover, it may be suitable to perform a type of function overloading. Function overloading thereby is the ability to create multiple functions of the same name with different implementations. Calls to an overloaded function (or functionalities) will run a specific implementation of that function appropriate to the context of the call, allowing one function call to perform different tasks depending on context. In the present disclosure the way the overloaded standard functionalities are processed are determined by network elements, for example by the configuration of thenetwork element such as a user equipment, UE, and particularly whether the UE is a semantic UE, i.e. a UE capable for semantic communication, or not.

[0099] It is therefore proposed to provide methods and signalling to overload (in the programming sense, i.e., defining a different implementation / working mode for the same entity) some of the standard functionalities to enable semantic communications in compatibility with wireless network standards.

[0100] Figure 2 schematically illustrates an example signaling / messaging diagram according to an embodiment of the present disclosure. In this non limiting embodiment, an example of an implementation of the present disclosure is shown and particularly the signaling between a base station, for example a gNB, and different types of UEs, or more broadly data radio beams, DRBs. It is therefore distinguished between semantic UEs or DRBs which are capable for semantic communication and non-semantic UEs or DRBs, which may be conventional and not capable for semantic communication. For the implementation of the semantic communication scheme of the present disclosure the presence of both, semantic and non-semantic UEs in the network are possible obeying the standard communication protocol, in particular regarding source coding, channel coding and modulation.

[0101] At service / flow / data radio bearer, DRB, configuration, the semantic UEs (or their clients) share their quality of service, QoS, requirements to the gNB. Of course, this is not mandatory in accordance with the present disclosure. In one implementation the QoS requirements may be predefined in the system and available at the gNB without the need of any transmission thereof. In another implementation the QoS requirements of a particular semantic UE may be transmitted to the gNB.

[0102] The gNB can then accept and / or decide whether to admit the semantic communication in the system. If the semantic communication is admitted, scheduling of radio resources for semantic communication can be decided. Of course, this is not mandatory in accordance with the present disclosure. In one example, the required radio resources can be requested by the semantic UE which provided and / or fulfils the accepted QoS requirements for semantic communication. Moreover, the semantic UE may be configured to transmit a scheduling request to the gNB in one implementation. This can be performed in real time, accordingly with procedures at every slot (and / or scheduling decision). Alternatively, this can be performed in non-real time (i.e. at a slower pace for saving resources) as procedures which typically happen at the beginning and / or with rare updates, such as QoS negotiation / setting or (semi-)persistent scheduling decision. Moreover, such a scheduling request may be required for the uplink, UL, dynamic configuration and particularly with dynamic scheduling requiring in UL a scheduling request operation. In case of UL-DS, a scheduling request should therefore be triggered by the semantic UE in order for the scheduler to allocate resources to it. Therefore, for UL, after a scheduling request from the UE is received, resources are granted by the gNB to the S-DRB, and the S-DRB can use these UL resources. A proper extension of logical channels, LCH, is implemented to handle scheduling requests of semantic communications and their corresponding QoS definitions.

[0103] In general, after the semantic communication is accepted, the required resources can be scheduled, in particular either semi-persistent scheduled, SPS, persistent scheduling, or with dynamic scheduling, DS, requiring in UL for a scheduling request operation.

[0104] With SPS and / or DS, radio resources can be allocated by the scheduler to semantic communications. The decision taken by the scheduler on whether to accept semanticcommunications and preferably how many resources to allocate to them is in one implementation performed in accordance with the QoS requirements and / or a received scheduling request. Moreover, after the resources are assigned, in one implementation the base station grants the scheduling request transmitting a respective scheduling grant signal to the UEs. In any case, the scheduling of the radio resources has to be compatible with and integrated into 3GPP standard frame structure.

[0105] Once the scheduler assigns radio resources, semantic communications can be performed, enabled by proper overloading of some of the physical, PHY, layer procedures and / or the media access control, MAC, layer procedures. The semantic communication can thereby be in UL, downlink, DL, and side link, SL.

[0106] Moreover, it is proposed to use different types of overloading mechanisms (overloading type) as an evolution of current 3GPP standards, trading off in different ways (i) freedom for semantic communications and (ii) number of overloaded features of standard, e.g., numerology, RE mapping, etc. Although the description is made in reference to the 3GPP terminology, a similar concept can apply for other network standards.

[0107] To summarize, semantic communication can be performed using different communications schemes requiring different concepts. The main options for the semantic communication schemes are therefore configurations based on SPS and DS as options for the scheduling of the resources. Moreover, these cases may be further differentiated for the UL and the DL and resulting different types of overloading. These concepts will be described in the following.

[0108] In general radio resources can be asked from semantic UEs while specifying the QoS requirements. The present disclosure envisions two main ways on how these resources can be granted by the scheduler. The former is with DS, where semantic communicationscan require dynamically resources when they need them (e.g., in the case of non-periodic operations). The latter allows a semantic data radio bearer, S-DRB, to require a periodic pattern of resources, that the scheduler can allocate with SPS mechanisms, in a way similar to what already implemented for communications. The main options for the semantic communication schemes are therefore configurations based on SPS and DS. Figure 3 is an implementation of semantic communication with DS and figure 4 is an implementation of semantic communication with SPS.

[0109] In figure 3 a flowchart shows DS handling S-DRBs. In one implementation DS requires the semantic UEs to define its QoS requirements upon connection (and / or with periodic long-term updates) in the RAN. Therefore, the QoS requirements may be shared with a base station in a first step, preferably together with an associated request for semantic communications. The request of the UE requiring semantic communication may also include parameters or parametrization for the overloading, in order to specify the allowable or preferrable overloading type (or types). Then, the scheduler may choose to allocate UL or DL resources dynamically in a way similar to what is already done for standard communications in the 3GPP standard frame structure. These resources are allocated and assigned in accordance with the different overloading types as described in relation to figures 5a to 5d. For UL, after a scheduling request from the UE, resources are granted by the gNB to the S-DRB, and finally the S-DRB can use these UL resources. In DL, the gNB can inform UEs that some resources are assigned to a S-DRB (e.g., with an extension of the DCI), and then these resources can be used to transmit the signal generated by the S-DRB.

[0110] As shown in figure 3 the UL communication is triggered in one implementation by the scheduling request of the semantic UE requesting the semantic communication, in UL or SL case 300A. After the gNB received the scheduling request a scheduling grant signal isreceived at the requesting semantic UE. Once the scheduler assigns radio resources, semantic communications can be performed, enabled by proper overloading. The semantic communication can be performed by the UE transmitting signals by overloading of some of the physical, PHY, layer procedures and / or the media access control, MAC, layer procedures (in accordance with an overloading type). Moreover, as shown in figure 3, in the DL case 300B, the gNB transmits semantic communications downlink control information, DCI, to the requesting semantic UE. More particularly, an extended DCI is transmitted. Preferably the DCI is extended for semantic communications with at least one of the following features:• Directly communicating any power degradation used on the resources allocated to S-DRBs. This can be important to calibrate the amplitude of the received signal properly at the receiver. With normal communications this is not necessary, since power changes are used also in the presence of pilots (DMRS), that may be overloaded with semantic communications in one of the proposed implementations.• Extension of the DCI for indicating the overloading type. Moreover, in case the demodulation reference signal, DMRS, is either partially or completely overloaded where PRBs are allocated to semantic communications, other UEs must be properly warned not to use the corresponding REs to estimate the channel.

[0111] Accordingly, one or all of the indicated features are provided in the extended DCI which is transmitted to the semantic UE. Subsequently gNB transmits signals by overloading of some of the physical, PHY, layer procedures and / or the media access control, MAC, layer procedures, using a selected overloading type. Accordingly, a concept is provided to extend the existing standard functionalities to enable an end-to-end communication for the semantic and effective communication. For that matter it is proposed to integrate semanticcommunications into the standard communication protocols while at the same time assuring compatibility with existing network standards.

[0112] Figure 4 relates to the case of SPS handling the S-DRBs. In one implementation the semantic UEs define its QoS requirements upon connection in the RAN. Therefore, the QoS requirements may be shared with a base station in a first step, preferably together with an associated request for semantic communications. The request of the UE requiring semantic communication may also include parameters or parametrization for the overloading, in order to specify the allowable or preferrable overloading type (or types). If the semantic communication is accepted, the gNB may transmit a SPS grant signal to the semantic UE. The scheduler may choose to allocate UL or DL resources in a way similar to what is already done for standard communications in the 3GPP standard frame structure. These resources are allocated and assigned in accordance with the different overloading types as described in relation to figures 5a to 5d. Once the scheduler assigns radio resources, semantic communications can be performed (in the assigned resource blocks), enabled by proper overloading. The gNB or the semantic UE transmits signals by overloading of some of the physical, PHY, layer procedures and / or the media access control, MAC, layer procedures, using a selected overloading type. Therefore, in one implementation there may be a periodic semantic communication between the base station and the semantic network element or semantic UE. With SPS, resources are granted in a periodic manner to the S- DRB, that can use them without the additional need of control information to allocate them dynamically. Preferably additional control info may be provided in real time to warn legacy UEs about overloaded features. Accordingly, a concept is provided to extend the existing standard functionalities to enable an end-to-end communication for the semantic and effective communication. For that matter it is proposed to integrate semanticcommunications into the standard communication protocols while at the same time assuring compatibility with existing network standards. Moreover, SPS may reduce the overhead compared to sending DL dynamic scheduling grants (e.g., reduced physical downlink control channel (PDCCH) overhead). In addition to the lower PDCCH overhead, use of SPS may also help to offload the computational burden from a busy dynamic gNB scheduler.

[0113] In some implementations one key element of the proposed semantic communication may be the QoS definition for semantic communications. Different from conventional QoS measurements for standard procedure such as required throughput, latency and first transmission target block error rate, present in, e.g., the 5G QoS identifier (5QI), for semantic communications a different group of QoS measurements needs to be introduced. This may be done to cope with the needs of a goal-oriented semantic encoder and decoder. The preferrable QoS measurements may include one or more of the following: Required number of resource elements (REs) or PRBs: Since the semantic communication scheme may encode the raw information into a fixed number of symbols per service query (e.g., a JSCC encoder), the semantic UE requests from the communications system a specific number of resource elements, RE, or PRBs. Therefore, this number may be exactly matched, requiring the scheduler to allocate an exact number of REs / PRBs per semantic communications allocation. This contrast the legacy communications QoS definitions, where requirements should be typically guaranteed to a minimum / maximum value, e.g., minimum throughput, maximum latency, etc. There are two classes of the SC encoder and decoder architecture designs: 1) both the encoder’s output and the decoder’s input have fixed dimensions, and 2) the output dimension of the encoder and the input dimension of the decoder are adapted based on the channel feedback. The former scheme requestsa fixed number of REs / PRBs per S-DRB, while the latter triggers the need for adaptive QoS requirements per S-DRB (i.e., varying number of the required REs / PRBs based on the channel feedback) for semantic communication, which contrasts to the state-of-the-art QoS update paradigm where fixed QoS requirements are defined for each DRB. Thus, for the former scheme, a new field in the QoS definition is proposed regarding the amount or number of requested REs / PRBs. On the other hand, for the latter scheme, not only a new QoS field is defined, but the QoS of a given S-DRB could be also updated adaptively based on the channel quality feedback.•Periodic vs dynamic behavior: an enumeration field with two possible values is proposed. If the semantic communication must happen deterministically and periodically, then the behavior is periodic. If the semantic communications must be triggered every time, then its behavior is dynamic. These configurations can be indicated in the proposed enumeration field of the QoS measurements.Expected inter-arrival time of the requests: with periodic arrivals, this corresponds to the required period of allocations. With dynamic arrival, it can correspond to its average / expected value.Information to allow the resource allocation method to understand which kind of overloading (type of overloading) is supported by the semantic communications applications.

[0114] Therefore, for semantic communications a different group of QoS measurements can be introduced in order to allow a semantic communication. The QoS measurements can be integrated alternatively or in addition to conventional QoS measurements. Accordingly, a concept is provided to extend the existing standard functionalities to enable an end-to-endcommunication for the semantic and effective communication integrated into the standard communication protocols and assuring compatibility with existing or future network standards.

[0115] Allocation and assignment in accordance with the different overloading types are described in figures 5a to 5d. Starting from figure 5a, where no overloading is included, an increasing amount of resources are overloaded in figures 5b and 5c and in figure 5d an example of maximum overloading is shown. As indicated, different overloading types are suggested, preferably having a different impact on the communication system. It is therefore proposed to provide a signalling to overload (in the programming sense, i.e., defining a different implementation / working mode for the same entity) some of the standard functionalities to enable semantic communications in compatibility with current and future wireless network standards.

[0116] In figure 5a an example of a slot for the 5G standard frame structure (3GPP standard frame structure and resources as in e.g. 3GPP specification TS 38.211 version 16.2.0, R16, incorporated by reference) is shown, for the DL. More specifically, 12 subcarriers are provided as one row and one column is included as an OFDM (Orthogonal Frequency Division Multiplexing) symbol. One full row is one physical resource block (PRB) in a slot with 14 symbols. In said standard frame structure there is provided a control channel, pilots and a data channel in each slot. Hereafter, a detailed description is given focusing on DL resources and signal transmission procedures, but the same concept applies for UL. The conventional 5G DL slot of figure 5a includes resource allocation for NR DL control, NR demodulation reference signal (DMRS), NR DL data, and NR DL data that can be redirected for DMRS, as illustrated with different blocks of the physical downlink controlchannel (PDSCH) and the physical downlink shared channel (PDCCH). In the figure the standard allocation is shown so that no overloading of resources is implemented in this case.

[0117] A first overloading type, which may also be referred to as PRB allocation to semantic communications, is shown in figure 5b. In particular, the 5G slot is overloaded such that PRBs are allocated to semantic communications wherein the DMRS is not overloaded by semantic communication in this implementation. As shown in the figure, in the NR slot in the PDSCH, overloading in three subcarriers can be implemented. Based on this overloading semantic information can be included in the NR slot, while further resource elements remain basically unaffected. Moreover, since the PDCCH is also preserved, it is possible to allocate semantic information to the given resources of the slot compatibility can be assured. Therefore, the effects on the system can be limited while at the same time semantic communication can be integrated. Semantic communications therefore overloads (or substitutes) some of the standard functionalities (such as encoding, modulation and / or power control and / or beamforming) while at the same time preserving compatibility with legacy services.

[0118] Accordingly, for the first overloading type, some PRB are allocated to semantic communications by the scheduler. Given the associations of the granted resources to the semantic-data radio bearer, S-DRB, instead of a legacy DRB, the UE(s) receiving the data are already informed that these PRBs will carry semantic communications. In order to keep compatibility with other legacy services, the numerology, frame structure, pilots, control channel, RE mapping may be kept. In particular, the DMRS can be kept (Figure 5b) or overloaded by semantic communications (Figure 5c) for the second overloading type. If the latter is the case, the DCI must signal with a special field that the PRBs allocated to semantic communications have overloaded the DMRS, allowing legacy UEs to perform channelestimation without considering these symbols. In a preferrable further development the scheduler may be allowed to make the decision whether to overload or not a part or all of the DMRS symbols in the PRBs allocated to semantic communications. As indicated, the DCI must support the necessary signaling to share with legacy UEs which DMRS symbols have been overloaded. Accordingly, the first overloading type may be provided without or with overloading of the DMRS. Accordingly, a concept is provided to extend the existing standard functionalities to enable an end-to-end communication for the semantic and effective communication integrated into the standard communication protocols and assuring compatibility with existing or future network standards.

[0119] The semantic communication can overload complex symbols transmitted in each resource element, thus the modulation coding scheme, MCS, as most of the semantic communications applications require to do. Also, power control mechanisms can be incorporated in the semantic communications design to make sure that the transmission matches the hardware requirements, link quality, etc. Moreover (optionally) beamforming can be overloaded for the resource blocks and symbols occupied by semantic communications. Of course, this is not mandatory in accordance with the present disclosure.

[0120] In a further preferrable development also the control resource set, CORESET, resources can be assigned to and overloaded by semantic communications to allow semantic communications to change the behavior of control channel for their own objective.

[0121] As shown in figure 5d, a second overloading type is suggested with which substantially more resources are considered for overloading. The second overloading type may be referred to as the full slot overloading type where the full slot (preferably the subframe or frame) is overloaded to Semantic Communications.

[0122] For the second overloading type a more disruptive approach is suggested with respect to current standards. Here, semantic communications are allocated to the full bandwidth in the carrier (or to a bandwidth part) for semantic communications. This allows to overload more functionalities, at the price of higher impact in the system.

[0123] The second overloading type can be described in view of four cases of the DL-UL and the DS-SPS case. In general, the second overloading type allows to overload not only the MCS, but also the waveform and / or beamforming and remove the need of fixed RE transmissions for pilots and control channels.

[0124] For the DL-SPS case, the whole slot can be overloaded, making sure power control mechanisms are in place. In particular, power control mechanisms can be incorporated in the semantic communications design to make sure that the transmission matches the hardware requirements, link quality, etc. Optionally, an initial transmission of a standard-compliant symbol may be provided to signal UEs that the current slot is fully being overloaded for a given S-DRB, as in figure 5d. In the particular case in which all the UEs may be warned in advance, since it is known at the scheduler that the slot is SPSed, then this first transmission may not be necessary. Here, the MCS, waveform and part of the control channel can be overloaded.

[0125] For the DL-DS case, the whole slot can be overloaded, while just keeping power control mechanisms in check. An initial transmission of a standard-compliant symbol is required to signal UEs that the current slot is fully being overloaded for a given S-DRB, as in figure 5d. Here, the MCS, waveform and part of the control channel can be overloaded.

[0126] For the UL-SPS and UL-DS case, the whole slot can be overloaded, just keeping power control mechanisms in check and not transmitting on the resource elements allocated to sounding reference signal, SRS, that are likely to be occupied by legacy UEs’ SRStransmissions. Given the presence of SRS, it’s likely that in UL it may not be possible overload the waveform, at least when SRS may be transmitted by other network elements or participants.

[0127] In case of UL-DS, a scheduling request should be triggered by the semantic UE(s) in order for the scheduler to allocate resources to it. A proper extension of logical channels (LCH) can be done to handle scheduling requests of semantic communications (and their corresponding QoS definition). For instance, the number of PRBs / REs required for the semantic communications should be exactly respected by the scheduler, not allocating less or more resources than that (something that could happen with normal data transmissions). In the UL case, the standard should enforce that grants (dynamic or SPS) associated to S- DRB cannot be used by legacy communications logical channels, and vice versa.

[0128] It is noted that, although in the above-illustrated example embodiments (with reference to the figures), the messages communicated / exchanged between the network components / elements may appear to have specific / explicit names, depending on various implementations (e.g., the underlining technologies), these messages may have different names and / or be communicated / exchanged in different forms / formats, as can be understood and appreciated by the skilled person.

[0129] According to some example embodiments, there are also provided corresponding methods suitable to be carried out by the apparatuses (network elements / components) as described above, such as the UE, the CU, the DU, etc.

[0130] It should nevertheless be noted that the apparatus (device) features described above correspond to respective method features that may however not be explicitly described, for reasons of conciseness. The disclosure of the present document is considered to extend also to such method features. In particular, the present disclosure is understood torelate to methods of operating the devices described above, and / or to providing and / or arranging respective elements of these devices.

[0131] Further, according to some further example embodiments, there is also provided a respective apparatus (e.g., implementing the UE, the CU, the DU, etc., as described above) that comprises at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the respective apparatus to at least perform the respective steps as described above.

[0132] Yet in some other example embodiments, there is provided a respective apparatus (e.g., implementing the UE, the CU, the DU, etc., as described above) that comprises respective means configured to at least perform the respective steps as described above.

[0133] It is to be noted that examples of embodiments of the disclosure are applicable to various different network configurations. In other words, the examples shown in the above described figures, which are used as a basis for the above discussed examples, are only illustrative and do not limit the present disclosure in any way. That is, additional further existing and proposed new functionalities available in a corresponding operating environment may be used in connection with examples of embodiments of the disclosure based on the principles defined.

[0134] It should also to be noted that the disclosed example embodiments can be implemented in many ways using hardware and / or software configurations. For example, the disclosed embodiments may be implemented using dedicated hardware and / or hardware in association with software executable thereon. The components and / or elements in the figures are examples only and do not limit the scope of use or functionality of any hardware, software in combination with hardware, firmware, embedded logic component, or acombination of two or more such components implementing particular embodiments of the present disclosure.

[0135] It should further be noted that the description and drawings merely illustrate the principles of the present disclosure. Those skilled in the art will be able to implement various arrangements that, although not explicitly described or shown herein, embody the principles of the present disclosure and are included within its spirit and scope. Furthermore, all examples and embodiment outlined in the present disclosure are principally intended expressly to be only for explanatory purposes to help the reader in understanding the principles of the proposed method. Furthermore, all statements herein providing principles, aspects, and embodiments of the present disclosure, as well as specific examples thereof, are intended to encompass equivalents thereof.List of abbreviations:5G - 5thGeneration gNB - 5G / NR base stationNR - New RadioRAN - Radio Access NetworkUE - User EquipmentUL - UplinkDL - DownlinkDCI - Downlink Control InformationPUCCH - Physical Uplink Control ChannelPUSCH - Physical Uplink Shared ChannelPDCCH - Physical Downlink Control ChannelPDSCH - Physical Downlink Shared ChannelCORESET - Control Resource SetSRS - Sounding Reference Signal

Claims

Claims1. Method for data transmission in a communication system, the method comprising: admitting semantic communication upon receiving a request for semantic communication service, selecting resource elements, RE, of the physical, PHY, layer and / or the media access control, MAC, layer for semantic communication, overloading the selected RE for semantic communication and associating the selected RE to a semantic-data radio bearer, S-DRB.

2. The method for data transmission according to claim 1, further including, for generating a signal to be transmitted, overloading at least a part of a standard protocol of the communication system by occupying the selected RE for semantic communication and transmitting the generated signal.

3. The method according to at least one of the previous claims, wherein overloading of a standard protocol includes overloading at least a part of the modulation and / or coding schemes, MCS, for semantic communication.

4. The method according to at least one of the previous claims, the method further comprising, receiving at a base station a request for semantic communicationincluding QoS requirements for semantic communication and / or a configuration for overloading parametrization.

5. The method according to at least one of the previous claims, wherein the RE are scheduled by semi persistent scheduling, SPS, persistent scheduling, PS, or by dynamic scheduling, DS.

6. The method according to at least one of the previous claims, further comprising: receiving a scheduling request from a user equipment, UE, allocating resources in accordance with the received scheduling request by function overloading at least part of the PHY layer and / or MAC layer procedure to enable semantic communication.

7. The method according to at least one of the previous claims, wherein the QoS requirements for semantic communication include an indication for a required amount of radio resources and preferably a specific number of required RE or physical resource blocks, PRB; and / or wherein the QoS requirements for semantic communication indicates an adaptive amount of required RE or physical resource blocks, PRB, depending on a channel feedback.

8. The method according to at least one of the previous claims, wherein based on a parameter in the QoS requirements for semantic communication the semantic communication is set to be a dynamic communication requiring to be triggered or a periodic communication.

9. The method according to at least one of the previous claims, wherein an expected inter-arrival time of the requests is defined in the QoS requirements for semantic communication to set the required period of allocations or an average value thereof; and / or wherein an overloading type is defined in the QoS requirements for semantic communication to determine the accepted type of overloading for the semantic communication.

10. The method according to at least one of the previous claims, wherein for overloading the standard protocol, selected PRB are associated to the S-DRB while maintaining at least one of the numerologies, the frame structure, the pilots, the control channel and the RE mapping in order to remain compatible with the standard protocol; and / or wherein at least a part of the demodulation reference signal, DMRS, is assigned for semantic communication and overloaded, wherein the downlink control information, DO, indicates that the PRB are allocated to semantic communication and overloaded.

11. The method according to at least one of the previous claims, wherein for assuring that the transmission matches required transmission requirements, at least one of a power control or beamforming or waveform shaping mechanism is included in the semantic communication.

12. The method according to at least one of the previous claims, wherein at least a part of the control resource set, CORESET, resources are assigned for semantic communication and overloaded.

13. The method according to at least one of the previous claims, wherein for a fullslot overloaded type, an entire bandwidth part or the full bandwidth in the carrier is assigned for semantic communication and overloaded; and / or wherein for the full-slot overloaded type the MCS and a part of the control channel is overloaded; and / or wherein for the full-slot overloaded type, and in case of a downlink, DL, SPS, the entire slot is overloaded and a power control mechanism is included in the semantic communication; and / or wherein for the full-slot overloaded type, and in case of DL, the method includes an initial transmission of a standard compliant symbol indicating that the current slot is fully overloaded for a given S-DRB.

14. Method for data transmission in a communication system, the method comprising: transmitting to a base station a request for semantic communication service; after semantic communication has been admitted, receiving or transmitting a signal in which at least a part of a standard protocol is overloaded by occupying selected resource elements, RE, of the physical, PHY, layer and / or the media access control, MAC, layer for semantic communication, wherein the selected RE are associated to a semantic-data radio bearer, S-DRB.

15. An apparatus for a communication system, the apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: admit semantic communication upon receiving a request for semantic communication service; select resource elements, RE, of a physical, PHY, layer and / or a media access control, MAC, layer and overload the selected RE for semantic communication, wherein the selected RE are associated to a semantic-data radio bearer, S-DRB.

Images