WO2022203003A1 - 端末、基地局及び無線通信方法 - Google Patents
端末、基地局及び無線通信方法 Download PDFInfo
- Publication number
- WO2022203003A1 WO2022203003A1 PCT/JP2022/014000 JP2022014000W WO2022203003A1 WO 2022203003 A1 WO2022203003 A1 WO 2022203003A1 JP 2022014000 W JP2022014000 W JP 2022014000W WO 2022203003 A1 WO2022203003 A1 WO 2022203003A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- edrx
- rrc
- terminal
- message
- base station
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 44
- 238000004891 communication Methods 0.000 title claims description 42
- 230000005540 biological transmission Effects 0.000 claims description 12
- 238000010586 diagram Methods 0.000 description 24
- 238000012545 processing Methods 0.000 description 22
- 230000007704 transition Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 12
- 230000008859 change Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- CIWBSHSKHKDKBQ-JLAZNSOCSA-N Ascorbic acid Chemical compound OC[C@H](O)[C@H]1OC(=O)C(O)=C1O CIWBSHSKHKDKBQ-JLAZNSOCSA-N 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 238000007726 management method Methods 0.000 description 5
- 238000012544 monitoring process Methods 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 4
- 230000007774 longterm Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 239000000969 carrier Substances 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 241000699670 Mus sp. Species 0.000 description 1
- 241000700159 Rattus Species 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012508 change request Methods 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/005—Transmission of information for alerting of incoming communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
- H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
- H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
- H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/02—Arrangements for increasing efficiency of notification or paging channel
-
- 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
Definitions
- the present disclosure relates to terminals, base stations, and wireless communication methods.
- LTE Long Term Evolution
- RAT Radio Access Technology
- NR New Radio
- Non-Patent Document 1 LTE (Long Term Evolution) considers the existence of terminals whose power consumption is further limited, such as IoT (Internet of Things) equipment, and limits the period during which wireless signals can be received to reduce power consumption.
- IoT Internet of Things
- eDRX extended discontinuous reception
- NR Radio Resource Control
- RRC Radio Resource Control
- One of the purposes of the present disclosure is to provide a terminal, a base station, and a wireless communication method that can notify a terminal of eDRX setting information applied to the terminal in the RRC inactive state.
- a terminal is a terminal that communicates with a base station, and is determined by the base station and receives an RRC message including eDRX (extended DRX) parameters for RRC inactive state. and a control unit that controls to monitor control channel candidates in the paging search space set by the paging search space information in the RRC inactive state, based on the eDRX parameters included in the RRC message. .
- eDRX extended DRX
- a terminal capable of notifying a terminal of eDRX setting information applied to the terminal in the RRC inactive state.
- FIG. 1 is a diagram showing an example of an outline of a wireless communication system according to this embodiment.
- FIG. 2 is a diagram illustrating an example of state transition of a terminal.
- FIG. 3 is a diagram for explaining the DRX operation during paging.
- FIG. 4 is a diagram for explaining the eDRX operation during paging.
- FIG. 5 is a diagram illustrating an example of a processing procedure when eDRX parameters for the inactive state are managed by the core network.
- FIG. 6 is a diagram illustrating an example of a processing procedure when setting information related to eDRX for inactive state is managed by a base station.
- FIG. 7 is a diagram illustrating a specification change example of the 3GPP specifications.
- FIG. 8 is a diagram showing an example of specification change of the 3GPP specifications.
- FIG. 9 is a diagram showing a specification change example of the 3GPP specifications.
- FIG. 10 is a diagram showing a specification change example of the 3GPP specifications.
- FIG. 11 is a diagram showing a specification change example of the 3GPP specifications.
- FIG. 12 is a diagram illustrating an example of the hardware configuration of each device within the wireless communication system.
- FIG. 13 is a diagram illustrating an example of a functional configuration of a terminal;
- FIG. 14 is a diagram illustrating an example of a functional configuration of a base station;
- FIG. 1 is a diagram showing an example of an overview of a wireless communication system according to this embodiment.
- the wireless communication system 1 may include a terminal 10, a base station 20, and a core network 30.
- the numbers of terminals 10 and base stations 20 shown in FIG. 1 are merely examples, and are not limited to the numbers shown.
- NR Radio Access Technology: RAT
- NR Radio Access Technology: RAT
- LTE Long Term Evolution
- LTE-Advanced Long Term Evolution-Advanced
- 6th generation or later RAT etc.
- Various RATs are available.
- the terminal 10 is, for example, a predetermined terminal or device such as a smartphone, a personal computer, an in-vehicle terminal, an in-vehicle device, a stationary device, a telematics control unit (TCU), or the like.
- Terminal 10 may also be called a User Equipment (UE), a Mobile Station (MS), a User Terminal, a Radio apparatus, a subscriber terminal, an access terminal, and so on.
- the terminal 10 may be mobile or stationary.
- the terminal 10 is configured to be able to communicate using, for example, NR as the RAT.
- Release 17 of NR it is lower than terminals for high-speed large capacity (enhanced Mobile Broadband: eMBB), ultra-reliable and low latency Communications (URLLC) introduced in Release 15 or 16 It is being considered to support functions for terminals that assume performance and price ranges.
- the terminal is also called a reduced capability (RedCap) terminal, device, etc., and is used for, for example, industrial wireless sensors, video surveillance, wearable devices, etc. is assumed.
- RedCap terminals are assumed to have higher performance than terminals for low power wide area communication (Low Power Wide Area: LPWA), and the carriers used by RedCap terminals are, for example, 20MHz, 50MHz or 100MHz bandwidth. There may be.
- LPWA includes, for example, Category 1, Long Term Evolution for Machine-type-communication (LTE-M) and Narrow Band IoT (NB-IoT) that operate on LTE RAT.
- LTE-M Long Term Evolution for Machine-type-communication
- NB-IoT Narrow Band IoT
- the maximum bandwidth of Category 1 is 20 MHz
- the maximum bandwidth of LTE-M is 1.4 MHz (6 RB)
- the maximum bandwidth of NB-IoT is 180 kHz (1 RB).
- the terminal 10 includes a RedCap terminal and a terminal for LPWA.
- the base station 20 forms one or more cells C and communicates with the terminal 10 using the cell C.
- Cell C may be interchangeably referred to as serving cell, carrier, component carrier (CC), and the like.
- Base station 20 includes gNodeB (gNB), en-gNB, Next Generation-Radio Access Network (NG-RAN) node, eNB, low-power node, Central Unit (CU), Distributed Unit (DU) , gNB-DU, Remote Radio Head (RRH), Integrated Access and Backhaul/Backhauling (IAB) node, etc.
- the base station 20 is not limited to one node, and may be composed of a plurality of nodes (for example, a combination of a lower node such as DU and an upper node such as CU).
- the core network 30 is, for example, an NR-compatible core network (5G Core Network: 5GC), but is not limited to this.
- a device on the core network 30 (hereinafter also referred to as “core network device”) performs mobility management such as paging and location registration of the terminal 10 .
- a core network device may be connected to the base station 20 via a predetermined interface (eg, S1 or NG interface).
- the core network device includes, for example, AMF (Access and Mobility Management Function) for managing information related to access and mobility management, SMF (Session Management Function) for session management, and User Plane Function (UPF) for U-plane transmission control. , NSSF (Network Slice Selection Function) for managing network slices.
- AMF Access and Mobility Management Function
- SMF Session Management Function
- UPF User Plane Function
- NSSF Network Slice Selection Function
- the terminal 10 receives downlink (DL) signals from the base station 20 and/or transmits uplink (UL) signals.
- Terminal 10 may be configured with one or more carriers. Each carrier has a bandwidth of, for example, 5 MHz to 400 MHz.
- One carrier may be configured with one or more bandwidth parts (BWP).
- BWP bandwidth parts
- the RRC state of the terminal 10 includes an RRC idle state (hereinafter referred to as “idle state”), an RRC inactive state (hereinafter referred to as “inactive state”), and an RRC connected state (hereinafter referred to as “connected state”). ”).
- FIG. 2 is a diagram showing an example of state transition of the terminal 10.
- the idle state is a state in which an RRC connection is not established between the terminal 10 and the base station 20, and is also called RRC_IDLE, idle mode, RRC idle mode, or the like.
- the idle state terminal 10 camps on a cell C selected by cell selection and/or cell reselection (hereinafter referred to as "cell selection/reselection"), and broadcasts on the cell C. receive system information
- the terminal 10 in the idle state transitions to the connected state when the RRC connection is established.
- the inactive state is a state in which an RRC connection is established but suspended, and is also called RRC_INACTIVE, inactive mode, RRC inactive mode, and the like.
- the inactive state does not exist in LTE and is a newly defined RRC state in NR.
- a terminal 10 in an inactive state camps on a cell C selected by cell selection/reselection and receives system information broadcast on the cell C.
- FIG. Like the idle state, the inactive state enables power saving of the terminal 10, but unlike the idle state, the terminal 10, the base station 20, and the core network 30 hold the RRC context and the NAS context. is doing.
- a RAN Notification Area (RAN Notification Area: RNA), which is an area obtained by subdividing a TA (Tracking Area), is newly defined. manages the RAN notification area that
- NR introduces a technique called “RAN paging” that performs paging processing in units of RAN notification areas, which is used when calling a terminal 10 that is in an inactive state.
- RAN paging paging signals are simultaneously transmitted from a plurality of base stations 20 forming a RAN notification area in which terminals 10 in the inactive state exist. The terminal 10 in the inactive state that has received the paging signal resumes the RRC connection and transitions to the connected state.
- the connected state is a state in which the RRC connection is established, and is also called RRC_CONNECTED, connected mode, RRC connected mode, and the like.
- Terminal 10 in the connected state monitors PDCCH (Physical Downlink Control Channel) and controls reception of PDSCH (Physical Downlink Shared Channel) based on detected DCI (Downlink Control Information).
- PDCCH Physical Downlink Control Channel
- PDSCH Physical Downlink Shared Channel
- DCI Downlink Control Information
- eDRX enhanced DRX
- a subframe with a time length of 1 ms, a radio frame with a time length of 10 ms, and a hyperframe with a time length of 10.24 seconds is stipulated.
- the position of the radio frame is represented by an SFN (System Frame Number) from 0 to 1023.
- SFN System Frame Number
- hyperframes with a length of SFN numbered 0 to 1023 that is, 10.24 seconds
- a hyperframe is represented by an H-SFN (Hyper-SFN (System Frame Number)) from 0 to 1023 numbers.
- FIG. 3 is a diagram for explaining the DRX (Discontinuous Reception) operation during paging.
- the terminal 10 in idle state receives a paging signal by monitoring downlink control channel candidates (PDCCH candidates) during a period called PO (Paging Occasion). While the terminal 10 operates according to the DRX setting, the base station 20 transmits the paging signal during the PO period and does not transmit the paging signal during other periods.
- the terminal 10 that receives the paging signal within the PO period establishes communication with the base station 20 and transitions to the connected state. There is one PO per DRX cycle.
- the DRX cycle has a maximum of 2.56 seconds.
- FIG. 4 is a diagram for explaining the eDRX operation during paging.
- the terminal 10 in an idle state receives a paging signal by monitoring downlink control channel candidates during a PO period within a period called PTW (Paging Time Window).
- PTW Paging Time Window
- One PTW is set in a hyperframe called PH (Paging Hyperframe).
- PH Paging Hyperframe
- the eDRX cycle is up to 2.91 hours (i.e. 1024 hyperframes) for terminals 10 that are NB-IoT and up to about 44 minutes (i.e. 256 hyperframes) for terminals 10 that are not NB-IoT. be.
- the base station 20 While the terminal 10 is operating according to the eDRX settings, the base station 20 transmits paging signals during the PTW period and the PO period, and does not transmit the paging signal during other periods.
- the terminal 10 that has received the paging signal establishes communication with the base station 20 and transitions to the connected state.
- PH H-SFN that satisfies Equation 1 below.
- H-SFN mod TeDRX,H (UE_ID_H mod TeDRX,H) "TeDRX, H” indicates an eDRX cycle and is set with a length that is an integral multiple of the hyperframe.
- UE_ID_H is the most significant 10 or 12 bits of a hashed ID determined based on S-TMSI (SAE Temporary Mobile Subscriber Identity) or 5G-S-TMIS (5G S-Temporary Mobile Subscriber Identity).
- the SFN which is the PTW start position (PTW_start) (start timing), is expressed by Equations 2 and 3 below.
- a processing procedure is defined for the terminal 10 to request the core network 30 to notify setting information regarding eDRX using NAS messages. Therefore, by applying this processing procedure to NR, it is possible for the terminal 10 to request the core network 30 to notify (set) the eDRX parameters applied to the terminal 10 in the idle state.
- the current 3GPP does not define a processing procedure for the terminal 10 to request notification (setting) of the eDRX parameters applied to the inactive state (second issue).
- the eDRX parameters applied to the terminal 10 in the inactive state can be notified to the terminal 10 using NAS messages or RRC messages. Further, in the present embodiment, in order to solve the second problem, the terminal 10 sets the eDRX parameters applied to the terminal 10 in the inactive state to the base station 20 in order to request the eDRX operation in the inactive state. Alternatively, transmission to the core network 30 is possible.
- eDRX parameters may mean only parameters that determine the eDRX operation, such as the eDRX cycle and PTW. It may mean that it also includes parameters that determine the DRX behavior.
- eDRX parameters for inactive state refer to eDRX parameters applied to the terminal 10 in inactive state.
- eDRX parameters for idle state mean eDRX parameters applied to the terminal 10 in idle state.
- ⁇ Procedure for realizing eDRX in an inactive state there are two possible methods: a method in which the core network 30 manages eDRX parameters for inactive state, and a method in which the base station 20 manages the eDRX parameters.
- the process of paging performed by the terminal 10 may be the same as the process described in the conventional eDRX technology, unless otherwise specified.
- FIG. 5 is a diagram showing an example of a processing procedure when the core network 30 manages the eDRX parameters for the inactive state. Note that the core network 30 is assumed to be AMF, for example, but is not limited to this.
- a terminal 10 desiring to enable eDRX transmits a Registration Request message including "eDRX parameters" indicating the desired eDRX operation to the core network 30 (S100).
- eDRX parameters indicating the desired eDRX operation to the core network 30 (S100).
- a terminal 10 desiring eDRX operation with an eDRX cycle of 2 hyperframes and a PTW of 1 second may set eDRX parameters indicating that the eDRX cycle is 2 hyperframes and the PTW is 1 second. to the core network 30.
- the terminal 10 may include "eDRX parameters" indicating the eDRX operation for the idle state and "eDRX parameters" indicating the eDRX operation for the inactive state in the registration request message.
- the terminal 10 desires eDRX operation with an eDRX cycle of 8 hyperframes and a PTW of 2 seconds in the idle state, and an eDRX cycle of 2 hyperframes and a PTW in the inactive state.
- the terminal 10 sets the "eDRX parameters for idle state” indicating that the eDRX cycle in the idle state is 8 hyperframes and the PTW is 2 seconds, and the eDRX cycle in the inactive state is 2 hyperframes. and the PTW is 1 second to the core network 30 .
- the terminal 10 may set the eDRX parameters for the inactive state to the eDRX parameters for the idle state in the registration request message.
- Information indicating the same value as the parameter may be explicitly or implicitly included. For example, if the registration request message includes eDRX parameters for the idle state but does not include eDRX parameters for the inactive state (i.e., if the eDRX parameters are "absent"), the inactive It may be implied that the eDRX parameters for state are the same as the eDRX parameters for idle state.
- the core network 30 determines eDRX parameters for the idle state and eDRX parameters for the inactive state based on the registration request received from the terminal 10 (S101).
- the core network 30 considers, for example, the eDRX parameters received from the terminal 10, the network load, the attributes of the terminal 10, and/or the capabilities of the terminal 10, and eDRX parameters for idle state to be set in the terminal 10, Determine the eDRX parameters for the inactive state.
- the core network 30 may determine the eDRX parameters to be set in the terminal 10 to be the same values as the eDRX parameters included in the registration request, or may determine values different from the eDRX parameters included in the registration request. may
- the core network 30 sends a Registration Accept message including the determined eDRX parameters for the idle state and the eDRX parameters for the inactive state to the terminal 10. (S102). Note that if the determined eDRX parameters for the idle state and the eDRX parameters for the inactive state are the same, the core network 30 adds the eDRX parameters for the inactive state to the eDRX parameters for the idle state in the registration response message. Information indicating the same value may be explicitly or implicitly included.
- the registration response message contains eDRX parameters for the idle state but does not contain eDRX parameters for the inactive state (that is, if the eDRX parameters are 'absent'), the inactive It may be implied that the eDRX parameters for state are the same as the eDRX parameters for idle state.
- the terminal 10 sets the eDRX parameters for the idle state and the eDRX parameters for the inactive state included in the registration response message (stores the eDRX parameters in the storage device 12) (S103).
- the registration response message explicitly or implicitly includes information indicating that the eDRX parameter for the inactive state is the same value as the eDRX parameter for the idle state
- the terminal 10 The eDRX parameters for idle state may be recognized as having the same values as the eDRX parameters for idle state. In this case, the terminal 10 may set the eDRX parameter for inactive state to the same value as the eDRX parameter for idle state.
- the registration request message and the registration acceptance message described above are examples, and any message may be used as long as it is a NAS message.
- the terminal 10 monitors control channel candidates in the paging search space with the PTW in the PH indicated by the set eDRX parameters for the idle state. Also, when transmitting a paging message to the terminal 10 in the idle state, the base station 20 transmits DCI in the paging search space with the PTW at the PH indicated by the eDRX parameters for the idle state set in the terminal 10. . Also, when the terminal 10 is in the inactive state, the terminal 10 monitors control channel candidates in the paging search space with the PTW on the PH indicated by the set eDRX parameters for the inactive state.
- the base station 20 uses the PTW at the PH indicated by the eDRX parameters for the inactive state set in the terminal 10 to transmit DCI in the paging search space. Send.
- the core network 30 can determine the eDRX parameters for the inactive state and notify the terminal 10 of them. Also, the terminal 10 desiring to enable eDRX can request the core network 30 to notify (set) eDRX parameters for the inactive state. In addition, in the processing procedure described above, if the eDRX parameters for the inactive state are the same as the eDRX parameters for the idle state, for example, the eDRX parameters for the inactive state are omitted. This makes it possible to reduce the amount of data in the NAS message.
- FIG. 6 is a diagram showing an example of a processing procedure when setting information regarding eDRX for inactive state is managed by the base station 20.
- the terminal 10 starting the registration process with the core network 30 transmits an RRC setup request (RRCSetupRequest) message to the base station 20 in order to establish an RRC connection with the base station 20 (S200).
- RRC setup request RRCSetupRequest
- the base station 20 Upon receiving the RRC setup request, the base station 20 transmits an RRC setup (RRCSetup) message (S201).
- the terminal 10 transmits an RRC setup complete (RRC Setup Complete) message to the base station 20.
- the RRC setup complete message includes a Registration Request message, which is a NAS message to be sent to the core network 30 (S202).
- the base station 20 extracts the registration request message included in the RRC setup complete message and transmits (transfers) it to the core network 30 (S203).
- the terminal 10 desiring to enable eDRX transmits a registration request message including an "eDRX parameter" indicating the idle state eDRX operation desired to be set in the processing procedure of step S202.
- the core network 30 determines eDRX parameters for the idle state based on the registration request message received from the terminal 10 (S204).
- the core network 30, for example, considers the eDRX parameters received from the terminal 10, the load of the network, the attributes of the terminal 10 and/or the capabilities of the terminal 10, and determines the idle state eDRX parameters to be set in the terminal 10. .
- the core network 30 may determine the eDRX parameters to be set in the terminal 10 to be the same values as the eDRX parameters desired by the terminal 10, or to values different from the eDRX parameters desired by the terminal 10. may
- the core network 30 transmits a Registration Accept message including the determined eDRX parameters for the idle state to the terminal 10 (S205).
- the terminal 10 sets the eDRX parameters for the idle state and the eDRX parameters for the inactive state included in the registration response message (stores the eDRX parameters in the storage device 12) (S206).
- the core network 30 transmits an initial context setup request message to the base station 20 in order to notify the base station 20 of the information necessary for the terminal 10 to communicate (S207).
- the core network 30 transmits the idle state eDRX parameters included in the initial context setup request in order to notify the base station 20 of the idle state eDRX parameters determined by the core network 30 .
- the eDRX parameters for idle state are included in the initial context setup request. It may be part of Core Network Assistance Information for RRC INACTIVE.
- a message transmitted and received between the base station 20 and the core network 30 is called an N2 message.
- the N2 message includes a UE context modification message, a handover resource allocation message, a path change request (Path switch request) message, and the like.
- the core network 30 may send these N2 messages to the base station 20 including the eDRX parameters for idle state.
- the base station 20 can recognize the eDRX parameters for the idle state desired by the terminal 10 .
- RRC messages are transmitted and received as necessary (S208).
- RRC messages transmitted from the terminal 10 to the base station 20 include an RRC reconfiguration complete (RRCReconfigurationComplete) message, an RRC reestablishment request (RRCReestablishmentRequest) message, an RRC reestablishment complete (RRCReestablishmentComplete) message, an RRC resumption request (RRCResumeRequest/ RRCResumeRequest1) message, RRC Resume Complete message, and the like.
- the terminal 10 desiring to enable eDRX transmits to the base station 20 "eDRX parameters" indicating the eDRX operation for the inactive state, which the terminal 10 desires to set.
- the terminal 10 may include the eDRX parameters in an RRC setup request message (S200) or an RRC setup complete message (S202) and transmit them to the base station 20.
- the terminal 10 may include it in an RRC reconfiguration complete message, RRC re-establishment request message, RRC re-establishment complete message, RRC resumption request message, RRC resumption completion message, etc. (S208) and transmit it to the base station 20. good.
- the terminal 10 may include the eDRX parameters for the inactive state in the RRC setup complete message, and include the eDRX parameters for the idle state in the Registration Request message included in the RRC setup complete message. Since the transmission of the eDRX parameters for the idle state and the transmission of the eDRX parameters for the inactive state can be performed at the same timing, the processing logic of the terminal 10 can be simplified.
- the terminal 10 desires eDRX operation with an eDRX cycle of 2 hyperframes and a PTW of 1 second in the inactive state.
- the terminal 10 transmits to the base station 20 an “eDRX parameter for inactive state” indicating that the eDRX cycle in the inactive state is 2 hyperframes and the PTW is 2 seconds.
- the terminal 10 may set the eDRX parameters for the inactive state to the eDRX parameters for the idle state in the RRC message.
- Information indicating that the value is the same as the value may be included explicitly or implicitly.
- the eDRX parameters for the inactive state there is information indicating a request for "eDRX parameters" for the inactive state (for example, the name of the information element (Information Element) that stores the eDRX parameters), but the specific eDRX parameters is not included (i.e., the eDRX parameter is "absent"), it may be implied that the eDRX parameters for the inactive state are the same as the eDRX parameters for the idle state.
- Information Element Information Element
- the base station 20 determines eDRX parameters for inactive state to be set in the terminal 10 based on the eDRX parameters for inactive state received from the terminal 10 (S209).
- the base station 20 for example, considers the eDRX parameters received from the terminal 10, the load of the radio network, the attributes of the terminal 10 and/or the capabilities of the terminal 10, and determines the inactive eDRX parameters to be set for the terminal 10. do.
- the base station 20 may determine the eDRX parameters to be set in the terminal 10 to be the same values as the eDRX parameters desired by the terminal 10, or to values different from the eDRX parameters desired by the terminal 10. may
- the base station 20 transmits an RRC release message (RRC Release) message including the determined eDRX parameters for the inactive state to the terminal 10 (S210). ). Note that if the determined eDRX parameters for the idle state and the eDRX parameters for the inactive state are the same, the base station 20 adds the eDRX parameters for the inactive state to the eDRX parameters for the idle state in the RRC release message. Information indicating the same value may be explicitly or implicitly included.
- the RRC release message contains information indicating that "eDRX parameters" for the inactive state are set (for example, the name of the information element that stores the eDRX parameters), but does not contain specific eDRX parameters. case (ie, the eDRX parameter is "absent"), it may be implied that the eDRX parameters for the inactive state are the same as the eDRX parameters for the idle state.
- the terminal 10 sets the eDRX parameters for inactive state included in the RRC release message (stores the eDRX parameters in the storage device 12) (S211). Note that when the RRC release message explicitly or implicitly includes information indicating that the eDRX parameters for the inactive state are the same as the eDRX parameters for the idle state, the terminal 10 The eDRX parameters for idle state may be recognized as having the same values as the eDRX parameters for idle state. In this case, the terminal 10 may set the eDRX parameter for inactive state to the same value as the eDRX parameter for idle state.
- the terminal 10 monitors the control channel candidate in the paging search space with the PTW on the PH indicated by the set eDRX parameter for the idle state or the eDRX parameter for the inactive state, as in the description of FIG. . Also, when transmitting a paging message, the base station 20 transmits DCI in the paging search space with the PTW on the PH indicated by the eDRX parameter for idle state or the eDRX parameter for inactive state.
- the base station 20 When setting the determined eDRX parameters in the terminal 10, the base station 20 adds the eDRX parameters for the inactive state to another RRC message transmitted from the base station 20 to the terminal 10 instead of the RRC release message. may be included.
- RRC messages for example, RRC reconfiguration (RRCReconfiguration) message, RRC reestablishment (RRCReestablishment) message, RRC resume request (RRCResumeRequest/RRCResumeRequest1) message, RRC resume (RRCResume) message, RRC setup (RRCSetup) message, etc. mentioned.
- the base station 20 can determine the eDRX parameters for the inactive state and notify the terminal 10 of them. Also, the terminal 10 desiring to enable eDRX can request the base station 20 to notify (set) eDRX parameters for the inactive state.
- the base station 20 includes eDRX parameters for the inactive state in the RRC release message that is transmitted when the terminal 10 transitions from the connected state to the inactive state.
- the base station 20 needs to notify the terminal 10 of the eDRX parameters only when it is necessary to set the eDRX parameters for the inactive state, so radio resources can be used efficiently.
- the terminal 10 since the terminal 10 does not need to store the eDRX parameters for the inactive state when not transitioning to the inactive state, the memory capacity of the terminal 10 can be reduced.
- the eDRX parameters when the eDRX parameters are included in an RRC message other than the RRC release message, depending on the timing of transition to the inactive state, the eDRX parameters may not be set in time, and a time lag may occur before the transition to the inactive state is actually completed. may occur. However, by including the eDRX parameters for the inactive state in the RRC release message, it is possible to eliminate this time lag and quickly transition to the inactive state.
- the eDRX parameters for the inactive state are the same as the eDRX parameters for the idle state, the eDRX parameters for the inactive state can be omitted. This avoids transmission of duplicated data, making it possible to reduce the amount of data in the RRC message.
- the terminal 10, base station 20, and core network 30 may use eDRX parameters similar to those in LTE. That is, PH may be determined according to Equation 1, the start position of PTW may be determined according to Equations 2 and 3, and the end position of PTW may be determined according to Equation 4.
- the eDRX parameters include the eDRX cycle (TeDRX, H in Equations 1 and 3) and the length of time of the PTW (L in Equation 4).
- the terminal 10, the base station 20, and the core network 30 include predetermined information regarding the setting of the PTW start position in the eDRX parameters, so that the PTW start position can be set more flexibly than in LTE. You may do so.
- the predetermined information regarding the setting of the start position of the PTW includes information indicating the number of start positions of the PTW in the PH (the number of SFNs that can be set as the start SFN of the PTW), and the start position of the PTW is: It may be determined by inputting information indicating the number of PTW start positions in PH into a predetermined formula.
- the predetermined calculation formula may be Formula 5 and Formula 6 shown below.
- the end position of PTW may be determined according to Equation 4 as in LTE.
- the eDRX parameters include the eDRX cycle (TeDRX,H in Equation 6) and the time length of the PTW ( L) and the number of starting positions of the PTW in PH (NPTW in Equation 5).
- the predetermined information regarding the setting of the PTW start position may include information designating the radio frame indicating the PTW start position.
- the eDRX parameters include an eDRX cycle, information specifying a radio frame indicating the start position of the PTW, and information specifying a radio frame indicating the end position of the PTW.
- ⁇ Specification change example> 7 to 11 are diagrams showing examples of specification changes in the 3GPP specifications.
- the underlined parts in FIGS. 7 to 11 indicate specifications of information elements storing fields indicating eDRX parameters and values set in the fields indicating eDRX parameters.
- FIG. 7 shows a specification change example of the RRC release message used when the base station 20 sets eDRX parameters for the inactive state in the terminal 10.
- the eDRX parameters for the inactive state are stored in 'Ran-PagingExtendedDRX-Info-r17' contained in the information element 'SuspendConfig'.
- the 'pagingExtendedDRX-Cycle-r17' field corresponds to the eDRX cycle and the 'pagingTimeWindow-r17' field corresponds to the PTW.
- the terminal 10 is inactive. It recognizes that the eDRX parameters for state should be set to the same values as the eDRX parameters for idle state.
- FIG. 8 shows a specification example of values set in the "pagingExtendedDRX-Cycle-r17" field and the "pagingTimeWindow-r17" field.
- FIG. 9 shows a specification change example of the RRC setup request message transmitted by the terminal 10 desiring to enable eDRX.
- the eDRX parameters for the inactive state are stored in the information element "Ran-PagingExtendedDRX-Info-r17".
- the 'pagingExtendedDRX-Cycle-r17' field corresponds to the eDRX cycle and the 'pagingTimeWindow-r17' field corresponds to the PTW.
- FIGS. 10 and 11 show examples of specification changes of the RRC setup complete message and RRC reconfiguration complete message, respectively.
- specification examples of values set in the "pagingExtendedDRX-Cycle-r17" field and “pagingTimeWindow-r17” field are the same as those in the lower part of FIG.
- FIG. 12 is a diagram illustrating an example of the hardware configuration of each device within the wireless communication system.
- Each device in the wireless communication system 1 eg, terminal 10, base station 20, core network 30, etc.
- the processor 11 is, for example, a CPU (Central Processing Unit) and controls each device within the wireless communication system 1 .
- the processor 11 may read and execute the program from the storage device 12 to execute various processes described in this embodiment.
- Each device within the wireless communication system 1 may be configured with one or more processors 11 .
- Each device may also be called a computer.
- the storage device 12 is composed of storage such as memory, HDD (Hard Disk Drive) and/or SSD (Solid State Drive).
- the storage device 12 may store various types of information necessary for execution of processing by the processor 11 (for example, programs executed by the processor 11, etc.).
- the communication device 13 is a device that communicates via a wired and/or wireless network, and may include, for example, network cards, communication modules, chips, antennas, and the like. Further, the communication device 13 may include an amplifier, an RF (Radio Frequency) device that performs processing related to radio signals, and a BB (BaseBand) device that performs baseband signal processing.
- RF Radio Frequency
- BB BaseBand
- the RF device for example, performs D/A conversion, modulation, frequency conversion, power amplification, etc. on the digital baseband signal received from the BB device to generate a radio signal to be transmitted from the antenna. Further, the RF device generates a digital baseband signal by performing frequency conversion, demodulation, A/D conversion, etc. on the radio signal received from the antenna, and transmits the digital baseband signal to the BB device.
- the BB device performs a process of converting a digital baseband signal into a packet and a process of converting the packet into a digital baseband signal.
- the input/output device 14 includes input devices such as keyboards, touch panels, mice and/or microphones, and output devices such as displays and/or speakers.
- Each device in the wireless communication system 1 may omit part of the hardware shown in FIG. 12, or may include hardware not shown in FIG. Also, the hardware shown in FIG. 12 may be configured by one or a plurality of chips.
- FIG. 13 is a diagram showing an example of the functional configuration of the terminal 10.
- Terminal 10 includes receiver 101 , transmitter 102 , and controller 103 . All or part of the functions realized by the receiving unit 101 and the transmitting unit 102 can be realized using the communication device 13 . All or part of the functions realized by the receiving unit 101 and the transmitting unit 102 and the control unit 103 can be realized by the processor 11 executing a program stored in the storage device 12 . Also, the program can be stored in a storage medium.
- the storage medium storing the program may be a non-transitory computer readable medium.
- the non-temporary storage medium is not particularly limited, but may be a storage medium such as a USB memory or CD-ROM, for example.
- eDRX parameters are an example of eDRX setting values.
- information elements including eDRX parameters for inactive state eg, Ran-PagingExtendedDRX-Info
- RRC messages and/or NAS messages are examples of first configuration information.
- the first configuration information may be called configuration information.
- information elements including eDRX parameters for idle state, RRC messages and/or NAS messages are examples of second configuration information.
- the information element including the eDRX parameters for the inactive state and/or the idle state, the RRC message and/or the NAS message transmitted from the terminal 10 are examples of request information.
- the receiving unit 101 receives the downstream signal. Also, the receiving section 101 may receive information and/or data transmitted via a downlink signal.
- “receiving” may include, for example, performing processing related to reception such as at least one of receiving, demapping, demodulating, decoding, monitoring, and measuring radio signals.
- the receiving unit 101 receives the first setting information including the eDRX setting values for the inactive state.
- the receiving section 101 may receive an RRC message including the first setting information from the base station 20 .
- the RRC message may be, for example, an RRC release message, an RRC reconfiguration message, an RRC reestablishment message, an RRC resume request message, an RRC resume message, an RRC setup message, or the like.
- the receiving unit 101 may receive a NAS message including the first setting information from the core network 30 .
- the NAS message may be, for example, a registration response message, but is not limited to this.
- the receiving unit 101 may receive the second setting information including the eDRX setting value for the idle state.
- the transmission unit 102 transmits an upstream signal. Also, the transmitting section 102 may transmit information and/or data transmitted via an uplink signal. Here, “transmitting” may include performing processing related to transmission, such as at least one of encoding, modulation, mapping, and transmission of radio signals. Also, the transmitting unit 102 transmits request information including eDRX setting values for the inactive state. The transmission unit 102 may transmit an RRC message including the request information to the base station 20 .
- the RRC message may be, for example, an RRC setup request message, an RRC reconfiguration complete message, an RRC re-establishment request message, an RRC re-establishment complete message, an RRC resumption request message, an RRC resumption complete message, or the like.
- the transmission unit 102 may transmit a NAS message containing the request information to the core network 30.
- the NAS message may be, for example, a registration request message, but is not limited to this.
- the transmitting unit 102 may make it transmit the request information which shows that it is the same as a value. For example, the transmitting unit 102 may transmit the request information including the eDRX setting values for the RRC idle state but not the eDRX setting values for the RRC inactive state in the NAS message. Also, the transmitting unit 102 may transmit an RRC message that includes information indicating a request for eDRX parameters for inactive state but does not include eDRX setting values for inactive state.
- the control unit 103 performs various processes related to eDRX based on the eDRX setting values received by the receiving unit 101 . Further, in the RRC non-active state, the control unit 103 controls the PTW (receiving period) in the PH (predetermined H-SFN) indicated by the eDRX setting value included in the first setting information, and the control channel in the paging search space. Control to monitor the candidate (PDCCH Candidate).
- the control unit 103 controls the second setting information (for example, the eDRX parameter for the idle state) in the RRC inactive state. ) may be controlled to monitor the control channel candidate in the paging search space during the reception period in the predetermined H-SFN indicated by the eDRX set value included in the .
- the eDRX setting value included in the first setting information includes information indicating the number of reception period start positions in a predetermined H-SFN, and the reception period start position is the start of the reception period in a predetermined H-SFN. It may be determined by inputting information indicating the number of positions (for example, information indicating the number of PTW starting positions in PH, NPTW) into a predetermined formula.
- FIG. 14 is a diagram showing an example of the functional configuration of the base station 20.
- Base station 20 includes receiver 201 , transmitter 202 , and controller 203 . All or part of the functions realized by the receiving unit 201 and the transmitting unit 202 can be realized using the communication device 13 . All or part of the functions realized by the receiving unit 201 and the transmitting unit 202 and the control unit 103 can be realized by the processor 11 executing a program stored in the storage device 12 . Also, the program can be stored in a storage medium.
- the storage medium storing the program may be a computer-readable non-temporary storage medium.
- the non-temporary storage medium is not particularly limited, but may be a storage medium such as a USB memory or CD-ROM, for example.
- the receiving unit 201 receives an upstream signal. Also, the receiving section 201 may receive information and/or data transmitted via the uplink signal. Also, the receiving unit 201 receives request information including eDRX setting values for the RRC inactive state from the terminal 10 .
- the transmission unit 202 transmits a downlink signal. Also, the transmitting section 202 may transmit information and/or data transmitted via the downlink signal. Also, the transmitting unit 202 transmits first configuration information including eDRX configuration values for the RRC inactive state to the terminal 10 . In addition, transmitting section 202 transmits configuration information including eDRX configuration values to be applied to terminal 10 in the RRC inactive state to terminal 10 .
- the control unit 203 controls RAN paging processing for the terminal 10 in the RRC inactive state.
- control section 203 allows terminal 10 in the RRC inactive state to perform a paging search in the PTW (receiving period) at the PH (predetermined H-SFN) indicated by the eDRX setting value included in the first setting information. It controls to transmit downlink control information (for example, DCI) within the space.
- DCI downlink control information
- the eDRX parameters, the information element including the eDRX parameters, the RRC message including the eDRX parameters, and/or the NAS message including the eDRX parameters are examples of eDRX configuration information.
- Explicitly or implicitly including information indicating that the eDRX parameter for the inactive state is the same value as the eDRX parameter for the idle state means, for example, specifying NULL or the like in each eDRX parameter for the inactive state. It may be that the character string or number of is included.
- Monitoring the control channel candidates within the paging search space may be expressed as "monitoring the control channel candidates within the search space set set by the paging search space information (pagingSearchSpace)".
- an example of the first time unit is 1 hyperframe (10.24 sec)
- an example of the second time unit is 1 radio frame (10 ms)
- an example of the third time unit is 1 subframe (1 ms).
- the second time unit may be defined as a time shorter than the first time unit
- the third time trough may be defined as a time shorter than the second time unit.
- SFN may be an example of the number indicating the position of the periodically repeated second time unit
- H-SFN may be an example of the number indicating the position of the periodically repeated first time unit.
- the H-SFN may be expressed as a first time interval at a position indicated by a predetermined number among the periodically repeated first time intervals.
- the PH may be set in a plurality of hyperframes among 0 to 1023 H-SFNs.
- Various signals, information, and parameters in the above embodiments may be signaled in any layer. That is, the various signals, information, and parameters are replaced with signals, information, and parameters of any layer such as higher layers (eg, NAS layer, RRC layer, MAC layer, etc.), lower layers (eg, physical layer), etc. good too. Further, the notification of the predetermined information is not limited to being performed explicitly, but may be performed implicitly (for example, by not notifying the information or using other information).
- a slot may be named any unit of time having a predetermined number of symbols.
- RB may be any name as long as it is a frequency unit having a predetermined number of subcarriers.
- the use of the terminal 10 in the above embodiment is not limited to those illustrated, as long as it has similar functions, any use (for example, eMBB, URLLC, Device-to- Device (D2D), Vehicle-to-Everything (V2X), etc.).
- the terminal of the present embodiment includes a receiving unit that receives the first setting information including the eDRX setting value for the RRC inactive state, and the eDRX setting value included in the first setting information in the RRC inactive state. and a control unit for controlling to monitor the control channel candidate in the paging search space in the reception period at a predetermined H-SFN indicated by .
- the receiving unit may receive an RRC message including the first setting information from the base station.
- the receiving unit may receive a NAS message including the first setting information from a core network.
- the receiving unit receives second setting information including an eDRX setting value for RRC idle state, and the control unit, if the first setting information does not include an eDRX setting value, In the RRC inactive state, control may be performed to monitor control channel candidates in the paging search space during the reception period in a predetermined H-SFN indicated by the eDRX setting value included in the second setting information.
- the eDRX setting value included in the first setting information includes information indicating the number of start positions of the reception period in the predetermined H-SFN, and the start position of the reception period is the predetermined may be determined by inputting information indicating the number of starting positions of the receiving period in the H-SFN of the number into a predetermined formula.
- the base station of the present embodiment includes a transmitting unit that transmits first setting information including an eDRX setting value for RRC inactive state to the terminal, and the terminal that is in the RRC inactive state, the first setting information and a control unit that controls to transmit downlink control information within the paging search space in a reception period in a predetermined H-SFN indicated by the eDRX setting value included in the control unit.
- the wireless communication method performed by the terminal of the present embodiment includes the steps of: receiving first setting information including an eDRX setting value for RRC inactive state; and controlling to monitor the control channel candidate within the paging search space during the reception period at the predetermined H-SFN indicated by the set value.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
次に、NRで規定されている、端末10のRRC状態(RRC state)について説明する。端末10のRRC状態は、RRCアイドル状態(以下、「アイドル状態」と言う。)、RRC非アクティブ状態(以下、「非アクティブ状態」と言う。)、RRCコネクティッド状態(以下、「コネクティッド状態」と言う。)を含む。
ここで、LTEで規定されている従来のeDRX(拡張DRX)技術について説明する。LTEでは、時間の長さが1msであるサブフレーム(Subframe)と、時間の長さが10msである無線フレーム(Radio Frame)と、時間の長さが10.24秒であるハイパーフレーム(Hyperframe)が規定されている。無線フレームの位置は、0~1023番までのSFN(System Frame Number)により表される。また、1024個の無線フレームより長い時間を管理するため、0~1023番のSFN(つまり10.24秒)の長さであるハイパーフレームが規定されている。ハイパーフレームは、0~1023番号までのH-SFN(Hyper-SFN(System Frame Number))により表される。
H-SFN mod TeDRX,H = (UE_ID_H mod TeDRX,H)
「TeDRX,H」は、eDRXサイクルを示し、ハイパーフレームの整数倍の長さで設定される。UE_ID_Hは、S-TMSI(SAE Temporary Mobile Subscriber Identity)又は5G-S-TMIS(5G S-Temporary Mobile Subscriber Identity)に基づいて定められるハッシュID(Hashed ID)の最上位10又は12ビットである。
SFN = 256 * ieDRX
(数式3)
ieDRX=floor(UE_ID_H/TeDRX,H) mod 4
PTWの終了位置(PTW_end)(終了タイミング)であるSFNは、以下の数式4で表される。
SFN = (PTW_start+L*100-1) mod 1024
Lは、PTWの時間長(Paging Time Window length)である。eDRXサイクル及びPTWの時間長等のeDRX動作を決定するパラメータ(以下、「eDRXパラメータ」と言う。)は、上位レイヤ(NAS(Non Access Stratum))のメッセージにより端末10に設定される。以下、「PTW」は、特に断りが無い限りPTWの時間長を意味する。
現在、3GPPでは、NRでeDRXを実現するための検討が進められている。ここで、LTEでは、NASメッセージを利用して、eDRXパラメータをコアネットワーク30から端末10に通知する処理手順が規定されている。従って、当該処理手順をNRに適用することで、アイドル状態の端末10に適用されるeDRXパラメータを、端末10に通知することは可能である。しかしながら、非アクティブ状態の端末10に適用されるeDRXパラメータを、端末10に通知(設定)するための処理手順は、現状の3GPPでは規定されていない(第1の課題)。
非アクティブ状態でeDRXを実現する際、非アクティブ状態向けeDRXパラメータを、コアネットワーク30で管理する方法と、基地局20で管理する方法との2通りが考えられる。なお、以下の説明において、端末10がページングを行う処理は、特に断りのない限り、従来のeDRX技術で説明した処理と同一であってもよい。
本実施形態に係る端末10、基地局20及びコアネットワーク30は、LTEと同様のeDRXパラメータを利用することとしてもよい。つまり、PHは数式1に従って決定され、PTWの開始位置は数式2及び3に従って決定され、PTWの終了位置は数式4により決定されることとしてもよい。この場合、eDRXパラメータには、eDRXサイクル(数式1及び3におけるTeDRX,H)と、PTWの時間長(数式4におけるL)とが含まれる。
SFN = (1024 div NPTW)*ieDRX
(数式6)
ieDRX=floor(UE_ID_H/TeDRX,H) mod NPTW
数式5及び6において、NPTWは、PHにおけるPTWの開始位置の数を示す情報である。例えば、NPTW=8とした場合、ieDRXの取り得る値は、0~7になるから、PTWの開始位置は、SFN=0、128、256、384、512、640、768、896の8つのうちいずれかになる。なお、NPTW=4である場合、数式5及び6は、それぞれ、数式2及び3と同一になる。つまり、数式5及び6を利用することで、PTWの開始位置を、LTEよりも柔軟に設定することが可能になる。
図7~図11は、3GPP仕様書の仕様変更例を示す図である。図7~図11の下線部は、eDRXパラメータを示すフィールドを格納する情報要素及びeDRXパラメータを示すフィールドに設定される値の仕様を示している。
図12は、無線通信システム内の各装置のハードウェア構成の一例を示す図である。無線通信システム1内の各装置(例えば、端末10、基地局20、コアネットワーク30など)は、プロセッサ11、記憶装置12、有線又は無線通信を行う通信装置13、各種の入力操作を受け付ける入力装置や各種情報の出力を行う入出力装置14を含む。
(端末)
図13は、端末10の機能構成の一例を示す図である。端末10は、受信部101と、送信部102と、制御部103とを含む。受信部101と送信部102とが実現する機能の全部又は一部は、通信装置13を用いて実現することができる。また、受信部101と送信部102とが実現する機能の全部又は一部と、制御部103とは、プロセッサ11が、記憶装置12に記憶されたプログラムを実行することにより実現することができる。また、当該プログラムは、記憶媒体に格納することができる。当該プログラムを格納した記憶媒体は、コンピュータ読み取り可能な非一時的な記憶媒体(Non-transitory computer readable medium)であってもよい。非一時的な記憶媒体は特に限定されないが、例えば、USBメモリ又はCD-ROM等の記憶媒体であってもよい。
図14は、基地局20の機能構成の一例を示す図である。基地局20は、受信部201と、送信部202と、制御部203とを含む。受信部201と送信部202とが実現する機能の全部又は一部は、通信装置13を用いて実現することができる。また、受信部201と送信部202とが実現する機能の全部又は一部と、制御部103とは、プロセッサ11が、記憶装置12に記憶されたプログラムを実行することにより実現することができる。また、当該プログラムは、記憶媒体に格納することができる。当該プログラムを格納した記憶媒体は、コンピュータ読み取り可能な非一時的な記憶媒体であってもよい。非一時的な記憶媒体は特に限定されないが、例えば、USBメモリ又はCD-ROM等の記憶媒体であってもよい。
eDRXパラメータ、eDRXパラメータを含む情報要素、eDRXパラメータを含むRRCメッセージ及び/又はeDRXパラメータを含むNASメッセージは、eDRXの設定情報の一例である。
Claims (20)
- 基地局と通信する端末であって、
前記基地局によって決定される、RRC非アクティブ状態向けのeDRX(extended DRX)パラメータを含むRRCメッセージを受信する受信部と、
RRC非アクティブ状態において、前記RRCメッセージに含まれるeDRXパラメータに基づいて、ページング用サーチスペース情報により設定されるページング用サーチスペース内の制御チャネル候補をモニタするように制御する制御部と、
を有する端末。 - 前記RRCメッセージは、RRC解放メッセージである、
請求項1に記載の端末。 - 前記RRCメッセージに含まれるeDRXパラメータは、eDRXサイクルの設定を含む、
請求項1又は2に記載の端末。 - 前記RRCメッセージに含まれるeDRXパラメータはPTW(Paging Time Window)の設定を含む
請求項1~3のいずれか一項に記載の端末。 - 前記受信部は、コアネットワーク装置から、RRCアイドル状態向けのeDRXパラメータを含むNASメッセージを受信し、
前記制御部は、前記RRCメッセージにeDRXパラメータが含まれていない場合、RRC非アクティブ状態において、前記NASメッセージに含まれるeDRXパラメータに基づいて、ページング用サーチスペース内の制御チャネル候補をモニタするように制御する、
請求項1~4のいずれか一項に記載の端末。 - 端末と通信する基地局であって、
当該基地局によって決定される、RRC非アクティブ状態向けのeDRX(extended DRX)パラメータを含むRRCメッセージを前記端末に送信する送信部と、
RRC非アクティブ状態である前記端末に対し、前記RRCメッセージに含まれるeDRXパラメータに基づいて、ページング用サーチスペース情報により設定されるページング用サーチスペース内で下り制御情報を送信するように制御する制御部と、
を有する基地局。 - 前記RRCメッセージは、RRC解放メッセージである、
請求項6に記載の基地局。 - 前記RRCメッセージに含まれるeDRXパラメータは、eDRXサイクルの設定を含む、
請求項6又は7に記載の基地局。 - 前記RRCメッセージに含まれるeDRXパラメータは、PTW(Paging Time Window)の設定を含む、
請求項6~8のいずれか一項に記載の基地局。 - 前記制御部は、前記RRCメッセージにeDRXパラメータが含まれていない場合、RRC非アクティブ状態である前記端末に対し、コアネットワーク装置から受信するeDRXパラメータに基づいて、前記ページング用サーチスペース内で下り制御情報を送信するように制御する、
請求項6~9のいずれか一項に記載の基地局。 - 基地局と通信する端末が実行する無線通信方法であって、
前記基地局によって決定される、RRC非アクティブ状態向けのeDRX(extended DRX)パラメータを含むRRCメッセージを受信するステップと、
RRC非アクティブ状態において、前記RRCメッセージに含まれるeDRXパラメータに基づいて、ページング用サーチスペース情報により設定されるページング用サーチスペース内の制御チャネル候補をモニタするように制御するステップと、
を含む無線通信方法。 - 前記RRCメッセージは、RRC解放メッセージである、
請求項11に記載の無線通信方法。 - 前記RRCメッセージに含まれるeDRXパラメータは、eDRXサイクルの設定を含む、
請求項11又は12に記載の無線通信方法。 - 前記RRCメッセージに含まれるeDRXパラメータはPTW(Paging Time Window)の設定を含む
請求項11~13のいずれか一項に記載の無線通信方法。 - 前記受信するステップは、コアネットワーク装置から、RRCアイドル状態向けのeDRXパラメータを含むNASメッセージを受信し、
前記制御するステップは、前記RRCメッセージにeDRXパラメータが含まれていない場合、RRC非アクティブ状態において、前記NASメッセージに含まれるeDRXパラメータに基づいて、ページング用サーチスペース内の制御チャネル候補をモニタするように制御する、
請求項11~14のいずれか一項に記載の無線通信方法。 - 端末と通信する基地局が実行する無線通信方法であって、
当該基地局によって決定される、RRC非アクティブ状態向けのeDRX(extended DRX)パラメータを含むRRCメッセージを前記端末に送信するステップと、
RRC非アクティブ状態である前記端末に対し、前記RRCメッセージに含まれるeDRXパラメータに基づいて、ページング用サーチスペース情報により設定されるページング用サーチスペース内で下り制御情報を送信するように制御するステップと、
を含む無線通信方法。 - 前記RRCメッセージは、RRC解放メッセージである、
請求項16に記載の無線通信方法。 - 前記RRCメッセージに含まれるeDRXパラメータは、eDRXサイクルの設定を含む、
請求項16又は17に記載の無線通信方法。 - 前記RRCメッセージに含まれるeDRXパラメータは、PTW(Paging Time Window)の設定を含む、
請求項16~18のいずれか一項に記載の無線通信方法。 - 前記制御するステップは、前記RRCメッセージにeDRXパラメータが含まれていない場合、RRC非アクティブ状態である前記端末に対し、コアネットワーク装置から受信するeDRXパラメータに基づいて、前記ページング用サーチスペース内で下り制御情報を送信するように制御する、
請求項16~19のいずれか一項に記載の無線通信方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112023018702A BR112023018702A2 (pt) | 2021-03-25 | 2022-03-24 | Terminal que se comunica com uma estação base, estação base que se comunica com um terminal, e, método de comunicação sem fio |
CN202280023797.XA CN117099413A (zh) | 2021-03-25 | 2022-03-24 | 终端、基站以及无线通信方法 |
EP22775784.6A EP4319390A1 (en) | 2021-03-25 | 2022-03-24 | Terminal, base station, and wireless communication method |
US18/471,265 US20240073859A1 (en) | 2021-03-25 | 2023-09-20 | Terminal, base station, and wireless communication method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021052279A JP2022149927A (ja) | 2021-03-25 | 2021-03-25 | 端末、基地局及び無線通信方法 |
JP2021-052279 | 2021-03-25 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/471,265 Continuation US20240073859A1 (en) | 2021-03-25 | 2023-09-20 | Terminal, base station, and wireless communication method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022203003A1 true WO2022203003A1 (ja) | 2022-09-29 |
Family
ID=83397413
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/014000 WO2022203003A1 (ja) | 2021-03-25 | 2022-03-24 | 端末、基地局及び無線通信方法 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20240073859A1 (ja) |
EP (1) | EP4319390A1 (ja) |
JP (1) | JP2022149927A (ja) |
CN (1) | CN117099413A (ja) |
BR (1) | BR112023018702A2 (ja) |
WO (1) | WO2022203003A1 (ja) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20200098962A (ko) * | 2019-02-13 | 2020-08-21 | 삼성전자주식회사 | 차세대 이동통신 시스템에서 비활성 모드에서 확장된 비연속 수신 모드를 수행하는 방법 및 장치 |
-
2021
- 2021-03-25 JP JP2021052279A patent/JP2022149927A/ja active Pending
-
2022
- 2022-03-24 WO PCT/JP2022/014000 patent/WO2022203003A1/ja active Application Filing
- 2022-03-24 EP EP22775784.6A patent/EP4319390A1/en active Pending
- 2022-03-24 CN CN202280023797.XA patent/CN117099413A/zh active Pending
- 2022-03-24 BR BR112023018702A patent/BR112023018702A2/pt unknown
-
2023
- 2023-09-20 US US18/471,265 patent/US20240073859A1/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20200098962A (ko) * | 2019-02-13 | 2020-08-21 | 삼성전자주식회사 | 차세대 이동통신 시스템에서 비활성 모드에서 확장된 비연속 수신 모드를 수행하는 방법 및 장치 |
Non-Patent Citations (2)
Title |
---|
3GPP TS 36.300, December 2020 (2020-12-01) |
3GPP TS 38.300, September 2020 (2020-09-01) |
Also Published As
Publication number | Publication date |
---|---|
BR112023018702A2 (pt) | 2023-10-24 |
US20240073859A1 (en) | 2024-02-29 |
JP2022149927A (ja) | 2022-10-07 |
EP4319390A1 (en) | 2024-02-07 |
CN117099413A (zh) | 2023-11-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP2021520675A (ja) | Rrcインアクティブ状態における測定の一時停止/再開 | |
JP2014528222A (ja) | 間欠受信 | |
US11218961B2 (en) | Power saving for wireless device | |
JP2015537456A (ja) | 低アクティブモードでセル又はネットワークからタイミング情報を受け取るための方法及び装置 | |
US20230379825A1 (en) | Terminal, base station, and wireless communication method | |
WO2022203003A1 (ja) | 端末、基地局及び無線通信方法 | |
WO2022203004A1 (ja) | 端末、基地局及び無線通信方法 | |
US20230232314A1 (en) | System information acquisition for reduced capability nr devices | |
WO2023054545A1 (ja) | 端末、コアネットワーク装置及び無線通信方法 | |
WO2022260160A1 (ja) | 端末及び無線通信方法 | |
WO2023054546A1 (ja) | 端末、基地局、コアネットワーク装置及び無線通信方法 | |
WO2023277026A1 (ja) | 端末及び無線通信方法 | |
WO2023277027A1 (ja) | 端末及び無線通信方法 | |
WO2022154101A1 (ja) | 基地局及び無線通信方法 | |
WO2022154100A1 (ja) | 端末、基地局及び無線通信方法 | |
CN116325818A (zh) | 一种通信方法及装置 | |
US20230403724A1 (en) | Terminal, base station and wireless communication method | |
WO2023132325A1 (ja) | 端末、基地局及び通信方法 | |
WO2023165420A1 (zh) | 通信方法及通信装置 |
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: 22775784 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280023797.X Country of ref document: CN |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112023018702 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112023018702 Country of ref document: BR Kind code of ref document: A2 Effective date: 20230914 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022775784 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022775784 Country of ref document: EP Effective date: 20231025 |