Patent Description:
A user equipment needs to be equipped with a Subscriber Identity Module (SIM) in order to utilize a mobile communication service (voice call service, data communication service, or the like) provided by a communication operator (operator or communication carrier) via a mobile network. Once the user equipment is registered with the mobile network using the SIM, the user equipment can utilize the mobile communication service from the mobile network of the registration destination.

In recent years, a user equipment that can be equipped with a plurality of SIMs has been spread. A user equipment equipped with two SIMs (a first SIM and a second SIM) may utilize a mobile communication service from a first mobile network, which is a mobile network with which the first SIM is registered, and may utilize a mobile communication service from a second mobile network, which is a mobile network of with which the second SIM is registered. Discussions on use cases for using both mobile communication services has started in the Third Generation Partnership Project (3GPP) (e.g., Non-Patent Literature <NUM>). <CIT> relates to paging and system information broadcast handling for multi-SIM WTRUs using mobile networks to access resources and/or services, wherein a WTRU may determine to monitor a plurality of mobile networks. <CIT> relates to a method for using a user equipment with a first public land mobile network and with a second public land mobile network, wherein the user equipment is a Dual SIM dual standby (DSDS) user equipment.

The present invention provides a communication control method, a chipset, a user equipment, a computer program, and a system according to the respective independent claims. Preferred embodiments are described in the dependent claims.

In a user equipment, when a communication in a first mobile network and a communication in a second mobile network occur at the same time, one of the communications may not be performed. In particular, in a case that the first mobile network and the second mobile network belong to different communication operators, collaboration between the mobile networks makes it difficult to avoid such problems.

An object of the present disclosure is to enable a user equipment that can be equipped with a plurality of SIMs to appropriately perform communication in a plurality of mobile networks.

A mobile communication system according to embodiments is described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference signs.

A configuration of a mobile communication system according to an embodiment is described.

While the mobile communication system according to an embodiment is a 3GPP <NUM> system, the 3GPP Long Term Evolution (LTE) may be at least partially applied to the mobile communication system.

<FIG> is a diagram illustrating a configuration of the mobile communication system according to an embodiment.

As illustrated in <FIG>, the mobile communication system includes a first mobile network (MN <NUM>-<NUM>) operated by a first communication operator, a second mobile network (MN <NUM>-<NUM>) operated by a second communication operator, and a User Equipment (UE) <NUM>. The UE <NUM> can register with the MN <NUM>-<NUM> using a SIM <NUM>-<NUM> described later, and can register with the MN <NUM>-<NUM> using a SIM <NUM>-<NUM>. The MN <NUM>-<NUM> and the MN <NUM>-<NUM> are hereinafter simply referred to as the MN <NUM> unless otherwise distinguished.

The MN <NUM> may be a network using the <NUM> technology, or may be a network using the LTE technology. <FIG> is an example where the MN <NUM> uses the <NUM> technology. The MN <NUM> includes a <NUM> radio access network (Next Generation Radio Access Network (NG-RAN)) <NUM>, and a <NUM> core network (5GC) <NUM>. When the MN <NUM> uses the LTE technology, the NG-RAN is interpreted as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN), and the 5GC is interpreted as an Evolved Packet Core (EPC). When the MN <NUM> uses the LTE technology, a gNB described later is interpreted as an eNB, and an AMF described later is interpreted as a Mobility Management Entity (MME). A UPF described later is interpreted as a Serving Gateway (S-GW) and/or Packet Data Network Gateway (P-GW).

The UE <NUM> is a mobile apparatus. The UE <NUM> may be any type of apparatus so long as it is utilized by a user, and examples of the UE <NUM> include a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or an apparatus provided on a sensor, a vehicle or an apparatus provided on a vehicle (Vehicle UE), and a flying object or an apparatus provided on a flying object (Aerial UE).

The NG-RAN <NUM> includes base stations (referred to as "gNBs" in the <NUM> system) <NUM>. The gNBs <NUM> may also be referred to as NG-RAN nodes. The gNBs <NUM> are connected to each other via an Xn interface (not illustrated) corresponding to an inter-base station interface. Each gNB <NUM> manages one or a plurality of cells. The gNB <NUM> performs wireless communication with the UE <NUM> that has established a connection to the cell of the gNB <NUM>. The gNB <NUM> has a radio resource management (RRM) function, a function of routing user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, and the like. The "cell" is used as a term representing a minimum unit of a wireless communication area. The "cell" is also used as a term representing a function or a resource for performing wireless communication with the UE <NUM>. One cell belongs to one carrier frequency.

Note that the gNB may be connected to an Evolved Packet Core (EPC) which is a core network of LTE, or a base station of LTE may be connected to the 5GC. The base station of LTE and the gNB may be connected via the inter-base station interface.

The 5GC <NUM> includes an Access and Mobility Management Function (AMF) <NUM> and a User Plane Function (UPF) <NUM>. The AMF <NUM> performs various types of mobility controls and the like for the UE <NUM>. The AMF <NUM> manages information of the area in which the UE <NUM> exists by communicating with the UE <NUM> by using Non-Access Stratum (NAS) signaling. The UPF <NUM> controls data transfer. The AMF <NUM> and the UPF <NUM> are connected to the gNB <NUM> via an NG interface which is an interface between the base station and the core network.

<FIG> is a diagram illustrating a configuration of the UE <NUM> (user equipment).

As illustrated in <FIG>, the UE <NUM> includes a receiver <NUM>, a transmitter <NUM>, a controller <NUM>, a SIM <NUM>-<NUM> (first SIM), a SIM <NUM>-<NUM> (second SIM), and a user interface <NUM>. The UE <NUM> may include three or more SIMs <NUM>.

The receiver <NUM> performs various types of reception under control of the controller <NUM>. The receiver <NUM> includes an antenna and a reception device. The reception device converts a radio signal received through the antenna into a baseband signal (a reception signal) and outputs the resulting signal to the controller <NUM>.

The transmitter <NUM> performs various types of transmission under control of the controller <NUM>. The transmitter <NUM> includes an antenna and a transmission device. The transmission device converts a baseband signal output by the controller <NUM> (a transmission signal) into a radio signal and transmits the resulting signal through the antenna.

The controller <NUM> performs various types of control in the UE <NUM>. The controller <NUM> includes at least one processor and at least one memory electrically connected to the processor. The memory stores a program to be executed by the processor and information to be used for processing by the processor. The processor may include a baseband processor and a central processing unit (CPU). The baseband processor performs modulation and demodulation, coding and decoding, and the like of a baseband signal. The CPU executes the program stored in the memory to thereby perform various types of processing.

The SIM <NUM> records information identifying a subscriber to receive a mobile communication service provided from the mobile network. In the SIM <NUM>, information may be recorded that includes, in addition to information identifying a subscriber, operator identification information for identifying a communication operator, and information related to available services that a subscriber subscribes to. The SIM <NUM> may be an IC card referred to as a removable SIM card (or a USIM card), i.e., an information card. The SIM <NUM> may be an Embedded SIM (eSIM) which is of an embedded type.

Information recorded in the SIM <NUM>-<NUM> (first SIM) identifies a first International Mobile Subscriber Identity (IMSI) corresponding to an identification number assigned to a user of the UE <NUM> from a first communication operator operating the first mobile network <NUM>-<NUM>. Information recorded in the SIM <NUM>-<NUM> (second SIM) identifies a second IMSI corresponding to an identification number assigned to the user of the UE <NUM> from a second communication operator operating the second mobile network <NUM>-<NUM>. The SIM <NUM>-<NUM> and the SIM <NUM>-<NUM> may be separate information cards, or may be integrated into an identical information card. The SIM <NUM>-<NUM> and the SIM <NUM>-<NUM> may be included in an Embedded SIM (eSIM).

The SIM <NUM>-<NUM> is managed by the first communication operator. The SIM <NUM>-<NUM> is managed by the second communication operator. Note that the SIM <NUM>-<NUM> and the SIM <NUM>-<NUM> may be managed by the identical communication operator.

In a case of using the SIM <NUM>-<NUM> to register with the first mobile network <NUM>-<NUM>, the UE <NUM> can utilize the mobile communication service provided by the first communication operator via the first mobile network <NUM>-<NUM>. In a case of using the SIM <NUM>-<NUM> to register with the second mobile network <NUM>-<NUM>, the UE <NUM> can utilize the mobile communication service provided by the second communication operator via the second mobile network <NUM>-<NUM>.

The user of the UE <NUM> may configure the priorities of SIM <NUM>-<NUM> and SIM <NUM>-<NUM> via the user interface <NUM>. The user may configure the priorities such that the SIM <NUM>-<NUM> is prioritized over the SIM <NUM>-<NUM> or that the SIM <NUM>-<NUM> is prioritized over the SIM <NUM>-<NUM>.

<FIG> is a diagram illustrating a configuration of the gNB <NUM> (a base station).

As illustrated in <FIG>, the gNB <NUM> includes a transmitter <NUM>, a receiver <NUM>, a controller <NUM>, and a backhaul communicator <NUM>.

The controller <NUM> performs various types of controls for the gNB <NUM>. The controller <NUM> includes at least one processor and at least one memory electrically connected to the processor. The memory stores a program to be executed by the processor and information to be used for processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation and demodulation, coding and decoding, and the like of a baseband signal. The CPU executes the program stored in the memory to thereby perform various types of processing.

The backhaul communicator <NUM> is connected to a neighboring base station via the inter-base station interface. The backhaul communicator <NUM> is connected to the AMF/UPF <NUM> via the interface between the base station and the core network.

<FIG> is a diagram illustrating a configuration of an AMF <NUM> (core network apparatus).

As illustrated in <FIG>, the AMF <NUM> includes a controller <NUM> and a backhaul communicator <NUM>.

The controller <NUM> performs various types of control in the AMF <NUM>. The controller <NUM> includes at least one processor and at least one memory electrically connected to the processor. The memory stores a program to be executed by the processor and information to be used for processing by the processor.

The backhaul communicator <NUM> is connected to the gNB <NUM> via the interface between the base station and the core network.

<FIG> is a diagram illustrating a configuration of a protocol stack of a radio interface in a user plane handling data.

As illustrated in <FIG>, the radio interface protocol in the user plane includes a physical (PHY) layer, a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, and a Service Data Adaptation Protocol (SDAP) layer.

The PHY layer performs coding and decoding, modulation and demodulation, antenna mapping and demapping, and resource mapping and demapping. Data and control information are transmitted between the PHY layer of the UE <NUM> and the PHY layer of the gNB <NUM> via a physical channel.

In the PHY layer, a frame structure is used that includes radio frames, subframes, slots, and symbols. The radio frame includes <NUM> subframes on a time axis. Each subframe has a length of <NUM>. Each subframe includes a plurality of slots. Each slot includes a plurality of symbols. Each subframe includes a plurality of resource blocks (RBs) on a frequency axis. Each resource block includes a plurality of subcarriers on the frequency axis. Among the radio resources (time and frequency resources) allocated to the UE <NUM>, frequency resources can be identified by resource blocks, and time resources can be identified by subframes (or slots or symbols).

In a downlink, a section of first several symbols of each subframe is a region used as a Physical Downlink Control Channel (PDCCH) for mainly transmitting downlink control information. The remaining portion of each subframe is a region that can be used as a Physical Downlink Shared Channel (PDSCH) for mainly transmitting downlink data.

The MAC layer performs preferential control of data, retransmission processing using a hybrid ARQ (HARQ), a random access procedure, and the like. Data and control information are transmitted between the MAC layer of the UE <NUM> and the MAC layer of the gNB <NUM> via a transport channel. The MAC layer of the gNB <NUM> includes a scheduler. The scheduler determines transport formats (transport block sizes, modulation and coding schemes (MCSs)) in the uplink and the downlink and resource blocks to be allocated to the UE <NUM>.

The RLC layer transmits data to the RLC layer on the reception side by using functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the UE <NUM> and the RLC layer of the gNB <NUM> via a logical channel.

The PDCP layer performs header compression and decompression, and encryption and decryption.

The SDAP layer performs mapping between an IP flow being a unit for a core network to perform QoS control and a radio bearer being a unit for an access stratum (AS) to perform QoS control. Note that, when the RAN is connected to the EPC, the SDAP may not be provided.

<FIG> is a diagram illustrating a configuration of a protocol stack of a radio interface in a control plane handling signaling (control signal).

As illustrated in <FIG>, the protocol stack of the radio interface of the control plane includes a Radio Resource Control (RRC) layer and a Non-Access Stratum (NAS) layer instead of the SDAP layer illustrated in <FIG>.

RRC signaling for various configurations is transmitted between the RRC layer of the UE <NUM> and the RRC layer of the gNB <NUM>. The RRC layer controls a logical channel, a transport channel, and a physical channel according to establishment, reestablishment, and release of a radio bearer. When a connection between the RRC of the UE <NUM> and the RRC of the gNB <NUM> (RRC connection) exists, the UE <NUM> is in an RRC connected state. When a connection between the RRC of the UE <NUM> and the RRC of the gNB <NUM> (RRC connection) does not exist, the UE <NUM> is in an RRC idle state. When the RRC connection is interrupted (suspended), the UE <NUM> is in an RRC inactive state.

The NAS layer located in a layer higher than the RRC layer performs session management, mobility management, and the like. NAS signaling is transmitted between the NAS layer of the UE <NUM> and the NAS layer of the AMF <NUM>.

Note that the UE <NUM> includes an application layer other than the protocol of the radio interface.

A first embodiment is described based on the assumption of the system configuration as described above.

When the communication of the UE <NUM> in the MN <NUM>-<NUM> and the communication of the UE <NUM> in the MN <NUM>-<NUM> at the same time are scheduled, one of the communications may not be performed due to the capability of the UE <NUM>. For example, when both MNs <NUM> schedule downlink communications at the same timing at different frequencies for the UE <NUM>, the UE <NUM> having only a single radio reception device (receiver <NUM>) cannot perform one of both downlink communications. When one of the downlink communications uses large amount of resources of the CPU of the UE <NUM>, even the UE <NUM> including a plurality of radio reception devices cannot perform the other of the downlink communications. It is preferable that the UE100 does not cause both communications to collide with each other. The first embodiment is an embodiment for solving such a problem.

In the first embodiment, the UE <NUM> transmits, to the NW <NUM>-<NUM>, timing information for identifying an execution timing which is a timing for performing communication in the NW <NUM>-<NUM>. This allows the NW <NUM>-<NUM> to recognize the timing at which the UE <NUM> performs the communication in the NW <NUM>-<NUM> and schedule a communication with the UE <NUM> at a timing not overlapping the former timing. Thus, a collision between the communication in the NW <NUM>-<NUM> and the communication in the NW <NUM>-<NUM> can be avoided.

The execution timing includes at least one of a paging reception occasion, a unicast scheduling occasion, an MBS scheduling occasion, and a sidelink scheduling occasion.

The paging reception occasion is the timing at which the UE <NUM> in the RRC idle state or the RRC inactive state monitors paging from the NW <NUM>-<NUM>.

The UE <NUM> in the RRC idle state monitors CN paging. The UE <NUM> in the RRC inactive state monitors CN paging and RAN paging. The CN paging is paging initiated by the core network (CN). The RAN paging is paging initiated by the RAN.

The UE <NUM> in the RRC idle state and the RRC inactive state monitors the paging using discontinuous reception (DRX) to reduce power consumption.

The UE <NUM> monitors one paging occasion (PO) per DRX cycle. The DRX cycle is represented by the number of radio frames. The DRX cycle may be referred to as a paging cycle. The PO includes one or more subframes or one or more symbols. One PO is associated with a paging frame (PF) that is one radio frame. The PO associated with the PF may start within the PF or after the PF.

The paging reception occasion for the UE <NUM> is a timing (subframe or symbol) included in the PO generated per DRX cycle.

The UE <NUM> determines that any smaller one of a default DRX cycle and a UE-specific DRX cycle configured for the UE <NUM> is the DRX cycle (referred to as "T" below) to be used by the UE <NUM> for monitoring paging.

The default DRX cycle is included in the system information received from a serving cell (gNB <NUM>) in which the UE <NUM> exists.

The UE-specific DRX cycle is differentiated depending on the RRC state of the UE <NUM>. When the UE <NUM> is in the RRC idle state, the UE-specific DRX cycle includes a first UE-specific DRX cycle. When the UE <NUM> is in the RRC inactive state, the UE-specific DRX cycle includes the first UE-specific DRX cycle and a second UE-specific DRX cycle.

The first UE-specific DRX cycle is a UE-specific DRX cycle configured for the UE <NUM> by a NAS message to monitor the CN paging. Such a NAS message is, for example, a REGISTER ACCESS message from the AMF <NUM>-<NUM> in the NW <NUM>-<NUM> when the UE <NUM> registers with the NW <NUM>-<NUM>.

The second UE-specific DRX cycle is a UE-specific DRX cycle configured for the UE <NUM> by a dedicated RRC message to monitor the RAN paging. Such a dedicated RRC message is, for example, an RRCrelease message for causing the UE <NUM> to transition from the RRC connected state to the RRC inactive state. Such an RRCrelease message includes a "SuspendConfig" information element (IE), and "SuspendConfig" includes information indicating the second UE-specific DRX cycle.

The UE <NUM> in the RRC idle state determines any smaller one of the default DRX cycles and the first UE-specific DRX cycle as "T".

The UE <NUM> in the RRC inactive state determines any smaller one of the default DRX cycles, the first UE-specific DRX cycle, and the second UE-specific DRX cycle as "T".

Note that when the UE-specific DRX cycle is not configured, the UE <NUM> determines the default DRX cycle as "T".

After determining "T", the UE <NUM> determines the radio frame number of the PF and the subframe or symbol included in the PO, based on "T", "UE_ID", and paging-related information.

Here, "UE_ID" represents a value calculated by a temporary subscriber identifier assigned to the UE <NUM> by the AMF <NUM>-<NUM>. For example, such a temporary subscriber identifier is a <NUM>-S- Temporary Mobile Subscriber Identity (TMSI). For example, "UE_ID" has a value obtained by "<NUM>-S-TMSI mod <NUM>.

The paging-related information is included in the system information received from the serving cell (gNB <NUM>) in which the UE <NUM> exists. The paging-related information includes parameters such as N, Ns, and PF_offset.

Note that for details of the determination method of T, the PF, and the PO described above, see the 3GPP technical specification TS38. <NUM>, for example. Note that for details of the determination method when the UE <NUM> exists in an LTE cell, see the 3GPP technical specification TS36. <NUM>, for example.

The unicast scheduling occasion is a candidate timing at which unicast data transmission/reception between the UE <NUM> in the RRC connected state and the NW <NUM>-<NUM> (gNB <NUM>-<NUM>) is scheduled.

The unicast scheduling occasion is a timing included in a scheduling period generated in a cycle.

<FIG> is a diagram illustrating an example of the unicast scheduling occasion.

As illustrated in <FIG>, the schedule period is a period generated per cycle "P". The scheduling period starts from a start timing (t1, t2, t3. The scheduling period has a predetermined duration (D).

The gNB <NUM> assigns a communication timing (subframe, slot, symbol, or the like) of unicast data with the UE <NUM> in a scheduling period within one cycle. On the other hand, the gNB <NUM> does not assign a communication timing to the UE <NUM> in a non-scheduling period (a period that is not a scheduling period) in one cycle. The communication timing includes at least one of a timing at which the UE <NUM> transmits the unicast data to the gNB <NUM> and a timing at which the gNB <NUM> transmits the unicast data to the UE <NUM>.

The unicast scheduling occasion is identified by three parameters of the start timing, the cycle, and the predetermined duration.

The start timing may be represented by a radio frame number and a subframe number, or may be represented by a slot number or a symbol number in addition to the radio frame number and the subframe number. The cycle is represented by the number of radio frames, the number of subframes, or the number of slots. The predetermined duration is represented by the number of subframes, the number of slots, or the number of symbols.

The unicast scheduling occasion is configured for the UE <NUM> from the gNB <NUM> in a unicast RRC message (e.g., RRCreconfiguration message). The gNB <NUM> may configure the unicast scheduling occasion for the UE <NUM> in response to a request from the UE <NUM>. The gNB <NUM> may configure the unicast scheduling occasion for the UE <NUM> based on past traffic history of the UE <NUM> and/or future traffic prediction of the UE <NUM> and/or the like.

The scheduling period generated per cycle may include a plurality of discontinuous timings. For example, the scheduling period may include a plurality of discontinuous timings within a predetermined duration (D). In this case, the plurality of discontinuous timings within the predetermined duration are represented by a bitmap. For example, when the predetermined duration corresponds to four subframes and the first subframe and the fourth subframe of the fourth subframes are timings corresponding to the scheduling periods, the scheduling periods are identified by a bitmap of (<NUM>, <NUM>, <NUM>, <NUM>) and the predetermined duration.

The MBS scheduling occasion is a candidate timing at which MBS data transmission from the NW <NUM>-<NUM> to the UE <NUM> is scheduled. The MBS is a service that performs data transmission from the NW <NUM>-<NUM> to the UE <NUM> in broadcast or multicast mode, in other words, point-to-multipoint (PTM) mode. The MBS may be referred to as a Multimedia Broadcast and Multicast Service (MBMS). The MBS data refers to data transmitted by the MBS.

The MBS scheduling occasion is a timing included in a scheduling period generated in a cycle.

The MBS scheduling occasion may be identified by the parameters such as the start timing, the cycle, the predetermined duration, and the bitmap, the same as and/or similar to the unicast scheduling occasion described above. Here, the parameters for identifying the MBS scheduling occasion are different from the parameters for identifying the unicast scheduling occasion.

The MBS scheduling occasion is configured for the UE <NUM> from the gNB <NUM> via a broadcast RRC message (e.g., MBS SIB). The MBS scheduling occasion may be configured for the UE <NUM> regardless of the RRC state of the UE <NUM>.

When the UE <NUM> is interested in receiving the MBS data regardless of the RRC state of the UE <NUM>, the UE <NUM> acquires the MBS SIB and identifies the MBS scheduling occasion based on MBS information included in the MBS SIB. The MBS information may directly include parameters for identifying the MBS scheduling occasion. The MBS information may include MBS control channel configuration information for the UE <NUM> to receive MBS control channel on which the parameters for identifying the MBS scheduling occasion are carried.

The sidelink scheduling occasion is a candidate timing at which sidelink communication is scheduled in the NW <NUM>-<NUM> by the UE <NUM>. The sidelink communication is communication performed between nearby UEs <NUM> without being through a network node (e.g., gNB <NUM>). The sidelink communication includes at least one of sidelink transmission in which the UE <NUM> transmits data to another UE <NUM> and sidelink reception in which the UE <NUM> receives data from another UE <NUM>.

The sidelink scheduling occasion is a timing included in a scheduling period generated in a cycle.

The sidelink scheduling occasion may be identified by the parameters such as the start timing, the cycle, the predetermined duration, and the bitmap, same as or similar to the unicast scheduling occasion described above. Here, the parameters for identifying the sidelink scheduling occasion are different from the parameters for identifying the unicast scheduling occasion. The parameters for identifying the sidelink scheduling occasion are different from the parameters for identifying the MBS scheduling occasion.

The sidelink scheduling occasion may be configured for the UE <NUM> from the gNB <NUM> via a broadcast RRC message (e.g., sidelink SIB). The sidelink scheduling occasion may be configured for the UE <NUM> regardless of the RRC state of the UE <NUM>.

When the UE <NUM> is interested in the sidelink communication regardless of the RRC state of the UE <NUM>, the UE <NUM> acquires the sidelink SIB and identifies the sidelink scheduling occasion based on sidelink information included in the sidelink SIB. The sidelink information is, for example, information indicating a resource pool for the sidelink communication.

<FIG> is a diagram illustrating operations of Operation Example <NUM> according to the first embodiment.

As illustrated in <FIG>, in an initial state of Operation Example <NUM>, the UE <NUM> registers with both the MN <NUM>-<NUM> and the MN <NUM>-<NUM>. In the initial state, the UE <NUM> is in an RRC state being any of the RRC connected state, the RRC idle state, and the RRC inactive state in the MN <NUM>-<NUM>. The UE <NUM> is in an RRC state being any of the RRC connected state, the RRC idle state, and the RRC inactive state in the MN <NUM>-<NUM>.

In step S101, the UE <NUM> determines whether a predetermined event occurs. The predetermined event is described in detail below. When the UE <NUM> determines that the predetermined event occurs (step S101: YES), the UE <NUM> advances the processing to step S102.

In step S102, the UE <NUM> transmits, to the NW <NUM>-<NUM>, the timing information for identifying the execution timing which is a timing for performing communication in the NW <NUM>-<NUM>. The timing information includes at least one of information for identifying the paging reception occasion, information for identifying the unicast scheduling occasion, information for identifying the MBS scheduling occasion, and information for identifying the sidelink scheduling occasion.

In step S102, when the UE <NUM> is in the RRC idle state or the RRC inactive state in the NW <NUM>-<NUM>, the UE <NUM> may transition to the RRC connected state and then transmit the timing information.

In step S102, a transmission destination of the timing information is the gNB <NUM>-<NUM> and/or the AMF <NUM>-<NUM> in the NW <NUM>-<NUM>. When the transmission destination of the timing information is the gNB <NUM>-<NUM>, the timing information is transmitted in the RRC message. When the transmission destination of the timing information is the AMF <NUM>-<NUM>, the timing information is transmitted in the NAS message.

When the UE <NUM> prefers to transition from the RRC connected state to the RRC idle state in the MN <NUM>-<NUM>, the UE <NUM> may determine the transmission destination of the timing information as the AMF <NUM>-<NUM>. In this case, the UE <NUM> may transmit, to the gNB <NUM>-<NUM>, information indicating that the UE <NUM> prefers to transition to the RRC idle state after step S102. When the UE <NUM> prefers to transition from the RRC connected state to the RRC inactive state in the MN <NUM>-<NUM>, the UE <NUM> may determine the transmission destination of the timing information as both the AMF <NUM>-<NUM> and the gNB <NUM>-<NUM>. In this case, the UE <NUM> may transmit, to the gNB <NUM>-<NUM>, information indicating that the UE <NUM> prefers to transition to the RRC inactive state after step S102.

When the UE <NUM> transmits the timing information in the NAS message, the NAS layer of the UE <NUM> generates the timing information. In this case, the RRC layer transmits, to the NAS layer of the UE <NUM>, information required for identifying the execution timing. The required information includes, for example, the above-described second UE-specific DRX cycle and default DRX cycle that the RRC layer recognizes.

The UE <NUM> may transmit the timing information together with information indicating guard time. The guard time is time required by the UE <NUM> to switch from communication with the NW <NUM>-<NUM> (gNB <NUM>-<NUM>) to communication with the NW <NUM>-<NUM> (gNB <NUM>-<NUM>). The guard time is represented by the number of radio frames, the number of subframes, the number of slots, or the number of symbols. The guard time may be provided before and after the execution timing (e.g., PO).

When the timing between the NW <NUM>-<NUM> (gNB <NUM>-<NUM>) and the NW <NUM>-<NUM> (gNB <NUM>-<NUM>) is asynchronous, the timing information transmitted to NW <NUM>-<NUM> may include information for identifying the timing of the NW <NUM>-<NUM> (radio frame number, subframe number, slot number, symbol number, etc.) corresponding to the execution timing of the NW <NUM>-<NUM>. In this case, the timing information may be information indicating the timing of the NW <NUM>-<NUM> (i.e., the radio frame number, subframe number, slot number, symbol number, or the like of the NW <NUM>-<NUM>) corresponding to the execution timing of the NW <NUM>-<NUM>. The timing information may include information indicating the execution timing of the NW <NUM>-<NUM>, and information indicating a difference between the timings of the NW <NUM>-<NUM> (gNB <NUM>-<NUM>) and the NW <NUM>-<NUM> (gNB <NUM>-<NUM>). The difference between the timings is represented by the number of radio frames, the number of subframes, the number of slots, the number of symbols. and the like.

In step S103, the MN <NUM>-<NUM> (gNB <NUM>-<NUM> and/or AMF <NUM>-<NUM>) communicates with the UE <NUM> without using the timing identified by the information received in step S102 (timing information, or timing information and information indicating the guard time). Hereinafter, the timing identified by the information received in step S102 (timing information, information indicating the guard time) is referred to as "non-use timing".

The operation in step S103 includes, for example, the following operations <NUM> to <NUM>.

Operation <NUM>: When the gNB <NUM>-<NUM> causes the UE <NUM> to transition to the RRC inactive state, the gNB <NUM>-<NUM> configures the UE-specific DRX cycle of the UE <NUM> (the second UE-specific DRX cycle described above), so that the PO corresponding to the RAN paging transmitted from the gNB <NUM>-<NUM> is arranged at the non-use timing, and transmits the RRCrelease message including the UE-specific DRX cycle to the UE <NUM>.

Operation <NUM>: The gNB <NUM>-<NUM> assigns a timing other than the non-use timing to the transmission/reception of data to/from the UE <NUM> in the RRC connected state.

Operation <NUM>: The gNB <NUM>-<NUM> configures a predetermined period of time including the non-use timing as a communication gap of the UE <NUM> in the RRC connected state, and transmits information indicating the communication gap to the UE <NUM>. The gNB <NUM>-<NUM> does not schedule the transmission/reception of data to/from the UE <NUM> in the communication gap.

Operation <NUM>: The AMF <NUM>-<NUM> configures the UE-specific DRX cycle of the UE <NUM> (the first UE-specific DRX cycle described above) and a new <NUM>-S-TMSI assigned to the UE <NUM>, so that the PO corresponding to the CN paging transmitted from the AMF <NUM>-<NUM> is arranged at the non-use timing, and notifies them to the UE <NUM> in the NAS message. Alternatively, the AMF <NUM>-<NUM> may notify the UE <NUM> of an offset value for the <NUM>-S-TMSI already assigned to the UE <NUM> instead of assigning the new <NUM>-S-TMSI to the UE <NUM>. The offset value is only used to identify paging reception occasion. The offset value may be notified from the AMF <NUM>-<NUM> to the gNB <NUM>-<NUM> during the paging execution.

Note that the operation in step S103 is optional.

The predetermined event is described. The predetermined event includes any of the following events A to F.

The event A is an event that causes the UE <NUM> to start monitoring a paging message in the NW <NUM>-<NUM>.

When the event A occurs in the UE <NUM> in step S101, the UE <NUM>, in step S102, transmits the timing information including information indicating the paging reception occasion. The timing information may further include information for identifying another execution timing that the UE <NUM> recognizes at this time (unicast scheduling occasion, MBS scheduling occasion, and sidelink scheduling occasion).

The event A includes, for example, any of the following events A1 to A3.

The event A1 indicates that the UE <NUM> transitions from the RRC connected state to the RRC inactive state in the NW <NUM>-<NUM>.

The event A2 indicates that the UE <NUM> transitions from the RRC connected state to the RRC idle state in the NW <NUM>-<NUM>.

The Event B is an event that may cause the paging reception occasion to change in the UE <NUM> that already starts monitoring the paging message in the NW <NUM>-<NUM>.

When the event B occurs in the UE <NUM> in step S101, the UE <NUM>, in step S102, transmits the timing information including information indicating the paging reception occasion (updated paging reception occasion). The timing information may further include information for identifying another execution timing that the UE <NUM> recognizes at this time.

The event B is, for example, any of the following events B1 to B3.

The event B1 indicates that the UE <NUM> in the RRC inactive state transitions to the RRC idle in the NW <NUM>-<NUM>. In this case, the UE <NUM> determines "T" without taking into account the second UE-specific DRX cycle, so "T" may change.

The event B2 indicates that the RRC inactive state is maintained after the UE <NUM> in the RRC inactive state in the NW <NUM>-<NUM> performs a Ran Notification Area (RNA) update procedure. In this case, the UE <NUM> again receives the RRCRelease message including "suspendConfig", and thus the second UE-specific DRX cycle may be updated and "T" may change. For details of the RNA update procedure, see the 3GPP technology specification TS38. <NUM>, chapter <NUM>.

The event B3 indicates that the UE <NUM> in the RRC inactive state or the RRC idle state in the NW <NUM>-<NUM> performs cell reselection. In this case, the default DRX cycle may be changed in response to changing the serving cell of the UE <NUM>, and thus "T" may change.

The event C indicates that the unicast scheduling occasion is configured for the UE <NUM> in the NW <NUM>-<NUM>, or the unicast scheduling occasion for the UE <NUM> is changed in the NW <NUM>-<NUM>.

When the event C occurs in the UE <NUM> in step S101, the UE <NUM>, in step S102, transmits the timing information including the information for identifying the unicast scheduling occasion. The timing information may further include information for identifying another execution timing that the UE <NUM> recognizes at this time.

The event D indicates that the UE <NUM> is interested in receiving the MBS data in the NW <NUM>-<NUM>, that the UE <NUM> starts receiving the MBS data in the NW <NUM>-<NUM>, or that the MBS scheduling occasion of the UE <NUM> is changed in the NW <NUM>-<NUM>.

When the event D occurs in the UE <NUM> in step S101, the UE <NUM>, in step S102, transmits the timing information including the information for identifying the MBS scheduling occasion. The timing information may further include information for identifying another execution timing that the UE <NUM> recognizes at this time.

The event E indicates that the UE <NUM> is interested in the sidelink communication in the NW <NUM>-<NUM>, that the UE <NUM> starts the sidelink communication in the NW <NUM>-<NUM>, or that the sidelink scheduling occasion of the UE <NUM> is changed in the NW <NUM>-<NUM>.

When the event E occurs in the UE <NUM> in step S101, the UE <NUM>, in step S102, transmits the timing information including the information for identifying the sidelink scheduling occasion. The timing information may further include information for identifying another execution timing that the UE <NUM> recognizes at this time.

The event F indicates that the UE <NUM> transitions to the RRC connected state in the NW <NUM>-<NUM>.

When the event F occurs in the UE <NUM> in step S101, the UE <NUM>, in step S102, transmits the timing information including the information for identifying the execution timing that the UE <NUM> already recognizes at the time when the event F occurs. For example, when the UE <NUM> already monitors the paging in the NW <NUM>-<NUM> and receives the MBS data at the time when the event F occurs, the UE <NUM> transmits the timing information including the information for identifying the paging reception occasion and the information for identifying the MBS scheduling occasion.

Differences of Operation Example <NUM> from Operation Example <NUM> is mainly described. The Operation Example <NUM> is an operation example related to permission to transmit the timing information.

In step S201, the UE <NUM> receives, from the NW <NUM>-<NUM> (gNB <NUM>-<NUM>), information indicating whether the timing information is permitted to be transmitted (hereinafter referred to as "transmittability information"). The UE <NUM> may receive the transmittability information in the dedicated RRC message, or may receive the transmittability information in the SIB. The UE <NUM> stores the transmittability information received.

Prior to step S201, the UE <NUM> may transmit a request message for permitting transmission of the timing information to the gNB <NUM>-<NUM>. The gNB <NUM>-<NUM> transmits the transmittability information in the dedicated RRC message to the UE <NUM> in response to receiving the request message. The request message may include information indicating that the UE <NUM> is in a state of registering with both the MN <NUM>-<NUM> and the MN <NUM>-<NUM> (hereinafter referred to as a "MUSIM state"). When the UE <NUM> is in the MUSIM state, the gNB <NUM>-<NUM> may transmit, to the UE <NUM>, the transmittability information indicating that the timing information is permitted to be transmitted. In the current LTE specification, the handling of the UE <NUM> having a plurality of SIMs is not defined, and thus when the NW <NUM>-<NUM> uses the LTE technology (i.e., the NW <NUM>-<NUM> has the E-UTRAN and the EPC), the timing information may not be permitted to be transmitted.

In step S202, the UE <NUM> determines whether the predetermined event occurs. The predetermined event occurs. When the UE <NUM> determines that the predetermined event occurs (step S202: YES), the UE <NUM> advances the processing to step S203.

In step S203, the UE <NUM> determines whether the timing information is permitted to be transmitted based on the stored transmittability information. When the UE <NUM> determines that the timing information is not permitted to be transmitted (step S202: NO), the UE <NUM> ends the flow. When the UE determines that the timing information is permitted to be transmitted (step S203: YES), the UE <NUM> advances the processing to step S204.

The operation in step S204 is the same as or similar to the operation in step S102.

Differences of Operation Example <NUM> from Operation Example <NUM> is mainly described. Operation Example <NUM> is an operation example related to a priority network.

In Operation Example <NUM>, when the UE <NUM> registers with both the MN <NUM>-<NUM> and the MN <NUM>-<NUM>, the UE <NUM> determines that one MN <NUM> is a priority network and determine that the other MN <NUM> is a non-priority network.

The UE <NUM> performs communication in the priority network (such as paging monitoring, and transmission/reception of data) more preferentially than communication in the non-priority network. For example, when the communication in the priority network and the communication in the non-priority network are scheduled in the same timing, the UE <NUM> may perform the communication in the priority network and not perform the communication in the non-priority network. When the UE <NUM> receives the data transmitted by the priority network and the data transmitted by the non-priority network at the same timing, the UE <NUM> may discard the data transmitted by the non-priority network. Accordingly, the non-priority network on scheduling the communication with the UE <NUM> needs to take into account the execution timing of the UE <NUM> in the priority network in order to succeed the communication.

A determination method of the priority network is described. The determination method includes, for example, any of first to fourth methods below.

In the first method, the UE <NUM> determines the priority network based on user configuration. For example, when the user configures to prioritize the SIM <NUM>-<NUM> over the SIM <NUM>-<NUM>, the UE <NUM> determines that the MN <NUM>-<NUM> corresponding to the SIM <NUM>-<NUM> is a priority network, and determines that the MN <NUM>-<NUM> corresponding to the SIM <NUM>-<NUM> is a non-priority network.

In the second method, the UE <NUM> determines that the MN <NUM> using the LTE technology is a priority network. For example, when the MN <NUM>-<NUM> uses the <NUM> technology, and the MN <NUM>-<NUM> uses the LTE technology, the UE <NUM> determines that the MN <NUM>-<NUM> is a priority network and determines that the MN <NUM>-<NUM> is a non-priority network. Note that when the MN <NUM>-<NUM> and the MN <NUM>-<NUM> use the same technology, the UE <NUM> does not determine the priority network by the second method.

In the third method, the UE <NUM> determines, as a priority network, the MN <NUM> in which a radio bearer having a priority equal to or greater than a threshold is established. For example, when a radio bearer having a priority equal to or greater than a threshold is established between the MN <NUM>-<NUM> and the UE <NUM>, the UE <NUM> determines that the MN <NUM>-<NUM> is a priority network, and determines that the MN <NUM>-<NUM> is a non-priority network.

The priority of the radio bearer is determined by the type of traffic of the user data mapped to the radio bearer. For example, when the type of traffic is voice call, the priority is determined to be high, or when the type of the traffic is a mail, a chat, web browsing or the like, the priority is determined to be low. The priority of the radio bearer may be a value associated with a <NUM> QI. For the correspondence between the <NUM> QI and the priority, see the 3GPP Technical Specification TS <NUM>, Table <NUM>. The priority of the radio bearer may be a value associated with the QCI. For the correspondence between the QCI and the priority, see the 3GPP Technical Specification TS <NUM>, Table <NUM>.

In the fourth method, the UE <NUM> determines that the MN <NUM> configuring a periodic communicable period for the UE <NUM> is a priority network. The periodic communicable period is, for example, a communication period identified by the Semi-Persistent Scheduling (SPS), or a communication period identified by a Configured Grant (CG). For example, when the MN <NUM>-<NUM> configures the SPS for the UE <NUM>, the UE <NUM> determines that the MN <NUM>-<NUM> is a priority network and determines that the MN <NUM>-<NUM> is a non-priority network.

Operation Example <NUM> is described using <FIG>.

In step S301, the UE <NUM> uses the determination method of the priority network described above to determine that one of the MN <NUM>-<NUM> and the MN <NUM>-<NUM> is a priority network, and determines that the other is a non-priority network.

In step S302, the UE <NUM> determines whether the predetermined event occurs. The predetermined event occurs. When the UE <NUM> determines that the predetermined event occurs (step S302: YES), the UE <NUM> advances the processing to step S303.

In step S303, the UE <NUM> determines whether the MN <NUM>-<NUM> is a non-priority network. When the UE <NUM> determines that the MN <NUM>-<NUM> is not a non-priority network (step S303: NO), the UE <NUM> ends the flow. When the UE <NUM> determines that the MN <NUM>-<NUM> is a non-priority network (step S303: YES), the UE <NUM> advances the processing to step S304.

The operation in step S304 is the same as or similar to the operation in step S102.

In Operation Example <NUM>, after step S301, the UE <NUM> may transmit, to the NW <NUM> determined to be a non-priority network, a non-priority notification indicating that the NW <NUM> is a non-priority network. For example, when the UE <NUM> determines that the NW <NUM>-<NUM> is a non-priority network, the UE <NUM> transmits the non-priority notification to the NW <NUM>-<NUM> (gNB <NUM>-<NUM> and/or the AMF <NUM>-<NUM>). The UE <NUM> configured with the periodic communicable period in the NW <NUM>-<NUM> may transmit the information for identifying the periodic communicable period together with the non-priority notification.

The gNB <NUM>-<NUM> receiving the non-priority notification recognizes that the NW <NUM>-<NUM> is a non-priority network. When the NW <NUM>-<NUM> recognizes that the NW <NUM>-<NUM> is a non-priority network, the gNB <NUM>-<NUM> may restrict the establishment of the radio bearer having the priority equal to or greater than the threshold (e.g., radio bearer for voice call) with the UE <NUM>.

In Operation Example <NUM>, when the UE <NUM> determines that the NW <NUM>-<NUM> is not a non-priority network after transmitting the non-priority notification to the NW <NUM>-<NUM>, the UE <NUM> may notify the NW <NUM>-<NUM> of such determination. In this case, the restriction on the establishment of the radio bearer having the priority equal to or greater than the threshold is released.

In Operation Example <NUM>, the UE <NUM> may transmit, to the NW <NUM> determined to be a non-priority network, information indicating that the UE prefers to transition to the RRC idle state or the RRC inactive state. Such information is information indicating that a preferred RRC-State of the UE <NUM> is the RRC idle state, for example. Such information may be information indicating that the preferred RRC-State of the UE <NUM> is the RRC inactive state. Such information may be information indicating that the UE <NUM> simply prefers to release the RRC connection and has no preferred RRC-State.

For example, when the UE <NUM> determines the NW <NUM>-<NUM> as a non-priority network and is in the RRC connected state in the NW <NUM>-<NUM>, the UE <NUM> transmits, to the gNB <NUM>-<NUM>, the information indicating that the UE prefers to transition to the RRC idle state or the RRC inactive state. The information may be transmitted together with the timing information. The gNB <NUM>-<NUM> may cause the UE <NUM> to transition to the RRC idle state or the RRC inactive state in response to the reception of the information.

Differences of Operation Example <NUM> from Operation Example <NUM> is mainly described. Operation Example <NUM> is an operation example related to UE context.

<FIG> is a diagram illustrating operations of Operation Example <NUM>. As illustrated in <FIG>, in an initial state, the UE <NUM> registers with the MN <NUM>-<NUM>. The UE <NUM> has an RRC connection with a gNB <NUM>-<NUM>(a) belonging to the MN <NUM>-<NUM>.

The operation in step S401 is the same as or similar to the operation in step S101.

In step S402, the UE <NUM> transmits the timing information to the gNB <NUM>-<NUM>(a) belonging to the MN <NUM>-<NUM>.

In step S403, the gNB <NUM>-<NUM>(a) stores the timing information as part of the UE context of the UE <NUM>.

In step S404, the gNB <NUM>-<NUM>(a) transmits the UE context including the timing information in a predetermined procedure for establishing an RRC connection between the gNB <NUM>-<NUM>(b) belonging to the MN <NUM>-<NUM> and the UE <NUM>.

Examples of the predetermined procedure include a handover procedure, an RRC connection re-establishment procedure, and an RRC connection resume procedure.

For example, the gNB <NUM>-<NUM>(a) transmits a HandoverPreparationInformation message in the handover procedure including the UE context (including the timing information).

In the RRC Resume procedure, the gNB <NUM>-<NUM>(a) may transmit the UE context to the gNB <NUM>-<NUM>(b) in response to receiving a RETRIEVE UE CONTEXT REQUEST message for requesting for provision of the UE context from the gNB <NUM>-<NUM>(b).

After the predetermined procedure is completed, in step S405, the RRC connection between the UE <NUM> and the gNB <NUM>-<NUM>(b) is established.

In step S406, the gNB <NUM>-<NUM>(b) communicates with the UE <NUM> without using the timing identified by the timing information (the operations <NUM> to <NUM> in step S103 described above).

A second embodiment is an operation example related to voice communication.

<FIG> is a diagram illustrating operations according to the second embodiment.

In step S501, the UE <NUM> determines whether a voice communication event occurs in the NW <NUM>-<NUM>. When the UE <NUM> determines that the voice communication event occurs (step S501: YES), the UE <NUM> advances the processing to step S502.

The voice communication event indicates that the user of the UE <NUM> sends outgoing voice via the NW <NUM>-<NUM>, or that the UE <NUM> receives a paging message to notify incoming voice.

In step S502, the UE <NUM> inquiries of the MN <NUM>-<NUM> whether the voice communication is permitted to be performed for the UE <NUM>.

In step S503, the UE <NUM> receives a permission notification indicating that the voice communication is permitted to be performed from the MN <NUM>-<NUM>.

In Step S504, the UE <NUM> performs the voice communication in response to receiving the permission notification. Note that the UE <NUM> not receiving the permission notification does not perform the voice communication.

A third embodiment assumes that the NW <NUM>-<NUM> and the NW <NUM>-<NUM> belong to the same communication operator.

In the third embodiment, when the UE <NUM> registers with both the NW <NUM>-<NUM> and the NW <NUM>-<NUM>, the UE <NUM> transmits information indicating that the UE <NUM> is in a state of registering with both the MN <NUM>-<NUM> and the MN <NUM>-<NUM> (MUSIM state) (hereinafter, "MUSIM state information") to both the NW <NUM>-<NUM> and the NW <NUM>-<NUM>. This allows the NW <NUM>-<NUM> and the NW <NUM>-<NUM> to recognize that the same UE <NUM> registers with both the NW <NUM>-<NUM> and the NW <NUM>-<NUM>. Accordingly, the NW <NUM>-<NUM> and the NW <NUM>-<NUM> can cooperate with each other to appropriately perform communication with the UE <NUM>.

When the UE <NUM> is in the RRC connected state in both the NW <NUM>-<NUM> and the NW <NUM>-<NUM>, the UE <NUM> may transmit the MUSIM state information further indicating this state.

A transmission destination of the MUSIM state information is the AMF <NUM> (both the AMF <NUM>-<NUM> and the AMF <NUM>-<NUM>) and/or the gNB <NUM> (both the gNB <NUM>-<NUM> and the gNB <NUM>-<NUM>). The AMF <NUM>-<NUM> may transfer the MUSIM state information received from the UE <NUM> to the gNB <NUM>-<NUM>. The gNB <NUM>-<NUM> may transfer the MUSIM state information received from the UE <NUM> to the AMF <NUM>-<NUM>. The gNB <NUM>-<NUM> may store the MUSIM state information received from the UE <NUM> as part of the UE context of the UE <NUM>.

When the transmission destination of the MUSIM state information is the AMF <NUM>, the UE <NUM> may transmit the MUSIM state information together with information indicating that the registration with the NW <NUM>-<NUM> and the registration with the NW <NUM>-<NUM> belong to the same UE <NUM>. Such information may indicate that the temporary subscriber identifiers (such as <NUM>-S-TMSI) assigned from both NWs <NUM> belong to the same UE <NUM>, for example.

When the transmission destination of the MUSIM state information is the gNB <NUM> and the UE <NUM> is in the RRC connected state in both the NW <NUM>-<NUM> and the NW <NUM>-<NUM>, the UE <NUM> may transmit information indicating that the RRC connection in the NW <NUM>-<NUM> and the RRC connection in the NW <NUM>-<NUM> belong to the same UE <NUM> along with the MUSIM state information. Such information may indicate that network temporary identifiers (such as C-RNTI) assigned from both NWs <NUM> belong to the same UE <NUM>, for example.

When the UE <NUM> in the MUSIM state is deregistered in any one of the NW <NUM>-<NUM> and the NW <NUM>-<NUM>, the UE <NUM> may transmit information indicating the deregistration to the other NW.

The embodiments described above may not only be separately and independently implemented, but also be implemented in combination of two or more embodiments.

In the first embodiment described above, the timing information identifies the execution timing, which is the timing for performing the communication in the NW <NUM>-<NUM>, without limitation. The timing information may be information indicating a communicable timing at which communication with the NW <NUM>-<NUM> can be performed. In this case, the NW <NUM>-<NUM> can schedule communication with the UE <NUM> at the communicable timing.

A program that causes a computer to execute each of the processing operations according to the embodiments described above may be provided. The program may be recorded in a computer readable medium. Use of the computer readable medium enables the program to be installed on a computer. Here, the computer readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.

Embodiments have been described above in detail with reference to the drawings, but specific configurations are not limited to those described above, and various design variation can be made without departing from the scope as defined by the appended claims.

Claim 1:
A communication control method using a user equipment (<NUM>), the user equipment (<NUM>) comprising a first subscriber identity module, SIM (<NUM>-<NUM>), corresponding to a first mobile network (<NUM>-<NUM>) and a second SIM (<NUM>-<NUM>) corresponding to a second mobile network (<NUM>-<NUM>), the method comprising
receiving, by the user equipment (<NUM>) from the first mobile network (<NUM>-<NUM>), information related to whether the user equipment (<NUM>) is configured to transmit timing information, the timing information being based on an execution timing that is a timing at which communication is performed in the second mobile network (<NUM>-<NUM>),
determining, by the user equipment (<NUM>), whether transmission of the timing information is permitted based on the information related to transmission of the timing information, and
transmitting, by the user equipment (<NUM>), the timing information to the first mobile network (<NUM>-<NUM>) in response to determining that transmission of the timing information is permitted and the user equipment (<NUM>) being in a RRC connected state in the first mobile network (<NUM>-<NUM>).