Communication system
The communication system addresses the challenge of maintaining continuous communication with ultra-low power consumption IoT devices by enabling UE detection of disconnections and coordinated searches among UEs to re-establish connections, ensuring uninterrupted service and efficient resource management.
Patent Information
- Application Number
- PCT/JP2024/016670
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-10
- Filing Date
- 2024-04-30
- Publication Date
- 2024-11-14
AI Technical Summary
Current 5G wireless communication systems face challenges in maintaining continuous communication with ultra-low power consumption IoT devices, particularly when these devices move and lose connection with the UE, leading to disruptions in communication between the device and the network.
The proposed solution involves a communication system where the UE detects disconnections with IoT devices and initiates a search process to re-establish connection, involving multiple UEs in the search and notification to the base station or core network to quickly identify and reconnect with the device, ensuring continuous communication.
This approach enables the restoration of communication between IoT devices and the network even when connections are lost, ensuring uninterrupted service and efficient resource management in the communication system.
Smart Images

Figure JP2024016670_14112024_PF_FP_ABST
Abstract
Description
communication systems
[0001] The present disclosure relates to wireless communication technology.
[0002] The 3rd Generation Partnership Project (3GPP), a standardization organization for mobile communication systems, is considering a fifth-generation (hereinafter sometimes referred to as "5G") wireless access system 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) (for example, Non-Patent Document 2). 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 studied based on the LTE system and the LTE-A system.
[0003] For example, in Europe, an organization called METIS has compiled 5G requirements (see Non-Patent Document 3). The requirements for a 5G wireless access system are that it must have 1000 times the system capacity, 100 times the data transmission speed, one-fifth the data processing delay, and 100 times the number of simultaneous connections of communication terminals compared to an LTE system, while also achieving further reductions in power consumption and cost reductions for the equipment (see Non-Patent Document 3).
[0004] In order to meet such demands, 3GPP is currently studying 5G standards (see Non-Patent Documents 4 to 23).
[0005] The NR access method uses OFDM (Orthogonal Frequency Division Multiplexing) in the downlink direction and OFDM and DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) in the uplink direction. Also, like LTE and LTE-A, the 5G system does not include circuit switching and is only a packet communication method.
[0006] NR allows the use of higher frequencies than LTE in order to improve transmission speeds and reduce processing delays.
[0007] In NR, which may use higher frequencies than LTE, cell coverage is ensured by forming a narrow beam-shaped transmission and reception range (beam forming) and changing the direction of the beam (beam sweeping).
[0008] The decisions made by 3GPP regarding the frame structure in an NR system, as described in Non-Patent Document 1 (Chapter 5), are explained using Figure 1. Figure 1 is an explanatory diagram showing the structure of a radio frame used in an NR communication system. In Figure 1, one radio frame is 10 ms. The radio frame is divided into 10 equally sized subframes. The NR frame structure supports one or more numerologies, i.e., one or more subcarrier spacings (SCSs). In NR, one subframe is 1 ms long, and one slot consists of 14 symbols, regardless of the subcarrier spacing. Furthermore, the number of slots included in one subframe is one when the subcarrier spacing is 15 kHz, and the number of slots at other subcarrier spacings increases in proportion to the subcarrier spacing (see Non-Patent Document 11 (3GPP TS38.211)).
[0009] 3GPP's decisions regarding channel configuration in NR systems are described in Non-Patent Document 2 (Chapter 5) and Non-Patent Document 11.
[0010] A physical broadcast channel (PBCH) is a channel for downlink transmission from a base station device (hereinafter sometimes simply 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 simply referred to as a "mobile terminal"). The PBCH is transmitted together with a downlink synchronization signal.
[0011] Downlink synchronization signals in NR include a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS). Synchronization signals are transmitted from base stations as synchronization signal bursts (hereinafter sometimes referred to as SS bursts) at predetermined intervals and for a predetermined duration. SS bursts are composed of synchronization signal blocks (hereinafter sometimes referred to as SS blocks) for each beam of the base station.
[0012] The base station transmits the SS block of each beam by changing the beam during the duration of the SS burst. 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 a base station to a communication terminal. The PDCCH carries downlink control information (DCI). The DCI includes resource allocation information for a Downlink Shared Channel (DL-SCH), which is one of the transport channels described below, resource allocation information for a Paging Channel (PCH), which is one of the transport channels described below, and Hybrid Automatic Repeat reQuest (HARQ) information related to the DL-SCH. The DCI may also include an uplink scheduling grant. The DCI may also include an acknowledgement (Ack) / negative acknowledgement (Nack), which is a response signal to the uplink transmission. In addition, in order to flexibly switch between DL and UL within a slot, the DCI may include a slot format indication (SFI). The PDCCH or the DCI is also called an L1 / L2 control signal.
[0014] In NR, a time-frequency region that is a candidate for including a PDCCH is provided. This region is called a control resource set (CORESET). A communication terminal monitors the CORESET and acquires a PDCCH.
[0015] The Physical Downlink Shared Channel (PDSCH) is a channel for downlink transmission from a base station to a communication terminal. The Downlink Shared Channel (DL-SCH), which is a transport channel, and the PCH, which is a transport channel, are mapped to the PDSCH.
[0016] The Physical Uplink Control Channel (PUCCH) is a channel for uplink transmission from a communication terminal to a base station. The PUCCH carries uplink control information (UCI). The UCI includes Ack / Nack, which is a response signal to a downlink transmission, CSI (Channel State Information), a scheduling request (SR), and the like. The CSI is composed of a Rank Indicator (RI), a Precoding Matrix Indicator (PMI), and a CQI (Channel Quality Indicator) report. The RI is rank information of a channel matrix in MIMO (Multiple Input Multiple Output). The PMI is information on a precoding weight matrix used in MIMO. The CQI is quality information indicating the quality of received data or the quality of a communication path. The UCI may be carried by the PUSCH, which will be described later. The PUCCH or UCI is also called an L1 / L2 control signal.
[0017] The Physical Uplink Shared Channel (PUSCH) is a channel for uplink transmission from a communication terminal to a base station. The Uplink Shared Channel (UL-SCH), which is one of the transport channels, is mapped to the PUSCH.
[0018] A physical random access channel (PRACH) is a channel for uplink transmission from a communication terminal to a base station. The PRACH carries a random access preamble.
[0019] A downlink reference signal (RS) is a known symbol in an NR communication system. The following four types of downlink reference signals are defined: a demodulation reference signal (DM-RS), which is a UE-specific reference signal, a phase tracking reference signal (PT-RS), a positioning reference signal (PRS), and a channel state information reference signal (CSI-RS). Measurements of the physical layer of a communication terminal include reference signal received power (RSRP) measurement and reference signal received quality (RSRQ) measurement.
[0020] Similarly, the uplink reference signal is a known symbol in an NR communication system. The following three types of uplink reference signals are defined: a data demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), and a sounding reference signal (SRS).
[0021] The transport channels described in Non-Patent Document 2 (Chapter 5) will be described below. Among the downlink transport channels, a broadcast channel (BCH) is broadcast to the entire coverage of the base station (cell). The BCH is mapped to a physical broadcast channel (PBCH).
[0022] Retransmission control using HARQ is applied to the Downlink Shared Channel (DL-SCH). The DL-SCH can be broadcast to the entire coverage of the base station (cell). The DL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also called semi-persistent scheduling. The DL-SCH supports discontinuous reception (DRX) in communication terminals to reduce power consumption of the communication terminals. The DL-SCH is mapped to the Physical Downlink Shared Channel (PDSCH).
[0023] The Paging Channel (PCH) supports DRX of communication terminals to enable low power consumption of the communication terminals. The PCH is required to broadcast to the entire coverage of the base station (cell). The PCH is mapped to physical resources such as the Physical Downlink Shared Channel (PDSCH) that can be dynamically used for traffic.
[0024] Among the uplink transport channels, the uplink shared channel (UL-SCH) is subject to retransmission control using HARQ. The UL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also called 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, has a risk of collision, and is mapped to the Physical Random Access Channel (PRACH).
[0026] The following describes HARQ. HARQ is a technology that improves the communication quality of a transmission path by combining Automatic Repeat reQuest (ARQ) and Forward Error Correction. HARQ has the advantage that error correction functions effectively through retransmission even for transmission paths whose communication quality varies. In particular, by combining the reception result of the initial transmission and the reception result of the retransmission when retransmitting, it is possible to obtain further quality improvement.
[0027] An example of a retransmission method will be described below. If the receiving side is unable to decode the received data correctly, in other words, if a CRC (Cyclic Redundancy Check) error occurs (CRC=NG), the receiving side will send a "Nack" to the transmitting side. The transmitting side, having received the "Nack", will retransmit the data. If the receiving side is able to decode the received data correctly, in other words, if no CRC error occurs (CRC=OK), the receiving side will send an "Ack" to the transmitting side. The transmitting side, having received the "Ack", will send the next data.
[0028] Another example of a retransmission method will be described. If a CRC error occurs on the receiving side, the receiving side requests a retransmission from the transmitting side. The retransmission request is made by toggling an NDI (New Data Indicator). The transmitting side, upon receiving the retransmission request, retransmits the data. If no CRC error occurs on the receiving side, no retransmission request is made. If the transmitting side does not receive a retransmission request for a predetermined period of time, it assumes that no CRC error 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 for broadcasting system control information. The BCCH, which is a logical channel, is mapped to the broadcast channel (BCH) or the downlink shared channel (DL-SCH), which are transport channels.
[0030] The Paging Control Channel (PCCH) is a downlink channel for transmitting paging information and changes to system information. The PCCH, which is a logical channel, is mapped to the Paging Channel (PCH), which is a transport channel.
[0031] The Common Control Channel (CCCH) is a channel for transmitting control information between a communication terminal and a base station. The CCCH is used when the communication terminal does not have an RRC connection with the network. In the downlink direction, the CCCH is mapped to the Downlink Shared Channel (DL-SCH), which is a transport channel. In the uplink direction, the CCCH is mapped to the Uplink Shared Channel (UL-SCH), which is a transport channel.
[0032] A Dedicated Control Channel (DCCH) is a channel that transmits dedicated control information between a communication terminal and a network in a one-to-one relationship. The DCCH is used when the communication terminal has an RRC connection with the network. The DCCH is mapped to an uplink shared channel (UL-SCH) in the uplink and to a downlink shared channel (DL-SCH) in the downlink.
[0033] A Dedicated Traffic Channel (DTCH) is a point-to-point communication channel for transmitting user information to a communication terminal. DTCH exists in both uplink and downlink. In uplink, DTCH is mapped to an uplink shared channel (UL-SCH) and in downlink, it is mapped to a downlink shared channel (DL-SCH).
[0034] The location of a communication terminal is tracked in units of an area consisting of one or more cells. Location tracking is performed to track the location of the communication terminal even when it is in standby mode and to call the communication terminal, in other words, to enable the communication terminal to receive calls. The area for tracking the location of this communication terminal is called a Tracking Area (TA).
[0035] In NR, paging of communication terminals within a range that is smaller than a tracking area is supported. This range is called a RAN Notification Area (RNA). Paging of communication terminals in the RRC_INACTIVE state, which will be described later, is performed within this range.
[0036] In NR, in order to support wide frequency bandwidths (transmission bandwidths), carrier aggregation (CA) is being considered, which aggregates (also referred to as "aggregation") two or more component carriers (CCs). CA is described in Non-Patent Document 1.
[0037] When CA is configured, a communication terminal (UE) has only one RRC connection with the network (NW). In the RRC connection, one serving cell provides NAS (Non-Access Stratum) mobility information and security input. This cell is called a primary cell (PCell). Depending on the UE's capabilities, a secondary cell (SCell) is configured to form a serving cell set together with the PCell. A serving cell set consisting of one PCell and one or more SCells is configured for one UE.
[0038] In addition, in 3GPP, in order to further increase communication capacity, there is a dual connectivity (abbreviated as DC) in which a UE connects to two base stations to communicate. DC is described in Non-Patent Documents 1 and 22.
[0039] Of the base stations performing dual connectivity (DC), one may be referred to as a "master base station (Master Node: MN)" and the other as a "secondary base station (Secondary Node: SN)." Serving cells configured by the master base station may be collectively referred to as a master cell group (MCG), and serving cells configured by secondary base stations may be collectively referred to as a secondary cell group (SCG). In DC, the primary cell in the MCG or SCG is referred to as a special cell (SpCell or SPCell). The special cell in the MCG is referred to as a PCell, and the special cell in the SCG is referred to as a primary SCG cell (PSCell).
[0040] In addition, in NR, the base station pre-sets a portion of the carrier frequency band (hereinafter sometimes referred to as the Bandwidth Part (BWP)) for the UE, and the UE transmits and receives data to and from the base station using this BWP, thereby reducing power consumption in the UE.
[0041] Additionally, 3GPP is considering supporting services (or applications) using side link (SL) communication (also referred to as PC5 communication) in both the Evolved Packet System (EPS) (described later) and the 5G core system (see Non-Patent Documents 1, 2, 26 to 28). SL communication involves communication between terminals. Services using SL communication include, for example, vehicle-to-everything (V2X) services and proximity services. In SL communication, not only direct communication between terminals but also communication between a UE and a network via a relay has been proposed (see Non-Patent Documents 26 and 28).
[0042] The physical channels used for SL (see Non-Patent Documents 2 and 11) are as follows: The physical sidelink broadcast channel (PSBCH) carries information related to the system and synchronization and is transmitted from the UE.
[0043] The physical sidelink control channel (PSCCH) carries control information from the UE for sidelink and V2X sidelink communications.
[0044] The physical sidelink shared channel (PSSCH) carries data from the UE for sidelink and V2X sidelink communications.
[0045] The physical sidelink feedback channel (PSFCH) carries HARQ feedback on the sidelink from a UE that received a PSSCH transmission to the UE that transmitted the PSSCH.
[0046] The transport channel used for SL (see Non-Patent Document 1) will be described. The sidelink broadcast channel (SL-BCH) has a predetermined transport 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 base station scheduled resource allocation. UE autonomous resource selection involves a collision risk, whereas when the UE is allocated dedicated resources by the base station, there is no collision. The SL-SCH also supports dynamic link adaptation by changing transmit power, modulation, and coding. The SL-SCH is mapped to the PSSCH, which is a physical channel.
[0048] The logical channels used for SL (see Non-Patent Document 2) will be described. The Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel for broadcasting 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 point-to-multipoint traffic channel for transmitting user information from one UE to other UEs. The STCH is used only by UEs with sidelink communication capability and UEs with V2X sidelink communication capability. Point-to-point communication between two sidelink-capable UEs is also realized by the STCH. The STCH is mapped to the SL-SCH, a transport channel.
[0050] The Sidelink Control Channel (SCCH) is a control channel for transmitting control information from one UE to another UE. The SCCH is mapped to the SL-SCH, which is a transport channel.
[0051] In LTE, only broadcast was supported for SL communication. In NR, support for unicast and groupcast as SL communication in addition to broadcast is being considered (see Non-Patent Document 27 (3GPP TS23.287)).
[0052] In unicast communication and groupcast communication in SL, HARQ feedback (Ack / Nack), CSI reporting, etc. are supported.
[0053] In addition, 3GPP is considering integrated access and backhaul (IAB), which performs both the access link between a UE and a base station and the backhaul link between base stations wirelessly (see Non-Patent Documents 2, 20, and 29).
[0054] Several new technologies are being required for mobile communication systems. For example, new technologies are being required to incorporate ultra-low power consumption Internet of Things (IoT) devices into mobile communication systems, such as battery-less devices or devices that can communicate using only an energy storage function without the need for battery replacement or charging. Discussions on such new technologies have begun within the 3GPP (Non-Patent Documents 30, 31, 32, 33).
[0055] 3GPP TS36.300 V17.2.03GPP TS38.300 V17.2.0“Scenarios, requirements and KPIs for 5G mobile and wireless system”、ICT-317669-METIS / D1.13GPP TR23.799 V14.0.03GPP TR38.801 V14.0.03GPP TR38.802 V14.2.03GPP TR38.804 V14.0.03GPP TR38.912 V16.0.03GPP RP-1721153GPP TS23.501 V17.6.03GPP TS38.211 V17.3.03GPP TS38.212 V17.3.03GPP TS38.213 V17.3.03GPP TS38.214 V17.3.03GPP TS38.321 V17.2.03GPP TS38.322 V17.1.03GPP TS38.323 V17.2.03GPP TS37.324 V17.0.03GPP TS38.331 V17.2.03GPP TS38.401 V17.2.03GPP TS38.413 V17.2.03GPP TS37.340 V17.2.03GPP TS38.423 V17.2.03GPP TS38.305 V17.2.03GPP TS23.273 V17.6.03GPP TR23.703 V12.0.03GPP TS23.287 V17.4.03GPP TS23.303 V17.0.03GPP TS38.340 V17.2.03GPP RP-2233963GPP RP-2223353GPP RP-2221263GPP RP-2220693GPP RP-2224403GPP TS22.261 V19.1.0
[0056] Mobile communication systems are expected to use a huge number of IoT devices, such as wearable terminals and sensors, in the future, as communications for a wide variety of services are conducted. Therefore, there is a demand for ultra-low-power IoT devices, such as those that are battery-less or that can communicate using only an energy storage function without the need for replacement or charging. New technologies are needed to incorporate such ultra-low-power IoT devices into mobile communication systems. Discussions on this new technology have begun in 3GPP (Non-Patent Documents 30, 31, 32, 33). However, as such ultra-low-power IoT devices move, the UEs that can connect to the IoT devices may change. However, no processing related to the change in UEs has been disclosed. As a result, a problem arises in which the movement of the IoT device causes the connection with the UE to be severed, subsequently rendering communication between the IoT device and the communication system impossible.
[0057] In view of the above-mentioned problems, one of the objects of the present disclosure is to realize a communication system that enables continuous communication with an IoT device that consumes ultra-low power.
[0058] In order to solve the above-mentioned problems and achieve the objectives, the present disclosure includes a base station compatible with a fifth-generation wireless access system, a communication terminal connected to the base station, and a device connected to the base station, and when the connection between the device and the communication terminal is disconnected, multiple communication terminals execute a device search process, and the communication terminal that is able to search for the device operates as the communication terminal to which the device is connected.
[0059] According to the present disclosure, a communication system that enables continuous communication with an IoT device that consumes ultra-low power can be realized.
[0060] The objects, features, aspects, and advantages of the present disclosure will become more apparent from the following detailed description and the accompanying drawings.
[0061] 1 is an explanatory diagram showing the configuration of a radio frame used in an NR communication system. FIG. 2 is a block diagram showing the overall configuration of an NR communication system 210 being discussed in 3GPP. FIG. 3 is a configuration diagram of DC by a base station connected to an NG core. FIG. 4 is a block diagram showing the configuration of a mobile terminal 202 shown in FIG. 2. FIG. 5 is a block diagram showing the configuration of a base station 213 shown in FIG. 2. FIG. 6 is a block diagram showing the configuration of a 5GC unit. FIG. 7 is a flowchart showing an overview of operations from cell search to standby performed by a communication terminal (UE) in an NR communication system. FIG. 8 is a diagram showing an example of the configuration of a cell in an NR system. FIG. 9 is a connection configuration diagram showing an example of the connection configuration of a terminal in SL communication. FIG. 10 is a connection configuration diagram showing an example of the connection configuration of a base station that supports access / backhaul integration. FIG. 11 is a diagram showing the first half of a sequence illustrating an example of an operation of communication interruption and recovery between a UE and a device according to a first embodiment. FIG. 12 is a diagram showing the second half of a sequence illustrating an example of an operation of communication interruption and recovery between a UE and a device according to a first embodiment. FIG. 13 is a diagram showing the first half of a sequence illustrating another example of an operation of communication interruption and recovery between a UE and a device according to a first embodiment. FIG. 10 is a sequence diagram showing an example of an RLF and its recovery operation in a UE connected to a device, according to a second embodiment. FIG. 11 is a sequence diagram showing another example of an RLF and its recovery operation in a UE connected to a device, according to the second embodiment. FIG. 12 is a diagram showing the first half of a sequence showing another example of an RLF and its recovery operation in a UE connected to a device, according to the second embodiment. FIG. 13 is a diagram showing the second half of a sequence showing another example of an RLF and its recovery operation in a UE connected to a device, according to the second embodiment. FIG. 14 is a diagram showing the first half of a sequence showing an example of communication between a device and a communication network using a plurality of UEs, according to a third embodiment. FIG. 15 is a diagram showing the second half of a sequence showing an example of communication between a device and a communication network using a plurality of UEs, according to the third embodiment.FIG. 10 is a diagram showing the first half of a sequence illustrating another example of communication between a device and a communication network using a plurality of UEs, for the third embodiment. FIG. 11 is a diagram showing the second half of a sequence illustrating another example of communication between a device and a communication network using a plurality of UEs, for the third embodiment. FIG. 12 is a diagram showing the first half of a sequence illustrating an example of an operation of switching a UE to which a device is connected, regarding communication between a UE and a device, for the fourth embodiment. FIG. 13 is a diagram showing the second half of a sequence illustrating an example of an operation of switching a UE to which a device is connected, regarding communication between a UE and a device, for the fourth embodiment. FIG. 14 is a diagram showing the first half of a sequence illustrating another example of an operation of switching a UE to which a device is connected, regarding communication between a UE and a device, for the fourth embodiment. FIG. 15 is a diagram showing the second half of a sequence illustrating another example of an operation of switching a UE to which a device is connected, regarding communication between a UE and a device, for the fourth embodiment. FIG. 16 is a diagram showing the first half of a sequence illustrating an example of an operation of switching a UE to which a device is connected, regarding communication between a UE and a device, for the fifth embodiment. FIG. 17 is a diagram showing the second half of a sequence illustrating an example of an operation of switching a UE to which a device is connected, regarding communication between a UE and a device, for the fifth embodiment. 10 is a diagram showing the first half of a sequence illustrating another example of an operation for switching a UE to which a device is connected, regarding communication between a UE and a device, for embodiment 5. FIG. 11 is a diagram showing the second half of a sequence illustrating another example of an operation for switching a UE to which a device is connected, regarding communication between a UE and a device, for embodiment 5. FIG. 12 is a sequence diagram showing an example of a UE handover operation, regarding communication between a UE and a device, for embodiment 6. FIG. 13 is a diagram showing the first half of a sequence illustrating an example of an operation for a UE to which a device is connected, switching from a UE connected to a 3GPP network to a non-3GPP terminal, regarding embodiment 7. FIG. 14 is a diagram showing the second half of a sequence illustrating an example of an operation for a UE to which a device is connected, switching from a UE connected to a 3GPP network to a non-3GPP terminal, regarding embodiment 7.
[0062] Embodiment 1. Figure 2 is a block diagram showing the overall configuration of an NR communication system 210 being discussed in 3GPP. Figure 2 will be explained. The radio access network is called an NG-RAN (Next Generation Radio Access Network) 211. A mobile terminal device (hereinafter referred to as a "mobile terminal (User Equipment: UE)") 202, which is a communication terminal device, is capable of wireless communication with a base station device (hereinafter referred to as an "NR base station (NG-RAN NodeB: gNB)") 213, and transmits and receives signals via wireless communication. The 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 cell phone terminal devices, but also stationary devices such as sensors. In the following description, the term "communication terminal device" may be simply referred to as a "communication terminal."
[0064] An access stratum (AS) protocol is terminated between the UE 202 and the NG-RAN 211. Examples of AS protocols include radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and physical layer (PHY). RRC is used in the control plane (hereinafter sometimes referred to as the C-plane, C-Plane, or CP), SDAP is used in the user plane (hereinafter sometimes referred to as the U-plane, U-Plane, or UP), and PDCP, MAC, RLC, and PHY are used in both the C-plane and the U-plane.
[0065] The control protocol RRC (Radio Resource Control) between the UE 202 and the NR base station 213 performs broadcasting, paging, RRC connection management, etc. The states of the NR base station 213 and the UE 202 in RRC include RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.
[0066] In RRC_IDLE, PLMN (Public Land Mobile Network) selection, system information (SI) broadcast, paging, cell re-selection, mobility, etc. are performed. In RRC_CONNECTED, the mobile terminal has an RRC connection and can transmit and receive data with the network. In addition, in RRC_CONNECTED, handover (HO), measurement of neighbor cells, etc. are performed. In RRC_INACTIVE, the connection between the 5G core unit 214 and the NR base station 213 is maintained, and system information (SI) broadcast, paging, cell re-selection, mobility, etc. are performed.
[0067] The gNB 213 is connected to a 5G core unit (hereinafter sometimes referred to as the "5GC unit") 214, which includes an Access and Mobility Management Function (AMF), a Session Management Function (SMF), or a User Plane Function (UPF), via an NG interface. Control information and / or user data is communicated between the gNB 213 and the 5GC unit 214. The NG interface is a collective 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. Multiple 5GC units 214 may be connected to one gNB 213. The gNBs 213 are connected via an Xn interface, and control information and / or user data are communicated between the gNBs 213.
[0068] The 5GC unit 214 is a higher-level device, specifically a higher-level node, and controls the connection between the NR base station 213 and the mobile terminal (UE) 202, distributes paging signals to one or more NR base stations (gNB) 213 and / or LTE base stations (E-UTRAN NodeB: eNB), and performs other functions. The 5GC unit 214 also 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, in the inactive state, and in the active state. The 5GC unit 214 initiates a paging protocol by transmitting a paging message to a cell belonging to the tracking area in which the mobile terminal 202 is registered.
[0069] The gNB 213 may configure one or more cells. When one gNB 213 configures multiple cells, each cell is configured to be able to communicate with the UE 202.
[0070] The gNB 213 may be divided into a central unit (hereinafter, sometimes referred to as CU) 215 and a distributed unit (hereinafter, sometimes referred to as DU) 216. One CU 215 is configured within the gNB 213. One or more DUs 216 are configured within the gNB 213. One DU 216 configures one or more cells. The CU 215 is connected to the DU 216 via an F1 interface, and control information and / or user data is communicated between the CU 215 and the DU 216. The F1 interface consists of an F1-C interface and an F1-U interface. The CU 215 is responsible for the functions of the RRC, SDAP, and PDCP protocols, and the DU 216 is responsible for the functions of the RLC, MAC, and PHY protocols. One or more TRPs (Transmission Reception Points) 219 may be connected to the DU 216. The TRP 219 transmits and receives radio signals to and from the UE.
[0071] The CU 215 may be divided into a C-plane CU (CU-C) 217 and a U-plane CU (CU-U) 218. One CU-C 217 is configured within the CU 215. One or more CU-Us 218 are configured within the CU 215. The CU-C 217 is connected to the CU-U 218 via an E1 interface, and control information is communicated between the CU-C 217 and the CU-U 218. The CU-C 217 is connected to the DU 216 via an F1-C interface, and control information is communicated between the CU-C 217 and the DU 216. The CU-U 218 is connected to the DU 216 via an F1-U interface, and user data is communicated between the CU-U 218 and the DU 216.
[0072] In a 5G communication system, a Unified Data Management (UDM) function and a Policy Control Function (PCF) described in Non-Patent Document 10 (3GPP TS23.501) may be included. The UDM and / or PCF may be included in the 5GC unit 214 in FIG. 2 .
[0073] In a 5G communication system, a Location Management Function (LMF) described in Non-Patent Document 24 (3GPP TS 38.305) may be provided. The LMF may be connected to a base station via an AMF as disclosed in Non-Patent Document 25 (3GPP TS 23.273).
[0074] A 5G communication system may include a Non-3GPP Interworking Function (N3IWF) described in Non-Patent Document 10 (3GPP TS23.501). The N3IWF may terminate an Access Network (AN) between the UE and the N3IWF in non-3GPP access between the UE and the N3IWF.
[0075] FIG. 3 is a diagram showing a DC (dual connectivity) configuration connected to an NG core. In FIG. 3, solid lines indicate U-Plane connections, and dashed lines indicate C-Plane connections. In FIG. 3, the master base station 240-1 may be a gNB or an eNB. Furthermore, the secondary base station 240-2 may be a gNB or an eNB. For example, in FIG. 3, a DC configuration in which the master base station 240-1 is a gNB and the secondary base station 240-2 is an eNB may be referred to as NG-EN-DC. In FIG. 3, an example is shown in which 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 may also be performed directly between the 5GC unit 214 and the secondary base station 240-2. 3, an EPC (Evolved Packet Core), which is a core network connected to the LTE system and the LTE-A system, may be connected to the master base station 240-1 instead of the 5GC unit 214. A U-Plane connection may be directly established between the EPC and the secondary base station 240-2.
[0076] FIG. 4 is a block diagram showing the configuration of mobile terminal 202 shown in FIG. 2. The transmission process of mobile terminal 202 shown in FIG. 4 will be described. First, control data from control unit 310 and user data from application unit 302 are sent to protocol processing unit 301. Buffering of the control data and user data may be performed. Buffers for the control data and user data may be provided in control unit 310, application unit 302, or protocol processing unit 301. Protocol processing unit 301 performs protocol processing such as SDAP, PDCP, RLC, and MAC, for example, determining a destination base station in DC, and adding a header for each protocol. The protocol-processed data is passed to encoder unit 304, where it is subjected to encoding such as error correction. Some data may be output directly from protocol processing unit 301 to modulation unit 305 without being encoded. The data encoded by encoder unit 304 is modulated by modulation unit 305. Precoding in MIMO may be performed by modulation unit 305. The modulated data is converted into a baseband signal, and then output to frequency conversion section 306, where it is converted into a radio transmission frequency. Then, the transmission signal is transmitted from antennas 307-1 to 307-4 to base station 213. Although the example in FIG. 4 shows a case where the number of antennas is four, the number of antennas is not limited to four.
[0077] Furthermore, the reception process of the mobile terminal 202 is performed as follows. Radio signals from the base station 213 are received by the antennas 307-1 to 307-4. The received signals are converted from a radio reception frequency to a baseband signal by the frequency conversion unit 306, and demodulated by the demodulation unit 308. The demodulation unit 308 may also perform weight calculation and multiplication processing. The demodulated data is passed to the decoder unit 309, where decoding processes such as error correction are performed. The decoded data is passed to the protocol processing unit 301, where protocol processing such as MAC, RLC, PDCP, and SDAP is performed, for example, operations such as removing headers in each protocol. Of the data that has undergone protocol processing, the control data is passed to the control unit 310, and the user data is passed to the application unit 302.
[0078] A series of processes in the mobile terminal 202 is controlled by a control unit 310. Therefore, the control unit 310 is also connected to each of the units 302, 304 to 309, although this is omitted in FIG.
[0079] Each unit of the mobile terminal 202, such as the control unit 310, protocol processing unit 301, encoder unit 304, and decoder unit 309, is implemented by a processing circuit including, for example, a processor and memory. For example, the control unit 310 is implemented by a processor executing a program describing a series of processes performed by the mobile terminal 202. The program describing the series of processes performed by the mobile terminal 202 is stored in memory. Examples of memory include non-volatile or volatile semiconductor memory such as RAM (Random Access Memory), ROM (Read Only Memory), and flash memory. Each unit of the mobile terminal 202, such as the control unit 310, protocol processing unit 301, encoder unit 304, and decoder unit 309, may be implemented by a dedicated processing circuit such as an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a DSP (Digital Signal Processor). In FIG. 4, the number of antennas used by the mobile terminal 202 for transmission and the number of antennas used for reception may be the same or different.
[0080] 5 is a block diagram showing the configuration of the base station 213 shown in FIG. 2. The transmission process of the base station 213 shown in FIG. 5 will be described. 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 (such as the 5GC unit 214). The other base station communication unit 402 transmits and receives data with other base stations. The EPC communication unit 401, the 5GC communication unit 412, and the other base station communication unit 402 each exchange information with the protocol processing unit 403. Control data from the control unit 411, and user data and control data from the EPC communication unit 401, the 5GC communication unit 412, and the other base station communication unit 402 are sent to the protocol processing unit 403. Buffering of the control data and user data may be performed. Buffers for control data and user data may be provided in the control unit 411, the EPC communication unit 401, the 5GC communication unit 412, or the other base station communication unit 402.
[0081] The protocol processing unit 403 performs protocol processing such as SDAP, PDCP, RLC, MAC, etc., such as routing transmission data in DC, etc., and adding headers for each protocol. The protocol-processed data is passed to the encoder unit 405, where it is subjected to encoding processing such as error correction. Some data may be output directly from the protocol processing unit 403 to the modulation unit 406 without being encoded. Data may also be sent from the protocol processing unit 403 to the other base station communication unit 402. For example, in DC, data sent from the 5GC communication unit 412 or the EPC communication unit 401 may be sent to another base station, such as a secondary base station, via the other base station communication unit 402. The encoded data is modulated by the modulation unit 406. The modulation unit 406 may also perform MIMO precoding. The modulated data is converted into a baseband signal, and then output to the frequency conversion unit 407, where it is converted into a radio transmission frequency. Thereafter, the transmission signals are transmitted from antennas 408-1 to 408-4 to one or more mobile terminals 202. Although the number of antennas is four in the example shown in Fig. 5, the number of antennas is not limited to four.
[0082] Furthermore, the reception process of the base station 213 is performed as follows. Radio signals from one or more mobile terminals 202 are received by antennas 408-1 to 408-4. The received signals are converted from a radio reception frequency to a baseband signal by a frequency conversion unit 407, and demodulated by a demodulation unit 409. The demodulated data is passed to a decoder unit 410, where decoding processes such as error correction are performed. The decoded data is passed to a protocol processing unit 403, where protocol processes such as MAC, RLC, PDCP, and SDAP are performed, for example, operations such as removing headers in each protocol. Of the data that has undergone protocol processing, control data is passed to the control unit 411, 5GC communication unit 412, EPC communication unit 401, or other base station communication unit 402, and user data is passed to the 5GC communication unit 412, EPC communication unit 401, or other base station communication unit 402. Data sent from the other base station communication unit 402 may be sent to the 5GC communication unit 412 or the 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 another base station in DC.
[0083] A series of processes in the base station 213 is controlled by a control unit 411. Therefore, the control unit 411 is also connected to each of the units 401, 402, 405 to 410, and 412, although this is omitted in FIG.
[0084] Each unit of the base station 213, for example, 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 encoder unit 405, and the decoder unit 410, is realized 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 above-mentioned mobile terminal 202. In Fig. 5, the number of antennas used by the base station 213 for transmission and the number of antennas used for reception may be the same or different.
[0085] As an example of the configuration of the CU 215 shown in Fig. 2, a configuration in which a DU communication unit is provided is sometimes used, excluding the encoder unit 405, modulation unit 406, frequency conversion unit 407, antennas 408-1 to 408-4, demodulation unit 409, and decoder unit 410 shown in Fig. 5. The DU communication unit is connected to a protocol processing unit 403. The protocol processing unit 403 in the CU 215 performs protocol processing such as PDCP and SDAP.
[0086] As an example of the configuration of the DU 216 shown in Fig. 2, a configuration in which a CU communication unit is provided may be used, excluding the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown in Fig. 5. The CU communication unit is connected to a protocol processing unit 403. The protocol processing unit 403 in the DU 216 performs protocol processing such as PHY, MAC, and RLC.
[0087] FIG. 6 is a block diagram showing the configuration of the 5GC unit. FIG. 6 shows the configuration of the 5GC unit 214 shown in FIG. 2 described above. FIG. 6 shows a case where the 5GC unit 214 shown in FIG. 2 includes an AMF configuration, an SMF configuration, and a UPF configuration. In the example shown in FIG. 6, the AMF may have the function of the control plane control unit 525, the SMF may have the function of the session management unit 527, and the UPF may have the functions of the user plane communication unit 523 and the Data Network communication unit 521. The Data Network communication unit 521 transmits and receives data between the 5GC unit 214 and the Data Network. The base station communication unit 522 transmits and receives data via the NG interface between the 5GC unit 214 and the base station 213. User data sent from the Data Network is passed from the Data Network communication unit 521 to the base station communication unit 522 via the user plane communication unit 523, and then transmitted to one or more base stations 213. User data sent from the base station 213 is passed from the base station communication unit 522 to the Data Network communication unit 521 via the user plane communication unit 523, and then transmitted to the Data Network.
[0088] The control data sent from the base station 213 is passed from the base station communication unit 522 to the control plane control unit 525. The control plane control unit 525 may pass the control data to the session management unit 527. The control data may be sent from the Data Network. The control data sent from the Data Network may be sent from the Data Network communication unit 521 to the session management unit 527 via the user plane communication unit 523. The session management unit 527 may send the control data to the control plane control unit 525.
[0089] The user plane communication unit 523 includes a PDU processing unit 523-1, a mobility anchoring unit 523-2, etc., and performs general processing for the user plane (hereinafter sometimes referred to as U-Plane). The PDU processing unit 523-1 processes data packets, for example, transmitting and receiving packets to and from the Data Network communication unit 521, and transmitting and receiving packets to and from the base station communication unit 522. The mobility anchoring unit 523-2 is responsible for anchoring the data path during UE mobility.
[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, etc. 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 assigns an IP address to the mobile terminal 202, etc.
[0091] The control plane control unit 525 includes a NAS security unit 525-1, an idle state mobility management unit 525-2, etc., and performs overall processing for the control plane (hereinafter sometimes referred to as the C-Plane). The NAS security unit 525-1 performs security for NAS (Non-Access Stratum) messages, etc. The idle state mobility management unit 525-2 performs mobility management in the standby state (idle state: also referred to as RRC_IDLE state or simply idle), generation and control of paging signals in the standby state, addition, deletion, update, search, tracking area list management, etc. for one or more mobile terminals 202 under its control.
[0092] A series of processes of the 5GC unit 214 is controlled by a control unit 526. Therefore, although the control unit 526 is omitted in Fig. 6, it is connected to each unit 521 to 523, 525, and 527. Like the control unit 310 of the mobile terminal 202 described above, each unit of the 5GC unit 214 is realized by, for example, a processing circuit configured to include a processor and 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. Fig. 7 is a flowchart showing an outline of the process from cell search to standby operation performed by a communication terminal (UE) in an NR communication system. When the communication terminal starts a cell search, in step ST601, it synchronizes slot timing and frame timing using a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS) transmitted from a surrounding base station.
[0094] P-SS and S-SS are collectively called a synchronization signal (SS). A synchronization code is assigned to the synchronization signal (SS) in one-to-one correspondence with a PCI (Physical Cell Identifier) assigned to each cell. 1008 different PCIs are being considered. A communication terminal synchronizes using these 1008 different PCIs and detects (identifies) the PCI of the synchronized cell.
[0095] In step ST602, the communication terminal receives the PBCH for the next synchronized cell. A master information block (MIB) including cell configuration information is mapped to the BCCH on the PBCH. Therefore, the MIB can be obtained by receiving the PBCH and obtaining the BCCH. Examples of MIB information include a system frame number (SFN), scheduling information for system information block (SIB) 1, subcarrier spacing for SIB1 and the like, and information on the DM-RS position.
[0096] Furthermore, the communication terminal acquires an SS block identifier from the PBCH. A part of the bit string of the SS block identifier is included in the MIB. The remaining bit string is included in an identifier used to generate a sequence of DM-RS associated with the PBCH. The communication terminal acquires the SS block identifier using the MIB included in the PBCH and the sequence of DM-RS associated with the PBCH.
[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, for example, the cell with the highest reception power, that is, the best cell, from among the one or more cells detected up to step ST603. The communication terminal also selects the beam with the best reception quality, for example, the beam with the highest reception power of the SS block, that is, the best beam. The reception power of the SS block for each SS block identifier is used, for example, to select the best beam.
[0099] Next, in step ST605, the communication terminal receives DL-SCH based on the scheduling information of SIB1 included in the MIB, and obtains SIB (System Information Block) 1 in the broadcast information BCCH. SIB1 includes information on access to the cell, cell configuration information, and scheduling information of other SIBs (SIBk: k is an integer greater than or equal to 2). SIB1 also includes a tracking area code (TAC).
[0100] Next, 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 a TAI list. The TAI is identification information for identifying a tracking area, and is composed of an MCC (Mobile Country Code), an MNC (Mobile Network Code), and a TAC (Tracking Area Code). The MCC is a country code. The MNC is a network code. The TAC is a tracking area code number.
[0101] If the comparison in step ST606 shows 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 the cell. If the comparison shows that the TAC received in step ST605 is not included in the tracking area list, the communication terminal requests a core network (EPC) including an MME and the like to change the tracking area through the cell in order to perform a Tracking Area Update (TAU).
[0102] An apparatus constituting a core network (hereinafter sometimes referred to as a "core network side apparatus") updates the tracking area list based on the identification number (UE-ID, etc.) of the communication terminal sent from the communication terminal together with a TAU request signal. The core network side apparatus transmits the updated tracking area list to the communication terminal. The communication terminal rewrites (updates) the TAC list held by the communication terminal based on the received tracking area list. Thereafter, the communication terminal enters standby mode in the cell.
[0103] Next, examples of random access methods in a communication system are shown. Four-step random access and two-step random access are used for random access. For each of the four-step and two-step random access methods, there is contention-based random access, i.e., random access in which timing collisions with other mobile terminals may occur, and contention-free random access.
[0104] An example of a collision-based four-step random access method is shown below. In the first step, the mobile terminal transmits a random access preamble to the base station. The random access preamble may be selected by the mobile terminal from a predetermined range, or may be individually assigned to the mobile terminal and notified by the base station.
[0105] In the second step, the base station transmits a random access response to the mobile terminal, which includes uplink scheduling information used in the third step, a terminal identifier used in the uplink transmission in the third step, and the like.
[0106] In the third step, the mobile terminal performs uplink transmission to the base station. The mobile terminal uses the information acquired in the second step for uplink transmission. In the fourth step, the base station notifies the mobile terminal whether or not the collision has been resolved. If the mobile terminal is notified that there is no collision, it ends the random access process. If the mobile terminal is notified that there is a collision, it starts the process over from the first step.
[0107] The contention-free four-step random access method differs from the contention-based four-step random access method in the following points: Prior to the first step, the base station pre-assigns a random access preamble and uplink scheduling to the mobile terminal, and the notification of whether or not contention has been resolved in the fourth step is not required.
[0108] An example of a collision-based two-step random access method is shown below. In the first step, the mobile terminal transmits a random access preamble and performs uplink transmission to the base station. In the second step, the base station notifies the mobile terminal whether there is a collision. If the mobile terminal is notified that there is no collision, it terminates the random access process. If the mobile terminal is notified that there is a collision, it restarts the process from the first step.
[0109] The contention-free two-step random access method differs from the contention-based two-step random access method in the following points: prior to the first step, the base station pre-assigns a random access preamble and uplink scheduling to the mobile terminal, and in the second step, the base station transmits a random access response to the mobile terminal.
[0110] FIG. 8 shows an example of a cell configuration in NR. In an NR cell, narrow beams are formed and transmitted in different directions. In the example shown in FIG. 8, at certain times, base station 750 transmits and receives signals to and from a mobile terminal using beam 751-1. At other times, base station 750 transmits and receives signals to and from a mobile terminal using beam 751-2. In a similar manner, base station 750 transmits and receives signals to and from a mobile terminal using one or more of beams 751-3 to 751-8. In this way, base station 750 forms a wide-area cell 752.
[0111] 8 shows an example in which the number of beams used by the base station 750 is 8, but the number of beams may be different from 8. Also, in the example shown in FIG. 8, the number of beams used simultaneously by the base station 750 is 1, but it may be multiple.
[0112] The concept of Quasi-CoLocation (QCL) is used to identify beams (see Non-Patent Document 14 (3GPP TS38.214)). That is, the beam is identified by information indicating which reference signal (e.g., SS block, CSI-RS) the beam can be considered to be the same as. The information may include types of information regarding the aspects of the beams that can be considered to be the same, such as Doppler shift, Doppler shift spread, mean delay, mean delay spread, and spatial Rx parameters (see Non-Patent Document 14 (3GPP TS38.214)).
[0113] In 3GPP, a side link (SL) is supported for D2D (Device to Device) communication and V2V (Vehicle to Vehicle) communication (see Non-Patent Document 1 and Non-Patent Document 16). The SL is defined by the PC5 interface.
[0114] In order to support unicast and groupcast in addition to broadcast in SL communication, support for PC5-S signaling is being considered (see Non-Patent Document 27 (3GPP TS23.287)). For example, PC5-S signaling is implemented to establish a link for implementing SL, i.e., PC5 communication. The link is implemented in the V2X layer and is also called a Layer 2 link.
[0115] Furthermore, support for RRC signaling in SL communication is being considered (see Non-Patent Document 27 (3GPP TS23.287)). RRC signaling in SL communication is also referred to as PC5 RRC signaling. For example, it has been proposed to notify UE capabilities between UEs performing PC5 communication, or to notify AS layer settings for performing V2X communication using PC5 communication.
[0116] An example of a connection configuration of mobile terminals in SL communication is shown in Fig. 9. In the example shown in Fig. 9, UE 805 and UE 806 exist within the coverage 803 of base station 801. UL / DL communication 807 is performed between base station 801 and UE 805. UL / DL communication 808 is performed between base station 801 and UE 806. SL communication 810 is performed between UE 805 and UE 806. UE 811 and UE 812 exist outside the coverage 803. SL communication 814 is performed between UE 805 and UE 811. In addition, SL communication 816 is performed between UE 811 and UE 812.
[0117] As an example of communication between a UE and a NW via a relay in SL communication, a UE 805 shown in FIG. 9 relays communication between a UE 811 and a base station 801.
[0118] A configuration similar to that shown in FIG. 4 may be used for a UE that performs relaying. The relaying process in the UE will be described using FIG. 4. The relaying process by UE 805 in communication from UE 811 to base station 801 will be described. A radio signal from UE 811 is received by antennas 307-1 to 307-4. The received signal is converted from a radio reception frequency to a baseband signal by frequency conversion unit 306, and demodulated by demodulation unit 308. Weight calculation and multiplication processing may also be performed by demodulation unit 308. The demodulated data is passed to decoder unit 309, where decoding processing such as error correction is performed. The decoded data is passed to protocol processing unit 301, where protocol processing such as MAC and RLC used for communication with UE 811 is performed, such as removing headers in each protocol. Protocol processing such as RLC and MAC used for communication with base station 801 is also performed, such as adding headers in each protocol. Protocol processing of PDCP and SDAP may be performed in protocol processing unit 301 of UE 811. The protocol-processed data is passed to encoder unit 304, where encoding such as error correction is performed. Some data may be output directly from protocol processing unit 301 to modulation unit 305 without being encoded. The data encoded by encoder unit 304 is modulated by modulation unit 305. Precoding in MIMO may be performed by modulation unit 305. The modulated data is converted into a baseband signal, and then output to frequency conversion unit 306, where it is converted into a radio transmission frequency. Thereafter, a transmission signal is transmitted to base station 801 from antennas 307-1 to 307-4.
[0119] In the above, an example of relaying by UE 805 in communication from UE 811 to base station 801 has been shown, but similar processing is also used in relaying communication from base station 801 to UE 811.
[0120] 5G base stations can support integrated access and backhaul (IAB) (see Non-Patent Documents 2 and 20). A base station supporting IAB (hereinafter sometimes referred to as an IAB base station) is composed of an IAB donor CU, which is a CU of the base station operating as an IAB donor that provides IAB functions, an IAB donor DU, which is a DU of the base station operating as an IAB donor, and an IAB node connected to the IAB donor DU and to a UE via a radio interface. An F1 interface is provided between the IAB node and the IAB donor CU (see Non-Patent Document 2).
[0121] An example of IAB base station connections is shown in Figure 10. IAB donor CU 901 is connected to IAB donor DU 902. IAB node 903 is connected to IAB donor DU 902 using a wireless interface. IAB node 903 is connected to IAB node 904 using a wireless interface. In other words, IAB nodes may be connected in cascade. UE 905 is connected to IAB node 904 using a wireless interface. UE 906 may be connected to IAB node 903 using a wireless interface, and UE 907 may be connected to IAB donor DU 902 using a wireless interface. Multiple IAB donor DUs 902 may be connected to an IAB donor CU 901, multiple IAB nodes 903 may be connected to an IAB donor DU 902, and multiple IAB nodes 904 may be connected to an IAB node 903.
[0122] A BAP (Backhaul Adaptation Protocol) layer is provided in the connection between the IAB donor DU and the IAB node and in the connection between the IAB nodes (see Non-Patent Document 29). The BAP layer performs operations such as routing received data to the IAB donor DU and / or the IAB node, and mapping to an RLC channel (see Non-Patent Document 29).
[0123] As an example of the configuration of the IAB donor CU, a configuration similar to that of CU 215 is used.
[0124] An example of the configuration of the IAB donor DU is the same as that of the DU 216. The protocol processing unit of the IAB donor DU performs BAP layer processing, such as adding a BAP header to downstream data, routing to an IAB node, and removing the BAP header from upstream data.
[0125] As an example of the configuration of an IAB node, a configuration excluding the EPC communication unit 401, other base station communication unit 402, and 5GC communication unit 412 shown in Figure 5 may be used.
[0126] The transmission and reception processing at the IAB node will be described using FIGS. 5 and 10 . The transmission and reception processing at the IAB node 903 in communication between the IAB donor CU 901 and the UE 905 will be described. In uplink communication from the UE 905 to the IAB donor CU 901, a radio signal from the IAB node 904 is received by the antenna 408 (some or all of the antennas 408-1 to 408-4). The received signal is converted from a radio reception frequency to a baseband signal by the frequency conversion unit 407, and demodulated by the demodulation unit 409. The demodulated data is passed to the decoder unit 410, where decoding processing such as error correction is performed. The decoded data is passed to the protocol processing unit 403, where protocol processing such as MAC and RLC used for communication with the IAB node 904 is performed, such as removing headers in each protocol. In addition, routing to the IAB donor DU 902 is performed using a BAP header, and protocol processing such as RLC and MAC used for communication with the IAB donor DU 902, such as adding headers for each protocol, is performed. The protocol-processed data is passed to the encoder unit 405, where it is subjected to encoding processing such as error correction. Some data may be output directly from the protocol processing unit 403 to the modulation unit 406 without being encoded. The encoded data is modulated by the modulation unit 406. The modulation unit 406 may also perform precoding in MIMO. The modulated data is converted into a baseband signal, and then output to the frequency conversion unit 407, where it is converted into a radio transmission frequency. Then, a transmission signal is transmitted to the IAB donor DU 902 from antennas 408-1 to 408-4. Similar processing is performed in downlink communication from the IAB donor CU 901 to the UE 905.
[0127] The IAB node 904 also performs the same transmission and reception processing as the IAB node 903. The protocol processing unit 403 of the IAB node 903 performs BAP layer processing, such as adding a BAP header and routing to the IAB node 904 in upstream communication, and removing the BAP header in downstream communication.
[0128] 3GPP is currently discussing the incorporation of ultra-low power IoT devices (hereinafter sometimes referred to as "devices") into mobile communication systems. It has been proposed that ultra-low power IoT devices communicate with UEs or gNBs using a communication method different from the communication method used for the air interface defined by conventional 3GPP (Non-Patent Documents 31, 33, 34). Therefore, a method is required for coexistence of communication over the air interface (Uu) between UEs and gNBs and communication over the air interface between devices and UEs or gNBs. Furthermore, 3GPP defines not only the air interface (Uu) between UEs and gNBs, but also the air interface (PC5) between UEs. Therefore, a method is also required for coexistence of communication over the air interface (PC5) between UEs and UEs and communication over the air interface between devices and UEs or gNBs.
[0129] When a device moves, the radio wave environment between the device and the UE changes, and a situation where communication between the device and the UE becomes impossible is conceivable. However, no recovery method from such a situation is disclosed. Therefore, a problem occurs in that communication between the device and the communication network cannot be continued after communication between the device and the UE becomes impossible.
[0130] This embodiment discloses a method for solving such a problem.
[0131] To solve the above problem, in this embodiment, the UE detects a communication interruption with the device (hereinafter, sometimes referred to as a device communication interruption).
[0132] The UE may detect a device communication interruption when it is unable to receive a signal from the device a predetermined number of times in succession, or when it is unable to receive a signal from the device for a predetermined period of time in succession. The signal from the device may be, for example, a search instruction response from the device, a data transmission from the device, or a signal related to alive monitoring from the device.
[0133] The predetermined number of times may be statically determined in advance by a standard, or may be determined by a base station or a core network device and notified to the UE. The information may be included in a communication configuration between the UE and the device. The information may be notified using RRC signaling, MAC signaling, L1 / L2 signaling, or signaling between the core network device and the UE, such as NAS signaling. The same may be true for the predetermined period.
[0134] The core network device may be an AMF, a UPF, or an SMF. The core network device may be an entity that plays a role of a host in communication with a device. A new entity related to communication with a device may be provided. The core network device may be a new entity. The same may be applied hereinafter to the core network device.
[0135] The UE may search for a device. The UE may transmit a search signal to the device. The device search by the UE may be triggered by an instruction from a base station or an instruction from a core network device. The base station and / or the core network device may instruct the UE to search for a device.
[0136] The UE may perform a device search when it is unable to receive a signal from a device a predetermined number of times in succession. As another example, the UE may perform a device search when it is unable to receive a signal from a device for a predetermined period of time. The UE may notify the base station and / or core network apparatus of the device search results. The notification may include information about the device, such as information about the presence or absence of the device, or information about the received power from the device. This allows the UE to quickly perform device search, for example.
[0137] The predetermined number of times for searching for a device may be statically determined in advance by a standard, or may be determined by a base station or a core network device and notified to the UE. The information may be included in a communication configuration between the UE and the device. The information may be notified using RRC signaling, MAC signaling, L1 / L2 signaling, or signaling between the core network device and the UE, such as NAS signaling. The same may be true for the predetermined period for searching for a device.
[0138] The predetermined number of times for searching for a device may be the same as or different from the predetermined number of times for detecting a device communication interruption. The same may also be true for the predetermined period for searching for a device.
[0139] The device may transmit a signal to the UE. The transmission of the signal from the device to the UE may be performed, for example, in response to a device search from the UE. As another example, the device may transmit the signal autonomously.
[0140] The UE may notify the base station and / or the core network device of information about the device search result. The notification may include information about the presence or absence of the searched device, identification information of the searched device, or information about the received power from the searched device.
[0141] The UE may search for devices at a predetermined interval. The interval may be predetermined by a standard, or may be instructed to the UE by a base station or a core network device.
[0142] The UE may transmit a signal to the device when no signal has been transmitted to the device for a predetermined period of time. The signal may be, for example, a device search signal or a signal for monitoring the device's status. The predetermined period of time may be predetermined by a standard, or may be instructed to the UE by a base station or a core network device.
[0143] The UE notifies the base station of information regarding the device communication interruption. As another example, the UE may notify the core network device of the information. For example, when the host in the device communication is the core network device, the UE may notify the core network device of the information.
[0144] The notification may include information about the device, for example, information about the device's identification. This allows, for example, a base station and / or a core network device to quickly identify a device that has lost communication with the UE. The notification may include information about the time when the device communication was lost, or information about the time elapsed since the device communication was lost. The notification may include information about the location of the UE when the device communication was lost, or information about the location of the device immediately before the device communication was lost. This allows, for example, a base station and / or a core network device to estimate the approximate location of the device.
[0145] For this notification, RRC signaling may be used, MAC signaling may be used, L1 / L2 signaling may be used, or signaling on the interface between the UE and the core network, for example, NAS signaling may be used.
[0146] The UE may search for the device. The UE may search for the device when a communication interruption of the device is triggered, or when the notification to the base station and / or the core network device is triggered. The UE may continue to search for the device even after the notification to the base station and / or the core network device.
[0147] The base station and / or core network device may instruct the UE to search for the device. This instruction may be sent to other UEs. For example, the base station and / or core network device may send this instruction to UEs surrounding the UE that detected the device communication outage. The surrounding UEs may be UEs under the same base station as the UE that detected the device communication outage, UEs in the same cell as the UE that detected the device communication outage, UEs that can communicate with the device, UEs that belong to the same group as the UE, or UEs that belong to a specific group. The instruction from the base station and / or core network device may be triggered by a notification of the device communication outage from the UE. The base station and / or core network device may send this instruction to multiple UEs.
[0148] The predetermined group may be statically determined in advance by a standard, or may be determined by a base station or a core network device and notified to the UE. Information about the predetermined group may be included in a communication configuration between the UE and a device. The information about the predetermined group may be notified using RRC signaling, MAC signaling, L1 / L2 signaling, or signaling between the core network device and the UE, such as NAS signaling.
[0149] The device search by the UE may be triggered by the instruction from the base station and / or the core network device. This may, for example, improve the efficiency of communication resource utilization. As another example, the UE may perform device search without the instruction. This may, for example, enable rapid device search.
[0150] The UE may notify the base station and / or the core network device of the device search result. The notification may include information about the device, such as information about the presence or absence of the device, or information about the received power from the device.
[0151] The base station and / or core network device may instruct the UE to stop searching for the device. For example, the instruction may be sent to the UE that instructed the device search. The UE may stop searching for the device in response to the instruction. This allows, for example, after a UE finds a device, other UEs to stop searching for the device, thereby improving resource usage efficiency in the communication system.
[0152] The instruction to stop device search may include information about the device, such as device identification information. The UE may stop searching for devices included in the instruction. The UE may continue searching for devices not included in the instruction. This allows, for example, flexible settings for device search.
[0153] The UE may retain data to be transmitted to the device. For example, the UE may retain the data when a device communication interruption occurs. The data may be data transmitted from a base station and / or a core network device. As another example, the base station may retain the data, or the core network device may retain the data. Retention of the data in the base station and / or the core network device may be triggered by notification of information related to the device communication interruption from the UE.
[0154] As another example, the UE may discard data to be transmitted to the device. For example, the UE may discard data upon detecting a loss of communication with the device, or upon the passage of a predetermined time since detecting a loss of communication with the device. This may, for example, reduce memory usage in the UE.
[0155] Data transmission and reception may continue between the UE and the device. For example, the UE may transmit data to the device or receive data from the device. The device may transmit data to the UE or receive data from the UE.
[0156] The operation of transmitting and receiving data between the UE and the device may continue for a predetermined period of time. The predetermined period of time may be statically determined in advance by a standard, or may be determined by a base station or a core network device and notified to the UE. The information may be included in a communication configuration between the UE and the device. The information may be notified using RRC signaling, MAC signaling, L1 / L2 signaling, or signaling between the core network device and the UE, such as NAS signaling.
[0157] As another example, the operation of transmitting and receiving data between the UE and the device may continue until the setting used by the UE for communication with the device (hereinafter sometimes referred to as the device setting) is released.
[0158] The UE may transmit data received from the device to the base station and / or core network device. The data may be, for example, data that does not fill a predetermined unit of information. The data that does not fill a predetermined unit of information may be, for example, a fragment of a packet or data that is being retransmitted.
[0159] As another example, the UE may discard data received from the device. For example, the UE may discard the data upon detecting a loss of communication with the device, or upon the passage of a predetermined time since detecting a loss of communication with the device. This may, for example, reduce memory usage in the UE.
[0160] The base station or the core network device may instruct the UE whether to discard data to be transmitted to the device. The UE may retain or discard the data to be transmitted to the device in response to the instruction. This allows, for example, improved flexibility in the communication system.
[0161] The base station or the core network device may instruct the UE whether to discard data received from the device. The UE may transmit the data received from the device to the base station and / or the core network device or discard the data, triggered by the instruction. This allows, for example, improved flexibility in the communication system.
[0162] The UE may notify the base station and / or the core network device of information about data already transmitted to the device. The base station and / or the core network device may use the information to keep track of data already transmitted to the device.
[0163] The UE may retain device configurations, which may allow, for example, quicker communication restoration with the device.
[0164] As another example, the UE may discard the device configuration. For example, the UE may discard the device configuration upon detecting a device communication interruption, or upon the passage of a predetermined time since the detection of the device communication interruption. This may, for example, reduce memory usage in the UE.
[0165] The base station or the core network device may instruct the UE whether to discard the device configuration. The UE may retain or discard the device configuration in response to the instruction. This allows, for example, improved flexibility in the communication system.
[0166] The UE may notify the base station and / or the core network device of the device configuration. The notification may be triggered by a device communication interruption in the UE. The base station and / or the core network device may use the device configuration included in the notification to determine the device configuration after recovery from the device communication interruption.
[0167] The device may detect a communication interruption with the UE (hereinafter, sometimes referred to as a UE communication interruption). The device may detect a UE communication interruption when it is unable to receive a signal from the UE a predetermined number of times in succession, or when it is unable to receive a signal from the UE for a predetermined period of time in succession. The signal from the UE may be, for example, a search instruction from the UE, a data transmission from the UE, or a signal related to alive monitoring from the UE. The predetermined number of times may be predetermined by a standard, or may be instructed to the device via the UE by the base station, or may be instructed to the device via the UE by the core network device. The same may be true for the predetermined period of time.
[0168] The device may transmit a signal to the UE when no signal has been transmitted to the UE for a predetermined period of time. The signal may be, for example, a signal for alive monitoring. The predetermined period of time may be predetermined by a standard, or the base station may instruct the device via the UE, or the core network device may instruct the device via the UE.
[0169] The return of communication between the device and the UE may be to the same UE as before the communication loss.
[0170] The UE may determine that communication with the device has been restored upon receiving a signal from the device, which may be a response to a search signal or a health check signal transmitted from the device.
[0171] The UE may notify the base station and / or the core network device of recovery from the device communication outage. For the notification, RRC signaling, MAC signaling, L1 / L2 signaling, or signaling in the interface between the UE and the core network, such as NAS signaling, may be used. For the notification, the same signaling as that used for notifying information about the device communication outage may be used.
[0172] The UE may transmit the stored data upon recovery from the device communication interruption. For example, the UE may transmit data received from the base station to the device upon the recovery. In the communication between the UE and the device, for example, the device configuration stored in the UE may be used.
[0173] 11 and 12 are sequence diagrams showing an example of communication disconnection and recovery operation between a UE and a device. Fig. 11 shows the first half of the sequence, and Fig. 12 shows the second half of the sequence. In the examples shown in Fig. 11 and 12, an example is shown in which a device communicating with UE #1 is disconnected from UE communication, and then communication with the same UE #1 is restored. In the examples of Fig. 11 and 12, a case is shown in which the host in communication with the device is an AMF.
[0174] In step ST1105 shown in FIG. 11 , settings for communication between UE #1 and a device are made between the base station and UE #1. In step ST1105, the base station notifies UE #1 of a device connection setting. The setting may include information regarding device identification. The notification may be made using RRC signaling, for example, RRC reconfiguration, or may be made using MAC signaling, or may be made using L1 / L2 signaling. UE #1 transmits a response to the device connection setting to the base station. The response may be made using RRC signaling, for example, RRC reconfiguration complete, or may be made using MAC signaling, or may be made using L1 / L2 signaling.
[0175] In step ST1110, settings for communication between UE#2 and the device are made between the base station and UE#2. In step ST1110, the same processing as in step ST1105 is performed between the base station and UE#2.
[0176] In step ST1112 shown in Figure 11, the AMF requests UE #1 to transmit data from the device. In the following description, data transmitted by the device may be referred to as device data. In step ST1113, UE #1 instructs the device to start transmitting device data.
[0177] In step ST1115 and step ST1116 shown in Figure 11, data is transmitted from the device to the AMF via UE #1. Step ST1115 shows data transmission from the device to UE #1, and step ST1116 shows data transmission from UE #1 to the AMF.
[0178] In step ST1118 and step ST1119 shown in Figure 11, data is transmitted from the AMF to the device via UE #1. Step ST1118 shows data transmission from the AMF to UE #1, and step ST1119 shows data transmission from UE #1 to the device.
[0179] In step ST1122 shown in Fig. 11, data is transmitted from the AMF to the UE #1. In step ST1123, the data of step ST1122 is transmitted from the UE #1 to the device, but the device cannot receive the data.
[0180] In step ST1125 shown in FIG. 11, data is transmitted from the device to UE#1, but UE#1 cannot receive the data.
[0181] Steps ST1127 and ST1128 shown in Fig. 11 are the same as steps ST1122 and ST1123. As in step ST1123, the device cannot receive the data in step ST1128.
[0182] In step ST1129 shown in FIG. 11, similarly to step ST1125, data is transmitted from UE#1 to the device, but the device cannot receive the data.
[0183] 11, the device detects a communication interruption with UE #1. The detection may be triggered by the device being unable to receive the data transmitted from UE #1 in step ST1128.
[0184] 11, UE#1 detects a disconnection of device communication. This detection may be triggered by UE#1 being unable to receive transmission data from the device in step ST1129.
[0185] 11, UE #1 holds data to be transmitted to the device. The data held by UE #1 may be data received from the AMF in steps ST1122 and ST1127.
[0186] In step ST1136 shown in Fig. 11 , UE #1 notifies the AMF of information related to the device. The notification may include information related to the device communication interruption, information related to the device identification, or information related to the settings used for communication with the device. The notification may include the data held in step ST1134. For example, NAS signaling may be used for the notification. The AMF recognizes the device communication interruption of UE #1 upon receiving the notification in step ST1136.
[0187] In step ST1138 shown in Figure 11, the AMF notifies the base station of information related to the device. The notification may include information related to device communication disconnection, information related to device identification, information related to the UE for which device communication has been disconnected (e.g., information related to UE identification), or information related to settings used for communication with the device. The base station grasps the device communication disconnection of UE #1 based on the notification in step ST1138.
[0188] In step ST1140 shown in FIG. 12 , the base station requests the AMF to search for devices. The request may include information about the device, information about device communication disconnection, or information about the UE for which device communication has been disconnected. In step ST1142, the AMF instructs UE #2 to search for devices. The instruction may include information about the device, or may not include information about the device. The instruction may specify a device to be searched for. For example, when device information is included in step ST1142, the instruction may specify a device to be searched for. As another example, the instruction may not specify a device to be searched for. For example, when device information is not included in step ST1142, the instruction may not specify a device to be searched for.
[0189] In step ST1144 shown in FIG. 12 , UE #2 performs device search. The search may be triggered by a device search instruction from the AMF. In step ST1146, the device transmits a response to UE #2. The response may include information regarding the identification of its own device. When transmitting step ST1146 from the device to UE #2, UE #2 may be emitting radio waves to the device. The device may transmit step ST1146 using radio waves from UE #2. UE #2 acquires device information using step ST1146. UE #2 measures the received power in step ST1146.
[0190] In step ST1148 shown in Fig. 12, UE #2 notifies the AMF of information about the discovered device. The notification may include information about device identification, information about power measurement results, or information about a reception error rate. For example, NAS signaling may be used for transmitting step ST1148.
[0191] Step ST1148 may include only information about the device that is the target of the search instruction, or may include information indicating whether the device has been found. This makes it possible to reduce, for example, the amount of signaling from UE #2 to the AMF. As another example, step ST1148 may include information about some or all of the devices that UE #2 has searched for and found. This makes it possible, for example, for the AMF to quickly perform a connection initiation process with devices other than the device that is the target of the search instruction.
[0192] In step ST1152 shown in FIG. 12, UE #1 performs device search. The search may be performed by UE #1 on its own initiative, or may be performed in response to a device search instruction from the AMF. In the example shown in FIG. 12, UE #1 performs the search on its own initiative. In step ST1154, the device transmits a response to UE #1. The response may include information regarding the identification of its own device. When transmitting step ST1154 from the device to UE #1, UE #1 may be emitting radio waves to the device. The device may transmit step ST1154 using radio waves from UE #1. UE #1 acquires device information using step ST1154. UE #1 measures the received power in step ST1154.
[0193] In step ST1156 shown in Fig. 12, UE #1 notifies the AMF of information about the discovered device. The notification may include information about device identification, information about power measurement results, or information about a reception error rate. For example, NAS signaling may be used for the transmission of step ST1148.
[0194] In step ST1160 shown in Figure 12, the AMF notifies the base station of information related to the discovered device. The notification may include the information notified in step ST1148 or the information notified in step ST1156. In step ST1162, the base station determines the UE to which the device is to be connected. In the example shown in Figure 12, the base station determines UE #1 as the UE to which the device is to be connected.
[0195] In steps ST1164 and ST1165 shown in FIG. 12 , the same processing as in step ST1105 is performed. In step ST1164, the base station notifies UE #1 of device connection setup. The setup may include information related to device identification. The notification may be performed using RRC signaling, for example, RRC reconfiguration, MAC signaling, or L1 / L2 signaling. In step ST1165, UE #1 transmits a response to the device connection setup to the base station. The response may be performed using RRC signaling, for example, RRC reconfiguration completion, MAC signaling, or L1 / L2 signaling.
[0196] In step ST1166 shown in Figure 11, the base station notifies the AMF of the determination of the UE to which the device is connected. The notification may include information regarding the identification of the device or information regarding the determined UE. In step ST1167, the AMF responds to step ST1166 to the base station.
[0197] In steps ST1168 and ST1169 shown in FIG. 12, the same processing as in steps ST1112 and ST1113 is performed.
[0198] 12, the same processes as those in steps ST1115 and ST1116 are performed. In steps ST1178 and ST1179, the same processes as those in steps ST1118 and ST1119 are performed.
[0199] 11 and 12, the AMF may instruct UE #1 and / or UE #2 to stop device search. The instruction to stop may be performed, for example, after step ST1148, after step ST1156, after step ST1160, after step ST1166, or after step ST1167. This makes it possible to improve the utilization efficiency of the communication system, for example.
[0200] The return of communication between the device and the UE may be to a different UE than before the communication loss.
[0201] 13 and 14 are sequence diagrams showing another example of communication disconnection and recovery operation between a UE and a device. FIG. 13 shows the first half of the sequence, and FIG. 14 shows the second half of the sequence. In the examples shown in FIGS. 13 and 14, an example is shown in which a device communicating with UE #1 is disconnected from the UE, and then communication with UE #2 is restored. In the examples of FIGS. 13 and 14, a case is shown in which the host in communication with the device is an AMF. In FIGS. 13 and 14, the same step numbers are assigned to processes similar to those in FIGS. 11 and 12, and common explanations are omitted.
[0202] Steps ST1105 to ST1148 shown in FIGS. 13 and 14 are the same as those in FIGS.
[0203] In step ST1252 shown in Fig. 14, UE #1 performs device discovery. This discovery may be performed in the same manner as in step ST1152 shown in Fig. 12. In the example shown in Fig. 14, the device fails to receive the device discovery in step ST1252, and as a result, UE #1 fails to receive a response from the device.
[0204] Steps ST1156 to ST1162 shown in Fig. 14 are the same as those in Fig. 12. In the example shown in Fig. 14, information indicating that UE #1 was unable to receive a response from the device may be included in the notification of step ST1156. In the example shown in Fig. 14, the base station determines UE #2 as the UE to which the device is to be connected in step ST1162.
[0205] In step ST1264 shown in FIG. 14 , the base station instructs UE #1 to release the device configuration. The instruction may include information regarding device identification. The instruction may be performed using RRC signaling, for example, RRC reconfiguration, MAC signaling, or L1 / L2 signaling. In step ST1265, UE #1 releases the device configuration. In step ST1266, UE #1 discards the data it has retained. The data discarded by UE #1 may be, for example, data received from the AMF in steps ST1122 and ST1127. In step ST1267, UE #1 notifies the base station of the completion of the device configuration release. The notification may be performed using RRC signaling, for example, RRC reconfiguration completion, MAC signaling, or L1 / L2 signaling.
[0206] In step ST1270 shown in Figure 14, the base station notifies the AMF of the determination of the UE to which the device is connected. The information may include information regarding the identification of the device, or information regarding the UE determined to be the connection destination. The AMF, triggered by the notification, recognizes that the UE connected to the device has been switched to UE #2.
[0207] Step ST1167 shown in FIG. 14 is the same as that in FIG.
[0208] In steps ST1272 and ST1273 shown in FIG. 14, the same processing as in steps ST1112 and ST1113 is performed via UE#2.
[0209] In steps ST1275 and ST1276 shown in Fig. 14, the same processes as in steps ST1115 and ST1116 are performed via UE #2. In steps ST1278 and ST1279, the same processes as in steps ST1118 and ST1119 are performed via UE #2.
[0210] A device search instruction to a UE may be issued in advance by broadcast information, for example, system information. System information related to device search for a UE may be newly provided. The information may include information on the time and / or frequency resources used for device search, information on the power used for device search, or information on devices to be searched. The information may include information on the cycle at which device search is performed, information on the timing to start device search, or information on the period during which device search is performed. A UE that receives the system information may perform device search. The UE may be an RRC_CONNECTED UE, an RRC_INACTIVE UE, or an RRC_IDLE UE. This may, for example, reduce the amount of signaling related to a device search instruction.
[0211] The UE may notify the base station and / or core network device of the device discovery result. The UE may be, for example, a UE that performed device discovery in response to an instruction in the system information. The UE may be, for example, a UE that found one or more devices. The UE may be an RRC_CONNECTED UE, an RRC_INACTIVE UE, or an RRC_IDLE UE. Small Data Transmission (SDT) (see Non-Patent Document 2) may be used for the notification. This allows, for example, the base station and / or core network device to obtain device-related information from many UEs.
[0212] Another solution will be disclosed. The UE may notify nearby UEs of information regarding the device communication interruption. For example, the PC5 may be used for the notification. The nearby UE may search for the device in response to the notification.
[0213] The notification from the UE to the neighboring UE may be performed when the UE is outside the coverage area of the base station, or may be performed when the UE is within the coverage area.
[0214] According to the first embodiment, even if a device communication interruption occurs, it is possible to restore communication between the device and the UE, and as a result, it is possible to restore the connection of the device to the communication system.
[0215] Embodiment 2. As the UE to which a device is connected moves, the radio wave environment between the UE and the base station may change, making communication between the UE and the base station impossible. However, no method for recovering from such a situation is disclosed regarding device communication. Therefore, a problem arises in that communication between the device and the communication network cannot be continued after communication between the UE and the base station becomes impossible.
[0216] This embodiment discloses a method for solving such a problem.
[0217] The UE stops communication with the device, which may occur, for example, when a Radio Link Failure (RLF) occurs.
[0218] The UE may retain data received from the device, for example, in response to RLF detection.
[0219] As another example, the UE may discard data received from the device. For example, the UE may discard data when an RLF is detected, or when a predetermined time has elapsed since the RLF was detected. This may reduce, for example, the memory usage of the UE.
[0220] The UE may transmit data received from the base station and / or the core network device to the device. The data may be, for example, data that does not fill a predetermined unit of information. The data that does not fill a predetermined unit of information may be, for example, a fragment of a packet or data that is being retransmitted.
[0221] As another example, the UE may discard data received from the base station and / or the core network device. For example, the UE may discard the data when an RLF is detected, or when a predetermined time has elapsed since the RLF detection. This may reduce, for example, the memory usage of the UE.
[0222] The base station or the core network device may instruct the UE whether to discard data to be transmitted to the base station and / or the core network device. The base station and / or the core network device may instruct the UE in advance. The UE may retain or discard the data to be transmitted to the device in response to the instruction. This, for example, enables improved flexibility in the communication system.
[0223] The base station or the core network device may instruct the UE whether to discard data to be transmitted to the device. The base station and / or the core network device may instruct the UE in advance. The UE may transmit or discard the data it holds to the device in response to the instruction. This, for example, enables improved flexibility in the communication system.
[0224] The UE may discard the device configuration. For example, the UE may discard the device configuration when an RLF is detected, or when a predetermined time has elapsed since the RLF was detected. This may reduce, for example, the memory usage of the UE.
[0225] As another example, the UE may retain the device configuration, for example, even after detecting an RLF.
[0226] The base station or the core network device may instruct the UE whether to release the device setting. The base station and / or the core network device may instruct the UE in advance. The UE may retain or discard the device setting in response to the instruction. This, for example, enables improved flexibility in the communication system.
[0227] The above-described operation may be triggered by the CM-IDLE state transition of the UE. For example, when the host in communication with the device is a core network device, the above-described operation may be triggered by the CM-IDLE state transition.
[0228] Figure 15 is a sequence diagram showing an example of an RLF and its recovery operation in a UE connected to a device. The example of Figure 15 shows a case where communication with the device is not performed during an RLF. The example of Figure 15 shows a case where the host in communication with the device is an AMF. In Figure 15, the same step numbers are assigned to processes similar to those in Figures 11 and 12, and common descriptions will be omitted.
[0229] Steps ST1105 to ST1119 shown in FIG. 15 are the same as those in FIG.
[0230] 15, the device transmits data to UE #1. In step ST1326, UE #1 attempts to transmit data to the AMF via the base station, but the base station cannot receive step ST1326. In step ST1328, UE #1 holds the data received in step ST1325.
[0231] In step ST1330 shown in Fig. 15, the base station transmits an SS block to UE #1, but UE #1 cannot receive the SS block. In step ST1332, UE #1 detects an RLF. Step ST1332 may be performed when UE #1 cannot detect the SS block.
[0232] 15 , UE #1 releases the device configuration. In step ST1336, UE #1 discards the data it has stored. The data to be discarded by UE #1 may be, for example, the data received in step ST1325.
[0233] 15, the base station transmits an SS block to UE #1, and UE #1 receives the SS block. In step ST1350, a random access process is performed between UE #1 and the base station, and a connection between the base station and UE #1 is re-established.
[0234] Steps ST1164 to ST1179 shown in FIG. 15 are the same as those in FIG.
[0235] A timer related to device settings may be provided. The timer may be included in the UE. The timer may be provided for each device or may be common to all devices.
[0236] The timer may be started when the UE detects an RLF. The timer may be stopped when the UE re-establishes a connection with the base station, or when a random access procedure between the UE and the base station is completed. As another example, the timer may be stopped when a device configuration release instruction is received from the base station. The UE may discard the device configuration when the timer expires.
[0237] As another example, the timer may be started when the UE transitions to CM-IDLE. The timer may be stopped when the UE transitions to CM-CONNECTED. As another example, the timer may be stopped when a device configuration release instruction is received from the base station. The UE may discard the device configuration when the timer expires.
[0238] A timer related to device data may be provided. The timer may be included in the UE. The timer may be provided for each device or may be common to all devices. The start and stop conditions and expiration operation of the timer related to device data may be the same as those of the timer related to device settings.
[0239] The timer for device settings and the timer for device data may be integrated. For example, the UE may discard the device settings and the stored data upon expiration of the integrated timer. This may, for example, reduce complexity in the communication system.
[0240] Fig. 16 is a sequence diagram showing another example of the operation of RLF and its recovery in a UE connected to a device. The example of Fig. 16 shows a case where communication with the device continues even after RLF. The example of Fig. 16 shows a case where the host in communication with the device is an AMF. In Fig. 16, the same step numbers are assigned to processes similar to those in Figs. 11, 12, and 15, and common descriptions will be omitted.
[0241] Steps ST1105 to ST1119 shown in FIG. 16 are the same as those in FIG.
[0242] Steps ST1325 to ST1332 shown in Fig. 16 are the same as those in Fig. 15. UE #1 starts the device setting timer / device data timer in step ST1332. In the example shown in Fig. 16, the start time of the timer is indicated by dotted line 1433, and the expiration time is indicated by dotted line 1437.
[0243] Steps ST1345 to ST1350 shown in Fig. 16 are the same as those in Fig. 15. Upon completion of step ST1350, UE#1 stops the device setting timer / device data timer.
[0244] Steps ST1164 and ST1165 shown in FIG. 16 are the same as those in FIG.
[0245] 16 , UE#1 transmits the device data it has held to the AMF. The data to be transmitted in Step ST1466 may be, for example, the data received in Step ST1325.
[0246] Steps ST1168 to ST1179 shown in FIG. 16 are the same as those in FIG.
[0247] A device connected to a UE that has detected an RLF may connect to another UE. The base station may detect a disconnection between the UE and the device. The base station may instruct the other UE to search for devices upon detecting the disconnection. The other UE may perform a device search upon receiving the instruction. The other UE may notify the base station of information related to the device search results. The base station may use the notification to determine a UE to which the device should be connected.
[0248] As another example, the base station may notify the core network device of information regarding the disconnection with the UE. The core network device may use the notification as an opportunity to instruct other UEs to search for devices. This operation may be performed, for example, when the device's host is the core network device. The other UEs may use the instruction as an opportunity to search for devices. The other UEs may notify the core network device of information regarding the device search results. The core network device may notify the base station of the information. The base station may use the notification to determine the UE to which the device should be connected.
[0249] A core network device, for example, an AMF, may detect a disconnection with the UE. The core network device may perform the detection, for example, when the UE transitions to CM-IDLE. The core network device, for example, an AMF, may notify the base station of the disconnection with the UE.
[0250] As another example, the core network device may use the detection as a trigger to instruct other UEs to search for the device. This operation may be performed, for example, when the host of the device is the core network device. The other UEs may use the instruction as a trigger to search for the device. The other UEs may notify the core network device of information regarding the device search results. The core network device may notify the base station of the information. The base station may use the notification to determine the UE to which the device should be connected.
[0251] 17 and 18 are sequence diagrams showing another example of the operation of RLF and its recovery in a UE connected to a device. FIG. 17 shows the first half of the sequence, and FIG. 18 shows the second half of the sequence. The examples of FIGS. 17 and 18 show a case where, after RLF is detected in UE #1 to which the device is connected, the UE to which the device is connected is switched to UE #2. The examples of FIGS. 17 and 18 show a case where the host in communication with the device is an AMF. In FIGS. 17 and 18, the same step numbers are assigned to processes similar to those in FIGS. 11 to 16, and common explanations will be omitted.
[0252] Steps ST1105 to ST1119 shown in FIG. 17 are the same as those in FIG.
[0253] Steps ST1325 to ST1332 shown in Fig. 17 are the same as those in Fig. 15. UE #1 starts the device setting timer / device data timer in step ST1332. In the examples shown in Fig. 17 and Fig. 18, the start time of the timer is indicated by dotted line 1433, and the expiration time is indicated by dotted line 1437.
[0254] 17, the AMF detects a CM-IDLE transition of the CM state for UE #1. The AMF performs step ST1142 in response to step ST1540.
[0255] Steps ST1142 to ST1162 shown in Figures 17 and 18 are the same as those in Figure 11. In the example shown in Figures 17 and 18, UE#2 is determined as the UE to which the device is to be connected in step ST1162.
[0256] 18, UE#1 performs steps ST1265 and ST1266 upon the arrival of expiration time 1437 of the device setting timer / device data timer. The processes of steps ST1265 and ST1266 in FIG. 18 are the same as those in FIG.
[0257] Steps ST1268 to ST1270 shown in FIG. 18 are the same as those in FIG.
[0258] Step ST1167 shown in FIG. 18 is the same as that in FIG.
[0259] Steps ST1272 to ST1279 shown in FIG. 18 are the same as those in FIG.
[0260] 17 and 18 show an example in which the AMF issues the device search instruction shown in step ST1142 to UE #2, but the AMF may also issue the device search instruction shown in step ST1142 to UE #1. This enables UE #1 to perform device search when UE #1 recovers from RLF, for example, and as a result, communication between the device and the communication network can be quickly restored.
[0261] The UE connected to the device may connect to another base station, for example, the UE that has become RLF may connect to another base station.
[0262] The UE may stop communication with the device, discard data received from the device, discard data received from the base station and / or the core network device, and / or release device settings using an RRC release (RRCRelease). This may reduce memory usage in the UE after the RRC release, for example.
[0263] According to the second embodiment, even if an RLF occurs, it is possible to restore communication between the device and the UE, and as a result, it is possible to restore the connection of the device to the communication system.
[0264] Embodiment 3. Among services using communication networks, there are some services that require extremely high reliability, such as communication between sensors used for remote control of robots (see Non-Patent Document 35 (3GPP TS22.261) Section 7.11). When using devices for such services, ensuring reliability becomes an issue.
[0265] This embodiment discloses a method for solving such a problem.
[0266] To solve the above problem, in this embodiment, a connection between a device and a communication network is made via a plurality of UEs. The device may be connected to a plurality of UEs. For example, the device may be connected to a plurality of UEs in parallel.
[0267] The connection between the device and the communication network may be via multiple base stations, the device may connect to multiple base stations, the device may for example connect to multiple base stations in parallel.
[0268] The connection between the device and the communication network may be via multiple UEs and multiple base stations. The device may connect to multiple UEs and multiple base stations. The device may, for example, connect to multiple UEs and / or multiple base stations in parallel.
[0269] Device configuration may be performed for each UE connected to the device. The configuration may be performed by a base station or a core network device. The configuration may include information indicating that the connection is made with multiple UEs.
[0270] The UE may measure the received power of a signal from the device. The UE may transmit information about the measurement results of the received power from the device to the base station. The base station may, for example, use the information transmitted from the UE to determine which UE to use to connect to the device.
[0271] The notification of information on the power received from the device from the UE to the base station may be triggered by an instruction from the base station, may be performed periodically, or may be triggered by a predetermined condition (event) being satisfied and / or the condition (event) no longer being satisfied. The base station may notify the UE of information on the predetermined condition. The information may be included in the communication setting between the UE and the device (e.g., step ST1105 in FIG. 11 ).
[0272] Notification of the information is triggered by the satisfaction of the condition (event), which allows, for example, the base station to quickly determine whether to start communication with the device using multiple routes. Notification of the information is triggered by the non-satisfaction of the condition (event), which allows, for example, the base station to quickly determine whether to end communication with the device using multiple routes.
[0273] As examples of the predetermined conditions, the following (a1) to (a10) are disclosed.
[0274] (a1) The received power from the device is less than or equal to a predetermined threshold.
[0275] (a2) The path loss between the device and the UE is greater than or equal to a predetermined threshold.
[0276] (a3) The power used for transmission with the device is greater than or equal to a predetermined threshold.
[0277] (a4) The SINR (Signal to Interference plus Noise Ratio) of the received signal from the device is less than or equal to a threshold value.
[0278] (a5) The reception error rate of the received signal from the device is greater than or equal to a threshold value.
[0279] (a6) The ratio of the power transmitted to the device to the power received from the device (transmitted power / received power) is greater than or equal to a threshold value.
[0280] (a7) The ratio of the power received from the device to the power transmitted to the device (received power / transmitted power) is less than or equal to a threshold value.
[0281] (a8) The received power at the UE of a signal transmitted by a device using radio waves from other UEs and / or base stations as a power source is greater than or equal to the received power at the UE of a signal transmitted by a device using radio waves from the UE as a power source.
[0282] (a9) The distance between the UE and the device is greater than or equal to a threshold.
[0283] (a10) A combination of the above (a1) to (a9).
[0284] The above (a1) enables the base station to quickly detect a decrease in the received power from the device at the UE, and as a result, it becomes possible to continue communication between the device and the communication network.
[0285] The above (a2) enables the base station to quickly grasp an increase in path loss from the device at the UE, thereby enabling communication between the device and the communication network to continue and reducing interference with other UEs, etc. by preventing an excessive increase in the UE's transmission power.
[0286] The above (a3) enables the base station to prevent an excessive increase in the transmission power of the UE, thereby reducing interference with other UEs, etc.
[0287] The above (a4) allows the base station to quickly detect an increase in interference around the UE, thereby allowing communication between the device and the communication network to continue.
[0288] The above (a5) allows the base station to set the condition without depending on the reception performance and / or demodulation performance of the UE, thereby making it possible to avoid the complexity involved in setting the condition.
[0289] Regarding the above (a6), the UE may determine whether the predetermined condition is satisfied by using information measured by the UE itself. This, for example, eliminates the need for feedback from the device to the UE, and as a result, it is possible to reduce the amount of signaling between the device and the UE.
[0290] By using the above (a7), it is possible to keep the value of the ratio that the UE needs to calculate small, which in turn makes it possible to prevent overflow in the calculation and therefore prevents malfunctions in the UE.
[0291] The above (a8) enables the base station to recognize the existence of a UE or base station that is more suitable than the UE to which the device is to be connected, thereby ensuring the quality of communication between the device and the communication network.
[0292] The above (a9) allows the base station to quickly determine that the distance between the UE and the device has increased and is therefore unsuitable for communication, thereby enabling communication between the device and the communication network to continue.
[0293] An offset may be provided to the threshold value related to the above-mentioned condition. For example, the UE may determine whether the condition is satisfied based on a value obtained by adding the offset to the above-mentioned threshold, or may determine whether the condition is satisfied based on a value obtained by subtracting the offset from the above-mentioned threshold, or may compare a value obtained by adding the offset to a result measured or derived by the UE with a threshold, or may compare a value obtained by subtracting the offset from a result measured or derived by the UE with a threshold. This allows, for example, the base station to flexibly set the condition.
[0294] A plurality of the aforementioned offsets may be provided. For example, the UE may compare a value obtained by adding a first offset to a result measured or derived by the UE with a value obtained by subtracting a second offset from a threshold, or may compare a value obtained by subtracting the first offset from a result measured or derived by the UE with a value obtained by adding a second offset to a threshold, or may compare a value obtained by adding the first offset to a result measured or derived by the UE with a value obtained by adding a second offset to a threshold, or may compare a value obtained by subtracting the first offset from a result measured or derived by the UE with a value obtained by subtracting the second offset from a threshold. This allows the base station to set the conditions more flexibly, for example.
[0295] As another example of the offset, the offset used to determine whether the condition is satisfied and the offset used to determine whether the condition is no longer satisfied may be different from each other. For example, hysteresis may be provided for the condition. This makes it possible to prevent excessive notification of the information from the UE to the base station due to frequent occurrences of the condition being satisfied and not being satisfied.
[0296] The value of the one or more offsets may be determined by a standard, or may be determined by the base station and broadcasted or notified to the UE. For example, the base station may notify information about the offsets by including it in the information about the condition. This may reduce the amount of signaling between the base station and the UE. As another example, the base station may notify information about the offsets using signaling different from that used to notify information about the condition. This may allow the base station to flexibly set the condition.
[0297] The base station may notify the UE of information about the offset using RRC signaling. This allows, for example, the base station to notify the UE of more information. As another example, the base station may notify the information using MAC signaling. This allows, for example, the base station to notify the UE of the information quickly. As another example, the base station may notify the information using L1 / L2 signaling. This allows, for example, the base station to notify the UE of the information even more quickly.
[0298] The same data may be transmitted and received between the device and each UE. The device may transmit the same data to multiple UEs. The multiple UEs may each transmit the same data to the base station and / or core network device. The base station and / or core network device may transmit the same data to multiple UEs. The multiple UEs may each transmit the same data to the device.
[0299] In the above, the following problem occurs: the device cannot determine whether the data received from each UE is the same data. For example, if the data instructs a device associated with the device to perform some operation, the device may perform the same operation multiple times, resulting in a malfunction.
[0300] A method for solving the above problem is disclosed, which involves adding information about the device's identity to data transmitted between the device and the communication network, and possibly to signaling transmitted between the device and the communication network.
[0301] The device may remove any duplicated data received, for example, the device may only keep the data received initially and discard data received from other UEs.
[0302] The base station and / or core network device may delete duplicated data. For example, the base station and / or core network device may retain only the data first received from a certain UE and discard data received from other UEs.
[0303] The identification information may be, for example, a sequence number. The information may be assigned at a layer terminating between the device and the base station and / or core network device. The layer may be, for example, a TCP layer, a UDP layer, an IP layer, or an application layer. The information may be assigned to the data itself or to a header of the data. The information may be uniquely assigned between data transmitted and received between the device and the communication network, between signaling transmitted and received between the device and the communication network, or through the data and signaling transmitted and received between the device and the communication network. The information may be uniquely assigned between data and / or signaling transmitted from the device to the communication network and data and / or signaling transmitted from the communication network to the device, respectively, or may be uniquely assigned throughout.
[0304] The device may use the information to discard duplicate data. For example, the device may discard data to which the same information is assigned. Discarding of duplicate data in the base station and / or core network device may also be performed in a similar manner.
[0305] Device configuration performed by a base station and / or a core network device on a UE may include information regarding duplication. The information regarding duplication may include, for example, information instructing the start of duplication, information regarding the UE through which the duplicated data passes, or information regarding the identification of communication using multiple routes. The device may use the information to start a duplication detection operation for data received from the communication network or delete duplicately received data. The device may use the information to start duplication of data to be transmitted to the communication network. The device may use the information to transmit data to multiple UEs. For example, the device may start duplication of data to be transmitted or may start duplication detection operation for received data when information regarding the identification of communication using multiple routes received from multiple UEs matches. This allows the device to quickly determine the start of data duplication, for example.
[0306] Duplication may be performed for both downstream communication (communication from the communication network to the device) and upstream communication (communication from the device to the communication network), which may improve flexibility in the communication system, for example.
[0307] The device configuration performed by the base station and / or the core network device for the UE may include information about duplication of downlink communication. The information may include information instructing deletion of duplicated received data, or information about identifying communication using multiple routes.
[0308] The device configuration performed by the base station and / or the core network device for the UE may include information about duplication of uplink communication. The information may include information instructing duplication of data, information instructing transmission to multiple UEs, information about the destination UE, or information about identifying communication using multiple routes.
[0309] Other examples of the information regarding duplication may include information instructing the device to stop duplication, information regarding a UE to which data is to be transmitted after duplication is stopped, or information regarding the identification of a communication for which duplication is to be stopped. The device may use the information to stop deleting data received from multiple UEs. The device may also use the information to stop duplication of data. This allows the device to quickly determine when duplication of data has been stopped, for example.
[0310] The duplication may be stopped for both downstream and upstream communications, which may improve the flexibility of the communication system.
[0311] The device configuration performed by the base station and / or the core network device for the UE may include information instructing the UE to stop duplication of downlink communication. The information may include information instructing the UE to stop deleting duplicated received data, or information regarding identification of communication using multiple routes.
[0312] The device configuration performed by the base station and / or the core network device for the UE may include information regarding the stop of duplication of uplink communication. The information may include information instructing the UE to stop duplication of data, information instructing the UE to stop transmission to multiple UEs, information regarding the UE to which the data is to be transmitted after duplication is stopped, or information regarding the identification of communication using multiple routes.
[0313] Another example of the identification information may be a timestamp. The timestamp may be provided by a base station and / or a core network device. The device may keep one piece of data with the same timestamp and delete the other.
[0314] The timestamp may be assigned by the device. The device may transmit data with the same timestamp assigned to multiple UEs. The base station and / or core network device may keep one piece of data with the same timestamp and delete the others. This, for example, makes it unnecessary for the device to manage the sequence numbers described above, thereby avoiding complexity in the communication system.
[0315] The decision to use multiple UEs may be made by the base station, for example using received power measurements from the UEs.
[0316] 19 and 20 are sequence diagrams showing an example of communication between a device and a communication network using multiple UEs. FIG. 19 shows the first half of the sequence, and FIG. 20 shows the second half of the sequence. In the example shown in FIGS. 19 and 20, the device communicates using UE #1 and UE #2, and then communicates using only UE #1. In the example shown in FIGS. 19 and 20, the base station determines whether communication is performed using multiple routes. In FIGS. 19 and 20, the same step numbers are used for processes similar to those in FIGS. 11 and 12, and common descriptions will be omitted.
[0317] Steps ST1105 to ST1119 shown in FIG. 19 are the same as those in FIG.
[0318] In step ST1638 shown in Fig. 19 , UE #1 notifies the base station of information related to the measurement result of the received power. The notification may include information related to the measurement result of the received power in step ST1115 or information related to device identification. The notification may be made using RRC signaling, for example, measurement report signaling, MAC signaling, or L1 / L2 signaling.
[0319] Steps ST1140 to ST1160 shown in FIG. 19 are the same as those in FIG.
[0320] 19 and 20, the base station determines to communicate with the device using multiple routes. In the examples shown in FIGS. 19 and 20, the base station determines to use UE#1 and UE#2.
[0321] In step ST1654 shown in Fig. 19, the base station notifies UE #1 of information related to device configuration. This information may include information indicating that multiple routes will be used. UE #1 performs device configuration using the information received in step ST1654. In step ST1656, UE #1 responds to the base station with the device configuration.
[0322] In steps ST1658 and ST1660 shown in FIG. 19, the same processes as in steps ST1654 and ST1656 are performed between the base station and UE#2.
[0323] In step ST1662 shown in Figure 19, the base station notifies the AMF of information indicating that communication with the device using multiple routes will be started. The information may include information regarding device identification or information regarding UE identification. In the examples shown in Figures 19 and 20, the information regarding UE identification may include identifiers of UE #1 and UE #2.
[0324] In step ST1664 shown in FIG. 20, the AMF requests UE #1 to transmit data from the device. The request may include information indicating that communication is using multiple routes. An example of the information may include information related to UE identification. Step ST1664 may use the same signaling as step ST1112 in FIG. 11. In step ST1666, UE #1 instructs the device to start transmitting device data. The request may include information indicating that communication is using multiple routes. An example of the information may include information related to UE identification, or information related to identification of communication using multiple routes. Step ST1666 may use the same signaling as step ST1113 in FIG. 11.
[0325] In steps ST1668 and ST1670 shown in FIG. 20, the same processes as in steps ST1664 and ST1666 are performed between the base station and UE#2.
[0326] The device may start copying data to be transmitted to the communication network or may start duplication detection operation of data received from the communication network, triggered by step ST1666 and / or step ST1670. For example, the device may start copying data to be transmitted or may start duplication detection operation of data received, triggered by a match between the information on identification of communication using multiple routes, included in step ST1666, and the information included in step ST1670.
[0327] In step ST1672 and step ST1673 shown in Figure 20, data is transmitted from the device to the AMF via UE #1. Step ST1672 shows data transmission from the device to UE #1, and step ST1673 shows data transmission from UE #1 to the AMF.
[0328] In steps ST1674 and ST1675 shown in FIG. 20 , data is transmitted from the device to the AMF via UE #2. Step ST1674 indicates data transmission from the device to UE #2, and step ST1675 indicates data transmission from UE #2 to the AMF. The data transmitted in step ST1674 is the same as that in step ST1672.
[0329] In step ST1676 shown in Figure 20, the AMF deletes the duplicated data. In the example shown in Figure 20, the AMF deletes the data of step ST1675 received later.
[0330] In step ST1678 and step ST1679 shown in Figure 20, data is transmitted from the AMF to the device via UE #1. Step ST1678 shows data transmission from the AMF to UE #1, and step ST1679 shows data transmission from UE #1 to the device.
[0331] In steps ST1680 and ST1681 shown in FIG. 20 , data is transmitted from the AMF to the device via UE #2. Step ST1680 indicates data transmission from the AMF to UE #2, and step ST1681 indicates data transmission from UE #2 to the device. The data transmitted in step ST1680 is the same as that in step ST1678.
[0332] In step ST1682 shown in Fig. 20, the device deletes the duplicated data. In the example shown in Fig. 20, the device deletes the data received in step ST1681 later.
[0333] In step ST1684 shown in Fig. 20, UE #1 notifies the base station of information related to the measurement result of the received power. The notification may include information related to the measurement result of the received power in step ST1672 or information related to the identification of the device. In step ST1684, the same signaling as in step ST1638 may be used.
[0334] In step ST1685 shown in Fig. 20, UE #2 notifies the base station of information related to the measurement result of the received power. The notification may include information related to the measurement result of the received power in step ST1674 or information related to the identification of the device. In step ST1685, the same signaling as in step ST1638 may be used.
[0335] 20, the base station decides to end use of multiple routes in communication with the device. The base station may decide to use only UE #1 in communication with the device.
[0336] In step ST1688 shown in FIG. 20 , the base station notifies UE #1 of information related to device configuration. This information may include information indicating the end of the use of multiple routes. UE #1 performs device configuration using the information notified in step ST1688. In step ST1690, UE #1 instructs the device to start transmitting device data. This request may include information indicating the end of the use of multiple routes. An example of this information may include information related to the identification of the UE. Step ST1690 is triggered by the device stopping data duplication. In step ST1692, UE #1 responds to the base station with its device configuration.
[0337] In step ST1694 shown in FIG. 20 , the base station instructs UE #2 to release the device configuration. For this instruction, RRC signaling, for example, RRC reconfiguration signaling, MAC signaling, or L1 / L2 signaling may be used. In step ST1696, UE #2 instructs the device to stop transmitting device data. Taking step ST1696 as an opportunity, the device stops transmitting data to UE #2. In step ST1698, UE #2 responds to the base station with the device configuration release instruction.
[0338] In step ST1699 shown in Figure 20, the base station notifies the AMF of information indicating that communication with the device using multiple routes will be terminated. The information may include information regarding device identification, or information regarding UE identification. In the example shown in Figure 20, the identifier of UE #1 may be included as the information regarding UE identification. The AMF stops copying data to be transmitted to the device in response to the notification.
[0339] Steps ST1175 to ST1179 shown in FIG. 20 are the same as those in FIG.
[0340] As another example, the core network apparatus may determine whether to use multiple UEs. For example, the core network apparatus may make the determination using information about QoS in communication with the device.
[0341] 21 and 22 are sequence diagrams showing another example of communication between a device and a communication network using multiple UEs. FIG. 21 shows the first half of the sequence, and FIG. 22 shows the second half of the sequence. In the example shown in FIG. 21 and FIG. 22, the device communicates using UE #1 and UE #2, and then communicates using only UE #1. In the example shown in FIG. 21 and FIG. 22, the AMF determines whether communication is performed using multiple routes. In FIG. 21 and FIG. 22, the same step numbers are used for processes similar to those in FIG. 11, FIG. 12, FIG. 19, and FIG. 20, and common descriptions will be omitted.
[0342] Steps ST1105 to ST1148 shown in Figure 21 are the same as those in Figure 11. The AMF may determine whether to perform step ST1142 by using the information on QoS in step ST1116.
[0343] In Step ST1750 shown in Figure 21, the AMF determines to communicate with the device using multiple routes. In the example shown in Figure 21, it determines to use UE #1 and UE #2.
[0344] In Step ST1752 shown in Figure 21, the AMF notifies the base station of information indicating that communication with the device using multiple routes is started. The information may include information regarding device identification, or information regarding UE identification. In the example shown in Figure 21, the information regarding UE identification may include identifiers of UE #1 and UE #2. The base station may determine the device configuration of UE #2 based on Step ST1752.
[0345] Steps ST1654 to ST1682 shown in FIGS. 21 and 22 are the same as those in FIGS.
[0346] In Step ST1786 shown in Figure 22, the AMF decides to terminate communication with the device using multiple routes. In the example shown in Figure 22, the AMF decides to use only UE #1. For example, the AMF may determine whether to make this decision by using information related to QoS in Step ST1673 and / or Step ST1675.
[0347] In step ST1787 shown in Figure 22, the AMF notifies the base station of information indicating that communication with the device using multiple routes is to be terminated. The information may include information regarding device identification, or information regarding UE identification. In the example shown in Figure 22, the identifier of UE #1 may be included as the information regarding UE identification. The base station performs processing to terminate communication with the device using multiple routes, triggered by step ST1787.
[0348] Steps ST1688 to ST1698 shown in FIG. 22 are the same as those in FIG.
[0349] In step ST1799 shown in FIG. 22, the base station transmits a response to step ST1787 to the AMF.
[0350] Steps ST1175 to ST1179 shown in FIG. 22 are the same as those in FIG.
[0351] The decision on whether to use multiple UEs may be made by both the core network device and the base station, which can improve the flexibility of the communication system, for example.
[0352] A single piece of data transmitted by a base station and / or a core network device may be received by multiple UEs. The multiple UEs may transmit the data to a device. The device may receive data from the multiple UEs. The device may detect duplication of the data received from the multiple UEs and delete the duplicated data. This makes it possible to improve resource usage efficiency in a communication system while ensuring the reliability of communication from a communication network to a device, for example.
[0353] Multiple UEs may receive data transmitted by a device. The multiple UEs may transmit the data to a base station and / or a core network device. The base station and / or core network device may receive data from the multiple UEs. The base station and / or core network device may detect duplication of the data received from the multiple UEs and delete the duplicated data. This, for example, can improve resource usage efficiency in a communication system while ensuring the reliability of communication from a device to a communication network.
[0354] Multicast may be used for communication to a device using multiple UEs. For example, multicast may be used for transmission from a base station and / or a core network apparatus to a UE. Information regarding communication to the device may be included in the multicast setting from the base station and / or the core network apparatus to the UE. The UE may use the information to transmit multicast data to the device. This may, for example, avoid complexity in the communication system.
[0355] The data transmitted from the base station and / or the core network device to the UE may include information used for deduplication. The information used for deduplication may be, for example, information about the identification of the data, as disclosed above. This allows, for example, the device to detect data duplication.
[0356] As another example, multicast may be used for transmission from the device to the UE. Information regarding communication to the device may be included in the multicast setting from the base station and / or core network device to the UE. The UE may use the information to transmit multicast data to the device. This may, for example, avoid complexity in the communication system.
[0357] The data transmission from the device to the UE may include information used for deduplication. The information used for deduplication may be, for example, information about the identification of the data as disclosed above. This allows, for example, a base station and / or a core network device to detect data duplication.
[0358] The base station may instruct one or more UEs to transmit from a device. The one or more UEs may instruct the device to transmit data. The base station may instruct one or more UEs other than the aforementioned UEs to receive data transmitted from the device. The instruction to receive data may include information on time / frequency resources related to the reception, or may include information on the device. A new DCI may be provided and used for the instruction to receive data. The UE may receive data from the device in response to the instruction.
[0359] According to the third embodiment, it is possible to improve the reliability of communication between a device and a communication network.
[0360] Fourth Embodiment The UE to which a device is connected may be switched. This switching may be performed, for example, when the core network device is the host.
[0361] The decision to switch the UE may be made by the base station, which may use information about measurements at the UE of signals from the device.
[0362] The UE may notify the base station of the information. The following (1) to (11) are examples of the information notified from the UE to the base station.
[0363] (1) Information regarding device identification.
[0364] (2) Information about power measurement results.
[0365] (3) Information regarding reception error rate.
[0366] (4) Information about the time when power was measured.
[0367] (5) Information regarding the location of the UE.
[0368] (6) Information about the location of the device.
[0369] (7) Information regarding the identification of the area.
[0370] (8) Information about the time when the position was measured.
[0371] (9) Information about the resources used to communicate with the device.
[0372] (10) Information regarding reception delay.
[0373] (11) A combination of the above (1) to (10).
[0374] As examples of the information (2) above, the following (2-1) to (2-6) are disclosed.
[0375] (2-1) Information regarding the power of the signal received by the UE from the device.
[0376] (2-2) Information regarding the path loss between the UE and the device.
[0377] (2-3) Information regarding the power of the signal transmitted by the UE to the device.
[0378] (2-4) Information regarding the ratio between the power of the signal transmitted by the UE to the device and the power of the signal received by the UE from the device.
[0379] (2-5) Information regarding SINR.
[0380] (2-6) A combination of the above (2-1) to (2-5).
[0381] As another example, the UE may notify the core network device of information regarding the measurement results of the signal from the device. The core network device may notify the base station of the information. The base station may use the information to make the above-mentioned determination. The information notified by the UE to the core network device may be the same as (1) to (11) above.
[0382] As another example, the UE may notify the core network device and the base station of information regarding measurement results of signals from the device. For example, the UE may notify the base station of the information (1) and / or (2) above, or the UE may notify the core network device of the information (1), (3) to (11) above. The core network device may notify the base station of the information (1), (3) to (11) above. This, for example, makes it possible to avoid complexity in designing signaling from the UE to the base station.
[0383] The base station may request a core network device to search for a device. The core network device may use the request to determine a UE to which the device search should be directed. The request may include the information (1) to (11) described above. For example, by including the information (6) described above, the core network device can quickly determine a UE to which the device search should be directed.
[0384] The request from the base station to the core network apparatus may include information about the power used for device discovery, which enables the core network apparatus to instruct the UE on the power used for device discovery, for example.
[0385] The core network device may instruct the UE to search for the device. The core network device may issue the instruction to multiple UEs. The UE to which the device is connected may or may not be included in the UEs to which the instruction is directed. The core network device may issue the instruction in response to a notification from the UE, or may issue the instruction in advance to another UE. The instruction may be performed using signaling between the core network device and the UE, such as NAS signaling. The UE may search for the device or measure the received power from the device in response to the instruction from the core network device.
[0386] The following (A) to (D) are disclosed as information included in the instruction from the core network device to other UEs.
[0387] (A) Information regarding the identification of the device.
[0388] (B) Information about resources used to communicate with the device.
[0389] (C) Information regarding transmission power.
[0390] (D) A combination of (A) to (C) above.
[0391] The UE may notify the core network device of the device search results. The notification may include information about the device, for example, information about the presence or absence of the device, or the above-described information (1) to (11). The core network device may notify the base station of the device search results. The information from the core network device to the base station may include the above-described information (1) to (11).
[0392] The base station determines the UE to which the handover is to be performed. The base station may make the determination using the information notified from the core network device.
[0393] The base station may request the source UE to notify the device configuration. The request may include information about the device involved in the UE switching, such as information about the device's identification. The request may be made using RRC signaling, such as RRC reconfiguration, MAC signaling, or L1 / L2 signaling.
[0394] The source UE may notify the base station of the device configuration. The notification may include information about the device identification. The notification from the source UE to the base station may be triggered by the request from the base station to the target UE. The notification may be performed using RRC signaling, for example, RRC reconfiguration complete, MAC signaling, or L1 / L2 signaling.
[0395] The device configuration may include information regarding device identification, information regarding the device location, information regarding the UE, or information regarding the UE location. The information regarding time may include information regarding the time when the device acquired data. The information regarding the device location and / or the information regarding the UE location may include, for example, information regarding the device's location when the device acquired data. The device configuration may include information regarding the configuration of communication between the UE and a base station, information regarding resources (e.g., time, frequency, power, beam) used for communication between the UE and the base station, or information regarding scheduling between the UE and the device. The device configuration may include information regarding the configuration of communication between the UE and a core network device. The device configuration may include information regarding the configuration of communication between the device and a base station, or information regarding the configuration of communication between the device and a core network device.
[0396] The request from the base station to the source UE may include a request for transmission of data related to the device. The source UE may transmit the data to the base station. Transmission of the data from the source UE may be triggered by, for example, the request from the base station to the source UE for transmission of data related to the device.
[0397] The base station may notify the target UE of information regarding device configuration. The notification may include information regarding device identification. The target UE may use the notification to perform device configuration. The target UE may notify the base station of a response to the notification.
[0398] The base station may notify a core network device, for example, an AMF, of switching of a UE to which the device is connected. The notification may include information regarding the device's identification, or information regarding the UE, for example, information regarding the UE's identification. The UE may be, for example, a UE after switching. The core network device may transmit a response to the notification of switching to the base station. The core network device may use the information to transmit data to the UE to which the device is connected or receive data from the UE.
[0399] The UE may stop transmitting data to the device. The stop in the UE may be triggered by a notification of information regarding a measurement result of a signal from the device, a request for notification of a device setting from the base station to the UE, or a device setting release instruction from the base station to the UE. The UE may hold the data received from the core network device.
[0400] Data transmission from the device to the UE may be stopped. The UE may instruct the device to stop transmitting data. The stop may be triggered by a notification of information related to a signal measurement result from the device, a request for notification of device settings from the base station to the UE, or a device setting release instruction from the base station to the UE.
[0401] As another example of stopping data transmission from a device to a UE, the device may stop data transmission to the UE when it receives a device search signal from another UE, or may stop data transmission to the UE when it sends a response to the device search signal to the other UE, or may stop data transmission to the UE when it receives an instruction to start device data transmission from the other UE.
[0402] The source UE may transfer data to be transmitted to the device to the base station. The data transferred by the source UE may be the data held by the UE as described above. The transfer by the source UE may be triggered by notification of information on measurement results of signals from the device, by a request from the base station to the UE for notification of device settings, or by a device setting release instruction from the base station to the UE. The base station may hold the data.
[0403] The base station may transfer data to be transmitted to the device to the target UE. The data transferred by the base station may be the data held by the base station as described above. The transfer by the base station may be triggered by the transfer of the data from the source UE to the base station, or may be triggered by a response from the target UE to a notification of device setting from the base station to the target UE. The target UE may hold the data. The target UE may transmit the data to the device.
[0404] As another example, data to be transmitted to the device may be transferred from the source UE to the core network apparatus. The transfer may be performed via a base station. The core network apparatus may transfer the data to the target UE. The transfer from the core network apparatus to the target UE may be performed via a base station.
[0405] As another example, the source UE may notify the base station and / or core network device of information regarding data to be transmitted to the device. The information may be, for example, information regarding identification, a sequence number, or a timestamp, as disclosed in the third embodiment. The base station and / or core network device may transmit data to be transmitted to the target UE. The base station and / or core network device may perform the transmission using the above-mentioned information. This may improve communication efficiency between the source UE and the base station and / or core network device, for example.
[0406] 23 and 24 are sequence diagrams showing an example of the operation of switching the destination UE and destination base station of a device, relating to communication between a UE and a device. FIG. 23 shows the first half of the sequence, and FIG. 24 shows the second half of the sequence. In the examples shown in FIGS. 23 and 24, the case where the destination UE of the device is switched from UE #1 to UE #2 is shown. UE #1 is the source UE, and UE #2 is the destination UE. FIG. 23 and 24 show the case where the host of the device is an AMF. In the examples shown in FIGS. 23 and 24, the case where the base station determines the switching of the destination UE of the device is shown. In FIGS. 23 and 24, the same step numbers are assigned to processes similar to those in FIGS. 11, 12, 13, and 14, and common descriptions are omitted.
[0407] 23, UE#1 may stop transmitting data to the device in step ST1638. In step ST1134, UE#1 holds the data to the device shown in step ST1122.
[0408] In step ST1862 of FIG. 24, the base station decides to switch the device connection destination UE. In step ST1864, the base station requests UE #1 to notify it of its device setting. In step ST1866, UE #1 notifies the base station of its device setting.
[0409] In Step ST1868 of FIG. 24 , the source UE transfers data to be transmitted to the device to the base station. The base station holds the data. In Step ST1870, the base station transfers the data to the target UE. In Step ST1279, the data transmitted by the target UE to the device may include data transferred from the source UE to the target UE via the base station. The transfer may be performed via the AMF.
[0410] 23 and 24 show an example in which UE #1 stops transmitting data to the device in response to step ST1638, but data transmission to the device may be stopped in response to a device setting release instruction in step ST1264. This makes it possible to shorten the time during which data transmission from the UE to the device is stopped, for example.
[0411] In the examples shown in Figures 23 and 24, the device may stop transmitting data to UE #1 when it receives a device search signal from UE #2 as shown in step ST1144, or may stop transmitting data to UE #1 when it sends a response to the device search signal to UE #2 as shown in step ST1146, or may stop transmitting data to UE #1 when it receives a device data transmission start instruction from UE #2 as shown in step ST1273.
[0412] As another example, the suspension of data transmission from the device to UE #1 may be triggered by a notification of the received power measurement result shown in step ST1638, by a device setting request from the base station to UE #1 shown in step ST1864, or by a device setting release instruction from the base station to UE #1 shown in step ST1264. UE #1 may instruct the device to stop transmitting data triggered by any of the above.
[0413] Another solution is disclosed. The core network device may determine whether to switch the UE. The core network device may be, for example, an AMF or a UPF. Alternatively, an entity related to device-to-device communication may be provided and the entity may make the determination. The core network device may determine whether to switch the UE, for example, using information about QoS in communication with the device. The QoS information may be, for example, a packet loss rate or a delay in received data. As another example of the determination, the core network device may make the determination using information about the received power of a signal from the device at the UE, or may make the determination using both of the above. The UE may notify the core network device of information about the received power. The notification may include, for example, information about the device identification.
[0414] The core network device may notify the base station of switching of the UE to which the device is connected. The notification may include information regarding the identification of the device, or information regarding the UE, for example, information regarding the identification of the UE. The base station may perform a UE switching process in response to the notification. The UE switching process performed by the base station may be the same as that described above.
[0415] The base station may transmit a response to the notification of switching of the device connection destination UE to the core network apparatus. The core network apparatus may recognize the completion of switching of the UE upon receiving the notification.
[0416] 25 and 26 are sequence diagrams showing another example of the operation of switching the destination UE and destination base station of a device, relating to communication between a UE and a device. FIG. 25 shows the first half of the sequence, and FIG. 26 shows the second half of the sequence. In the examples shown in FIGS. 25 and 26, a case is shown in which the destination UE of the device is switched from UE #1 to UE #2. UE #1 is the source UE, and UE #2 is the destination UE. FIG. 25 and 26 show a case in which the host of the device is an AMF. In the examples shown in FIGS. 25 and 26, a case in which the AMF determines the switching of the destination UE of the device is shown. In FIGS. 25 and 26, the same step numbers are assigned to processes similar to those in FIGS. 11, 12, 13, 14, 23, and 24, and common descriptions are omitted.
[0417] In Step ST1950 in FIG. 26, the AMF determines to switch the device connection destination UE. In Step ST1952, the AMF notifies the base station of the device connection destination switch.
[0418] In step ST1970 in FIG. 26 , the base station responds to the AMF to switch the device connection destination UE.
[0419] According to the fourth embodiment, it becomes possible to switch the UE to which the device is connected, and as a result, it becomes possible to continue communication between the UE and the core network device.
[0420] Fifth embodiment Disclosed is a process in which the UE to which a device is connected is switched to a UE connected to a different base station.
[0421] The base station to which the source UE is connected (hereinafter, sometimes referred to as the source base station) determines whether to switch the UE and / or the base station. By doing so, when the device moves, it becomes possible to switch the connection destination to a UE under a base station different from the source base station and continue communication.
[0422] The request from the source base station to the core network device to search for devices, the instruction from the core network device to the UE to search for devices, the notification of the device search results from the UE to the core network device, the notification of the device search results from the core network device to the source base station, and the device setting request from the source base station to the source UE may be performed in the same manner as in embodiment 4.
[0423] The source base station may request the target base station to switch the UE to which the device is connected. The request may be made using, for example, mobility request signaling. The target base station may notify the target UE of information regarding device settings. The target UE may transmit a response to the notification to the target base station.
[0424] The source base station may notify the core network device of the switch of the UE to which the device is connected. The notification may include information regarding the device's identification, information regarding the UE (e.g., information regarding the UE's identification), or information regarding the base station (e.g., information regarding the destination base station). The UE may be, for example, the destination UE. The core network device may transmit a response to the switch notification to the source base station. The core network device may use the information to transmit data to the UE to which the device is connected or receive data from the UE.
[0425] The source UE may stop transmitting data to the device and retain the data in the same manner as in the fourth embodiment.
[0426] The source UE may transfer data to be transmitted to the device to the source base station. The transfer by the source UE may be performed in the same manner as in the fourth embodiment.
[0427] The source base station may transfer data to be transmitted to the device to the destination base station. The data transferred by the source base station may be data held by the base station as described above. The transfer by the source base station may be triggered by the transfer of the data from the source UE to the source base station. The destination base station may hold the data. The transfer may be performed via a core network device.
[0428] The target base station may transfer data to be transmitted to the device to the target UE. The data transferred by the target base station may be data held by the base station as described above. The transfer by the target base station may be performed in the same manner as in embodiment 4. The target UE may transmit the data to the device.
[0429] 27 and 28 are sequence diagrams showing an example of the operation of switching the destination UE and destination base station of a device, relating to communication between a UE and a device. FIG. 27 shows the first half of the sequence, and FIG. 28 shows the second half of the sequence. The examples shown in FIGS. 27 and 28 show a case where an AMF is used as a core NW device. In the examples shown in FIGS. 27 and 28, UE #1 connected to base station #1 is the source UE, UE #2 connected to base station #2 is the target UE, base station #1 is the source base station, and base station #2 is the target base station. The examples in FIGS. 27 and 28 show a case where the target UE is determined by the source base station. In FIGS. 27 and 28, the same step numbers are assigned to processes similar to those in FIGS. 11, 12, 23, and 24, and common descriptions will be omitted.
[0430] In step ST2010 shown in FIG. 27, the same processing as in step ST1105 is performed between base station #2 and UE #2.
[0431] In steps ST2011 and ST2012 shown in FIG. 27, the same processing as step ST1112 in FIG. 11 is performed. Hereinafter, steps ST2016 and ST2017 are the same as step ST1116 in FIG. 11. Steps ST2018 and ST2019 are the same as step ST1118 in FIG. 11. Steps ST2021 and ST2022 are the same as step ST1122 in FIG. 23. In steps ST2042 and ST2048, the same processing as steps ST1142 and ST1148 in FIG. 23 is performed between the AMF and UE #2. In steps ST2044 and ST2046, the same processing as steps ST1144 and ST1146 in FIG. 23 is performed between UE #2 and the device. In step ST2060, the same processing as step ST1160 in FIG. 23 is performed between the AMF and base station #1.
[0432] In step ST2062 shown in Fig. 28, the base station #1 determines to switch the UE to which the device is connected. In the example shown in Fig. 28, the base station #1 determines that the UE to which the device is connected is UE #2.
[0433] In step ST2066 shown in FIG. 28, base station #1 requests base station #2 to switch the UE to which the device is connected. For example, mobility request signaling may be used for this request. The request may include a device identifier, information about the target UE, or information about the device settings. In steps ST2068 and ST2069, the same processes as in steps ST1268 and ST1269 in FIG. 24 are performed between base station #2 and UE #2. In step ST2070, base station #2 transmits a response to step ST2066 to base station #1.
[0434] In step ST2072 shown in Figure 28, base station #1 notifies the AMF of switching of the UE to which the device is connected. The notification may include information related to device identification, information related to the UE, for example, information related to UE identification, or information related to the base station, for example, information related to the switching destination base station. In step ST2074, the AMF transmits a response to step ST2072 to base station #1.
[0435] In step ST2076 shown in FIG. 28 , UE #1 transmits data for the device to base station #1. This data may be, for example, the data stored in step ST1134. In step ST2077, base station #1 transfers the data of step ST2076 to base station #2. In step ST2078, base station #2 transfers the data of step ST2077 to UE #2. In step ST2079, UE #2 transfers the data of step ST2078 to the device.
[0436] In steps ST2081 and ST2082 shown in Fig. 28, the same processing as in step ST1272 in Fig. 14 is performed. In steps ST2085 and ST2086, the same processing as in step ST1276 in Fig. 14 is performed. In steps ST2087 and ST2088, the same processing as in step ST1278 in Fig. 14 is performed.
[0437] Another solution is disclosed. The source base station may determine a destination base station. The source base station may notify the destination base station of information regarding device switching. The notification may include information regarding measurement results of the device, information regarding the UE that performed the measurement, information regarding the device, information regarding the device settings, or a request regarding determination of a UE to which the device will be connected. As another example, the source base station may request the destination base station to switch the UE to which the device is connected. The request may include, for example, information similar to the information included in the notification described above.
[0438] The target base station may determine the target UE using information included in the notification and / or the request from the source base station.
[0439] The target base station may notify the core network device of the switch of the UE to which the device is connected. The notification may include information regarding the device's identification, information regarding the UE (e.g., information regarding the UE's identification), or information regarding the base station (e.g., information regarding the target base station). The UE may be, for example, the target UE. The core network device may transmit a response to the notification of the switch to the target base station. The core network device may use the information to transmit data to the UE to which the device is connected or receive data from the UE.
[0440] As another example, the source base station may notify the core network device of information regarding the switch of the connection destination of the device. The information may include information regarding the destination base station, information regarding the measurement result of the device, information regarding the UE that performed the measurement, information regarding the device, or information regarding the device settings. This allows the core network device to quickly grasp the switch of the UE connected to the device, for example.
[0441] The core network device may notify the target base station of information related to the switch of the connection destination of the device. The notification may include the same information as the notification from the source base station to the core network device.
[0442] The target base station may determine the target UE. The target base station may determine the target UE using the notification from the core network device.
[0443] The target base station may notify the core network apparatus of the switch of the UE to which the device is connected. The notification may be performed, for example, in the same manner as described above.
[0444] 29 and 30 are sequence diagrams showing another example of the operation of switching the destination UE and destination base station of a device, relating to communication between a UE and a device. FIG. 29 shows the first half of the sequence, and FIG. 30 shows the second half of the sequence. The examples shown in FIGS. 29 and 30 illustrate a case where an AMF is used as a core NW device. In the examples shown in FIGS. 29 and 30, UE #1 connected to base station #1 is the source UE, UE #2 connected to base station #2 is the destination UE, base station #1 is the source base station, and base station #2 is the destination base station. The examples in FIGS. 29 and 30 illustrate a case where the destination UE is determined by the destination base station. In FIGS. 29 and 30, the same step numbers are assigned to processes similar to those in FIGS. 11, 12, 23, 24, 27, and 28, and common descriptions will be omitted.
[0445] In step ST2162 shown in Fig. 29 , base station #1 determines to switch the base station to which the UE to which the device is connected is to be connected. In the example shown in Fig. 29 , base station #1 determines that the base station to which the UE to which the device is connected is to be connected is base station #2.
[0446] In step ST2166 shown in FIG. 29, base station #1 requests base station #2 to switch the UE to which the device is connected. For example, mobility request signaling may be used for the request. The request may include information about the measurement results of the device, information about the UE that performed the measurement, information about the device, or information about the device settings. In step ST2167 shown in FIG. 30, base station #2 determines the UE to which the device is connected as UE #2. In the example shown in FIG. 30, base station #2 determines that the UE to which the device is connected is UE #2.
[0447] In steps ST2172 and ST2174 shown in FIG. 30, processing similar to steps ST2072 and ST2074 in FIG. 28 is performed between base station #2 and the AMF.
[0448] A combination of the fourth and fifth embodiments may be used. For example, a device search instruction from a core network device may be sent to a UE serving the same base station as the source UE before a UE serving a base station other than the source UE. The core network device may transmit a device search instruction to a UE serving a base station other than the source UE when a UE serving the base station fails to find the device. This may reduce the number of times a device switches between base stations, thereby reducing the amount of signaling in the communication system.
[0449] As another example of a combination of the fourth and fifth embodiments, a device search instruction from a core network device may be issued in parallel to a UE that is in the same coverage area as the source UE and a UE that is in a different coverage area from the source UE. This enables, for example, a communication network to quickly search for a device, and as a result, quickly switch the UE to which the device is connected.
[0450] This fifth embodiment makes it possible to switch the UE to which a device is connected to a UE connected to a different base station, thereby enabling communication between the UE and the core network device to continue.
[0451] Sixth Embodiment A UE to which a device is connected may be handed over to a different base station. In this embodiment, the base station to which the UE was connected before moving is called a source base station, and the base station to which the UE is connected after the UE has changed its connection destination due to the movement is called a destination base station.
[0452] To solve the above problem, in this embodiment, information about the device is included in a handover request from a source base station to a destination base station. The information about the device may include information about identifying the device (e.g., a device identifier) or may include settings used for communication between the UE and the device.
[0453] The handover request response (e.g., handover request acknowledgement) from the target base station to the source base station may include information about the device and may include settings to be used for communication between the UE and the device. The settings included in the response may be determined by the target base station. The settings included in the response may be different from the settings included in the handover request from the source base station.
[0454] The handover instruction from the source base station to the UE may include settings to be used for communication between the UE and the device, which may be settings determined by the target base station.
[0455] The UE may stop transmitting and receiving device data with the source base station in response to the handover instruction. The UE may continue communication with the device. The UE may retain data received from the device in response to the instruction. The UE may start transmitting and receiving device data with the destination base station in response to the start of connection with the destination base station, for example, the completion of random access processing with the destination base station, or may start transmitting and receiving device data with the destination base station in response to a handover completion notification to the destination base station. The UE may transmit the retained data to the destination base station.
[0456] The UE may stop data transmission and reception with the device when the handover instruction is triggered. The UE may resume data transmission and reception with the device when the connection with the target base station is completed, for example, when a random access process is completed, or when a handover completion notification is transmitted from the UE to the target base station, or when a device data transmission start request is transmitted via the target base station.
[0457] As another example, the UE may continue transmitting and receiving data to and from the device. The UE may retain data received from the device. The UE may transmit the retained data to the target base station when the connection with the target base station is completed, for example, when the random access process is completed, or when a handover completion notification is transmitted from the UE to the target base station.
[0458] The UE may switch the setting used for communication with the device in response to the handover instruction. For example, the UE may switch the setting used for communication with the device to the device setting included in the handover instruction. As another example, the UE may switch the setting used for communication with the device in response to a device data transmission start request notified via the target base station.
[0459] The target base station may request the core network device to switch the communication path between the target base station and the device. The request may include information about the device or information about the UE. In response to the request, the core network device may start communication with the device via the UE after handover.
[0460] 31 is a sequence diagram showing an example of a UE handover operation related to communication between a UE and a device. In the example shown in FIG. 31, the case where the connection destination base station of UE #1 is switched from base station #1 to base station #2 is shown. In FIG. 31, the same step numbers are assigned to processes similar to those in FIG. 11, FIG. 12, FIG. 15, FIG. 27, and FIG. 28, and common explanations will be omitted.
[0461] In step ST2238 shown in FIG. 31 , UE #1 reports a measurement to base station #1. Although not shown in FIG. 31 , UE #1 performs measurements at a predetermined timing to obtain information (e.g., received power) used to determine whether to switch the base station to which it is connected. UE #1 reports the measurement result in the measurement report of step ST2238. In step ST2244, base station #1 decides to hand over UE #1 to base station #2. Base station #1 may make this decision based on the measurement result reported in the measurement report of step ST2238.
[0462] In step ST2250 shown in FIG. 31 , base station #1 notifies base station #2 of a handover request. The request in step ST2250 includes information about the device. The information about the device may include information about identifying the device (e.g., a device identifier) or may include settings used for communication between UE #1 and the device.
[0463] In step ST2252 shown in Fig. 31 , base station #2 notifies base station #1 of a handover request response. In the example shown in Fig. 31 , step ST2252 is a handover request acknowledgement. The response in step ST2252 may include information about the device or may include settings used for communication between UE #1 and the device.
[0464] In step ST2255 shown in FIG. 31 , base station #1 issues a handover instruction to UE #1. The instruction may be issued, for example, using RRC reconfiguration signaling. The instruction may include settings to be used for communication between UE #1 and the device. The settings included in the instruction may be the settings determined by base station #2. Step ST2255 is triggered by UE #1 to start handover processing. Step ST2255 is triggered by UE #1 to stop device data transmission and reception with base station #1. The UE may continue communication with the device. In step ST1328, the UE may hold the data received from the device.
[0465] 31 , the UE #1 notifies the base station #2 of a response to the handover command. The response may be notified using RRC signaling, for example, signaling of RRC reconfiguration complete (RRCReconfigurationComplete).
[0466] In step ST2272 shown in Figure 31, base station #2 requests the AMF to switch the communication path between the device. The request may include information about the device or information about UE #1. In step ST2274, the AMF transmits a response to step ST2272 to base station #2.
[0467] In step ST2278 shown in FIG. 31 , UE #1 transmits the stored data to base station #2. The data may be, for example, the data of step ST1325. In step ST2279, base station #2 transfers the data of step ST2278 to the AMF.
[0468] In steps ST2281, ST2282, and ST2283 shown in Fig. 31, the same processes as in steps ST2081, ST2082, and ST1273 in Fig. 28 are performed. In steps ST2284, ST2285, and ST2286, the same processes as in steps ST1275, ST2085, and ST2086 in Fig. 28 are performed. In steps ST2287, ST2288, and ST2289, the same processes as in steps ST2087, ST2088, and ST1279 in Fig. 28 are performed.
[0469] In the example shown in Fig. 31, the transmission of device data in steps ST2278 and ST2279 is performed after step ST2276, but it may be performed after step ST2259. This enables, for example, rapid transmission of device data.
[0470] As another example relating to Fig. 31 , the transmission of device data shown in step ST2278 may be included in the signaling of step ST2259, or the transmission of device data shown in step ST2279 may be included in the signaling of step ST2272. This enables, for example, rapid transmission of device data.
[0471] Although an example has been shown in which the UE instructs the device to start transmitting device data in step ST2283 in Fig. 31 , the UE may not perform step ST2283. This makes it possible to reduce signaling between the UE and the device, for example.
[0472] The method disclosed in the sixth embodiment may be used for inter-DU handover. For example, the signaling of a UE context setup request (UE CONTEXT SETUP REQUEST) from the CU to the target DU may include information about the device, or information about settings used for communication between the UE and the device. The signaling of a UE context release request from the CU to the source DU may include information about the device, or device context. This makes it possible to maintain communication between the device and the communication system, for example, even after inter-DU mobility of the UE.
[0473] A combination of the fourth embodiment and the sixth embodiment may be used. For example, in a handover of a UE connected to multiple devices, some of the multiple devices may continue to be connected to the UE, and the remaining devices may switch the connection destination UE to another UE. The other UE may be a UE connected to the source base station of the UE being handed over. This makes it possible to reduce the load on the UE, for example.
[0474] As another example, the switching of the UE to which the device is connected may be performed after the UE has been handed over, which may avoid, for example, complexity in the communication system.
[0475] The UE may suspend notification of information related to measurement results of signals from devices. For example, the UE may suspend such notification during handover. The UE may resume such notification after the handover is completed. This may, for example, avoid processing complexity in the communication system.
[0476] According to the sixth embodiment, even when the UE to which the device is connected undergoes handover, communication between the device and the core network apparatus can be continued.
[0477] Seventh Embodiment The UE to which the device connects may be switched from a UE connected to a 3GPP network to a non-3GPP terminal.
[0478] The base station may decide to switch. The base station may request a core network device to search for devices. The core network device may request a non-3GPP interworking function (N3IWF) (see Non-Patent Document 10) to search for devices.
[0479] A device discovery process and a process related to the response thereto may be performed between the N3IWF, the non-3GPP access device, the non-3GPP terminal, and the device.
[0480] The N3IWF may transmit information about device measurement results to the core network device. The measurement results may be, for example, measurement results by a non-3GPP terminal.
[0481] The base station may request device mobility from the core network device. The request may include information about a destination network, e.g., a non-3GPP network, or information about a destination terminal, e.g., a non-3GPP terminal. The core network device may request device mobility from the N3IWF.
[0482] Processing related to device switching may be performed between the N3IWF, non-3GPP access device, non-3GPP terminal, and device.
[0483] The N3IWF may send a response to the device's mobility request to the core network device.
[0484] The UE may transmit data intended for the device to the core network device. The core network device may forward the data to the N3IWF. The N3IWF may forward the data to the non-3GPP access device. The non-3GPP access device may forward the data to the device via the non-3GPP terminal.
[0485] Figures 32 and 33 are sequence diagrams showing an example of an operation in which a UE to which a device is connected switches from a UE connected to a 3GPP network to a non-3GPP terminal. Figure 32 shows the first half of the sequence, and Figure 33 shows the second half of the sequence. In Figures 32 and 33, the same step numbers are used for processes similar to those in Figures 11, 12, 27, and 28, and common explanations will be omitted.
[0486] In Fig. 32, the UE may stop transmitting data to the device in Step ST1638. In Step ST1134, the UE holds the data to the device shown in Step ST2022.
[0487] In Step ST2342 shown in FIG. 32 , the AMF requests the N3IWF to search for devices. The request may include information regarding device identification.
[0488] In step ST2343 shown in FIG. 32 , the N3IWF instructs the non-3GPP terminal to search for a device. In steps ST2345 and ST2347, the same processes as those in steps ST2044 and ST2046 in FIG. 27 are performed between the device and the non-3GPP terminal. In step ST2349, the non-3GPP terminal notifies the N3IWF of information about the measurement results of the device. In step ST2351, the N3IWF notifies the AMF of information about the measurement results of the device. The information about the measurement results may include information about the identification of the device, or may include information about the identification of the non-3GPP terminal. In step ST2353, the AMF notifies the base station of the information about the measurement results of the device. The notification may include information similar to the information included in the notification in step ST2351, or may include information about the non-3GPP network.
[0489] In Step ST2355 shown in FIG. 33, the base station decides to switch the connection destination of the device.
[0490] In Step ST2357 shown in FIG. 33 , the base station requests device mobility from the AMF. The request may include information on a target network, for example, a non-3GPP network, or information on a target terminal, for example, a non-3GPP terminal. In Step ST2359, the AMF may request device mobility from the N3IWF. The request may include information similar to the information included in the request in Step ST2357.
[0491] In step ST2361 shown in FIG. 33, processing related to device switching is performed among the N3IWF, the non-3GPP access device, and the non-3GPP terminal.
[0492] In Step ST2363 shown in FIG. 33 , the N3IWF transmits the response of Step ST2359 to the AMF. In Step ST2365, the AMF transmits the response of Step ST2357 to the base station.
[0493] In Step ST2367 shown in FIG. 33, the UE transmits device-destined data to the AMF. The data may be data held by the UE in Step ST1134.
[0494] In steps ST2381 and ST2382 shown in Fig. 33, the same processing as in step ST1272 in Fig. 24 is performed for the non-3GPP terminal via the N3IWF and the non-3GPP access device. In step ST2383, the same processing as in step ST1273 in Fig. 24 is performed from the non-3GPP terminal to the device.
[0495] In steps ST2384 to ST2386 shown in FIG. 33, data from the device to the AMF is transmitted via the non-3GPP network. In steps ST2387 to ST2389, data from the AMF to the device is transmitted via the non-3GPP network.
[0496] 32 and 33 show an example in which the UE stops data transmission to the device in response to step ST1638, but the UE may stop data transmission to the device in response to a device setting request in step ST1864, or may stop data transmission to the device in response to a device setting release instruction in step ST1264. This makes it possible to shorten the time during which data transmission from the UE to the device is stopped, for example.
[0497] In the examples shown in Figures 32 and 33, the device may stop transmitting data to UE #1 when it receives a device search signal from the non-3GPP terminal as shown in step ST2345, or may stop transmitting data to UE #1 when it transmits a response to the device search signal to the non-3GPP terminal as shown in step ST2347, or may stop transmitting data to UE #1 when it receives a device data transmission start instruction from the non-3GPP terminal as shown in step ST2383.
[0498] As another example, the suspension of data transmission from the device to UE #1 may be triggered by a notification of the received power measurement result shown in step ST1638, by a device setting request from the base station to UE #1 shown in step ST1864, or by a device setting release instruction from the base station to UE #1 shown in step ST1264. UE #1 may instruct the device to stop transmitting data triggered by any of the above.
[0499] As another solution, the decision to switch may be made by the core network device. In the process of switching, a combination of the method disclosed in the fifth embodiment and the above-mentioned method may be used.
[0500] According to the seventh embodiment, even when the connection destination of the device is switched to a non-3GPP terminal, it is possible to continue communication between the device and the core network apparatus.
[0501] In the present disclosure, searching for a device has been described, but the present disclosure may also be confirming a device or detecting a device.
[0502] One or more cells are configured in one gNB. In this disclosure, although it is described as a gNB or a cell, it may be a gNB or a cell unless otherwise specified.
[0503] In the present disclosure, a gNB may be an MCG or an SCG.
[0504] The above-described embodiments and their modifications are merely examples, and the embodiments and their modifications can be freely combined. Furthermore, any of the components of the embodiments and their modifications can be modified or omitted as appropriate.
[0505] For example, in the above-described embodiments and their modifications, a slot is an example of a time unit for communication in a fifth-generation communication system. A slot may be a scheduling unit. In the above-described embodiments and their modifications, processing described as being performed in slot units may be performed in TTI units, subframe units, subslot units, or minislot units.
[0506] For example, the methods disclosed in the above-described embodiments and their modifications may be applied to the IAB, to communication between an IAB donor and an IAB node, or to processing using a Uu in the IAB.
[0507] For example, the methods disclosed in the above-described embodiments and their modifications may be applied to communication between UEs or between a UE and a NW via a relay using SL communication.
[0508] For example, the methods disclosed in the above-described embodiments and their modified examples may be applied to services that use SL communication, not limited to V2X (Vehicle-to-everything) services, such as proximity-based services, public safety, communication between wearable devices, and communication between devices in factories.
[0509] Various aspects of the present disclosure are summarized below as appendices.
[0510] (Supplementary Note 1) A communication system comprising: a base station compatible with a fifth-generation wireless access system; a communication terminal connected to the base station; and a device connected to the base station, wherein, when the connection between the device and the communication terminal is disconnected, a plurality of the communication terminals execute a search process for the device, and a communication terminal that is able to search for the device operates as a communication terminal to which the device is connected. (Supplementary Note 2) The communication system according to Supplementary Note 1, wherein, when communication with the base station becomes impossible while connected to the device, the communication terminal stops communication with the device. (Supplementary Note 3) The communication system according to Supplementary Note 1, wherein, when communication with the base station becomes impossible while connected to the device, the communication terminal continues communication with the device and holds data received from the device, and when communication with the base station is restored, transmits the held data to the base station. (Supplementary Note 4) The communication system according to Supplementary Note 1, wherein, when communication with the base station becomes impossible while connected to the device, the communication terminal continues communication with the device and retains data received from the device, and discards the retained data when communication with the base station is not restored or when the device connects to another communication terminal. (Supplementary Note 5) The communication system according to any one of Supplements 1 to 4, wherein the device connects to a plurality of the communication terminals and transmits and receives the same data via each of the plurality of communication terminals to which it is connected. (Supplementary Note 6) The communication system according to Supplementary Note 5, wherein, when the device receives the same data from a plurality of the communication terminals, the device retains one of the received identical data and discards the rest, and when the same data transmitted by the device via the plurality of the communication terminals is discarded in a core network apparatus, the rest of the data retains one.(Supplementary Note 7) The communications system according to any one of Supplementary Notes 1 to 6, wherein the communications terminal transmits information relating to measurement results of signal reception power from the device to the base station or core network apparatus, and the base station or core network apparatus, having received the information relating to the measurement results, determines whether or not switching of the device's connection destination is necessary based on the information relating to the measurement results. (Supplementary Note 8) The communications system according to Supplementary Note 7, wherein, when determining based on the information relating to the measurement results that switching of the device's connection destination is necessary, the base station determines the communications terminal to be a new connection destination for the device. (Supplementary Note 9) The communications system according to Supplementary Note 8, wherein, when the communications terminal determined as a new connection destination for the device is connected to another base station, the base station transmits information relating to the communications terminal determined as a new connection destination for the device and information relating to the device to the other base station. (Supplementary Note 10) The communication system according to Supplementary Note 7, wherein, when it is determined based on the information on the measurement result that switching of the connection destination of the device is necessary, the base station determines another base station to which the communication terminal is connected as a new connection destination of the device and transmits information on the device to the other base station, and the other base station determines the communication terminal as a new connection destination of the device based on the information on the device. (Supplementary Note 11) The communication system according to any one of Supplementary Notes 1 to 8, wherein, when the communication terminal currently connected to the device and connected to the base station is to be handed over to another base station, the base station transmits information on the device to the other base station, and the other base station determines settings to be used for communication between the device and the communication terminal based on the information on the device.(Supplementary Note 12) The communication system described in any one of Supplementary Notes 1 to 9, characterized in that when the base station switches the connection destination of the device to a communication terminal of another communication system different from the fifth generation wireless access system, the base station transmits information about the device and information about the other communication system to a core network device, and the core network device forwards the information about the device and information about the other communication system received from the base station to the other communication system.
[0511] 202 Communication terminal device (mobile terminal), 210 Communication system, 213, 240-1, 240-2, 750 Base station device (NR base station, base station), 214 5G core unit, 215 Central unit, 216 Distributed unit, 217 Central unit for control plane, 218 Central unit for user plane, 219 TRP, 301, 403 Protocol processing unit, 302 Application unit, 304, 405 Encoder unit, 305, 406 Modulation unit, 306, 407 Frequency conversion unit, 307-1 to 307-4, 408-1 to 408-4 Antenna, 308, 409 Demodulation unit, 309, 410 Decoder unit, 310, 411, 526 Control unit, 401 EPC communication unit, 402 Other base station communication unit, 412 5GC communication unit, 521 Data Network communication unit, 522 base station communication unit, 523 user plane communication unit, 523-1 PDU processing unit, 523-2 mobility anchoring unit, 525 control plane control unit, 525-1 NAS security unit, 525-2 idle state mobility management unit, 527 session management unit, 527-1 PDU session control unit, 527-2 UE IP address allocation unit, 751-1 to 751-8 beams, 752 cell.
Claims
1. A communications system comprising: a base station compatible with a fifth-generation wireless access system; a communications terminal connected to said base station; and a device connected to said base station, wherein when a connection between said device and said communications terminal is disconnected, a plurality of said communications terminals execute a search process for said device, and a communications terminal that is able to search for said device operates as a communications terminal to which said device is connected.
2. The communication system according to claim 1, characterized in that said communication terminal stops communication with said device when communication with said base station becomes impossible while connected to said device.
3. The communication system according to claim 1, characterized in that, when communication with the base station becomes impossible while connected to the device, the communication terminal continues communication with the device and retains data received from the device, and when communication with the base station is restored, transmits the retained data to the base station.
4. The communication system according to claim 1, characterized in that, when communication with the base station becomes impossible while connected to the device, the communication terminal continues communication with the device and retains data received from the device, and, when communication with the base station is not restored or when the device connects to another communication terminal, the communication terminal discards the retained data.
5. The communication system according to claim 1, wherein the device is connected to a plurality of the communication terminals, and the device transmits and receives the same data via each of the plurality of communication terminals to which it is connected.
6. The communication system according to claim 5, characterized in that, when the device receives the same data from a plurality of the communication terminals, it retains one of the received identical data and discards the others, and when the device transmits the same data via a plurality of the communication terminals, the core network device discards the other data and retains one of the received identical data.
7. A communication system as described in any one of claims 1 to 6, characterized in that the communication terminal transmits information regarding the measurement results of the signal reception power from the device to the base station or core network device, and the base station or core network device receiving the information regarding the measurement results determines whether or not it is necessary to switch the connection destination of the device based on the information regarding the measurement results.
8. The communication system according to claim 7, characterized in that, when the base station determines that it is necessary to switch the connection destination of the device based on the information regarding the measurement results, it determines the communication terminal to be the new connection destination of the device.
9. The communication system according to claim 8, characterized in that, when the communication terminal determined as the new connection destination of the device is connected to another base station, the base station transmits information about the communication terminal determined as the new connection destination of the device and information about the device to the other base station.
10. The communication system described in claim 7, characterized in that, when the base station determines based on the information regarding the measurement results that it is necessary to switch the connection destination of the device, it determines another base station to which the communication terminal to be the new connection destination of the device will be connected and transmits information regarding the device to the other base station, and the other base station determines the communication terminal to be the new connection destination of the device based on the information regarding the device.
11. The communication system according to claim 1, characterized in that, when the communication terminal connected to the device connected to the base station is handed over to another base station, the base station transmits information about the device to the other base station, and the other base station determines settings to be used for communication between the device and the communication terminal based on the information about the device.
12. The communication system described in claim 1, characterized in that, when the base station switches the connection destination of the device to a communication terminal of another communication system that uses a different method from the fifth generation wireless access system, the base station transmits information about the device and information about the other communication system to a core network device, and the core network device forwards the information about the device and information about the other communication system received from the base station to the other communication system.
Citation Information
Patent Citations
Radio communication system, radio communication terminal and subscriber information management device
JP2012256986A
