Communication control method

Abstract

The communication control method according to an aspect is a communication control method using a user equipment including a first SIM corresponding to a first mobile network and a second SIM corresponding to a second mobile network. The communication control method includes, in response to occurrence of a predetermined event, transmitting, by the user equipment, timing information to the first mobile network, and the timing information indicating a timing at which communication is performed in the second mobile network.

Description

Technical Field

[0001] This invention relates to communication control methods. Background Technology

[0002] In order to utilize mobile communication services (voice calling services, data communication services, etc.) provided by telecommunications operators (operators or telecommunications companies) via mobile networks, user equipment needs to be equipped with a subscriber identification module (SIM). Once the user equipment registers with the mobile network using the SIM, the user equipment can utilize mobile communication services from the mobile network at the registration destination.

[0003] In recent years, user equipment that can be equipped with multiple SIMs has become commonplace. A user equipment equipped with two SIMs (a first SIM and a second SIM) can utilize mobile communication services from a first mobile network (the mobile network to which the first SIM is registered) and can also utilize mobile communication services from a second mobile network (the mobile network to which the second SIM is registered). Discussions relating to use cases involving the use of these two mobile communication services have been initiated within the 3rd Generation Partnership Project (3GPP) (e.g., Non-Patent Document 1).

[0004] Reference List

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP Technical Report TR22.834 “TR22.834V17.1.0”, September 2019, URL<URL:http: / / www.3gpp.org / ftp / Specs / archive / 22_series / 22.834 / 22834-h10.zip> . Summary of the Invention

[0007] The communication control method according to the first aspect uses a user equipment communication control method, the user equipment including a first subscriber identification module (SIM) corresponding to a first mobile network and a second SIM corresponding to a second mobile network. The communication control method includes: in response to the occurrence of a predetermined event, the user equipment sending timing information to the first mobile network, the timing information indicating the execution of timing, the execution of timing being the timing for performing communication in the second mobile network. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating the configuration of a mobile communication system according to an embodiment.

[0009] Figure 2 This is a diagram illustrating the configuration of a user equipment according to an embodiment.

[0010] Figure 3This is a diagram illustrating the configuration of a base station according to an embodiment.

[0011] Figure 4 This is a diagram illustrating the configuration of the core network device according to an embodiment.

[0012] Figure 5 This is a diagram illustrating the protocol stack configuration of the radio interface in the user plane according to an embodiment.

[0013] Figure 6 This is a diagram illustrating the protocol stack configuration of the radio interface in the control plane that processes signaling (control signals) according to an embodiment.

[0014] Figure 7 This is a diagram illustrating an example of unicast scheduling timing according to the first embodiment.

[0015] Figure 8 This is a diagram illustrating the operation of Operation Example 1 according to the first embodiment.

[0016] Figure 9 This is a diagram illustrating the operation of Operation Example 2 according to the first embodiment.

[0017] Figure 10 This is a diagram illustrating the operation of operation example 3 according to the first embodiment.

[0018] Figure 11 This is a diagram illustrating the operation of operation example 4 according to the first embodiment.

[0019] Figure 12 This is a diagram illustrating operation according to the second embodiment. Detailed Implementation

[0020] In user equipment, when communication occurs simultaneously in a first mobile network and a second mobile network, one of the communications may not be executed. Specifically, when the first and second mobile networks belong to different communication operators, such problems are difficult to avoid in cooperation between the mobile networks.

[0021] The purpose of this disclosure is to enable user equipment equipped with multiple SIMs to properly perform communications in multiple mobile networks.

[0022] A mobile communication system according to an embodiment is described with reference to the accompanying drawings. In the description of the drawings, the same or similar reference numerals denote the same or similar parts.

[0023] Mobile communication system

[0024] The configuration of a mobile communication system according to an embodiment is described. Although the mobile communication system according to the embodiment is a 3GPP 5G system, 3GPP Long Term Evolution (LTE) can be applied at least partially to this mobile communication system.

[0025] Figure 1 This is a diagram illustrating the configuration of a mobile communication system according to an embodiment.

[0026] like Figure 1 As shown, the mobile communication system includes a first mobile network (MN 40-1) operated by a first communication operator, a second mobile network (MN 40-2) operated by a second communication operator, and user equipment (UE) 100. UE 100 can register with MN 40-1 using SIM 140-1, which will be described later, and can register with MN 40-2 using SIM 140-2. Unless otherwise specified, MN 40-1 and MN 40-2 are referred to as MN 40 below.

[0027] MN 40 can be a network using 5G technology or a network using LTE technology. Figure 1 This is an example of MN 40 using 5G technology. MN 40 includes a 5G radio access network (Next Generation Radio Access Network (NG-RAN)) 10 and a 5G core network (5GC) 20. When MN 40 uses LTE technology, NG-RAN is understood as the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), and 5GC is understood as the Evolved Packet Core (EPC). When MN 40 uses LTE technology, the gNB, described later, is understood as the eNB, and the AMF, described later, is understood as the Mobility Management Entity (MME). The UPF, described later, is understood as the Serving Gateway (S-GW) and / or the Packet Data Network Gateway (P-GW).

[0028] UE 100 is a mobile device. UE 100 can be any type of device as long as it is used by a user, and examples of UE 100 include mobile phone terminals (including smartphones), tablet terminals, laptop PCs, communication modules (including communication cards or chipsets), sensors or devices mounted on sensors, vehicles or devices mounted on vehicles (vehicle UE), and flying objects or devices mounted on flying objects (airborne UE).

[0029] NG-RAN 10 includes base stations (referred to as "gNBs" in 5G systems) 200. gNBs 200 can also be referred to as NG-RAN nodes. gNBs 200 are interconnected via an Xn interface (not shown) corresponding to the inter-base station interface. Each gNB 200 manages one or more cells. gNBs 200 perform wireless communication with UE 100, which has established a connection to a cell of the gNB 200. gNBs 200 have Radio Resource Management (RRM) functions, functions for routing user data (hereinafter referred to as "data"), measurement and control functions for mobility control and scheduling, etc. "Cell" is used as a term to represent the smallest unit of a wireless communication area. "Cell" is also used as a term to represent the functions or resources used to perform wireless communication with UE 100. A cell belongs to one carrier frequency.

[0030] Please note that a gNB can connect to the Evolved Packet Core (EPC), which serves as the core network of LTE, or an LTE base station can connect to the 5GC. LTE base stations and gNBs can connect via an inter-base station interface.

[0031] 5GC 20 includes Access and Mobility Management Function (AMF) 300 and User Plane Function (UPF) 400. AMF 300 performs various types of mobility control for UE 100. AMF 300 manages information about the area where UE 100 exists by communicating with UE 100 using Non-Access Stratum (NAS) signaling. UPF 400 controls data transmission. AMF 300 and UPF 400 are connected to gNB 200 via the NG interface, which is the interface between the base station and the core network.

[0032] Figure 2 This is a diagram showing the configuration of UE 100 (User Equipment).

[0033] like Figure 2 As shown, UE 100 includes a receiver 110, a transmitter 120, a controller 130, SIM 140-1 (first SIM), SIM 140-2 (second SIM), and a user interface 150. UE 100 may include three or more SIMs 140.

[0034] Receiver 110 performs various types of reception under the control of controller 130. Receiver 110 includes an antenna and receiving equipment. The receiving equipment converts the radio signals received through the antenna into baseband signals (received signals) and outputs the obtained signals to controller 130.

[0035] Transmitter 120 performs various types of transmissions under the control of controller 130. Transmitter 120 includes an antenna and a transmitting device. The transmitting device converts the baseband signal (transmit signal) output by controller 130 into a radio signal and transmits the obtained signal through the antenna.

[0036] Controller 130 performs various types of control within UE 100. Controller 130 includes at least one processor and at least one memory electrically connected to the processor. The memory stores programs 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, encoding and decoding of baseband signals, etc. The memory stores programs to be executed by the processor and information to be used for processing by the processor.

[0037] SIM 140 records information identifying the subscriber for receiving mobile communication services provided from a mobile network. In addition to subscriber identification information, SIM 140 may record operator identification information for identifying the communication operator, as well as information related to the available services subscribed to by the subscriber. SIM 140 can be an IC card (i.e., a data card) known as a removable SIM card (or USIM card). SIM 140 can also be an embedded type of embedded SIM (eSIM).

[0038] The information recorded in SIM 140-1 (first SIM) identifies a first International Mobile Subscriber Identity (IMSI), which corresponds to an identification number assigned to the user of UE 100 by a first communication operator operating the first mobile network 40-1. The information recorded in SIM 140-2 (second SIM) identifies a second IMSI, which corresponds to an identification number assigned to the user of UE 100 by a second communication operator operating the second mobile network 40-2. SIM 140-1 and SIM 140-2 can be separate information cards or integrated into the same information card. SIM 140-1 and SIM 140-2 can be included in an embedded SIM (eSIM).

[0039] SIM 140-1 is managed by the first telecommunications operator. SIM 140-2 is managed by the second telecommunications operator. Note that SIM 140-1 and SIM 140-2 can be managed by the same telecommunications operator.

[0040] When UE 100 registers with the first mobile network 40-1 using SIM 140-1, UE 100 can use mobile communication services provided by the first telecommunications operator via the first mobile network 40-1. When UE 100 registers with the second mobile network 40-2 using SIM 140-2, UE 100 can use mobile communication services provided by the second telecommunications operator via the second mobile network 40-2.

[0041] Users of UE 100 can configure the priority of SIM 140-1 and SIM 140-2 via user interface 150. Users can configure the priority so that SIM 140-1 takes precedence over SIM 140-2, or SIM 140-2 takes precedence over SIM 140-1.

[0042] Figure 3 This is a diagram showing the configuration of gNB 200 (base station).

[0043] like Figure 3 As shown, the gNB 200 includes a transmitter 210, a receiver 220, a controller 230, and a backhaul communicator 240.

[0044] Transmitter 210 performs various types of transmissions under the control of controller 230. Transmitter 210 includes an antenna and a transmitting device. The transmitting device converts the baseband signal (transmit signal) output by controller 230 into a radio signal and transmits the obtained signal through the antenna.

[0045] Receiver 220 performs various types of reception under the control of controller 230. Receiver 220 includes an antenna and receiving equipment. The receiving equipment converts the radio signals received through the antenna into baseband signals (received signals) and outputs the resulting signals to controller 230.

[0046] Controller 230 performs various types of control for gNB 200. Controller 230 includes at least one processor and at least one memory electrically connected to the processor. The memory stores programs to be executed by the processor and information for the processing performed by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation and demodulation, encoding and decoding of baseband signals, etc. The memory stores programs to be executed by the processor and information for the processing performed by the processor.

[0047] The backhaul communicator 240 is connected to the adjacent base station via the inter-base station interface. The backhaul communicator 240 is connected to the AMF / UPF 300 via the interface between the base station and the core network.

[0048] Figure 4 This is a diagram showing the configuration of the AMF 300 (core network device).

[0049] like Figure 4 As shown, the AMF 300 includes a controller 330 and a backhaul communicator 340.

[0050] The controller 330 performs various types of control within the AMF 300. The controller 330 includes at least one processor and at least one memory electrically connected to the processor. The memory stores programs to be executed by the processor and information for the processing performed by the processor.

[0051] The backhaul communicator 340 is connected to the gNB 200 via the interface between the base station and the core network.

[0052] Figure 5 This is a diagram illustrating the protocol stack configuration of the radio interface in the user plane that processes data.

[0053] like Figure 5 As shown, the radio interface protocols in the user plane include the Physical (PHY) layer, the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, the Packet Data Convergence Protocol (PDCP) layer, and the Service Data Adaptation Protocol (SDAP) layer.

[0054] The PHY layer performs encoding 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 UE 100 and the PHY layer of gNB 200 via physical channels.

[0055] In the PHY layer, a frame structure is used, comprising radio frames, subframes, time slots, and symbols. A radio frame consists of 10 subframes on the time axis. Each subframe is 1 ms long. Each subframe includes multiple time slots. Each time slot includes multiple symbols. Each subframe includes multiple resource blocks (RBs) on the frequency axis. Each resource block includes multiple subcarriers on the frequency axis. In the radio resources (time resources and frequency resources) allocated to UE 100, frequency resources can be identified by resource blocks, and time resources can be identified by subframes (or time slots or symbols).

[0056] In the downlink, the first few symbols of each subframe are used as the Physical Downlink Control Channel (PDCCH), which is primarily used to transmit downlink control information. The remaining portion of each subframe is used as the Physical Downlink Shared Channel (PDSCH), which is primarily used to transmit downlink data.

[0057] The MAC layer performs data priority control, retransmission processing using Hybrid ARQ (HARQ), random access procedures, etc. Data and control information are transmitted between the MAC layer of UE 100 and the MAC layer of gNB 200 via the transport channel. The MAC layer of gNB 200 includes a scheduler. The scheduler determines the transport format (transport block size, modulation and coding scheme (MCS)) in the uplink and downlink and the resource blocks to be allocated to UE 100.

[0058] The RLC layer transmits data to the receiving RLC layer using the functions of the MAC and PHY layers. Data and control information are transmitted between the RLC layer of UE 100 and the RLC layer of gNB 200 via logical channels.

[0059] The PDCP layer performs header compression and decompression, as well as encryption and decryption.

[0060] The SDAP layer performs the mapping between IP flows and radio bearers. IP flows are the units used by the core network to perform QoS control, while radio bearers are the units used by the access layer (AS) to perform QoS control. Note that SDAP may not be provided when the RAN is connected to the EPC.

[0061] Figure 6 This is a diagram illustrating the protocol stack configuration of the radio interface in the control plane that processes signaling (control signals).

[0062] like Figure 6 As shown, the protocol stack of the control plane's radio interface includes a Radio Resource Control (RRC) layer and a Non-Access Stratum (NAS) layer, instead of... Figure 5 The SDAP layer is shown in the figure.

[0063] RRC signaling for various configurations is transmitted between the RRC layer of UE 100 and the RRC layer of gNB 200. The RRC layer controls logical channels, transport channels, and physical channels based on the establishment, reconstruction, and release of radio bearers. When a connection exists between the RRC of UE 100 and the RRC of gNB 200 (RRC connection), UE 100 is in an RRC connected state. When no connection exists between the RRC of UE 100 and the RRC of gNB 200 (RRC connection), UE 100 is in an RRC idle state. When the RRC connection is interrupted (suspended), UE 100 is in an RRC inactive state.

[0064] The NAS layer, located above the RRC layer, performs session management, mobility management, and other functions. NAS signaling is transmitted between the NAS layer of UE 100 and the NAS layer of AMF 300.

[0065] Note that, in addition to the radio interface protocol, UE 100 includes the application layer.

[0066] First Embodiment

[0067] The first embodiment is described based on the system configuration assumptions described above.

[0068] When scheduling simultaneous communications of UE 100 in MN 40-1 and UE 100 in MN 40-2, one of the communications may be unable to execute due to the capabilities of UE 100. For example, when the two MN 40s schedule downlink communications at different frequencies at the same timing for UE 100, UE 100 with only a single radio receiving device (receiver 110) cannot execute one of the two downlink communications. Even if UE 100 includes multiple radio receiving devices, it may not be able to execute the other downlink communication when one of the downlink communications uses significant resources of UE 100's CPU. Preferably, UE 100 does not allow the two communications to conflict with each other. The first embodiment is an embodiment for solving such a problem.

[0069] In the first embodiment, UE 100 sends timing information to NW 40-1 to identify the execution timing, which is the timing for performing communication in NW 40-2. This allows NW 40-1 to recognize the timing of UE 100's communication in NW 40-2 and schedule communication with UE 100 at a timing that does not overlap with the former. Therefore, conflicts between communication in NW 40-1 and communication in NW 40-2 can be avoided.

[0070] The execution timing includes at least one of the following: paging reception timing, unicast scheduling timing, MBS scheduling timing, and secondary link scheduling timing.

[0071] Paging reception timing

[0072] The paging reception timing is the timing when the UE 100, which is in an RRC idle state or an RRC inactive state, monitors a paging from NW 40-2.

[0073] UE 100 in RRC idle state monitors CN paging. UE 100 in RRC inactive state monitors both CN paging and RAN paging. CN paging is a paging initiated by the core network (CN). RAN paging is a paging initiated by the RAN.

[0074] UE 100 in RRC idle state and RRC inactive state uses discontinuous reception (DRX) to monitor paging in order to reduce power consumption.

[0075] UE 100 monitors a paging opportunity (PO) per DRX cycle. A DRX cycle is represented by the number of radio frames. A DRX cycle may be referred to as a paging cycle. A PO may consist of one or more subframes, or one or more symbols. A PO is associated with a paging frame (PF) as a radio frame. A PO associated with a PF may begin within or after the PF.

[0076] The paging reception timing of UE 100 is included in the timing (subframe or symbol) in the PO generated for each DRX cycle.

[0077] UE 100 determines: the smaller of the default DRX cycle configured for UE 100 and the UE-specific DRX cycle is the DRX cycle that UE 100 is to use to monitor paging (hereinafter referred to as "T").

[0078] The default DRX cycle is included in the system information received from the serving cell (gNB 200) where UE 100 exists.

[0079] The UE-specific DRX cycle varies depending on the RRC state of UE 100. When UE 100 is in an RRC idle state, the UE-specific DRX cycle includes a first UE-specific DRX cycle. When UE 100 is in an RRC inactive state, the UE-specific DRX cycle includes a first UE-specific DRX cycle and a second UE-specific DRX cycle.

[0080] The first UE-specific DRX cycle is the UE-specific DRX cycle configured for UE 100 to monitor CN paging by a NAS message. Such a NAS message is, for example, the registration receive (REGISTER ACCEPT) message from AMF 300-2 in NW 40-2 when UE 100 registers with NW 40-2.

[0081] The second UE-specific DRX cycle is a UE-specific DRX cycle configured for UE 100 to monitor RAN paging by a dedicated RRC message. Such a dedicated RRC message is, for example, an RRC release message used to transition UE 100 from an RRC connected state to an RRC inactive state. Such an RRC release message includes a "SuspendConfig" information element (IE), and the "SuspendConfig" includes information indicating the second UE-specific DRX cycle.

[0082] UE 100 in RRC idle state will determine the smaller of the default DRX period and the first UE-specific DRX period as "T".

[0083] When UE 100 is in an RRC inactive state, it will determine the smaller of the default DRX period, the first UE-specific DRX period, and the second UE-specific DRX period as "T".

[0084] Note that when no specific DRX period is configured for the UE, the UE 100 will set the default DRX period to "T".

[0085] After determining “T”, UE 100 uses “T”, “UE_ID” and paging-related information to determine the radio frame number of PF and the subframes or symbols included in PO.

[0086] Here, "UE_ID" represents the value calculated using the temporary subscriber identifier assigned to UE 100 via AMF 300-2. For example, such a temporary subscriber identifier is the 5G-S-Temporary Mobile Subscriber Identifier (TMSI). For example, "UE_ID" has a value obtained by "modulo 1024 using the 5G-S-TMSI".

[0087] Paging-related information is included in the system information received from the serving cell (gNB 200) where UE 100 resides. Paging-related information includes parameters such as N, Ns, and PF_offset.

[0088] Note that for details regarding the determination methods of T, PF, and PO mentioned above, please refer to 3GPP technical specification TS38.304, for example. Note that for details regarding the determination method when UE 100 is present in an LTE cell, please refer to 3GPP technical specification TS36.304, for example.

[0089] Unicast scheduling timing

[0090] Unicast scheduling timing is a candidate timing for scheduling unicast data transmission / reception between UE 100, which is in RRC connection state, and NW 40-2 (gNB 200-2).

[0091] Unicast scheduling timing is the timing within a scheduling period generated within a cycle.

[0092] Figure 7 This is a diagram illustrating an example of unicast scheduling timing.

[0093] like Figure 7 As shown, a scheduling period is a time period generated for each cycle "P". The scheduling period begins at the start timing (t1, t2, t3...). The scheduling period has a predetermined duration (D).

[0094] During a scheduled period within a cycle, gNB 200 allocates communication timing (subframes, time slots, symbols, etc.) for unicast data to UE 100. Conversely, gNB 200 does not allocate communication timing to UE 100 during non-scheduled periods (periods not within a scheduled period) within a cycle. Communication timing includes at least one of the timing for UE 100 to send unicast data to gNB 200 and the timing for gNB 200 to send unicast data to UE 100.

[0095] The timing of unicast scheduling is identified by three parameters: start time, period, and predetermined duration.

[0096] The start timing can be indicated by the radio frame number and subframe number, or by a slot number or symbol number in addition to the radio frame number and subframe number. The period is indicated by the number of radio frames, the number of subframes, or the number of slots. The predetermined duration is indicated by the number of subframes, the number of slots, or the number of symbols.

[0097] The gNB 200 configures unicast scheduling timing for UE100 in unicast RRC messages (e.g., RRC reconfiguration messages). The gNB 200 can configure unicast scheduling timing for UE100 in response to requests from UE100. The gNB 200 can configure unicast scheduling timing for UE100 based on UE100's past service history and / or UE100's future service predictions.

[0098] The scheduling period generated for each cycle can include multiple discontinuous timings. For example, a scheduling period can include multiple discontinuous timings within a predetermined duration (D). In this case, the multiple discontinuous timings within the predetermined duration are represented by a bitmap. For example, when the predetermined duration corresponds to four subframes, and the first and fourth subframes of the four subframes are timings corresponding to the scheduling period, the scheduling period is identified by a bitmap (1,0,0,1) and the predetermined duration.

[0099] MBS scheduling timing

[0100] MBS scheduling is a candidate timing for scheduling MBS data transmission from NW 40-2 to UE 100. MBS is a service that performs data transmission from NW 40-2 to UE 100 in broadcast or multicast mode (in other words, point-to-multipoint (PTM) mode). MBS can be referred to as Multimedia Broadcast and Multicast Service (MBMS). MBS data refers to data sent via MBS.

[0101] MBS scheduling timing is the timing within the scheduling period generated within the cycle.

[0102] Similar to or in the case of unicast scheduling, MBS scheduling can be identified by parameters such as start timing, period, predetermined duration, and bitmap. Here, the parameters used to identify MBS scheduling are different from those used to identify unicast scheduling.

[0103] MBS scheduling timing can be configured for UE 100 from gNB 200 via broadcast RRC messages (e.g., MBS SIB). MBS scheduling timing can be configured for UE 100 regardless of UE 100's RRC status.

[0104] When UE 100 is interested in receiving MBS data regardless of its RRC status, UE 100 acquires the MBSSIB and identifies the MBS scheduling timing based on the MBS information included in the MBS SIB. The MBS information may directly include parameters used to identify the MBS scheduling timing. The MBS information may also include MBS control channel configuration information for UE 100 to receive the MBS control channel carrying parameters used to identify the MBS scheduling timing.

[0105] Secondary link scheduling timing

[0106] Secondary link scheduling timing is a candidate timing for UE 100 to schedule secondary link communication in NW 40-2. Secondary link communication is communication performed between nearby UE 100s without going through a network node (e.g., gNB 200). Secondary link communication includes at least one of secondary link transmission and secondary link reception, in which UE 100 sends data to another UE 100 and in which UE 100 receives data from another UE 100.

[0107] The timing of secondary link scheduling includes the timing of the scheduling period generated within the cycle.

[0108] Similar to or the unicast scheduling timings described above, secondary link scheduling timings can be identified by parameters such as start timing, period, predetermined duration, and bitmap. Here, the parameters used to identify secondary link scheduling timings differ from those used to identify unicast scheduling timings. The parameters used to identify secondary link scheduling timings also differ from those used to identify MBS scheduling timings.

[0109] Secondary link scheduling timing can be configured for UE 100 from gNB 200 via broadcast RRC messages (e.g., secondary link SIB). Secondary link scheduling timing can be configured for UE 100 regardless of UE 100's RRC status.

[0110] When UE 100 is interested in secondary link communication, regardless of its RRC status, UE 100 acquires the secondary link SIB and identifies the timing of secondary link scheduling based on the secondary link information included in the SIB. The secondary link information includes, for example, information indicating the resource pool used for secondary link communication.

[0111] Operation Example 1 of the First Embodiment

[0112] Figure 8 This is a diagram illustrating the operation of Operation Example 1 according to the first embodiment.

[0113] like Figure 8 As shown, in the initial state of Operation Example 1, UE 100 registers with both MN 40-2 and MN 40-1. In the initial state, UE 100 is in an RRC state in MN 40-2, which can be any one of the following RRC states: RRC connected, RRC idle, and RRC inactive. UE 100 is also in an RRC state in MN 40-1, which can be any one of the following RRC states: RRC connected, RRC idle, and RRC inactive.

[0114] In step S101, UE 100 determines whether a predetermined event has occurred. The predetermined event is described in detail below. When UE 100 determines that a predetermined event has occurred (step S101: Yes), UE 100 proceeds the process to step S102.

[0115] In step S102, UE 100 sends timing information to NW 40-1 to identify the execution timing, which is the timing for performing communication in NW 40-2. The timing information includes at least one of information for identifying the paging reception timing, information for identifying the unicast scheduling timing, information for identifying the MBS scheduling timing, and information for identifying the secondary link scheduling timing.

[0116] In step S102, when UE 100 is in RRC idle state or RRC inactive state in NW 40-1, UE 100 can switch to RRC connected state and then send timing information.

[0117] In step S102, the destination of the timing information is gNB 200-1 and / or AMF 300-1 in NW 40-1. When the destination of the timing information is gNB 200-1, the timing information is sent in an RRC message. When the destination of the timing information is AMF 300-1, the timing information is sent in a NAS message.

[0118] When UE 100 preferably transitions from an RRC connected state to an RRC idle state in MN 40-1, UE 100 can determine the destination of the timing information transmission as AMF 300-1. In this case, UE 100 can send information indicating that UE 100 preferably transitions to an RRC idle state to gNB 200-1 after step S102. When UE 100 preferably transitions from an RRC connected state to an RRC inactive state in MN 40-1, UE 100 can determine the destination of the timing information transmission as both AMF300-1 and gNB 200-1. In this case, UE 100 can send information indicating that UE 100 preferably transitions to an RRC inactive state to gNB 200-1 after step S102.

[0119] When UE 100 sends timing information in a NAS message, the NAS layer of UE 100 generates the timing information. In this case, the RRC layer sends information identifying the necessary timing to the NAS layer of UE 100. This necessary information includes, for example, the second UE-specific DRX period and the default DRX period identified by the RRC layer as described above.

[0120] UE 100 can send timing information along with information indicating the protection time. The protection time is the time required for UE 100 to switch from communication with NW 40-2 (gNB 200-2) to communication with NW 40-1 (gNB 200-1). The protection time is represented by the number of radio frames, the number of subframes, the number of time slots, or the number of symbols. The protection time can be provided before and after timing (e.g., PO).

[0121] When the timing between NW 40-1 (gNB 200-1) and NW 40-2 (gNB 200-2) is asynchronous, the timing information sent to NW 40-1 may include information identifying the timing (radio frame number, subframe number, time slot number, symbol number, etc.) of NW 40-1 corresponding to the execution timing of NW 40-2. In this case, the timing information may be information indicating the timing (radio frame number, subframe number, time slot number, symbol number, etc.) of NW 40-1 corresponding to the execution timing of NW 40-2. The timing information may include information indicating the execution timing of NW 40-2, and information indicating the timing difference between NW 40-1 (gNB 200-1) and NW 40-2 (gNB 200-2). This timing difference is represented by the number of radio frames, the number of subframes, the number of time slots, the number of symbols, etc.

[0122] In step S103, MN 40-1 (gNB 200-1 and / or AMF 300-1) communicates with UE 100 without using the timing identified by the information received in step S102 (timing information, or timing information and information indicating protection time). Hereinafter, the timing identified by the information received in step S102 (timing information, information indicating protection time) will be referred to as "unused timing".

[0123] The operations in step S103 include, for example, the following operations 1 to 4.

[0124] Operation 1: When gNB 200-1 transitions UE 100 to the RRC inactive state, gNB 200-1 configures the UE-specific DRX cycle of UE 100 (the second UE-specific DRX cycle mentioned above) so that the PO corresponding to the RAN paging sent from gNB 200-1 is arranged at an unused timing, and sends an RRC release message including the UE-specific DRX cycle to UE 100.

[0125] Operation 2: gNB 200-1 assigns a timing other than the one used to the data transmission / reception of UE 100 in RRC connection state.

[0126] Operation 3: gNB 200-1 will configure a communication gap for UE100 in RRC connection state, including a predetermined time period without timed usage, and send information indicating the communication gap to UE100. gNB 200-1 will not schedule data transmission to UE100 or data reception from UE100 in this communication gap.

[0127] Operation 4: The AMF 300-1 configures the UE-specific DRX cycle of UE 100 (the first UE-specific DRX cycle mentioned above) and the new 5G-S-TMSI assigned to UE 100 so that the PO corresponding to the CN paging sent from the AMF 300-1 is scheduled at an unused time, and notifies UE 100 of these times in a NAS message. Alternatively, the AMF 300-1 may notify UE 100 of the offset value for the 5G-S-TMSI already assigned to UE 100, instead of assigning a new 5G-S-TMSI to UE 100. The offset value is only used to identify the paging reception timing. The offset value may be notified from the AMF 300-1 to the gNB 200-1 during paging execution.

[0128] Note that the operation in step S103 is optional.

[0129] The scheduled event is described. The scheduled event includes any one of the following events A through F.

[0130] Event A is the event that causes UE 100 to start monitoring paging messages in NW 40-2.

[0131] When event A occurs in UE 100 in step S101, in step S102, UE 100 sends timing information including information indicating the timing of paging reception. The timing information may also include information for identifying another execution timing (unicast scheduling timing, MBS scheduling timing, and secondary link scheduling timing) identified by UE 100 at that time.

[0132] Event A includes, for example, any of the following events A1 to A3.

[0133] Event A1 indicates that UE 100 transitions from RRC connected state to RRC inactive state in NW 40-2.

[0134] Event A2 indicates that UE 100 transitions from RRC connected state to RRC idle state in NW 40-2.

[0135] Event A3 is an event that can cause the paging reception timing to change in UE 100, which has already started monitoring paging messages in NW 40-2.

[0136] When event B occurs in UE 100 in step S101, in step S102, UE 100 sends timing information including information indicating the paging reception timing (updated paging reception timing). The timing information may also include information for identifying another execution timing recognized by UE 100 at that time.

[0137] Event B is any of the following events, such as B1 to B3.

[0138] Event B1 indicates that UE 100, which is in an RRC inactive state, transitions to an RRC idle state in NW 40-2. In this case, UE 100 determines "T" without considering the second UE-specific DRX cycle, so "T" may change.

[0139] Event B2 indicates that after UE 100, which is in an RRC inactive state in NW 40-2, performs a Ran Notification Area (RNA) update procedure, it maintains its RRC inactive state. In this case, UE 100 again receives an RRC release message including "Pause Configuration," and therefore, can update the second UE-specific DRX cycle and change "T." For details of the RNA update procedure, see 3GPP Technical Specification TS38.300, Chapter 9.2.2.5.

[0140] Event B3 instructs UE 100, which is in an RRC inactive or RRC idle state in NW 40-2, to perform cell reselection. In this case, the default DRX period can be changed in response to changing the serving cell of UE 100, and therefore, "T" can be changed.

[0141] Event C indicates that a unicast scheduling timing is configured for UE 100 in NW 40-2, or that the unicast scheduling timing of UE 100 is changed in NW 40-2.

[0142] When event C occurs in UE 100 in step S101, in step S102, UE 100 sends timing information including information for identifying the timing of unicast scheduling. The timing information may also include information for identifying another execution timing identified by UE 100 at that time.

[0143] Event D indicates that UE 100 is interested in receiving MBS data in NW 40-2, UE 100 starts receiving MBS data in NW 40-2, or the timing of UE 100's MBS scheduling changes in NW 40-2.

[0144] When event D occurs in UE 100 in step S101, in step S102, UE 100 sends timing information including information for identifying the MBS scheduling timing. The timing information may also include information for identifying another execution timing identified by UE 100 at that time.

[0145] Event E indicates that UE 100 is interested in secondary link communication in NW 40-2, UE 100 starts secondary link communication in NW 40-2, or the timing of secondary link scheduling of UE 100 changes in NW 40-2.

[0146] When event E occurs in UE 100 in step S101, in step S102, UE 100 sends timing information including information for identifying the timing of secondary link scheduling. The timing information may also include information for identifying another execution timing identified by UE 100 at that time.

[0147] Event F indicates that UE 100 has transitioned to RRC connected state in NW 40-1.

[0148] When event F occurs in UE 100 in step S101, in step S102, UE 100 sends timing information, which includes information identifying the execution timing that UE 100 has identified when event F occurs. For example, when UE 100 has been monitoring paging in NW 40-2 and receiving MBS data when event F occurs, UE 100 sends timing information including information identifying the paging reception timing and information identifying the MBS scheduling timing.

[0149] Operation Example 2 of the First Embodiment

[0150] This section primarily describes the differences between Operation Example 2 and Operation Example 1. Operation Example 2 is an example related to allowing the sending of timing information.

[0151] Figure 9 This is a diagram illustrating the operation of Operation Example 2 according to the first embodiment.

[0152] In step S201, UE 100 receives information from NW 40-1 (gNB 200-1) indicating whether timing information transmission is permitted (hereinafter referred to as "transmittability information"). UE 100 may receive the transmittability information in a dedicated RRC message or in an SIB. UE 100 stores the received transmittability information.

[0153] Before step S201, UE 100 may send a request message to gNB 200-1 requesting permission to transmit timing information. In response to receiving the request message, gNB 200-1 sends transmittance information to UE 100 in a dedicated RRC message. This request message may include information indicating that UE 100 is in a state registered with both MN 40-1 and MN 40-2 (hereinafter referred to as the "MUSIM state"). When UE 100 is in the MUSIM state, gNB 200-1 may send transmittance information to UE 100 indicating permission to transmit timing information. In the current LTE specification, there is no defined processing for UE 100 with multiple SIMs, and therefore, when NW 40-1 uses LTE technology (i.e., NW 40-1 has E-UTRAN and EPC), transmitting timing information may not be permitted.

[0154] In step S202, UE 100 determines whether a predetermined event has occurred. The predetermined event has occurred. When UE 100 determines that the predetermined event has occurred (step S202: Yes), UE 100 proceeds the process to step S203.

[0155] In step S203, UE 100 determines whether to allow the transmission of timing information based on the stored transmissibility information. When UE 100 determines that the transmission of timing information is not allowed (step S202: No), UE 100 terminates the process. When UE determines that the transmission of timing information is allowed (step S203: Yes), UE 100 advances the process to step S204.

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

[0157] Operation Example 3 of the First Embodiment

[0158] This section primarily describes the differences between Operation Example 3 and Operation Example 1. Operation Example 3 is an operation example related to priority networks.

[0159] In Operation Example 3, when UE 100 registers with both MN 40-1 and MN 40-2, UE 100 determines that one MN40 is a priority network and the other MN 40 is a non-priority network.

[0160] Compared to communications in non-priority networks, UE 100 prioritizes communications (such as paging monitoring and data transmission / reception) within the priority network. For example, when communications in the priority network and non-priority networks are scheduled within the same timing, UE 100 may perform communications in the priority network but not in the non-priority network. When UE 100 receives data sent from both the priority network and the non-priority network at the same timing, UE 100 may discard the data sent from the non-priority network. Therefore, for successful communication, the non-priority network needs to consider the timing of UE 100's execution within the priority network when scheduling communications with UE 100.

[0161] A method for determining the priority network is described. This method includes, for example, any one of the following first to fourth methods.

[0162] In the first method, UE 100 determines the preferred network based on user configuration. For example, when the user configures SIM140-2 to take precedence over SIM 140-1, UE 100 determines MN 40-2, which corresponds to SIM 140-2, as the preferred network and determines MN 40-1, which corresponds to SIM 140-1, as the non-preferred network.

[0163] In the second method, UE 100 determines MN 40, which uses LTE technology, as the priority network. For example, when MN 40-1 uses 5G technology and MN 40-2 uses LTE technology, UE 100 determines MN 40-2 as the priority network and MN 40-1 as a non-priority network. Note that when MN 40-1 and MN 40-2 use the same technology, UE 100 does not use the second method to determine the priority network.

[0164] In the third method, UE 100 identifies MN 40, where a radio bearer with a priority equal to or greater than a threshold is established, as a priority network. For example, when a radio bearer with a priority equal to or greater than the threshold is established between MN 40-2 and UE 100, UE 100 identifies MN 40-2 as a priority network and MN 40-1 as a non-priority network.

[0165] The priority of a radio bearer is determined by the service type of the user data mapped to that radio bearer. For example, a high priority is assigned when the service type is voice call, and a low priority is assigned when the service type is email, chat, web browsing, etc. The priority of a radio bearer can be a value associated with 5QI. For the correspondence between 5QI and priority, see 3GPP technical specification TS 23.501, Table 5.7.4. The priority of a radio bearer can also be a value associated with QCI. For the correspondence between QCI and priority, see 3GPP technical specification TS 23.203, Table 6.1.7.

[0166] In the fourth method, UE 100 determines MN 40, which is configured with periodic communication periods for UE 100, as the priority network. Periodic communication periods are, for example, communication periods identified by semi-persistent scheduling (SPS) or by configuration authorization (CG). For example, when MN 40-2 is configured with SPS for UE 100, UE 100 determines MN 40-2 as the priority network and MN 40-1 as the non-priority network.

[0167] use Figure 10 Let's describe operation example 3.

[0168] Figure 10 This is a diagram illustrating the operation of operation example 3 according to the first embodiment.

[0169] In step S301, UE 100 uses the priority network determination method described above to determine one of MN 40-2 and MN 40-1 as a priority network and the other network as a non-priority network.

[0170] In step S302, UE 100 determines whether a predetermined event has occurred. The predetermined event has occurred. When UE 100 determines that the predetermined event has occurred (step S302: Yes), UE 100 proceeds the process to step S303.

[0171] In step S303, UE 100 determines whether MN 40-1 is a non-priority network. When UE 100 determines that MN 40-1 is not a non-priority network (step S303: No), UE 100 terminates the process. When UE 100 determines that MN 40-1 is a non-priority network (step S303: Yes), UE 100 advances the process to step S304.

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

[0173] In Operation Example 3, after step S301, UE 100 may send a non-priority notification indicating that NW 40 is a non-priority network to NW 40, which has been determined to be a non-priority network. For example, when UE 100 determines that NW 40-1 is a non-priority network, UE 100 sends a non-priority notification to NW 40-1 (gNB 200-1 and / or AMF 300-1). UE 100 configured with periodic communicable periods in NW 40-2 may send information identifying the periodic communicable periods along with the non-priority notification.

[0174] Upon receiving a non-priority notification, gNB 200-1 identifies NW 40-1 as a non-priority network. When NW 40-1 identifies NW 40-1 as a non-priority network, gNB 200-1 can restrict the establishment of radio bearers with a priority equal to or greater than a threshold (e.g., radio bearers for voice calls) with UE 100.

[0175] In Operation Example 3, when UE 100 determines that NW 40-1 is not a non-priority network after sending a non-priority notification to NW 40-1, UE 100 can send such a determination notification to NW 40-1. In this case, the restriction on establishing radio bearers with a priority equal to or greater than the threshold is lifted.

[0176] In Operation Example 3, UE 100 can send information to NW 40, which is determined to be a non-priority network, instructing UE 100 to preferably transition to an RRC idle state or an RRC inactive state. For example, such information could indicate that UE 100's preferred RRC state is an RRC idle state. Such information could also indicate that UE 100's preferred RRC state is an RRC inactive state. Furthermore, such information could indicate that UE 100 simply prefers to release the RRC connection without specifying a preferred RRC state.

[0177] For example, when UE 100 determines that NW 40-1 is a non-priority network and is in RRC connected state within NW 40-1, UE 100 sends a message to gNB 200-1 instructing the UE to preferably transition to an RRC idle state or an RRC inactive state. This message may be sent along with timing information. gNB 200-1 can respond to the receipt of this message by causing UE 100 to transition to an RRC idle state or an RRC inactive state.

[0178] Operation Example 4 of the First Embodiment

[0179] This section primarily describes the differences between Operation Example 4 and Operation Example 1. Operation Example 4 is an operation example related to the UE context.

[0180] Figure 11 This is a diagram illustrating the operation of example 4. (For example...) Figure 11 As shown, in the initial state, UE 100 registers with MN40-2. UE 100 has an RRC connection with gNB 200-1(a) belonging to MN 40-1.

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

[0182] In step S402, UE 100 sends timing information to gNB 200-1(a) belonging to MN 40-1.

[0183] In step S403, gNB 200-1(a) stores timing information as part of the UE context of UE 100.

[0184] In step S404, during the predetermined process for establishing an RRC connection between gNB 200-1(b) belonging to MN 40-1 and UE 100, gNB 200-1(a) sends a UE context including timing information.

[0185] Examples of pre-defined procedures include switching procedures, RRC connection reconstruction procedures, and RRC connection recovery procedures.

[0186] For example, gNB 200-1(a) sends a HandoverPreparationInformation message during the handover process, which includes the UE context (including timing information).

[0187] During RRC recovery, gNB 200-1(a) may send the UE context to gNB 200-1(b) in response to receiving a RETRIEVE UE CONTEXT REQUEST message from gNB 200-1(b) requesting the provision of the UE context.

[0188] After the predetermined process is completed, in step S405, an RRC connection is established between UE 100 and gNB 200-1(b).

[0189] In step S406, gNB 200-1(b) communicates with UE 100 without using the timing identified by the timing information (operations 1 to 3 in step S103 above).

[0190] Second Embodiment

[0191] The second embodiment is an example of operation related to voice communication.

[0192] Figure 12 A diagram illustrating operation according to the second embodiment is shown.

[0193] In step S501, UE 100 determines whether a voice communication event has occurred in NW 40-2. When UE 100 determines that a voice communication event has occurred (step S501: Yes), UE 100 proceeds the process to step S502.

[0194] The voice communication event instructs the user of UE 100 to send an outgoing voice call via NW 40-2, or instructs UE 100 to receive a paging message to notify of an incoming voice call.

[0195] In step S502, UE 100 queries MN 40-1 whether voice communication is permitted for UE 100.

[0196] In step S503, UE 100 receives a permission notification from MN 40-1 indicating that voice communication is permitted.

[0197] In step S504, UE 100 performs voice communication in response to receiving an permission notification. Note that UE 100 does not perform voice communication if it does not receive a permission notification.

[0198] Third Embodiment

[0199] The third embodiment assumes that NW 40-1 and NW 40-2 belong to the same telecommunications operator.

[0200] In the third embodiment, when UE 100 registers with both NW 40-1 and NW 40-2, UE 100 sends information (hereinafter referred to as "MUSIM state information") to both NW 40-1 and NW 40-2 indicating that UE 100 is in a state of registration with both NW 40-1 and NW 40-2. This allows NW 40-1 and NW 40-2 to recognize that the same UE 100 has registered with both NW 40-1 and NW 40-2. Therefore, NW 40-1 and NW 40-2 can cooperate with each other to properly communicate with UE 100.

[0201] When UE 100 is in RRC connected state in both NW 40-1 and NW 40-2, UE 100 can send MUSIM status information that further indicates the state.

[0202] The destination for sending MUSIM status information is AMF 300 (both AMF 300-1 and AMF 300-2) and / or gNB200 (both gNB 200-1 and gNB 200-2). AMF 300-1 can forward MUSIM status information received from UE 100 to gNB 200-1. gNB 200-1 can forward MUSIM status information received from UE 100 to AMF 300-1. gNB200-1 can store the MUSIM status information received from UE 100 as part of the UE context of UE 100.

[0203] When the destination of the MUSIM status information is AMF 300, UE 100 can send the MUSIM status information together with information indicating that the registration to NW 40-1 and the registration to NW 40-2 belong to the same UE 100. For example, such information can indicate that the temporary subscriber identifiers (such as 5G-S-TMSI) assigned from the two NW 40s belong to the same UE 100.

[0204] When the destination of the MUSIM status information is gNB 200, and UE 100 is in RRC connection state in both NW 40-1 and NW 40-2, UE 100 can send information indicating that the RRC connection in NW 40-1 and the RRC connection in NW 40-2 belong to the same UE 100 along with the MUSIM status information. For example, such information could indicate that the network temporary identifier (such as C-RNTI) assigned from the two NW 40s belongs to the same UE 100.

[0205] When UE 100, which is in MUSIM state, is deregistered in either NW 40-1 or NW 40-2, UE 100 can send a message indicating the deregistration to the other NW.

[0206] Other embodiments

[0207] The above embodiments can be implemented individually and independently, or in combination of two or more embodiments.

[0208] In the first embodiment described above, the timing information identifies an execution timing, which is a timing for performing communication in NW 40-2, but is not limited to this. The timing information may be information indicating a communicable timing at which communication with NW 40-1 can be performed. In this case, NW 40-1 can schedule communication with UE 100 at that communicable timing.

[0209] A program may be provided that enables a computer to perform each processing operation according to the above embodiments. This program may be recorded on a computer-readable medium. The use of a 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. Non-transitory recording media are not particularly limited and may, for example, be a recording medium such as a CD-ROM or DVD-ROM.

[0210] The embodiments have been described in detail above with reference to the accompanying drawings, but the specific configurations are not limited to those described above, and various design changes can be made without departing from the spirit of this disclosure.

[0211] This application claims priority to Japanese Patent Application No. 2020-146146 (filed on August 31, 2020), the entire contents of which are incorporated herein by reference.

[0212] Figure Labels

[0213] 100:UE

[0214] 110: Receiver

[0215] 120: Transmitter

[0216] 130: Controller

[0217] 200: gNB

[0218] 210: Transmitter

[0219] 220: Receiver

[0220] 230: Controller

[0221] 260: Backhaul Communicator

[0222] 300: AMF

[0223] 310: Controller

[0224] 320: Backhaul communicator.

Claims

1. A communication control method using a user equipment, the user equipment including a first subscriber identification module (SIM) and a second SIM, the first SIM corresponding to a first mobile network and the second SIM corresponding to a second mobile network, the method comprising: The user equipment receives information related to the transmission of timing information from the first mobile network, and the timing information is based on execution timing, which is the timing of communication performed in the second mobile network; The user equipment determines whether to allow the transmission of the timing information based on information related to the transmission of the timing information; as well as In response to determining that the timing information can be sent, the user equipment sends the timing information to the first mobile network.

2. The communication control method according to claim 1, wherein... The timing information includes: Information used to identify the timing of the first mobile network based on the execution timing.

3. The communication control method according to claim 1 further includes: The user equipment sends its preferred RRC status in the first mobile network to the base station in the first mobile network.

4. The communication control method according to claim 1 further includes: The timing information is received by a base station in the first mobile network; as well as The base station uses the timing information as part of the user equipment (UE) context of the user equipment and sends a HandoverPreparationInformation message that includes the handover process of the UE context.

5. The communication control method according to claim 1, further comprising: The base station in the first mobile network sets a communication gap for the user equipment based on the timing information. During the communication gap, the user equipment neither sends data to the first mobile network nor receives data from the first mobile network.

6. The communication control method according to claim 1, comprising: The user equipment determines one of the first mobile network and the second mobile network as a priority network, and determines the other mobile network as a non-priority network. Sending the timing information includes: sending the timing information when the first mobile network is determined to be the non-priority network.

7. The communication control method according to claim 1, wherein... The transmission also includes: In response to the occurrence of a predetermined event, the user equipment sends the timing information to the first mobile network, wherein... The predetermined event indicates that the user equipment transitions from a Radio Resource Control (RRC) connected state to an RRC inactive state in the second mobile network, or the user equipment transitions to the RRC connected state in the first mobile network.

8. A user equipment, the user equipment comprising a first subscriber identification module (SIM) and a second SIM, the first SIM corresponding to a first mobile network, and the second SIM corresponding to a second mobile network, the user equipment comprising: The receiving unit receives information related to the transmission of timing information from the first mobile network, wherein the timing information is based on execution timing, and the execution timing is the timing for performing communication in the second mobile network; The control unit determines whether to allow the transmission of the timing information based on information related to the transmission of the timing information; as well as The transmitting unit, in response to determining that transmission of the timing information is permitted, transmits the timing information to the first mobile network.

9. A processor for controlling a user equipment, the user equipment including a first subscriber identification module (SIM) and a second SIM, the first SIM corresponding to a first mobile network and the second SIM corresponding to a second mobile network, the processor performing the following processes: Receive information related to the transmission of timing information from the first mobile network, wherein the timing information is based on execution timing, which is the timing of communication performed in the second mobile network; Based on information related to the transmission of the timing information, determine whether to allow the transmission of the timing information; as well as In response to determining that transmission of the timing information is permitted, the timing information is transmitted to the first mobile network.

Images