WO2018087034A1 - Données de petite taille peu fréquentes pour dispositifs sans fil à économie de batterie - Google Patents

Données de petite taille peu fréquentes pour dispositifs sans fil à économie de batterie Download PDF

Info

Publication number
WO2018087034A1
WO2018087034A1 PCT/EP2017/078311 EP2017078311W WO2018087034A1 WO 2018087034 A1 WO2018087034 A1 WO 2018087034A1 EP 2017078311 W EP2017078311 W EP 2017078311W WO 2018087034 A1 WO2018087034 A1 WO 2018087034A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless device
radio access
core network
node
data
Prior art date
Application number
PCT/EP2017/078311
Other languages
English (en)
Inventor
Stefan Rommer
Gunnar Rydnell
Kaj Johansson
Hans Bertil RÖNNEKE
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2018087034A1 publication Critical patent/WO2018087034A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to a wireless network and, in particular, to infrequent small data for battery saving wireless communication devices.
  • NG Next Generation
  • the solutions should allow for unidirectional transmission (i.e., uplink or downlink only transmission), efficient security mechanisms depending on user and/or operator needs, different options for addressing, charging, policing, and inter-operator interworking.
  • a method of operation of one or more core network nodes in a Core Network (CN) of a wireless communications system comprises receiving data destined for a wireless device, where the wireless device is unreachable via a Radio Access Network (RAN).
  • RAN Radio Access Network
  • the wireless device is unreachable while operating in a Power Savings Mode (PSM) or extended idle mode Discontinuous Reception (eDRX) or similar.
  • PSM Power Savings Mode
  • eDRX Extended idle mode Discontinuous Reception
  • the method further comprises buffering the data in the CN until the wireless device is indicated as being reachable via the RAN and, upon the wireless device being indicated as being reachable, forwarding the data to the wireless device via the RAN.
  • Figure 1 illustrates one example of a wireless communication system in which embodiments of the present disclosure may be implemented
  • FIG. 2 illustrates one example of a downlink Packet Data Unit (PDU) flow
  • Figure 3 illustrates one example of a downlink PDU flow for a wireless device operating in a power savings mode according to some embodiments of the present disclosure
  • Figures 4 and 5 illustrate example embodiments of a wireless device
  • Figures 6 through 8 illustrate example embodiments of a network node.
  • Radio Node As used herein, a "radio node” is either a radio access node or a wireless device.
  • Radio Access Node As used herein, a “radio access node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals, preferably within a cell, preferably covering a limited geographical area.
  • RAN Radio Access Network
  • a radio access node examples include, but are not limited to, a base station (e.g., an enhanced or evolved Node B (eNB) in a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.
  • a radio access node may also be referred to herein as a RAN node or an Access Network (AN) node.
  • AN Access Network
  • a cell may correspond to one or more beams within which a RAN node transmits and/or receives radio signals.
  • Core Network Node is any type of node in a Core Network (CN).
  • CN Core Network
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network
  • MME Mobility Management Entity
  • Packet Data Network Packet Data Network
  • the CN nodes may be virtual or functional entities, e.g. the CN node may be a function, i.e. a function implemented by the CN.
  • Wireless Device As used herein, a “wireless device” is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting and/or receiving signals to a radio access node(s). Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device. A wireless device is also referred to herein as a wireless communication device.
  • UE User Equipment device
  • MTC Machine Type Communication
  • Network Node As used herein, a "network node” is any node that is either part of the radio access network or the CN of a cellular communications network/system.
  • NG Generation
  • beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.
  • 3GPP TR 23.799 presents a number of “Key Issues” and a number of “solutions.”
  • Key Issue 4 One of the key issues, which is referred to in 3GPP TR 23.799 as “Key Issue 4,” addresses the scenario for infrequent small user data transmission with minimal signalling.
  • requirements listed in 3GPP TR 23.799 for Key Issue 4 include:
  • the solutions should allow for unidirectional transmission (i.e., uplink or downlink only transmission), efficient security mechanisms depending on user and/or operator needs, different options for addressing, charging, policing, and inter-operator interworking.
  • 3GPP TR 23.799 includes a solution, referred to as "Solution 4.18" and is described in Section 6.4.18 of 3GPP TR 23.799, for infrequency small data. The requirements for infrequent small data mentioned in Key Issue 4 were considered. Solution 4.18 is based on reusing the Inactive 'state' which is expected to be defined by the RAN and also applicable for small data transfers. In this way, a unified handling of sessions is reached.
  • wireless devices may be more or less mobile, ranging from stationary wireless devices such as, e.g., the smart home with wireless devices attached to refrigerators to highly moving wireless devices in vehicles.
  • stationary wireless devices such as, e.g., the smart home with wireless devices attached to refrigerators to highly moving wireless devices in vehicles.
  • the combination of high mobility and infrequent data with battery saving requirements may need further considerations.
  • Solution 4.18 for infrequent small data uses the method of INACTIVE state in the AN.
  • the wireless device e.g., UE
  • the CN will forward any received packets towards the AN immediately. It is then the responsibility of the AN, if the wireless device is in INACTIVE state, to store the packet, to page the wireless device if needed, and deliver the packet to the wireless device when reachable.
  • a CN Control Plane (CP) function uses messages similar to Release 13
  • the wireless communications system 10 which may also be referred to herein as a cellular communications system, includes a RAN 12 or AN or similar that includes a number of radio access nodes 14 providing radio access to wireless devices 16 (e.g., UEs).
  • the radio access nodes 14 may also be referred to herein as RAN nodes or AN nodes 14.
  • the radio access nodes 14 are connected to a CN 18 that includes a number of CN nodes 20 or functions (e.g., MMEs, Serving Gateways (S-GWs), P-GWs, CP functions, UP functions, MMF, SMF, and/or the like).
  • CN nodes 20 or functions (e.g., MMEs, Serving Gateways (S-GWs), P-GWs, CP functions, UP functions, MMF, SMF, and/or the like).
  • functions e.g., MMEs, Serving Gateways (S-GWs), P-GWs, CP functions, UP functions, MMF, SMF, and/or the like.
  • the wireless communications system 10 is a 3GPP NG or 5G system, wherein the RAN 12 is a NG (R)AN and the CN 18 is a NG CN.
  • the Packet Data Unit may be Internet Protocol (IP) based or non- IP based.
  • IP Internet Protocol
  • the method is based on using the methods in RAN developed for 5G, specifically the "RRC Inactive Connected/Active Connected" states and potential optimizations thereof.
  • the solution thus assumes that the AN does not release the wireless device, or UE, context. In case the AN releases the UE context, the solution falls back to regular CN IDLE state handling.
  • - CN CP preserves UE PDU session contexts as long as the PDU session is maintained.
  • - CN UP can refrain from preserving wireless device, or UE, state
  • CN UP context and connectivity is established when wireless device, or UE, originated or terminated packets need to be forwarded in the UP.
  • a UE context is held for a short time in the CN UP to facilitate the server to send, e.g., Acknowledgements (ACKs) to/from the wireless device 16.
  • ACKs Acknowledgements
  • Removing UE context from CN UP during inactivity periods and maintaining UE state only for a small fraction of the time allows the CN UP to multiplex its resources over a larger number of wireless devices 16.
  • the downlink PDUs are stored in the CN 18 until an indication is received that the wireless device 16 is reachable or the paging occasion occurs.
  • CN CP function is to certain extent synchronized with the AN.
  • Figure 2 illustrates how a downlink PDU is transferred from a data network 28 (e.g., from an Application Server (AS) in the data network) to the wireless device 16, where the wireless device 16 is a device that sends data infrequently.
  • a data network 28 e.g., from an Application Server (AS) in the data network
  • Figure 2 is a reproduction (at least to a large extent) of Figure 6.4.18.2.3-1 of 3GPP TR 23.700.
  • Figure 2 illustrates a number of CN functions that are implemented in the CN 18 via one or more of the CN nodes 20.
  • Figure 2 illustrates a CP function 22, an UP function 24, and a policy function 26.
  • RRC Radio Resource Control
  • Step 100 An application server in a data network 28 transfers a mobile terminated PDU towards the UP function 24.
  • IP the protocol for transporting a mobile terminated PDU towards the UP function 24.
  • IP address is the IP address of the wireless device 16. Note that this solution relies on the regular PDU session concept and any solution for non-IP PDU types thus applies also for this solution, i.e. no separate solution for non-IP is needed.
  • Step 102 The UP function 24 receives the downlink PDU and, as the UE context does not exist, the UP function 24 obtains the UE context from the proper CP function 22.
  • the IP address is used to derive the proper Session Management (SM) function (i.e., the control function (separated from the UP function)).
  • SM Session Management
  • this step is omitted.
  • Step 104 The UP function 24 encapsulates the PDU into a tunnel protocol header and forwards the PDU to the AN, and more specifically the radio access node 14 identified by the AN tunnel identifier part of the UE context.
  • the UP function 24 may enforce, e.g., Quality of Service (QoS) marking, rate limiting, charging, etc.
  • QoS Quality of Service
  • Step 106 When the radio access node 14 receives the PDU, the wireless device 16 and the radio access node 14 transition to RRC active state.
  • Step 108 The radio access node 14 forwards the PDU to the wireless device 16.
  • Step 1 10 After the radio access node 14 has forwarded the PDU, the radio access node 14 initiates the transition to RRC inactive state with the wireless device 16, e.g. due to wireless device 16 inactivity during a time period. The wireless device 16 is moved to RRC inactive connected state.
  • Step 1 12 The UP function 24 may remove the UE context due to, e.g., inactivity.
  • the UE context may need to be kept in the UP function 24 for longer times to avoid unnecessary signaling between UP and CP in step 102 (e.g., due to Denial-of- Service (DoS) attacks in which case the signaling should not be allowed to propagate into the network).
  • the CP function 22 can instruct the UP function 24 to not release UE context or instruct the UP function 24 to use a longer inactivity timer.
  • Figure 3 illustrates how a downlink PDU is transferred from the data network 28 to a battery saving wireless device 16 that sends data infrequently according to some embodiments of the present disclosure. Note that while a number of "steps" are illustrated, these "steps" are actions that can be performed in any desired order unless otherwise stated or required. Further, Figure 3 illustrates a number of CN functions that are implemented in the CN 18 via one or more of the CN nodes 20. In particular, Figure 3 illustrates a CP function 22, a UP function 24, and a policy function 26.
  • Step 200 The wireless device 16 (e.g., UE) enters RRC Idle.
  • the wireless device 16 prior to entering RRC Idle, the wireless device 16 was connected to a source radio access node 14-1 .
  • Step 202 The state change is notified to the CN 18 (i.e., to the CP function 22) as in Release 13 in the S1AP suspend procedure.
  • NG Mobility Management (MM) enters Idle.
  • the source radio access node 14-1 communicates with the CP function 22 to notify the CN 18 of this state change (i.e., notify the CN 18, or more specifically the CP function 22, that the wireless device 16 is now unreachable).
  • Step 204 An application server in the data network 28 transfers a MT PDU towards the UP function(s) 24.
  • the destination address is the IP address of the wireless device 16.
  • Step 206 If the UE context does not exist, the UP function(s) 24 obtains the UE context for the wireless device 16 from the proper CP function(s) 22. In case of IP, the IP address is used to derive the proper SM function. In the case of non-IP, some other device or user identifier received in the packet is used to derive the proper SM function. In case a UE context already exists in the UP function(s) 24, this step is omitted.
  • Step 208 In case the wireless device 16 is subject to functionality similar to Release 13 PSM, the downlink PDU is buffered in the CN 18, the CN 18 waiting for the AN to indicate the wireless device 16 is reachable, e.g., by means of a Release 13 S1AP resume procedure, before proceeding to forward the PDU to the AN.
  • the CP function(s) 22 and/or the UP function(s) 24, either together or alone buffer the PDU, e.g., in a respective CN node 20.
  • the CN 18 buffers the PDU until the CN 18 receives an indication that the wireless device 16 is reachable.
  • the wireless device 16 may be considered "reachable" when the wireless device 16 wakes up from PSM to check for (i.e., to listen for) paging, e.g., according to a configured DRX cycle.
  • Step 210 For long DRX, the CP function 22 will be able to calculate the paging occasions assuming the CN CP function 22 is to some extent synchronized with the AN.
  • the CP function 22 pages the wireless device 16. This paging may be performed in the conventional manner.
  • the CP function 22 may initiate the transmission of a paging message to the wireless device 16 by, e.g., the radio access nodes 14 in a tracking area in which the wireless device 16 is located.
  • the wireless device 16 is located within a tracking area that includes at least a target radio access node 14-2.
  • the target radio access node 14-2 may be the same as the source radio access node 14-1 or different than the source radio access node 14-1 depending on, e.g., the mobility of the wireless device 16.
  • Step 212 In response to the paging, the wireless device 16 transmits a notification to, in this example, the target radio access node 14-2 that the wireless device 16 is now reachable.
  • the wireless device 16 may transmit a paging response that indicates to the target radio access node 14-2 that the wireless device 16 is now reachable.
  • the target radio access node 14-2 provides a notification to the CN 18, and more specifically to the CP function 22 in this example, that the wireless device 16 is reachable.
  • the AN indicates to the CN 18 that the wireless device 16 is reachable, e.g. using the Release 13 S1AP resume procedure.
  • Step 214 The UP path between the AN and the UP function(s) 24 (specifically between the target radio access node 14-2 and the UP function(s) 24) is set up.
  • the UP function(s) 24 is updated with the AN tunnel identifier for the PDU session.
  • Step 216 The PDU is forwarded to the AN (specifically to the radio access node 14, which in this example is the target radio access node 14-2) identified by the AN tunnel identifier part of the UE context.
  • the UP function 24 may enforce, e.g., QoS marking, rate limiting, charging, etc.
  • FIG. 4 is a schematic block diagram of the wireless device 16 according to some embodiments of the present disclosure.
  • the wireless device 16 includes circuitry 22 comprising one or more processors 24 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like) and memory 26.
  • the wireless device 16 also includes one or more transceivers 28 each including one or more transmitters 30 and one or more receivers 32 coupled to one or more antennas 34.
  • the functionality of the wireless device 16 described above may be fully or partially implemented in software that is, e.g., stored in the memory 26 and executed by the processor(s) 24.
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless device 16 according to any of the embodiments described herein is provided.
  • a carrier containing the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • Figure 5 is a schematic block diagram of the wireless device 16 according to some other embodiments of the present disclosure.
  • the wireless device 16 includes one or more modules 36, each of which is implemented in software.
  • the module(s) 36 provide the functionality of the wireless device 16 described herein.
  • FIG. 6 is a schematic block diagram of a network node 38 (e.g., a radio access node 14 or a CN node 20) according to some embodiments of the present disclosure.
  • the network node 38 includes a control system 40 that includes circuitry comprising one or more processors 42 (e.g., CPUs, ASICs, FPGAs, and/or the like) and memory 44.
  • the control system 40 also includes a network interface 46.
  • the network node 38 is a radio access node 14
  • the network node 38 also includes one or more radio units 48 that each include one or more transmitters 50 and one or more receivers 52 coupled to one or more antennas 54.
  • the functionality of the network node 38 (e.g., the functionality of the radio access node 14 or the functionality of a CN node 20 implementing, e.g., the CP function 22 and/or the UP function 24) described above may be fully or partially implemented in software that is, e.g., stored in the memory 44 and executed by the processor(s) 42.
  • FIG. 7 is a schematic block diagram that illustrates a virtualized embodiment of the network node 38 (e.g., the radio access node 14 or a CN node 20 implementing the CP function 22 and/or the UP function 24) according to some embodiments of the present disclosure.
  • a "virtualized" network node 38 is a network node 38 in which at least a portion of the functionality of the network node 38 is implemented as a virtual component (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • the network node 38 optionally includes the control system 40, as described with respect to Figure 6.
  • the network node 38 is a radio access node 14
  • the network node 38 also includes the one or more radio units 48, as described with respect to Figure 6.
  • the control system 40 (if present) is connected to one or more processing nodes 56 coupled to or included as part of a network(s) 58 via the network interface 46.
  • the one or more radio units 48 (if present) are connected to the one or more processing nodes 56 via a network interface(s).
  • all of the functionality of the network node 38 described herein may be implemented in the processing nodes 56 (i.e., the network node 38 does not include the control system 40 or the radio unit(s) 48).
  • Each processing node 56 includes one or more processors 60 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 62, and a network interface 64.
  • functions 66 of the network node 38 described herein are implemented at the one or more processing nodes 56 or distributed across the control system 40 (if present) and the one or more processing nodes 56 in any desired manner.
  • some or all of the functions 66 of the network node 38 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 56.
  • additional signaling or communication between the processing node(s) 56 and the control system 40 (if present) or alternatively the radio unit(s) 48 (if present) is used in order to carry out at least some of the desired functions.
  • the control system 40 may not be included, in which case the radio unit(s) 48 (if present) communicates directly with the processing node(s) 56 via an appropriate network interface(s).
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 38 or a processing node 56 according to any of the embodiments described herein is provided.
  • a carrier containing the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 8 is a schematic block diagram of the network node 38 (e.g., the radio access node 14 or a CN node 20 implementing the CP function 22 and/or the UP function 24) according to some other embodiments of the present disclosure.
  • the network node 38 includes one or more modules 68, each of which is implemented in software.
  • the module(s) 68 provide the functionality of the network node 38 described herein.
  • paging (210) the wireless device (16) comprises paging (210) the wireless device 16 during a paging occasion configured for the wireless device (16).
  • the wireless device (16) is indicated as unreachable while the wireless device (16) is operating in a power savings mode, and the paging occasion is a paging occasion configured for the wireless device (16) during a period of time in which the wireless device (16) wakes up from power savings mode to check for paging.
  • the core network node (20) comprising one or more modules (68) operable to perform the method of any one of embodiments 1 to 9.

Landscapes

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

Abstract

La présente solution concerne un procédé de fonctionnement d'un ou plusieurs nœuds de réseau central (20) dans un réseau central (18) d'un système de communication sans fil (10) et un nœud de réseau central (20) conçu pour mettre en oeuvre le procédé, comprenant les étapes consistant à : recevoir (204) des données destinées à un dispositif sans fil (16), le dispositif sans fil (16) étant inaccessible par l'intermédiaire d'un réseau d'accès radio (12) ; mettre en mémoire tampon (208) les données dans le réseau central (18) jusqu'à ce que le dispositif sans fil (16) soit indiqué comme pouvant être atteint par l'intermédiaire du réseau d'accès radio (12) ; et, lorsque le dispositif sans fil (16) est indiqué comme pouvant être atteint, transmettre (216) les données au dispositif sans fil (16) par l'intermédiaire du réseau d'accès radio (12).
PCT/EP2017/078311 2016-11-11 2017-11-06 Données de petite taille peu fréquentes pour dispositifs sans fil à économie de batterie WO2018087034A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662420951P 2016-11-11 2016-11-11
US62/420,951 2016-11-11

Publications (1)

Publication Number Publication Date
WO2018087034A1 true WO2018087034A1 (fr) 2018-05-17

Family

ID=60702590

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/078311 WO2018087034A1 (fr) 2016-11-11 2017-11-06 Données de petite taille peu fréquentes pour dispositifs sans fil à économie de batterie

Country Status (1)

Country Link
WO (1) WO2018087034A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112369113A (zh) * 2018-05-18 2021-02-12 瑞典爱立信有限公司 用于在5gs中的网络调度的到cm-connected/rrc连接模式的ue转变的装置和方法
EP3934207A4 (fr) * 2019-03-20 2022-04-27 Huawei Technologies Co., Ltd. Procédé et appareil de communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3018945A1 (fr) * 2014-11-04 2016-05-11 Alcatel Lucent Support de communication à destination d'une station mobile dans un système par paquets évolué
US20160262041A1 (en) * 2014-06-25 2016-09-08 Telefonaktiebolaget L M Ericsson (Publ) Node and method for buffering downlink data
WO2016163998A1 (fr) * 2015-04-07 2016-10-13 Nokia Solutions And Networks Oy Procédé et appareil pour faire face à la consommation énergétique d'un équipement d'utilisateur

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160262041A1 (en) * 2014-06-25 2016-09-08 Telefonaktiebolaget L M Ericsson (Publ) Node and method for buffering downlink data
EP3018945A1 (fr) * 2014-11-04 2016-05-11 Alcatel Lucent Support de communication à destination d'une station mobile dans un système par paquets évolué
WO2016163998A1 (fr) * 2015-04-07 2016-10-13 Nokia Solutions And Networks Oy Procédé et appareil pour faire face à la consommation énergétique d'un équipement d'utilisateur

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112369113A (zh) * 2018-05-18 2021-02-12 瑞典爱立信有限公司 用于在5gs中的网络调度的到cm-connected/rrc连接模式的ue转变的装置和方法
EP3934207A4 (fr) * 2019-03-20 2022-04-27 Huawei Technologies Co., Ltd. Procédé et appareil de communication
US11963034B2 (en) 2019-03-20 2024-04-16 Huawei Technologies Co., Ltd. Communication method and apparatus

Similar Documents

Publication Publication Date Title
US11064457B2 (en) Paging policy differentiation in 5G system
US11611949B2 (en) Keeping the UE awake
CN107113598B (zh) 演进分组系统中的移动台终止的通信的支持
US10631266B2 (en) Mobile-terminated data control method in wireless communication system and device therefor
EP3162127B1 (fr) Noeud et procédé pour mettre en mémoire tampon des données de liaison descendante
CN109076427B (zh) 经由scef的高延时通信
US11778550B2 (en) Methods and apparatus relating to inactive mode in a wireless communications network
US20190021130A1 (en) Method for changing connection mode and mobility management entity
JP2019525553A (ja) 低頻度の小さいデータのための効率的な送達方法および装置
US20170311371A1 (en) Method and nodes for handling connections in a communications system
KR20160060091A (ko) 페이징 방법, 네트워크 디바이스 및 통신 시스템
CN112369113A (zh) 用于在5gs中的网络调度的到cm-connected/rrc连接模式的ue转变的装置和方法
WO2018087034A1 (fr) Données de petite taille peu fréquentes pour dispositifs sans fil à économie de batterie
EP3457807B1 (fr) Dispositif de terminal et procédés permettant de transmettre des données
WO2018107368A1 (fr) Procédé et dispositif d'établissement de connexion pour une transmission de données
KR101356051B1 (ko) 이동 통신망에서 전송되는 데이터의 착신 지연 시간을 감소시키는 방법
WO2020254960A1 (fr) Systèmes et procédés de transmission de données précoce à terminaison mobile
US11451996B2 (en) Methods and apparatuses for PLMN rate control
US20220174775A1 (en) Ue-triggered connection resume with early data transmission and network-triggered connection resume

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17816451

Country of ref document: EP

Kind code of ref document: A1