WO2017173158A1 - Messagerie de radiorecherche provenant d'un réseau d'accès radio (ran) - Google Patents

Messagerie de radiorecherche provenant d'un réseau d'accès radio (ran) Download PDF

Info

Publication number
WO2017173158A1
WO2017173158A1 PCT/US2017/025164 US2017025164W WO2017173158A1 WO 2017173158 A1 WO2017173158 A1 WO 2017173158A1 US 2017025164 W US2017025164 W US 2017025164W WO 2017173158 A1 WO2017173158 A1 WO 2017173158A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran
paging
base station
node
message
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2017/025164
Other languages
English (en)
Inventor
Richard Burbidge
Sudeep Palat
Alexandre Stojanovski
Sangeetha Bangolae
Marta MARTINEZ TARRADELL
Mo-Han Fong
Youn Hyoung Heo
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel IP Corp
Original Assignee
Intel IP Corp
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 Intel IP Corp filed Critical Intel IP Corp
Priority to CN201780014275.2A priority Critical patent/CN108702732B/zh
Priority to HK19100740.2A priority patent/HK1258369B/xx
Publication of WO2017173158A1 publication Critical patent/WO2017173158A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/04—User notification, e.g. alerting and paging, for incoming communication, change of service or the like multi-step notification using statistical or historical mobility data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • OFDM orthogonal frequency-division multiplexing
  • 3 GPP third generation partnership project
  • LTE long term evolution
  • IEEE Institute of Electrical and Electronics Engineers 802.16 standard
  • WiMAX Worldwide Interoperability for Microwave Access
  • WiFi Wireless Fidelity
  • the node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
  • RNCs Radio Network Controllers
  • the downlink (DL) transmission can be a communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.
  • UE user equipment
  • FIG. 1 illustrates a wireless communication system in accordance with an example
  • FIG. 2 illustrates signaling between an eNodeB and a user equipment (UE) for paging in accordance with an example
  • UE user equipment
  • FIG. 3 is a flowchart illustrating operations for performing paging between an eNodeB and a user equipment (UE) in accordance with an example
  • FIG. 4 depicts functionality of a base station operable to provide paging messages to a user equipment (UE) in accordance with an example
  • FIG. 5 depicts functionality of a user equipment (UE) operable to decode paging messages received from a base station in accordance with an example
  • FIG. 7 illustrates an architecture of a wireless network in accordance with an example
  • FIG. 9 illustrates interfaces of baseband circuitry in accordance with an example
  • FIG. 10 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.
  • FIG. 1 illustrates an exemplary wireless communication system 100.
  • the wireless communication system 100 can be an LTE wireless communication system.
  • the wireless communication system 100 can include mobility management entities (MMEs) / serving gateways (S-GWs) 102, 104.
  • the wireless communication system can include eNodeBs 106, 108, 110 in an E-UTRAN 112.
  • the MMEs / S-GWs 102, 104 can each be connected to the eNodeBs 106, 108, 110 over an SI interface.
  • Each of the eNodeBs 106, 108, 110 can be connected to each other over an X2 interface.
  • the eNodeBs 106, 108, 110 can be connected to one or more user equipment (UE) 114 over an Uu interface.
  • UE user equipment
  • the wireless communication system 100 can support fifth generation (5G/) new radio (NR) capabilities.
  • the MMEs / S-GWs 102, 104 can be referred to as next generation-control plane / user plane gateways (NG- CP/UPGW), the eNodeBs 106, 108, 110 can be referred to as enhanced LTE (eLTE) eNBs or gNBs.
  • eLTE enhanced LTE
  • the eLTE eNBs or gNBs can be connected to each other over an Xn interface.
  • the wireless communication system 100 can support a reduced bandwidth or narrowband, new radio access technologies/networks (RAT/RAN) and/or new core networks (CN).
  • RAT/RAN new radio access technologies/networks
  • CN new core networks
  • the UE 114 can be in a radio resource control (RRC) connected state or an RRC idle state.
  • RRC radio resource control
  • the UE 114 and an eNodeB 106 have a UE context that stores a current RAN configuration for the UE 114, which can be used for communication between the UE 114 and the eNodeB 106 (or network).
  • the UE 114 when the UE 114 has no data to send, the UE 114 can be moved to the RRC idle state and the UE context in the eNodeB 106 can be released.
  • the UE 114 may not communicate with the eNodeB 106 (or network).
  • the UE 114 when the UE 114 is in the RRC idle state and there is data to be exchanged between the UE 114 and the eNodeB 106 (or network), the UE 114 can transition to the RRC connected state in order to exchange the data.
  • the UE context (with a current RAN configuration for the UE 114) can be established in the eNodeB 106 and the UE 114.
  • the establishment of the UE context in the eNodeB 106 and the UE 114 can involve a relatively large amount of signaling (in terms of number of messages and number of bytes that are exchanged between the UE 114 and the eNodeB 106).
  • the UE 114 when the UE 114 is in the RRC idle state (i.e., the UE context is not maintained in the UE 114 and the eNodeB 106, but the UE context is stored in an MME and S-GW), the UE 114 can update the network on its location each time the UE 114 crosses a geographical area (or tracking area). For example, the UE 114 can inform the MME when the UE 114 enters a tracking area 2 (TA2). When there is downlink data to be delivered from the network to the UE 114, the data can first be passed from the S-GW to the MME, and the MME can subsequently page the UE 114.
  • TA2 tracking area 2
  • the MME can send a paging message to all eNodeBs in that particular tracking area.
  • the paging for the UE 114 can be initiated by the MME.
  • the paging message is a broadcast message that can be listened to by a plurality of UEs, and the paging message can have one or more UE identifiers for a particular UE 114 for which the paging message is applicable.
  • the UE identifier (ID) in the paging message can be used to wake up a specific UE (e.g., UE 114).
  • UE e.g., UE 114
  • several identifiers can be associated with the UE 114.
  • LTE systems can use protocol layer transparency, so each protocol layer can provide its own UE identifier.
  • a RAN-based ID is a cell radio network temporary identifier (C-RNTI)
  • C-RNTI cell radio network temporary identifier
  • NAS CN
  • SAE System Architecture Evolution
  • the UE 114 can transition to the RRC connected state using a reduced signaling load, which can be achieved by storing a last used UE context (with a last used RAN configuration for the UE 114) in the eNodeB 106 and the UE 114 even when the UE 114 is in the RRC ide mode. Therefore, when the UE 114 transitions from the RRC idle mode to the RRC connected mode, the UE 114 can simply revive the stored last used UE context in the eNodeB 106 and the UE 114. This resumption (or revival) of the stored last used UE context can involve a reduced amount of signaling, thereby reducing the number of messages and the number of bytes that are exchanged between the UE 114 and the eNodeB 106.
  • the UE 114 can utilize a discontinuous reception (DRX) mechanism for power saving when the UE 114 is in the RRC idle mode (or suspended mode).
  • the suspended mode can be part of an RRC connected mode.
  • DRX discontinuous reception
  • the UE 114 can only wake up for a short period of time to monitor for a paging message and can be asleep for the remainder of a paging cycle.
  • a period for which the UE 114 wakes up to monitor for the paging message can be referred to as a DRX cycle length parameter, which can be selected by the UE 114.
  • the DRX cycle length parameter can effectively determine a delay to provide data to the UE 114.
  • the DRX cycle length parameter can be negotiated between the UE 114 and the MME using non access stratum (NAS) signaling when the UE 114 attaches to the network or when the UE 114 sends a tracking area update (TAU). Since the DRX cycle length parameter can be negotiated between the UE 114 and the MME, this parameter can be referred to as a core network (CN) DRX cycle length parameter. In addition, in previous solutions, the selection of the DRX cycle length parameter by the UE during attach/TAU does not allow the DRX cycle length parameter to be controlled based on current traffic constraints for the UE 114.
  • NAS non access stratum
  • TAU tracking area update
  • the UEs that monitors for paging messages can be in various states.
  • a "UE-1" or “UE in idle” can indicate a UE that is released to the RRC idle mode (RRC IDLE), as in legacy LTE.
  • RRC IDLE RRC idle mode
  • UE AS context is not stored by the UE or the RAN node, i.e., the UE is not suspended.
  • a "UE-2" or "UE suspended” can indicate a UE that is suspended, e.g., as defined in 3GPP LTE
  • a UE can be released to the RRC idle mode, and the UE can store the UE AS context which is also stored in the eNodeB.
  • the UE can use a DRX cycle based on legacy LTE (e.g., a minimum of a UE specific paging DRX cycle, indicated to the UE via NAS, and a cell specific paging DRX cycle) and paging for the UE can be triggered by the MME (CN node).
  • legacy LTE e.g., a minimum of a UE specific paging DRX cycle, indicated to the UE via NAS, and a cell specific paging DRX cycle
  • a "UE-3" or “UE in light connected” or “UE in light state” or “UE suspended that are paged by RAN node” or “UE suspended with RAN DRX cycle” can indicate a UE that is suspended similarly to "UE-2" but the UE can be allocated with a different kind of DRX cycle and the paging message can be triggered by the RAN node, as described in further details below.
  • FIG. 2 illustrates exemplary signaling between an eNodeB 210 and a user equipment (UE) 220 for paging.
  • the UE 220 can be in suspended state, and therefore, UE context information for the UE 220 can be stored in memory of the eNodeB 210 and the UE 220.
  • the eNodeB 210 can determine radio access network (RAN)-based UE paging parameters for configuration of the UE 220 when the UE 220 is in the suspended state.
  • RAN-based UE paging parameters can include a RAN discontinuous reception (DRX) cycle length paging parameter and a UE paging identifier (ID) (or simply UE ID).
  • DRX RAN discontinuous reception
  • ID UE paging identifier
  • the eNodeB 210 can receive a power saving preference message from the UE 220, and the eNodeB 210 can determine the RAN DRX cycle length paging parameter based on the power saving preference message.
  • the eNodeB 210 can receive a message from the UE 220 that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE 220.
  • QoS quality of service
  • DRBs data radio bearers
  • the eNodeB 210 can receive QoS constraints and power saving information related to the UE 220 from a core network (CN) node, such as an MME.
  • CN core network
  • the eNodeB 210 can determine the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE 220. In other words, based on the power saving preference message and/or the QoS constraints for the DRBs, the eNodeB 210 can determine the RAN DRX cycle length paging parameter, which is one of the RAN-based UE paging parameters for the UE 220.
  • the eNodeB 210 can send the RAN-based UE paging parameters (which can include the RAN DRX cycle length paging parameter and the UE paging ID) to the UE 220.
  • the UE 220 can receive the RAN-based UE paging parameters, and the UE 220 can store the RAN-based UE paging parameters for subsequent usage.
  • the eNodeB 210 can receive a message from the UE 220 that indicates QoS constraints for one or more DRBs established for the UE 220 or applications executed at the UE 220, and the eNodeB 210 can select different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.
  • the eNodeB 210 can send the RAN-based UE paging parameters (which can include the different RAN DRX cycle length paging parameters for each DRB or application category and the UE paging ID) to the UE 220.
  • the eNodeB 210 can receive downlink data for the UE 220.
  • the eNodeB 210 can receive the downlink data from an MME (not shown), and the downlink data can be for the UE 220.
  • the eNodeB 210 can send a RAN- originated paging message to the UE 220 when the UE 220 is in the suspended state, which can indicate to the UE 220 that the eNodeB 210 is currently holding downlink data for the UE 220 (i.e., downlink data to be retrieved by the UE 220).
  • the eNodeB 210 can directly send the RAN-originated paging message to the UE 220 (i.e., the paging message originates at the eNodeB 210 and not at another CN node, such as an MME).
  • the UE 220 can receive the RAN-originated paging message in accordance with the RAN-based UE paging parameters that were previously received at the UE 220.
  • the UE 220 can monitor for the RAN-originated paging message in accordance with the DRX cycle length paging parameter included in the RAN-based UE paging parameters.
  • the UE 220 can detect the RAN-originated paging message based on the UE paging ID.
  • the UE 220 can initiate a transition to a radio resource control (RRC) connected state to retrieve the downlink data from the eNodeB 210 after receiving the RAN-originated paging message.
  • RRC radio resource control
  • the downlink data can be sent to the UE 220 in an inactive state without fully transitioning to the RRC connected state.
  • the eNodeB 210 can receive a NAS UE ID from a CN node, such as an MME (not shown).
  • the eNodeB 210 can receive NAS DRX paging parameters received from the CN node.
  • the eNodeB 210 can store the NAS UE ID and the NAS DRX paging parameters along with UE RAN context for the UE 220.
  • the eNodeB 210 can include the NAS UE ID and the NAS DRX paging parameters received from the CN node in the RAN-based UE paging parameters.
  • the eNodeB 210 can send the RAN-based UE paging parameters (with the NAS UE ID and the NAS DRX paging parameters) to the UE 220.
  • the eNodeB 210 can receive the power saving preference message and/or the QoS constraints for the DRBs established for the UE 220, and the eNodeB 210 can determine the RAN DRX cycle length paging parameter, which is one of the RAN-based UE paging parameters for the UE 220.
  • the RAN- based UE paging parameters can be negotiated between the UE 220 and the eNodeB 210.
  • the eNodeB 210 can send the RAN-based UE paging parameters to a CN node, such as an MME.
  • the CN node can receive and store the RAN-based UE paging parameters, and the CN node can utilize the RAN-based UE paging parameters for subsequent paging messages from the CN node (i.e., CN-originated paging messages).
  • the eNodeB 210 can send certain paging parameters to the CN node, and the CN node can originate the paging message using these paging parameters (and possibly other parameters)
  • the eNodeB 210 can originate the paging message and send the RAN-originated paging message across a paging area.
  • the paging area may be the same or different than a tracking area. Since the paging area can include multiple eNodeBs, the eNodeB 210 can send the RAN-originated paging message to other eNodeBs across X2 connections.
  • the X2 connections may not exist between al of the eNodeBs, and in this case, the eNodeB 210 can request the MME (which is connected to all of the eNodeBs in the paging area) to forward the RAN- originated paging message to all of the eNodeBs in the paging area.
  • the MME which is connected to all of the eNodeBs in the paging area
  • the CN node e.g., MME
  • the CN node can consider the QoS constraints for the DRBs established for UE 220, and the CN node can determine a DRX cycle length paging parameter based on the QoS constraints.
  • the CN node can provide the DRX cycle length paging parameter to the UE 220 directly over NAS signaling or RRC signaling.
  • the eNodeB 210 can send the RAN-originated paging message with the NAS UE ID and the NAS DRX cycle (in addition to the RAN-based UE ID and DRX cycle length parameter).
  • a control plane node in the network can store UE RAN context along with a RAN DRX cycle length parameter (which may be different from a CN DRX cycle length parameter).
  • the Sl-U bearers can be retained to a user plane node.
  • the user plane node and the control plane node can be the same node or different nodes. These nodes can be the same as a last serving eNodeB for the UE, or these nodes can include previous eNodeBs that have served the UE, or these nodes can include a node that is serving as an anchor point for the UE storing the UE RAN context and terminating the Sl-U bearers associated with the user plane.
  • the RAN DRX cycle length parameter provided to the UE can take into consideration UE power saving constraints, a desired QoS for established data radio bearers (DRBs), etc.
  • DRB can contain data from different TCP/IP flows (e.g., a voice session which utilizes an increased QoS can be associated with a certain DRB).
  • the network can configure a short DRX cycle length parameter for the UE that causes the UE to wake up more frequently.
  • the network can configure a long DRX cycle length parameter for the UE that causes the UE to wake up less frequently.
  • the network can configure specific DRX cycle length parameters that satisfy particular DRB constraints for the UE.
  • This dynamic configuration of the DRX cycle length parameters based on specific DRBs can be in contrast to static DRX cycle length parameters that are agnostic to the DRBs that are used.
  • This dynamic configuration of the DRX cycle length parameters can be based on the QoS constraints for a particular DRB for a particular UE, which allows for more flexible DRX
  • the RAN DRX cycle length parameter can be a network configured value (any value) or chosen from a list such as/similar to long DRX cycle parameters defined for a connected mode DRX configuration that is already defined over a wide range.
  • the RAN DRX cycle length parameter can be determined from/based on the connected DRX parameters.
  • a new default value can be broadcast by the network, although the QoS of individual UEs may not be taken into consideration in this example.
  • a CN node in a legacy LTE paging mechanism, can negotiate a CN DRX cycle length parameter with the UE and the CN node can trigger the paging for the UE.
  • the UE in the legacy LTE paging mechanism, can be a UE-1 or a UE-2.
  • a RAN node e.g., eNodeB
  • the UE can be a UE-3.
  • the RAN node can be an anchor for a paging decision, as opposed to the CN node, as in the legacy LTE paging mechanism.
  • a RAN paging message can be defined in different manners independent of whether the CN node or the RAN node triggers the paging for the UE.
  • a same RAN paging message e.g., RRC paging message
  • can be used to page UEs e.g., UE-1, UE-2 or UE-3 when the paging originates at the CN node or the RAN node.
  • a UE-3 can be paged with a different RRC message as compared to a UE-1 or UE-2.
  • These two RAN paging messages e.g., the RRC paging message and RRC light paging message
  • the different RAN paging messages can include different paging UE IDs.
  • the different RAN paging messages can utilize a same P-RNTI or a new/different RNTI.
  • the MME can provide the UE NAS ID to the RAN node storing the UE RAN context over S 1 signaling between the MME and the RAN node.
  • the UE RAN context and/or an S l-U bearer termination point can be transferred from one RAN node (e.g., eNodeB) to another RAN node when the UE is connected or suspended.
  • the UE paging parameters, such as the DRX parameters and the UE paging ID can also be transferred to the new network node at that time.
  • paging that is initiated by the RAN node can be referred to as suspend-mode paging (localized paging) or RAN-originated paging, which can be differentiated from NAS-based paging that originates from the MME (core network).
  • the RAN-originated paging message can encompass only an agreed UE paging ID, such as the Suspend UE ID, whereas in legacy LTE systems, a paging message can include multiple paging records each with a UE ID (e.g., S-TMSI or IMSI) and a circuit switched (CS) or packet switched (PS) domain indicator.
  • UE ID e.g., S-TMSI or IMSI
  • CS circuit switched
  • PS packet switched
  • the UE paging ID can include a network code field, e.g., referring to a cell that allocated the UE paging ID, and a UE specific field that refers to a specific UE within that cell.
  • the network code field can be unique over a large area and perhaps even the whole network.
  • the UE specific portion can refer to a time when the UE paging ID was allocated and/or the UE specific portion can refer to a time since a RAN node/cell that allocated the UE paging ID was restarted.
  • a paging occasion at which the UE checks a physical downlink control channel (PDCCH) for the P-RNTI can be calculated using a timer based on a configured DRX cycle length value.
  • the timer can be from a system frame number (SFN) corresponding to a point in time at which the UE started a suspended mode, and the SFN can be used as a clock reference.
  • the paging occasion at which the UE checks the PDCCH for the P-RNTI can be calculated using legacy calculations as a baseline, as per 3GPP LTE Release 13 36.304 idle mode procedures which allow for further randomness if desired.
  • the paging occasion at which the UE checks the PDCCH for the P- RNTI can be calculated using an absolute time reference based on a coordinated universal time (UTC) in a system information block 16 (SIB 16), and the absolute time reference can be utilized when a paging window is defined.
  • UTC coordinated universal time
  • SIB 16 system information block 16
  • a new P-RNTI specific to this novel RAN-based paging mechanism can be defined with a new value.
  • the RAN-originated paging message can be transferred using a legacy logical channel, such as a paging control channel (PCCH), and a transport channel, such as a paging channel (PCH), or corresponding new channels can be defined.
  • PCCH paging control channel
  • PCH paging channel
  • the RAN-based paging DRX range can be the same as a legacy LTE 2.56sec.
  • the RAN-based paging DRX range can be increased, e.g., up to 5.12 or 10.24 sec, but a similar paging DRX operation can be utilized, e.g., a paging frame (PF) can be found with one or multiple paging occasions (PO) every certain time (TRAN-basedDRx).
  • PF paging frame
  • PO paging occasions
  • this functionality can be allowed, negotiated/configured and controlled by different nodes.
  • a CN node e.g., MME
  • the RAN node can determine when the UE is reachable during the active periods (PF/PO) of the RAN-based DRX cycle.
  • PF/PO active periods
  • a paging window time PW
  • the CN node e.g., MME
  • the CN node can control a portion of the I-eDRX operation (e.g., allow and negotiate/configure its usage) and a remaining portion can be handled by the RAN node (e.g., an actual control of I-eDRX operations can be handled by the RAN node).
  • the CN node can negotiate the usage/parameters for the I- eDRX cycle and PTW, but the RAN node can later control when the UE becomes reachable with the RAN-based DRX cycle and a period of time (e.g., a PTW time) before the UE enters again in an extended inactive period configured by the I-eDRX cycle.
  • the RAN node e.g., eNodeB
  • the extended DRX operation can be changed for a UE-3 in order to simplify operation considering that the paging is RAN-based. Therefore, a UE within an I-eDRX cycle may not be reached for multiple DRX cycles (which are currently defined as short based on DRX cycles). Instead, a length of the RAN based DRX cycle can be extended as the UE only wakes up for one PF.
  • multiple RAN DRX parameters can be utilized per UE.
  • a UE can have associated different DRX cycle parameters per bearer or application.
  • the UE can be configured to use a minimum DRX cycle parameter 'x', and each bearer or category of applications or category of pagings can have associated different paging DRX cycle parameters, e.g., "x", "n*x” or "m*x", where n,m are integers and "x" is the minimum value of the DRX cycle parameter.
  • the ability to have different DRX cycle parameters per bearer of application or application category can reduce a number of times in which the UE wakes up for mobile terminated (MT) traffic, while guaranteeing different MT reachability delays.
  • MT mobile terminated
  • the UE can check a paging frame (PF) and/or paging occasion (PO) every 'x' seconds, and the network (e.g., RAN or CN node) can send the paging message to the UE in a reduced amount of time (every 'x' sec) or in an increased amount of time (every "n*x") depending on whether the paging message was received on bearer 1 or 2.
  • PF paging frame
  • PO paging occasion
  • This approach can be useful for UEs that take an increased amount of time when transitioning into RRC connected mode or UEs that consume an increased amount of power (e.g., due to poor location) when transitioning into RRC connected mode.
  • FIG. 3 is an exemplary flowchart illustrating operations for performing paging between an eNodeB and a user equipment (UE).
  • the eNodeB can determine radio access network (RAN)-based paging parameters for the UE, as in block 302.
  • the eNodeB can determine the RAN-based paging parameters for the UE based on quality of service (QoS) constraints of data radio bearers (DRBs) of the UE, a UE power saving preference, etc.
  • the RAN-based paging parameters can include a C-RNTI, a S-TMSI, a Suspend UE ID or a new specific UE IE.
  • the signaling of the RAN-based paging parameters and the RAN originated paging message can be performed in 3GPP LTE systems that utilize suspend/resume mechanisms.
  • the signaling of the RAN-based paging parameters and the RAN originated paging message can be performed in other RANs that support a power efficient state, such as a 5G New Radio (NR) system.
  • NR 5G New Radio
  • a user equipment can use radio access network (RAN)- assigned paging parameters in order to receive paging messages from a RAN (e.g., eNodeB).
  • the RAN-assigned paging parameters can include a paging discontinuous reception (DRX) parameter and/or a paging UE identifier (ID).
  • the paging UE ID can be a C-RNTI, a S-TMSI, a Suspend UE ID or a new specific UE ID.
  • the RAN-assigned paging parameters can be a combination of RAN-assigned parameters and CN-assigned parameters.
  • the UE can provide a power saving preference to the RAN (e.g., eNodeB), and the power saving preference can assist in determining a RAN DRX setting for the UE.
  • the RAN e.g., eNodeB
  • a network node e.g., a RAN node or CN node
  • the paging parameters can include a paging DRX parameter and/or a paging UE ID.
  • the network node can utilize quality of service (QoS) constraints of bearers and/or power saving constraints from the UE when determining the paging parameters, such as the paging DRX parameter.
  • QoS quality of service
  • a RAN node e.g., eNodeB
  • a RAN node can receive a UE NAS ID and/or a NAS DRX from a CN node for storage with a UE RAN context, and the RAN node can use the UE NAS ID and/or NAS DRX for subsequent paging messages.
  • the RAN node can originate a paging message and send the paging message using a combination of RAN-based parameters and CN-based parameters.
  • the RAN node can use NAS paging parameters for RAN-originated paging to handle UEs that may have been in an RRC idle state when the RAN node believes the UEs were in a suspended state.
  • the RAN node can allocate a unique UE ID that includes a part field referring to a time the unique UE ID was allocated or when a network node was restarted.
  • a CN node e.g., MME
  • MME Mobility Management Entity
  • the CN node can store the paging parameters and utilize the paging parameters for subsequent paging messages that originate at the CN node.
  • the base station can comprise memory and one or more processors.
  • the one or more processors can be configured to determine, at the base station, radio access network (RAN)-based UE paging parameters for configuration of a UE when the UE is in a suspended state, wherein UE context information for the UE is stored in the memory of the base station when the UE is in the suspended state, as in block 410.
  • the one or more processors can be configured to encode, at the base station, the RAN-based UE paging parameters for transmission to the UE, as in block 420.
  • FIG. 5 Another example provides functionality 500 of a user equipment (UE) operable to decode paging messages received from a base station, as shown in FIG. 5.
  • the UE can comprise one or more processors.
  • the one or more processors can be configured to decode, at the UE, radio access network (RAN)-based UE paging parameters received from the base station, wherein the RAN-based UE paging parameters include a RAN discontinuous reception (DRX) cycle length paging parameter of the base station and a UE paging identifier (ID), as in block 510.
  • RAN radio access network
  • DRX RAN discontinuous reception
  • ID UE paging identifier
  • the one or more processors can be configured to decode, at the UE, a RAN-originated paging message received from the base station when the UE is in a suspended state, wherein the RAN-originated paging message is received at the UE when downlink data for the UE is stored at the base station and in accordance with the RAN-based UE paging parameters, as in block 520.
  • the one or more processors can be configured to initiate, at the UE, a radio resource control (RRC) connected state to retrieve the downlink data from the base station after receiving the RAN-originated paging message, as in block 530.
  • the UE can comprise memory interfaced with the one or more processors, and the memory can be configured to store the RAN-based UE paging parameters received from the base station.
  • Another example provides at least one machine readable storage medium having instructions 600 embodied thereon for providing paging messages from a node to a user equipment (UE), as shown in FIG. 6.
  • the instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or at least one non-transitory machine readable storage medium.
  • the instructions when executed by one or more processors perform: determining, at the node, radio access network (RAN)- based UE paging parameters for configuration of a UE, as in block 610.
  • the instructions when executed by one or more processors perform: encoding, at the node, the RAN-based UE paging parameters for transmission to the UE, as in block 620.
  • RAN radio access network
  • the instructions when executed by one or more processors perform: generating, at the node, a RAN-originated paging message for the UE when downlink data is received for the UE, as in block 630.
  • the instructions when executed by one or more processors perform: encoding, at the node, the RAN-originated paging message for transmission to the UE, wherein the RAN- originated paging message is transmitted from the node and received at the UE in accordance with the RAN-based UE paging parameters, as in block 640.
  • any of the UEs 701 and 702 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for (machine initiated) exchanging data with an MTC server and/or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • M2M machine-to-machine
  • MTC machine-type communications
  • PLMN public land mobile network
  • D2D device-to-device
  • An IoT network describes interconnecting uniquely identifiable embedded computing devices (within the internet infrastructure) having short-lived connections, in addition to background applications (e.g., keep-alive messages, status updates, etc.) executed by the I
  • the UEs 701 and 702 are configured to access a radio access network (RAN)— in this embodiment, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) 710.
  • RAN radio access network
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • the UEs 701 and 702 utilize connections 703 and 704, respectively, each of which comprises a physical
  • connections 703 and 704 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE 3GPP Long Term Evolution
  • the UEs 701 and 702 may further directly exchange communication data via a ProSe interface 705.
  • the ProSe interface 705 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 702 is shown to be configured to access an access point (AP) 706 via connection 707.
  • the connection 707 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 706 would comprise a wireless fidelity (WiFi) router.
  • WiFi wireless fidelity
  • the AP 706 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • any of the RAN nodes 711 and 712 can terminate the air interface protocol and can be the first point of contact for the UEs 701 and 702.
  • any of the RAN nodes 711 and 712 can fulfill various logical functions for the E-UTRAN 710 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs 701 and 702 can be configured to communicate using Orthogonal Frequency -Division Multiplexing (OFDM)
  • OFDM Orthogonal Frequency -Division Multiplexing
  • OFDMMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 711 and 712 to the UEs 701 and 702, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this represents the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel (PDSCH) carries user data and higher-layer signaling to the UEs 701 and 702.
  • the physical downlink control channel (PDCCH) carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It also informs the UEs 701 and 702 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • H-ARQ Hybrid Automatic Repeat Request
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) is performed at any of the RAN nodes 711 and 712 based on channel quality information fed back from any of the UEs 701 and 702, and then the downlink resource assignment information is sent on the PDCCH used for (i.e., assigned to) each of the UEs 701 and 702.
  • the E-UTRAN 710 is shown to be communicatively coupled to a core network— in this embodiment, an Evolved Packet Core (EPC) network 720 via an SI interface 713.
  • EPC Evolved Packet Core
  • the SI interface 713 is split into two parts: the S I -U interface 714, which carries traffic data between the RAN nodes 711 and 712 and the serving gateway (S-GW) 722, and the Sl-MME interface 715, which is a signaling interface between the RAN nodes 711 and 712 and the mobility management entities (MMEs) 721.
  • S-GW serving gateway
  • MMEs mobility management entities
  • the EPC network 720 comprises the MMEs 721, the S-GW 722, the Packet Data Network (PDN) Gateway (P-GW) 723, and a home subscriber server (HSS) 724.
  • the MMEs 721 are similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 721 manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 724 comprises a database for network users, including subscription-related information to support the network entities' handling of
  • the EPC network 720 may comprise one or several HSSs 724, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 724 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 722 terminates the SI interface 713 towards the E-UTRAN 710, and routes data packets between the E-UTRAN 710 and the EPC network 720.
  • the S-GW 722 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 723 terminates an SGi interface toward a PDN.
  • the P-GW 723 routes data packets between the EPC network 723 and external networks such as a network including the application server 730 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 725.
  • the application server 730 is an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 723 is shown to be communicatively coupled to an application server 730 via an IP communications interface 725.
  • the application server 730 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 701 and 702 via the EPC network 720.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 723 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 726 is the policy and charging control element of the EPC network 720.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • UE User Equipment's
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 726 may be communicatively coupled to the application server 730 via the P-GW 723.
  • the application server 730 may signal the PCRF 726 to indicate a new service flow and selecting the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 726 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server.
  • PCEF Policy and Charging Enforcement Function
  • FIG. 8 illustrates example components of a device in accordance with some embodiments.
  • the device 1500 may include application circuitry 802, baseband circuitry 804, Radio Frequency (RF) circuitry 806, front-end module (FEM) circuitry 808, and one or more antennas 810, coupled together at least as shown.
  • the components of the illustrated device 1500 may be included a UE or a RAN node.
  • the device 1500 may include less elements (e.g., a RAN node may not utilize application circuitry 802, and instead include a processor/controller to process IP data received from an EPC).
  • the device 1500 may include additional elements such as, for example, memory /storage, display, camera, sensor, and/or input/output (I/O) interface.
  • additional elements such as, for example, memory /storage, display, camera, sensor, and/or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • C-RAN Cloud-RAN
  • the application circuitry 802 may include one or more application processors.
  • the application circuitry 802 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with and/or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications and/or operating systems to run on the system.
  • processors of application circuitry 802 may process IP data packets received from an EPC.
  • the baseband circuitry 804 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 804 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806.
  • Baseband processing circuity 804 may interface with the application circuitry 802 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806.
  • the baseband circuitry 804 may include a second generation (2G) baseband processor 804a, third generation (3G) baseband processor 804b, fourth generation (4G) baseband processor 804c, and/or other baseband processor(s) 804d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 804 e.g., one or more of baseband processors 804a-d
  • encoding/decoding circuitry of the baseband circuitry 804 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 804f.
  • the audio DSP(s) 804f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 804 and the application circuitry 802 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 804 may provide for
  • the baseband circuitry 804 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 806 may enable communication with wireless networks
  • the RF circuitry 806 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 806 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 804.
  • RF circuitry 806 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 804 and provide RF output signals to the FEM circuitry 808 for transmission.
  • the RF circuitry 806 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 806 may include mixer circuitry 806a, amplifier circuitry 806b and filter circuitry 806c.
  • the transmit signal path of the RF circuitry 806 may include filter circuitry 806c and mixer circuitry 806a.
  • RF circuitry 806 may also include synthesizer circuitry 806d for synthesizing a frequency for use by the mixer circuitry 806a of the receive signal path and the transmit signal path.
  • the mixer circuitry 806a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806d.
  • the amplifier circuitry 806b may be configured to amplify the down-converted signals and the filter circuitry 806c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 804 for further processing.
  • the output baseband signals may be zero-frequency baseband signals.
  • mixer circuitry 806a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 806a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 806d to generate RF output signals for the FEM circuitry 808.
  • the baseband signals may be provided by the baseband circuitry 804 and may be filtered by filter circuitry 806c.
  • the filter circuitry 806c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • LPF low-pass filter
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 804 may include a digital baseband interface to communicate with the RF circuitry 806.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • the synthesizer circuitry 806d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 806d may be configured to synthesize an output frequency for use by the mixer circuitry 806a of the RF circuitry 806 based on a frequency input and a divider control input.
  • the synthesizer circuitry 806d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO).
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 804 or the applications processor 802 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 802.
  • Synthesizer circuitry 806d of the RF circuitry 806 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 806d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 806 may include an IQ/polar converter.
  • FEM circuitry 808 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 806 for further processing.
  • FEM circuitry 808 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 806 for transmission by one or more of the one or more antennas 810.
  • the FEM circuitry 808 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806).
  • LNA low-noise amplifier
  • the transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 810.
  • PA power amplifier
  • the device 1500 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 1500 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device cannot receive data in this state, in order to receive data, it must transition back to RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 802 and processors of the baseband circuitry 804 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 804 alone or in combination, may be used execute Layer 3, Layer 2, and/or Layer 1 functionality, while processors of the application circuitry 804 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • FIG. 9 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 804 of FIG. 8 may comprise processors 804a-804e and a memory 804g utilized by said processors.
  • Each of the processors 804a-804e may include a memory interface, 904a-904e, respectively, to send/receive data to/from the memory 804g.
  • the baseband circuitry 804 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 912 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 804), an application circuitry interface 914 (e.g., an interface to send/receive data to/from the application circuitry 802 of FIG. 8), an RF circuitry interface 916 (e.g., an interface to send/receive data to/from RF circuitry 806 of FIG. 8), and a wireless hardware connectivity interface 918 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components).
  • NFC Near Field Communication
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components Wi-Fi® components
  • FIG. 10 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile
  • Example 2 includes the apparatus of Example 1, further comprising a transceiver configured to: transmit the RAN-based UE paging parameters to the UE; and transmit the RAN-originated paging message to the UE.
  • Example 4 includes the apparatus of any of Examples 1 to 3, wherein the UE paging ID is a RAN-based UE ID or a CN-based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C-RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).
  • C-RNTI cell radio network temporary identifier
  • NAS non-access stratum
  • SAE System Architecture Evolution
  • Example 6 includes the apparatus of any of Examples 1 to 5, wherein the one or more processors are further configured to: decode a message received from the UE or the CN node that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE; and determine the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE.
  • QoS quality of service
  • DRBs data radio bearers
  • Example 7 includes the apparatus of any of Examples 1 to 6, wherein the one or more processors are further configured to: decode a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE; and select different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.
  • QoS quality of service
  • DRBs data radio bearers
  • Example 8 includes the apparatus of any of Examples 1 to 7, wherein the one or more processors are further configured to: decode a non-access stratum (NAS) UE ID received from the CN node; and decode NAS discontinuous reception (DRX) paging parameters received from the CN node, wherein the NAS UE ID and the NAS DRX paging parameters received from the CN node are included in the RAN-based UE paging parameters.
  • NAS non-access stratum
  • DRX NAS discontinuous reception
  • Example 10 includes the apparatus of Example 9, further comprising a transceiver configured to: receive the RAN-based UE paging parameters from the base station;
  • Example 12 includes the apparatus of any of Examples 9 to 11, wherein the UE paging ID is a RAN-based UE ID or a core network (CN) based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C-RNTI), and the CN -based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).
  • C-RNTI cell radio network temporary identifier
  • NAS non-access stratum
  • SAE System Architecture Evolution
  • Example 15 includes the apparatus of any of Examples 9 to 14, wherein the one or more processors are further configured to encode a message for transmission to the base station that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE, wherein the message enables the base station to configure different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints
  • Example 16 includes at least one machine readable storage medium having instructions embodied thereon for providing paging messages from a node to a user equipment (UE), the instructions when executed by one or more processors perform the following: determining, at the node, radio access network (RAN)-based UE paging parameters for configuration of a UE; encoding, at the node, the RAN-based UE paging parameters for transmission to the UE; generating, at the node, a RAN-originated paging message for the UE when downlink data is received
  • RAN radio
  • Example 17 includes the at least one machine readable storage medium of Example 16, further comprising instructions when executed perform the following:
  • Example 18 includes the at least one machine readable storage medium of any of Examples 16 to 17, wherein the UE paging ID is a RAN-based UE ID or a CN-based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C- RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).
  • C- RNTI cell radio network temporary identifier
  • CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).
  • SAE System Architecture Evolution
  • Example 19 includes the at least one machine readable storage medium of any of Examples 16 to 18, wherein the RAN-based UE paging parameters includes one or more of: a RAN discontinuous reception (DRX) cycle length paging parameter or a UE paging identifier (ID).
  • DRX RAN discontinuous reception
  • ID UE paging identifier
  • Example 20 includes the at least one machine readable storage medium of any of Examples 16 to 19, further comprising instructions when executed perform the following: decoding a power saving preference message received from the UE; and determining the RAN DRX cycle length paging parameter based on the power saving preference message.
  • Example 21 includes the at least one machine readable storage medium of any of Examples 16 to 20, further comprising instructions when executed perform the following: decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE; and determining the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE.
  • QoS quality of service
  • DRBs data radio bearers
  • Example 22 includes the at least one machine readable storage medium of any of Examples 16 to 21, further comprising instructions when executed perform the following: decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE; and selecting different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.
  • QoS quality of service
  • DRBs data radio bearers
  • Example 23 includes the at least one machine readable storage medium of any of Examples 16 to 22, further comprising instructions when executed perform the following: decoding a non-access stratum (NAS) UE ID received from the CN node; and decoding NAS discontinuous reception (DRX) paging parameters received from the CN node, wherein the NAS UE ID and the NAS DRX paging parameters received from the CN node are included in the RAN-based UE paging parameters.
  • NAS non-access stratum
  • DRX NAS discontinuous reception
  • Example 24 includes a node operable to provide paging messages to a user equipment (UE), the node comprising: means for determining, at the node, radio access network (RAN)-based UE paging parameters for configuration of a UE; means for encoding, at the node, the RAN-based UE paging parameters for transmission to the UE; means for generating, at the node, a RAN-originated paging message for the UE when downlink data is received for the UE; and means for encoding, at the node, the RAN- originated paging message for transmission to the UE directly or via a core network (CN) node, wherein the RAN-originated paging message is transmitted from the node and received at the UE in accordance with the RAN-based UE paging parameters.
  • RAN radio access network
  • Example 25 includes the node of Example 24, further comprising: means for storing UE context information in memory of the node when the UE is in a suspended state.
  • Example 26 includes the node of any of Examples 24 to 25, wherein the UE paging ID is a RAN-based UE ID or a CN-based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C-RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).
  • C-RNTI cell radio network temporary identifier
  • NAS non-access stratum
  • SAE System Architecture Evolution
  • Example 27 includes the node of any of Examples 24 to 26, wherein the RAN- based UE paging parameters include a RAN discontinuous reception (DRX) cycle length paging parameter and a UE paging identifier (ID).
  • DRX RAN discontinuous reception
  • ID UE paging identifier
  • Example 28 includes the node of any of Examples 24 to 27, further comprising: means for decoding a power saving preference message received from the UE; and determining the RAN DRX cycle length paging parameter based on the power saving preference message.
  • Example 29 includes the node of any of Examples 24 to 28, further comprising: means for decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE; and determining the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE.
  • QoS quality of service
  • DRBs data radio bearers
  • Example 30 includes the node of any of Examples 24 to 29, further comprising: means for decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE; and selecting different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.
  • QoS quality of service
  • DRBs data radio bearers
  • Example 31 includes the node of any of Examples 24 to 30, further comprising: means for decoding a non-access stratum (NAS) UE ID received from the CN node; and decoding NAS discontinuous reception (DRX) paging parameters received from the CN node, wherein the NAS UE ID and the NAS DRX paging parameters received from the CN node are included in the RAN-based UE paging parameters.
  • NAS non-access stratum
  • DRX NAS discontinuous reception
  • Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
  • the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device.
  • the volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data.
  • the node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer).
  • transceiver module i.e., transceiver
  • a counter module i.e., counter
  • a processing module i.e., processor
  • a clock module i.e., clock
  • timer module i.e., timer
  • selected components of the transceiver module can be located in a cloud radio access network (C-RAN).
  • C-RAN cloud radio access network
  • One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like.
  • API application programming interface
  • Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system.
  • the program(s) may be implemented in assembly or machine language, if desired.
  • the language may be a compiled or interpreted language, and combined with hardware implementations.
  • circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • modules may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules may also be implemented in software for execution by various types of processors.
  • An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
  • a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • the modules may be passive or active, including agents operable to perform desired functions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne une technologie pour une station de base. La station de base peut déterminer des paramètres de radiorecherche d'UE basée sur un réseau d'accès radio (RAN), pour la configuration d'un UE lorsque l'UE est dans un état suspendu. Des informations de contexte d'UE de l'UE peuvent être stockées dans une mémoire de la station de base lorsque l'UE est dans l'état suspendu. La station de base peut encoder les paramètres de radiorecherche d'UE basée sur un RAN, pour une transmission à l'UE directement ou via un nœud de réseau central (CN). La station de base peut générer un message de radiorecherche provenant d'un RAN pour l'UE lorsque des données de liaison descendante sont reçues à la station de base pour l'UE. La station de base peut encoder le message de radiorecherche provenant d'un RAN, pour une transmission à l'UE. Le message de radiorecherche provenant d'un RAN peut être transmis à partir de la station de base et être reçu à l'UE d'après les paramètres de radiorecherche d'UE basée sur un RAN.
PCT/US2017/025164 2016-04-01 2017-03-30 Messagerie de radiorecherche provenant d'un réseau d'accès radio (ran) Ceased WO2017173158A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201780014275.2A CN108702732B (zh) 2016-04-01 2017-03-30 无线电接入网络(ran)始发的寻呼消息传送方法和装置
HK19100740.2A HK1258369B (en) 2016-04-01 2017-03-30 Method and apparatus for radio access network (ran)-originated paging messaging

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662317213P 2016-04-01 2016-04-01
US62/317,213 2016-04-01

Publications (1)

Publication Number Publication Date
WO2017173158A1 true WO2017173158A1 (fr) 2017-10-05

Family

ID=58549223

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/025164 Ceased WO2017173158A1 (fr) 2016-04-01 2017-03-30 Messagerie de radiorecherche provenant d'un réseau d'accès radio (ran)

Country Status (2)

Country Link
CN (1) CN108702732B (fr)
WO (1) WO2017173158A1 (fr)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019219753A1 (fr) * 2018-05-18 2019-11-21 Telefonaktiebolaget Lm Ericsson (Publ) Appareils et procédés de transition d'ue programmée en réseau vers un mode connecté cm/rrc en 5gs
CN110913505A (zh) * 2018-09-14 2020-03-24 电信科学技术研究院有限公司 一种下行数据缓存方法、网络设备及upf实体
KR20200120946A (ko) * 2018-02-13 2020-10-22 지티이 코포레이션 셀 처리 방법, 장치 및 시스템
CN112262600A (zh) * 2020-08-20 2021-01-22 北京小米移动软件有限公司 扩展非连续接收参数确定方法、通信设备和存储介质
US20210058893A1 (en) * 2018-04-04 2021-02-25 Zte Corporation Paging method, base station, and user equipment
CN112543442A (zh) * 2019-09-20 2021-03-23 维沃移动通信有限公司 非连续接收参数配置方法及设备
CN112752341A (zh) * 2019-10-29 2021-05-04 中国移动通信有限公司研究院 一种寻呼检测及指示方法、设备、介质
CN112788618A (zh) * 2019-11-06 2021-05-11 大唐移动通信设备有限公司 非连续接收参数的配置、监听寻呼的方法、设备及终端
WO2021114054A1 (fr) * 2019-12-09 2021-06-17 华为技术有限公司 Procédé et appareil de radiomessagerie
KR20220027988A (ko) * 2019-07-04 2022-03-08 엘지전자 주식회사 무선통신시스템에서 사이드링크 drx에 관련된 ue의 동작 방법
CN114270889A (zh) * 2019-08-12 2022-04-01 Lg电子株式会社 用于在无线通信系统中操作与副链路drx关联的ue的方法和设备
CN116210282A (zh) * 2020-07-21 2023-06-02 苹果公司 基于网络的寻呼错误警报减轻
CN116250362A (zh) * 2020-08-06 2023-06-09 苹果公司 用于非活动直接传输的用户装备的访问控制
US12219582B2 (en) 2021-12-17 2025-02-04 T-Mobile Usa, Inc. Network-based cell assignment for carrier aggregation systems and methods
US12389370B2 (en) 2021-04-02 2025-08-12 Zte Corporation Channel transmission method, channel receiving method, communication node, and storage medium
CN121442458A (zh) * 2025-12-29 2026-01-30 荣耀终端股份有限公司 通信方法、装置及存储介质
US12621901B2 (en) 2020-08-20 2026-05-05 Beijing Xiaomi Mobile Software Co., Ltd. Method for determining extended discontinuous reception parameter, communication device, and storage medium

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020086804A1 (fr) * 2018-10-25 2020-04-30 Intel Corporation Perte d'un message 4 (msg4) de transmission de données précoce (edt) dans un plan utilisateur
CN111148128A (zh) * 2018-11-02 2020-05-12 夏普株式会社 由用户设备执行的方法以及用户设备
CN112970301B (zh) * 2018-11-08 2023-11-10 上海诺基亚贝尔股份有限公司 针对寻呼消息中的下行链路早期数据传输的确认
CN119997265A (zh) * 2019-02-14 2025-05-13 谷歌有限责任公司 恢复通信网络中的无线电连接的装置和方法
CN113661771B (zh) * 2019-04-11 2024-06-25 索尼集团公司 多用户标识无线通信设备的寻呼的通信间隙
CN111867018B (zh) * 2019-04-30 2022-09-23 华为技术有限公司 通信方法、装置及系统
CN114631397A (zh) * 2019-10-18 2022-06-14 欧芬诺有限责任公司 无线网络中的信令传送
CN119815535A (zh) * 2019-11-07 2025-04-11 中兴通讯股份有限公司 无线通信方法、装置、计算机程序产品
US20230254769A1 (en) * 2020-07-10 2023-08-10 Lenovo (Beijing) Ltd. Method and apparatus for additional reference signal monitoring
KR20230048249A (ko) * 2020-08-07 2023-04-11 지티이 코포레이션 무선 네트워크에서의 페이징 및 ue id 송신을 위한 방법, 디바이스, 및 시스템
WO2023010343A1 (fr) * 2021-08-04 2023-02-09 Lenovo (Beijing) Limited Procédés et appareils pour mécanisme de réception discontinue améliorée
CN118435199A (zh) * 2021-12-24 2024-08-02 华为技术有限公司 用于实现自动迁移学习的系统和方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080232310A1 (en) * 2007-03-19 2008-09-25 Shugong Xu Flexible user equipment-specified discontinuous reception
US20100240420A1 (en) * 2009-03-17 2010-09-23 Qualcomm Incorporated Methods and apparatus for changing paging parameters in a communication system
WO2014013057A1 (fr) * 2012-07-19 2014-01-23 Nec Europe Ltd. Procédé et système pour exécuter des configurations de porteuse dans un réseau d'accès 3ggp
US20150173121A1 (en) * 2012-08-02 2015-06-18 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for reducing signaling in a core network

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101568113B (zh) * 2008-04-21 2010-12-08 大唐移动通信设备有限公司 一种实现承载状态同步的方法、装置和系统
CN101635664B (zh) * 2008-07-21 2011-11-30 中兴通讯股份有限公司 一种空闲状态协议模块状态迁移的方法及终端
CN101730205A (zh) * 2008-10-31 2010-06-09 大唐移动通信设备有限公司 更新ue寻呼drx周期的方法、系统及装置
CN102281502B (zh) * 2010-06-11 2016-07-06 中兴通讯股份有限公司 Mtc分组终端寻呼drx周期参数获取方法及装置
US8588120B2 (en) * 2010-09-16 2013-11-19 Qualcomm Incorporated Power conservation in wireless client terminals using proxy device
US9049746B2 (en) * 2011-11-08 2015-06-02 Blackberry Limited Management of multi-mode wireless devices
CN103179644B (zh) * 2011-12-21 2016-03-30 华为技术有限公司 一种读取系统消息的方法、设备
US9295095B2 (en) * 2012-03-27 2016-03-22 Blackberry Limited UE preference indicator for suspension
CN103338500A (zh) * 2012-12-24 2013-10-02 上海华为技术有限公司 一种数据传输方法、装置、系统及网络侧设备和终端设备
CN105103634B (zh) * 2013-03-29 2019-03-22 英特尔Ip公司 无线通信网络中的扩展型呼叫非连续接收(drx)周期
CN104509179B (zh) * 2013-06-27 2018-06-19 华为技术有限公司 数据接收方法、发送方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080232310A1 (en) * 2007-03-19 2008-09-25 Shugong Xu Flexible user equipment-specified discontinuous reception
US20100240420A1 (en) * 2009-03-17 2010-09-23 Qualcomm Incorporated Methods and apparatus for changing paging parameters in a communication system
WO2014013057A1 (fr) * 2012-07-19 2014-01-23 Nec Europe Ltd. Procédé et système pour exécuter des configurations de porteuse dans un réseau d'accès 3ggp
US20150173121A1 (en) * 2012-08-02 2015-06-18 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for reducing signaling in a core network

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114423054A (zh) * 2018-02-13 2022-04-29 中兴通讯股份有限公司 一种小区处理方法、装置和系统
US12513662B2 (en) 2018-02-13 2025-12-30 Zte Cell processing method, device, and system
KR20200120946A (ko) * 2018-02-13 2020-10-22 지티이 코포레이션 셀 처리 방법, 장치 및 시스템
KR102862756B1 (ko) 2018-02-13 2025-09-19 지티이 코포레이션 셀 처리 방법, 장치 및 시스템
JP7565975B2 (ja) 2018-02-13 2024-10-11 中興通訊股▲ふん▼有限公司 セル処理方法、装置及びシステム
US12063622B2 (en) 2018-02-13 2024-08-13 Zte Corporation Cell processing method, device, and system
JP2022122944A (ja) * 2018-02-13 2022-08-23 中興通訊股▲ふん▼有限公司 セル処理方法、装置及びシステム
US20210058893A1 (en) * 2018-04-04 2021-02-25 Zte Corporation Paging method, base station, and user equipment
US11864155B2 (en) * 2018-04-04 2024-01-02 Zte Corporation Paging method, base station, and user equipment
US11533708B2 (en) 2018-05-18 2022-12-20 Telefonaktiebolaget Lm Ericsson (Publ) Apparatuses and methods for network scheduled UE transition to CM-connected/RRC connected mode in 5GS
WO2019219753A1 (fr) * 2018-05-18 2019-11-21 Telefonaktiebolaget Lm Ericsson (Publ) Appareils et procédés de transition d'ue programmée en réseau vers un mode connecté cm/rrc en 5gs
CN112369113B (zh) * 2018-05-18 2024-07-09 瑞典爱立信有限公司 用于在5gs中的网络调度的到cm-connected/rrc连接模式的ue转变的装置和方法
CN112369113A (zh) * 2018-05-18 2021-02-12 瑞典爱立信有限公司 用于在5gs中的网络调度的到cm-connected/rrc连接模式的ue转变的装置和方法
CN110913505A (zh) * 2018-09-14 2020-03-24 电信科学技术研究院有限公司 一种下行数据缓存方法、网络设备及upf实体
EP3996426A4 (fr) * 2019-07-04 2023-08-02 LG Electronics Inc. Procédé de fonctionnement d'équipement d'utilisateur relatif à une drx de liaison latérale dans un système de communication sans fil
US12150201B2 (en) 2019-07-04 2024-11-19 Lg Electronics Inc. UE operation method related to sidelink DRX in wireless communication system
KR102874285B1 (ko) * 2019-07-04 2025-10-22 엘지전자 주식회사 무선통신시스템에서 사이드링크 drx에 관련된 ue의 동작 방법
KR20220027988A (ko) * 2019-07-04 2022-03-08 엘지전자 주식회사 무선통신시스템에서 사이드링크 drx에 관련된 ue의 동작 방법
CN114270889A (zh) * 2019-08-12 2022-04-01 Lg电子株式会社 用于在无线通信系统中操作与副链路drx关联的ue的方法和设备
CN112543442B (zh) * 2019-09-20 2022-08-19 维沃移动通信有限公司 非连续接收参数配置方法及设备
CN112543442A (zh) * 2019-09-20 2021-03-23 维沃移动通信有限公司 非连续接收参数配置方法及设备
WO2021082892A1 (fr) * 2019-10-29 2021-05-06 中国移动通信有限公司研究院 Procédé de détection et d'indication de radiomessagerie, dispositif et support
CN112752341A (zh) * 2019-10-29 2021-05-04 中国移动通信有限公司研究院 一种寻呼检测及指示方法、设备、介质
CN112788618A (zh) * 2019-11-06 2021-05-11 大唐移动通信设备有限公司 非连续接收参数的配置、监听寻呼的方法、设备及终端
WO2021114054A1 (fr) * 2019-12-09 2021-06-17 华为技术有限公司 Procédé et appareil de radiomessagerie
CN116210282A (zh) * 2020-07-21 2023-06-02 苹果公司 基于网络的寻呼错误警报减轻
CN116250362A (zh) * 2020-08-06 2023-06-09 苹果公司 用于非活动直接传输的用户装备的访问控制
CN112262600B (zh) * 2020-08-20 2024-01-30 北京小米移动软件有限公司 扩展非连续接收参数确定方法、通信设备和存储介质
CN112262600A (zh) * 2020-08-20 2021-01-22 北京小米移动软件有限公司 扩展非连续接收参数确定方法、通信设备和存储介质
EP4203573A4 (fr) * 2020-08-20 2023-10-25 Beijing Xiaomi Mobile Software Co., Ltd. Procédé permettant de déterminer un paramètre de réception discontinue étendue, dispositif de communication et support de stockage
US12621901B2 (en) 2020-08-20 2026-05-05 Beijing Xiaomi Mobile Software Co., Ltd. Method for determining extended discontinuous reception parameter, communication device, and storage medium
US12389370B2 (en) 2021-04-02 2025-08-12 Zte Corporation Channel transmission method, channel receiving method, communication node, and storage medium
US12219582B2 (en) 2021-12-17 2025-02-04 T-Mobile Usa, Inc. Network-based cell assignment for carrier aggregation systems and methods
CN121442458A (zh) * 2025-12-29 2026-01-30 荣耀终端股份有限公司 通信方法、装置及存储介质

Also Published As

Publication number Publication date
CN108702732A (zh) 2018-10-23
HK1258369A1 (zh) 2019-11-08
CN108702732B (zh) 2021-11-19

Similar Documents

Publication Publication Date Title
US12143846B2 (en) Support of flexible PDCCH monitoring in new radio (NR)
US11102661B2 (en) Beam indication information transmission
CN108702732B (zh) 无线电接入网络(ran)始发的寻呼消息传送方法和装置
US11310861B2 (en) Bandwidth part configuration and operation for new radio (NR) wideband user equipment (UE)
US10834717B2 (en) Interrupted transmission indication for new radio (NR)
WO2020033895A1 (fr) Transmissions de liaison montante dans des ressources pré-configurées pour communication de type machine améliorée (emtc) et internet des objets à bande étroite (ido-be)
WO2020051152A1 (fr) Multiplexage d'informations de commande de liaison montante (uci) sur plusieurs canaux physiques partagés de liaison montante (pusch)
US20210297204A1 (en) Downlink waveform type and guard interval adaptation for wireless system
WO2018064477A1 (fr) Systèmes et procédés de réception discontinue dans une communication de dispositif à dispositif
US20200389917A1 (en) Monitoring control channels in control resource sets for new radio
US12256264B2 (en) Latency management for integrated access and backhaul
US20220039032A1 (en) Coordination signaling for synchronization signal block (ssb) transmission configurations
WO2018031802A1 (fr) Optimisations de radiomessagerie à base de réseau d'accès radioélectrique
US11968568B2 (en) Performance measurements in a next generation radio access network (NG-RAN)
US11991610B2 (en) Long term evolution (LTE) control region for downlink transmissions for enhanced machine type communications (eMTC)
US20210195395A1 (en) Release of emergency pdn bearer for a volte emergency call without emergency registration
HK1258369B (en) Method and apparatus for radio access network (ran)-originated paging messaging

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17718197

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17718197

Country of ref document: EP

Kind code of ref document: A1