Method and system for supporting semantic communication in mobile networks

Abstract

Various aspects of the present disclosure relate to a User Equipment, UE, for enabling processing of semantic communication, the UE comprising a processor and a memory, the memory configured to store instructions that, when executed by the processor, cause the UE to generate a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication and transmit the PDU session establishment request from the UE to a control-plane function in a mobile communication network. The instructions, when executed by the processor further cause the UE to receive, from the control-plane function, a PDU session establishment accept message notifying the UE of establishment of a PDU session, and transmit semantic communication via the established PDU session for processing.

Description

METHOD AND SYSTEM FOR SUPPORTING SEMANTIC COMMUNICATION IN MOBILE NETWORKSTECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to a method and system of supporting semantic communication between agents, such as Artificial Intelligence (Al) agents in mobile communication networks.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an examplestep that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] Some implementations of the method and apparatuses described herein may further include a UE for enabling processing of semantic communication, the UE comprising: a processor; and a memory, configured to store instructions that, when executed by the processor, cause the UE to: generate a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication, transmit the PDU session establishment request from the UE to a control-plane function in a mobile communication network; receive, from the control-plane function, a PDU session establishment accept message notifying the UE of establishment of a PDU session; and transmit semantic communication via the established PDU session for processing.

[0005] Preferred implementations of the method and apparatuses described herein include wherein the UE is an autonomous vehicle, a robot, a sensor device, a drone, a smartphone, a tablet, or a smartwatch.

[0006] Preferred implementations of the method and apparatuses described herein include wherein the instructions, when executed by the processor, further cause the UE to generate the PDU session establishment request for the PDU session in response to receiving a request from an application on the UE to establish a data connection for semantic communication.

[0007] Preferred implementations of the method and apparatuses described herein include wherein the indication is a Data Network Name, DNN, value associated with semantic communication.

[0008] Preferred implementations of the method and apparatuses described herein include wherein the indication is a PDU session type associated with semantic communication.

[0009] Preferred implementations of the method and apparatuses described herein include wherein the DNN value is pre-configured in the UE or provisioned by a network node.

[0010] Preferred implementations of the method and apparatuses described herein include wherein the instructions, when executed by the processor, further cause the UE to establish a second concurrent PDU session for non-semantic communication.

[0011] Preferred implementations of the method and apparatuses described herein include wherein the sematic communication is transmitted from the UE to a user-plane function in the mobile communication network.

[0012] Some implementations of the method and apparatuses described herein may further include a processor for wireless communication, comprising: at least one controller, coupled with at least one memory and configured to cause the processor to: generate a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication, output the PDU session establishment request for transmission to a control-plane function in a mobile communication network; obtain an indication that the PDU session is established; and output semantic communication for transmission via the established PDU session.

[0013] Some implementations of the method and apparatuses described herein may further include a network node for wireless communication comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network node to: receive a protocol data unit, PDU, session establishment request, wherein the PDU session establishment request includes an indication that the PDU session is for semantic communication; based on the indication, select a user-plane function that is capable of supporting processing of semantic communication; transmit, to the user-plane function, a request message for establishing a PDU session comprising the indication; receive, from the user-plane function, a response message for establishing the PDU session; and transmit a PDU session establishment accept message.

[0014] Preferred implementations of the method and apparatuses described herein include wherein the request message further comprises an identifier of a semantic processing entity configured for processing semantic communication.

[0015] Preferred implementations of the method and apparatuses described herein include wherein the indication is one of: a Data Network Name, DNN, value associated with semantic communication; or a PDU session type associated with semantic communication.

[0016] Some implementations of the method and apparatuses described herein may further include a network node for wireless communication comprising: at least one memory; at least one processor coupled with the at least one memory and configured to cause the network node to: receive from a control plane function, a request message for establishing a PDU session, the request message comprising an indication that the PDU session is for semantic communication; responsive to the request message, configure a semantic processing entity to process semantic communication; transmit, to the control plane function, a response message for establishing the PDU session; receive one or more semantic communication packets via the established PDU session; and route the one or more semantic communication packets to the semantic processing entity for processing.

[0017] Preferred implementations of the method and apparatuses described herein include wherein the network node is further configured, in response to receiving the request message, to determine a semantic processing entity to process semantic communication.

[0018] Preferred implementations of the method and apparatuses described herein include wherein the request message further comprises an identifier of a semantic processing entity capable of processing semantic communication.

[0019] Preferred implementations of the method and apparatuses described herein include wherein the semantic processing entity is external to the network node and wherein the configuring the semantic processing entity comprises establishing a tunnel to the semantic processing entity.

[0020] Preferred implementations of the method and apparatuses described herein include wherein the network node comprises the semantic processing entity and theconfiguring the semantic processing entity comprises enabling the semantic processing entity to process semantic information.

[0021] Preferred implementations of the method and apparatuses described herein include wherein the semantic processing entity is configured to: in response to receiving the one or more packets, extract semantic information from the one or more packets; and determine an action to be taken regarding the one or more packets on the basis of the semantic information.

[0022] Preferred implementations of the method and apparatuses described herein include wherein the semantic processing entity is further configured to parse the semantic information using an ontology to determine a meaning of the one or more packets.

[0023] Preferred implementations of the method and apparatuses described herein include wherein the action to be taken by the semantic processing entity comprises one or more of: routing at least one of the one or more packets to a second network node for further processing; or performing processing of at least one of the one or more packets.BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Various aspects of the present disclosure are described with reference to the following Figures.

[0025] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0026] Figure 2 illustrates an example system architecture for supporting semantic communication in a mobile network.

[0027] Figure 3 illustrates an example message flow diagram for the handling of semantic traffic in the mobile network.

[0028] Figure 4 illustrates an alternative example system architecture for supporting semantic communication in a mobile network.

[0029] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure.

[0030] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure.

[0031] Figure 7 illustrates an example of a network equipment (NE) 700 in accordance with aspects of the present disclosure.

[0032] Figure 8 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0033] Figure 9 illustrates a flowchart of a method performed by a chipset in accordance with aspects of the present disclosure.

[0034] Figure 10 illustrates a flowchart of a method performed by a NE, such as a Session Management Function, in accordance with aspects of the present disclosure.

[0035] Figure 11 illustrates a flowchart of a method performed by a NE, such as a User Plane Function, in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0036] The present disclosure relates to methods, apparatuses, and systems that support and enable communication and processing of semantic communication in mobile networks. Semantic communication is communication of data that may encapsulate the meaning of a set of data. For example, raw sensor data may be processed to generate the data to be conveyed in semantic communication, the processed data providing context to, and / or meaning of, the sensor data. For instance, aspects of the disclosure enable the establishment and operation of a PDU session dedicated to semantic communication, that is, the communication of semantic traffic, and the processing of the semantic communication.

[0037] In traditional communication mechanisms between two devices such as a sensing agent and one or more receiving devices, raw data is transmitted from the sensing agent to the one or more receiving devices. This has associated drawbacks, such as inefficiency in transmitting significant amounts of sensor data via an interface such as a wireless interface. Other associated drawbacks include latency, since, in some instances, a large amount of data must be sent via the interface before a receiving device such as aserver can act in response to the data, and each receiving device which receives the data from the sensing agent has to process the data individually, leading to a lack of cohesive understanding of a situation that may be developing, and thus inhibiting effective collaboration.

[0038] Such drawbacks with traditional communication methods may be exacerbated by future developments in this area. For example, more accurate sensors able to make measurements at greater precision generate greater amounts of data to be transmitted over the interface to a receiving device. Alternatively, automating previously human-based tasks, such as search and rescue operations, places higher requirements on all parts of the system in regards of the efficiency, latency, and reliability of performance. It is therefore an object of this invention to address these and other problems associated with traditional methods of communication.

[0039] The approach disclosed herein is to decentralize processing of data obtained by a UE, such that initial processing of data takes place at the UE, and semantic communication is then performed over the interface with other devices. This reduces latency, as the processing of data happens as close as possible to the data source, reducing transmission times and thus the overall latency from sensing to any necessary action. This approach further improves efficiency, both of communication over the network, since a reduced amount of data needs to be transmitted via the interface, and of processing performed in the network, since a reduced number of devices are required to perform processing on the data sensed. Furthermore, this approach enhances the ability of devices such as Al agents to collaborate effectively, by enabling them to share a common understanding of a developing situation. We refer herein to an “Al agent” as being functionality capable of autonomously performing tasks (e.g. on behalf of a user or a system) by itself or in collaboration with other Al agents without human intervention. As examples, the Al agent may comprise a Large Language Model or a Vision-Language- Action Model.

[0040] Semantic communication of data, that is, communication of traffic that requires semantic processing, is communication of data that encapsulates the meaning of a set of data. Semantic communication, in some examples, may have a specified format to enableand enhance semantic processing of the data. For example, a UE (e.g., a robot) may comprise a number of sensors, and be deployed in a Search and Rescue operation. In this case, the sensors of the UE may obtain large amounts of data. The processor of the UE may process the data obtained by the sensors, and perform semantic communication to another device, such as a central command node. For example, instead of transmitting the raw sensor data, the sensor data obtained by the UE may be processed by the processor, and the semantic communication by the UE may comprise an indication of “Probable Survivor, Location [X, Y], Confidence 80%”.

[0041] Therefore aspects of the present disclosure enable a method for separating semantic communication from traditional traffic in a clear and unambiguous way. The disclosed method and example embodiments utilize the existing PDU session and DNN concepts within the current 5G architecture, such that integration with current systems is improved and made easier. Required alterations to base stations communicating with UEs are kept to a minimum, and in at least one embodiment, user plane elements in the mobile communication network are not required to perform deep packet inspection or complex classification, instead simply forwarding the packet to a specialized processing entity. This reduces latency and improves throughput of data. Efficient routing of semantic communication may be enabled directly to a specialized processing entity, located at an edge data network.

[0042] Furthermore, multiple DNNs may be associated with semantic communication, which may in turn be associated with different types of semantic services, different Quality of Service requirements, different UEs, and other divisions within a broader classification of semantic communication. This may enable accurate, and more particular, routing of semantic communication to processing entities that are adapted to perform processing of the particular semantic communication.

[0043] Aspects of the present disclosure are described in the context of a wireless communications system.

[0044] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106.The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LIE- A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0045] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0046] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0047] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0048] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0049] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0050] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets orinterconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0051] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0052] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0053] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0054] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0055] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0056] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0057] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0058] Future advancements of mobile networks, such as those of wireless communications system 100 as in Figure 1, specifically 6G, are expected to support a wide range of advanced applications driven by Artificial Intelligence (Al). These applications will often involve the collaboration of multiple, heterogeneous Al agents, each with specialized capabilities, operating across various devices and systems. An example is a disaster response scenario where autonomous drones, ground robots, and sensor networks equipped with different Al agents need to communicate and coordinate their actions in real time to efficiently locate and rescue survivors.

[0059] Traditional communication mechanisms, which primarily focus on transmitting raw data between devices based on IP addresses, are inadequate for these complex Al-driven applications. In the disaster response example, a drone might detect a faint heat signature indicating a potential survivor. Simply transmitting raw sensor data to other agents or a central command is inefficient and insufficient. The receiving agents need to understand the meaning of the data - that it represents a potential survivor - to take appropriate action. Furthermore, efficiency of communication and latency are essential considerations in the proper function of systems such as this.

[0060] Current 5G networks, and even earlier generations, rely on Data Network Names (DNNs) to identify specific data networks that a UE can connect to. However, these DNNs are used for basic traffic segregation and routing based on the destination data network. They do not provide any mechanism for conveying or processing the semantic meaning of the data being transmitted.

[0061] To illustrate the importance of semantic communication for Al agents, consider a disaster response example scenario involving a swarm of heterogeneous autonomous systems. An earthquake has struck a densely populated area, causing widespread damage and trapping survivors. It will be appreciated that reference to this example scenario is for explanatory purposes only and embodiments of the present disclosure are not limited to this application.

[0062] In the example scenario, the following autonomous systems, each equipped with its own Al agent, may be deployed:Aerial Drones: Equipped with cameras and thermal sensors, these drones survey the area, identify structural damage, and search for signs of life.Ground Robots: These robots navigate through debris, enter collapsed buildings, and provide close-up inspection. Some are equipped with manipulators to move obstacles or deliver aid.Sensor Network: A network of static sensors (seismic, acoustic) provides data about the stability of structures and potential locations of survivors.Central Command Agent: An Al agent, located at the edge data network, coordinates the entire operation, analyzes data from all agents, and makes high-level decisions.

[0063] Without semantic communication, i.e. using traditional communication methods, these agents would be limited to exchanging raw data. Drones would send streams of images and sensor readings, ground robots would transmit telemetry data, and the sensor network would provide raw measurements. The Central Command Agent would then have the enormous task of processing all this raw data to understand the situation and coordinate the response. This is inefficient, slow, and prone to errors. The agents do not understand each other, but merely exchange raw data that should be individually processed and understood by the recipient.

[0064] However, using a semantic DNN, these agents can communicate meaningfully. To continue the above example:Drone Agent: A drone detects a heat signature beneath debris. Its Al agent, instead of just sending raw thermal data, sends a message over the semantic DNN that states: "Detected potential survivor with 80% confidence at coordinates [X, Y], Requesting ground robot assistance for confirmation." This message uses terms defined in a shared ontology, enabling other agents to understand its meaning.Network Routing: The mobile communication network (e.g. 6G network), recognizing the semantic DNN, automatically routes this message to the semantic gateway in the edge data network.Central Command Agent: The Central Command Agent receives the message. Because it shares the same ontology as the drone agent, it understands that a "potential survivor" has been detected with high probability at a specific location.Ground Robot Agent: The Central Command Agent, based on its understanding of the situation and the capabilities of different agents, sends a message over the semantic DNN to a suitable ground robot agent: "Proceed to coordinates [X, Y] and confirm the presence of a survivor. Drone- 1 will provide aerial support."Ground Robot Action: The ground robot agent receives the message, understands its task, and navigates to the specified location. It might then use its sensors to confirm the presence of a survivor and send a new semantic message back to the Central Command Agent: "Confirmed survivor at coordinates [X, Y], Requesting medical assistance."

[0065] This example scenario demonstrates how semantic communication, enabled by our semantic DNN approach, allows devices and the applications supported thereby, such as Al agents, to collaborate effectively in a complex, time-critical situation. Agents are enabled to share not just data, but also the meaning of that data, leading to faster, more efficient, and more coordinated actions. Therefore, it is crucial for mobile communication networks to evolve beyond traditional data transport and develop mechanisms to natively support semantic communication, enabling Al agents to interact and collaborate intelligently.

[0066] Embodiments of the proposed invention introduce a new and highly effective method for supporting semantic communication in mobile networks by designating specific DNN values to indicate semantic communication. When a UE establishes a PDU session using a semantic DNN, the network understands that all communication, i.e., traffic, within that session requires semantic processing. The network then routes this traffic to specialized nodes within the network, typically within an edge data network, which are capable of understanding and processing the semantic content of the messages. Other methods of indicating semantic traffic are also disclosed. This provides a practical and straightforward way to interlace existing 5G architecture and concepts with the requirements and future needs of semantic-aware applications and devices.

[0067] In essence, disclosed herein is a dedicated pathway for Al agents to communicate meaningfully. Unlike traditional communication that treats data as mere bits and bytes, semantic communication allows Al agents to exchange information that includes the context, relationships, and meaning associated with the data.

[0068] Consider again the disaster response scenario. The drone's Al agent may be enabled to send a message that conveys, "I have detected a potential survivor with high confidence at these coordinates." This message, sent over the semantic PDU Session, maybe automatically routed to a semantic-aware data network that hosts an Al agent responsible for coordinating rescue operations. This agent, understanding the meaning of the message due to shared semantic definitions, can then immediately act such as dispatching the appropriate resources, such as a ground robot, to the specified location. This is more efficient than transmitting raw sensor data that needs to be manually interpreted or processed through complex algorithms before any action can be taken.

[0069] This approach offers significant advantages for Al agent communication. First, it reduces latency by ensuring that semantic processing happens as close to the data source as possible, at the network edge. Second, it improves efficiency by avoiding the need to send large amounts of raw data to a central location for processing. Third, it enhances the ability of Al agents to collaborate effectively by enabling them to share a common understanding of the situation.

[0070] Turning to Figure 2, the devices shown in Figure 2 may be implemented by aspects of the wireless communications system 100 described herein with reference to Figure 1. For example, the UE 104 shown in Figure 2, may be an example of a UE 104 as described herein with reference to Figure 1. Furthermore, the system architecture 200 shown in Figure 2 may include one or more NE 102 and / or the CN 106 described herein with reference to Figure 1.

[0071] Figure 2 illustrates a system architecture 200 designed to support semantic communication between Al agents in a mobile communication network such as a 5G or 6G network. This is performed by leveraging PDU sessions with an indication of a semantic communication, such as a dedicated Data Network Name (DNN) to route semantic traffic to a specific and / or specialized Data Network which is able to support semantic communication.

[0072] The Figure shows two UEs 104a, 104b, which may be, for example, a ground robot and a drone. Each UE incorporates various computing hardware and software, and in particular may support a respective Al agent 202a, 202b. Each UE may be capable of generating and processing semantic information, and of communicating such semantic information to other devices in a network for (additional) processing. Also shown are two access networks 204a and 204b, which may comprise network nodes configured to provideaccess to the CN 106 for the UEs 104a, 104b. The CN 106 may comprise a UPF 206, as well as at least one Control Plane Function 208, such as a Session Management Function (SMF) and an Access and Mobility Management Function (AMF) in the context of a 5G network. One or more network entities in the CN 106 may implement the UPF206 and Control Plane Function(s) 208.

[0073] Each UE 104a, 104b may establish a respective protocol data unit, PDU, session for semantic communication with the CN106. The PDU session may be established using a special DNN, called a semantic DNN. That is, a particular DNN may be associated with semantic communication, and reception of a session request at the CN 106 from a UE 104a, 104b including the particular DNN may result in establishment of a PDU session for semantic communication. Each semantic PDU session may be a virtual connection between a UE and a UPF in the CN 106 that is established to carry semantic traffic, that is, to facilitate semantic communication. Each UE may also, prior to the establishment of the semantic PDU session, simultaneously with the establishment of the semantic PDU session, or subsequently to the establishment of the semantic PDU session, establish one or more other “conventional” PDU sessions, for the transmission of one or more other types of traffic. Such traffic may include IP traffic, Ethernet traffic, etc. Other methods for designating the PDU session as a semantic PDU session may alternatively be used, such as the use of a dedicated PDU session type. For example, the PDU session establishment request may include an indication of a particular PDU session type, the particular PDU session type being associated with semantic communication and a semantic PDU session. In response to this PDU session establishment request from the UE 104a, 104b, the CN 106 may establish a semantic PDU session with the UE from which the request was transmitted.

[0074] There is thus proposed specific, reserved DNN values (or other indication) to indicate that a PDU session carries semantic traffic. These semantic DNNs can be standardized according to specifications, or configured by network operators. When a UE, such as a drone or a robot in the above example disaster scenario, needs to establish a connection for semantic communication, it may include the designated semantic DNN in the PDU Session Establishment Request.

[0075] Continuing this above example, the Session Management Function (SMF) 208 in the Mobile Core Network, upon receiving a request with a semantic DNN, may recognize the need for special handling of data packets to be transmitted. It may select a UPF, 206, that is connected to a data network 210, such as an edge data network, equipped with semantic processing capabilities. The UPF 206 may then be configured to route some or all traffic from this PDU session to a designated semantic gateway 212 within the edge data network 210. The semantic gateway 212 may thus act as an entry point to a network of specialized nodes and / or functions that can perform tasks like semantic parsing, reasoning, and knowledge graph querying.

[0076] The edge data network 210 is where the core of the semantic processing may take place. Processing applications such as Al agents, residing on edge servers, can communicate with each other using a shared understanding of the data, facilitated by common ontologies, that is, shared definitions of concepts and relationships between the concepts. For instance, in our disaster scenario, different agents can access a shared ontology that defines concepts like "survivor," "collapsed building," "heat signature," and the relationships between them. This may enable a more sophisticated and coordinated response in networks comprising multiple heterogeneous agents than would be possible with traditional communication methods. The edge data network 210 may also include other sub-systems, and nodes. For example, the edge data network 210 may include a Knowledge Graph 214, which may be provided in many forms such as a table, or a repository, and may be hosted on a separate node or incorporated into one or more other nodes. This Knowledge Graph 214 may determine and provide access to a shared ontology for the semantic gateway 212, and may also provide a shared ontology for other devices and nodes in the edge data network 210. The edge data network 210 may also comprise one or more processing entities, such as a server or cluster 216. The server or cluster 216 may perform processing tasks at the command of the semantic gateway 212, or the server or cluster 216 may provide processing tasks and coordination of multiple semantic gateways. For example, the server or cluster 216 may host an entity such as an Al agent 218 configured to perform Central Command and Coordination tasks. This entity 218 may coordinate and enable collaboration between the semantic communications processed by one or more semantic gateways 212, and hence with UEs that transmit the semanticcommunications. In this example architecture, the semantic gateway 212 is separate to the UPF 206, and there is a connection between the semantic gateway and the UPF, and by extension between the CN 106 and the Edge Data Network.

[0077] Therefore, the proposed invention simplifies the process of integrating semantic communication into existing mobile network architectures. It may leverage the familiar DNN mechanism and require minimal changes to the Radio Access Network (RAN). The primary modifications may be within the Mobile Core Network, such as the 5G Core, specifically in the SMF and UPF, and the introduction of semantic processing capabilities at the network edge.

[0078] Figure 3 illustrates an example message flow diagram 300 in accordance with aspects of the present disclosure. This message flow outlines the core steps for handling semantic traffic using a DNN associated with semantic communication. Specific implementation details might vary depending on the network architecture and the chosen technologies. For example, in some instances, one or more specific steps may be altered, or removed, or some steps of the flow diagram may occur in a different order than as presented.

[0079] In a first optional step S302 a UE 104, and more specifically an agent such as an Al agent hosted on the UE determines that it is required to transmit data over the network, and that the data to be transmitted over the network requires semantic processing. The Al agent may therefore request or instruct the UE to establish a Protocol Data Unit, PDU, session for the transmission of data requiring semantic processing.

[0080] In a second step S304, the UE signals the need for semantic processing of data to the receiving node of the CN 106 within the transmission of a PDU session establishment request from the UE to an element of the CN 106, in this case, a Control Plane Function, such as an Access and Mobility Management Function, AMF, 208a. The AMF 208a thus receives the PDU session establishment request, with the indication of semantic processing. This indication can be achieved in one of several ways. For example, the UE 104 can specify a semantic DNN (e.g., “internet. semantic”) in the PDU session establishment request. This use of a specific DNN leverages existing 5 G mechanisms and simplifies network-side processing of the PDU session establishment request. Alternatively, a newsemantic PDU session type could be indicated in the PDU session establishment request to indicate that data transmitted via the session requires semantic processing. This PDU session type would exist in addition to existing PDU session types in 5G networks, such as Ethernet, IPv4, and IPv6, and the UE may communicate via different PDU session types with corresponding data types. By using either a dedicated DNN or a new PDU session type, the network is able to identify traffic requiring semantic interpretation and handle it appropriately, for example routing it to specialized nodes, such as a semantic gateway within an edge data network, for appropriate processing. This ensures that Al agents communicating through the network can exchange and understand the meaning of their data, enabling more intelligent and efficient collaboration.

[0081] When a dedicated semantic DNN is used, the UE could determine or be provisioned with this DNN value through various means, such as:The UE could be pre-configured with the semantic DNN value.An application on the UE could be programmed to use the semantic DNN value when communicating with specific services, such that different applications may use different DNNs, or when communicating with different services.The UE could query the network for available DNNs and their capabilities and receive a response indicating available DNNs for semantic communication.

[0082] Examples of semantic DNN values include "internet. semantic," "iot. semantic," or a specific value like "semantic-net". Such DNN values would be understood by the network infrastructure such as the CN 106 (e.g., the SMF and UPF) to trigger special handling for all traffic associated with it. Methods of obtaining a specific PDU type indication to use when transmitting a PDU session establishment request may be obtained by the UE in a similar manner to the DNN values discussed above; via pre-configuring, via programming of particular applications on the UE, or when communicating with particular services, and via querying the network.

[0083] In a third step S306, the AMF 208a, in response to receiving the PDU session establishment request including the indication of the need for semantic processing of data, may forward the PDU session establishment request to another Control Plane Functionwithin the CN 106, the SMF 208b (Session Management Function). The SMF 208b may interact with other network functions within the CN 106 such as a Unified Data Management function, UDM, or a Unified Data Repository, UDR. Following this optional interaction, and based on the configuration of the SMF 208b and potentially the interaction with other network functions, the SMF 208b may recognize the indicator for required semantic processing. Following from above, this recognition may include recognizing the presence of a predetermined DNN associated with semantic processing, or it may include recognizing the presence of a specific PDU session type associated with semantic processing.

[0084] In a fourth step S308, the SMF 208b, in response to receiving the PDU session establishment request forwarded by the AMF 208a, may select or determine a UPF 206, which is able to support semantic handling of data and may, in some instances, connect to data networks supporting semantic communication. Such data networks for example, may host a Semantic Gateway and other resources as required for semantic processing.

[0085] In a fifth step S310, the SMF 208b sends a message (otherwise referred to herein as a request message for establishing a PDU session) to the selected UPF to instruct the selected UPF 206 to configure a semantic processing entity, such as a semantic gateway 212, for the reception and processing of semantic communication. In the example of message flow 300, the SMF 208b instructs the UPF 206 to establish a dedicated path (a tunnel) for routing all traffic associated with the semantic PDU session to the Semantic Gateway. As appreciated from Figure 2, the semantic processing entity may be part of a data network such as an edge data network 210. This path may be visually represented as a semantic DNN tunnel. Information for establishing this tunnel (e.g. the address of the semantic gateway, configuration details in respect of the tunnel, an identifier of the UE 104 or the PDU session to which the tunnel relates) may be provided either by SMF 208b within the message or through a separate message, or may be determined separately by the UPF 206.

[0086] In a sixth step S312, the UPF 206, having received the instructing message from the SMF 208b, may establish the instructed tunnel using GTP-U or another appropriate tunneling technology, from the UPF 206 to the semantic processing entity, that is, to thesemantic gateway 212. In this example, the tunnel is specifically associated with the PDU session established for the transmission of semantic communication from the UE 104. One of the two endpoints of the tunnel, located at the UPF 206, may be configured to receive all traffic associated with the PDU session to which the tunnel relates.

[0087] In a seventh step, S314, the UPF 206, having determined that the tunnel from the UPF 206 to the semantic gateway 212 is established, transmits a message (otherwise referred to herein as a response message for establishing the PDU session) to the SMF 208b to indicate that the tunnel is established. For example, the UPF 206 may transmit a Session Establishment Response to the SMF 208b and include within the Session Establishment Response an indication that the tunnel to the semantic gateway 212 is established.

[0088] In an eighth step S316, the SMF 208b, on receipt of the Session Establishment Response from the UPF 206, may transmit an indication to another control plane function, such as the AMF 208a, to indicate that the PDU session establishment request is accepted and that the tunnel has been established. For example, the SMF 208b may transmit to the AMF 208a a PDU session establishment accept message.

[0089] In a ninth step S318, the AMF 208a, on receipt of the indication that the session establishment request has been accepted and that the tunnel has been established, may generate a Non-Access Stratum, NAS, message to be transmitted from the AMF 208a to the UE 104. This NAS message may be configured to include the accept message transmitted from the SMF 208b and received at the AMF 208a, the PDU session establishment accept message. The AMF 208a may then transmit the NAS message to the UE to notify the UE that the PDU session has been established, and that the Core Network is prepared for the transmission thereto of data requiring semantic processing.

[0090] Thus, at the conclusion of the ninth step in the flow diagram 300, a UE 104 may have determined a need for transmission of data requiring semantic processing, requested the establishment of a PDU session specifically associated with semantic communication, and received an indication from the CN 106 that the requested PDU session is established.

[0091] An application on the UE 104, such as the Al agent, may then generate or obtain data that requires semantic processing (not shown). Thus, in a tenth step S320, theapplication may cause the UE 104 to transmit communications over the established PDU session associated with semantic communication. That is, the UE 104 may send traffic (i.e. one or more data packets) within the established PDU session, where the one or more data packets contain semantic information. This transmission of data packets via the semantic PDU session may be directed toward a first network node, such as an access network node 204, and received at the access network node 204.

[0092] In an eleventh step S322, the access network node 204 may forward the data packets containing semantic information to another network entity. For example, the access network node 204 may forward the data packets containing semantic information to the UPF 206, either directly or indirectly. That is, the data packets which require semantic processing may be transmitted from the access network node 204 to the UPF 206, where an end of the tunnel may be located.

[0093] In a twelfth step, S324, the UPF 206 may then route the data packets requiring semantic processing via the tunnel established between the UPF 206 and the semantic processing entity, i.e., the semantic gateway 212, to the semantic processing entity. The semantic processing entity may thus receive the data packets forwarded via the access network node 204 and the UPF 206, and originally generated at the UE 104.

[0094] Thus, as a result of the preceding steps, semantic information is provided to a semantic processing entity that is configured to process the data in the data packets in accordance with semantic processing. On receipt of the semantic communication and in a final step S326, the semantic processing entity may extract a payload of the data packets, such as a predetermined semantic information contents, and utilize a designated ontology, which is accessible via a Knowledge Graph 214, to understand the meaning of the semantic information. The Knowledge Graph 214 may act as a shared repository of knowledge, defining the concepts, relationships, and vocabulary used by devices in the network such as the Al agents. This shared understanding based on standardized ontologies may thus allow the agents to communicate accurately and effectively.

[0095] The Knowledge graph 214, as mentioned above, may function as a shared repository of knowledge and define the concepts in the semantic information, as well as relationships between the concepts. To return to the Search and Rescue example usedabove, the knowledge graph, and the ontology provided by it, may contain concepts such as:Survivor: A person who has experienced the disaster and needs assistance.Heat Signature: An indication of a living being detected by thermal sensors.Collapsed Building: A structure that has been damaged and may pose risks.Location: The specific coordinates where a survivor or other relevant object is located.Confidence Level: The degree of certainty associated with a detection or assertion.

[0096] The concepts may be related by relationships between the various concepts:A "survivor" may be located in a "collapsed building."A "heat signature" may indicate the presence of a "survivor."A "location" is associated with a "survivor" or a "collapsed building."A "confidence level" qualifies the certainty of a "heat signature" indicating a "survivor."The ontology provided by the knowledge graph may thus act as a “language” for the Al agents to communicate.

[0097] Once semantic information has been extracted from the data packets by the semantic processing entity, i.e., the semantic gateway 212, the semantic processing entity may parse the semantic information to understand its meaning. That is, the semantic processing entity may analyse the structure of the data to understand its components and any relationships between the concepts referred to. For example, an example data packet may include the following semantic information: {"event_type": 2, "location": [34.5, - 118.2], "confidence": 0.8}. In this example the semantic processing entity may extract the relevant fields of the semantic information (event type, location, and confidence values), and then parse the information extracted. For example, this may include mapping event_type: 2 to "Survivor" using the ontology, interpreting the coordinates as a specificlocation where the survivor is located, and understand the confidence value as a probability associated with the above event type and location.

[0098] The semantic processing entity may thus use the ontology and the shared concepts and relationships defined therein to understand the meaning of the semantic information communicated to the semantic processing entity. Following the extraction of the semantic information, the semantic processing entity may determine an action to be taken in regard of the one or more packets transmitted to the semantic processing entity. This determination step may be based on the contents of the semantic information in the one or more packets.

[0099] Determining the meaning of the semantic information contained within the one or more data packets may be referred to as parsing the semantic information, and may be performed by the semantic processing entity in accordance with semantic processing customs, as well as utilizing the shared ontology provided by the knowledge graph 214. The action to be taken by the semantic processing entity may comprise routing some or all of the one or more data packets to another network node for the data packets to be processed at another network node. In the architecture of Figure 2, the semantic gateway 212 may route the data packets received, based on the meaning of the semantic information contained within the data packets as determined by the parsing of the data packets, to the server or cluster 216 for processing by the Al agent for Central Command and Coordination 218. In the above disaster response example, a message from a UE indicating a “potential survivor” could be routed to the Central Command and Coordination Al agent to enable an increased level of collaboration to rescue the survivor. In other examples, the location of the event leading to the semantic communication may be determinative as to the routing of the data packets. For example, a disaster response area may be divided into separate sections for different disaster response teams; if parsing of the semantic information determines that a location corresponds to Zone B, the semantic processing entity may route the data packets to a node associated with coordinating the disaster response in Zone B.

[0100] Alternatively, the semantic processing entity may determine that the semantic processing entity itself may perform processing of the data packets, and may, for example, determine an action to be taken by itself or another device in the network in response to thesemantic information. For example, the semantic processing entity may determine that a drone device should be deployed to a vicinity of the location of the UE 104 which transmitted the semantic communication.

[0101] In the example scenario where the semantic gateway routes the data packets to another node, such as the Al agent for Centralized Command and Coordination 218, Al agents within the data network may process the received semantic information and take appropriate actions. The agents can thus communicate with each other using the same semantic communication principles, facilitated by the Semantic Gateway 212 and the shared Knowledge Graph 214. Responses to the originating UE 104 may be routed back through the Semantic Gateway 212, the UPF 206, and the established PDU session.

[0102] Figure 4 illustrates an alternative example architecture 400. Broadly speaking, the architecture depicted in Figure 4 is similar to that of Figure 2 and corresponding elements will thus not be described below for the sake of brevity. However, rather than being implemented on separate nodes, the functionality of the semantic gateway 212 is incorporated into the UPF 206, which thus forms part of the edge data network 210. The CN 106 is maintained in the architecture 400, and supports the Control Plane Function 208, such as the SMF and / or AMF as described in Figure 3. By integrating the functionality of the Semantic Gateway directly into a UPF, this alternative approach makes the mobile network more semantic aware and can reduce latency by eliminating an extra hop for semantic traffic (as there is consequently no need for a semantic DNN tunnel). Instead of routing traffic through a separate semantic processing entity, the UPF 206 itself may be enhanced with the capability to parse, interpret, and route semantic information. This enables faster processing of semantic communication and reduced latency by performing semantic interpretation, processing, and routing directly within the user-plane function.

[0103] For this example architecture, a corresponding message flow may be altered with respect to the message flow illustrated in Figure 3. Steps 1-4, S302-S308 may be unchanged with respect to Figure 3, and at step 5 S310, the SMF 208b may send a message to the UPF 206 as in Figure 3. However, since the semantic processing entity is present on the UPF 206 rather than implemented separately, the message which instructs the UPF 206 to configure the semantic processing entity may take account of the incorporation of thesemantic processing entity into the UPF 206. For example, the message from the SMF 208b to the UPF 206 may not include an indication that the UPF 206 is to establish a tunnel between the UPF 206 and the semantic processing entity or associated information for the UPF 206 to establish the tunnel, but may contain an indication that the UPF 206 is to enable the semantic processing entity such that the semantic processing entity is enabled to process semantic information. Furthermore, many later steps of the method utilizing the alternative example architecture are also similar to that of Figure 3, such as S314, S316, S318, S320, and S322. S324 may be altered in that the UPF 206 does not forward the data packets received via a tunnel to the semantic processing entity, but routes the data packets to the semantic processing entity within the UPF 206. S326 in the alternative architecture, where the semantic processing entity processes the data packets from the UE 104, may be substantially similar to step S326 in Figure 3, with the alteration that the semantic processing happens at the UPF 206 supporting the semantic processing entity within it, rather than at a semantic processing entity external to the UPF 206.

[0104] Thus, in this alternative scenario, when a semantic PDU session is requested by a UE 104 by indicating a semantic DNN or a semantic PDU type, the SMF 208b may instruct the UPF 206 to perform both traditional user plane forwarding and semantic processing. The UPF 206, upon receiving packets over the semantic PDU session, may thus extract semantic information from the data packets transmitted by the UE 104 and forwarded by the access network node 204 and may utilize semantic processing capabilities integrated into the UPF 206 to determine an appropriate action. This may involve interacting with a knowledge graph 214 (that is, the ontology provided to the semantic processing entity by the knowledge graph) to understand the meaning of the semantic information in the data packets. The UPF 206 may then forward the message to a relevant Al agent within the data network, or potentially even handle some of the semantic processing directly within the UPF 206. For example, the integrated UPF 206 and semantic processing entity may determine that a message from UE 104 should be forwarded to the Al agent for Central Command and Coordination 218. If the UPF 206 handles the semantic processing of the data packets through the use of the semantic processing entity implemented on the UPF 206, the UPF 206 may thus be enabled to operate as an Al agent itself, and may determine any necessary routing of the data packets originating from the UE104 and / or determine an action to be taken based on the data packets. The action to be taken may be one that is to be performed by another device in the system architecture 200. To continue the example above, the UPF 206 may determine to deploy another device such as a robot to further inspect the location of the survivor. Alternatively, the action to be taken may be one that is to be performed by the semantic processing entity on the UPF 206. In another example, the semantic information may indicate a sensor measurement from a sensor, such as a seismic sensor providing stability information with regard to a structure such as a building. Accordingly, the action to be taken may not be one that is to be performed by another device in the network, but instead may be an action that is to be taken by the semantic processing entity on the UPF 206, and may, for instance, be the recording of the measurement in a memory available to the UPF 206. Other actions performed by the UPF 206 and by other devices in the system architecture 200 are envisaged in accordance with the meaning of the semantic information in the data packets.

[0105] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure. The UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0106] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0107] The processor 502 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502.The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the UE 500 to perform various functions of the present disclosure.

[0108] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the UE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 504 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0109] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the UE 500 in accordance with examples as disclosed herein. The UE 500 may correspond to the UE 104. The UE 500 may be configured to support a means for enabling processing of semantic communication. For example, the UE may be configured to perform operations including generating a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication, and transmitting the PDU session establishment request from the UE to a control-plane function in a mobile communication network. The UE may also be configured to receive, from the control-plane function, a PDU session establishment accept message notifying the UE of establishment of a PDU session, and transmit semantic communication via the established PDU session for processing.

[0110] The controller 506 may manage input and output signals for the UE 500. The controller 506 may also manage peripherals not integrated into the UE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0111] In some implementations, the UE 500 may include at least one transceiver 508. In some other implementations, the UE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

[0112] A receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 510 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 510 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0113] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0114] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure. The processor 600 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein. The processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units(ALUs) 606. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0115] The processor 600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 600) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0116] The controller 602 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. For example, the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0117] The controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction(s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein. The controller 602 may be configured to track memory address of instructions associated with the memory 604. The controller 602 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as describedherein. Additionally, or alternatively, the controller 602 may be configured to manage flow of data within the processor 600. The controller 602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 600.

[0118] The memory 604 may include one or more caches (e.g., memory local to or included in the processor 600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600). In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600).

[0119] The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 600, cause the processor 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 602 and / or the processor 600 may be configured to execute computer-readable instructions stored in the memory 604 to cause the processor 600 to perform various functions. For example, the processor 600 and / or the controller 602 may be coupled with or to the memory 604, the processor 600, the controller 602, and the memory 604 may be configured to perform various functions described herein. In some examples, the processor 600 may include multiple processors and the memory 604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0120] The one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600). In some other implementations, the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600). One or more ALUs 606 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 606 may receive input operands and an operation code, whichdetermines an operation to be executed. One or more ALUs 606 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.

[0121] The processor 600 may support wireless communication in accordance with examples as disclosed herein. The UE 104 may comprise the processor 600. The processor 600 may be configured to or operable to support a means for generating a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication, and outputting the PDU session establishment request for transmission to a control-plane function in a mobile communication network. The processor 600 may also be configured to obtain an indication that the PDU session is established, and output semantic communication for transmission via the established PDU session.

[0122] Figure 7 illustrates an example of a NE 700 in accordance with aspects of the present disclosure. The NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0123] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0124] The processor 702 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). Insome implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the NE 700 to perform various functions of the present disclosure.

[0125] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the NE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0126] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the NE 700 in accordance with examples as disclosed herein. The NE 700 may be configured to support a means for wireless communication, and, in particular, may be configured to receive a protocol data unit, PDU, session establishment request, wherein the PDU session establishment request includes an indication that the PDU session is for semantic communication and based on the indication, select a user-plane function that is capable of supporting processing of semantic communication. The NE may also be configured to transmit, to the user-plane function, a request message for establishing a PDU session comprising the indication, receive, from the user-plane function, a response message for establishing the PDU session, and transmit a PDU session establishment accept message.

[0127] Additionally, in some implementations, the NE 700 may be configured to support a means for wireless communication, and, in particular, may be configured to receive from a control plane function, a request message for establishing a PDU session, the request message comprising an indication that the PDU session is for semanticcommunication, and, responsive to the request message, configure a semantic processing entity to process semantic communication. The NE 700 may also be configured to transmit, to the control plane function, a response message for establishing the PDU session, receive one or more semantic communication packets via the established PDU session, and route the one or more semantic communication packets to the semantic processing entity for processing.

[0128] The controller 706 may manage input and output signals for the NE 700. The controller 706 may also manage peripherals not integrated into the NE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0129] In some implementations, the NE 700 may include at least one transceiver 708. In some other implementations, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0130] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 710 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0131] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitudemodulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0132] Figure 8 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0133] At 802, the method may include generating a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication. The operations of generating a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of generating a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication may be performed by a UE as described with reference to Figure 5.

[0134] At 804, the method may include transmitting the PDU session establishment request from the UE to a control-plane function in a mobile communication network. The operations of transmitting the PDU session establishment request from the UE to a controlplane function in a mobile communication network may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of transmitting the PDU session establishment request from the UE to a control-plane function in a mobile communication network may be performed by a UE as described with reference to Figure 5.

[0135] At 806, the method may include receiving, from the control-plane function, a PDU session establishment accept message notifying the UE of establishment of a PDU session. The operations of receiving, from the control-plane function, a PDU session establishment accept message notifying the UE of establishment of a PDU session may beperformed in accordance with examples as described herein. In some implementations, aspects of the operations of receiving, from the control-plane function, a PDU session establishment accept message notifying the UE of establishment of a PDU session may be performed by a UE as described with reference to Figure 5.

[0136] At 808, the method may include transmitting semantic communication via the established PDU session for processing. The operations of transmitting semantic communication via the established PDU session for processing may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of transmitting semantic communication via the established PDU session for processing may be performed by a UE as described with reference to Figure 5.

[0137] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0138] Figure 9 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a chipset as described herein. In some implementations, the chipset may execute a set of instructions to control the function elements of the chipset to perform the described functions.

[0139] At 902, the method may include generating a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication. The operations of generating a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of generating a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication may be performed by a chipset as described with reference to Figure 6.

[0140] At 904, the method may include outputting the PDU session establishment request for transmission to a control-plane function in a mobile communication network.The operations of outputting the PDU session establishment request for transmission to a control-plane function in a mobile communication network may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of outputting the PDU session establishment request for transmission to a control-plane function in a mobile communication network may be performed by a chipset as described with reference to Figure 6.

[0141] At 906, the method may include obtaining an indication that the PDU session is established. The operations of obtaining an indication that the PDU session is established may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of obtaining an indication that the PDU session is established may be performed by a chipset as described with reference to Figure 6.

[0142] At 908, the method may include outputting semantic communication for transmission via the established PDU session. The operations of outputting semantic communication for transmission via the established PDU session may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of outputting semantic communication for transmission via the established PDU session may be performed by a chipset as described with reference to Figure 6.

[0143] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0144] Figure 10 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0145] At 1002, the method may include receiving a protocol data unit, PDU, session establishment request, wherein the PDU session establishment request includes an indication that the PDU session is for semantic communication. The operations of receiving a protocol data unit, PDU, session establishment request, wherein the PDU session establishment request includes an indication that the PDU session is for semanticcommunication may be performed in accordance with examples as described herein. In some implementations, aspects of the operations receiving a protocol data unit, PDU, session establishment request, wherein the PDU session establishment request includes an indication that the PDU session is for semantic communication may be performed by a NE as described with reference to Figure 7.

[0146] At 1004, the method may include, based on the indication, selecting a user-plane function that is capable of supporting processing of semantic communication. The operations of based on the indication, selecting a user-plane function that is capable of supporting processing of semantic communication may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of based on the indication, selecting a user-plane function that is capable of supporting processing of semantic communication may be performed by a NE as described with reference to Figure 7.

[0147] At 1006, the method may include transmitting, to the user-plane function, a request message for establishing a PDU session comprising the indication. The operations of transmitting, to the user-plane function, a request message for establishing a PDU session comprising the indication may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of transmitting, to the user-plane function, a request message for establishing a PDU session comprising the indication may be performed a NE as described with reference to Figure 7.

[0148] At 1008, the method may include receiving, from the user-plane function, a response message for establishing the PDU session. The operations of receiving, from the user-plane function, a response message for establishing the PDU session may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of receiving, from the user-plane function, a response message for establishing the PDU session may be performed a NE as described with reference to Figure 7.

[0149] At 1010, the method may include transmitting a PDU session establishment accept message. The operations of transmitting a PDU session establishment accept message may be performed in accordance with examples as described herein. In someimplementations, aspects of the operations of transmitting a PDU session establishment accept message may be performed a NE as described with reference to Figure 7.

[0150] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0151] Figure 11 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0152] At 1102, the method may include receiving from a control plane function, a request message for establishing a PDU session, the request message comprising an indication that the PDU session is for semantic communication. The operations of receiving from a control plane function, a request message for establishing a PDU session, the request message comprising an indication that the PDU session is for semantic communication may be performed in accordance with examples as described herein. In some implementations, aspects of the operations receiving from a control plane function, a request message for establishing a PDU session, the request message comprising an indication that the PDU session is for semantic communication may be performed by a NE as described with reference to Figure 7.

[0153] At 1104, the method may include responsive to the request message, configuring a semantic processing entity to process semantic communication. The operations of responsive to the request message, configuring a semantic processing entity to process semantic communication may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of responsive to the request message, configuring a semantic processing entity to process semantic communication may be performed by a NE as described with reference to Figure 7.

[0154] At 1106, the method may include transmitting, to the control plane function, a response message for establishing the PDU session. The operations of transmitting, to the control plane function, a response message for establishing the PDU session may beperformed in accordance with examples as described herein. In some implementations, aspects of the operations of transmitting, to the control plane function, a response message for establishing the PDU session may be performed a NE as described with reference to Figure 7.

[0155] At 1108, the method may include receiving one or more semantic communication packets via the established PDU session. The operations of receiving one or more semantic communication packets via the established PDU session may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of receiving one or more semantic communication packets via the established PDU session may be performed a NE as described with reference to Figure 7.

[0156] At 1110, the method may include routing the one or more semantic communication packets to the semantic processing entity for processing. The operations of routing the one or more semantic communication packets to the semantic processing entity for processing may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of routing the one or more semantic communication packets to the semantic processing entity for processing may be performed a NE as described with reference to Figure 7.

[0157] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0158] Whilst embodiments have been described with reference to network functions in the context of a 5G mobile communication network for explanatory purposes, embodiments are not limited to being implemented in accordance with 5G radio access technology, and may extend to other radio access technologies.

[0159] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, thedisclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A User Equipment, UE, for enabling processing of semantic communication, the UE comprising: a processor; and a memory, configured to store instructions that, when executed by the processor, cause the UE to: generate a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication; transmit the PDU session establishment request from the UE to a controlplane function in a mobile communication network; receive, from the control-plane function, a PDU session establishment accept message notifying the UE of establishment of a PDU session; and transmit semantic communication via the established PDU session for processing.

2. The UE of claim 1, wherein the instructions, when executed by the processor, further cause the UE to generate the PDU session establishment request for the PDU session in response to receiving a request from an application on the UE to establish a data connection for semantic communication.

3. The UE of claim 1 or 2, wherein the indication is a Data Network Name, DNN, value associated with semantic communication.

4. The UE of claim 1 or 2, wherein the indication is a PDU session type associated with semantic communication.

5. The UE of claim 3, wherein the DNN value is pre-configured in the UE or provisioned by a network node.

6. The UE of any preceding claim, wherein the instructions, when executed by the processor, further cause the UE to establish a second concurrent PDU session for non- semantic communication.

7. The UE of any preceding claim wherein the sematic communication is transmitted from the UE to a user-plane function in the mobile communication network.

8. A processor for wireless communication, comprising: at least one controller, coupled with at least one memory and configured to cause the processor to: generate a Protocol Data Unit, PDU, session establishment request for a PDU session, the PDU session establishment request including an indication that the PDU session is for semantic communication; output the PDU session establishment request for transmission to a controlplane function in a mobile communication network; obtain an indication that the PDU session is established; and output semantic communication for transmission via the established PDU session.

9. A network node for wireless communication comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network node to: receive a protocol data unit, PDU, session establishment request, wherein the PDU session establishment request includes an indication that the PDU session is for semantic communication; based on the indication, select a user-plane function that is capable of supporting processing of semantic communication; transmit, to the user-plane function, a request message for establishing a PDU session comprising the indication; receive, from the user-plane function, a response message for establishing the PDU session; and transmit a PDU session establishment accept message.

10. The network node of claim 9, wherein the request message further comprises an identifier of a semantic processing entity configured for processing semantic communication.

11. The network node of either claim 9 or 10, wherein the indication is one of: a Data Network Name, DNN, value associated with semantic communication; or a PDU session type associated with semantic communication.

12. A network node for wireless communication comprising: at least one memory;at least one processor coupled with the at least one memory and configured to cause the network node to: receive from a control plane function, a request message for establishing a PDU session, the request message comprising an indication that the PDU session is for semantic communication; responsive to the request message, configure a semantic processing entity to process semantic communication; transmit, to the control plane function, a response message for establishing the PDU session; receive one or more semantic communication packets via the established PDU session; and route the one or more semantic communication packets to the semantic processing entity for processing.

13. The network node of claim 12, wherein the network node is further configured, in response to receiving the request message, to determine a semantic processing entity to process semantic communication.

14. The network node of claim 12, wherein the request message further comprises an identifier of a semantic processing entity capable of processing semantic communication.

15. The network node of any one of claims 12-14, wherein the semantic processing entity is external to the network node and wherein the configuring the semantic processing entity comprises establishing a tunnel to the semantic processing entity.

16. The network node of any one of claims 12-14, wherein the network node comprises the semantic processing entity and the configuring the semantic processing entity comprises enabling the semantic processing entity to process semantic information.

17. The network node of claim 16, wherein the semantic processing entity is configured to: in response to receiving the one or more packets, extract semantic information from the one or more packets; and determine an action to be taken regarding the one or more packets on the basis of the semantic information.

18. The network node of claim 17, wherein the semantic processing entity is further configured to parse the semantic information using an ontology to determine a meaning of the one or more packets.

19. The network node of claim 17 or 18, wherein the action to be taken by the semantic processing entity comprises routing at least one of the one or more packets to a second network node for further processing.

20. The network node of any of claims 17 to 19, wherein the action to be taken by the semantic processing entity comprises performing processing of at least one of the one or more packets.

Images