Communication system

Abstract

The communication system of the present invention can communicate with an ultra-low power consumption IoT device, and comprises: a base station corresponding to a fifth generation wireless access system; a communication terminal connected to the base station; and a device connected to the base station or the communication terminal, the base station transmitting, to the communication terminal, setting information for communication and setting information for device data transmission, the setting information for communication being information relating to settings for communication between the communication terminal and the device. The setting information for device data transmission is information relating to a setting for transmitting device data acquired from a device to a base station by a communication terminal, and the communication terminal communicates with the device using the setting information for communication received from the base station. The device data is transmitted to the base station using the device data transmission setting information received from the base station.

Description

Technical Field

[0001] The present disclosure relates to wireless communication technology. Background Art

[0002] In the 3rd Generation Partnership Project (3GPP), a standardization organization for mobile communication systems, the fifth generation (hereinafter sometimes referred to as "5G") wireless access system is being explored (for example, Non-Patent Document 2) as a successor to Long Term Evolution (LTE) and Long Term Evolution Advanced (LTE-A), one of the fourth generation wireless access systems (see Non-Patent Document 1). The technology for the wireless section of 5G is called "New Radio Access Technology" ("New Radio" is abbreviated as "NR"). The NR system is being explored based on the LTE system and the LTE-A system.

[0003] For example, in Europe, the METIS organization is summarizing the requirements for 5G (see Non-Patent Document 3). In a 5G wireless access system, the system capacity is 1000 times greater than that of an LTE system, the data transmission speed is 100 times greater, the data processing delay is reduced to one-fifth (1 / 5), and the number of simultaneous connections of communication terminals is increased by 100 times. Furthermore, further reductions in power consumption and device costs are listed as requirements (see Non-Patent Document 3).

[0004] In order to meet such requirements, discussions on 5G standards are progressing in 3GPP (see Non-Patent Documents 4 to 23).

[0005] NR uses OFDM (Orthogonal Frequency Division Multiplexing) for downlink access and OFDM and DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) for uplink access. Also, like LTE and LTE-A, the 5G system does not include circuit switching and is a packet-based communication system.

[0006] NR uses higher frequencies than LTE to increase transmission speeds and reduce processing delays.

[0007] In NR, which sometimes uses higher frequencies than LTE, a narrow beam-shaped transmission and reception range is formed (beamforming) and the direction of the beam is changed (beam scanning), thereby ensuring cell coverage.

[0008] use Figure 1 This section explains the decisions made by 3GPP regarding the frame structure of the NR system as described in Non-Patent Document 1 (Chapter 5). Figure 1 This is an explanatory diagram showing the structure of a wireless frame used in an NR communication system. Figure 1 In NR, one radio frame is 10ms. The radio frame is divided into 10 subframes of equal size. The NR frame structure supports one or more parameter sets (Numerology), that is, one or more subcarrier spacings (Subcarrier spacing: SCS). In NR, one subframe is 1ms, and one time slot consists of 14 code elements, regardless of the subcarrier spacing. In addition, the number of time slots contained in one subframe is one when the subcarrier spacing is 15kHz, and the number of time slots in other subcarrier spacings increases in proportion to the subcarrier spacing (refer to non-patent document 11 (3GPPTS38.211)).

[0009] Non-Patent Document 2 (Chapter 5) and Non-Patent Document 11 record the decisions made by 3GPP regarding the channel structure in the NR system.

[0010] The Physical Broadcast Channel (PBCH) is a channel used for downlink transmissions from a base station (hereinafter sometimes referred to as a "base station") to a communication terminal device (hereinafter sometimes referred to as a "communication terminal" or "terminal"), such as a mobile terminal device (hereinafter sometimes referred to as a "mobile terminal"). The PBCH is transmitted together with a downlink synchronization signal.

[0011] The downlink synchronization signal in NR includes a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS). The synchronization signal is transmitted from the base station as a synchronization signal burst (SS burst, sometimes referred to as SS burst) at a specified cycle for a specified duration. The SS burst consists of a synchronization signal block (SS block, sometimes referred to as SS block) for each beam of the base station.

[0012] The base station changes the beam during the duration of the SS burst to transmit the SS block of each beam. The SS block consists of the P-SS, S-SS, and PBCH.

[0013] The Physical Downlink Control Channel (PDCCH) is a channel for downlink transmission from the base station to the communication terminal. PDCCH transmits downlink control information (DCI). DCI includes resource allocation information for the downlink shared channel (DL-SCH), one of the transmission channels described later, resource allocation information for the paging channel (PCH), one of the transmission channels described later, and HARQ (Hybrid Automatic Repeat request) information related to DL-SCH. In addition, DCI sometimes includes uplink scheduling grant. DCI sometimes includes a response signal for uplink transmission, namely Ack (Acknowledgement) / Nack (Negative Acknowledgement). In addition, in order to flexibly switch DL / UL within a time slot, DCI sometimes includes a time slot composition notification (Slot Format Indication: SFI). PDCCH or DCI is also called L1 / L2 control signal.

[0014] In NR, there is a time domain and frequency domain that are candidates for including the PDCCH. This area is called a control resource set (CORESET). The communication terminal monitors the CORESET and acquires the PDCCH.

[0015] The Physical Downlink Shared Channel (PDSCH) is a downlink transmission channel from a base station to a communication terminal. The PDSCH is mapped with the Downlink Shared Channel (DL-SCH) as a transport channel and the PCH as a transport channel.

[0016] The Physical Uplink Control Channel (PUCCH) is a channel for uplink transmission from the communication terminal to the base station. PUCCH transmits uplink control information (UCI). UCI includes response information (response signal) for downlink transmission, namely Ack / Nack, CSI (Channel State Information), Scheduling Request (SR), etc. CSI is composed of RI (Rank Indicator), PMI (Precoding Matrix Indicator), and CQI (Channel Quality Indicator) reports. RI refers to the rank information of the channel matrix in MIMO (Multiple Input Multiple Output). PMI refers to the information of the precoding waiting matrix used in MIMO. CQI is quality information indicating the quality of the received data or the quality of the communication line. UCI is sometimes transmitted through the PUSCH described later. PUCCH or UCI is also called L1 / L2 control signal.

[0017] The Physical Uplink Shared Channel (PUSCH) is an uplink transmission channel from a communication terminal to a base station. The Uplink Shared Channel (UL-SCH), one of the transport channels, is mapped to the PUSCH.

[0018] The Physical Random Access Channel (PRACH) is an uplink transmission channel from a communication terminal to a base station. The PRACH transmits a random access preamble.

[0019] The downlink reference signal (Reference Signal: RS) is a codeword known as a communication system of the NR mode. The following four downlink reference signals are defined. The UE-specific reference signal (UE-specific Reference Signal) is the data demodulation reference signal (Demodulation Reference Signal: DM-RS), the phase tracking reference signal (Phase Tracking Reference Signal: PT-RS), the positioning reference signal (Positioning Reference Signal: PRS), and the channel state information reference signal (Channel State Information Reference Signal: CSI-RS). As measurements of the physical layer of the communication terminal, there are reference signal received power (Reference Signal Received Power: RSRP) measurements and reference signal received quality (Reference Signal Received Quality: RSRQ) measurements.

[0020] Uplink reference signals are also symbols known as NR communication systems. The following three types of uplink reference signals are defined: the Data Demodulation Reference Signal (DM-RS), the Phase Tracking Reference Signal (PT-RS), and the Sounding Reference Signal (SRS).

[0021] The transport channels described in Non-Patent Document 2 (Chapter 5) are explained below. The broadcast channel (BCH) in the downlink transport channel is broadcast to the entire coverage area of ​​its base station (cell). The BCH is mapped to the physical broadcast channel (PBCH).

[0022] HARQ-based retransmission control is applied to the downlink shared channel (DL-SCH). DL-SCH can be broadcast to the entire coverage area of ​​the base station (cell). DL-SCH supports dynamic or semi-static resource allocation. Quasi-static resource allocation is also called semi-persistent scheduling. DL-SCH supports discontinuous reception (DRX) of communication terminals in order to reduce power consumption of communication terminals. DL-SCH is mapped to the physical downlink shared channel (PDSCH).

[0023] The Paging Channel (PCH) supports DRX in communication terminals to reduce power consumption. The PCH is broadcast to the entire coverage area of ​​a base station (cell). The PCH is mapped to physical resources such as the Physical Downlink Shared Channel (PDSCH), which can be dynamically used for traffic.

[0024] Retransmission control using HARQ is applied to the uplink shared channel (UL-SCH) within the uplink transport channel. The UL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also known as a configured grant. The UL-SCH is mapped to the physical uplink shared channel (PUSCH).

[0025] The Random Access Channel (RACH) is limited to control information. There is a risk of collision with the RACH. The RACH is mapped to the Physical Random Access Channel (PRACH).

[0026] The following explains HARQ. HARQ is a technology that improves the communication quality of transmission lines by combining Automatic Repeat Request (ARQ) and Forward Error Correction (Forward Error Correction). HARQ offers the advantage of enabling effective error correction through retransmissions, even for transmission lines with fluctuating communication quality. In particular, when performing retransmissions, the quality can be further improved by combining the initial and retransmission reception results.

[0027] An example of a retransmission method is described below. When the receiving side cannot correctly decode the received data, in other words, when a CRC (Cyclic Redundancy Check) error occurs (CRC = NG), the receiving side sends a "Nack" to the transmitting side. Upon receiving the "Nack," the transmitting side retransmits the data. When the receiving side can correctly decode the received data, in other words, when no CRC error occurs (CRC = OK), the receiving side sends an "Ack" to the transmitting side. Upon receiving the "Ack," the transmitting side transmits the next data.

[0028] Another example of the retransmission method is described below. If a CRC error occurs on the receiving side, a retransmission request is made from the receiving side to the sending side. The retransmission request is made by switching the NDI (New Data Indicator). The sending side, having received the retransmission request, retransmits the data. If no CRC error occurs on the receiving side, no retransmission request is made. If the sending side does not receive a retransmission request within the specified time, it is deemed that no CRC error has occurred on the receiving side.

[0029] The logical channels described in Non-Patent Document 1 (Chapter 6) are explained below. The Broadcast Control Channel (BCCH) is a downlink channel used to broadcast system control information. The BCCH, a logical channel, is mapped to the Broadcast Channel (BCH) or the Downlink Shared Channel (DL-SCH), a transport channel.

[0030] The Paging Control Channel (PCCH) is a downlink channel used to transmit paging information (PagingInformation) and changes to system information (SystemInformation). The PCCH, a logical channel, is mapped to the Paging Channel (PCH), a transport channel.

[0031] The Common Control Channel (CCCH) is a channel used to transmit control information between a communication terminal and a base station. The CCCH is used when there is no RRC connection between the communication terminal and the network. In the downlink direction, the CCCH is mapped to the downlink shared channel (DL-SCH), which serves as a transport channel. In the uplink direction, the CCCH is mapped to the uplink shared channel (UL-SCH), which serves as a transport channel.

[0032] The Dedicated Control Channel (DCCH) is a channel used to transmit dedicated control information between a communication terminal and the network in a point-to-point manner. The DCCH is used when an RRC connection exists between the communication terminal and the network. The DCCH is mapped to the Uplink Shared Channel (UL-SCH) in the uplink and to the Downlink Shared Channel (DL-SCH) in the downlink.

[0033] The Dedicated Traffic Channel (DTCH) is a channel used to transmit user information and conduct point-to-point communications with communication terminals. The DTCH exists in both the uplink and downlink. In the uplink, the DTCH is mapped to the Uplink Shared Channel (UL-SCH), and in the downlink, it is mapped to the Downlink Shared Channel (DL-SCH).

[0034] The location tracking of a communication terminal is performed in units of one or more cells. This tracking is performed to track the location of the communication terminal even in standby mode, allowing it to be called. The area used for tracking the location of the communication terminal is called a Tracking Area (TA).

[0035] NR supports calling of communication terminals within an area smaller than the tracking area. This area is called the RAN Notification Area (RNA). Paging of communication terminals in the RRC_INACTIVE state, described later, is performed within this area.

[0036] In NR, to support wider transmission bandwidths, carrier aggregation (CA), which aggregates (also called "aggregation") two or more component carriers (CCs), is being studied. CA is described in Non-Patent Document 1.

[0037] When CA is configured, the UE, a communication terminal, has a unique RRC connection with the network (Network: NW). In the RRC connection, one serving cell provides NAS (Non-Access Stratum) mobility information and security input. This cell is called the primary cell (Primary Cell: PCell). Based on the UE's capabilities (capabilities), secondary serving cells (SCells) are configured to form a serving cell group together with the PCell. For one UE, a serving cell group consisting of one PCell and one or more SCells is formed.

[0038] Furthermore, in 3GPP, there is Dual Connectivity (DC), in which a UE connects to two base stations for communication, in order to further increase communication capacity. DC is described in Non-Patent Documents 1 and 22.

[0039] Sometimes one of the base stations performing dual connectivity (DC) is called the "master base station (Master Node: MN)" and the other is called the "secondary base station (Secondary Node: SN)". The service cells formed by the master base station are sometimes collectively referred to as the master cell group (Master Cell Group: MCG), and the service cells formed by the secondary base stations are sometimes collectively referred to as the secondary cell group (Secondary Cell Group: SCG). In DC, the main cell in the MCG or SCG is called a special cell (Special Cell: SpCell or SPCell). The special cell in the MCG is called PCell, and the special cell in the SCG is called the primary SCG cell (PSCell).

[0040] In addition, in NR, the base station pre-sets a part of the carrier frequency band for the UE (hereinafter sometimes referred to as the Bandwidth Part: Bandwidth Part (BWP)), and the UE transmits and receives between itself and the base station in the BWP, thereby being able to reduce power consumption in the UE.

[0041] In addition, in 3GPP, the use of sidelink (SL) communication (also called PC5 communication) in both the EPS (Evolved Packet System) and the 5G core system described later (also referred to as PC5 communication) is discussed (see non-patent documents 1, 2, 26 to 28). In SL communication, communication is performed between terminals. As services using SL communication, there are, for example, V2X (Vehicle-to-everything) services and proxy services. In SL communication, not only direct communication between terminals, but also communication between UE and NW via relay is proposed (see non-patent documents 26 and 28).

[0042] The physical channels used for SL will be described below (see Non-Patent Documents 2 and 11). The physical sidelink broadcast channel (PSBCH) transmits information related to system synchronization and is sent from the UE.

[0043] The physical side link control channel (PSCCH) transmits control information from the UE for side link communication and V2X side link communication.

[0044] The physical sidelink shared channel (PSSCH) transmits data from the UE for sidelink communication and V2X sidelink communication.

[0045] The physical sidelink feedback channel (PSFCH) transmits HARQ feedback on the sidelink from the UE that receives the PSSCH transmission to the UE that transmits the PSSCH.

[0046] The transport channel used for SL will be described below (see Non-Patent Document 1). The sidelink broadcast channel (SL-BCH) has a predetermined transport channel format and is mapped to the PSBCH, which is a physical channel.

[0047] The sidelink shared channel (SL-SCH) supports broadcast transmissions. The SL-SCH supports both UE autonomous resource selection and resource allocation scheduled by the base station. UE autonomous resource selection carries a risk of conflict, but there is no conflict when the UE is allocated dedicated resources by the base station. Furthermore, the SL-SCH supports dynamic link adaptation by changing transmit power, modulation, and coding. The SL-SCH is mapped to the PSSCH, a physical channel.

[0048] The logical channels used for SL are described below (see Non-Patent Document 2). The Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel used to broadcast sidelink system information from one UE to other UEs. The SBCCH is mapped to the SL-BCH, which is a transport channel.

[0049] The Sidelink Traffic Channel (STCH) is a one-to-many sidelink traffic channel used to transmit user information from one UE to another. The STCH is used only by UEs with sidelink communication capabilities and UEs with V2X sidelink communication capabilities. One-to-one communication between two sidelink-capable UEs is also achieved separately via the STCH. The STCH is mapped to the SL-SCH, which serves as a transport channel.

[0050] The Sidelink Control Channel (SCCH) is a sidelink control channel used to transmit control information from one UE to other UEs. The SCCH is mapped to the SL-SCH, which is a transport channel.

[0051] In LTE, SL communication is limited to broadcast. In NR, in addition to broadcast, support for unicast and groupcast is also being studied as SL communication (see Non-Patent Document 27 (3GPP TS 23.287)).

[0052] In SL's unicast and multicast communications, HARQ feedback (Ack / Nack), CSI reporting, etc. are supported.

[0053] Furthermore, 3GPP is studying Integrated Access and Backhaul (IAB), in which both an access link between a UE and a base station and a backhaul link between base stations are wirelessly performed (see Non-Patent Documents 2, 20, and 29).

[0054] New technologies are required for mobile communication systems. For example, new technologies are needed to integrate ultra-low-power IoT (Internet of Things) devices into mobile communication systems, such as those that require no batteries or that communicate solely through energy storage without the need for replacement or recharging. 3GPP is already discussing these new technologies (Non-Patent Documents 30, 31, 32, and 33). Prior art literature Non-patent literature

[0055] Non-Patent Document 1: 3GPP TS36.300 V17.2.0 Non-Patent Document 2: 3GPP TS38.300 V17.2.0 Non-Patent Document 3: “Scenarios, requirements and KPIs for 5G mobile and wireless system”, ICT-317669-METIS / D1.1 Non-Patent Document 4: 3GPP TR23.799 V14.0.0 Non-Patent Document 5: 3GPP TR38.801 V14.0.0 Non-Patent Document 6: 3GPP TR38.802 V14.2.0 Non-Patent Document 7: 3GPP TR38.804 V14.0.0 Non-Patent Document 8: 3GPP TR38.912 V16.0.0 Non-Patent Document 9: 3GPP RP-172115 Non-Patent Document 10: 3GPP TS23.501 V17.6.0 Non-Patent Document 11: 3GPP TS38.211 V17.3.0 Non-Patent Document 12: 3GPP TS38.212 V17.3.0 Non-Patent Document 13: 3GPP TS38.213 V17.3.0 Non-Patent Document 14: 3GPP TS38.214 V17.3.0 Non-Patent Document 15: 3GPP TS38.321 V17.2.0 Non-Patent Document 16: 3GPP TS38.322 V17.1.0 Non-Patent Document 17: 3GPP TS38.323 V17.2.0 Non-Patent Document 18: 3GPP TS37.324 V17.0.0 Non-Patent Document 19: 3GPP TS38.331 V17.2.0 Non-Patent Document 20: 3GPP TS38.401 V17.2.0 Non-Patent Document 21: 3GPP TS38.413 V17.2.0 Non-Patent Document 22: 3GPP TS37.340 V17.2.0 Non-Patent Document 23: 3GPP TS38.423 V17.2.0 Non-Patent Document 24: 3GPP TS38.305 V17.2.0 Non-Patent Document 25: 3GPP TS 23.273 V17.6.0 Non-Patent Document 26: 3GPP TR23.703 V12.0.0 Non-Patent Document 27: 3GPP TS 23.287 V17.4.0 Non-Patent Document 28: 3GPP TS 23.303 V17.0.0 Non-Patent Document 29: 3GPP TS 38.340 V17.2.0 Non-Patent Document 30: 3GPP RP-222685 Non-Patent Document 31: 3GPP RP-222335 Non-Patent Document 32: 3GPP RP-222126 Non-Patent Document 33: 3GPP RP-222069 Non-Patent Document 34: 3GPP RP-222440 Non-Patent Document 35: 3GPP TS-38.101-1V17.6.0 Non-Patent Document 36: 3GPP TS-38.101-2 V17.7.0 Non-Patent Document 37: 3GPP TS 37.320 V17.1.0 Non-Patent Document 38: 3GPP TS32.422 V17.8.0 Summary of the Invention Technical problem to be solved by the invention

[0056] Since communications for a variety of services are performed in mobile communication systems, it is foreseeable that a large number of IoT devices such as wearable terminals and sensors will be used in the future. Therefore, it is required to use ultra-low power IoT devices that are battery-free or can communicate only through energy storage functions that do not need to be replaced or charged. New technologies are sought for incorporating such ultra-low power IoT devices into mobile communication systems. It is known that discussions on such new technologies have begun in 3GPP (non-patent documents 30, 31, 32, 33). However, there is currently no disclosure regarding methods for incorporating such ultra-low power IoT devices into mobile communication systems. For example, resources for communicating with ultra-low power IoT devices, communication methods between IoT devices and UE or gNB, etc. have not been disclosed, resulting in the inability to incorporate ultra-low power IoT devices into mobile communication systems and the inability to communicate.

[0057] In view of the above-mentioned problems, one of the objectives of the present disclosure is to realize a communication system capable of communicating with ultra-low power consumption IoT devices. Technical means for solving technical problems

[0058] The communication system of the present invention includes: a base station, which corresponds to a fifth-generation wireless access system; a communication terminal, which is connected to the base station; and a device, which is connected to the base station or the communication terminal. The base station sends communication setting information and device data sending setting information to the communication terminal. The above-mentioned communication setting information is information related to the settings for communication between the communication terminal and the device, and the above-mentioned device data sending setting information is information related to the settings for sending device data obtained from the device by the communication terminal to the base station. The communication terminal uses the communication setting information received from the base station to communicate with the device, and uses the device data sending setting information received from the base station to send device data to the base station. Effects of the Invention

[0059] According to the present disclosure, a communication system can be realized that enables communication with ultra-low power consumption IoT devices.

[0060] The objects, features, aspects and advantages of the present disclosure will become more apparent from the following detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 This is an explanatory diagram showing the structure of a wireless frame used in an NR communication system. Figure 2 This is a block diagram showing the overall structure of the NR communication system 210 discussed in 3GPP. Figure 3 This is a structural diagram of the DC based on the base station connected to the NG core. Figure 4 Yes Figure 2 A block diagram of the structure of the mobile terminal 202 is shown. Figure 5 Yes Figure 2 A block diagram of the structure of the base station 213 is shown. Figure 6 This is a block diagram showing the structure of the 5GC unit. Figure 7 This is a flowchart that outlines the cell search and standby actions performed by a communication terminal (UE) in an NR communication system. Figure 8 This is a diagram showing an example of a cell structure in an NR system. Figure 9 This is a connection structure diagram showing an example of the connection structure of terminals in SL communication. Figure 10 FIG. 1 is a diagram showing an example of a connection structure of a base station supporting access backhaul integration. Figure 11 This is a diagram showing an example of a sequence in which the UE transmits device data acquired from the device to the base station in the first embodiment. Figure 12 This is a diagram showing an example of a sequence in which a UE transmits device data acquired from a plurality of devices to a base station in the first embodiment. Figure 13 This is a diagram showing another sequence example in which the UE transmits device data acquired from a plurality of devices to the base station in the first embodiment. Figure 14 This is a diagram showing an example of a sequence in which a UE that is not connected to a base station transmits device data acquired from a device to the base station in the second embodiment. Figure 15 This is a diagram showing an example of a sequence of device data communication between a device and the NW in the third embodiment. Figure 16 This is a diagram showing a first other sequence example of device data communication between a device and a NW in the third embodiment. Figure 17 This is a diagram showing a second other sequence example of device data communication between the device and the NW in the third embodiment. Figure 18 This is a diagram showing a third other sequence example of device data communication between the device and the NW in the third embodiment. DETAILED DESCRIPTION

[0062] Implementation method 1. Figure 2 This is a block diagram showing the overall structure of a communication system 210 using the NR method discussed in 3GPP. Figure 2The radio access network is referred to as NG-RAN (Next Generation Radio Access Network) 211. A communication terminal device, i.e., a mobile terminal device (hereinafter referred to as "mobile terminal (User Equipment: UE)") 202, can wirelessly communicate with a base station device (hereinafter referred to as "NR base station (NG-RAN NodeB: gNB)") 213, and transmit and receive signals using wireless communication. NG-RAN 211 is composed of one or more NR base stations 213.

[0063] Here, the term "communication terminal device" includes not only mobile terminal devices such as mobile phone terminal devices but also immobile devices such as sensors. In the following description, the term "communication terminal device" may be simply referred to as "communication terminal."

[0064] The AS (Access Stratum) protocol is terminated between the UE 202 and the NG-RAN 211. Examples of AS protocols include RRC (Radio Resource Control), SDAP (Service Data Adaptation Protocol), PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical Layer). RRC is used in the control layer (hereinafter sometimes referred to as the C-layer, C-Plane, or CP), SDAP is used in the user layer (hereinafter sometimes referred to as the U-layer, U-Plane, or UP), and PDCP, MAC, RLC, and PHY are used in both the C and U layers.

[0065] The control protocol RRC (Radio Resource Control) between UE202 and NR base station 213 performs broadcast, paging, RRC connection management, etc. The states between NR base station 213 and UE202 in RRC include RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.

[0066] In RRC_IDLE, PLMN (Public Land Mobile Network) selection, broadcasting of system information (System Information: SI), paging, cell reselection, movement, etc. are performed. In RRC_CONNECTED, the mobile terminal has an RRC connection and can send and receive data with the network. In addition, in RRC_CONNECTED, handover (Handover: HO), measurement of neighbor cells, etc. are performed. RRC_INACTIVE maintains the connection between the 5G core unit 214 and the NR base station 213 while broadcasting of system information (System Information: SI), paging, cell reselection, movement, etc.

[0067] The gNB 213 is connected to the 5G core unit (hereinafter sometimes referred to as the "5GC" unit) 214 including the Access and Mobility Management Function (AMF), Session Management Function (SMF), or User Plane Function (UPF) through the NG interface. Communication of control information and / or user data is performed between the gNB 213 and the 5GC unit 214. The NG interface is a general term for the N2 interface between the gNB 213 and the AMF 220, the N3 interface between the gNB 213 and the UPF 221, the N11 interface between the AMF 220 and the SMF 222, and the N4 interface between the UPF 221 and the SMF 222. One gNB 213 can be connected to multiple 5GC units 214. The gNBs 213 are connected to each other through the Xn interface, and communication of control information and / or user data is performed between the gNBs 213.

[0068] The 5GC unit 214 is an upper device, specifically an upper node, and controls the connection between the NR base station 213 and the mobile terminal (UE) 202, allocates paging signals to one or more NR base stations (gNB) 213 and / or LTE base stations (E-UTRAN NodeB: eNB), etc. In addition, the 5GC unit 214 performs mobility control in the idle state. The 5GC unit 214 manages the tracking area list when the mobile terminal 202 is in the idle state and in the inactive state and active state. The 5GC unit 214 starts the paging protocol by sending a paging message to the cell belonging to the tracking area where the mobile terminal 202 is registered.

[0069] gNB213 can constitute one or more cells. When one gNB213 constitutes multiple cells, each cell is configured to be able to communicate with UE202.

[0070] The gNB 213 can be divided into a central unit (CU) 215 and a distributed unit (DU) 216. A CU 215 is configured as one in the gNB 213. A DU 216 is configured as one or more in the gNB 213. One DU 216 constitutes one or more cells. The CU 215 is connected to the DU 216 via the F1 interface, and control information and / or user data are communicated between the CU 215 and the DU 216. The F1 interface consists of the F1-C interface and the F1-U interface. The CU 215 is responsible for the functions of the RRC, SDAP, and PDCP protocols, while the DU 216 is responsible for the functions of the RLC, MAC, and PHY protocols. One or more TRPs (Transmission Reception Points) 219 are sometimes connected to the DCU 216. The TRP 219 transmits and receives wireless signals to and from the UE.

[0071] The CU 215 can be divided into a C-layer CU (CU-C) 217 ​​and a U-layer CU (CU-U) 218. A single CU-C 217 is provided in the CU 215. One or more CU-Us 218 are provided in the CU 215. The CU-C 217 is connected to the CU-U 218 via the E1 interface, and control information is communicated between the two CUs. The CU-C 217 is connected to the DU 216 via the F1-C interface, and control information is communicated between the two CUs. The CU-U 218 is connected to the DU 216 via the F1-U interface, and user data is communicated between the CU-U 218 and the DU 216.

[0072] The 5G communication system may include the Unified Data Management (UDM) function and the Policy Control Function (PCF) described in Non-Patent Document 10 (3GPP TS 23.501). UDM and / or PCF may be included in Figure 2 In the 5GC section 214.

[0073] In 5G communication systems, a location management function (LMF) described in non-patent document 24 (3GPP TS 38.305) can be provided. As disclosed in non-patent document 25 (3GPP TS 23.273), the LMF can be connected to a base station via an AMF.

[0074] 5G communication systems may also include the Non-3GPP Interworking Function (N3IWF) described in Non-Patent Document 10 (3GPP TS 23.501). The N3IWF can use the Access Network (AN) as a terminal between the UE and the N3IWF in non-3GPP access with the UE.

[0075] Figure 3 This is a diagram showing a structure based on DC (dual connection) connected to the NG core. Figure 3 In the figure, the solid line represents the connection of the U-Plane, and the dotted line represents the connection of the C-Plane. Figure 3 In the example, the primary base station 240-1 can be a gNB or an eNB. In addition, the secondary base station 240-2 can be a gNB or an eNB. Figure 3 In the DC structure where the primary base station 240-1 is a gNB and the secondary base station 240-2 is an eNB is sometimes referred to as NG-EN-DC. Figure 3In the example, the U-Plane connection between the 5GC unit 214 and the secondary base station 240-2 is performed via the master base station 240-1, but it can also be performed directly between the 5GC unit 214 and the secondary base station 240-2. Figure 3 In the present invention, the core network connected to the LTE system and LTE-A system, namely the EPC (Evolved Packet Core), can be connected to the primary base station 240-1 instead of the 5GC unit 214. The U-Plane connection between the EPC and the secondary base station 240-2 can be directly established.

[0076] Figure 4 Yes Figure 2 The structure of the mobile terminal 202 is shown in FIG. Figure 4 The transmission processing of the mobile terminal 202 shown in FIG. First, control data from the control unit 310 and user data from the application unit 302 are sent to the protocol processing unit 301. Buffering of control data and user data may be performed. This buffering can be implemented in the control unit 310, the application unit 302, or the protocol processing unit 301. The protocol processing unit 301 performs protocol processing such as SDAP, PDCP, RLC, and MAC. For example, it determines the target base station for transmission in DC and other protocols and adds headers to each protocol. Data that has undergone protocol processing is transferred to the encoding unit 304 for encoding, such as error correction. Data may be directly output from the protocol processing unit 301 to the modulation unit 305 without undergoing encoding. The data encoded by the encoding unit 304 is modulated in the modulation unit 305. MIMO precoding may also be performed in the modulation unit 305. The modulated data is converted to a baseband signal and then output to the frequency conversion unit 306 for conversion to a wireless transmission frequency. After that, the transmission signal is sent from antennas 307-1 to 307-4 to base station 213. Figure 4 , the example shows a case where the number of antennas is 4, but the number of antennas is not limited to 4.

[0077] In addition, the reception processing of the mobile terminal 202 is performed as follows. The wireless signal from the base station 213 is received through the antennas 307-1 to 307-4. The received signal is converted from the wireless reception frequency to a baseband signal by the frequency conversion unit 306 and demodulated by the demodulation unit 308. In the demodulation unit 308, waiting calculation and multiplication processing can be performed. The demodulated data is transmitted to the decoding unit 309, and decoding processing such as error correction is performed. The decoded data is transmitted to the protocol processing unit 301, and protocol processing such as MAC, RLC, PDCP, SDAP, etc. is performed, such as the removal of headers in each protocol. Of the data that has undergone protocol processing, control data is transmitted to the control unit 310, and user data is transmitted to the application unit 302.

[0078] A series of processes of the mobile terminal 202 are controlled by the control unit 310. Figure 4 Although omitted in FIG. 3 , the control unit 310 is also connected to each of the units 302 and 304 to 309 .

[0079] Each part of the mobile terminal 202, such as the control unit 310, the protocol processing unit 301, the encoding unit 304, and the decoding unit 309, is implemented by a processing circuit composed of a processor and a memory. For example, the control unit 310 is implemented by the processor executing a program that describes a series of processes of the mobile terminal 202. The program that describes a series of processes of the mobile terminal 202 is stored in the memory. Examples of memories are non-volatile or volatile semiconductor memories such as RAM (Random Access Memory), ROM (Read Only Memory), and flash memory. Each part of the mobile terminal 202, such as the control unit 310, the protocol processing unit 301, the encoding unit 304, and the decoding unit 309 can be implemented by a dedicated processing circuit such as FPGA (Field Programmable Gate Array), ASIC (Application Specific Integrated Circuit), or DSP (Digital Signal Processor). In Figure 4 In the embodiment, the number of antennas used by the mobile terminal 202 for sending and the number of antennas used for receiving may be the same or different.

[0080] Figure 5 Yes Figure 2 The block diagram of the structure of the base station 213 is shown. Figure 5 2. The transmission processing of the base station 213 shown in FIG. 2 is explained. The EPC communication unit 401 transmits and receives data between the base station 213 and the EPC. The 5GC communication unit 412 transmits and receives data between the base station 213 and the 5GC (5GC unit 214, etc.). The other base station communication units 402 transmit and receive data with other base stations. The EPC communication unit 401, the 5GC communication unit 412, and the other base station communication units 402 exchange information with the protocol processing unit 403 respectively. The control data from the control unit 411, and the user data and control data from the EPC communication unit 401, the 5GC communication unit 412, and the other base station communication units 402 are sent to the protocol processing unit 403. Buffering of control data and user data can be performed. The buffering of control data and user data can be set in the control unit 411, in the EPC communication unit 401, in the 5GC communication unit 412, or in the other base station communication units 402.

[0081] The protocol processing unit 403 performs protocol processing such as SDAP, PDCP, RLC, and MAC, for example, routing of transmission data in DC, assigning headers in each protocol, and other actions. The data that has undergone protocol processing is transmitted to the coding unit 405, and coding processing such as error correction is performed. There may also be data that is directly output from the protocol processing unit 403 to the modulation unit 406 without performing coding processing. In addition, data can be sent from the protocol processing unit 403 to other base station communication units 402. For example, in DC, data sent from the 5GC communication unit 412 or the EPC communication unit 401 can be sent to other base stations, such as auxiliary base stations, via other base station communication units 402. The coded data is modulated in the modulation unit 406. Precoding in MIMO can also be performed in the modulation unit 406. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 407 and converted into a wireless transmission frequency. Thereafter, the transmission signal is sent to one or more mobile terminals 202 using antennas 408-1 to 408-4. In Figure 5 , the example shows a case where the number of antennas is 4, but the number of antennas is not limited to 4.

[0082] Furthermore, base station 213 performs reception processing as follows. Radio signals from one or more mobile terminals 202 are received by antennas 408-1 to 408-4. The received signal is converted from the radio reception frequency to a baseband signal by frequency conversion unit 407 and demodulated by demodulation unit 409. The demodulated data is transmitted to decoding unit 410 for decoding processing such as error correction. The decoded data is transmitted to protocol processing unit 403, which performs protocol processing such as MAC, RLC, PDCP, and SDAP, such as removing headers from each protocol. Of the data that has undergone protocol processing, control data is transmitted to control unit 411, 5GC communication unit 412, EPC communication unit 401, or another base station communication unit 402, while user data is transmitted to 5GC communication unit 412, EPC communication unit 401, or another base station communication unit 402. Data transmitted from another base station communication unit 402 can be transmitted to 5GC communication unit 412 or EPC communication unit 401. The data may be, for example, uplink data sent to the 5GC communication unit 412 or the EPC communication unit 401 via other base stations in DC.

[0083] A series of processing of the base station 213 is controlled by the control unit 411. Figure 5 Although omitted in the figure, the control unit 411 is also connected to the parts 401, 402, 405 to 410, and 412.

[0084] Each part of the base station 213, such as the control unit 411, the protocol processing unit 403, the 5GC communication unit 412, the EPC communication unit 401, the other base station communication unit 402, the encoding unit 405, and the decoding unit 410, is implemented by a processing circuit including a processor and a memory, or a dedicated processing circuit such as an FPGA, an ASIC, or a DSP, similar to the mobile terminal 202. Figure 5 In the example, the number of antennas used by the base station 213 for sending may be the same as or different from the number of antennas used for receiving.

[0085] As Figure 2 The example of the structure of CU215 is shown, except Figure 5 In addition to the coding unit 405, modulation unit 406, frequency conversion unit 407, antennas 408-1 to 408-4, demodulation unit 409, and decoding unit 410 shown, a configuration may also include a DU communication unit. The DU communication unit is connected to the protocol processing unit 403. The protocol processing unit 403 in the CU 215 performs protocol processing such as PDCP and SDAP.

[0086] As Figure 2 The example of the structure of DU216 is shown, except Figure 5 In addition to the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown, a configuration with a CU communication unit may also be used. The CU communication unit is connected to the protocol processing unit 403. The protocol processing unit 403 in the DU 216 performs protocol processing such as PHY, MAC, and RLC.

[0087] Figure 6 This is a block diagram showing the structure of the 5GC unit. Figure 6 The above is shown in Figure 2 The structure of the 5GC unit 214 is shown. Figure 6 Shown in Figure 2 The 5GC unit 214 shown includes the AMF structure, the SMF structure, and the UPF structure. Figure 6In the example shown, the AMF may have the function of a control layer control unit 525, the SMF may have the function of a session management unit 527, and the UPF may have the functions of a user layer communication unit 523 and a data network communication unit 521. The data network communication unit 521 performs data transmission and reception between the 5GC unit 214 and the data network. The base station communication unit 522 performs data transmission and reception between the 5GC unit 214 and the base station 21 via the NG interface. User data sent from the data network is transmitted from the data network communication unit 521 to the base station communication unit 522 via the user layer communication unit 523 and is sent to one or more base stations 213. User data sent from the base station 213 is transmitted from the base station communication unit 522 to the data network communication unit 521 via the user layer communication unit 523 and is sent to the data network.

[0088] Control data transmitted from the base station 21 is transmitted from the base station communication unit 522 to the control layer control unit 525. The control layer control unit 525 may transmit the control data to the session management unit 527. Control data may be transmitted from the data network. Control data transmitted from the data network may be transmitted from the data network communication unit 521 to the session management unit 527 via the user layer communication unit 523. The session management unit 527 may transmit the control data to the control layer control unit 525.

[0089] The user plane control unit 523 includes a PDU processing unit 523-1, a mobility anchor unit 523-2, and other components, and performs overall processing for the user plane (hereinafter sometimes referred to as the U-Plane). The PDU processing unit 523-1 processes data packets, such as sending and receiving packets with the data network communication unit 521 and with the base station communication unit 522. The mobility anchor unit 523-2 is responsible for connecting data paths when the UE is mobile.

[0090] The session management unit 527 manages the PDU session established between the UE and the UPF. The session management unit 527 includes a PDU session control unit 527-1, a UE IP address allocation unit 527-2, and other functions. The PDU session control unit 527-1 manages the PDU session between the mobile terminal 202 and the 5GC unit 214. The UE IP address allocation unit 527-2 allocates an IP address to the mobile terminal 202.

[0091] The control plane control unit 525 includes a NAS security unit 525-1 and an idle state mobility management unit 525-2, and performs overall processing for the control plane (hereinafter sometimes referred to as the C-Plane). The NAS security unit 525-1 performs security protection for NAS (Non-Access Stratum) messages, etc. The idle state mobility management unit 525-2 manages mobility in the idle state (idle state: RRC_IDLE state, or simply idle), generates and controls paging signals in the idle state, and adds, deletes, updates, retrieves, and manages the tracking area list for one or more mobile terminals 202 within the coverage area.

[0092] A series of processing of the 5GC unit 214 is controlled by the control unit 526. Figure 6 Although omitted in the figure, the control unit 526 is connected to each unit 521 to 523, 525, and 527. As with the control unit 310 of the mobile terminal 202, each component of the 5GC unit 214 is implemented by, for example, a processing circuit including a processor and a memory, or a dedicated processing circuit such as an FPGA, ASIC, or DSP.

[0093] Next, an example of a cell search method in a communication system is shown. Figure 7 This flowchart outlines the cell search and standby operations performed by a communication terminal (UE) in an NR communication system. Once the communication terminal initiates a cell search, in step ST601, it synchronizes slot timing and frame timing using the primary synchronization signal (P-SS) and secondary synchronization signal (S-SS) transmitted from neighboring base stations.

[0094] The P-SS and S-SS are collectively referred to as the Synchronization Signal (SS). The SS contains a synchronization code that corresponds one-to-one with the physical cell identifier (PCI) assigned to each cell. The number of PCIs is set to 1008. Communication terminals use these 1008 PCIs to achieve synchronization and detect (determine) the PCI of the synchronized cell.

[0095] In step ST602, the communication terminal receives the PBCH for the next cell to which it is synchronized. The Master Information Block (MIB), which contains cell structure information, is mapped to the BCCH on the PBCH. Therefore, by receiving the PBCH and obtaining the BCCH, the MIB can be obtained. MIB information includes, for example, the SFN (System Frame Number), scheduling information for SIB (System Information Block) 1, subcarrier spacing for SIB1, and DM-RS position information.

[0096] In addition, the communication terminal obtains the SS block identifier through the PBCH. A portion of the SS block identifier bit column is included in the MIB. The remaining bit column is included in the identifier used to generate the DM-RS sequence accompanying the PBCH. The communication terminal uses the MIB included in the PBCH and the DM-RS sequence accompanying the PBCH to obtain the SS block identifier.

[0097] Next, in step ST603, the communication terminal measures the received power of the SS block.

[0098] Next, in step ST604, the communication terminal selects the cell with the best reception quality from the one or more cells detected up to step ST603, for example, the cell with the highest received power, i.e., the best cell. Furthermore, the communication terminal selects the beam with the best reception quality, for example, the beam with the highest received power per SS block, i.e., the best beam. The best beam is selected using, for example, the received power of each SS block identified.

[0099] Next, in step ST605, the communication terminal receives the DL-SCH based on the scheduling information in SIB1 contained in the MIB, and obtains SIB1 from the broadcast information BCCH. SIB1 contains information related to access to the cell, cell configuration information, and scheduling information for other SIBs (SIBk: an integer k ≥ 2). SIB1 also contains the Tracking Area Code (TAC).

[0100] Then, in step ST606, the communication terminal compares the TAC of SIB1 received in step ST605 with the TAC portion of the Tracking Area Identity (TAI) in the tracking area list already held by the communication terminal. The tracking area list is also called the TAI list (TAIlist). TAI is identification information used to identify the tracking area and consists of MCC (Mobile Country Code), MNC (Mobile Network Code), and TAC (Tracking Area Code). MCC is the country code. MNC is the network code. TAC is the code number of the tracking area.

[0101] If the comparison result in step ST606 indicates that the TAC received in step ST605 is the same as the TAC included in the tracking area list, the communication terminal enters standby mode in that cell. If the TAC received in step ST605 is not included in the tracking area list, the communication terminal passes through that cell and requests a tracking area change from the core network (EPC) including the MME, thereby performing a TAU (Tracking Area Update).

[0102] The core network device (hereinafter sometimes referred to as the "core network device") updates the tracking area list based on the TAU request signal and the identification number (UE-ID, etc.) of the communication terminal sent from the communication terminal. The core network device sends the updated tracking area list to the communication terminal. The communication terminal rewrites (updates) its TAC list based on the received tracking area list. The communication terminal then enters standby mode in the cell.

[0103] Next, examples of random access methods in a communication system are described. Four-step random access and two-step random access are used for random access. Four-step random access and two-step random access include contention-based random access (i.e., random access that may cause timing contention with other mobile terminals) and contention-free random access.

[0104] This example shows a four-step contention-based random access method. In step 1, the mobile terminal transmits a random access preamble to the base station. The random access preamble can be selected by the mobile terminal from a specified range or individually assigned to the mobile terminal and notified by the base station.

[0105] As step 2, the base station sends a random access response to the mobile terminal. The random access response includes the uplink scheduling information used in step 3, the terminal identity used in the uplink transmission in step 3, and the like.

[0106] As step 3, the mobile terminal performs an uplink transmission to the base station. The mobile terminal uses the information acquired in step 2 in the uplink transmission. As step 4, the base station notifies the mobile terminal whether contention resolution has occurred. Mobile terminals notified of no contention complete the random access process. Mobile terminals notified of a contention process restart the process from step 1.

[0107] The contention-free 4-step random access method differs from the contention-based 4-step random access method in the following respects: Prior to step 1, the base station pre-allocates a random access preamble and uplink scheduling to the mobile terminal. Furthermore, notification of contention resolution in step 4 is unnecessary.

[0108] This example illustrates a two-step random access method based on contention. In step 1, the mobile terminal transmits a random access preamble and an uplink transmission to the base station. In step 2, the base station notifies the mobile terminal of the presence of a contention. A mobile terminal notified of the absence of a contention completes the random access process. A mobile terminal notified of a contention restarts the process from step 1.

[0109] The contention-free 2-step random access method differs from the contention-based 2-step random access method in the following respects: Prior to step 1, the base station pre-allocates a random access preamble and uplink scheduling to the mobile terminal. Furthermore, in step 2, the base station transmits a random access response to the mobile terminal.

[0110] Figure 8 This shows an example of the structure of a cell in NR. In a cell in NR, a narrow beam is formed and its direction is changed for transmission. Figure 8 In the example shown, base station 750 uses beam 751-1 at certain times to transmit and receive signals with a mobile terminal. At other times, base station 750 uses beam 751-2 to transmit and receive signals with the mobile terminal. Similarly, base station 750 uses one or more of beams 751-3 through 751-8 to transmit and receive signals with the mobile terminal. Thus, base station 750 forms a wide-area cell 752.

[0111] exist Figure 8 In FIG. 8 , an example is shown in which the number of beams used by the base station 750 is set to 8, but the number of beams may be different from 8. Figure 8 In the example shown, the number of beams used simultaneously by the base station 750 is set to one, but it can also be multiple.

[0112] Beam identification uses the concept of QCL (Quasi-CoLocation) (see non-patent document 14 (3GPP TS 38.214)). That is, it is identified by information indicating which reference signal (e.g., SS block, CSI-RS) the beam can be considered to be the same as. This information sometimes includes information about the type of viewpoint that can be considered the same beam, such as information about Doppler shift, Doppler shift spread, average delay, average delay spread, and spatial Rx parameters (see non-patent document 14 (3GPP TS 38.214)).

[0113] 3GPP supports Side Link (SL) for D2D (Device to Device) communication and V2V (Vehicle to Vehicle) communication (see Non-Patent Documents 1 and 16). SL is defined by the PC5 interface.

[0114] In SL communications, support for PC5-S signaling is being studied to support unicast and groupcast in addition to broadcast (see Non-Patent Document 27 (3GPP TS 23.287)). For example, PC5-S signaling is implemented to establish a SL link, or link for PC5 communications. This link is implemented in the V2X layer and is also called a Layer 2 link.

[0115] In addition, support for RRC signaling in SL communications is under study (see Non-Patent Document 27 (3GPP TS 23.287)). RRC signaling in SL communications is also referred to as PC5 RRC signaling. For example, proposals include notifying UEs performing PC5 communications of their capabilities, or notifying AS layer settings for V2X communications using PC5 communications.

[0116] Figure 9 An example of a connection structure of a mobile terminal in SL communication is shown in FIG. Figure 9 In the example shown, UEs 805 and 806 are within coverage 803 of base station 801. UL / DL communication 807 is conducted between base station 801 and UE 805. UL / DL communication 808 is conducted between base station 801 and UE 806. SL communication 810 is conducted between UE 805 and UE 806. UEs 811 and 812 are outside coverage 803. SL communication 814 is conducted between UE 805 and UE 811. Furthermore, SL communication 816 is conducted between UE 811 and UE 812.

[0117] As an example of communication between UE and NW via relay in SL communication, Figure 9UE 805 is shown relaying communications between UE 811 and base station 801 .

[0118] UEs that relay sometimes use Figure 4 Same structure. Use Figure 4 The relay processing in the UE is explained. The relay processing in UE 805 during communication from UE 811 to base station 801 is explained. Wireless signals from UE 811 are received via antennas 307-1 to 307-4. The received signal is converted from the wireless reception frequency to a baseband signal by frequency converter 306 and demodulated by demodulator 308. Demodulator 308 can perform latency calculations and multiplication. The demodulated data is transferred to decoder 309 for decoding processing such as error correction. The decoded data is transferred to protocol processor 301, which performs protocol processing such as MAC and RLC for communication with UE 811, such as removing headers in each protocol. Furthermore, protocol processing such as RLC and MAC for communication with base station 801, such as adding headers in each protocol, is performed. Protocol processor 301 in UE 811 may also perform protocol processing for PDCP and SDAP. The data that has undergone protocol processing is transmitted to the encoding unit 304, where it undergoes encoding processing such as error correction. Some data may be directly output from the protocol processing unit 301 to the modulation unit 305 without undergoing encoding processing. The data encoded by the encoding unit 304 is modulated in the modulation unit 305. MIMO precoding may also be performed in the modulation unit 305. The modulated data is converted into a baseband signal and then output to the frequency conversion unit 306 for conversion to a wireless transmission frequency. The transmission signal is then transmitted from antennas 307-1 to 307-4 to the base station 801.

[0119] In the above description, an example of relaying by UE 805 in communication from UE 811 to base station 801 is shown, but the same process is also used in relaying communication from base station 801 to UE 811.

[0120] 5G base stations can support integrated access and backhaul (Integrated Access and Backhaul: IAB) (see non-patent documents 2 and 20). A base station that supports IAB (hereinafter sometimes referred to as an IAB base station) is composed of a CU of a base station that acts as an IAB host providing IAB functions, namely, an IAB host CU, a DU of a base station that acts as an IAB host, namely, an IAB host DU, and an IAB node that uses a wireless interface to connect to the IAB host DU and to the UE. An F1 interface is set between the IAB node and the IAB host CU (see non-patent document 2).

[0121] Figure 10shows an example of an IAB base station connection. An IAB host CU 901 is connected to an IAB host DU 902. An IAB node 903 is connected to the IAB host DU 902 using a wireless interface. IAB node 903 is connected to an IAB node 904 using a wireless interface. In other words, multi-level connections of IAB nodes may be made. A UE 905 is connected to an IAB node 904 using a wireless interface. A UE 906 may be connected to an IAB node 903 using a wireless interface, and a UE 907 may be connected to an IAB host 902 using a wireless interface. Multiple IAB host DUs 902 may be connected to the IAB host CU 901, multiple IAB nodes 903 may be connected to the IAB host DU 902, and multiple IAB nodes 904 may be connected to the IAB node 903.

[0122] The BAP (Backhaul Adaptation Protocol) layer is used in the connection between the IAB host DU and IAB nodes, and in the connection between IAB nodes (see Non-Patent Document 29). The BAP layer performs operations such as routing received data to the IAB host DU and / or IAB nodes and mapping it to RLC channels (see Non-Patent Document 29).

[0123] As an example of the structure of the IAB host CU, the same structure as that of the CU 215 is used.

[0124] As an example of the structure of the IAB host DU, the same structure as DU 216 is used. The protocol processing unit of the IAB host DU performs BAP layer processing, such as adding a BAP header to downlink data, routing to IAB nodes, and removing the BAP header from uplink data.

[0125] As an example of the structure of an IAB node, sometimes in addition to Figure 5 The structure other than the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown.

[0126] use Figure 5 、 Figure 10To illustrate the transmission and reception processing in the IAB node. The transmission and reception processing of the IAB node 903 in the communication between the IAB host CU representation 901 and the UE representation 905 is explained. In the uplink communication from the UE905 to the IAB host CU901, the wireless signal from the IAB node 904 is received through the antenna 408 (part or all of the antennas 408-1 to 408-4). The received signal is converted from the wireless reception frequency to a baseband signal by the frequency conversion unit 407, and demodulated in the demodulation unit 409. The demodulated data is transmitted to the decoding unit 410 for decoding processing such as error correction. The decoded data is transmitted to the protocol processing unit 403, and protocol processing such as MAC, RLC, etc. for communication with the IAB node 904, such as the removal of headers in each protocol, is performed. In addition, routing to the IAB host DU902 using the BAP header is performed, and protocol processing such as RLC and MAC for communication with the IAB host DU902, such as the addition of headers in each protocol, is performed. The data that has undergone protocol processing is transmitted to the encoding unit 405 and subjected to encoding processing such as error correction. There may also be data that is directly output from the protocol processing unit 403 to the modulation unit 406 without undergoing encoding processing. The encoded data is modulated in the modulation unit 406. Precoding in MIMO may also be performed in the modulation unit 406. After the modulated data is converted into a baseband signal, it is output to the frequency conversion unit 407 and converted into a wireless transmission frequency. Thereafter, the transmission signal is transmitted to the IAB host DU902 using antennas 408-1 to 408-4. The same processing is also performed in the downlink communication from the IAB host CU901 to the UE905.

[0127] IAB node 904 also performs the same transmission and reception processing as IAB node 903. The protocol processing unit 403 of IAB node 903 performs BAP layer processing, such as adding a BAP header in uplink communications and routing to IAB node 904, and removing the BAP header in downlink communications.

[0128] 3GPP is exploring the integration of ultra-low-power IoT devices (hereinafter sometimes referred to as "devices") into mobile communication systems. It is proposed that ultra-low-power IoT devices communicate with UEs or base stations using a communication method different from the communication method used for the air interface specified in the existing 3GPP (Non-Patent Documents 31, 33, and 34). When integrating devices into mobile communication systems, it is assumed that the UE communicating with the device must also communicate with the network. A method is disclosed that enables the UE to communicate with the device and the network.

[0129] Communication between a device and a UE is direct communication between the device and the UE, and communication between a device and a base station is direct communication between the device and the base station. Communication between UEs is direct communication between UEs, and communication between a UE and a base station is direct communication between the UE and the base station.

[0130] The communication between the device and the UE may also be the communication between the device and the UE for communication between the device and the NW via the UE.

[0131] To incorporate a device into the mobile communication system, the base station transmits a UE-device communication configuration to the UE. The base station may transmit a device data transmission configuration from the UE to the base station to the UE.

[0132] The method for sending these settings from the base station to the UE is disclosed. The base station can broadcast this setting information. The base station can include this setting information in a SIB. The base station can broadcast the SIB. Since it can be sent to the entire cell, UEs present in the cell area can receive the setting information. The base station can send this setting information individually to the UE. The base station can send this setting information to the UE through RRC signaling. This setting information can be included in an RRC message for transmission. For example, it can be included in an RRC reconfiguration message for transmission. Since it can be sent individually to the UE, UE-specific setting information can be sent.

[0133] Other methods are disclosed. The base station can send this setting information through MAC signaling. For example, it can be included in the MAC CE and sent. The base station can multiplex this setting information with other MAC data and send it to the UE. It can be sent together with other data, thereby enabling efficient transmission. Other methods are disclosed. The base station can send this setting information through L1 / L2 signaling. The base station can include this setting information in the DCI. The base station can send this DCI to the UE via the PDCCH. This setting information can be sent as early as possible.

[0134] The following discloses 14 examples of configuration information for UE-device communication.

[0135] (1) Communication frequency information. (2) Communication time information. (3) Information during communication. (4) Time information. (5) Communication area information. (6) Grouping information. (7) Receive quality information. (8) Information related to the service. (9) Information related to the equipment. (10) Information related to the sending source node. (11) Information sent from UE to device. (12) Information related to the beam. (13) Information related to interference. (14) A combination of (1) to (13).

[0136] (1) Information related to the frequency at which UE-device communication is performed. For example, it may be frequency, frequency band, etc. For example, it may be BWP information. For example, it may be RB (Resource Block) or subcarrier information. For example, it may be information related to the subcarrier spacing. This information may be one or more. (2) Information related to the time at which UE-device communication is performed. For example, it may be communication start time, communication end time, communication time interval, cycle, offset, etc. For example, it may be information related to code element length. This information may be one or more. The time unit may be time, and the time unit used between UE and base station may be used. The time unit used between UE and base station may be, for example, code element, time slot, subframe, TTI (Transmission Timing Interval), radio frame, etc. By using the time unit used between UE and base station, the control of UE becomes easier. (3) Information related to the period during which UE-device communication is performed. It may be the UE-device communication service period. During this communication period, communication is performed, for example, at the time disclosed in (2). This information may be one or more. The communication period may be set as a timer setting. It is possible to set a timer to enable UE-device communication and disable UE-device communication when the timer expires. By setting the communication time (2) and the communication period (3), it is possible to provide services that require regular or periodic communication with devices.

[0137] (4) is information for setting time for UE. The absolute time on the NW side can be sent. This information can be one or more. Based on the received time, the UE can derive, for example, the communication time with the device. In this way, time synchronized between UEs can be used. Time information can be notified to the device. Time information can be sent to the device from the base station or the UE. For example, it can be used when information representing time is derived from the data acquisition time in the device. Time information synchronized between devices can be used.

[0138] (5) It is information about the area where UE-device communication is possible. It can be information about the area where UE-device communication is not possible (or prohibited). One or more areas can be set as a list. It can be set as a list of areas for inter-device communication. This information can be one or more. As area information, for example, it can be a beam, a cell, a base station, RNA (RAN Notification Area), a TA, a LAMN, an NPN (Non-Public Network), etc. The information used to determine these can be, for example, an identifier. For example, it can be an identifier of a beam that can communicate with UE-device, etc.

[0139] One or more devices can be grouped. (6) is information about the group to which one or more devices belong. It can be information about which device is assigned to which group. This information can be one or more. As a method of grouping, there are, for example, each service, each device type, each area, etc. As types of services, there are, for example, devices for asset management services, devices for temperature management services, services for specified companies, etc. As types of devices, there are, for example, speed / acceleration sensor devices, temperature sensor devices, pressure sensor devices, etc. Information for determining a device group can be set. This information can be, for example, a device group ID. Information that associates a device group ID with a device ID belonging to the device group ID can be set.

[0140] (7) is information related to the reception quality from the device that enables UE-device communication. It can be information related to the reception quality from the device that does not enable UE-device communication. This information can be one or more. As reception quality information, for example, it can be reception quality, reception power, RSSI (Received Signal Strength Indicator: received signal strength indication), SINR (Signal to Interference plus Noise Ratio: signal-to-noise ratio), etc. In addition, the reception quality information can be, for example, the bit error rate. It can be BER (Bit Error Rate: bit error rate) or FER (Frame Error Rate: frame error rate). A specified value can be set for whether UE-device communication can be performed or not. It can be set as a threshold.

[0141] (8) is information related to services using UE-device communication. For example, there are devices for asset management services, devices for temperature management services, services for specified companies, etc. For example, it can be eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communication), URLLC (Ultra-Reliability Low Latency Communication). This information can be one or more. Information used to determine the service can be set. This information can be, for example, a service identifier. Information obtained by associating the service identifier with the corresponding device identifier can be set. Information obtained by associating the service identifier with the corresponding group identifier can be set. This information can be, for example, information related to AF (Application Function) and AS (Application Server) used in the service. This information can be, for example, an address.

[0142] (9) is information related to devices that can communicate with the UE. This information may be information related to devices that cannot communicate with the UE (or may be prohibited). For example, it may be information used to identify the device, such as an identifier. For example, it may be a device name. For example, it may be a sensor name. This information may be one or more. A list of information related to one or more devices may be set.

[0143] (10) is information related to the source node for setting up communication between UE and device. It can be information related to the source node for setting up device data transmission. It can be information indicating which node the setting is sent from. The setting can be a node that sends it directly or indirectly. For example, it can be an AF, a CN node, an MnS (Management Service), a base station, etc. As a CN base station, for example, it can be an AMF, PCF, etc. As an MnS, for example, it can be a MaS (Management System). The UE that receives this information can identify which node the setting is sent from.

[0144] (11) is information sent from the UE to the device. For example, it is data sent to the device, setting information for UE-device communication, etc. The UE sends this information to the device.

[0145] (12) is information related to the beam used by the UE for communication with the device. This information may be information related to the beam formed by the UE. This information may be information related to the beam formed by the base station. This information may be information used to determine the beam, such as a beam identifier.

[0146] (13) is information related to interference in UE-device communication. For example, it can be information related to interference received by the device. It can be information related to interference caused by the device. It can be information related to interference generated by multiple wireless transmission and reception methods within the UE. It can be information related to interference received by other UEs. Information related to interference can be, for example, the wireless method that causes interference, the wireless method that is interfered with, the frequency that causes interference, the frequency that is interfered with, the time that causes interference, the time that is interfered with, the power that causes interference, the power that is interfered with, information related to the device that causes interference, and information related to the device that is interfered with. Information related to interference can be information related to interference avoidance. The UE can obtain information related to interference in UE-device communication. For example, by utilizing this information, interference in UE-device communication can be reduced.

[0147] The above-disclosed UE-device communication configuration may be one or more. Information identifying the UE-device communication configuration, such as an identifier, may be provided. The base station may associate the identifier with the configuration and transmit it to the UE. One or more lists of such configurations may be provided. The identifiers of one or more configurations set in the list may be included.

[0148] The UE that receives the UE-device communication configuration from the base station uses the configuration information to perform UE-device communication. For example, the UE uses the configuration information to send a data transmission instruction to the device and receives data sent by the device in response.

[0149] The UE transmits data acquired from the device (hereinafter referred to as "device data") to the device data transmission destination node. The base station configures the UE for transmitting this device data. The following describes seven examples of device data transmission configuration information sent from the base station to the UE.

[0150] (1) Information related to the device. (2) Information related to the group. (3) Information related to the service. (4) Information related to transmission timing setting and / or transmission timing. (5) Information related to the sending target node. (6) Information about nodes used in device data communication. (7) A combination of (1) to (6).

[0151] (1) is information indicating which device the device data is being sent from. This information may be, for example, information for identifying the device, such as an identifier. This information may be one or more. A list of information related to one or more devices may be provided. The device-related information may include the number of devices. A maximum value may be set for the number of devices that send device data. Data may be sent when it is received from a specified number of devices, or the specified number of devices.

[0152] (2) Information indicating the device group from which the device data is being transmitted. This information may be, for example, information for identifying the device group, such as an identifier. This information may be one or more. A list of information related to one or more device groups may be provided. This information may be obtained by associating a device group identifier with the identifiers of devices belonging to that group.

[0153] (3) is information indicating the device data of the device from which service is being sent. This information may be, for example, information for identifying the service, such as an identifier. This information may be one or more. A list of information related to one or more services may be provided. This information may be obtained by associating a service identifier with a device identifier for that service.

[0154] (4) is information related to the setting of the timing for transmitting device data from the UE. 8 examples of information related to the setting of the transmission timing are disclosed below.

[0155] (4-1) Sending time setting. (4-2) Periodic. (4-3) After the UE-device communication is completed. (4-4) After the communication setting time between UE and device ends. (4-5) After receiving the device data. (4-6) Event triggering. (4-7) After receiving the device data sending instruction. (4-8) A combination of the above (4-1) to (4-7).

[0156] In the case of (4-1), the UE transmits the device data at the set transmission time. Examples of transmission time include a transmission start time, a transmission end time, and a transmission duration. This transmission time can be included in information related to transmission timing. The transmission timing of the device data from the UE can be flexibly set.

[0157] In the case of (4-2), the UE transmits device data at the set period. The period and offset can be included in the information related to the transmission timing. For example, this is effective when UE-device communication is performed periodically. The period can be equal to the period set for UE-device communication or an integer multiple thereof. The period can be statically determined by a standard, etc. to be equal to or an integer multiple of the period set for UE-device communication. This can simplify control.

[0158] In the case of (4-3), the UE transmits the device data after the UE-device communication is completed. The setting may be set to transmit immediately after the communication is completed. Alternatively, the setting may be set to transmit after a specified period after the communication is completed. For example, this can also be applied when the UE-device communication is performed aperiodically. The specified period may be included in the information related to the transmission timing. When the specified period is set to 0, the setting may be set to transmit immediately after the specified period after the communication is completed.

[0159] In the case of (4-4), the UE sends the device data after the UE-device communication setting time ends. The setting may be set to send the device data immediately after the communication setting time ends. Alternatively, the setting may be set to send the device data after a specified period after the communication setting time ends. The specified period may be included in the information related to the transmission timing. When the specified period is set to 0, the setting may be set to send the device data immediately after the communication setting time ends. As the UE-device communication setting time, the information included in the UE-device communication setting information may be used.

[0160] In the case of (4-5), the UE sends the device data after receiving the device data. It can be set to send the device data immediately after receiving the device data. Alternatively, it can be set to send the device data after a specified period of time after receiving the device data. For example, it can also be applied when it is unknown when the UE-device communication will be performed. The specified period can be included in the information related to the transmission timing. When the specified period is set to 0, the device data can be set to send the device data immediately after receiving the device data.

[0161] In the case of (4-6), the UE sends device data when the conditions set by the event trigger are met. The following discloses five examples of event trigger conditions. The event trigger conditions can be included in the device data transmission configuration information.

[0162] (4-6-1) Equipment data volume. (4-6-2) Number of devices. (4-6-3) Number of times the device receives data. (4-6-4) Number of communications with the device. A combination of (4-6-5)(4-6-1) to (4-6-4).

[0163] (4-6-1) When the UE receives a specified amount of device data, the device data is sent. The specified amount of device data can be set for each device. For example, it can be set according to the characteristics of each device. The specified amount of device data can be set for each of one or more devices. For example, the amount of information of the setting information can be reduced. The specified amount of device data can be set for each device group. For example, it can be controlled by the total amount of device data of one or more devices belonging to the device group. The specified amount of device data can be set for each service. For example, it can be controlled by the total amount of device data of one or more devices used for a specified service. The specified amount of device data can be set for each UE. For example, it can be applied without predetermining which device the UE will communicate with.

[0164] (4-6-2) When the UE receives device data from a specified number of devices, it transmits the device data received from the device. The specified number of devices can be set for each device group, each service, or each UE. The same effect as above can be achieved.

[0165] (4-6-3) When the UE receives device data from a device a specified number of times, it transmits the device data received from the device. The device may be one or multiple devices. The specified number of device data receptions can be set for each device, for one or more devices, for each device group, for each service, or for each UE. The same effects as above can be achieved.

[0166] (4-6-4) When the UE has communicated with a device a specified number of times, the UE transmits device data received from the device. The device may be one or multiple devices. The specified number of communications with a device can be set for each device, for one or more devices, for each device group, for each service, or for each UE. The same effects as above can be achieved.

[0167] The predetermined amount may be included in the device data transmission setting information.

[0168] In the case of (4-7), the UE transmits the device data when receiving the device data transmission instruction from the base station. The setting may be set to transmit immediately after receiving the device data transmission instruction. Alternatively, the setting may be set to transmit after a specified period after receiving the device data transmission instruction. The specified period may be included in the information related to the transmission timing. When the specified period is set to 0, the setting may be set to transmit the device data immediately after the communication ends. The specified period may be included in the setting information for device data transmission. The base station can indicate the device data transmission timing from the UE. Dynamic control of the device data transmission timing becomes possible.

[0169] (5) is information related to the target node for sending device data. It can be information indicating to which node the device data is to be sent. It can be a node that directly sends the device data or a node that indirectly sends the device data. The target node is, for example, an AS, a CN node, an MnS, a base station, etc. CN nodes are, for example, NF (Network Function), AMF, SMF, UPF, NWDAF (Network Data Analytics Function), NEF, etc. A node (which can be an entity or function) for managing (or collecting) device data can be set in the CN. This node will be referred to as DMF (Device Management Function) in this specification. As an MnS, for example, it can be MaS. A node (which can be an entity or function) for managing (or collecting) device data can be set in the MnS. This node will be referred to as DCE (Device data Collection Entity) in this specification. This allows the UE to identify to which node the device data should be sent.

[0170] (6) For example, base stations, CN nodes, MnS, AS, AF, etc. The information related to the nodes used in device data communication in (6) can be, for example, information related to the transmission path of device data. The information can include one or more transmission target nodes. For example, it can include information about the device or UE that is the source of device data transmission. For example, it can include information about devices, UE, base stations, AMF, NEF (Network Exposure Function), AF, etc. Information for determining the device data transmission path, such as an identifier, can be set. The device data transmission path identifier can be matched with the identifier or address of the node included in the transmission path. The setting of the device data transmission path can be one or more. In this way, the UE can identify the device data transmission path.

[0171] The device data transmission configuration disclosed above may be one or more. Information identifying the device data transmission configuration, such as an identifier, may be provided. The base station may associate the identifier with the configuration and transmit it to the UE. A list of one or more configurations may be provided. The identifiers of one or more configurations set in the list may be included.

[0172] The UE that has received the device data transmission configuration from the base station uses the configuration information to transmit the device data.

[0173] The UE may send a request to the base station for UE-device communication settings. The UE may send this request even if it does not have UE-device communication settings. Even if it has UE-device communication settings, the UE may send a request to reconfigure them. The base station that receives this request can recognize that the UE has requested UE-device communication settings. The base station that receives this request may configure the UE for UE-device communication settings and send the settings to the UE.

[0174] The UE can send a request to the base station for device data transmission configuration. The method disclosed in the above-mentioned UE-device communication configuration can be appropriately applied to achieve the same effect.

[0175] The UE may send a request to the base station to initiate UE-device communication. This request may be a request for UE-device communication configuration. The base station receiving this request may recognize that the UE has requested UE-device communication. The base station receiving this request may configure the UE-device communication configuration for the UE and send this configuration to the UE.

[0176] The UE may send a device data transmission start request to the base station. The method disclosed in the above-mentioned UE-device communication start request may be appropriately applied to achieve the same effect.

[0177] The UE can send an activation / deactivation (sometimes referred to as "act / deact") request for UE-device communication configuration to the base station. When performing one or more UE-device communication configurations, the base station that receives the request can send the activation / deactivation configuration. The UE can use the configuration to perform UE-device communication.

[0178] The UE can send an activation / deactivation request for a device data transmission configuration to the base station. When one or more device data transmission configurations are configured, the base station that receives the request can send an activation / deactivation (act / deact) configuration. The UE can then use the configuration to transmit device data.

[0179] The base station may send a UE-device communication start / end indication to the UE. It may also send an identifier for UE-device communication settings used in the start / end communication. For example, the base station may send the identifier together with the indication, or include it in the indication.

[0180] The base station may send a device data transmission start / end indication to the UE. It may also send an identifier for device data transmission used in the communication start / end. For example, the base station may send the identifier together with the indication or include it in the indication.

[0181] The base station can send activation / deactivation information for UE-device communication settings to the UE. It can also send activation / deactivation identifiers for UE-device communication settings. When performing one or more UE-device communication settings, it is not necessary to activate all settings. This can simplify UE processing and reduce power consumption.

[0182] The base station can send activation / deactivation information for device data transmission settings to the UE. It can also send activation / deactivation identifiers for device data transmission settings. When performing one or more device data transmission settings, it is not necessary to activate all settings. This can simplify UE processing and reduce power consumption.

[0183] The base station can reconfigure UE-device communication settings for the UE. The base station can modify UE-device communication settings for the UE. When modifying UE-device communication settings for the UE, the base station can notify the UE of part or all of the information related to the settings. For example, only the modified information may be notified as part of the information related to the settings. The method for reconfiguring or modifying UE-device communication settings from the base station to the UE can appropriately apply the method for configuring UE-device communication settings.

[0184] The base station may reconfigure the device data transmission settings for the UE. The base station may modify the device data transmission settings for the UE. When modifying the device data transmission settings for the UE, the base station may notify the UE of part or all of the information related to the settings. For example, only the modified information may be notified as part of the information related to the settings. The method for reconfiguring or modifying the device data transmission settings from the base station to the UE may appropriately apply the device data transmission settings method.

[0185] The base station may reconfigure the settings used in UE-device communication for the UE. The base station may change the settings used in UE-device communication for the UE. The base station may send an identifier of the settings used in UE-device communication to the UE. The base station may send an identifier of the changed settings used in UE-device communication to the UE.

[0186] This reconfiguration or change may use activation / deactivation. The base station may deactivate the pre-changed configuration for UE-device communication. An identifier of the deactivated configuration may be sent. The base station may activate the post-changed configuration for UE-device communication. An identifier of the activated configuration may be sent.

[0187] This resetting or change can use activation / deactivation. The base station can deactivate the settings before the change used in the device data transmission to the UE. The identifier of the deactivated settings can be sent. The base station can activate the settings after the change used in the device data transmission to the UE. The identifier of the activated settings can be sent. In this way, the settings used for UE-device communication can be re-set as early as possible. The UE and / or the base station can abandon the deactivation of the settings for a specified period. The specified period can be notified to the UE from the base station. For example, the specified period can be included in the settings for UE-device communication. In this way, for example, the amount of memory of the UE can be reduced.

[0188] The base station may reset or change the UE-device communication settings when instructing the UE to start / end UE-device communication. The base station may reset or change the device data transmission settings when instructing the UE to start / end device data transmission. The above method may be applied as appropriate.

[0189] By enabling resetting and changing of settings, flexible control suitable for communication conditions can be performed.

[0190] A method for releasing settings for UE-device communication is disclosed. The base station notifies the UE of the release of settings for UE-device communication. The method for notifying the release may appropriately apply the method for notifying settings for UE-device communication disclosed above. The UE can receive the release of settings for UE-device communication. The UE that receives the release of settings for UE-device communication releases the set settings for UE-device communication. The release notified to the UE by the base station may include information for determining the released settings for UE-device communication. The UE that receives the release may use the information to determine the released settings for UE-device communication. The UE that receives the release may release all the set settings for UE-device communication.

[0191] Upon receiving a release notification for UE-device communication settings, the UE releases the UE-device communication settings. The UE can discard the released UE-device communication settings. Enabling this release eliminates the need for the UE to retain unused UE-device communication settings when, for example, UE-device communication is not in progress. This allows for efficient use of UE memory, etc.

[0192] The base station can notify the UE of the release of the device data transmission setting. The notification method of the release can appropriately apply the notification method of the device data transmission setting disclosed above. The UE can receive the release of the device data transmission setting. The UE that receives the release of the device data transmission setting releases the set device data transmission setting. The release notified to the UE by the base station may include information for determining the released device data transmission setting. The UE that receives the release can use the information to determine the released device data transmission setting. The UE that receives the release of the device data transmission setting can release all the set device data transmission settings.

[0193] After releasing the device data transmission configuration, the UE can clear any remaining device data in its buffer. This allows the UE's buffer container to be used for other purposes as soon as possible. Alternatively, after releasing the device data transmission configuration, the UE can send any remaining device data in its buffer. For example, this can continue until all device data in the buffer is depleted. For example, the device data transmission configuration can be released at the end of a service. The UE can then send device data until the end of the service.

[0194] The device data transmission process for the device data in the buffer after release of the device data transmission settings can be configured. The base station can notify the UE of this transmission process method. For example, the information about this transmission process method can be included in the UE-device communication settings or the device data transmission settings and sent from the base station to the UE. This enables flexible control tailored to the conditions of the UE and base station, or to the content of the service.

[0195] The UE starts UE-device communication by receiving a setting for UE-device communication. The UE ends UE-device communication by receiving a setting for releasing UE-device communication. As another method, the UE may start UE-device communication by receiving an indication for starting UE-device communication. The UE may end UE-device communication by receiving an indication for ending UE-device communication. As another method, the UE may start UE-device communication by receiving an activation setting for UE-device communication. The UE may end UE-device communication by receiving a deactivation setting for UE-device communication.

[0196] Information indicating whether device data has ended can be set. For example, the device can generate this information. The device can notify the UE of whether device data has ended. Alternatively, the UE can generate this information. The UE can send this information to the base station. The base station can send this information to the CN node. This information can be sent together with the device data or separately. Thus, the UE, base station, and CN node that receive this information can recognize that the device data sent from the device has ended.

[0197] The UE can store device data received from devices. A buffer for device data storage can be set up within the UE. Device data can be stored, for example, for each device or each device group. It can be stored in association with a device identifier or device group identifier. Device data can be stored, for example, for each UE-device communication. Flexible control can be provided for the processing of device data and the transmission of device data from the UE to the base station.

[0198] An upper limit may be set on the number of UE-device communications performed to receive device data sent to a base station once. For example, if the upper limit is exceeded, the device data may not be stored. Alternatively, if the upper limit is reached, no further UE-device communication may be performed. Alternatively, if the upper limit is exceeded, the oldest device data may be cleared. The oldest device data may be cleared, and the latest device data for UE-device communication may be stored. If device data has been sent, the number may be cleared. Device data may be sent after a specified number of UE-device communications have been performed. For example, by setting a limit on the number of UE-device communications, control of the UE can be simplified.

[0199] A lower limit can be set for the number of UE-device communications required to receive device data sent to a base station. For example, if the number of communications falls below the lower limit, device data transmission may not occur. Alternatively, if the lower limit is reached, device data transmission may be enabled. If the UE transmits device data, the number of communications can be cleared. For example, by limiting the number of UE-device communications required to transmit device data, the device data communication load from the UE to the base station can be reduced.

[0200] The upper and / or lower limits for the number of communications can be sent from the base station to the UE. These limits can be included in the UE-device communication settings or the device data transmission settings. The upper and lower limits for the number of communications can be set, enabling flexible control.

[0201] The UE sends device data to the base station using the device data transmission settings received from the base station. The UE starts device data transmission by receiving the device data transmission settings. The UE ends device data transmission by receiving a release of the device data transmission settings. As another method, the UE can start device data transmission by receiving a device data transmission start indication. The UE can end device data transmission by receiving a device data transmission end indication. As another method, the UE can start device data transmission by receiving an activation of the device data transmission settings. The UE can end device data transmission by receiving a deactivation of the device data transmission settings.

[0202] A method for sending device data from a UE to a base station is disclosed. The UE can send device data to the base station through RRC signaling. The device data can be included in an RRC message for transmission. A larger amount of data can be sent. For example, the device data can be included in a UL Information Transfer message or an RRC Reconfiguration Complete message for transmission. For example, the device data can be included in a NAS message and sent through RRC signaling. As another method, a new RRC message for sending device data can be set. A message applicable to the settings for sending device data and the device data to be sent can be set.

[0203] Other methods are disclosed. The UE can send device data to the base station via MAC signaling. For example, it can be included in a MAC CE and sent. The UE can multiplex it with other MAC data and send it to the base station. It can be sent together with other data, thereby enabling efficient transmission.

[0204] Other methods are disclosed. The UE can send device data to the base station via L1 / L2 signaling. The device data can be included in the UCI. The device data can be included in the UCI and sent using the PUCCH. This enables earlier communication of device data between the UE and the base station.

[0205] Other methods are disclosed. A UE can send device data to a base station through RA (Random Access). For example, device data can be sent in Msg3 of a four-step RA process or in MsgA of a two-step RA process. This allows for earlier communication of device data between the UE and base station.

[0206] Figure 11 This is a diagram showing an example of a sequence in which a UE sends device data acquired from a device to a base station. The UE connected to the base station (which may be RRC_Connected) notifies the base station in step ST1101 of information indicating that it can communicate with the device. The information indicating that it can communicate with the device may be information indicating support for the RAT (Radio Access Technology) or communication method used in communication with the device. The information may be the number of devices that can communicate. The information may be information related to the frequency used for communication between devices. The information related to the frequency used for communication may be a frequency band. This information may be combined. The information may be included in the UE capabilities.

[0207] In step ST1102, the base station sends the UE settings for UE-device communication and settings for device data transmission. This transmission can use RRC signaling, for example. This setting can be sent, for example, in an RRC reconfiguration message. The UE that receives the setting can receive setting information for communication with the device and setting information for sending device information to the base station. The UE that receives the setting for UE-device communication uses the setting information to communicate with the device in step ST1103. For example, when settings are made so that UE-device communication is performed periodically, the UE periodically communicates with the device. The UE that receives data from the device stores the device data in step ST1104. It can be stored in a buffer set in the UE. It can also be stored in the buffer until the device data is sent to the base station.

[0208] The UE uses the device data transmission setting received in step ST1102 to send device data to the base station in step ST1105. For example, when the setting is made so that device data is sent in the same cycle as the cycle of UE-device communication, the UE sends the device data received in each cycle to the base station. For example, when the setting is made so that device data is sent when the amount of device data stored in the buffer exceeds a prescribed amount, the UE sends device data to the base station when the amount of device data stored through UE-device communication exceeds a prescribed amount. The base station can receive device data sent from the UE. The device data transmission setting sent in step ST1102 can be sent by signaling different from the UE-device communication setting. For example, RRC signaling can be used to send the device data in step ST1105. For example, the device data can be included in the RRC Reconfiguration Complete message and sent.

[0209] The UE may store the device data-related information. The base station may transmit the device data-related information. Details of the device data-related information will be described later. In step ST1104, the UE may store the device data-related information together with the device data. In step ST1105, the UE may transmit the device data-related information to the base station. For example, if the device data transmission settings include configuration information for transmitting the device data-related information, the UE may store the device data-related information together with the device data in step ST1104 and transmit the device data-related information together with the device data in step ST1105. The base station can receive the device data-related information.

[0210] When the UE-device communication settings and / or the device data transmission settings are changed, the base station transmits the setting changes to the UE in step ST1106. This setting change can be transmitted using, for example, RRC signaling. For example, the setting change can be transmitted in an RRC Reconfiguration message. Upon receiving the UE-device communication setting changes, the UE uses the changed setting information to communicate with the device in step ST1107. Upon receiving data from the device, the UE stores the device data in step ST1108.

[0211] The UE uses the changes to the device data transmission configuration received in step ST1106 to transmit device data to the base station in step ST1109. The base station can receive device data transmitted from the UE. The changes to the device data transmission configuration transmitted in step ST1106 can be transmitted using signaling separate from changes to the UE-device communication configuration. The transmission of device data in step ST1109 can use, for example, RRC signaling. For example, the device data can be transmitted in an RRC Reconfiguration Complete message.

[0212] In step ST1109, the UE may send information related to the device data to the base station, and the base station may receive the device data-related information.

[0213] In step ST1110, the base station sends the release of the settings for UE-device communication and the release of the settings for device data transmission to the UE. For example, RRC signaling can be used for this transmission. The settings can be sent, for example, in an RRC reconfiguration message. The UE that receives the release of the settings for UE-device communication ends the UE-device communication in step ST1111. The UE that receives the release of the settings for device data transmission ends the transmission of device data to the base station in step ST1111. The release of the settings for device data transmission can be sent by signaling different from the release of the settings for UE-device communication. The method disclosed above can be applied to the transmission processing of the device data in the buffer when the UE receives the release of the settings for device data transmission.

[0214] This enables UE-device communication and the transmission of device data received from a device to a base station. The base station can receive device data from the device via the UE. This also enables communication between the device and the NW.

[0215] Device data can be sent from a UE to a base station using the PUSCH. The UE can send device data to the base station via the PUSCH. The UE can send an SR (Scheduling Request) to request scheduling of the PUSCH for device data transmission. Upon receiving this SR, the base station can send scheduling information for the PUSCH to the UE. The UE, receiving this PUSCH scheduling information from the base station, uses this information to send device data using the PUSCH.

[0216] Scheduling information for PUSCH for device data transmission from the base station to the UE may be included in the DCI. A new DCI may be set for scheduling PUSCH for device data transmission. The DCI containing scheduling information for PUSCH for device data transmission may be detected using the UE's RNTI (Radio Network Temporary Identifier). As another method, the RNTI may be different for device data transmission and existing data transmission for services. A new RNTI may be set for DCI detection including scheduling information for PUSCH for device data transmission. The UE can identify whether the DCI is scheduling information for device data transmission or scheduling information for data transmission for existing services. The UE can select and receive these DCIs.

[0217] The base station can pre-set the PUSCH for device data transmission to the UE. For example, the CG (Configured Grant: permission has been set) for device data transmission can be set. The CG used for device data transmission can be CG type 1 or CG type 2. In this way, the signaling amount can be reduced. In addition, the SR can be omitted, so the device data can be sent as early as possible at the device data transmission timing from the UE to the base station. The base station can include the setting of the CG in the setting for device data transmission and send it to the UE. The setting for device data transmission and the CG setting used for device data transmission can be associated and sent. The UE can identify which CG setting is used for device data transmission.

[0218] When the PUSCH for device data transmission is set by the CG, the RNTI for the CG can be set. The UE can detect and receive the DCI for the CG in the RNTI for the CG. The UE can choose to receive the DCI of the CG for device data transmission or the CG for data transmission of existing services.

[0219] Disclose information about a UE communicating with multiple devices. Configure UE-device communication settings for each device. Configure UE-device communication settings for each device. Configure UE-device communication settings applicable to each device. Configure device data transmission settings for each device. Configure device data transmission settings for each device. Configure device data transmission settings applicable to each device.

[0220] The UE can store device data for each device. The UE can associate the device identifier with the device data for storage. The UE can identify the device data for each device. The UE can send device data to the base station for each device. The UE uses the device data transmission settings for each device to send device data to the base station.

[0221] This allows the UE to transmit device data acquired by the UE for each device to the base station even when communicating with multiple devices. This allows for configurations to be made for UE-device communication and device data transmission that are appropriate for the services using the devices, thereby ensuring, for example, that the QoS required by the service is met.

[0222] Figure 12 This is a diagram showing an example of a sequence in which a UE transmits device data acquired from a plurality of devices to a base station. Figure 12 In the example, two devices (device #1, device #2) are shown. Figure 11 The same step numbers are assigned to the common steps, and the common descriptions are omitted.

[0223] In step ST1102, the base station transmits the UE-device communication settings and device data transmission settings for each device to the UE. In step ST1201, the UE communicates with device #1 using the UE-device communication settings configured for device #1. In step ST1202, the device data received from device #1 is stored in the UE's internal buffer. Using the device data transmission settings for device #1 received in step ST1102, the UE transmits device data to the base station in step ST1203. The base station can now receive the device data for device #1 transmitted from the UE.

[0224] In step ST1204, the UE communicates with device #2 using the UE-device communication settings configured for device #2. In step ST1205, the device data received from device #2 is stored in the UE's internal buffer. In step ST1206, the UE transmits the device data to the base station using the device data transmission settings for device #2 received in step ST1102. The base station can now receive the device data for device #2 transmitted from the UE.

[0225] Figure 12In the example, communication between UE-device #1 and UE-device #2 is performed after communication between UE-device #1. However, the communication period between UE-device #1 and the communication period between UE-device #2 may overlap. For example, communication between UE-device #1 and communication between UE-device #2 may be performed alternately.

[0226] The device data transmission configuration sent in step ST1102 can be sent using signaling different from the UE-device communication configuration. In steps ST1203 and ST1206, the UE can send device data-related information for each device to the base station. The base station can receive device data-related information for each device.

[0227] Each device can be configured with information indicating whether device data has ended. The device can generate this information and send it to the UE. Alternatively, the UE can generate this information. The UE can send this information to the base station. This information can be sent with the device data or separately. Thus, the UE and base station receiving this information can recognize that the device data sent from the device has ended.

[0228] Thus, the UE can transmit device data received from multiple devices capable of communicating with multiple devices to the base station. The base station can receive device data from multiple devices via the UE. Communication between multiple devices and the NW is possible.

[0229] Disclosed are other methods for a UE to communicate with multiple devices. Settings for UE-device communication are made common across all devices. Setting information for UE-device communication is made common across all devices. A single setting can be set for UE-device communication. Communication between one or more devices and the UE is enabled using the same setting. For example, the UE can communicate with one or more devices during the configured UE-device communication period.

[0230] Device data transmission settings can be made common across all devices. Device data transmission settings can be made common across all devices. A single device data transmission setting can be set. One or more device data can be transmitted using the same setting. For example, a UE can transmit one or more device data during the set device data transmission period.

[0231] This reduces the amount of information required for configuration, enables communication with one or more devices using the same configuration, and enables transmission of device data, thereby reducing the complexity of UE control.

[0232] The UE can aggregate and store one or more device data. The UE can associate the device identifier with the device data for storage. Even when aggregated, the device data can still be identified. The UE can also send information indicating the device data's origin when transmitting the device data. For example, the UE can associate the device identifier with the device data and send it to the base station. This allows the base station to identify the device data's origin.

[0233] Figure 13 This is a diagram showing another example of a sequence in which a UE sends device data acquired from multiple devices to a base station. In the example of the diagram, two devices (device #1 and device #2) are shown. Figure 11 The same step numbers are assigned to the common steps, and the common descriptions are omitted.

[0234] In step ST1102, the base station transmits one UE-device communication configuration and one device data transmission configuration to the UE. The UE uses the received UE-device communication configuration to communicate with device #1 in step ST1301 and with device #2 in step ST1302. For example, communication between UE and device #1 in step ST1301 and between UE and device #2 in step ST1302 occurs within the UE-device communication time specified in the UE-device communication configuration.

[0235] In step ST1303, the device data received from device #1 and device #2 is stored in a buffer within the UE. The device data received from each device can be stored in association with the identifier of each device. This allows identification of the device from which the data was received. Using the device data transmission settings received in step ST1102, the UE transmits the device data for device #1 and device #2 to the base station in step ST1304. The device data for each device can be transmitted in association with the identifier of each device. This allows identification of the device from which the data was received. The base station can receive the device data for device #1 and device #2 transmitted from the UE.

[0236] The device data transmission settings sent in step ST1102 can be sent using signaling different from the UE-device communication settings. In step ST1304, the UE can send device data association information for each device to the base station. The device data association information for each device can be associated with the device identifier and sent. The base station can receive the device data association information for each device.

[0237] Information indicating whether device data from multiple devices has ended can be set. The UE can generate this information. This is effective when the UE aggregates and sends device data from multiple devices. The UE can send this information to the base station. This information can be sent together with the device data or separately. The UE and base station that receive this information can then identify that the device data sent from the device has ended.

[0238] This allows the UE to transmit device data received from multiple devices capable of communicating with multiple devices to the base station. The base station can receive device data from multiple devices via the UE. This enables communication between multiple devices and the network. Furthermore, since individual device configuration and device data transmission are unnecessary, control is simplified.

[0239] The above-disclosed methods may be appropriately combined. Figure 13 In the example of , it is disclosed that the base station sends 1 UE-device communication setting and 1 device data transmission setting to the UE, but Figure 12 As shown in the example, arbitrary settings can be specific to each device. For example, the base station can send a single UE-device communication setting to the UE, along with a device data transmission setting for each device. UE-device communication can be performed using the single setting received by the UE. The UE can use the device data transmission setting configured for each device to send the device data stored in the UE's buffer to the base station. By appropriately combining these settings, flexible control of services more appropriate for the devices being used can be achieved.

[0240] The UE can communicate with devices with which it can communicate during the UE-Device Communication Setup period. It can also communicate with devices not previously indicated to the UE. For example, it can communicate with devices detected by the UE during the UE-Device Communication Setup period. This allows the UE to receive device data from devices with which it can communicate. The base station can also receive device data from devices with which the UE can communicate.

[0241] Disclosed are other methods for a UE to communicate with multiple devices. UE-device communication settings can be specific to each device group containing one or more devices. UE-device communication setting information can be configured for each device group containing one or more devices. Communication between the UE and one or more devices in a device group can be performed using the same settings. For example, a UE can communicate with one or more devices in a device group during the configured UE-device communication period.

[0242] Device data transmission settings can be specific to each device group containing one or more devices. Device data transmission settings information can be specific to each device group containing one or more devices. Data transmission for one or more devices in a device group is performed using the same settings. For example, the UE can transmit data for one or more devices in a device group during the specified device data transmission period.

[0243] This reduces the amount of information required for configuration. The same configuration allows communication with one or more devices, enabling the transmission of device data, thus reducing the complexity of UE control. Furthermore, by configuring settings for each device group, more appropriate settings can be made for each device group.

[0244] For example, a device group can be set for each service. A device group consisting of devices used in a specified service can be set. For example, a device group can be set for each area. A device group consisting of devices existing in a specified area can be set. The device group can be predetermined. As another method, the device group can be determined by the NW node. Information for determining the device group, such as an identifier, can be set. The device group identifier can be associated with the identifier of the device included in the device group. The NW node sends information related to one or more device groups to the UE. Information related to the device group may include, for example, device information included in the device group, information related to the service, information related to the area, etc. This information can be included in the settings for UE-device communication or in the settings for device data transmission. The UE can identify which device group the setting is for.

[0245] Each service can be configured to specify whether UE-device communication settings and / or device data transmission settings are UE-specific, common across multiple UEs, or group-specific. The base station can make this setting for each service using the device being communicated with. A network node can also make this setting. This allows for more flexible settings tailored to the service.

[0246] The UE can associate device data received from a device with the device group identifier and store it. For example, device data can be stored for each service or region. The UE can associate device data received from a device with the device group identifier and the device identifier and store it. Device data can be stored not only in the device group but also for each device.

[0247] The UE transmits device data to the base station using the device data transmission settings configured for each device group. The UE can transmit device data received from one or more devices within a device group to the base station. The UE can associate the device group identifier with the device data and transmit it to the base station. The base station can then identify the device group from which the device data originates. The UE can associate the device group identifier, the device identifier, and the device data and transmit them to the base station. The base station can identify not only the device group but also the device from which the device data originates.

[0248] Device data-related information can be sent along with the device data. Alternatively, it can be sent separately from the device data. Twenty examples of device data-related information are disclosed below.

[0249] (1) Equipment data identification. (2) Equipment group identification. (3) Information related to the service. (4) Information related to the region. (5) Information related to the PDU session. (6) Information related to network slicing. (7) Information indicating the destination of device data transmission. (8) Location information. (9) Information related to the timing of UE-device communication. (10) UE-device communication frequency information. (11) Reception quality. (12) Information related to PLMN and NPN. (13) Information related to the user. (14) Information related to RNA. (15) Information related to base stations and cells. (16) Information related to the beam. (17) Information related to the time of device data. (18) Equipment identification. (19) Information related to interference. (20) A combination of (1) to (19).

[0250] (1) is information for identifying device data. This information can be assigned to the device data, for example. For example, it can be set as the header of the device data. This information can be numbered according to the order in which it is sent from the device. Thus, even if the order in which the device data is received differs among the UE, NW node, etc. that receives the device data, the device data can be arranged in the order in which it is sent.

[0251] (3) is information indicating the device from which service the device data is received. This information may be, for example, a service identifier. (4) is information indicating the device data from which region the device data is received. This information may be, for example, a region identifier. (5) is information related to the PDU session set up for sending the device data. This information may be, for example, a PDU session identifier. (6) is information related to the network slice set up for sending the device data. This information may be, for example, a network slice identifier. (7) is information indicating the sending destination of the device data. As information indicating the sending destination, this information may be, for example, an identifier or an address. As the device sending destination, for example, it may be AMF, UPF, NWDAF, NEF, NF, AF, AS. It may be set as their identifier or address.

[0252] (8) For example, it may be the location information of the UE. For example, it may be the location information of the device. The location information of the device may be derived by the UE. The location information of the device may be derived by the device. The location information of the device derived by the device may be notified to the UE from the device. This information may be notified together with the device data, for example.

[0253] (9) For example, it may be timestamp information of the time of communication between the UE and the device. For example, it may be information indicating the time when the UE received the device data. For example, it may be information indicating the start time, end time, and device data reception time of the device data received by the UE. (9) For example, it may be information indicating the time when the device sent the device data. For example, it may be information indicating the start time, end time, and device data transmission time of the device data sent by the device. The information indicating the time when the device sent the device data can be notified from the device to the UE. This information can be notified together with the device data, for example.

[0254] (10) may be information indicating how many times UE-device communications have been performed. The device data sent may be information indicating how many times the UE has received device data in the UE-device communications.

[0255] (11) is the reception quality of the signal from the device measured by the UE. Examples of the reception quality include received power, SINR, and SNR (Signal to Noise Ratio). Examples of received power include RSSI.

[0256] (12) is information indicating which PLMN or NPN the UE is located in. This information may be information for determining the PLMN or NPN, such as the identifier of the PLMN or NPN. (13) is information indicating which TA the UE is located in. This information may be information for determining the TA, such as the TAC. (14) is information indicating which RNA the UE is located in. This information may be information for determining the RNA, such as the identifier of the RNA. (15) is information related to the base station or cell to which the UE is connected. This information may be information for determining the base station or cell, such as the identifier of the base station or the identifier of the cell. (16) is information related to the beam used by the UE for communication with other devices. This information may be information related to the beam formed by the UE. This information may be information related to the beam formed by the base station. This information may be information for determining the beam, such as the identifier of the beam.

[0257] (17) is information indicating the time when the device acquired the data. This information may be information indicating the start time, end time, or measurement time of data acquisition. For example, if the device is a temperature sensor, this information may be information indicating the time when the temperature data was acquired. The information indicating the time when the device acquired the data may be notified from the device to the UE. For example, this information may be notified together with the device data.

[0258] Identifiers such as the device data identifier (1), the device group identifier (2), and the device identifier (18) may be identification information that can be recognized by the user. For example, the UE that receives the identification information from the device displays the identification information on a display. Alternatively, the identification information may be output as sound. Thus, by using identification information that can be recognized by the user as an identifier, the user can identify which device the information belongs to.

[0259] (19) is information related to interference in UE-device communication. For example, it can be information related to interference measured by the UE. It can be information related to interference measured by the device. It can be information related to interference caused by transmission and reception through multiple wireless methods within the UE. Information related to interference can be, for example, the wireless method that causes interference, the wireless method that is interfered with, the frequency that causes interference, the frequency that is interfered with, the time that causes interference, the time that is interfered with, the power that causes interference, the power that is interfered with, information related to the device that causes interference, and information related to the device that is interfered with. UE and NW nodes can obtain information related to interference. For example, by utilizing this information, interference in UE-device communication can be reduced.

[0260] The UE that receives the device data stores the device data. Device data-related information may be stored along with the device data. The base station may configure the UE to store the device data-related information along with the device data. This information may be included in the UE-device communication settings or the device data transmission settings.

[0261] The device data association information may be included in the device data or may be sent together with the device data. Alternatively, it may be sent separately from the device data. The sending target of the device data association information and the sending target of the device data may be the same or different. For example, when the NW node that utilizes the device data also uses the device data association information, the sending target may be set to be the same. For example, when a NW node different from the NW node that utilizes the device data uses the device data association information, the sending target may be made different. The UE sends the device data association information to the base station. The device may send the device data association information to the UE. The UE that receives the information may send part or all of the received information to the base station. The base station can receive the device data association information. Thus, for example, the UE and the NW node can identify the status of communication between the UE and the device. The acquisition of the device data association information required for the service can be performed in the NW, and services using the device can be provided.

[0262] Device data association information can be configured. The base station can send device data association information configuration to the UE. This configuration can be sent together with or included in the UE-device communication configuration or the device data transmission configuration. Alternatively, the device data association information configuration can be sent separately from the configuration. The device data association information transmission configuration can include, for example, information indicating which device data association information to obtain and which device data association information to send. Device data association information requested by the network can be configured.

[0263] The method for transmitting the device data related information transmission configuration from the base station to the UE can appropriately apply the method for transmitting the device data transmission configuration disclosed above, and the same effect can be achieved.

[0264] By adopting the method disclosed in this embodiment, UE-device communication is enabled. The UE can receive device data. In addition, device data can be sent from the UE to the base station. The base station can receive device data from the device. This enables communication between the device and the network via the UE.

[0265] Furthermore, the base station configures UE-device communication settings and device data transmission settings from the UE to the base station, thereby reducing interference between UE-device communication and communications on the Uu or PC 5. This provides high-quality and stable device data communication.

[0266] Implementation method 2. 3GPP is exploring the integration of ultra-low-power IoT devices into mobile communication systems. When integrating these devices into mobile communication systems, it is assumed that communication between the devices and base stations must occur via a UE that is not connected to the base station. This paper discloses a method that enables such UEs to communicate with both the device and the base station.

[0267] In this embodiment, communication can be carried out between a UE and a device that is not in a connected state with the base station (which can also be RRC_Idle or RRC_Inactive). For example, the UE communicates with the device through RRC_Idle or RRC_Inactive. The UE stores the device data after communicating with the device. The UE transitions to a connected state with the base station and sends the device data to the base station. For example, the UE transitions to RRC_Connected and sends the device data to the base station. The UE can send the device data to the base station during the connection process with the base station. The UE can send the device data to the base station during the transition process to RRC_Connected.

[0268] The base station sends a setting for UE-device communication to a UE that is in a connected state with the base station. The base station can send a setting for sending device data to a UE that is in a connected state with the base station. The method for sending the setting can appropriately apply the method disclosed in Implementation 1. In the case where the setting information is included in an RRC message, for example, it can be included in a message that causes the UE to transition from the RRC_Connected state to the RRC_Idle state. For example, it can be included in a message that causes the UE to transition from the RRC_Connected state to the RRC_Inactive state. For example, it can be included in an RRC Release message accompanied by a suspend (suspend) to send. A UE that is in a connected state with a base station can receive settings for UE-device communication and settings for sending device data from the UE to the base station from the base station.

[0269] The base station may send UE-device communication settings when the UE is in RRC_Connected state to enable UE-device communication to a UE that is not in a connected state. The base station may send device data transmission settings when the UE is in RRC_Connected state to enable a UE that is not in a connected state to send device data received from a device to the base station.

[0270] The base station may include the UE-device communication settings and / or device data transmission settings in the SIB and broadcast them. The method disclosed in Implementation 1 may be appropriately applied. A UE that is not in a connected state can receive the UE-device communication settings and / or device data transmission settings by receiving the SIB containing this information broadcast from the base station. The UE uses this information to communicate with the device in RRC_Idle or RRC_Inactive mode.

[0271] The base station can send notifications of settings for UE-device communication and / or settings for device data transmission for the UE through both SIB-based broadcasting and RRC signaling. For example, a part of the setting information is broadcast using the SIB, and the remaining part is included in the RRC message and notified through dedicated RRC signaling. For example, information in the setting information that is common to one or more UEs is broadcast using the SIB, and UE-specific information is included in the RRC message for notification. As described above, notifications in the RRC signaling can be performed when the UE is in a connected state. In this way, the amount of signaling can be reduced. The UE uses the information received through the SIB and RRC signaling to communicate with the device in RRC_Idle or RRC_Inactive.

[0272] The example of information disclosed in Embodiment 1 can be applied as appropriate to the example of information configuration for UE-device communication. This is valid even if the UE is in RRC_Inactive or RRC_Inactive. The example of information configuration for device data transmission can be applied as appropriate to the example of information configuration for Embodiment 1.

[0273] The period of UE-device communication set in the UE can be set to an integer multiple of the DRX period. The DRX period can be the DRX period set in the base station. The DRX period can be the DRX period set in the UE. The DRX period can be the DRX period used for paging reception. The timing of UE-device communication can be set near the reception timing of DRX. For example, the UE-device communication time can be set near the reception time of DRX. For example, the UE-device communication time can be set so as not to overlap with the reception time of DRX. For example, the UE-device communication time can be set before or after the reception time of DRX. The UE-device communication time and the reception time of DRX can be continuous or non-continuous. The UE-device communication time and the reception time of DRX can be set within a specified period. For example, the offset of the UE-device communication timing can be an offset from the reception time of DRX.

[0274] Therefore, by associating the DRX cycle, DRX reception timing, and UE-device communication timing, the power consumption of the UE can be reduced when the UE that is not connected to the base station performs UE-device communication.

[0275] The UE that receives the device data stores the device data. Device data-related information may be stored along with the device data. The example of device data-related information may be appropriately applied to the example disclosed in Implementation 1. The base station may configure the UE to store device data-related information along with the device data. This configuration may be included in the UE-device communication configuration. It may also be included in the device data transmission configuration. The base station may configure which device data-related information is stored and whether it is transmitted to the base station.

[0276] Information related to the buffer for storing device data in the UE can be set. This information can be, for example, the amount of device data stored by the UE. For example, it can be the maximum amount of device data stored by the UE. The amount of device data can be set to a specified amount. The specified amount can be set to a threshold. For example, when the threshold is reached, the device data can be sent to the base station. For example, device data exceeding the threshold can be not stored or discarded. For example, instead of directly discarding device data exceeding the threshold, new data can be stored and the portion exceeding the threshold can be discarded from the old data. For example, device data of a service with a higher priority can be stored, and the portion exceeding the threshold can be discarded from the device data of a service with a lower priority. For example, device data of a service with a smaller request delay time can be stored, and the portion exceeding the threshold can be discarded from the device data of a service with a larger request delay time.

[0277] The base station can send information related to the UE's device data storage buffer to the UE. The base station can also send the UE instructions for handling when the amount of device data stored in the UE exceeds a threshold. This handling method can be included in the UE-device communication settings. It can also be included in the device data transmission settings. A UE not connected to the base station stores device data received from a device until it connects to the base station and transmits it to the base station. This can, for example, limit the amount of buffer required by the UE to store device data.

[0278] Information related to the number of devices for which the UE stores device data may be set. This information may be, for example, the maximum number of devices for which the UE stores device data. The number of devices may be set to a specified number. The specified number may be set to a threshold. For example, when the threshold is reached, the device data may be sent to the base station. For example, device data from devices exceeding the threshold may not be stored or may be discarded. For example, data from a number of new devices exceeding the threshold may be stored, and data from a portion of old devices exceeding the threshold may be discarded, without directly discarding device data from devices exceeding the threshold. For example, data from devices of a service with a higher priority may be stored, and the portion exceeding the threshold may be discarded from the data from devices of a service with a lower priority. For example, data from devices of a service requesting a smaller delay time may be stored, and the portion exceeding the threshold may be discarded from the data from devices of a service requesting a larger delay time.

[0279] The base station may transmit information related to the number of devices whose device data is stored by the UE to the UE. The base station may transmit information to the UE regarding a method for handling when the number of devices whose device data is stored by the UE exceeds a threshold. This method may be included in the UE-device communication settings. It may also be included in the device data transmission settings. This can achieve the same effect as described above.

[0280] Disclosed is a method for transmitting device data received from a device by a UE that is not connected to a base station to a base station. Device data is transmitted when the UE is connected to a base station. Device data can be transmitted when the UE transitions to RRC_Connected. When the UE transitions to RRC_Connected, device data received from a device by the UE when the UE is in RRC_Idle or RRC_Inactive is transmitted to the base station. After receiving the device data, the UE can transmit the device data to the base station when it first transitions to RRC_Connected. This avoids, for example, the UE connecting to the base station solely to transmit device data. This simplifies UE control and avoids increased power consumption.

[0281] Other methods are disclosed. A timing setting for sending device data from a UE is applied, and the UE sends the device data to a base station. The UE can use information related to the timing setting for sending device data received from the base station to send device data to the base station. In order to send device data, the UE connects to the base station at the timing for sending device data or before the timing for sending device data. The UE can transition to the RRC_Connected state. The UE connected to the base station sends device data to the base station. As a result, a UE that is not connected to the base station can send device data to the base station at the timing for sending device data.

[0282] Other methods are disclosed. The UE sends device data when receiving a device data sending indication from the NW node. For example, paging can be used. The device data sending indication information can be included in a paging message. The device data sending indication information can be included in the DCI used for paging for sending. The device data sending indication information can be included in a short message. It can be set to send immediately after the device data sending indication is received. Alternatively, it can be set to send after a specified period after the device data sending indication is received. The specified period can be included in information related to the sending timing. When the specified period is set to 0, it can be set to send immediately after the communication ends. The specified period can be included in the device data sending setting information, can be included in the paging message, can be included in the DCI used for paging, or can be included in the short message. The specified period can be included in the paging message together with the device data sending indication information, can be included in the DCI used for paging together with the device data sending indication information, or can be included in the short message together with the device data sending indication information. In this way, a UE that is not connected to the base station can receive the device data sending indication information. The UE that receives the device data sending indication information is connected to the base station. The UE connected to the base station transmits device data to the base station. This allows the UE to transmit device data received when not connected to the base station to the base station.

[0283] Other methods are disclosed. SIB is used in sending the device data sending indication. The base station includes the device data sending indication information in the SIB and sends it. The above-disclosed method can be applied to the sending timing after receiving the device data sending indication. In addition, the specified period can be included in the setting information for device data sending or in the SIB. It can be included in the same SIB as the device data sending indication information. The UE that receives the device data sending indication information is connected to the base station. As a result, the UE that is not connected to the base station can receive the device data sending indication information. The UE connected to the base station sends device data to the base station. As a result, the UE can send device data to the base station.

[0284] Other methods are disclosed. Device data is transmitted when the UE is moving between cells. For example, device data is transmitted when the UE is performing cell selection or cell reselection. The UE can transmit device data to the selected cell or the reselected cell. When there is device data to be transmitted, the UE connects to the selected cell or the reselected cell. The UE connected to the cell transmits device data to the cell. Thus, even when the UE is moving between cells, device data can be transmitted to the base station.

[0285] Another method is disclosed. A UE transmits device data when moving between RNAs. A UE can transmit device data to a base station while moving between RNAs. When there is device data to be transmitted, the UE connects to the base station. The UE connected to the base station transmits the device data to the base station. Thus, even when the UE is moving between RNAs, it can transmit device data to the base station.

[0286] Another method is disclosed. A UE transmits device data when moving between TAs. A UE can transmit device data to a base station when moving between TAs. When there is device data to be transmitted, the UE connects to the base station. The UE connected to the base station transmits device data to the base station. Thus, even when the UE moves between TAs, device data can be transmitted to the base station.

[0287] In the above disclosed method, the UE is connected to the base station and sends device data to the base station. The UE can send device data to the base station during the connection process with the base station. The device data can be sent to the base station as soon as possible.

[0288] The base station can configure a method for a UE to transmit device data received from a device to the base station when the UE is not connected to the base station. The base station can transmit information indicating the transmission method to the UE. For example, the base station can transmit information indicating which of the above-disclosed transmission methods is used to the UE. The information indicating the transmission method can be included in the device data transmission settings. The base station can configure the method for transmitting device data received by a UE not connected to the base station to the base station, for example, enabling flexible control appropriate to the service.

[0289] The UE sends device data to the base station. The UE can send part or all of the stored device data. The UE can send device data-related information to the base station. The UE can send part or all of the stored device data-related information. It is possible to set which device data and device data-related information are to be sent to the base station. For example, it is possible to set it so that only device data and device data-related information of a specific service are sent to the base station. For example, it is possible to set it so that only device data and device data-related information received from devices in a specific area are sent to the base station. The base station sends information to the UE about which device data and device data-related information are to be sent to the base station. This information can be included in the settings for sending device data. Thus, for example, the base station can receive desired device data and device data-related information from the UE.

[0290] After receiving the UE-Device communication settings, if the connection with the base station is released (or transitioned to RRC_Idle or RRC_Inactive), the UE can start UE-Device communication. After the UE transitions from RRC_Idle or RRC_Inactive to RRC_Connected, the UE-Device communication can be terminated. If the UE transitions to RRC_Idle or RRC_Inactive again, the UE-Device communication can be resumed.

[0291] For example, when a UE connected to a base station uses the method disclosed in Implementation 1 to perform UE-device communication, when the connection with the base station is released (it may also be transferred to RRC_Idle or RRC_Inactive), the UE-device communication can be continued. When the UE transfers to RRC_Idle or RRC_Inactive, the UE-device communication settings in the state where it is not connected to the base station can be used to perform UE-device communication. The UE-device communication settings applicable to the state of the UE can be used. As another method, the UE-device communication settings in the state where it is connected to the base station can continue to be used. There is no need to change the UE-device communication settings, communication processing can be continued, and communication can be performed with low latency.

[0292] When a UE that is not connected to a base station performs UE-device communication, the UE-device communication can be continued when the connection with the base station is established (it can also be transferred to RRC_Connected). The method disclosed in Implementation 1 can be used to continue the communication. When the UE transfers to RRC_Connected, the UE-device communication settings in the state of being connected to the base station can be used to perform UE-device communication. The UE-device communication settings applicable to the state of the UE can be used. As another method, the UE-device communication settings in the state of not being connected to the base station can be continued. There is no need to change the UE-device communication settings, communication processing can be continued, and communication can be performed with low latency.

[0293] Whether to continue using the UE-device communication settings when the UE's connection state transitions can be pre-configured. The base station can notify the UE whether to continue using the UE-device communication settings. This enables UE-device communication suitable for the service used by the device.

[0294] The release of the setting for UE-device communication, the UE-device communication start indication, the UE-device communication end indication, the activation (act) of the setting for UE-device communication, and the deactivation (deact) of the setting for UE-device communication disclosed in Implementation Method 1 can be appropriately applied. They can be notified while the UE is connected to the base station. When the connection between the UE and the base station is released, it can be decided whether to perform UE-device communication according to the above settings. For example, when the UE transitions to RRC_Idle or RRC_Inactive, the UE can start UE-device communication if the UE-device communication start indication is notified and the UE-device communication end indication is not notified.

[0295] Information indicating whether the device data has ended can be set by appropriately applying the method disclosed in Implementation 1. The UE, base station, and CN node that receive this information can recognize that the device data sent from the device has ended.

[0296] A UE that is not connected to a base station can store device data received from a device. A buffer for storing device data can be set in the UE.

[0297] The UE sends device data to the base station. The UE that is not connected to the base station connects to the base station before sending device data to the base station. The UE sends the device data to the base station using the device data sending setting received from the base station. The UE can end the device data sending by receiving the device data sending setting release. As another method, the UE that is connected to the base station before sending device data to the base station can start the device data sending by receiving the device data sending start indication. The UE can end the device data sending by receiving the device data sending end indication. As another method, the UE that is connected to the base station before sending device data to the base station can start the device data sending by receiving the device data sending setting activation. The UE can end the device data sending by receiving the device data sending setting deactivation.

[0298] The UE can receive the release of the device data transmission configuration, receive the device data transmission start instruction, receive the device data transmission end instruction, and receive the activation and deactivation of the device data transmission configuration during the connection process with the base station. The accompanying processing can be performed during the connection process with the base station. By performing these processes during the connection process with the base station, these processes can be implemented as early as possible, including device data transmission.

[0299] A method for transmitting device data from a UE to a base station is disclosed. A base station can transmit device data to another base station via RRC signaling. Device data can be included in an RRC message for transmission. This allows for the transmission of larger amounts of data.

[0300] Device data may be sent, for example, during the RRC establishment process. Device data may be sent, for example, in an RRC Setup Complete message. Device data may be sent, for example, during the RRC reestablishment process. Device data may be sent, for example, in an RRC Reestablishment Complete message. Device data may be sent, for example, during the RRC Resume process. Device data may be sent, for example, in an RRC Resume Complete message.

[0301] Device data may be sent, for example, during the RRC reconfiguration process. Device data may be sent, for example, within an RRC reconfiguration message. Device data may be sent, for example, within a UE Information Response message. Device data may be sent, for example, within a UL Information Transfer message. Device data may be sent, for example, within a NAS message and via RRC signaling.

[0302] As another method, a new RRC message for transmitting device data can be provided. This message can be adapted to the device data transmission settings and the device data to be transmitted.

[0303] Other methods are disclosed. The UE can send device data to the base station via MAC signaling. For example, the UE can include the device data in a MAC CE and send it. The UE can multiplex the device data with other MAC data and send it to the base station. The device data can be sent together with other data, thereby enabling efficient transmission.

[0304] Other methods are disclosed. The UE can send device data to the base station via L1 / L2 signaling. The device data can be included in the UCI. The device data can be included in the UCI and sent using the PUCCH. This enables earlier communication of device data between the UE and the base station.

[0305] Other methods are disclosed. A UE can send device data to a base station through RA processing. For example, device data can be included in Msg3 of a four-step RA process or in MsgA of a two-step RA process. This allows for earlier communication of device data between the UE and the base station.

[0306] The PUSCH can be used to transmit device data from the UE to the base station, and the method disclosed in Embodiment 1 can be appropriately applied.

[0307] After sending device data to the base station, the UE can maintain the connection with the base station. As another method, the UE can release the connection with the base station after sending device data to the base station. After sending device data to the base station, the UE can return the connection with the base station to the original state before starting to send device data. It can be set to be able to set the processing after the device data is sent. The base station sets the processing method after the device data is sent to the UE. The setting information can be included in the settings for UE-device communication or the settings for sending device data. Thus, for example, the base station can perform processing suitable for the situation of the UE sending device data.

[0308] Information indicating that transmittable device data is located within the UE can be provided. For example, if the UE cannot transmit device data to the base station via a single signaling operation, the UE sends this information to the base station. The base station, upon receiving this information, can identify the presence of device data that can be transmitted to the UE. This information can be sent along with the device data, for example, to indicate as early as possible that transmittable device data remains. This information can also be sent separately from the device data, providing a timely indication of the presence of transmittable device data.

[0309] The method for transmitting device data-related information from the UE to the base station can appropriately apply the aforementioned device data transmission method. The device data-related information can be transmitted along with the device data or using other signaling. The UE can use the device data transmission configuration received from the base station to transmit the device data and device data-related information. This allows the base station to receive the device data-related information.

[0310] Figure 14 This is a diagram showing an example of a sequence in which a UE not connected to a base station sends device data acquired from a device to a base station. This diagram shows a case in which a UE in RRC_Idle sends device data acquired from a device to a base station. Figure 11 Common steps are marked with the same step numbers, and common descriptions are omitted. While the UE is connected to the base station (which may be RRC_Connected), in step ST1101, the base station notifies the base station of information indicating that communication with the device is possible. The information indicating that communication with the device is possible may include information indicating the connection status of the UE that can communicate with the device.

[0311] The settings for UE-device communication when the UE is not connected to the base station and the settings for sending device data received when the UE is not connected to the base station can be set. The settings can be set for each connection state of the UE (RRC_Connected, RRC_Idle, RRC_Inactive). The UE can use this setting according to the connection state between the UE and the base station when communicating with the device. The setting method for each connection state of the UE can be different in the settings for UE-device communication and the settings for sending device data. For example, the settings for UE-device communication can be set for each connection state of the UE, and the settings for sending device data can be set to one identical setting in all states. The settings for each connection state of the UE can be sent separately or as one setting. When sent as one setting, information indicating in which connection state the setting is used can be set and included in the setting for sending. In this way, settings applicable to the connection state between the UE and the base station when communicating with the device can be made. More flexible control can be performed.

[0312] In step ST1104, the base station sends the UE the settings for UE-device communication and the settings for device data transmission under RRC_Idle. The base station can send the settings during the period when the UE is connected to the base station. This transmission can use RRC signaling, for example. The settings can be included in the RRC release message and sent, and the RRC release message is, for example, a message for transitioning from the RRC_Connected state to the RRC_Idle state. The settings for device data transmission can be sent using signaling different from the settings for UE-device communication. The UE that receives the settings can receive setting information for communication with the device in RRC_Idle and setting information for sending device data received in RRC_Idle to the base station. The UE that receives the RRC release transitions to RRC_Idle in step ST1402.

[0313] A UE that has received UE-device communication configuration during the RRC_Connected state, after transitioning to the RRC_Idle state, uses this configuration information to communicate with the device in step ST1403. The UE, having received device data from the device, stores the device data in step ST1404. This data can be stored in a buffer within the UE or in the buffer until the device data is sent to the base station.

[0314] The UE performs connection processing with the base station to transmit device data. In step ST1405, the UE performs RA processing with the base station. In step ST1406, the UE transmits device data to the base station. The base station receives the device data transmitted from the UE. This device data can be transmitted using, for example, RRC signaling. For example, the device data can be transmitted in an RRC Setup Complete message during the connection processing between the UE and the base station.

[0315] If the UE cannot send the device data through a single signaling, it further sends the device data. For example, RRC signaling can be used for this transmission. For example, it can be included in the UL Information Transfer message for transmission. The UE continues to send the device data to the base station until the device data is completed. When the device data to be sent is completed, in step ST1407, the UE sends information indicating whether the device data has ended together with the device data. The base station that receives the information indicating whether the device data has ended can recognize the end through the device data sent in step ST1407.

[0316] After the device data transmission is completed, the UE can return to the state before the communication with the UE (UE-device communication) was started, that is, RRC_Idle in step ST1408. In order to make the UE return to RRC_Idle, an RRC release message can be sent from the base station to the UE. For example, the base station that received the last device data in step ST1407 sends an RRC release message to the UE. The UE that receives the RRC release message transfers to RRC_Idle. The UE can perform UE-device communication again after transferring to RRC_Idle. The UE can also perform UE-device communication after the RRC_Idle transfer until the UE-device communication setting release is received from the base station. Steps ST1403 to ST1408 can be repeated until the UE receives the UE-device communication setting release from the base station.

[0317] The UE may store the device data-related information. The UE may transmit the device data-related information to the base station. In step ST1404, the UE may store the device data-related information together with the device data. In steps ST1406 and ST1407, the UE may transmit the device data-related information to the base station. For example, if the device data transmission settings include configuration information for transmitting the device data-related information, the device data-related information may be stored together with the device data in step ST1404 and transmitted together with the device data in steps ST1406 and ST1407. The base station may receive the device data-related information.

[0318] Figure 14The example discloses the case where the UE in RRC_Idle performs UE-device communication. As another example, the UE in RRC_Inactive can perform UE-device communication. Figure 14 Example of a sequence. For example, in step ST1401, the base station transmits settings for UE-device communication in RRC_Inactive and settings for device data transmission of device data received by the UE from the device in RRC_Inactive. An RRC release message accompanied by a pause can be used in this transmission. The UE that receives the RRC release message accompanied by a pause transitions to RRC_Inactive. The UE that transitions to RRC_Inactive uses the settings received from the base station to perform UE-device communication. The transmission of device data from the UE to the base station can use an RRC recovery complete message.

[0319] This allows UEs not connected to the base station to communicate with devices and transmit device data received from the device to the base station. The base station can receive device data from the device via the UE, enabling communication between the device and the network.

[0320] A UE that is not connected to a base station can communicate with multiple devices. The method disclosed in Embodiment 1 can be appropriately applied to the method for communicating with multiple devices. The same effect can be achieved.

[0321] The base station can notify the surrounding base stations of the settings for UE-device communication and / or the settings for sending device data set for the UE. When the UE moves to another base station, the base station can use the settings for the UE received from the surrounding base stations. When connected to a base station different from the base station that received the settings so that the UE can send device data, the UE can use the settings to send device data. The different base station can receive the device data by receiving the settings of the UE from the surrounding base stations. When the UE is within the range of a base station different from the base station that received the settings, the settings can be used in communication with the device. The different base station can identify the settings for UE-device communication by receiving the settings of the UE from the surrounding base stations.

[0322] A base station can modify some or all of the UE-device communication settings and / or device data transmission settings received from neighboring base stations. If a UE is connected to a different base station than the one that received the settings, the different base station can send the modified settings to the UE. Only the modified information can be sent. This allows, for example, the base station to configure new settings for the UE based on the conditions of the base station itself.

[0323] By adopting the method disclosed in this embodiment, a UE not connected to a base station can conduct UE-device communication. A UE not connected to a base station can receive device data. In addition, device data received from a device when the UE is not connected to a base station can be sent to the base station. A base station can receive device data received by a UE not connected to the base station. This enables communication between a device and the network via the UE.

[0324] Implementation method 3. 3GPP is exploring the integration of ultra-low-power IoT devices into mobile communication systems. Integrating these devices into mobile communication systems requires methods for communicating device data with the network (NW) and managing device data within the NW. However, no public disclosure exists regarding these methods. This embodiment discloses a method for addressing this issue.

[0325] As an example of a method for solving the above problem, settings for UE-device communication and / or settings for device data transmission can be sent from an application to a base station. As an application, it can be, for example, AF or AS. The settings can be sent to the base station from DN (Data Network). The settings can be sent to the base station from MnS. The device can be managed in MnS. As MnS, it can be, for example, MaS or DCE. The settings can be sent to the base station from a CN node. The CN node can manage the device. As a CN node, it can be, for example, AMF, SMF, UPF, PCF, UDM, NF, NWDAF (Network Data Analytics Function), DMF, etc. The base station sends the settings to the UE. The method for sending the settings from the base station to the UE can appropriately apply the methods disclosed in Implementation 1 and Implementation 2. The UE communicates with the device. The UE can use the settings for UE-device communication received from the application, etc. via the base station to perform UE-device communication.

[0326] The UE sends device data to the base station. The UE can use the device data transmission settings received from the application, etc. via the base station to send device data. The UE sends device data received from the UE to the application. The base station can send device data to the DN. The base station can send device data to the MnS. The base station can send device data to the CN node.

[0327] Device data-related information can be sent along with the device data. The device data-related information can be included in the device data or sent along with the device data. Alternatively, it can be sent separately from the device data. The destinations for the device data and the device data-related information can be different. The method for sending the device data-related information can appropriately apply the methods disclosed in Embodiments 1 and 2.

[0328] As a result, applications using the device can perform the settings and receive device data and device data-related information. Services using the device can be performed. Furthermore, the settings can be sent from the DN, and device data and device data-related information can be received. For example, a node connected to the DN can manage the device, device data, and device data-related information. Furthermore, the MnS can perform the settings and receive device data and device data-related information. The MnS can manage the device, device data, and device data-related information. The device can be incorporated into the management of the mobile communication system. Furthermore, the CN node can perform the settings and receive device data and device data-related information. The CN node can manage the device, device data, and device data-related information. The device can be incorporated into the mobile communication system.

[0329] The source of this setting can be different from the source of the device data and device data-related information. For example, the MnS can set this setting, and the device data can be sent to the application. This allows for the provision of various services using the device.

[0330] UE-device communication settings and / or device data transmission settings can be sent from an application to nodes associated with UE-device communication or device data transmission. These settings can be sent from DN, MnS, or CN nodes, rather than from the application. Examples of associated nodes include base stations, AMFs, SMFs, UPFs, NWDAFs, NEFs, and DMFs. The settings sent to the associated nodes can be part or all of the settings sent to the UE.

[0331] The source of this configuration information can be multiple rather than just one. The configuration information can be shared among multiple sources. For example, the AF can configure the service, while the base station can configure the RAN. This allows for configurations tailored to the functions of the source of the configuration.

[0332] Publicize the transmission path of device data and / or device data-related information. When sending device data, etc. to a CN node, it is sent from the base station to the CN node. Device data, etc. can be sent from the base station to the CN node via other CN nodes. For example, device data, etc. can be sent from the base station to the NWDAF via the AMF. Device data, etc. can be sent from the base station to the DMF via the AMF and NWDAF, for example. When sending device data, etc. to the MnS, it is sent from the base station to the MnS. It can be sent to the MnS via the CN node. For example, it can be sent from the base station to the NWDAF via the AMF and DCE. When sending device data, etc. to the AF, it is sent from the base station to the AF via the CN node. It can be sent to the AF via the MnS. For example, it can be sent from the base station to the AF via the AMF and NEF. For example, it can be sent from the base station to the AF via the MnS. For example, it can be sent from the base station to the AF via the AMF and MnS. For example, it can be sent to the AF via the AMF, NWDAF, and DCE.

[0333] When sending device data, etc. to an AS, it is sent from the base station via a CN node to the AS. For example, it can be sent from the base station via a UPF. For example, it can be sent from the base station to the AS via an AMF, SMF, or UPF. When sending device data to a DN, it is sent from the base station via a CN node to the DN. For example, it can be sent from the base station via a UPF. For example, it can be sent from the base station to the DN via an AMF, SMF, or UPF.

[0334] A transmission path for device data and / or device data-related information can be configured. The transmission source of the device data transmission configuration can configure the device data transmission path. The device data transmission path configuration information can be included in the device data transmission configuration. The transmission source of the device data transmission configuration can transmit the transmission path configuration information to nodes related to device data transmission.

[0335] The following discloses examples of six device data transmission path setting information.

[0336] (1) Information related to the device data transmission destination. (2) Information about the node that sent the device data. (3) Information about the node that receives the device data. (4) Information related to the service. (5) Information used to determine the device data transmission path. (6) A combination of (1) to (5).

[0337] (1) Information related to the target of device data transmission. It can be information used to determine the transmission target. For example, it can be an identifier, address, etc. This information can be, for example, information used to identify the device data transmission target node (for example, AMF, UPF, etc.). They can also be combined. (2) It can be information indicating to which node the device data is sent. For example, information used to determine the node can be an identifier, address, etc. This information can be, for example, information used to identify the device data transmission target node. They can also be combined. (3) It can be information indicating from which node the device data is received. For example, information used to determine the node can be an identifier, address, etc. This information can be, for example, information used to identify the device data transmission source node (for example, AMF, UPF, etc.). They can also be combined. (4) It can be information used to determine the service. For example, it can be the identifier of the service, etc. In addition, it can be the QoS required by the service.

[0338] Information, such as an identifier, for determining the set service data transmission path can be set. (5) This information can be used. Multiple paths can be set, and the identifier can be used to set which path to use. For example, the service can be associated with the identifier of the path. The information associated with (1) to (4) can be set for each path. In this way, a path suitable for the service can be set.

[0339] Each node that has received the setting information of the transmission path can identify the node from which the device data is to be received, the node to which the device data is to be transmitted, and the final destination of the device data.

[0340] This makes it possible to set a transmission path for device data. For example, it is possible to set a transmission path suitable for a service using the device or a transmission path suitable for the status of each node.

[0341] An application can send a device data transmission request to a base station. A DN, MnS, or CN node can send a device data transmission request to a base station. A base station can send a device data transmission request to a UE. The method for sending a device data transmission request from a base station to a UE can appropriately apply the methods disclosed in Embodiments 1 and 2. Upon receiving the request, the UE transmits the device data to the base station. The base station, which receives the device data from the UE, sends the device data to the requesting source.

[0342] The source of the device data transmission request may be the device data transmission destination disclosed above. The transmission path of the device data transmission request may be the opposite of the device data transmission path disclosed above. The source of the device data transmission request may configure the device data transmission path. The source of the device data transmission request may configure the device data transmission path and transmit the configuration information to nodes related to device data transmission. The source of the device data transmission request may be the same as or different from the source of the UE-device communication configuration and / or the device data transmission configuration.

[0343] This method also allows the source of the UE-device communication settings and / or device data transmission settings to be different from the source of the device data transmission request. For example, the source of the UE-device communication settings and / or device data transmission settings can be set to the PCF, while the source of the device data transmission request can be set to the AF. This enables communication of device data suitable for services using the device.

[0344] The above disclosure discloses that NWDAF can be set as the target for sending device data and / or device data-related information or a node within the sending path. Device data and / or device data-related information can be set as input to NWDAF. NWDAF is an application for analyzing NW data. By setting device data and / or device data-related information as input to NWDAF, various analyses can be performed using the device data and / or device data-related information in NWDAF. In addition, the analysis results in NWDAF can be used as output and sent to the device data sending target. As a result, device data and device data-related information can be analyzed and processed within the mobile communication system, and the results can be used in applications, MnS, etc.

[0345] Figure 15 : is a diagram showing a sequence example of device data communication between a device and the NW. Figure 15 The example in Figure 15 illustrates a case where the AF is the source of UE-device communication settings and device data transmission settings, and the AS is the destination of device data. In step ST1501, the UE sends information to the base station indicating that it can communicate with the device. Upon receiving this information, the base station sends this information to the AMF in step ST1502. This information can be sent, for example, in a NAS message. The AMF can then recognize that the UE can communicate with the device.

[0346] In step ST1503, the AF sends the UE-device communication settings and the device data transmission settings to the NEF. The NEF, having received the settings, sends the settings to the AMF in step ST1504. The AMF, having received the settings, sends the settings to the base station in step ST1505. The base station, having received the settings, sends the settings to the UE in step ST1508. Thus, the AF can send the UE-device communication settings and the device data transmission settings to the UE. The UE can receive the UE-device communication settings and the device data transmission settings from the AF. The AMF, having received the settings from the NEF, can determine which UE can communicate with the device. The settings can be sent to UEs that can communicate with the device.

[0347] After receiving this configuration from the NEF, the AMF sends the device data transmission configuration to the SMF in step ST1506. The AMF can use the information about the device data transmission path included in this configuration to determine the node to which the configuration should be sent. The SMF, having received this configuration, sends this configuration to the UPF in step ST1507. The SMF and AMF can use the information about the device data transmission path included in this configuration to determine the node to which the configuration should be sent. This allows the AF to send the configuration to nodes requiring the UE-device communication configuration and nodes requiring the device data transmission configuration.

[0348] The settings for sending device data can be sent through signaling different from the settings for UE-device communication.

[0349] The UE that has received the UE-device communication configuration in step ST1508 uses the configuration to communicate with the device in step ST1509. The UE that has received device data from the device stores the device data in a buffer within the UE in step ST1510. The UE transmits the device data to the base station in step ST1511. This transmission may use the configuration for transmitting device data. The base station transmits the device data to the UPF in step ST1512. This transmission may use the configuration for transmitting device data. The base station may use information about the device data transmission path included in the configuration to determine to which node the configuration is to be transmitted. The UPF transmits the device data to the AS in step ST1513. This transmission may use the configuration for transmitting device data.

[0350] The information on whether the device data has ended can be set. The device can generate this information and send it to the UE. As another method, the UE can generate this information. This information can be set for each device. For example, it is valid when the transmission of device data is performed on each device. This information can be set for device data from multiple devices. For example, it is valid when the device data of multiple devices are sent in a bundle. The UE can notify the CN node of the information on whether the device data has ended. The CN node can notify the AS of the information on whether the device data has ended. The UE can send this information to the base station, the base station can send this information to the CN node, and the CN node can send this information to the AS. It can be sent together with the device data or separately from the device data. As a result, the CN node and AS that receive this information can recognize that the device data sent from the UE has ended.

[0351] The UE may store the device data association information. In step ST1510, the device data association information may be stored together with the device data. The UE may send the device data association information to the base station. The base station may send the device data association information to the UPF, and the UPF may send the device data association information to the AS. The device data association information may be sent together with the device data. The base station, UPF, and AS may receive the device data association information.

[0352] You can configure changes and releases for UE-device communication settings and / or device data transmission settings. For example, the AF can send changes and releases for UE-device communication settings and / or device data transmission settings to the NEF, AMF, base station, and UE. Each node can use this setting change to change settings and terminate UE-device communication and device data transmission by releasing the settings.

[0353] As a result, the AF enables the UE to perform UE-device communication, the AS can receive device data from the UE, applications can receive device data via the UE, and communication between devices and the NW is possible.

[0354] Figure 16 This is a diagram showing a first other sequence example of device data communication between the device and the NW. Figure 16 Illustrate the device data transmission path and Figure 15 For different cases. Figure 15Common steps are marked with the same step numbers, and common descriptions are omitted. The base station that receives the device data from the UE in step ST1511 sends the device data to the AMF in step ST1601. The device data sending setting can be used in this sending. For example, information related to the device data sending path included in the setting can be used to determine to which node the device data is to be sent. The AMF sends the device data to the SMF in step ST1602. The device data sending setting can be used in this sending. The SMF sends the device data to the UPF in step ST1603. The device data sending setting can be used in this sending. The UPF sends the device data to the AS in step ST1604. The device data sending setting can be used in this sending.

[0355] like Figure 16 As shown in the example, device data is sent from the base station to the UPF and AS via the AMF and SMF, so that device data can be sent from the UE to the AMF on the CP (Control Plane). The UP (User Plane) can be omitted. For example, a DRB (Data Radio Bearer) can be omitted to send device data. An SRB (Signaling Radio Bearer) can be used to send device data.

[0356] Figure 17 This is a diagram showing a second other sequence example of device data communication between the device and the NW. Figure 17 The following example shows that the AF is the source of the UE-device communication settings and the device data transmission settings, and the device data is also sent to the AF. There can be one or more CN nodes. The communication between the NEF and the base station can be carried out through one or more CN nodes. Figure 15 The same step numbers are assigned to the common steps, and the common descriptions are omitted.

[0357] In step ST1701, the AF sends the settings for UE-device communication and the settings for device data transmission to the NEF. The NEF, having received the settings, sends the settings to the CN node in step ST1702. The CN node, having received the settings, sends the settings to the base station in step ST1703. The base station, having received the settings, sends the settings to the UE in step ST1704. As a result, the AF can send the settings for UE-device communication and the settings for device data transmission to the UE. The UE can receive the settings for UE-device communication and the settings for device data transmission from the AF. The CN node, having received the settings from the NEF, can determine which UE can communicate with the device. The CN node can send the settings to the UE that can communicate with the device.

[0358] The settings for sending device data can be sent through signaling different from the settings for UE-device communication.

[0359] The UE that has received the UE-device communication settings in step ST1704 uses the settings to perform communication with the device in step ST1705. The UE that has received device data from the device stores the data in a buffer within the UE in step ST1706. The UE sends the device data to the base station in step ST1707. The device data transmission settings can be used in this transmission. The base station sends the device data to the CN node in step ST1708. The device data transmission settings can be used in this transmission. Information related to the transmission path of the device data included in the settings can be used to determine which node to send the settings. The CN node sends the device data to the NEF in step ST1709. The device data transmission settings can be used in this transmission. The NEF sends the device data to the AF in step ST1710. The device data transmission settings can be used in this transmission.

[0360] The UE may store the device data association information. In step ST1706, the device data association information may be stored together with the device data. The UE may send the device data association information to the base station. The base station may send the device data association information to the CN node. The CN node may send the device data association information to the NEF. The NEF may send the device data association information to the AF. The device data association information may be sent together with the device data. The AF may receive the device data association information.

[0361] This allows the AF to enable UE-to-device communication and receive device data from the UE. For example, by using a CP node as a CN node, the AF can receive device data without using a UP CN node. Device-to-NW communication is possible within the CP.

[0362] Figure 18 This is a diagram showing a third other sequence example of device data communication between the device and the NW. Figure 18 The following example is shown: MnS is the source of the settings for UE-device communication and device data transmission, and the destination of device data is DCE. There can be one or more CN nodes. The communication between NEF and base station can be carried out through one or more CN nodes. Figure 15 The same step numbers are assigned to the common steps, and the common descriptions are omitted.

[0363] In step ST1801, the MnS sends the UE-device communication settings and the device data transmission settings to the CN node. The CN node that receives these settings sends them to the base station in step ST1802. The base station that receives these settings sends them to the UE in step ST1803. Thus, the MnS can send the UE-device communication settings and the device data transmission settings to the UE. The UE can receive the UE-device communication settings and the device data transmission settings from the MnS. The CN node that receives these settings from the MnS can determine which UE can communicate with the device. The CN node can send these settings to UEs that can communicate with the device.

[0364] The settings for sending device data can be sent through signaling different from the settings for UE-device communication.

[0365] The UE that has received the UE-device communication settings in step ST1803 uses the settings to communicate with the device in step ST1804. The UE that has received device data from the device stores the device data in a buffer within the UE in step ST1805. The UE sends the device data to the base station in step ST1806. The device data transmission settings can be used in this transmission. The base station sends the device data to the CN node in step ST1807. The device data transmission settings can be used in this transmission. Information related to the device data transmission path included in the settings can be used to determine to which node the settings are to be sent. The CN node sends the device data to the DCE in step ST1808. The device data transmission settings can be used in this transmission.

[0366] The UE may store the device data association information. In step ST1805, the device data association information may be stored together with the device data. The UE may send the device data association information to the base station. The base station may send the device data association information to the CN node. The CN node may send the device data association information to the DCE. The device data association information may be sent together with the device data. The DCE may receive the device data association information.

[0367] As a result, the management service of the mobile communication system enables the UE to perform UE-device communication, the data collection node can receive device data from the UE, and communication between the device and the NW can be carried out.

[0368] The sending destination of the device data association information and the sending destination of the device data may be the same or different. For example, in the case where the NW node that utilizes the device data also uses the device data association information, the sending destination may be set to be the same. For example, in the case where the NW node that is different from the NW node that utilizes the device data uses the device data association information, the sending destination may be made different. For example, the device data may be sent to the AS, and the device data association information may be sent to the AF. The data from the device may be stored in the AS and used for applications, and the device data association information may be used by the AF for application management. For example, the device data may be sent to the AS, and the device data association information may be sent to the MnS. The data from the device may be stored in the AS and used for applications, and the device data association information may be used by the MnS for network management suitable for the application. In this way, the device can be incorporated, and an NW that is more suitable for services that use the device can be constructed.

[0369] By adopting the method disclosed in this embodiment, device data communication can be performed between the device and the NW. Applications, DNs, MnSs, and CN nodes can obtain device data and device data-related information, and can process and manage device data. For example, by sending device data and device data-related information from devices such as wearable terminals to applications, the health status can be grasped and managed through applications. For example, by sending device data and device data-related information such as reception quality and location information from industrial sensor equipment to NWDAF, the information can be analyzed by NWDAF. For example, by sending device data and device data-related information such as time information and location information from environmental sensor equipment to MnS, network resources corresponding to the environment, time, location, etc. can be optimized. In this way, the device can be incorporated into the 3GPP mobile communication system, and services using the device can be provided.

[0370] The UE can send device data and device data-related information to other UEs. Alternatively, the UE can send device data and device data-related information to the NW via other UEs. UE-UE relays can be used for transmission from the UE to other UEs. UE-NW relays can be used for transmission from the UE to the NW. PC5, which serves as an interface for direct communication between UEs, can be used in these communications. For example, in the methods disclosed in Embodiments 1 to 3, UE-NW relays can be used for communication between the UE and the NW. Communication between the UE and the base station can be carried out via the UE-NW relay. For example, a UE that is outside the range of the base station can send device data to the base station via the UE-NW relay. For example, in the methods disclosed in Embodiments 1 to 3, the UE sends device data and device data-related information to other UEs. The other UE can send the received device data and device data-related information to the NW. For example, a UE that is outside the range of the base station can send device data to the base station via other UEs. For example, in the method disclosed in Embodiment 2, if the device data or device data-related information exceeds a specified amount and cannot be stored in the buffer, the UE can send the device data or device data-related information exceeding the specified amount to other UEs. The other UEs can then send the received device data or device data-related information to the NW. This allows more device data or device data-related information to be sent to the NW even when the amount that the UE can store is limited.

[0371] In the communication system described in this disclosure, one gNB forms one or more cells. Although references to gNBs or cells are made in this disclosure, unless otherwise specified, the term "gNB" may refer to either cell.

[0372] In this disclosure, gNB can be either MCG or SCG.

[0373] The above-mentioned embodiments and their modifications are merely examples, and the embodiments and their modifications can be freely combined. In addition, any structural elements of the embodiments and their modifications can be appropriately changed or omitted.

[0374] For example, in the above embodiments and their variations, a subframe is an example of a time unit for communication in a fifth-generation communication system. A time slot can be a scheduling unit. In the above embodiments and their variations, processing described in terms of time slots can be performed in terms of TTIs, subframes, subslots, or minislots.

[0375] For example, the methods disclosed in the above embodiments and their variations can be applied to IAB, communications between an IAB host and an IAB node, and processing using Uu in IAB.

[0376] For example, the methods disclosed in the above-mentioned embodiments and their variations can be applied to communication between UEs or between UEs and NWs via a relay using SL communication.

[0377] For example, the methods disclosed in the above embodiments and their variations are not limited to V2X (Vehicle-to-Everything) services but can also be applied to services that utilize SL communication. For example, they can be applied to SL communication used in various services, such as proximity-based services, public safety, communication between wearable devices, and communication between devices in factories. Label Description

[0378] 202 Communication terminal device (mobile terminal) 210 Communication System 213, 240-1, 240-2, 750 base station devices (NR base stations, base stations) 214 5G Core Department 215 Central Unit 216 decentralized units 217 Central unit for control layer 218 User Floor Central Unit 219TRP 301, 403 protocol processing department 302 Application Department 304, 405 coding department 305, 406 modulation department 306, 407 frequency conversion unit 307-1 to 307-4, 408-1 to 408-4 antennas 308, 409 demodulation unit 309, 410 decoding unit 310, 411, 526 Control Department 401EPC Communications Department 402 Other base station communication departments 412 5GC Communications Department 521 Data Network Communications Department 522 Base Station Communications Department 523 User Layer Communication Department 523-1PDU Processing Unit 523-2 Mobile Anchoring Unit 525 Control Layer Control Unit 525-1NAS Security Department 525-2 Idle State Mobility Management Department 527 Session Management Department 527-1PDU Session Control Unit 527-2UE IP Address Allocation Department Beams 751-1 to 751-8 Community 752.

Claims

1. A communication system, characterized in that: include: A base station, which corresponds to a fifth-generation wireless access system; a communication terminal connected to the base station; as well as a device connected to the base station or the communication terminal, The base station transmits communication setting information and device data transmission setting information to the communication terminal, wherein the communication setting information is information related to settings for communication between the communication terminal and the device, and the device data transmission setting information is information related to settings for the communication terminal to transmit device data acquired from the device to the base station. The communication terminal communicates with the device using the communication setting information received from the base station, and transmits the device data to the base station using the device data transmission setting information received from the base station.

2. The communication system according to claim 1, wherein When the communication terminal communicates with the device and acquires device data while not connected to the base station, the communication terminal stores the acquired device data, and transmits the stored device data to the base station when connected to the base station.

3. The communication system according to claim 1 or 2, wherein: The device data transmission setting information includes device data transmission path setting information, which is information related to the transmission path of the device data. The communication terminal transmits the device data by following the path of the device data transmission path setting information included in the device data transmission setting information received from the base station.

Images