Network node and communication method

Abstract

This network node comprises: a reception unit that receives data which is related to a terminal and collected by a first network node; a control unit that subjects the data to pre-processing for data storage; and a transmission unit that transmits the data subjected to the pre-processing to a second network node.

Description

Network Node and Communication Method

[0001] The present invention relates to data collection technology in a mobile network.

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to achieve further increases in system capacity, further increases in data transmission speed, further reduction in latency in the radio section, etc., a wireless communication method called 5G or NR (New Radio) (hereinafter, this wireless communication method is referred to as "5G" or "NR") has been introduced. In 5G, various wireless technologies have been introduced in order to meet the requirement of achieving a throughput of 10 Gbps or more while reducing the latency in the radio section to 1 ms or less. Furthermore, research on 6G, which is a future communication system, is also being conducted.

[0003] In 5G, communications according to use cases such as eMBB, URLLC, and mMTC are provided. In 6G, which is a future communication system, in addition to providing the same services as 5G, services such as AI and sensing are provided. In both AI and sensing, it is necessary to collect data from UEs and the like.

[0004] 3GPP TS 26.531 V18.2.0 (2024-06)

[0005] However, data collection in the conventional 5G mainly targets the collection of UE data and does not support use cases using various big data within the 3GPP (Registered Trademark) network for 6G and the utilization of AI / ML based on such big data. Also, in the prior art, preprocessing for data storage or postprocessing for data release is not appropriately performed.

[0006] The present invention has been made in view of the above points, and an object thereof is to provide a technology that enables appropriate preprocessing or postprocessing of collected data.

[0007] According to the disclosed technology, a network node is provided comprising: a receiving unit that receives data related to terminals collected by a first network node; a control unit that performs preprocessing on the data for data storage; and a transmitting unit that transmits the preprocessed data to a second network node.

[0008] The disclosed technology provides a method for appropriately performing pre-processing or post-processing on collected data.

[0009] This is a diagram illustrating an example of a communication system. This is a diagram illustrating an example of a communication system in a roaming environment. This is a diagram illustrating an example configuration for data collection in the prior art. This is a diagram illustrating an example configuration for data collection in the prior art. This is a diagram illustrating an example configuration of a communication system in an embodiment of the present invention. This is a diagram illustrating operation example 1. This is a diagram illustrating operation example 2. This is a diagram illustrating an example of the functional configuration of a network node 100 in an embodiment of the present invention. This is a diagram illustrating an example of the functional configuration of a terminal 10 in an embodiment of the present invention. This is a diagram illustrating an example of the hardware configuration of a terminal 10 and a network node 100 in an embodiment of the present invention. This is a diagram illustrating an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0010] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE or existing NR, but are not limited to these.

[0012] Furthermore, in embodiments of the present invention, "configuring" wireless parameters means that predetermined values ​​are pre-configured, or that wireless parameters notified from a network node or terminal 10 are configured. Below, we will first describe an example of the configuration of a 5G core network, which is an example of a network to which the technology of the present invention is applied, and then describe the configuration and operation related to embodiments of the present invention.

[0013] Figure 1 is a diagram illustrating an example of a communication system corresponding to a core network. As shown in Figure 1, this communication system consists of a UE (User Interface) which is a terminal, and multiple network nodes. Note that a configuration including one or more network nodes may be called a "network". Hereinafter, one network node will be assumed to correspond to each function, but one network node may implement multiple functions, or multiple network nodes may implement one function. Also, the "connection" described below may be a logical connection or a physical connection. Furthermore, although Figure 1 shows a 5G core network, all or part of the network nodes in the core network shown in Figure 1 may also be used in 6G, which is envisioned as the application target of the technology according to this embodiment.

[0014] A RAN (Radio Access Network) is a network node with radio access functionality, which may include a base station, and is connected to a UE, AMF (Access and Mobility Management Function), and UPF (User plane function). A RAN may also be called a base station. An AMF is a network node that has functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. A UPF is a network node that interconnects with a DN (Data Network) and has functions such as a PDU (Protocol Data Unit) session point to the outside world, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice.

[0015] AMF is connected to UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), AF (Application Function), and UDR (User Data Repository). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and UDR are network nodes that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf, and Nudr.

[0016] The SMF is a network node with functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. The NEF is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node with functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. The PCF is a network node with the function of controlling network policies. The AF is a network node with the function of controlling application servers. The NRF is a network node with the function of discovering NF instances that provide services. The UDM is a network node that manages subscriber data and authentication data. The UDM is connected to the UDR that holds the said data. Note that the AF may also be called the application function.

[0017] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 10 (UE) and multiple network nodes.

[0018] SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). In Figure 2, vSEPP is SEPP in the visited network, and hSEPP is SEPP in the home network.

[0019] As shown in Figure 2, the UE is in a roaming environment connected to the RAN and AMF in the Visited PLMN. The Visited PLMN and Home PLMN are connected via vSEPP and hSEPP. The UE can communicate with the UDM of the Home PLMN, for example, via the AMF of the Visited PLMN.

[0020] (Regarding the issue) Non-patent document 1 (TS26.531) discloses a data collection mechanism in 5G. Figure 3 shows an example of a configuration for data collection in 3GPP (registered trademark). Regarding the handling of data within a 3GPP (registered trademark) network in 5G, data collection from the UE is the main focus, and only a portion of the data is collected when considering the RAN / transport / core network as a whole.

[0021] Furthermore, the collected data is not intended to be made available outside the 3GPP® network for use outside of it. In other words, conventional technology only envisioned data collection, analysis using NWDAF, and partial use by collaborating application service providers.

[0022] Figure 4 shows the functional configuration of data collection in current 5G, as disclosed in Non-Patent Document 1 (TS26.531). As shown in Figure 4, current 5G data collection mainly targets UE data collection and does not support use cases using various big data within 3GPP (registered trademark) for 6G, nor does it support AI / ML utilization based on big data.

[0023] Furthermore, it does not support data anonymization, abstraction, or reduction, nor does it apply to data policies that differ from region to region, country to country, or company to company. In other words, conventional technologies do not properly perform pre-processing for data storage or post-processing for data release.

[0024] (Outline of the Embodiment) The 6G communication system envisioned in this embodiment is expected to be a system that utilizes big data within the RAN / transport network / core network and AI / ML based on that big data.

[0025] Therefore, this embodiment proposes a new data collection method within the 3GPP® network. The method in this embodiment includes a function to anonymize the collected data, a function to abstract the collected data, and a function to reduce (reduce) the collected data.

[0026] Furthermore, in this embodiment, appropriate data policies are defined within the 3GPP® network and applied to address the different systems, laws, or rules that vary by region, country, and company. This establishes secure data management. At the same time, when exposing data outside the 3GPP® network, the system adheres to appropriate policies, ensuring that no security issues arise.

[0027] In this embodiment, the function that collects data is called a Data Function (DF). The DF serves as an element for data collection and utilization in each domain, similar to a network function in the 5G era. Furthermore, a U-Plane in 5G is used as an interface between domains. Note that the name of the function that collects data is not limited to Data Function; a name other than Data Function may be used as the name of the function that collects data.

[0028] (System Configuration Example) Figure 5 shows an example of the configuration of the communication system in this embodiment. As shown in Figure 5, this communication system includes UE10, RAN20, TN (Transport Network)30, CN (Core Network)40, Application service provider50, and AS (Application Server)60.

[0029] UE10, RAN20, TN30, and CN40 may also be referred to as the UE domain, RAN domain, TN domain, and CN domain, respectively.

[0030] UE10 has DF11. DF11 has Data Collection Agent12. The Data Collection Agent is a functional unit that performs data collection in the DF. RAN20 has DF21. DF21 has Data Collection Agent22. TN30 has DF31. DF31 has Data Collection Agent32.

[0031] CN40 has DF41. DF41 has Data collection Agent42. CN40 further has Data Management Function43, Data Pre-processing Function44, Data Storage45, Data Post-processing Function46, Data Exposure Function47, NRF70, NWDAF80, and NEF90.

[0032] The Application service provider 50 includes a Provisioning AF 51, an Indirect Data Collection Client 52, and an Event Consumer AF 53. Note that the Application service provider 50 is the same as the conventional Application service provider shown in Figure 4.

[0033] The Data Management Function 43, Data Pre-processing Function 44, Data Storage 45, Data Post-processing Function 46, and Data Exposure Function 47 are each network nodes. Alternatively, each DF and RAN may also be referred to as a network node.

[0034] Furthermore, the Data Management Function, Data Pre-processing Function, Data Storage, Data Post-processing Function, and Data Exposure Function may also be referred to as the data management function, data pre-processing function, data storage device, data post-processing function, and data release function, respectively.

[0035] (Operation Example 1) Operation Example 1 of the communication system in this embodiment will be described with reference to the sequence chart shown in Figure 6. In Operation Example 1, data is collected in each domain and pre- and post-processing is performed in the core network 40.

[0036] In S101, DF11 in UE10 performs data collection related to UE10. For example, DF11 collects data acquired by sensors held by UE10. In S102, DF11 transfers the collected data to DF21 on the RAN20 side using the existing U-Plane.

[0037] In S103, DF21 in RAN20 performs data collection related to UE10. For example, DF21 collects location information of UE10 acquired by RAN20. In S104, DF21 transfers the collected data and the data received from DF11 to DF31 on the TN30 side using the existing U-Plane.

[0038] In S105, DF31 in TN30 performs data collection related to UE10. For example, DF31 collects area information of UE10 acquired by TN30. In S106, DF31 transfers the collected data and the data received from DF21 to DF41 on the CN40 side using the existing U-Plane.

[0039] In S107, DF41 in CN40 performs data collection related to UE10. For example, DF41 collects wide-area information of UE10 acquired by CN40. In S108, DF41 transfers the collected data and the data received from DF31 to Data Pre-processing Function 44 using the existing U-Plane.

[0040] In S109, the Data Pre-processing Function 44 performs preprocessing on the data received from DF 41, applying a pre-configured policy. Examples of preprocessing include data abstraction, data size reduction, data anonymization, and data encryption. Depending on the policy, one of the following may be performed: abstraction, size reduction, anonymization, or encryption; two of the following may be performed: abstraction, size reduction, anonymization, or encryption; three of the following may be performed: abstraction, size reduction, anonymization, or encryption; or all of the following may be performed: abstraction, size reduction, anonymization, or encryption.

[0041] In S110, the Data Pre-processing Function 44 transfers the pre-processed data to the Data Storage 45 using an existing U-Plane.

[0042] In S111, Data Storage 45 stores the data after preprocessing performed by Data Pre-processing Function 44. In S112, Data Storage 45 reads the data to be released and transfers it to Data Post-processing Function 46 using an existing U-Plane.

[0043] In S113, the Data Post-processing Function 46 performs post-processing for exposure on the data received from the Data Storage 45 according to a pre-configured policy. As post-processing, for example, it may delete excess data or create detailed data.

[0044] In S114, the Data Post-processing Function 46 transfers the post-processed data to the Data Exposure Function 47 using the existing U-Plane. In S115, the Data Exposure Function 47 completes the preparation for exposing data inside and outside the 3GPP (registered trademark) network.

[0045] Note that in the above example, data collection is performed in all of the UE 10, RAN 20, TN 30, and CN 40. However, data collection may not be performed in at least one domain among the UE 10, RAN 20, TN 30, and CN 40.

[0046] (Operation Example 2) Next, referring to the sequence chart shown in FIG. 7, an operation example 2 of the communication system in the present embodiment will be described. In the operation example, data collection is performed in each domain, and pre-processing is performed in each domain.

[0047] As shown in FIG. 7, in the communication system in operation example 2, a Data Pre-processing Function 13 is provided between DF11 and DF21. The Data Pre-processing Function 13 may be provided inside the UE 10 (inside the UE domain).

[0048] Also, a Data Pre-processing Function 23 is provided between DF21 and DF31. The Data Pre-processing Function 23 may be provided inside the RAN 20 (inside the RAN domain).

[0049] Also, a Data Pre-processing Function 33 is provided between DF31 and DF41. The Data Pre-processing Function 33 may be provided inside the TN 30 (inside the TN domain). The Data Pre-processing Functions 13, 23, and 33 are each network nodes.

[0050] In S201, DF11 in UE10 performs data collection related to UE10. For example, DF11 collects data acquired by sensors held by UE10. In S202, DF11 transfers the collected data to Data Pre-processing Function 13 using an existing U-Plane.

[0051] In S203, the Data Pre-processing Function 13 performs preprocessing on the data received from DF 11, applying a pre-configured policy. Examples of preprocessing include data abstraction, data size reduction, data anonymization, and data encryption. Depending on the policy, one of the following may be performed: abstraction, size reduction, anonymization, or encryption; two of the following may be performed: abstraction, size reduction, anonymization, or encryption; three of the following may be performed: abstraction, size reduction, anonymization, or encryption; or all of the following may be performed: abstraction, size reduction, anonymization, or encryption.

[0052] In S204, the Data Pre-processing Function 13 transfers the pre-processed data to the DF 21 on the RAN 20 side using the existing U-Plane.

[0053] In S205, DF21 in RAN20 performs data collection related to UE10. For example, DF21 collects location information of UE10 acquired by RAN20. In S206, DF21 transfers the collected data and the data received from Data Pre-processing Function 13 to Data Pre-processing Function 23 using the existing U-Plane.

[0054] In S207, the Data Pre-processing Function 23 applies a pre-configured policy to the data collected by DF21 from the data received from DF21. The content of the pre-processing is the same as the content of the pre-processing in S203.

[0055] In S208, the Data Pre-processing Function 23 transfers the pre-processed data and the pre-processed data received from DF 21 to DF 31 on the TN 31 side using the existing U-Plane.

[0056] In S209, DF31 in TN30 performs data collection related to UE10. For example, DF31 collects area information of UE10 acquired by TN30. In S210, DF31 transfers the collected data and the data received from Data Pre-processing Function 23 to Data Pre-processing Function 33 using the existing U-Plane.

[0057] In S211, the Data Pre-processing Function 33 applies a pre-configured policy to the data collected by DF 31 from the data received from DF 31. The content of the pre-processing is the same as the content of the pre-processing in S203.

[0058] In S212, the Data Pre-processing Function 33 transfers the pre-processed data and the pre-processed data received from DF 31 to DF 41 on the CN 40 side using the existing U-Plane.

[0059] In S213, DF41 in CN40 performs data collection related to UE10. For example, DF41 collects wide-area information of UE10 acquired by CN40. In S214, DF41 transfers the collected data and the data received from Data Pre-processing Function 33 to Data Pre-processing Function 44 using the existing U-Plane.

[0060] In S215, the Data Pre-processing Function 44 applies a pre-configured policy to the data collected by DF41 from the data received from DF41. The content of the pre-processing is the same as the content of the pre-processing in S203.

[0061] Subsequently, the Data Pre-processing Function 44 transfers the pre-processed data and the pre-processed data received from DF 41 to the Data Storage 45 using the existing U-Plane. The subsequent processing is the same as steps S111 to S115 in Operation Example 1.

[0062] (Applying policies to Data Functions) In this embodiment, policies can be set for a Data Function (DF), and the DF can collect data based on those policies. The process is described below. The following description is applicable to any of DFs 11, 21, 31, and 41.

[0063] First, set a policy for the Data Function in Data Management Function 43. This policy may be, for example, one, more, or all of the following methods for data acquisition: "data abstraction method, data anonymization method, data reduction method, and data encryption method." This policy may be set on a region-by-region, country-by-country, or company-by-company basis.

[0064] In this embodiment, "region" refers to, for example, the region where the UE (Unified Enterprise) whose data is collected is located. "Country" refers to the country in which the region is located. "Company" may refer to, for example, a business that collects data, or a business that uses the collected data.

[0065] If there are no issues with the policy, Data Management Function 43 sets the policy for the Data Factory (DF). When the DF retrieves data, it processes the data according to the configured policy.

[0066] (Applying policies to the Data Pre-processing Function) In this embodiment, policies can be set for the Data Pre-processing Function, allowing the Data Pre-processing Function to perform preprocessing based on those policies. The following describes this process. The following description is applicable to any of the Data Pre-processing Functions 13, 23, 33, and 44.

[0067] First, a preprocessing policy is set in the Data Management Function 43. This policy may be, for example, one, more, or all of the following methods for long-term storage: "data abstraction method, data anonymization method, data reduction method, and data encryption method." This policy may be set on a region-by-region, country-by-country, or company-by-company basis.

[0068] If there are no issues with the policy, Data Management Function 43 sets the policy for Data Pre-processing Function. When Data Pre-processing Function receives data from the previous node, it performs data preprocessing according to the configured policy.

[0069] (Applying policies to the Data Post-processing Function) In this embodiment, policies can be set for the Data Post-processing Function 46, and the Data Post-processing Function 46 can perform post-processing based on those policies. The following describes that process.

[0070] First, set up post-processing policies in Data Management Function 43. These policies could be, for example, region-specific policies, country-specific policies, or company-specific policies for exposure.

[0071] If there are no issues with the policy, the Data Management Function 43 sets the policy for the Data Post-processing Function 46. When the Data Post-processing Function 46 receives data from the previous node, it performs post-processing of the data according to the set policy.

[0072] (Effects of the Technology According to the Embodiment) As described above, the technology according to this embodiment is equipped with a Data Function for each domain, which performs pre-processing, storage, or post-processing on the data. This defines a data management location that will expand toward 6G within the 3GPP (registered trademark) domain, and enables data exposure in accordance with different policies of regions, countries, and companies.

[0073] (Device Configuration) Next, an example of the functional configuration of the network node 100 and UE 10 (hereinafter referred to as terminal 10) that perform the processing and operations described above will be explained. The network node 100 supports any of the following: Data Pre-processing Function, Data Management Function, Data Post-processing Function, DF, and RAN.

[0074] <Network Node 100> Figure 8 is a diagram showing an example of the functional configuration of network node 100. As shown in Figure 8, network node 100 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 8 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention.

[0075] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 10 or other network nodes and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 10 or other network nodes and obtaining information from the received signals, for example, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0076] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 10 or other network nodes in a storage device, and reads it from the storage device as needed. The control unit 140 controls the network node 100. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120. The transmission unit 110 and the reception unit 120 may also be called the transmitter and receiver, respectively.

[0077] <Terminal 10> Figure 9 is a diagram showing an example of the functional configuration of terminal 10. As shown in Figure 9, terminal 10 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 9 is merely an example. Any functional classification and name of functional unit is acceptable as long as it enables the operation according to the embodiment of the present invention.

[0078] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly (or via wire). The receiving unit 220 receives various signals wirelessly (or via wire) and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals transmitted from the base station. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0079] The setting unit 230 stores various setting information received from base stations, etc., by the receiving unit 220 in its storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-set setting information.

[0080] The control unit 240 controls the terminal 10. The signal transmission function of the control unit 240 may be included in the transmission unit 210, and the signal reception function of the control unit 240 may be included in the reception unit 220. The transmission unit 210 and the reception unit 220 may also be called the transmitter and receiver, respectively.

[0081] (Hardware Configuration) The block diagrams (Figures 8 and 9) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the above one device or the above multiple devices with software.

[0082] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0083] For example, the network node 100 and terminal 10 in one embodiment of the present disclosure may function as computers that process the communication method of the present disclosure. Figure 10 is a diagram showing an example of the hardware configuration of the network node 100 and terminal 10 according to one embodiment of the present disclosure. The network node 100 and terminal 10 described above may be physically configured as computer devices including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0084] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the network node 100 and the terminal 10 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0085] Each function in the network node 100 and terminal 10 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which causes the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0086] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0087] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the network node 100 shown in Figure 8 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 10 shown in Figure 9 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0088] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0089] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0090] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0091] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0092] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0093] Furthermore, the network node 100 and terminal 10 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0094] Figure 11 shows an example of the configuration of vehicle 2001. As shown in Figure 11, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013. For example, a network node 100 or a terminal 10 may be included in the communication module 2013.

[0095] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0096] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0097] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front and rear wheel rotation speed signals acquired by rotation speed sensor 2022, front and rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0098] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0099] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0100] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0101] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, terminal, network node, etc.

[0102] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input.

[0103] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0104] Furthermore, if the communication module 2013 includes a network node 100 (or terminal 10), the communication module 2013 can perform the operations of the aforementioned network node 100 (or terminal 10).

[0105] This specification discloses at least the configurations described in the following appendix.

[0106] <Notes> (Note 1) A network node comprising: a receiving unit that receives data related to terminals collected by a first network node; a control unit that performs pre-processing on the data for data storage; and a transmitting unit that transmits the pre-processed data to a second network node. (Note 2) The network node according to Note 1, wherein the pre-processing includes data abstraction processing, data anonymization processing, data reduction processing, or data encryption processing. (Note 3) The network node according to Note 1, which executes the pre-processing based on a policy set by the data management function. (Note 4) A network node comprising: a receiving unit that receives data from a first network node that stores data related to terminals; a control unit that performs post-processing on the data for data release; and a transmitting unit that transmits the post-processed data to a second network node. (Note 5) The network node according to Note 4, which executes the post-processing based on a policy set by the data management function. (Appendix 6) A communication method performed by a network node, comprising the steps of: receiving data related to a terminal collected by a first network node; performing preprocessing on the data for data storage; and transmitting the preprocessed data to a second network node.

[0107] Any of the appendices 1 to 6 provides technology that enables appropriate pre-processing or post-processing of the collected data. Appropriate pre-processing can be performed according to specific policies according to appendices 2, 3, and 5.

[0108] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the network node 100 and terminal 10 have been described using a functional block diagram, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the network node 100 according to an embodiment of the present invention and the software operated by the processor of the terminal 10 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0109] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0110] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0111] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0112] In this specification, specific operations performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with terminal 10 can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0113] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0114] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0115] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0116] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0117] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0118] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0119] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0120] The terms “system” and “network” as used in this disclosure are interchangeable.

[0121] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0122] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0123] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0124] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0125] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0126] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0127] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0128] Either the network node 100 or the terminal 10 may be called a transmitter, receiver, communication device, etc. Either the network node 100 or the terminal 10 may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. Furthermore, the mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0129] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 10 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 10 may have the functions that the base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0130] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0131] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0132] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0133] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0134] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0135] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0136] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0137] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0138] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0139] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0140] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0141] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0142] 10 Terminal, UE 11 DF 12 Data Collection Agent 20 RAN (Base Station) 21 DF 22 Data Collection Agent 30 TN 31 DF 32 Data Collection Agent 40 CN 41 DF 42 Data collection Agent 43 Data Management Function 44 Data Pre-processing Function 45 Data Storage 46 Data Post-processing Function 47 Data Exposure Function 50 Application service provider 51 Provisioning AF 52 Indirect Data Collection Client 53 Event Consumer AF 60 AS 70 NRF 80 NWDAF 90 NEF 100 Network Node 110 Transmitter 120 Receiver 130 Configuration Unit 140 Control Unit 210 Transmitter 220 Receiver 230 Configuration Unit 240 Control Unit 1001 Processor 1002 Storage Device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A network node comprising: a receiving unit that receives data related to terminals collected by a first network node; a control unit that performs pre-processing on the data for data storage; and a transmitting unit that transmits the pre-processed data to a second network node.

2. The network node according to claim 1, wherein the preprocessing includes data abstraction, data anonymization, data reduction, or data encryption.

3. The network node according to claim 1, wherein the network node performs the preprocessing based on a policy set by the data management function.

4. A network node comprising: a receiving unit that receives data from a first network node that stores data related to a terminal; a control unit that performs post-processing on the data for data release; and a transmitting unit that transmits the post-processed data to a second network node.

5. The network node according to claim 4, wherein the network node performs the post-processing based on a policy set by the data management function.

6. A communication method performed by a network node, comprising the steps of: receiving data related to a terminal collected by a first network node; performing preprocessing on the data for data storage; and transmitting the preprocessed data to a second network node.

Images