Terminal, network node, and communication method

Abstract

This terminal comprises a transmission unit that transmits, to a network node, a registration request for data collection using renewable energy, and a reception unit that receives, from the network node, a response indicating completion of registration after the network node performs the registration.

Description

Terminal, 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 increase in system capacity, further increase 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 corresponding 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.

[0004] 3GPP TS 23.501 V18.7.0 (2024-09)3GPP TS 23.502 V18.7.0 (2024-09)3GPP TS 23.548 V18.7.0 (2024-09)3GPP TS 23.434 V18.9.0 (2024-06)

[0005] In both AI and sensing, it is necessary to collect data from UEs, etc. Also, the types and characteristics of data used in AI or sensing vary depending on the use case. Therefore, in AI or sensing, it is required to collect data in a method that matches the types and characteristics of data corresponding to the use case. However, in the prior art, data collection cannot be performed in a method corresponding to the use case.

[0006] This invention has been made in view of the above points, and aims to provide a technology that enables data collection in a manner appropriate to the use case.

[0007] According to the disclosed technology, a terminal is provided comprising a transmitting unit that transmits a registration request for data collection using renewable energy to a network node, and a receiving unit that receives a response from the network node indicating the completion of registration after the network node has performed the registration.

[0008] The disclosed technology provides a method that enables data collection in a way that is tailored to the use case.

[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 a problem. This is a diagram illustrating an overview of the first embodiment. This is a diagram illustrating examples of existing 5QIs and newly added 5QIs. This is a diagram illustrating that 7, indicating data collection, has been added as a value for SST (Slice / Service type). This is a diagram illustrating the processing sequence in the first embodiment. This is a diagram illustrating NSSAI. This is a diagram illustrating an overview of the second embodiment. This is a diagram illustrating the SEAL architecture. This is a diagram illustrating the processing sequence in the second embodiment. This is a diagram illustrating an example of the functional configuration of the network node 100 in an embodiment of the present invention. This is a diagram illustrating an example of the functional configuration of the terminal 20 in an embodiment of the present invention. This is a diagram illustrating an example of the hardware configuration of the terminal 20 and the network node 100 in an embodiment of the present invention. This is a diagram illustrating an example of the configuration of the 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 20 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 (Terminal 20) and multiple network nodes. A configuration including one or more network nodes may be referred to as a "network." Hereafter, one network node will be assigned to each function, but one network node may implement multiple functions, or multiple network nodes may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection. In addition, although Figure 1 shows a 5G core network, all or some of the network nodes in the core network shown in Figure 1 may also be used in 6G.

[0014] The RAN (Radio Access Network) 10 is a network node with wireless access functionality, which may include a base station 10, and is connected to the UE 20, AMF (Access and Mobility Management Function) 30, and UPF (User plane function) 50. The AMF 30 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. The UPF 50 is a network node that interconnects with the DN (Data Network) 60 and has functions such as a PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF 50 and DN 60 constitute a network slice.

[0015] AMF30 is connected to UE20, RAN10, SMF (Session Management function)40, 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)70, AF (Application Function)80, and UDR (User Data Repository). AMF30, SMF40, NSSF, NEF, NRF, UDM, AUSF, PCF70, AF80, 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] SMF40 is a network node with functions such as session management, IP (Internet Protocol) address allocation and management for UE20, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. NEF is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. NSSF is a network node with functions such as selecting the network slice to which UE20 connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be configured, and determining the AMF set to which UE20 connects. PCF70 is a network node with the function of controlling network policies. AF80 is a network node with the function of controlling application servers. NRF is a network node with the function of discovering NF instances that provide services. UDM is a network node that manages subscriber data and authentication data. UDM is connected to UDR, which holds the said data. Furthermore, AF80 can also be referred to as an 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 20 (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 challenges) As mentioned above, 5G provides communication tailored to use cases such as eMBB, URLLC, and mMTC. In 6G, the future communication system, in addition to providing services similar to 5G, services such as AI and sensing will also be provided.

[0021] Both AI and sensing require data collection from sources such as user interfaces (UEs). Furthermore, the types and characteristics of data used in AI or sensing vary depending on the use case. In other words, AI and sensing require data collection methods tailored to the specific data types and characteristics of each use case. Figure 3 illustrates this challenge.

[0022] The following describes the first and second embodiments as technologies for solving the above-mentioned problems. In the embodiments described below, it is assumed that the technology according to the present invention is applied to a 6G communication system, but the application of the technology according to the present invention is not limited to 6G. The technology according to the present invention can also be applied to communication systems other than 6G (e.g., 5G, LTE, 3G, and the next communication system after 6G). Furthermore, in the following description, the operation based on the 5G specification can also be executed in the 6G communication system assumed in this embodiment.

[0023] The second embodiment is implemented in combination with the first embodiment. However, the second embodiment may be implemented independently of the first embodiment.

[0024] (First Embodiment) <First Embodiment: 5QI and Slicing> In existing 5G technology, 5QI (5G network Quality of service class Identifier) ​​is defined to indicate the quality of service of communication. Network nodes in 5GC identify which QoI flow a packet belongs to based on the QFI (QoS Flow Identifier) ​​set for the packet, and process the packet according to the QoS requirements of the 5QI set for each QoS flow. Note that a QoS flow is a flow included in a PDU session.

[0025] However, 5G does not define a QoS specifically for data collection. Therefore, in the first embodiment, 5QI for data collection is defined and used. As a result, as shown in Figure 4, QoS settings can be configured for the 6G system network according to the type of data to be collected from the UE. Figure 4 shows the network node that performs data collection in the 6G system. In other words, data transmitted from the UE is sent to the network node that performs data collection using a communication channel with the configured quality of service.

[0026] Figure 5 shows examples of the existing 5QIs and the newly added 5QIs. Figure 5 shows the QoS requirements for each of the 5QIs. 5QIs 1-9 in Figure 5 are the existing 5QIs, while 5QIs 11 and 12 are the newly added 5QIs. In the examples in Figure 5, a smaller priority number indicates a higher priority.

[0027] As shown in Figure 5, both 5QI=11 and 5QI=12 are 5QIs for data collection, with 5QI=11 being a higher priority data collection tool than 5QI=12. 5QI=12 is used, for example, in use cases where data collection is performed in batch processing. Note that the numbers "11" and "12" are just examples, and other numbers may be used. GBR (Guaranteed Bit Rate) indicates that the bit rate is guaranteed.

[0028] Furthermore, in the first embodiment, data collection may be defined as the network slicing type. As a specific example, as shown in Figure 6, 7 is added as the SST (Slice / Service type) value to indicate data collection. In the example in Figure 6, a slice with SST value = 7 is a slice suitable for data collection.

[0029] <First Embodiment: Processing Sequence> The processing sequence in the first embodiment will be described with reference to Figure 7. Figure 7 shows the processing procedure in a communication system having UE20, RAN10, and CN (Core Network)90. CN90 is a system having multiple network nodes (AMF30, SMF40, UPF50, UDM, etc.) as shown in Figure 1. This system may also be called a "network node".

[0030] In S101, UE20 is registered with CN90 (specifically AMF30) by a registration procedure disclosed, for example, in Non-Patent Document 2 (TS23.502). In S102, a PDU session (logical communication channel) is established between UE20 and CN90 (specifically UPF50). The QoS in this PDU session (specifically QoS flow) is set by a predetermined Default 5QI.

[0031] In steps S103 to S106, the PDU session modification procedure changes the 5QI of the PDU session established in S102 from the default 5QI to the 5QI for data collection.

[0032] Specifically, in S103, UE20 sends a PDU session modification request to RAN10. A PDU session modification request is an example of a communication request. This request includes, as an example of an identifier representing the quality of service for data collection, five QIs (e.g., 11 or 12) corresponding to data collection.

[0033] In S104, RAN10 selects AMF30 as the destination for the PDU session modification request. In S105, RAN10 sends a PDU session modification request to CN90 (specifically AMF30 selected in S104), which includes the 5QIs corresponding to the data collection. In S106, the 5QIs in the PDU session are changed to the 5QIs corresponding to the data collection according to the PDU session modification procedure after the PDU session modification request has been sent to AMF30 (e.g., Figure 4.3.3.2-1 in Non-Patent Literature 2).

[0034] Subsequently, the data transmitted from UE20 is sent to the network node performing data collection using a communication channel with a quality of service suitable for data collection.

[0035] <First Embodiment: Network Slicing> As mentioned above, in the first embodiment, "7: Data collection" is added to the SST value (Slice / Service Type value). The SST value is a value that indicates the classification or behavior of a slice, and together with the SD (Slice Differentiator, a value for distinguishing slices), it constitutes S-NSSAI (Single-Network Slice Selection Assistance Information). In other words, "S-NSSAI = SST value + SD". S-NSSAI is also called the slice ID.

[0036] In step 1 of the Registration procedure shown in Fig. 4.2.2.2.2-1 of Non-Patent Document 2, UE20 sends Configured NSSAI and Requested NSSAI to RAN10. These NSSAIs include the SST value (e.g., 7). The NSSAIs are also used in subsequent procedures. Finally, the UE20 is notified of any available NSSAIs from the network side.

[0037] When establishing or modifying a PDU session, UE20 can communicate using the communication channel that utilizes the available slice by sending a request to the network that includes an S-NSSAI indicating the available slice.

[0038] Figure 8 shows the inter-node communication regarding NSSAI. NSSAI is a collection of slice IDs (S-NSSAI). Subscribed S-NSSAIs are identifiers that indicate slices held in the user's contract information. Default S-NSSAI is an identifier that indicates the slice set as default among Subscribed S-NSSAIs. Requested NSSAI is an identifier that indicates the slice requested by the UE in Registration. Allowed NSSAI is an NSSAI among the Requested NSSAI that has been permitted by the NW. Configured NSSAI is an identifier that indicates the slice available in PLMN configured on the UE. Rejected NSSAI is an identifier that indicates the slice that has been rejected by the NW.

[0039] <Effects of the First Embodiment> According to the technology of the first embodiment, it becomes possible to perform data communication with QoS suitable for data collection corresponding to the use case. As a result, for example, data collection can be realized without consuming network resources more than necessary.

[0040] That is, in 6G, data transmission and data collection tailored to more refined classification of data types such as AI and sensing are required. With the technology in the first embodiment, efficient and flexible data collection according to use cases becomes possible.

[0041] The PDU session (communication path) in the subsequent embodiments is assumed to have a service quality suitable for data collection by the technology described in the first embodiment. However, the PDU session (communication path) in the subsequent embodiments may have an existing service quality.

[0042] (Second Embodiment) <Second Embodiment: Overview> Next, the second embodiment will be described. These days, energy efficiency improvement (Energy efficiency) and CO2 reduction have been attracting attention from the perspective of promoting sustainability. In the 5G era, operators (communication carriers) have begun to work on CO2 reduction from the sustainability perspective.

[0043] In the 6G era, in order to contribute more to CO2 reduction, a network configuration considering energy efficiency and CO2 reduction is required. That is, in 6G, a mechanism that can actively utilize renewable energy is required. Note that renewable energy may also be referred to as Green energy. Renewable energy / Green energy is energy generated from sunlight, wind power, hydropower, geothermal energy, biomass, and the like.

[0044] In the second embodiment, a mechanism from the Energy perspective is introduced in data collection. For example, as shown in FIG. 9, the network node (node within the 6G system) that collects data performs data collection only during the time when it is operating with Green energy. In the example of FIG. 9, the 6G system side notifies the UE that the network node uses Green energy. The UE performs data transmission in response to this notification.

[0045] More specifically, for example, the collection of data used for batch processing of data analysis is performed only during power generation by Green energy.

[0046] <Second Embodiment: SEAL> In the second embodiment, since the SEAL function is used, first, SEAL will be described. Note that in the second embodiment, it is also possible not to use the SEAL function.

[0047] Fig. 10 shows the SEAL architecture described in Non-Patent Document 4 (TS23.434). As shown in Fig. 10, both the client side and the server side are divided into a Service Enabler Architecture layer (SEAL) and a Vertical Application Layer (VAL). SEAL is responsible for common services for each VAL, such as group management and location information management. VAL client / server varies depending on the application (e.g., FFAPP, UASAPP, V2XAPP, 5GMARCH,...).

[0048] The following are the SEAL services supported for the vertical application layer: Location management, Group management, Configuration management, Identity management, Key management, Network resource management, Data delivery, Notification management, Network slice capability enablement, Application data analytics enablement.

[0049] <Second Embodiment: Processing Sequence> The processing sequence of the second embodiment will be described with reference to Figure 11. In the configuration of Figure 11, it is assumed that a specific network node for data collection is provided within the 6GS (6G system) 95. Furthermore, this network node can be operated using power generated by Green Energy. The 6GS 95 may be considered to be this network node.

[0050] Furthermore, AF80 is a server that manages, for example, network nodes that collect data and UE20 that transmit data to those network nodes. AF80 includes a function to acquire (understand) the usage status of Green energy at those network nodes.

[0051] Furthermore, UE20 is equipped with a SEAL client, and AF80 is equipped with a SEAL server. For example, by utilizing the key management function defined in SEAL, encryption (decryption) keys can be shared between the SEAL client and the SEAL server. As a result, UE20 can transmit data encrypted with that key, and AF80 can decrypt the data encrypted with that key using that key.

[0052] For example, AF80 can retrieve encrypted data collected from UE20 by a network node in 6GS95 from that network node and decrypt it.

[0053] Furthermore, by using SEAL's group management function, the AF80 can create groups consisting of multiple UE20s that transmit data, and manage the members within those groups.

[0054] In step S201 of Figure 11, UE20 sends a Green data collection registration request to AF80.

[0055] A Green data collection registration request is, for example, a message requesting that UE20 be registered with AF80. In addition to information about UE20 (e.g., UE20 address information, UE20 owner information), this message may also include information about the type of Green energy desired by the UE20 (owner) (e.g., solar power generation). The owner of UE20 may be an individual or a business operator that provides IoT services, etc.

[0056] In S202, AF80 registers UE20 as "a UE that sends data to network nodes that collect data using Green energy".

[0057] In S202, AF80 determines whether UE20 meets the requirements of "a UE that transmits data to network nodes that collect data using Green energy," and may register only if it meets the requirements. For example, AF80 determines whether UE20 can be registered based on the owner information of UE20. In S203, AF80 returns a response to UE20 indicating that registration is complete.

[0058] AF80 monitors the usage status of network nodes that collect data by receiving notifications from 6GS95 (S204).

[0059] For example, in S204, AF80 receives a notification from 6GS95 indicating that the network node performing data collection has started operating using Green Energy. Upon receiving this notification, in S205, AF80 sends a Green data collection Notification to UE20.

[0060] A Green data collection Notification is a notification instructing UE20 to transmit data to a network node that performs data collection. The Green data collection Notification may include the address information of the network node. Upon receiving the notification, UE20 transmits the data to the network node in S206. The network node receives the data transmitted from UE20 and stores it in its own storage device. The data may also be transferred from the network node to AF80.

[0061] Subsequently, for example, if AF80 detects that the operation using Green Energy at the network node has ended, AF80 sends an instruction to UE20 to stop transmitting data to the network node.

[0062] <Effects of the Second Embodiment> According to the technology of the second embodiment, it becomes possible to collect data that reduces CO2 emissions, taking energy considerations into account.

[0063] (Device Configuration) Next, an example of the functional configuration of the network node 100 and UE20 (hereinafter referred to as terminal 20) that perform the processing and operations described above will be explained. The network node 100 is compatible with both PCF70 and AF80.

[0064] <Network Node 100> Figure 12 shows an example of the functional configuration of network node 100. As shown in Figure 12, 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 12 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.

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

[0066] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 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 control unit 140 also holds registration information. 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.

[0067] <Terminal 20> Figure 13 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 13, 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 Figure 13 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.

[0068] 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.

[0069] 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.

[0070] The control unit 240 controls the terminal 20. 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.

[0071] (Hardware Configuration) The block diagrams (Figures 12 and 13) 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.

[0072] 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.

[0073] For example, the network node 100 and terminal 20 in one embodiment of the present disclosure may function as computers that process the communication method of the present disclosure. Figure 14 is a diagram showing an example of the hardware configuration of the network node 100 and terminal 20 according to one embodiment of the present disclosure. The network node 100 and terminal 20 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.

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

[0075] Each function in the network node 100 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows 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.

[0076] 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.

[0077] 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 12 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 20 shown in Figure 13 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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).

[0082] 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.

[0083] Furthermore, the network node 100 and the terminal 20 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.

[0084] Figure 15 shows an example of the configuration of vehicle 2001. As shown in Figure 15, 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 20 may be included in the communication module 2013.

[0085] 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.

[0086] 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).

[0087] 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.

[0088] 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.).

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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.

[0093] 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.

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

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

[0096] <Notes> (Note 1) A terminal comprising a transmitting unit that transmits a registration request for data collection using renewable energy to a network node, and a receiving unit that receives a response from the network node indicating the completion of registration after the network node has performed the registration. (Note 2) The terminal according to Note 1, wherein the receiving unit receives a data transmission instruction from the network node based on the renewable energy usage status at a specific network node that performs the data collection, and the transmitting unit transmits the data to the specific network node in accordance with the instruction. (Note 3) A network node comprising a receiving unit that receives a registration request for data collection using renewable energy from a terminal, and a transmitting unit that transmits a response to the terminal indicating the completion of registration after registering the terminal based on the registration request. (Note 4) The network node according to Note 3, wherein the transmitting unit acquires the renewable energy usage status at a specific network node that performs the data collection, and transmits a data transmission instruction to the terminal based on the usage status. (Appendix 5) The network node described in Appendix 3, wherein the terminal is equipped with a SEAL client and the network node is equipped with a SEAL server. (Appendix 6) A communication method performed by a terminal, comprising the steps of: sending a registration request for data collection using renewable energy to a network node; and receiving a response from the network node indicating the completion of registration after the network node has performed the registration.

[0097] Any of the appendices 1 through 6 provides technology that enables data collection in a manner appropriate to the use case. According to appendices 2 and 4, data collection can be realized according to the usage status of renewable energy. According to appendice 5, the SEAL function can be utilized.

[0098] (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 20 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 20 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.

[0099] 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.

[0100] 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).

[0101] 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.

[0102] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (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 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0103] 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.

[0104] 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.

[0105] 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).

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.

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

[0111] 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.

[0112] 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.

[0113] 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.

[0114] 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.

[0115] 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.

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

[0117] 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.

[0118] Either the network node 100 or the terminal 20 may be called a transmitter, receiver, communication device, etc. Either the network node 100 or the terminal 20 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.

[0119] 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 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 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.

[0120] 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.

[0121] 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."

[0122] 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.

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

[0124] 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."

[0125] 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.

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

[0127] 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.

[0128] 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.

[0129] 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."

[0130] 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).

[0131] 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.

[0132] 10 RAN (Base Station) 20 Terminal, UE 30 AMF 40 SMF 50 UPF 60 DN 70 PCF 80 AF 100 Network Node 110 Transmitter 120 Receiver 130 Setting Unit 140 Control Unit 210 Transmitter 220 Receiver 230 Setting Unit 240 Control Unit 1001 Processor 1002 Storage Device 1003 Auxiliary Storage Device 1004 Communication Device 1005 Input Device 1006 Output Device

Claims

A transmission unit that sends a registration request for data collection using renewable energy to a network node, After the registration by the network node is completed, the receiving unit receives a response from the network node indicating that the registration is complete. A terminal equipped with the following features. 　 The receiving unit receives a data transmission instruction from a specific network node based on the renewable energy usage status at that network node, and the transmitting unit transmits the data to the specific network node in accordance with the instruction. The terminal according to claim 1. 　 A receiving unit that receives registration requests from a terminal regarding data collection using renewable energy, A transmission unit that, after registering the terminal based on the registration request, sends a response to the terminal indicating that registration is complete. A network node equipped with the following features. 　 The transmitting unit acquires the usage status of renewable energy at a specific network node that collects the data, and based on the usage status, transmits a data transmission instruction to the terminal. The network node according to claim 3. 　 The terminal is equipped with a SEAL client, and the network node is equipped with a SEAL server. 　 The network node according to claim 3. 　 The steps include sending a registration request for data collection using renewable energy to a network node, After the registration by the network node is completed, the network node receives a response indicating that the registration is complete. A communication method performed by a terminal, comprising the following features.

Images