Base station, network node, and terminal

Abstract

To ensure continuity of data even when handover is executed in a wireless communication system.SOLUTION: A base station includes: a transmission part configured to transmit, to a network node, a handover related message including identification information associated with data collection by a terminal; and a reception part configured to receive, from the network node, data collected by data collection by the terminal and the identification information.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a base station, a network node and a terminal in a wireless communication system. [Background technology]

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is considering the application of artificial intelligence / machine learning (AIML) to wireless communication systems, and is discussing methods for collecting data from user equipment (UE) for training AIML models.

[0003] Here, after the handover is completed, the UE may report data collected before the handover to the target base station, which may include data that the UE wanted the source base station, which was serving the UE before the handover, to collect. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.331 V18.6.0(2025-06) Summary of the Invention [Problem to be solved by the invention]

[0005] However, when the UE reports the collected data to the target base station after the handover is completed and the target base station transfers the data to the source base station, the source base station may have already discarded the UE context. As a result, data continuity may not be maintained. In such a case, it is unclear how to transfer the data collected by the UE to the source base station that configured the data collection. [Means for solving the problem]

[0006] The base station in this embodiment comprises a transmitter that transmits a handover-related message to a network node, the handover-related message including identification information associated with data collection by the terminal, and a receiver that receives the data collected by the data collection by the terminal and the identification information from the network node. [Effects of the Invention]

[0007] According to this embodiment, data continuity can be ensured even when a handover is performed in a wireless communication system. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present invention. [Figure 2] FIG. 10 is a sequence diagram illustrating an example of an operation procedure of the wireless communication system according to the first embodiment of the present invention. [Figure 3] FIG. 10 is a sequence diagram illustrating an example of an operation procedure of a wireless communication system according to a second embodiment of the present invention. [Figure 4] FIG. 11 is a sequence diagram illustrating an example of an operation procedure of a wireless communication system according to a third embodiment of the present invention. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of an operation procedure of a wireless communication system according to a fourth embodiment of the present invention. [Figure 6] FIG. 11 is a sequence diagram illustrating an example of an operation procedure of a wireless communication system according to a fifth embodiment of the present invention. [Figure 7] 10 is a diagram showing an example of the structure of a handover-related message including a data collection ID in this embodiment. FIG. [Figure 8] 10 is a diagram showing an example of the configuration of a collected data transfer message including a data collection ID in the present embodiment. FIG. [Figure 9]10 is a diagram showing an example of the structure of a report message from a UE including a data collection ID in this embodiment. FIG. [Figure 10] 10 is a diagram showing an example of the structure of a report message from a UE including a data collection ID in this embodiment. FIG. [Figure 11] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station according to the present embodiment. [Figure 12] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal according to the present embodiment. [Figure 13] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station or a terminal according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] The present embodiment will be described below with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0010] In operation of the wireless communication system of this embodiment, existing technologies (e.g., LTE and NR (5G)) or future technologies (e.g., 6G) may be used as appropriate. The technologies used in the wireless communication system of this embodiment may not be limited to the above-mentioned LTE, NR, and 6G.

[0011] In the present embodiment described below, terms used in existing technologies, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. The above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0012] In this embodiment, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or other methods (for example, flexible duplex, etc.).

[0013] In this embodiment, when radio parameters etc. are "configured," it may mean that a predetermined value is pre-configured, or that radio parameters notified from a base station or a terminal are set.

[0014] (System Configuration) Fig. 1 is a diagram for explaining a wireless communication system in this embodiment. As shown in Fig. 1, the wireless communication system in this embodiment includes a base station (gNB) 10 and a terminal (UE (User Equipment)) 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0015] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. A TTI (Transmission Time Interval) in the time domain may be a slot, or a TTI may be a subframe. The base station 10 may also be referred to as a network node.

[0016] The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via the NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell) and a primary cell (PCell) using Carrier Aggregation (CA). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 by DC (Dual Connectivity) and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10. The base station 10 may be realized by a CU (Central Unit) / DU (Distributed Unit) split configuration.

[0017] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.

[0018] The wireless communication system includes a core network. The core network includes an AMF (Access and Mobility Management Function) 30. The AMF 30 is a network node with access and mobility management functions. The AMF 30 is connected to the base station 10 via an N2 interface and transmits and receives control information (registration, connection, mobility, etc.) for the UE 20. The AMF 30 selects an SMF (Session Management Function) that manages the data communication session of the UE 20 and cooperates with it to establish or change the session. The AMF 30 obtains authentication information, etc. from a UDM (Unified Data Management) that manages user subscription information and uses it in the authentication process.

[0019] The wireless communication system according to the present embodiment may support AIML functionality. AIML is a technology for learning, recognizing patterns, and making predictions based on data. An AIML model refers to a mathematical or algorithmic structure for realizing such AIML functionality. The AIML model may be trained using training data and configured to perform a specific task. The AIML model may be used in various functions (AIML functionality). The AIML functionality may include one or more functionalities selected from AIML for beam management, AIML for CSI prediction, AIML for CSI compression, AIML for positioning, and AIML for mobility.

[0020] In this embodiment, "data collection" means that the UE collects and stores data according to a configuration from the network. The data may be any data collected by the UE. For example, the data may be data used for training an AIML model, data on measurement results such as wireless quality by the UE, data indicating the processing load or power consumption status of the UE, or data used for mobility control. Data collection may be performed, for example, on a process basis, a process group basis including multiple processes, an event basis, a time basis, or any combination thereof.

[0021] In this embodiment, "reporting data" means that the UE transmits collected data to the network (cell) in which it is currently located (camped on).

[0022] In this embodiment, "forwarding data" means transmitting data received by a network node from a UE to another network node.

[0023] In this embodiment, "data continuity" refers to the association of data with a specific UE from which the data was collected, and may also refer to information about the category to which the UE that collected the data belongs. For example, if the network categorizes and lumps together data collected from UEs passing north of the antenna, "data continuity" indicates to which category the transferred data belongs.

[0024] In this embodiment, the "Source gNB" may be a network node that "instructed the UE to collect data but is not currently located in its coverage area" such as a gNB other than the Source gNB in ​​the handover or a CU / DU. For example, the Source gNB may be gNB#1 when the UE is handed over to gNB#1, gNB#2, and gNB#3 in that order, and the UE reports data collected at gNB#1 to gNB#3, and then reports it from gNB#3 to gNB#1, or when the UE reports it from gNB#3 to gNB#2, and then reports it from gNB#2 to gNB#1.

[0025] In this embodiment, the "Target gNB" may be a network node such as a gNB or CU / DU to which the UE will move during the handover, which has not instructed the UE to collect data but is currently located within its coverage area.

[0026] In the wireless communication system of this embodiment, at least one of the following (1) to (6) may be applied.

[0027] (1) When a Source gNB instructs a UE to collect data, it may assign a Data Collection ID to the data to be collected. The Source gNB may assign a Data Collection ID when instructing the UE to collect data, or when receiving a report from the UE. The Data Collection ID may be assigned per UE per data collection, per UE, or per UE category. For example, UE category #1 may represent UEs passing north of the antenna.

[0028] (2) When the Source gNB instructs the UE to collect data, it may also notify the UE of the data collection ID associated with that data collection.

[0029] (3) When a source gNB sends an Xn Application Protocol (XnAP) handover request message to a target gNB for a UE, the source gNB may also include in the message a data collection ID associated with the data collection currently configured for the UE. The XnAP handover request may be a procedure related to other mobility. The data collection ID may be explicitly included in the XnAP message or may be included as information not mentioned (INM). For example, it may be handover preparation information. The data collection ID may be explicitly included in an NG Application Protocol (NGAP) message or may be included as an INM. For example, the data collection ID may be included in an NGAP Handover Required / Handover Request message.

[0030] (4) When the Target gNB receives data collected from the UE and forwards the received data to the Source gNB, the Target gNB may include the data collection ID assigned by the Source gNB in ​​the message containing the received data. The data collection ID may be explicitly included in the Xn message or may be included in the INM. The data transfer may be performed using a UE Context Release message or by a new XnAP procedure. In this case, a non-UE associated procedure may be used. The assignment (assignment) of the data collection ID and the data transfer may be performed by an NGAP message. This may be a newly introduced message / procedure or an existing message / procedure.

[0031] (5) When reporting collected data to a gNB, the UE may include a data collection ID assigned by the gNB that configured the data collection or a data collection ID assigned by the gNB in ​​which the UE is located. A data collection ID associated with each piece of data may be included, or data associated with the same data collection ID may be reported together.

[0032] (6) When collecting data, the UE may collect each piece of data by linking it to a data collection ID assigned by the gNB that set up the data collection or a data collection ID assigned by the gNB in ​​which it is located.

[0033] Hereinafter, an embodiment will be described in which one or more of the above (1) to (6) are applied to a wireless communication system.

[0034] Example 1 The first embodiment is an example in which the above (1), (3), and (4) are applied to a wireless communication system. Fig. 2 is a sequence diagram showing an example of an operation procedure of the wireless communication system in the first embodiment. Fig. 2 shows an operation procedure of data collection and transfer in Xn handover by a UE 20 from an S-gNB (Source gNB) 10A to a T-gNB (Target gNB) 10B.

[0035] In step S101, the S-gNB 10A transmits a data collection configuration to the UE 20. The data collection configuration may include, for example, an instruction to cause the UE 20 to perform data collection and configuration information for data collection.

[0036] In step S102, the UE 20 performs data collection based on the received data collection setting.

[0037] In step S103, the UE 20 transmits an L3 measurement report to the S-gNB 10A. The L3 measurement report may include data collected at the UE 20 and a data collection ID assigned to the data collection. As described above, if the L3 measurement report does not include a data collection ID, the S-gNB 10A may assign a data collection ID to the collected data included in the L3 measurement report.

[0038] In step S104, the S-gNB 10A makes a handover (HO) decision based on the L3 measurement report, etc.

[0039] In step S105, the S-gNB 10A transmits a handover request including the data collection ID to the T-gNB 10B. The handover request may further include a data retain indication. The data retain indication included in the handover request is an instruction (determination result) by the S-gNB 10A indicating whether data collected by the UE 20 should be retained in the UE 20 after handover.

[0040] In step S106, the T-gNB 10B transmits an Ack (acknowledgement) to the S-gNB 10A in response to the handover request. This Ack includes a data retention indication. The data retention indication included in the Ack is an instruction (determination result) by the T-gNB 10B indicating whether data collected by the UE 20 should be retained in the UE 20 after handover.

[0041] In step S107, the handover procedure is performed.

[0042] In step S108, after the handover, the UE 20 reports the collected data to the T-gNB 20.

[0043] In step S109, the T-gNB 10B transmits a collected data transfer message including the collected data from the UE 20 to the S-gNB 10A. The collected data transfer message includes the data collection ID received in step S105. In this way, the T-gNB 10B associates the collected data with the data collection ID notified by the S-gNB 10A, and includes the data collection ID in the collected data transfer message.

[0044] As described above, according to the first embodiment, the S-gNB 10A can receive data collected by the UE 20 even after handover. The first embodiment is an example in which a data collection ID is applied to a handover procedure via the Xn interface. This configuration enables the source gNB to receive collected data reported by the user equipment (UE) to the target gNB even after handover. This prevents interruption of data collection due to handover and maintains data continuity.

[0045] Example 2 The second embodiment is an example in which the above (1), (3), and (4) are applied to a wireless communication system. Fig. 3 is a sequence diagram showing an example of an operation procedure of the wireless communication system in the second embodiment. Fig. 3 shows an operation procedure of data collection and transfer in NG handover performed via a core network (e.g., AMF 30).

[0046] In step S1001, the S-gNB 10A sends data collection configuration to the UE 20.

[0047] In step S1002, the UE 20 performs data collection based on the received data collection setting.

[0048] In step S1003, the UE 20 transmits an L3 measurement report to the S-gNB 10A.

[0049] In step S1004, the S-gNB 10A decides on a handover based on the L3 measurement report, etc.

[0050] In step S1005, S-gNB 10A sends a handover request (Handover Required) to AMF 30, including a data collection ID and a data retention indication.

[0051] In step S1006, the AMF 30 sends a handover request to the T-gNB 10B. The handover request includes the data collection ID and data retention indication sent from the S-gNB 10A.

[0052] In step S1007, the T-gNB 10B sends an Ack (acknowledgment) to the AMF 30 in response to the handover request.

[0053] In step S1008, AMF 30 sends a handover command to S-gNB 10A.

[0054] In step S1009, a handover procedure is performed between the UE 20, the S-gNB 10A and the T-gNB 10B.

[0055] In step S1010, after the handover, the UE 20 reports the collected data to the T-gNB 10B.

[0056] In step S1011, the T-gNB 10B transmits a collection data forwarding message including the collected data from the UE 20 to the AMF 30. The collection data forwarding message includes the data collection ID received in step S1006. In this way, the T-gNB 10B associates the collected data with the data collection ID notified by the S-gNB 10A via the AMF 30, and includes the data collection ID in the collection data forwarding message.

[0057] In step S1012, the AMF 30 sends a collection data transfer message from the T-gNB 10B to the S-gNB 10A. The collection data transfer message includes the collected data and a data collection ID.

[0058] The second embodiment is an example in which a data collection ID is applied to an NG interface handover via a core network (AMF). With this configuration, even in the case of a handover via the core network, the source gNB can receive collected data transferred from the target gNB after the handover. As with the first embodiment, this avoids interruption of data collection due to handover and ensures data continuity.

[0059] Example 3 The third embodiment is an example in which the above (1), (3), and (4) are applied to a wireless communication system. Fig. 4 is a sequence diagram showing an example of an operation procedure of the wireless communication system in the third embodiment. Fig. 4 shows an example of data transfer when a UE 20 moves between multiple gNBs.

[0060] In step S201, gNB#1 (10A) sends data collection settings to UE 20.

[0061] In step S202, the UE 20 performs data collection based on the received data collection setting.

[0062] In step S203, the UE 20 transmits an L3 measurement report to the gNB#1.

[0063] In step S204, gNB#1 decides to perform a handover.

[0064] In step S205, gNB#1 transmits a handover request including a data collection ID to gNB#2 (10B).

[0065] In step S206, a handover procedure is performed between UE 20, gNB#1 and gNB#2.

[0066] In step S207, gNB#2 sends a handover request including the data collection ID received in step S205 to gNB#3 (10C).

[0067] In step S208, a handover procedure is performed between UE 20, gNB#1, gNB#2 and gNB#3.

[0068] In step S209, UE 20 reports the collected data to gNB#3.

[0069] In step S210, gNB#3 transmits to gNB#2 a collection data transfer message including the collected data from UE 20. The collection data transfer message includes the data collection ID received in step S207. In this way, gNB#3 associates the collected data with the data collection ID notified from gNB#1 via gNB#2, and includes the data collection ID in the collection data transfer message.

[0070] In step S211, gNB#2 transmits a collection data transfer message from gNB#3 to gNB#1. The collection data transfer message includes the collected data and a data collection ID.

[0071] In the above step S209, if UE 20 retains collected data but moves to gNB#3 without ever reporting the collected data to gNB#2, the data reported to gNB#3 may include data collected when gNB#1 was in service. In such a case, in step S210, gNB#2 receives data from gNB#3, and in step S211, gNB#2 may further forward the received data to gNB#1.

[0072] Example 3 is an example in which a data collection ID is applied to a scenario in which a UE successively handovers between multiple gNBs. With this configuration, even if the UE moves via multiple base stations, by using the data collection ID, the gNB (gNB#1) that originally instructed data collection can ultimately receive data from the gNB (gNB#3) where the UE is located. This makes it possible to reliably track and forward data collection even in a complex mobility environment.

[0073] Example 4 The second embodiment is an example in which the above (1), (2), (4), (5), and (6) are applied to a wireless communication system. Fig. 5 is a sequence diagram showing an example of an operation procedure of the wireless communication system in the fourth embodiment. Fig. 5 shows an operation procedure related to data collection setting including a data collection ID and handover.

[0074] In step S301, the S-gNB 10A transmits a data collection configuration including a data collection ID to the UE 20. The S-gNB 10A assigns a data collection ID for data collection by the UE 20 and includes the assigned data collection ID in the data collection configuration.

[0075] In step S302, the UE 20 performs data collection based on the received data collection setting, and stores the collected data in association with the data collection ID included in the data collection setting.

[0076] In step S303, the UE 20 transmits an L3 measurement report to the S-gNB 10A.

[0077] In step S304, the S-gNB 10A decides to perform a handover.

[0078] In step S305, the S-gNB 10A transmits a handover request including a data retention indication to the T-gNB 10B. The data retention indication included in the handover request is an instruction (determination result) by the S-gNB 10A indicating whether data collected by the UE 20 should be retained in the UE 20 after handover.

[0079] In step S306, the T-gNB 10B sends an Ack in response to the handover request to the S-gNB 10A. This Ack includes a data retention indication. The data retention indication included in the Ack is an instruction (determination result) by the T-gNB 10B indicating whether data collected by the UE 20 should be retained in the UE 20 after handover.

[0080] In step S307, a handover procedure is performed between the UE 20, the S-gNB 10A and the T-gNB 10B.

[0081] In step S308, the UE 20 reports the data collection ID and the data stored in association with the data collection ID to the T-gNB 10B.

[0082] In step S309, the T-gNB 10B transfers the collected data to the S-gNB 10A. The data transfer may include a data collection ID and the collected data. The T-gNB 10B sends a collection data transfer message including the collected data from the UE 20 to the S-gNB 10A. The collection data transfer message includes the data collection ID received in step S308. In this way, the T-gNB 10B associates the collected data with the data collection ID sent from the UE 20 (i.e., the data collection ID assigned by the S-gNB 10A) and includes the data collection ID in the collection data transfer message.

[0083] In the fourth embodiment, the source gNB directly notifies the UE of the data collection ID, and the UE reports the ID in association with the data. This configuration allows the UE to manage the data collection ID itself, and when reporting data to the target gNB after handover, it can include the ID in the data. As a result, the target gNB can correctly forward the received data to the source gNB that originally instructed data collection. This clarifies the attribution of data even after handover, ensuring data continuity.

[0084] Example 5 The fifth embodiment is an example in which the above (1), (2), (4), (5), and (6) are applied to a wireless communication system. Fig. 6 is a sequence diagram showing an example of an operation procedure of the wireless communication system in the fifth embodiment. Fig. 6 shows an operation procedure related to the collection and reporting of data corresponding to a plurality of data collection IDs.

[0085] In step S401, the S-gNB 10A transmits a data collection setting including a data collection ID (e.g., ID#1) to the UE 20. The S-gNB 10A assigns the data collection ID#1 to data collection by the UE 20 and includes the assigned data collection ID#1 in the data collection setting.

[0086] In step S402, the UE 20 performs data collection based on the received data collection setting, and stores the collected data in association with the data collection ID #1 included in the data collection setting.

[0087] In step S403, the UE 20 transmits an L3 measurement report to the S-gNB 10A.

[0088] In step S404, the S-gNB 10A decides to perform a handover.

[0089] In step S405, S-gNB 10A sends a handover request to T-gNB 10B, including data collection ID #1 and a data retention indication.

[0090] In step S406, the T-gNB 10B transmits an Ack (acknowledgement) to the S-gNB 10A in response to the handover request. This Ack includes a data retention indication. The data retention indication included in the Ack is an instruction (determination result) by the T-gNB 10B indicating whether data collected by the UE 20 should be retained in the UE 20 after handover.

[0091] In step S407, a handover procedure is performed between the UE 20, the S-gNB 10A and the T-gNB 10B.

[0092] In step S408, the T-gNB 10B transmits a data collection setting including the data collection ID #2 to the UE 20. The UE 20 performs data collection based on the data collection setting, and retains (stores) the collected data in association with the data collection ID #2 included in the data collection setting.

[0093] In step S409, the UE 20 reports the collected data corresponding to data collection ID #1 to the T-gNB 10B. In step S410, the UE 20 reports the collected data corresponding to data collection ID #2 to the T-gNB 10B. In this way, the UE 20 can report the collected data to the T-gNB 10B individually for each data collection ID associated with the data.

[0094] In step S411, T-gNB 10B transfers to S-gNB 10A, of the data reported from UE 20, the data corresponding to data collection ID #1 notified by S-gNB 10A in step S405. In this way, when the data collection ID transmitted from UE 20 is the same as the data collection ID notified by S-gNB 10A, T-gNB 10B may transmit the collected data and data collection ID to S-gNB 10A.

[0095] Example 5 is an example in which a UE manages and reports data corresponding to multiple data collection IDs. With this configuration, even if a UE receives multiple data collection settings simultaneously, each piece of data can be managed by linking it to the corresponding data collection ID. Furthermore, after handover, the target gNB can identify which data was collected by instruction from which source gNB using the data collection ID, and transfer the data to the appropriate source gNB. This makes it possible to maintain the consistency of each piece of data even in a complex environment where multiple data collections are performed in parallel.

[0096] (Example of a handover-related message including a data collection ID) As shown in Examples 1, 3, and 5 above, the data collection ID may be explicitly included in an XnAP message sent from a gNB (e.g., S-gNB 10A) to another gNB (e.g., T-gNB 10B) or may be included as an INM. The XnAP message is, for example, an XnAP Handover Request message. The XnAP Handover Request may also be a message / procedure related to other mobility.

[0097] For example, the data collection ID may be included as the IE "dataCollectionId-r19 HandoverPreparationInformation" in HandoverPreparationInformation, as shown in FIG.

[0098] As shown in the above Example 2, the data collection ID may be explicitly included in the NGAP message transmitted between the gNB and the AMF or may be included as an INM. The NGAP message is, for example, a Handover Required message or a Handover Request message.

[0099] (Example of a message structure for transferring collected data including a data collection ID) As shown in Examples 1-5 above, when the T-gNB 10B sends a transfer message including collected data from the UE 20 to the S-gNB 10A, the T-gNB 10B includes in the transfer message a data collection ID assigned by the S-gNB 10A. The data collection ID included in the collection data transfer message may be explicitly included in an XnAP message sent between the gNB and another gNB, or may be included as an INM.

[0100] As shown in Fig. 8, the data collection ID included in the collection data transfer message may be set as "UE Data Collection ID." Furthermore, the data collection ID may be included in the RRC Container.

[0101] (Example of the configuration of a report message from a UE including a data collection ID) As shown in Examples 4 and 5, the data collection ID may be transmitted together with the collected data reported from the UE 20 to the gNB 10 (e.g., T-gNB 10B). The report from the UE 20 may include a data collection ID associated with each piece of collected data, or may be reported together for each piece of data associated with the same data collection ID.

[0102] For example, as shown in Fig. 9, in a report from the UE 20, for example, a data collection ID "dataCollectionId" may be assigned to each set of collected data and stored. For example, as shown in Fig. 10, in a report from the UE 20, a data collection ID "dataCollectionId" may be stored for each piece of data.

[0103] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station (gNB) 10 and the terminal (UE) 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions to execute the above-described embodiments. However, the base station 10 and the terminal 20 may each have only some of the functions of the embodiments. The AMF 30 may have the same functions as the base station 10.

[0104] <Base station (gNB)> Fig. 11 is a diagram showing an example of the functional configuration of the base station 10 in this embodiment. As shown in Fig. 11, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 11 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations in this embodiment. The transmitting unit 110 and the receiving unit 120 may be collectively referred to as a communication unit.

[0105] The transmitter 110 includes a function to generate a signal to be transmitted to the terminal 20 and transmit the signal wirelessly. The transmitter 110 transmits setting information, instructions, notifications, etc. related to the low-power wake-up signal to the terminal 20. The transmitter 110 transmits notifications related to switching of monitoring operations to the terminal. The receiver 120 includes a function to receive various signals transmitted from the terminal 20 and obtain, for example, information of higher layers from the received signals. The transmitter 110 has a function to transmit PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 receives inter-network node messages from other network nodes.

[0106] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information on the operations explained in the embodiments.

[0107] The control unit 140 controls the settings, instructions, and notifications related to the operations described in the embodiments. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0108] <Device (UE)> Fig. 12 is a diagram showing an example of the functional configuration of the terminal 20 in this embodiment. As shown in Fig. 12, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 12 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations in this embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

[0109] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitter 210 transmits capability information in a low-power wake-up signal to the base station 10. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 has a function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiver 220 receives paging notification information and setting information, instructions, notifications, etc. related to the low-power wake-up signal from the base station 10. For example, the receiver 220 receives a low-power wake-up signal from the base station 10. The setting unit 230 stores various setting information received from the base station 10 by the receiver 220. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information on the operations described in the embodiments.

[0110] As described in the embodiments, the control unit 240 controls settings, instructions, and notifications related to the operations described in the embodiments. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0111] (Hardware configuration) The block diagrams (FIGS. 11 and 12) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by hardware, software, or a combination of these. The method for realizing each functional block is not particularly limited. That is, each functional block may be realized by using a single device that is physically or logically coupled, or may be realized by using two or more physically or logically separated devices that are connected directly or indirectly (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0112] For example, the base station, terminal, network node, etc. in this embodiment may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram showing an example of the hardware configuration of a base station and a terminal in one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0113] In the present disclosure, the term "apparatus" may be interchangeable with any two terms selected from a set of terms such as circuit, device, unit, module, chip, means, etc. The hardware configurations of the base station 10 and the terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0114] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls the reading, writing, or both reading and writing of data in the memory 1002 and storage 1003.

[0115] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, a baseband signal processing unit, a call processing unit, etc. may be realized by the processor 1001. Although only one processor 1001 is shown in the figure, there may be multiple processors.

[0116] The processor 1001 reads programs (program codes), software modules, data, etc. from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by a single processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line, or may be provided to the computer via the communication device 1004, for example.

[0117] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).

[0118] The memory 1002 is a computer-readable recording medium and may be configured, for example, as a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), or a combination of at least two of these. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), or the like. The memory 1002 can store executable programs (program codes), software modules, and the like for executing the wireless communication method according to one embodiment of the present disclosure.

[0119] Storage 1003 is a computer-readable recording medium, and may be, for example, an optical disk 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 versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, or a combination of at least two of these. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, memory 1002, storage 1003, or a database, server, or other appropriate medium including both memory 1002 and storage 1003.

[0120] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, or a combination of at least two of these. For example, a transmitting / receiving antenna, an amplifier unit, a transmitting / receiving unit, or a transmission path interface may be realized by the communication device 1004. The transmitting / receiving unit may be implemented as a transmitting unit and a receiving unit that are physically or logically separated.

[0121] The input device 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or a combination of at least two of these). The output device 1006 is an output device that executes output to the outside (for example, a display, a speaker, an LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0122] The processor 1001, memory 1002, and other devices are connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between the devices.

[0123] The base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0124] <Additional notes> (Additional note 1) a transmitter configured to transmit a handover-related message to a network node (e.g., a T-gNB 10B or an AMF 30) including identification information associated with data collection by a terminal (e.g., a UE 20); A base station (e.g., S-gNB 10A) comprising: a receiving unit that receives the data collected by the terminal through the data collection and the identification information from the network node.

[0125] (Additional note 2) the transmission unit transmits setting information instructing the terminal to collect the data, The base station described in Supplementary Claim 1, wherein the setting information includes the identification information associated with the data collection.

[0126] (Additional note 3) The base station described in Supplementary Claim 1, wherein the network node is a target base station in a handover or a network node having access and mobility management functions.

[0127] (Additional note 4) a receiver for receiving a handover-related message from a base station, the handover-related message including identification information associated with data collection by the terminal; a transmitter configured to transmit the data collected by the terminal and the identification information to the base station.

[0128] (Additional note 5) the receiving unit receives data collected by the data collection and identification information associated with the data collection from the terminal; The network node described in Supplementary Claim 4, wherein the transmitter transmits the collected data and the identification information to the base station when the identification information transmitted from the terminal is the same as the identification information included in the handover-related message.

[0129] (Additional note 6) a receiving unit that receives, from a base station, a data collection instruction and setting information including identification information associated with the data collection; a control unit that performs the data collection based on the setting information and manages the data collected by the data collection in association with the identification information; a transmitter that transmits the data collected by the data collection and the identification information to a target base station in handover.

[0130] According to the configuration described in the supplementary paragraph, data continuity can be ensured even when a handover is executed in a wireless communication system.

[0131] (Supplementary explanation of the embodiment) Although the present embodiment has been described above, the disclosed invention is not limited to such an embodiment, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0132] The aspects / embodiments described in the present disclosure may be categorized as Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (x is, for example, an integer or a decimal number)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (O-RAN), Wideband Code Division Multiple Access (W-CDMA) (registered trademark), Global System for Mobile communications (GSM) (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) Engineers) 802.11, IEEE802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x=n it is called Wi-Fi4, when x=ac it is called Wi-Fi5, when x=ax it is called Wi-Fi6 or Wi-Fi6E, when x=be it is Wi-Fi7, and when x=bn it is called Wi-Fi8, etc. Wi-Fi is a registered trademark.), IEEE802.16 (WiMAX (registered trademark), IEEE802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), network virtualization technology (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Of course, "based on" may refer not only to a system that uses the technology, but also to a system that uses an extension or modification of the technology.

[0133] In the present disclosure, any two terms selected from a set of terms such as "base station (BS)", "radio base station", "fixed station (fixed station)", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point (AP)", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "radio unit (RU)", "remote unit (RU)", "control unit (CU)", "distributed unit (DU)", "remote radio head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "high altitude platform station (HAPS)", "airborne platform", "panel", "cell", "radio access network (RAN)", and "network" may be used interchangeably.

[0134] Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, or a super cell. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0135] In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE 20)", "Device", "Module" and "Terminal" may be used interchangeably.

[0136] A terminal may be referred to 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, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other suitable terminology.

[0137] The base station and the terminal may each be composed of one or more devices. The devices constituting at least a portion of the base station and the terminal may be called a transmitting device, a receiving device, a communication device, etc. Note that the devices constituting at least a portion of the base station and the terminal may be, for example, an object itself, such as a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an unmanned aerial vehicle, a stratospheric base station (e.g., a High Altitude Platform Station (HAPS)), an artificial satellite (e.g., a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a Geostationary Earth Orbit (GEO) satellite), a drone (registered trademark), a multicopter, a quadcopter, a balloon, or an Internet of Things (IoT) device (e.g., a smart meter, a sensor), or may include, but are not limited to, an object or device mounted on the object. The object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is in a stationary state where it is not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0138] A base station in the present disclosure may be read as a terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)) or communication of a non-terrestrial network (NTN). In this case, the terminal 20 may be configured to have at least some of the functions of the base station 10 described above. Terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be read as a sidelink channel.

[0139] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the ground (for example, in the atmosphere or outer space).

[0140] In this disclosure, the term "terminal" may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the terminal 20 described above.

[0141] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination of at least two of these. Note that the physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU), for example. The RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC message may be, for example, a message used for controlling an RRC connection (for example, setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a Measurement Report, or notification of a terminal's capabilities, or may be an information element within the message. Notification of information may be explicit or implicit. Note that explicit notification of certain information means notification of the certain information itself, and implicit notification of certain information may mean notification of information other than the certain information, or may mean that the certain information is considered to have been notified when a certain condition is satisfied.Notification of information may include not only notification between the same layers of different devices (e.g., between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (e.g., between a lower layer and an upper layer in the base station 10 or the terminal 20). Notification of information from one device to another device may be performed via one or more devices. With regard to any information (e.g., a variable, a constant, a parameter, a setting) described in the present disclosure, even if not specifically specified in the above embodiments, information indicating / specifying (or related to) the any information (value) may be notified from any first device (e.g., a terminal / base station) to any second device (e.g., a base station / terminal).

[0142] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0143] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, or DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provides one or more network functions (NF: Network Functions), but is not limited to this.

[0144] In the present disclosure, the action of "a terminal receives information from a base station" accompanies the action of "the base station transmits the information to the terminal", "the base station generates the information", or both. Similarly, the action of "a terminal transmits information to a base station" accompanies the action of "the base station receives the information from the terminal". The actions of "the terminal is configured to..." or "configure UE 20 to..." may include the action of "the base station transmits configuration information regarding the configuration of the terminal" and the action of "the terminal configures a predetermined operation based on the configuration information".

[0145] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation.

[0146] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.

[0147] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0148] The radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.

[0149] For example, resources in the time domain may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. The time unit may be a fixed-length time unit independent of numerology, a variable-length time unit dependent on numerology, or both. Examples of fixed-length time units include, but are not limited to, a subframe consisting of one or more slots and a radio frame including multiple subframes. Examples of variable-length time units include, but are not limited to, a symbol and a slot including a fixed number of symbols. Note that a certain time unit may be divided into time units shorter than the certain time unit. Examples of shorter time units include, but are not limited to, a minislot consisting of fewer symbols than the number of symbols constituting a slot. The above-described time units may include, for example, time units used as units for scheduling, link adaptation, etc. Any time unit in the present disclosure may be read as another time unit.

[0150] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time, for example.

[0151] Resources in the frequency domain may be defined, for example, by one or more frequency units. The one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the terminology of the frequency units is not limited to these. The number of subcarriers included in a frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology. For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. A BWP may be composed, for example, of one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Any frequency unit in the present disclosure may be interchangeable with another frequency unit.

[0152] Resources in both the time domain and the frequency domain may be defined by one or more time / frequency units, each of which is composed of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) composed of one symbol and one subcarrier, a resource element group (REG) composed of a predetermined number of REs, or a control resource set (CORESET) composed of a predetermined number of symbols and a predetermined number of RBs.

[0153] The resources in the spatial domain may be defined, for example, by one or more spatial units, including, but not limited to, a beam, a layer of a multi-input multi-output (MIMO), an antenna port, or a combination of at least two of these.

[0154] The resources in the code domain may be defined by one or more code units, such as, but not limited to, a cyclic shift (CS), an orthogonal cover code (OCC), or a combination thereof.

[0155] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0156] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc. [Explanation of symbols]

[0157] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device

Claims

1. a transmitter for transmitting a handover-related message to a network node, the message including identification information associated with data collection by the terminal; a receiving unit that receives the data collected by the terminal through the data collection and the identification information from the network node.

2. the transmission unit transmits setting information instructing the terminal to collect the data, The base station of claim 1 , wherein the configuration information includes the identification information associated with the data collection.

3. The base station according to claim 1 , wherein the network node is a target base station in a handover or a network node having access and mobility management functionality.

4. a receiver for receiving a handover-related message from a base station, the handover-related message including identification information associated with data collection by the terminal; a transmitter configured to transmit the data collected by the terminal and the identification information to the base station.

5. the receiving unit receives data collected by the data collection and identification information associated with the data collection from the terminal; 5. The network node according to claim 4, wherein the transmitter transmits the collected data and the identification information to the base station when the identification information transmitted from the terminal is the same as the identification information included in the handover-related message.

6. a receiving unit that receives, from a base station, a data collection instruction and setting information including identification information associated with the data collection; a control unit that performs the data collection based on the setting information and manages the data collected by the data collection in association with the identification information; a transmitter that transmits the data collected by the data collection and the identification information to a target base station in handover.

Images