Terminal device, base station device, and communication system

Abstract

To enable quick network (NW) connections.SOLUTION: A terminal device has a plurality of SIMs (Subscriber Identity Modules) and is configured to connect to a plurality of networks using the plurality of SIMs. The plurality of networks include a first network and a second network, and the terminal device transmits, to a base station device of the first network, information indicating whether the terminal device receives paging from the first network.SELECTED DRAWING: Figure 14

Description

[Technical field]

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

[0002] 3GPP (3rd Generation Partnership Project), a standardization organization for mobile communication systems, is considering a communication method called Long Term Evolution (LTE) for wireless sections and System Architecture Evolution (SAE) for the overall system configuration including a core network and a wireless access network (hereinafter collectively referred to as a network) (for example, Non-Patent Documents 1 to 5). This communication method is also called a 3.9G (3.9 Generation) system.

[0003] LTE uses OFDM (Orthogonal Frequency Division Multiplexing) for downlink and SC-FDMA (Single Carrier Frequency Division Multiple Access) for uplink as its access method. Also, unlike W-CDMA (Wideband Code Division Multiple Access), LTE does not include circuit switching and is only a packet communication method.

[0004] The decisions made by 3GPP regarding the frame configuration in the LTE system, which are described in Non-Patent Document 1 (Chapter 5), will be described with reference to FIG. 1. FIG. 1 is an explanatory diagram showing the configuration of a radio frame used in an LTE communication system. In FIG. 1, one radio frame is 10 ms. The radio frame is divided into 10 equally sized subframes. The subframe is divided into two equally sized slots. The first and sixth subframes of each radio frame include a downlink synchronization signal. The synchronization signal includes a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS).

[0005] The decisions made by 3GPP regarding the channel configuration in the LTE system are described in Non-Patent Document 1 (Chapter 5). It is assumed that the same channel configuration as that of a non-CSG cell is used in a CSG (Closed Subscriber Group) cell.

[0006] The 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 simply referred to as a "communication terminal") such as a mobile terminal device (hereinafter, sometimes simply referred to as a "mobile terminal"). A BCH transport block is mapped to four subframes in a 40 ms interval. There is no explicit signaling of the 40 ms timing.

[0007] The Physical Control Format Indicator Channel (PCFICH) is a channel for downlink transmission from a base station to a communication terminal. The PCFICH notifies the communication terminal of the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols used for PDCCHs from the base station. The PCFICH is transmitted every subframe.

[0008] The Physical Downlink Control Channel (PDCCH) is a channel for downlink transmission from a base station to a communication terminal. The PDCCH reports 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 for the DL-SCH. The PDCCH carries an uplink scheduling grant. The PDCCH carries Acknowledgement (Acknowledgement) / Nack (Negative Acknowledgement), which are response signals to uplink transmission. The PDCCH is also called an L1 / L2 control signal.

[0009] A physical downlink shared channel (PDSCH) is a channel for downlink transmission from a base station to a communication terminal. A downlink shared channel (DL-SCH), which is a transport channel, and a PCH, which is a transport channel, are mapped to the PDSCH.

[0010] A physical multicast channel (PMCH) is a channel for downlink transmission from a base station to communication terminals. A multicast channel (MCH), which is a transport channel, is mapped to the PMCH.

[0011] The Physical Uplink Control Channel (PUCCH) is a channel for uplink transmission from a communication terminal to a base station. The PUCCH carries Ack / Nack, which is a response signal to a downlink transmission. The PUCCH carries Channel State Information (CSI). The CSI is composed of a Rank Indicator (RI), a Precoding Matrix Indicator (PMI), and a Channel Quality Indicator (CQI) report. The RI is information on the rank of a channel matrix in MIMO. The PMI is information on the precoding weight matrix used in MIMO. The CQI is quality information that indicates the quality of received data or the quality of the communication path. The PUCCH also carries a Scheduling Request (SR).

[0012] A Physical Uplink Shared Channel (PUSCH) is a channel for uplink transmission from a communication terminal to a base station. An Uplink Shared Channel (UL-SCH), which is one of the transport channels, is mapped to the PUSCH.

[0013] The Physical Hybrid ARQ Indicator Channel (PHICH) is a channel for downlink transmission from a base station to a communication terminal. The PHICH carries Ack / Nack, which is a response signal to an uplink transmission. The 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.

[0014] Downlink reference signals (RS) are known symbols in LTE communication systems. The following five types of downlink reference signals are defined: Cell-specific Reference Signal (CRS), MBSFN Reference Signal, UE-specific Reference Signal (DM-RS) Demodulation Reference Signal (PRS), Positioning Reference Signal (PRS), and Channel State Information Reference Signal (CSI-RS). Measurement of the physical layer of a communication terminal includes measurement of the reference signal received power (RSRP).

[0015] Similarly, the uplink reference signal is a known symbol in the LTE communication system. Two types of uplink reference signals are defined: a data demodulation reference signal (DM-RS) and a sounding reference signal (SRS).

[0016] The transport channel described in Non-Patent Document 1 (Chapter 5) will be explained. Among the downlink transport channels, the broadcast channel (BCH) is broadcast to the entire coverage of the base station (cell). The BCH is mapped to the physical broadcast channel (PBCH).

[0017] Retransmission control using HARQ (Hybrid ARQ) is applied to the Downlink Shared Channel (DL-SCH). DL-SCH can be broadcast to the entire coverage of a base station (cell). DL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also called persistent scheduling. DL-SCH supports discontinuous reception (DRX) of communication terminals to reduce power consumption of communication terminals. DL-SCH is mapped to the physical downlink shared channel (PDSCH).

[0018] The Paging Channel (PCH) supports DRX of communication terminals to enable low power consumption of the communication terminals. The PCH is required to be 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.

[0019] The Multicast Channel (MCH) is used for broadcasting to the entire coverage of a base station (cell). The MCH supports SFN combining of MBMS (Multimedia Broadcast Multicast Service) services (MTCH and MCCH) in multi-cell transmission. The MCH supports semi-static resource allocation. The MCH is mapped to the PMCH.

[0020] Among the uplink transport channels, the uplink shared channel (UL-SCH) is subject to retransmission control using HARQ (Hybrid ARQ). The UL-SCH supports dynamic or semi-static resource allocation. The UL-SCH is mapped to the physical uplink shared channel (PUSCH).

[0021] The Random Access Channel (RACH) is limited to control information. The RACH is subject to collision risk. The RACH is mapped to the Physical Random Access Channel (PRACH).

[0022] Let us explain about HARQ. HARQ is a technology that improves the communication quality of a transmission line by combining Automatic Repeat reQuest (ARQ) and Forward Error Correction. HARQ has the advantage that error correction works effectively by retransmission even for transmission lines whose communication quality changes. In particular, it is possible to obtain further quality improvement by combining the reception result of the initial transmission and the reception result of the retransmission when retransmitting.

[0023] An example of a retransmission method will be described below. If the received data cannot be decoded correctly on the receiving side, 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 that receives the "Nack" will retransmit the data. If the received data can be decoded correctly on the receiving side, in other words, if no CRC error occurs (CRC=OK), the receiving side will send an "Ack" to the transmitting side. The transmitting side that receives the "Ack" will send the next data.

[0024] The logical channel described in Non-Patent Document 1 (Chapter 6) will be explained. The Broadcast Control Channel (BCCH) is a downlink channel for broadcast system control information. The logical channel BCCH is mapped to the broadcast channel (BCH) or the downlink shared channel (DL-SCH), which are transport channels.

[0025] The Paging Control Channel (PCCH) is a downlink channel for transmitting paging information and changes to system information. The PCCH is used when the network does not know the cell location of the communication terminal. The PCCH, which is a logical channel, is mapped to the Paging Channel (PCH), which is a transport channel.

[0026] A Common Control Channel (CCCH) is a channel for transmission control information between a communication terminal and a base station. CCCH is used when a communication terminal does not have an RRC connection with the network. In the downlink direction, CCCH is mapped to a transport channel, the Downlink Shared Channel (DL-SCH). In the uplink direction, CCCH is mapped to a transport channel, the Uplink Shared Channel (UL-SCH).

[0027] The Multicast Control Channel (MCCH) is a downlink channel for point-to-multipoint transmission. The MCCH is used for transmission of MBMS control information for one or several MTCHs from the network to communication terminals. The MCCH is used only by communication terminals receiving MBMS. The MCCH is mapped to the Multicast Channel (MCH), which is a transport channel.

[0028] A Dedicated Control Channel (DCCH) is a channel that transmits dedicated control information between a communication terminal and a network on a one-to-one basis. DCCH is used when a communication terminal is in an RRC connection. DCCH is mapped to an uplink shared channel (UL-SCH) in the uplink and to a downlink shared channel (DL-SCH) in the downlink.

[0029] A Dedicated Traffic Channel (DTCH) is a one-to-one communication channel for transmitting user information to an individual communication terminal. DTCH exists in both uplink and downlink. DTCH is mapped to an uplink shared channel (UL-SCH) in uplink and to a downlink shared channel (DL-SCH) in downlink.

[0030] A Multicast Traffic Channel (MTCH) is a downlink channel for transmitting traffic data from a network to a communication terminal. The MTCH is a channel used only by communication terminals receiving MBMS. The MTCH is mapped to a Multicast Channel (MCH).

[0031] CGI stands for Cell Global Identifier. ECGI stands for E-UTRAN Cell Global Identifier. CSG (Closed Subscriber Group) cells are introduced in LTE, LTE-A (Long Term Evolution Advanced) (described below), and UMTS (Universal Mobile Telecommunication System).

[0032] 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 enable the communication terminal to be called, in other words, to allow the communication terminal to receive calls. The area for tracking the location of this communication terminal is called a tracking area.

[0033] 3GPP is also working on the development of standards for Long Term Evolution Advanced (LTE-A) as Release 10 (see Non-Patent Documents 3 and 4). LTE-A is based on the LTE wireless communication method, and is configured by adding several new technologies to it.

[0034] In the LTE-A system, in order to support wider frequency bandwidths (transmission bandwidths) up to 100 MHz, Carrier Aggregation (CA) is being considered, which aggregates two or more Component Carriers (CCs) (also called "aggregation"). CA is described in Non-Patent Document 1.

[0035] When CA is configured, the UE has only one RRC connection with the network (NW). In the RRC connection, one serving cell provides NAS mobility information and security input. This cell is called a Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell is the Downlink Primary Component Carrier (DL PCC). In the uplink, the carrier corresponding to the PCell is the Uplink Primary Component Carrier (UL PCC).

[0036] Depending on the UE's capabilities, a secondary cell (SCell) is configured to form a set of serving cells together with the PCell. In the downlink, the carrier corresponding to the SCell is the downlink secondary component carrier (DL SCC). In the uplink, the carrier corresponding to the SCell is the uplink secondary component carrier (UL SCC).

[0037] A set of serving cells, which includes one PCell and one or more SCells, is configured for one UE.

[0038] New technologies for LTE-A include a technology that supports wider bandwidth (Wider Bandwidth Extension) and a Coordinated Multiple Point transmission and reception (CoMP) technology. CoMP, which is being considered for LTE-A by 3GPP, is described in Non-Patent Document 1.

[0039] In addition, in 3GPP, in order to handle the huge traffic in the future, the use of small eNBs (hereinafter sometimes referred to as "small-scale base station devices") that configure small cells is being considered. For example, technologies are being considered that improve frequency utilization efficiency and increase communication capacity by installing many small eNBs and configuring many small cells. Specifically, there is dual connectivity (abbreviated as DC) in which a UE connects to two eNBs to communicate. DC is described in Non-Patent Document 1.

[0040] Of the eNBs performing dual connectivity (DC), one may be referred to as a "master eNB (abbreviated as MeNB)" and the other as a "secondary eNB (abbreviated as SeNB)."

[0041] Mobile network traffic is on the rise, and communication speeds are also getting faster. Once LTE and LTE-A are fully operational, communication speeds are expected to become even faster.

[0042] Furthermore, to cope with the increasing sophistication of mobile communications, fifth-generation (hereinafter sometimes referred to as "5G") wireless access systems are being considered, with the goal of starting services after 2020. For example, in Europe, an organization called METIS has compiled requirements for 5G (see Non-Patent Document 5).

[0043] Compared to the LTE system, the 5G wireless access system requires a system capacity that is 1,000 times greater, a data transmission speed that is 100 times greater, data processing delay that is one-tenth (1 / 10), and 100 times the number of simultaneous connections of communication terminals, while also achieving further reductions in power consumption and reductions in equipment costs.

[0044] In order to meet such demands, 3GPP is currently working on 5G standards as Release 15 (see Non-Patent Documents 6 to 18). The technology for 5G wireless sections is called "New Radio Access Technology" ("New Radio" is abbreviated as "NR").

[0045] The NR system is being developed based on the LTE system and LTE-A system, but the following changes and additions have been made to the LTE system and LTE-A system:

[0046] The NR access method uses OFDM for the downlink and OFDM and DFT-s-OFDM (DFT-spread-OFDM) for the uplink.

[0047] NR allows the use of higher frequencies than LTE in order to improve transmission speeds and reduce processing delays.

[0048] In NR, cell coverage is ensured by forming a narrow beam-shaped transmission and reception range (beamforming) and changing the direction of the beam (beam sweeping).

[0049] In the NR frame configuration, various subcarrier intervals, i.e., various numerologies, are supported. In NR, regardless of the numerology, one subframe is 1 millisecond, and one slot is composed of 14 symbols. In addition, the number of slots included in one subframe is one in a numerology with a subcarrier interval of 15 kHz, and increases in proportion to the subcarrier interval in other numerologies (see Non-Patent Document 13 (TS38.211 V16.0.0)).

[0050] In NR, downlink synchronization signals are transmitted from base stations as synchronization signal bursts (hereinafter sometimes referred to as SS bursts) at a predetermined cycle with a predetermined duration. An SS burst is composed of synchronization signal blocks (hereinafter sometimes referred to as SS blocks) for each beam of the base station. The base station transmits the SS blocks of each beam within the duration of the SS burst by changing the beam. An SS block is composed of P-SS, S-SS, and PBCH.

[0051] In NR, the influence of phase noise is reduced by adding a Phase Tracking Reference Signal (PTRS) as a downlink reference signal for NR. PTRS is also added to the uplink reference signal in the same way as in the downlink.

[0052] In NR, in order to flexibly switch between DL and UL within a slot, slot format indication (SFI) has been added to the information contained in the PDCCH.

[0053] In addition, in NR, the base station pre-configures 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 that BWP, thereby reducing power consumption in the UE.

[0054] In 3GPP, the following DC forms are being considered: DC by LTE base stations and NR base stations connected to the EPC, DC by NR base stations connected to the 5G core system, and DC by LTE base stations and NR base stations connected to the 5G core system (see non-patent documents 12, 16, and 19).

[0055] Also, 3GPP is considering several new technologies, such as the operation of a terminal using multiple SIMs (Subscriber Identity Modules) (see Non-Patent Document 20). [Prior art documents] [Non-patent literature]

[0056] [Non-Patent Document 1] 3GPP TS 36.300 V16.0.0 [Non-Patent Document 2] 3GPP S1-083461 [Non-Patent Document 3] 3GPP TR 36.814 V9.2.0 [Non-Patent Document 4] 3GPP TR 36.912 V15.0.0 [Non-Patent Document 5] “Scenarios, requirements and KPIs for 5G mobile and wireless system”, ICT-317669-METIS / D1.1

Non-licensed Document 6

Non-licensed Document 7

Non-licensed literature 9

Non-licensed literature 10

Non-licensed Document 11

Non-licensed Document 12

Non-licensed Document 13

Non-licensed Document 14

Non-licensed Document 15

Non-licensed Document 16

Non-licensed Document 17

Non-licensed Document 18

Non-licensed Document 19

Non-licensed Document 20

Non-licensed Document 21

Non-licensed Document 22

Non-licensed Document 23

[0057] In 3GPP, the operation of a UE using multiple SIMs is being studied. For example, measures to be taken when the timing of paging to the UE from two networks overlaps, and a method of notifying the type of data related to paging are being studied (see Non-Patent Document 20). However, no specific method is disclosed for determining from which network a paging is to be received. For example, when paging for emergency communication such as ETWS (Earthquake and Tsunami Warning System) or CMAS (Commercial Mobile Alert System) is included in paging that collides with each other, the UE may not be able to receive the paging for the emergency communication. As a result, a problem occurs in that the UE cannot promptly receive the emergency communication.

[0058] In view of the above-mentioned problems, one of the objects of the present disclosure is to provide a technique that enables rapid network connection. [Means for solving the problem]

[0059] The terminal device of the present disclosure is a terminal device having a plurality of SIMs (Subscriber Identity Modules) and configured to connect to a plurality of networks using the plurality of SIMs, the plurality of networks including a first network and a second network, and the terminal device is configured to transmit, to a base station device of the first network, information indicating whether the terminal device receives paging from the first network. A base station device according to the present disclosure is a base station device in a communication system including a plurality of networks including a first network and a second network, and a terminal device having a plurality of SIMs (Subscriber Identity Modules) and configured to connect to the plurality of networks using the plurality of SIMs, wherein the first network includes the base station device, and the base station device is configured to receive information from the terminal device indicating whether the terminal device receives paging from the first network. The communication system of the present disclosure is a communication system including a plurality of networks including a first network and a second network, and a terminal device having a plurality of SIMs (Subscriber Identity Modules) and configured to connect to the plurality of networks using the plurality of SIMs, wherein the first network includes a base station device, and the terminal device is configured to transmit, to the base station device, information indicating whether the terminal device receives paging from the first network. Effect of the Invention

[0060] According to the present disclosure, quick network connection is possible.

[0061] The objects, features, aspects, and advantages of the present disclosure will become more apparent from the following detailed description and the accompanying drawings. [Brief description of the drawings]

[0062] [Figure 1] FIG. 1 is an explanatory diagram showing the configuration of a radio frame used in an LTE communication system. [Diagram 2] 1 is a block diagram showing the overall configuration of a communication system 200 based on the LTE standard that is being discussed in 3GPP. [Diagram 3] FIG. 2 is a block diagram showing the overall configuration of a communication system 210 of the NR standard being discussed in 3GPP. [Figure 4] FIG. 1 is a diagram illustrating a DC configuration using eNBs and gNBs connected to an EPC. [Diagram 5] This is a diagram of a DC using gNB connected to an NG core. [Figure 6] This is a diagram showing the configuration of DC using eNBs and gNBs connected to the NG core. [Figure 7] This is a diagram showing the configuration of DC using eNBs and gNBs connected to the NG core. [Figure 8] FIG. 3 is a block diagram showing a configuration of a mobile terminal 202 shown in FIG. [Figure 9] FIG. 3 is a block diagram showing a configuration of a base station 203 shown in FIG. [Figure 10] FIG. 2 is a block diagram showing the configuration of an MME. [Figure 11] A block diagram showing the configuration of 5GC. [Figure 12] 1 is a flowchart showing an overview of operations from cell search to standby performed by a communication terminal (UE) in an LTE communication system. [Figure 13] FIG. 1 is a diagram showing an example of a cell configuration in an NR system. [Figure 14] FIG. 2 is an architecture diagram showing an example of a connection between a multi-SIM equipped UE and a plurality of networks according to the first embodiment. [Figure 15] FIG. 11 is a diagram showing a first example of allocation of timing priorities of paging from multiple networks and paging received by a UE in accordance with the first embodiment. [Figure 16] FIG. 11 is a diagram showing a second example of allocation of timing priorities of paging from multiple networks and paging received by a UE in accordance with the first embodiment. [Figure 17] FIG. 11 is a sequence diagram showing an example of the operation of stopping and restarting RLF timers associated with switching of a transmission / reception destination of a UE, according to the second embodiment. [Figure 18] FIG. 13 is a diagram illustrating an example of offsetting priority in a logical channel having a survival time requirement, in accordance with the first modification of the third embodiment. [Figure 19] FIG. 13 is a diagram illustrating an example of implicit control of the number of packet copies in a logical channel having a survival time requirement, in accordance with a second modification of the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0063] Embodiment 1 Fig. 2 is a block diagram showing the overall configuration of an LTE-based communication system 200 being discussed in 3GPP. Fig. 2 will now be described. The radio access network is called E-UTRAN (Evolved Universal Terrestrial Radio Access Network) 201. A mobile terminal device (hereinafter referred to as "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 "base station (E-UTRAN NodeB: eNB)") 203, and transmits and receives signals via wireless communication.

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

[0065] If control protocols for mobile terminals 202, such as RRC (Radio Resource Control), and user planes (hereinafter sometimes referred to as U-Planes), such as PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer), terminate in a base station 203, E-UTRAN is composed of one or more base stations 203.

[0066] A control protocol RRC (Radio Resource Control) between the mobile terminal 202 and the base station 203 performs broadcast, paging, RRC connection management, etc. The states of the base station 203 and the mobile terminal 202 in RRC include RRC_IDLE and RRC_CONNECTED.

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

[0068] The base station 203 is composed of one or more eNBs 207. A system composed of the core network EPC (Evolved Packet Core) and the radio access network E-UTRAN 201 is called an EPS (Evolved Packet System). The core network EPC and the radio access network E-UTRAN 201 are sometimes collectively called a "network."

[0069] The eNB207 is connected to a Mobility Management Entity (MME), or a Serving Gateway (S-GW), or an MME / S-GW unit (hereinafter sometimes referred to as an "MME unit") 204 including an MME and an S-GW via an S1 interface, and control information is communicated between the eNB207 and the MME unit 204. A plurality of MME units 204 may be connected to one eNB207. The eNBs 207 are connected to each other via an X2 interface, and control information is communicated between the eNBs 207.

[0070] The MME unit 204 is an upper device, specifically an upper node, and controls a connection between the eNB 207, which is a base station, and the mobile terminal (UE) 202. The MME unit 204 constitutes the EPC, which is a core network. The base station 203 constitutes the E-UTRAN 201.

[0071] The base station 203 may configure one cell or multiple cells. Each cell has a predetermined range as a coverage area in which communication with the mobile terminal 202 is possible, and performs wireless communication with the mobile terminal 202 within the coverage area. When one base station 203 configures multiple cells, each cell is configured to be able to communicate with the mobile terminal 202.

[0072] FIG. 3 is a block diagram showing the overall configuration of a 5G communication system 210 being discussed in 3GPP. FIG. 3 will be described. The radio access network is called NG-RAN (Next Generation Radio Access Network) 211. The UE 202 is capable of wireless communication with an NR base station device (hereinafter referred to as "NR base station (NG-RAN NodeB: gNB)") 213, and transmits and receives signals via wireless communication. The core network is called 5G Core (5G Core: 5GC).

[0073] If control protocols for UE202, such as RRC (Radio Resource Control), and user plane (hereinafter sometimes referred to as U-Plane), such as SDAP (Service Data Adaptation Protocol), PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer), terminate at the NR base station 213, the NG-RAN is composed of one or more NR base stations 213.

[0074] The function of the control protocol RRC (Radio Resource Control) between the UE 202 and the NR base station 213 is similar to that of LTE. The states of the NR base station 213 and the UE 202 in the RRC include RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.

[0075] RRC_IDLE and RRC_CONNECTED are the same as those in the LTE system. In RRC_INACTIVE, the connection between the 5G core and the NR base station 213 is maintained, and system information (SI) is reported, paging, cell re-selection, mobility, and the like are performed.

[0076] The gNB 217 is connected to an AMF / SMF / UPF unit (hereinafter sometimes referred to as a "5GC unit") 214 including an Access and Mobility Management Function (AMF), a Session Management Function (SMF), or a User Plane Function (UPF), or an AMF, SMF, and UPF, via an NG interface. Control information and / or user data are communicated between the gNB 217 and the 5GC unit 214. The NG interface is a collective term for the N2 interface between the gNB 217 and the AMF, the N3 interface between the gNB 217 and the UPF, the N11 interface between the AMF and the SMF, and the N4 interface between the UPF and the SMF. A plurality of 5GC units 214 may be connected to one gNB 217. The gNBs 217 are connected to each other via an Xn interface, and control information and / or user data are communicated between the gNBs 217.

[0077] The NR base station 213 may configure one or more cells, similar to the base station 203. When one NR base station 213 configures multiple cells, each of the cells is configured to be capable of communicating with the UE 202.

[0078] The gNB 217 may be divided into a central unit (hereinafter, sometimes referred to as CU) 218 ​​and a distributed unit (hereinafter, sometimes referred to as DU) 219. One CU 218 is configured in the gNB 217. One or more DUs 219 are configured in the gNB 217. The CU 218 is connected to the DU 219 by an F1 interface, and control information and / or user data are communicated between the CU 218 and the DU 219.

[0079] In a 5G communication system, a Unified Data Management (UDM) function and a Policy Control Function (PCF) described in Non-Patent Document 27 (3GPP TS23.501 V16.3.0) may be included. The UDM and / or PCF may be included in the 5GC unit in FIG.

[0080] In a 5G communication system, a non-3GPP interworking function (N3IWF) described in non-patent document 27 (3GPP TS23.501 V16.3.0) may be included. The N3IWF may terminate an access network (AN) between the UE and the N3IWF in a non-3GPP access between the UE and the N3IWF.

[0081] FIG. 4 is a diagram showing a configuration of DC by eNB and gNB connected to EPC. In FIG. 4, solid lines indicate U-Plane connections, and dashed lines indicate C-Plane connections. In FIG. 4, eNB223-1 is a master base station, and gNB224-2 is a secondary base station (this DC configuration may be referred to as EN-DC). In FIG. 4, an example is shown in which U-Plane connection between MME unit 204 and gNB224-2 is made via eNB223-1, but it may also be made directly between MME unit 204 and gNB224-2.

[0082] FIG. 5 is a diagram showing a DC configuration by a gNB connected to an NG core. In FIG. 5, a solid line indicates a U-Plane connection, and a dashed line indicates a C-Plane connection. In FIG. 5, gNB 224-1 is a master base station, and gNB 224-2 is a secondary base station (this DC configuration may be referred to as NR-DC). In FIG. 5, an example is shown in which a U-Plane connection between 5GC unit 214 and gNB 224-2 is made via gNB 224-1, but it may be made directly between 5GC unit 214 and gNB 224-2.

[0083] FIG. 6 is a diagram showing a configuration of DC by eNB and gNB connected to the NG core. In FIG. 6, a solid line indicates a U-Plane connection, and a dashed line indicates a C-Plane connection. In FIG. 6, eNB226-1 becomes a master base station, and gNB224-2 becomes a secondary base station (this DC configuration may be referred to as NG-EN-DC). In FIG. 6, an example is shown in which U-Plane connection between 5GC unit 214 and gNB224-2 is made via eNB226-1, but it may be made directly between 5GC unit 214 and gNB224-2.

[0084] FIG. 7 is a diagram showing another configuration of DC by eNB and gNB connected to the NG core. In FIG. 7, solid lines indicate U-Plane connections, and dashed lines indicate C-Plane connections. In FIG. 7, gNB224-1 is the master base station, and eNB226-2 is the secondary base station (this DC configuration may be referred to as NE-DC). In FIG. 7, an example is shown in which U-Plane connection between 5GC unit 214 and eNB226-2 is made via gNB224-1, but it may be made directly between 5GC unit 214 and eNB226-2.

[0085] FIG. 8 is a block diagram showing the configuration of the mobile terminal 202 shown in FIG. 2. The transmission process of the mobile terminal 202 shown in FIG. 8 will be described. First, the control data from the protocol processing unit 301 and the user data from the application unit 302 are stored in the transmission data buffer unit 303. The data stored in the transmission data buffer unit 303 is passed to the encoder unit 304, where encoding such as error correction is performed. There may be data that is directly output from the transmission data buffer unit 303 to the modulation unit 305 without encoding. The data that has been encoded by the encoder unit 304 is modulated by the modulation unit 305. Precoding in MIMO may be performed by the modulation unit 305. The modulated data is converted into a baseband signal, and then output to the frequency conversion unit 306, where it is converted into a radio transmission frequency. Thereafter, a transmission signal is transmitted from the antennas 307-1 to 307-4 to the base station 203. Although the case where the number of antennas is four is illustrated in FIG. 8, the number of antennas is not limited to four.

[0086] Moreover, the reception process of the mobile terminal 202 is executed as follows. Radio signals from the base station 203 are received by the antennas 307-1 to 307-4. The received signal is 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 perform weight calculation and multiplication. The demodulated data is passed to the decoder unit 309, where decoding such as error correction is performed. Of the decoded data, the control data is passed to the protocol processing unit 301, and the user data is passed to the application unit 302. A series of processes of the mobile terminal 202 is controlled by the control unit 310. Therefore, although the control unit 310 is omitted in FIG. 8, it is connected to each unit 301 to 309. In FIG. 8, 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.

[0087] FIG. 9 is a block diagram showing the configuration of the base station 203 shown in FIG. 2. The transmission process of the base station 203 shown in FIG. 9 will be described. The EPC communication unit 401 transmits and receives data between the base station 203 and the EPC (such as the MME unit 204). The 5GC communication unit 412 transmits and receives data between the base station 203 and the 5GC (such as the 5GC unit 214). The other base station communication unit 402 transmits and receives data between the base station 203 and the 5GC. The EPC communication unit 401, the 5GC communication unit 412, and the other base station communication unit 402 each transmit and receive information to and from the protocol processing unit 403. The control data from the protocol processing unit 403, and the 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 stored in the transmission data buffer unit 404.

[0088] The data stored in the transmission data buffer unit 404 is passed to the encoder unit 405, where it is subjected to encoding such as error correction. There may be data that is directly output from the transmission data buffer unit 404 to the modulation unit 406 without being subjected to encoding. The encoded data is modulated by the modulation unit 406. The modulation unit 406 may 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. Thereafter, a transmission signal is transmitted to one or more mobile terminals 202 from the antennas 408-1 to 408-4. Although the case where the number of antennas is four is illustrated in FIG. 9, the number of antennas is not limited to four.

[0089] The reception process of the base station 203 is executed as follows. A radio signal from one or more mobile terminals 202 is received by the antenna 408. 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 such as error correction is performed. Of the decoded data, the control data is passed to the protocol processing unit 403 or the 5GC communication unit 412 or the EPC communication unit 401 and the other base station communication unit 402, and the user data is passed to the 5GC communication unit 412, the EPC communication unit 401, and the other base station communication unit 402. A series of processes of the base station 203 is controlled by the control unit 411. Therefore, although the control unit 411 is omitted in FIG. 9, it is connected to each unit 401 to 410. In FIG. 9, the number of antennas used by the base station 203 for transmission and the number of antennas used for reception may be the same or different.

[0090] Fig. 9 is a block diagram showing the configuration of base station 203, but base station 213 may have a similar configuration. In addition, in Fig. 8 and Fig. 9, the number of antennas of mobile terminal 202 and the number of antennas of base station 203 may be the same or different.

[0091] FIG. 10 is a block diagram showing the configuration of an MME. FIG. 10 shows the configuration of the MME 204a included in the MME unit 204 shown in FIG. 2 described above. The PDN GW communication unit 501 transmits and receives data between the MME 204a and the PDN GW. The base station communication unit 502 transmits and receives data between the MME 204a and the base station 203 via the S1 interface. If the data received from the PDN GW is user data, the user data is passed from the PDN GW communication unit 501 to the base station communication unit 502 via the user plane communication unit 503 and transmitted to one or more base stations 203. If the data received from the base station 203 is user data, the user data is passed from the base station communication unit 502 to the PDN GW communication unit 501 via the user plane communication unit 503 and transmitted to the PDN GW.

[0092] When the data received from the PDN GW is control data, the control data is passed from the PDN GW communication unit 501 to the control plane control unit 505. When the data received from the base station 203 is control data, the control data is passed from the base station communication unit 502 to the control plane control unit 505.

[0093] The control plane control unit 505 includes a NAS security unit 505-1, an SAE bearer control unit 505-2, an idle state mobility management unit 505-3, etc., and performs general processing for the control plane (hereinafter, sometimes referred to as C-Plane). The NAS security unit 505-1 performs security for NAS (Non-Access Stratum) messages, etc. The SAE bearer control unit 505-2 performs management of SAE (System Architecture Evolution) bearers, etc. The idle state mobility management unit 505-3 performs mobility management in the idle state (also called the LTE-IDLE state or simply idle), generation and control of paging signals in the idle state, addition, deletion, update, search, and tracking area list management of one or more mobile terminals 202 under its control.

[0094] The MME 204a distributes a paging signal to one or more base stations 203. The MME 204a also performs mobility control in an idle state. The MME 204a manages a tracking area list when a mobile terminal is in an idle state and in an active state. The MME 204a initiates a paging protocol by transmitting a paging message to a cell that belongs to a tracking area in which the UE is registered. The idle state mobility management unit 505-3 may manage the CSG, CSG ID, and whitelist of the eNB 207 connected to the MME 204a.

[0095] FIG. 11 is a block diagram showing the configuration of 5GC. FIG. 11 shows the configuration of the 5GC unit 214 shown in FIG. 3 described above. FIG. 11 shows the case where the 5GC unit 214 shown in FIG. 5 includes the AMF configuration, the SMF configuration, and the UPF configuration. 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 S1 interface between the 5GC unit 214 and the base station 203, and / or the NG interface between the 5GC unit 214 and the base station 213. If the data received from the Data Network is user data, the user data is passed from the Data Network communication unit 521 to the base station communication unit 522 via the user plane communication unit 523, and is transmitted to one or more base stations 203 and / or base stations 213. If the data received from base station 203 and / or base station 213 is user data, the user data is passed from base station communication unit 522 to Data Network communication unit 521 via user plane communication unit 523 and transmitted to the Data Network.

[0096] If the data received from the Data Network is control data, the control data is passed 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 passes the control data to the control plane control unit 525. If the data received from the base station 203 and / or base station 213 is control data, the control data is passed from the base station communication unit 522 to the control plane control unit 525. The control plane control unit 525 passes the control data to the session management unit 527.

[0097] The control plane control unit 525 includes a NAS security unit 525-1, a PDU session control unit 525-2, an idle state mobility management unit 525-3, etc., and performs general processing for the control plane (hereinafter, sometimes referred to as C-Plane). The NAS security unit 525-1 performs security for NAS (Non-Access Stratum) messages, etc. The PDU session control unit 525-2 performs management of PDU sessions between the mobile terminal 202 and the 5GC unit 214, etc. The idle state mobility management unit 525-3 performs mobility management in a standby state (also called an idle state; RRC_IDLE state, or simply idle), generation and control of paging signals in a standby state, addition, deletion, update, search, tracking area list management, etc. of one or more mobile terminals 202 under its umbrella.

[0098] The 5GC unit 214 distributes paging signals to one or more base stations 203 and / or base station 213. The 5GC unit 214 also performs mobility control in an idle state. The 5GC unit 214 manages a tracking area list when the mobile terminal is in an idle state, an inactive state, and an active state. The 5GC unit 214 initiates a paging protocol by transmitting a paging message to a cell belonging to a tracking area in which the UE is registered.

[0099] Next, an example of a cell search method in a communication system is shown. Fig. 12 is a flow chart showing an outline of a process from cell search to standby operation performed by a communication terminal (UE) in an LTE communication system. When the communication terminal starts a cell search, in step ST601, the communication terminal 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.

[0100] P-SS and S-SS are collectively called the Synchronization Signal (SS). The Synchronization Signal (SS) is assigned a synchronization code that corresponds one-to-one to the PCI assigned to each cell. 504 different PCIs are being considered. These 504 different PCIs are used to achieve synchronization and to detect (identify) the PCI of the synchronized cell.

[0101] Next, in step ST602, for the synchronized cell, a cell-specific reference signal (CRS), which is a reference signal (RS) transmitted from the base station for each cell, is detected and the RS received power (Reference Signal Received Power: RSRP) is measured. A code that has a one-to-one correspondence with the PCI is used for the reference signal (RS). By correlating with the code, it is possible to separate the cell from other cells. By deriving the code for the RS of the cell from the PCI identified in step ST601, it is possible to detect the RS and measure the RS received power.

[0102] Next, in step ST603, the cell with the best RS reception quality, for example the cell with the highest RS reception power, that is, the best cell, is selected from among one or more cells detected up to step ST602.

[0103] Next, in step ST604, the PBCH of the best cell is received to obtain a BCCH, which is broadcast information. A MIB (Master Information Block), which includes 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 DL (downlink) system bandwidth (also called transmission bandwidth configuration: dl-bandwidth), the number of transmitting antennas, SFN (System Frame Number), and the like.

[0104] Next, in step ST605, the DL-SCH of the cell is received based on the cell configuration information in the MIB, and SIB (System Information Block) 1 in the broadcast information BCCH is obtained. SIB 1 includes information on access to the cell, information on cell selection, and scheduling information of other SIBs (SIBk; k is an integer ≧2). SIB 1 also includes a tracking area code (TAC).

[0105] Next, in step ST606, the communication terminal compares the TAC of the SIB1 received in step ST605 with the TAC portion of the tracking area identity (TAI) in the tracking area list that the communication terminal already holds. The tracking area list is also called a TAI list. The TAI is identification information for identifying a tracking area, and is composed of a 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 code number of the tracking area.

[0106] If the TAC received in step ST605 is the same as the TAC included in the tracking area list as a result of the comparison in step ST606, the communication terminal enters standby mode in the cell. If the TAC received in step ST605 is not included in the tracking area list as a result of the comparison, the communication terminal requests a core network (EPC) including an MME, etc., to change the tracking area in order to perform a Tracking Area Update (TAU) through the cell.

[0107] In the example shown in FIG. 12, an example of operations from cell search to standby in the LTE system is shown, but in the NR system, in addition to the best cell, the best beam may be selected in step ST603. Also, in the NR system, beam information, for example, a beam identifier, may be acquired in step ST604. Also, in the NR system, scheduling information of Remaining Minimum SI (RMSI) may be acquired in step ST604. In the NR system, RMSI may be received in step ST605.

[0108] An apparatus constituting a core network (hereinafter sometimes referred to as a "core network side apparatus") updates the tracking area list based on an identification number (such as a UE-ID) of a 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. After that, the communication terminal enters standby mode in the cell.

[0109] The spread of smartphones and tablet terminal devices has led to an explosive increase in traffic via cellular wireless communications, raising concerns about a shortage of wireless resources around the world. In response to this, efforts are being made to create smaller cells and promote spatial separation in order to improve frequency utilization efficiency.

[0110] In a conventional cell configuration, a cell configured by an eNB has a relatively wide coverage area. Conventionally, a cell is configured to cover a certain area by the relatively wide coverage areas of a plurality of cells configured by a plurality of eNBs.

[0111] In the case of small cell configuration, the cell configured by the eNB has a narrower coverage range than the coverage of the cell configured by the conventional eNB. Therefore, as in the past, in order to cover a certain area, a large number of small cell eNBs are required compared to the conventional eNBs.

[0112] In the following description, a cell with a relatively large coverage, such as a cell configured by a conventional eNB, is referred to as a "macro cell," and an eNB that configures the macro cell is referred to as a "macro eNB." Also, a cell with a relatively small coverage, such as a cell that has been made into a small cell, is referred to as a "small cell," and an eNB that configures the small cell is referred to as a "small eNB."

[0113] The macro eNB may be, for example, a “Wide Area Base Station” as described in Non-Patent Document 7.

[0114] The small eNB may be, for example, a low power node, a local area node, a hotspot, etc. Also, the small eNB may be a pico eNB constituting a pico cell, a femto eNB constituting a femto cell, a HeNB, a remote radio head (RRH), a remote radio unit (RRU), a remote radio equipment (RRE), or a relay node (RN). Also, the small eNB may be a "local area base station" or a "home base station" as described in Non-Patent Document 7.

[0115] FIG. 13 shows an example of a cell configuration in NR. In an NR cell, a narrow beam is formed and transmitted while changing the direction. In the example shown in FIG. 13, at a certain time, the base station 750 transmits and receives with a mobile terminal using a beam 751-1. At another time, the base station 750 transmits and receives with a mobile terminal using a beam 751-2. In the same manner, the base station 750 transmits and receives with a mobile terminal using one or more of the beams 751-3 to 751-8. In this way, the base station 750 configures a wide-range cell.

[0116] 13 shows an example in which the number of beams used by the base station 750 is eight, but the number of beams may be different from eight. Also, in the example shown in FIG. 13, the number of beams used simultaneously by the base station 750 is one, but it may be multiple.

[0117] A UE may be connected to or connectable to multiple networks. Hereinafter, "connected" may include not only an actual connected state but also a connectable state. A UE may connect to the multiple networks using multiple SIMs. The UE may have only one pair of transceivers or multiple pairs of transceivers. The multiple networks may be PLMNs, non-public networks (NPNs), or private networks. The connections to the multiple networks may be made in parallel.

[0118] With respect to the connection between the UE and each NW, the RRC state of the UE may be an RRC_CONNECTED state, an RRC_INACTIVE state, or an RRC_IDLE state. The CM state of the UE may be a CM-IDLE state or a CM-CONNECTED state. The UE may be in an RRC_CONNECTED state or a CM-CONNECTED state for two or more of the multiple NWs to which it is connected. As another example, the UE may be in an RRC_CONNECTED state or a CM-CONNECTED state for only one of the multiple NWs to which it is connected.

[0119] Fig. 14 is an architecture diagram showing an example of a connection between a UE using multiple SIMs (hereinafter, sometimes referred to as a multi-SIM UE) and multiple networks. In Fig. 14, the multi-SIM UE is connected in parallel to NW#1 and NW#2.

[0120] In the example shown in FIG. 14, UE 1400 connects to gNB 1401 in NW #1. UE 1400 also connects to gNB 1411 in NW #2. gNB 1401 connects to AMF 1402 and UPF 1403 in NW #1. SMF 1404 in NW #1 connects to AMF 1402 and UPF 1403. gNB 1411 connects to AMF 1412 and UPF 1413 in NW #2. SMF 1414 in NW #2 connects to AMF 1412 and UPF 1413.

[0121] 14 shows an example in which UE 1400 is connected to two networks, but UE 1400 may be connected to three or more networks. In addition, one or more of the two networks connected to UE 1400 may be an NPN. The same may be true in the case in which UE 1400 is connected to three or more networks.

[0122] In a UE connected to multiple networks in parallel, overlapping of paging timing may occur (hereinafter, may be referred to as paging collision). A UE in which paging collision occurs may be a UE having only one pair of a transceiver. In this case, the UE can receive paging from only one of the networks. Therefore, for example, when paging for emergency communication such as ETWS or CMAS is included in the paging that collide with each other, the UE may not be able to receive the paging for the emergency communication. As a result, a problem occurs in that the UE cannot promptly receive the emergency communication.

[0123] In the first embodiment, a method for solving the above-mentioned problem will be disclosed.

[0124] Priorities are assigned to timings at which paging may be transmitted. Such priorities may hereinafter be referred to as timing priorities. Priorities are assigned to types of paging. Such priorities may hereinafter be referred to as type priorities.

[0125] The timing priority may be, for example, two levels, or three or more levels. A parameter relating to the timing priority may be provided.

[0126] The type priority may be, for example, two stages or three or more stages. A parameter related to the type priority may be provided.

[0127] The timing priority and the type priority are associated with each other. For example, when both the timing priority and the type priority are configured in two stages, a high timing priority may be associated with a high type priority, and a low timing priority may be associated with a low type priority. At a paging timing of a predetermined timing priority, a paging of a predetermined type priority may be transmitted. For example, at a certain paging transmission timing, a paging of a type priority equal to or lower than the timing priority associated with the timing priority may be transmitted. When paging timings from base stations of a plurality of networks collide, the UE may receive a paging of a high timing priority among the colliding pagings. When receiving a paging of a high timing priority, the UE may switch the network of the transmission / reception destination. The connection between the UE and the base station of the transmission / reception destination network may be RRC_CONNECTED, RRC_INACTIVE, or RRC_IDLE. This allows the UE to receive, for example, a paging related to emergency communication in priority to other paging.

[0128] As another example, a high type priority may be sent with a low timing priority. The above operation may be applied, for example, when a paging with a certain timing priority cannot be received due to a timing collision with a paging with a higher timing priority from another network. This allows, for example, a prompt reception of a paging with a certain timing priority in the above case.

[0129] The UE may expect that a paging with a type priority equal to or lower than the timing priority at the paging timing is transmitted. That is, the UE may expect that a paging with a type priority higher than the timing priority at the paging timing is not transmitted. In the above, a type priority equal to or lower than the timing priority may be a type priority lower than the timing priority, and a paging with a type priority higher than the timing priority may be a paging with a type priority equal to or higher than the timing priority.

[0130] As an example of timing priority allocation, when the timing priority is divided into two stages, a high timing priority and a low timing priority may be alternately assigned for each Paging Frame (PF). A high timing priority and a low timing priority may be alternately assigned for each Paging Occasion (PO). A high timing priority and a low timing priority may be alternately assigned for each PDCCH monitoring occasion used for paging reception.

[0131] The paging to which the type priority is assigned may be paging for downlink data or paging for voice calls. The paging for voice calls may be paging for normal incoming calls or paging for return voice calls from voice calls for emergency calls. The paging to which the type priority is assigned may be paging for SI update or paging for emergency calls, as another example. The emergency calls may be, for example, a PWS (Public Warning System). The emergency calls may be, for example, an ETWS (Earthquake and Tsunami Warning System), a CMAS (Commercial Mobile Alert System), an EU-ALERT (European Public Warning System), a KPAS (Korean Public Alert System), or other emergency calls.

[0132] An emergency communication for a private network (or a non-public network) may be provided. The emergency communication for a private network may be included in the above-mentioned emergency communication. This enables, for example, a quick notification to a UE of a trouble in a premises where a private network is applied.

[0133] As an example of the assignment of type priority, in a case where there are two levels of type priority, a high priority may be assigned to emergency communication and SI update paging, and a low priority may be assigned to other paging. As another example, in a case where there are three levels of type priority, a high priority may be assigned to emergency communication, a medium priority may be assigned to SI update and voice calls, and a low priority may be assigned to other paging.

[0134] The number of stages of the timing priority and the type priority may be the same. This makes it possible to avoid, for example, complexity in associating the timing priority and the type priority. As another example, the number of stages of the timing priority and the type priority may be different. This makes it possible, for example, to improve the flexibility of associating the timing priority and the type priority.

[0135] Timing priority may be assigned for each Paging Frame (PF). This allows, for example, a network device to assign timing priority with a small amount of processing. As another example, timing priority may be assigned for each Paging Occasion (PO). This allows, for example, improved flexibility in assigning timing priority. As another example, timing priority may be assigned for each PDCCH monitoring occasion used for paging reception. This allows, for example, further improved flexibility in assigning timing priority.

[0136] As another example, the timing priority may be assigned for each DRX cycle, which may reduce the amount of processing required for timing priority assignment, for example.

[0137] The allocation of timing priorities may be determined by standards, which may allow, for example, avoiding design complexity in communication systems.

[0138] As another example, the core NW may determine the allocation of timing priority. This allows, for example, improved flexibility in the allocation of timing priority. The core NW may be, for example, an AMF or a PCF. The core NW may notify the base station of information regarding the determined allocation. The base station may notify the UE of the information regarding the allocation individually or may broadcast it. As another example of notifying the information regarding the allocation, the core NW may directly notify the UE. For example, the AMF may notify the UE of the information using NAS signaling.

[0139] As another example of the allocation of timing priorities, the base station may determine the allocation, which may allow, for example, further flexibility in the allocation of timing priorities. The base station may notify or broadcast information about the allocation to the UEs.

[0140] A parameter for determining the timing priority may be provided. The parameter may be, for example, a UE identifier, or may be a parameter similar to the PCCH configuration information (PCCH-Config) disclosed in Non-Patent Document 22 (TS38.331). A method for obtaining the timing priority from the parameter may be defined by a standard. This makes it possible to reduce the size of notification of information required for determining the timing priority, for example.

[0141] The value of the parameter may be determined by each NW and notified to the UE. The notification may be performed via a base station. As another example, the value of the parameter may be determined by a base station and notified or broadcast to the UE. As another example, the value of the parameter may be determined for each cell.

[0142] An average value of the timing priority may be set. For example, the average value may be the same between networks or between base stations. This makes it possible to prevent, for example, the paging reception destination of a UE from being biased toward a specific network.

[0143] As another example, the average value may be different between networks. This allows, for example, adjustment between networks regarding ease of paging reception for UE. As another example, the average value may be different between base stations. This allows, for example, adjustment between base stations regarding ease of paging reception for UE.

[0144] Similarly to the allocation of timing priorities, the average value of the timing priorities may be determined by a standard, by the core network, or by the base station.

[0145] The following (1) to (8) are disclosed as examples of information regarding allocation of timing priority that the core NW and / or base station notifies or broadcasts to the UE.

[0146] (1) Information regarding the number of stages of timing priority.

[0147] (2) Timing priority value.

[0148] (3) Information regarding paging timing.

[0149] (4) Information regarding timing priority allocation patterns.

[0150] (5) Information regarding the period of timing priority assignment.

[0151] (6) Reference paging timing.

[0152] (7) Information for determining paging timing for each timing priority.

[0153] (8) A combination of (1) to (7) above.

[0154] The number of stages in the above (1) may be, for example, 2, or 3 or more. For example, when no timing priority is assigned, the number of stages in the above (1) may be 1. The UE may obtain the number of stages of the timing priority using the information in the above (1). This makes it possible to reduce the amount of processing required for the UE to grasp the assignment of timing priority, for example.

[0155] The information in (2) above may be, for example, information indicating whether the priority level is high or low when the number of stages in (1) above is 2. The UE may obtain the timing priority level by using the information in (2) above. This makes it possible to reduce the amount of processing required for the UE to grasp the allocation of timing priorities, for example.

[0156] The above-mentioned information (3) may be, for example, information indicating the ordinal number of the PF among the PFs in the DRX cycle. Alternatively, the above-mentioned information (3) may be, for example, information indicating the ordinal number of the PO among the POs in the PF. Alternatively, the above-mentioned information (3) may be, for example, information indicating the ordinal number of the PDCCH monitoring occasion for paging among the PDCCH monitoring occasions for paging in the PO. As another example, the above-mentioned information (3) may be information indicating the ordinal number of the PO or the PDCCH monitoring occasion for paging among the POs or the PDCCH monitoring occasions for paging in the DRX cycle. For example, the above-mentioned information (3) enables the UE to quickly grasp the paging timing to which a predetermined timing priority is assigned.

[0157] As another example, the information in (3) above may include a parameter used to determine paging timing. The parameter may include a part or all of the broadcast information from the base station of the network, for example, PCCH setting information (PCCH-Config) disclosed in Non-Patent Document 22 (TS38.331). This makes it possible to reduce the amount of processing by the base station when notifying the UE from the base station, for example.

[0158] The information in (4) above may be, for example, information indicating a pattern in which, in the case of two-stage timing priority, a high timing priority and a low timing priority are alternately assigned to each PF. Alternatively, the information in (4) above may be information indicating a pattern in which a high timing priority is assigned twice in succession, followed by a low timing priority is assigned twice in succession, and this is repeated. The PF in the above may be a PO or a PDCCH monitoring occasion for paging. For example, the information in (4) above enables a UE to quickly grasp the assignment of timing priorities.

[0159] The information (5) above may be, for example, information about the cycle of the pattern (4) above. The information (5) above may be given in a cycle different from the DRX cycle. For example, the cycle of the timing priority allocation pattern may span a plurality of DRX cycles. This makes it possible to avoid a situation in which, for example, paging at a certain paging timing in a certain network cannot always be received because the timing priority is lower than the paging timing in another network.

[0160] The information in (6) above may be information on a paging timing to which a high timing priority is assigned when, for example, a high timing priority and a low timing priority are assigned alternately to each PF. The information in (6) above may include information on a timing priority in a reference paging timing. This makes it possible to prevent, for example, discrepancies in the recognition of timing priority assignment between a base station and a UE. As a result, it is possible to improve the stability of the operation in the communication system.

[0161] The information in (7) above may be information indicating, for example, which PF, PO, or PDCCH monitoring occasion for paging is assigned in a DRX cycle for each timing priority. The DRX cycle may be a PF or a PO. The information in (7) above allows, for example, a UE to quickly grasp a paging timing to which a predetermined timing priority is assigned.

[0162] As another example, the information in (7) above may include parameters used to determine paging timing for each timing priority. The parameters may include a part or all of the broadcast information from the base station of the network, for example, PCCH setting information (PCCH-Config) disclosed in Non-Patent Document 22 (TS38.331). This makes it possible to improve the flexibility of paging timing setting in a communication system, for example.

[0163] The correspondence between the timing priority and the type priority may be determined by a standard. For example, the message identifier disclosed in section 9.4.1.2.2 of non-patent document 21 (TS23.041 V16.2.0) may be used to determine the correspondence. This makes it possible to avoid design complexity in a communication system, for example.

[0164] As another example, the core NW may determine the correspondence between the timing priority and the type priority. This allows, for example, improved flexibility in the correspondence between the two priorities. The core NW may be, for example, an AMF or a PCF. The core NW may notify the base station of information on the determined correspondence. The base station may notify the UE of the information on the correspondence individually or may broadcast it. As another example, the core NW may directly notify the UE of the information. For example, the AMF may notify the UE of the information by using NAS signaling.

[0165] As another example, the base station may determine the correspondence between the timing priority and the type priority. This allows, for example, further improvement in flexibility regarding the correspondence between the two priorities. The base station may notify the UE of the information regarding the correspondence individually or may broadcast it.

[0166] As another example of the correspondence between the timing priority and the type priority, the above combination may be used. For example, the type priority corresponding to each timing priority may have a predetermined range in the standard, and the core NW may determine the correspondence using the predetermined range in the standard. This makes it possible to flexibly perform the correspondence in the communication system, for example.

[0167] The assignment of type priorities may be determined by a standard. For example, the message identifier disclosed in section 9.4.1.2.2 of non-patent document 21 (TS23.041 V16.2.0) may be used for the assignment. This makes it possible to avoid complexity in the design of a communication system, for example.

[0168] As another example, the core NW may determine the allocation of type priorities. This allows, for example, improved flexibility in the allocation of type priorities. The core NW may be, for example, an AMF or a PCF. The core NW may notify the base station of information on the determined allocation. The base station may notify the UE of the information on the allocation individually or may broadcast it. As another example of notifying the information on the allocation, the core NW may directly notify the UE. For example, the AMF may notify the UE of the information by using NAS signaling.

[0169] As another example of the assignment of type priority, the base station may determine the assignment. This allows, for example, further improvement in the flexibility of the assignment of type priority. The base station may notify the UE of the information on the assignment individually or may broadcast it.

[0170] As another example of the type priority assignment, the above combination may be used. For example, the type priority assigned to each type of paging may have a predetermined range in the standard, and the core NW may determine the type priority using the predetermined range in the standard. This makes it possible to flexibly assign the type priority of paging in the communication system, for example.

[0171] The UE receives a paging with a high timing priority among the paging of multiple networks with timing collisions. The UE may perform this operation when the UE has a single receiver. The UE may switch the receiving network when receiving a paging with a high timing priority. This allows the UE to receive a paging with a high priority among multiple paging with timing collisions, for example.

[0172] The UE may receive only the paging with the highest timing priority among the paging messages from multiple networks whose timings collide. This makes it possible to reduce the power consumption of the UE, for example.

[0173] The UE may notify the base station of information about a paging that is not received (hereinafter, may be referred to as a non-received paging). The information may include information about a paging from another NW (hereinafter, may be referred to as a colliding NW) that collides with the non-received paging (hereinafter, may be referred to as a colliding NW paging).

[0174] As examples of information regarding non-received paging, the following (1) to (15) are disclosed.

[0175] (1) Information regarding the timing of missed pages.

[0176] (2) Information regarding the timing priority of unreceived pages.

[0177] (3) Information regarding the identifier of the colliding network.

[0178] (4) Information regarding the timing of collision NW paging.

[0179] (5) Information on numerology in the collision network.

[0180] (6) Information regarding frame timing in the collision network.

[0181] (7) Information used to derive the timing of collision network paging.

[0182] (8) Information about the beam used for communication with the collision network.

[0183] (9) Information regarding the synchronization signal of the collision network.

[0184] (10) Information regarding the Radio Access Technology (RAT) of the conflicting network.

[0185] (11) Information regarding timing priority of paging in a collision network.

[0186] (12) Information regarding the operation of multiple SIMs in the UE.

[0187] (13) Information indicating a request for a setting change regarding non-received paging.

[0188] (14) Information regarding type priority.

[0189] (15) A combination of (1) to (14) above.

[0190] The information (1) above may be information indicating which PF, PO, or PDCCH monitoring occasion for paging in a DRX cycle is a non-received paging. The information (1) above may be information using the frame number, subframe number, slot number, or symbol number of the non-received paging. This allows, for example, a quick notification from the UE to the base station.

[0191] The information in (2) above may be the same as the information on timing priority allocation that the core network and / or base station notifies or reports to the UE, disclosed in (2). The information in (2) above makes it possible to reduce the amount of processing required for the base station to redo the allocation of timing priority, for example.

[0192] The information (3) above may be, for example, the PLMN-ID of the other network, may include the NPN-ID disclosed in Non-Patent Document 25 (TR23.734), or may include the CAG-ID. This allows, for example, the base station to know the network for which paging collision should be avoided, and as a result, the complexity of the avoidance process can be avoided.

[0193] As another example of the information of (3) above, an identifier that uniquely identifies the UE may be used. The identifier may be, for example, a 5G Globally Unique Temporary Identifier (5G-GUTI). The base station may extract the PLMN-ID of the other NW from the 5G-GUTI. This allows the base station to simultaneously obtain, for example, the identifier of the other NW and the identifier of the UE. As a result, the base station can obtain information used to derive paging timing in the other NW with less signaling.

[0194] The information in (4) above may be, for example, a paging frame (PF) in another network, a paging occasion (PO), a PDCCH monitoring occasion used for paging reception, or a combination of a plurality of the above. This makes it possible to reduce the amount of processing required for avoiding paging collisions by the base station, for example.

[0195] As another example, the information (4) above may include information about the time of paging timing in another network. The information about the time may include, for example, the time at the start point of the paging timing, the time at the end point of the paging timing, information about the duration of the paging timing, or a combination of multiple pieces of information from among the above. The paging timing may be a paging frame (PF) or a paging occasion (PO) in the other network, a PDCCH monitoring occasion used for paging reception, or a combination of multiple pieces of information from among the above. This makes it possible to reduce the amount of processing in avoiding paging collisions by a base station, for example.

[0196] The information in (5) above may be, for example, a subcarrier interval, a slot length, or a symbol length used by the UE when receiving paging from another network. The information in (5) above may be a parameter μ disclosed in Section 4.2 of Non-Patent Document 13 (TS38.211). This makes it possible to improve the reliability of paging collision avoidance by the base station, for example.

[0197] The information in (6) above may be, for example, the difference in frame timing between the notification destination base station and the base station of another network given in SFN units, subframe units, slot units, symbol units, or the smallest unit in the communication system (for example, Ts units), or may be a combination of these. The slot in the above may be a slot in the notification destination base station or a slot in another network. This makes it possible to reduce the amount of processing in paging collision avoidance by the base station, for example.

[0198] As another example, the information in (6) above may be a predetermined time point in the other network, for example, the time at a boundary of a predetermined SFN. The boundary may be the beginning of the SFN, or the end of the SFN. As another example, the information in (6) above may be the time at a predetermined subframe boundary, the time at a predetermined slot boundary, or the time at a predetermined symbol boundary. The UE may obtain the information by a cell search for the other network, or may obtain the information from broadcast information from the other network. This makes it possible to reduce, for example, the amount of processing required for the notification by the UE.

[0199] The information in (7) above may include, for example, an identifier of the UE in another network, or may include a parameter used to determine paging timing in the other network. The parameter may include a part or all of the broadcast information from the base station of the network, for example, PCCH setting information (PCCH-Config) disclosed in Non-Patent Document 22 (TS38.331). This makes it possible to reduce, for example, the amount of processing required for the notification from the UE.

[0200] The identifier for the information (7) may be, for example, the UE_ID disclosed in section 7.1 of non-patent document 26 (TS38.304), or the 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier), 5G-TMSI (5G Temporary Mobile Subscription Identifier), or 5G-GUTI disclosed in non-patent document 27 (TS23.501).

[0201] The above-mentioned parameters relating to the information (7) may include the UE's Discontinuous Reception (DRX) period (T), the total number of paging frames in the period (N), the number of paging occasions in the PF (Ns), an offset (PF_offset) used in determining the PF, or the first PDCCH monitoring occasion in the PO (first-PDCCH-MonitoringOccasionOfPO), as disclosed in Non-Patent Document 26 (TS38.304).

[0202] The information in (8) above may be information about a beam that the UE uses to receive from the notified base station. The beam may be information about a beam that the UE uses to receive SS blocks from the base station. The beam may be information about a beam that the UE uses to receive broadcast information from the base station, for example, SIB1 or RMSI (Remaining Minimum System Information). The base station may use the information in (8) above to change the paging timing in the beam in which the UE is located. The base station may change the broadcast information in the beam. This allows the base station to flexibly change the paging timing, for example.

[0203] The information in (9) above may be, for example, information about the period of an SS burst, or may be the SS block transmission duration in one period of an SS burst. The base station may use the information in (9) above to set paging timing, for example, by avoiding multiple SS burst periods transmitted from a base station of another NW, or may set paging timing by avoiding the SS block transmission duration. The UE may use the information to receive a synchronization signal from a base station of another NW. The UE may receive paging after receiving the synchronization signal. This makes it possible to prevent, for example, timing deviation in the UE's paging reception.

[0204] The information of (10) above may be, for example, information indicating that the base station of the other network is an NR base station, or may be information indicating that the base station is an LTE base station. The base station may use the information to change the paging timing. For example, when the base station of the other network is an LTE base station and the paging timing in the LTE base station is fixed, the base station may change the period of the paging timing. This makes it possible to reduce, for example, the possibility of failing to avoid paging collisions in the communication system.

[0205] The information in (11) above may be, for example, a value of the timing priority of a paging that collides with a non-received paging, or may be information about a timing priority assigned to a paging from a base station of another network. The base station may use the information in (11) above to change the timing priority of a non-received paging, or may change the allocation of timing priority to the paging of the base station. This makes it possible to reduce, for example, the possibility of failing to avoid paging collision in a communication system.

[0206] The information in (12) above may be, for example, information indicating whether the UE is a UE with multiple SIMs, or may be information regarding operation using multiple SIMs. The information regarding operation using multiple SIMs may include, for example, the number of transmitters and / or receivers in the UE, the number of networks to which the UE can connect, or the number of RRCs that the UE can hold. The information regarding operation using multiple SIMs may be information regarding a combination of RRC states in the UE, for example, information indicating whether the UE can be RRC_CONNECTED simultaneously with multiple base stations among the base stations of multiple networks. The UE may notify the base station of the information, for example, by including the information in UE capabilities. The base station may use the information for data transmission and reception between the UE. This makes it possible to improve the efficiency in the communication system, for example.

[0207] The information of (13) above may be, for example, information requesting a change in paging timing in the base station, information requesting a change in allocation of paging timing priority in the base station, information requesting a change in the correspondence between paging timing priority and type priority, or a method combining two or more of the above. The base station may use the information to change the paging timing, change the allocation of paging timing priority, or change the allocation of paging timing priority and type priority. This makes it possible to reduce the amount of processing related to the above-mentioned setting change in the base station, for example.

[0208] The information in (14) above may be, for example, information indicating a correspondence relationship between paging timing priority and type priority in a collision network, or may be similar information in the own network. The base station may change the timing of paging, may change the allocation of paging timing priority, or may change the allocation of paging timing priority and type priority using the information in (14) above. This makes it possible to reduce the amount of processing related to the above-mentioned setting changes in the base station, for example.

[0209] The UE may notify the base station of information regarding non-received paging by using RRC signaling. For example, the UE may use an RRC Setup Request for the notification. When the RRC state regarding the connection with the base station is RRC_IDLE, the UE may use the signaling of the RRC Setup Request for the notification. This allows, for example, the UE to quickly execute the notification to the base station. As another example, the UE may use an RRC Setup Complete for the notification. When the RRC state regarding the connection with the base station transitions from RRC_IDLE to RRC_CONNECTED, the UE may use the signaling of the RRC Setup Complete for the notification. This allows, for example, the UE to notify the base station including a lot of information.

[0210] As another example, the UE may use an RRC Resume Request (RRCResumeRequest) for the notification. When the RRC state related to the connection with the base station is RRC_INACTIVE, the UE may use signaling of an RRC Resume Request for the notification. This allows, for example, the UE to quickly execute the notification to the base station. As another example, the UE may use an RRC Resume Complete (RRCResumeComplete) for the notification. When the RRC state related to the connection with the base station transitions from RRC_INACTIVE to RRC_CONNECTED, the UE may use signaling of an RRC Resume Complete for the notification. This allows, for example, the UE to notify the base station including a lot of information.

[0211] As another example, the UE may use RRCReconfigurationComplete for the notification, which allows the UE to notify the base station of a large amount of information.

[0212] As another example, new RRC signaling may be provided. For example, signaling called RRC reconfiguration request may be provided and used, or signaling called paging configuration information notification may be provided and used.

[0213] As another example of the notification from the UE to the base station, MAC signaling may be used, which may, for example, allow the UE to quickly notify the base station of a paging collision. As another example, L1 / L2 signaling may be used, which may, for example, allow the UE to more quickly notify the base station of a paging collision.

[0214] The base station may use information regarding non-received paging obtained from the UE to change the allocation of timing priorities, change the timing of paging, change the correspondence between timing priorities and type priorities, or change the allocation of type priorities to each paging type.

[0215] The base station may change the paging timing using the notification from the UE. The base station may change a parameter used to determine the paging timing. The parameter may be, for example, PCCH configuration information (PCCH-Config) disclosed in Non-Patent Document 22 (TS38.331).

[0216] The base station may uniformly assign timing priorities, determine the correspondence between timing priorities and type priorities, assign type priorities to each paging type, and / or change the timing of paging to UEs served by the cell. The base station may notify the UEs served by the cell of information related to the change. The UEs served by the cell may use the information related to the change to update settings related to the timing priorities of paging, settings related to the timing of paging, settings related to the correspondence between timing priorities and type priorities, or settings related to the assignment of type priorities to each paging type.

[0217] For example, the base station may report the changed parameters to the UEs under its control. For example, the base station may report the changed parameters by including them in SIB1. The UEs may use the report to change the timing at which they receive paging (hereinafter, may be referred to as paging reception timing).

[0218] As another example, the base station may change the parameter for each beam. The broadcast information from the base station may be different for each beam. This makes it possible to improve the flexibility of the parameter setting in the communication system, for example.

[0219] As another example, the base station may individually assign timing priorities, determine the correspondence between timing priorities and type priorities, assign type priorities to each paging type, and / or change the timing of paging for each UE. The base station may individually notify the UEs under the cell of information on the change. For example, RRC individual signaling may be used for the notification. The UE may use the information on the change to update a setting on the timing priority of paging, a setting on the timing of paging, a setting on the correspondence between timing priorities and type priorities, or a setting on the assignment of type priorities to each paging type.

[0220] For example, the base station may change parameters used to determine paging timing for each UE. The base station may notify the UE of the changed parameters. The base station may include the changed parameters in RRC signaling, for example, RRC reconfiguration, and notify the UE of the changed parameters. The UE may change the paging reception timing using the individual notification. This makes it possible to avoid, for example, complex processing related to changing the paging timing in a communication system.

[0221] As another example, the base station may set or change the parameter for multiple UEs collectively. For example, the base station may set and / or change the parameter for multiple multi-SIM UEs collectively. For example, the multiple multi-SIM UEs may be all the multiple SIM UEs under the umbrella of the base station. For example, the multiple multi-SIM UEs may have the same or different network connection destinations other than the base station. The multiple multi-SIM UEs may be treated as a UE group. The base station sets and / or changes the parameter for the UE group.

[0222] The base station may collectively notify the plurality of UEs of the parameters collectively set and / or changed for the plurality of UEs. For example, RRC signaling may be used for the notification. A specific UE-ID, for example, a multicast UE-ID, may be provided for the collective notification. The plurality of UEs may set and / or change the parameters using the collective notification. This makes it possible to reduce, for example, the amount of signaling between the base station and the plurality of UEs.

[0223] The above-mentioned collective notification from the base station to the multiple UEs may be performed in other RRC signaling, which may, for example, further reduce the amount of signaling between the base station and the multiple UEs.

[0224] The UE may notify the base station of the other NW of the changed parameter notified by the base station. The UE may include information on the UE's identifier in the notification to the base station of the other NW. The identifier may be an identifier assigned in the NW of the base station that changed the parameter. The base station of the other NW may or may not change the paging timing in the other NW using the parameter. This makes it possible, for example, to change the paging timing in the other NW while avoiding the notified parameter. As a result, it is possible to prevent paging collisions after changing the paging timing.

[0225] The base station may request the AMF to change the identifier of the UE. The base station may make the request, for example, when paging collision cannot be avoided by changing only a parameter (for example, PCCH configuration information (PCCH-Config)) used to determine paging timing. The base station may not make the request to the AMF when paging collision is possible by changing the parameter. This makes it possible to prevent unnecessary change of the identifier, for example, when paging collision can be avoided by changing only the PCCH configuration information. The request may include one or more UE identifiers that are candidates for change. For example, signaling on the N2 interface may be used for the request. New signaling, for example, signaling of an N2 UE configuration update request, may be provided and used. The identifier of the UE may be, for example, the UE_ID disclosed in section 7.1 of non-patent document 26 (TS38.304), or the 5S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​disclosed in non-patent document 27 (TS23.501). The identifier of the UE may be, for example, the UE_ID disclosed in section 7.1 of non-patent document 26 (TS38.304), or the 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier), 5G-TMSI (5G Temporary Mobile Subscription Identifier), or 5G-GUTI disclosed in non-patent document 27 (TS23.501). The AMF may change the identifier of the UE using the signaling.

[0226] The base station may notify the AMF of information used for avoiding paging collisions. The base station may notify the information by including it in the request for the UE identifier. The information may include the above-mentioned information (1) to (15). The base station may convert the above-mentioned information (1) to (15) notified from the UE into signaling in the N2 interface and notify it. The information may further include information about the own network. The information about the own network may be the above-mentioned information (1) to (15) with another network replaced with the own network. The AMF may change the UE identifier using the information about the own network. This makes it possible to prevent paging collisions in the UE identifier after the change, for example.

[0227] The AMF may notify the UE of the changed identifier. For the notification, NAS signaling, for example, a configuration update command (CONFIGURATION UPDATE COMMAND) disclosed in non-patent document 32 (TS24.501), may be used. The identifier may be, for example, a 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI) disclosed in non-patent document 27 (TS23.501). The UE may update its own UE-ID using the notification.

[0228] The UE may notify the AMF of the completion of updating the UE's identifier. For the notification, NAS signaling, for example, CONFIGURATION UPDATE COMPLETE disclosed in Non-Patent Document 32 (TS24.501), may be used.

[0229] The AMF may notify the base station of the changed identifier. The notification may be performed using signaling on the N2 interface. The base station may use the notification to change the paging timing of the UE. For example, the base station may use the changed identifier of the UE to change a parameter used to determine the paging timing. This may improve the flexibility of changing the paging timing in the UE. The notification of the changed parameter from the base station to the UE may be the same as described above.

[0230] FIG. 15 is a diagram showing a first example of allocation of timing priority of paging from a plurality of NWs and paging received by a UE. In the example shown in FIG. 15, timing priority is allocated in two stages, high and low. In the example shown in FIG. 15, an arrow 1500 indicates a DRX cycle in NW#1 of the UE, and an arrow 1501 indicates a DRX cycle in NW#2 of the UE. In the example shown in FIG. 15, the paging timing of NW#1 is shown in areas 1505-1507, and the paging timing of NW#2 is shown in areas 1510-1512. In the example shown in FIG. 15, areas 1505, 1507, and 1511 written in white squares are paging timings assigned with low timing priority, and areas 1506, 1510, and 1512 written in black squares are paging timings assigned with high timing priority.

[0231] 15, the paging timings indicated by areas 1505 and 1510 overlap each other. In this case, the UE receives a paging from NW#2, which is assigned a higher timing priority, in area 1515. Similarly, the UE receives a paging from NW#1 in area 1516 and a paging from NW#2 in area 1517.

[0232] As another example of timing priority allocation, paging timing may be set for each timing priority. For example, each parameter of the PCCH configuration information (PCCH-Config) disclosed in Non-Patent Document 22 may be determined for each timing priority. A UE may have multiple paging timings in one paging cycle. When the timing of paging with a certain timing priority overlaps with that of another timing priority in one UE, a paging with a higher timing priority may be prioritized.

[0233] Fig. 16 is a diagram showing a second example of allocation of timing priority of paging from multiple NWs and paging received by a UE. In the example shown in Fig. 16, timing priority is allocated in two stages, high and low. In Fig. 16, paging timing with high timing priority and paging timing with low timing priority are respectively set for the UE from both NW#1 and NW#2. In Fig. 16, elements common to Fig. 15 are assigned the same element numbers, and common explanations are omitted.

[0234] 16, paging timings with high timing priority assigned from NW#1 are set as areas 1606, 1608, and 1610, and paging timings with low timing priority assigned from NW#1 are set as areas 1605, 1607, and 1609. In the example shown in FIG. 16, paging timings with high timing priority assigned from NW#2 are set as areas 1615, 1617, and 1619, and paging timings with low timing priority assigned from NW#2 are set as areas 1616, 1618, and 1620.

[0235] In the example shown in FIG. 16, the paging timings shown in the regions 1605 and 1615 overlap with each other. In this case, the UE receives a paging from the NW#2 to which a high timing priority is assigned in the region 1625. Since neither of the paging timings shown in the regions 1606 and 1616 overlaps with other paging timings, the UE receives a paging from the NW#1 in the region 1626 and a paging from the NW#2 in the region 1627. Similarly, the UE receives a paging from the NW#2 to which a high timing priority is assigned in the region 1628, a paging from the NW#1 in the region 1629, and a paging from the NW#2 in the region 1630. Similarly, the UE receives a paging from the NW#2 to which a high timing priority is assigned in the region 1631, a paging from the NW#1 in the region 1632, and a paging from the NW#2 in the region 1633.

[0236] The UE may associate the timing priority assigned in a certain network with the timing priority assigned in another network. The association may be performed, for example, when the number of stages of the timing priority in a certain network is different from the number of stages of the timing priority in another network. This allows the UE to compare the timing priority between multiple networks, even when the number of stages of the timing priority is different between the multiple networks.

[0237] The method of the association may be determined by a standard. The association may be performed, for example, from a timing priority with a smaller number of stages to a timing priority with a larger number of stages. For example, when the number of stages is two or three, high and low in the two-stage timing priority may be associated with high and low in the three-stage timing priority, respectively. This makes it possible, for example, to avoid the complexity of the association.

[0238] As another example, the correspondence may be performed from a timing priority with a larger number of stages to a timing priority with a smaller number of stages. For example, when the number of stages is two or three, high, medium, and low in the three stages of timing priority may be respectively associated with high, high, and low in the two stages of timing priority. This allows, for example, to improve the flexibility of the correspondence.

[0239] Another solution is disclosed. A transmittable paging type is assigned for each timing priority. For example, in a case where two stages of timing priority are provided, all types of paging may be transmitted in paging with high timing priority, and all types of paging except emergency communication may be transmitted in paging with low timing priority. As another example, in a case where three stages of timing priority, high, medium, and low, are provided, all types of paging may be transmitted in paging with high timing priority, all types of paging except emergency communication may be transmitted in paging with medium timing priority, and all types of paging except emergency communication, voice call, and SI update may be transmitted in paging with low timing priority. The method disclosed in the first embodiment may be used for the allocation of timing priority. The operation of the UE may be the same as the operation disclosed in the first embodiment. This, for example, makes it unnecessary to assign type priority, and as a result, it is possible to reduce the amount of processing in the NW side device of the communication system.

[0240] As another example, all paging types may be transmittable regardless of the timing priority. This allows for prompt reception of a paging with a certain timing priority, for example, in a case where a paging with a certain timing priority cannot be received due to a timing collision with a paging with a higher timing priority from another network.

[0241] Another solution is disclosed. A timing priority for transmission may be set for each paging type. In the case where two stages of timing priority are provided, emergency communication may be transmitted only by paging with high timing priority, and other types of paging may be transmitted by both high and low timing priority paging. As another example, in the case where three stages of timing priority, high, medium, and low, are provided, emergency communication may be transmitted only by paging with high timing priority, voice call and SI update may be transmitted by paging with high or medium timing priority, and other types of paging may be transmitted by paging with any of high, medium, and low timing priority. The method disclosed in the first embodiment may be used for the allocation of timing priority. The operation of the UE may be the same as that disclosed in the first embodiment. This, for example, makes it unnecessary to assign type priority, and as a result, it is possible to reduce the amount of processing in the NW side device of the communication system.

[0242] As another example, all types of paging may be transmitted at all timing priorities, which allows prompt reception of a paging of a certain type when, for example, a paging of a certain timing priority cannot be received due to a timing collision with a paging of a higher timing priority from another network.

[0243] The method disclosed in the present embodiment 1 may be used when the connections with multiple networks are active, for example, when the RRC state between the base stations of multiple networks is RRC_CONNECTED. The method disclosed in the present embodiment 1 may be used when only the connections with one network are active and the connections with other networks are inactive, for example, when the RRC state between the base station of one network is RRC_CONNECTED and the RRC state between the base station of the other network is RRC_INACTIVE or RRC_IDLE. The method disclosed in the present embodiment 1 may be used when the connections with multiple networks are inactive, for example, when the RRC state between the base stations of multiple networks is RRC_INACTIVE or RRC_IDLE. The UE may switch the destination network when receiving paging. In this way, the UE may notify the base station of the source network of the switch of information related to the connection switch. The base station of the source network of the switch may stop scheduling for the UE using the information. This enables, for example, efficient use of radio resources in the base station of the source network.

[0244] According to the first embodiment, it is possible to reduce the possibility that the UE will not receive paging for emergency communication due to a collision between the timing of paging for emergency communication and the timing of paging for another network.

[0245] Variation 1 of the first embodiment In the first embodiment, a method is disclosed in which a UE gives priority to receiving a paging message having a high timing priority. In the present first modification, a method is disclosed regarding a reception operation of a UE in a case where timings of paging messages having the same timing priority collide with each other.

[0246] The UE may receive paging from a base station with good communication quality, which may, for example, improve the reliability of paging reception.

[0247] To determine communication quality, the UE may use a synchronization signal transmitted from a base station, a CSI-RS, a PDCCH, or a DM-RS, which may be the DM-RS of the PDCCH, the DM-RS of the PDSCH, or the DM-RS of the PBCH.

[0248] As another example, the UE may preferentially receive paging from a base station with fewer paging timings. In determining the base station with fewer paging timings, the UE may use the DRX cycle, the number of PFs in the DRX cycle, the number of POs in the PF, or the number of PDCCH monitoring occasions in the PO. A combination of the above may be used. As another example, the UE may preferentially receive paging from a base station with a longer time until the next paging timing. This makes it possible to reduce latency in paging reception, for example.

[0249] As another example, the UE may receive a paging from a network different from the network of the previously received paging. For example, the UE may switch the network of the paging to be received in order when paging with the same timing priority collides. That is, the network of the paging to be received by the UE may be determined using a round robin. The above method may be used, for example, when paging from multiple networks collides at the same period. This makes it possible to prevent a situation in which paging from a specific network cannot be received for a long time in the above case.

[0250] As another example, the UE may switch the NW from which the paging is received by using the fact that a paging occurred at the paging timing at which the UE performed the reception operation. The switching may be, for example, a switching between multiple NWs in order. The switching may be, for example, by using the above-mentioned round robin. This allows the UE to receive paging from multiple NWs even if, for example, the timings at which paging is actually transmitted overlap with each other at the paging timings from multiple NWs.

[0251] As another example, the UE may have parameters related to paging reception from a plurality of NWs. The parameters may be provided for each NW to which the UE is connected, or may be provided for each paging timing from the same NW, or both of the above may be used in combination. The parameters may be, for example, ones whose value is increased over time. The parameters may be ones whose value is subtracted from a predetermined value or ones whose value is initialized when the UE performs a paging reception operation from the NW. The parameters may be ones whose value is subtracted from a predetermined value or ones whose value is initialized when the UE actually receives a paging from the NW. The predetermined value to be subtracted may be a constant value, may be different for each timing priority, may be different for each type of paging actually received, or may be different between when the UE performs a reception operation and when the UE actually receives. The UE may perform a paging reception operation from a NW with the highest value of the parameter. When the value of the parameter is the same among a plurality of NWs, it may be predetermined which NW the UE will perform a paging reception operation from. This enables, for example, improved flexibility in receiving paging from multiple networks at a UE.

[0252] As another example, the UE may have a timer related to paging reception from a plurality of networks. The timer may be provided for each network to which the UE is connected, or may be provided for each paging timing from the same network, or both of the above may be used in combination. The timer may be started, for example, when the UE registers with the network (for example, when the UE becomes RM_REGISTERED). The timer may be stopped or initialized when the UE performs a paging reception operation from the network. The parameter may be stopped or initialized when the UE actually receives a paging from the network. The UE may perform a paging reception operation from the network with the shortest remaining time on the timer, or may perform a paging reception operation from the network whose timer expired first. The initial value of the timer may be constant among a plurality of networks, or may be different for each network. The initial value of the timer may be determined by a standard, or may be determined by a device of each network (for example, an AMF, a PCF, a UPF, an SMF, or a base station) and notified to the UE. This provides, for example, the same effects as those described above.

[0253] The UE may notify the base station of information on the aforementioned parameters or may notify the base station of information on the aforementioned timer. The base station may use the information to determine whether or not to transmit paging at a predetermined paging timing, or may determine the type of paging at the predetermined paging timing. The base station may not transmit paging at the paging timing by using, for example, that the value of the parameter for its own network is the second highest or lower among the networks. This makes it possible to reduce power consumption in the communication system, for example.

[0254] As another example, the UE may receive a paging of a preceding paging timing. The UE may perform this operation, for example, when the timings of paging from multiple networks partially overlap. This allows, for example, the UE to receive the paging quickly.

[0255] As another example, the UE may make the determination using the type of the network. The type of the network may be, for example, a PLMN or a private network (or a non-public network). The UE may, for example, preferentially receive paging from a base station on the PLMN side. This allows, for example, the UE to quickly receive an emergency call from the PLMN. As another example, the UE may, for example, preferentially receive paging from a base station on the private network side. This allows, for example, the UE to quickly receive downlink data generated in the private network.

[0256] A primary network and a secondary network may be provided. A multi-SIM equipped UE may configure a primary network or a secondary network. The UE may configure the primary network and / or the secondary network in a base station and / or an AMF of the primary network or in a base station and / or an AMF of the secondary network. This makes it possible to avoid the complexity of processing for notifying information regarding paging collisions in designing a communication system.

[0257] A person may configure a primary network and / or a secondary network for a UE. For example, a primary network and a secondary network are configured according to a person's preference. This makes it possible to perform paging collision avoidance for a network that is preferred by the person. The configuration of the primary network and / or the secondary network may be stored in the UE in advance. The UE can use the configuration of the primary network and / or the secondary network at any time.

[0258] The UE may receive paging from the base station of the primary network, which may reduce the amount of processing in the UE, for example.

[0259] For each timing priority disclosed in the first embodiment, it may be determined which NW to preferentially receive paging from. For example, when two stages of timing priority are provided, for paging with a high timing priority, paging from a base station on the PLMN side may be preferentially received, and for paging with a low timing priority, paging from a base station on the private NW side may be preferentially received. This allows, for example, the UE to quickly receive downlink data generated in the private NW while quickly receiving an emergency call from the PLMN.

[0260] The UE may determine a network from which to receive paging with priority by a method different from that described above, which may allow, for example, flexible execution of paging reception operations in the UE.

[0261] The UE may notify the base station of which base station of the NW from which the UE will receive paging with priority. As another example, the UE may notify the base station that it will not receive paging from the base station. The base station to which the notification is sent may be a base station from which the UE will not receive paging. The base station may use the notification to change the allocation of timing priority or to change the paging timing. The base station may notify the UE of the changed timing priority allocation or to notify the UE of the changed paging timing. The notification from the base station to the UE may be performed using, for example, the method disclosed in the first embodiment. This makes it possible to prevent, for example, paging received by the UE from being biased toward a base station of a specific NW. As another example, the base station to which the notification is sent may be a base station from which the UE receives paging. The UE may notify the base station from which the UE receives paging that it will receive paging. The base station may use the notification to determine the paging allocation at each paging timing. This makes it possible to improve, for example, the efficiency of paging notification in a communication system.

[0262] The UE may perform the notification to the base station after acquiring information on paging timing from the base station of each connected NW. Alternatively, the UE may perform the notification after acquiring information on timing priority in paging timing from the base station of each connected NW. Alternatively, the UE may perform the notification after acquiring both of the above information.

[0263] As another example, when the UE switches which base station of the NW from which paging is to be preferentially received, for example, when the communication quality with the base station from which the UE does not receive exceeds the communication quality with the base station from which the UE receives, the UE may notify the base station. The communication quality may be, for example, a synchronization signal from the base station and / or the RSRP, RSRQ, SINR, or received power of the CSI-RS. In the above case, the UE may include the notification to the base station in a measurement report. This allows, for example, a base station whose communication quality has deteriorated to use the paging timing for communication with other UEs, thereby improving the efficiency of communication.

[0264] The information included in the information from the UE to the base station regarding which base station of which network a paging is to be preferentially received may be the same as the information (1) to (15) disclosed as an example of information regarding non-received paging in embodiment 1. The information may include information regarding collision of the same timing priority.

[0265] The notification from the UE to the base station may include a request for changing the paging timing. The base station may use the request to change the paging timing. The change in the paging timing at the base station, the notification or report of the paging timing change from the base station to the UE, and / or the operation at the UE may be the same as the method disclosed in the first embodiment, for example.

[0266] As another example, the base station may determine which base station of a network the UE will preferentially receive paging from. The base station may make the determination using, for example, a measurement report from the UE, or may make the determination using the type of network (e.g., PLMN, private network), or may give priority to a base station on the primary network side.

[0267] The base station making the decision may be, for example, a base station on the primary NW side. This makes it possible to avoid, for example, the complexity of control in the communication system. As another example, the base station making the decision may be a base station having good communication quality with the UE. This makes it possible to improve, for example, the quality of control from the base station to the UE. As another example, the base station making the decision may be a base station in which the state of the RRC connection with the UE is RRC_CONNECTED. This makes it possible to avoid, for example, the complexity of control in the communication system.

[0268] The base station may notify the UE of which base station of the network from which the UE will receive paging with priority. The UE may use the notification to perform reception processing of paging with overlapping timing.

[0269] The notification from the base station to the UE may be performed using RRC signaling, for example, signaling of RRC connection reconfiguration. This allows, for example, the base station to notify the UE of a large amount of information. As another example, the notification from the base station to the UE may be performed using MAC signaling. This allows, for example, the base station to notify the UE of the information quickly. As another example, the notification from the base station to the UE may be performed using L1 / L2 signaling. This allows, for example, the base station to notify the UE of the information even more quickly.

[0270] As another example, the core network may determine which base station of the network the UE will preferentially receive paging from. The core network may be, for example, an AMF, an SMF, or a PCF. The core network device may make the determination using, for example, the type of network (e.g., PLMN, private network), or may give priority to the base station on the primary network side.

[0271] The core NW device making the decision may be, for example, a device on the primary NW side. This makes it possible to avoid, for example, the complexity of control in the communication system. As another example, the core NW device making the decision may be a core NW device of a NW in a base station having good communication quality with the UE. This makes it possible to improve, for example, the quality of control from the base station to the UE. As another example, the core NW device making the decision may be a core NW device of a NW in a base station in which the state of the RRC connection with the UE is RRC_CONNECTED. This makes it possible to avoid, for example, the complexity of control in the communication system. As another example, the core NW device making the decision may be a core NW device of a NW in which the connection state with the UE is CM_CONNECTED. This makes it possible to avoid, for example, the complexity of control in the communication system.

[0272] The core network device may notify the UE of which base station of the network to receive paging from with priority. The UE may use the notification to perform reception processing of paging with overlapping timing.

[0273] The notification from the core NW device to the UE may be performed using NAS signaling. This allows, for example, the core device to notify the UE of a lot of information. As another example, the notification from the core NW device to the UE may be performed via a base station. The notification from the base station to the UE may be performed using RRC signaling, for example, signaling of RRC connection reconfiguration. This allows, for example, the core NW device to notify the UE of a lot of information. As another example, the notification from the base station to the UE may be performed by MAC signaling. This allows, for example, the base station to quickly notify the UE of the information. As another example, the notification from the base station to the UE may be performed using L1 / L2 signaling. This allows, for example, the base station to more quickly notify the UE of the information.

[0274] The method disclosed in this modification 1 may be applied when the timing priority is not set. This allows the UE to quickly know from which NW the UE will receive paging, even when the timing priority of paging is not set, for example.

[0275] According to this modification 1, the base station and / or the core NW device can know which NW the UE has priority in receiving paging from. As a result, it is possible to prevent malfunctions in the communication system.

[0276] Variation 2 of embodiment 1 A UE equipped with multiple SIMs transmits and receives data to and from multiple networks. For this reason, for example, when the UE is connected to multiple PLMNs, the UE may receive emergency communications with the same content from multiple PLMNs. This causes a problem of memory size pressure on the UE.

[0277] In this second modification, a method for solving the above-mentioned problem will be disclosed.

[0278] The UE deletes the paging of the same type. The UE may keep only the first received paging. The UE may delete the later received paging. The UE may, for example, delete data related to the later received paging or may not receive the data.

[0279] The operation in the UE may be applied only to a predetermined type of paging. For example, the operation in the UE may be applied to emergency communication. The emergency communication may be, for example, a Public Warning System (PWS), an Earthquake and Tsunami Warning System (ETWS), a Commercial Mobile Alert System (CMAS), a European Public Warning System (EU-ALERT), or a Korean Public Alert System (KPAS). The emergency communication may be, for example, an emergency communication for a private network disclosed in the first embodiment. The emergency communication may be another emergency communication. This makes it possible to prevent, for example, data with different contents from being mistakenly deleted as the same data in the UE.

[0280] The UE may determine whether or not there is a duplication by using information on the paging type. The information may be, for example, information included in the paging or information included in data related to the paging. The information may be, for example, a message identifier (Message Identifier) ​​disclosed in Section 9.4.1.2.2 of Non-Patent Document 21 (TS23.041 V16.2.0).

[0281] The paging may include information about the caller. For example, the paging of the emergency communication may include information about the caller of the emergency communication. The information about the caller may be uniquely assigned regardless of the PLMN, or may be assigned by each PLMN. When each PLMN assigns the information about the caller, each PLMN may notify the UE of the information about the assignment to the caller. The notification to the UE may be performed by, for example, the AMF. The UE may use the information about the caller to determine whether or not there is overlap. This makes it possible to prevent, for example, erroneous detection of overlap of data from different callers.

[0282] The paging may include information about a sequence number. The sequence number may be unique among the aforementioned sources. The UE may use the information about the sequence number to determine whether there is a duplication. This may, for example, prevent erroneous detection of duplication of different data from the same source.

[0283] The UE may determine that paging of a predetermined type received within a predetermined time difference is paging related to the same data. For example, when the UE receives emergency communication paging from base stations of multiple networks within a predetermined time difference, the UE may determine that the emergency communications have the same content. This allows the UE to determine that the emergency communications have the same content even when emergency communications with the same content are received from multiple networks at different times.

[0284] The predetermined time difference may be specified in advance, may be determined by the core network and notified to the UE, or may be determined by the base station and notified to the UE.

[0285] The base station making the decision may be, for example, a base station on the primary NW side, as in the first modification of the first embodiment. This makes it possible, for example, to avoid the complexity of control in the communication system. As another example, the base station making the decision may be a base station having good communication quality with the UE. This makes it possible, for example, to improve the quality of control from the base station to the UE. As another example, the base station making the decision may be a base station in which the state of the RRC connection with the UE is RRC_CONNECTED. This makes it possible, for example, to avoid the complexity of control in the communication system.

[0286] As in the first modification of the first embodiment, the core network may be, for example, an AMF, an SMF, or a PCF. The core network device may make the decision using, for example, the type of network (for example, PLMN, private network), or may prioritize the base station on the primary network side.

[0287] The core NW device making the decision may be, for example, a device on the primary NW side, as in the first modification of the first embodiment. This makes it possible to avoid, for example, the complexity of control in the communication system. As another example, the core NW device making the decision may be a core NW device of a NW in a base station having good communication quality with the UE. This makes it possible to improve, for example, the quality of control from the base station to the UE. As another example, the core NW device making the decision may be a core NW device of a NW in a base station in which the state of the RRC connection with the UE is RRC_CONNECTED. This makes it possible to avoid, for example, the complexity of control in the communication system. As another example, the core NW device making the decision may be a core NW device of a NW in which the connection state with the UE is CM_CONNECTED. This makes it possible to avoid, for example, the complexity of control in the communication system.

[0288] The predetermined time difference may be determined by a plurality of networks, for example, a plurality of core network devices. Alternatively, the predetermined time difference may be determined by a plurality of base stations. The predetermined time difference may be different among a plurality of networks, or may be different among a plurality of base stations. The UE may use a shorter time among the times that differ among a plurality of networks and / or base stations. This makes it possible, for example, to prevent the UE from erroneously deleting different data as the same data. As another example, the UE may use a longer time among the times that differ among a plurality of networks and / or base stations. This makes it possible, for example, to prevent the UE from erroneously detecting the same data as different data, and as a result, it becomes possible to reduce the amount of processing by the UE.

[0289] The predetermined time difference may be set for each paging type, which may, for example, improve the flexibility of the communication system.

[0290] The operation in the UE may be applied when the same PLMN is used. In other words, the operation in the UE may not be applied when the UE is connected to different PLMNs. This makes it possible to prevent the UE from erroneously detecting different paging types as the same paging type when different paging types are set for the same message identifier (see Non-Patent Document 21 (TS23.041 V16.2.0)) in each NW.

[0291] The operation in the UE may be applied in the private network, which enables the UE to detect duplicate emergency communications for the private network having the same content, thereby reducing the amount of processing in the UE.

[0292] As another example, the operation in the UE may be applied when the networks are the same private networks. This makes it possible to prevent the UE from erroneously detecting different paging types as the same paging type when different paging types are set for the same message identifier (see Non-Patent Document 21 (TS23.041 V16.2.0)) in each network.

[0293] Information regarding the allocation of message identifiers (see Non-Patent Document 21 (TS23.041 V16.2.0)) to paging types in each network may be notified to the UE. For example, NAS signaling may be used for the notification. The UE may use the notification to detect paging with the same content. This allows the UE to detect paging of the same type even when, for example, different message identifiers are assigned to the same paging type in different networks.

[0294] According to the second modification, it becomes possible to avoid receiving duplicate paging messages, and as a result, it becomes possible to reduce the amount of processing in the UE.

[0295] Embodiment 2 A multi-SIM UE may maintain RRC connections with base stations of multiple networks. The UE may transmit and receive data to and from each of the base stations of the multiple networks in a time-division manner.

[0296] In the above-mentioned operation, the following problem occurs. For example, when the UE switches the transmission / reception destination from the base station of the original NW (hereinafter, sometimes referred to as base station #1) to the base station of another NW (hereinafter, sometimes referred to as base station #2) and performs transmission / reception with the base station #2, the UE maintains the RRC state with the base station #1 in RRC_CONNECTED, but is unable to receive signals from the base station #1. In this case, when the UE detects loss of synchronization with the base station #1 and, as a result, detects RLF with the base station #1, the UE needs to execute reconnection with the base station #1.

[0297] In the second embodiment, a method for solving the above-mentioned problem will be disclosed.

[0298] The UE stops a timer and / or a counter (hereinafter, sometimes referred to as RLF timers) used for RLF detection between the UE and base station #1. The RLF timers in the UE may be stopped when the UE switches the transmission / reception destination from base station #1 to base station #2. The RLF timers may be, for example, T310, N310, or N311 disclosed in Non-Patent Document 22 (TS38.331), or a combination of two or more of the above.

[0299] The UE may notify base station #1 of switching the transmission / reception destination, or may notify base station #1 of stopping RLF timers for base station #1. Using the notification, base station #1 may not perform scheduling for the UE. This may improve communication efficiency in base station #1, for example.

[0300] The base station may have a timer. The timer may be, for example, a timer that manages the activity of the UE (hereinafter, may be referred to as an inactivity timer). For example, the timer may be a timer that runs while no transmission or reception is performed between the base station and the UE. The timer may be a timer that is stopped or initialized when transmission or reception is performed between the base station and the UE. When the timer expires, the base station may instruct the UE to release the RRC connection or may instruct the UE to interrupt the RRC connection.

[0301] Using the notification from the UE, the base station #1 may stop the inactivity timer. This makes it possible to prevent the timer from progressing when, for example, the connection destination of the UE is switched from the base station #1 to the base station #2. As a result, it becomes possible to prevent the base station from deciding to interrupt the RRC connection of the UE during the switching.

[0302] The RLF timers in the UE may be stopped before the notification to base station #1, after the notification, or simultaneously with the notification. For example, stopping the RLF timers before the notification can reduce memory usage in the UE when switching between transmitting and receiving destinations in the UE. Also, for example, stopping the RLF timers after the notification can reduce the amount of processing when the UE notifies base station #1. Also, for example, stopping the RLF timers simultaneously with the notification can avoid complexity related to management of the timers in the UE.

[0303] The notification from the UE to the base station #1 may be performed dynamically. For example, L1 / L2 signaling may be used for the notification. This enables rapid execution of transmission / reception switching when, for example, uplink data is generated from the UE to the base station #2. As another example, MAC signaling may be used for the notification. This makes it possible to notify a large amount of information by uplink transmission with a high modulation order, and to improve reliability by retransmission control.

[0304] As another example, the notification from the UE to the base station #1 may be performed semi-statically. For example, RRC signaling may be used for the notification. RRC signaling for the notification may be newly provided. This eliminates the need for the UE to perform the notification every time the transmission / reception destination is switched. As a result, it is possible to reduce the amount of signaling between the UE and the base station.

[0305] As another example, the destination switching in the UE may be determined in advance by the base station and notified to the UE. The UE may use the notification to determine the destination base station. The base station that notifies the UE may be determined in advance, for example. For example, the information may be included in the SIM of the UE. This makes it possible to reduce the amount of signaling between the UE and the base station, for example.

[0306] The UE may establish downlink synchronization with the base station #2. The UE may establish downlink synchronization using a synchronization signal (e.g., SS block) from the base station #2, or may establish downlink synchronization using another signal, e.g., CSI-RS from the base station #2. The UE may establish downlink synchronization with the base station #2 after stopping the RLF timers for the base station #1. This makes it possible to prevent the RLF timers for the base station #1 from expiring while the UE is receiving a downlink signal from the base station #2. As another example, the UE may establish downlink synchronization with the base station #2 after notifying the base station #1 of switching of the transmission / reception destination. This makes it unnecessary to schedule from the base station #1 to the UE while the UE is performing the operation of establishing the downlink synchronization, and as a result, it becomes possible to improve the communication efficiency in the base station #1.

[0307] As another example, the UE may hold information about frame timing in both base stations #1 and #2. For example, the UE may hold information about frame offset between base station #1 and base station #2. The UE may acquire each of the above-mentioned information when an RRC connection is established with each of base stations #1 and #2. The UE may update each of the above-mentioned information. The UE may perform the update at a predetermined period or when some event occurs. When the UE holds each of the above-mentioned information, the UE may not perform downlink synchronization establishment operation with base station #2. This makes it possible to quickly execute transmission / reception switching between base station #1 and base station #2, for example.

[0308] The UE starts or restarts a timer and / or a counter (hereinafter, may be referred to as RLF timers) used for RLF detection between the UE and base station #2. The RLF timers in the UE may be started or restarted after the UE switches the transmission / reception destination from base station #1 to base station #2, for example, after the random access process between the UE and base station #2 is completed.

[0309] The random access may be, for example, a two-step random access consisting of a PRACH transmission from the UE to the base station and an RA response from the base station to the UE, or may be a four-step random access. The UE may start or restart RLF timers after receiving the RA response from the base station, or may start or restart RLF timers after receiving a fourth-step response from the base station. After completing the random access, the base station may start a timer for the UE, for example an inactivity timer, or may restart it without initialization. This makes it possible to avoid, for example, complexity in controlling the RLF timers in the UE and / or the inactivity timer in the base station.

[0310] The UE may not perform random access processing with the base station #2. The UE may not perform the random access processing described above, for example, when it can maintain uplink synchronization with the base station #2. The case where the UE can maintain uplink synchronization with the base station #2 may be, for example, when a predetermined time has not elapsed since transmission and reception between the UE and the base station #2 has stopped, when the position of the UE is within a predetermined range, or when the speed of the UE is within a predetermined range. This allows, for example, quick resumption of transmission and reception between the UE and the base station #2.

[0311] The UE may notify the base station #2 that the transmission / reception destination has been switched to the base station #2, or may notify the base station #2 of restarting the RLF timers. The notification from the UE to the base station #2 may be performed, for example, when random access is not performed between the UE and the base station #2. The notification may be performed using L1 / L2 signaling. This allows, for example, the UE to promptly notify the base station #2 of the switching of the transmission / reception destination. As another example, the notification may be performed using MAC signaling. This allows, for example, retransmission control to improve reliability. As another example, the notification may be performed using RRC signaling. This allows, for example, the UE to notify the base station of a lot of information. The base station may use the notification to start an inactivity timer for the UE, or may restart it without initialization. This allows, for example, to avoid complexity regarding the control of the inactivity timer in the base station.

[0312] Upon restarting the RLF timers, the RLF timers may be initialized, which avoids complexity in the design of the UE. Alternatively, the RLF timers may not be initialized, i.e., restarted from their stopped values. This allows the UE to quickly detect the RLF, and therefore quickly recover from it, in case, for example, the UE is actually out of sync with base station #2.

[0313] Fig. 17 is a sequence diagram showing an example of the operation of stopping and restarting RLF timers associated with switching of the transmission / reception destination of the UE. In Fig. 17, the UE is connected to base station #1 under NW #1 and base station #2 under NW #2.

[0314] In Step ST1703 shown in Fig. 17, the UE is in an RRC_CONNECTED state for the connection between gNB #1 and gNB #2. In Step ST1705, data is transmitted and received between the UE and gNB #1.

[0315] In step ST1707 shown in FIG. 17, data for gNB#2 is generated from the UE. In step ST1709, the UE notifies gNB#1 that it will switch the connection destination of its own UE to gNB#2. The notification in step ST1709 may be performed by L1 / L2 signaling, MAC signaling, or RRC signaling. The gNB#1 uses the notification in step ST1709 to stop scheduling for the UE. In step ST1711, the UE stops RLF timers for gNB#1. The RLF timers may be, for example, T310, N310, or N311 disclosed in non-patent document 22 (TS38.331), or a combination of two or more of the above.

[0316] 17, the gNB#2 transmits an SS block to the UE. In Step ST1715, the UE establishes downlink synchronization with the gNB#2 by receiving the SS block in Step ST1713.

[0317] In step ST1717 shown in FIG. 17, random access processing is performed between the UE and gNB#2. The random access processing in step ST1717 may be random access consisting of two steps: PRACH transmission from the UE to gNB#2 and RA response from gNB#2 to the UE. This enables, for example, rapid completion of the random access processing between the UE and gNB#2. In step ST1719, the UE resumes RLF timers for gNB#2. In the resumption, RLF timers for gNB#2 may be initialized. Step ST1719 may be performed with the completion of step ST1717 as a trigger. The RLF timers for gNB#2 may be the same as the RLF timers for gNB#1 that were stopped in step ST1711. In step ST1721, data transmission and reception is performed between the UE and gNB#2.

[0318] In FIG. 17, after completion of step ST1721, the UE's connection destination is switched from gNB#2 to gNB#1. In step ST1723, the UE notifies gNB#2 that it will switch the UE's connection destination to gNB#1. For the notification in step ST1723, the same signaling as in step ST1709 may be used. In step ST1731, the UE stops the RLF timers for gNB#2. In step ST1733, gNB#1 transmits an SS block to the UE. In step ST1735, the UE establishes downlink synchronization with gNB#1 by receiving the SS block in step ST1733.

[0319] In step ST1737 shown in FIG. 17, a random access process is performed between the UE and gNB#1. The random access process in step ST1737 may be the same as that in step ST1717. In step ST1739, the UE restarts the RLF timers for the gNB#1. In the restart, the RLF timers for the gNB#1 may be initialized. In step ST1741, data transmission and reception is performed between the UE and gNB#1.

[0320] In Fig. 17, the case where the random access in steps ST1717 and ST1737 is configured in two steps is shown, but a four-step random access process may be used. When a four-step random access is used, the base station may reconfigure the RRC parameters for the UE. This makes it possible to improve the flexibility of the communication system, for example.

[0321] Another solution is disclosed. The UE may not stop the RLF timers for base station #1. The UE may not perform the RLF process after the expiration of the RLF timers between the UE and base station #1. The RLF process may be, for example, a transition to RRC_IDLE, or the process disclosed in section 5.3.10.3 of non-patent document 22 (TS38.331), or a combination of both of the above. This makes it possible to avoid, for example, complexity in controlling the RLF timers in the UE.

[0322] In the above case, after the UE's transmission / reception destination is switched back to base station #1, the UE should initialize the timers related to base station #1. This makes it possible to prevent erroneous detection of RLF when the UE's transmission / reception destination is switched back to base station #1, for example.

[0323] Other solutions are disclosed. When the transmission / reception destination is switched from base station #1 to base station #2, the UE may detect RLF with base station #1. A part of the RLF process with base station #1 may not be performed. For example, the UE may not transition to RRC_IDLE. In the RRC re-establishment operation disclosed in section 5.3.7 of non-patent document 22 (TS38.331), the radio bearer may not be stopped. The MAC reset may not be performed. The SCell of the MCG (Master Cell Group) may not be released. The spCellcConfig may not be released. The DC may not be released. The p-NR-FR1 may not be released. The p-UE-FR1 may not be released. The delayBudgetReportingConfig may not be released. T342 may not be stopped. The overheatingAssistanceConfig may not be released. T345 may not be stopped.

[0324] The UE may perform cell selection. A timer (e.g., T311) related to cell selection disclosed in Non-Patent Document 22 (TS38.331) may be started. This makes it possible, for example, to avoid the complexity of the cell selection process. As another example, the UE may not start T311. This makes it possible, for example, to prevent an RRC_IDLE transition due to the expiration of T311.

[0325] The UE may maintain the RRC parameters. The operation of maintaining the RRC parameters in the UE may be applied, for example, when the UE selects the same cell as before the RLF detection. This allows, for example, a reduction in the amount of processing involved in re-establishing the RRC connection. As another example, the UE may release the RRC parameters. The operation of releasing the RRC parameters in the UE may be applied, for example, when the UE selects a cell different from the cell before the RLF detection. This allows, for example, an improvement in flexibility in the communication system.

[0326] The method disclosed in the second embodiment may be applied to beam failure. For example, the number of beam failure instance indications and / or the timer and / or counter associated with the number of beam failure instance indications disclosed in Section 9.2.8 of Non-Patent Document 16 (TS38.300) may be stopped or restarted when the UE switches between the transmitting and receiving destinations. The timer and / or counter may be, for example, the beamFailureRecoveryTimer, beamFailureDetectionTimer, or BFI_COUNTER disclosed in Non-Patent Document 17 (TS38.321). This makes it possible to prevent erroneous detection of beam failure when the UE switches between the transmitting and receiving destinations.

[0327] In applying the method disclosed in the second embodiment, the switching of the transmission / reception destination may not be performed until a random access response is received. As another example, the switching of the transmission / reception destination may not be performed until a message 4 in the random access process is received. The above-mentioned operation may be applied, for example, when the UE transmits a PRACH to the base station. This makes it possible to prevent, for example, a failure in the random access process.

[0328] In applying the method disclosed in the second embodiment, a connection (e.g., NAS connection) between the UE and the NW of the base station before the transmission / reception switching may be maintained. This allows, for example, a quick reconnection to the NW of the base station. As another example, the connection between the UE and the NW may be released. This allows, for example, a reduction in memory usage in the UE.

[0329] The method disclosed in the second embodiment may be applied to beam management and / or beam measurement. For example, the UE may include information indicating that the beam could not be measured in a measurement report to the base station and notify the base station. The notification of the information indicating that the beam could not be measured from the UE to the base station may be performed, for example, when the UE switches the transmission / reception destination to a base station of another NW. The UE may include information regarding the reason why the measurement could not be performed in the notification. The reason may be, for example, switching of the transmission / reception destination. The base station may use the information in beam control for the UE. This makes it possible to prevent, for example, the base station from erroneously determining that the quality of the beam used between the UE and the base station is poor.

[0330] The method disclosed in the second embodiment may be used in the random access process. For example, when the destination base station of the UE is switched from gNB#1 to gNB#2, the collision resolution timer for gNB#1, for example, the ra-ContentionResolutionTimer disclosed in Non-Patent Document 17 (TS38.321), may be stopped. This makes it possible to prevent erroneous detection of collision in the random access process after the destination base station is switched, for example.

[0331] When the destination base station of the UE is switched from gNB#1 to gNB#2, the collision resolution timer for gNB#1 may be started or restarted. The above-mentioned starting or restarting may be performed from an initial value. This makes it possible, for example, to avoid complexity in the management of the timer in the UE. As another example, the collision resolution timer may be restarted from a value after it was stopped. This makes it possible, for example, for the UE to quickly detect a random access collision.

[0332] In the second embodiment, the case where the UE is connected to base station #1 and base station #2 has been disclosed, but the number of base stations to which the UE is connected may be three or more. For example, the method disclosed in the second embodiment may be used to switch the transmission / reception destination from base station #1 to base station #3. Also, for example, the method disclosed in the second embodiment may be used to switch the transmission / reception destination from base station #3 to base station #4. This enables, for example, flexible execution of switching of the transmission / reception destination base station in the UE.

[0333] The method disclosed in the second embodiment may be used in the MAC process. For example, when the destination base station of the UE is switched from gNB#1 to gNB#2, a timer (for example, SCellDeactivationTimer disclosed in Non-Patent Document 17 (TS38.321)) that manages the operation state of the SCell for gNB#1 may be stopped. The timer may be restarted when the destination of the UE is switched back to gNB#1. This makes it possible to prevent the timer from expiring after the destination base station of the UE is switched from gNB#1 to gNB#2, for example. As a result, it is possible to reduce the amount of processing related to reactivation of the SCell in the UE.

[0334] The above-mentioned operation may be applied to a timer (e.g., bwp-InactivityTimer disclosed in Non-Patent Document 17 (TS38.321)) that manages the operation state of the BWP (BandWidth Part) for gNB#1. This makes it possible to reduce the amount of processing related to reactivation of the BWP in the UE, for example, as described above.

[0335] The above operation may be applied to a timer (e.g., dataInactivitiTimer disclosed in TS38.321) that manages the activity of data conduction for gNB#1. This, for example, can prevent the UE from transitioning to RRC_IDLE as described above.

[0336] The method disclosed in the second embodiment may be used in the RLC process. For example, the above-mentioned operation may be applied to a timer (e.g., t-Reassembly disclosed in Non-Patent Document 29 (TS38.322)) used in the reassembly process of the RLC PDU for gNB#1. This makes it possible to reduce the number of state confirmation (e.g., RLC STATUS PDU transmission) processes in the RLC, as described above.

[0337] The method disclosed in the second embodiment may be used in the PDCP process. For example, the above-mentioned operation may be applied to a timer (for example, the discardTimer disclosed in Non-Patent Document 30 (TS38.323)) used to manage the discarding of PDCP SDUs for gNB#1. This makes it possible to prevent the discarding of PDCP SDUs, for example, as described above. As a result, it becomes possible to prevent packet loss in the communication system.

[0338] The above-mentioned operation may be applied to a timer used for PDCP reordering control (for example, t-Reordering disclosed in Non-Patent Document 30 (TS38.323)). This makes it possible to prevent received data undergoing reordering from being transmitted to a higher layer, as described above. As a result, it is possible to reduce the reordering process in the higher layer.

[0339] According to the second embodiment, it is possible to prevent the expiration of RLF timers related to the connection with the base station of the original network while the multi-SIM-equipped UE is transmitting and receiving with the base station of another network. As a result, it becomes unnecessary to re-establish the RRC connection with the base station of the original network.

[0340] Embodiment 3 A survival time (see Non-Patent Document 23 (TR22.832 V17.1.0)) indicating a permissible communication interruption time until an application layer is interrupted when a communication interruption occurs may be used for QoS control in a network.

[0341] However, a method for QoS control using survival time has not been disclosed, which means that the network cannot control communications using survival time, and the network cannot perform communications that satisfy the requirements of the application layer.

[0342] In the third embodiment, a method for solving the above-mentioned problem will be disclosed.

[0343] A QoS parameter related to the survival time is provided. The NW side device may notify the UE of the QoS parameter related to the survival time. The QoS parameter notified by the NW side device to the UE may be a QoS parameter related to the survival time in downlink communication. The UE may notify the NW side device of the QoS parameter related to the survival time. The QoS parameter notified by the UE to the NW side device may be a QoS parameter related to the survival time in uplink communication.

[0344] As examples of QoS parameters related to survival time, the following (1) to (16) are disclosed.

[0345] (1) Survival time value.

[0346] (2) MTBF (Mean Time Between Failure).

[0347] (3) MTTR (Mean Time To Repair).

[0348] (4) MUT (Mean Up Time).

[0349] (5) MDT (Mean Down Time).

[0350] (6) Inherent Availability.

[0351] (7) Operational Availability.

[0352] (8) Tolerable latency.

[0353] (9) Number of allowed latency violations.

[0354] (10) The number of consecutive latency violations permitted.

[0355] (11) Number of times communication failure is permitted.

[0356] (12) The number of consecutive unreachable communications permitted.

[0357] (13) Communication cycle.

[0358] (14) RLC layer retention.

[0359] (15) PDCP layer retention amount.

[0360] (16) A combination of (1) to (15) above.

[0361] Regarding the above (1), for example, the core network device, the base station, and / or the UE may use the survival time value itself for QoS control. For example, the survival time requirement may be added to the 5QI table described in Non-Patent Document 27 (TS23.501). This makes it possible to avoid the complexity of QoS control using the survival time, for example.

[0362] The above-mentioned (2) may be a value calculated by treating the expiration of the survival time timer as a failure. The core network device, the base station, and / or the UE may set up a communication path between the base station and the UE using the above-mentioned value of (2). This makes it possible to avoid complexity in controlling the reliability of communication, for example.

[0363] The above (3) may be, for example, the time from when the survival time requirement is not satisfied to when the communication path is restored. The core network device, the base station, and / or the UE may set up the communication path between the base station and the UE using the value of the above (3). This can provide, for example, the same effect as the above (2).

[0364] The above (4) may be, for example, the average time that an application operates while satisfying the survival time requirement. The core network device, the base station, and / or the UE may set up a communication path between the base station and the UE using the value of the above (4). This may provide, for example, the same effect as the above (2).

[0365] The above (5) may be, for example, the average time that an application stops without satisfying the survival time requirement. The core network device, the base station, and / or the UE may set up a communication path between the base station and the UE using the value of the above (5). This may provide, for example, the same effect as the above (2).

[0366] The above-mentioned (6) may be a parameter given as MTBF / (MTBF+MTTR) using the above-mentioned (2) and (3). The core network device, the base station, and / or the UE may set up a communication path between the base station and the UE using the value of the above-mentioned (6). This can provide an effect similar to that of the above-mentioned (2), for example.

[0367] The above-mentioned (7) may be a parameter given as MUT / (MUT+MDT) using the above-mentioned (4) and (5), for example. The core network device, the base station, and / or the UE may set up a communication path between the base station and the UE using the value of the above-mentioned (7). This can provide the same effect as the above-mentioned (2), for example.

[0368] As the information of (8) above, for example, the packet delay budget disclosed in section 5.7.3.4 of Non-Patent Document 27 (TS23.501) may be used. The above-mentioned (8) may be used when communication is performed periodically on a communication path, or may be used for non-periodic communication. The core NW device, the base station, and / or the UE may use the value of the above-mentioned (8) to assign QoS to data to be transmitted and received, or may perform scheduling. This makes it possible to prevent, for example, adverse effects on applications due to excessive data latency on a communication path.

[0369] The above (9) may be used, for example, when communication is performed periodically on a communication path. The above (9) may be, for example, a value derived using the survival time value and the tolerable latency, for example, the survival time value divided by the tolerable latency. The core NW device, the base station, and / or the UE may use the value of the above (9) to assign QoS to data to be transmitted or received, or may perform scheduling. This may provide, for example, the same effect as the above (8).

[0370] The above-mentioned (10) may be used, for example, when communication is performed periodically. The above-mentioned (10) may be a value obtained similarly to the above-mentioned (9). By using the above-mentioned (10), for example, in a communication system, it is possible to prevent a case where latency exceedance occurs sporadically from being erroneously detected as a survival time exceedance.

[0371] The above (11) may be used, for example, when data is not discarded after a latency exceedance, which can prevent application failures due to a latency exceedance in a communication system where the latency exceedance is not critical.

[0372] The above-mentioned (12) may be used, for example, when data is not discarded after the latency is exceeded. By using the above-mentioned (12), for example, in a communication system, it is possible to prevent a case where communication failures occur sporadically from being erroneously detected as a survival time exceedance.

[0373] The above (13) may be used, for example, when communication is performed periodically on a communication path. The core network device, the base station, and / or the UE may assign QoS to data to be transmitted and received, or may perform scheduling, using the value of the above (13). This may provide the same effect as the above (8), for example.

[0374] The above-mentioned (14) may be used, for example, when communication is performed periodically on a communication path. The above-mentioned (14) may be calculated, for example, using a survival time value, a communication cycle, and the amount of data transmitted and received in one cycle. The above-mentioned (14) may be the amount of data held up in an RLC entity of a receiving device. This allows, for example, the reception status of a receiving device to be quickly reflected in QoS control. As another example, the value of the above-mentioned (14) may be the amount of data held up in an RLC entity of a transmitting device. This allows, for example, only data whose delivery has been confirmed to be reflected in QoS control, and as a result, QoS control closer to the control status of a higher layer is possible.

[0375] The above-mentioned (15) may be obtained, for example, using the value of the survival time, the communication cycle, and the amount of data transmitted and received in one cycle. The above-mentioned (15) may be the amount of data held up in the PDCP entity of the receiving device, as in the above-mentioned (14), or may be the amount of data held up in the PDCP entity of the transmitting device. By using the amount of data held up in the PDCP layer, for example, it becomes possible to perform QoS control that is closer to the control situation of the upper layer.

[0376] Regarding (16) above, for example, the survival time may be used as the product of the allowable number of consecutive communication failures and the communication cycle.

[0377] The above (1) to (16) may be used in combination with existing QoS parameters, such as the QoS parameters disclosed in Section 5.7.2 of Non-Patent Document 27 (TS23.501). This allows for flexible QoS control, for example.

[0378] Information about the survival time (e.g., the value of the survival time) may be notified from the AF. The notification may be, for example, a request to the 5G system to meet the survival time. The notification may include information about the communication that should meet the survival time. The information about the communication that should meet the survival time may include, for example, information about the sending and receiving hosts (e.g., source IP address, destination IP address, source port number, and / or destination port number), or information about the transmission data (e.g., information indicating whether it is TCP / UDP).

[0379] The AF may notify the core NW device of the information. The core NW device may be, for example, a PCF, a UDM, an SMF, an AMF, a UPF, or an NWDAF (Network Data Analytics Function, see Non-Patent Document 31 (TS23.288)). The core NW device may use the information to perform QoS control in the communication system. For example, the core NW device may use the information to convert to (2) to (16) disclosed as examples of QoS parameters related to survival time, to existing QoS parameters, or to both of the above. As an example of the above conversion, the value of survival time and the allowable latency may be used to derive the allowable number of consecutive latency exceedances by dividing the value of survival time by the value of allowable latency.

[0380] For example, the NWDAF may use the information from the AF to convert to QoS parameters used in the communication system. The NWDAF may use information acquired by itself (for example, input data disclosed in section 6.4.2 of non-patent document 31 (TS23.288)) to convert to QoS parameters. Information on the occlusion frequency disclosed in the third modification of the third embodiment may be used. This enables, for example, QoS control that reflects the status of the communication system and reduces the amount of signaling in deriving the QoS parameters.

[0381] As another example, the AF may notify the core NW device of (1) to (16) disclosed as examples of QoS parameters related to survival time. As described above, the core NW device may be a PCF, a UDM, an SMF, an AMF, a UPF, or an NWDAF (Network Data Analytics Function, see Non-Patent Document 31 (TS23.288)). The core NW device may use the information to perform QoS control in the communication system. This makes it possible to reduce the amount of processing for QoS control in the core NW device, for example.

[0382] Information related to the survival time may be changed (e.g., updated or modified). The NW side device may notify the UE of a change in the QoS parameters related to the survival time. The AF may notify the core NW device of the change. The notification may include (1) to (16) disclosed as examples of the QoS parameters related to the survival time. As another example, the notification may include information related to the reason for the change. The reason for the change may be, for example, a change in the environment in the application (e.g., a change in the time zone, season, etc. in which the application is used) or other reasons.

[0383] The core network device may request the AF to change information related to the survival time. The request may include information related to the reason for changing the information. The information related to the reason may include, for example, excessive requests related to the survival time from the AF, or a situation in which the requests related to the survival time from the AF are likely to be unable to be satisfied. The AF may use the request to change QoS parameters related to the survival time. This allows, for example, flexible operation of the communication system.

[0384] As another example, the base station may request the AF to change information related to the survival time. The base station may make the request to the AF via a core NW device. As another example, the UE may make the request. The UE may make the request via the base station and the core NW device. The AF may use the request to change information related to the survival time. This makes it possible to prevent application interruptions caused by, for example, failure to satisfy requirements related to the survival time in a communication system.

[0385] A plurality of pieces of information related to the survival time may be set for one UE. For example, a plurality of pieces of information related to the survival time may be set for one UE from a plurality of applications. The plurality of pieces of information may be, for example, a plurality of combinations of (1) to (16) disclosed as examples of QoS parameters related to the survival time and / or existing QoS parameters. The UE may use the information to communicate with the base station. This enables, for example, flexible QoS control for different applications.

[0386] A plurality of such settings for one UE may be made to a core NW device or may be made to a base station. The core NW device and / or the base station may use the settings to perform QoS control or scheduling for the UE. This enables efficient scheduling in a communication system, for example.

[0387] One application may set multiple pieces of information related to survival time. For example, different information may be set for the control information of the application and for the actual data. The setting from the application may be performed for the core NW device or for the UE. This makes it possible to improve the efficiency of QoS control in the application, for example.

[0388] The information on the survival time may include information on a validity period. For example, when the survival time varies over time, a validity period may be provided. This allows, for example, flexible QoS control in a communication system.

[0389] A default value may be set for the information regarding the survival time. The default value may be, for example, determined by a standard, determined by a core NW device, determined by an AF, or determined by a base station. Each device in the communication system may perform communication using a default value when the information regarding the survival time is not set. When the validity period described above expires, the default value may be used. This makes it possible to prevent, for example, malfunctions in the communication system.

[0390] QoS control using the survival time may be performed in the DC. In the DC, QoS control using the survival time may be performed in the base station on the MCG side. This makes it possible to avoid, for example, complexity in QoS control during the DC. As another example, the SCG (Secondary Cell Group) may perform QoS control. This makes it possible to reduce, for example, the amount of processing in the MCG. As another example, the MCG and the SCG may each perform QoS control. This makes it possible to improve the flexibility of QoS control.

[0391] As another example, QoS control may be performed in a cell group through which a QoS flow to be QoS controlled passes. For example, when the QoS flow passes through an MCG bearer, the MCG may perform QoS control. When the QoS flow passes through a split bearer, the MCG and the SCG may each perform QoS control. This, for example, makes it possible to improve the flexibility of QoS control. As another example, when the QoS flow passes through a split bearer, the MCG may perform QoS control. This, for example, makes it possible to avoid the complexity of QoS control.

[0392] As another example, a cell group performing SDAP processing may perform QoS control. The cell group may be an MCG or an SCG. This allows, for example, the same cell group to perform QoS flow mapping and QoS control, and as a result, the amount of processing for QoS flow mapping and QoS control can be reduced.

[0393] As another example, a cell group performing PDCP processing may perform QoS control. The QoS control may be applied, for example, when performing the processing of the second modification of the third embodiment. This makes it possible to reduce the amount of processing in the communication system, for example, in the processing of the second modification of the third embodiment.

[0394] As another example, the cell group performing the RLC process may perform the QoS control, which enables flexible QoS control that takes into account, for example, the RLC ARQ.

[0395] As another example, a cell group performing MAC processing may perform QoS control. The QoS control may be applied, for example, when performing the processing of the first modification of the third embodiment. This makes it possible to reduce the amount of processing in the communication system, for example, in the processing of the first modification of the third embodiment.

[0396] The MCG may notify the SCG of information related to the survival time. The information may be, for example, (1) to (16) disclosed above as examples of QoS parameters related to the survival time. This makes it possible to prevent, for example, discrepancies in QoS control of the survival time between the MCG and the SCG, and as a result, makes it possible to improve the stability of the operation in the communication system.

[0397] Information regarding the survival time may be acquired (or monitored). The monitored information may be, for example, (1) to (16) disclosed as examples of QoS parameters related to the survival time. For example, with respect to (1) above, a timer for the survival time may be provided.

[0398] The above-mentioned monitoring may be performed by the UE. The layer that performs the above-mentioned monitoring in the UE may be RRC, SDAP, PDCP, RLC, or MAC. As another example, the V2X layer in the sidelink (see Non-Patent Document 28 (TS23.287)) may perform the above-mentioned monitoring. In the layer that performs the above-mentioned monitoring, for example, a survival time timer may be provided. For example, the timer may be started when a HARQ NACK or a DCI for retransmission is received. This allows, for example, the UE to quickly reflect a transmission failure in the HARQ layer in the survival time timer.

[0399] The UE may notify the base station of the information monitored above. The notification may use RRC signaling. This allows, for example, the UE to transmit a lot of information to the base station. As another example, the notification may use MAC signaling. This allows, for example, the UE to notify the base station quickly. As another example, the notification may use L1 / L2 signaling. This allows, for example, the UE to notify the base station even more quickly. The base station may use the information to control the communication system. For example, the base station may change the coding rate in scheduling for the UE when the number of consecutive communication failures becomes equal to or exceeds a predetermined value. This allows, for example, the expiration of the survival time to be prevented.

[0400] As another example, the UE may report the information to the AMF, and the reporting may be performed using NAS signaling. The AMF may use the information to control the communication system.

[0401] As another example of the above-mentioned monitoring, the monitoring may be performed by a base station. For example, the monitoring may be performed by a CU or a DU. The layer that performs the above-mentioned monitoring in the base station may be RRC, SDAP, PDCP, RLC, or MAC. In the layer that performs the above-mentioned monitoring, for example, a survival time timer may be provided. For example, when a HARQ NACK or a DCI for retransmission is received, the timer may be started. This allows, for example, the base station to quickly reflect a transmission failure in the HARQ layer in the survival time timer.

[0402] The base station may report the above-mentioned monitored information to the UE. In another example, the base station may report the information to the AMF. The AMF may use the information to control the communication system.

[0403] As another example of the above-mentioned monitoring, the monitoring may be performed by a core NW device. The above-mentioned core NW device may be a UPF, an AMF, or an SMF. For example, the UPF may perform the monitoring on U-plane data, and the AMF may perform the monitoring on C-plane data. The AMF may perform the monitoring on small data.

[0404] According to the third embodiment, QoS control using survival time is possible for both the network device and the UE, and as a result, communication that satisfies the requirements of the application layer is possible.

[0405] Variation 1 of embodiment 3 QoS control using survival time may be used in MAC. The MAC layer of the UE and / or the base station may have a survival time timer. In the communication system, for example, transmission of data with a short time remaining until the expiration of the survival time timer may be preferentially scheduled.

[0406] A survival time timer may be provided for each logical channel, which allows, for example, increased flexibility in the communication system.

[0407] A parameter indicating priority in MAC scheduling (see non-patent document 17 (3GPPTS38.321 V15.8.0)) may be dynamically variable. For example, a value obtained by subtracting a predetermined value (hereinafter, sometimes referred to as a priority offset) from the priority value in non-patent document 17 using the time until the survival timer expires may be used in scheduling. The parameter indicating priority may be a parameter in which the lower the value, the higher the priority.

[0408] The subtracted priority value may not be less than a predetermined threshold. When the subtracted priority value is less than the predetermined threshold, the UE may set the subtracted priority value to the same value as the predetermined threshold. The predetermined threshold may be determined by a standard, or may be determined by a base station and notified to the UE. This makes it possible to prevent, for example, the subtracted priority value from falling outside the range defined by the standard, and as a result, to prevent malfunction in the LCP. In addition, as another example, it is possible to prevent the priority from being excessively high in the priority offset.

[0409] The priority offset may be a uniform value within the survival time tolerance, which may avoid design complexity in, for example, the LCP.

[0410] As another example, the priority offset may be variable within the survival time tolerance. For example, when there is little time left until the survival time timer expires, the priority offset may be increased. This allows, for example, even when a HARQ retransmission occurs, the retransmission to be transmitted with priority, and as a result, the retransmission can be transmitted before the survival time timer expires.

[0411] A priority offset may be given for each scheduling unit of time. For example, within a time range until the expiration of the survival time timer, a higher priority offset may be set for later times. This, for example, in addition to the above-mentioned effects, makes it possible to flexibly allocate logical channels in the LCP. The scheduling unit of time may be a subframe, a slot, a minislot, or a symbol.

[0412] Fig. 18 is a diagram illustrating an example of priority offset assignment for a logical channel having a survival time requirement. Fig. 18 shows an example in which, after a survival time timer is started, the priority offset is set to be larger as the remaining time of the timer decreases.

[0413] FIG. 18 shows an example in which the time when the priority offset value becomes constant varies depending on the offset value. In contrast, the time when the priority offset value becomes constant may be constant regardless of the offset value. This makes it possible to avoid design complexity in the processing of the LCP of the UE, for example.

[0414] The priority offset may be predefined by a standard. For example, a uniform offset amount may be defined. Alternatively, an offset amount may be defined for each scheduling timing. Alternatively, the offset amount may be defined in association with the range of the remaining time until the expiration of the survival time timer. As an example of the association between the range of the remaining time and the offset amount, the time range from the start of the survival time timer to its expiration may be divided, and an offset amount may be defined for each divided range. For example, an offset amount for the range from the start of the survival time timer to the remaining half until its expiration, and an offset amount for the range from the remaining half until its expiration may be defined.

[0415] The logical channel to which the priority offset is applied may be predefined in the standard. For example, the priority offset may be applied to a logical channel for which a survival time requirement is set. This allows, for example, the priority of the logical channel to be higher than other logical channels, thereby allowing the survival time requirement to be met.

[0416] As another example, the base station may determine the priority offset and notify the UE. For example, RRC signaling may be used for the notification. The notification may include information on the logical channel. The information may include information on the offset amount. The UE may apply the offset included in the notification to the logical channel included in the notification. The information on the offset amount may be the same as the offset amount predetermined by the standard. This allows the base station to notify the UE of a lot of information, for example, and therefore improves the flexibility in setting the priority offset.

[0417] As another example of the notification, MAC signaling may be used. The notification may include information on a logical channel or may include information on an offset. The information on the offset may be information similar to an offset amount predetermined in a standard. The UE may apply the offset included in the notification to the logical channel included in the notification. This allows the UE to quickly apply the offset, for example.

[0418] As another example of the notification, L1 / L2 signaling may be used. The notification may include information about a logical channel or may include information about an offset. The notification may be included in a DCI including a scheduling grant, may be included in a different DCI, or may be transmitted by a different L1 / L2 signaling. The information about the offset may be the same as an offset amount predefined in a standard, or may be an offset amount applied in the grant. This allows, for example, the UE to apply the offset more quickly.

[0419] A plurality of pieces of information regarding the offset amount may be provided. The plurality of pieces of information may be defined by a standard, may be determined by a base station and notified to the UE, or may be determined by an upper NW device and notified to the UE via the base station. The base station may notify the UE of an identifier of the information to be used among the plurality of pieces of information. The identifier may be notified by RRC signaling, MAC signaling, or L1 / L2 signaling. The notification may include information regarding a logical channel to which the offset is applied. The UE may derive the information to be used by using the identifier. The base station may determine the information to be used by using a setting from an upper NW device, for example, a QoS parameter. Alternatively, the base station may determine the information to be used by using information regarding network slicing. This makes it possible to reduce the amount of signaling from the base station to the UE, for example.

[0420] The following (1) to (6) are disclosed as examples of information regarding the amount of priority offset that the base station notifies the UE of.

[0421] (1) Survival time value.

[0422] (2) Information about the logical channel to which the priority offset applies.

[0423] (3) The number of priority offset patterns to be assigned.

[0424] (4) The priority offset value.

[0425] (5) The remaining survival timer time to which the priority offset is applied.

[0426] (6) A combination of (1) to (5) above.

[0427] The information (1) above may be a value of a survival time timer. The information (1) above may be information including, for example, the allowable number of consecutive transmission failures and a transmission cycle. For example, the information (1) above may be an initial value of a survival time timer. This makes it possible to avoid, for example, complexity in setting a priority offset in the UE.

[0428] The information (2) above may be, for example, a logical channel identifier (LCID), which allows, for example, a MAC layer of a UE to quickly identify a logical channel to which a priority offset is to be assigned.

[0429] The information in (3) above may be the number of stages of priority offset given to the logical channel. The number of stages may or may not include the case where there is no priority offset. For example, in the case where a certain priority offset is assigned during the period from when the remaining time of the survival time timer is less than half until the timer expires, the value in (3) above may be 1. This allows, for example, the MAC layer of the UE to quickly grasp the number of stages of the priority offset. As a result, the processing speed in the UE can be improved.

[0430] The information in (4) above may be a value of a priority offset given to the logical channel. As another example, the information in (4) above may be an increment of the priority offset value. This allows, for example, the UE to appropriately assign a priority offset to the logical channel. As a result, the stability of the communication system can be improved.

[0431] The information in (5) above may be, for example, the value of the timer at which the offset in (4) above is applied. This allows, for example, the UE to appropriately apply a priority offset to the logical channel. As a result, the stability of the communication system can be improved.

[0432] The information items (4) and (5) may be provided in multiple numbers, for example, the number of values ​​of the information item (3). This allows, for example, the UE to appropriately assign a priority offset to the logical channel. As a result, the stability of the communication system can be improved.

[0433] The UE may provide an offset to the priority value by using the information notified from the base station. The offset may be provided for each logical channel or for each HARQ process ID.

[0434] The UE may start the survival time timer when receiving a HARQ NACK, or may start the survival time timer when receiving scheduling information for HARQ retransmission. The base station may start the survival time timer when transmitting a HARQ NACK to the UE, or may start the survival time timer when transmitting scheduling information for HARQ retransmission. This makes it possible to prevent discrepancies in the survival time timer values ​​between the UE and the base station, and as a result, it is possible to prevent malfunctions in the communication system.

[0435] The method disclosed in this first modification may be used after the expiration of the survival time timer. For example, a predetermined priority offset may be provided after the expiration of the survival time timer. Also, for example, a predetermined priority offset may be provided in the Application Recovery Time described in Non-Patent Document 23 (TR22.832). The priority offset after the expiration of the survival time timer may be set in the same manner as the priority offset before the expiration of the timer. The UE may use the setting to provide a priority offset after the expiration of the survival time timer. This makes it possible to quickly recover from a state in which an application is disconnected due to the expiration of the survival time timer, for example.

[0436] According to the first modification, the UE can transmit data with priority when there is little time left until the expiration of the survival time timer, and as a result, it is possible to prevent the expiration of the survival time timer.

[0437] Variation 2 of embodiment 3 A survival time may be used in controlling packet duplication. For example, packet duplication may be performed automatically when the survival time timer starts. For example, the UE may automatically initiate packet duplication upon receiving scheduling information for HARQ retransmission. The scheduling information may include scheduling information for transmission of the duplicated packet.

[0438] In the above, the following problems occur. It is being discussed to set the maximum number of packets to four (see Non-Patent Document 24 (3GPP RP-192590)). In this case, since the number of packets to be automatically replicated is not disclosed, a discrepancy in operation occurs between the UE and the base station. For example, even though the base station expects a packet replication number of four, the UE may replicate a packet in two and transmit it. In that case, the use of reception resources in the base station becomes inefficient.

[0439] In this second modification, a method for solving the above-mentioned problems will be disclosed.

[0440] The number of packet copies is controlled using the survival time. The UE implicitly changes the number of packet copies using the survival time. For example, the UE may vary the number of packet copies using the time until the expiration of the survival timer. The base station implicitly controls the number of packet copies using the survival time timer. For example, the base station may schedule transmission resources used by the UE using the time until the expiration of the survival timer. The number of packet copies may be increased, for example, as the expiration of the survival time timer approaches.

[0441] Implicit packet duplication may involve implicit control of activation / deactivation of a leg used in packet duplication.

[0442] CA may be used for implicit packet duplication. The base station may notify the UE of information about a cell used in implicit packet duplication. The UE may use the information to transmit and receive data to and from the base station using the cell in implicit packet duplication. This may provide, for example, a frequency diversity effect in implicit packet duplication. As a result, reliability in implicit packet duplication can be improved.

[0443] DC may be used for implicit packet duplication. The base station may notify the UE of information on cells used in implicit packet duplication. The notification from the base station to the UE may include information on cells in the MCG or may include information on cells in the SCG. The UE may notify a cell group added in DC of information indicating that implicit packet duplication is to be started. The cell group may be an SCG or an MCG. The cell group may start receiving or transmitting the duplicated packets using the notification from the UE. This, for example, provides the effects of frequency diversity and spatial diversity in implicit packet duplication, and as a result, the reliability of implicit packet duplication can be improved.

[0444] CA and DC may be used in combination for implicit packet duplication. In packet duplication using the combination of CA and DC, the UE may notify the cell group added in DC of information indicating that implicit packet duplication is to be started.

[0445] Fig. 19 is a diagram illustrating an example of implicit control of the number of packet copies in a logical channel having a survival time requirement, in which the number of packet copies is set to be larger as the remaining time of the survival time timer decreases after the timer is started.

[0446] 19 shows an example in which the time when the number of packet copies becomes constant varies depending on the number of copies. In contrast, the time when the number of packet copies becomes constant may be constant regardless of the number of copies. This makes it possible to avoid, for example, the complexity of designing packet copy processing by the UE.

[0447] The number of packet copies may be predefined by a standard. For example, a uniform number of copies may be defined. Alternatively, the number of packet copies may be defined for each scheduling timing. Alternatively, the number of packet copies may be defined in association with the range of the remaining time until the expiration of the survival time timer. As an example of the association between the range of the remaining time and the number of packet copies, the time range from the start of the survival time timer to its expiration may be divided, and the number of packet copies may be defined for each divided range. For example, the number of packet copies for the range from the start of the survival time timer to the remaining half until its expiration, and the number of packet copies for the range from the remaining half until its expiration to its expiration may be defined.

[0448] The logical channel to which the implicit control of the number of packet copies is applied may be predefined in the standard. For example, the implicit control of the number of packet copies may be applied to a logical channel for which a survival time requirement is set. This allows, for example, packet copies to be automatically applied in the logical channel, thereby improving the reliability of the logical channel.

[0449] As another example, the base station may determine the packet duplication number and notify the UE. For example, RRC signaling may be used for the notification. The notification may include information on the logical channel. The information may include information on the packet duplication number or information on the remaining time of the survival time timer. The UE may apply the packet duplication number included in the notification to the logical channel included in the notification. The information on the packet duplication number may be the same as the packet duplication number predetermined by the standard. This allows the base station to notify the UE of more information, for example, and thus improves the flexibility of the implicit control of the packet duplication number.

[0450] As another example of the notification, MAC signaling may be used. The notification may include information on a logical channel, information on the remaining time of a survival time timer, or information on the number of packet copies. The information on the number of packet copies may be the same as the number of packet copies predefined in a standard. The UE may apply the number of packet copies included in the notification to the logical channel included in the notification. This allows the UE to quickly reflect the control of the number of packet copies, for example.

[0451] As another example of the notification, L1 / L2 signaling may be used. The notification may include information about a logical channel, information about the remaining time of a survival time timer, or information about the number of packet copies. The notification may be included in a DCI including a scheduling grant, or may be included in a different DCI, or may be transmitted by a different L1 / L2 signaling. The information about the number of packet copies may be the same as the number of packet copies predefined in a standard, or may be the number of packet copies applied in the grant. This allows, for example, the UE to more quickly apply control of the number of packet copies.

[0452] A plurality of pieces of information regarding the number of packet duplications may be provided. The plurality of pieces of information may be defined by a standard, may be determined by a base station and notified to the UE, or may be determined by an upper NW device and notified to the UE via the base station. The base station may notify the UE of an identifier of the information to be used among the plurality of pieces of information. The identifier may be notified by RRC signaling, MAC signaling, or L1 / L2 signaling. The notification may include information regarding a logical channel to which the number of packet duplications is applied. The UE may derive the information to be used by using the identifier. The base station may determine the information to be used by using a setting from an upper NW device, for example, a QoS parameter. Alternatively, the base station may determine the information to be used by using information regarding network slicing. This makes it possible to reduce, for example, the amount of signaling from the base station to the UE.

[0453] The following items (1) to (8) are disclosed as examples of information related to implicit control of the number of packet duplications that the base station notifies the UE of.

[0454] (1) Survival time value.

[0455] (2) Information about the radio bearer to which the implicit control of the number of packet copies applies.

[0456] (3) The number of packet duplication patterns.

[0457] (4) Number of packet duplications.

[0458] (5) Whether or not DC applies.

[0459] (6) Information about cells used for packet duplication.

[0460] (7) The remaining time on the survival time timer to which the packet duplication count is applied.

[0461] (8) A combination of (1) to (7) above.

[0462] The information in (1) above may be an initial value of a survival time timer, or may be information including, for example, the number of consecutive transmission failures allowed and a transmission cycle. This makes it possible to avoid complexity in controlling the number of packet duplications in the UE, for example.

[0463] The information (2) above may be, for example, a data radio bearer identifier (DRB-ID) before packet duplication is performed, which allows, for example, the PDCP layer of the UE to quickly determine the radio bearer for which implicit packet duplication control is performed.

[0464] The information in (3) above may be the number of packet duplication patterns given in the radio bearer. The number of stages may or may not include the case of no packet duplication. For example, in the case where packet duplication with a duplication number of 4 is performed during the period from when the remaining time of the survival time timer becomes less than half until the timer expires, the value in (3) above may be 1. This allows, for example, the PDCP layer of the UE to quickly grasp the number of packet duplication stages. As a result, the processing speed in the UE can be improved.

[0465] The information (4) above may be the number of packet copies in the radio bearer. As another example, the information (4) above may be an increment in the number of packet copies. This allows, for example, the UE to appropriately control packet copies in the radio bearer. As a result, the stability of the communication system can be improved.

[0466] As another example of the information (4) above, information on the number of packet copies in each of the MCG and SCG may be included. For example, the information may be included when DC is used in implicit packet copy. This allows, for example, improved flexibility in implicit packet copy.

[0467] The information of (5) above may be, for example, information indicating whether DC is used for implicit packet duplication at the timing of (7) above. The UE may start or stop packet duplication using DC using the information of (5) above. This allows, for example, improved flexibility in implicit packet duplication.

[0468] The information in (6) above may be, for example, a cell identifier. The information in (6) above may include information about a cell of an MCG used in implicit packet duplication, may include information about a cell of an SCG, or may include both of the above. The UE may transmit and receive data to and from a base station using a cell indicated in the information in (6) above. This makes it possible to reduce, for example, the amount of processing related to implicit packet duplication in the UE.

[0469] The information in (7) above may be, for example, the number of copies in (4) above and / or the value of the timer at which the DC in (5) above is started. This allows, for example, the UE to appropriately control packet duplication in the radio bearer. As a result, the stability of the communication system can be improved.

[0470] The information items (4) to (7) may be provided in multiple numbers, for example, the number of pieces of information may be the same as the value of the information item (3). This allows, for example, the UE to appropriately control packet duplication of the radio bearer, thereby improving the stability of the communication system.

[0471] The base station may change the implicit packet duplication setting. The base station may change the implicit packet duplication setting, for example, by using a measurement report from the UE. The base station may notify the UE of the changed setting. The notification of the changed setting may include, for example, the information (1) to (8) disclosed as information related to implicit control of the number of packet duplications. This allows, for example, the base station to select an appropriate cell or cell group according to the communication quality with the UE, thereby improving the reliability of communication.

[0472] As in the first modification of the third embodiment, the UE may start the survival time timer upon receiving a HARQ NACK, or upon receiving scheduling information for HARQ retransmission. The base station may start the survival time timer upon transmitting a HARQ NACK to the UE, or upon transmitting scheduling information for HARQ retransmission. This makes it possible to prevent discrepancies in the survival time timer values ​​between the UE and the base station, and as a result, to prevent malfunctions in the communication system.

[0473] The notification from the UE to the cell group may be performed using L1 / L2 signaling, MAC signaling, or RRC signaling. The L1 / L2 signaling may be, for example, SR. For example, the UE may use L1 / L2 signaling for the notification, which allows the UE to quickly notify the cell group.

[0474] The UE may notify the cell group of information indicating that implicit packet duplication is stopped. The notification may be performed, for example, when a survival time timer is stopped or initialized. The cell group may stop receiving or not transmitting the duplicated packets using the notification from the UE. This allows, for example, efficient use of frequency and time resources in the cell group. The notification from the UE to the cell group indicating the stop of implicit packet duplication may be performed in the same manner as the notification indicating the start of implicit packet duplication.

[0475] The UE may request the base station to change the setting related to implicit packet duplication. The change request may be, for example, a request to increase the number of duplications, a request to decrease the number of duplications, a request for packet duplication using DC, a request for release of packet duplication using DC, or a combination of two or more of the above. The base station may use the request to change the setting related to implicit packet duplication. The base station may notify the UE of the changed setting. The notification of the changed setting may include, for example, the information (1) to (8) disclosed as information related to implicit control of the number of packet duplications. This makes it possible to improve the reliability of implicit packet duplication, for example.

[0476] For example, RRC signaling may be used for the request. For example, the RRC signaling may be signaling requesting RRC reconfiguration. The signaling may be newly provided. This allows, for example, a lot of information to be transmitted from the UE to the base station. As another example, MAC signaling may be used for the request. This allows, for example, the UE to quickly notify the base station of the request. As another example, L1 / L2 signaling may be used for the request. This allows, for example, the UE to more quickly notify the base station of the request.

[0477] The method disclosed in the present modified example 2 may be used after the expiration of the survival time timer. For example, implicit packet duplication may be performed after the expiration of the survival time timer, or implicit packet duplication may be performed during the Application Recovery Time described in Non-Patent Document 23 (TR22.832). The setting of implicit packet duplication after the expiration of the survival time timer may be performed in the same manner as the setting of implicit packet duplication before the expiration of the timer. The UE may use the setting to perform implicit packet duplication after the expiration of the survival time timer. This makes it possible to quickly recover from a state in which an application is disconnected due to the expiration of the survival time timer, for example.

[0478] According to the present modification 2, the UE can improve the reliability of data transmission when there is little time left until the expiration of the survival time timer, and as a result, it is possible to prevent the expiration of the survival time timer.

[0479] Variation 3 of embodiment 3 Scheduling using the survival time may be performed. For example, the scheduling for the UE may be automatically changed using the remaining time of the survival time timer. The UE may change and use the scheduling for its own UE using information on the remaining time of the survival time timer.

[0480] As examples of automatic schedule changes using survival time, the following (1) to (7) are disclosed.

[0481] (1) Configured Grant.

[0482] (2) Information regarding the cells used for transmission and reception.

[0483] (3) Information about the beams and / or antenna panels used by the UE.

[0484] (4) Information regarding the beams, antenna panels, and / or TRPs used by the base station.

[0485] (5) Information about the base station to which the UE transmits and receives data.

[0486] (6) Information regarding the UE that transmits and receives data.

[0487] (7) A combination of (1) to (6) above.

[0488] The above-mentioned (1) preset grant may be, for example, a grant that allocates a large frequency resource when the remaining time of the survival time timer reaches a predetermined time. This allows, for example, the UE to transmit uplink data at a low coding rate. As a result, the reliability of communication can be improved.

[0489] In the above (2), for example, when the remaining time of the survival timer reaches a predetermined time, a cell with a low frequency may be used. This makes it possible to select a cell using a frequency with less chance of occlusion when there is little time left until the survival timer expires. As a result, it is possible to improve the reliability of communication.

[0490] In the above (3), for example, when the remaining time of the survival time timer reaches a predetermined time, the beam and / or antenna panel to be used by the UE may be designated. The beam to be used by the UE may be, for example, a beam of the SRS, or may be designated by information on the DMRS antenna port (for example, the DMRS antenna port number). The above (3) may be applied, for example, to uplink communication. This makes it possible to improve the reliability of uplink communication, for example.

[0491] The base station may measure uplink signals from the UE to each antenna panel and / or TRP of the base station. The uplink signals measured by the base station may be SRS or DMRS. The base station may measure the shadowing frequency. The base station may hold the uplink measurement results. For example, the base station may hold information (e.g., a database) regarding the reliability of the uplink signals. This allows the base station to quickly select a beam, antenna panel, and / or TRP with high reliability, for example.

[0492] In the above (4), for example, when the remaining time of the survival time timer reaches a predetermined time, the beam and / or antenna panel to be used by the base station may be designated. The above (4) may be applied, for example, to downlink communication. This makes it possible to improve the reliability of downlink communication, for example.

[0493] The UE may measure downlink signals from each antenna panel and / or TRP of the base station. The UE may measure, for example, CSI-RS from the base station or SS blocks. The UE may measure information about the occlusion frequency of the downlink signal. The UE may report information about the measurement result of the downlink signal to the base station. The UE may report, for example, the measurement result about the occlusion frequency of the downlink signal to the base station. The information about the occlusion frequency may be, for example, the number of times that the reception strength of the downlink signal falls below a predetermined threshold within a predetermined time, or the time that the reception strength of the downlink signal falls below a predetermined threshold. The base station may use the information to determine the beam, antenna panel, and / or TRP to be used for downlink communication with the UE. This makes it possible to avoid beams that are prone to occlusion in downlink communication between the base station and the UE. As a result, it is possible to improve the reliability of downlink communication.

[0494] Regarding the above (3) and / or (4), the base station may notify the measurement results of the uplink signal and / or the downlink signal to the NWDAF (Network Data Analytics Function, see Non-Patent Document 31 (TS23.288)). The measurement results may include, for example, information on the occlusion frequency. An interface may be provided between the base station and the NWDAF. The NWDAF may use the measurement results to generate or hold information (for example, a database) on the reliability of the uplink signal and / or the downlink signal. The NWDAF may notify the base station of the information on the reliability. The base station may use the information on the reliability to determine the beam and / or antenna panel to be used by the UE, or may determine the beam and / or antenna panel to be used by the base station itself. This makes it possible to reduce the amount of processing of the base station regarding, for example, the above (3) and (4).

[0495] The UE may notify the NWDAF of the measurement result of the downlink signal. An interface may be provided between the UE and the NWDAF. The NWDAF may generate or store information regarding the reliability of the downlink signal using the information from the UE. This may, for example, reduce the amount of processing in the base station.

[0496] As another example, information regarding the occlusion frequency may be notified to the NWDAF by OAM (Operations, Administration and Maintenance). The OAM may derive the occlusion frequency using a measurement result of the UE. The OAM may include the information regarding the occlusion frequency to the NWDAF in a notification of information regarding RSRP, in a notification of information regarding RSRQ, or in a notification of information regarding SINR. This makes it possible to reduce the amount of signaling in a communication system, for example.

[0497] As another example, the NWDAF may derive information on the shadowing frequency. The NWDAF may derive information on the shadowing frequency using, for example, information on RSRP, information on RSRQ, and / or information on SINR notified to the NWDAF by OAM (Operations, Administration and Maintenance). The NWDAF may notify the information on the shadowing frequency to the OAM, to the base station, to the AMF, to the SMF, to the UPF, to the PCF, or to the AF (Application Function). For example, the base station may use the information on the shadowing frequency to determine information on (3) and / or (4) above. This, for example, can reduce the amount of signaling in the communication system and improve the reliability of communication between the base station and the UE.

[0498] The above-mentioned (5) may be, for example, an identifier of a base station to which the UE is to transmit and receive (for example, gNB-ID), an identifier indicating whether the base station is a master base station or a secondary base station, or a serial number given to a base station to which the UE is connected. Each of the above-mentioned identifiers may be applied, for example, when the UE uses a DC configuration, or when multi-connectivity is used (for example, when the UE is connected to three or more base stations). This, for example, can provide a spatial diversity effect, which can improve reliability.

[0499] The above-mentioned (6) may be, for example, a UE identifier (for example, a UE-ID) or an identifier assigned to each UE in an application device. The above-mentioned (6) may be applied, for example, to a case where a plurality of UEs are mounted in one application device. This can provide, for example, the same effect as the above-mentioned (5).

[0500] The base station may inform the UE of scheduling information, and the UE may use the information to transmit and receive data to and from the base station.

[0501] The following (1) to (5) are disclosed as examples of information related to scheduling that the base station notifies the UE of.

[0502] (1) Survival time value.

[0503] (2) The number of automatic scheduling patterns.

[0504] (3) Information regarding automatic scheduling.

[0505] (4) The remaining survival time timer to which automatic scheduling is applied.

[0506] (5) A combination of (1) to (4) above.

[0507] The above-mentioned information (1) may be the same as the information (1) disclosed as the information on the offset amount of priority in the first modification of the third embodiment. This makes it possible to avoid, for example, complexity in setting automatic scheduling in the UE.

[0508] The information (2) above may be the same as the information (3) disclosed as the information on the priority offset amount in the first modification of the third embodiment. This allows, for example, the UE to quickly grasp the number of stages of automatic scheduling, and as a result, the processing speed in the UE can be improved.

[0509] The information (3) above may be the information (1) to (7) disclosed as examples of automatic scheduling changes using survival time in this modification 3. This enables, for example, appropriate scheduling from the base station to the UE, and as a result, the stability of the communication system can be improved.

[0510] The information in (4) above may be the same as the information in (5) disclosed as the information on the priority offset amount in the first modification of the third embodiment. This enables, for example, appropriate scheduling from the base station to the UE, and as a result, the stability of the communication system can be improved.

[0511] The information items (3) and (4) may be provided in multiple numbers, for example, the number of values ​​of the information item (2) may be provided. This allows, for example, appropriate scheduling from the base station to the UE, which results in improved stability in the communication system.

[0512] According to the third modification, the base station can perform highly reliable scheduling for the UE in transmitting data when there is little time left until the expiration of the survival time timer, thereby making it possible to prevent the expiration of the survival time timer.

[0513] The above-described embodiments and their modifications are merely examples, and the embodiments and their modifications can be freely combined. In addition, any of the components of the embodiments and their modifications can be modified or omitted as appropriate.

[0514] For example, in each of the above-mentioned embodiments and their modifications, a subframe is an example of a time unit of communication in a fifth generation base station communication system. It may be a scheduling unit. In each of the above-mentioned embodiments and their modifications, the processing described as a subframe unit may be performed in a TTI unit, a slot unit, a subslot unit, or a minislot unit.

[0515] For example, the methods disclosed in the above-mentioned embodiments and their modified examples may be applied not only to V2X (Vehicle-to-everything) services but also to services using SL communication. SL communication is used in many types of services, such as proximity-based services, public safety, communication between wearable terminals, and communication between devices in factories. The methods disclosed in the above-mentioned embodiments and their modified examples may be applied to SL communication used in such many types of services.

[0516] Although the present disclosure has been described in detail, the above description is illustrative in all respects and does not limit the present disclosure. It is understood that countless variations not illustrated can be assumed without departing from the scope of the present disclosure. [Explanation of symbols]

[0517] 200, 210 communication system, 202 communication terminal device, 203 base station device.

Claims

1. A terminal device having a plurality of SIMs (Subscriber Identity Modules) and configured to connect to a plurality of networks using the plurality of SIMs, the plurality of networks includes a first network and a second network; The terminal device is configured to transmit, to a base station device of the first network, information indicating whether the terminal device receives paging from the first network. Terminal device.

2. The information includes information regarding paging that the terminal device does not receive. The terminal device according to claim 1 .

3. the terminal device is configured to determine a prioritized type of paging; the information includes information regarding the type of prioritized paging. The terminal device according to claim 1 .

4. The information on the type of paging indicates that the terminal device is to preferentially receive paging for voice calls. The terminal device according to claim 3.

5. The first network includes an Access and Mobility Management Function (AMF), The terminal device is configured to receive, from the AMF, a Non-Access Stream (NAS) signaling including information indicating whether the terminal device receives paging from the first network; The terminal device according to claim 1 .

6. The NAS signaling includes information regarding prioritized paging. The terminal device according to claim 5.

7. a plurality of networks including a first network and a second network; A base station device in a communication system including: a terminal device having a plurality of SIMs (Subscriber Identity Modules) and configured to connect to the plurality of networks using the plurality of SIMs; the first network includes the base station device; the base station apparatus is configured to receive, from the terminal apparatus, information indicating whether the terminal apparatus receives paging from the first network; Base station equipment.

8. a plurality of networks including a first network and a second network; A terminal device having a plurality of SIMs (Subscriber Identity Modules) and configured to connect to the plurality of networks using the plurality of SIMs, the first network includes a base station device; The terminal device is configured to transmit, to the base station device, information indicating whether the terminal device receives paging from the first network. Communication systems.

Images