Provision of prediction information

Abstract

The present disclosure provides a method related to provision of prediction information. This network node performs a step of transmitting configuration information related to a sensing service. The network node performs a step of receiving, by the network node, information related to a prediction sensing request. The network node performs a step of transmitting, by the network node, prediction information. The prediction information includes (i) prediction information related to a specific area and / or (ii) prediction information related to a specific time.

Description

Providing predictive information

[0001] This specification relates to the provision of predictive information.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communication. Many methods have been proposed to achieve LTE goals, such as reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. As high-level requirements, 3GPP LTE demands reduced cost per bit, improved service availability, flexible use of frequency bands, a simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio communication sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

[0004] NR targets a single technical framework that covers all deployment scenarios, usage scenarios, and requirements, including eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type-Communications), and URLLC (Ultra-Reliable and Low Latency Communications). NR must be forward compatible by nature.

[0005] Cellular networks have been used solely for data transmission. For objects that do not possess communication modules (environments, people, animals, etc.), sensing technologies have so far been limited to radar, lidar, RF, cameras, etc.

[0006] In SA1, sensing use cases based on 3GPP signals as well as non-3GPP signals, and some service and performance requirements to satisfy them, have been standardized.

[0007] However, the definition of the functional structure, procedures, and detailed protocols (stage 2 / stage 3) is at a stage where the study has not yet begun. The technology for implementing the actual service has not been defined.

[0008] Therefore, it is necessary to discuss system functions and procedures that can effectively control sensing and communication functions targeting 5G evolution / 6G systems.

[0009] In one embodiment, a method for providing prediction information is provided. The method comprises: transmitting configuration information related to a sensing service by a network node; receiving information related to a prediction sensing request by the network node; and transmitting prediction information by the network node, wherein the prediction information includes (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time.

[0010] In another aspect, a device for implementing the above method is provided.

[0011] The present disclosure may have various effects.

[0012] According to some embodiments of the present disclosure, the device can efficiently provide prediction information.

[0013] According to some embodiments of the present disclosure, a network node can efficiently receive prediction information.

[0014] According to some embodiments of the present disclosure, a device or network node can efficiently enable or disable the provision of predictive information.

[0015] For example, according to the present disclosure, the functionality of a network node (e.g., AF) can be enhanced by targeting a 5G evolution / 6G system in a zero-touch configuration / operation environment where network automation is extended. For example, by enabling or disabling the provision of sensing-related predictive information used in the system, the relevant information can be efficiently transmitted to a third party. Thus, the information can be effectively utilized in AI services.

[0016] According to some embodiments of the present disclosure, a wireless communication system can efficiently provide prediction information.

[0017] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0018] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0019] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0020] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0021] FIG. 4 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0022] FIGS. 5 and FIGS. 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0023] Figures 7 and 8 specify a procedure for establishing a PDU session associated with a single connection type at a given time.

[0024] Figure 9 shows an example of a method for controlling the provision of prediction information.

[0025] Figure 10 shows an example of a method for controlling the provision of prediction information.

[0026] FIG. 11 illustrates an example of a scenario according to some embodiments of the present disclosure.

[0027] FIG. 12 illustrates an example of a procedure for providing predictive information and enabling the provision of predictive information according to some embodiments of the present disclosure.

[0028] FIG. 13 illustrates examples of a procedure for providing predictive information and disabling predictive information provision according to some embodiments of the present disclosure.

[0029] FIG. 14 illustrates an example of a service flow according to some embodiments of the present disclosure.

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

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

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

[0033] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0034] A slash ( / ) or a comma used in this specification 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."

[0035] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0036] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

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

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

[0039] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be applied to various fields where wireless communication and / or connectivity between devices (e.g., 5G) is required.

[0040] The present specification will be described in more detail below with reference to the drawings. In the following drawings and / or description, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, and / or function blocks unless otherwise indicated.

[0041] In this specification, embodiments are described based on the structure, procedures, and messages of a 5G mobile communication system, but this is not limited thereto and can be extended to an evolved form of a 6G mobile communication system. For example, although described as a 5G-based message, it may be defined as an existing message, a new message, or a parameter.

[0042] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

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

[0044] The three main requirement categories for 5G are (1) enhanced Mobile BroadBand (eMBB) category, (2) massive Machine Type Communication (mMTC) category, and (3) Ultra-Reliable and Low Latency Communications (URLLC) category.

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

[0046] The base station (200) and the network (300) can be implemented as wireless devices, and a specific wireless device can operate as a base station / network node in relation to another wireless device.

[0047] Wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), eXtended Reality (XR) devices (100c), portable devices (100d), home appliances (100e), Internet-Of-Things (IoT) devices (100f), and Artificial Intelligence (AI) devices / servers (400). For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices) and HUDs (Head-Up Displays) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0048] In this specification, wireless devices (100a to 100f) may be referred to as User Equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a PDA (Personal Digital Assistant), a PMP (Portable Multimedia Player), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a 5G service-related device, or a device related to the Fourth Industrial Revolution.

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

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

[0051] NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0052] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges may change. For example, the two types of frequency ranges (FR1, FR2) may be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 may mean "sub 6GHz range" and FR2 may mean "above 6GHz range" and may be referred to as Millimeter Wave (mmW).

[0053] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

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

[0055] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

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

[0057] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

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

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

[0060] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or generally, the memory (104) may be placed outside the processing chip (101).

[0061] The processor (102) can control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and transmit a wireless signal containing the first information / signal through the transceiver (106). The processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and process the second information / signal to store the obtained information in the memory (104).

[0062] Memory (104) may be connected to the processor (102) so as to be operable. Memory (104) may store various types of information and / or instructions. Memory (104) may store firmware and / or software code (105) that implements code, instructions, and / or a set of instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may implement instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

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

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

[0065] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or generally, the memory (204) may be placed outside the processing chip (201).

[0066] The processor (202) can control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and transmit a wireless signal containing the third information / signal through the transceiver (206). The processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and process the fourth information / signal to store the obtained information in the memory (204).

[0067] Memory (204) may be connected to the processor (202) so as to be operable. Memory (204) may store various types of information and / or instructions. Memory (204) may store firmware and / or software code (205) that implements code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

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

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

[0070] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors. One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), Erasable Programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, cache memory, computer read storage media, and / or combinations thereof.One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

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

[0072] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0073] 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 received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) can convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters. For example, one or more transceivers (106, 206) can up-convert an OFDM baseband signal into an OFDM signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) can receive an OFDM signal at a carrier frequency and down-convert the OFDM signal into an OFDM baseband signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

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

[0075] In an implementation of the present specification, the UE may operate as a transmitting device in the uplink and as a receiving device in the downlink. In an implementation of the present specification, the base station may operate as a receiving device in the UL and as a transmitting device in the DL. For technical convenience, it is generally assumed that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released to the first wireless device (100) may be configured to perform UE operations according to an implementation of the present specification or to control a transceiver (106) to perform UE operations according to an implementation of the present specification. A processor (202) connected to, mounted on, or released to the second wireless device (200) may be configured to perform base station operations according to an implementation of the present specification or to control a transceiver (206) to perform base station operations according to an implementation of the present specification.

[0076] In this specification, the base station may be referred to as Node B, eNode B, or gNB.

[0077] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

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

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

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

[0081] Memory (104) is coupled to the processor (102) so as to be operable and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the implementation is implemented in software, the technology described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed herein. Modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or outside the processor (102), in which case it may be communicatively coupled to the processor (102) through various methods known in the technology.

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

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

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

[0085] A SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile device such as a mobile phone or computer. Additionally, contact information can be stored on many SIM cards.

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

[0087] FIG. 4 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0088] The 5G system (5GS) structure consists of the following network functions (NF).

[0089] - AUSF (Authentication Server Function)

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

[0091] - DN (Data Network), for example, operator services, internet access, or third-party services

[0092] - USDF (Unstructured Data Storage Function)

[0093] - NEF (Network Exposure Function)

[0094] - I-NEF (Intermediate NEF)

[0095] - NRF (Network Repository Function)

[0096] - NSSF (Network Slice Selection Function)

[0097] - PCF (Policy Control Function)

[0098] - SMF (Session Management Function)

[0099] - UDM (Unified Data Management)

[0100] - UDR (Unified Data Repository)

[0101] - UPF (User Plane Function)

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

[0103] - AF (Application Function)

[0104] - UE (User Equipment)

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

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

[0107] - NWDAF (Network Data Analytics Function)

[0108] - CHF (CHarging Function)

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

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

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

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

[0113] Figure 4 shows the 5G system structure in a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0114] In Figure 4, UDSF, NEF, and NRF are not described for clarity of the point-to-point diagram. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

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

[0116] The 5G system structure includes the following reference points.

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

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

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

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

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

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

[0123] The following reference points show the interactions that exist between the NF services of NF.

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

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

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

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

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

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

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

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

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

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

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

[0135] In some cases, two NFs may need to be connected to each other to service the UE.

[0136] The registration procedure is described. Refer to Section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0137] FIGS. 5 and FIGS. 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0138] The UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types.

[0139] - Initial registration for the 5GS; or

[0140] - Mobility registration update; or

[0141] - Periodic registration update; or

[0142] - Emergency registration

[0143] The general registration procedure of Figures 5 and 6 applies to all registration procedures described above, but the periodic registration update does not need to include all parameters used in other registration procedures.

[0144] The general registration procedure of Figures 5 and 6 is used when a UE is registered to a 3GPP connection when it is already registered to a non-3GPP connection, and vice versa. To register a UE to a 3GPP connection when it is already registered to a non-3GPP connection scenario, an AMF change may be required.

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

[0146] (1) Step 1: The UE sends a Registration Request message to the (R)AN. The Registration Request message corresponds to the AN message.

[0147] A registration request message may include AN parameters. For NG-RAN, AN parameters include, for example, 5G-S-TMSI (5G SAE temporary mobile subscriber identity) or GUAMI (globally unique AMF ID), a selected PLMN (public land mobile network) ID (or PLMN ID and NID (network identifier)), and requested NSSAI (Requested network slice selection assistance information). AN parameters also include an establishment cause. The establishment cause provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter.

[0148] The registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in the RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process because the UE moves, or the UE wants to update capabilities or protocol parameters, or requests a change to the set of network slices allowed for the UE to use), or a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process due to the expiration of the periodic registration update timer), or an urgent registration (i.e., the UE is in the restricted service state).

[0149] When a UE performs initial registration, the UE specifies the UE ID in the registration request message as follows, listed in order of decreasing priority.

[0150] i) If the UE has a valid EPS (evolved packet system) GUTI (globally unique temporary identifier), the 5G-GUTI mapped from the EPS GUTI;

[0151] ii) Native 5G-GUTI assigned by the PLMN for which the UE is attempting to register (if available);

[0152] iii) Native 5G-GUTI assigned by a PLMN equivalent to the PLMN for which the UE is attempting to register;

[0153] iv) Native 5G-GUTI assigned by other PLMNs (if available);

[0154] v) Otherwise, the UE includes SUCI (subscriber concealed identifier) ​​in the registration request message.

[0155] If the UE performing the initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also marks the native 5G-GUTI as an additional GUTI. If one or more native 5G-GUTIs are available, the UE selects the 5G-GUTIs from items (ii)-(iv) in the list above in decreasing order of priority.

[0156] When the UE performs initial registration with native 5G-GUTI, the UE displays relevant GUAMI information in AN parameters. When the UE performs initial registration with SUCI, the UE does not display GUAMI information in AN parameters.

[0157] In the case of emergency registration, SUCI is included if the UE does not have a valid 5G-GUTI, and PEI is included if the UE does not have a SUPI (subscriber permanent identifier) ​​and does not have a valid 5G-GUTI. In other cases, a 5G-GUTI is included, which indicates the last serving AMF.

[0158] The registration request message may also include security parameters, PDU session status, etc. Security parameters are used for authentication and integrity protection. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the PDU session status indicates the established PDU session of the current PLMN in the UE.

[0159] (2) Step 2: (R)AN selects AMF.

[0160] If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not represent a valid AMF, (R)AN selects an AMF based on (R)AT and the requested NSSAI, where available.

[0161] If the UE is in the CM-CONNECTED state, (R)AN can forward a registration request message to the AMF based on the UE's N2 connection.

[0162] If (R)AN cannot select a suitable AMF, (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in (R)AN.

[0163] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0164] The registration request message may include all information and / or part of the information contained in the registration request message received from the UE described in Step 1.

[0165] The registration request message may include N2 parameters. When NG-RAN is used, the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information and cell ID associated with the cell where the UE is camping, and a UE context request indicating that a UE context including security information in NG-RAN must be established. When NG-RAN is used, the N2 parameters also include the cause for establishment.

[0166] If the registration type indicated by the UE is a periodic registration update, steps 4-19 described below may be omitted.

[0167] (4) Step 4: If the UE's 5G-GUTI is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may call the Namf_Communication_UEContextTransfer service operation on the previous AMF, including the full registration request NAS (non-access stratum) message to request the UE's SUPI and UE context.

[0168] (5) Step 5: The previous AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call, including the UE's SUPI and UE context.

[0169] (6) Step 6: If SUCI is not provided by the UE or is not retrieved from the previous AMF, the new AMF may initiate the identity request procedure by sending an identity request message to the UE to request SUCI.

[0170] (7) Step 7: The UE may respond with an Identity Response message containing SUCI. The UE derives SUCI using the provided public key of the home PLMN (HPLMN).

[0171] (8) Step 8: The new AMF may decide to call AUSF to initiate UE authentication. In this case, the new AMF selects AUSF based on SUPI or SUCI.

[0172] (9) Step 9: Authentication / security may be established by UE, new AMF, AUSF and / or UDM.

[0173] (10) Step 10: If the AMF is changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the previous AMF that UE registration to the new AMF is complete. If the authentication / security procedure fails, registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to the previous AMF with a reject indication reason code. The previous AMF may continue as if no UE context passing service operation was received.

[0174] (11) Step 11: If the PEI is not provided by the UE or has not been retrieved from the previous AMF, the new AMF may initiate an Identity Request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted in encryption, except in cases where the UE cannot perform emergency registration and be authenticated.

[0175] (12) Step 12: Optionally, the new AMF can call the N5g-eir_EquipmentIdentityCheck_Get service operation to start ME ID checking.

[0176] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is explained.

[0177] (13) Step 13: If you perform Step 14 below, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0178] (14) Step 14: New AMFs can be registered with UDM.

[0179] (15) Step 15: The new AMF can select PCF.

[0180] (16) Step 16: The new AMF may optionally establish / modify AM policy associations.

[0181] (17) Step 17: The new AMF can send update / release SM context messages (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0182] (18) Step 18: If the new AMF and the previous AMF are in the same PLMN, the new AMF can send a request to modify the UE context to N3IWF / TNGF / W-AGF.

[0183] (19) Step 19: N3IWF / TNGF / W-AGF can send a UE context modification response to the new AMF.

[0184] (20) Step 20: After the new AMF receives a response message from N3IWF / TNGF / W-AGF in Step 19, the new AMF can register with UDM.

[0185] (21) Step 21: The new AMF sends a Registration Accept message to the UE.

[0186] The new AMF sends a registration acceptance message to the UE indicating that the registration request has been accepted. If the new AMF assigns a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in the RM-REGISTERED state via another connection on the same PLMN, the UE uses the 5G-GUTI received in the registration acceptance message for both registrations. If the registration acceptance message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration as well. If the new AMF assigns a new registration area, it transmits the registration area to the UE via the registration acceptance message. If the registration acceptance message does not contain a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included when mobility restrictions apply to the UE and the registration type is not an urgent registration. The new AMF indicates the PDU session established for the UE in the PDU session state. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU session state. When a UE connects to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with the PDU session of the current PLMN that are not indicated as established in the received PDU session state. If PDU session state information is present in the registration acceptance message, the new AMF instructs the UE on the PDU session state.

[0187] The Allowed NSSAI provided in the registration acceptance message is valid in the registration area and applies to all PLMNs having a tracking area included in the registration area. The Mapping of Allowed NSSAI is to map the HPLMN S-NSSAI to each S-NSSAI of the Allowed NSSAI. The Mapping of Configured NSSAI is to map the HPLMN S-NSSAI to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0188] Additionally, the new AMF optionally performs UE policy association establishment.

[0189] (22) Step 22: If the UE succeeds in updating itself, it can send a Registration Complete message to the new AMF.

[0190] The UE can send a registration completion message to the new AMF to check if a new 5G-GUTI has been assigned.

[0191] (23) Step 23: In the case of registration via a 3GPP connection, if the new AMF does not release the signaling connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. In the case of registration via a non-3GPP connection, if the UE is in a CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

[0192] (24) Step 24: AMF can perform information updates on UDM.

[0193] (25) Step 25: The UE can execute network slice-specific authentication and authorization (NSSAA) procedures.

[0194] <PDU 세션 수립 절차>

[0195] The procedure for establishing a PDU session is described. Refer to Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0196] FIGS. 7 and FIGS. 8 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0197] PDU session establishment may fall under the following:

[0198] - Procedure for establishing a PDU session initiated by the UE

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

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

[0201] - Procedure for establishing a PDU session triggered by the network

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

[0203] Figures 7 and 8 specify a procedure for establishing a PDU session associated with a single connection type at a given time.

[0204] In the procedure shown in Figures 7 and 8, it is assumed that the AMF has already retrieved user subscription data from the UDM, unless the UE is urgently registered, since the UE is already registered with the AMF.

[0205] First, the procedure of Fig. 7 will be explained.

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

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

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

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

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

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

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

[0213] If the request type indicates an "existing PDU session" that refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and the serving PLMN S-NSSAI of the PDU session exists in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases.

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

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

[0216] Otherwise, the AMF rejects the request to establish a PDU session with an appropriate reason for rejection.

[0217] AMF rejects requests from urgently registered UEs where the request type does not indicate "Urgent Request" or "Existing Urgent PDU Session".

[0218] (3) Step 3: If the AMF is not associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "initial request"), the AMF calls the Create SMContext request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "existing PDU session"), the AMF calls the Update SMContext request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

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

[0220] The AMF ID is the UE's GUAMI and uniquely identifies the AMF serving the UE. The AMF transmits the PDU Session ID along with an N1 SM container containing the PDU session establishment request message received from the UE. The generic public subscription identifier (GPSI) is included if available in the AMF.

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

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

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

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

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

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

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

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

[0229] (7b) Step 7b: SMF can establish an SM policy association with PCF and obtain a basic PCC rule for the PDU session by performing the SM policy association establishment procedure.

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

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

[0232] (10) Step 10: If the request type indicates an “initial request,” the SMF may initiate an N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate an N4 Session Modification procedure with the selected UPF.

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

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

[0235] The N1N2 message delivery message may include N2 SM information. The N2 SM information carries the following information that the AMF will transmit to the (R)AN.

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

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

[0238] - PDU Session ID: Indicates to the UE the association between the RAN resource and the PDU session for the UE;

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

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

[0241] - Maximum data rate for UE integrity protection received in PDU session establishment request message: When integrity protection is indicated as "Preferred" or "Required" in user plane security enforcement information

[0242] - RSN (redundancy sequence number) parameter

[0243] The N1N2 message delivery message may include an N1 SM container. The N1 SM container includes a PDU session establishment acceptance message that the AMF will provide to the UE. The PDU session establishment acceptance message includes an S-NSSAI from an allowed NSASI. In the case of an LBO roaming scenario, the PDU session establishment acceptance message includes an S-NSSAI from an allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI for the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0244] If necessary for QoS flows related to QoS rules and QoS profiles, multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment acceptance message and N2 SM information within the N1 SM container.

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

[0246] (12) Step 12: The AMF sends a NAS message containing a PDU session ID destined for the UE, a message accepting the establishment of a PDU session, and N2 SM information received from the SMF to (R)AN within the N2 PDU session request message.

[0247] (13) Step 13: (R)AN can perform AN-specific signal exchanges with the UE regarding information received from the SMF. For example, in the case of NG-RAN, it can perform RRC connection reconfiguration with the UE to set up necessary NG-RAN resources in relation to the QoS rules for the PDU session request received by the UE in Step 12.

[0248] (R)AN forwards the NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signal exchange with the UE includes the addition of (R)AN resources related to the received N2 command.

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

[0250] The procedure of Fig. 8 following the procedure of Fig. 7 is described.

[0251] (14) Step 14: (R)AN sends an N2 PDU session response message to AMF. The N2 PDU session response message may include a PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs, user plane enforcement policy notifications), etc.

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

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

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

[0255] After this step, UPF can deliver the DL packet that may have been buffered for this PDU session to the UE.

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

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

[0258] After this step, AMF delivers the relevant events subscribed to by SMF.

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

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

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

[0262] (21) Step 21: If the establishment of a PDU session fails after Step 4, and the SMF no longer processes the UE's PDU session, the SMF may unsubscribe from the modification of the session management subscription data.

[0263] Meanwhile, cellular networks have been used solely for data transmission. For objects that do not have communication modules (environments, people, animals, etc.), technologies for sensing objects have so far been limited to radar, Lidar, RF, cameras, etc.

[0264] In SA1, sensing use cases based on 3GPP signals as well as non-3GPP signals, and some service and performance requirements to satisfy them, have been standardized.

[0265] However, the definition of the functional structure, procedures, and detailed protocols (stage 2 / stage 3) is at a stage where the study has not yet begun. The technology for implementing the actual service has not been defined.

[0266] Therefore, it is necessary to discuss system functions and procedures that can effectively control sensing and communication functions targeting 5G evolution / 6G systems.

[0267] Hereinafter, a method and apparatus for enabling the provision of predictive information according to some embodiments of the present disclosure will be described with reference to the following drawings.

[0268] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings. Hereinafter, a wireless device may be referred to as a User Equipment (UE).

[0269] Figure 9 shows an example of a method for controlling the provision of prediction information.

[0270] In particular, Fig. 9 shows an example of a method performed by a network node in a wireless communication system.

[0271] In step S901, the network node may perform the step of transmitting configuration information related to the sensing service.

[0272] For example, the configuration information related to the above sensing service may include information related to the area of ​​interest, information related to the sensing time, and / or information related to the sensing period.

[0273] For example, the network node may be (i) an Application Function node (AF), (ii) an Edge Server, (iii) a Central Server, or (iv) a Sensing Function node (SF). For example, the network node may be a Sensing Function node (SF).

[0274] For example, setting information related to the above sensing service can be transmitted to the first device.

[0275] The first device may be a wireless device, a user device (User Equipment, UE), an autonomous mobile robot (AMR), a drone, a robot, a base station, or a roadside unit (RSU).

[0276] For example, the first device may be connected to the network node. For example, the first device may register with the network and / or create a PDU session. For example, in the step of registering with the network and / or creating a PDU session, configuration information related to the sensing service may be transmitted.

[0277] In step S902, the network node may perform the step of receiving information related to the prediction sensing request.

[0278] For example, information related to a predictive sensing request may include a predictive sensing enable indicator or a predictive sensing disable indicator.

[0279] For example, based on a received prediction sensing enable indicator or prediction sensing disable indicator, the network node can enable or disable the generation of prediction information.

[0280] For example, information related to a predictive sensing request may include (i) collected sensing information, (ii) time information related to said collected sensing information, and / or (iii) location information related to said collected sensing information.

[0281] For example, information related to the above-mentioned predictive sensing request may be received from the first device. For example, based on configuration information related to the above-mentioned sensing service, the first device may perform a sensing measurement. For example, the first device may sense a target person / object, etc., and collect sensing measurement data.

[0282] For example, information related to the above prediction sensing request may be transmitted to a network node (e.g., AF or server) via a RAN node, AMF, SF, and / or NEF.

[0283] In step S903, the network node can perform the step of transmitting prediction information.

[0284] The above forecast information may include (i) forecast information related to a specific region and / or (ii) forecast information related to a specific time.

[0285] For example, the prediction information may include (i) information related to the number of prediction targets, (ii) information related to a prediction zone associated with the prediction targets, and / or (iii) information related to the prediction time at which the prediction targets will be located in the prediction zone.

[0286] For example, the above prediction information may include (i) whether the prediction target is one or multiple, (ii) information about the area associated with the prediction target (e.g., area X), and (iii) information about whether the prediction target is currently in the area or will arrive after a certain amount of time (e.g., y seconds).

[0287] For example, a network node can directly generate prediction information. For example, based on information related to a prediction sensing request, a network node can directly generate prediction information.

[0288] Alternatively, a network node can obtain prediction information generated by another network node (e.g., SF or NWDAF). For example, a network node transmits information related to a prediction sensing request to another network node. The other network node can generate prediction information based on the information related to the prediction sensing request. The network node can receive prediction information generated by the other network node.

[0289] For example, the network node may further perform the step of transmitting configuration information related to the updated sensing service based on the above prediction information. For example, the step of transmitting configuration information related to the updated sensing service may be performed optionally.

[0290] For example, based on predictive information, a network node may generate configuration information related to an updated sensing service for the purpose of providing better service. For example, the configuration information related to the updated sensing service may include information related to a changed region of interest, a changed sensing time, and / or a changed sensing cycle.

[0291] Figure 10 shows an example of a method for controlling the provision of prediction information.

[0292] In particular, FIG. 10 shows an example of a method performed by a first device in a wireless communication system.

[0293] For example, the first device may include a wireless device, a user device (User Equipment, UE), an autonomous mobile robot (AMR), a drone, a robot, a base station, a roadside unit (RSU), etc.

[0294] In step S1001, the first device may perform the step of receiving configuration information related to the sensing service.

[0295] For example, the configuration information related to the above sensing service may include information related to the area of ​​interest, information related to the sensing time, and / or information related to the sensing period.

[0296] For example, the above network node may be (i) an Application Function node (AF), (ii) an Edge Server, (iii) a Central Server, or (iv) a Sensing Function node (SF).

[0297] For example, setting information related to the above sensing service can be transmitted to the first device.

[0298] For example, the first device may be connected to the network node. For example, the first device may register with the network and / or create a PDU session. For example, in the network registration and / or PDU session creation step, configuration information related to the sensing service may be transmitted.

[0299] In step S1002, the first device may perform the step of performing sensing and collecting data.

[0300] In step S1003, the first device may perform the step of transmitting information related to a prediction sensing request.

[0301] For example, information related to the above prediction sensing request may include a prediction sensing enable indicator or a prediction sensing disable indicator.

[0302] For example, based on a received prediction sensing enable indicator or prediction sensing disable indicator, the network node can enable or disable the generation of prediction information.

[0303] For example, information related to the above prediction sensing request can be transmitted to a network node.

[0304] For example, information related to a predictive sensing request may include (i) collected sensing information, (ii) time information related to said collected sensing information, and / or (iii) location information related to said collected sensing information.

[0305] For example, information related to the above-mentioned predictive sensing request may be received from the first device. For example, based on configuration information related to the above-mentioned sensing service, the first device may perform a sensing measurement. For example, the first device may sense a target person / object, etc., and collect sensing measurement data.

[0306] For example, information related to the above prediction sensing request may be transmitted to network nodes (e.g., AF or server) through RAN nodes, AMF, SF (Sensing Function), and / or NEF.

[0307] In step S1004, the first device may perform the step of receiving prediction information.

[0308] For example, the above prediction information may include (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time.

[0309] For example, the prediction information may include (i) information related to the number of prediction targets, (ii) information related to a prediction zone associated with the prediction targets, and / or (iii) information related to the prediction time at which the prediction targets will be located in the prediction zone.

[0310] For example, the above prediction information may include (i) whether the prediction target is one or multiple, (ii) information about the area associated with the prediction target (e.g., area X), and (iii) information about whether the prediction target is currently in the area or will arrive after a certain amount of time (e.g., y seconds).

[0311] For example, a network node can directly generate prediction information. For example, based on information related to a prediction sensing request, a network node can directly generate prediction information.

[0312] For example, the second device may include a wireless device, a user device (User Equipment, UE), an autonomous mobile robot (AMR), a drone, a robot, a base station, a roadside unit (RSU), etc.

[0313] For example, the first device may perform the step of performing at least one action based on the prediction information. For example, the at least one action may include at least one of deceleration, preparation to stop, and a change of path due to congestion.

[0314] For example, the first device may perform the step of transmitting the prediction information to the second device. For example, the second device may perform the step of performing at least one action based on the prediction information. For example, the at least one action may include at least one of deceleration, preparation to stop, and a change of route due to congestion.

[0315] For example, the network node may further perform the step of transmitting configuration information related to the updated sensing service based on the above prediction information. For example, the step of transmitting configuration information related to the updated sensing service may be performed optionally.

[0316] For example, based on predictive information, a network node may generate configuration information related to an updated sensing service for the purpose of providing better service. For example, the configuration information related to the updated sensing service may include information related to a changed region of interest, a changed sensing time, and / or a changed sensing cycle.

[0317] According to some embodiments of the present disclosure, the first device can communicate with at least one of user equipment, a network, or an autonomous vehicle other than a wireless device.

[0318] The following describes methods for providing prediction information and controlling (enabling or disabling) the provision of prediction information.

[0319] According to some embodiments of the present disclosure, the methods and steps presented below may be performed or used in combination or complementarily.

[0320] A mobile communication system (e.g., terminal, base station, core network, and / or server) collects sensing measurement information through sensing.

[0321] The mobile communication system can transmit the collected information as is, or process it into meaningful service information regarding the situation in an area of ​​interest and transmit it to mobile communication system terminals / nodes necessary for service provision.

[0322] For example, meaningful service information regarding the situation in an area of ​​interest can be processed to include predictive information.

[0323] For example, meaningful service information regarding the situation in an area of ​​interest may be provided to a user / terminal receiving a sensing-related service, or to a network node / base station and internal / external server (which may be located at the edge or central) of a mobile communication network providing / operating a sensing-related service.

[0324] FIG. 11 illustrates an example of a scenario according to some embodiments of the present disclosure.

[0325] For example, AMR A may or may not have sensing capability. AMR A may have the capability to connect to / register with a network and communicate (registration / communication capability). For example, AMR A may be a UE.

[0326] In FIG. 11, AMR A may not be able to sense people or objectives in a specific area that it intends to sense. Alternatively, AMR A may be located in an area where it is difficult to sense people or objectives in that specific area. Alternatively, AMR A may be located in an area where sensing of people or objectives in that specific area is possible, but the sensing results are insufficient or lacking. AMR A may be approaching that area.

[0327] For example, AMR B may have sensing capability.

[0328] In FIG. 11, AMR B may be in a position that is relatively good for sensing people / objectives in a specific area compared to AMR A. Alternatively, AMR B may be in a condition that allows for obtaining more accurate and reliable measurement results regarding people / objectives in that specific area.

[0329] For example, AMR B can be stationary or moving. For example, AMR B can be a stationary network node (e.g., RSU, base station, AP, etc.). For example, AMR B can be a mobile device (e.g., drone, user terminal, robot, etc.). For example, AMR B can connect to an Edge or central server via the network.

[0330] In FIG. 11, for example, the sensing target may be people in a specific area (e.g., a sensing range). For example, the sensing target may have access to an area of ​​interest (e.g., a range for extracting / transmitting contextual information). For example, the people in the specific area (e.g., a sensing range) who are the sensing targets may have access to an area of ​​interest (e.g., a range for extracting / transmitting contextual information). For example, the sensing target may be distinguished / described by the characteristics of the density / complexity of the area of ​​interest. For example, the sensing target may be a single person or a group of several people.

[0331] In FIG. 11, the sensing target is depicted as a person, but the sensing target can be various types of devices (e.g., AMR, drone, user terminal, and / or robot, etc.).

[0332] FIG. 12 illustrates an example of a procedure for providing predictive information and enabling the provision of predictive information according to some embodiments of the present disclosure.

[0333] In FIG. 12, the corresponding functional nodes and procedures are described based on the functional nodes and procedures of a 3GPP 5G system, but can be extended and used for a 6G system. For example, the nodes in FIG. 12 can be viewed as 6G nodes that replace or include extended functions of the corresponding 5G functional nodes.

[0334] SF is a network node newly defined in the present disclosure, which performs sensing-specific functions (collection and processing of sensing data, configuration and provision of sensing-related information, generation of analytics of sensing-related information, etc.) and can be co-located with other network nodes such as NWDAF.

[0335] In step S1201, AMR A and AMR B can be connected to the network.

[0336] For example, AMR A and AMR B can register with the network and / or create PDU sessions.

[0337] In step S1202, the server providing the service may transmit sensing service-related configuration information (e.g., area of ​​interest, sensing time / period, etc.) to AMR A and AMR B.

[0338] The transmission of the relevant information may be performed together during the process of forming a network registration / PDU session, or through a separate procedure.

[0339] In step S1203, AMR B can sense the target person / object, etc., and collect sensing measurement data.

[0340] In step S1204, AMR B can request the activation of predictive sensing from the AF / server located at the edge / central via control signals between network nodes or user data.

[0341] For example, AMR B can forward predictive sensing requests to AF or servers located at the edge / center.

[0342] Predictive sensing requests can be transmitted to an AF or server via RAN nodes, AMF, SF, and / or NEF.

[0343] A predictive sensing request may include a predictive sensing activation indication, time information, location information, and / or sensing-related data. Alternatively, a predictive sensing request may include not only the predictive sensing activation indication but also other indications for activating predictive sensing.

[0344] Additionally, a predictive sensing request may include time information / location information at which sensing information was collected and sensing-related data.

[0345] In step S1205, AF and / or the server may request SF and NWDAF to collect / monitor information and generate analytics. Alternatively, the server itself may perform information forecasting, such as collecting / monitoring information and generating analytics.

[0346] In step S1206, AF and / or the server may directly send prediction information about the situation of a particular area of ​​interest at a particular time of interest to AMR A.

[0347] Alternatively, AF and / or the server can transmit the information to AMR A via AMR B.

[0348] - Examples of predictive information regarding a situation are as follows: multiple people are "now" in "Zone X" (e.g., a zone shared by human workers and robots); or multiple people will "soon" (e.g., in X seconds) access "Zone X"; one worker is "now" in "Zone Z"; or one worker will "soon" (e.g., in X seconds) access "Zone X".

[0349] Additionally, as an example of prediction information, there may be situations regarding congestion levels of robots, people, etc., in a specific area expected to change at a certain point in time. This can be expressed in terms of the number of individual objects or relative density levels.

[0350] In step S1207, based on predictive information, for the purpose of providing better service, AF and / or the server send information to AMR B regarding changes to the region of interest, changes to the sensing time / period, etc. Additionally, if configuration changes to AMR A and other network nodes are required, an information update procedure may be performed.

[0351] According to some embodiments of the present disclosure, after the above procedure, a procedure to disable predictive sensing may be performed.

[0352] Similar to the activation procedure, a direct deactivation request from AMR B (in situations where sensing results are deemed meaningless in a specific area, etc.) or network node (in situations where there is a problem with the use of network resources for sensing, etc.) may be transmitted to AF and / or server.

[0353] Alternatively, AF and / or the server may perform a deactivation procedure based on its own judgment (such as reasons for service interruption or conditions under an agreement with a network operator). In this case, a procedure to update the configuration information of the targets (base stations and network nodes, etc.) participating in the provision of the relevant information sensing service may be performed.

[0354] FIG. 13 illustrates examples of a procedure for providing predictive information and disabling predictive information provision according to some embodiments of the present disclosure.

[0355] In step S1301, AMR A and AMR B can be connected to the network.

[0356] For example, AMR A and AMR B can register with the network and / or create PDU sessions.

[0357] Step S1301 may be performed optionally. For example, if AMR A and AMR B are already connected to the network, Step S1301 may be omitted.

[0358] In step S1302, the service-providing server transmits sensing service-related configuration information (e.g., area of ​​interest, sensing time / period, etc.) to AMR A and AMR B.

[0359] In step S1303, AMR B senses the target person / object, etc., and collects the sensing measurement data.

[0360] In step S1304, AMR B requests the AF / server located at the edge / central to deactivate predictive sensing via control signals between network nodes or user data.

[0361] For example, AMR B can forward a request to disable predictive sensing to an AF or a server located at the edge / center.

[0362] A request to disable predictive sensing can be sent to an AF or server via a RAN node, AMF, SF, and / or NEF.

[0363] A predictive sensing disable request may include a predictive sensing activation indication, time information, location information, and / or sensing-related data. For example, a predictive sensing disable request may include sensing measurement data performed to date.

[0364] Alternatively, a request to disable predictive sensing may include not only an indication to disable predictive sensing, but also other indications to disable predictive sensing.

[0365] In step S1305, AF and / or the server may request SF and NWDAF to collect / monitor information and generate analytics. Alternatively, the server itself may perform information forecasting, such as collecting / monitoring information and generating analytics.

[0366] In step S1306, AF and / or the server may directly send prediction information about the situation of a particular area of ​​interest at a particular time of interest to AMR A.

[0367] Alternatively, AF and / or the server can transmit the information to AMR A via AMR B.

[0368] - Examples of predictive information regarding a situation are as follows: multiple people are "now" in "Zone X" (e.g., a zone shared by human workers and robots); or multiple people will "soon" (e.g., in X seconds) access "Zone X"; one worker is "now" in "Zone Z"; or one worker will "soon" (e.g., in X seconds) access "Zone X".

[0369] Additionally, as an example of prediction information, there may be situations regarding congestion levels of robots, people, etc., in a specific area expected to change at a certain point in time. This can be expressed in terms of the number of individual objects or relative density levels.

[0370] In step S1307, based on predictive information, for the purpose of providing better service, AF and / or the server send information to AMR B regarding changes to the region of interest, changes to the sensing time / period, etc. Additionally, if configuration changes to AMR A and other network nodes are required, an information update procedure may be performed.

[0371] A method performed by a first network node (e.g., AF / server) according to some embodiments of the present invention is described.

[0372] The first network node can perform a configuration step. For example, the first network node can transmit Sensing service related configuration info (e.g., area of ​​interest, sensing time / period, etc.) to targets participating in the provision of the sensing service (base station and network node, etc.).

[0373] The first network node may perform a request reception step. The first network node receives a Predictive sensing request from entities participating in the provision of sensing services (e.g., AMR, base station, and network node, etc.). This request includes an indication to activate predictive sensing. Additionally, it may include time information / location information where sensing information was collected and sensing-related data.

[0374] The first network node can perform the information prediction execution step. The first network node may request SF and NWDAF to collect / monitor information and generate analytics, or the Server itself may perform information prediction, such as collecting / monitoring information and generating analytics.

[0375] The first network node can perform a predicted information transmission step. The first network node can transmit the predicted information to a target receiving the sensing service directly or via other participating terminals and network nodes.

[0376] The first network node can perform a configuration update step. Based on predictive information, the first network node can send information to entities participating in the provision of sensing services (e.g., AMR, base station and network node, etc.) for the purpose of providing better services, such as changing the area of ​​interest, changing the sensing time / period, etc.

[0377] Hereinafter, several embodiments related to a use case on supporting intelligence leveraging nearby entities for real-time awareness are described.

[0378] In everyday life, there are many situations where physical entities (e.g., devices, vehicles, or equipment) need to perceive events or changes that are occurring or expected to occur near where they will soon be located.

[0379] For example, delivery robots driving in urban areas can benefit from timely information about traffic congestion along their routes, and autonomous vehicles entering parking areas can benefit from real-time updates on occupancy status.

[0380] The quality of such information, including aspects such as timeliness, accuracy, and relevance, is often significantly enhanced through collaboration with surrounding entities (devices or systems with similar sensing and processing capabilities) that are closer to the event or location of interest.

[0381] By sharing real-time data or situation updates, these surrounding entities can be enabled to access more accurate and immediate information from one another, ultimately improving response and decision-making processes in dynamic environments.

[0382] Preconditions

[0383] In indoor (or outdoor) work site environments, there may be specific regions of interest shared by workers and automated mobile robots (AMRs) that are working and moving.

[0384] AMR A can observe and monitor a region of interest (e.g., Zone X) to some extent using its detection capabilities. However, the quality of observation and monitoring may not be sufficient for the following reasons.

[0385] for example,

[0386] - Because detection performance is poor (e.g., due to a relatively long distance); and / or

[0387] This is because Zone X may not be directly observed by some AMRs (e.g., AMR A) that need to know the situation in that zone.

[0388] AMR B is closer to Zone X, which is the region of interest of AMR A, and AMR B can observe and monitor that region more accurately and stably.

[0389] Service flow

[0390] FIG. 14 illustrates an example of a service flow according to some embodiments of the present disclosure.

[0391] In Fig. 14, AMR A (UE) can obtain more reliable and accurate information (predictive information) about situations currently occurring or likely to occur in a timely manner with the help of another UE (i.e., AMR B).

[0392] AMR A can move along a planned trajectory in an outdoor environment.

[0393] The trajectory may share areas where humans (e.g., pedestrians, human workers) enter, exit, or stay. If the AMR has limited information regarding proximity (e.g., tens of meters), the speed of AMR A is limited to Speed ​​Level A. On the other hand, if the AMR can obtain real-time information regarding proximity and determines that a specific area of ​​interest is safe, the AMR can increase its speed to Level B. This specific area may be within the coverage or reach of AMR B, which is capable of co-communication and detection.

[0394] [Expected Case 1] AMR B recognizes that a specific AMR is approaching and responds by transmitting contextual information (e.g., presence of a person or object), which allows the AMR(s) to prepare necessary measures (e.g., deceleration, reroute planning).

[0395] [Expected Case 2] AMR B periodically broadcasts situational information (e.g., presence of people or objects), and through this, AMR can prepare necessary measures (e.g., deceleration, replanning).

[0396] For example: Context information may include detection results, data processed from detection results, or information inferred from detection results (e.g., indication of the presence of "objects" or "congestion" levels). Context information may be prepared by the AMR itself (e.g., on-device AI / computing) or by an edge server or a group of servers.

[0397] AMR A receives the information transmitted by AMR B.

[0398] AMR A determines what action to perform (e.g., deceleration, preparation to stop, route replanning due to "congestion," etc.).

[0399] AMR B transmits situational information, such as an increase or decrease in the number of people or objects in a specific area of ​​interest, so that AMR A can manage the operation.

[0400] In addition, this information can be used to coordinate network resources required for the stable operation of AMRs in 6G networks.

[0401] Post-conditions

[0402] AMR A can collect more accurate information about the scene of interest through cooperation with AMR B.

[0403] AMR A can reduce speed to an appropriate level of deceleration (e.g., maintain physical load balance of the forklift), replan the movement path at the work site, or establish advance plans to prevent collisions.

[0404] Existing features that encompass some or all of the use case capabilities

[0405] Here are a few examples:

[0406] - 5G systems can support network exposure to authorized third parties (e.g., TS 23.501, TS 23.502, and TS 23.503).

[0407] - 5G systems can support AI / ML operations at the application layer (e.g., TS 23.501, TS 23.502, and TS 23.503).

[0408] - Sensing-related service requirements for 5G systems may be specified in TS 22.137.

[0409] - AIML-related service requirements for 5G systems may be specified in TS 22.261.

[0410] - Support for QoS prediction information for intelligent physical systems (e.g., UEs supporting V2X applications, automated mobile robots) in TS 22.186 and TS 22.104.

[0411] - 5G system features that support network data analysis (predictive or statistical) services specified in some Phase 2 specifications (e.g., TS 23.228, TS 23.501, TS 23.502, and TS 23.503).

[0412] Potential new requirements needed to support use cases

[0413] If requested by an application, the 6GS must provide means to enable and disable the function of providing predictive information about the situation of a specific time of interest in a specific region of interest to an approved application running within the UE.

[0414] - For example, examples of predictive information regarding a situation are as follows: multiple people are "now" in "Zone X" (e.g., a zone shared by human workers and robots); or multiple people will access "Zone X" "soon" (e.g., in X seconds); one worker is "now" in "Zone Z"; or one worker will access "Zone X" "soon" (e.g., in X seconds).

[0415] - For example, this requirement is based on a scenario in which an AMR (UE) initiating and detecting detection or contextual information (e.g., detection or other mechanisms) requests the processing and provision of contextual information from an edge server, including timestamps, locations, and orientations. (For example, the information may be "about the relevant AMR" or "about AMRs that are already in or will be in the region of interest.")

[0416] In the case where multiple AMRs exist, the 6G system must provide a means to scalably and efficiently utilize network resources necessary for the stable operation of AMRs containing predictive information.

[0417] For example, this requirement focuses on the need to optimize network resources for detection and communication when the number of objects of interest is large, particularly when the number of objects changes dynamically over time.

[0418] - When providing context information to the UE, the 6G system must be able to provide a means to guarantee the latency limit requested by the application.

[0419] For example, latency depends on how fast the AMR moves in the area of ​​interest and various types of applications in diverse fields such as factories and mines.

[0420] According to some embodiments of the present disclosure, a wireless device communicates with at least one of user equipment, a network, or an autonomous vehicle other than the wireless device.

[0421] Some of the detailed steps illustrated in the examples of FIGS. 9 through 14 are not essential steps and may be omitted. In addition to the steps illustrated in FIGS. 9 through 14, other steps may be added, and the order of the steps may vary. Some of the above steps may have unique technical significance.

[0422] Hereinafter, a network node according to some embodiments of the present disclosure will be described. Here, the network node may be AF of FIG. 4.

[0423] For example, a network node can perform the methods described above. Detailed descriptions that overlap with the foregoing may be simplified or omitted.

[0424] A network node may include a memory and at least one processor operably connected to the memory. The at least one processor may be adapted to perform at least one operation.

[0425] The above at least one operation includes the step of transmitting configuration information related to a sensing service; the step of receiving information related to a prediction sensing request; and the step of transmitting prediction information, wherein the prediction information may include (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time.

[0426] For example, information related to a predictive sensing request may include a predictive sensing enable indicator or a predictive sensing disable indicator.

[0427] For example, information related to a predictive sensing request may include (i) collected sensing information, (ii) time information related to said collected sensing information, and / or (iii) location information related to said collected sensing information.

[0428] For example, the above network node may be (i) an Application Function node (AF), (ii) an Edge Server, (iii) a Central Server, or (iv) a Sensing Function node (SF).

[0429] For example, the above at least one operation may further include the step of transmitting configuration information related to an updated sensing service based on the prediction information.

[0430] For example, information related to the above-mentioned predictive sensing request is received from a first device, and the first device may be a wireless device, a user device (User Equipment, UE), an autonomous mobile robot (AMR), a drone, a robot, a base station, or a roadside unit (RSU).

[0431] For example, the prediction information may include (i) information related to the number of prediction targets, (ii) information related to a prediction zone associated with the prediction targets, and / or (iii) information related to the prediction time at which the prediction targets will be located in the prediction zone.

[0432] Hereinafter, a device for providing predictive information in a wireless communication system according to some embodiments of the present disclosure will be described. Here, the device may be the wireless device (100 or 200) of FIGS. 2 and 3.

[0433] For example, the first device may perform the methods described above. Detailed descriptions that overlap with the foregoing may be simplified or omitted.

[0434] For example, the first device (100) may include a processor (102) and a memory (104).

[0435] According to some embodiments of the present disclosure, the processor (102) may be configured to be operablely coupled with the memory (104).

[0436] The processor is adapted to perform the steps of: receiving configuration information related to a sensing service; transmitting information related to a prediction sensing request; and receiving prediction information, wherein the prediction information may include (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time.

[0437] For example, the processor may be adapted to further perform the step of transmitting the prediction information to a second device.

[0438] For example, the processor may be adapted to perform an additional step of performing at least one action based on the prediction information. For example, the at least one action may include at least one of deceleration, preparation to stop, and a change of path due to congestion.

[0439] For example, information related to a predictive sensing request may include a predictive sensing enable indicator or a predictive sensing disable indicator.

[0440] For example, the first device may be a wireless device, a user device (User Equipment, UE), an autonomous mobile robot (AMR), a drone, a robot, a base station, or a roadside unit (RSU).

[0441] For example, information related to the above prediction sensing request is transmitted to a network node, and the network node may be (i) an Application Function node (AF), (ii) an Edge Server, (iii) a Central Server, or (iv) a Sensing Function node (SF).

[0442] For example, the first device may communicate with at least one of user equipment, a network, or an autonomous vehicle other than the first device.

[0443] A processor for a network node for providing predictive information, according to some embodiments of the present disclosure, is described.

[0444] The processor may be configured to perform the steps of: transmitting configuration information related to a sensing service; receiving information related to a prediction sensing request; and transmitting prediction information. The prediction information may be characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time.

[0445] A processor for a first device for providing predictive information according to some embodiments of the present disclosure is described.

[0446] The processor may be configured to perform the steps of: receiving configuration information related to a sensing service; transmitting information related to a prediction sensing request; and receiving prediction information. The prediction information may include (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time.

[0447] A non-transient computer-readable medium storing a plurality of instructions for providing predictive information, according to some embodiments of the present disclosure, is described.

[0448] According to some embodiments of the present invention, the technical features of the present invention may be directly implemented in hardware, software executed by a processor, or a combination thereof. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or other storage media.

[0449] In some examples, storage media are connected to the processor so that the processor can read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. As another example, the processor and storage media can exist as separate configuration elements.

[0450] Computer-readable media may include tangible non-transient computer-readable storage media.

[0451] For example, non-transient computer-readable media may include synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically eraseable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, or random access memory (RAM) such as other media that can be used to store instructions or data structures. Additionally, non-transient computer-readable media may include combinations thereof.

[0452] Additionally, the method described herein may be realized at least partially by a computer-readable communication medium that transmits or communicates code in the form of something that can be accessed, read, and / or executed by a computer, such as instructions or data structures.

[0453] According to some embodiments of the present specification, a plurality of instructions may be stored in a non-transient computer-readable medium.

[0454] Multiple stored instructions can be executed by the processor of a network node.

[0455] A plurality of stored instructions may be configured to perform the steps of: transmitting configuration information related to a sensing service; receiving information related to a prediction sensing request; and transmitting prediction information.

[0456] For example, the above prediction information may be characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time.

[0457] Multiple stored instructions can be executed by the processor of the first device.

[0458] A plurality of stored instructions may be configured to perform the steps of: the processor receiving configuration information related to a sensing service; transmitting information related to a prediction sensing request; and receiving prediction information.

[0459] The above forecast information may include (i) forecast information related to a specific region and / or (ii) forecast information related to a specific time.

[0460] The present disclosure may have various effects.

[0461] According to some embodiments of the present disclosure, the device can efficiently provide prediction information.

[0462] According to some embodiments of the present disclosure, a network node can efficiently receive prediction information.

[0463] According to some embodiments of the present disclosure, a device or network node can efficiently enable or disable the provision of predictive information.

[0464] For example, according to the present disclosure, the functionality of a network node (e.g., AF) can be enhanced by targeting a 5G evolution / 6G system in a zero-touch configuration / operation environment where network automation is extended. For example, by enabling or disabling the provision of sensing-related predictive information used in the system, the relevant information can be efficiently transmitted to a third party. Thus, the information can be effectively utilized in AI services.

[0465] According to some embodiments of the present disclosure, a wireless communication system can efficiently provide prediction information.

[0466] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0467] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method. Other implementations are within the scope of the following claims.

Claims

1. Regarding the method, A step of transmitting configuration information related to a sensing service by a network node; A step of receiving information related to a prediction sensing request by the above network node; and The method includes the step of transmitting prediction information by the above network node, The above prediction information is characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time. method.

2. In Paragraph 1, Information related to a predictive sensing request is characterized by including a predictive sensing enable indicator or a predictive sensing disable indicator. method.

3. In Paragraph 1, Information related to a predictive sensing request is characterized by including (i) collected sensing information, (ii) time information related to said collected sensing information, and / or (iii) location information related to said collected sensing information. method.

4. In Paragraph 1, The above network node is characterized as being (i) an Application Function node (AF), (ii) an Edge Server, (iii) a Central Server, or (iv) a Sensing Function node (SF). method.

5. In Paragraph 1, Characterized by further including the step of transmitting configuration information related to an updated sensing service based on the prediction information by the above network node. method.

6. In Paragraph 1, Information related to the above prediction sensing request is received from the first device, and The above first device is characterized as being a wireless device, user equipment (UE), autonomous mobile robot (AMR), drone, robot, base station, or roadside unit (RSU). method.

7. In Paragraph 1, The above prediction information is characterized by including (i) information related to the number of prediction targets, (ii) information related to a prediction zone related to the prediction targets, and / or (iii) information related to the predicted time at which the prediction targets will be located in the prediction zone. method.

8. Regarding the method, A step of receiving setting information related to a sensing service by a first device; A step of performing sensing and collecting sensing data by the first device above; A step of transmitting information related to a prediction sensing request by the first device; and The method includes the step of receiving prediction information by the first device, The above prediction information is characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time. method.

9. In Paragraph 8, Characterized by including the step of transmitting the prediction information to the second device by the first device. method.

10. In Paragraph 8, Characterized by including the step of performing at least one operation based on the prediction information by the first device. method.

11. In Paragraph 10, The above at least one operation includes at least one of deceleration, preparation for stopping, and a change of path due to congestion, method.

12. In Paragraph 8, Information related to a predictive sensing request is characterized by including a predictive sensing enable indicator or a predictive sensing disable indicator. method.

13. In Paragraph 8, The above first device is characterized as being a wireless device, user equipment (UE), autonomous mobile robot (AMR), drone, robot, base station, or roadside unit (RSU). method.

14. In Paragraph 8, Information related to the above prediction sensing request is transmitted to network nodes, and The above network node is characterized as being (i) an Application Function (AF), (ii) an Edge Server, (iii) a Central Server, or (iv) a Sensing Function Node (SF). method.

15. In Paragraph 8, The first device is characterized by communicating with at least one of user equipment, a network, or an autonomous vehicle other than the first device. method.

16. Regarding network nodes, Memory; and It includes at least one processor operably connected to the memory, wherein the at least one processor is adapted to perform at least one operation, and the at least one operation is, A step of transmitting configuration information related to the sensing service; A step of receiving information related to a predictive sensing request; and Includes a step of transmitting prediction information, The above prediction information is characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time. Network node.

17. In Paragraph 16, Information related to a predictive sensing request is characterized by including a predictive sensing enable indicator or a predictive sensing disable indicator. Network node.

18. In Paragraph 16, Information related to a predictive sensing request is characterized by including (i) collected sensing information, (ii) time information related to said collected sensing information, and / or (iii) location information related to said collected sensing information. Network node.

19. In Paragraph 16, The above network node is characterized as being (i) an Application Function (AF), (ii) an Edge Server, (iii) a Central Server, or (iv) a Sensing Function Node (SF). Network node.

20. In claim 16, the above at least one operation is, Characterized by further including the step of transmitting configuration information related to an updated sensing service based on the above prediction information, Network node.

21. In Paragraph 16, Information related to the above prediction sensing request is received from the first device, and The above first device is characterized as being a wireless device, user equipment (UE), autonomous mobile robot (AMR), drone, robot, base station, or roadside unit (RSU). Network node.

22. In Paragraph 16, The above prediction information is characterized by including (i) information related to the number of prediction targets, (ii) information related to a prediction zone related to the prediction targets, and / or (iii) information related to the predicted time at which the prediction targets will be located in the prediction zone. Network node.

23. In the first device, Memory; and It includes at least one processor operably connected to the memory, wherein the at least one processor is, A step of receiving configuration information related to a sensing service; Step of performing sensing and collecting sensing data; A step of transmitting information related to a predictive sensing request; and Adapted to perform the step of receiving prediction information, The above prediction information is characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time. First device.

24. In claim 23, the at least one processor is, Characterized by being adapted to further perform the step of transmitting the prediction information to a second device. First device.

25. In claim 23, the at least one processor is, Characterized by being adapted to perform an additional step of performing at least one operation based on the above prediction information, First device.

26. In Paragraph 25, The above at least one operation includes at least one of deceleration, preparation for stopping, and a change of path due to congestion, First device.

27. In Paragraph 23, Information related to a predictive sensing request is characterized by including a predictive sensing enable indicator or a predictive sensing disable indicator. First device.

28. In Paragraph 23, The above first device is characterized as being a wireless device, user equipment (UE), autonomous mobile robot (AMR), drone, robot, base station, or roadside unit (RSU). First device.

29. In Paragraph 23, Information related to the above prediction sensing request is transmitted to network nodes, and The above network node is characterized as being (i) an Application Function node (AF), (ii) an Edge Server, (iii) a Central Server, or (iv) a Sensing Function node (SF). First device.

30. In Paragraph 23, The first device is characterized by communicating with at least one of user equipment, a network, or an autonomous vehicle other than the first device. First device.

31. A processor for a network node in a wireless communication system, wherein the processor is configured for the network node to perform operations, and said operations are: A step of transmitting configuration information related to the sensing service; A step of receiving information related to a predictive sensing request; and Includes a step of transmitting prediction information, The above prediction information is characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time. Processor.

32. In a wireless communication system, a non-transitory computer-readable medium storing a plurality of instructions based on execution by a processor of a network node, wherein the plurality of instructions are configured for the network node to perform operations, and the operations are: A step of transmitting configuration information related to the sensing service; A step of receiving information related to a predictive sensing request; and Includes a step of transmitting prediction information, The above prediction information is characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time. Non-transient computer-readable medium.

33. A processor for a first device in a wireless communication system, wherein the processor is configured to enable the first device to perform operations, and said operations are: A step of receiving configuration information related to a sensing service; Step of performing sensing and collecting sensing data; A step of transmitting information related to a predictive sensing request; and Includes the step of receiving prediction information, The above prediction information is characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time. Processor.

34. In a wireless communication system, a non-transitory computer-readable medium storing a plurality of instructions based on execution by a processor of a first device, wherein the plurality of instructions are configured for the first device to perform operations, and the operations are: A step of receiving configuration information related to a sensing service; A step of transmitting information related to a predictive sensing request; and Includes the step of receiving prediction information, The above prediction information is characterized by including (i) prediction information related to a specific region and / or (ii) prediction information related to a specific time. Non-transient computer-readable medium.

Images