WO2023201496A1 - Procédés, dispositifs et support lisible par ordinateur destinés à la communication - Google Patents

Procédés, dispositifs et support lisible par ordinateur destinés à la communication Download PDF

Info

Publication number
WO2023201496A1
WO2023201496A1 PCT/CN2022/087512 CN2022087512W WO2023201496A1 WO 2023201496 A1 WO2023201496 A1 WO 2023201496A1 CN 2022087512 W CN2022087512 W CN 2022087512W WO 2023201496 A1 WO2023201496 A1 WO 2023201496A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
pei
information
indication
capability
Prior art date
Application number
PCT/CN2022/087512
Other languages
English (en)
Inventor
Gang Wang
Original Assignee
Nec Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nec Corporation filed Critical Nec Corporation
Priority to PCT/CN2022/087512 priority Critical patent/WO2023201496A1/fr
Publication of WO2023201496A1 publication Critical patent/WO2023201496A1/fr

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005Transmission of information for alerting of incoming communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0225Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229Power 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/28Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/04Terminal devices adapted for relaying to or from another terminal or user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/16Interfaces between hierarchically similar devices
    • H04W92/18Interfaces between hierarchically similar devices between terminal devices

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices, and computer readable medium for communication.
  • sidelink communication is a feature aiming at enabling device-to-device (D2D) communications.
  • D2D device-to-device
  • sidelink Unlike uplink or downlink, sidelink enables a direct communication between proximal user equipments (UEs) , and data does not need to go through the network device.
  • Relay has also been introduced to enhance the coverage area of a network device by improving the throughput of a UE that is located in the coverage or far from the network device.
  • a UE (called relay terminal device) can provide other UEs (called remote UEs) that could experience coverage problems with connectivity.
  • the UE-to-Network relay effectively extends network coverage by relaying traffic between the network and remote UEs.
  • the relay communicates with remote UEs using UE-to-UE direct communication while connecting to the network using existing cellular communication technologies. Further, when the relay UE in radio resource control (RRC) IDLE/RRC INACTVE and the remote UE in RRC IDLE/RRC INACTIVE, the relay UE can monitor paging occasions of its connected remote UE (s) . Therefore, it is worth further studying paging in the sidelink communications.
  • RRC radio resource control
  • example embodiments of the present disclosure provide a solution for communication.
  • a method for communication comprises receiving paging early indication (PEI) information related to at least one second terminal device, wherein the first terminal device relays a communication between the at least one second terminal device and a network device; and determining whether to monitor a PEI for the at least one second terminal device from the network device.
  • PEI paging early indication
  • a method for communication comprises transmitting, at a second terminal device and to a first terminal device, PEI information related to the second terminal device, wherein the first terminal device relays a communication between the second terminal device and a network device.
  • a method for communication comprises transmitting, at a network device and to a first terminal device, PEI information related to at least one second terminal device, wherein the PEI information comprises at least one of: a PEIC capability of the second terminal device, last used cell information of the at least one second terminal device, or information for extended discontinuous reception (eDRX) .
  • PEI information comprises at least one of: a PEIC capability of the second terminal device, last used cell information of the at least one second terminal device, or information for extended discontinuous reception (eDRX) .
  • a terminal device comprising a processing unit; and a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the terminal device to perform acts comprising: receiving paging early indication (PEI) information related to at least one second terminal device, wherein the first terminal device relays a communication between the at least one second terminal device and a network device; and determining whether to monitor a PEI for the at least one second terminal device from the network device.
  • PEI paging early indication
  • a terminal device comprising a processing unit; and a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the terminal device to perform acts comprising: transmitting to a first terminal device, PEI information related to the second terminal device, wherein the first terminal device relays a communication between the second terminal device and a network device.
  • a network device comprising a processing unit; and a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the network device to perform acts comprising transmitting, to a first terminal device, PEI information related to at least one second terminal device, wherein the PEI information comprises at least one of: a PEIC capability of the second terminal device, last used cell information of the at least one second terminal device, or information for extended discontinuous reception (eDRX) .
  • eDRX extended discontinuous reception
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the first, second or third aspect.
  • Fig. 1 shows a schematic diagram of paging occasions and a paging early indication (PEI) occasion according to some embodiments of the present disclosure, respectively;
  • PEI paging early indication
  • Fig. 2 is a schematic diagram of a communication environment in which embodiments of the present disclosure can be implemented;
  • Fig. 3 illustrates a signaling flow for communications according to some embodiments of the present disclosure
  • Fig. 4 illustrates a signaling flow for communications according to some embodiments of the present disclosure
  • Figs. 5A-5C illustrate signaling flows for communications according to some embodiments of the present disclosure, respectively;
  • Fig. 6 illustrates a signaling flow for communications according to some embodiments of the present disclosure
  • Fig. 7 illustrates a signaling flow for communications according to some embodiments of the present disclosure
  • Fig. 8 is a flowchart of an example method in accordance with an embodiment of the present disclosure.
  • Fig. 9 is a flowchart of an example method in accordance with an embodiment of the present disclosure.
  • Fig. 10 is a flowchart of an example method in accordance with an embodiment of the present disclosure.
  • Fig. 11 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV)
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
  • the terminal device or the network device may have Artificial Intelligence (AI) or Machine Learning (ML) capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial Intelligence
  • ML Machine Learning
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Terahertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node such as a fe
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • Communications discussed herein may use conform to any suitable standards including, but not limited to, New Radio Access (NR) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , cdma2000, and Global System for Mobile Communications (GSM) and the like.
  • NR New Radio Access
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GSM Global System for Mobile Communications
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.85G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , and the sixth (6G) communication protocols.
  • the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies.
  • the embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • values, procedures, or apparatus are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the group of UEs monitoring the same paging occasion can be further divided into multiple subgroups.
  • a UE shall monitor physical downlink control channel (PDCCH) in its PO for paging if the subgroup to which the UE belongs is paged as indicated via associated paging early indication (PEI) . If a UE cannot find its subgroup ID with the PEI configurations in a cell or if the UE is unable to monitor the associated PEI occasion corresponding to its PO, it shall monitor the paging in its PO.
  • the UE monitors one PEI occasion per DRX cycle.
  • a PEI occasion is a set of PDCCH monitoring occasions (MOs) and can consist of multiple time slots (e.g. subframe or OFDM symbol) where PEI can be sent. If PEI and subgrouping are configured, UEs monitoring the same PO can be divided into one or more subgroups. With subgrouping, the UE monitors PO if the corresponding bit for subgroup the UE belongs to is indicated as 1 by PEI corresponding to its PO.
  • Fig. 1 shows an example schematic diagram of paging occasions and a paging early indication (PEI) .
  • PEI occasion 210-1 and POs 220-1, 220-2, 220-3 and 220-4 within the discontinuous reception (DRX) cycle 200-1 and there may be a PEI occasion 210-2 and POs 220-5, 220-6, 220-7 and 220-8 within the discontinuous reception (DRX) cycle 200-2.
  • a PEI occasion (PEI-O) is a set of PDCCH monitoring occasions (MOs) and can comprise multiple time slots (e.g. subframe or OFDM symbol) where PEI can be sent.
  • the time location of PEI-O for UE's PO can be determined by a reference point and an offset from the reference point to the start of the first PDCCH monitoring occasion of this PEI-O: the reference point is the start of a reference frame determined by a frame-level offset from the start of the first paging frame (PF) of the PF (s) associated with the PEI-O, provided by PEI-F_offset in system information block (SIB) 1; the offset is a symbol-level offset from the reference point to the start of the first PDCCH MO of PEI-O, provided by IE firstPDCCH-MonitoringOccasionOfPEI-O in SIB1.
  • SIB system information block
  • the UE may monitor the POs 220-1, 220-2, 220-3 and 220-4 associated with the PEI during the DRX cycle 200-1. If the UE does not the PEI in the PEI occasion 210-2, the UE may be required to monitor the POs 220-5, 220-6, 220-7 and 220-8 associated with the PEI during the DRX cycle 200-2. However, it is not clear how to support PEI and subgrouping in sidelink relay.
  • a relay terminal device receives paging early indication (PEI) information related to at least one remote terminal device from a network device or the at least one remote terminal device.
  • the relay terminal device determines whether to monitor a PEI for the at least one remote terminal device from the network device. In this way, it enables PEI monitoring for remote terminal device to save power consumption of relay terminal device.
  • PEI paging early indication
  • Fig. 1 illustrates a schematic diagram of a communication system in which embodiments of the present disclosure can be implemented.
  • the communication system 100 which is a part of a communication network, comprises a terminal device 110-1, a terminal device 110-2, ..., a terminal device 110-N, which can be collectively referred to as “terminal device (s) 110. ”
  • the number N can be any suitable integer number.
  • the interface among terminal devices 110 may be called PC5 interface.
  • the term “relay UE/relay terminal device” used herein can refer to a UE which is configured to relay data between a network device and one or more other UE via a direction connection between the UE and the one or more other UE.
  • remote UE/remote terminal device can refer to a UE which can communicate with a network device through a relay UE.
  • the terminal devices 110 may support one or more of: unicast, groupcast or broadcast.
  • the communication system 100 further comprises a network device 120.
  • the network device 120 can be serving the terminal device 110-1. In other words, the serving cell of the terminal device 110-1 is on the network device 120.
  • the network device 120 and the terminal devices 110 can communicate data and control information to each other.
  • the terminal devices 110 can also communicate with each other.
  • the terminal device110-1 is connected (i.e. RRC connected) with the terminal device 110-2.
  • the numbers of terminal devices shown in Fig. 1 are given for the purpose of illustration without suggesting any limitations.
  • the interface between the terminal device110 and the network device 120 may be called Uu interface.
  • Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • IEEE Institute for Electrical and Electronics Engineers
  • the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Divided Multiple Address (CDMA) , Frequency Divided Multiple Address (FDMA) , Time Divided Multiple Address (TDMA) , Frequency Divided Duplexer (FDD) , Time Divided Duplexer (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Divided Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Divided Multiple Address
  • FDMA Frequency Divided Multiple Address
  • TDMA Time Divided Multiple Address
  • FDD Frequency Divided Duplexer
  • TDD Time Divided Duplexer
  • MIMO Multiple-Input Multiple-Output
  • OFDMA Orthogonal Frequency Divided Multiple Access
  • Embodiments of the present disclosure can be applied to any suitable scenarios.
  • embodiments of the present disclosure can be implemented at reduced capability NR devices.
  • embodiments of the present disclosure can be implemented in one of the followings: NR multiple-input and multiple-output (MIMO) , NR sidelink enhancements, NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz, narrow band-Internet of Thing (NB-IOT) /enhanced Machine Type Communication (eMTC) over non-terrestrial networks (NTN) , NTN, UE power saving enhancements, NR coverage enhancement, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB) , NR Multicast and Broadcast Services, or enhancements on Multi-Radio Dual-Connectivity.
  • MIMO multiple-input and multiple-output
  • NR sidelink enhancements NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz
  • NB-IOT narrow band-Internet of
  • slot refers to a dynamic scheduling unit. One slot comprises a predetermined number of symbols.
  • the term “downlink (DL) sub-slot” may refer to a virtual sub-slot constructed based on uplink (UL) sub-slot.
  • the DL sub-slot may comprise fewer symbols than one DL slot.
  • the slot used herein may refer to a normal slot which comprises a predetermined number of symbols and also refer to a sub-slot which comprises fewer symbols than the predetermined number of symbols.
  • Fig. 3 shows a signaling chart illustrating process 300 among the terminal device and the network device according to embodiments of the present disclosure.
  • the process 300 is described with reference to Fig. 2. Only for the purpose of discussion, the terminal device 110-1 can act as a relay UE and the terminal device 110-2 can act as a remote UE. It should be noted that the process 300 is a general process according to embodiments of the present disclosure.
  • the terminal device 110-1 receives PEI information related to one or more remote UE (for example, the terminal device 110-2) .
  • the terminal device 110-2 may transmit 3010 the PEI information to the terminal device 110-1.
  • the PEI information may be transmitted via PC5 RRC dedicated signaling.
  • the PEI information may be transmitted via broadcast, for example, a discovery message.
  • the network device 120 may transmit 3020 the PEI information to the terminal device.
  • the PEI information may be transmitted via RRC signaling.
  • the PEI information may be transmitted via broadcast, for example, a system information block (SIB) .
  • SIB system information block
  • the network device 120 can provide multiple UEs’ PEI information.
  • the PEI information may comprise a PEI capability of the terminal device 110-2.
  • the PEI capability may indicate whether the terminal device can support monitoring PEI.
  • the PEI capability may comprise PEI and subgrouping capability.
  • the PEI capability may comprise PEI or subgrouping capability.
  • the PEI capability may comprise the configuration of PEI.
  • the configuration of PEI may be obtained from the SIB, such as IE PEI-config.
  • the PEI information may comprise a core network (CN) assigned subgrouping identity.
  • the PEI information may comprise a core network (CN) assigned subgrouping identity if terminal device 110-2 is configured with it by the core network, for example, Access and Mobility Management Function (AMF) .
  • AMF Access and Mobility Management Function
  • the terminal device 110-1 may determine the subgrouping for the terminal device 110-1. For example, the terminal device 110-1 may determine whether the terminal device 110-2 supports subgrouping or not. Alternatively or additionally, the terminal device 110-1 may determine whether the terminal device 110-2 support CN assigned subgrouping (also referred to as CN based subgrouping) or UE-ID based subgrouping.
  • the UE-ID may be represented as 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI) mod X, wherein X is 32768 when the extended DRX (eDRX) is applied otherwise X is 8192. In this way, it enables PEI monitoring for Remote UE with eDRX to save power consumption of Relay UE.
  • 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier
  • the terminal device 110-2 may determine its subgrouping ID and the PEI information can comprise the subgrouping ID.
  • the subgrouping ID may be a CN assigned subgrouping ID.
  • the subgrouping ID may be a UE-ID based subgrouping ID.
  • the terminal device 110-2 may retransmit the PEI information comprising the subgrouping ID in case that the serving cell of the terminal device 110-1 is changed, or the PEI capability for the serving cell of the terminal device 110-1 is changed or both the serving cell of the terminal device 110-1 and the serving cell’s PEI capability are changed. Additionally, whether the PEI information comprises the subgrouping ID or PEI capability is preconfigured or configured by the network.
  • the terminal device 110-2 may determine whether the PEI information comprises the subgrouping ID or PEI capability based on the receiving of at least one of the PEI capability of the network device 120 and the PEI capability of the terminal device 110-1. For example, if the PEI capability of at least one of the PEI capability of the network device 120 and the PEI capability of the terminal device 110-1 is received, the terminal device 110-2 may determine the PEI information comprise the subgrouping ID. As another example, if the PEI capability of at least one of the PEI capability of the network device 120 and the PEI capability of the terminal device 110-1 is not received, the terminal device 110-2 may determine the PEI information comprise the PEI capability.
  • the PEI information may comprise the last used cell information of the terminal device 110-2.
  • the PEI information may comprise the last serving cell information of the terminal device 110-2.
  • the terminal device 110-2 may reselect to relay UE served by the last used cell with higher priority.
  • the terminal device 110-1 may reselect the last used cell with higher priority.
  • the PEI information may also comprise information for eDRX.
  • the information for eDRX may comprise an indication regarding that the eDRX is configured and a set of eDRX parameters.
  • the information for eDRX may comprise the set of eDRX parameters.
  • the set of eDRX parameters may comprise a paging time window.
  • the set of eDRX parameters may comprise an extended idle mode DRX cycle length. It should be noted that the set of eDRX parameters may also comprise other proper parameters.
  • the terminal device 110-1 determines 3030 whether to monitor the PEI for the terminal device 110-2 from the network device 120. Monitoring the PEI used herein may comprise monitoring one or more of: the PEI or PEI-O. In some embodiments, the terminal device 110-1 may determine whether to monitor the PEI for the terminal device 110-1 based on a PEI capability of the terminal device 110-1 and a PEI capability of the network device 120. In this case, if terminal device 110-1 and the network device 120 support the PEI, the terminal device 110-1 may monitor the PEI for the terminal device 110-2. For example, the network device 120 supporting the PEI means that the network provides PEI configuration. As another example, the terminal device 110-1 supporting the PEI means that it is PEI-capable. If the terminal device 110-1 and the network device 120 cannot support the PEI, the terminal device 110-1 may not monitor the PEI for the terminal device 110-2.
  • the network device 120 supporting the PEI means that the network provides PEI configuration.
  • the terminal device 110-1 supporting the PEI means that it is PEI-cap
  • the terminal device 110-1 may determine whether to monitor the PEI for the terminal device 110-1 based on a serving cell of the terminal device 110-1 and the last used cell information of the terminal device 110-2. In this case, if the serving cell matches a last used cell of the terminal device 110-2, the terminal device 110-1 may monitor the PEI for the terminal device 110-2. In other words, if the serving cell is the same as the lased used cell, the terminal device 110-1 may monitor the PEI for the terminal device 110-2. If the serving cell does not match the last used cell, the terminal device 110-1 may not monitor the PEI for the terminal device 110-2.
  • the terminal device 110-1 may determine whether to monitor the PEI for the at least one terminal device (for example, the terminal device 110-2) based on the number of remote UEs and/or the number of paging occasions or PEI occasions. In this case, if the number of the remote terminal devices does not exceed a first threshold number or the number of paging occasions on which the remote terminal devices spread does not exceed a second threshold number, the terminal device 110-1 may monitor the PEI for the terminal device 110-2. If there are too many remote terminal devices or remote terminal devices spreading in too many POs or PEI-O in one DRX cycle, the terminal device 110-1 may not monitor the PEI for the terminal device 110-2. For example, if the number of the remote terminal devices exceeds the first threshold number and the number of paging occasions on which the remote terminal devices spread exceeds a second threshold number, the terminal device 110-1 may not monitor the PEI for the terminal device 110-2.
  • the network device 120 may transmit 3040 the PEI for the terminal device 110-2 to the terminal device 110-1. If the PEI indicates a subgrouping ID of the terminal device 110-2, the terminal device 110-1 may monitor a paging occasion for the terminal deice 110-2 according to the PEI. In other words, if the terminal device 110-1 detects PEI and the PEI indicates the subgroup the terminal device 110-2 belongs to to monitor the terminal device 110-2 ‘sassociated PO, the terminal device 110-1monitors the associated PO for the terminal device 110-2. In this case, if the terminal device 110-1 receives a paging message transmitted 3040 by the network device 120 in the paging occasion, the terminal device 110-1 may transmit 4045 a paging record of the terminal device 110-2 to the terminal device 110-2. Alternatively, if the PEI does not indicate the subgrouping ID of the terminal device 110-2, the terminal device 110-1 may not monitor the paging occasion for the terminal deice.
  • Example embodiments of the present disclosure are described with reference to Figs. 4-7 in details. For example, embodiments of the present disclosure are described with reference to Fig. 4 where the remote terminal device reports it PEI information directly. It should be noted that the process 400 is an example process according to embodiments of the present disclosure.
  • the network device 120 may transmit 4005 a system information block (SIB) to the terminal device 110-1.
  • the SIB may comprise PEI configuration.
  • the SIB may comprise an information element (IE) PEI-F_offset and IE firstPDCCH-MonitoringOccasionOfPEI-O. If the PEI is configured, it means that PEI is supported by the radio access network (RAN) /the network device 120.
  • the SIB may comprise subgrouping configuration.
  • the subgrouping configuration may comprise IE subgroupsNumPerPO and IE subgroupsNumForUEID. If the subgrouping configuration is configured, it means the subgrouping is supported by the RAN/the network device 120.
  • the subgrouping configuration may also implicitly indicate: the support of CN assigned subgrouping only, or UE_ID based subgrouping only or both of them.
  • the SIB may comprise IE PEI-Config.
  • the terminal device 110-2 may transmit 4010 PEI information to the terminal device 110-1.
  • the PEI information may be transmitted via PC5 RRC dedicated signaling.
  • the PEI information may be transmitted via broadcast, for example, a discovery message.
  • the PEI information may comprise a PEI capability of the terminal device 110-2.
  • the PEI information may comprise a core network (CN) assigned subgrouping identity.
  • the terminal device 110-1 may determine the subgrouping for the terminal device 110-2. For example, the terminal device 110-1 may determine whether the terminal device 110-2 supports subgrouping or not. Alternatively, the terminal device 110-1 may determine whether the terminal device 110-2 support CN assigned subgrouping or UE-ID based subgrouping.
  • the terminal device 110-2 may determine its subgrouping ID and the PEI information can comprise the subgrouping ID.
  • the terminal device 110-2 may determine its subgrouping ID based on at least one of the PEI capability of the network device 120, the PEI capability of the terminal device 110-2, the PEI capability of the terminal device 110-1 and the CN assigned ID.
  • the subgrouping ID may be a CN assigned subgroup ID.
  • the subgrouping ID may be a UE-ID based subgrouping ID.
  • the terminal device 110-1 may determine 4015 whether to monitor the PEI and/or PEI-O for the PEI and/or PEI-O for the terminal device 110-2. For example, the terminal device 110-1 may determine whether to monitor PEI for the terminal device 110-2 based on at least one of the PEI capability of the terminal device 110-1, the PEI capability of the network device 120 and the number of at least one of the terminal device 110-2 which reports PEI information. For example, if at least one of the terminal device 110-1 or the network device 120 supports the PEI, the terminal device 110-1 may monitor the PEI for the terminal device 110-2.
  • the terminal device 110-1 may monitor the PEI for the terminal device 110-2.
  • the terminal device 110-1 may determine 4020 the subgrouping for the terminal device 110-2. For example, the terminal device 110-1 may derive the subgrouping ID of the terminal device 110-2 based on the PEI capability of the terminal device 110-2 and/or CN assigned subgrouping ID. In some embodiments, the terminal device 110-1 may determine 4020 the subgrouping for the terminal device 110-2 in case that the terminal device 110-1 determines 4015 to monitor PEI for the terminal device 110-2. In other embodiments, the terminal device 110-1 may determine 4020 the subgrouping for the terminal device 110-2 and determine 4015 whether to monitor the PEI and/or PEI-O for the PEI and/or PEI-O for the terminal device 110-2 simultaneously.
  • the terminal device 110-1 may monitor the PEI for the terminal device 110-2 using the subgrouping ID. For example, if the PEI information comprises the subgrouping ID, the terminal device 110-1 may directly use the subgrouping ID to monitor the PEI for the terminal device 110-2. Alternatively, the terminal device 110-1 may use the determined subgrouping ID to monitor the PEI for the terminal device 110-2.
  • the terminal device 110-1 may not monitor the PEI and/or PEI-O for the terminal device 110-2. For example, if the number of the remote terminal devices exceeds a first threshold number or the number of POs or PEI-Os on which the remote terminal devices spread exceeds a second threshold number, the terminal device 110-1 may not monitor the PEI and/or PEI-O for the terminal device 110-2. In some embodiments, if the number of subgroups where the remote terminal devices spread exceeds a threshold number, the terminal device 110-1 may determine not to monitor the PEI and/or PEI-O for the remote terminal devices.
  • the terminal device 110-1 may determine not to monitor the PEI and/or PEI-O for the remote terminal devices. In some embodiments, if a proportion of the subgroups on which the remote terminal devices spread in the total number of subgroups is larger than a threshold proportion, the terminal device 110-1 may determine not to monitor the PEI for the remote terminal devices. For example, if the remote terminal devices spread in 60%of the subgroups which is larger than the threshold proportion 50%, the terminal device 110-1 may determine not to monitor the PEI for the remote terminal devices. Alternatively, if the number of remote terminal devices exceeds a threshold number, the terminal device 110-1 may determine not to monitor the PEI for the remote terminal devices.
  • the terminal device 110-1 may determine not to monitor the PEI for the remote terminal devices.
  • the terminal device 110-1 may determine not to monitor the PEI for the remote terminal devices. For example, if the remote terminal devices occupy 60%POs in the DRX cycle which is larger than the threshold proportion 50%, the terminal device 110-1 may determine not to monitor the PEI for the remote terminal devices.
  • the terminal device 110-1 may assign a new subgrouping ID (for example, a RAN assigned ID) to rearrange the remote terminal devices into the new subgroup. Alternatively or in addition, the terminal device 110-1 may assign new POs or PEI-Os for the remote terminal devices.
  • a new subgrouping ID for example, a RAN assigned ID
  • the terminal device 110-1 may assign new POs or PEI-Os for the remote terminal devices.
  • the above mentioned conditions for determining whether there are too many remote terminal devices or remote terminal devices in too many POs or PEI-O in one DRX cycle can also be applied.
  • the terminal device 110-1 may transmit 4025 the RAN assigned ID or PO or PEI-O for transmitting or receiving PEI to the terminal device 110-2.
  • the terminal device may also report 4030 the RAN assigned ID or PO or PEI-O for transmitting or receiving PEI to the network device 120.
  • the above mentioned conditions for example, thresholds
  • the terminal device 110-1 may transmit 4035 an indication to the network device 120.
  • This indication can request the network device 120 for RAN assigned ID or PO or PEI-O for transmitting or receiving PEI.
  • the indication may also comprise the number of remote terminal devices and/or the number of POs or PEI-Os on which the remote terminal devices spread. Alternatively or in addition, the indication may comprise the number of subgroups based on CN assigned subgrouping and/or UE-ID based subgrouping.
  • the network device 120 may transmit 4040 the RAN assigned ID/PO/PEI-O for transmitting or receiving PEI to the terminal device 110-1.
  • the terminal device 110-1 may further transmit 4045 the RAN assigned ID/PO to the terminal device 110-2.
  • a new RAN assigned ID/PO/PEI-O for transmitting or receiving PEI can be determined if the number of remote terminal devices in each PO is less than a predetermined threshold. Alternatively, if the number of remote terminal devices in each PO is bigger than another predetermined threshold, a new RAN assigned ID/PO/PEI-O for transmitting or receiving PEI can be determined.
  • the first device 110-1 may determine to monitor the PEI for the terminal device 110-2.
  • Example embodiments of monitoring the PEI and transmitting a paging record described with reference Fig. 3 can be applied in the process 400 in Fig. 4.
  • the relay UE can monitor PEI for remote UE to save power consumption of the relay UE.
  • the U2N Relay UE monitors PEI of its connected U2N Remote UE (s) .
  • the U2N Relay UE should monitor all PEI-Os of the U2N Remote UE.
  • the U2N Remote UE in RRC_IDLE or RRC_INACTIVE provides PEI capability and CN assigned subgrouping ID, if configured, to the U2N Relay UE to request it to perform PEI-O monitoring. It may also provide 5G-S-TMSI for PEI-O monitoring. For relay UE in a RRC connected state, the U2N Relay UE monitors POs and PEI-O of its connected U2N Remote UE (s) if the active DL BWP of U2N Relay UE is configured with CORESET and paging search space.
  • Example embodiments of the present disclosure are described with reference to Figs. 5A-5C where the remote UE reports PEI information in case the relay UE and/or RAN are PEI-capable.
  • the relay UE and RAN may send indications about their PEI capability to remote UE separately.
  • the network device 120 transmits 5010 an indication about PEI capability of the RAN to the terminal device 110-2.
  • this indication may be transmitted in SIB.
  • the SIB can be transmitted via on-demand system information request procedure which comprises PEI configuration and subgroup configuration.
  • the SIB can be SIB1, which may be derived without on-demand procedure.
  • this indication may be transmitted in RRC signaling, for example, RRC release message.
  • This indication may indicate that the network device 120 is PEI capable.
  • this indication may comprise information element (IE) about PEI capability and its value.
  • IE information element
  • this indication may comprise the configuration of PEI.
  • the configuration of PEI may be obtained from the SIB, such as IE PEI-config.
  • the network device 120 may be serving the terminal device 110-1. In other words, the serving cell of the terminal device 110-1 may be on the network device 120.
  • the terminal device 110-1 may transmit 5020 an indication about PEI capability of the terminal device 110-1 to the terminal device 110-2.
  • this indication may be transmitted in a broadcast message.
  • this indication may be in the discovery message.
  • this indication may be transmitted in a dedicated message.
  • the dedicated message may be a PC5-RRC message, for example, PC5-RRC Reconfiguration message.
  • This indication may indicate that the terminal device 110-1 is PEI capable.
  • this indication may comprise information element (IE) about PEI capability and its value. For example, if the value is one of: yes, true or 1, it means that the terminal device 110-1 is PEI capable. If the value is one of: no, false or 0, it means that the terminal device 110-1 is not PEI capable.
  • this indication may comprise the PEI information related to the terminal device 110-1, for example, the subgrouping ID for the terminal device 110-1.
  • the terminal device 110-2 may determine 5030 whether to report its PEI information to the terminal device 110-1. In some embodiments, if the terminal device 110-2 determines that both the terminal device 110-1 and the network device 120 are PEI-capable based on the indications (5010 and 5020) , the terminal device 110-2 may determine to report its PEI information. Alternatively, if the terminal device 110-2 determines that the terminal device 110-1 is PEI-capable based on the indication 5020, the terminal device 110-2 may determine to report its PEI information. The terminal device 110-2 may transmit 5040 the PEI information to the terminal device 110-1. For example, upon receiving the indication regarding that the terminal device 110-1 is PEI-capable from the terminal device 110-1, the terminal device 110-2 may transmit the PEI information to the terminal device 110-1.
  • the relay UE may send the indication of PEI capability for both relay UE and the network device 120.
  • the network device 120 may transmit 5110 the SIB to the terminal device 110-1.
  • the SIB may indicate the PEI capability of the network device 120.
  • the network device 120 may be serving the terminal device 110-1. In other words, the serving cell of the terminal device 110-1 may be on the network device 120.
  • the terminal device 110-1 may transmit 5120 a message to the terminal device 110-2.
  • the message may comprise a first indication about the PEI capability of the terminal device 110-1 and a second indication of the PEI capability of the network device 120.
  • this message may be transmitted in a broadcast message.
  • this message may be in the discovery message.
  • this message may be transmitted in a dedicated message.
  • the dedicated message may be PC5-RRC message, for example, PC5-RRC Reconfiguration.
  • this first indication may indicate that the terminal device 110-1 is PEI capable.
  • this first indication may comprise information element (IE) about PEI capability and its value.
  • IE information element
  • the value is one of: yes, true or 1, it means that the terminal device 110-1 is PEI capable. If the value is one of: no, false or 0, it means that the terminal device 110-1 is not PEI capable.
  • This second indication may indicate that the network device 120 is PEI capable. Alternatively, this second indication may comprise information element (IE) about PEI capability and its value. For example, if the value is one of: yes, true or 1, it means that the network device 120 is PEI capable. If the value is one of: no, false or 0, it means that the network device 120 is not PEI capable.
  • the message may comprise original PEI and subgrouping configuration from SIB, such as IE PEI-config, for RAN and PEI capability info for the terminal device 110-1.
  • the terminal device 110-2 may determine 5110 whether to report its PEI information to the terminal device 110-1. In some embodiments, if the terminal device 110-2 determines that both the terminal device 110-1 and the network device 120 are PEI-capable based on the indications, the terminal device 110-2 may determine to report its PEI information. Alternatively, if the terminal device 110-2 determines that the terminal device 110-1 is PEI-capable, the terminal device 110-2 may determine to report its PEI information. The terminal device 110-2 may transmit 5140 the PEI information to the terminal device 110-1. For example, upon receiving the indication regarding that the terminal device 110-1 is PEI-capable from the terminal device 110-1, the terminal device 110-2 may transmit the PEI information to the terminal device 110-1.
  • the relay UE may send the indication of capability for both relay and RAN or its PEI capability in case the RAN is PEI-capable and/or it is PEI-capable. In this way, it can save signaling overhead for sending the indication of capability.
  • the network device 120 may transmit 5210 the SIB to the terminal device 110-1.
  • the SIB may indicate the PEI capability of the network device 120.
  • the terminal device 110-1 may determine 5220 whether to send a message about the PEI capability to the terminal device 110-2. For example, if at least one of the network device 120 or the terminal device 110-1 is PEI capable, the terminal device 110-1 may determine to send the message. Alternatively and additionally, the terminal device 110-1 may determine 5220 whether to send a message about the PEI capability to the terminal device 110-2 in case the network device 120 is PEI capable.
  • the terminal device 110-1 may transmit 5230 a message to the terminal device 110-2.
  • the message may comprise a first indication about the PEI capability of the terminal device 110-1 and a second indication of the PEI capability of the network device 120.
  • the message may comprise the first indication about the PEI capability of the terminal device 110-1.
  • this message may request the terminal device 110-2 to send its PEI information.
  • this message may be transmitted in a broadcast message.
  • this message may be in the discovery message.
  • this message may be transmitted in a dedicated message.
  • the dedicated message may be PC5-RRC message, for example, PC5-RRC Reconfiguration.
  • this first indication may indicate that the terminal device 110-1 is PEI capable.
  • this first indication may comprise information element (IE) about PEI capability and its value. For example, if the value is one of: yes, true or 1, it means that the terminal device 110-1 is PEI capable. If the value is one of: no, false or 0, it means that the terminal device 110-1 is not PEI capable.
  • the first indication may comprise PEI information related to the terminal device 110-1.
  • this second indication may indicate that the network device 120 is PEI capable.
  • this second indication may comprise information element (IE) about PEI capability and its value. For example, if the value is one of: yes, true or 1, it means that the network device 120 is PEI capable. If the value is one of: no, false or 0, it means that the network device 120 is not PEI capable.
  • the message may comprise original PEI and subgrouping configuration from SIB for RAN and PEI capability info for the terminal device 110-1.
  • the second indication may comprise the configuration of PEI.
  • the configuration of PEI may be obtained from the SIB, such as IE PEI-config.
  • the terminal device 110-2 may transmit 5240 the PEI information to the terminal device 110-1. For example, upon receiving the indication regarding that the terminal device 110-1 is PEI-capable from the terminal device 110-1, the terminal device 110-2 may transmit the PEI information to the terminal device 110-1. As another example, upon receiving the message requesting its PEI information, the terminal device 110-2 may transmit the PEI information to the terminal device 110-1. In some embodiments, if the terminal device 110-1 determine 5220 whether to send a message about the PEI capability to the terminal device 110-2 only based on the PEI capability itself, it may determine whether to monitor PEI after receiving the PEI information of the network device 120.
  • the terminal device 110-2 may transmit its PEI information during RRC procedure. For example, the transmission of the PEI information may be based on state transition or mobility under network device’s control. In some embodiments, if the terminal device 110-2 receives a RRC release message for entering an idle state or an inactive state, the terminal device 110-2 may transmit its PEI information to the terminal device 110-1. In some other embodiments, if the terminal device 110-2 performs a path switch to the terminal device 110-1, the terminal device 110-2 may transmit its PEI information to the terminal device 110-1.
  • example embodiments of monitoring the PEI and transmitting a paging record described with reference Fig. 3 can be applied in the process 500 in Figs. 5A-5C.
  • the transmission of the PEI information may be based on UE-based state transition or mobility.
  • the terminal device 110-2 may transmit its PEI information to the terminal device 110-1.
  • the terminal device 110-2 may transmit its PEI information to the terminal device 110-1 after RRC connection reestablished to the network device 120 via the terminal device 110-1.
  • the terminal device 110-2 may transmit its PEI information to the terminal device 110-1.
  • the terminal device 110-2 may transmit its PEI information to the terminal device 110-1.
  • the terminal device 110-2 may transmit its PEI information to the terminal device 110-1.
  • the terminal device 110-2 may transmit its PEI information to the terminal device 110-1. In this way, the relay UE can monitor PEI for remote UE to save power consumption of the relay UE.
  • the remote UE may report the last used cell information to the relay UE in case the indication of PEI monitoring area (i.e. PEI monitoring is limited to the last used cell) is configured by the network.
  • the network device 120 may transmit 6010 an indication of PEI monitoring area to the terminal device 110-2.
  • the indication of the PEI monitoring area may be transmitted in the SIB.
  • the indication of the PEI monitoring area may be transmitted via RRC signaling, for example, RRC release message.
  • the terminal device 110-1 may transmit 6015 the indication of PEI monitoring area to the terminal device 110-2.
  • this message may be transmitted in a broadcast message.
  • this message may be in the discovery message.
  • this message may be transmitted in a dedicated message.
  • the dedicated message may be PC5-RRC message, for example, PC5-RRC Reconfiguration.
  • the terminal device 110-1 may transmit 6015 the indications of PEI capability for the terminal device 110-1 and/or the network device 120, if the indication of PEI monitoring area is configured by the network device 120.
  • the terminal device 110-1 may determine 6020 whether to report the last cell information to the terminal device 110-2. For example, if the indication of PEI monitoring area is configured by the network device 120, the terminal device 110-1 may determine to report the last cell information to the terminal device 110-2.
  • the terminal device 110-1 may transmit 6030 the last used cell information to the terminal device 110-2.
  • the last used cell information may be transmitted in the PEI information.
  • it can enable PEI monitoring for remote UE to save power consumption of relay UE in case the PEI monitoring is limited to the last used cell.
  • the network device may provide the PEI information related to the remote UEs to the relay UE.
  • the terminal device 110-2 may transmit 7010 PEI information related to the terminal device 110-2 to the network device 120.
  • the PEI information may comprise the CN assigned subgrouping ID.
  • the PEI information may comprise the UE-ID based subgrouping ID.
  • the PEI information may comprise eDRX information of the terminal device 110-2.
  • the PEI information may comprise the last used cell information of the terminal device 110-2.
  • the terminal device 110-1 may transmit 7020 sidelink UE information (SUI) to the network device 120.
  • the SUI may comprise UE ID for its connected remoted devices (for example, the terminal device 110-2) .
  • the SUI may comprise inactive radio network temporary identifier (I-RNTI) and 5-TMSI for the remote terminal devices in the inactive state.
  • the SUI may comprise 5-TMSI for the remote terminal devices in the idle state.
  • the terminal device 110-1 may report its PEI capability to the network device 120.
  • the network device 120 may transmit 7030 PEI information for its connected remote terminal devices (for example, devices indicated by the UE ID transmitted via SUI) to the terminal device 110-1.
  • the PEI information may be transmitted via RRC signaling.
  • the PEI information may comprise a PEI capability of the terminal device 110-2.
  • the PEI information may comprise a core network (CN) assigned subgrouping identity.
  • the PEI information may comprise last used cell information of the terminal device 110-2.
  • the PEI information may comprise last serving cell information of the terminal device 110-2.
  • the PEI information may also comprise information for eDRX.
  • the information for eDRX may comprise an indication regarding that the eDRX is configured and/or a set of eDRX parameters.
  • the information for eDRX may comprise the set of eDRX parameters.
  • the set of eDRX parameters may comprise a paging time window.
  • the set of eDRX parameters may comprise an extended idle mode DRX cycle length.
  • the terminal device 110-1 may determine 7040 whether the monitor the PEI for the terminal device 110-2.
  • the determination 7040 is same as the determination 3030 shown in Fig. 3. It should be noted that example embodiments of monitoring the PEI and transmitting a paging record described with reference Fig. 3 can be applied in the process 700 in Fig. 7. In this way, the network device can provide multiple UEs’ PEI related information.
  • the network device 120 may provide the PEI information for the remote UEs during RRC procedure.
  • the PEI information may be transmitted via RRC signaling.
  • the PEI information may be transmitted via media access control control element (MAC CE) .
  • the PEI information may be transmitted based on a state transition or mobility.
  • the PEI information may be transmitted in a RRC reconfiguration message for the terminal device 110-1.
  • the PEI information may be transmitted in a RRC release message for the terminal device 110-1 to enter the idle state or the inactive state. In this way, the network device can provide dedicate UE’s PEI related information, since above procedures are UE specific procedures.
  • Fig. 8 shows a flowchart of an example method 800 in accordance with an embodiment of the present disclosure where the terminal device monitors the filler signal.
  • the method 800 can be implemented at a relay terminal device which is referred to as the first terminal device.
  • the first terminal device receives paging early indication (PEI) information related to at least one second terminal device.
  • the first terminal device relays a communication between the at least one second terminal device and a network device.
  • the PEI information related to the at least one second terminal device may comprise at least one of: a PEI capability of the at least one second terminal device and a core network (CN) assigned subgrouping identity.
  • CN core network assigned subgrouping identity.
  • the first terminal device may determine the subgrouping identity of the at least one second terminal device based on the PEI capability of the at least one second terminal device.
  • the PEI information related to the at least one second terminal device may comprise a subgrouping identity determined by the at least one second terminal device.
  • the first terminal device may determine the subgrouping identity of the at least one second terminal device based on the PEI capability of the at least one second terminal device.
  • the first terminal device determines whether to monitor a PEI for the at least one second terminal device from the network device.
  • the first terminal device may determine whether to monitor the PEI for the at least one second terminal device based on a PEI capability of the first terminal device and a PEI capability of the network device. In this case, if both the first terminal device and the network device support the PEI, the first terminal device may monitor the PEI for the at least one second terminal device.
  • the PEI comprises a subgrouping identity of the at least one second terminal device
  • the first terminal device may monitor a paging occasion according to the PEI. The first terminal device may forward a paging record of the at least one second terminal device after receiving the paging message in the paging occasion.
  • the first terminal device may determine not to monitor the PEI for the at least one second terminal device, if at least one of the following is fulfilled: the number of the at least one second terminal device exceeds a first threshold number, or the number of paging occasions or PEI occasions in which the at least one second terminal device spreads exceeds a second threshold number.
  • the first terminal device may assign a radio access network (RAN) assigned identity or paging occasion to the at least one second terminal device, if t at least one of the following is fulfilled: the number of the at least one second terminal device exceeds a first threshold number, or the number of paging occasions or PEI occasions in which the at least one second device spreads exceeds a second threshold number.
  • the first terminal device may report the RAN assigned identity or paging occasion to the network device for PEI.
  • the first terminal device may transmit, to the at least one terminal device, the RAN assigned identity or paging occasion for PEI.
  • the first terminal device may transmit to the network device a request for a RAN assigned identity or paging occasion, if at least one of the following is fulfilled: the number of the at least one second terminal device exceeds a first threshold number, or the number of paging occasions or PEI occasions in which the at least one second terminal device spreads exceeds a second threshold number.
  • the request may comprise at least one of: a second number of the at least one second terminal device, a fourth number of subgroups.
  • the first terminal device may receive, from the network device, the RAN assigned identity or paging occasion for PEI.
  • the first terminal device may transmit, to the at least one terminal device, the RAN assigned identity or paging occasion for PEI.
  • the first terminal device may transmit, to the at least one second terminal device, a message comprising a first indication about a PEI capability of the first terminal device.
  • the message is may be broadcast message or a dedicated message.
  • the first terminal device may receive receiving the PEI information from the at least one second terminal device.
  • the message may also comprise a second indication about a PEI capability of the network device.
  • the first terminal device may transmit, to the at least one second terminal device, a fifth indication to request the PEI information. In some embodiments, the first terminal device may receive the PEI information from the at least one second terminal device.
  • the first indication about the PEI capability of the first terminal device comprises at least one of: the first indication indicates that the first terminal device is PEI-capable, a first information element (IE) about the PEI capability of the first terminal device, or PEI information related to the first terminal device.
  • IE first information element
  • the second indication about the PEI capability of the network device comprises at least one of: the second indication indicates that the network device is PEI-capable, the second indication comprises a second IE about the PEI capability of the network device, or the second indication comprises the configuration of PEI.
  • the first terminal device may transmit the message to the at least one second terminal device, if the first terminal device is PEI-capable or a determination that both the first terminal device and the network device are PEI-capable.
  • the first terminal device may receive the PEI information from the at least one second terminal device, and wherein the PEI information further comprises last used cell information of the at least one second terminal device.
  • the first terminal device may determine whether to monitor the PEI for the at least one terminal based on a serving cell of the first terminal device and the last used cell information of the at least one second terminal device. If the serving cell matches a last used cell of the at least one second terminal device, the first terminal device may determine to monitor the PEI for the at least one terminal.
  • the first terminal device may receive, from the network device, a third indication of PEI monitoring area.
  • the first terminal device may forward, to the at least one second terminal device, the third indication of PEI monitoring area.
  • the third indication of PEI monitoring area may be forwarded in a broadcast message or a dedicated message.
  • the first terminal device may receive, from the network device, a third indication of PEI monitoring area. In some embodiments, the first terminal device may transmit to the at least one second terminal device, a message comprising at least one of: a first indication about a PEI capability of the first terminal device or a second indication about a PEI capability of the network device.
  • the first terminal device may determine whether the network device is PEI-capable based on the third indication. If the network device is PEI-capable, the first terminal device may transmit the message to the at least one second terminal device.
  • the first terminal device may receive the PEI information from the at least one second terminal device.
  • the PEI information may comprise information for extended DRX (eDRX) .
  • the information for eDRX may comprise a fourth indication regarding that the eDRX is may comprise and a set of eDRX parameters.
  • the information for eDRX comprises the set of eDRX parameters.
  • the first terminal device may determine a user equipment (UE) identity based subgrouping identity based on the information for eDRX, if the first terminal device monitors the PEI for the at least one second terminal device.
  • UE user equipment
  • the first terminal device may transmit, to the network device, PEI information related to the first terminal device.
  • the first terminal device may receive the PEI information from the network device.
  • the PEI information comprises at least one of: a PEI capability of the at least one second terminal device, last used cell information of the at least one second terminal device, or information for extended DRX (eDRX) .
  • the PEI information is at least in a radio resource control (RRC) configuration message, or a RRC release message.
  • RRC radio resource control
  • Fig. 9 shows a flowchart of an example method 900 in accordance with an embodiment of the present disclosure where the terminal device monitors the filler signal.
  • the method 900 can be implemented at a remote terminal device which is referred to as the second terminal device.
  • the second terminal device transmits, to a first terminal device, PEI information related to the second terminal device.
  • the first terminal device relays a communication between the second terminal device and a network device.
  • the PEI information related to the at least one second terminal device comprises at least one of: a PEI capability of the at least one second terminal device and a core network (CN) assuaged subgroup identity.
  • the PEI information related to the at least one second terminal device comprises a subgrouping identity determined by the at least one second terminal device.
  • the second terminal device may receive, from the first terminal device, a radio access network (RAN) identity or paging occasion for PEI.
  • RAN radio access network
  • the second terminal device may receive, from the first terminal device, a message comprising a first indication about a PEI capability of the first terminal device.
  • the message may be a broadcast message or a dedicated message.
  • the second terminal device in response to the reception of the message, may transmit the PEI information to the first terminal device.
  • the message further comprises a second indication about a PEI capability of the network device.
  • the second terminal device may receive, from the first terminal device, a fifth indication to request the PEI information, and wherein the message is a broadcast message or a dedicated message. In some embodiments, the second terminal device may transmit the PEI information to the first terminal device, in response to the reception of the fifth indication.
  • the first indication about the PEI capability of the first terminal device comprises at least one of: the first indication indicates that the first terminal device is PEI-capable, the first indication comprises a first information element (IE) about the PEI capability of the first terminal device, or the first indication comprises PEI information related to the first terminal device.
  • IE first information element
  • the second terminal device may receive, from the network device, a second information about the PEI capability of the network device.
  • the second indication about the PEI capability of the network device comprises at least one of: the second indication indicates that the network device is PEI-capable, the second indication comprises a second IE about the PEI capability of the network device, or the second indication comprises the configuration of PEI.
  • the second terminal device may transmit the PEI information to the first terminal device, if at least one of the followings is fulfilled: the second terminal device receives a RRC release message for entering an idle state or an inactive state, the second terminal device performs a path switch to the first terminal device, the second terminal device receives establishes a RRC connection with the network device, the second terminal device determines to enter the idle state, or the second terminal device performs a reselection to the first terminal device.
  • the PEI information further comprises last used cell information of the at least one second terminal device.
  • the second terminal device may receive, form the network device, a third indication of PEI monitoring area, and wherein the third indication of PEI monitoring area is forwarded in a system information block or a RRC message.
  • the second terminal device may receive, form the first terminal device, a third indication of PEI monitoring area, and wherein the third indication of PEI monitoring area is forwarded in a broadcast message or a dedicated message.
  • the second terminal device may transmit the PEI information to the first terminal device, in response to the reception of the third indication of PEI monitoring area.
  • the PEI information further comprises information for extended DRX (eDRX) .
  • the information for eDRX comprises: a fourth indication regarding that the eDRX is configured and a set of eDRX parameters.
  • the information for eDRX comprises the set of eDRX parameters.
  • the second terminal device may transmit the PEI information related to the at least one second terminal device to the network device.
  • Fig. 10 shows a flowchart of an example method 1000 in accordance with an embodiment of the present disclosure where the terminal device monitors the filler signal.
  • the method 1000 can be implemented at a network device.
  • the network device transmits, to a first terminal device, PEI information related to at least one second terminal device.
  • the PEI information comprises at least one of: a PEIC capability of the second terminal device, last used cell information of the at least one second terminal device, or information for extended DRX.
  • a first terminal device comprises circuitry configured to perform: receiving paging early indication (PEI) information related to at least one second terminal device, wherein the first terminal device relays a communication between the at least one second terminal device and a network device; and determining whether to monitor a PEI for the at least one second terminal device from the network device.
  • PEI paging early indication
  • the PEI information related to the at least one second terminal device comprises at least one of: a PEI capability of the at least one second terminal device and a core network (CN) assigned subgrouping identity, or wherein the PEI information related to the at least one second terminal device comprises a subgrouping identity determined by the at least one second terminal device.
  • CN core network
  • the first terminal device comprises circuitry configured to perform: in accordance with a determining that first terminal device monitors the PEI for the at least one second terminal device, determining the subgrouping identity of the at least one second terminal device based on the PEI capability of the at least one second terminal device.
  • the first terminal device comprises circuitry configured to perform determine whether to monitor the PEI for the second terminal device by: determining whether to monitor the PEI for the at least one second terminal device based on a PEI capability of the first terminal device and a PEI capability of the network device. In some embodiments, the first terminal device comprises circuitry configured to perform in accordance with a determination that both the first terminal device and the network device support the PEI, monitoring the PEI for the at least one second terminal device.
  • the first terminal device comprises circuitry configured to perform in accordance with a determination that the PEI comprises a subgrouping identity of the at least one second terminal device, monitoring a paging occasion according to the PEI; and forwarding a paging record of the at least one second terminal device after receiving the paging message in the paging occasion.
  • the first terminal device comprises circuitry configured to perform determine whether to monitor the PEI for the at least one second terminal device by:determining not to monitor the PEI for the at least one second terminal device, in accordance with a determination that at least one of the following is fulfilled: the number of the at least one second terminal device exceeds a first threshold number, or the number of paging occasions or PEI occasions in which the at least one second terminal device spreads exceeds a second threshold number.
  • the first terminal device comprises circuitry configured to perform assigning a radio access network (RAN) assigned identity or paging occasion to the at least one second terminal device in accordance with a determination that at least one of the following is fulfilled: the number of the at least one second terminal device exceeds a first threshold number, or the number of paging occasions or PEI occasions in which the at least one second device spreads exceeds a second threshold number; reporting the RAN assigned identity or paging occasion to the network device for PEI; and transmitting, to the at least one terminal device, the RAN assigned identity or paging occasion for PEI.
  • RAN radio access network
  • the first terminal device comprises circuitry configured to perform transmitting to the network device a request for a RAN assigned identity or paging occasion, in accordance with a determination that at least one of the following is fulfilled: the number of the at least one second terminal device exceeds a first threshold number, or the number of paging occasions or PEI occasions in which the at least one second terminal device spreads exceeds a second threshold number, wherein the request comprises at least one of: a second number of the at least one second terminal device, a fourth number of subgroups; receiving, from the network device, the RAN assigned identity or paging occasion for PEI; and transmitting, to the at least one terminal device, the RAN assigned identity or paging occasion for PEI.
  • the first terminal device comprises circuitry configured to perform transmitting, to the at least one second terminal device, a message comprising a first indication about a PEI capability of the first terminal device, and wherein the message is a broadcast message or a dedicated message; and wherein receiving the PEI information related to the at least one second terminal device comprises: receiving the PEI information from the at least one second terminal device.
  • the message further comprises a second indication about a PEI capability of the network device.
  • the first terminal device comprises circuitry configured to perform transmitting, to the at least one second terminal device, a fifth indication to request the PEI information; and wherein receiving the PEI information related to the at least one second terminal device comprises: receiving the PEI information from the at least one second terminal device.
  • the first indication about the PEI capability of the first terminal device comprises at least one of: the first indication indicates that the first terminal device is PEI-capable, a first information element (IE) about the PEI capability of the first terminal device, or PEI information related to the first terminal device.
  • IE first information element
  • the second indication about the PEI capability of the network device comprises at least one of: the second indication indicates that the network device is PEI-capable, the second indication comprises a second IE about the PEI capability of the network device, or the second indication comprises the configuration of PEI.
  • the first terminal device comprises circuitry configured to perform transmit the message by: in accordance with a determination that the first terminal device is PEI-capable or a determination that both the first terminal device and the network device are PEI-capable, transmitting the message to the at least one second terminal device.
  • the first terminal device comprises circuitry configured to perform receive the PEI information related to the at least one second terminal device by: receiving the PEI information from the at least one second terminal device, and wherein the PEI information further comprises last used cell information of the at least one second terminal device.
  • the first terminal device comprises circuitry configured to perform determine whether to monitor the PEI for the at least one terminal device by: determining whether to monitor the PEI for the at least one terminal based on a serving cell of the first terminal device and the last used cell information of the at least one second terminal device; and in accordance with a determination that the serving cell matches a last used cell of the at least one second terminal device, determining to monitor the PEI for the at least one terminal.
  • the first terminal device comprises circuitry configured to perform receive, from the network device, a third indication of PEI monitoring area; and forward, to the at least one second terminal device, the third indication of PEI monitoring area, and wherein the third indication of PEI monitoring area is forwarded in a broadcast message or a dedicated message.
  • the first terminal device comprises circuitry configured to perform receive, from the network device, a third indication of PEI monitoring area; and transmitting to the at least one second terminal device, a message comprising at least one of: a first indication about a PEI capability of the first terminal device or a second indication about a PEI capability of the network device.
  • the first terminal device comprises circuitry configured to perform transmit the message by determining whether the network device is PEI-capable based on the third indication; and in accordance with a determination that the network device is PEI-capable, transmitting the message to the at least one second terminal device.
  • the first terminal device comprises circuitry configured to perform receiving the PEI information related to the at least one second terminal device by: receiving the PEI information from the at least one second terminal device, and wherein the PEI information comprises information for extended DRX (eDRX) .
  • eDRX extended DRX
  • the information for eDRX comprises a fourth indication regarding that the eDRX is configured and a set of eDRX parameters, or the information for eDRX comprises the set of eDRX parameters.
  • the first terminal device comprises circuitry configured to perform in accordance with a determination that the first terminal device monitors the PEI for the at least one second terminal device, determine a user equipment (UE) identity based subgrouping identity based on the information for eDRX.
  • UE user equipment
  • the first terminal device comprises circuitry configured to perform transmit, to the network device, PEI information related to the first terminal device.
  • the first terminal device comprises circuitry configured to perform receive the PEI information related to the at least one second terminal device by: receiving the PEI information from the network device, wherein the PEI information comprises at least one of: a PEI capability of the at least one second terminal device, last used cell information of the at least one second terminal device, or information for extended DRX (eDRX) .
  • the PEI information comprises at least one of: a PEI capability of the at least one second terminal device, last used cell information of the at least one second terminal device, or information for extended DRX (eDRX) .
  • the PEI information is at least in a radio resource control (RRC) configuration message, or a RRC release message.
  • RRC radio resource control
  • a second terminal device comprises circuitry configured to perform transmitting, at a second terminal device and to a first terminal device, PEI information related to the second terminal device, wherein the first terminal device relays a communication between the second terminal device and a network device.
  • the PEI information related to the at least one second terminal device comprises at least one of: a PEI capability of the at least one second terminal device and a core network (CN) assuaged subgroup identity, or wherein the PEI information related to the at least one second terminal device comprises a subgrouping identity determined by the at least one second terminal device.
  • CN core network
  • the second terminal device comprises circuitry configured to perform receiving, from the first terminal device, a radio access network (RAN) identity or paging occasion for PEI.
  • RAN radio access network
  • a second terminal device comprises circuitry configured to perform receiving, from the first terminal device, a message comprising a first indication about a PEI capability of the first terminal device, and wherein the message is a broadcast message or a dedicated message; and wherein transmitting the PEI information comprises: in response to the reception of the message, transmitting the PEI information to the first terminal device.
  • the message further comprises a second indication about a PEI capability of the network device.
  • the second terminal device comprises circuitry configured to perform receiving, from the first terminal device, a fifth indication to request the PEI information, and wherein the message is a broadcast message or a dedicated message; and wherein transmitting the PEI information comprises: in response to the reception of the fifth indication, transmitting the PEI information to the first terminal device.
  • the first indication about the PEI capability of the first terminal device comprises at least one of: the first indication indicates that the first terminal device is PEI-capable, the first indication comprises a first information element (IE) about the PEI capability of the first terminal device, or the first indication comprises PEI information related to the first terminal device.
  • IE first information element
  • the second terminal device comprises circuitry configured to perform receiving, from the network device, a second information about the PEI capability of the network device.
  • the second indication about the PEI capability of the network device comprises at least one of: the second indication indicates that the network device is PEI-capable, the second indication comprises a second IE about the PEI capability of the network device, or the second indication comprises the configuration of PEI.
  • the second terminal device comprises circuitry configured to perform transmitting the PEI information related to the at least one second terminal device by: transmitting the PEI information to the first terminal device, in accordance with a determination that at least one of the followings is fulfilled: the second terminal device receives a RRC release message for entering an idle state or an inactive state, the second terminal device performs a path switch to the first terminal device, the second terminal device receives establishes a RRC connection with the network device, the second terminal device determines to enter the idle state, or the second terminal device performs a reselection to the first terminal device.
  • the PEI information further comprises last used cell information of the at least one second terminal device.
  • the second terminal device comprises circuitry configured to perform receiving, form the network device, a third indication of PEI monitoring area, and wherein the third indication of PEI monitoring area is forwarded in a system information block or a RRC message.
  • the second terminal device comprises circuitry configured to perform receiving, form the first terminal device, a third indication of PEI monitoring area, and wherein the third indication of PEI monitoring area is forwarded in a broadcast message or a dedicated message.
  • the second terminal device comprises circuitry configured to perform transmitting the PEI information by: in response to the reception of the third indication of PEI monitoring area, transmitting the PEI information to the first terminal device.
  • the PEI information further comprises information for extended DRX (eDRX) .
  • the information for eDRX comprises: a fourth indication regarding that the eDRX is configured and a set of eDRX parameters, or wherein the information for eDRX comprises the set of eDRX parameters.
  • the second terminal device comprises circuitry configured to perform transmitting the PEI information related to the at least one second terminal device to the network device.
  • a network device comprises circuitry configured to perform transmitting, at a network device and to a first terminal device, PEI information related to at least one second terminal device, wherein the PEI information comprises at least one of: a PEIC capability of the second terminal device, last used cell information of the at least one second terminal device, or information for extended DRX (eDRX) .
  • PEI information comprises at least one of: a PEIC capability of the second terminal device, last used cell information of the at least one second terminal device, or information for extended DRX (eDRX) .
  • Fig. 11 is a simplified block diagram of a device 1100 that is suitable for implementing embodiments of the present disclosure.
  • the device 1100 can be considered as a further example implementation of the terminal devices 110 as shown in Figs. 1A and 1B. Accordingly, the device 1100 can be implemented at or as at least a part of the terminal device 110-1 or the terminal device 110-2.
  • the device 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transmitter (TX) and receiver (RX) 1140 coupled to the processor 1110, and a communication interface coupled to the TX/RX 1140.
  • the memory 1120 stores at least a part of a program 1130.
  • the TX/RX 1140 is for bidirectional communications.
  • the TX/RX 1140 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2 interface for bidirectional communications between eNBs, S1 interface for communication between a Mobility Management Entity (MME) /Serving Gateway (S-GW) and the eNB, Un interface for communication between the eNB and a relay node (RN) , or Uu interface for communication between the eNB and a terminal device.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Un interface for communication between the eNB and a relay node (RN)
  • Uu interface for communication between the eNB and a terminal device.
  • the program 1130 is assumed to include program instructions that, when executed by the associated processor 1110, enable the device 1100 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Fig. 3 to 10.
  • the embodiments herein may be implemented by computer software executable by the processor 1110 of the device 1100, or by hardware, or by a combination of software and hardware.
  • the processor 1110 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 1110 and memory 1120 may form processing means 1150 adapted to implement various embodiments of the present disclosure.
  • the memory 1120 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1120 is shown in the device 1100, there may be several physically distinct memory modules in the device 1100.
  • the processor 1110 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1100 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to Figs. 3 to 10.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic/flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eX
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , Network-controlled Repeaters, and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node such
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial intelligence
  • Machine learning capability it generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • the terminal device may have more than one connections with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • the network device may have the function of network energy saving, Self-Organising Networks (SON) /Minimization of Drive Tests (MDT) .
  • the terminal may have the function of power saving.
  • test equipment e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés, des dispositifs et un support lisible par ordinateur destinés à la communication. Selon des modes de réalisation de la présente divulgation, un dispositif terminal relais reçoit des informations d'indication précoce de radiomessagerie (PEI) relatives à au moins un dispositif terminal distant en provenance d'un dispositif de réseau ou du ou des dispositifs terminaux distants. Le dispositif terminal relais détermine s'il faut surveiller une PEI pour le ou les dispositifs terminaux distants en provenance du dispositif de réseau. De cette manière, il permet une surveillance de PEI pour un dispositif terminal distant, afin d'économiser la consommation d'énergie du dispositif terminal relais.
PCT/CN2022/087512 2022-04-18 2022-04-18 Procédés, dispositifs et support lisible par ordinateur destinés à la communication WO2023201496A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/087512 WO2023201496A1 (fr) 2022-04-18 2022-04-18 Procédés, dispositifs et support lisible par ordinateur destinés à la communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/087512 WO2023201496A1 (fr) 2022-04-18 2022-04-18 Procédés, dispositifs et support lisible par ordinateur destinés à la communication

Publications (1)

Publication Number Publication Date
WO2023201496A1 true WO2023201496A1 (fr) 2023-10-26

Family

ID=88418931

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/087512 WO2023201496A1 (fr) 2022-04-18 2022-04-18 Procédés, dispositifs et support lisible par ordinateur destinés à la communication

Country Status (1)

Country Link
WO (1) WO2023201496A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019030576A1 (fr) * 2017-08-08 2019-02-14 Alcatel Lucent Procédé, dispositif et support lisible par ordinateur pour une communication de dispositif à dispositif (d2d)
WO2021238993A1 (fr) * 2020-05-26 2021-12-02 FG Innovation Company Limited Équipement utilisateur et procédé d'économie d'énergie à l'état rrc inactif ou rrc en veille
WO2022007844A1 (fr) * 2020-07-08 2022-01-13 Mediatek Inc. Mécanisme de radiorecherche à faible consommation d'énergie avec indicateur précoce de radiorecherche (pei) à base d'une séquence
US20220046585A1 (en) * 2020-08-04 2022-02-10 Samsung Electronics Co., Ltd. Method and apparatus for performing paging in a communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019030576A1 (fr) * 2017-08-08 2019-02-14 Alcatel Lucent Procédé, dispositif et support lisible par ordinateur pour une communication de dispositif à dispositif (d2d)
WO2021238993A1 (fr) * 2020-05-26 2021-12-02 FG Innovation Company Limited Équipement utilisateur et procédé d'économie d'énergie à l'état rrc inactif ou rrc en veille
WO2022007844A1 (fr) * 2020-07-08 2022-01-13 Mediatek Inc. Mécanisme de radiorecherche à faible consommation d'énergie avec indicateur précoce de radiorecherche (pei) à base d'une séquence
US20220046585A1 (en) * 2020-08-04 2022-02-10 Samsung Electronics Co., Ltd. Method and apparatus for performing paging in a communication system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON, VODAFONE: "PEI monitoring in last used cell", 3GPP DRAFT; R2-2110415, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. eMeeting; 20211101 - 20211112, 22 October 2021 (2021-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052066856 *
QUALCOMM INC: "Power saving enhancements for paging reception", 3GPP DRAFT; R2-2100313, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973505 *

Similar Documents

Publication Publication Date Title
KR102064309B1 (ko) 시스템 정보를 온 디맨드로 브로드캐스팅하기 위한 방법들 및 디바이스들
KR20200138402A (ko) 채널 통신을 페이징하기 위한 빔 검색 파일럿
WO2024007176A1 (fr) Procédés, dispositifs et support de communication
WO2023201496A1 (fr) Procédés, dispositifs et support lisible par ordinateur destinés à la communication
US20240015616A1 (en) Method, device and computer storage medium of communication
WO2021102837A1 (fr) Procédés, dispositifs et support pour la communication
WO2020154855A1 (fr) Amélioration de la mobilité d'un dispositif terminal
WO2023050148A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour communication
WO2024087233A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
WO2023141904A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour des communications
WO2023178478A1 (fr) Procédé, dispositif et support de stockage informatique destinés à la communication
WO2023060601A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés à des communications
WO2023141941A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour des communications
WO2023178694A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés aux communications
WO2023159485A1 (fr) Procédé, dispositif et support de stockage informatique destinés à la communication
WO2023108502A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024103364A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
WO2023097657A1 (fr) Procédé, dispositif et support de stockage destinés à des communications
WO2024103363A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
WO2023173423A1 (fr) Procédés, dispositifs et support lisible par ordinateur pour des communications
WO2023147705A1 (fr) Procédés, dispositifs et support lisible par ordinateur destinés à des communications
WO2023236178A1 (fr) Procédé, dispositif et support lisible par ordinateur pour des communications de liaison latérale
WO2024000601A1 (fr) Procédés, dispositifs, ainsi que support de communication
WO2023141830A1 (fr) Procédé, dispositif et support de stockage destinés à la communication
WO2024087170A1 (fr) Procédé, dispositif et support de stockage informatique de communication

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: 22937734

Country of ref document: EP

Kind code of ref document: A1