Network node, terminal, and communication method

Abstract

This network node includes: a reception unit that uses renewable energy to receive, triggered by an operation of an application function, a setting request including a service code indicating that a relay service is provided; and a transmission unit that transmits policy information including the service code to a terminal that provides the relay service.

Description

Network Node, Terminal, and Communication Method

[0001] The present invention relates to the technology of relay services in a communication system.

[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 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] Also, a relay service (5G ProSe UE-to-Network Relay (Non-Patent Document 1, Chapter 4.2.7)) that relays the connection between a terminal and a network has been introduced. By using the relay service, a terminal can communicate with the network even in an area where network coverage is insufficient, an environment with many obstacles, and an environment where direct communication is difficult.

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

[0005] In recent years, energy efficiency and CO2 reduction have attracted attention from the perspective of promoting sustainability. Although proposals have been made to utilize Green base stations that use renewable energy, there are issues in securing a site for installing Green base stations, and it is difficult to cover a wide area with Green base stations.

[0006] The present invention has been made in view of the above points, and an object thereof is to provide a technology for realizing a relay service that utilizes renewable energy.

[0007] According to the disclosed technology, a network node is provided which includes a receiving unit that receives a configuration request, which includes a service code indicating that a relay service is provided using renewable energy, triggered by the operation of an application function, and a transmitting unit that transmits policy information, which includes the service code, to a terminal that provides the relay service.

[0008] According to the disclosed technology, a technology is provided to realize a relay service using renewable energy.

[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 showing the reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. This is a diagram showing the reference architecture for 5G ProSe Layer-2 UE-to-Network Relay. This is a diagram illustrating an overview of an embodiment. This is a sequence chart of the first embodiment. This is a diagram showing the SEAL architecture. This is a sequence chart of the second embodiment. This is a sequence chart of the third embodiment. This is a diagram showing an example of the functional configuration of the network node 100 in an embodiment of the present invention. This is a diagram showing an example of the functional configuration of the terminal 20 in an embodiment of the present invention. This is a diagram showing 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 showing 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. 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. Also, the "connection" described below may be a logical connection or a physical connection.

[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). 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 is a network node that interconnects with the DN (Data Network) 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 and DN constitute a network slice.

[0015] AMF30 is connected to UE20, RAN10, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function)60, NRF (Network Repository Function), UDM (Unified Data Management)70, AUSF (Authentication Server Function), PCF (Policy Control Function)50, AF (Application Function)40, and UDR (User Data Repository)80. AMF30, SMF, NSSF, NEF60, NRF, UDM70, AUSF, PCF50, AF40, and UDR80 are network nodes that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf, and Nudr.

[0016] The SMF is a network node with functions such as session management, IP (Internet Protocol) address allocation and management for UE20, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. The NEF60 is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node with functions such as selecting the network slice to which UE20 connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which UE20 connects. The PCF50 is a network node with the function of controlling network policies. The AF40 is a network node with the function of controlling application servers. The NRF is a network node with the function of discovering NF instances that provide services. The UDM70 is a network node that manages subscriber data and authentication data. The UDM70 is connected to the UDR80, which holds the said data. Furthermore, AF40 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 5G ProSe UE-to-Network Relay) As a prior art related to embodiments of the present invention, there is a relay service called 5G ProSe UE-to-Network Relay (Non-Patent Document 1, Chapter 4.2.7). This technology is related to proximity communication services (ProSe) and is a technology that relays the connection between terminal 20 and the network under specific conditions. This technology is effective in areas with insufficient network coverage, environments with many obstacles, and environments where direct communication is difficult. Hereafter, 5G ProSe UE-to-Network Relay will be referred to as "UE-to-Network Relay".

[0021] UE-to-Network Relay has two methods: one that uses Layer 3 for relaying and another that uses Layer 2. Figure 3 shows the method using Layer 3, and Figure 4 shows the method using Layer 2. The technology according to this embodiment is applicable to either method.

[0022] (Regarding the challenges) Recently, energy efficiency and CO2 reduction have been attracting attention from the perspective of promoting sustainability. In the 5G era, operators (telecommunications carriers) have begun to work on CO2 reduction from a sustainability perspective.

[0023] In the 6G era, network configurations that consider energy efficiency and CO2 reduction are required to contribute even more to CO2 reduction. In other words, 6G requires a system that can actively utilize renewable energy. Renewable energy can also be called green energy. Renewable energy / green energy is energy produced from sources such as solar, wind, hydro, geothermal, and biomass.

[0024] While proposals have been made to utilize Green base stations that use renewable energy, there are challenges in securing land for installing Green base stations, making it difficult to cover a wide area with Green base stations.

[0025] (Outline of the Embodiment) In this embodiment, in order to solve the above problems, a device utilizing Green Energy (referred to as Relay Node) acts as a proxy for communication of other devices. Specifically, the Relay Node utilizing Green Energy functions as a UE-to-Network Relay as shown in Figures 3 and 4.

[0026] Owners of Relay Nodes that utilize Green Energy (or terminals that function as Relay Nodes) are registered with AF40 as Green communication providers. Based on the registration information, these Relay Nodes are configured on the network as Green Relay Nodes and provide relay services.

[0027] Figure 5 shows an example of the system configuration in this embodiment. As shown in Figure 5, a Relay Node 25A that operates using Green Energy is provided. Terminal 20 can communicate with the 6G NW via the Relay Node (Relay UE) 25A. In this embodiment, it is also possible for terminal 20 to move and use another Relay Node (Relay UE) 25B that belongs to the same group as Relay Node 25A.

[0028] The first to third embodiments will be described below. The outlines of the first to third embodiments are as follows.

[0029] First Embodiment: Registration of ProSe support for Green energy Second Embodiment: Registration of Green provider Third Embodiment: Setting of Green Relay information triggered by AF In the first to third embodiments, since UE is used as the Relay Node, the Relay Node is referred to as Relay UE25. Furthermore, the UE that uses Relay UE25 is referred to as Remote UE20.

[0030] (First Embodiment) The sequence of the first embodiment will be described with reference to Figure 6. The first embodiment is the registration of a ProSe support for Green energy. In Figure 6, UE may be Relay UE25 or Remote UE20.

[0031] In S101, UE20 / 25 sends a Registration Request to RAN10 (base station). The Registration Request includes ProSe-Green-Relay as UE network capability. If the source of the Registration Request is Relay UE25, ProSe-Green-Relay means that Relay UE25 has the capability (function) to perform Relay operations with Green energy. If the source of the Registration Request is Remote UE20, ProSe-Green-Relay means that Remote UE20 has the capability (function) to utilize Relay UE25, which performs Relay operations with Green energy.

[0032] In S102, RAN10 selects an AMF30 suitable for UE20 / 25 and forwards the Registration Request to the CN (Core Network) 90 having the AMF30. Subsequently, the registration procedure described in 4.2.2.2 of Non-Patent Document 2 is executed (S104). The registration information, including ProSe-Green-Relay, is registered (stored) in UDM70 (or UDR80) by the AMF30.

[0033] In S105, the registration procedure is completed when CN90 returns "Registration accepted" to UE20 / 25.

[0034] <Effects of the First Embodiment> According to the first embodiment, both Relay UE25 and Remote UE20 can be registered with the core network. By registering with the core network, Relay UE25 and Remote UE20 can each utilize the core network.

[0035] (Second Embodiment) Next, a second embodiment will be described. The second embodiment is an embodiment of registering a Green provider to AF40. In the second embodiment, Relay UE25 is equipped with a Seal Client, and AF40 is equipped with a Seal Server. First, the Seal will be described.

[0036] Figure 7 shows the SEAL architecture described in Non-Patent Document 3. As shown in Figure 7, both the client and server sides are divided into a Service Enabler Architecture layer (SEAL) and a Vertical Application Layer (VAL). The SEAL is responsible for common services for each VAL, such as group management and location information management. The VAL client / server differs depending on the application (e.g., FFAPP, UASAPP, V2XAPP, 5GMARCH, ...).

[0037] Supported SEAL services for the vertical application layer include: Location management, Group management, Configuration management, Identity management, Key management, Network resource management, Data delivery, Notification management, Network slice capability enablement, and Application data analytics enablement.

[0038] The sequence of the second embodiment will be described with reference to Figure 8. AF40 shown in Figure 8 is, for example, an application server of a company deploying a Green Relay service.

[0039] In S201, Relay UE25 sends a Green Provider registration request to AF40. The Green Provider registration request includes Green energy information, Relay Node information, and operator information. Green energy information includes, for example, information indicating that renewable energy is being used for Relay UE25, and information indicating the type of renewable energy. Relay Node information includes, for example, the model and address information of Relay UE25. Operator information includes, for example, information (name, etc.) of the business operator providing Relay UE25.

[0040] In S202, the AF40 that has received the Green provider registration request checks whether the provider of the Relay UE25 (Green provider) or the Relay UE25 meets the requirements as a Green provider. For example, the AF40 determines whether the provider (or the Relay UE25) can be registered based on the operator information. In the determination, for example, a determination may be made to permit registration when the Relay UE25 uses a specific type of renewable energy. In S202, it is assumed that the requirements are met.

[0041] In S203, the AF40 permits and registers the provider or the Relay UE25 as a Green provider. The information to be registered may include, for example, Green energy information, Relay Node information, and operator information.

[0042] In S204, the AF40 returns a Green provider registration completion response to the Relay UE25.

[0043] <Effect of the Second Embodiment> According to the second embodiment, the provider or the Relay UE25 can be registered with the AF40 as a Green provider. The AF40 can, for example, use the registration information to manage relay services using renewable energy.

[0044] (Third Embodiment) Next, the third embodiment will be described. In the third embodiment, the PCF50 performs code setting for Relay service management. In the third embodiment, it is assumed that the registration of the Green provider with the AF40 in the second embodiment has been completed. Here, the setting of Green Relay information triggered by the AF40 is performed via the NEF60. Referring to FIG. 9, the sequence of the third embodiment will be described.

[0045] Note that the sequence shown in FIG. 9 is based on Figure 4.15.6.7.2-1 (Service specific information provisioning by AF to HPLMN) in Non-Patent Document 2 (TS23.502).

[0046] In S301, a policy association is executed between the AMF 30 and the PCF 50. In S302, Nudr_DM_Subscribe is sent from the PCF 50 to the UDR 80.

[0047] In S303, the AF 40 creates a new setting request (request for setting Green Relay information). In S304, as an example of the message of the above setting request, the AF 40 sends a Nnef_ServiceParameter_Create / Update / Delete Request to the NEF 60.

[0048] The message of S304 includes a Green provider name, a green group ID, and a Green Relay Service Code.

[0049] The Green provider name is the name of the Green provider (provider of the Relay UE 25). The green group ID is the ID of the group to which the Relay UE 25 belongs. The Green Relay Service Code is a service code indicating that a relay service is provided using renewable energy.

[0050] Regarding the green group ID, for example, in the AF 40, the association between the green group ID and the set of Relay UEs included in the group is managed.

[0051] For example, the Remote UE 20 can use a plurality of Relay UEs having the same green group ID. Therefore, even when the Remote UE 20 moves, the Relay UE can be continuously used.

[0052] In S305, the Nudm_SDM_Get service operation is performed between NEF60 and UDM70, and for example, the GPSI in Target UE Identifier is mapped to SUPI according to the information obtained from UDM70. In S306, the authorization of service specific parameters is performed according to 4.15.6.7a of Non-Patent Document 2.

[0053] In S307, information is stored in UDR80. The information stored here includes the Green provider name, green group ID, and Green Relay Service Code. In S308, the response to the request in S304 is returned from NEF60 to AF40.

[0054] In S309, a message (Nudr_DM_Notify) is sent from UDR80 to PCF50. This message is a configuration request and includes the Green provider name, green group ID, and Green Relay Service Code. In other words, the Green provider name, green group ID, and Green Relay Service Code are registered (configured) in PCF50 as information related to the Relay UE25 policy.

[0055] In S311, PCF50 notifies NEF60 of Npcf_EventExposure_Notify, and in S312, NEF60 notifies AF40 of Nnef_ServiceParameter_Notify.

[0056] In S310, the UE Policy delivery procedure described in Non-Patent Document 2 (TS23.502), section 4.2.4.3, is executed between Relay UE25 and PCF50. The UE Policy delivery procedure updates (sets) the UE policy in the UE configuration from PCF50 to Relay UE25. This policy information may be, for example, a policy regarding QoS for providing the Green relay service, or policy information regarding billing for providing the Green relay service. Furthermore, the policy information sent from PCF50 to Relay UE25 in S310 includes the Green provider name, green group ID, and Green Relay Service Code.

[0057] In S313, Relay UE25 sends a UE-to-Network Relay discovery Announcement message to Remote UE20. This UE-to-Network Relay discovery Announcement message includes a Green Relay Service Code as the Relay Service Code. The UE-to-Network Relay discovery Announcement message may also include a green group ID. This allows Remote UE20 to determine that the UE-to-Network Relay discovery Announcement message is from a Relay UE25 belonging to a specific group.

[0058] The UE-to-Network Relay discovery Announcement message itself is described in Chapter 6.3.2.3 of Non-Patent Document 1 (TS23.304). S305 enables Remote UE20 to discover Relay UE25 and utilize Relay UE25.

[0059] <Effects of the Third Embodiment> According to the technology of the third embodiment, it becomes possible to provide Green Relay Service based on appropriate policy settings.

[0060] (Regarding the effects common to the technologies according to the first to third embodiments) The technologies according to the first to third embodiments make it possible to realize a relay service using Relay Node that utilizes Green energy (renewable energy), and to provide a mechanism that actively utilizes Green energy.

[0061] While conventional technologies propose the use of renewable energy through Green base stations, securing land for Green base stations presents challenges, making it difficult to cover all areas with Green base stations.

[0062] In contrast, by using the technologies according to the first to third embodiments, it becomes possible to provide CO2-reducing communication services even in areas without Green base stations by utilizing Green Relay Node.

[0063] Furthermore, by using Green Relay Node, the radio wave output that the terminal would normally transmit directly to the base station is instead transmitted to the nearest Relay Node, thus reducing the terminal's radio wave output. In addition, by providing Green Relay Node, users can gain the opportunity to provide services centered on renewable energy.

[0064] (Device Configuration) Next, an example of the functional configuration of the network node 100 and terminal 20 that perform the processing and operations described above will be explained. The network node 100 corresponds to the base station 10, PCF 50, AMF 30, and AF 40. The terminal 20 corresponds to either Remote UE 20 or Relay UE 25. Relay UE 25 may also be called a relay device.

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

[0066] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or 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 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.

[0067] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 or network node 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.

[0068] <Terminal 20> Figure 11 is a diagram showing an example of the functional configuration of terminal 20 (Remote UE20 or Relay UE25). As shown in Figure 11, 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 11 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.

[0069] 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 network nodes. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0070] The setting unit 230 stores various setting information received from network nodes by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-configured setting information.

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

[0072] (Hardware Configuration) The block diagrams (Figures 10 and 11) 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 one device or the multiple devices with software.

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

[0074] 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 12 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.

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

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

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

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

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

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

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

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

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

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

[0085] Figure 13 shows an example of the configuration of vehicle 2001. As shown in Figure 13, 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.

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

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

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

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

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

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

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

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

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

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

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

[0097] <Notes> (Note 1) A network node comprising: a receiving unit that receives a configuration request including a service code indicating that a relay service will be provided using renewable energy, triggered by the operation of an application function; and a transmitting unit that transmits policy information including the service code to a terminal that will provide the relay service. (Note 2) The network node according to Note 1, wherein the configuration request further includes a group ID indicating the group to which the terminal belongs, and the policy information further includes the group ID. (Note 3) A terminal comprising: a receiving unit that receives policy information including a service code indicating that a relay service will be provided using renewable energy from a network node; and a transmitting unit that transmits a message including the service code to a remote terminal that will use the relay service. (Note 4) A communication method executed by a network node that receives a configuration request including a service code indicating that a relay service will be provided using renewable energy, triggered by the operation of an application function, and transmits policy information including the service code to a terminal that will provide the relay service.

[0098] Any of the appendices 1 to 4 provides the technology to realize a relay service using renewable energy. According to appendice 2, even when the remote terminal is in motion, it will be possible to continue using the relay service using renewable energy.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0133] 10 RAN (Base Station) 20 Terminal, Remote UE 25 Relay UE 30 AMF 40 AF 50 PCF 60 NEF 60 NRF 70 UDM 80 UDR 90 CN 100 Network Node 110 Transmitter 120 Receiver 130 Configuration Unit 140 Control Unit 210 Transmitter 220 Receiver 230 Configuration Unit 240 Control Unit 1001 Processor 1002 Storage Device 1003 Auxiliary Storage Device 1004 Communication Device 1005 Input Device 1006 Output Device

Claims

1. A network node comprising: a receiving unit that receives a configuration request including a service code indicating that a relay service will be provided using renewable energy, triggered by the operation of an application function; and a transmitting unit that transmits policy information including the service code to a terminal providing the relay service.

2. The network node according to claim 1, wherein the configuration request further includes a group ID indicating the group to which the terminal belongs, and the policy information further includes the group ID.

3. A terminal comprising: a receiving unit that receives policy information from a network node, including a service code indicating that a relay service is provided using renewable energy; and a transmitting unit that transmits a message including the service code to a remote terminal that uses the relay service.

4. A communication method performed by a network node that receives a configuration request, which includes a service code indicating that it will provide a relay service using renewable energy, triggered by the operation of an application function, and transmits policy information, which includes the service code, to a terminal that will provide the relay service.

Images