WO2022045222A1 - 通信制御方法 - Google Patents
通信制御方法 Download PDFInfo
- Publication number
- WO2022045222A1 WO2022045222A1 PCT/JP2021/031249 JP2021031249W WO2022045222A1 WO 2022045222 A1 WO2022045222 A1 WO 2022045222A1 JP 2021031249 W JP2021031249 W JP 2021031249W WO 2022045222 A1 WO2022045222 A1 WO 2022045222A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- timing
- information
- mobile network
- rrc
- timing information
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 93
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000004044 response Effects 0.000 claims abstract description 10
- 230000005540 biological transmission Effects 0.000 claims description 31
- 230000007704 transition Effects 0.000 claims description 11
- 238000010295 mobile communication Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 230000000737 periodic effect Effects 0.000 description 7
- 238000012544 monitoring process Methods 0.000 description 6
- CSRZQMIRAZTJOY-UHFFFAOYSA-N trimethylsilyl iodide Substances C[Si](C)(C)I CSRZQMIRAZTJOY-UHFFFAOYSA-N 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000011664 signaling Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 238000012546 transfer Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 2
- 230000001052 transient effect Effects 0.000 description 2
- 239000000969 carrier Substances 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1215—Wireless traffic scheduling for collaboration of different radio technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/40—Security arrangements using identity modules
- H04W12/45—Security arrangements using identity modules using multiple identity modules
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/72—Subscriber identity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
Definitions
- the present invention relates to a communication control method.
- the user device is a subscriber identification module (SIM: Subscriber) in order to use a mobile communication service (voice call service, data communication service, etc.) provided by a communication carrier (also referred to as an operator or a communication carrier) via a mobile network. It is necessary to install Identity Module).
- SIM subscriber identification module
- the user device registers with the mobile network using SIM, the mobile communication service from the registration destination mobile network can be used.
- the user device equipped with the two SIMs uses the mobile communication service from the first mobile network, which is the mobile network to which the first SIM is registered, and also uses the mobile communication service.
- the mobile communication service from the second mobile network which is the mobile network to which the second SIM is registered, may be used. Discussions on use cases when using both mobile communication services have been started in 3GPP (Third Generation Partnership Project) (for example, Non-Patent Document 1).
- the communication control method uses a user apparatus having a first subscriber identification module (SIM) corresponding to the first mobile network and a second SIM corresponding to the second mobile network. It is a communication control method.
- the first mobile network provides timing information indicating execution timing, which is the timing at which the user apparatus executes communication in the second mobile network in response to the occurrence of a predetermined event. Have to send to.
- the communication in the first mobile network and the communication in the second mobile network occur at the same time, there is a possibility that one of the communications cannot be executed.
- the first mobile network and the second mobile network belong to different carriers, it is difficult to avoid such a problem by cooperation between the mobile networks.
- the object of the present disclosure is to enable appropriate communication in a plurality of mobile networks in a user device capable of mounting a plurality of SIMs.
- the mobile communication system (Mobile communication system) The configuration of the mobile communication system according to the embodiment will be described.
- the mobile communication system according to one embodiment is a 5G system of 3GPP, but LTE (Long Term Evolution) of 3GPP may be applied to the mobile communication system at least partially.
- LTE Long Term Evolution
- FIG. 1 is a diagram showing a configuration of a mobile communication system according to an embodiment.
- the mobile communication system includes a first mobile network (MN40-1) operated by a first carrier and a second mobile network (MN40-) operated by a second carrier. 2) and a user device (UE: User Equipment) 100.
- the UE 100 can be registered in the MN40-1 using SIM140-1 described later, and can be registered in the MN40-2 using the SIM140-2.
- MN40-1 and MN40-2 are simply referred to as MN40.
- the MN40 may be a network that uses 5G technology or a network that uses LTE technology.
- FIG. 1 is an example of MN40 using 5G technology.
- the MN40 has a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10 and a 5G core network (5GC: 5G Core Network) 20.
- NG-RAN Next Generation Radio Access Network
- 5GC 5G Core Network
- NG-RAN is read as E-UTRAN (Evolved-UMTS Radio Access Network)
- 5GC is read as EPC (Evolved Packet Core).
- gNB described later is read as eNB
- AMF described later is read as MME (Mobile Management Entry).
- UPF described later is read as S-GW (Serving Gateway) and / or P-GW (Packet Data Network Gateway).
- the UE100 is a movable device.
- the UE 100 may be any device as long as it is a device used by the user.
- the UE 100 may be a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, or a communication module (communication card or communication card). (Including a chip set), a sensor or a device provided on the sensor, a vehicle or a device provided on the vehicle (Vehicle UE), a vehicle or a device provided on the vehicle (Arial UE).
- the NG-RAN 10 includes a base station (referred to as "gNB” in a 5G system) 200.
- the gNB 200 may also be referred to as an NG-RAN node.
- the gNB 200s 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 / scheduling, and the like.
- RRM radio resource management
- Cell is used as a term 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.
- the gNB may be connected to the LTE core network EPC (Evolved Packet Core), or the LTE base station may be connected to the 5GC. Further, the LTE base station and gNB may be connected via an interface between base stations.
- EPC Evolved Packet Core
- the 5GC20 includes AMF (Access and Mobility Management Function) 300 and UPF (User Plane Function) 400.
- the AMF 300 performs various mobility controls and the like 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 NAS (Non-Access Stratum) signaling.
- the UPF400 controls data transfer.
- the AMF300 and UPF400 are connected to the gNB200 via the NG interface, which is an interface between the base station and the core network.
- FIG. 2 is a diagram showing the configuration of the UE 100 (user device).
- the UE 100 has a receiving unit 110, a transmitting unit 120, a control unit 130, a SIM140-1 (first SIM), a SIM140-2 (second SIM), and a user interface 150.
- the UE 100 may have three or more SIM 140s.
- 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 the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 130.
- the transmission unit 120 performs various transmissions under the control of the control unit 130.
- the transmitter 120 includes an antenna and a transmitter.
- the transmitter converts the baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.
- the control unit 130 performs various controls on 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 a program executed by the processor and information used for processing by the processor.
- the processor may include a baseband processor and a CPU (Central Processing Unit).
- the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
- the CPU executes a program stored in the memory to perform various processes.
- the SIM 140 records information that identifies a subscriber in order to receive a mobile communication service provided by a mobile network. In addition to the information for identifying the subscriber, the SIM 140 may record the carrier identification information for identifying the telecommunications carrier and the information regarding the available services contracted by the subscriber.
- the SIM 140 may be an IC card called a removable SIM card (or USIM card), that is, an information card.
- the SIM 140 may be an embedded eSIM (Embedded SIM).
- the SIM 140-1 (first SIM) is a first IMSI (International Mobile Subscriber Identity) which is an identification number assigned to a user of the UE 100 by a first telecommunications carrier operating the first mobile network 40-1. ) Is recorded.
- the SIM 140-2 (second SIM) provides information for identifying the second IMSI, which is an identification number assigned to the user of the UE 100 by the second carrier operating the second mobile network 40-2. Record.
- SIM140-1 and SIM140-2 may be separate information cards or may be integrated into the same information card.
- SIM140-1 and SIM140-2 may be included in eSIM (Embedded SIM).
- SIM140-1 is managed by the first telecommunications carrier.
- SIM140-2 is managed by a second carrier. Note that SIM140-1 and SIM140-2 may be managed by the same telecommunications carrier.
- the UE 100 When the UE 100 registers with the first mobile network 40-1 using SIM 140-1, the UE 100 can use the mobile communication service provided by the first communication carrier via the first mobile network 40-1. Further, when the UE 100 registers with the second mobile network 40-2 using the SIM 140-2, the UE 100 uses the mobile communication service provided by the second communication carrier via the second mobile network 40-2. can.
- the user of the UE 100 may set the priority order between SIM140-1 and SIM140-2 via the user interface 150.
- the user may set SIM140-1 to take precedence over SIM140-2, or may set SIM140-2 to take precedence over SIM140-1.
- FIG. 3 is a diagram showing the configuration of gNB200 (base station).
- the gNB 200 includes a transmission unit 210, a reception unit 220, a control unit 230, and a backhaul communication unit 240.
- the transmission unit 210 performs various transmissions under the control of the control unit 230.
- the transmitter 210 includes an antenna and a transmitter.
- the transmitter converts the baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.
- the receiving unit 220 performs various receptions under the control of the control unit 230.
- the receiving unit 220 includes an antenna and a receiver.
- the receiver converts the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 230.
- the control unit 230 performs various controls on 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 a program executed by the processor and information used for processing by the processor.
- the processor may include a baseband processor and a CPU.
- the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
- the CPU executes a program stored in the memory to perform various processes.
- the backhaul communication unit 240 is connected to an adjacent base station via an interface between base stations.
- the backhaul communication unit 240 is connected to the AMF / UPF 300 via the base station-core network interface.
- FIG. 4 is a diagram showing the configuration of AMF300 (core network device).
- the AMF 300 includes a control unit 330 and a backhaul communication unit 340.
- the control unit 330 performs various controls on 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 a program executed by the processor and information used for processing by the processor.
- the backhaul communication unit 340 is connected to the gNB 200 via the base station-core network interface.
- FIG. 5 is a diagram showing a configuration of a protocol stack of a wireless interface of a user plane that handles data.
- the wireless interface protocol of the user plane includes a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, and the like. It has an SDAP (Service Data Adjustment Protocol) layer.
- PHY physical
- MAC Medium Access Control
- RLC Radio Link Control
- PDCP Packet Data Convergence Protocol
- SDAP Service Data Adjustment Protocol
- the PHY layer performs coding / 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.
- a frame structure containing radio frames, subframes, slots, and symbols is used.
- the radio frame is composed of 10 subframes on the time axis.
- the length of each subframe is 1 ms.
- Each subframe is composed of a plurality of slots.
- Each slot is composed of a plurality of symbols.
- Each subframe contains a plurality of resource blocks (RBs) on the frequency axis.
- Each resource block contains a plurality of subcarriers on the frequency axis.
- the frequency resource can be specified by the resource block, and the time resource can be specified by the subframe (or slot, symbol).
- the section of the first number symbol of each subframe is an area mainly used as a physical downlink control channel (PDCCH: Physical Downlink Control Channel) for transmitting downlink control information.
- the rest of each subframe is an area that can be used mainly as a physical downlink shared channel (PDSCH: Physical Downlink Shared Channel) for transmitting downlink data.
- PDSCH Physical Downlink Shared Channel
- the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ), random access procedure, and the like. Data and control information are transmitted between the MAC layer of the UE 100 and the MAC layer of the gNB 200 via the transport channel.
- the MAC layer of gNB200 includes a scheduler. The scheduler determines the transport format (transport block size, modulation / coding method (MCS)) of the upper and lower links and the resource block allocated to the UE 100.
- MCS modulation / coding method
- the RLC layer transmits data to the receiving RLC layer 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.
- the PDCP layer performs header compression / decompression and encryption / decryption.
- the SDAP layer maps the IP flow, which is a unit for performing QoS control by the core network, with the wireless bearer, which is a unit for performing QoS control by AS (Access Stratum).
- AS Access Stratum
- FIG. 6 is a diagram showing a configuration of a protocol stack of a wireless interface of a control plane that handles signaling (control signal).
- the protocol stack of the radio interface of the control plane has an RRC (Radio Resource Control) layer and a NAS (Non-Access Stratum) layer in place of the SDAP layer shown in FIG.
- RRC signaling for various settings is transmitted between the RRC layer of UE100 and the RRC layer of gNB200.
- the RRC layer controls logical channels, transport channels, and physical channels in response to the establishment, re-establishment, and release of radio bearers.
- RRC connection connection between the RRC of the UE 100 and the RRC of the gNB 200
- the UE 100 is in the RRC connected state.
- RRC connection no connection between the RRC of the UE 100 and the RRC of the gNB 200
- the UE 100 is in the RRC idle state. Further, when the RRC connection is suspended, the UE 100 is in the RRC inactive state.
- the NAS layer 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 AMF300.
- the UE 100 has an application layer and the like in addition to the wireless interface protocol.
- the first embodiment is an embodiment for solving such a problem.
- the UE 100 transmits timing information for specifying the execution timing, which is the timing for executing the communication in the NW40-2, to the NW40-1.
- the NW40-1 can grasp the timing at which the UE 100 executes the communication in the NW40-2, and can schedule the communication with the UE 100 at a timing that does not overlap with such a timing. Therefore, it is possible to avoid a collision between the communication in the NW40-1 and the communication in the NW40-2.
- the execution timing includes at least one of a paging reception opportunity, a unicast scheduling opportunity, an MBS scheduling opportunity, and a side link scheduling opportunity.
- the paging reception opportunity is the timing at which the UE 100 in the RRC idle state or the RRC inactive state monitors paging from the NW40-2.
- UE100 in the RRC idle state monitors CN paging.
- the UE 100 in the 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 RAN.
- the UE 100 monitors paging using Discontinuous reception (DRX) in the RRC idle state and the RRC inactive state in order to reduce power consumption.
- DRX Discontinuous reception
- the UE 100 monitors one paging opportunity (Paging Occasion (PO)) for each DRX cycle.
- the DRX cycle is represented by the number of radio frames.
- the DRX cycle is sometimes referred to as the paging cycle.
- PO is composed of one or more subframes or one or more symbols.
- One PO is associated with a paging frame (Paging Frame (PF)), which is one wireless frame.
- PF paging Frame
- the PO associated with the PF may start within or after the PF.
- the paging reception opportunity of the UE 100 is the timing (subframe or symbol) included in the PO generated in each DRX cycle.
- the UE 100 uses the smaller of the default DRX cycle and the UE-specific DRX cycle set in the UE 100 as the DRX cycle (hereinafter referred to as “T”) that the UE 100 should use for paging monitoring. decide.
- the default DRX cycle is included in the system information received from the serving cell (gNB200) in which the UE 100 is located.
- the UE-specific DRX cycle differs depending on the RRC state of the UE 100.
- the UE-specific DRX cycle includes a first UE-specific DRX cycle.
- the UE-specific DRX cycle includes a first UE-specific DRX cycle and a second UE-specific DRX cycle.
- 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.
- a NAS message is, for example, a REGISTRATION ACCESS message from AMF300-2 of NW40-2 when the UE100 registers with NW40-2.
- the second UE-specific DRX cycle is a UE-specific DRX cycle set in the UE 100 by an individual RRC message for monitoring RAN paging.
- Such an individual RRC message is, for example, an RRC release message for transitioning the UE 100 from the RRC connected state to the RRC inactive state.
- Such an RRCfreease message includes an information element (IE) called "Suspendconfig", and "Suspendconfig" contains information indicating a second UE-specific DRX cycle.
- IE information element
- the UE 100 in the RRC idle state determines the smaller of the default DRX cycle and the first UE-specific DRX cycle as "T".
- the UE 100 in the RRC inactive state determines the smaller of the default DRX cycle, the first UE-specific DRX cycle, and the second UE-specific DRX cycle as "T".
- the UE 100 determines the default DRX cycle as "T".
- the UE 100 After determining "T", the UE 100 determines the radio frame number of the PF and the subframe or symbol constituting the PO based on the "T”, the "UE_ID", and the paging-related information.
- UE_ID is a value calculated by a temporary subscriber identifier assigned to the UE 100 by the AMF300-2.
- a temporary subscription identifier is, for example, 5G-S-TMSI (Temporary Mobile Subscriber Identity).
- UE_ID is, for example, a value obtained by "5G-S-TMSI mod 1024".
- the paging-related information is included in the system information received from the serving cell (gNB200) in which the UE 100 is located.
- the paging-related information includes parameters such as N, Ns, and PF_offset.
- the unicast scheduling opportunity is a candidate timing in which the transmission / reception of unicast data between the UE 100 in the RRC connected state and the NW40-2 (gNB200-2) is scheduled.
- the unicast scheduling opportunity is the timing included in the periodic scheduling period.
- FIG. 7 is a diagram showing an example of a unicast scheduling opportunity.
- the schedule period is a period that occurs in each cycle "P".
- the scheduling period starts from the start timing (t1, t2, t3 ).
- the scheduling period has a predetermined time length (D).
- the gNB 200 allocates the communication timing (subframe, slot, symbol, etc.) of the unicast data with the UE 100 in the scheduling period within one cycle. On the other hand, the gNB 200 does not allocate communication timing to the UE 100 during the non-scheduling period (a period other than the scheduling period) within one cycle.
- the communication timing includes at least one of a timing of transmitting unicast data from the UE 100 to the gNB 200 and a timing of transmitting the unicast data from the gNB 200 to the UE 100.
- Unicast scheduling opportunities are specified by three parameters: start timing, cycle, and predetermined time length.
- 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.
- the unicast scheduling opportunity is set from gNB200 to UE100 by a unicast RRC message (for example, an RRCreconfiguration message).
- the gNB 200 may set a unicast scheduling opportunity to the UE 100 in response to a request from the UE 100.
- the gNB 200 may set a unicast scheduling opportunity for the UE 100 based on the history of past traffic of the UE 100 and / or the prediction of future traffic of the UE 100.
- the scheduling period that occurs in each cycle may be configured at a plurality of non-consecutive timings.
- the scheduling period may be configured by a plurality of non-consecutive timings within a predetermined time length (D).
- a plurality of non-consecutive timings within a predetermined time length are indicated by a bitmap. For example, when the predetermined time length is 4 subframes and the 1st and 4th subframes of the 4 subframes are the timings corresponding to the scheduling period, the scheduling period is the predetermined time length and ( It is specified by the bitmap of 1, 0, 0, 1).
- MBS scheduling opportunity is a candidate timing in which the transmission of MBS data from NW40-2 to UE100 is scheduled.
- MBS is a service that broadcasts or multicasts data from NW40-2 to UE100, that is, one-to-many (PTM: Point To Multipoint) data transmission.
- PTM Point To Multipoint
- MBS may be referred to as MBMS (Multicast Broadcast and Multicast Service).
- MBS data refers to data transmitted by MBS.
- the MBS scheduling opportunity is the timing included in the periodic scheduling period.
- the MBS scheduling opportunity may be specified by parameters such as start timing, cycle, predetermined time length, and bitmap, as in the above-mentioned unicast scheduling opportunity.
- the parameter for specifying the MBS scheduling opportunity is different from the parameter for specifying the unicast scheduling opportunity.
- the MBS scheduling opportunity is set from gNB200 to UE100 via a broadcast RRC message (eg, SIB for MBS).
- the MBS scheduling opportunity can be set on the UE 100 regardless of the RRC state of the UE 100.
- MBS information may directly include parameters that identify MBS scheduling opportunities.
- the MBS information may include MBS control channel setting information for the UE 100 to receive the MBS control channel to which the parameter specifying the MBS scheduling opportunity is carried.
- the side link scheduling opportunity is a candidate timing at which side link communication by the UE 100 is scheduled in NW40-2.
- Side-link communication is communication performed between nearby UEs 100 without going through a network node (for example, gNB200).
- the side link communication includes at least one of a side link transmission in which the UE 100 transmits data to another UE 100 and a side link reception in which the UE 100 receives data from the other UE 100.
- the side link scheduling opportunity is the timing included in the periodic scheduling period.
- the side link scheduling opportunity may be specified by parameters such as start timing, cycle, predetermined time length, and bitmap, as in the above-mentioned unicast scheduling opportunity.
- the parameter for specifying the side link scheduling opportunity is different from the parameter for specifying the unicast scheduling opportunity.
- the parameters that specify the sidelink scheduling opportunity are different from the parameters that specify the MBS scheduling opportunity.
- the side link scheduling opportunity may be set from gNB 200 to UE 100 via a broadcast RRC message (eg, SIB for side link).
- the sidelink scheduling opportunity can be set on the UE 100 regardless of the RRC state of the UE 100.
- the UE 100 When the UE 100 is interested in side-link communication regardless of its own RRC state, it acquires a side-link SIB and specifies a side-link scheduling opportunity based on the side-link information included in the side-link SIB.
- the side link information is, for example, information indicating a resource pool for side link communication.
- FIG. 8 is a diagram showing the operation of the operation example 1 of the first embodiment.
- the UE 100 is registered in both MN40-2 and MN40-1.
- the UE 100 is in any of the RRC connected state, the RRC idle state, and the RRC inactive state in the MN40-2.
- the UE 100 is in any of the RRC connected state, the RRC idle state, and the RRC inactive state in the MN40-1.
- step S101 the UE 100 determines whether or not a predetermined event occurs. The details of the predetermined event will be described later.
- step S101 determines that a predetermined event has occurred (step S101: YES)
- step S102 the UE 100 advances the process to step S102.
- step S102 the UE 100 transmits timing information for specifying the execution timing, which is the timing for executing the communication in the NW40-2, to the NW40-1.
- the timing information is 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. Including one.
- step S102 when the UE 100 is in the RRC idle state or the RRC inactive state in NW40-1, the UE 100 may transmit the timing information after transitioning to the RRC connected state.
- step S102 the destination of the timing information is gNB200-1 and / or AMF300-1 in NW40-1.
- the timing information is transmitted as an RRC message.
- the transmission destination of the timing information is AMF300-1
- the timing information is transmitted by the NAS message.
- the destination of the timing information may be determined as AMF300-1. In this case, the UE 100 may transmit information to gNB200-1 indicating that it wants to transition to the RRC idle state after step S102.
- the destination of the timing information may be determined as both AMF300-1 and gNB200-1. In this case, the UE 100 may transmit information to gNB200-1 indicating that it wants to transition to the RRC inactive state after step S102.
- the NAS layer of the UE 100 When the UE 100 transmits the timing information by the NAS message, the NAS layer of the UE 100 generates the timing information.
- the RRC layer transmits information necessary for specifying 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 default DRX cycle known to the RRC layer.
- the UE 100 may transmit the timing information and the information indicating the guard time together.
- the guard time is the time required for the UE 100 to switch from the communication with the NW40-2 (gNB200-2) to the communication with the NW40-1 (gNB200-1).
- the guard time is represented by the number of radio frames, the number of subframes, the number of slots, or the number of symbols.
- the guard time may be set before and after the execution timing (for example, PO).
- the timing information transmitted to NW40-1 corresponds to the execution timing of NW40-2.
- Information for specifying the timing of 1 may be included.
- the timing information is information indicating the timing of NW40-1 corresponding to the execution timing of NW40-2 (that is, the 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 timing difference is represented by the number of radio frames, the number of subframes, the number of slots, the number of symbols, and the like.
- step S103 MN40-1 (gNB200-1 and / or AMF300-1) does not use the timing specified by the information (timing information or timing information + information indicating guard time) received in step S102.
- the timing specified by the information (timing information, information indicating the guard time) received in step S102 is referred to as “non-use timing”.
- the operation in step S103 includes, for example, the following operations 1 to 4.
- the gNB200-1 is a UE-specific DRX cycle of the UE100 (described above) so that when the UE100 is transitioned to the RRC inactive state, the PO corresponding to the RAN paging transmitted from the gNB200-1 is arranged at the non-use timing.
- the second UE-specific DRX cycle) is set, and an RRC Release message including the UE-specific DRX cycle is transmitted to the UE 100.
- Operation 2 gNB200-1 allocates a timing other than the non-use timing to send / receive data to / from the UE 100 in the RRC connected state.
- Operation 3 The gNB200-1 sets a predetermined period including the non-use timing as a communication gap of the UE 100 in the RRC connected state, and transmits information indicating the communication gap to the UE 100. gNB200-1 does not schedule the transmission and reception of data with the UE 100 in the communication gap.
- the AMF300-1 has a UE-specific DRX cycle of the UE 100 (the first UE-specific DRX cycle described above) so that the PO corresponding to the CN paging transmitted from the AMF300-1 is arranged at the non-use timing.
- a new 5G-S-TMSI to be assigned to the UE 100 is set, and the UE 100 is notified by a NAS message.
- the AMF300-1 may notify the UE 100 of the offset value for the 5G-S-TMSI already assigned to the UE 100, instead of allocating the new 5G-S-TMSI to the UE 100.
- the offset value is used only to identify paging reception opportunities. Further, the offset value may be notified from AMF300-1 to gNB200-1 at the time of paging execution.
- step S103 is not essential.
- the predetermined event includes any of the following events A to F.
- Event A is an event that causes the UE 100 to start monitoring the paging message in NW40-2.
- step S101 when event A occurs in UE 100, in step S102, UE 100 transmits timing information including information indicating a paging reception opportunity.
- the timing information may further include information for identifying other execution timings (unicast scheduling opportunity, MBS scheduling opportunity, side link scheduling opportunity, etc.) known to the UE 100 at this time.
- Event A includes, for example, any of the following events A1 to A3.
- Event A1 is that the UE 100 transitions from the RRC connected state to the RRC inactive state in NW40-2.
- Event A2 is that the UE 100 transitions from the RRC connected state to the RRC idle state in NW40-2.
- Event B is an event that can cause a change in the paging reception opportunity in the UE 100 that has already started monitoring the paging message in NW40-2.
- step S101 when event B occurs in UE 100, in step S102, UE 100 transmits timing information including information indicating a paging reception opportunity (updated paging reception opportunity).
- the timing information may further include information for identifying other execution timings known to the UE 100 at this time.
- Event B is, for example, any of the following events B1 to B3.
- Event B1 is that the UE 100 in the RRC inactive state in NW40-2 transitions to the RRC idle. In this case, the UE 100 determines the “T” without considering the second UE-specific DRX cycle, so that the “T” may change.
- Event B2 is that the UE 100 in the RRC inactive state in NW40-2 maintains the RRC inactive state after performing the RNA (Ran Notification Area) update procedure.
- the UE 100 since the UE 100 receives the RRC Release message including the "suspendConfig" again, the second UE-specific DRX cycle may be updated and the "T” may be changed.
- RNA renewal procedure For details on the RNA renewal procedure, refer to Chapter 9.2.2.5 of 3GPP Technical Specification TS 38.300.
- Event B3 is that the UE 100 in the RRC inactive state or the RRC idle state in NW40-2 performs cell reselection.
- the "T" may change because the default DRX cycle may change in response to changes in the serving cell of the UE 100.
- Event C is that the unicast scheduling opportunity is set in UE100 in NW40-2, or the unicast scheduling opportunity of UE100 is changed in NW40-2.
- step S101 when event C occurs in UE 100, in step S102, UE 100 transmits timing information including information for specifying a unicast scheduling opportunity.
- the timing information may further include information for identifying other execution timings known to the UE 100 at this time.
- event D the UE 100 is interested in receiving MBS data in NW40-2, the UE 100 starts receiving MBS data in NW40-2, or the MBS scheduling opportunity of UE100 is changed in NW40-2. That is.
- the UE 100 transmits timing information including information for specifying the MBS scheduling opportunity in step S102.
- the timing information may further include information for identifying other execution timings known to the UE 100 at this time.
- the UE 100 is interested in side-link communication in NW40-2, the UE 100 starts side-link communication in NW40-2, or the side-link scheduling opportunity of UE100 is changed in NW40-2. Is.
- the UE 100 transmits timing information including information for specifying the side link scheduling opportunity in step S102.
- the timing information may further include information for identifying other execution timings known to the UE 100 at this time.
- Event F is that the UE 100 transitions to the RRC connected state in NW40-1.
- the UE 100 in step S102 transmits timing information including information for specifying the execution timing already grasped by the UE 100 at the time when the event F occurs. For example, if the UE 100 has already monitored paging in NW40-2 and has received MBS data at the time of event F, the UE 100 has information for identifying a paging reception opportunity and an MBS scheduling opportunity. Send timing information, including information to identify.
- the operation example 2 is an operation example relating to the transmission permission of the timing information.
- FIG. 9 is a diagram showing the operation of the operation example 2 of the first embodiment.
- step S201 the UE 100 receives from NW40-1 (gNB200-1) information indicating whether or not transmission of timing information is permitted (hereinafter, referred to as "transmission availability information").
- the UE 100 may receive transmission availability information in an individual RRC message, or may receive transmission availability information in SIB.
- the UE 100 stores the received transmission availability information.
- the UE 100 may send a request message for permitting transmission of timing information to gNB200-1.
- the gNB200-1 transmits the transmission availability information to the UE 100 as an individual RRC message in response to the reception of the request message.
- the request message may include information indicating that the UE 100 is in a state registered in both MN40-1 and MN40-2 (hereinafter, referred to as "MUSIM state").
- MUSIM state MN40-1 and MN40-2
- the gNB 200-1 may transmit transmission enable / disable information indicating that transmission of timing information is permitted to the UE 100.
- the current LTE specifications do not specify how to handle a UE 100 with multiple SIMs, so if the NW40-1 uses LTE technology (ie, the NW40-1 has E-UTRAN and EPC. ), The transmission of timing information may not be permitted.
- step S202 the UE 100 determines whether or not a predetermined event occurs. A given event occurs.
- step S202: YES the UE 100 advances the process to step S203.
- step S203 the UE 100 determines whether or not transmission of timing information is permitted based on the stored transmission availability information.
- step S202: NO the UE 100 ends this flow.
- step S203: YES the process proceeds to step S204.
- step S204 is the same as the operation in step S102.
- the operation example 3 is an operation example relating to the priority network.
- one MN40 is determined as the priority network and the other MN40 is determined as the non-priority network.
- 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 the communication in the priority network and the communication in the non-priority network are scheduled at the same timing, the UE 100 may perform communication in the priority network and may not perform communication in the non-priority network. Further, when the UE 100 receives the data transmitted by the priority network and the 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.
- the priority network paging monitoring, data transmission / reception, etc.
- the determination method includes, for example, any of the following first to fourth methods.
- the UE 100 determines the priority network based on the user's settings. For example, when the user sets SIM140-2 to be prioritized over SIM140-1, the UE 100 determines MN40-2 corresponding to SIM140-2 as the preferred network and MN40-1 corresponding to SIM140-1 as the non-priority network. To be determined as.
- the UE 100 determines the MN40 using LTE technology as the priority network. For example, if the MN40-1 uses 5G technology and the MN40-2 uses LTE technology, the UE 100 determines the MN40-2 as the preferred network and the MN40-1 as the non-priority network. When the MN40-1 and the MN40-2 use the same technology, the UE 100 does not determine the priority network by the second method.
- the UE 100 determines the MN 40 in which the wireless bearer having the priority equal to or higher than the threshold value is established as the priority network. For example, when a radio bearer having a priority equal to or higher than the threshold value is established between the MN40-2 and the UE100, the UE 100 determines the MN40-2 as the preferred network and the MN40-1 as the non-priority network.
- the priority of the wireless bearer is determined by the type of traffic of the user data mapped to the wireless bearer. For example, when the traffic type is a voice call, the priority is determined to be high, and when the traffic type is mail, chat, Web browsing, etc., the priority is determined to be low.
- the priority of the radio bearer may be a value corresponding to 5QI. For the correspondence between 5QI and priority, refer to Table 5.7.4 of 3GPP Technical Specification TS 23.501.
- the priority of the radio bearer may be a value associated with QCI. For the correspondence between QCI and priority, refer to Table 6.1.7 of 3GPP Technical Specification TS 23.203.
- the UE 100 determines the MN40 whose periodic communicable period is set in the UE 100 as the priority network.
- the periodic communicable period is, for example, a communication period specified by SPS (Semi-Persistent Scheduling) or a communication period specified by CG (Configured Grant).
- SPS Semi-Persistent Scheduling
- CG Configured Grant
- FIG. 10 is a diagram showing the operation of the operation example 3 of the first embodiment.
- step S301 the UE 100 determines one of MN40-2 and MN40-1 as the priority network and the other as the non-priority network by using the above-mentioned method for determining the priority network.
- step S302 the UE 100 determines whether or not a predetermined event occurs. A given event occurs.
- step S302 the UE 100 advances the process to step S303.
- step S303 the UE 100 determines whether the MN40-1 is a non-priority network.
- step S303: NO the UE 100 ends this flow.
- step S303: YES the UE 100 proceeds to the process in step S304.
- step S304 is the same as the operation in step S102.
- the UE 100 may send a non-priority notification indicating that the NW 40 is a non-priority network to the NW 40 determined as the non-priority network. For example, when the UE 100 determines NW40-1 as a non-priority network, it transmits a non-priority notification to NW40-1 (gNB200-1 and / or AMF300-1). When the periodic communicable period is set in NW40-2, the UE 100 may transmit information for specifying the periodic communicable period together with the non-priority notification.
- gNB200-1 When gNB200-1 receives the non-priority notification, it recognizes that NW40-1 is a non-priority network. Even if gNB200-1 recognizes that NW40-1 is a non-priority network, it restricts the establishment of a wireless bearer having a priority equal to or higher than the threshold value (for example, a wireless bearer for voice communication) with the UE 100. good.
- the threshold value for example, a wireless bearer for voice communication
- the UE 100 may notify the NW40-1 to that effect. In this case, the restriction on the establishment of the radio bearer whose priority is equal to or higher than the threshold value is lifted.
- the UE 100 may transmit information desired to transition to the RRC idle state or the RRC inactive state to the NW40 determined as the non-priority network.
- Such information is, for example, information indicating that the desired RRC state (preferred RRC-State) of the UE 100 is the RRC idle state.
- Such information may be information indicating that the preferred RRC-State of the UE 100 is in the RRC inactive state.
- Such information may be information indicating that the UE 100 simply wants to release the RRC connection and there is no desired RRC state.
- the gNB200-1 when the UE 100 determines NW40-1 as a non-priority network and is in the RRC connected state in the NW40-1, the gNB200-1 is changed to the RRC idle state or the RRC inactive state. Send the desired information.
- the information may be transmitted together with the timing information.
- the gNB 200-1 may shift the UE 100 to the RRC idle state or the RRC inactive state according to the reception of the information.
- the operation example 4 is an operation example relating to the UE context.
- FIG. 11 is a diagram showing the operation of the operation example 4. As shown in FIG. 11, in the initial state, the UE 100 is registered in the MN40-2. The UE 100 has an RRC connection with gNB200-1 (a) belonging to MN40-1.
- step S401 is the same as the operation in step S101.
- step S402 the UE 100 transmits the timing information to the gNB200-1 (a) belonging to the MN40-1.
- step S403 gNB200-1 (a) stores the timing information as part of the UE context of the UE100.
- 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.
- Examples of the predetermined procedure include a handover procedure, an RRC connection re-establishment procedure, an RRC connection resume procedure, and the like.
- gNB200-1 (a) transmits the HandoverPreparationInformation message in the handover procedure including the UE context (including timing information).
- the gNB200-1 (a) sets the UE context to gNB200-1 (a) in response to receiving a RETRIEVE UE TEXT REQUEST message for requesting the provision of the UE context from the gNB200-1 (b) in the RRC Resume procedure. It may be transmitted to b).
- step S406 gNB200-1 (b) communicates with the UE 100 without using the timing specified by the timing information (operations 1 to 3 of step S103 described above).
- the second embodiment is an operation example relating to voice communication.
- FIG. 12 is a diagram showing the operation of the second embodiment.
- step S501 the UE 100 determines whether or not a voice communication event occurs in the NW40-2.
- step S501: YES the process proceeds to step S502.
- the voice communication event is that the user of the UE 100 transmits voice via NW40-2, or the UE 100 receives a paging message notifying the arrival of voice.
- step S502 the UE 100 inquires of the MN40-1 whether or not the execution of voice communication is permitted to the UE 100.
- step S503 the UE 100 receives a permission notification from the MN40-1 indicating that the execution of voice communication is permitted.
- step S504 the UE 100 executes voice communication in response to receiving the permission notification. If the UE 100 has not received the permission notification, the UE 100 does not execute the voice communication.
- the third embodiment presupposes that NW40-1 and NW40-2 belong to the same telecommunications carrier.
- MUSIM state MN40-1 and MN40-2
- NW40-1 and NW40-2 can grasp that the same UE 100 is registered in both NW40-1 and NW40-2. Therefore, NW40-1 and NW40-2 can cooperate with each other so as to appropriately communicate with the UE 100.
- the UE 100 When the UE 100 is in the RRC connected state to both NW40-1 and NW40-2, the UE 100 may transmit MUSIM state information further indicating this state.
- the destination of the MUSIM status information is AMF300 (both AMF300-1 and AMF300-2) and / or gNB200 (both gNB200-1 and gNB200-2).
- the AMF300-1 may transfer the MUSIM status information received from the UE 100 to the gNB200-1.
- the gNB200-1 may transfer the MUSIM status information received from the UE 100 to the AMF300-1.
- the gNB200-1 may store the MUSIM status information received from the UE 100 as a part of the UE context of the UE 100.
- the UE 100 transmits the MUSIM status information together with the information indicating that the registration to the NW40-1 and the registration to the NW40-2 belong to the same UE100. You may. Such information may indicate, for example, that the temporary subscriber identifiers (such as 5G-S-TMSI) assigned by both NW40s belong to the same UE 100.
- the temporary subscriber identifiers such as 5G-S-TMSI
- the UE100 When the destination of the MUSIM status information is gNB200 and the UE 100 is in the RRC connected state to both the NW40-1 and the NW40-2, the UE100, together with the MUSIM status information, makes an RRC connection with the NW40-1 and a NW40.
- Information indicating that the RRC connection with -2 belongs to the same UE 100 may be transmitted. Such information may indicate, for example, that the network temporary identifiers (such as C-RNTI) assigned by both NW40s belong to the same UE 100.
- the UE 100 in the MUSIM state may transmit information indicating that fact to the other.
- the timing information specifies the execution timing, which is the timing for executing the communication in NW40-2, but this is not the case.
- the timing information may be information indicating the timing at which communication with NW40-1 is possible.
- the NW40-1 can schedule communication with the UE 100 at the timing at which the communication is possible.
- a program for causing a computer to execute each process according to the above-described embodiment may be provided.
- the program may be recorded on a computer-readable medium.
- Computer-readable media can be used to install programs on a computer.
- 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, but may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.
- UE 110 Receiver unit 120: Transmitter unit 130: Control unit 200: gNB 210: Transmitter 220: Receiver 230: Control 260: Backhaul communication unit 300: AMF 310: Control unit 320: Backhaul communication unit
Abstract
Description
一実施形態に係る移動通信システムの構成について説明する。一実施形態に係る移動通信システムは3GPPの5Gシステムであるが、移動通信システムには、3GPPのLTE(Long Term Evolution)が少なくとも部分的に適用されてもよい。
上述したようなシステム構成を前提として、第1実施形態について説明する。
ページング受信機会は、RRCアイドル状態又はRRCインアクティブ状態におけるUE100がNW40-2からのページングを監視するタイミングである。
ユニキャストスケジューリング機会は、RRCコネクテッド状態にあるUE100とNW40-2(gNB200-2)との間のユニキャストデータの送受信がスケジュールされる候補タイミングである。
MBSスケジューリング機会は、NW40-2からUE100へのMBSデータの送信がスケジュールされる候補タイミングである。MBSは、NW40-2からUE100に対してブロードキャスト又はマルチキャスト、すなわち、1対多(PTM:Point To Multipoint)でのデータ送信を行うサービスである。MBSは、MBMS(Multimedia Broadcast and Multicast Service)と呼ばれてもよい。MBSデータとは、MBSにより送信されるデータをいう。
サイドリンクスケジューリング機会は、NW40-2においてUE100によるサイドリンク通信がスケジュールされる候補タイミングである。サイドリンク通信は、ネットワークノード(例えば、gNB200)を経由せずに、近くのUE100間で行われる通信である。サイドリンク通信は、UE100が他のUE100にデータを送信するサイドリンク送信と、UE100が他のUE100からのデータを受信するサイドリンク受信との少なくとも1つを含む。
図8は、第1実施形態の動作例1の動作を示す図である。
動作例2について、動作例1との相違点を主として説明する。動作例2は、タイミング情報の送信許可に関する動作例である。
動作例3について、動作例1との相違点を主として説明する。動作例3は、優先ネットワークに関する動作例である。
動作例4について、動作例1との相違点を主として説明する。動作例4は、UEコンテキストに関する動作例である。
第2実施形態は、音声通信に関する動作例である。
第3実施形態は、NW40-1とNW40-2が同一の通信事業者に属することを前提とする。
上述した各実施形態を別個独立に実施する場合に限らず、2以上の実施形態を組み合わせてもよい。
110 :受信部
120 :送信部
130 :制御部
200 :gNB
210 :送信部
220 :受信部
230 :制御部
260 :バックホール通信部
300 :AMF
310 :制御部
320 :バックホール通信部
Claims (6)
- 第1の移動ネットワークに対応する第1の加入者識別モジュール(SIM)と、第2の移動ネットワークに対応する第2のSIMとを有するユーザ装置を用いる通信制御方法であって、
前記ユーザ装置が、所定のイベントが発生することに応じて、前記第2の移動ネットワークにおける通信を実行するタイミングである実行タイミングを示すタイミング情報を、前記第1の移動ネットワークに送信することを有し、
前記所定のイベントは、前記第2の移動ネットワークにおいて前記ユーザ装置がRRC(Radio Resource Control)コネクテッド状態からRRCインアクティブ状態に遷移すること、又は、前記第1の移動ネットワークにおいて前記ユーザ装置がRRCコネクテッド状態に遷移することである、
通信制御方法。 - 前記タイミング情報は、前記実行タイミングに対応する前記第1の移動ネットワークのタイミングを特定する情報を含む
請求項1に記載の通信制御方法。 - 前記ユーザ装置は、前記第1の移動ネットワークにおいて希望するRRC状態がRRCアイドル状態であることに応じて、前記第1の移動ネットワークにおけるコアネットワーク装置を前記タイミング情報の送信先として決定することをさらに有する
請求項1に記載の通信制御方法。 - 前記ユーザ装置が、前記第1の移動ネットワークから、前記タイミング情報の送信可否を示す情報を受信することをさらに有し、
前記タイミング情報を送信することは、前記タイミング情報の送信が許可されることを前記情報が示す場合、前記タイミング情報を送信することを含む
請求項1に記載の通信制御方法。 - 前記ユーザ装置が、前記第1の移動ネットワークと前記第2の移動ネットワークとの一方を優先ネットワークとして決定し、他方を非優先ネットワークとして決定することと
前記タイミング情報を送信することは、前記第1の移動ネットワークが前記非優先ネットワークとして決定される場合、前記タイミング情報を送信することを含む
請求項1に記載の通信制御方法。 - 前記第1の移動ネットワークにおける基地局が、前記タイミング情報を受信することと、
前記基地局が、前記タイミング情報を前記ユーザ装置のUE(User Equipment)コンテキストとして記憶することと、をさらに有する
請求項1に記載の通信制御方法。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180073016.3A CN116420358A (zh) | 2020-08-31 | 2021-08-25 | 通信控制方法 |
JP2022545686A JP7319474B2 (ja) | 2020-08-31 | 2021-08-25 | 通信制御方法 |
EP21861644.9A EP4192039A4 (en) | 2020-08-31 | 2021-08-25 | COMMUNICATION CONTROL METHOD |
US18/175,505 US20230209534A1 (en) | 2020-08-31 | 2023-02-27 | Communication control method |
JP2023118199A JP2023145566A (ja) | 2020-08-31 | 2023-07-20 | 通信制御方法、ユーザ装置及びプロセッサ |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2020146146 | 2020-08-31 | ||
JP2020-146146 | 2020-08-31 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/175,505 Continuation US20230209534A1 (en) | 2020-08-31 | 2023-02-27 | Communication control method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022045222A1 true WO2022045222A1 (ja) | 2022-03-03 |
Family
ID=80355331
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/031249 WO2022045222A1 (ja) | 2020-08-31 | 2021-08-25 | 通信制御方法 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20230209534A1 (ja) |
EP (1) | EP4192039A4 (ja) |
JP (2) | JP7319474B2 (ja) |
CN (1) | CN116420358A (ja) |
WO (1) | WO2022045222A1 (ja) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2020507971A (ja) * | 2017-02-03 | 2020-03-12 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | コンテキストフェッチなしの無線リソース制御再開 |
JP2020146146A (ja) | 2019-03-12 | 2020-09-17 | 株式会社三洋物産 | 遊技機 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
PL2807897T3 (pl) * | 2012-01-23 | 2017-10-31 | Deutsche Telekom Ag | Sposób stosowania wyposażenia użytkownika z pierwszą publiczną naziemną siecią telefonii komórkowej oraz z drugą publiczną naziemną siecią telefonii komórkowej, wyposażenie użytkownika, program oraz produkt w postaci programu komputerowego |
WO2013170140A2 (en) * | 2012-05-10 | 2013-11-14 | Interdigital Patent Holdings, Inc. | Paging and system information broadcast handling in virtualized networks |
WO2016095078A1 (en) | 2014-12-15 | 2016-06-23 | Qualcomm Incorporated | Dual active connections over single radio user equipment |
CN110839264B (zh) * | 2018-08-16 | 2021-03-23 | 维沃移动通信有限公司 | 通信方法和设备 |
-
2021
- 2021-08-25 EP EP21861644.9A patent/EP4192039A4/en active Pending
- 2021-08-25 CN CN202180073016.3A patent/CN116420358A/zh active Pending
- 2021-08-25 JP JP2022545686A patent/JP7319474B2/ja active Active
- 2021-08-25 WO PCT/JP2021/031249 patent/WO2022045222A1/ja active Application Filing
-
2023
- 2023-02-27 US US18/175,505 patent/US20230209534A1/en active Pending
- 2023-07-20 JP JP2023118199A patent/JP2023145566A/ja active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2020507971A (ja) * | 2017-02-03 | 2020-03-12 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | コンテキストフェッチなしの無線リソース制御再開 |
JP2020146146A (ja) | 2019-03-12 | 2020-09-17 | 株式会社三洋物産 | 遊技機 |
Non-Patent Citations (5)
Title |
---|
"TR 22.834 V17.1.0", 3GPP TECHNICAL REPORT TR 22.834, September 2019 (2019-09-01), Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Specs/archive/22seiies/22.834/22834-h10.zip> |
3GPP TECHNICAL SPECIFICATION TS36.304 |
3GPP TECHNICAL SPECIFICATION TS38.304 |
ERICSSON: "Paging collision avoidance", 3GPP DRAFT; R2-2007603, vol. RAN WG2, 6 August 2020 (2020-08-06), pages 1 - 5, XP051911076 * |
See also references of EP4192039A4 |
Also Published As
Publication number | Publication date |
---|---|
EP4192039A4 (en) | 2024-01-10 |
US20230209534A1 (en) | 2023-06-29 |
CN116420358A (zh) | 2023-07-11 |
JP2023145566A (ja) | 2023-10-11 |
JPWO2022045222A1 (ja) | 2022-03-03 |
JP7319474B2 (ja) | 2023-08-01 |
EP4192039A1 (en) | 2023-06-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10362627B2 (en) | Paging method and apparatus for communication of M2M/MTC device operating in high power saving reception mode in a mobile communication system, and system thereof | |
CN111264080B (zh) | 在无线通信系统中触发发送载波选择的方法和设备 | |
RU2768363C2 (ru) | Способ передачи данных и устройство | |
US10098162B2 (en) | Mobile communication system, user terminal, base station, processor, and communication control method | |
EP3354061B1 (en) | Method for transmitting a buffer status report in a d2d communication system and device therefor | |
US20150312821A1 (en) | Mobile communication system, user terminal, base station, processor, and communication control method | |
US20180249524A1 (en) | Method for handling an id collision for a d2d communication system and device therefor | |
US10939455B2 (en) | Method for allocating priorities to a logical channel group implicitly in a D2D communication system and device therefor | |
JP2019134476A (ja) | 基地局 | |
US20180255559A1 (en) | Method for transmitting a priority list reporting in a d2d communication system and device therefor | |
JP2023053106A (ja) | 通信制御方法、ユーザ装置、プロセッサ及びネットワーク装置 | |
US20230403626A1 (en) | Method and apparatus for relay communication | |
US20230413229A1 (en) | Method and Apparatus for Relay Communication | |
WO2022062846A1 (en) | Method and apparatus for path switch | |
US10667286B2 (en) | Method for selecting prose destinations or SL grants in a D2D communication system and device therefor | |
WO2022028277A1 (en) | Methods and apparatuses for resource allocation to terminal device | |
WO2022045222A1 (ja) | 通信制御方法 | |
US10952121B2 (en) | Method and apparatus for selecting a relay user equipment | |
WO2022197228A1 (en) | Methods, node, ue and computer readable media for aligning partial sensing configuration with drx configuration |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21861644 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022545686 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021861644 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2021861644 Country of ref document: EP Effective date: 20230227 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |