Method and apparatus for mapping QOS flow related to sensing service to drb

Abstract

Provided are a method by which a base station performs wireless communication, and an apparatus supporting same. The method may comprise the steps of: receiving sensing service data from a plane function for a sensing service; and mapping a first quality of service (QoS) flow related to the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

Description

Method and device for mapping QOS flows and DRBs related to sensing services

[0001] The present disclosure relates to a wireless communication system.

[0002] 5G NR, the successor to LTE (long-term evolution), is a new clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0003] The 6G (wireless communication) system aims to achieve (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy the requirements as shown in Table 1 below. For example, Table 1 can represent an example of the requirements of a 6G system.

[0004] Per device peak data rate 1 Tbps E2E latency 1 ms Maximum spectral efficiency 100 bps / Hz Mobility support Up to 1000 km / hr Satellite integration Fully AI Fully autonomous vehicle Fully XR Fully haptic communication Fully

[0005] In one embodiment, a method for a base station to perform wireless communication is provided. The method may include: receiving sensing service data from a plane function for a sensing service; and mapping a first quality of service (QoS) flow associated with the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

[0006] In one embodiment, a base station configured to perform wireless communication is provided. The base station may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, may cause the base station to: receive sensing service data from a plane function for a sensing service; and map a first quality of service (QoS) flow associated with the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

[0007] In one embodiment, a processing device configured to control a base station is provided. The processing device includes at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, when executed by the at least one processor, cause the base station to: receive sensing service data from a plane function for a sensing service; and map a first quality of service (QoS) flow associated with the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

[0008] In one embodiment, a non-transitory computer-readable storage medium having instructions recorded thereon is provided. The instructions, when executed, cause a base station to: receive sensing service data from a plane function for a sensing service; and map a first quality of service (QoS) flow associated with the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

[0009] Figure 1 illustrates a device-to-device communication procedure according to one embodiment of the present disclosure.

[0010] FIG. 2 illustrates a radio protocol architecture according to one embodiment of the present disclosure.

[0011] FIG. 3 illustrates the structure of a wireless frame according to one embodiment of the present disclosure.

[0012] FIG. 4 illustrates a slot structure of a frame according to one embodiment of the present disclosure.

[0013] FIG. 5 illustrates an example of a BWP according to one embodiment of the present disclosure.

[0014] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0015] FIG. 7 illustrates an example of a communication scenario based on a 6G system according to one embodiment of the present disclosure.

[0016] FIG. 8 illustrates an example of a sensing operation according to one embodiment of the present disclosure.

[0017] FIG. 9 illustrates a support scenario for a sensing service in ISAC according to one embodiment of the present disclosure.

[0018] FIG. 10 illustrates a QoS model for a conventional 5G communication service according to one embodiment of the present disclosure.

[0019] FIG. 11 illustrates a QoS model for a 6G sensing service according to an embodiment of the present disclosure.

[0020] FIG. 12 illustrates a rule for mapping a QoS flow related to sensing service data to a DRB according to an embodiment of the present disclosure.

[0021] FIG. 13 illustrates a rule for mapping a QoS flow related to sensing service data to a DRB according to one embodiment of the present disclosure.

[0022] FIG. 14 illustrates a rule for mapping a QoS flow related to sensing service data to a DRB according to one embodiment of the present disclosure.

[0023] FIG. 15 illustrates a rule for mapping a QoS flow related to sensing service data to a DRB according to one embodiment of the present disclosure.

[0024] FIG. 16 illustrates a mapping relationship between a QoS flow related to a sensing service, a DRB for the sensing service, and a PDU session for the sensing service, according to one embodiment of the present disclosure.

[0025] FIG. 17 illustrates a method for a base station to perform wireless communication according to one embodiment of the present disclosure.

[0026] FIG. 18 illustrates a method for a first device to perform wireless communication according to one embodiment of the present disclosure.

[0027] FIG. 19 illustrates a communication system (1) according to one embodiment of the present disclosure.

[0028] FIG. 20 illustrates a wireless device according to an embodiment of the present disclosure.

[0029] FIG. 21 illustrates a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0030] FIG. 22 illustrates a wireless device according to an embodiment of the present disclosure.

[0031] FIG. 23 illustrates a mobile device according to one embodiment of the present disclosure.

[0032] In this disclosure, "A or B" can mean "only A," "only B," or "both A and B." In other words, "A or B" in this disclosure can be interpreted as "A and / or B." For example, "A, B or C" in this disclosure can mean "only A," "only B," "only C," or "any combination of A, B and C."

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

[0034] In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, 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.”

[0035] Additionally, in the present disclosure, “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.”

[0036] Additionally, parentheses used in the present disclosure 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 the present disclosure 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."

[0037] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

[0038] Technical features individually described in one drawing in this disclosure may be implemented individually or simultaneously.

[0039] In the present disclosure, higher layer parameters may be parameters set for the terminal, preset, or predefined. For example, a base station or network may transmit higher layer parameters to the terminal. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0040] In the present disclosure, "setting or defining" may be interpreted as being set or preset to a device through predefined signaling (e.g., SIB, MAC, RRC) from a base station or a network. In the present disclosure, "setting or defining" may be interpreted as being preset to a device. In the present disclosure, "setting or defining" may be interpreted as being set or preset to a device through predefined signaling (e.g., MAC, RRC, SCI (sidelink control information), device-to-device signaling control information, etc.) from another device. In the present disclosure, "setting or defining" may be interpreted as being preset to a device.

[0041] In the present disclosure, a user equipment (UE) may refer to a device, a portable device, a wireless device, etc. In the present disclosure, a base station (BS) may refer to a radio access network (RAN) node, a non-terrestrial network (NTN) cell / node, a transmission reception point (TRP), a network, an integrated access and backhaul (IAB) node, a device, a portable device, a wireless device, etc.

[0042] The technology proposed in the present disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0043] The technology proposed in this disclosure can be implemented with 6G wireless technology and applied to various 6G systems. For example, 6G systems can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0044] FIG. 1 illustrates a device-to-device communication procedure according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0045] Referring to FIG. 1, in step S101, a first device and a second device can perform synchronization. For example, the first device can be a terminal and / or at least one of the devices proposed in the present disclosure. For example, the second device can be a base station, a network, a RAN node, an NTN node / cell, a TRP, a terminal and / or at least one of the devices proposed in the present disclosure. For example, the first device can perform an initial cell search operation. For example, the first device can detect at least one synchronization signal transmitted by the second device according to a predefined rule. Here, for example, the synchronization signal can include a plurality of synchronization signals classified according to a structure or purpose (e.g., a primary synchronization signal, a secondary synchronization signal, etc.). Through this, the first device can identify the boundaries of the frame, subframe, time unit, slot, and / or symbol of the second device, and the first device can obtain information about the second device (e.g., a cell identifier).

[0046] In step S103, the first device can obtain system information transmitted by the second device. For example, the system information may include information related to the properties, characteristics, and / or capabilities of the second device required to connect to the second device and use the service. For example, the system information may be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., the channel used, whether it is provided on-demand), etc. For example, the system information may be classified into a master information block (MIB) and a system information block (SIB). For example, if necessary, the first device may transmit a signal requesting system information before receiving the system information. For example, the request and provision of system information may be performed after a random access procedure described below.

[0047] In step S105, the first device and the second device can perform a random access procedure. For example, the first device can transmit and / or receive at least one message (e.g., a random access preamble, a random access response message, etc.) for the random access procedure based on information related to a random access channel of the second device obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the first device can transmit a preamble (e.g., Msg1) through the random access channel, the first device can receive a random access response message (e.g., Msg2), the first device can transmit a message (e.g., Msg3) including information related to the first device (e.g., identification information) to the second device using scheduling information included in the random access response message, and the first device can receive a message (e.g., Msg4) for contention resolution and / or connection establishment. For example, Msg1 and Msg3 can be sent and received as one message (e.g., MsgA), and / or Msg2 and Msg4 can be sent and received as one message (e.g., MsgB).

[0048] In step S107, the first device and the second device may perform signaling of control information. Here, for example, the control information may be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport channels (e.g., a media access control (MAC) layer), a layer that handles physical channels (e.g., a physical (PHY) layer), etc. For example, the first device and the second device may perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and / or signaling for indicating allocated resources. For example, the control information may be signaled / transmitted via a control channel. For example, the control information and / or the control channel may be used to schedule at least one of data, a data channel (e.g., a shared channel), and / or control information on the data channel.

[0049] In step S109, the first device and the second device may transmit and / or receive data. For example, the first device and the second device may process, transmit, and / or receive data based on signaling of control information. For example, when transmitting data, the first device or the second device may perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and / or resource mapping on the information bits. For example, when receiving data, the first device or the second device may perform at least one of signal extraction from resources, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and / or channel decoding.

[0050] For example, the layers of a radio interface protocol between a first device and a second device can be divided into L1 (layer 1), L2 (layer 2), L3 (layer 3), etc. For example, a physical layer belonging to the first layer can provide an information transfer service using a physical channel, and an RRC (radio resource control) layer located in the third layer can play a role in controlling radio resources between the first device and the second device. For this purpose, for example, the RRC layer can exchange RRC messages between the first device and the second device.

[0051] FIG. 2 illustrates a radio protocol architecture according to an embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. For example, (a) of FIG. 2 may illustrate a radio protocol stack of a user plane for uplink communication or downlink communication, and (b) of FIG. 2 may illustrate a radio protocol stack of a control plane for uplink communication or downlink communication. For example, (c) of FIG. 2 may illustrate a radio protocol stack of a user plane for device-to-device communication, and (d) of FIG. 2 may illustrate a radio protocol stack of a control plane for device-to-device communication.

[0052] For example, the physical layer can provide information transmission services to upper layers using physical channels. For example, the physical layer can be connected to the upper layer, the medium access control (MAC) layer, through a transport channel. For example, data can be transmitted between the MAC layer and the physical layer through the transport channel. For example, transport channels can be classified according to how and with what characteristics data is transmitted over the wireless interface. For example, data can be transmitted between different physical layers (e.g., between the physical layers of a first device and a second device) through a physical channel. For example, the physical channel can be modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and time and frequency can be utilized as radio resources.

[0053] For example, the MAC layer can provide services to the upper layer, the radio link control (RLC) layer, through logical channels. For example, the MAC layer can provide a mapping function from multiple logical channels to multiple transport channels. For example, the MAC layer can provide a logical channel multiplexing function by mapping multiple logical channels to a single transport channel. For example, the MAC sublayer can provide data transmission services on logical channels.

[0054] For example, the RLC layer can perform concatenation, segmentation, and reassembly of RLC service data units (SDUs). For example, to guarantee the various quality of service (QoS) required by radio bearers (RBs), the RLC layer can provide three operating modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). For example, AM RLC can provide error correction through automatic repeat request (ARQ).

[0055] For example, the RRC (radio resource control) layer can be defined only in the control plane. For example, the RRC layer can be responsible for controlling logical channels, transport channels, and physical channels in relation to the configuration, re-configuration, and release of radio bearers. For example, an RB can mean a logical path provided by a first layer (e.g., a physical layer) and a second layer (e.g., a MAC layer, an RLC layer, a PDCP (packet data convergence protocol) layer, a SDAP (service data adaptation protocol) layer, etc.) for data transmission between a first device and a second device.

[0056] For example, the functions of the PDCP layer in the user plane may include forwarding of user data, header compression, and ciphering. For example, the functions of the PDCP layer in the control plane may include forwarding of control plane data and ciphering / integrity protection.

[0057] For example, establishing an RB can refer to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. For example, RBs can be divided into two types: signaling radio bearers (SRBs) and data radio bearers (DRBs). For example, SRBs can be used as a channel to transmit RRC messages in the control plane, while DRBs can be used as a channel to transmit user data in the user plane.

[0058] For example, a downlink transmission channel may include at least one of a broadcast channel (BCH) for transmitting system information, and / or a downlink shared channel (SCH) for transmitting user traffic or control messages. For example, traffic or control messages of a downlink multicast or broadcast service may be transmitted through the downlink SCH, or may be transmitted through a separate downlink multicast channel (MCH). Meanwhile, an uplink transmission channel may include at least one of a random access channel (RACH) for transmitting initial control messages, and / or an uplink shared channel (SCH) for transmitting user traffic or control messages. For example, a logical channel located above a transmission channel and mapped to the transmission channel may include at least one of a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and / or a multicast traffic channel (MTCH).

[0059] FIG. 3 illustrates the structure of a wireless frame according to an embodiment of the present disclosure. The embodiment of FIG. 3 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0060] Referring to FIG. 3, for example, a radio frame may be used in uplink transmission, downlink transmission, and / or device-to-device transmission. For example, a radio frame may have a length of 10 ms and may be defined as two 5 ms half-frames (HF). For example, a half-frame may include five 1 ms subframes (SF). For example, a subframe may be divided into one or more slots, and the number of slots within a subframe may be determined according to a subcarrier spacing (SCS). For example, each slot may include 12 or 14 OFDM (A) symbols, depending on a cyclic prefix (CP).

[0061] For example, when normal CP is used, each slot can contain 14 symbols. For example, when extended CP is used, each slot can contain 12 symbols. Here, for example, the symbols can contain OFDM symbols (or CP-OFDM symbols), SC-FDMA (single carrier-FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0062] Table 2 below shows the number of symbols per slot (N) depending on the SCS setting (u) when normal CP or extended CP is used. slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot) is an example.

[0063] CP type SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot Normal CP15kHz (u=0)1410130kHz (u=1)1420260kHz (u=2)14404120kHz (u=3)14808240kHz (u=4)1416016Extended CP60kHz (u=2)12404

[0064] For example, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of time resources (e.g., subframes, slots, or transmit time intervals (TTIs)) composed of the same number of symbols may be set differently between the merged cells. For example, in the present disclosure, time resources such as subframes, slots, TTIs, etc. may be referred to as time units.

[0065] For example, multiple numerologies, or SCSs, may be supported to support various services. For example, a 15 kHz SCS may support wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS may support dense urban areas, lower latency, and wider carrier bandwidth. For example, a 60 kHz or higher SCS may support bandwidths greater than 24.25 GHz to overcome phase noise.

[0066] FIG. 4 illustrates a slot structure of a frame according to an embodiment of the present disclosure. The embodiment of FIG. 4 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0067] Referring to FIG. 4, for example, a slot may include multiple symbols in the time domain. For example, a carrier may include multiple subcarriers in the frequency domain. For example, a resource block (RB) may be defined as multiple consecutive subcarriers in the frequency domain. For example, a bandwidth part (BWP) may be defined as multiple consecutive (P)RBs ((physical) resource blocks) in the frequency domain, and may correspond to one numerology (e.g., SCS, CP length, etc.). For example, a carrier may include at most N BWPs (where N is a positive integer). For example, data communication may be performed through an activated BWP. For example, each element may be referred to as a resource element (RE) in the resource grid, and one complex symbol may be mapped to it.

[0068] For example, a BWP may be a contiguous set of PRBs in a given numerology. For example, a PRB may be selected from a contiguous subset of common resource blocks (CRBs) for a given numerology on a given carrier.

[0069] For example, the BWP may be at least one of an active BWP, an initial BWP, and / or a default BWP. For example, the UE may not monitor the downlink radio link quality in a DL BWP other than the active DL BWP on the PCell (primary cell). For example, the UE may not receive a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), or a channel state information-reference signal (CSI-RS) (except for radio resource management (RRM)) outside of the active DL BWP. For example, the UE may not trigger channel state information (CSI) reporting for an inactive DL BWP. For example, the UE may not transmit a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) outside of the active UL BWP. For example, for downlink, the initial BWP can be given as a set of consecutive resource blocks (RBs) for the remaining minimum system information (RMSI) CORESET (control resource set) (set by the physical broadcast channel (PBCH)). For uplink, for example, the initial BWP can be given by the system information block (SIB) for the random access procedure. For example, the default BWP can be set by a higher layer. For example, the initial value of the default BWP can be the initial DL BWP.For energy saving, if a terminal does not detect DCI (downlink control information) for a certain period of time, the terminal may switch its active BWP to a default BWP.

[0070] FIG. 5 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. In the embodiment of FIG. 5, it is assumed that there are three BWPs.

[0071] Referring to FIG. 5, for example, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other, and a PRB may be a numbered resource block within each BWP. For example, point A may indicate a common reference point for a resource block grid.

[0072] For example, BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP ) can be set by. For example, point A can be an outer reference point of the PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) aligns. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and point A. For example, the bandwidth can be the number of PRBs in a given numerology.

[0073] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0074] As core implementation technologies of the 6G system, technologies such as artificial intelligence (AI), THz (terahertz) communication, optical wireless technology, free-space optical transmission (FSO) backhaul networks, massive MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0075] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. For example, AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. AI can also facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0076] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by using sub-THz communication with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF. Key characteristics of THz communications include (i) the widely available bandwidth to support very high data rates and (ii) the high path loss that occurs at high frequencies (requiring highly directional antennas). The narrow beamwidths generated by highly directional antennas reduce interference. The small wavelength of THz signals allows for a significantly larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.

[0077] - Large-scale MIMO technology

[0078] - Hologram beamforming (HBF)

[0079] - Optical wireless technology

[0080] - Free-space optical transmission backhaul network (FSO backhaul network)

[0081] - Quantum communication

[0082] - Cell-free communication

[0083] - Integration of wireless information and power transmission

[0084] - Integration of wireless communication and sensing

[0085] - Integrated access and backhaul network

[0086] - Big data analysis

[0087] - Reconfigurable intelligent surface

[0088] - metaverse

[0089] - Blockchain

[0090] Advanced Air Mobility (AAM): AAM can be a broad concept encompassing urban air mobility (UAM), regional air mobility (RAM), and uncrewed aerial systems (UAS). For example, AAM can include UAM, RAM, UAS, and uncrewed aerial vehicles (UAVs).

[0091] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle to vehicle (V2V) wireless communication and vehicle to infrastructure (V2I) wireless communication.

[0092] Non-terrestrial network (NTN): NTN can refer to a network or network segment that utilizes radio frequency (RF) resources mounted on satellites (or UAS platforms). NTN services may be considered to secure wider coverage or provide wireless communication services in locations where the installation of wireless communication base stations is difficult.

[0093] - Integrated sensing and communication (ISAC)

[0094] - Reconfigurable intelligent surface (RIS): RIS can be used to manipulate and enhance signal propagation in wireless communication environments. For example, a RIS can be composed of many small antennas, or metasurfaces, arranged on a surface, each of which can actively control the phase, amplitude, polarization, etc. of the reflected signal. For example, a RIS can improve signal reception by controlling the path, phase, and / or intensity of the propagating signal. For example, in the case of a RIS, power consumption can be very low because power is consumed only for controlling the phase and amplitude of the small antennas. For example, because a RIS can be reconfigured to suit different environments, it can meet diverse communication requirements and operate effectively in dynamic network environments.

[0095] FIG. 7 illustrates an example of a communication scenario based on a 6G system, according to an embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0096] Referring to FIG. 7, NTN communication can be performed based on satellite networks, high-altitude platform stations (HAPS) as international mobile telecommunications (IMT) base stations (BS), and terminals capable of aerial communication (e.g., AAMs). For example, to improve coverage, etc., devices such as satellite networks, HIBS, and terminals capable of aerial communication (e.g., AAMs) can act as relays. For example, an AAM can communicate with a base station, a satellite network, etc., and / or an AAM can communicate directly with a terminal, another AAM, etc.

[0097] Below, the integrated sensing and communication (ISAC) mentioned above is described in detail.

[0098] Integrated Sensing and Communications (ISAC) is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the environment and / or the characteristics of objects within the environment. Because radio frequency sensing does not require a device to connect to the object through a network, it can provide services for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service (e.g., sensing operation) may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing may provide an opportunity to enhance existing communication systems from communication networks to wireless communication and sensing networks. FIG. 8 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. Specifically, FIG. 8 (a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 8 (b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

[0099] The meanings of terms used in this disclosure may be as follows.

[0100] - ISAC: Integrated Sensing and Communication

[0101] - Sensing signal: A reference signal transmitted and received for sensing.

[0102] - Sensing transmitter (Tx: entity that transmits sensing signals)

[0103] - Sensing receiver (sensing Rx(receiver)): an entity that receives a sensing signal

[0104] - Monostatic sensing: Sensing in which the sensing transmitter and sensing receiver are co-located in the same TRP or UE.

[0105] - Bi-static sensing: Sensing in which the sensing transmitter and the sensing receiver are located in different TRPs or UEs.

[0106] - Multi-static sensing: Sensing with multiple sensing transmitters and / or multiple sensing receivers for the sensing target.

[0107] - Target object (TO): The object to be detected through sensing.

[0108] - Environment object (EO): An object whose location is known other than the target object.

[0109] - Clutter: Background or objects whose location cannot be specified, excluding the target object and environment object.

[0110] - Sensing RS (reference signal): Reference signal used for measurement for sensing purposes

[0111] - BS-BS sensing: Sensing in which BS#1 transmits a sensing RS and BS#2 receives the sensing RS. For example, if BS#1 and BS#2 are separate BSs, this may mean a BS-BS bi-static sensing operation. For example, if BS#1 and BS#2 are the same BS, this may mean a BS-BS mono-static sensing operation. For example, the BS may be a base station or a transmission and reception point (TRP). For example, if BS#1 and / or BS#2 are one or more BSs, this may mean a BS-BS multi-static sensing operation.

[0112] - BS-UE sensing: Sensing in which a BS transmits a sensing RS and a UE receives the sensing RS. For example, the BS may be a base station or a transmission and reception point (TRP). For example, if the BS and / or the UE are one or more BSs and / or one or more UEs, this may refer to a BS-UE multi-static sensing operation.

[0113] - UE-BS sensing: Sensing in which a UE transmits a sensing RS and a BS receives the sensing RS. For example, the BS may be a base station or a transmission and reception point (TRP). For example, if the BS and / or the UE are one or more BSs and / or one or more UEs, this may refer to a UE-BS multi-static sensing operation.

[0114] - UE-UE sensing: Sensing in which UE#1 transmits a sensing RS and UE#2 receives the sensing RS. For example, if UE#1 and UE#2 are separate UEs, this may mean a UE-UE bi-static sensing operation. For example, if UE#1 and UE#2 are the same UE, this may mean a UE-UE mono-static sensing operation. For example, the BS may be a base station or a transmission and reception point (TRP). For example, if UE#1 and / or UE#2 are one or more UEs, this may mean a UE-UE multi-static sensing operation.

[0115] - SMF: Sensing Management Function

[0116] - TSA: Target Sensing Area

[0117] Meanwhile, in conventional communications (e.g., NR Uu or NR sidelink), the sensing procedure of a device (e.g., a terminal or a base station) was not considered a service. However, since the main purpose of the ISAC service is to quickly detect and distinguish a target object through sensing, it is necessary to classify the sensing procedure (or operation) as a service that must satisfy one QoS requirement (e.g., sensing latency: the time it takes for a terminal that triggers sensing to trigger the sensing procedure and for a receiving terminal to receive the sensing result of the target object, or sensing accuracy, etc.). For example, in ISAC, the sensing behavior of a device (e.g., a terminal or a base station or a sensing management function (SMF)) can be considered a service that must satisfy the ISAC sensing QoS requirement, and the terminal can perform a sensing operation (e.g., transmitting a sensing reference signal and / or receiving a sensing reference signal) based on the sensing QoS.

[0118] For example, sensing in ISAC can be considered as a higher layer service that must satisfy sensing QoS (or sensing quality) based on sensing results, and a new QoS (e.g., Sensing QoS Flow ID (SQFI)) for the ISAC sensing service can be defined as follows.

[0119] - SQFI (Sensing QoS Flow ID)

[0120] - SQFI 1 ~ 8: For example, they can be distinguished according to the level of sensing QoS requirements. For example, sensing QoS requirements can include sensing accuracy, sensing latency (e.g., latency boundary from sensing triggering to receiving sensing results), or sensing priority (e.g., priority that can be used to determine which sensing service is triggered first based on priority when multiple sensing procedures are required). For example, a sensing service with a smaller (or higher) SQFI value can be defined as having a tighter QoS requirement (e.g., a sensing service requiring high sensing accuracy, or a sensing service requiring low / lower / lowest sensing latency).

[0121] Additionally, ISAC defines terminal and TRP (or base station) operations to support sensing services such as detection, localization, and tracking.

[0122] For example, the sensing QoS for ISAC services (detection, localization, tracking, etc.) could be as follows:

[0123] - Detection QoS: detection probability, false alarm probability

[0124] - Localization QoS: localization of the static objects, QoS parameters of localization (e.g., time delay, angle of arrival)

[0125] - Tracking QoS: Tracking the status changes of moving targets (e.g., vehicles or drones) (range, angle, velocity, etc.)

[0126] FIG. 9 illustrates a support scenario for sensing services in an ISAC, according to an embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0127] Referring to Fig. 9, the six main sensing modes are as follows. Specifically, Fig. 9 (a) shows gNB mono-static. In this case, the same gNB can perform both Tx and Rx roles. Fig. 9 (b) shows gNB bi-static. In this case, one gNB can perform the Tx role and the other gNB can perform the Rx role. Fig. 9 (c) shows gNB-to-UE bi-static. In this case, the gNB can perform the Tx role and the UE can perform the Rx role. Fig. 9 (d) shows UE-to-gNB bi-static. In this case, the UE can perform the Tx role and the gNB can perform the Rx role. Fig. 9 (e) shows UE mono-static. In this case, the same UE can perform both Tx and Rx roles. Figure 9 (f) shows a UE bi-static. In this case, one UE can perform the Tx role and another UE can perform the Rx role.

[0128] Meanwhile, in existing 5G systems, sensing services were not defined as a separate QoS model from communication traffic. In this case, the following problems may arise. For example, sensing traffic may be larger or have a higher traffic load than communication traffic. Therefore, if sensing traffic is mapped to the same data radio bearer (DRB) as communication traffic, the sensing traffic may excessively occupy the DRB resources, which may increase delays in communication traffic. Alternatively, if sensing traffic is continuously transmitted in large quantities, the base station scheduler may face a high load in handling priority adjustments and resource allocation between communication and sensing traffic. Alternatively, if large volumes of sensing traffic are processed within the same QoS flow or PDU session as communication services, problems such as deterioration of communication service quality, unpredictable delays, and packet loss may occur.

[0129] In this disclosure, we propose an operation for mapping sensing QoS (quality of service) flows and DRB (data radio bearers) in ISAC.

[0130] As a background for the proposal of the present disclosure, the QoS model for conventional 5G communication services is as follows.

[0131] FIG. 10 illustrates a QoS model for a conventional 5G communication service according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0132] Referring to FIG. 10, a QoS model (e.g., QoS flow to DRB mapping) for supporting communication services (e.g., uplink transmission, downlink transmission, uplink reception, downlink reception) in a conventional 5G system is illustrated. For example, a user plane function (UPF), which is an entity of a core network, can map service data flows (e.g., video, voice over internet protocol (VoIP), Best Effort, etc.) received from a data network (DN) to (each) QoS flow. And, for example, the UPF can configure one or more QoS flows into one PDU session. For example, a gNB (or an SDAP of the gNB) can map a QoS flow for service data received from the UPF to a DRB. At this time, for example, the gNB (or the SDAP of the gNB) can map one QoS flow to one DRB, or map multiple QoS flows to one DRB.

[0133] For example, in 6G ISAC, sensing services must be supported together with communication services, so new procedures may be required to map (sensing) QoS flows to sensing service data flows and / or to map sensing QoS flows to DRBs.

[0134] In this disclosure, we propose a new procedure for mapping sensing service data flows to sensing QoS flows and mapping sensing QoS flows to sensing DRBs, as follows.

[0135] Proposal 1. Mapping operation of sensing QoS flow and DRB based on sensing service QoS mode

[0136] Below, an embodiment of a 6G QoS model for supporting sensing services (e.g., transmission or reception) in 6G is shown.

[0137] In this disclosure, we propose a QoS model and procedure that enables a 6G core network entity to manage communication data flows (e.g., Best Effort, voice over internet protocol (VoIP), video, etc.) and sensing service data flows (e.g., sensing data) received from a data network (DN) as independent QoS flows.

[0138] FIG. 11 illustrates a QoS model for a 6G sensing service according to an embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0139] Referring to FIG. 11, a 6G core network entity can map sensing data received from a sensing function (SF), which is a network entity that manages sensing data (or, the sensing data can be received from a DN in the same way as communication data), to a sensing-only QoS flow separate from a communication data flow (e.g., Best Effort, voice over internet protocol (VoIP), video, etc.) received from a data network (DN). And, for example, the 6G core network entity can configure one or more sensing QoS flows into one PDU session (e.g., PDU session #1 of FIG. 11). In summary, for example, from a 6G core network entity for sensing, a service data flow (SDF) related to sensing can be mapped to one or more sensing QoS flows, and these one or more sensing QoS flows can be configured as a PDU session for sensing (e.g., PDU session #1 in FIG. 11). Meanwhile, for example, from a core network entity for communication (e.g., a core network entity separate from the 6G core network), a service data flow (SDF) related to communication can be mapped to one or more communication QoS flows, and these one or more communication QoS flows can be configured as a PDU session for communication (e.g., PDU session #2 in FIG. 11). For example, a base station (or an SDAP of the base station) can map a sensing QoS flow for sensing service data received from a 6G core network entity to a (sensing) DRB.At this time, for example, the base station (or the SDAP of the base station) can map one sensing QoS flow to one (sensing) DRB (e.g., DRB #1 or DRB #2 in FIG. 11), or map multiple sensing QoS flows to one (sensing) DRB. Meanwhile, for example, one communication QoS flow can be mapped to one (communication) DRB, or map multiple communication QoS flows to one (communication) DRB (e.g., DRB #3 in FIG. 11).

[0140] For example, so that a 6G core network entity can map a sensing service data flow to a sensing-dedicated QoS flow, a sensing function (SF) may provide the 6G core network entity with mapping configuration information between the sensing service data flow and the sensing QoS flow (e.g., QoS requirement information for each sensing service (e.g., latency, priority, reliability, accuracy, etc.), DRB information for the sensing service (e.g., the maximum number of sensing DRBs), sensing QoS flow ID information mapped to each sensing DRB), PDCP configuration information for the sensing service data (e.g., PDCP sequence number size information, out-of-delivery configuration (e.g., TRUE) information, etc.), RLC configuration information for the sensing service data (e.g., ACK mode / un-ACK mode configuration information, and mapping information between the QoS flow and DRB in Proposal 2 below). (mapping rules) can be passed.

[0141] In addition, for example, so that the base station (or the SDAP of the base station) can map the sensing QoS flow to the sensing DRB, the sensing function (SF) provides the base station with mapping configuration information between the sensing QoS flow and the sensing DRB (e.g., the mapped sensing QoS flow ID for each sensing service, the QoS requirement information for each sensing service (e.g., latency, priority, reliability, accuracy, etc.), the DRB information for the sensing service (e.g., the maximum number of sensing DRBs), the sensing QoS flow ID information mapped for each sensing DRB), the PDCP configuration information for the sensing service data (e.g., the size information of the PDCP sequence number, the out-of-delivery configuration (e.g., TRUE) information, etc.), the RLC configuration information for the sensing service data (e.g., the ACK mode / un-ACK mode configuration information, the mapping between the QoS flow and the DRB of Proposal 2 below). (rules) can be conveyed.For example, the base station can transmit to the UE mapping configuration information between the sensing QoS flow configured from the SF (sensing function) and the sensing DRB (e.g., the sensing QoS flow ID mapped to each sensing service, the QoS requirement information for each sensing service (e.g., latency, priority, reliability, accuracy, etc.), the DRB information for the sensing service (e.g., the maximum number of sensing DRBs), the sensing QoS flow ID information mapped to each sensing DRB), the PDCP configuration information for the sensing service data (e.g., the size information of the PDCP sequence number, the out-of-delivery configuration (e.g., TRUE) information, etc.), and the RLC configuration information for the sensing service data (e.g., the ACK mode / un-ACK mode configuration information, the mapping rule between the QoS flow and the DRB of Proposal 2 below).

[0142] In addition, for example, the sensing function (SF) may also transmit mapping configuration information between the sensing QoS flow and the sensing DRB directly to the UE (e.g., the sensing QoS flow ID mapped to each sensing service, the QoS requirement information for each sensing service (e.g., latency, priority, reliability, accuracy, etc.), the DRB information for the sensing service (e.g., the maximum number of sensing DRBs), the sensing QoS flow ID information mapped to each sensing DRB), the PDCP configuration information for the sensing service data (e.g., the size information of the PDCP sequence number, the out-of-delivery configuration (e.g., TRUE) information, etc.), and the RLC configuration information for the sensing service data (e.g., the ACK mode / un-ACK mode configuration information).

[0143] For example, through the 6G QoS model and / or the sensing service data flow to QoS flow mapping rule and / or the sensing QoS flow to sensing DRB mapping rule to support the proposed sensing service, the UE or the base station or the network entity can perform the following procedures.

[0144] For example, ISAC can establish independent PDU sessions for each communication service and sensing service.

[0145] For example, ISAC could establish independent DRBs for each of its communication services and sensing services.

[0146] For example, a QoS flow for a sensing service can be restricted from forming a PDU session with a QoS flow for a communication service. For example, the sensing service and the communication service can be managed as separate PDU sessions.

[0147] For example, a rule can be applied to map sensing QoS flows for a sensing service to a separate DRB than QoS flows for a communication service. For example, QoS flows for sensing and communication can be restricted from being configured into the same DRB.

[0148] For example, when sensing service data is transmitted from a sensing function (SF) to a UPF (e.g., a 6G core network entity) (e.g., a case where the sensing data is stored in the SF), the SF can transmit related settings (e.g., a sensing service data flow to QoS flow mapping rule, a sensing QoS flow to sensing DRB mapping rule) to the UPF (e.g., a 6G core network entity) and the base station so that the sensing data can be managed as a separate QoS flow. Alternatively, for example, when sensing service data is transmitted from a data network (DN) to a UPF (e.g., a 6G core network entity) like communication data (e.g., when the sensing data is transmitted over the Internet), the sensing function (SF) may transmit related settings (e.g., a sensing service data flow to QoS flow mapping rule, a sensing QoS flow to sensing DRB mapping rule) to the UPF (e.g., a 6G core network entity) and / or a base station so that the communication data (e.g., Best Effort, voice over internet protocol (VoIP), video, etc.) transmitted over the DN and the QoS flow and / or DRB of the sensing data can be independently managed.

[0149] Proposal 2. Mapping Rules between Sensing QoS Flows and DRBs

[0150] In this disclosure, we propose the following rules for mapping sensing service data QoS flows to DRBs.

[0151] FIG. 12 illustrates rules for mapping QoS flows related to sensing service data to DRBs, according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0152] Referring to FIG. 12, a sensing service data flow (e.g., PDU 1) may be configured as an independent PDU session from a communication data flow (e.g., PDU 2), and the sensing service data flow may be separately mapped to a sensing-only sensing QoS flow (e.g., QoS flow 1). Additionally, for example, the sensing QoS flow may be mapped to a separate DRB (e.g., DRB 1) from a communication DRB (e.g., DRB 2).

[0153] FIG. 13 illustrates rules for mapping QoS flows related to sensing service data to DRBs, according to one embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0154] Referring to FIG. 13, a sensing service data flow (e.g., PDU 1) may be composed of an independent PDU session from a communication data flow (e.g., PDU 2), and the sensing service data flow may be separately mapped to a sensing-only sensing QoS flow (e.g., QoS flow 1). However, for example, the sensing QoS flow and the communication QoS flow may be mapped to the same DRB.

[0155] FIG. 14 illustrates rules for mapping QoS flows related to sensing service data to DRBs, according to one embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0156] Referring to FIG. 14, a sensing service data flow (e.g., PDU 1) may be configured as an independent PDU session from a communication data flow (e.g., PDU 2), and the sensing service data flow may be mapped to the same QoS flow as the communication service data flow. Furthermore, for example, the sensing service data flow (e.g., PDU 1) and the communication data flow (e.g., PDU 2) may be mapped to the same DRB.

[0157] FIG. 15 illustrates rules for mapping QoS flows related to sensing service data to DRBs, according to one embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0158] Referring to FIG. 15, the sensing service data flow may be composed of a PDU session independent of the communication data flow, and the sensing service data flow may be mapped to the same QoS flow as the communication service data flow. However, for example, the sensing data flow (e.g., PDU 1) may be mapped to a separate DRB from the communication data flow (e.g., PDU 2).

[0159] Proposal 3. Operations for managing SDAP functions and SDAP entities to support sensing services.

[0160] In this disclosure, we propose the following SDAP functions and operations for managing SDAP entities to support sensing services in ISAC.

[0161] For example, the SDAP sublayer can support the following functions:

[0162] - Transmit user plane data;

[0163] - Mapping between QoS flows and DRBs for both downlink and uplink;

[0164] - Mapping between MBS QoS flow flows and MRBs for downlink;

[0165] - Mapping between PC5 QoS flows and SL-DRB for NR sidelink communication;

[0166] - Mark QoS flow ID on both downlink and uplink packets;

[0167] - Marking PC5 QoS flow ID in unicast NR sidelink communication packets;

[0168] - Mapping between reflective QoS flows and DRBs for uplink SDAP data PDUs;

[0169] - Mapping between sensing QoS flows and sensing DRBs for ISAC.

[0170] For example, management of SDAP entities might be as follows:

[0171] For example, an SDAP entity may be located at an SDAP sublayer. For example, multiple SDAP entities may be defined for a UE. For example, there may be an SDAP entity configured for each PDU session or MBS session of an NR Uu. For example, for an NR sidelink, an SDAP entity may be configured for each destination layer-2 ID and cast type of the UE.

[0172] For example, an SDAP entity can receive / forward SDAP SDUs to / from upper layers, and can transmit / receive SDAP data PDUs to / from peer SDAP entities via lower layers.

[0173] For example, on the transmitting side, when an SDAP entity receives an SDAP SDU from a higher layer, it can construct a corresponding SDAP data PDU and transmit it to a lower layer.

[0174] For example, at the receiving end, when an SDAP entity receives an SDAP data PDU from a lower layer, it can retrieve the corresponding SDAP SDU and pass it on to the upper layer.

[0175] For example, if the DL SDAP header is set, mapping of reflective QoS flows and DRBs can be performed at the UE.

[0176] For example, the mapping of reflective QoS flows to MRBs may not be supported. In this case, for example, the MRB may not contain an SDAP header.

[0177] For example, for NR sidelink communication, mapping of reflective PC5 QoS flows to SL-DRB may not be supported.

[0178] For example, there may be an SDAP entity set up for an independent PDU session for an ISAC sensing service. For example, for ISAC sensing, an SDAP entity may be set up per sensing service ID of a sensing device, per sensing QoS flow ID, per sensing priority, per sensing service data flow ID, or per target sensing area (TSA).

[0179] FIG. 16 illustrates a mapping relationship between a QoS flow associated with a sensing service, a DRB for the sensing service, and a PDU session for the sensing service, according to an embodiment of the present disclosure. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0180] Referring to FIG. 16, the UE may be a sensing transmitter and / or a sensing receiver having sensing-related capabilities. The xNB may be a network node that performs a base station function that communicates with the UE via a wireless interface in a 6G wireless access network. Meanwhile, a 6G core network may be newly defined separately from the conventional Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), and Sensing Function (SF).

[0181] For example, when a 6G core network receives sensing service data from a data network that manages sensing data, the 6G core network can create a PDU session that only includes the sensing service data flow. Alternatively, for example, the 6G core network can define filtering rules for the sensing service data flow and map the sensing service data flow to a specific QoS flow.

[0182] For example, the 6G core network can configure / manage PDU sessions such that QoS flow #1 associated with sensing service #1, QoS flow #3 associated with sensing service #1, and QoS flow #2 associated with sensing service #1 are included in the PDU session for the sensing service. Alternatively, for example, the 6G core network can configure / manage PDU sessions such that QoS flow #1 associated with sensing service #1, QoS flow #3 associated with sensing service #1, and QoS flow #2 associated with sensing service #1 are not included in the PDU session for the communication service. Alternatively, for example, the 6G core network can configure / manage PDU sessions such that QoS flow #4 associated with communication service #1 is not included in the PDU session for the sensing service. For example, the PDU sessions for the sensing service and the PDU sessions for the communication service can be managed / configured independently of each other. Meanwhile, for example, information that can map each QoS flow and DRB can be transmitted from the 6G core network to the xNB.

[0183] For example, the xNB may create one or more DRBs based on information received from the 6G core network. For example, the xNB may map one or more QoS flows to the DRB. For example, the xNB may determine which QoS flows can be mapped to the DRB based on QoS requirements. For example, based on the fact that the QoS requirements of QoS flow #1 associated with sensing service #1 and QoS flow #2 associated with sensing service #2 are identical, the xNB may map QoS flow #1 associated with sensing service #1 and QoS flow #2 associated with sensing service #2 to DRB #1 for the sensing service. Alternatively, for example, based on the fact that the QoS requirements of QoS flow #1 associated with sensing service #1 are different from the QoS requirements of QoS flow #3 associated with sensing service #1, the xNB may map QoS flow #1 associated with sensing service #1 to DRB #1 for sensing service and may map QoS flow #3 associated with sensing service #1 to DRB #2 for sensing service. Meanwhile, for example, the xNB may not map DRB #1 for sensing service and DRB #2 for sensing service to QoS flow #4 associated with communication service #1. For example, DRB for sensing service and DRB for communication service may be managed / configured independently of each other.

[0184] Embodiments of the present disclosure can be extended and applied to all six sensing scenarios of FIG. 9 described above.

[0185] Also, for example, the term "specific threshold" in the present disclosure may mean a threshold that is defined in advance or set (in advance) by a higher layer (e.g., including an application layer) of a network or a base station or a terminal. Also, for example, the term "specific set value" may mean a value that is defined in advance or set (in advance) by a higher layer (e.g., including an application layer) of a network or a base station or a terminal. Also, for example, "set by the network / base station" may mean an operation in which the base station sets (in advance) to the UE via higher layer RRC signaling, sets / signals to the UE via MAC CE, or signals to the UE via DCI.

[0186] The unicast service of the present disclosure can be interpreted by replacing the source layer-2 ID and destination layer-2 ID pair.

[0187] The groupcast service of the present disclosure can be interpreted by replacing the groupcast destination layer-2 ID.

[0188] The broadcast service of the present disclosure can be interpreted by replacing the broadcast destination layer-2 ID.

[0189] The control message (or signal) and data message (or signal) of the present disclosure may mean a control message (or signal) and data message (or signal) for wireless communication (e.g., LTE communication, NR communication, 6G communication, Wi-Fi communication, Bluetooth communication, and other wireless communication) other than a radar signal.

[0190] The source ID and destination ID of the present disclosure may mean a source layer 1 ID, a destination layer 1 ID, and / or may mean a source layer 2 ID, a destination layer 2 ID.

[0191] For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set resource pool-specifically (or differently or independently). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set congestion level-specifically (or differently or independently). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set service priority-specifically or service type-specifically (or differently or independently). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set QoS requirements (e.g., latency, reliability) or QoS profiles or PQIs-specifically (or differently or independently). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for a traffic type (e.g., periodic or aperiodic generated traffic). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for a sidelink transmission resource allocation mode (e.g., resource allocation mode 1 or resource allocation mode 2). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for a Tx profile (e.g., a Tx profile indicating a service supporting sidelink DRX operation or a Tx profile indicating a service not required to support DRX operation).

[0192] For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on whether PUCCH configuration is supported (e.g., when PUCCH resources are configured or when PUCCH resources are not configured). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on a resource pool (e.g., a resource pool where PSFCH is configured or a resource pool where PSFCH is not configured). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on a type and / or priority of a service or packet. For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for a QoS profile or QoS requirement (e.g., URLLC / EMBB traffic, reliability, latency). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for a PQI (PC5 QoS indicator). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for a PFI (packet flow identifier). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) for a cast type (e.g., unicast, groupcast, broadcast).For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for a congestion level (e.g., CBR) of a resource pool. For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for a SL HARQ feedback scheme (e.g., NACK-only feedback, ACK / NACK feedback). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) for HARQ feedback enabled MAC PDU transmission and / or HARQ feedback disabled MAC PDU transmission. For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on whether a PUCCH-based SL HARQ feedback reporting operation is set. For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on whether pre-emption and / or re-evaluation are performed (or whether resource reselection based thereon is performed). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on (L2 or L1) source identifiers and / or destination identifiers. For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or their associated parameters (e.g., thresholds) may be set identifier-specifically (or differently or independently) based on the combination of the (L2 or L1) source layer ID and the destination layer ID.For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set identifier-specifically (or differently or independently) according to a pair of (L2 or L1) source / destination layer IDs and a combination of cast types. For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set direction-specifically (or differently or independently) of a pair of source layer IDs and destination layer IDs. For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on whether a PC5 RRC connection or link is established. For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on whether SL DRX is performed or whether SL DRX is supported. For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on an SL mode type (e.g., resource allocation mode 1 or resource allocation mode 2). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on whether periodic or aperiodic resource reservation is performed.

[0193] For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or their associated parameters (e.g., thresholds) can be set specifically (or differently or independently) for SL groupcast HARQ feedback options (e.g., NACK-only feedback, ACK / NACK feedback, distance-based NACK-only feedback). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or their associated parameters (e.g., thresholds) can be set specifically (or differently or independently) for SL mode 1 CG types (e.g., SL CG type 1 or SL CG type 2). For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or their associated parameters (e.g., thresholds) can be set specifically (or differently or independently) for SL link establishment. For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on the connection state between the terminal and the base station (e.g., RRC connected state, idle state, inactive state). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on the SL HARQ process identifier (ID). For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) can be set specifically (or differently or independently) depending on whether a transmitting terminal (Tx UE) or a receiving terminal (Rx UE) performs an SL DRX operation. For example, whether (some) of the proposed methods / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) may be set specifically (or differently or independently) depending on whether the transmitting or receiving terminal has a power saving function enabled (whether it is a power saving UE).For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set when PSFCH transmission (TX) and PSFCH reception (RX) overlap from a specific UE perspective. For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set when there are multiple PSFCH transmissions that exceed the UE capability. For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or related parameters (e.g., thresholds) may be specifically (or differently or independently) set when PSFCH transmission and / or reception are omitted. For example, whether (some) of the proposed schemes / rules of the present disclosure are applicable and / or the associated parameters (e.g., thresholds) may be specifically (or differently or independently) set when a receiving terminal (Rx UE) actually or successfully receives a PSCCH and / or PSSCH (re)transmission from a transmitting terminal (Tx UE).

[0194] The applicability of the proposals and proposed rules of the present disclosure (and / or the associated parameter settings) may also be applied to mmWave SL operation.

[0195] FIG. 17 illustrates a method for a base station to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0196] Referring to FIG. 17, in step S1710, the base station may receive sensing service data from a plane function for the sensing service. In step S1720, the base station may map a first quality of service (QoS) flow related to the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

[0197] For example, the first QoS flow associated with the sensing service data can be managed independently from the second QoS flow associated with the communication service data.

[0198] For example, based on the first QoS flow being a dedicated QoS flow for the sensing service, the sensing service data can be mapped to the first QoS flow.

[0199] For example, a PDU session for the sensing service including the first QoS flow associated with the sensing service data may be different from a PDU session including the second QoS flow associated with the communication service data.

[0200] For example, the sensing data radio bearer mapped to the first QoS flow associated with the sensing service data may be different from the data radio bearer mapped to the second QoS flow associated with the communication service data.

[0201] For example, based on the plurality of QoS flows including the first QoS flow being related to the sensing service, the plurality of QoS flows may be mapped to the sensing data radio bearer.

[0202] Additionally, for example, the base station can receive configuration information for mapping between a QoS flow related to sensing and a data radio bearer related to sensing from a plane function for the sensing service. For example, based on the configuration information, the first QoS flow related to the sensing service data can be mapped to the sensing data radio bearer. For example, the configuration information can include at least one of a sensing QFI (QoS Flow ID) mapped per sensing service, a QoS requirement per sensing service, a sensing data radio bearer for the sensing service, a sensing QFI mapped per sensing data radio bearer, radio link control (RLC) configuration information for sensing service data, or packet data convergence protocol (PDCP) configuration information for sensing service data.

[0203] For example, QoS flows related to communication services may be restricted from being included in PDU sessions for the sensing service.

[0204] For example, QoS flows associated with communication services may be restricted from being mapped to the sensing data radio bearer.

[0205] For example, the mapping between the first QoS flow associated with the sensing service data and the sensing data radio bearer may be supported by a service data adaptation protocol (SDAP) entity.

[0206] For example, an SDAP entity may be established for a PDU session for the sensing service. For example, the SDAP entity may be established based on at least one of a sensing service ID, a sensing service QFI, a sensing priority, a sensing service data flow ID, or a target sensing area.

[0207] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (202) of the base station (200) can control the transceiver (206) to receive sensing service data from a plane function for the sensing service. Then, the processor (202) of the base station (200) can map a first quality of service (QoS) flow related to the sensing service data to a sensing data radio bearer. For example, the first QoS flow can be included in a packet data unit (PDU) session for the sensing service.

[0208] According to one embodiment of the present disclosure, a base station configured to perform wireless communication may be provided. For example, the base station may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the base station to: receive sensing service data from a plane function for a sensing service; and map a first quality of service (QoS) flow associated with the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

[0209] According to one embodiment of the present disclosure, a processing device configured to control a base station may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the base station to perform the following steps: receiving sensing service data from a plane function for a sensing service; and mapping a first quality of service (QoS) flow associated with the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

[0210] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a base station to: receive sensing service data from a plane function for a sensing service; and map a first quality of service (QoS) flow associated with the sensing service data to a sensing data radio bearer. For example, the first QoS flow may be included in a packet data unit (PDU) session for the sensing service.

[0211] FIG. 18 illustrates a method for a first device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0212] Referring to FIG. 18, in step S1810, the first device may receive an RRC (radio resource control) message including configuration information related to a data radio bearer from a base station. In step S1820, the first device may receive sensing service data from the base station. For example, a QoS flow related to the sensing service data may be mapped to a sensing data radio bearer. For example, the QoS flow related to the sensing service data may be included in a PDU (packet data unit) session for the sensing service.

[0213] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (102) of the first device (100) can control the transceiver (106) to receive an RRC (radio resource control) message including configuration information related to a data radio bearer from a base station. Then, the processor (102) of the first device (100) can control the transceiver (106) to receive sensing service data from the base station. For example, a QoS flow related to the sensing service data can be mapped to a sensing data radio bearer. For example, the QoS flow related to the sensing service data can be included in a PDU (packet data unit) session for the sensing service.

[0214] According to one embodiment of the present disclosure, a first device configured to perform wireless communication may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: receive, from a base station, a radio resource control (RRC) message including configuration information related to a data radio bearer; and receive, from the base station, sensing service data. For example, a quality of service (QoS) flow related to the sensing service data may be mapped to a sensing data radio bearer. For example, the QoS flow related to the sensing service data may be included in a packet data unit (PDU) session for a sensing service.

[0215] According to one embodiment of the present disclosure, a processing device configured to control a first device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the first device to: receive, from a base station, a radio resource control (RRC) message including configuration information related to a data radio bearer; and receive, from the base station, sensing service data. For example, a quality of service (QoS) flow related to the sensing service data may be mapped to a sensing data radio bearer. For example, the QoS flow related to the sensing service data may be included in a packet data unit (PDU) session for a sensing service.

[0216] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a first device to: receive, from a base station, an RRC (radio resource control) message including configuration information related to a data radio bearer; and receive, from the base station, sensing service data. For example, a quality of service (QoS) flow related to the sensing service data may be mapped to a sensing data radio bearer. For example, the QoS flow related to the sensing service data may be included in a packet data unit (PDU) session for a sensing service.

[0217] According to various embodiments of the present disclosure, a separate QoS model for sensing services can be defined in a 6G system. Specifically, for example, QoS flows related to sensing services (or DRBs related to sensing services, or PDU sessions related to sensing services) can be managed independently from QoS flows related to communication services (or DRBs related to communication services, or PDU sessions related to communication services). In this case, for example, resources on a DRB basis can be independently allocated and scheduled for each sensing service and each communication service, thereby preventing in advance the problem of large-capacity sensing traffic affecting the delay of communication traffic. Alternatively, for example, a scheduler at a base station can independently process DRBs for sensing services and DRBs for communication services according to separate priorities and QoS requirements, thereby improving scheduling efficiency. Alternatively, for example, by separately managing sensing services and communication services at the QoS flow and / or PDU session level, it is possible to stably process large-capacity transmission of sensing traffic while ensuring the quality of communication services.

[0218] The various embodiments of the present disclosure may be combined with each other.

[0219] Below, a description is given of devices to which various embodiments of the present disclosure can be applied.

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

[0221] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0222] FIG. 19 illustrates a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 19 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0223] Referring to FIG. 19, a communication system (1) to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., an Advanced Air Mobility (AAM)). The XR device may include an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, a base station and a network may also be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0224] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, 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 devices (100a to 100f) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). 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 Machine Type Communication, 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 devices (100a to 100f) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0225] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (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, etc. 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 / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0226] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to 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 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 disclosure.

[0227] FIG. 20 illustrates a wireless device according to an embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0228] Referring to FIG. 20, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 19.

[0229] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). Furthermore, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The 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 disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0230] A second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0231] Hereinafter, the 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 PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. 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 functions, procedures, proposals and / or methods 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.

[0232] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, 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), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0233] 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 ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0234] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected 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, or wireless signals 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, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can 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 user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0235] FIG. 21 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure. The embodiment of FIG. 21 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0236] Referring to FIG. 21, the signal processing circuit (1000) may include a scrambler (1010), a modulator (1020), a layer mapper (1030), a precoder (1040), a resource mapper (1050), and a signal generator (1060). Although not limited thereto, the operations / functions of FIG. 21 may be performed in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 20. The hardware elements of FIG. 21 may be implemented in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 20. For example, blocks 1010 to 1060 may be implemented in the processor (102, 202) of FIG. 20. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 20, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 20.

[0237] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 21. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transport block (e.g., an UL-SCH transport block, a DL-SCH transport block). The wireless signal may be transmitted through various physical channels (e.g., a PUSCH or a PDSCH).

[0238] Specifically, the codeword can be converted into a bit sequence scrambled by a scrambler (1010). The scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of the wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by a precoding matrix W of N*M. Here, N is the number of antenna ports, and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on complex modulation symbols. In addition, the precoder (1040) can perform precoding without performing transform precoding.

[0239] The resource mapper (1050) can map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources can include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. The signal generator (1060) generates a wireless signal from the mapped modulation symbols, and the generated wireless signal can be transmitted to another device through each antenna. To this end, the signal generator (1060) can include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0240] The signal processing process for receiving signals in a wireless device can be configured in reverse order of the signal processing process (1010 to 1060) of FIG. 21. For example, a wireless device (e.g., 100, 200 of FIG. 20) can receive wireless signals from the outside through an antenna port / transceiver. The received wireless signals can be converted into baseband signals through a signal restorer. For this purpose, the signal restorer can include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Thereafter, the baseband signal can be restored to a codeword through a resource demapper process, a postcoding process, a demodulation process, and a descrambling process. The codewords can be restored to the original information blocks through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.

[0241] Figure 22 illustrates a wireless device according to an embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use case / service (see Figure 19). The embodiment of Figure 22 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0242] Referring to FIG. 22, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 20 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 20. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 20. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0243] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 19, 100a), a vehicle (Fig. 19, 100b-1, 100b-2), an XR device (Fig. 19, 100c), a portable device (Fig. 19, 100d), a home appliance (Fig. 19, 100e), an IoT device (Fig. 19, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 19, 400), a base station (Fig. 19, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0244] In FIG. 22, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be interconnected entirely via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of a random access memory (RAM), a dynamic RAM (DRAM), a read only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0245] Below, the implementation example of Fig. 22 is described in more detail with reference to the drawings.

[0246] FIG. 23 illustrates a mobile device according to an embodiment of the present disclosure. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smartwatch, smartglasses), or a portable computer (e.g., a laptop, etc.). The mobile device may be referred to as a Mobile Station (MS), a User Terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT). The embodiment of FIG. 23 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0247] Referring to FIG. 23, the portable device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140a), an interface unit (140b), and an input / output unit (140c). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 of FIG. 22, respectively.

[0248] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with other wireless devices and base stations. The control unit (120) can control components of the mobile device (100) to perform various operations. The control unit (120) can include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / codes / commands required for operating the mobile device (100). In addition, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the mobile device (100) and can include a wired / wireless charging circuit, a battery, etc. The interface unit (140b) can support connection between the mobile device (100) and other external devices. The interface unit (140b) can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can input or output video information / signals, audio information / signals, data, and / or information input from a user. The input / output unit (140c) may include a camera, a microphone, a user input unit, a display unit (140d), a speaker, and / or a haptic module.

[0249] For example, in the case of data communication, the input / output unit (140c) obtains information / signals (e.g., touch, text, voice, image, video) input by the user, and the obtained information / signals can be stored in the memory unit (130). The communication unit (110) converts the information / signals stored in the memory into wireless signals, and can directly transmit the converted wireless signals to other wireless devices or to a base station. In addition, the communication unit (110) can receive wireless signals from other wireless devices or base stations, and then restore the received wireless signals to the original information / signals. The restored information / signals can be stored in the memory unit (130) and then output in various forms (e.g., text, voice, image, video, haptic) through the input / output unit (140c).

[0250] 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 and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In the method, A step of the base station receiving sensing service data from a flat function for sensing service; and A step of mapping a first QoS (quality of service) flow related to the sensing service data to a sensing data radio bearer; including; A method wherein the first QoS flow is included in a PDU (packet data unit) session for the sensing service.

2. In paragraph 1, A method wherein the first QoS flow associated with the sensing service data is managed independently from the second QoS flow associated with the communication service data.

3. In paragraph 1, A method in which the sensing service data is mapped to the first QoS flow based on the first QoS flow being a dedicated QoS flow for the sensing service.

4. In paragraph 1, A method wherein a PDU session for the sensing service including the first QoS flow related to the sensing service data is different from a PDU session including the second QoS flow related to the communication service data.

5. In paragraph 1, A method wherein the sensing data radio bearer mapped to the first QoS flow associated with the sensing service data is different from the data radio bearer mapped to the second QoS flow associated with the communication service data.

6. In paragraph 1, A method in which a plurality of QoS flows including the first QoS flow are mapped to the sensing data radio bearer based on the plurality of QoS flows being related to the sensing service.

7. In paragraph 1, Further comprising: a step of receiving configuration information for mapping between a QoS flow related to sensing and a data radio bearer related to sensing from a flat function for the sensing service; A method wherein, based on the above configuration information, the first QoS flow related to the sensing service data is mapped to the sensing data radio bearer.

8. In paragraph 7, A method in which the above configuration information includes at least one of a sensing QFI (QoS Flow ID) mapped to each sensing service, a QoS requirement to each sensing service, a sensing data radio bearer for the sensing service, a sensing QFI mapped to each sensing data radio bearer, RLC (radio link control) configuration information for sensing service data, or PDCP (packet data convergence protocol) configuration information for sensing service data.

9. In paragraph 1, A method wherein QoS flows related to a communication service are restricted from being included in a PDU session for the sensing service.

10. In paragraph 1, A method in which QoS flows related to communication services are restricted from being mapped to the sensing data radio bearer.

11. In paragraph 1, A method in which the mapping between the first QoS flow associated with the sensing service data and the sensing data radio bearer is supported by a service data adaptation protocol (SDAP) entity.

12. In paragraph 1, A method in which an SDAP entity is established for a PDU session for the above sensing service.

13. In paragraph 12, A method wherein the above SDAP entity is set based on at least one of a sensing service ID, a sensing service QFI, a sensing priority, a sensing service data flow ID, or a target sensing area.

14. At the base station, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said base station: From the flat function for sensing service, receive sensing service data; and Map the first QoS (quality of service) flow related to the above sensing service data to the sensing data radio bearer, The base station, wherein the first QoS flow is included in a PDU (packet data unit) session for the sensing service.

15. In a processing device set to control a base station, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said base station: From the flat function for sensing service, receive sensing service data; and Map the first QoS (quality of service) flow related to the above sensing service data to the sensing data radio bearer, A processing device wherein the first QoS flow is included in a PDU (packet data unit) session for the sensing service.

16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the base station to: From the flat function for sensing service, receive sensing service data; and Map the first QoS (quality of service) flow related to the above sensing service data to the sensing data radio bearer, A non-transitory computer-readable storage medium, wherein the first QoS flow is included in a packet data unit (PDU) session for the sensing service.

17. In the method, A step in which a first device receives, from a base station, an RRC (radio resource control) message including configuration information related to a data radio bearer; and A step of receiving sensing service data from the base station; including: The QoS flow associated with the above sensing service data is mapped to the sensing data radio bearer, and A method wherein the QoS flow related to the above sensing service data is included in a PDU (packet data unit) session for the sensing service.

18. In the first device, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first device causes: Receive, from a base station, an RRC (radio resource control) message containing configuration information related to a data radio bearer; and Receive sensing service data from the above base station, The QoS flow associated with the above sensing service data is mapped to the sensing data radio bearer, and A first device, wherein the QoS flow related to the sensing service data is included in a packet data unit (PDU) session for the sensing service.

19. In a processing device set to control the first device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first device causes: Receive, from a base station, an RRC (radio resource control) message containing configuration information related to a data radio bearer; and Receive sensing service data from the above base station, The QoS flow associated with the above sensing service data is mapped to the sensing data radio bearer, and A processing device in which the QoS flow related to the above sensing service data is included in a PDU (packet data unit) session for the sensing service.

20. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the first device to: Receive, from a base station, an RRC (radio resource control) message containing configuration information related to a data radio bearer; and Receive sensing service data from the above base station, The QoS flow associated with the above sensing service data is mapped to the sensing data radio bearer, and A non-transitory computer-readable storage medium, wherein the QoS flow related to the sensing service data is included in a packet data unit (PDU) session for the sensing service.

Images