COMMUNICATION CONTROL METHOD, USER EQUIPMENT, AND PROCESSOR
By transmitting timing information for communication in the second network to the first network, user devices with multiple SIMs can avoid communication collisions, enabling simultaneous and coordinated use of multiple mobile networks.
Patent Information
- Application Number
- JP2023118199
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-08-31
- Filing Date
- 2023-07-20
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-08-25
AI Technical Summary
User devices equipped with multiple SIMs face challenges in simultaneously communicating with multiple mobile networks, particularly when these networks belong to different carriers, leading to potential communication collisions and difficulties in coordination between networks.
The user equipment transmits timing information to the first mobile network indicating the execution timing for communication in the second mobile network, allowing the first network to schedule communications without overlap, thereby avoiding collisions.
This approach enables seamless and coordinated communication with multiple mobile networks, ensuring that both communications can be executed without interference, even when networks belong to different carriers.
Smart Images

Figure 0007594055000001 
Figure 0007594055000002 
Figure 0007594055000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a communication control method, a user equipment, and a processor. [Background technology]
[0002] A user device needs to be equipped with a subscriber identity module (SIM) in order to use mobile communication services (such as voice call services and data communication services) provided by a communication service provider (also called an operator or a communication carrier) via a mobile network. When a user device registers with a mobile network using a SIM, the user device can use mobile communication services from the registered mobile network.
[0003] In recent years, user devices capable of carrying multiple SIMs have become widespread. A user device carrying two SIMs (a first SIM and a second SIM) may use a mobile communication service from a first mobile network in which the first SIM is registered, and may also use a mobile communication service from a second mobile network in which the second SIM is registered. Discussions on use cases in which both mobile communication services are used have been started in 3GPP (Third Generation Partnership Project) (registered trademark; the same applies below) (for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] 3GPP Technical Report TR 22.834 "TR 22.834 V17.1.0" September 2019, Internet<URL:http: / / www.3gpp.org / ftp / Specs / archive / 22_series / 22.834 / 22834-h10.zip> Summary of the Invention
[0005] A communication control method according to a first aspect is a communication control method using a user equipment having a first subscriber identity module (SIM) corresponding to a first mobile network and a second SIM corresponding to a second mobile network, the communication control method comprising the user equipment transmitting, to the first mobile network, timing information indicating an execution timing, which is a timing for executing communication in the second mobile network, in response to an occurrence of a predetermined event. [Brief description of the drawings]
[0006] [Figure 1] 1 is a diagram showing a configuration of a mobile communication system according to an embodiment; [Diagram 2] FIG. 2 is a diagram illustrating a configuration of a user device according to an embodiment. [Diagram 3] FIG. 2 is a diagram illustrating a configuration of a base station according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating a configuration of a core network device according to an embodiment. [Diagram 5] A diagram showing the configuration of a protocol stack of a user plane radio interface according to one embodiment. [Figure 6] FIG. 2 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals) according to one embodiment. [Figure 7] FIG. 2 is a diagram showing an example of a unicast scheduling opportunity according to the first embodiment; [Figure 8] FIG. 4 is a diagram illustrating an operation of an operation example 1 of the first embodiment. [Figure 9] FIG. 11 is a diagram illustrating an operation of an operation example 2 of the first embodiment. [Figure 10] FIG. 11 is a diagram illustrating an operation of an operation example 3 according to the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating an operation of an operation example 4 according to the first embodiment. [Figure 12] FIG. 11 is a diagram illustrating the operation of the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0007] In a user device, when a communication in a first mobile network and a communication in a second mobile network occur at the same time, there is a possibility that one of the communications cannot be executed. In particular, when the first mobile network and the second mobile network belong to different communication carriers, it is difficult to avoid such a problem by cooperation between the mobile networks.
[0008] An object of the present disclosure is to enable a user device capable of being equipped with multiple SIMs to appropriately perform communications in multiple mobile networks.
[0009] A mobile communication system according to an embodiment will be 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 numerals.
[0010] (Mobile communication system) A configuration of a mobile communication system according to an embodiment will be described. The mobile communication system according to an embodiment is a 3GPP 5G system, but the 3GPP LTE (Long Term Evolution) may be applied at least partially to the mobile communication system.
[0011] FIG. 1 is a diagram showing a configuration of a mobile communication system according to an embodiment.
[0012] As shown in Fig. 1, the mobile communication system includes a first mobile network (MN 40-1) operated by a first telecommunications carrier, a second mobile network (MN 40-2) operated by a second telecommunications carrier, and user equipment (UE) 100. UE 100 can be registered in MN 40-1 using SIM 140-1 (described later), and can be registered in MN 40-2 using SIM 140-2. Hereinafter, when there is no need to distinguish between MN 40-1 and MN 40-2, they will be simply referred to as MN 40.
[0013] The MN 40 may be a network using 5G technology or a network using LTE technology. FIG. 1 is an example in which the MN 40 uses 5G technology. The MN 40 has a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10 and a 5G core network (5GC: 5G Core Network) 20. When the MN 40 uses the LTE technology, NG-RAN is replaced with E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) and 5GC is replaced with EPC (Evolved Packet Core). In addition, when the MN 40 uses the LTE technology, a gNB described later is replaced with eNB and an AMF described later is replaced with MME (Mobility Management Entity). In addition, a UPF described later is replaced with S-GW (Serving Gateway) and / or P-GW (Packet Data Network Gateway).
[0014] The UE 100 is a mobile device. The UE 100 may be any device that is used by a user, and may be, for example, 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 a device provided in a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), or an aircraft or a device provided in an aircraft (Aerial UE).
[0015] The NG-RAN 10 includes a base station (called "gNB" in the 5G system) 200. The gNB 200 is sometimes called an NG-RAN node. The gNBs 200 are connected to each other via an Xn interface (not shown), which is an interface between base stations. The gNB 200 manages one or more cells. The gNB 200 performs wireless communication with the UE 100 that has established a connection with its own cell. The gNB 200 has a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, and the like. The term "cell" is used to indicate the smallest unit of a wireless communication area. The term "cell" is also used to indicate a function or resource for wireless communication with the UE 100. One cell belongs to one carrier frequency.
[0016] In addition, the gNB may be connected to an EPC (Evolved Packet Core), which is a core network of LTE, and the LTE base station may be connected to 5GC. In addition, the LTE base station and the gNB may be connected via an inter-base station interface.
[0017] The 5GC20 includes an Access and Mobility Management Function (AMF) 300 and a User Plane Function (UPF) 400. The AMF 300 performs various mobility controls for the UE 100. The AMF 300 manages information on the area in which the UE 100 is located by communicating with the UE 100 using Non-Access Stratum (NAS) signaling. The UPF 400 controls data forwarding. The AMF 300 and the UPF 400 are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network.
[0018] FIG. 2 is a diagram showing a configuration of UE 100 (user equipment).
[0019] 2, the UE 100 includes a receiving unit 110, a transmitting unit 120, a control unit 130, a SIM 140-1 (a first SIM), a SIM 140-2 (a second SIM), and a user interface 150. The UE 100 may include three or more SIMs 140.
[0020] The receiving unit 110 performs various receptions under the control of the control unit 130. The receiving unit 110 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.
[0021] The transmission unit 120 performs various transmissions under the control of the control unit 130. The transmission unit 120 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.
[0022] The control unit 130 performs various controls in the UE 100. The control unit 130 includes at least one processor and at least one memory electrically connected to the processor. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processing.
[0023] The SIM 140 records information for identifying a subscriber in order to receive mobile communication services provided by a mobile network. The SIM 140 may record information for identifying a subscriber, carrier-specific information for identifying a communication carrier, and information on available services subscribed to by the subscriber. The SIM 140 may be a removable IC card called a SIM card (or USIM card), that is, an information card. The SIM 140 may be an embedded eSIM (Embedded SIM).
[0024] The SIM 140-1 (first SIM) records information for identifying a first IMSI (International Mobile Subscriber Identity), which is an identification number assigned to a user of the UE 100 by a first carrier that operates the first mobile network 40-1. The SIM 140-2 (second SIM) records information for identifying a second IMSI, which is an identification number assigned to a user of the UE 100 by a second carrier that operates the second mobile network 40-2. The SIM 140-1 and the SIM 140-2 may be separate information cards, or may be integrated into the same information card. The SIM 140-1 and the SIM 140-2 may be included in an eSIM (Embedded SIM).
[0025] SIM 140-1 is managed by a first telecommunications carrier, and SIM 140-2 is managed by a second telecommunications carrier. SIM 140-1 and SIM 140-2 may be managed by the same telecommunications carrier.
[0026] When the UE 100 registers with the first mobile network 40-1 using the SIM 140-1, the UE 100 can use a mobile communication service provided by a first carrier via the first mobile network 40-1. When the UE 100 registers with the second mobile network 40-2 using the SIM 140-2, the UE 100 can use a mobile communication service provided by a second carrier via the second mobile network 40-2.
[0027] A user of UE 100 may set the priority order between SIM 140-1 and SIM 140-2 via user interface 150. The user may set SIM 140-1 to be prioritized over SIM 140-2, or may set SIM 140-2 to be prioritized over SIM 140-1.
[0028] Figure 3 is a diagram showing the configuration of gNB200 (base station).
[0029] As shown in FIG. 3, the gNB 200 includes a transmitter 210, a receiver 220, a control unit 230, and a backhaul communication unit 240.
[0030] The transmission unit 210 performs various transmissions under the control of the control unit 230. The transmission unit 210 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.
[0031] The receiving unit 220 performs various types of reception under the control of the control unit 230. The receiving unit 220 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 230.
[0032] The control unit 230 performs various controls in the gNB 200. The control unit 230 includes at least one processor and at least one memory electrically connected to the processor. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processing.
[0033] The backhaul communication unit 240 is connected to adjacent base stations via an inter-base station interface. The backhaul communication unit 240 is connected to the AMF / UPF 300 via a base station-core network interface.
[0034] FIG. 4 is a diagram showing the configuration of the AMF 300 (core network device).
[0035] As shown in FIG. 4, the AMF 300 includes a control unit 330 and a backhaul communication unit 340.
[0036] The control unit 330 performs various controls in the AMF 300. The control unit 330 includes at least one processor and at least one memory electrically connected to the processor. The memory stores programs executed by the processor and information used in processing by the processor.
[0037] The backhaul communication unit 340 is connected to the gNB 200 via a base station-core network interface.
[0038] FIG. 5 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data.
[0039] As shown in FIG. 5, the user plane radio interface protocol 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.
[0040] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of the UE 100 and the PHY layer of the gNB 200 via a physical channel.
[0041] In the PHY layer, a frame structure including a radio frame, a subframe, a slot, and a symbol is used. A radio frame is composed of 10 subframes on a time axis. The length of each subframe is 1 ms. Each subframe is composed of multiple slots. Each slot is composed of multiple symbols. Each subframe includes multiple resource blocks (RB) on a frequency axis. Each resource block includes multiple subcarriers on a frequency axis. Of the radio resources (time-frequency resources) allocated to UE 100, frequency resources can be specified by resource blocks, and time resources can be specified by subframes (or slots, symbols).
[0042] In the downlink, the section of the first few symbols of each subframe is an area used mainly as a physical downlink control channel (PDCCH) for transmitting downlink control information, and the remaining part of each subframe is an area used mainly as a physical downlink shared channel (PDSCH) for transmitting downlink data.
[0043] 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 the UE 100 and the MAC layer of the gNB 200 via a transport channel. The MAC layer of the gNB 200 includes a scheduler. The scheduler determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be assigned to the UE 100.
[0044] The RLC layer transmits data to the RLC layer on the receiving side by using the functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via a logical channel.
[0045] The PDCP layer performs header compression / decompression and encryption / decryption.
[0046] The SDAP layer maps IP flows, which are the units for QoS control by the core network, to radio bearers, which are the units for QoS control by the AS (Access Stratum). Note that if the RAN is connected to the EPC, the SDAP is not necessary.
[0047] FIG. 6 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals).
[0048] As shown in FIG. 6, the protocol stack of the radio interface of the control plane has a Radio Resource Control (RRC) layer and a Non-Access Stratum (NAS) layer instead of the SDAP layer shown in FIG.
[0049] Between the RRC layer of the UE 100 and the RRC layer of the gNB 200, RRC signaling for various settings is transmitted. The RRC layer controls logical channels, transport channels, and physical channels in response to establishment, re-establishment, and release of radio bearers. When there is a connection (RRC connection) between the RRC of the UE 100 and the RRC of the gNB 200, the UE 100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of the UE 100 and the RRC of the gNB 200, the UE 100 is in an RRC idle state. Also, when the RRC connection is interrupted (suspended), the UE 100 is in an RRC inactive state.
[0050] The NAS layer, which is located above the RRC layer, performs session management, mobility management, etc. NAS signaling is transmitted between the NAS layer of the UE 100 and the NAS layer of the AMF 300.
[0051] In addition, the UE 100 has an application layer and the like in addition to the protocol of the radio interface.
[0052] (First embodiment) The first embodiment will be described on the premise that the system configuration described above is used.
[0053] When the communication of the UE 100 in the MN 40-1 and the communication of the UE 100 in the MN 40-2 are scheduled at the same time, one of the communications may not be able to be executed depending on the capability of the UE 100. For example, when both MNs 40 schedule downlink communications to the UE 100 at the same timing with different frequencies, if the UE 100 has only a single wireless receiver (receiving unit 110), one of the two downlink communications cannot be executed. Even if the UE 100 has multiple wireless receivers, if one of the downlink communications uses a large amount of the CPU resources of the UE 100, the UE 100 cannot execute the other communication. It is preferable that the UE 100 does not cause the two communications to collide. The first embodiment is an embodiment for solving such a problem.
[0054] The UE 100 according to the first embodiment transmits timing information for identifying an execution timing, which is a timing for executing communication in the NW 40-2, to the NW 40-1. This allows the NW 40-1 to grasp the timing at which the UE 100 executes communication in the NW 40-2, and allows the NW 40-1 to schedule communication with the UE 100 at a timing that does not overlap with the timing. This makes it possible to avoid a collision between communication in the NW 40-1 and communication in the NW 40-2.
[0055] The execution timing includes at least one of a paging reception opportunity, a unicast scheduling opportunity, an MBS scheduling opportunity, and a sidelink scheduling opportunity.
[0056] (Paging reception opportunity) The paging reception opportunity is a timing at which the UE 100 in the RRC idle state or the RRC inactive state monitors for a paging from the NW 40-2.
[0057] A UE 100 in an RRC idle state monitors CN paging. A UE 100 in an RRC inactive state monitors CN paging and RAN paging. CN paging is paging initiated by the core network (CN). RAN paging is paging initiated by the RAN.
[0058] In order to reduce power consumption, the UE 100 monitors paging using Discontinuous Reception (DRX) in the RRC idle and RRC inactive states.
[0059] The UE 100 monitors one paging occasion (PO) per DRX cycle. The DRX cycle is expressed by the number of radio frames. The DRX cycle may be called a paging period. The PO consists of one or more subframes or one or more symbols. One PO is associated with a paging frame (PF), which is one radio frame. The PO associated with a PF may start within the PF or after the PF.
[0060] The paging reception opportunity of the UE 100 is a timing (subframe or symbol) included in a PO that occurs every DRX cycle.
[0061] The UE 100 determines the smaller one of the default DRX cycle and the UE-specific DRX cycle set in the UE 100 as a DRX cycle (hereinafter, referred to as "T") that the UE 100 should use for monitoring paging.
[0062] The default DRX cycle is included in the system information received from the serving cell (gNB200) in which UE100 is located.
[0063] The UE-specific DRX cycle differs depending on the RRC state of the UE 100. When the UE 100 is in an RRC idle state, the UE-specific DRX cycle includes a first UE-specific DRX cycle. When the 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.
[0064] The first UE-specific DRX cycle is a UE-specific DRX cycle set in the UE 100 by a NAS message for monitoring CN paging. Such a NAS message is, for example, a REGISTRATION ACCEPT message from the AMF 300-2 of the NW 40-2 when the UE 100 registers with the NW 40-2.
[0065] The second UE-specific DRX cycle is a UE-specific DRX cycle set in the UE 100 by a dedicated RRC message for monitoring RAN paging. Such a dedicated RRC message is, for example, an RRC release message for transitioning the UE 100 from an RRC connected state to an RRC inactive state. Such an RRC release message includes an information element (IE) called "Suspendconfig", and the "Suspendconfig" includes information indicating the second UE-specific DRX cycle.
[0066] The UE 100 in the RRC idle state determines the smaller one of the default DRX cycle and the first UE-specific DRX cycle as "T".
[0067] The UE 100 in the RRC inactive state determines the smaller one of the default DRX cycle, the first UE-specific DRX cycle, and the second UE-specific DRX cycle as "T".
[0068] When a UE-specific DRX cycle is not set, the UE 100 determines the default DRX cycle to be "T".
[0069] After determining "T", the UE 100 determines the radio frame number of the PF and the subframes or symbols that constitute the PO based on "T", the "UE_ID", and the paging related information.
[0070] Here, "UE_ID" is a value calculated by a temporary subscriber identifier assigned to the UE 100 by the AMF 300-2. Such a temporary subscription identifier is, for example, 5G-S-TMSI (Temporary Mobile Subscriber Identity). "UE_ID" is, for example, a value calculated by "5G-S-TMSI mod 1024".
[0071] The paging related information is included in system information received from a serving cell (gNB 200) in which the UE 100 is located. The paging related information includes parameters such as N, Ns, and PF_offset.
[0072] For details on the method of determining the above-mentioned T, PF, and PO, please refer to, for example, 3GPP technical specification TS 38.304. For details on the method of determining when the UE 100 is in an LTE cell, please refer to, for example, 3GPP technical specification TS 36.304.
[0073] (Unicast Scheduling Opportunity) The unicast scheduling opportunity is a candidate timing for scheduling transmission and reception of unicast data between UE 100 in an RRC connected state and NW 40-2 (gNB 200-2).
[0074] A unicast scheduling opportunity is a timing included in a periodically occurring scheduling period.
[0075] FIG. 7 illustrates an example of a unicast scheduling opportunity.
[0076] 7, a scheduling period is a period that occurs every cycle "P." A scheduling period starts from a start timing (t1, t2, t3...). A scheduling period has a predetermined time length (D).
[0077] The gNB200 assigns communication timing (subframes, slots, symbols, etc.) of unicast data with the UE100 in a scheduling period within one cycle. On the other hand, the gNB200 does not assign communication timing to the UE100 in a non-scheduling period (period that is not a scheduling period) within one cycle. The communication timing includes at least one of a timing of transmitting unicast data from the UE100 to the gNB200 and a timing of transmitting unicast data from the gNB200 to the UE100.
[0078] A unicast scheduling opportunity is specified by three parameters: a start timing, a periodicity, and a predetermined length of time.
[0079] The start timing may be represented by a radio frame number and a subframe number, or may be represented by a slot number and a symbol number in addition to the radio frame number and the subframe number. The period is represented by the number of radio frames, the number of subframes, or the number of slots. The predetermined time length is represented by the number of subframes, the number of slots, or the number of symbols.
[0080] The unicast scheduling opportunity is configured from the gNB 200 to the UE 100 by a unicast RRC message (e.g., an RRC reconfiguration message). The gNB 200 may configure the unicast scheduling opportunity to the UE 100 in response to a request from the UE 100. The gNB 200 may configure the unicast scheduling opportunity to the UE 100 based on a history of past traffic of the UE 100 and / or a prediction of future traffic of the UE 100, etc.
[0081] A scheduling period occurring every cycle may be composed of multiple non-consecutive timings. For example, a scheduling period may be composed of multiple non-consecutive timings within a predetermined time length (D). In this case, the multiple non-consecutive timings within the predetermined time length are indicated by a bitmap. For example, if the predetermined time length is four subframes, and the first and fourth subframes of the four subframes correspond to the scheduling period, the scheduling period is specified by the predetermined time length and a bitmap of (1, 0, 0, 1).
[0082] (MBS Scheduling Opportunity) The MBS scheduling opportunity is a candidate timing for scheduling transmission of MBS data from the NW 40-2 to the UE 100. The MBS is a service for broadcasting or multicasting, that is, point-to-multipoint (PTM) data transmission from the NW 40-2 to the UE 100. The MBS may be called an MBMS (Multimedia Broadcast and Multicast Service). The MBS data refers to data transmitted by the MBS.
[0083] An MBS scheduling opportunity is a timing included in a periodically occurring scheduling period.
[0084] The MBS scheduling opportunity may be identified by parameters such as a start timing, a period, a predetermined time length, a bitmap, etc., similar to the unicast scheduling opportunity described above, where the parameters identifying the MBS scheduling opportunity are different from the parameters identifying the unicast scheduling opportunity.
[0085] The MBS scheduling opportunity is configured to the UE 100 from the gNB 200 via a broadcast RRC message (eg, a SIB for MBS). The MBS scheduling opportunity may be configured to the UE 100 regardless of the RRC state of the UE 100.
[0086] When the UE 100 is interested in receiving MBS data regardless of its own RRC state, the UE 100 acquires an SIB for MBS and identifies an MBS scheduling opportunity based on MBS information included in the SIB for MBS. The MBS information may directly include a parameter for identifying the MBS scheduling opportunity. The MBS information may include MBS control channel configuration information for the UE 100 to receive an MBS control channel carrying a parameter for identifying the MBS scheduling opportunity.
[0087] (Sidelink Scheduling Opportunity) The sidelink scheduling opportunity is a candidate timing at which the sidelink communication by the UE 100 is scheduled in the NW 40-2. The sidelink communication is communication between nearby UEs 100 without passing through a network node (e.g., the gNB 200). The sidelink communication includes at least one of a sidelink transmission in which the UE 100 transmits data to another UE 100 and a sidelink reception in which the UE 100 receives data from another UE 100.
[0088] A sidelink scheduling opportunity is a timing included in a periodically occurring scheduling period.
[0089] A sidelink scheduling opportunity may be identified by parameters such as a start timing, a periodicity, a predetermined time length, a bitmap, etc., similar to the above-mentioned unicast scheduling opportunity. Here, the parameters identifying a sidelink scheduling opportunity are different from the parameters identifying a unicast scheduling opportunity. The parameters identifying a sidelink scheduling opportunity are different from the parameters identifying an MBS scheduling opportunity.
[0090] The sidelink scheduling opportunity may be configured to the UE 100 from the gNB 200 via a broadcast RRC message (e.g., a SIB for sidelink). The sidelink scheduling opportunity may be configured to the UE 100 regardless of the RRC state of the UE 100.
[0091] When the UE 100 is interested in sidelink communication regardless of its RRC state, the UE 100 acquires a sidelink SIB and identifies a sidelink scheduling opportunity based on sidelink information included in the sidelink SIB. The sidelink information is, for example, information indicating a resource pool for sidelink communication.
[0092] (Operation Example 1 of the First Embodiment) FIG. 8 is a diagram illustrating the operation of the first operation example of the first embodiment.
[0093] 8, in the initial state of the operation example 1, the UE 100 is registered in both the MN 40-2 and the MN 40-1. In the initial state, the UE 100 is in any of the RRC states of the RRC connected state, the RRC idle state, and the RRC inactive state in the MN 40-2. The UE 100 is in any of the RRC states of the RRC connected state, the RRC idle state, and the RRC inactive state in the MN 40-1.
[0094] In step S101, the UE 100 determines whether a predetermined event occurs. Details of the predetermined event will be described later. When the UE 100 determines that a predetermined event occurs (step S101: YES), the UE 100 advances the process to step S102.
[0095] In step S102, the UE 100 transmits timing information for identifying an execution timing, which is a timing for executing communication in the NW 40-2, to the NW 40-1. The timing information includes at least one of information for identifying a paging reception opportunity, information for identifying a unicast scheduling opportunity, information for identifying an MBS scheduling opportunity, and information for identifying a sidelink scheduling opportunity.
[0096] In step S102, when the UE 100 is in an RRC idle state or an RRC inactive state in the NW 40-1, the UE 100 may transmit the timing information after transitioning to an RRC connected state.
[0097] In step S102, the destination of the timing information is the gNB 200-1 and / or the AMF 300-1 in the NW 40-1. When the destination of the timing information is the gNB 200-1, the timing information is transmitted by an RRC message. When the destination of the timing information is the AMF 300-1, the timing information is transmitted by an NAS message.
[0098] When UE 100 desires to transition from the RRC connected state to the RRC idle state in MN 40-1, UE 100 may determine the transmission destination of the timing information as AMF 300-1. In this case, UE 100 may transmit information indicating that it desires to transition to the RRC idle state to gNB 200-1 after step S102. When UE 100 desires to transition from the RRC connected state to the RRC inactive state in MN 40-1, UE 100 may determine the transmission destination of the timing information as both AMF 300-1 and gNB 200-1. In this case, UE 100 may transmit information indicating that it desires to transition to the RRC inactive state to gNB 200-1 after step S102.
[0099] When the UE 100 transmits the timing information in the NAS message, the NAS layer of the UE 100 generates the timing information. In this case, the RRC layer transmits information required to specify the execution timing to the NAS layer of the UE 100. The required information includes, for example, the above-mentioned second UE-specific DRX cycle and the default DRX cycle that the RRC layer knows.
[0100] The UE 100 may transmit the timing information and information indicating the guard time together. The guard time is a time required for the UE 100 to switch from communication with the NW 40-2 (gNB 200-2) to communication with the NW 40-1 (gNB 200-1). The guard time is expressed 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 (for example, PO).
[0101] When the timing between NW40-1 (gNB200-1) and NW40-2 (gNB200-2) is asynchronous, the timing information transmitted to NW40-1 may include information for identifying the timing of NW40-1 corresponding to the execution timing of NW40-2 (radio frame number, subframe number, slot number, symbol number, etc.). In this case, the timing information may be information indicating the timing of NW40-1 corresponding to the execution timing of NW40-2 (i.e., radio frame number, subframe number, slot number, symbol number, etc. of NW40-1). The timing information may include information indicating the execution timing of NW40-2 and information indicating the difference in timing between NW40-1 (gNB200-1) and NW40-2 (gNB200-2). The difference in timing is expressed by the number of radio frames, the number of subframes, the number of slots, the number of symbols, etc.
[0102] In step S103, MN 40-1 (gNB 200-1 and / or AMF 300-1) communicates with UE 100 without using the timing specified by the information received in step S102 (timing information, or timing information+information indicating a guard time). Hereinafter, the timing specified by the information received in step S102 (timing information, information indicating a guard time) will be referred to as "non-use timing".
[0103] The operations in step S103 include, for example, the following operations 1 to 4.
[0104] Operation 1: When gNB200-1 transitions UE100 to an RRC inactive state, it sets a UE-specific DRX cycle (the second UE-specific DRX cycle described above) for UE100 so that the PO corresponding to RAN paging transmitted from gNB200-1 is placed in a non-usage timing, and transmits an RRCRelease message including the UE-specific DRX cycle to UE100.
[0105] Operation 2: The gNB 200-1 allocates timing other than non-use timing to transmitting and receiving data with the UE 100 in the RRC connected state.
[0106] Operation 3: The gNB 200-1 sets a predetermined period including a non-use timing as a communication gap for the UE 100 in an RRC connected state, and transmits information indicating the communication gap to the UE 100. The gNB 200-1 does not schedule transmission and reception of data to and from the UE 100 during the communication gap.
[0107] Operation 4: The AMF 300-1 sets a UE-specific DRX cycle (the above-mentioned first UE-specific DRX cycle) of the UE 100 and a new 5G-S-TMSI to be assigned to the UE 100 so that a PO corresponding to a CN paging transmitted from the AMF 300-1 is arranged in a non-use timing, and notifies the UE 100 by a NAS message. Alternatively, instead of assigning a new 5G-S-TMSI to the UE 100, the AMF 300-1 may notify the UE 100 of an offset value for the 5G-S-TMSI already assigned to the UE 100. The offset value is used only when identifying a paging reception opportunity. The offset value may also be notified from the AMF 300-1 to the gNB 200-1 when paging is executed.
[0108] It should be noted that the operation in step S103 is not essential.
[0109] Next, the predetermined event will be described. The predetermined event includes any one of the following events A to F.
[0110] Event A is an event that causes UE 100 to start monitoring for a paging message in NW 40-2.
[0111] In step S101, when an event A occurs in the UE 100, in step S102, the UE 100 transmits timing information including information indicating a paging reception opportunity. The timing information may further include information for identifying other execution timings (such as a unicast scheduling opportunity, an MBS scheduling opportunity, or a sidelink scheduling opportunity) that the UE 100 knows at this point.
[0112] Event A includes, for example, any of the following events A1 to A3.
[0113] Event A1 is the transition of UE 100 from an RRC connected state to an RRC inactive state in NW 40-2.
[0114] Event A2 is the transition of UE 100 from the RRC connected state to the RRC idle state in NW 40-2.
[0115] Event B is an event that may cause a change in paging reception opportunity in UE 100 that has already started monitoring for paging messages in NW 40-2.
[0116] In step S101, when an event B occurs in the UE 100, the UE 100 transmits timing information including information indicating a paging reception opportunity (updated paging reception opportunity) in step S102. The timing information may further include information for identifying other execution timings that the UE 100 knows at this point.
[0117] Event B is, for example, any one of the following events B1 to B3.
[0118] Event B1 is that the UE 100 in the RRC inactive state in the NW 40-2 transitions to RRC idle. In this case, the UE 100 determines “T” without considering the second UE-specific DRX cycle, so “T” may change.
[0119] Event B2 is that the UE 100 in the RRC inactive state in the NW 40-2 maintains the RRC inactive state after performing an RNA (Ran Notification Area) update procedure. In this case, the UE 100 receives an RRCRelease message including "suspendConfig" again, so that the second UE-specific DRX cycle is updated and "T" may change. For details of the RNA update procedure, please refer to Chapter 9.2.2.5 of the 3GPP technical specification TS 38.300.
[0120] Event B3 is that the UE 100 in the RRC inactive state or the RRC idle state in the NW 40-2 performs cell reselection. In this case, the default DRX cycle may be changed according to a change in the serving cell of the UE 100, so that "T" may change.
[0121] Event C is when a unicast scheduling opportunity is set for the UE 100 in the NW 40-2, or when the unicast scheduling opportunity for the UE 100 is changed in the NW 40-2.
[0122] In step S101, when an event C occurs in the UE 100, in step S102, the UE 100 transmits timing information including information for identifying a unicast scheduling opportunity. The timing information may further include information for identifying other execution timings known to the UE 100 at this time.
[0123] Event D is when the UE 100 in the NW 40-2 becomes interested in receiving MBS data, when the UE 100 in the NW 40-2 starts receiving MBS data, or when the MBS scheduling opportunity for the UE 100 in the NW 40-2 is changed.
[0124] In step S101, if an event D occurs in the UE 100, in step S102, the UE 100 transmits timing information including information for identifying an MBS scheduling opportunity. The timing information may further include information for identifying other execution timings known to the UE 100 at this time.
[0125] Event E is when UE 100 in NW 40-2 becomes interested in sidelink communication, when UE 100 in NW 40-2 starts sidelink communication, or when a sidelink scheduling opportunity for UE 100 in NW 40-2 is changed.
[0126] In step S101, if an event E occurs in the UE 100, in step S102, the UE 100 transmits timing information including information for identifying a sidelink scheduling opportunity. The timing information may further include information for identifying other execution timings known to the UE 100 at this time.
[0127] Event F is when UE 100 transitions to an RRC connected state in NW 40-1.
[0128] In step S101, when an event F occurs in the UE 100, in step S102, the UE 100 transmits timing information including information for identifying an execution timing already recognized by the UE 100 at the time when the event F occurs. For example, when the UE 100 is already monitoring paging in the NW 40-2 and receiving MBS data at the time when the event F occurs, the UE 100 transmits timing information including information for identifying a paging reception opportunity and information for identifying an MBS scheduling opportunity.
[0129] (Operation Example 2 of the First Embodiment) The following describes the operation example 2, focusing mainly on the differences from the operation example 1. The operation example 2 is an operation example related to permission to transmit timing information.
[0130] FIG. 9 is a diagram illustrating the operation of the second operation example of the first embodiment.
[0131] In step S201, UE 100 receives information indicating whether or not transmission of timing information is permitted (hereinafter, referred to as "transmission permission information") from NW 40-1 (gNB 200-1). UE 100 may receive the transmission permission information by an individual RRC message, or may receive the transmission permission information by an SIB. UE 100 stores the received transmission permission information.
[0132] Before step S201, UE 100 may transmit a request message to gNB 200-1 to permit transmission of timing information. In response to receiving the request message, gNB 200-1 transmits transmission permission information to UE 100 by an individual RRC message. The request message may include information indicating that UE 100 is in a state where it is registered with both MN 40-1 and MN 40-2 (hereinafter referred to as "MUSIM state"). When UE 100 is in the MUSIM state, gNB 200-1 may transmit to UE 100 transmission permission information indicating that transmission of timing information is permitted. In addition, since the current LTE specifications do not specify how to handle UE 100 having multiple SIMs, when NW 40-1 uses LTE technology (i.e., NW 40-1 has E-UTRAN and EPC), transmission of timing information may not be permitted.
[0133] In step S202, the UE 100 determines whether or not a predetermined event occurs. If the UE 100 determines that a predetermined event occurs (step S202: YES), the UE 100 advances the process to step S203.
[0134] In step S203, UE 100 determines whether transmission of timing information is permitted based on the stored transmission permission information. If UE 100 determines that transmission of timing information is not permitted (step S202: NO), this flow ends. If UE 100 determines that transmission of timing information is permitted (step S203: YES), the process proceeds to step S204.
[0135] The operation in step S204 is similar to the operation in step S102.
[0136] (Operation Example 3 of the First Embodiment) The following describes the operation example 3, focusing mainly on the differences from the operation example 1. The operation example 3 is an operation example related to a priority network.
[0137] When the UE 100 according to the third operation example is registered in both the MN 40-1 and the MN 40-2, it determines one of the MNs 40 as a prioritized network and determines the other MN 40 as a non-priority network.
[0138] The UE 100 prioritizes communication in the priority network (paging monitoring, data transmission / reception, etc.) over communication in the non-priority network. For example, when communication in the priority network and communication in the non-priority network are scheduled at the same timing, the UE 100 may perform communication in the priority network and not perform communication in the non-priority network. In addition, when the UE 100 receives data transmitted by the priority network and data transmitted by the non-priority network at the same timing, the UE 100 may discard the data transmitted by the non-priority network. Therefore, when scheduling communication with the UE 100, the non-priority network needs to consider the execution timing of the UE 100 in the priority network in order to make the communication successful.
[0139] Next, a method for determining a priority network will be described. The method for determining a priority network includes, for example, any one of the following first to fourth methods.
[0140] In the first method, the UE 100 determines a preferred network based on a user setting. For example, when the user sets SIM 140-2 to be prioritized over SIM 140-1, the UE 100 determines the MN 40-2 corresponding to SIM 140-2 as a preferred network and the MN 40-1 corresponding to SIM 140-1 as a non-preferred network.
[0141] In the second method, the UE 100 determines the MN 40 using the LTE technology as the priority network. For example, when the MN 40-1 uses the 5G technology and the MN 40-2 uses the LTE technology, the UE 100 determines the MN 40-2 as the priority network and determines the MN 40-1 as the non-priority network. Note that, when the MN 40-1 and the MN 40-2 use the same technology, the UE 100 does not determine the priority network by the second method.
[0142] In the third method, the UE 100 determines, as a priority network, the MN 40 for which a radio bearer with a priority equal to or higher than a threshold is established. For example, when a radio bearer with a priority equal to or higher than a threshold is established between the MN 40-2 and the UE 100, the UE 100 determines the MN 40-2 as a priority network and the MN 40-1 as a non-priority network.
[0143] The priority of a radio bearer is determined according to the type of user data traffic mapped to the radio bearer. For example, if the type of traffic is voice communication, the priority is determined to be high, and if the type of traffic is e-mail, chat, web browsing, etc., the priority is determined to be low. The priority of a radio bearer may be a value associated with 5QI. For the correspondence between 5QI and priority, see Table 5.7.4 of 3GPP Technical Specification TS 23.501. The priority of a radio bearer may be a value associated with QCI. For the correspondence between QCI and priority, see Table 6.1.7 of 3GPP Technical Specification TS 23.203.
[0144] In the fourth method, the UE 100 determines the MN 40 that has set a periodic communication available period for the UE 100 as a priority network. The periodic communication available period is, for example, a communication period specified by SPS (Semi-Persistent Scheduling) or a communication period specified by CG (Configured Grant). For example, when the MN 40-2 sets the SPS for the UE 100, the UE 100 determines the MN 40-2 as a priority network and determines the MN 40-1 as a non-priority network.
[0145] Next, an operation example 3 will be described with reference to FIG.
[0146] FIG. 10 is a diagram illustrating the operation of the operation example 3 of the first embodiment.
[0147] In step S301, the UE 100 determines one of the MN 40-2 and the MN 40-1 as a prioritized network and determines the other as a non-priority network, using the above-mentioned method for determining a prioritized network.
[0148] In step S302, the UE 100 determines whether a predetermined event occurs. A predetermined event occurs. If the UE 100 determines that a predetermined event has occurred (step S302: YES), the UE 100 advances the process to step S303.
[0149] In step S303, the UE 100 judges whether the MN 40-1 is a non-priority network. If the UE 100 judges that the MN 40-1 is not a non-priority network (step S303: NO), the UE 100 ends this flow. If the UE 100 judges that the MN 40-1 is a non-priority network (step S303: YES), the UE 100 advances the process to step S304.
[0150] The operation in step S304 is similar to the operation in step S102.
[0151] In the operation example 3, after step S301, the UE 100 may transmit a non-priority notification to the NW 40 determined as a non-priority network, indicating that the NW 40 is a non-priority network. For example, when the UE 100 determines the NW 40-1 as a non-priority network, the UE 100 transmits a non-priority notification to the NW 40-1 (gNB 200-1 and / or AMF 300-1). When a periodic communication available period is set in the NW 40-2, the UE 100 may transmit information for identifying the periodic communication available period together with the non-priority notification.
[0152] When the gNB 200-1 receives the non-priority notification, the gNB 200-1 recognizes that the NW 40-1 is a non-priority network. When the gNB 200-1 recognizes that the NW 40-1 is a non-priority network, the gNB 200-1 may restrict the establishment of a radio bearer (e.g., a radio bearer for a voice call) with the UE 100, the radio bearer having a priority equal to or higher than a threshold.
[0153] In the operation example 3, after transmitting the non-priority notification to the NW 40-1, when the UE 100 determines that the NW 40-1 is not a non-priority network, the UE 100 may notify the NW 40-1 of the determination. In this case, the restriction on the establishment of a radio bearer whose priority is equal to or higher than the threshold is lifted.
[0154] In the third operation example, the UE 100 may transmit information indicating a desire to transition to an RRC idle state or an RRC inactive state to the NW 40 determined as a non-prioritized network. Such information is, for example, information indicating that the desired RRC state (preferred RRC-State) of the UE 100 is an RRC idle state. Such information may be information indicating that the preferred RRC-State of the UE 100 is an RRC inactive state. Such information may be information indicating that the UE 100 simply wants to release the RRC connection and does not have a desired RRC state.
[0155] For example, when the UE 100 has determined that the NW 40-1 is a non-priority network and is in an RRC connected state in the NW 40-1, the UE 100 transmits information to the gNB 200-1 indicating a desire to transition to an RRC idle state or an RRC inactive state. The information may be transmitted together with timing information. In response to receiving the information, the gNB 200-1 may transition the UE 100 to an RRC idle state or an RRC inactive state.
[0156] (Operation Example 4 of the First Embodiment) The operation example 4 will be described mainly with respect to differences from the operation example 1. The operation example 4 is an operation example related to the UE context.
[0157] Fig. 11 is a diagram showing operations of operation example 4. As shown in Fig. 11, in an initial state, the UE 100 is registered in the MN 40-2. The UE 100 has an RRC connection with a gNB 200-1(a) belonging to the MN 40-1.
[0158] The operation in step S401 is similar to the operation in step S101.
[0159] In step S402, the UE 100 transmits timing information to the gNB 200-1(a) belonging to the MN 40-1.
[0160] In step S403, gNB200-1(a) stores the timing information as part of the UE context of UE100.
[0161] In step S404, gNB200-1(a) transmits a UE context including timing information in a predetermined procedure for establishing an RRC connection between gNB200-1(b) belonging to MN40-1 and UE100.
[0162] Examples of the predetermined procedure include a handover procedure, an RRC connection re-establishment procedure, an RRC connection resume procedure, and the like.
[0163] For example, gNB200-1(a) transmits a Handover Preparation Information message in the handover procedure including the UE context (including timing information).
[0164] In the RRC Resume procedure, gNB200-1(a) may transmit the UE context to gNB200-1(b) in response to receiving a RETRIEVE UE CONTEXT REQUEST message from gNB200-1(b) for requesting the provision of a UE context.
[0165] After the specified procedures are completed, in step S405, an RRC connection between UE100 and gNB200-1(b) is established.
[0166] In step S406, gNB200-1(b) communicates with UE100 without using the timing identified by the timing information (operations 1 to 3 of step S103 described above).
[0167] Second embodiment The second embodiment is an operation example relating to voice communication.
[0168] FIG. 12 is a diagram illustrating the operation of the second embodiment.
[0169] In step S501, the UE 100 determines whether or not a voice communication event occurs in the NW 40-2. When the UE 100 determines that a voice communication event occurs (step S501: YES), the UE 100 advances the process to step S502.
[0170] A voice communication event is when the user of the UE 100 makes a voice call via the NW 40-2, or when the UE 100 receives a paging message notifying an incoming voice call.
[0171] In step S502, the UE 100 inquires of the MN 40-1 as to whether the UE 100 is permitted to perform voice communication.
[0172] In step S503, the UE 100 receives a permission notification indicating that execution of voice communication is permitted from the MN 40-1.
[0173] In step S504, in response to receiving the permission notification, the UE 100 executes the voice communication. Note that, if the UE 100 has not received the permission notification, the UE 100 does not execute the voice communication.
[0174] Third embodiment The third embodiment is based on the premise that the NW 40-1 and the NW 40-2 belong to the same carrier.
[0175] When the UE 100 according to the third embodiment is registered in both the NW 40-1 and the NW 40-2, the UE 100 transmits information indicating that the UE 100 is in a state (MUSIM state) registered in both the MN 40-1 and the MN 40-2 (hereinafter, "MUSIM state information") to both the NW 40-1 and the NW 40-2. This allows the NW 40-1 and the NW 40-2 to know that the same UE 100 is registered in both the NW 40-1 and the NW 40-2. Therefore, the NW 40-1 and the NW 40-2 can cooperate with each other to appropriately communicate with the UE 100.
[0176] When the UE 100 is in an RRC connected state to both the NW 40-1 and the NW 40-2, the UE 100 may transmit MUSIM state information further indicating this state.
[0177] The destination of the MUSIM state information is AMF300 (both AMF300-1 and AMF300-2) and / or gNB200 (both gNB200-1 and gNB200-2). AMF300-1 may forward the MUSIM state information received from UE100 to gNB200-1. gNB200-1 may forward the MUSIM state information received from UE100 to AMF300-1. gNB200-1 may store the MUSIM state information received from UE100 as part of the UE context of the UE100.
[0178] When the destination of the MUSIM status information is the AMF 300, the UE 100 may transmit the MUSIM status information together with information indicating that the registration with the NW 40-1 and the registration with the NW 40-2 belong to the same UE 100. Such information may indicate, for example, that the temporary subscriber identifiers (5G-S-TMSI, etc.) assigned by both NWs 40 belong to the same UE 100.
[0179] When the destination of the MUSIM state information is the gNB 200 and the UE 100 is in an RRC connected state with both the NW 40-1 and the NW 40-2, the UE 100 may transmit, together with the MUSIM state information, information indicating that the RRC connection with the NW 40-1 and the RRC connection with the NW 40-2 belong to the same UE 100. Such information may indicate, for example, that the network temporary identifiers (C-RNTI, etc.) assigned by both the NWs 40 belong to the same UE 100.
[0180] When the UE 100 in the MUSIM state is deregistered in either the NW 40-1 or the NW 40-2, the UE 100 may transmit information indicating that the registration has been deregistered in the other one of the NWs 40-1 and 40-2.
[0181] (Other embodiments) The above-described embodiments are not limited to being implemented separately and independently, and two or more of the embodiments may be combined.
[0182] In the above-described first embodiment, the timing information specifies the execution timing, which is the timing for executing communication in the NW 40-2, but this is not limited thereto. The timing information may be information indicating a timing when communication with the NW 40-1 is possible. In this case, the NW 40-1 can schedule communication with the UE 100 at the timing when communication is possible.
[0183] A program may be provided that causes a computer to execute each process according to the above-described embodiment. The program may be recorded in a computer-readable medium. Using the computer-readable medium, it is possible to install the program in the computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.
[0184] The above describes the embodiments in detail with reference to the drawings, but the specific configuration is not limited to that described above, and various design changes, etc. are possible without departing from the spirit of the invention.
[0185] This application claims priority to Japanese Patent Application No. 2020-146146 (filed August 31, 2020), the entire contents of which are incorporated herein by reference. [Explanation of symbols]
[0186] 100:UE 110: Receiving unit 120: Transmitter 130: Control section 200: gNB 210: Transmission unit 220: Receiving unit 230: Control section 260: Backhaul communication unit 300:AMF 310: Control section 320: Backhaul communication unit
Claims
1. 1. A method of communication control using a user equipment having a first subscriber identity module (SIM) corresponding to a first mobile network and a second SIM corresponding to a second mobile network, comprising: receiving, by the user equipment, from the first mobile network, information regarding transmission of timing information for performing communication in the second mobile network; determining, by the user equipment, whether transmission of the timing information is permitted based on information relating to the transmission of the timing information; and transmitting, in response to the user equipment determining that transmission of the timing information is permitted, the timing information to the first mobile network. Communications control method.
2. The method further includes transmitting a desired RRC state in the first mobile network to a base station in the first mobile network. The communication control method according to claim 1 .
3. a base station in the first mobile network receiving the timing information; The base station further includes transmitting a HandoverPreparationInformation message including a UE (UserEquipment) context of the user equipment; The UE context of the user equipment includes the timing information. The communication control method according to claim 1 .
4. The method further includes: a base station in the first mobile network setting, for the user equipment, a communication gap in which the user equipment does not transmit or receive data to or from the first mobile network based on the timing information. The communication control method according to claim 1 .
5. determining, by the user equipment, one of the first mobile network and the second mobile network as a preferred network and determining the other as a non-preferred network; and transmitting the timing information includes transmitting the timing information if the first mobile network is determined to be the non-preferred network. The communication control method according to claim 1 .
6. and transmitting, by the user equipment, the timing information to the first mobile network in response to an occurrence of a predetermined event; The predetermined event is a transition of the user equipment from an RRC (Radio Resource Control) connected state to an RRC inactive state in the second mobile network, or a transition of the user equipment to an RRC connected state in the first mobile network. The communication control method according to claim 1 .
7. A user equipment having a first subscriber identity module (SIM) corresponding to a first mobile network and a second SIM corresponding to a second mobile network, a receiving unit for receiving information from the first mobile network regarding a transmission of timing information for performing communication in the second mobile network; a control unit that determines whether transmission of the timing information is permitted based on information related to the transmission of the timing information; a transmitting unit configured to transmit the timing information to the first mobile network in response to determining that the transmission of the timing information is permitted. User equipment.
8. 1. A processor for controlling a user equipment having a first subscriber identity module (SIM) corresponding to a first mobile network and a second SIM corresponding to a second mobile network, comprising: receiving from the first mobile network information regarding transmission of timing information for performing communication in the second mobile network; determining whether transmission of the timing information is permitted based on information regarding the transmission of the timing information; and transmitting the timing information to the first mobile network in response to determining that the transmission of the timing information is permitted. Processor.
Citation Information
Patent Citations
Dual active connectivity via a single wireless user equipment
JP2017539164A
