Semantic communication

Abstract

One disclosure of the present specification provides a method. The method may comprise the steps of: transmitting, to a first network entity, a request message related to a data session; receiving, from the first network entity, an acceptance message related to the data session; transmitting, to a second network entity, data related to task-oriented communication; and receiving, from the second network entity, information related to semantic decoding for the data.

Description

Semantic communication

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR, meeting both urgent market needs and the longer-term requirements outlined by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). NR must be inherently forward-compatible.

[0005] Conventional data communications, such as 5G communications, aim to transmit precise bit sequences. The need for semantic and / or task-oriented communication to accurately convey the meaning and / or intent of the data transmitted by the sender is being discussed. However, the problem with conventional technologies is that there is no method to support semantic and / or task-oriented communication.

[0006] According to one embodiment of the present disclosure, a method is provided. The method may include: transmitting a request message related to a data session to a first network entity; receiving an acceptance message related to the data session from the first network entity; transmitting data related to a task-oriented communication to a second network entity; and receiving information related to semantic decoding of the data from the second network entity.

[0007] According to one embodiment, a device implementing the method is provided.

[0008] According to one embodiment of the present disclosure, a method is provided. The method may include: receiving a request message related to a data session of a device from a first network entity; transmitting a response message related to the data session to the first network entity; receiving data transmitted by the device; performing semantic decoding on the data; and transmitting information related to the semantic decoding to the device.

[0009] According to one embodiment, a device implementing the method is provided.

[0010] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0011] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0012] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0013] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0014] Figures 5 and 6 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0015] Figure 7 shows an example of a data flow to which the implementation of this specification is applied.

[0016] Figures 8a and 8b illustrate examples of control plane protocol stacks to which the implementation of the present specification applies.

[0017] Figure 9 shows an example of a protocol stack related to UE / UPF measurement to which the implementation of this specification applies.

[0018] Figure 10 illustrates an example of a procedure related to semantic communication to which the implementation of this specification applies.

[0019] Figure 11 illustrates an example of the operations of a sender and a receiver related to semantic communication to which the implementation of this specification applies.

[0020] FIG. 12 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0021] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0022] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

[0023] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0024] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0025] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0026] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0027] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

[0028] Additionally, parentheses used herein may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0029] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0030] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0031] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

[0032] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0033] The 5G usage scenario shown in FIG. 1 is only an example, and the technical features of this specification can be applied to other 5G usage scenarios not shown in FIG. 1.

[0034] The three main requirement categories for 5G are (1) enhanced mobile broadband (eMBB), (2) massive machine type communication (mMTC), and (3) ultra-reliable and low latency communications (URLLC).

[0035] Referring to FIG. 1, a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

[0036] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0037] The wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0038] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

[0039] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0040] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communication / connection can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D (Device-To-Device) communication), and base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access and Backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of the various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present specification.

[0041] NR supports multiple numerologies, or subcarrier spacings (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0042] The NR frequency band can be defined by two types of frequency ranges (FR1 and FR2). The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range," and FR2 can mean the "above 6 GHz range," which can be called millimeter wave (mmW).

[0043] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0044] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 2 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include unlicensed bands. Unlicensed bands may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

[0045] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0046] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also Narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (Non-Bandwidth Limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PANs (Personal Area Networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0047] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0048] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

[0049] The first wireless device (100) may include at least one transceiver, such as a transceiver (106), at least one processing chip, such as a processing chip (101), and / or one or more antennas (108).

[0050] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0051] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0052] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0053] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0054] The second wireless device (200) may include at least one transceiver, such as a transceiver (206), at least one processing chip, such as a processing chip (201), and / or one or more antennas (208).

[0055] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0056] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0057] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements code, instructions and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0058] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0059] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, and a Service Data Adaptation Protocol (SDAP) layer). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0060] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a Memory Control Processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer readable storage media and / or combinations thereof.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0061] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0062] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0063] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0064] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0065] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of this specification or to control a transceiver (106) to perform UE operations according to the implementation of this specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

[0066] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0067] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0068] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0069] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0070] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0071] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

[0072] A transceiver (106) is operably coupled to the processor (102) and transmits and / or receives a radio signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a radio frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a radio signal.

[0073] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0074] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0075] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

[0076] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0077] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0078] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0079] - AUSF (Authentication Server Function)

[0080] -AMF (Access and Mobility Management Function)

[0081] - DN (Data Network), for example, operator services, Internet access, or third-party services.

[0082] - USDF (Unstructured Data Storage Function)

[0083] - NEF (Network Exposure Function)

[0084] - I-NEF (Intermediate NEF)

[0085] - NRF (Network Repository Function)

[0086] - NSSF (Network Slice Selection Function)

[0087] - PCF (Policy Control Function)

[0088] - SMF (Session Management Function)

[0089] - UDM (Unified Data Management)

[0090] - UDR (Unified Data Repository)

[0091] - UPF (User Plane Function)

[0092] - UCMF (UE radio Capability Management Function)

[0093] - AF (Application Function)

[0094] - UE (User Equipment)

[0095] - (R)AN ((Radio) Access Network)

[0096] - 5G-EIR (5G-Equipment Identity Register)

[0097] - NWDAF (Network Data Analytics Function)

[0098] - CHF (CHarging Function)

[0099] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

[0100] - N3IWF (Non-3GPP InterWorking Function)

[0101] - TNGF (Trusted Non-3GPP Gateway Function)

[0102] - W-AGF (Wireline Access Gateway Function)

[0103] Figure 4 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0104] For clarity of the point-to-point diagram in Figure 4, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0105] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0106] The 5G system architecture includes the following benchmarks:

[0107] - N1: Reference point between UE and AMF.

[0108] - N2: Reference point between (R)AN and AMF.

[0109] - N3: Reference point between (R)AN and UPF.

[0110] - N4: Reference point between SMF and UPF.

[0111] - N6: Reference point between UPF and data network.

[0112] - N9: Reference point between two UPFs.

[0113] The following benchmarks illustrate the interactions that exist between NF services in NF.

[0114] - N5: Reference point between PCF and AF.

[0115] - N7: Reference point between SMF and PCF.

[0116] - N8: Reference point between UDM and AMF.

[0117] - N10: Reference point between UDM and SMF.

[0118] - N11: Reference point between AMF and SMF.

[0119] - N12: Reference point between AMF and AUSF.

[0120] - N13: Reference point between UDM and AUSF.

[0121] - N14: Reference point between two AMFs.

[0122] - N15: Reference point between PCF and AMF for non-roaming scenarios, and reference point between PCF and AMF of visited network for roaming scenarios.

[0123] - N16: Reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network)

[0124] - N22: Reference point between AMF and NSSF.

[0125] In some cases, two NFs may need to be interconnected to serve a UE.

[0126] Describes the PDU session establishment procedure. See Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0127] Figures 5 and 6 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0128] Establishing a PDU session may involve:

[0129] - UE-initiated PDU session establishment procedure

[0130] - PDU session handover between 3GPP and non-3GPP initiated by UE

[0131] - PDU session handover from UE-initiated EPS to 5GS.

[0132] - Network-triggered PDU session establishment procedure

[0133] A PDU session may be associated with either (a) a single connection type at a given time, i.e., either a 3GPP connection or a non-3GPP connection, or (b) multiple connection types simultaneously, i.e., one 3GPP connection and one non-3GPP connection. A PDU session associated with multiple connection types is called a multi-access (MA) PDU session and may be requested by an access traffic steering, switching, splitting (ATSS) capable UE.

[0134] Figures 5 and 6 specify a procedure for establishing a PDU session associated with a single connection type at a given time.

[0135] In the procedures shown in Figures 5 and 6, it is assumed that the UE is already registered with the AMF, so unless the UE is emergency registered, the AMF has already retrieved the user subscription data from the UDM.

[0136] First, the procedure of Fig. 5 is explained.

[0137] (1) Step 1: To establish a new PDU session, the UE generates a new PDU session ID.

[0138] The UE initiates the PDU session establishment procedure requested by the UE by sending an NAS message containing a PDU session establishment request message within the N1 SM container. The PDU session establishment request message includes the PDU session ID, the requested PDU session type, the requested session and service continuity (SSC) mode, 5G SM capabilities, Protocol Configuration Options (PCO), the SM PDU DN Request Container, and the UE Integrity Protection Maximum Data Rate.

[0139] If the PDU session establishment is a request to establish a new PDU session, the request type is "Initial Request." If the request refers to an existing PDU session switching between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing packet data network (PDN) connection in the EPC, the request type is "Existing PDU Session." If the PDU session establishment is a request to establish a PDU session for emergency services, the request type is "Emergency Request." If the request refers to an existing PDU session for emergency services switching between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for emergency services in the EPC, the request type is "Existing Emergency PDU Session."

[0140] The UE includes the S-NSSAI from the allowed NSSAI of the current connection type. If a mapping of allowed NSSAIs (Mapping of Allowed NSSAIs) is provided to the UE, the UE provides both the S-NSSAI of the VPLMN (visited VPLMN) from the allowed NSSAIs and the corresponding S-NSSAI of the HPLMN from the mapping of allowed NSSAIs.

[0141] (2) Step 2: AMF selects an SMF. If the request type indicates "Initial Request" or the request is due to a handover from an EPS or other non-3GPP connection provided by an AMF, AMF stores the connection type of the PDU session as well as the association of S-NSSAI(s), data network name (DNN), PDU session ID, and SMF ID.

[0142] If the request type is "Initial Request" and the message also contains a previous PDU session ID representing an existing PDU session, AMF selects an SMF and stores the association of the new PDU session ID, S-NSAI(s), and the selected SMF ID.

[0143] If the request type indicates "Existing PDU Session," AMF selects an SMF based on the SMF-ID received from the UDM. AMF updates the stored connection type for the PDU session.

[0144] If the request type indicates "Existing PDU Session", which refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and if the serving PLMN S-NSSAI of the PDU session is in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases:

[0145] - When the SMF ID and AMF corresponding to the PDU session ID belong to the same PLMN;

[0146] - If the SMF ID corresponding to the PDU session ID belongs to HPLMN;

[0147] Otherwise, AMF rejects the PDU session establishment request with an appropriate rejection cause.

[0148] AMF rejects requests from emergency-registered UEs whose request type does not indicate "Emergency Request" or "Existing Emergency PDU Session".

[0149] (3) Step 3: If the AMF is not associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Initial Request"), the AMF invokes the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Existing PDU Session"), the AMF invokes the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

[0150] The AMF transmits the S-NSSAI of the serving PLMN to the SMF from the allowed NSSAI. For a roaming scenario of local breakout (LBO), the AMF also transmits the corresponding S-NSSAI of the HPLMN to the SMF from the mapping of the allowed NSSAI.

[0151] The AMF ID is the UE's GUAMI, which uniquely identifies the AMF serving the UE. The AMF passes the PDU session ID along with the N1 SM container containing the PDU session establishment request message received from the UE. The GPSI (generic public subscription identifier) ​​is included if available to the AMF.

[0152] If a UE in limited service state is registered for emergency services without providing SUPI, the AMF provides PEI instead of SUPI. If a UE in limited service state is registered for emergency services while providing SUPI but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive a SUPI for the UE or if the AMF indicates that the SUPI is not authenticated, the UE is considered unauthenticated.

[0153] AMF can include a PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies the home PCF (H-PCF) in non-roaming cases and the visited PCF (V-PCF) in LBO roaming cases.

[0154] (4) Step 4: If the session management subscription data for the S-NSSAI of the corresponding SUPI, DNN, or HPLMN is not available, the SMF can retrieve the session management subscription data from the UDM and be notified when the subscription data is modified.

[0155] (5) Step 5: SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF according to the request received in step 3.

[0156] If SMF receives the Nsmf_PDUSession_CreateSMContext Request in step 3 and can process the PDU session establishment request, SMF creates an SM context and responds to AMF by providing the SM context ID.

[0157] If the SMF decides not to accept the PDU session establishment, the SMF rejects the UE request by sending a NAS SM signal including the relevant SM rejection cause by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and the SMF proceeds to step 20 below, aborting the PDU session establishment procedure.

[0158] (6) Step 6: Optional secondary authentication / authorization may be performed.

[0159] (7a) Step 7a: When dynamic policy and charging control (PCC) is used in a PDU session, the SMF can perform PCF selection.

[0160] (7b) Step 7b: SMF performs the SM policy association establishment procedure to establish a PCF and SM policy association, and obtains the basic PCC rules for the PDU session.

[0161] (8) Step 8: SMF selects one or more UPFs.

[0162] (9) Step 9: The SMF may provide information about the satisfied policy control request trigger conditions by performing the SM policy association modification procedure initiated by the SMF.

[0163] (10) Step 10: If the request type indicates an "Initial Request," the SMF may initiate the N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate the N4 Session Modification procedure with the selected UPF.

[0164] In step 10a, the SMF can send an N4 session establishment / modification request to the UPF, providing packet detection, enforcement, and reporting rules to be installed in the UPF for the PDU session. In step 10b, the UPF can confirm by sending an N4 session establishment / modification response.

[0165] (11) Step 11: SMF sends an N1N2 message transfer message (e.g. Namf_Communication_N1N2 Message Transfer) to AMF.

[0166] The N1N2 Message Forwarding message may contain N2 SM information. The N2 SM information carries the following information that the AMF will forward to the (R)AN:

[0167] - CN Tunnel Info: Corresponds to the core network address of the N3 tunnel corresponding to the PDU session;

[0168] - QFI (QoS flow ID) corresponding to one or more QoS (quality of service) profiles;

[0169] - PDU Session ID: Indicates to the UE the association between RAN resources and a PDU session for the UE;

[0170] - S-NSSAI with value for serving PLMN (i.e. HPLMN S-NSSAI, or VPLMN S-NSSAI in case of LBO roaming);

[0171] - User plane security enforcement information determined by SMF;

[0172] - UE integrity protection maximum data rate received in PDU session establishment request message: if integrity protection is indicated as "Preferred" or "Required" in the user plane security enforcement information.

[0173] - RSN (redundancy sequence number) parameter

[0174] The N1N2 message transfer message may include an N1 SM container. The N1 SM container includes a PDU Session Establishment Accept message that the AMF will provide to the UE. The PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI. For the LBO roaming scenario, the PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0175] Multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment accept message and N2 SM information within the N1 SM container, if required, for QoS flows associated with QoS rules and QoS profiles.

[0176] If the PDU session establishment fails between steps 5 and 11, the N1N2 message forwarding message contains an N1 SM container containing a PDU session establishment rejection message, but does not contain N2 SM information. The (R)AN sends an NAS message containing a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted.

[0177] (12) Step 12: AMF sends a NAS message containing the PDU Session ID and PDU Session Establishment Accept message destined for the UE and the N2 SM information received from SMF to (R)AN within an N2 PDU Session Request message.

[0178] (13) Step 13: The (R)AN may perform AN-specific signaling exchanges with the UE related to the information received from the SMF. For example, in the case of the NG-RAN, the UE may perform an RRC connection reconfiguration with the UE to set up the necessary NG-RAN resources related to the QoS rules for the PDU session request received in step 12.

[0179] (R)AN forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signaling exchange with the UE includes (R)AN resource additions related to the received N2 command.

[0180] If N2 SM information is not included in step 11, steps 14-16b and 17 below are omitted.

[0181] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is described.

[0182] (14) Step 14: (R)AN sends an N2 PDU Session Response message to AMF. The N2 PDU Session Response message may include PDU Session ID, cause, N2 SM information (PDU Session ID, AN tunnel information, accepted / rejected QFI list, user plane enforcement policy notification), etc.

[0183] (15) Step 15: AMF sends an update SM context request message (e.g., Nsmf_PDUSession_UpdateSMContext Request) to SMF. AMF forwards the N2 SM information received from (R)AN to SMF.

[0184] (16a) Step S16a: SMF initiates the N4 session modification procedure with UPF. SMF provides AN tunnel information and corresponding forwarding rules to UPF.

[0185] (16b) Step S16b: UPF provides an N4 session modification response to SMF.

[0186] After this step, the UPF can forward any DL packets that may have been buffered for this PDU session to the UE.

[0187] (16c) Step 16c: If the SMF is not yet registered for this PDU session, the SMF may register with the UDM for the given PDU session.

[0188] (17) Step 17: SMF sends an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF.

[0189] After this step, AMF forwards the relevant events to which SMF subscribes.

[0190] (18) Step 18: At any time during the procedure after Step 5, if the PDU session establishment is not successful, the SMF can notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify (release). The SMF can also release the created N4 session, the PDU session address (e.g., IP address) if assigned, and possibly the association with the PCF. In this case, Step 19 below is omitted.

[0191] (19) Step 19: For PDU session type IPv6 or IPv4v6, SMF may generate and send an IPv6 Router Advertisement to the UE.

[0192] (20) Step 20: SMF can perform SM policy association modification initiated by SMF.

[0193] (21) Step 21: If the PDU session establishment fails after step 4, the SMF may unsubscribe for modification of session management subscription data if the SMF no longer processes the UE's PDU session.

[0194] Conventional wireless communication systems, guided by Claude E. Shannon's information theory, aim for the received bit stream to be identical to the transmitted bit stream, without a single bit of error. This bit-accuracy-centric design repeatedly requires physical-layer error correction, upper-layer retransmission (HARQ / ARQ) procedures, and extensive header and metadata insertion, accumulating transmission delays and energy consumption.

[0195] Meanwhile, mobile data traffic is projected to reach 250 Exabit (EB) per month by 2030, and there are reports that a single 5G base station consumes up to 10 KiloWatts (kW) of power when operating multiple bands. In other words, if bit-by-bit transmission continues, backhaul and base station equipment, as well as carbon emissions, will increase exponentially, making it difficult to meet the requirements of the 6G era, which demands ultra-low latency, ultra-low power, and eco-friendly services.

[0196] Moreover, existing protocols transmit raw data in its entirety, regardless of the meaning or intended use of the content, resulting in the inefficiency of transmitting 4K video as is, even in situations where, for example, a drone only needs to determine the “presence of a person.”

[0197] To overcome these limitations, semantic communication, or meaning-recovery-based communication, is being discussed. Semantic communication allows a sender to compress various data (e.g., sentences, images, and / or sensors) into a semantic feature vector based on semantic encoding, and then transmit the data.

[0198] The receiver can recover the same meaning as the data sent by the sender, rather than the same bit string as the data sent by the sender, based on semantic decoding (e.g., decoding using a pre-shared knowledge graph or a pre-trained language model).

[0199] Therefore, if the receiver understands the original meaning of the message as the sender, the transmission is considered successful, so retransmission can be omitted even if some bit errors are present. For example, when evaluating based on the Semantic Error Rate (SER), experimental results have shown that even in low Signal-to-Noise ratio environments, the amount of transmitted data can be reduced by up to 90% while maintaining an SER of 5% or less.

[0200] Semantic communication can support the ultra-reliable, ultra-low latency services that 6G aims for by reducing transmission delay, improving spectrum efficiency, and reducing base station power consumption.

[0201] In the various examples disclosed in this specification, semantic communication and task-oriented communication may be used interchangeably.

[0202] For reference, based on task-oriented communication, the sender can transmit only the minimum information necessary to ensure the success rate of a specific task to be performed by the receiver. The sender extracts only the features essential for task execution through information bottleneck theory or attention weight analysis, and the sender can adjust the transmission rate according to channel conditions and deadlines based on encoding (e.g., adaptive encoding, semantic encoding, etc.). The receiver can perform classification, control, and / or inference based on the features received from the sender, and can retrain the encoder by providing real-time feedback on the task success rate (TSR).

[0203] However, the prior art has a problem in that it lacks a method that supports semantic communication and / or task-oriented communication. For example, a method is needed to effectively perform semantic communication and / or task-oriented communication.

[0204] As previously explained, conventional communication technologies are based on the Shannon paradigm, which aims for error-free communication by the receiver, ensuring that the transmitted bits are accurately received. According to conventional technology, communication is performed regardless of the meaning conveyed by the transmitted bits. For example, a receiver can only send a success acknowledgment if it correctly receives the transmitted bits. However, in semantic networks that employ task-oriented data communication, the principle of the data transmission mechanism is not error-free communication based on the Shannon paradigm.

[0205] For reference, “semantic errors” mentioned in the prior art mean a case where the transmitted bits themselves were received correctly, but the receiver transmitted semantically erroneous information. For example, semantic errors are used in the following cases. For example, TS 24.501 V18.6.0 discloses 5GSM cause - #41 Semantic error in the TFT operation. For example, TS 24.007 V18.1.0 discloses Syntactic errors - “A message is defined to have semantically incorrect contents if it contains information which, possibly dependant on the state of the receiver, is in contradiction to the resources of the receiver and / or to the procedural part.”

[0206] Unlike communication that aims to accurately convey bit sequences used in conventional technology, semantic communication or task-oriented communication can mean communication that aims to accurately convey the meaning or intent of data.

[0207] For example, in conventional communication technologies, a transmitter may support channel encoding, and a receiver may support channel decoding. The transmitter may encode input data through channel encoding and transmit it over a physical channel. The receiver may channel decode the received signal to generate output data.

[0208] In semantic communication, a sender can support semantic encoding and channel encoding. Furthermore, the sender may store background knowledge for semantic communication. A receiver can support semantic decoding and channel decoding. Furthermore, the receiver may store background knowledge for semantic communication. In semantic communication, the sender can semantically encode input data based on the background knowledge. The sender can channel-encode the semantically encoded data and transmit it over a physical channel. The receiver can channel-decode the received signal and then semantically decode it based on the background knowledge to generate output data.

[0209] To support semantic communications, various detailed technologies may be required, such as semantic coding (e.g., semantic source coding, semantic channel coding), and transmission and reception techniques to overcome the diversity of background knowledge.

[0210] Various examples of the disclosure of this specification describe examples of methods for effectively resolving semantic mismatches between senders and receivers based on semantic communication. For example, according to one embodiment, a method for resolving semantic mismatches between information senders and receivers during data transmission and reception, among semantic communication protocol technologies, may be described.

[0211] In future 6G networks, semantic and goal-oriented aspects may be emphasized. This may imply the importance of interpreting the sender's intended meaning or achieving a common goal. For example, a receiver may be able to interpret the meaning of received bits. For example, in a smart building monitoring system, if a receiver receives "Hire," it may interpret the event "Fire" based on the received information. In future communications, such as 6G, semantic networks may also adopt machine learning-based semantic learning mechanisms to develop semantic learning strategies to achieve interpretation capabilities.

[0212] If semantic communication is adopted as a 3GPP standard, the existing 3GPP protocol stack may not be suitable for efficiently handling processing for semantic communication, and a new data transmission mechanism for semantic communication other than the existing 3GPP data transmission processing method may be required.

[0213] Referring to the example of FIG. 7, an example of encapsulating user plane data (e.g., IP packets) in a conventional 5G system is described.

[0214] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0215] Figure 7 shows an example of a data flow to which the implementation of this specification is applied.

[0216] For reference, with respect to Figure 7, a data flow example based on TS 38.300 V18.1.0 Figure 6.6-1 may be referenced.

[0217] In a conventional 5G system, user plane data (e.g., the IP packet at the top of Figure 7) can be encapsulated within an SDAP SDU, as shown in Figure 7. In a conventional 4G system, user data can be encapsulated within a PDCP SDU. For example, semantic analysis of user plane data can be performed above the SDAP sublayer and below the application layer.

[0218] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0219] Figures 8a and 8b illustrate examples of control plane protocol stacks to which the implementation of the present specification applies.

[0220] Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), Physical Layer (PHY), Non-Access Stratum (NAS), and Radio Resource Control (RRC) are shown.

[0221] Figures 8a and 8b illustrate an example of a control plane protocol stack. For reference, TS 38.300 V18.1.0 Figure 4.4.2-1 Control-Plane Protocol Stack may be referenced.

[0222] With respect to control plane data, each protocol layer of FIGS. 8a and 8b can generate signaling data.

[0223] For example, the NAS control protocol may terminate at a network entity involved in mobility on the network side (e.g., an AMF or a Mobility Management Entity (MME)). However, if the data is encoded in a container within a NAS message (e.g., a Steering of Roaming (SOR) transport container), the receiver interpreting the data may not be the AMF. For example, if the SOR signaling data is encoded in a SOR transport container within a NAS signaling message, the receiver interpreting the SOR signaling data may be an Application Function (AF) rather than the AMF. At a minimum, the final endpoint can perform semantic analysis of the control plane data.

[0224] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0225] Figure 9 shows an example of a protocol stack related to UE / UPF measurement to which the implementation of this specification applies.

[0226] Figure 9 illustrates an example of a protocol stack related to UE / UPF measurements in connection with a MA PDU session based on 3GPP access and type IP. With respect to Figure 9, reference may be made to TS 23.501 V18.5.0 Figure 5.32.5.4-1.

[0227] Referring to FIG. 9, an example of a user plane measurement protocol called Performance Measurement Function (PMF) for measuring access network performance in a 5G system is illustrated.

[0228] For data transmission based on semantic analysis, data modifications based on semantic analysis at the receiver may be related to error rates or traffic distribution. Therefore, semantic analysis-based data transmission may require functions similar to conventional user-level measurement and measurement reporting.

[0229] Various examples of the disclosure herein may describe the actions of a sender and / or a receiver in semantic communication. Examples of actions taken by a network entity involved in analysis to perform analysis related to semantic communication and transmit the analysis results to a receiver may also be described.

[0230] For reference, in various examples disclosed herein, a sender may refer to an entity that transmits data related to semantic communication. For example, a sender may be a terminal (e.g., UE) or a base station. For example, a sender may also be a network entity, such as an application-related network entity (e.g., AF), a mobility-related network entity (e.g., AMF), or a session-related network entity (e.g., SMF).

[0231] For reference, in various examples of the disclosure of this specification, a receiver may refer to an entity that receives data related to semantic communication. For example, the receiver may be a terminal (e.g., UE) or a base station. For example, the receiver may also be a network entity such as an application-related network entity (e.g., AF), a mobility-related network entity (e.g., AMF), or a session-related network entity (e.g., SMF).

[0232] Note that in various examples disclosed herein, if the receiver transmits data related to semantic communication (e.g., semantically encodes the data), the receiver may also be the sender. Conversely, if the sender receives data related to semantic communication (e.g., semantically decodes the data), the sender may also be the receiver.

[0233] For reference, in various examples disclosed herein, a network entity involved in analysis may perform analysis on data related to semantic communication. For example, the network entity involved in analysis may be a NWDAF. For example, the network entity involved in analysis may be referred to as a SEMantic Analysis monitoring Function (SEMAF), but this is merely an example, and the name of the network entity involved in analysis is not limited thereto.

[0234] According to one embodiment of the disclosure of the present specification, in semantic communications or task-oriented communications, a sending entity (e.g., a sender) can transmit semantically encoded data to a receiving entity (e.g., a receiver).

[0235] A receiver can perform semantic decoding on data received from a sender. The receiver can transmit one or more of the following information (e.g., information relevant to semantic decoding) to the sender:

[0236] a) Data modification information (or indication) (e.g., information regarding whether the recipient has modified and interpreted the data received)

[0237] b) The result of the recipient modifying the data (e.g. modified data)

[0238] c) The result of the recipient's interpretation of the data (e.g., information interpreted by the recipient), or the result of the recipient's interpretation after modifying the data (e.g., the result of the recipient's interpretation of the modified data after modifying the data).

[0239] d) Information relating to requesting the sender to retransmit the data (e.g., information indicating that it would be helpful for the sender to retransmit the data).

[0240] e) Information relating to assistance information for data interpretation (e.g., information requesting the recipient to transmit assistance information to the sender);

[0241] f) Information on whether the interpreted information (or the interpreted information after modification by the receiver) is information related to the task-oriented operation of the receiver. For example, in a smart building monitoring system, the receiver may perform an operation related to smart building monitoring. In this case, if the receiver receives the received data called hire, the receiver may modify hire to fire and then interpret fire. In this case, the receiver may transmit to the sender information that the interpreted information was information related to the task-oriented operation of the receiver. In this case, the receiver may transmit f) together with a) and / or b) to the sender. In another example, the receiver may transmit to the sender information that the interpreted information was information not related to the task-oriented operation of the receiver. In this case, the receiver may transmit f) together with d) and / or e) to the sender.

[0242] g) Request for confirmation (e.g. request for confirmation)

[0243] h) statistics (e.g., statistics related to semantic decoding)

[0244] i) Additional semantic information. For example, the receiver can semantically analyze (or decode) the received data using the word "fire." After semantically analyzing (or decoding), the receiver can transmit additional semantic information, such as "emergency event," to the sender.

[0245] For example, statistics may mean statistical values ​​for improving tasks related to semantic communication.

[0246] Additionally, and / or optionally, the recipient may transmit the statistics to a statistics collection entity (e.g., an entity involved in the analysis) (e.g., NWDAF, SEMAF).

[0247] Below, an example of a procedure related to semantic communication is described with reference to FIG. 10.

[0248] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0249] Figure 10 illustrates an example of a procedure related to semantic communication to which the implementation of this specification applies.

[0250] Referring to Figure 10, the network entities involved in the sender, receiver, and analysis are illustrated.

[0251] Note that the sender can also act as the receiver. Alternatively, the receiver can act as the sender.

[0252] Note that in the example of Figure 10, the network entity involved in the analysis receives information from the receiver and / or transmits information to the receiver, but this is merely an example. For example, the network entity involved in the analysis may also receive information from the sender and / or transmit information to the sender.

[0253] For reference, in the example of Fig. 10, the sender may be interpreted as an information transmitting entity, and the receiver may be interpreted as an information receiving entity.

[0254] In step (S1001), the sender can transmit data to the receiver.

[0255] For example, a sender may perform semantic encoding and then transmit data to a receiver.

[0256] The receiver can perform semantic decoding on the data transmitted from the sender.

[0257] In step (S1002), the receiver can transmit an analysis request message to a network entity involved in the analysis.

[0258] For example, the analysis request message may include information related to semantic decoding. For example, the analysis request message may include one or more of the information described in a) to i) above. For example, the analysis request message may include statistics.

[0259] Information related to semantic decoding may include, for example, one or more of information related to whether the receiver modified and interpreted data received from the sender, information related to whether the information interpreted by the receiver was the information intended by the sender, and / or information related to statistics related to semantic decoding.

[0260] In step (S1003), a network entity involved in the analysis may transmit a message including the analysis results to a recipient. The network entity involved in the analysis may be a network entity performing the analysis.

[0261] For reference, with regard to analysis, this specification mainly describes the proposed content, and for operations and procedures between network entities related to analysis, refer to TS 23.288V18.6.0.

[0262] Network entities involved in the analysis (e.g., SEMAF, NWDAF) may collect one or more of the following information as input for the analysis. In addition, network entities involved in the analysis may also receive one or more of the information a) to i) described above. The information below is an example, and the collected information is not limited thereto. The entity transmitting the information below may be a device acting as a sender of semantic communication (e.g., UE, network entity, etc.) and / or a device acting as a receiver (e.g., UE, network entity, etc.), or the entity transmitting the information below may be intermediate nodes / network entities participating in the semantic communication:

[0263] a-1) Number of network entities that transmitted data

[0264] b-1) Number of times the received data was modified as a result of semantic decoding

[0265] c-1) Number of failures in information verification after semantic decoding

[0266] d-1) Number of times the semantic decoding result received data was incorrectly modified

[0267] After performing the analysis, a network entity involved in the analysis may generate an output (e.g., an analysis result) containing one or more of the following information. The network entity involved in the analysis may transmit the output (e.g., an analysis result) to a receiver, a sender, and / or intermediate nodes / network entities participating in the semantic communication. The receiver may utilize the output (e.g., an analysis result) as background knowledge. The information below is provided as an example, and the output information generated after the analysis is not limited to:

[0268] a-2) Assistance data or assistance information (e.g., assistance information for data interpretation, assistance information to be used for data encoding)

[0269] b-2) The number of network entities from which the network entity involved in the analysis (e.g., the statistics collecting network entity) collected data (e.g., the number of network entities that provided data to the network entity involved in the analysis).

[0270] c-2) Data collection time

[0271] d-2) Data collection area

[0272] e-2) Reliability of semantic decoding (e.g., reliability of data collection) (e.g., a standard value for the accuracy of collected data indicating the validity of semantic communication as a result of semantic decoding, similar to the accuracy of collected data used in AI / ML data collection)

[0273] f-2) Statistics related to semantic decoding

[0274] A network entity involved in the analysis can transmit outputs (e.g., analysis results) to network entities that utilize the output information (e.g., senders, receivers, and intermediate nodes / network entities participating in the semantic communication). Based on the outputs (e.g., analysis results), the network entities that utilize the output information (e.g., senders, receivers, and intermediate nodes / network entities participating in the semantic communication) can perform one or more of the following actions to improve semantic communication performance:

[0275] a-3) When transmitting semantic data, the sender of semantic communication can send assistance data that aids in data interpretation. For example, the assistance data "emergency event" can be sent along with "fire."

[0276] b-3) The recipient of semantic communication can interpret data based on assistance data. For example, based on pre-stored assistance data such as "normal event, emergency event," the recipient can interpret the result as "fire."

[0277] c-3) A network entity involved in the analysis can transmit an output (e.g., analysis result) including the data collection time to a receiver of semantic communication or a network entity transmitting the analysis data input. In this case, the receiver of semantic communication or the network entity transmitting the analysis data input can adjust the data collection unit time based on the data collection reliability result. For example, if the data collection reliability is sufficiently high, the receiver or the network entity transmitting the analysis data input can reduce the data collection time. For another example, if the data collection reliability is not high, the receiver or the network entity transmitting the analysis data input can increase the data collection time.

[0278] d-3) As another example, if the data collection reliability is sufficiently high, the sender, receiver, and intermediate nodes / network entities involved in semantic communication may reduce the number of network entities used for data collection. Conversely, if the data collection reliability is not high, the sender, receiver, and intermediate nodes / network entities involved in semantic communication may increase the number of network entities used for data collection.

[0279] e-3) Based on the output (e.g., analysis results), the data collection area can be changed according to the requirements for specific tasks related to semantic communication. These requirements can be provided, for example, by the Application Function (AF) or Application Server (AS). Based on these requirements, the network entity involved in the analysis can adjust the analysis area and generate output information that includes the adjusted analysis area.

[0280] Note that one or more of steps (S1002) and / or (S1003) may be omitted. For example, steps (S1001) and (S1004) may be performed, or steps (S1001), (S1003), and (S1004) may be performed.

[0281] In step (S1004), the receiver can transmit information to the sender based on semantic decoding.

[0282] The information transmitted by the recipient may include one or more of the information i) to g) described above.

[0283] In the disclosure of this specification, task-oriented communications and semantic communications are used interchangeably.

[0284] In the disclosure of this specification, data transmitted by a transmitter may refer to data transmitted after the transmitter performs semantic encoding (or semantic data processing). For example, in a communication system (e.g., 5G system, 6G system, etc.), data transmitted by a transmitter may be data that is converted into a semantic data format (and / or task-oriented data format) after a bit sequence of data generally refers to is semantically encoded by the transmitter.

[0285] In the disclosure of the present specification, the sender (or the operation of the sender) and / or the receiver (or the operation of the receiver) may be some layers of the protocol stack layers of FIGS. 8A and 8B (or operations performed by some layers), or may be a newly added layer (or operations performed by a newly added layer). For example, the sender (or the operation of the sender) and / or the receiver (or the operation of the receiver) may be a new layer between PDCP and SDAP, a new layer above SDAP (or operations performed by the new layer), or a new layer above NAS (or operations performed by the new layer). The new layer for task-oriented communications may have an interface with the protocol layers of the existing 5G system, and the new layer may operate for functions such as semantic analysis and semantic data processing.

[0286] In the disclosure of this specification, the sender and / or receiver may be some of the network entities of FIG. 4, or may be newly added new entities. Alternatively, the sender and / or receiver may be newly added network functions. For example, the sender may be a new entity that interfaces with the UE. For example, the receiver may be a new entity that interfaces with the AF or UPF.

[0287] In the disclosure of this specification, data transmission may include user data transmission and / or control signaling data transmission. For example, user data (e.g., IP packet) may be encapsulated in an SDAP SDU or in a PDCP SDU, as described in the example of FIG. 7.

[0288] Referring to the example of Fig. 11, an example of the actions of a receiver and / or a sender related to semantic communication is described.

[0289] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0290] Figure 11 illustrates an example of the operations of a sender and a receiver related to semantic communication to which the implementation of this specification applies.

[0291] Figure 11 is an example scenario. Below, an example of the operation of the sender and / or the operation of the receiver is described.

[0292] In step (S1101), the sender can transmit data to the receiver.

[0293] For example, a sender can perform semantic data processing for task-oriented communication. The sender can transmit semantically encoded data to the receiver.

[0294] In step (S1102), the receiver can perform semantic decoding.

[0295] For example, a receiver that receives data can perform semantic decoding on the data. For example, the receiver can perform semantic decoding, interpreting the received bit sequence using semantic analysis functions to extract information relevant to a given task.

[0296] For example, the receiver may convert the received bit sequence into semantic information for task-oriented communications through background knowledge and semantic decoding. For example, if the bit sequence received by the receiver is "hire," the receiver may interpret "hire" as semantic information "fire" by semantically decoding it based on the background knowledge "environmental monitoring." Note that in various examples of the disclosure of this specification, task-oriented communications and semantic communications may be used as terms with the same meaning.

[0297] Alternatively, for example, the receiver could perform semantic decoding based on the received bit sequence (e.g., the receiver could interpret the result as "hire" after semantic decoding). This could limit the receiver's autonomy in interpreting information during semantic communication. In this case, the receiver may need to verify the accuracy of the information extracted through semantic decoding.

[0298] In step (S1103), the receiver can transmit information to the sender.

[0299] For example, the recipient may transmit to the sender one or more of the information a) to i) described above.

[0300] For example, a receiver may modify the received data to extract meaningful information from it, such as by changing the bit sequence. In this case, the receiver may transmit an indication (e.g., information a)) and / or b) described above to the sender, informing the sender that the data has been modified.

[0301] For example, the Receiver may transmit the interpreted information (e.g., modified data, semantic information after semantic analysis) to the Sender after Semantic Decoding.

[0302] In some implementations, the receiver may also send a request (e.g., Request for confirmation) to the sender to confirm that the extracted information is accurate (e.g., g) information).

[0303] For example, in task-oriented communications for an environmental monitoring system, a receiver might receive the message "hire." After semantic decoding, the receiver might extract the message "fire." In this case, the receiver could then send the sender information (e.g., "fire" or "emergency"), interpreted as appropriate for its task, and request confirmation from the sender. For example, the receiver could send information c) and information g) to the sender.

[0304] Here, the message including information (or indication) and / or confirmation request information transmitted by the receiver to the sender may be a protocol layer message of an existing 5G system (e.g., NAS signaling, PDCP SDU), a newly added protocol layer message, or an application layer message in the form of user data.

[0305] For example, a new SDU type can be defined as shown in the example in Table 3.

[0306] Bit Description000IP001Non-IP010Ethernet011Unstructured100ARPXXXSemantic data101-111Reserved

[0307] A receiver can send a message to a sender with the SDU type set to semantic data (Bit XXX), as shown in the example in Table 3. For example, the SDU type of a message containing information transmitted by the receiver to the sender can be set to semantic data.

[0308] The receiver can transmit statistics on the information extracted after semantic decoding to the receiver or a network entity involved in the analysis (e.g., a statistics collection network entity). The receiver and / or the network entity involved in the analysis (e.g., a statistics collection network entity) can also perform tasks such as background knowledge updates based on the statistics information to make task-oriented data transmission for the receiver's task more efficient. For example, the receiver and / or the network entity involved in the analysis (e.g., a statistics collection network entity) can transmit an analysis result message containing information related to tasks such as background knowledge updates to the receiver.

[0309] In step (S1104), the sender can transmit information to the receiver.

[0310] For example, based on an indication or confirmation request message received from the receiver, the sender may transmit information to the receiver. For example, the sender may retransmit data to the receiver, transmit confirmation to the receiver, transmit support information for semantic decoding to the receiver, or transmit the result (e.g., success, failure) of an analysis related to semantic decoding (e.g., receiver analysis) to the receiver. For example, after receiving the semantic decoding analysis result, the receiver may transmit the decoding analysis result to the network entity performing the analysis. For another example, if the sender transmits a failure, the sender may subsequently transmit the number of semantic decoding failures, the time and / or the region information when the analysis result was collected.

[0311] As another example, a sender may receive an "emergency" message from the receiver, interpreted by the receiver as a result of data decoding analysis. In this case, if the resulting value received by the sender differs from the semantics of the data originally transmitted, the sender may retransmit the data.

[0312] When a transmitter retransmits data, it may also send an indication to the receiver that the receiver's semantic decoding is incorrect. This indication may be a response message to a conformation request received from the receiver, or it may be a transmitter-initiated indication.

[0313] Based on an indication (e.g., information related to assistance information for data interpretation) or confirmation request message received from the Receiver, the Transmitter may transmit assistance information to the Receiver. For example, assistance information may be information related to updating the Receiver with background knowledge that may be helpful for semantic decoding.

[0314] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0315] FIG. 12 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0316] For reference, the procedure illustrated in FIG. 12 is merely an example, and the scope of the disclosure of this specification is not limited by the example in FIG. 12.

[0317] For example, with respect to the example of FIG. 12, the operations described in the examples of FIGS. 1 to 11 may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 12, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0318] The operations illustrated in FIG. 12 are merely examples, and the scope of the disclosure of this specification is not limited to the operations illustrated in FIG. 12.

[0319] In the example of FIG. 12, the network entity may be a network entity associated with the user plane (e.g., UPF). The network entity illustrated in FIG. 12 may be referred to as a second network entity in the description related to FIG. 12.

[0320] In the following description, the first network entity may be a network entity involved in the session (e.g., SMF). The third network entity may be a network entity involved in the analysis (e.g., SEMAF or NWDAF).

[0321] Before the operations according to the example of FIG. 12 are performed, the PDU session establishment procedure according to the examples of FIG. 5 and FIG. 6 may be performed.

[0322] For example, a UE may transmit a request message related to a data session (e.g., a PDU Session Establishment Request) to the AMF, and the AMF may forward the request message related to the data session (e.g., a PDU Session Establishment Request) to a selected SMF. When the SMF transmits an acceptance message related to the data session (e.g., a PDU Session Acceptance Request) to the AMF, the AMF may transmit an acceptance message related to the data session (e.g., a PDU Session Acceptance Request) to the UE.

[0323] For example, as described in step 10 of FIG. 5, the SMF may transmit an N4 session establishment (or modification) request message related to the UE's PDU session to the UPF. The UPF may transmit an N4 session establishment (or modification) request message related to the UE's PDU session to the SMF.

[0324] For reference, although not illustrated in FIG. 12, examples of the behavior of network entities involved in the analysis may also be described below. Network entities involved in the analysis may be network entities that perform analysis related to semantic communication (e.g., SEMAF and / or NWDAF).

[0325] At step (S1201), the UE can transmit data to a second network entity.

[0326] For example, the data may be data related to task-oriented communication.

[0327] At step (S1202), the second network entity can perform semantic decoding.

[0328] At step (S1203), the second network entity may transmit information to the UE.

[0329] For example, the information may be information related to semantic decoding of data.

[0330] For example, information related to semantic decoding may include one or more of: information related to whether the second network entity modified the data; information related to a result of the second network entity modifying the data; information related to a result of the second network entity interpreting the data; information related to a request for retransmission of the data; information requesting support information; information related to whether a result of the second network entity interpreting the data is related to a task-oriented operation of the second network entity; a confirmation request; statistics related to the semantic decoding; and / or additional semantic information.

[0331] In some implementations, information related to semantic decoding may include one or more of the information a) to i) described above.

[0332] In some implementations, the UE may determine, based on the information received in step (S1203), whether the result of the second network entity interpreting or modifying the data is related to the semantics of the data transmitted by the UE. For example, based on the information related to semantic decoding including information related to the result of the second network entity interpreting the data and / or information related to the result of the second network entity modifying the data, the UE may determine whether the result of the interpretation or the result of the modification is related to the semantics of the data.

[0333] In this case, for example, based on whether the interpretation or modification result is determined to be relevant to the semantics of the data, the UE may transmit a confirmation message to the second network entity. Based on whether the interpretation or modification result is determined to be irrelevant to the semantics of the data, the UE may retransmit the data to the second network.

[0334] In some implementations, information related to semantic decoding may include information requesting support information. In this case, the UE may transmit support information containing background knowledge related to semantic decoding to the second network entity.

[0335] In some implementations, the second network entity may transmit an analysis request message containing information related to the semantic decoding to the third network entity. In this case, the second network entity may receive an analysis response message containing the analysis results from the third network entity.

[0336] For example, the analysis results may include one or more of the following: support information related to semantic decoding; the number of network entities that provided data to the network entities involved in the analysis; the time of data collection; the region of data collection; and / or the confidence of the semantic decoding.

[0337] In some implementations, a transmitter may perform one or more of the following actions: The transmitter may transmit data to a receiving entity (e.g., a receiver) after semantic encoding. The transmitter may receive information related to the result of semantic decoding from the receiving entity. The transmitter may transmit data or a confirmation to the receiving entity based on the information received from the receiving entity. Optionally, the transmitter may also transmit support information to the receiving entity based on the information received from the receiving entity.

[0338] In some implementations, a receiver may perform one or more of the following actions: The receiver may receive data from a sender (e.g., a network entity). After semantic decoding, the receiver may determine whether the received data has been modified (or whether to modify the received data). The receiver may transmit information related to the semantic decoding result to the sender (e.g., the network entity). The receiver may transmit statistics to inform the sender (e.g., the network entity) or other network entities about the semantic decoding result.

[0339] This specification may have various effects.

[0340] For example, to effectively support semantic communication and / or task-oriented communication, we propose data transmission result reporting and analysis operations for semantic communication accuracy and improvement. Based on the various examples disclosed in this specification, semantic communication and / or task-oriented communication can be effectively performed.

[0341] For example, semantic data processing based on a different method from that of conventional communication systems can be effectively supported, and extended protocol enhancements can be supported.

[0342] For reference, the operation of the terminal (e.g., UE, etc.) described in this specification can be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal can be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal described in this specification can be processed by one or more processors (102 or 202). The operation of the terminal described in this specification can be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). The one or more processors (102 or 202) control one or more memories (104 or 204) and one or more transceivers (105 or 206), and execute the instructions / programs stored in one or more memories (104 or 204) to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0343] Additionally, the commands for performing the operations of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the terminal described in the disclosure of this specification.

[0344] For reference, the operations of a network node (e.g., AMF, SMF, UPF, AF, SEMAF, etc.) or a base station (e.g., NG-RAN, gNB, RAN, (R)AN, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operations of the network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operations of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

[0345] Additionally, the instructions for performing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the network node or base station described in the disclosure of this specification.

[0346] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to these specific embodiments, and may be modified, changed, or improved in various forms within the scope of the spirit and claims of this specification.

[0347] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0348] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. A step of transmitting a request message related to a data session to a first network entity; A step of receiving an acceptance message related to the above data session from a first network entity; A step of transmitting data related to task-oriented communication to a second network entity; and A method comprising the step of receiving information related to semantic decoding of the data from the second network entity.

2. In paragraph 1, Information related to the above semantic decoding is: Information regarding whether the second network entity has modified the data; Information relating to the result of the second network entity modifying the data; Information related to the results of the second network entity interpreting the data; Information relating to a request for retransmission of the above data; Information requesting support information; Information on whether the result of the second network entity interpreting the data is related to the task-oriented operation of the second network entity; Request for confirmation; Statistics related to the above semantic decoding; and / or Additional semantic information, A method comprising one or more pieces of information.

3. In paragraph 1 or 2, A method further comprising a step of determining whether the interpretation result or the modification result is related to the semantics of the data, based on the information related to the semantic decoding including information related to the result of the second network entity interpreting the data and / or information related to the result of the second network entity modifying the data.

4. In paragraph 3, A method further comprising the step of transmitting a confirmation message to the second network entity based on the determination that the interpreted result or the modified result is related to the semantics of the data.

5. In paragraph 3, A method further comprising the step of retransmitting the data to the second network based on a determination that the interpreted result or the modified result is not related to the semantics of the data.

6. In any one of paragraphs 1 to 5, A method further comprising the step of transmitting support information including background knowledge related to the semantic decoding to the second network entity based on the information related to the semantic decoding including information requesting support information.

7. In the device, At least one transmitter / receiver; at least one processor; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein at least one processor is adapted to perform a method according to any one of claims 1 to 6.

8. At least one processor; and At least one memory storing instructions and being operably electrically connected to at least one processor, At least one processor is: an apparatus adapted to perform a method according to any one of claims 1 to 6.

9. A non-transitory computer-readable medium (CRM) that records commands, The above instructions, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 1 to 6. CRM.

10. A step of receiving a request message related to a data session of the device from a first network entity; A step of transmitting a response message related to the data session to the first network entity; A step of receiving data transmitted by the above device; A step of performing semantic decoding on the above data; and A method comprising the step of transmitting information related to the semantic decoding to the device.

11. In paragraph 10, Information related to the above semantic decoding is: Information regarding whether the second network entity has modified the data; Information relating to the result of the second network entity modifying the data; Information related to the results of the second network entity interpreting the data; Information relating to a request for retransmission of the above data; Information requesting support information; Request for confirmation; Statistics related to the above semantic decoding; and / or Semantic information after analysis related to the above semantic decoding, A method comprising one or more pieces of information.

12. In paragraph 10 or 11, A method in which the device determines whether the interpretation result or the modification result is related to the semantics of the data based on the information related to the semantic decoding including information related to the result of the second network entity interpreting the data and / or information related to the result of the second network entity modifying the data.

13. In paragraph 12, further comprising the step of receiving a confirmation message from said device, A method in which the above confirmation message is transmitted based on the determination that the above interpretation result or the above modification result is related to the semantics of the data.

14. In paragraph 12, further comprising a step of receiving data retransmitted by the device; A method in which the retransmitted data is transmitted based on the determination that the interpretation result or the modification result is not related to the semantics of the data.

15. In any one of paragraphs 10 to 14, A method further comprising the step of receiving support information including background knowledge related to the semantic decoding from the device, based on the information related to the semantic decoding including information requesting support information.

16. In any one of paragraphs 10 to 15, A step of transmitting an analysis request message including information related to the above semantic decoding to a third network entity; and A method further comprising the step of receiving an analysis response message including the analysis results from the third network entity.

17. In paragraph 16, The above analysis results include one or more of the following: Support information related to the above semantic decoding; The number of network entities that provided data to the network entities involved in the above analysis; Data collection time; Data collection area; and / or Reliability of the above semantic decoding, method.

18. In the device, the device: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein at least one processor is adapted to perform a method according to any one of claims 10 to 17.

Images