Terminal device, base station device, and communication system

Abstract

The invention relates to a terminal device, a base station device and a communication system. A communication system includes a communication terminal and a plurality of networks configured so as to be capable of wireless communication with the communication terminal. A priority is assigned to at least one of a paging timing and a paging type for paging transmitted from each of a plurality of networks. The communication terminal selects the received paging based on the priority.

Description

This invention application is a divisional application of the invention patent application with international application number PCT / JP2021 / 004583, international application date February 8, 2021, application number 202180011937.7 entering the Chinese national phase, and name “Communication system, communication terminal and network”. Technical Field

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

[0002] In the 3rd Generation Partnership Project (3GPP), a standardization organization for mobile communication systems, a communication method called Long Term Evolution (LTE) in terms of the wireless section and System Architecture Evolution (SAE) in terms of the overall system structure including the core network and the radio access network (hereinafter collectively referred to as the network) is studied (for example, non-patent documents 1 to 5). This communication method is also called a 3.9G (3.9 Generation) system.

[0003] As the access method of LTE, OFDM (Orthogonal Frequency Division Multiplexing) is used in the downlink direction, and SC-FDMA (Single Carrier Frequency Division Multiple Access) is used in the uplink direction. In addition, unlike W-CDMA (Wideband Code Division Multiple Access), LTE does not include line switching and is only a packet communication method.

[0004] use Figure 1 The following describes the decisions regarding the frame structure of the LTE system in 3GPP described in Non-Patent Document 1 (Chapter 5). Figure 1 This is an explanatory diagram showing the structure of a radio frame used in a communication system of the LTE method. Figure 1In the radio frame, a radio frame is 10ms. The radio frame is divided into 10 subframes of equal size. The subframe is divided into 2 slots of equal size. The first subframe and the sixth subframe of each radio frame contain the downlink synchronization signal. The synchronization signal includes the first synchronization signal (Primary Synchronization Signal: P-SS) and the second synchronization signal (Secondary Synchronization Signal: S-SS).

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

[0006] The Physical Broadcast Channel (PBCH) is a downlink transmission channel from a base station device (hereinafter sometimes referred to as "base station") to a communication terminal device (hereinafter sometimes referred to as "communication terminal") such as a mobile terminal device (hereinafter sometimes referred to as "mobile terminal"). The BCH transport block is mapped to four subframes in a 40ms interval. There is no clear signaling of 40ms timing.

[0007] The Physical Control Format Indicator Channel (PCFICH) is a downlink transmission channel 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 in each subframe.

[0008] The Physical Downlink Control Channel (PDCCH) is a channel for downlink transmission from the base station to the communication terminal. PDCCH notifies the resource allocation information of the downlink shared channel (DL-SCH), which is one of the transmission channels described later, the resource allocation information of the paging channel (PCH), which is one of the transmission channels described later, and the HARQ (Hybrid Automatic Repeat reQuest) information related to the DL-SCH. PDCCH transmits the uplink scheduling grant. PDCCH transmits the response signal for the uplink transmission, namely Ack (Acknowledgement) / Nack (Negative Acknowledgement). PDCCH is also called L1 / L2 control signal.

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

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

[0011] The Physical Uplink Control Channel (PUCCH) is a channel for uplink transmission from the communication terminal to the base station. PUCCH transmits the response signal (response signal) for downlink transmission, namely Ack / Nack. PUCCH transmits CSI (Channel State Information). CSI is composed of RI (Rank Indicator), PMI (Precoding Matrix Indicator), and CQI (Channel Quality Indicator) reports. RI refers to the rank information of the channel matrix of MIMO. PMI refers to the information of the precoding waiting matrix used in MIMO. CQI refers to quality information indicating the quality of the received data, or indicating the quality of the communication line. And PUCCH transmits a scheduling request (Scheduling Request: SR).

[0012] The 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. PHICH transmits Ack / Nack, a response signal for uplink transmission. The Physical Random Access Channel (PRACH) is a channel for uplink transmission from a communication terminal to a base station. PRACH transmits a random access preamble.

[0014] The downlink reference signal (Reference Signal: RS) is a codeword known as a communication system in the LTE mode. The following five types of downlink reference signals are defined. Cell-specific Reference Signal (CRS), MBSFN Reference Signal (MBSFN Reference Signal), UE-specific Reference Signal (UE-specific Reference Signal) i.e., Data Demodulation Reference Signal (Demodulation Reference Signal: DM-RS), Positioning Reference Signal (Positioning Reference Signal: PRS), and Channel State Information Reference Signal (Channel State Information Reference Signal: CSI-RS). As a measurement of the physical layer of the communication terminal, there is a measurement of the received power of the reference signal (Reference Signal Received Power: RSRP).

[0015] In the LTE communication system, the uplink reference signal is also a known symbol. The following two types of uplink reference signals are defined: a data demodulation reference signal (Demodulation Reference Signal: DM-RS) and a sounding reference signal (Sounding Reference Signal: SRS).

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

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

[0018] The Paging Channel (PCH) supports DRX of the communication terminal in order to reduce the power consumption of the communication terminal. The PCH is required to be broadcast to the entire coverage area of ​​the base station (cell). The PCH is mapped to a physical resource such as the Physical Downlink Shared Channel (PDSCH) that can be dynamically used for traffic.

[0019] The multicast channel (MCH) is used to broadcast to the entire coverage area of ​​the base station (cell). MCH supports SFN synthesis of MBMS (Multimedia Broadcast Multicast Service) services (MTCH and MCCH) in multi-cell transmission. MCH supports quasi-static resource allocation. MCH is mapped to PMCH.

[0020] Retransmission control based on HARQ (Hybrid ARQ) is applied to the uplink shared channel (UL-SCH) in the uplink transmission channel. UL-SCH supports dynamic or semi-static resource allocation. UL-SCH is mapped to the physical uplink shared channel (PUSCH).

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

[0022] HARQ is explained. HARQ is a technology that improves the communication quality of a transmission line by combining automatic repeat request (ARQ) and forward error correction (forward error correction). HARQ has the following advantages: even for a transmission line with changed communication quality, error correction can be effectively used by retransmission. In particular, when retransmission is performed, the quality can be further improved by synthesizing the reception result of the initial transmission and the reception result of the retransmission.

[0023] An example of the retransmission method is described. When the receiving side cannot correctly decode the received data, in other words, when a CRC (Cyclic Redundancy Check) error occurs (CRC=NG), "Nack" is sent from the receiving side to the sending side. The sending side that receives "Nack" retransmits the data. When the receiving side can correctly decode the received data, in other words, when no CRC error occurs (CRC=OK), "Ack" is sent from the receiving side to the sending side. The sending side that receives "Ack" sends the next data.

[0024] The logical channel described in Non-Patent Document 1 (Chapter 6) is described below. The Broadcast Control Channel (BCCH) is a downlink channel for broadcasting system control information. The BCCH as a logical channel is mapped to the Broadcast Channel (BCH) as a transport channel or the Downlink Shared Channel (DL-SCH).

[0025] The Paging Control Channel (PCCH) is a downlink channel used to send paging information and changes to system information. 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] The Common Control Channel (CCCH) is a channel used to send control information between a communication terminal and a base station. The CCCH is used when there is no RRC connection between the communication terminal and the network. In the downlink direction, the CCCH is mapped to the downlink shared channel (DL-SCH) as a transmission channel. In the uplink direction, the CCCH is mapped to the uplink shared channel (UL-SCH) as a transmission channel.

[0027] The Multicast Control Channel (MCCH) is a downlink channel used for point-to-multipoint transmission. The MCCH is used to send MBMS control information for one or more MTCHs from the network to the communication terminal. The MCCH is only used by the communication terminal during the MBMS reception process. The MCCH is mapped to the Multicast Channel (MCH) as a transport channel.

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

[0029] Dedicated Traffic Channel (DTCH) is a point-to-point communication channel used to send user information to dedicated communication terminals. DTCH exists in both uplink and downlink. DTCH is mapped to the uplink shared channel (UL-SCH) in the uplink and to the downlink shared channel (DL-SCH) in the downlink.

[0030] The multicast traffic channel (MTCH) is a downlink channel for transmitting traffic data from the network to the communication terminal. The MTCH is a channel used only for the communication terminal in the MBMS reception process. The MTCH is mapped to the multicast channel (MCH).

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

[0032] The location tracking of the communication terminal is performed in units of an area consisting of one or more cells. The location tracking is performed to track the location of the communication terminal even in the standby state, so as to call the communication terminal, in other words, to be able to call the communication terminal. The area used for the location tracking of the communication terminal is called a tracking area.

[0033] In addition, 3GPP is advancing the standardization of Long Term Evolution Advanced (LTE-A) as Release 10 (see Non-Patent Documents 3 and 4). LTE-A is based on the wireless communication method of LTE and is constructed by adding some new technologies thereto.

[0034] In the LTE-A system, in order to support a wider frequency bandwidth (transmission bandwidths) up to 100 MHz, carrier aggregation (CA) of aggregating (also called aggregation) two or more component carriers (CC) is studied. CA is described in Non-Patent Document 1.

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

[0036] According to the capability of the UE (capability), a secondary cell (SCell) is formed to form a group 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] For one UE, a group of service cells consisting of one PCell and one or more SCells is formed.

[0038] In addition, new technologies of LTE-A include technologies supporting wider bandwidth (Wider bandwidth extension) and coordinated multiple point transmission and reception (CoMP) technologies, etc. CoMP, which is being studied to implement LTE-A in 3GPP, is described in Non-Patent Document 1.

[0039] In addition, in order to cope with the large amount of traffic in the future, 3GPP is studying the use of small eNBs (hereinafter sometimes referred to as "small-scale base station devices") that constitute small cells. For example, the following technologies are being studied, namely, by setting up multiple small eNBs and constituting multiple small cells to improve frequency utilization efficiency and increase communication capacity. Specifically, there is dual connectivity (DC) in which a UE connects to two eNBs for communication. DC is described in Non-Patent Document 1.

[0040] Sometimes, one of the eNBs performing dual connectivity (DC) is called a master "eNB (abbreviated as MeNB)", and the other is called a "secondary eNB (abbreviated as SeNB)".

[0041] Mobile network traffic is increasing, and communication speeds are also increasing. If LTE and LTE-A are put into full-scale use, communication speeds will be further increased.

[0042] In addition, the fifth generation (hereinafter sometimes referred to as "5G") wireless access system is being studied with the goal of starting service for the upgraded mobile communication after 2020. For example, in Europe, the METIS organization is summarizing the requirements for 5G (see Non-Patent Document 5).

[0043] In the 5G wireless access system, with respect to the LTE system, assuming that the system capacity is 1000 times, the data transmission speed is 100 times, the data processing delay is 1 / 10, and the number of simultaneous connections of communication terminals is 100 times, further low power consumption and low cost of the device can be listed as necessary conditions.

[0044] In order to meet such requirements, 3GPP is advancing the discussion of 5G standards as Release 15 (see Non-Patent Documents 6 to 18). The technology of the wireless section of 5G is called "New Radio Access Technology" ("New Radio" is abbreviated as "NR").

[0045] Discussions on the NR system based on the LTE system and LTE-A system are continuously advancing, but changes and additions from the LTE system and LTE-A system are made in the following point.

[0046] As the access method of NR, OFDM is used in the downlink direction, and OFDM and DFT-s-OFDM (DFT-spread-OFDM) are used in the uplink direction.

[0047] In NR, higher frequencies can be used compared to LTE to increase transmission speeds and reduce processing delays.

[0048] In NR, a narrow beam-shaped transmission and reception range is formed (beam forming) and the direction of the beam is changed (beam scanning) in an effort to ensure cell coverage.

[0049] The NR frame structure supports various subcarrier spacings, that is, various parameter sets (Numerology). In NR, one subframe is 1 millisecond, and one time slot consists of 14 symbols, regardless of the parameter set. In addition, the number of time slots contained in one subframe is one in the parameter set with a subcarrier spacing of 15kHz, and increases in proportion to the subcarrier spacing in other parameter sets (refer to non-patent document 13 (TS38.211 V16.0.0)).

[0050] The downlink synchronization signal in NR is sent from the base station as a synchronization signal burst (Synchronization Signal Burst; sometimes referred to as SS burst below) at a specified period for a specified duration. The SS burst consists of a synchronization signal module (Synchronization Signal Block; sometimes referred to as SS module below) for each beam of the base station. The base station changes the beam to send the SS module of each beam during the duration of the SS burst. The SS module consists of P-SS, S-SS and PBCH.

[0051] In NR, a phase tracking reference signal (PTRS) is added as a downlink reference signal of NR to reduce the influence of phase noise. PTRS is also added to the uplink reference signal in the same way as the downlink.

[0052] In NR, in order to flexibly switch DL / UL within a time slot, a time slot format indication (Slot Format Indication: SFI) is added to the information included in the PDCCH.

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

[0054] In 3GPP, as DC methods, DC performed by LTE base stations and NR base stations connected to EPC, DC performed by NR base stations connected to 5G core systems, and DC performed by LTE base stations and NR base stations connected to 5G core systems are discussed (refer to non-patent documents 12, 16, and 19).

[0055] In addition, 3GPP is studying some new technologies, such as the operation of a terminal using a plurality of SIMs (Subscriber Identity Modules) (see Non-Patent Document 20). Prior art literature 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: “Senarios, requirements and KPIs for 5G mobile and wireless system”, ICT-317669-METIS / D1.1 Non-patent document 6: 3GPP TR 23.799 V14.0.0 Non-patent document 7: 3GPP TR 38.801 V14.0.0 Non-patent document 8: 3GPP TR 38.802 V14.2.0 Non-patent document 9: 3GPP TR 38.804 V14.0.0 Non-patent document 10: 3GPP TR 38.912 V15.0.0 Non-patent document 11: 3GPP RP-172115 Non-patent document 12: 3GPP TS 37.340 V16.0.0 Non-patent document 13: 3GPP TS 38.211 V16.0.0 Non-patent document 14: 3GPP TS 38.213 V16.0.0 Non-patent document 15: 3GPP TS 38.214 V16.0.0 Non-patent document 16: 3GPP TS 38.300 V16.0.0 Non-patent document 17: 3GPP TS 38.321 V15.8.0 Non-patent document 18: 3GPP TS 38.212 V16.0.0 Non-Patent Document 19: 3GPP RP-161266 Non-patent document 20: 3GPP RP-193263 Non-patent document 21: 3GPP TS23.041V16.2.0 Non-patent document 22: 3GPP TS 38.331 V15.8.0 Non-patent document 23: 3GPP TR 22.832 V17.1.0 Non-patent document 24: 3GPP RP-192590 Non-patent document 25: 3GPP TR 23.734 V16.2.0 Non-patent document 26: 3GPP TS 38.304 V15.6.0 Non-patent document 27: 3GPP TS23.501V16.3.0 Non-patent document 28: 3GPP TS23.287V16.1.0 Non-patent document 29: 3GPP TS 38.322 V15.5.0 Non-patent document 30: 3GPP TS 38.323 V15.6.0 Non-patent document 31: 3GPP TS23.288V16.2.0 Non-patent document 32: 3GPP TS24.501V16.3.0 Summary of the invention Technical problem to be solved by the invention

[0057] In 3GPP, the operation of UE using multiple SIMs is discussed. For example, countermeasures when the paging from two NWs to the UE is timed to be repeated, and a method for notifying the category of data involved in the paging is discussed (refer to non-patent document 20). However, a specific method for determining which NW to receive the paging from is not disclosed. Therefore, for example, when the conflicting paging includes paging for emergency communications such as ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System), the UE is unable to receive the paging for the emergency communication. As a result, the following problem occurs: the UE cannot quickly receive the emergency communication.

[0058] In view of the above problems, one of the objects of the present disclosure is to provide a technology that enables rapid NW connection. Technical means for solving technical problems

[0059] The communication system involved in the present disclosure includes: a communication terminal; and multiple networks, which are configured to enable wireless communication with the communication terminal. The communication system is characterized in that, for a paging sent from each of the multiple networks, a priority is assigned to at least one of a paging timing and a paging category, and the communication terminal selects a received paging based on the priority. The communication terminal involved in the present disclosure is configured to be able to communicate wirelessly with multiple networks. The communication terminal is characterized in that, for a paging sent from each of the multiple networks, a priority is assigned to at least one of a paging timing and a paging category, and the communication terminal selects the received paging based on the priority. The network involved in the present disclosure is configured to be able to communicate wirelessly with a communication terminal, and the network is characterized in that, for a paging sent from the network, priorities are assigned to a paging timing and a paging category, the priority of the paging timing and the priority of the paging category correspond to each other, and the network selects the paging to be sent based on the correspondence between the priority of the paging timing and the priority of the paging category. Effects of the Invention

[0060] According to the present disclosure, rapid NW connection can be performed.

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

[0062] Figure 1This is an explanatory diagram showing the structure of a radio frame used in a communication system of the LTE method. Figure 2 This is a block diagram showing the overall configuration of a communication system 200 of the LTE scheme being discussed in 3GPP. Figure 3 This is a block diagram showing the overall structure of the NR-based communication system 210 discussed in 3GPP. Figure 4 This is a structural diagram of DC based on eNB and gNB connected to EPC. Figure 5 This is a structural diagram of the DC based on the gNB connected to the NG core. Figure 6 This is a structural diagram of DC based on eNB and gNB connected to the NG core. Figure 7 This is a structural diagram of DC based on eNB and gNB connected to the NG core. Figure 8 It is shown Figure 2 A block diagram of the structure of the mobile terminal 202 is shown. Fig. 9 It is shown Figure 2 A block diagram of the structure of the base station 203 is shown. Fig.10 is a block diagram showing the structure of an MME. Fig.11 It is a block diagram showing the structure of 5GC. Fig.12 This is a flowchart showing an overview of operations from cell search to standby performed by a communication terminal (UE) in a communication system using the LTE method. Fig.13 is a diagram showing an example of a cell structure in an NR system. Fig.14 This is an architectural diagram showing an example of connection between a UE equipped with multiple SIMs and multiple NWs in Embodiment 1. Fig.15 This is a diagram showing a first example of allocation of timing priorities of paging from a plurality of NWs and paging received by a UE in the first embodiment. Fig.16 This is a diagram showing a second example of allocation of timing priorities of paging from a plurality of NWs and paging received by a UE in the first embodiment. Fig.17 This is a flowchart showing an example of the action of stopping and resuming the RLF timer class accompanying the switching of the UE's transmission and reception target in implementation method 2. Fig.18This is a diagram illustrating the assignment of priority offsets in logical channels having a lifetime requirement in Variation 1 of Implementation Example 3. Fig.19 This is a diagram illustrating implicit control of the number of packet copies in a logical channel with a lifetime requirement in Variation 2 of Implementation Example 3. DETAILED DESCRIPTION

[0063] Implementation method 1. Figure 2 1 is a block diagram showing the overall structure of a communication system 200 of the LTE method discussed in 3GPP. Figure 2 The wireless access network is referred to as E-UTRAN (Evolved Universal Terrestrial Radio Access Network) 201. The communication terminal device, i.e., the mobile terminal device (hereinafter referred to as "mobile terminal (User Equipment: UE)") 202 can wirelessly communicate with the base station device (hereinafter referred to as "base station (E-UTRAN NodeB: eNB)") 203, and transmit and receive signals by wireless communication.

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

[0065] If the control protocols for the mobile terminal 202, such as RRC (Radio Resource Control), and the user plane (hereinafter sometimes also referred to as U-Plane), such as PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer) are terminated at the base station 203, then the E-UTRAN is composed of one or more base stations 203.

[0066] The 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 are RRC_IDLE and RRC_CONNECTED.

[0067] In RRC_IDLE, PLMN (Public Land Mobile Network) selection, system information (SI) broadcasting, paging, cell reselection, mobility, etc. are performed. In RRC_CONNECTED, the mobile terminal has an RRC connection and can send and receive data with the network. In addition, in RRC_CONNECTED, handover (HO), neighbor cell measurement, etc. are performed.

[0068] The base station 203 is composed of one or more eNBs 207. In addition, the system composed of EPC (Evolved Packet Core) as the core network and E-UTRAN 201 as the radio access network is called EPS (Evolved Packet System). Sometimes, EPC as the core network and E-UTRAN 201 as the radio access network are collectively referred to as "network".

[0069] The eNB 207 is connected to a Mobility Management Entity (MME), a Serving Gateway (S-GW), or an MME / S-GW unit (hereinafter sometimes referred to as an "MME unit") 204 including the MME and the S-GW via an S1 interface, and control information is communicated between the eNB 207 and the MME unit 204. One eNB 207 can be connected to multiple MME units 204. 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 the connection between the eNB 207 as a base station and the mobile terminal (UE) 202. The MME unit 204 constitutes the EPC as a core network. The base station 203 constitutes the E-UTRAN 201.

[0071] The base station 203 may constitute one cell or multiple cells. Each cell has a predetermined range as a range in which communication with the mobile terminal 202 can be performed, i.e., a coverage range, and wireless communication is performed with the mobile terminal 202 within the coverage range. When one base station 203 constitutes multiple cells, each cell is configured to be able to communicate with the mobile terminal 202.

[0072] Figure 32 is a block diagram showing the overall structure of a 5G communication system 210 discussed in 3GPP. Figure 3 For explanation. The radio access network is called NG-RAN (Next Generation Radio Access Network: Next Generation Radio Access Network) 211. UE 202 can wirelessly communicate with the NR base station device (hereinafter referred to as "NR base station (NG-RAN NodeB: gNB)") 213 to send and receive signals in the form of wireless communication. In addition, the core network is called 5G Core (5G Core: 5GC).

[0073] If the control protocols for UE202, such as RRC (Radio Resource Control), and the user plane (hereinafter sometimes also 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) are terminated at the NR base station 213, then 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 UE202 and NR base station 213 is the same as that of LTE. The states between NR base station 213 and UE202 in RRC include RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.

[0075] RRC_IDLE and RRC_CONNECTED are the same as LTE. RRC_INACTIVE maintains the connection between the 5G core and the NR base station 213 while performing broadcasting of system information (SI), paging, cell reselection, movement, etc.

[0076] gNB217 is connected to the access / mobility management function (Access and Mobility Management Function: AMF), session management function (Session Management Functio: SMF), or UPF (User Plane Function), or the AMF / SMF / UPF unit (hereinafter sometimes referred to as "5GC unit") 214 including AMF, SMF and UPF through the NG interface. Communication of control information and / or user data is performed between gNB217 and the 5GC unit 214. The NG interface is a general term for the N2 interface between gNB217 and AMF, the N3 interface between gNB217 and UPF, the N11 interface between AMF and SMF, and the N4 interface between UPF and SMF. One gNB217 can be connected to multiple 5GC units 214. gNB217 are connected to each other through the Xn interface, and communication of control information and / or user data is performed between gNB217.

[0077] The NR base station 213 is also the same as the base station 203 and can constitute one or more cells. When one NR base station 213 constitutes multiple cells, each cell is configured to be able to communicate with the UE 202.

[0078] gNB217 can be divided into a central unit (Central Unit; sometimes referred to as CU below) 218 ​​and a distributed unit (Distributed Unit: sometimes referred to as DU below) 219. CU218 is configured as one in gNB217. DU219 is configured as one or more in gNB217. CU218 is connected to DU219 via an F1 interface, and control information and / or user data are communicated between CU218 and DU219.

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

[0080] The 5G communication system may include the Non-3GPP Interworking Function (N3IWF) described in Non-Patent Document 27 (3GPP TS23.501 V16.3.0). The N3IWF can terminate the Access Network (AN) between the UE and the UE in the non-3GPP access between the UE and the UE.

[0081] Figure 4 This is a diagram showing the structure of DC performed by eNB and gNB connected to EPC. Figure 4 In the figure, the solid line indicates the connection of U-Plane, and the dotted line indicates the connection of C-Plane. Figure 4 In the example, eNB 223-1 is the primary base station and gNB 224-2 is the secondary base station (this DC structure is sometimes referred to as EN-DC). Figure 4 In the figure, an example is shown in which the U-Plane connection between the MME unit 204 and the gNB 224-2 is performed via the eNB 223-1, but it can also be performed directly between the MME unit 204 and the gNB 224-2.

[0082] Figure 5 1 is a diagram showing the structure of a DC based on a gNB connected to an NG core. Figure 5 In the figure, the solid line indicates the connection of U-Plane, and the dotted line indicates the connection of C-Plane. Figure 5 In this example, gNB224-1 is the primary base station and gNB224-2 is the secondary base station (this DC structure is sometimes referred to as NR-DC). Figure 5 In the figure, an example is shown in which the U-Plane connection between the 5GC unit 214 and the gNB 224-2 is performed via the gNB 224-1, but it can also be performed directly between the 5GC unit 214 and the gNB 224-2.

[0083] Figure 6 This is a diagram showing the structure of DC performed by eNB and gNB connected to the NG core. Figure 6 In the figure, the solid line indicates the connection of U-Plane, and the dotted line indicates the connection of C-Plane. Figure 6 In the example, eNB 226-1 is the primary base station and gNB 224-2 is the secondary base station (this DC structure is sometimes referred to as NG-EN-DC). Figure 6 In the figure, an example is shown in which the U-Plane connection between the 5GC unit 214 and the gNB 224-2 is performed via the eNB 226-1, but it can also be performed directly between the 5GC unit 214 and the gNB 224-2.

[0084] Figure 7This is a diagram showing other structures of DC performed by eNB and gNB connected to the NG core. Figure 7 In the figure, the solid line indicates the connection of U-Plane, and the dotted line indicates the connection of C-Plane. Figure 7 In the example, gNB 224-1 is the primary base station and eNB 226-2 is the secondary base station (this DC structure is sometimes referred to as NE-DC). Figure 7 In the figure, an example is shown in which the U-Plane connection between the 5GC unit 214 and the eNB 226-2 is performed via the gNB 224-1, but it can also be performed directly between the 5GC unit 214 and the eNB 226-2.

[0085] Figure 8 It shows Figure 2 The structure of the mobile terminal 202 is shown in FIG. Figure 8 The transmission processing of the mobile terminal 202 shown in the figure is explained. First, the control data from the protocol processing unit 301 and the user data from the application unit 302 are saved in the transmission data buffer unit 303. The data saved in the transmission data buffer unit 303 is transmitted to the encoding unit 304 to implement encoding processing such as error correction. There may also be data that is directly output from the transmission data buffer unit 303 to the modulation unit 305 without implementing encoding processing. The data after the encoding processing by the encoding unit 304 is modulated in the modulation unit 305. Precoding in MIMO may also be performed in the modulation unit 305. The modulated data is converted into a baseband signal, and then output to the frequency conversion unit 306, and converted into a wireless transmission frequency. Thereafter, the transmission signal is sent from the antennas 307-1 to 307-4 to the base station 203. In Figure 8 , the example shows a case where the number of antennas is 4, but the number of antennas is not limited to 4.

[0086] In addition, the receiving process of the mobile terminal 202 is performed as follows. The wireless signal from the base station 203 is received through the antennas 307-1 to 307-4. The received signal is converted from the wireless receiving frequency to the baseband signal in the frequency conversion unit 306, and demodulated in the demodulation unit 308. In the demodulation unit 308, waiting calculation and multiplication processing can be performed. The demodulated data is transmitted to the decoding unit 309 for decoding processing such as error correction. Among the decoded data, the control data is transmitted to the protocol processing unit 301, and the user data is transmitted to the application unit 302. A series of processing of the mobile terminal 202 is controlled by the control unit 310. Therefore, although in Figure 8 Although omitted in FIG. 3 , the control unit 310 is connected to each of the units 301 to 309. Figure 8 In the present invention, the number of antennas used by the mobile terminal 202 for sending may be the same as or different from the number of antennas used for receiving.

[0087] Fig. 9 It is shown Figure 2 The structure of the base station 203 is shown in FIG. Fig. 9 The sending processing of the base station 203 shown is explained. The EPC communication unit 401 performs data transmission and reception between the base station 203 and the EPC (MME unit 204, etc.). The 5GC communication unit 412 performs data transmission and reception between the base station 203 and the 5GC (5GC unit 214, etc.). The other base station communication unit 402 performs data transmission and reception with other base stations. The EPC communication unit 401, the 5GC communication unit 412 and the other base station communication unit 402 respectively exchange information with 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 saved in the sending data buffer unit 404.

[0088] The data stored in the transmission data buffer unit 404 is transmitted to the encoding unit 405 to implement encoding processing such as error correction. There may also be data that is directly output from the transmission data buffer unit 404 to the modulation unit 406 without implementing encoding processing. The encoded data is modulated in the modulation unit 406. Precoding in MIMO may also be performed in the modulation unit 406. The modulated data is converted into a baseband signal and then output to the frequency conversion unit 407 to be converted into a wireless transmission frequency. Thereafter, the transmission signal is sent to one or more mobile terminals 202 using antennas 408-1 to 408-4. Fig. 9 , the example shows a case where the number of antennas is 4, but the number of antennas is not limited to 4.

[0089] In addition, the receiving processing of the base station 203 is performed as follows. The wireless signal from one or more mobile terminals 202 is received by the antenna 408. The received signal is converted from the wireless receiving frequency to a baseband signal by the frequency conversion unit 407, and is demodulated in the demodulation unit 409. The demodulated data is transmitted to the decoding unit 410 for decoding processing such as error correction. Among the decoded data, the control data is transmitted to the protocol processing unit 403 or the 5GC communication unit 412 or the EPC communication unit 401, and other base station communication units 402, and the user data is transmitted to the 5GC communication unit 412, the EPC communication unit 401 and other base station communication units 402. A series of processing of the base station 203 is controlled by the control unit 411. Therefore, although in Fig. 9 Although omitted in FIG. 4 , the control unit 411 is connected to each unit 401 to 410. Fig. 9 In the example, the number of antennas used by the base station 203 for sending may be the same as or different from the number of antennas used for receiving.

[0090] Fig. 92 is a block diagram showing the structure of the base station 203, but the same structure can be used for the base station 213. Figure 8 and Fig. 9 , the number of antennas of the mobile terminal 202 and the number of antennas of the base station 203 may be the same or different.

[0091] Fig.10 is a block diagram showing the structure of an MME. Fig.10 In the above Figure 2 The structure of MME204a included in the MME unit 204 shown. The PDN GW communication unit 501 transmits and receives data between MME204a and PDN GW. The base station communication unit 502 transmits and receives data between MME204a and base station 203 via the S1 interface. In the case where the data received from the PDN GW is user data, the user data is transmitted from the PDN GW communication unit 501 to the base station communication unit 502 via the user plane communication unit 503, and is sent to one or more base stations 203. In the case where the data received from the base station 203 is user data, the user data is transmitted from the base station communication unit 502 to the PDN GW communication unit 501 via the user plane communication unit 503, and is sent to the PDN GW.

[0092] When the data received from the PDN GW is control data, the control data is transmitted 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 transmitted 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 all processing for the control plane (hereinafter, sometimes also referred to as C-Plane). The NAS security unit 505-1 performs the security of NAS (Non-Access Stratum) messages, etc. The SAE bearer control unit 505-2 performs the management of SAE (System Architecture Evolution) bearers, etc. The idle state mobility management unit 505-3 performs mobility management in the idle state (idle state; LTE-IDLE state, or simply idle), generation and control of paging signals in the idle state, addition, deletion, update, retrieval, and tracking area list management of one or more mobile terminals 202 under coverage, etc.

[0094] MME204a distributes paging signals to one or more base stations 203. In addition, MME204a performs mobility control in the idle state. MME204a manages the tracking area list when the mobile terminal is in the idle state and in the active state. MME204a starts the paging protocol by sending a paging message to the cell belonging to the tracking area registered by the UE. The management of the CSG of the eNB207 connected to MME204a, the management of the CSG ID, and the whitelist management can be performed by the idle state mobility management unit 505-3.

[0095] Fig.11 It is a block diagram showing the structure of 5GC. Fig.11 The above Figure 3 The structure of the 5GC unit 214 is shown. Fig.11 Shown in Figure 5 The 5GC unit 214 shown includes the structure of AMF, the structure of SMF, and the structure of UPF. The data network communication unit 521 performs data transmission and reception between the 5GC unit 214 and the data network. The base station communication unit 522 performs data transmission and reception between the 5GC unit 214 and the base station 203 through the S1 interface, and / or performs data transmission and reception between the 5GC unit 214 and the base station 213 through the NG interface. In the case where the data received from the data network is user data, the user data is transmitted from the data network communication unit 521 to the base station communication unit 522 via the user plane communication unit 523, and is sent to one or more base stations 203 and / or base stations 213. In the case where the data received from the base station 203 and / or the base station 213 is user data, the user data is transmitted from the base station communication unit 522 to the data network communication unit 521 via the user plane communication unit 523, and is sent to the data network.

[0096] When the data received from the data network is control data, the control data is transmitted 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 transmits the control data to the control plane control unit 525. When the data received from the base station 203 and / or the base station 213 is control data, the control data is transmitted from the base station communication unit 522 to the control plane control unit 525. The control plane control unit 525 transmits 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 (IdleState) mobility management unit 525-3, etc., and performs all processing for the control plane (hereinafter, sometimes also referred to as C-Plane). The NAS security unit 525-1 performs the security of NAS (Non-Access Stratum) messages, etc. The PDU session control unit 525-2 manages the PDU session between the mobile terminal 202 and the 5GC unit 214, etc. The idle state mobility management unit 525-3 performs mobility management in the standby state (idle state (Idle State); RRC_IDLE state, or simply called idle), generation and control of paging signals in the standby state, addition, deletion, update, retrieval, and tracking area list management of one or more mobile terminals 202 under coverage, etc.

[0098] The 5GC unit 214 allocates paging signals to one or more base stations 203 and / or base stations 213. In addition, the 5GC unit 214 performs mobility control in the idle state. The 5GC unit 214 manages the tracking area list when the mobile terminal is in the idle state, in the inactive state, and in the active state. The 5GC unit 214 starts the paging protocol by sending a paging message to the cell belonging to the tracking area registered by the UE.

[0099] Next, an example of a cell search method in a communication system is shown. Fig.12 This is a flowchart showing an overview of the cell search and standby operation performed by a communication terminal (UE) in an LTE communication system. If the communication terminal starts the cell search, in step ST601, the first synchronization signal (P-SS) and the second synchronization signal (S-SS) sent from the surrounding base stations are used to synchronize the slot timing and the frame timing.

[0100] P-SS and S-SS are collectively referred to as synchronization signals (SS). Synchronization codes corresponding to the PCIs assigned to each cell are allocated to the synchronization signal (SS). It is studied to set the number of PCIs to 504. Synchronization is achieved using these 504 PCIs, and the PCI of the synchronized cell is detected (determined).

[0101] Next, in step ST602, the reference signal (RS) sent from the base station to each cell, i.e., the cell-specific reference signal (CRS), is detected for the synchronized cell, and the RS received power (RSRP) is measured. The reference signal (RS) uses a code that corresponds to the PCI one-to-one. This code can be used to obtain correlation and separate from other cells. By deriving the RS code for the cell based on the PCI determined in step ST601, the RS can be detected and the RS received power can be measured.

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

[0103] Then, in step ST604, the PBCH of the best cell is received to obtain the broadcast information, i.e., the BCCH. The MIB (Master Information Block) containing the cell structure information is mapped in the BCCH on the PBCH. Therefore, by receiving the PBCH and obtaining the BCCH, the MIB can be obtained. The information of the MIB includes, for example, the DL (downlink) system bandwidth (also called the transmission bandwidth configuration (transmission bandwidth configuration: dl-bandwidth)), the number of transmitting antennas, and the SFN (System Frame Number: system frame number).

[0104] Then in step ST605, the DL-SCH of the cell is received based on the cell structure information of the MIB, and the SIB (System Information Block) 1 in the broadcast information BCCH is obtained. SIB1 contains information related to accessing the cell, information related to cell selection, and scheduling information of other SIBs (SIBk; k is an integer ≥ 2). In addition, SIB1 also contains the Tracking Area Code (TAC).

[0105] Then in step ST606, the communication terminal compares the TAC of SIB1 received in step ST605 with the TAC part of the tracking area identity (TAI) in the tracking area list already held by the communication terminal. The tracking area list is also called the TAI list. TAI is identification information for identifying the tracking area, and is composed of MCC (Mobile Country Code), MNC (Mobile Network Code), and TAC (Tracking Area Code). MCC is the country code. MNC is the network code. TAC is the code number of the tracking area.

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

[0107] exist Fig.12 In the example shown, an example of the action from cell search to standby in the LTE mode is shown, but in the NR mode, in addition to the best cell, the best beam can also be selected in step ST603. In addition, in the NR mode, in step ST604, beam information such as a beam identifier can be obtained. In addition, in the NR mode, in step ST604, scheduling information of the remaining minimum SI (Remaining Minimum SI: RMSI) can be obtained. In the NR mode, in step ST605, it can be set to receive RMSI.

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

[0109] Due to the popularity of smartphones and tablet terminals, the volume of cellular wireless communications has exploded, causing concerns about the shortage of wireless resources worldwide. In order to cope with this situation and improve the efficiency of frequency utilization, research has been conducted on miniaturization of cells and promotion of spatial separation.

[0110] In the existing cell structure, a cell formed by an eNB has a wide coverage area. Conventionally, cells are formed so that a certain area is covered by a wide coverage area of ​​a plurality of cells formed by a plurality of eNBs.

[0111] When the cell is miniaturized, the cell formed by the eNB has a narrower coverage area than the coverage area of ​​the cell formed by the existing eNB. Therefore, as in the prior art, a larger number of eNBs with miniaturized cells are required to cover a certain area than the existing eNBs.

[0112] In the following description, a cell with a relatively large coverage, such as a cell composed of existing eNBs, is referred to as a "macro cell", and an eNB constituting a macro cell is referred to as a "macro eNB". In addition, a cell with a relatively small coverage, such as a cell after cell miniaturization, is referred to as a "small cell", and an eNB constituting a small cell is referred to as a "small eNB".

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

[0114] Small eNBs may be, for example, low-power nodes, local nodes, and hotspots. In addition, small eNBs may be pico eNBs constituting pico cells, femto eNBs constituting femto cells, HeNBs, RRHs (Remote Radio Heads), RRUs (Remote Radio Units), RREs (Remote Radio Equipment), or RNs (Relay Nodes). In addition, small eNBs may also be "local area base stations" or "home base stations" as described in non-patent document 7.

[0115] Fig.13 An example of a cell structure in NR is shown. In a cell in NR, a narrow beam is formed and its direction is changed for transmission. Fig.13In the example shown, the base station 750 uses beam 751-1 at a certain time to transmit and receive with the mobile terminal. At other times, the base station 750 uses beam 751-2 to transmit and receive with the mobile terminal. Similarly, the base station 750 uses one or more of beams 751-3 to 751-8 to transmit and receive with the mobile terminal. Thus, the base station 750 forms a wide range of cells.

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

[0117] The UE can be connected to multiple NWs and can also be in a state where it can be connected. In the following, "connection" not only includes the actual connected state, but sometimes also includes the state where it can be connected. The UE can use multiple SIMs to connect to the multiple NWs. The UE can have only one set of transceivers or multiple sets of transceivers. The multiple NWs can be PLMNs, non-public networks (NPNs) or private networks. The connections to the multiple NWs can be made in parallel.

[0118] Regarding the connection between the UE and each NW, the RRC state of the UE can be the RRC_CONNECTED state, the RRC_INACTIVE state, or the RRC_IDLE state. The CM state of the UE can be the CM-IDLE state or the CM-CONNECTED state. For more than two of the multiple NWs of the connection target, the UE can be in the RRC_CONNECTED state or the CM-CONNECTED state. As another example, for only one of the multiple NWs of the connection target, the UE can be set to the RRC_CONNECTED state or the CM-CONNECTED state.

[0119] Fig.14 This is an architectural diagram showing an example of connection between a UE using multiple SIMs (hereinafter sometimes referred to as a UE equipped with multiple SIMs (Multi-SIM UE)) and multiple NWs. Fig.14 In the example, a UE equipped with multiple SIM cards is connected in parallel to NW#1 and NW#2.

[0120] Fig.14In the example shown, UE1400 is connected to gNB1401 in NW#1. In addition, UE1400 is connected to gNB1411 in NW#2. gNB1401 is connected to AMF1402 and UPF1403 in NW#1. SMF1404 in NW#1 is connected to AMF1402 and UPF1403. gNB1411 is connected to AMF1412 and UPF1413 in NW#2. SMF1414 in NW#2 is connected to AMF1412 and UPF1413.

[0121] Fig.14 , an example in which UE 1400 is connected to two NWs is shown, but UE 1400 may be connected to three or more NWs. In addition, one or more of the two NWs connected to UE 1400 may be NPNs. This is also the case when UE 1400 is connected to three or more NWs.

[0122] In a UE connected to multiple NWs in parallel, the timing of paging sometimes overlaps (hereinafter sometimes referred to as a paging conflict). The UE that generates the paging conflict may be a UE that has only one set of transceivers. In this case, the UE can only receive paging from any NW. Therefore, for example, in a case where the paging for emergency communications such as ETWS and CMAS is included in the conflicting paging, the UE is unable to receive the paging for the emergency communication. As a result, the following problem arises: the UE cannot quickly receive the emergency communication.

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

[0124] Priority is assigned to the timing at which paging can be sent. Hereinafter, this priority may be referred to as timing priority. Priority is assigned to the type of paging. Hereinafter, this priority may be referred to as type priority.

[0125] The timing priority may be, for example, level 2 or level 3 or higher. Parameters related to the timing priority may be set.

[0126] The category priority may be, for example, level 2 or level 3 or higher. Parameters related to the category priority may be set.

[0127] The timing priority is matched with the category priority. For example, when both the timing priority and the category priority are composed of two levels, a higher timing priority can correspond to a higher category priority, and a lower timing priority can correspond to a lower category priority. At the paging timing of the specified timing priority, a paging of the specified category priority can be sent. For example, at a certain paging sending timing, a paging below the category priority corresponding to the timing priority can be sent. In the case where the timing of paging from base stations of multiple NWs conflicts, the UE can receive the paging with a higher timing priority among the conflicting pagings. In the reception of the paging with a higher timing priority, the UE can switch the target NW for transmission and reception. The connection between the UE and the base station of the target NW for transmission and reception can be RRC_CONNECTED, RRC_INACTIVE, or RRC_IDLE. As a result, for example, the UE can receive paging related to emergency communications in priority over other paging.

[0128] As another example, a higher category priority may be sent with a lower timing priority. The above action may be applied, for example, to a situation where a paging with a specified timing priority cannot be received due to a timing conflict with a paging with a higher timing priority from another NW. Thus, for example, in the above situation, a paging with a specified timing priority can be quickly received.

[0129] The UE may expect to send a paging with a category priority lower than the timing priority in the paging timing. That is, the UE may expect not to send a paging with a category priority higher than the timing priority in the paging timing. In the above content, the category priority lower than the timing priority may be a category priority lower than the timing priority, and the paging with a category priority higher than the timing priority may be a paging with a category priority higher than the timing priority.

[0130] As an example related to the allocation of timing priority, when the timing priority is divided into two levels, a high timing priority and a low timing priority may be alternately allocated to each PF (Paging Frame). A high timing priority and a low timing priority may be alternately allocated to each PO (Paging Occasion). A high timing priority and a low timing priority may also be alternately allocated to each PDCCH monitoring opportunity for paging reception.

[0131] The paging for allocating category priorities 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 notifications. As another example, the paging for allocating category priorities may be paging for SI updates or paging for emergency communications. The emergency communications may be, for example, PWS (Public Warning System). The emergency communications may be, for example, ETWS (Earthquake and Tsunami Warning System), CMAS (Commercial Mobile Alert System), EU-ALERT (European Public Warning System), KPAS (Korean Public Alert System), or other emergency communications.

[0132] Emergency communication for private NW (or non-public NW) may be provided. The emergency communication may include emergency communication for private NW. Thus, for example, a failure in an area where private NW is used can be quickly notified to UE.

[0133] As an example of the allocation of category priorities, when there are two levels of category priorities, a high priority may be allocated to emergency communications and SI update paging, and a low priority may be allocated to other paging. As another example, when there are three levels of category priorities, a high priority may be allocated to emergency communications, a medium priority may be allocated to SI update and voice calls, and a low priority may be allocated to other paging.

[0134] The number of levels of the timing priority and the category priority can be the same. Thus, for example, the complexity involved in the correspondence between the timing priority and the category priority can be avoided. As another example, the number of levels of the timing priority and the category priority can be different. Thus, for example, the flexibility of the correspondence between the timing priority and the category priority can be improved.

[0135] A timing priority can be assigned to each PF (Paging Frame). Thus, for example, the NW device can perform the allocation of timing priority with less processing. As another example, the timing priority can be assigned to each PO (Paging Occasion). Thus, for example, the flexibility related to the allocation of timing priority can be improved. As another example, the timing priority can be assigned to each PDCCH monitoring occasion (PDCCH monitoring occasion) for paging reception. Thus, for example, the flexibility related to the allocation of timing priority can be further improved.

[0136] As another example, the timing priority may be allocated to each DRX cycle. This can reduce the amount of processing related to the allocation of the timing priority, for example.

[0137] The allocation of timing priorities can be determined by a standard, thereby, for example, avoiding complexity in the design of the communication system.

[0138] As another example, the allocation of timing priority can be determined by the core NW. As a result, for example, the flexibility related to the allocation of timing priority can be improved. The core NW can be, for example, an AMF or a PCF. The core NW can notify the base station of information related to the determined allocation. The base station can notify the UE of the information related to the allocation separately or by broadcasting. As another related example of notification of the information related to the allocation, the core NW can directly notify the UE. For example, the AMF can use NAS signaling to notify the UE of the information.

[0139] As another example related to the allocation of timing priorities, the allocation may be determined by the base station. Thus, for example, the flexibility related to the allocation of timing priorities can be further improved. The base station may notify the UE of the information related to the allocation individually or broadcast it.

[0140] A parameter for determining the timing priority can be set. The parameter can be, for example, a UE identifier, or can be the same parameter as the PCCH setting information (PCCH-Config) disclosed in non-patent document 22 (TS38.331). A method for determining the timing priority based on the parameter can be determined by a standard. Thus, for example, the size of the notification of the information required for determining the timing priority can be reduced.

[0141] Each NW may determine the value of the parameter and notify the UE. The notification may be made via the base station. As another example, the base station may determine the value of the parameter and notify or broadcast it 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 can be set. For example, the average value can be the same between NWs and between base stations. This can prevent the UE's paging reception object from being biased towards a specific NW, for example.

[0143] As another example, the average value may be different between NWs. Thus, for example, the difficulty of paging reception of UE can be adjusted between NWs. As another example, the average value may be different between base stations. Thus, for example, the difficulty of paging reception of UE can be adjusted between base stations.

[0144] The average value of the timing priority can be determined by a standard, by the core NW, or by the base station, similarly to the allocation of the timing priority.

[0145] The following (1) to (8) are disclosed as examples of information related to the allocation of timing priorities that is notified or broadcasted by the core NW and / or the base station to the UE.

[0146] (1) Information on the level of timing priority.

[0147] (2) Timing priority value.

[0148] (3) Information related to paging timing.

[0149] (4) Information on the allocation pattern of timing priorities.

[0150] (5) Information on the period of timing priority allocation.

[0151] (6) Paging timing serving as a reference.

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

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

[0154] The number of levels in (1) above may be, for example, 2, or more than 3. For example, when no timing priority is allocated, the number of levels in (1) above may be 1. The UE may use the information in (1) above to obtain the number of timing priority levels. Thus, for example, the amount of processing required for the UE to grasp the allocation of timing priority levels may be reduced.

[0155] The information in (2) may be information indicating high or low priority when the level in (1) is 2, for example. The UE may acquire the timing priority using the information in (2). This can reduce the amount of processing required for the UE to understand the allocation of timing priority, for example.

[0156] The information in (3) above may be, for example, information indicating the number of PFs in a PF within a DRX cycle. Alternatively, the information in (3) above may be, for example, information indicating the number of POs in a PO within a PF. Alternatively, the information in (3) above may be, for example, information indicating the number of PDCCH monitoring timings for paging in a PO. As another example, it may be information indicating the number of POs or PDCCH monitoring timings for paging in a PO or PDCCH monitoring timings for paging within a DRX cycle. Through the information in (3), for example, the UE can quickly grasp the paging timing assigned a specified timing priority.

[0157] As another example, the information in (3) above may include parameters for determining paging timing. The parameters may include part or all of the broadcast information from the base station of the NW, such as the PCCH configuration information (PCCH-Config) disclosed in non-patent document 22 (TS38.331). Thus, for example, the processing amount of the base station in the notification from the base station to the UE can be reduced.

[0158] The information in (4) may be, for example, information indicating a mode in which, in the case of a two-level timing priority, a high timing priority and a low timing priority are alternately assigned to each PF. Alternatively, the information in (4) may be information indicating a mode in which a high timing priority is repeated twice, and then a low timing priority is repeated twice. The PF may be a PO or a PDCCH monitoring opportunity for paging. By using the information in (4), for example, the UE can quickly grasp the allocation of timing priorities.

[0159] The information in (5) may be, for example, information related to the period of the pattern in (4). The information in (5) may be given in a period different from the DRX period. For example, the period of the allocation pattern of the timing priority may span multiple DRX periods. Thus, for example, the following situation can be avoided: the paging of the specified paging timing in a certain NW has a lower timing priority than the paging timing in other NWs and cannot be received.

[0160] The information in (6) may be, for example, information related to the paging timing to which the high timing priority is assigned when the high timing priority and the low timing priority are alternately assigned to each PF. The information in (6) may include information related to the timing priority in the paging timing that serves as the reference. Thus, for example, it is possible to prevent the inconsistency in the understanding related to the allocation of the timing priority between the base station and the UE. As a result, the stability of the operation in the communication system can be improved.

[0161] The information in (7) may be, for example, information indicating which PF, PO or PDCCH monitoring opportunity for paging is allocated to each timing priority within the DRX cycle. The DRX cycle may be PF or PO. By using the information in (7), for example, the UE can quickly grasp the paging timing allocated with a specified timing priority.

[0162] As another example, the information in (7) above may include parameters for determining paging timing for each timing priority. The parameters may include part or all of the broadcast information from the base station of the NW, such as the PCCH setting information (PCCH-Config) disclosed in non-patent document 22 (TS38.331). Thus, for example, the flexibility of paging timing setting in the communication system can be improved.

[0163] The correspondence between the timing priority and the category priority can be determined by a standard. When determining the correspondence, for example, the message identifier disclosed in Section 9.4.1.2.2 of Non-Patent Document 21 (TS23.041 V16.2.0) can be used. This can avoid, for example, the complexity of the design in the communication system.

[0164] As another example, the correspondence between the timing priority and the category priority can be determined by the core NW. As a result, for example, the flexibility related to the correspondence between the two priorities can be improved. The core NW device can be, for example, an AMF or a PCF. The core NW can notify the base station of information related to the determined correspondence. The base station can notify the UE of the information related to the correspondence separately or broadcast it. As another example, the core NW can directly notify the UE of the information. For example, the AMF can use NAS signaling to notify the UE of the information.

[0165] As another example, the base station may determine the correspondence between the timing priority and the category priority. Thus, for example, the flexibility related to the correspondence between the two priorities can be further improved. The base station may notify the UE of the information related to the correspondence individually or broadcast it.

[0166] As another example of the correspondence between the timing priority and the class priority, the above combination can be used. For example, the class priority corresponding to each timing priority can have a prescribed range in the standard, and the core NW uses the prescribed range in the standard to determine the correspondence. Thus, for example, the correspondence can be flexibly performed in the communication system.

[0167] The allocation of class priorities can be determined by standards. For example, the message identifier disclosed in Section 9.4.1.2.2 of Non-Patent Document 21 (TS23.041 V16.2.0) can be used for this allocation. This can avoid, for example, the complexity of the design of the communication system.

[0168] As another example, the allocation of category priorities may be determined by the core NW. Thus, for example, the flexibility associated with the allocation of category priorities may be improved. The core NW device may be, for example, an AMF or a PCF. The core NW may notify the base station of information associated with the determined allocation. The base station may notify the UE of the information associated with the allocation individually or by broadcasting it. As another example related to notification of the information associated with the allocation, the core NW may directly notify the UE. For example, the AMF may use NAS signaling to notify the UE of the information.

[0169] As another example related to the allocation of class priorities, the allocation may be determined by the base station. Thus, for example, the flexibility related to the allocation of class priorities can be further improved. The base station may notify the UE of the information related to the allocation individually or broadcast it.

[0170] As another example related to the allocation of class priorities, the above combination can be used. For example, the class priorities allocated to each category of paging can have a specified range in the standard, and the core NW uses the specified range in the standard to determine the class priority. In this way, for example, the allocation of class priorities of paging can be flexibly performed in the communication system.

[0171] The UE receives a paging with a higher timing priority among pagings of multiple NWs with conflicting timings. If the UE has a single receiver, the UE can perform this action. When receiving a paging with a higher timing priority, the UE can switch the NW to receive. Thus, for example, the UE can receive a paging with a higher priority among multiple pagings with conflicting timings.

[0172] The UE does not need to receive any paging other than the paging with the highest timing priority among the pagings of a plurality of NWs whose timings partially conflict. This can reduce the power consumption of the UE, for example.

[0173] The UE may notify the base station of information about paging that is not receiving (hereinafter sometimes referred to as non-receiving paging). This information may include information about paging from other NWs (hereinafter sometimes referred to as conflicting NWs) that conflict with the non-receiving paging (hereinafter sometimes referred to as conflicting NW paging).

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

[0175] (1) Information related to the timing of non-received paging.

[0176] (2) Information on the timing priority of non-received paging.

[0177] (3) Information related to the identification of the conflicting NW.

[0178] (4) Information related to the timing of conflicting NW paging.

[0179] (5) Information related to the parameter sets in the conflicting NW.

[0180] (6) Information related to frame timing in the conflicting NW.

[0181] (7) Information used to derive the timing of conflicting NW paging.

[0182] (8) Information on the beam used in communication with the conflicting NW.

[0183] (9) Information related to the synchronization signal of the conflicting NW.

[0184] (10) Information related to the Radio Access Technology (RAT) of the conflicting NW.

[0185] (11) Information on the timing priority of paging in the conflicting NW.

[0186] (12) Information related to the use of multiple SIM cards of this UE.

[0187] (13) Information indicating a request for a change in settings related to non-reception paging.

[0188] (14) Information related to category priority.

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

[0190] The information in (1) above may be information indicating which PF, PO or PDCCH monitoring opportunity for paging within the DRX cycle is non-receiving paging. The information in (1) above may be information on the frame number, subframe number, time slot number, or symbol number used for non-receiving paging. Thus, for example, a quick notification from the UE to the base station can be performed.

[0191] The information in (2) above may be the same as the information in (2) disclosed as information about the allocation of timing priorities notified or broadcasted by the core NW and / or the base station to the UE. The information in (2) above can reduce the amount of processing when the base station reallocates timing priorities, for example.

[0192] The information in (3) above may be, for example, the PLMN-ID of the other NW, may include the NPN-ID disclosed in non-patent document 25 (TR23.734), or may include the CAG-ID. Thus, for example, the base station can grasp the NW for which paging conflicts should be avoided, thereby avoiding the complexity of the avoidance process.

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

[0194] The information in (4) above may be, for example, PF (Paging Frame) in other NWs, PO (Paging Occasion), PDCCH monitoring occasion for paging reception, or a combination of the above. This can reduce the amount of processing required for avoiding paging conflicts in the base station, for example.

[0195] As another example, the information in (4) above may include information related to the moment of paging timing in other NWs. The information related to the moment may, for example, include the moment of the starting point of the paging timing, the moment related to the end point of the paging timing, the information related to the duration of the paging timing, or multiple pieces of the above information. The paging timing may be a PF (Paging Frame) in other NWs, a PO (Paging Occasion), a PDCCH monitoring occasion (PDCCH monitoring occasion) for paging reception, or a combination of multiple of the above. Thus, for example, the amount of processing required for the base station to avoid paging conflicts can be reduced.

[0196] The information in (5) above may be, for example, the subcarrier spacing, slot length, or symbol length used by the UE when receiving paging from other NWs. The information in (5) above may be the parameter μ disclosed in Section 4.2 of Non-Patent Document 13 (TS38.211). Thus, for example, the reliability of the base station in avoiding paging conflicts can be improved.

[0197] The information in (6) above may be, for example, information that gives the difference in frame timing between the notification target base station and the base stations of other NWs in SFN units, subframe units, time slot units, symbol units, or the minimum unit in the communication system (e.g., Ts units), or a combination thereof. The time slot may be a time slot in the notification target base station or a time slot in other NWs. Thus, for example, the amount of processing when the base station performs paging conflict avoidance can be reduced.

[0198] As another example, the information in (6) above may be a specified time in other NWs, such as a time at a boundary of a specified SFN. The boundary may be the beginning of the SFN or the end of the SNF. As another example, the information in (6) above may be a time at a specified subframe boundary, a time at a specified time slot boundary, or a time at a specified symbol boundary. The UE may obtain the information by searching for a cell of the other NW or may obtain the information from broadcast information from the other NW. Thus, for example, the amount of processing required for the UE to be notified may be reduced.

[0199] The information in (7) above may include, for example, the identifier of the UE in another NW, or may include a parameter for determining the paging timing in the other NW. The parameter may include part or all of the broadcast information from the base station of the NW, such as the PCCH setting information (PCCH-Config) disclosed in non-patent document 22 (TS38.331). Thus, for example, the amount of processing required in the notification from the UE can be reduced.

[0200] The above-mentioned identifier related to the information in (7) above can 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 S-temporary mobile user identifier), 5G-TMSI (5GTemporary Mobile Subscription Identifier: 5G temporary mobile user identifier) ​​or 5G-GUTI disclosed in non-patent document 27 (TS23.501).

[0201] The above parameters related to the information in (7) above may include the DRX (Discontinuous Reception) cycle (T) of the UE disclosed in non-patent document 26 (TS38.304), the total number of paging frames in the cycle (N), the number of paging occasions in PF (Ns), the offset used in PF determination (PF_offset), and the initial PDCCH monitoring occasion in PO (first-PDCCH-MonitoringOccasionOfPO).

[0202] The information in (8) above may be information about the beam used by the UE in receiving the notification target base station. The beam may be information about the beam used by the UE in receiving the SS block from the base station. The beam may be information about the beam used by the UE in receiving the broadcast information, such as SIB1 or RMSI (Remaining Minimum System Information) from the base station. The base station may use the information in (8) above to change the paging timing in the beam where the UE is located. The base station may change the broadcast information in the beam. Thus, for example, the base station can flexibly change the paging timing.

[0203] The information in (9) above may be, for example, information related to the period of the SS burst, or the duration of the SS block transmission in one period of the SS burst. The base station may use the information in (9) above to, for example, avoid setting the paging timing by avoiding multiple SS burst periods transmitted from base stations of other NWs, or may set the paging timing by avoiding the duration of the SS block transmission. The UE may use the information to receive the synchronization signal of the base station of other NWs. The UE may receive the paging after receiving the synchronization signal. Thus, for example, it is possible to prevent the timing deviation in the paging reception of the UE.

[0204] The information in (10) above may be, for example, information indicating that the base station of the other NW is an NR base station, or information indicating that it is an LTE base station. The base station may use this information to change the paging timing. For example, when the base station of the other NW is an LTE base station and the paging timing in the LTE base station is fixed, the base station may change the cycle of the paging timing. Thus, for example, the possibility of failure to avoid paging conflicts in the communication system can be reduced.

[0205] The information in (11) may be, for example, a value of the timing priority of the paging that conflicts with the non-receiving paging, or may be information related to the timing priority of the paging allocated to the base station from another NW. The base station may use the information in (11) to change the timing priority of the non-receiving paging, or may change the allocation of the timing priority of the paging to the base station. Thus, for example, the possibility of failure to avoid paging conflicts in the communication system can be reduced.

[0206] The information in (12) above may be, for example, information indicating whether the UE is a UE equipped with multiple SIMs, or information related to operations using multiple SIMs. The information related to operations using multiple SIMs may include, for example, the number of transmitters and / or receivers in the UE, the number of NWs to which the UE can connect, or the number of RRCs that the UE can maintain. The information related to operations using multiple SIMs may be information related to a combination of RRC states in the UE, for example, information indicating whether multiple base stations among base stations of multiple NWs can simultaneously become RRC_CONNECTED. The UE may, for example, include the information in the UE capabilities to notify the base station. The base station may use the information in data transmission and reception between the UE and the UE. Thus, for example, the efficiency of the communication system can be improved.

[0207] The information in (13) may be, for example, information requesting a change in the timing of paging in the base station, information requesting a change in the allocation of the timing priority of paging in the base station, information requesting a change in the correspondence between the timing priority of paging and the category priority, or a method combining the above. The base station may use the information to change the timing of paging, change the allocation of the timing priority of paging, or change the allocation of the timing priority of paging and the category priority. Thus, for example, the amount of processing involved in the change of the above setting can be reduced in the base station.

[0208] The information (14) may be, for example, information indicating the correspondence between the timing priority and the category priority of paging in the conflicting NW, or may be the same information in the own NW. The base station may use the information (14) to change the timing of paging, to change the allocation of the timing priority of paging, or to change the allocation of the timing priority and the category priority of paging. Thus, for example, the processing amount involved in the change of the above setting can be reduced in the base station.

[0209] The UE may use RRC signaling to notify the base station of information related to non-receiving paging. For example, the UE may use an RRC setup request (RRCSetupRequest) in the notification. In the case where the RRC state related to the connection between the base station is RRC_IDLE, the UE may use the signaling of the RRC setup request for the notification. Thus, for example, the UE can quickly execute the notification to the base station. As another example, the UE may use RRC Setup Complete (RRCSetupComplete) in the notification. In the case where the RRC state related to the connection between the base station is transferred from RRC_IDLE to RRC_CONNECTED, the UE may use the signaling of the RRC setup complete for the notification. Thus, for example, the UE can include more information and notify the base station.

[0210] As another example, the UE can use an RRC recovery request (RRCResumeRequest) in the notification. In the case where the RRC state related to the connection between the base station is RRC_INACTIVE, the UE can use the signaling of the RRC recovery request for the notification. Thus, for example, the UE can quickly execute the notification to the base station. As another example, the UE can use an RRC recovery complete (RRCResumeComplete) in the notification. In the case where the RRC state related to the connection between the base station is transferred from RRC_INACTIVE to RRC_CONNECTED, the UE can use the signaling of the RRC recovery complete for the notification. Thus, for example, the UE can include more information and notify the base station.

[0211] As another example, the UE can use RRCReconfigurationComplete in the notification. Thus, the UE can include more information and notify the base station.

[0212] As another example, new RRC signaling may be set up, for example, a signaling called an RRC reconfiguration request (RRCReconfigurationRequest) may be set up and used, or a signaling called a paging configuration information notification (PagingConfigurationInformationNotification) may be set up and used.

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

[0214] The base station can use the information about non-reception paging obtained from the UE to change the allocation of timing priority, change the timing of paging, change the correspondence between timing priority and category priority, or change the allocation of category priority for each paging category.

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

[0216] The base station may uniformly allocate timing priority, correspondence between timing priority and category priority, allocate category priority to each paging category, and / or change the timing of paging to the UEs under the cell. The base station may broadcast information related to the change to the UEs under the cell. The UEs under the cell may use the information related to the change to update settings related to the timing priority of paging, update settings related to the timing of paging, update settings related to the correspondence between timing priority and category priority, and update settings related to the allocation of category priority to each paging category.

[0217] For example, the base station may broadcast the changed parameter to subordinate UEs. For example, the base station may broadcast the changed parameter by including it in SIB1. The UE may use the broadcast to change the timing of receiving paging (hereinafter sometimes 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 in each beam. Thus, for example, the flexibility of the parameter setting in the communication system can be improved.

[0219] As another example, the base station may individually allocate timing priority to the UE, correspondence between timing priority and category priority, allocation of category priority for each paging category, and / or change of timing of paging. The base station may individually notify the UE under the cell of information related to the change. The notification may use RRC dedicated signaling, for example. The UE may use the information related to the change to update settings related to timing priority of paging, may update settings related to timing of paging, may update settings related to correspondence between timing priority and category priority, and may update settings related to allocation of category priority for each paging category.

[0220] For example, the base station may change the parameter used to determine the paging timing for the UE individually. For the UE, the base station may notify the UE of the changed parameter individually. The base station may include the changed parameter in RRC signaling, such as RRC reconfiguration, and notify the UE individually. The UE may use the dedicated notification to change the paging reception timing. Thus, for example, the complexity of the processing related to the change of the paging timing in the communication system can be avoided.

[0221] As another example, the base station may collectively set the parameter for multiple UEs, or may collectively change it. For example, the base station may collectively set and / or change the parameter for multiple UEs equipped with multiple SIMs. For example, the multiple UEs equipped with multiple SIMs may be all UEs equipped with multiple SIMs located within the coverage area of ​​the base station. For example, among the multiple UEs equipped with multiple SIMs, the NW connection targets other than the base station may be the same or different. The multiple UEs equipped with multiple SIMs may be treated as a UE group. The base station may set and / or change the parameter for the UE group.

[0222] The base station may collectively notify the multiple UEs of the parameter after the collective setting and / or change to the multiple UEs. The notification may use RRC signaling, for example. The collective notification may be provided with a specific UE-ID, such as a multicast UE-ID. The multiple UEs may use the collective notification to set and / or change the parameter. Thus, for example, the amount of signaling between the base station and the multiple UEs may be reduced.

[0223] The above-mentioned aggregated notification from the base station to the plurality of UEs may be performed in other RRC signaling. Thus, for example, the amount of signaling between the base station and the plurality of UEs can be further reduced.

[0224] The UE may notify the base station of the other NW of the changed parameter obtained from the notification of the base station. The UE may include information related to the UE's identity in the notification to the base station of the other NW. The identity may be an identity allocated in the NW of the base station after the parameter is changed. The base station of the other NW may use the parameter to change the paging timing in the other NW, or may not change it. Thus, for example, it is possible to avoid using the parameter obtained from the notification and changing the paging timing in the other NW. As a result, it is possible to prevent paging conflicts after the paging timing is changed.

[0225] The base station may request the AMF to change the UE's identifier. For example, in a case where a paging conflict cannot be avoided by only changing the parameters used to determine the paging timing (for example, PCCH configuration information (PCCH-Config)), the base station may make the request. In a case where a paging conflict will occur by changing the parameter, the base station may not make the request to the AMF. Thus, for example, unnecessary changes to the identifier can be prevented when the paging conflict can be avoided by only changing the PCCH configuration information. The request may include one or more UE identifiers that are candidates for change. The request may use, for example, signaling in the N2 interface. New signaling, such as signaling of an N2 UE configuration update request (N2 UE configuration update request), may be set and used. The UE identifier may be, for example, the UE_IE disclosed in Section 7.1 of non-patent document 26 (TS38.304), or the 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier: 5GS-temporary mobile user identifier), 5G-TMSI (5G Temporary Mobile Subscription Identifier: 5G temporary mobile user identifier) ​​or 5G-GUTI disclosed in non-patent document 27 (TS23.501). The AMF may use this signaling to change the UE identifier.

[0226] The base station may notify the AMF of information used to avoid paging conflicts. The base station may include the information in the request for the UE's identity. The information may include the above information (1) to (15). The base station may convert the above information (1) to (15) obtained from the UE notification into signaling in the N2 interface for notification. The information may further include information related to this NW. Regarding the above information (1) to (15), the information related to this NW may be information obtained by replacing other NWs with this NW. The AMF may use the information related to this NW to change the UE's identity. Thus, for example, paging conflicts in the changed UE's identity can be prevented.

[0227] The AMF can notify the UE of the changed identity. The notification can use NAS signaling, such as the configuration update indication (CONFIGURATION UPDATE COMMAND) disclosed in non-patent document 32 (TS24.501). The identity can be, for example, the 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier: 5G S-Temporary Mobile User Identity) disclosed in non-patent document 27 (TS23.501). The UE can use the notification to update the UE-ID of this UE.

[0228] The UE may notify the AMF that the update of the UE's identity is complete. The notification may use NAS signaling, such as the configuration update complete (CONFIGURATION UPDATE COMPLETE) disclosed in non-patent document 32 (TS24.501).

[0229] The AMF may notify the base station of the changed identifier. The notification may use 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 the parameter used to determine the paging timing. Thus, for example, the flexibility of the paging timing change in the UE can be improved. The notification of the changed parameter from the base station to the UE may be the same as described above.

[0230] Fig.15 This is a diagram showing a first example regarding allocation of timing priorities of paging from a plurality of NWs and paging received by a UE. Fig.15 In the example shown, the timing priorities are assigned in two levels: high and low. Fig.15 In the example shown, arrow 1500 indicates the DRX cycle in NW#1 of the UE, and arrow 1501 indicates the DRX cycle in NW#2 of the UE. Fig.15 In the example shown, the paging timing of NW#1 is indicated by areas 1505 to 1507, and the paging timing of NW#2 is indicated by areas 1510 to 1512. Fig.15 In the illustrated example, areas 1505 , 1507 , and 1511 indicated by white squares are paging timings to which low timing priorities are allocated, and areas 1506 , 1510 , and 1512 indicated by black squares are paging timings to which high timing priorities are allocated.

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

[0232] As another example related to the allocation of timing priorities, paging timing can be set for each timing priority. For example, the parameters of the PCCH setting information (PCCH-Config) disclosed in non-patent document 22 can be determined for each timing priority. The UE can have multiple paging timings in one paging cycle. In one UE, when the timing of paging with a certain timing priority overlaps with that of other timing priorities, the paging with a higher timing priority can be prioritized.

[0233] Fig.16 This is a diagram of a second example related to allocation of timing priorities of paging from a plurality of NWs and paging received by a UE. Fig.16 In the example shown, the timing priorities are assigned in two levels: high and low. Fig.16 In the UE, NW#1 and NW#2 set a paging timing with a higher timing priority and a paging timing with a lower timing priority. Fig.16 In, with Fig.15 The same element numbers are assigned to the common elements, and the common descriptions are omitted.

[0234] exist Fig.16 In the example shown, paging timings with a higher timing priority assigned from NW#1 are set to areas 1606, 1608, and 1610, and paging timings with a lower timing priority assigned from NW#1 are set to areas 1605, 1607, and 1609. Fig.16 In the example shown, paging timings with a higher timing priority assigned from NW#2 are set in areas 1615, 1617, and 1619, and paging timings with a lower timing priority assigned from NW#2 are set in areas 1616, 1618, and 1620.

[0235] Fig.16 In the example shown, the paging timings shown in areas 1605 and 1615 overlap with each other. In this case, the UE receives paging from NW#2 assigned with a high timing priority in area 1625. The paging timings shown in areas 1606 and 1616 do not overlap with other paging timings, so the UE receives paging from NW#1 in area 1626 and paging from NW#2 in area 1627. Similarly, the UE receives paging from NW#2 assigned with a high timing priority in area 1628, receives paging from NW#1 in area 1629, and receives paging from NW#2 in area 1630. Similarly, the UE receives paging from NW#2 assigned with a high timing priority in area 1631, receives paging from NW#1 in area 1632, and receives paging from NW#2 in area 1633.

[0236] The UE can associate the timing priority assigned in a certain NW with the timing priority assigned in other NWs. This association can be performed, for example, when the number of the timing priority in a certain NW is different from the number of the timing priority in other NWs. Thus, for example, even when the number of the timing priority is different between multiple NWs, the UE can compare the timing priorities between the multiple NWs.

[0237] The method of the correspondence can be determined by a standard. The correspondence can be performed, for example, from a timing priority with a smaller number of levels to a timing priority with a larger number of levels. For example, in the case of 2 or 3 levels, the high and low timing priorities in the 2nd level can correspond to the high and low timing priorities in the 3rd level, respectively. Thus, for example, the complexity of the correspondence can be avoided.

[0238] As another example, the correspondence can be performed from a timing priority with a larger number of levels to a timing priority with a smaller number of levels. For example, in the case of 2 or 3 levels, the high, medium, and low timing priorities in the 3 levels can correspond to the high, high, and low timing priorities in the 2 levels, respectively. Thus, for example, the flexibility of the correspondence can be improved.

[0239] Other solutions are disclosed. Allocate the paging category that can be sent for each timing priority. For example, in the case where there are two levels of timing priority, in the paging with a high timing priority, it can be set that all categories of paging can be sent, and in the paging with a low timing priority, it can be set that all categories of paging except emergency communication can be sent. As another example, in the case where the timing priority is set to three levels of high, medium, and low, in the paging with a high timing priority, it can be set that all categories of paging can be sent, in the paging with a medium timing priority, it can be set that all categories of paging except emergency communication can be sent, and in the paging with a low timing priority, it can be set that all categories of paging except emergency communication, voice call, and SI update can be sent. The allocation of timing priority can use the method disclosed in the present embodiment 1. The action of the UE can be set to be the same as the action disclosed in the present embodiment 1. As a result, for example, there is no need to allocate category priorities, and as a result, the amount of processing in the NW side device of the communication system can be reduced.

[0240] As another example, all paging types can be sent regardless of timing priority. Thus, for example, when a paging with a predetermined timing priority cannot be received due to a timing conflict between a paging with a higher timing priority from another NW, a paging with a predetermined timing priority can be quickly received.

[0241] Other solutions are disclosed. The timing priority that can be sent can be set for each paging category. In the case of two levels of timing priority, emergency communications can be set to be sent only in paging with a high timing priority, and other categories of paging can be set to be sent in both high and low timing priorities. As another example, in the case of three levels of timing priority, high, medium, and low, emergency communications can be set to be sent only in paging with a high timing priority, voice calls and SI updates can be set to be sent in paging with a high or medium timing priority, and other categories of paging can be set to be sent in any of high, medium, and low timing priorities. The allocation of timing priorities can use the method disclosed in this embodiment 1. The action of the UE can be set to be the same as the action disclosed in this embodiment 1. As a result, for example, there is no need to allocate category priorities, which results in a reduction in the amount of processing in the NW side device of the communication system.

[0242] As another example, all types of paging can be sent at all timing priorities. This allows, for example, paging of a specified timing priority to be received quickly when paging of a specified timing priority cannot be received due to a timing conflict with a paging of a higher timing priority from another NW.

[0243] The method disclosed in the present embodiment 1 can be used in the case where the connection with multiple NWs is activated, for example, the RRC state between the base stations of multiple NWs is RRC_CONNECTED. The method disclosed in the present embodiment 1 can be used in the case where the connection with only one NW is activated, and the connection with other NWs is inactive, for example, the RRC state between the base station of one NW is RRC_CONNECTED, and the RRC state between the base stations of other NWs is RRC_INACTIVE or RRC_IDLE. The method disclosed in the present embodiment 1 can be used in the case where the connection with multiple NWs is inactive, for example, the RRC state between the base stations of multiple NWs is RRC_INACTIVE or RRC_IDLE. The UE can switch the NW of the connection target during the reception of paging. Thus, the UE can notify the base station of the switching source NW of information related to the switching of the connection. The base station of the switching source NW can use this information to stop scheduling for the UE. Thus, for example, the wireless resources in the base station of the switching source NW can be efficiently utilized.

[0244] According to the first embodiment, the possibility that the UE cannot receive the emergency communication paging due to the conflict between the timing of the emergency communication paging and the timing of the paging of other NWs can be reduced.

[0245] Modification 1 of Implementation Example 1. In Embodiment 1, a method for a UE to preferentially receive a paging with a higher timing priority is disclosed. In this Modification 1, a method is disclosed regarding a reception operation of a UE when timings of pagings with the same timing priority conflict.

[0246] The UE can receive paging from a base station with high communication quality, thereby, for example, improving the reliability of paging reception.

[0247] In judging the communication quality, the UE may use the synchronization signal sent from the base station, the CSI-RS, the PDCCH, or the DM-RS. The DM-RS 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 give priority to receiving 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 PF number in the DRX cycle, the PO number in the PF, or the PDCCH monitoring opportunity number in the PO. A combination of the above may be used. As another example, the UE may give priority to receiving paging from a base station with a longer time until the next paging timing. Thus, for example, the delay in paging reception can be reduced.

[0249] As another example, the UE may receive paging from an NW different from the NW of the paging received last time. For example, in the case where paging with the same timing priority conflicts, the UE may switch the NW of the received paging in sequence. That is, the NW of the paging received by the UE may be determined using polling. The above method may be used, for example, in the case where paging from multiple NWs conflicts in the same cycle. Thus, for example, a state in which paging from a specific NW cannot be received in the above situation can be prevented.

[0250] As another example, the UE can use the situation that there is a paging in the paging timing of the receiving action to switch the NW of the received paging. The switching can, for example, switch between multiple NWs in sequence. The switching can, for example, use the above-mentioned polling. Thus, for example, in the case where the timing of actually sending paging in the paging timing from multiple NWs overlaps with each other, the UE can also receive paging from multiple NWs.

[0251] As another example, the UE may have a parameter related to the reception of paging from multiple NWs. The parameter may be set for each NW to which the UE is connected, may be set for each paging timing from the same NW, or may be used in combination with the above two. The parameter may, for example, add values ​​as time passes. In the case where the UE performs a paging reception action from the NW, the parameter may be a parameter obtained by subtracting a specified value, or may be a parameter obtained by initialization. In the case where the UE actually receives a paging from the NW, the parameter may be a parameter obtained by subtracting a specified value, or may be a parameter obtained by initialization. The subtracted specified value may be a constant value, may be different for each timing priority, may be different for each category of the paging actually received, or may be different when the UE performs a receiving action from the case where the UE actually receives. The UE may perform a paging reception action from the NW with the highest parameter. In the case where the value of the parameter is the same among multiple NWs, it may be predetermined which NW the UE performs the paging reception action from. Thus, for example, the flexibility in the paging reception from multiple NWs in the UE can be improved.

[0252] As another example, the UE may have a timer related to the reception of paging from multiple NWs. The timer may be set for each NW to which the UE is connected, may be set for each paging timing from the same NW, or may be used in combination with the above two. The timer may be started, for example, when the UE registers to the NW (for example, when it becomes RM_REGISTERED). In the case where the UE performs a paging reception action from the NW, the timer may be stopped or initialized. In the case where the UE actually receives a paging from the NW, the parameter may be stopped or initialized. The UE may perform a paging reception action from the NW with the least remaining time of the timer, or may perform a paging reception action from the NW whose timer expires first. The initial value of the timer may be constant between multiple NWs, or may be different in each NW. The initial value of the timer may be determined by a standard, or may be determined by the device of each NW (for example, AMF, PCF, UPF, SMF, base station) and notified to the UE. Thus, for example, the same effect as described above can be obtained.

[0253] The UE may notify the base station of information related to the above parameters, and may also notify the base station of information related to the above timer. The base station may use the information to determine whether to send paging at a specified paging timing, and may also determine the type of paging at a specified paging timing. For example, the base station may use the case where the value of the parameter for the NW is less than the second highest among the NWs to set it not to send paging at the paging timing. Thus, for example, power consumption in the communication system can be reduced.

[0254] As another example, the UE may receive a paging at a previous paging timing. For example, the UE may perform this operation when a portion of the timings of paging from multiple NWs overlap. Thus, for example, the UE can quickly receive paging.

[0255] As another example, the UE may use the category of the NW to make the determination. The category of the NW may be, for example, a PLMN or a private NW (or, a non-public NW). The UE may, for example, give priority to receiving paging from a base station on the PLMN side. Thus, for example, the UE can quickly receive emergency notifications from the PLMN. As another example, the UE may give priority to receiving paging from a base station on the private NW side. Thus, for example, the UE can quickly receive downlink data generated in the private NW.

[0256] A primary NW and a secondary NW can be set. A UE equipped with multiple SIM cards can set a primary NW or a secondary NW. The UE can make the settings related to the primary NW and / or the secondary NW for the base station and / or the AMF of the primary NW, and can also make the settings related to the primary NW and / or the secondary NW for the base station and / or the AMF of the secondary NW. As a result, in the design of the communication system, the complexity of the processing for notifying information related to paging conflicts can be avoided.

[0257] A person can set the primary NW and / or the secondary NW for the UE. For example, the primary NW and the secondary NW can be set according to the person's preferences. Thus, paging conflicts can be avoided for the NW that the person likes. The settings of the primary NW and / or the secondary NW can be pre-stored in the UE. The UE can use the settings of the primary NW and / or the secondary NW at any time.

[0258] The UE can receive paging from the base station of the master NW, thereby, for example, reducing the amount of processing in the UE.

[0259] For each timing priority disclosed in Embodiment 1, it is possible to determine which NW to receive paging from first. For example, in the case of two levels of timing priority, for paging with a higher timing priority, paging from a base station on the PLMN side can be received first, and for paging with a lower timing priority, paging from a base station on the private NW side can be received first. Thus, for example, the UE can quickly receive an emergency notification from the PLMN and can quickly receive downlink data generated in the private NW.

[0260] The UE can determine the NW that preferentially receives the paging by a method different from the above. This makes it possible, for example, to flexibly perform the paging reception operation in the UE.

[0261] The UE can notify the base station of the base station of which NW the UE will receive paging from first. As another example, the UE can notify the base station of the situation that it does not receive paging from the base station. The base station of the notification target can be a base station from which the UE does not receive paging. The base station can use the notification to change the allocation of timing priority, and can also change the paging timing. The base station can notify the UE of the changed timing priority allocation, and can also notify the changed paging timing. The notification from the base station to the UE can be carried out, for example, using the method disclosed in Implementation Example 1. Thus, for example, it is possible to prevent the paging received by the UE from being biased towards the base station of a specific NW. As another example, the base station of the notification target can be the base station from which the UE receives paging. The UE can notify the base station receiving the paging of the reception of the paging. The base station can use the notification to determine the paging allocation in each paging timing. Thus, for example, it is possible to improve the efficiency of the notification of paging in the communication system.

[0262] The UE may make the notification to the base station after acquiring information related to the paging timing from the base stations of each connected NW. Alternatively, the UE may make the notification after acquiring information related to the timing priority in the timing of paging from the base stations of each connected NW. Alternatively, the UE may make the notification after acquiring the information of both parties.

[0263] As another example, in the case of switching which NW base station to receive paging from first, for example, when the communication quality with the non-receiving base station exceeds the communication quality with the receiving base station, the UE can make the notification to the base station. The communication quality can be, for example, the RSRP of the synchronization signal and / or CSI-RS from the base station, RSRQ, SINR, or received power. In the above case, the UE can include the notification to the base station in the measurement report. Thus, for example, a base station with deteriorated communication quality can use the paging timing for communication with other UEs, resulting in improved communication efficiency.

[0264] The information included in the paging from which NW the UE gives priority to the base station may be the same as the information (1) to (15) disclosed as examples of information on non-reception paging in Embodiment 1. This information may include information on conflicts of the same timing priority.

[0265] The notification from the UE to the base station may include a request for a change in paging timing. The base station may use the request to change the paging timing. The change in the paging timing in the base station, the notification or broadcast of the change in the paging timing from the base station to the UE, and / or the action in the UE may be the same as the method disclosed in Implementation 1, for example.

[0266] As another example, the base station may decide which NW base station the UE should receive paging from first. The base station may make this decision using, for example, a measurement report from the UE, the type of NW (e.g., PLMN, private NW), or may prioritize base stations on the main NW side.

[0267] The base station that makes the decision may be, for example, a base station on the main NW side. Thus, for example, the complexity of control in the communication system can be avoided. As another example, the base station that makes the decision may be a base station with good communication quality with the UE. Thus, for example, the quality of control of the UE from the base station can be improved. As another example, the base station that makes the decision may be a base station whose RRC connection status with the UE is RRC_CONNECTED. Thus, for example, the complexity of control in the communication system can be avoided.

[0268] The base station can notify the UE of which NW base station's paging is to be received first, and the UE can use this notification to perform reception processing of the paging that is repeated at a fixed time.

[0269] The notification from the base station to the UE may be performed using RRC signaling, such as signaling for resetting the RRC connection. Thus, for example, the base station can notify the UE of more information. As another example, the notification from the base station to the UE may be performed using MAC signaling. Thus, for example, the base station can 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. Thus, for example, the base station can more quickly notify the UE of the information.

[0270] As another example, the core NW may determine which NW base station the UE should receive paging from first. The core NW may be, for example, an AMF, an SMF, or a PCF. The core NW device may use, for example, the category of the NW (e.g., PLMN, private NW) to make the decision, or may prioritize the base station on the main NW side.

[0271] The core NW device that makes the decision may be, for example, a device on the master NW side. Thus, for example, the complexity of control in the communication system can be avoided. As another example, the core NW device that makes the decision may be a core NW device of a NW in a base station having better communication quality with the UE. Thus, for example, the quality of control of the UE from the base station can be improved. As another example, the core NW device that makes the decision may be a core NW device of a NW in a base station whose RRC connection status with the UE is RRC_CONNECTED. Thus, for example, the complexity of control in the communication system can be avoided. As another example, the core NW device that makes the decision may be a core NW device of a NW whose connection status with the UE is CM_CONNECTED. Thus, for example, the complexity of control in the communication system can be avoided.

[0272] The core NW device can notify the UE of which NW base station should receive paging first, and the UE can use this notification to perform reception processing of the paging that is repeated at a fixed time.

[0273] The notification from the core NW device to the UE can be performed using NAS signaling. Thus, for example, the core NW device can notify the UE of more information. As another example, the notification from the core NW device to the UE can be performed via a base station. The notification from the base station to the UE can be performed using RRC signaling, such as signaling for resetting the RRC connection. Thus, for example, the base station can notify the UE of more information. As another example, the notification from the base station to the UE can be performed using MAC signaling. Thus, for example, the base station can quickly notify the UE of the information. As another example, the notification from the base station to the UE can be performed using L1 / L2 signaling. Thus, for example, the base station can more quickly notify the UE of the information.

[0274] The method disclosed in this modification 1 can also be applied when the timing priority is not set. Thus, for example, even when the timing priority of paging is not set, the UE can quickly understand which NW is receiving the paging.

[0275] According to the first modification, the base station and / or the core NW device can understand from which NW the UE should receive paging preferentially. As a result, malfunctions in the communication system can be prevented.

[0276] Modification 2 of Implementation Example 1. A UE equipped with multiple SIM cards sends and receives data with multiple NWs. Therefore, for example, when all the connection targets of the UE are PLMNs, the UE may receive emergency communications with the same content from multiple PLMNs. This causes a problem in which the memory size of the UE is squeezed.

[0277] In this modification example 2, a method for solving the above-mentioned problem is disclosed.

[0278] The UE deletes paging of the same category. The UE may retain only the initially received paging. The UE may delete the paging received later. For example, the UE may delete the data involved in the paging received later, or may not receive the data.

[0279] This action in the UE can be applied only in paging of a specified category. For example, this action in the UE can be applied to emergency communications. The emergency communication can be, for example, PWS (Public Warning System), ETWS (Earthquake and Tsunami Warning System), CMAS (Commercial Mobile Alert System), EU-ALERT (European Public Warning System), or KPAS (Korean Public Alert System). The emergency communication can be, for example, the emergency communication for private NW disclosed in Implementation Example 1. The emergency communication can also be other emergency communications. Thus, for example, it is possible to prevent data with different contents from being mistakenly deleted as the same data in the UE.

[0280] The UE may use information related to the paging category to determine whether there is duplication. The information may be, for example, information included in the paging or information included in the data involved in the paging. The information may be, for example, a 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 related to the transmission source. For example, the paging of emergency communication may include information related to the transmission source of the emergency communication. The information related to the transmission source may be uniquely allocated independent of the PLMN, or may be allocated by each PLMN. In the case where each PLMN allocates information related to the transmission source, each PLMN may notify the UE of the allocated information for the transmission source. The notification to the UE may be performed by the AMF, for example. The UE may use the information of the transmission source to determine whether there is duplication. Thus, for example, erroneous detection of data from different transmission sources can be prevented.

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

[0283] The UE can judge the paging of the specified category received within the specified time difference as the paging related to the same data. For example, when the UE receives paging of emergency communication from base stations of multiple NWs within the specified time difference, the emergency communication can be judged as the same content. Thus, for example, when emergency communications with the same content are received from multiple NWs at different timings, the UE can also judge the emergency communication as the same content.

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

[0285] The base station that makes this decision may be, for example, a base station on the main NW side, similar to the variant example 1 of the implementation example 1. Thus, for example, the complexity of control in the communication system can be avoided. As another example, the base station that makes this decision may be a base station with good communication quality with the UE. Thus, for example, the quality of control of the UE from the base station can be improved. As another example, the base station that makes this decision may be a base station whose RRC connection status with the UE is RRC_CONNECTED. Thus, for example, the complexity of control in the communication system can be avoided.

[0286] Similar to the first variant of the first embodiment, the core NW may be, for example, an AMF, an SMF, or a PCF. The core NW device may use the type of NW (e.g., PLMN, private NW) to make the decision, or may give priority to the base station on the main NW side.

[0287] The core NW device that makes this decision may be, for example, a device on the main NW side, similar to variant example 1 of implementation example 1. Thus, for example, the complexity of control in the communication system can be avoided. As another example, the core NW device that makes this decision may be a core NW device of a NW in a base station having better communication quality with the UE. Thus, for example, the quality of control of the UE from the base station can be improved. As another example, the core NW device that makes this decision may be a core NW device of a NW in a base station whose RRC connection status with the UE is RRC_CONNECTED. Thus, for example, the complexity of control in the communication system can be avoided. As another example, the core NW device that makes this decision may be a core NW device of a NW whose connection status with the UE is CM_CONNECTED. Thus, for example, the complexity of control in the communication system can be avoided.

[0288] Multiple NWs, such as multiple core NW devices, can determine the specified time difference. Alternatively, multiple base stations can determine the specified time difference. The specified time difference can be different between multiple NWs, and can also be different between multiple base stations. The UE can use a shorter time among the times that are different between multiple NWs and / or base stations. Thus, for example, it is possible to prevent different data from being mistakenly deleted as the same data in the UE. As another example, the UE can use a longer time among the times that are different between multiple NWs and / or base stations. Thus, for example, it is possible to prevent the same data from being mistakenly detected as different data in the UE, resulting in a reduction in the amount of processing of the UE.

[0289] The prescribed time difference can be set for each paging category, thereby, for example, improving the flexibility of the communication system.

[0290] This action in the UE can be applied to the case where the same PLMN is used. That is, when the UE is connected to different PLMNs, this action in the UE may not be applied. Thus, for example, when different paging categories are set for the same message identifier (refer to non-patent document 21 (TS23.041 V16.2.0)) in each NW, the UE can prevent different paging categories from being mistakenly detected as the same paging category.

[0291] This operation in the UE can be applied to the private NW. Thus, for example, the UE can repeatedly detect emergency communications for the private NW of the same content, resulting in a reduction in the amount of processing in the UE.

[0292] As another example, this action in the UE can be applied in the case of the same private NW. Thus, for example, when different paging categories are set for the same message identifier (refer to non-patent document 21 (TS23.041V16.2.0)) in each NW, the UE can prevent different paging categories from being mistakenly detected as the same paging category.

[0293] Information on the allocation of message identifiers for paging categories in each NW (refer to non-patent document 21 (TS23.041V16.2.0)) can be notified to the UE. This notification can use NAS signaling, for example. The UE can use this notification to detect paging of the same content. Thus, for example, when different message identifiers are allocated to the same paging category in different NWs, the UE can also detect paging of the same category.

[0294] According to the second variant, the reception of duplicate paging can be avoided, resulting in a reduction in the amount of processing in the UE.

[0295] Implementation method 2. A UE equipped with multiple SIM cards can maintain RRC connections with base stations of multiple NWs. The UE can transmit and receive signals with each of the base stations of the multiple NWs in a time-division manner.

[0296] The above actions cause the following problems. For example, when the UE switches the transmission and reception target from the base station of the source 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 transmits and receives with base station #2, the UE maintains the RRC state between the UE and base station #1 in RRC_CONNECTED, but becomes unable to receive the signal from base station #1. In this case, if the UE detects a synchronization deviation with base station #1 and as a result, RLF is detected with base station #1, the UE needs to perform a reconnection with base station #1.

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

[0298] The UE stops the timer and / or counter (hereinafter sometimes referred to as the RLF timer class) used for RLF detection with base station #1. The stopping of the RLF timer class in the UE can be performed when the UE switches the transmission and reception target from base station #1 to base station #2. The RLF timer class can be, for example, T310 disclosed in non-patent document 22 (TS38.331), N310, N311, or a combination of multiple of the above.

[0299] The UE may notify base station #1 of switching the transmission and reception target, and may also notify base station #1 of stopping the RLF timer. Base station #1 may not use the notification to schedule the UE. This may improve the communication efficiency in base station #1, for example.

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

[0301] Base station #1 can use the notification from the UE to stop the inactivity timer. This can prevent the timer from advancing when the UE's connection target switches from base station #1 to base station #2, for example. As a result, it can prevent the base station from deciding to terminate the RRC connection with the UE during the switching.

[0302] The stopping of the RLF timer class in the UE may be performed before the notification to the base station #1, after the notification, or simultaneously with the notification. For example, by stopping the RLF timer class before the notification, the memory usage of the UE when the transmission and reception target in the UE is switched can be reduced. In addition, for example, by stopping the RLF timer class after the notification, the processing amount when notifying from the UE to the base station #1 can be reduced. In addition, for example, by stopping the RLF timer class simultaneously with the notification, the complexity related to the management of the timer in the UE can be avoided.

[0303] The notification from the UE to the base station #1 can be performed dynamically. For example, the notification can use L1 / L2 signaling. Thus, for example, in the case where uplink data from the UE to the base station #2 is generated, the transceiver target switching can be performed quickly. As another example, the notification can use MAC signaling. Thus, for example, more information can be notified by uplink transmission with a high-order modulation order, and reliability can be improved by retransmission control.

[0304] As another example, the notification from the UE to the base station #1 can be performed quasi-statically. The notification can use RRC signaling, for example. RRC signaling for the notification can be newly set. Thus, for example, the UE does not need to perform the notification for each switch of the transceiver target. As a result, the amount of signaling between the UE and the base station can be reduced.

[0305] As another example, the switching of the transceiver target in the UE may be predetermined by the base station and notified to the UE. The UE may use the notification to determine the base station of the transceiver target. The base station that notifies the UE may be predetermined, for example. For example, the information may be included in the SIM of the UE. Thus, for example, the amount of signaling between the UE and the base station may be reduced.

[0306] The UE can establish downlink synchronization with base station #2. The UE can use a synchronization signal (e.g., SS block) from base station #2 to establish downlink synchronization, or can use other signals, such as CSI-RS from base station #2, to establish downlink synchronization. The establishment of downlink synchronization with base station #2 in the UE can be performed, for example, after the RLF timer class for base station #1 stops. Thus, for example, the expiration of the RLF timer class for base station #1 can be prevented while the UE is receiving a downlink signal from base station #2. As another example, the establishment of downlink synchronization with base station #2 in the UE can be performed after the notification of the switching of the transceiver target for base station #1. Thus, for example, scheduling from base station #1 to the UE is not required during the period when the UE performs the downlink synchronization establishment action, as a result, the communication efficiency in base station #1 can be improved.

[0307] As another example, the UE may maintain information related to the frame timing of both base stations #1 and #2. For example, the UE may maintain information related to the frame offset between base station #1 and base station #2. The UE may obtain the above information when establishing an RRC connection with base stations #1 and #2, respectively. The UE may update the above information. The UE may perform the update at a specified period or when a certain event occurs. While maintaining the above information, the UE may not perform the downlink synchronization establishment action with base station #2. As a result, for example, the transmission and reception switching between base station #1 and base station #2 can be quickly performed.

[0308] The UE starts or resumes a timer and / or counter (hereinafter sometimes referred to as an RLF timer class) used for RLF detection with base station #2. The start or resumption of the RLF timer class in the UE can be performed after the UE switches the transmission and reception target 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] This random access may be, for example, a random access consisting of two steps of PRACH transmission from the UE to the base station and RA response from the base station to the UE, or a random access consisting of four steps. The UE may start or resume the RLF timer class after receiving the RA response from the base station, or may start or resume the RLF timer class after receiving the response of the fourth step from the base station. The base station may start a timer for the UE, such as an inactive timer, after the random access is completed, or may resume it without initializing. Thus, for example, complexity associated with the control of the RLF timer class in the UE and / or the inactive timer in the base station can be avoided.

[0310] The UE may not perform random access processing with base station #2. For example, if the UE can maintain uplink synchronization with base station #2, the UE may not perform the above random access processing. The situation where the UE can maintain uplink synchronization with base station #2 may be, for example, a situation where a prescribed time has not passed after the transmission and reception between the UE and base station #2 stopped, a situation where the position of the UE converges within a prescribed range, or a situation where the speed of the UE is within a prescribed range. As a result, for example, the transmission and reception between the UE and base station #2 can be quickly restored.

[0311] The UE can notify base station #2 of the situation that the transceiver target is switched to base station #2, and can also notify the recovery of the RLF timer class for base station #2. The notification from the UE to base station #2 can be performed, for example, without random access between the UE and base station #2. The notification can be performed using L1 / L2 signaling. Thus, for example, the UE can quickly notify base station #2 of the switching of the transceiver target. As another example, the notification can be performed using MAC signaling. Thus, for example, reliability can be improved through retransmission control. As another example, the notification can be performed using RRC signaling. Thus, for example, the UE can notify the base station of more information. The base station can use the notification to start an inactive timer for the UE, or it can resume it without initialization. Thus, for example, the complexity associated with the control of the inactive timer in the base station can be avoided.

[0312] When the RLF timer class is restored, the RLF timer class may be initialized. Thus, complexity in the design of the UE can be avoided. As another example, the RLF timer class may not be initialized, i.e., restored from the value when it was stopped. Thus, for example, in the case where synchronization deviation actually occurs between the UE and base station #2, the UE can quickly detect the RLF, and as a result, can quickly recover from the RLF.

[0313] Fig.17 This is a flowchart showing an example of the stopping and resuming actions of the RLF timer class accompanying the switching of the UE's transmission and reception target. Fig.17 In the example, the UE is connected to base station #1 under NW#1 and base station #2 under NW#2.

[0314] Fig.17 In step ST1703 shown, the UE enters the RRC_CONNECTED state for the connection between gNB#1 and gNB#2. In step ST1705, data is sent and received between the UE and gNB#1.

[0315] Fig.17 In step ST1707 shown, data for gNB#2 is generated from the UE. In step ST1709, the UE notifies gNB#1 that the connection target of the UE will be switched to gNB#2. The notification of step ST1709 can be performed using L1 / L2 signaling, MAC signaling, or RRC signaling. gNB#1 uses the notification of step ST1709 to stop scheduling for the UE. In step ST1711, the UE stops the RLF timer class for gNB#1. The RLF timer class can be, for example, T310 disclosed in non-patent document 22 (TS38.331), N310, N311, or a combination of multiple of the above.

[0316] Fig.17 In step ST1713 shown, gNB#2 sends an SS block to the UE. In step ST1715, the UE establishes downlink synchronization with gNB#2 by receiving the SS block of step ST1713.

[0317] Fig.17 In step ST1717 shown, a random access process is performed between the UE and gNB#2. The random access process of step ST1717 may be a random access consisting of two steps of PRACH transmission from the UE to gNB#2 and RA response from gNB#2 to the UE. Thus, for example, the random access process between the UE and gNB#2 can be completed quickly. In step ST1719, the UE resumes the RLF timer class for gNB#2. In this resumption, the RLF timer class for gNB#2 may be initialized. Step ST1719 may be performed based on the completion of step ST1717. The RLF timer class for gNB#2 may be the same as the RLF timer class for gNB#1 stopped in step ST1711. In step ST1721, data is sent and received between the UE and gNB#2.

[0318] Fig.17 In step ST1721, after completion of step ST1721, the UE's connection target is switched from gNB#2 to gNB#1. In step ST1723, the UE notifies gNB#2 that the UE's connection target is switched to gNB#1. In the notification of step ST1723, the same signaling as step ST1709 can be used. In step ST1731, the UE stops the RLF timer class for gNB#2. In step ST1733, gNB#1 sends an SS block to the UE. In step ST1735, the UE establishes downlink synchronization with gNB#1 by receiving the SS block of step ST1733.

[0319] Fig.17 In step ST1737 shown, random access processing is performed between the UE and gNB#1. The random access processing of step ST1737 may be the same processing as step ST1717. In step ST1739, the UE restores the RLF timer class for gNB#1. In this restoration, the RLF timer class for gNB#1 may be initialized. In step ST1741, data is sent and received between the UE and gNB#1.

[0320] Fig.17 , the random access of steps ST1717 and ST1737 is shown as consisting of two steps, but a four-step random access process may also be used. When a four-step random access is used, the base station can reset the RRC parameters for the UE. Thus, for example, the flexibility in the communication system can be improved.

[0321] Other solutions are disclosed. The UE may not stop the RLF timer class related to base station #1. After the RLF timer class between base station #1 expires, the UE may not perform RLF processing. The RLF processing may be, for example, a transition to RRC_IDLE, the processing disclosed in Section 5.3.10.3 of non-patent document 22 (TS38.331), or a combination of the above. Thus, for example, the complexity of the control of the RLF timer class in the UE can be avoided.

[0322] In the above case, after the UE's transmission and reception target is switched to base station #1 again, the UE can initialize the timer class related to base station #1. This can prevent, for example, erroneous detection of RLF when the UE's transmission and reception target is switched to base station #1 again.

[0323] Other solutions are disclosed. The UE can detect the RLF between the UE and base station #1 when the receiving and transmitting target is switched from base station #1 to base station #2. Part of the RLF processing with base station #1 may not be performed. For example, the UE may not transfer to RRC_IDLE. In the RRC re-establishment action disclosed in Section 5.3.7 of non-patent document 22 (TS38.331), the radio bearer may not be stopped. The MAC may not be reset. The SCell of the MCG (Master Cell Group) may not be released. spCellcConfig may not be released. DC may not be released. p-NR-FR1 may not be released. p-UE-FR1 may not be released. delayBudgetReportingConfig may not be released. T342 may not be stopped. 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. Thus, for example, the complexity of the cell selection process can be avoided. As another example, the UE may not start T311. Thus, for example, RRC_IDLE transfer accompanying the expiration of T311 can be prevented.

[0325] The UE may maintain the RRC parameters. The maintenance action in the UE may be applied, for example, to a case where the UE selects the same cell as before the RLF detection. Thus, for example, the amount of processing involved in re-establishing the RRC connection may be reduced. As another example, the UE may release the RRC parameters. The release action in the UE may be applied, for example, to a case where the UE selects a different cell than before the RLF detection. Thus, for example, the flexibility in the communication system may be improved.

[0326] The method disclosed in this embodiment 2 can be applied to beam failure. For example, the number of beam failure instance indications and / or the timer and / or counter attached to the number of beam failure instance indications disclosed in Section 9.2.8 of non-patent document 16 (TS38.300) can be stopped or resumed when the UE's transceiver target is switched. The timer and / or counter can be, for example, the beamFailureRecoveryTimer disclosed in non-patent document 17 (TS38.321), the beamFailureDetectionTimer, or the BFI_COUNTER. Thus, for example, it is possible to prevent false detection of beam failure during UE's transceiver switching.

[0327] In the application of the method disclosed in this embodiment 2, the switching of the transmission and reception target may not be performed until the random access response is received. As another example, the switching of the transmission and reception target may not be performed until the message 4 in the random access process is received. The above-mentioned action may be applied, for example, when the UE sends the PRACH to the base station. Thus, for example, the failure of the random access process can be prevented.

[0328] In the application of the method disclosed in this embodiment 2, the connection (e.g., NAS connection) between the UE and the NW of the base station before the target of the transmission and reception is switched can be maintained. Thus, for example, a quick reconnection can be made with the NW of the base station. As another example, the connection between the UE and the NW can be released. Thus, for example, the memory usage in the UE can be reduced.

[0329] The method disclosed in this embodiment 2 can be applied to beam management and / or beam measurement. For example, the UE can include information indicating that the beam was not measured in a measurement result report (measurement report) to the base station for notification. The notification from the UE to the base station indicating that the beam was not measured can be performed, for example, when the UE switches the transceiver target to a base station of another NW. The UE can include information related to the reason why the measurement cannot be made in the notification. The reason can be, for example, the switching of the transceiver target. The base station can use this information for beam control for the UE. Thereby, for example, it can prevent the base station from erroneously determining that the quality of the beam used between the UE and the UE is poor.

[0330] The method disclosed in this embodiment 2 can be used for random access processing. For example, when the UE's target base station for transmission and reception is switched from gNB#1 to gNB#2, the conflict resolution timer for gNB#1, such as the ra-ContentionResolutionTimer disclosed in non-patent document 17 (TS38.321), can be stopped. Thus, for example, it is possible to prevent misdetection of conflicts in random access processing after the target base station for transmission and reception is switched.

[0331] In the case where the UE's target base station for transmission and reception is switched from gNB#1 to gNB#2, the conflict resolution timer for gNB#1 may be started or resumed. The above start or resume may be from the initial value. Thus, for example, the complexity in the management of the timer of the UE can be avoided. As another example, the conflict resolution timer may be resumed from the value after it was stopped. Thus, for example, the UE can quickly detect the conflict of random access.

[0332] In this Embodiment 2, a case where the UE is connected to base station #1 and base station #2 is disclosed, but the number of base stations to which the UE is connected may be more than 3. For example, the method disclosed in this Embodiment 2 may be used in switching the transceiver target from base station #1 to base station #3. In addition, for example, the method disclosed in this Embodiment 2 may be used in switching the transceiver target from base station #3 to base station #4. Thus, for example, switching of the transceiver target base station in the UE can be flexibly performed.

[0333] The method disclosed in this embodiment 2 can be used in MAC processing. For example, when the UE's transceiver target base station switches from gNB#1 to gNB#2, the timer that manages the action state of the SCell facing gNB#1 (for example, the SCellDeactivationTimer disclosed in non-patent document 17 (TS38.321)) can be stopped. The timer can be restored when the UE's transceiver target is switched to gNB#1 again. Thus, for example, the expiration of the timer after the UE's transceiver target base station switches from gNB#1 to gNB#2 can be prevented. As a result, the amount of processing involved in the reactivation of the SCell in the UE can be reduced.

[0334] The above actions can be applied to a timer (e.g., bwp-InactivityTimer disclosed in non-patent document 17 (TS38.321)) that manages the action state of BWP (BandWidth Part) for gNB#1. Thus, for example, as described above, the amount of processing involved in reactivating BWP in the UE can be reduced.

[0335] The above actions can be applied to the timer for managing the activity of data conduction to gNB#1 (for example, dataInactivitiTimer disclosed in non-patent document 17 (TS38.321)). Thus, for example, as described above, it is possible to prevent the UE from transitioning to RRC_IDLE.

[0336] The method disclosed in this embodiment 2 can be used for RLC processing. For example, the above action can be applied to the timer used in the reassembly process of the RLC PDU for gNB#1 (for example, t-Reassembly disclosed in non-patent document 29 (TS38.322)). Thus, for example, as described above, the number of status confirmation (for example, RLC STATUS PDU sending) processes in the RLC can be reduced.

[0337] The method disclosed in this embodiment 2 can be used in PDCP processing. For example, the above action can be applied to the timer used in the management of the abandonment of the PDCP SDU for gNB#1 (for example, the discardTimer disclosed in non-patent document 30 (TS38.323)). Thus, for example, as described above, the abandonment of the PDCP SDU can be prevented. As a result, packet loss in the communication system can be prevented.

[0338] The above-mentioned action can be applied to the timer used in the reordering control of PDCP (for example, t-Reordering disclosed in Non-Patent Document 30 (TS38.323)). Thus, for example, as described above, it is possible to prevent the received data in the process of reordering from being sent to the upper layer. As a result, the reordering process in the upper layer can be reduced.

[0339] According to the second embodiment, the RLF timer related to the connection with the base station of the original NW can be prevented from expiring while the UE equipped with multiple SIMs is transmitting and receiving with the base station of another NW. As a result, it is not necessary to re-establish the RRC connection with the base station of the original NW.

[0340] Implementation method 3. The life time indicating the communication interruption allowable time until the application layer is interrupted when the communication interruption occurs (refer to Non-Patent Document 23 (TR22.832 V17.1.0)) can be used for QoS control in the NW.

[0341] However, a method of QoS control using the life time is not disclosed. Therefore, there is a problem that the NW cannot perform communication control using the life time, and the NW cannot perform communication that meets the requirements of the application layer.

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

[0343] Set the QoS parameters related to the survival time. The NW side device may notify the UE of the QoS parameters related to the survival time. The QoS parameters notified by the NW side device to the UE may be QoS parameters related to the survival time in downlink communication. The UE may notify the NW side device of the QoS parameters related to the survival time. The QoS parameters notified by the UE to the NW side device may be QoS parameters related to the survival time in uplink communication.

[0344] As examples of QoS parameters related to the lifetime, 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: average working time).

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

[0350] (6) Inherent availability.

[0351] (7) Application availability.

[0352] (8) Allow delay.

[0353] (9) The delay exceeds the allowed number of times.

[0354] (10) The delay exceeds the allowed number of consecutive times.

[0355] (11) The communication times do not reach the allowed times.

[0356] (12) Communication fails to reach the allowed number of consecutive times.

[0357] (13) Communication cycle.

[0358] (14) RLC layer retention.

[0359] (15)PDCP layer retention amount.

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

[0361] Regarding (1) above, for example, the core NW device, base station and / or UE may use the value of the lifetime itself for QoS control. For example, the lifetime requirement may be added to the table of 5QI described in non-patent document 27 (TS23.501). Thus, for example, the complexity of QoS control using the lifetime can be avoided.

[0362] The above (2) may be, for example, a value calculated by treating the expiration of the survival timer as a failure. The core NW device, the base station and / or the UE may use the above value (2) to set the communication path between the base station and the UE. Thus, for example, the complexity in controlling the reliability of communication can be avoided.

[0363] The above (3) may be, for example, the time from the timing when the survival time requirement is not met to the time when the communication path is restored. The core NW device, the base station and / or the UE may use the value of the above (3) to set the communication path between the base station and the UE. Thus, for example, the same effect as the above (2) can be obtained.

[0364] The above (4) may be, for example, the average time that the application runs to meet the lifetime requirement. The core NW device, base station and / or UE may use the value of (4) to set the communication path between the base station and the UE. Thus, for example, the same effect as the above (2) may be obtained.

[0365] The above (5) may be, for example, the average time that the application stops because it does not meet the survival time requirement. The core NW device, base station and / or UE may use the value of the above (5) to set the communication path between the base station and the UE. Thus, for example, the same effect as the above (2) can be obtained.

[0366] The above (6) may be a parameter given as MTBF / (MTBF+MTTR) using the above (2) and (3), for example. The core NW device, the base station and / or the UE may use the value of the above (6) to set the communication path between the base station and the UE. Thus, for example, the same effect as the above (2) can be obtained.

[0367] The above (7) may be, for example, a parameter given as MUT / (MUT+MDT) using the above (4) and (5). The core NW device, the base station and / or the UE may use the value of the above (7) to set the communication path between the base station and the UE. Thus, for example, the same effect as the above (2) can be obtained.

[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) can be used. (8) above can be used when communication is performed periodically in the access path, and can also be used for non-periodic communication. The core NW device, base station and / or UE can use the value of (8) above to perform QoS allocation of data sent and received, and can also perform scheduling. In this way, for example, it is possible to prevent adverse effects on applications caused by data delay exceeding the communication path.

[0369] The above (9) can be used, for example, when communication is performed periodically in a communication path. The above (9) can be, for example, a value derived using the value of the lifetime and the allowed delay, for example, a value obtained by dividing the value of the lifetime by the allowed delay. The core NW device, base station and / or UE can use the value of the above (9) to perform QoS allocation of data to be sent and received, or can perform scheduling. As a result, for example, the same effect as the above (8) can be obtained.

[0370] The above (10) can be used, for example, when communication is performed periodically. The above (10) can be a value obtained in the same manner as the above (9). By using the above (10), for example, in a communication system, it is possible to prevent sporadic delays from being erroneously detected as time-to-live exceeding.

[0371] The above (11) can be used, for example, in the case where data is not discarded after the delay exceeds the limit. Thus, for example, in a communication system where the delay exceeds the limit and is not fatal, it is possible to prevent the application from being interrupted due to the delay exceeding the limit.

[0372] The above (12) can be used, for example, when data is not discarded after the delay exceeds the time limit. By using the above (12), for example, in a communication system, it is possible to prevent sporadic communication failures from being erroneously detected as exceeding the survival time.

[0373] The above (13) can be used, for example, when communication is performed periodically in a communication path. The core NW device, base station and / or UE can use the value of the above (13) to perform QoS allocation of received and sent data, and can also perform scheduling. Thus, for example, the same effect as the above (8) can be obtained.

[0374] The above (14) can be used, for example, when communication is performed periodically in a communication path. The above (14) can be calculated, for example, using the value of the lifetime, the cycle of communication, and the size of data sent and received in one cycle. The above (14) can be the retention amount in the RLC entity of the receiving side device. Thus, for example, the receiving status of the receiving side device can be quickly reflected in the QoS control. As another example, the value of the above (14) can be the retention amount in the RLC entity of the sending side. Thus, for example, only the data for which delivery confirmation has been obtained can be reflected in the QoS control, and as a result, QoS control that is closer to the control status of the upper layer can be performed.

[0375] The above (15) can be obtained using, for example, the value of the lifetime, the communication cycle, and the size of the data sent and received in one cycle. The above (15) can be the retention amount in the PDCP entity of the receiving side device or the retention amount in the PDCP entity of the transmitting side device, as in the above (14). By using the retention amount of the PDCP layer, it is possible to perform QoS control that is closer to the control status of the upper layer, for example.

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

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

[0378] Information related to the survival time (for example, the value of the survival time) can be notified by the AF. The notification can be, for example, a request to the 5G system to meet the survival time. The notification can include information related to the communication that should meet the survival time. The information related to the communication that should meet the survival time can, for example, include information related to the sending and receiving hosts (for example, the source IP address, the destination IP address, the source port number and / or the destination port number), and can also include information related to the sent data (for example, information indicating which one of TCP / UDP is used).

[0379] AF can notify the core NW device of this information. The core NW device can be, for example, PCF, UDM, SMF, AMF, UPF, or NWDAF (Network Data Analytics Function. Refer to non-patent document 31 (TS23.288)). The core NW device can use this information to perform QoS control in the communication system. For example, the core NW device can use this information to perform conversion to (2) to (16) disclosed as examples of QoS parameters related to the lifetime, can perform conversion to existing QoS parameters, or can perform conversion to both of the above. As an example of the above conversion, the value of the lifetime and the allowed delay can be used, for example, the value of the lifetime can be divided by the value of the allowed delay to derive the number of consecutive allowed delays.

[0380] For example, the NWDAF can use the information from the AF to convert it into QoS parameters used in the communication system. The NWDAF can use the information obtained by the NWDAF (for example, the input data disclosed in Section 6.4.2 of Non-Patent Document 31 (TS23.288)) to convert it into QoS parameters. The information related to the masking frequency disclosed in Variation 3 of Implementation Example 3 can be used. Thus, for example, QoS control that reflects the status of the communication system can be performed, and the amount of signaling when the QoS parameters are derived can be reduced.

[0381] As another example, AF can notify the core NW device of (1) to (16) disclosed as examples of QoS parameters related to lifetime. The core NW device, similar to the above, can be PCF, UDM, SMF, AMF, UPF, or NWDAF (Network Data Analytics Function: network data analysis function. Refer to non-patent document 31 (TS23.288)). The core NW device can use this information to perform QoS control in the communication system. As a result, for example, the amount of QoS control processing in the core NW device can be reduced.

[0382] Changes (e.g., updates, corrections) may be made to information related to the lifetime. The NW-side device may notify the UE of changes to QoS parameters related to the lifetime. The AF may notify the core NW device of the change. The above notification may include (1) to (16) disclosed as examples of QoS parameters related to the lifetime. As another example, the above 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 NW device can request the AF to change the information related to the life span. The request can include information related to the reason for the change of the information. The information related to the reason can include, for example, a situation where there are too many requests related to the life span from the AF, and can also include a situation where the request related to the life span from the AF may not be satisfied. The AF can use the request to change the QoS parameters related to the life span. As a result, for example, flexible use of the communication system becomes possible.

[0384] As another example, the base station may make a request for a change in information related to the life span to the AF. The base station may make the request to the AF via a core NW device. As another example, the request may be made by a UE. The UE may make the request via a base station or a core NW device. The AF may use the request to make a change in information related to the life span. Thus, for example, it is possible to prevent application interruptions caused by failure to meet requirements related to the life span in a communication system.

[0385] Multiple information related to the lifetime can be set for one UE. For example, information related to the lifetime can be set for one UE from multiple applications. For example, multiple (1) to (16) disclosed as examples of QoS parameters related to the lifetime and / or a combination of existing QoS parameters can be provided. The UE can use this information to communicate with the base station. As a result, for example, flexible QoS control can be performed for different applications.

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

[0387] One application can set multiple information related to the lifetime. For example, different information can be set in the control information of the application and the actual data. The setting from the application can be performed on the core NW device or on the UE. This can improve the efficiency of QoS control in the application, for example.

[0388] The information related to the life time may include information about the validity period. For example, in the case where the life time varies with the passage of time, the validity period may be set. Thus, for example, flexible QoS control can be performed in the communication system.

[0389] A default value may be set for the information related to the life span. The default value may be determined, for example, by a standard, by a core NW device, by an AF, or by a base station. In the case where the information related to the life span is not set, each device in the communication system may use the default value to communicate. In the case where the above-mentioned validity period expires, the default value may be used. This, for example, can prevent malfunctions in the communication system.

[0390] QoS control using the lifetime can be performed in DC. In DC, QoS control using the lifetime can be performed in the base station on the MCG side. Thus, for example, the complexity of QoS control in DC can be avoided. As another example, SCG (Secondary Cell Group) can perform QoS control. Thus, for example, the amount of processing in MCG can be reduced. As another example, MCG and SCG can perform QoS control separately. Thus, the flexibility of QoS control can be improved.

[0391] As another example, QoS control can be performed in the cell group through which the QoS flow of the QoS control object passes. For example, in the case where the QoS flow is carried by MCG, MCG can perform QoS control. In the case where the QoS flow is carried by a fork, MCG and SCG can perform QoS control respectively. Thus, for example, the flexibility of QoS control can be improved. As another example, in the case where the QoS flow is carried by a fork, MCG can perform QoS control. Thus, for example, the complexity of QoS control can be avoided.

[0392] As another example, a cell group that performs SDAP processing can perform QoS control. The cell group can be an MCG or an SCG. Thus, for example, the mapping of QoS flows and QoS control can be performed by the same cell group, resulting in a reduction in the amount of processing for mapping and QoS control of QoS flows.

[0393] As another example, a cell group performing PDCP processing may perform QoS control. This QoS control may be applied, for example, when performing the processing of Modification 2 of Implementation 3. Thus, for example, the processing amount of the communication system in the processing of Modification 2 of Implementation 3 can be reduced.

[0394] As another example, a cell group that performs RLC processing can perform QoS control. Thus, for example, flexible QoS control taking RLC ARQ into consideration can be performed.

[0395] As another example, a cell group performing MAC processing may perform QoS control. This QoS control may be applied, for example, when performing the process of Modification 1 of Implementation Example 3. Thus, for example, the amount of processing of the communication system in the process of Modification 1 of Implementation Example 3 can be reduced.

[0396] The MCG may notify the SCG of information related to the life span. The information may be, for example, (1) to (16) disclosed as examples of QoS parameters related to the life span in the above content. Thus, for example, inconsistency in QoS control of the life span between the MCG and the SCG can be prevented, and as a result, the stability of the operation in the communication system can be improved.

[0397] The information related to the life 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 life time. For example, regarding (1) above, a timer for the life time may be set.

[0398] The UE can perform the above monitoring. The layer that performs the above monitoring in the UE can be RRC, SDAP, PDCP, RLC, or MAC. As another example, the V2X layer in the sidelink (refer to non-patent document 28 (TS23.287)) can perform the above monitoring. In the layer that performs the above monitoring, for example, a timer for the lifetime can be set. For example, when a HARQ NACK or a DCI for retransmission is received, the timer can be started. Thus, for example, the UE can quickly reflect the transmission failure in the HARQ layer in the timer for the lifetime.

[0399] The UE may notify the base station of the above-mentioned monitored information. The notification may use RRC signaling. Thus, for example, the UE can send more information to the base station. As another example, the notification may use MAC signaling. Thus, for example, the UE can quickly notify the base station. As another example, L1 / L2 signaling may be used in the notification. Thus, for example, the UE can notify the base station more quickly. The base station may use this information to control the communication system. For example, the base station may use the situation where the number of consecutive communications does not reach a specified value or more to change the coding rate in the scheduling for the UE. Thus, for example, the expiration of the lifetime can be prevented.

[0400] As another example, the UE may notify the AMF of the information. The notification may use NAS signaling. The AMF may use the information to control the communication system.

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

[0402] The base station may notify the UE of the monitored information. As another example, the base station may notify the AMF of the information. The AMF may use the information to control the communication system.

[0403] As another example related to the above monitoring, the monitoring can be performed by a core NW device. The above core NW device can be a UPF, an AMF, or an SMF. For example, the UPF can perform the monitoring related to U-layer data, and the AMF can perform the monitoring related to C-layer data. The AMF can perform the monitoring related to small data.

[0404] According to the third embodiment, both the NW device and the UE can perform QoS control using the life time, and as a result, communication that satisfies the requirements of the application layer can be performed.

[0405] Modification 1 of Implementation 3. QoS control using the lifetime can be used in MAC. The MAC layer of the UE and / or the base station can have a lifetime timer. In the communication system, for example, the transmission of data with a shorter time until the lifetime timer expires can be scheduled preferentially.

[0406] The timer of the survival time can be set for each logical channel. This can, for example, improve the flexibility of the communication system.

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

[0408] The reduced priority value may not be less than a prescribed threshold value. In the case where the reduced priority value is less than a prescribed threshold value, the UE may set the reduced priority value to the same value as the prescribed threshold value. The prescribed threshold value may be determined by a standard, or may be determined by a base station and notified to the UE. Thus, for example, it is possible to prevent the reduced priority value from deviating from the range determined by the standard, and as a result, it is possible to prevent malfunctions in the LCP. At the same time, as another example, it is possible to prevent the priority from being excessively increased in the priority offset.

[0409] The priority offset can be a uniform value within the allowable range of the survival time. This can avoid, for example, the complexity of the design in the LCP.

[0410] As another example, the priority offset can be made variable within the range allowed by the lifetime. For example, when the remaining time until the lifetime timer expires is small, the priority offset can be made larger. Thus, for example, even when HARQ retransmission occurs, the retransmission can be sent with priority, and as a result, the retransmission can be performed before the lifetime timer expires.

[0411] The priority offset can be provided for each time that becomes a scheduling unit. For example, within the time range until the expiration of the timer of the lifetime, the later the time is, the higher the priority offset can be set. Thus, for example, in addition to the above-mentioned effects, the allocation of logical channels in the LCP can be flexibly performed. The time that becomes the scheduling unit can be a subframe, a time slot, a micro time slot, or a code element.

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

[0413] Fig.18 An example is shown in which the time at which the offset value of the priority becomes constant is different for each offset value. In contrast, the time at which the offset value of the priority becomes constant may also be constant regardless of the offset value. Thus, for example, the complexity of the design in the LCP processing of the UE can be avoided.

[0414] The offset of the priority can be predetermined using a standard. For example, a uniform offset can be determined. Alternatively, an offset can be determined for each scheduling timing. Alternatively, the offset can be determined in correspondence with the range of the remaining time until the expiration of the timer of the lifetime. As an example of the correspondence between the range of the remaining time and the offset, the time range from the start of the timer of the lifetime to the expiration can be divided, and the offset can be determined for each divided range. For example, an offset can be determined for the range from the start of the timer of the lifetime to the half remaining before expiration, and an offset can be determined for the range from the start of the timer of the lifetime to the half remaining before expiration.

[0415] The logical channels to which the priority offset is applied can be predetermined by a standard. For example, the priority offset can be applied to a logical channel for which a lifetime requirement is set. Thus, for example, the priority of the logical channel can be made higher than that of other logical channels, and as a result, the lifetime requirement can be met.

[0416] As another example, the priority offset may be determined by the base station and notified to the UE. The notification may use RRC signaling, for example. The notification may include information related to the logical channel. The information may include information related to the offset. The UE may apply the offset included in the notification to the logical channel included in the notification. The information related to the offset may be the same information as the offset predetermined by the standard. Thus, for example, since the base station can notify the UE of more information, the flexibility in setting the priority offset can be increased.

[0417] As another example related to the notification, MAC signaling may be used. The notification may include information related to the logical channel and may also include information related to the offset. The information related to the offset may be the same information as the offset predetermined by the standard. The UE may apply the offset included in the notification to the logical channel included in the notification. Thus, for example, the UE can quickly apply the offset.

[0418] As another example related to the notification, L1 / L2 signaling may be used. The notification may include information related to the logical channel and may also include information related to the offset. The notification may be included in the DCI including the scheduling grant, may be included in a different DCI, or may be sent using different L1 / L2 signaling. The information related to the offset may be the same information as the offset predetermined by the standard, or may be the offset applied in the above grant. Thus, for example, the UE can quickly apply the offset.

[0419] Multiple information related to the offset can be set. Multiple information can be determined by standards, and can be determined by the base station and notified to the UE, or can be determined by the upper NW device and notified to the UE via the base station. The base station can notify the UE of the identifier of the information used in the multiple information. The notification of the identifier can use RRC signaling, MAC signaling, or L1 / L2 signaling. The notification can include information related to the logical channel to which the offset is applied. The UE can use the identifier to derive the information used. The base station can use settings from the upper NW device, such as QoS parameters, to determine the information used. Alternatively, the base station can use information related to the network slice to determine the information used. Thus, for example, the amount of signaling from the base station to the UE can be reduced.

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

[0421] (1) Survival time value.

[0422] (2) Information on logical channels to which priority offset is applied.

[0423] (3) The number of patterns to which priority offsets are assigned.

[0424] (4) The value of the priority offset.

[0425] (5) The remaining time of the timer for the lifetime of the application priority offset.

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

[0427] The information in (1) may be the value of the timer of the survival time. The information in (1) may be, for example, information including the number of consecutive transmission failures and the transmission period. For example, the information in (1) may be the initial value of the timer of the survival time. Thus, for example, the complexity in setting the priority offset in the UE can be avoided.

[0428] The information in (2) above may be, for example, an identifier of a logical channel (Logical Channel ID; LCID). Thus, for example, the MAC layer of the UE can quickly identify the logical channel to which the priority offset is assigned.

[0429] The information in (3) above may be the number of priority offsets given in the logical channel. The number may or may not include a case where there is no priority offset. For example, when a constant priority offset is allocated from the time when the remaining time of the lifetime timer is halved to the expiration of the timer, the value of (3) above may be 1. Thus, for example, the MAC layer of the UE can quickly grasp the number of priority offsets. As a result, the processing speed in the UE can be improved.

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

[0431] The information in (5) may be, for example, the value of the timer for starting the offset assignment in (4). Thus, for example, in the UE, the priority offset can be appropriately assigned to the logical channel. As a result, the stability of the communication system can be improved.

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

[0433] The UE can use the information notified by the base station to provide an offset to the priority value. The offset can be assigned for each logical channel or for each HARQ process ID.

[0434] The UE may start the timer of the life time when receiving the HARQ NACK, or may start the timer of the life time when receiving the scheduling information for HARQ retransmission. The base station may start the timer of the life time when sending the HARQ NACK to the UE, or may start the timer of the life time when sending the scheduling information for HARQ retransmission. Thus, the inconsistency of the timer value of the life time between the UE and the base station can be prevented, and as a result, malfunction in the communication system can be prevented.

[0435] The method disclosed in this variant example 1 can be used after the expiration of the timer of the life time. For example, a specified priority offset can be provided after the expiration of the timer of the life time. In addition, for example, in the application recovery time (Application Recovery Time) described in non-patent document 23 (TR22.832), a specified priority offset can be provided. The setting of the priority offset after the expiration of the timer of the life time can be performed in the same way as the setting of the priority offset before the expiration of the timer. The UE can use this setting to assign a priority offset after the expiration of the timer of the life time. Thereby, for example, recovery from a state of application interruption caused by the expiration of the timer of the life time can be performed quickly.

[0436] According to this modification 1, the UE can give priority to sending data when there is less time left before the expiration of the lifetime timer. As a result, the expiration of the lifetime timer can be prevented.

[0437] Modification 2 of Implementation 3. The life time may be used in the control of packet duplication. For example, packet duplication may be automatically performed when a timer of the life time starts. For example, the UE may automatically start packet duplication upon receipt of scheduling information for HARQ retransmissions. The scheduling information may include scheduling information for the transmission of the duplicated packets.

[0438] In the above case, the following problems occur. It has been discussed to set the maximum number of copies in packet replication to 4 (refer to non-patent document 24 (3GPP RP-192590)). In this case, the number of copies in automatic packet replication is not disclosed, so there is inconsistency in the actions between the UE and the base station. For example, although the base station expects 4 copies, the UE may copy the packet into 2 and send them. In this case, the use of reception resources in the base station becomes inefficient.

[0439] In this modification 2, a method for solving the above-mentioned problems is disclosed.

[0440] The number of packet copies is controlled using the life time. The UE implicitly changes the number of packet copies using the life time. For example, the UE can set the number of packet copies to be variable using the time until the life timer expires. The base station uses the timer of the life time to implicitly control the number of packet copies. For example, the base station can use the time until the life timer expires to schedule the transmission resources used by the UE. For example, the number of packet copies can be set to become more as the timer expires closer to the life time.

[0441] Implicit packet copy can implicitly control activation (activation) / deactivation (deactivation) of a leg (Leg) used in packet copy.

[0442] CA can be used in implicit packet replication. The base station can notify the UE of information related to the cell used in the implicit packet replication. The UE can use the information to use the cell in the implicit packet replication to perform transmission and reception with the base station. As a result, for example, the effect of frequency diversity can be obtained in the implicit packet replication. As a result, the reliability in the implicit packet replication can be improved.

[0443] DC can be used in implicit packet replication. The base station can notify the UE of information related to the cells used in the implicit packet replication. The notification from the base station to the UE can include information related to the cells of the MCG, and can also include information related to the cells of the SCG. The UE can notify the cell group added in the DC of information indicating the start of implicit packet replication. The cell group can be either the SCG or the MCG. The cell group can use the notification from the UE to start receiving the replicated packets, or it can start sending. Thus, for example, the effects of frequency diversity and space diversity can be obtained in implicit packet replication, with the result that the reliability in implicit packet replication can be improved.

[0444] In implicit packet replication, CA and DC can be used in combination. In packet replication using a combination of CA and DC, the UE can notify the cell group added to DC of information indicating the start of implicit packet replication.

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

[0446] Fig.19 The following example is shown: the time during which the number of packet copies is constant varies for each copy number. In contrast, the time during which the number of packet copies is constant can be constant regardless of the copy number. This can avoid, for example, the complexity of the design of the packet copy processing performed by the UE.

[0447] The number of packet copies can be predetermined using a standard. For example, a uniform number of copies can be determined. Alternatively, the number of packet copies can be determined for each scheduling timing. Alternatively, the number of packet copies can be determined in correspondence with the range of the remaining time until the expiration of the timer of the lifetime. As an example of the correspondence between the range of the remaining time and the number of packet copies, the time range from the start of the timer of the lifetime to the expiration can be divided, and the number of packet copies can be determined for each divided range. For example, the number of packet copies for the range from the start of the timer of the lifetime to the half remaining before expiration, and the number of packet copies for the range from the half remaining before expiration to the expiration can be determined.

[0448] The logical channels to which the implicit control of the number of packet copies is applied may be predetermined by a standard. For example, the implicit control of the number of packet copies may be applied to a logical channel for which a time-to-live requirement is set. Thus, for example, packet copies may be automatically applied to the logical channel, resulting in an increase in the reliability of the logical channel.

[0449] As another example, the number of packet copies may be determined by the base station and notified to the UE. The notification may use RRC signaling, for example. The notification may include information related to the logical channel. The information may include information related to the number of packet copies and may also include information related to the remaining time of the timer of the lifetime. The UE may apply the number of packet copies included in the notification to the logical channel included in the notification. The information related to the number of packet copies may be the same information as the number of packet copies predetermined by the standard. Thus, for example, since the base station can notify the UE of more information, the flexibility in the implicit control of the number of packet copies can be improved.

[0450] As another example related to the notification, MAC signaling may be used. The notification may include information related to the logical channel, may include information related to the remaining time of the timer of the lifetime, and may include information related to the number of packet copies. The information related to the number of packet copies may be the same information as the number of packet copies predetermined by the standard. The UE may apply the number of packet copies included in the notification to the logical channel included in the notification. Thus, for example, the UE can quickly reflect the control of the number of packet copies.

[0451] As another example related to the notification, L1 / L2 signaling can be used. The notification can include information related to the logical channel, information related to the remaining time of the timer of the lifetime, and information related to the number of packet copies. The notification can be included in the DCI including the scheduling grant, can be included in a different DCI, and can be sent in a different L1 / L2 signaling. The information related to the number of packet copies can be the same information as the number of packet copies predetermined by the standard, or can be the number of packet copies applied in the above-mentioned grant. Thereby, for example, the UE can further quickly apply the control of the number of packet copies.

[0452] Multiple pieces of information related to the number of packet replications can be set. Multiple pieces of information can be determined using standards, and can be determined by the base station and notified to the UE, or can be determined by the upper NW device and notified to the UE via the base station. The base station can notify the UE of the identifier of the information used in the multiple pieces of information. The notification of the identifier can use RRC signaling, MAC signaling, or L1 / L2 signaling. The notification can include information related to the logical channel to which the number of packet replications is applied. The UE can use the identifier to derive the information used. The base station can use settings from the upper NW device, such as QoS parameters, to determine the information used. Alternatively, the base station can use information related to the network slice to determine the information used. Thus, for example, the amount of signaling from the base station to the UE can be reduced.

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

[0454] (1) Survival time value.

[0455] (2) Information related to the radio bearer to which implicit control of the number of application packet duplications is applied.

[0456] (3) The number of patterns in the number of group replications.

[0457] (4) Number of group replications.

[0458] (5) Whether DC is used in the application.

[0459] (6) Information on cells used in packet replication.

[0460] (7) The remaining time of the timer of the lifetime of the application packet replication number.

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

[0462] The information in (1) above may be the initial value of the survival timer, for example, information including the number of consecutive transmission failures and the transmission cycle. This can avoid the complexity of packet duplication number control in the UE, for example.

[0463] The information in (2) above may be, for example, a data radio bearer identifier (DRB-ID) before packet duplication is performed. Thus, for example, the PDCP layer of the UE can quickly identify the radio bearer on 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 patterns may or may not include a case where there is no packet duplication. For example, when a packet duplication number of 4 is performed between the time remaining in the lifetime timer being halved and the timer expiring, the value of (3) above may be 1. Thus, for example, the PDCP layer of the UE can quickly grasp the number of packet duplication patterns. As a result, the processing speed in the UE can be improved.

[0465] The information in (4) may be the number of packet copies in the radio bearer. As another example, the information in (4) may be the amount of increase in the number of packet copies. Thus, for example, in the UE, packet copies can be appropriately controlled in the radio bearer. As a result, the stability of the communication system can be improved.

[0466] As another example of the information related to the above (4), information related to the number of packet replications of each MCG and SCG may be included. For example, when DC is used in implicit packet replication, this information may be included. Thus, for example, the flexibility in implicit packet replication can be improved.

[0467] The information in (5) above may be, for example, information indicating whether DC is used for implicit packet replication under the timing in (7) above. The UE may use the information in (5) above to start packet replication using DC or to stop packet replication using DC. Thus, for example, the flexibility in implicit packet replication can be improved.

[0468] The information in (6) above may be, for example, an identifier of a cell. The information in (6) above may include information related to the cell of the MCG used in implicit packet replication, may include information related to the cell of the SCG, or may include both of the above. The UE may use the cell shown in the information in (6) above to perform transmission and reception with the base station. Thus, for example, the amount of processing related to implicit packet replication in the UE can be reduced.

[0469] The information in (7) above may be, for example, the number of copies in (4) above and / or the value of the timer for starting the DC in (5) above. Thus, for example, in the UE, packet replication can be properly controlled in the wireless bearer. As a result, the stability of the communication system can be improved.

[0470] The information of (4) to (7) above may be provided in plural numbers, for example, the number of values ​​of (3) above may be provided. Thus, for example, in the UE, packet duplication of the radio bearer can be appropriately controlled, and as a result, the stability of the communication system can be improved.

[0471] The base station can change the implicit packet replication setting. The base station can change the implicit packet replication setting, for example, using a measurement report from the UE. The base station can notify the UE of the changed setting. The notification of the changed setting can, for example, include information (1) to (8) disclosed as information related to implicit control of the number of packet replications. Thus, for example, the base station can select an appropriate cell or cell group based on the communication quality with the UE, resulting in improved communication reliability.

[0472] Similar to the first variant of the third embodiment, the UE may start the timer of the life time when receiving the HARQ NACK, or may start the timer of the life time when receiving the scheduling information for HARQ retransmission. The base station may start the timer of the life time when sending the HARQ NACK to the UE, or may start the timer of the life time when sending the scheduling information for HARQ retransmission. Thus, the inconsistency of the timer value of the life time between the UE and the base station can be prevented, and as a result, malfunction in the communication system can be prevented.

[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. The UE uses L1 / L2 signaling for the notification, thereby, for example, the UE can quickly notify the cell group.

[0474] The UE may notify the cell group of information indicating the cessation of implicit packet duplication. The notification may be made, for example, when a timer of a lifetime is stopped or initialized. The cell group may use the notification from the UE to stop receiving the duplicated packets, or may not send them. Thus, for example, the frequency and time resources in the cell group can be efficiently utilized. The notification from the UE to the cell indicating the cessation of implicit packet duplication may be made in the same manner as the notification indicating the start of implicit packet duplication.

[0475] The UE may request a base station to change settings related to implicit packet replication. The request for change may be, for example, a request to increase the number of replications, a request to decrease the number of replications, a request to use DC for packet replication, a request to cancel DC for packet replication, or a combination of any of the above. The base station may use the request to change settings related to implicit packet replication. The base station may notify the UE of the changed settings. The notification of the changed settings may, for example, include information (1) to (8) disclosed as information related to implicit control of the number of packet replications. Thus, for example, the reliability in implicit packet replication can be improved.

[0476] In the request, for example, RRC signaling may be used. The RRC signaling may be, for example, a signaling requesting RRC reconfiguration. The signaling may be newly set. Thus, for example, more information can be sent from the UE to the base station. As another example, MAC signaling may be used in the request. Thus, for example, the UE can quickly notify the base station of the request. As another example, L1 / L2 signaling may be used in the request. Thus, for example, the UE can more quickly notify the base station of the request.

[0477] The method disclosed in this variant example 2 can be used after the expiration of the timer of the lifetime. For example, implicit packet replication can be performed after the expiration of the timer of the lifetime, and can also be performed in the application recovery time (Application Recovery Time) described in non-patent document 23 (TR22.832). The setting of implicit packet replication after the expiration of the timer of the lifetime can be performed in the same way as the setting of implicit packet replication before the expiration of the timer. The UE can use this setting to perform implicit packet replication after the expiration of the timer of the lifetime. As a result, for example, recovery from a state of application interruption caused by the expiration of the timer of the lifetime can be quickly performed.

[0478] According to this modification 2, the reliability of data transmission by the UE can be improved when there is little data left before the expiration of the lifetime timer. As a result, the expiration of the lifetime timer can be prevented.

[0479] Modification 3 of Implementation 3. Scheduling using the lifetime can be performed. For example, the remaining time of the lifetime timer can be used to automatically change the scheduling for the UE. The UE can use information related to the remaining time of the lifetime timer to change and use the scheduling for the UE.

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

[0481] (1) Configured Grant

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

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

[0484] (4) Information related to the beam, antenna panel and / or TRP (Transmission Reception Point) used by the base station.

[0485] (5) Information on base stations that are the transmission and reception targets of the UE.

[0486] (6) Information related to the UE performing transmission and reception.

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

[0488] The configured permission in (1) above can allocate a larger frequency resource when the remaining time of the lifetime timer is a predetermined time, for example. Thus, for example, the UE can send uplink data at a lower coding rate. As a result, the reliability of communication can be improved.

[0489] In (2) above, for example, when the remaining time of the survival time timer is a predetermined time, a cell with a lower frequency can be used. Thus, for example, in the short time remaining until the survival time timer expires, a cell using a frequency that is less likely to be shielded can be selected. As a result, the reliability of communication can be improved.

[0490] In (3) above, for example, when the remaining time of the survival time timer is a specified time, the beam and / or antenna panel used by the UE can be specified. The beam used by the UE can be, for example, an SRS beam, or can be specified by information related to a DMRS antenna port (for example, a DMRS antenna port number). (3) above can be applied, for example, to uplink communications. As a result, for example, the reliability of uplink communications can be improved.

[0491] The base station can measure the uplink signal from the UE to each antenna panel and / or TRP of the base station. The uplink signal measured by the base station can be SRS or DMRS. The base station can measure the shielding frequency. The base station can maintain the uplink measurement results. For example, the base station can maintain information related to the reliability of the uplink signal (e.g., a database). As a result, for example, the base station can quickly select a beam, antenna panel and / or TRP with higher reliability.

[0492] In (4) above, for example, when the remaining time of the survival time timer is a specified time, the beam and / or antenna panel used by the base station can be specified. (4) above can be applied, for example, to downlink communication. Thus, for example, the reliability of downlink communication can be improved.

[0493] The UE can measure the downlink signal from each antenna panel and / or TRP of the base station. For example, the UE can measure the CSI-RS from the base station, and can also measure the SS block. The UE can measure information related to the shielding frequency of the downlink signal. The UE can report information related to the measurement result of the downlink signal to the base station. For example, the UE can report the measurement result related to the shielding frequency of the downlink signal to the base station. The information related to the shielding frequency can be, for example, the number of times the received strength of the downlink signal is lower than a specified threshold within a specified time, or the time when the received strength of the downlink signal is lower than a specified threshold. The base station can use this information to determine the beam, antenna panel and / or TRP used in the downlink communication between the UE. As a result, for example, in the downlink communication between the base station and the UE, beams that are prone to shielding can be avoided. As a result, the reliability of downlink communication can be improved.

[0494] Regarding the above (3) and / or (4), the base station can notify the NWDAF (Network Data Analytics Function: Network Data Analysis Function. Refer to non-patent document 31 (TS23.288)) of the measurement results of the uplink signal and / or downlink signal. The measurement results may include, for example, information related to the shielding frequency. An interface can be set between the base station and the NWDAF. The NWDAF can use the measurement results to generate information related to the reliability of the uplink signal and / or downlink signal (for example, a database), or maintain it. The NWDAF can notify the base station of the information related to reliability. The base station can use the information related to reliability to determine the beam and / or antenna panel used by the UE, and can also determine the beam and / or antenna panel used by this base station. As a result, for example, the processing volume of the base station related to the above (3) and (4) can be reduced.

[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 use the information from the UE to generate information related to the reliability of the downlink signal, or may maintain it. Thus, for example, the processing amount of the base station can be reduced.

[0496] As another example, the notification of information related to the masking frequency to the NWDAF may be performed by OAM (Operations, Administration and Maintenance). OAM may derive the masking frequency using the measurement result of the UE. OAM may include the notification of information related to the masking frequency to the NWDAF in the notification of information related to RSRP, in the notification of information related to RSRQ, or in the notification of information related to SINR. Thus, for example, the amount of signaling in the communication system can be reduced.

[0497] As another example, NWDAF can derive information related to the shielding frequency. For example, NWDAF can use OAM (Operations, Administration and Maintenance) to derive information related to the shielding frequency from information related to RSRP, information related to RSRQ and / or information related to SINR notified by NWDAF. NWDAF can notify OAM of the information related to the shielding frequency, can notify the base station, can notify AMF, can notify SMF, can notify UPF, can notify PCF, can also notify AF (Application Function). For example, the base station can use the information related to the shielding frequency to determine the information related to (3) and / or (4) above. Thus, for example, the amount of signaling in the communication system can be reduced, and the reliability of communication between the base station and the UE can be improved.

[0498] The above (5) can be, for example, an identifier of a base station that is the target of the UE's transmission and reception (for example, gNB-ID), an identifier indicating whether it is a primary base station or a secondary base station, or a serial number given to the base station to which the UE is connected. The above identifiers can be applied, for example, to a case where the UE uses a DC structure, or to a case where multiple connections are used (for example, a case where the UE is connected to more than three base stations). Thus, for example, a spatial diversity effect can be obtained, resulting in improved reliability.

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

[0500] The base station may notify the UE of information related to scheduling, and the UE may use the information to perform transmission and reception with 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.

[0502] (1) Survival time value.

[0503] (2) Number of automatic scheduling modes.

[0504] (3) Information related to automatic scheduling.

[0505] (4) The remaining time of the timer for the automatically scheduled lifetime of the application.

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

[0507] The information of (1) above may be the same as the information of (1) disclosed as information on the offset of the priority in Variation 1 of Embodiment 3. This can avoid, for example, the complexity in the setting of the automatic scheduling in the UE.

[0508] The information (2) described above may be the same as the information (3) disclosed as information on the priority offset in Variation 1 of Implementation 3. Thus, for example, the UE can quickly grasp the number of automatic scheduling modes, resulting in an increase in the processing speed in the UE.

[0509] The information in (3) may be the information in (1) to (7) disclosed as an example of automatic scheduling change using the life time in this modification 3. This enables, for example, the base station to perform appropriate scheduling on the UE, resulting in improved stability in the communication system.

[0510] The information (4) described above may be the same as the information (5) disclosed as information on the priority offset in Variation 1 of Embodiment 3. This allows, for example, the base station to perform appropriate scheduling on the UE, resulting in improved stability in the communication system.

[0511] The information of (3) and (4) above may be provided in multiple numbers, for example, the number of values ​​of (2) above may be provided. Thus, for example, the base station can perform appropriate scheduling on the UE, and as a result, the stability of the communication system can be improved.

[0512] According to this modification 3, the base station can perform highly reliable scheduling for UE in data transmission when there is little time left before the lifetime timer expires. As a result, it is possible to prevent the lifetime timer from expiring.

[0513] The above-mentioned embodiments and their modifications are merely examples, and the embodiments and their modifications can be freely combined. In addition, arbitrary components of the embodiments and their modifications can be appropriately changed or omitted.

[0514] For example, in each of the above embodiments and their variations, a subframe is an example of a time unit for communication in a fifth-generation base station communication system. It may also be a scheduling unit. In each of the above embodiments and their variations, processing recorded in subframe units may be performed in TTI units, time slot units, sub-time slot units, and micro-time slot units.

[0515] For example, the methods disclosed in the above-mentioned embodiments and their variants are not limited to V2X (Vehicle-to-everything) services, but can also be applied to services that use SL communication. SL communication is used in a variety of services such as proximity services, public safety, communication between wearable terminals, and communication between devices in factories. Therefore, the methods disclosed in the above-mentioned embodiments and their variants can be applied to SL communication used in a variety of services.

[0516] The present disclosure has been described in detail, but the above description is only an example in all aspects and the present disclosure is not limited thereto. Numerous modifications not shown by way of example are conceivable without departing from the scope of the present disclosure.

[0517] In addition, the present disclosure can freely combine the various embodiments within the scope of the disclosure, and can appropriately modify or omit the various embodiments.

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 include a first network and a second network, The terminal device is configured to transmit, to the base station device of the first network, information indicating whether the terminal device receives paging from the first network.

2. The terminal device according to claim 1, characterized in that The information includes information related to paging for which the terminal device does not perform a receiving action.

3. The terminal device according to claim 1, wherein: The terminal device is configured to determine a priority paging category, The information includes information related to the category of prioritized paging.

4. The terminal device according to claim 3, characterized in that The information related to the type of paging indicates that the terminal device receives paging for voice calls with priority.

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

6. The terminal device according to claim 5, characterized in that The NAS signaling includes information related to the prioritized paging.

7. A base station device, which is a base station device in a communication system, wherein the communication system comprises: a plurality of networks, the plurality of networks comprising 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, The base station device is characterized in that: The first network includes the base station device, The base station device is configured to receive, from the terminal device, information indicating whether the terminal device has received paging from the first network.

8. A communication system, comprising: a plurality of networks, the plurality of networks comprising 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, The communication system is characterized in that The first network includes the 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.

Images