Terminal, network node, and communication method

Abstract

This terminal comprises: a transmission unit that transmits, to a network node, information indicating that the terminal has the ability to operate as an AIoT (Ambient Internet of Things) intermediate node and information requesting that the terminal operates as an AIoT intermediate node; a reception unit that receives, from the network node, information indicating that AIoT network capability is supported and AIoT intermediate node setting information including an AIoT registration area; and a control unit that sets the own device as an AIoT intermediate node. The reception unit receives an AIoT registration request and an uplink data transmission request from an AIoT terminal, and the transmission unit transmits the AIoT registration request and the uplink data transmission request to the network node.

Description

Terminal, network node and communication method

[0001] The present invention relates to a terminal, a network node and a communication method in a communication system.

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system will be referred to as "5G" or "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. Various wireless technologies are being studied for 5G to meet the requirements of achieving a throughput of 10 Gbps or more while keeping latency in wireless sections to 1 ms or less.

[0003] In NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in the network architecture of LTE (Long Term Evolution), and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the network architecture of LTE, is being considered (for example, Non-Patent Document 1 and Non-Patent Document 2).

[0004] 3GPP TS 23.501 V18.4.0 (2023-12)3GPP TS 23.502 V18.4.0 (2023-12)3GPP TR 38.848 V18.0.0 (2023-09)3GPP TS 23.288 V18.4.0 (2023-12)

[0005] Ambient Internet of Things (AIoT) devices are being considered (see Non-Patent Document 3). AIoT aims to achieve a significantly higher number of connections, higher device density, lower complexity, and lower power consumption than conventional LTE-MTC (Long Term Evolution - Machine Type Communication) or NB-IoT (Narrowband IoT).

[0006] As a network configuration including AIOT devices, a topology in which devices are connected to the network via an intermediate node that acts as a terminal is being considered. However, it is difficult to apply existing procedures to the procedure for registering and connecting AIOT devices that do not have a power source via the intermediate node.

[0007] The present invention has been made in consideration of the above points, and aims to execute procedures related to the registration or connection of an AIoT (Ambient Internet of Things) device via an intermediate node.

[0008] According to the disclosed technology, there is provided a terminal having a transmitter that transmits to a network node information indicating that the network node has the capability to operate as an AIoT (Ambient Internet of Things) intermediate node and information requesting that the network node operate as an AIoT intermediate node, a receiver that receives from the network node information indicating that the network node has the AIoT network capability and AIoT intermediate node setting information including an AIoT registration area, and a control unit that sets the terminal itself as an AIoT intermediate node, wherein the receiver receives an AIoT registration request and an uplink data transmission request from an AIoT terminal, and the transmitter transmits the AIoT registration request and the uplink data transmission request to the network node.

[0009] According to the disclosed technology, procedures related to the registration or connection of an AIoT (Ambient Internet of Things) device can be performed via an intermediate node.

[0010] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 2 is a sequence diagram for explaining an operation example (1) in an embodiment of the present invention. FIG. 3 is a sequence diagram for explaining an operation example (2) in an embodiment of the present invention. FIG. 4 is a sequence diagram for explaining an operation example (3) in an embodiment of the present invention. FIG. 5 is a sequence diagram for explaining an operation example (4) in an embodiment of the present invention. FIG. 6 is a sequence diagram for explaining an operation example (5) in an embodiment of the present invention. FIG. 7 is a sequence diagram for explaining an operation example (7) in an embodiment of the present invention. FIG. 8 is a sequence diagram for explaining an operation example (8) in an embodiment of the present invention. FIG. 1 is a diagram for explaining an example of the functional configuration of a base station 10 in an embodiment of the present invention. FIG. 2 is a diagram for explaining an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 3 is a diagram for explaining an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention. FIG. 4 is a diagram for explaining an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced, and systems subsequent to LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0013] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are set.

[0014] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0015] The RAN (Radio Access Network) is a network node 30 having a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having 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 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices may be configured.

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

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

[0018] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0019] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0020] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0021] The SMF is a network node 30 having functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 2 is a SEPP in the visited network, and the hSEPP is a SEPP in the home network.

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

[0023] Here, ambient Internet of Things (AIoT) devices are being considered (see Non-Patent Document 3). AIoT is considering communication systems for three categories of terminals and four types of network configurations. Compared to conventional LTE-MTC (Long Term Evolution - Machine Type Communication) or NB-IoT (Narrowband IoT), AIoT aims for a significantly higher number of connections, terminal density, low complexity, and low power consumption. For example, the network topology consists of terminals and base stations. The base station that transmits radio waves and signals to the terminal may be different from the base station that receives backscattered signals from the terminal.

[0024] As a network configuration including AIOT devices, a topology in which devices are connected to the network via an intermediate node that acts as a terminal is being considered. However, it is difficult to apply existing procedures to the procedure for registering and connecting AIOT devices that do not have a power source via the intermediate node.

[0025] Therefore, a normal terminal that additionally has the capability to communicate with an AIOT device is assumed as an intermediate node. When the intermediate node executes its own registration procedure, it notifies the AMF that it has the capability to function as an intermediate node and that it will operate as an intermediate node. The intermediate node obtains necessary configuration information from the AMF. The intermediate node behaves toward the AIOT device in the same way as a base station in Topology 1, in which the AIOT device and the base station are directly connected. When the AMF receives an AIOT registration request from the intermediate node, it registers the intermediate node and its own device in the UDM as accommodating the AIOT device in turn. When transmitting DL data, the AMF calls the intermediate node, and then the intermediate node calls the AIOT device.

[0026] 3 is a sequence diagram for explaining an operation example (1) in an embodiment of the present invention. The registration procedure will be explained using FIG. 3. Device 1 is an AIot device 20A. The intermediate node is a terminal 20B. gNB 10A is a base station that accommodates the intermediate node.

[0027] The pubsub platform (Publish-Subscribe platform) was introduced in 5GS as the Data Collection Coordination Function (DCCF) and the Messaging Framework Adaptor Function (MFAF) (see Non-Patent Document 4). It is assumed that an NF, an AF, or a terminal will be the publisher or subscriber of the pubsub platform. DCCF and MFAF were introduced as an extension of the Network Data Analytics Function (NWDAF). DCCF and MFAF have a general-purpose configuration and can be applied as is to areas where a pubsub platform is required in next-generation systems, as long as the involvement of the terminal is excluded. The NF or AF becomes the publisher or subscriber and uses DCCF and MFAF. In existing specifications, the involvement of the terminal is limited. A terminal application can indirectly become a publisher by linking with a specific AF (see Non-Patent Document 4).

[0028] In step S101, the intermediate node sends a Registration request (5GMM capability (AIoT intermediate node), 5GS update type (AIoT intermediate node behavior request)) to the AMF. As a result, the AMF recognizes that the terminal operates as an intermediate node.

[0029] In step S102, the AMF selects an AIoT registration area and a terminal registration area so that the AIoT registration area includes a terminal registration area (Tracking Area Identity (TAI) list) so that the terminal does not cross the AIoT registration area boundary without issuing a mobility registration request.

[0030] In step S103, the AMF sends Registration accept (TAI list, 5GS network feature support (AIoT support), AIoT intermediate node setting information (AIoT registration area, periodic broadcast timer)) to the intermediate node. As a result, the intermediate node recognizes that the network supports AIoT, and the values ​​of the AIoT registration area and periodic broadcast timer.

[0031] 4 is a sequence diagram for explaining an operation example (2) in the embodiment of the present invention, and will be used to explain the registration procedure via an intermediate node without a device context.

[0032] In step S201, a periodic notification timer set for each intermediate node expires in the intermediate node. For example, the periodic notification timer may be one hour. In step S202, the intermediate node transmits an unmodulated wave to device 1. In step S203, device 1 performs power storage.

[0033] In step S204, the intermediate node transmits an AIoT registration activation request including information indicating a filter for excluding target devices to the device 1. In step S205, the device 1 compares the filter with the device identifier to determine whether the device is a target device. If the filter does not include the device identifier of the device itself and the device is a target device, the process proceeds to the next step.

[0034] In step S206, device 1 performs response preparation. In step S207, the intermediate node transmits an unmodulated wave to device 1. In step S208, device 1 transmits an AIoT registration request including device identifier #1 and an UL transmission including device identifier #1, an UL transmission request ID, and data content to the intermediate node. The AIoT registration request and the UL transmission may be transmitted in different messages, or may be transmitted in one message including two information elements.

[0035] In step S209, if there is a context for device 1, the intermediate node uses the periodic registration timer value in the context to set the periodic registration timer for device 1. If there is no context for device 1, the intermediate node uses a default value to set the periodic registration timer. Here, it is assumed that there is no context for device 1.

[0036] In step S210, the intermediate node sends a control plane service request to the AMF, the control plane service request having an AIoT registration request including information indicating initial registration and device identifier #1, and an AIoT container including an AIoT UL data transmission request including device identifier #1 and data content as a payload. The AIoT registration request and the UL data transmission request may be sent in different messages, or may be sent in one message including two information elements.

[0037] In step S211, the AMF sets an AIoT Mobile Reachable timer using a default value for device 1. For example, the AIoT Mobile Reachable timer may be 6 hours and 30 minutes. The AMF may retain a set of a terminal identifier, a registration area, and an AIoT Mobile Reachable timer associated with a device.

[0038] In step S212, the AMF sends a Nudm_UECM_Registration request (Amf3GppAIoTAccessRegistration (device identifier, intermediate node identifier)) including information indicating a device identifier and an intermediate node identifier to the UDM. Note that the Nudm_UECM_Registration request may be a UE message or a non-UE message. In step S213, the UDM sends a Nudm_UECM_Registration response to the AMF.

[0039] In step S214, the AMF sends a Nudm_SDM_Get request to the UDM. In step S215, the UDM sends a Nudm_SDM_Get response to the AMF, including the periodic registration timer value in the subscriber information. In step S216, the AMF calculates and updates the value of the AIoT Mobile Reachable timer for device 1 using the periodic registration timer value in the subscriber information. In step S217, the AMF sends a service accept to the intermediate node, including as a payload an AIoT container including an AIoT registration response including the periodic registration timer value.

[0040] In step S218, the intermediate node updates the value of the periodic registration timer of device 1 based on the received periodic registration timer value. In step S219, the AMF sends an AIoT UL data transmission request including device identifier #1 and data content to any PubSub infrastructure. In step S220, the any PubSub infrastructure sends an AIoT UL data transmission response to the AMF. In step S221, the AMF sends a DL NAS transport including an AIoT container including the AIoT UL data transmission response as a payload to the intermediate node.

[0041] 5 is a sequence diagram for explaining an operation example (3) in the embodiment of the present invention, with reference to which a registration procedure via an intermediate node when a device context exists will be explained.

[0042] In step S301, a periodic notification timer set for each intermediate node expires in the intermediate node. For example, the periodic notification timer may be one hour. In step S302, the intermediate node transmits an unmodulated wave to device 1. In step S303, device 1 performs power storage.

[0043] In step S304, the intermediate node transmits an AIoT registration activation request including information indicating a filter for excluding target devices to device 1. In step S305, device 1 compares the filter with the device identifier to determine whether the device is a target device. If the filter does not include the device identifier of the device itself and the device is a target device, the process proceeds to the next step.

[0044] In step S306, device 1 performs response preparation. In step S307, the intermediate node transmits an unmodulated wave to device 1. In step S308, device 1 transmits an AIoT registration request including device identifier #1 and an UL transmission including device identifier #1, an UL transmission request ID, and data content to the intermediate node. The AIoT registration request and the UL transmission may be transmitted in different messages, or may be transmitted in one message including two information elements.

[0045] In step S309, if there is a context for device 1, the intermediate node sets the periodic registration timer for device 1 using the periodic registration timer value in the context. That is, the periodic registration timer is initialized. If there is no context for device 1, the intermediate node sets the periodic registration timer using a default value. Here, it is assumed that there is a context for device 1.

[0046] In step S310, the intermediate node sends a control plane service request to the AMF, the control plane service request having an AIoT container as a payload, the AIoT container including an AIoT registration request including information indicating periodic registration and device identifier #1, and an AIoT UL data transmission request including device identifier #1 and data content. The AIoT registration request and the UL data transmission request may be sent in different messages, or may be sent in one message including two information elements.

[0047] In step S311, the AMF sets an AIoT Mobile Reachable timer for device 1 using the value in the UE context. For example, the AIoT Mobile Reachable timer may be 6 hours and 30 minutes. The AMF may retain a set of a terminal identifier, a registration area, and an AIoT Mobile Reachable timer associated with a device. In step S312, the AMF sends an AIoT registration response to the intermediate node.

[0048] In step S313, the AMF sends an AIoT UL data transmission request including device identifier #1 and data content to any PubSub platform. In step S314, the any PubSub platform sends an AIoT UL data transmission response to the AMF. In step S315, the AMF sends a DL NAS transport to the intermediate node, with an AIoT container including the AIoT UL data transmission response as its payload.

[0049] 6 is a sequence diagram for explaining an operation example (4) in the embodiment of the present invention. An example of changing the periodic registration timer will be explained using FIG.

[0050] In step S401, the AF sends a Nnef_ParameterProvision_Create request to the NEF, which includes a device identifier #1 and a periodic UL data transmission interval. Note that the periodic UL data may be replaced with periodic DL data. The periodic UL data transmission interval may be, for example, 3 hours. In step S402, the NEF sends a Nudm_ParameterProvision_Create request to the UDM, which includes the device identifier #1 and the periodic UL data transmission interval.

[0051] In step S403, the UDM sets the value of the periodic UL data transmission interval and the value of the periodic registration timer in the subscriber information of device 1. For example, the periodic UL data transmission interval may be 3 hours, and the periodic registration timer may be 3 hours. In step S404, the UDM sends a Nudm_SDM_Notification Notify request to the AMF, which includes device identifier #1, the value of the periodic UL data transmission interval, and the value of the periodic registration timer.

[0052] In step S405, the AMF calculates and updates the value of the AIoT Mobile Reachable timer using the received periodic registration timer value. The AMF also identifies intermediate nodes within the registration area of ​​device 1. In step S406, the AMF sends a DL NAS transport, the payload of which is an AIoT container including an AIoT intermediate node configuration update including the periodic registration timer value, to the intermediate node. In step S407, the intermediate node updates the value of device 1's periodic registration timer using the received periodic registration timer value. In step S408, the intermediate node sends a UL NAS transport, the payload of which is an AIoT container including an AIoT intermediate node configuration update response, to the AMF.

[0053] 7 is a sequence diagram illustrating an operation example (5) according to an embodiment of the present invention. An example of timer initialization by arbitrary data transmission / reception will be described using FIG. 7. In step S501, the intermediate node transmits an unmodulated wave to device 1. In step S502, device 1 stores power. In step S503, device 1 recognizes that it has UL data.

[0054] In step S504, the intermediate node transmits an arbitrary command including information indicating the access barring bit to the device 1. The access barring bit may be set to any number of digits from 1 to n. Only when the access barring bit has the same value as the bit string at the corresponding position in the terminal identifier of the own device (for example, it may be n digits from the least significant bit), the terminal corresponding to the terminal identifier may be allowed to transmit data. In conventional access class barring, the minimum permitted terminal rate was 10%. For example, if the access barring bit is set to five digits, communication can be more distributed, such as 1 / 32 = 3.125%.

[0055] In step S505, the device 1 checks the access restriction bit against the device identifier to determine whether data transmission is permitted. If data transmission is permitted, the device 1 proceeds to the next step.

[0056] In step S506, device 1 prepares for a response. In step S507, the intermediate node transmits an unmodulated wave to device 1. In step S508, device 1 transmits a connection grant request including device identifier #1 and a UL transmission request ID to the intermediate node. In step S509, the intermediate node considers responses from other devices, i.e., determines whether to grant the request based on the network congestion state. If granting the request, proceed to the next step.

[0057] In step S510, the intermediate node transmits an unmodulated wave to device 1. In step S511, the intermediate node transmits a connection grant including information indicating device identifier #1 and an UL transmission request ID to device 1. In step S512, device 1 performs UL transmission preparation.

[0058] In step S513, the intermediate node transmits an unmodulated wave to device 1. In step S514, device 1 transmits an UL transmission including device identifier #1, an UL transmission request ID, and data content to the intermediate node. In step S515, if the time interval between the previous registration request and the current UL data reception is longer than the periodic notification timer, the intermediate node initializes the periodic registration timer of device 1. The intermediate node also sends an AIoT registration request to the AMF to notify the AMF of the periodic registration timer initialization.

[0059] In step S516, the intermediate node sends a control plane service request to the AMF, the control plane service request having as its payload an AIoT container including an AIoT UL data transmission request including device identifier #1 and the received data content, and an AIoT container including an AIoT registration request including information indicating periodic registration and device identifier #1. In step S517, the AMF initializes the AIoT Mobile Reachable timer of device 1.

[0060] In step S518, the AMF sends a service accept to the intermediate node. In step S519, the AMF sends an AIoT UL data transmission request including device identifier #1 and the received data content to any PubSub platform. In step S520, the any PubSub platform sends an AIoT UL data transmission response to the AMF. In step S521, the AMF sends a DL NAS transport to the intermediate node, with an AIoT container including the AIoT UL data transmission response as its payload.

[0061] 8 is a sequence diagram illustrating an operation example (6) according to an embodiment of the present invention. An example of UL data transmission will be described using FIG. 8. In step S601, the intermediate node transmits an unmodulated wave to device 1. In step S602, device 1 stores power. In step S603, device 1 recognizes that it has UL data.

[0062] In step S604, the intermediate node transmits an arbitrary command including information indicating the access barring bit to the device 1. The access barring bit may be set to any number of digits from 1 to n. Only when the access barring bit has the same value as the bit string at the corresponding position in the terminal identifier of the own device (for example, it may be n digits from the least significant bit), the terminal corresponding to the terminal identifier may be allowed to transmit data. In conventional access class barring, the minimum permitted terminal rate was 10%. For example, if the access barring bit is set to five digits, communication can be more distributed, such as 1 / 32 = 3.125%.

[0063] In step S605, the device 1 checks the access restriction bit against the device identifier to determine whether data transmission is permitted. If data transmission is permitted, the device 1 proceeds to the next step.

[0064] In step S606, device 1 prepares for a response. In step S607, the intermediate node transmits an unmodulated wave to device 1. In step S608, device 1 transmits a connection grant request including device identifier #1 and a UL transmission request ID to the intermediate node. In step S609, the intermediate node considers responses from other devices, i.e., determines whether to grant the request based on the network congestion state. If granting the request, proceed to the next step.

[0065] In step S610, the intermediate node transmits an unmodulated wave to device 1. In step S611, the intermediate node transmits a connection grant including information indicating device identifier #1 and an UL transmission request ID to device 1. In step S612, device 1 performs UL transmission preparation.

[0066] In step S613, the intermediate node transmits an unmodulated wave to device 1. In step S614, device 1 transmits an UL transmission including device identifier #1, UL transmission request ID, and data content to the intermediate node.

[0067] In step S615, the intermediate node sends a control plane service request to the AMF, the payload of which is an AIoT container including an AIoT UL data transmission request including device identifier #1 and the received data content. In step S616, the AMF sends a service accept to the intermediate node. In step S617, the AMF sends an AIoT UL data transmission request including device identifier #1 and the received data content to any PubSub infrastructure. In step S618, the any PubSub infrastructure sends an AIoT UL data transmission response to the AMF. In step S619, the AMF sends a DL NAS transport to the intermediate node, the payload of which is an AIoT container including the AIoT UL data transmission response.

[0068] 9 is a sequence diagram for explaining an operation example (7) according to an embodiment of the present invention. Using FIG. 9, a DL data transmission procedure when there is a response from device 1 will be explained.

[0069] In step S701, the NF recognizes that DL data exists in the NF itself. In step S702, the NF sends a Nudm_UECM_Get request including information indicating device identifier #1 to the UDM. In step S703, the UDM sends a Nudm_UECM_Get response including an AMF ID and an intermediate node identifier to the NF itself.

[0070] In step S704, any NF sends an AIoT DL data transmission request to the AMF, including device identifier #1, DL data to be transmitted, maximum transmission delay, and intermediate node identifier. In step S705, the AMF requests a page from the intermediate node. In step S706, the AMF sends paging to the gNB, including the intermediate node identifier as the UE paging identity. In step S707, the gNB sends the paging to the intermediate node. In step S708, the intermediate node sends a service request to the AMF.

[0071] In step S709, the AMF sends a service accept to the intermediate node, with an AIoT container as its payload, including an AIoT DL data transmission request including device identifier #1, DL data to be transmitted, and a maximum transmission delay. If the remaining value of the periodic registration timer is less than the received maximum transmission delay, the intermediate node may buffer the received DL data without calling the target device. The intermediate node may also transmit the buffered DL data to the target device when the next periodic registration timer expires.

[0072] In step S710, the intermediate node transmits an unmodulated wave to device 1. In step S711, device 1 performs power storage. In step S712, the intermediate node transmits a call including device identifier #1 to device 1. In step S713, device 1 performs response preparation. In step S714, the intermediate node transmits an unmodulated wave to device 1.

[0073] In step S715, device 1 transmits a connection grant request including device identifier #1 to the intermediate node. In step S716, the intermediate node transmits an unmodulated wave to device 1. In step S717, the intermediate node transmits a DL transmission including device identifier #1 and data content to device 1.

[0074] In step S718, the intermediate node sends a UL NAS transport with an AIoT container including an AIoT DL data transmission response as a payload to the AMF. In step S719, the AMF sends the AIoT DL data transmission response to any NF.

[0075] 10 is a sequence diagram for explaining an operation example (8) according to an embodiment of the present invention. Using FIG. 10, the DL data transmission procedure when there is no response from device 1 will be explained. In FIG. 10, device 1 is assumed to be far enough away from the intermediate node that it cannot communicate with the intermediate node. Furthermore, device 1 is assumed to be in a position where it can communicate with the AIot base station 10B.

[0076] Assume that the process is performed up to step S714 in Figure 9 and there is no response from device 1. In step S801, the intermediate node sends a UL NAS transport to the AMF, with an AIoT container including an AIoT DL data transmission unsuccessful response as its payload. In step S802, the AMF calls an AIoT base station within its registration area.

[0077] In step S803, the AMF sends paging to the AIoT base station, including device identifier #1 as the UE paging identity, including the AIoT registration area as the TAI list, and including DL data to be transmitted.

[0078] In step S804, the AIot base station transmits an unmodulated wave to device 1. In step S805, device 1 stores power. In step S806, the AIot base station transmits a call including device identifier #1 to device 1. In step S807, device 1 prepares for a response. In step S808, the AIot base station transmits an unmodulated wave to device 1.

[0079] In step S809, device 1 transmits a connection authorization request including device identifier #1 to the AIoT base station. In step S810, the AIoT base station transmits an unmodulated wave to device 1. In step S811, the AIoT base station transmits a DL transmission including device identifier #1 and data content to device 1.

[0080] In step S812, the AMF sends an Uplink NAS transport to the AMF, the Uplink NAS transport having an AIoT container including an AIoT DL data transmission response as a payload. In step S813, the AMF sends the AIoT DL data transmission response to an arbitrary NF.

[0081] The above-described embodiment allows an unpowered AIOT device to perform registration and connection procedures via an intermediate node, and efficiently perform registration, transmission of UL data, and reception of DL data.

[0082] That is, procedures related to registration or connection of an AIoT (Ambient Internet of Things) device can be performed via the intermediate node.

[0083] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0084] <Base Station 10 and Network Node 30> Fig. 11 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 11, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 11 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0085] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal.

[0086] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads the information from the storage device as needed. The content of the setting information includes, for example, settings related to the operations described in the embodiments.

[0087] As described in the embodiments, the control unit 140 performs processing related to the operations described in the embodiments. The control unit 140 also performs processing related to communication with the terminal 20. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0088] <Terminal 20> Fig. 12 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 12, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 12 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention.

[0089] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, and the like transmitted from the network node 30. The transmitter 210 may transmit using a backscattering method.

[0090] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, settings related to the operations described in the embodiments.

[0091] The control unit 240 performs processing related to the operations described in the embodiments as described in the embodiments. The control unit 240 also performs processing related to the capacity-enhanced cell. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0092] The terminal 20 may have a power receiving unit that receives radio waves transmitted from a base station or the like, and may have hardware that receives and stores power.

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

[0094] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0095] For example, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the terminal 20 may be physically configured as a computer device 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, etc.

[0096] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

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

[0098] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0099] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 11 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 12 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

[0101] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0102] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0103] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0104] 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 may be configured using different buses between each device.

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

[0106] Fig. 14 shows an example configuration of a vehicle 2001. As shown in Fig. 14, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0107] The drive unit 2002 is configured, for example, by 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 operated by the user.

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

[0109] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0110] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

[0111] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0113] 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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, or the like.

[0114] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0115] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the external devices 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 to 2029, etc. provided in the vehicle 2001.

[0116] (Summary of embodiment) As described above, according to an embodiment of the present invention, there is provided a terminal including: a transmitter that transmits, to a network node, information indicating that the terminal has the capability to operate as an AIoT (Ambient Internet of Things) intermediate node and information requesting that the terminal operate as an AIoT intermediate node; a receiver that receives, from the network node, AIoT intermediate node setting information including information indicating that the terminal has AIoT network capability and an AIoT registration area; and a controller that sets the terminal itself as an AIoT intermediate node, wherein the receiver receives an AIoT registration request and an uplink data transmission request from an AIoT terminal, and the transmitter transmits the AIoT registration request and the uplink data transmission request to the network node.

[0117] When transmitting the AIOT registration request and the uplink data transmission request to the network node, the transmitter may use a NAS (Non-Access Stratum) message including a payload container type having an AIOT container as a value.

[0118] Furthermore, according to an embodiment of the present invention, there is provided a network node having a receiving unit that receives, from a terminal, information indicating that the terminal has the capability to operate as an AIoT (Ambient Internet of Things) intermediate node and information requesting that the terminal operate as an AIoT intermediate node, a control unit that selects an AIoT registration area and a terminal registration area so that the AIoT registration area includes the terminal registration area, and a transmitting unit that transmits, to the terminal, information indicating that the terminal has AIoT network capability and AIoT intermediate node setting information including the AIoT registration area.

[0119] Furthermore, according to an embodiment of the present invention, there is provided a network node including: a receiving unit that receives an AIoT registration request from an AIoT terminal via a terminal operating as an AIoT (Ambient Internet of Things) intermediate node; and a transmitting unit that transmits information indicating that the AIoT terminal is accommodated in the terminal operating as the AIoT intermediate node and is accommodated in the first network node, wherein the receiving unit receives a downlink data transmission request addressed to the AIoT terminal from a second network node; the transmitting unit transmits a message to a base station requesting a call to the terminal operating as the AIoT intermediate node; and the transmitting unit transmits the downlink data transmission request to the terminal operating as the AIoT intermediate node.

[0120] The receiving unit may receive a downlink data transmission impossible response from the terminal operating as the AIOT intermediate node, and the transmitting unit may transmit a paging signal including the downlink data to an AIOT base station located in an AIOT registration area to which the terminal operating as the AIOT intermediate node belongs.

[0121] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal executes the following procedures: a procedure of transmitting, to a network node, information indicating that the terminal has the capability to operate as an AIoT (Ambient Internet of Things) intermediate node and information requesting that the terminal operate as an AIoT intermediate node; a procedure of receiving, from the network node, AIoT intermediate node setting information including information indicating that the terminal has AIoT network capability and an AIoT registration area; a procedure of setting the terminal itself as an AIoT intermediate node; a procedure of receiving an AIoT registration request and an uplink data transmission request from an AIoT terminal; and a procedure of transmitting the AIoT registration request and the uplink data transmission request to the network node.

[0122] The above-described apparatus allows an unpowered AIoT device to perform registration and connection procedures via an intermediate node, and efficiently perform registration, UL data transmission, and DL data reception, i.e., to perform registration or connection procedures for an AIoT (Ambient Internet of Things) device via the intermediate node.

[0123] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention. Two or more items may be used in combination as needed, and items described in one item may apply to items described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to physical component boundaries. The operations of multiple functional units may be physically performed by a single component, or the operations of a single functional unit may be physically performed by multiple components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the network node 30 and the terminal 20 have been described using functional block diagrams. However, such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the network node 30 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in any suitable storage medium, such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or the like.

[0124] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0125] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), 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, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0126] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (x is, for example, an integer or a decimal number)), 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.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

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

[0128] In this specification, a specific operation that is described as being performed by the network node 30 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes including the network node 30, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the network node 30 and another network node other than the network node 30 (for example, an MME or an S-GW, etc., are possible, but are not limited to these). Although the above example illustrates a case where there is one other network node other than the network node 30, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0129] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0130] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0131] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0132] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0133] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0135] Note that terms described 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0136] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0137] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0138] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0139] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0140] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can 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 the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

[0142] 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 some other suitable terminology.

[0143] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do 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.

[0144] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the above-described network node 30. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0145] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

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

[0147] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0148] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0149] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

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

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

[0152] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

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

[0154] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0155] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0156] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0157] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A terminal having a transmitter that transmits to a network node information indicating that it has the ability to operate as an AIoT (Ambient Internet of Things) intermediate node and information requesting that it operate as an AIoT intermediate node; a receiver that receives from the network node information indicating that it has AIoT network capability and AIoT intermediate node setting information including an AIoT registration area; and a control unit that sets the terminal itself as an AIoT intermediate node, wherein the receiver receives an AIoT registration request and an uplink data transmission request from an AIoT terminal, and the transmitter transmits the AIoT registration request and the uplink data transmission request to the network node.

2. The terminal of claim 1, wherein the transmitter uses a NAS (Non-Access Stratum) message including a payload container type having an AIoT container as a value when transmitting the AIoT registration request and the uplink data transmission request to the network node.

3. A network node having a receiving unit that receives from a terminal information indicating that it has the ability to operate as an AIoT (Ambient Internet of Things) intermediate node and information requesting that it operate as an AIoT intermediate node; a control unit that selects an AIoT registration area and a terminal registration area so that the AIoT registration area includes the terminal registration area; and a transmitting unit that transmits to the terminal information indicating that it has AIoT network capability and AIoT intermediate node setting information including the AIoT registration area.

4. A network node comprising: a receiving unit that receives an AIoT registration request from an AIoT terminal via a terminal operating as an AIoT (Ambient Internet of Things) intermediate node; and a transmitting unit that transmits information to a first network node indicating that the AIoT terminal is accommodated in the terminal operating as the AIoT intermediate node and is accommodated in the first network node, wherein the receiving unit receives a downlink data transmission request addressed to the AIoT terminal from a second network node; the transmitting unit transmits a message to a base station requesting a call to the terminal operating as the AIoT intermediate node; and the transmitting unit transmits the downlink data transmission request to the terminal operating as the AIoT intermediate node.

5. The network node according to claim 4, wherein the receiver receives a downlink data transmission unsuccessful response from the terminal operating as the AIOT intermediate node, and the transmitter transmits a paging signal including the downlink data to an AIOT base station located in an AIOT registration area to which the terminal operating as the AIOT intermediate node belongs.

6. A communications method in which a terminal executes the following procedures: transmitting information indicating that the terminal has the capability to operate as an AIoT (Ambient Internet of Things) intermediate node and information requesting that the terminal operate as an AIoT intermediate node to a network node; receiving information indicating that the terminal has AIoT network capability and AIoT intermediate node setting information including an AIoT registration area from the network node; configuring the terminal itself as an AIoT intermediate node; receiving an AIoT registration request and an uplink data transmission request from an AIoT terminal; and transmitting the AIoT registration request and the uplink data transmission request to the network node.

Images