WO2020085964A1 - Solutions pour permettre une transmission de données à faible surdébit pour dispositifs cellulaires - Google Patents

Solutions pour permettre une transmission de données à faible surdébit pour dispositifs cellulaires Download PDF

Info

Publication number
WO2020085964A1
WO2020085964A1 PCT/SE2018/051095 SE2018051095W WO2020085964A1 WO 2020085964 A1 WO2020085964 A1 WO 2020085964A1 SE 2018051095 W SE2018051095 W SE 2018051095W WO 2020085964 A1 WO2020085964 A1 WO 2020085964A1
Authority
WO
WIPO (PCT)
Prior art keywords
user plane
wireless communication
network node
communication device
network
Prior art date
Application number
PCT/SE2018/051095
Other languages
English (en)
Inventor
Göran RUNE
Gunnar Mildh
Jari Vikberg
Paul Schliwa-Bertling
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)
Priority to PCT/SE2018/051095 priority Critical patent/WO2020085964A1/fr
Publication of WO2020085964A1 publication Critical patent/WO2020085964A1/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/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • 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 disclosure relates to methods and devices of connecting a wireless communication device to a communication network.
  • 3rd Generation Partnership Project (3 GPP) is standardizing a fifth generation (5G) Core Network (CN), being referred to as 5GC, and Next Generation Radio Access Network (NG-RAN).
  • 5G Fifth Generation
  • NG-RAN Next Generation Radio Access Network
  • FIG. 1 shows a 5G wireless communication network 100 as depicted in 3GPP TS 23.50 1 comprising a User Equipment (UE, 110) in the form of for instance a mobile phone, tablet, smart phone, Internet-of- Things (IoT) sensor, etc., connecting to a (Radio) Access Network ((R)AN, 111), and to a Data Network (DN, 113) via a User Plane Function (UPF, 112).
  • the UPF is a service function that processes user plane packets ; processing may include altering the packet’s payload and/ or header, interconnection to data network(s), packet routing and forwarding, etc.
  • the network is shown to comprise a Network Slice Selection
  • NSSF Network Exposure Function
  • NEF Network Exposure Function
  • NRF Network Exposure Function
  • NRF Network Exposure Function
  • NRF Network Function Repository Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • AF Application Function
  • the network is shown to comprise an Authentication Server Function (AUSF, 120) for storing data for authentication of UE, a core network control plane function configured to provide mobility management in the form of an Access and Mobility Function (AMF, 121) for providing UE- based authentication, authorization, mobility management, etc., and a core network control plane function configured to provide session management in the form of a Session Management Function (SMF, 122) configured to perform session management, e.g. session establishment, modify and release, etc.
  • AUSF Authentication Server Function
  • AMF Access and Mobility Function
  • SMF Session Management Function
  • Figure 2 illustrates a prior art 5G wireless communication network 100 in a different view illustrating a radio base station 124, a so called Next
  • the gNB 124 comprises a radio access network control plane function in the form of a Central Unit Control Plane (CU-CP, 125), a radio access network user plane function in the form of a Central Unit User Plane (CU-UP, 126) and a Distributed Unit (DU, 127) for connecting the NG UE 110 to the control plane and the user plane, respectively, which is referred to as a Higher Layer Split (HLS).
  • the gNB provides NR control and user plane terminations towards the UE, and is connected via NG-C/ N2 and NG-U/ N3 interfaces to the 5GC.
  • the NG-RAN may comprise evolved Long Term Evolution (eLTE) base stations, referred to as ng-eNBs.
  • eLTE evolved Long Term Evolution
  • the CU-CP 125 hosts the Radio Resource Control (RRC) protocol and the control plane part of the Packet Data Convergence Protocol (PDCP) protocol, while the CU-UP 126 hosts the Service Data Adaptation Protocol (SDAP) protocol and the user plane part of the PDCP protocol.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • SDAP Service Data Adaptation Protocol
  • the CU-CP 125 is controlling the CU-UP 126 via an El interface.
  • the CU-CP 125 is the function that terminates an N2 interface from the AMF 121 in the 5GC
  • the CU-UP 126 is the function terminating an N3 interface from the UPF H2b in the 5GC.
  • the NG UE 110 has one CU-UP 126 configured per Packet Data Unit (PDU) session.
  • PDU Packet Data Unit
  • the SMF 122 connects to UPFs H2a, H2b via the N4 interface and to the AMF 121 via the Nll interface.
  • the Nll interface can alternatively be realized using service-based interfaces utilized by the AMF 121 and SMF 122, i.e. Namf and Nsmf, respectively.
  • Figure 2 illustrates that the network 100 comprises a plurality of UPFs H2a, H2b, but it is also envisaged that the UPF H2b connecting the NG UE 110 to a local service network 123 via local breakout is omitted, in which case the interface N3 extends between the CU-UP 126 and the UPF H2a.
  • a UE power-saving state such as NR RRC_INACTIVE state or NR
  • RRC_IDLE defined in 3GPP has potential to reduce signalling over the radio interface which in turn reduces UE battery consumption. This is particularly evident for UEs/ devices only sending small amounts of data, such as Cellular Internet of Things (CIoT) devices.
  • CCIoT Cellular Internet of Things
  • NR RRC_INACTIVE state a problem with the NR RRC_INACTIVE state is that a relatively large amount of configuration data associated with the UE must be kept in the RAN, which is not efficient for devices which rarely send any data (such as e.g. once a month or once a week, or even once every day), for instance CIoT devices.
  • An object of the disclosure is to solve, or at least mitigate, this problem in the art and thus to provide methods for efficient communication for devices which rarely transmits/ receives data.
  • a method performed by a network node providing radio access network, RAN, control plane functionality in a wireless communication network the network node being configured to connect a wireless communication device to a control plane of the wireless communication network.
  • the method comprises instructing at least one network node providing RAN user plane functionality in the wireless communication network to maintain UE user plane context upon the wireless communication device entering a power-saving state, and releasing UE control plane context at said network node providing RAN control plane functionality upon the wireless communication device entering the power saving state.
  • a node configured to provide RAN control plane functionality in a communications network to enable connection of a wireless communication device to a control plane of the wireless communication network
  • the node comprising a processing unit and a memory, said memory containing instructions executable by said processing unit, whereby the node is operative to instruct at least one network node providing RAN user plane functionality in the wireless communication network to maintain UE user plane context upon the wireless communication device entering a power-saving state, and to release UE control plane context at said network node providing RAN control plane functionality upon the wireless communication device entering the power saving state.
  • This object is attained in a third aspect by a method performed by a network node providing RAN user plane functionality in a wireless communication network, the network node being configured to connect a wireless
  • the method comprises receiving, from a network node providing RAN control plane functionality in the wireless communication network, an instruction to maintain UE user plane context upon the wireless
  • a node configured to provide RAN user plane functionality in a wireless communication network to enable connection of a wireless communication device to a user plane of the wireless communication network
  • the node comprising a processing unit and a memory, said memory containing instructions executable by said processing unit, whereby the node is operative to receive, from a network node providing RAN control plane functionality in the wireless communication network, an instruction to maintain UE user plane context upon the wireless
  • the method comprises receiving, from a network node providing RAN control plane functionality in the wireless communication network, information identifying at least one network node providing RAN user plane functionality in the wireless communication network, the at least one network node providing RAN user plane functionality maintaining UE user plane context upon the wireless communication device entering a power saving state, and storing said information.
  • a wireless communication device configured to connect to a wireless communication network
  • the wireless communication device ( 110) comprising a processing unit and a memory, said memory containing instructions executable by said processing unit, whereby the wireless communication device is operative to receive, from a network node providing RAN control plane functionality in the wireless communication network, information identifying at least one network node providing RAN user plane functionality in the wireless communication network, the at least one network node providing RAN user plane functionality maintaining UE user plane context upon the wireless communication device entering a power-saving state, and to store said information.
  • a method performed by a core network user plane function configured to provide user plane functionality in a wireless communication network, the core network user plane function being configured to connect a wireless communication device to a user plane of the wireless communication network.
  • the method comprises receiving, from a core network control plane function configured to provide session management, an instruction to suspend a communication session between said core network user plane function and at least one network node providing RAN user plane functionality in downlink direction but to keep the communication session active in uplink direction upon the wireless communication device entering the power-saving state.
  • a core network user plane function configured to provide user plane functionality in a wireless communication network for enabling connection of a wireless
  • the core network user plane function comprising a processing unit and a memory, said memory containing instructions executable by said processing unit, whereby the core network user plane function is operative to receive, from a core network control plane function configured to provide session management, an instruction to suspend a communication session between said core network user plane function and at least one network node providing RAN user plane functionality in downlink direction but to keep the communication session active in uplink direction upon the wireless communication device entering the power-saving state.
  • This object is attained in a ninth aspect by a method performed by a
  • the method comprises receiving, from the wireless communication device or at least one network node providing RAN control plane functionality, information identifying one of the said at least one network node providing RAN user plane functionality, information identifying UE user plane context being ongoing with said one of said at least one network node providing RAN user plane functionality, and data to be sent by the wireless communication device, identifying said one of said at least one network node providing RAN user plane functionality from the received information, and sending said data and said information identifying UE user plane context to the identified one of said at least one network node providing RAN user plane functionality for further uplink transmission.
  • Distributed Unit configured to connect a wireless communication device to at least one network node providing RAN control plane functionality, and to at least one network node providing RAN user plane functionality in a wireless communication network
  • the Distributed Unit comprising a processing unit and a memory, said memory containing instructions executable by said processing unit, whereby the Distributed Unit is operative to receive, from the wireless communication device or at least one network node providing RAN control plane functionality, information identifying one of the said at least one network node providing RAN user plane functionality, information identifying UE user plane context being ongoing with said one of said at least one network node providing RAN user plane functionality, and data to be sent by the wireless communication device, identify said one of said at least one network node providing RAN user plane functionality from the received information, and to send said data and said information identifying UE user plane context to the identified one of said at least one network node providing RAN user plane functionality for further uplink transmission.
  • Figure 1 shows a prior art 5G wireless communication network
  • Figure 2 illustrates a prior art 5G wireless communication network in a different view:
  • FIG 3 shows a 5G wireless communication network similar to that of Figure 1 in which embodiments are implemented, where various aspects of are indicated;
  • Figure 4 shows a signalling diagram illustrating establishment of a PDU session for a UE in a 5G communication network as performed in the art
  • Figure 5 shows a signalling diagram illustrating establishment of a PDU session for a UE in a 5G communication network as performed according to an embodiment
  • Figure 6 shows a signalling diagram illustrating an UE entering a power saving state according to an embodiment
  • Figure 7a shows a signalling diagram illustrating uplink data transmission when a UE exits a power-saving state according to an embodiment
  • Figure 7b shows a signalling diagram illustrating uplink data transmission when a UE exits a power-saving state according to another embodiment
  • Figure 8 shows a signalling diagram illustrating downlink data reception at the UE upon the UE exiting the power-saving state
  • Figure 9 shows a signalling diagram illustrating change of CU-UP according to an embodiment
  • Figure 10 shows a combined CU-UP and UPF according to an embodiment
  • Figure 11 illustrates a CU-CP according to an embodiment
  • Figure 12 illustrates a CU-UP according to an embodiment
  • Figure 13 illustrates a wireless communication device according to an embodiment
  • Figure 14 illustrates a UPF according to an embodiment
  • Figure 15 illustrates a DU according to an embodiment.
  • Figure 1 shows a prior art 5G wireless communication network having been previously discussed.
  • Figure 2 illustrates a prior art 5G wireless communication network in a different view, also having been previously discussed.
  • a problem with the prior art NR RRC_INACTIVE state is that a relatively large amount of configuration data associated with the UE must be kept in the RAN, which is not efficient for devices which rarely send any data.
  • control plane aspects of this are problematic since it is the responsibility of the RAN to keep track of the UEs in this state and the UE needs to do periodic or mobility-based RAN area updates and the RAN needs to page the UE for incoming data.
  • both RAN control and user plane contexts are released, which is also problematic since appropriate RAN nodes must be supplied with the contexts again upon the UE attaching to the RAN, i.e. upon the UE entering CONNECTED state, which results in overhead signalling as well as increased battery consumption in the UE.
  • NAS non-access stratum
  • This solution has the advantage of facilitating low signalling overhead, but instead it will impact the CN control plane with additional functionality needed to support user data via control signalling. Sending data via control signalling is not generally seen as good practice, since it makes it difficult to separately optimize data and signalling.
  • SDFP Small Data Fast Path
  • the UE 110 Upon the UE 110 entering a power-saving state, it will enter CM-IDLE state in the control plane.
  • the RRC state for the UE in the power-saving state 110 may be a new sub-state of RRC_IDLE, a new sub-state of RRC_ INACTIVE or any other new RRC state.
  • the CU-CP 125 releases its UE control plane context and further signals to the CU-UP 126 to maintain the UE user plane context for the UE transiting to the power-saving state.
  • the UE is still in CM-IDLE towards the core network and existing CN based IDLE mobility mechanisms can be used.
  • the UE RAN user plane context e.g. PDCP
  • PDCP UE RAN user plane context
  • This embodiment facilitates battery-efficient infrequent data transmission for CIoT devices without the need to maintain UE control plane context in a RAN node while keeping UE user plane context user plane in the RAN, thereby e.g. enabling encryption and integrity protection handling in the RAN user plane node.
  • the latter means that there is no need to add such functionality to the UPF in 5GC.
  • the embodiments exemplified herein are described in an NR radio interface context or for NG-RAN connected to 5GC. However, the embodiments described are equally applicable to radio networks including LTE connected to Evolved Packet Core (EPC) networks, e.g. enhanced Machine-Type
  • EPC Evolved Packet Core
  • eMTC narrowband Internet of Things
  • NB-IoT narrowband Internet of Things
  • LoRA Long Range
  • Figure 3 shows a 5G wireless communication network similar to that of Figure 1 (but with a single UPF 112) in which embodiments are implemented, where various aspects are indicated.
  • the UE 110 transits to the power-saving state but stores information as regards which CU-UP(s) 126 will maintain the UE user plane context when the UE 110 enters the power-saving state. This will be referred to as a CU-UP identifier.
  • the UE 110 may store one CU-UP identifier for each PDU session, even if the PDU sessions are ongoing via one and the same CU-UP 126.
  • the CU-CP 125 releases the currently held UE control plane context upon the UE 110 entering the power-saving state.
  • the AMF 121 maintains the UE control plane context upon the UE 110 entering the power-saving state.
  • the UE control plane context in the AMF 121 is mainly used for Registration Management (RM) and Connection
  • At least one SMF 122 maintains the UE control plane context upon the UE 110 entering the power-saving state.
  • the UE control plane context in the SMF 122 is mainly used for Session Management (SM), e.g. UE PDU session(s).
  • SM Session Management
  • the CU-UP 126 maintains the currently held UE user plane context for each ongoing PDU session of the UE 110 upon the UE 110 entering the power saving state.
  • the UE 100 may have ongoing PDU sessions via different CU-UPs.
  • the UPF 112 maintains the currently held UE user plane context for each ongoing PDU session of the UE 110 upon the UE 110 entering the power saving state.
  • the UE 100 may have ongoing PDU sessions via different UPFs. g. User plane (UP) tunnels between the CU-UP (s) 126 and the UPF(s) 112 are temporarily disabled. This implies that uplink (UL) traffic is allowed to be sent from the CU-UP 126 to the UPF 112. For downlink (DL) traffic arriving at the UPF 112, the UPF 112 needs to trigger paging of the UE 110 by sending a Data Notification to the SMF 122.
  • UP User plane
  • Figure 4 shows a signalling diagram illustrating establishment of PDU session for an NG UE 110 in a 5G communication network 100 as performed in the prior art.
  • a first step S 10 1 the NG UE 110 sends a request for establishment of a PDU session to the AMF 121 which in step S102 selects an SMF 122 via which the PDU session will be managed.
  • step S103 the AMF 121 sends the PDU session request to the selected SMF 122, which transmits a response message back to the AMF 121 in step S104 before carrying through a PDU Session authentication/ authorization procedure with the NG UE 110 in step S 105.
  • the SMF 122 successfully authenticates the NG UE 110 , an UPF 112 is selected in step S106, via which the NG UE 110 will connect to the user plane of the network 100.
  • the SMF 122 sends an N4 session establishment request to the selected UPF 112 in step S107, and the UPF 112 sends a response accordingly in step S 108 comprising for instance an UPF transport address and an UPF Tunnel Endpoint Identifier (TEID).
  • TEID UPF Tunnel Endpoint Identifier
  • the SMF 122 will in its turn forward the received data to the AMF 121 in step S 109, which sends a request to the CU-CP 125 in step S110 to setup PDU session resources for the PDU session to be established, the request comprising the UPF transport address and the UPF TEID.
  • the CU-CP 125 selects a CU-UP 126 in step Slll via which the PDU session is to be established with the UPF 112, and a request to this effect is sent to the selected CU-UP 126 in step S 112 , which responds in step S 113 with a CU-UP establishment response comprising for instance a CU-UP transport address and a CU-UP TEID.
  • the CU-CP 125 performs an AN resources setup procedure with the NG UE 110 in step S 114 (the DU can also be configured in relation to this step) and sends a setup PDU session resources response (to the message received in step S110) to the AMF 121 containing the CU-UP transport address and the CU-UP TEID in step S 115.
  • the AMF 121 will in its turn send a message comprising the CU-UP transport address and the CU-UP TEID to the SMF 122 in step S 116, which sends the CU-UP transport address and the CU-UP TEID to the UPF 112 in step S 117.
  • step S 118 the PDU session is established with a user plane between the NG UE 110 , the DU 127, the CU-UP 126 and the UPF 112.
  • the UPF 112 and CU-UP 126 are selected independently of each other and these functions are also configured using separate interfaces, i.e. the UPF 112 is configured by the SMF 122 using the N4 interface and the CU-UP 126 is configured by the CU-CP 125 using the El interface.
  • Figure 4 shows a scenario where a single UPF 112 is selected by the SMF 122.
  • the SMF 122 may also select multiple UPFs H2a, H2b connected via N9 interface as shown in Figure 2.
  • Figure 5 shows a signalling diagram illustrating establishment of PDU session for an NG UE 110 in a 5G communication network 100 as performed according to an embodiment.
  • steps S20 1-S213 and steps S215-S217 are similar to corresponding steps S 10 1-S113 and S 115-S 117, respectively, of Figure 4 and will not be described again, with the exception of three options as listed in the following.
  • the UE 110 may indicate during PDU session setup, for instance in step S20 1 or step S205, that a special PDU session is required in line with what will be described with reference to embodiments herein.
  • the core network may verify UE subscription data (e.g. by contacting the UDM) to see if the UE 110 is allowed to setup a special PDU session.
  • This function could be performed by any appropriate core network node, e.g. the AMF, the SMF, the PCF, etc.
  • the core network may indicate, e.g. in step S210 , to the RAN that special PDU session resources are required. This would be a trigger for the RAN to setup RAN UP functions which will be kept also when the UE 110 is in CM-IDLE. Alternatively, this signalling could be performed by the UE 110 to the RAN (using RRC signalling).
  • step S2 l4a the CU-CP 125 informs the UE 110 about which CU-UP(s) store UE user plane context for the PDU session(s) that are ongoing for the UE 110. This will be referred to in the following as the CU-UP identifier. This information may consist of the address(es) to the CU-UP(s) storing the context.
  • the CU-CP 125 or the CU-UP 126 allocates one or more UE CU-UP identifiers (one per PDU session) which are signalled to the UE 110.
  • the UE CU-UP identifiers could contain information which the RAN later can use to identify the corresponding CU-UP serving the UE (or a specific data radio bearer (DRB) of the UE), and further an identifier of the UE user plane context in each CU-UP is allocated.
  • DRB data radio bearer
  • the CU-UP 126 stores UE user plane context for a number of PDU sessions that are ongoing for the UE 110 , in which case it is necessary to identify each individual UE user plane context.
  • Multiple coding options of this element exists, e.g. a concatenation of the CU-UP identifier or address and the UE context identifier within that CU-UP, or the CU-UP identifier could be any function of the two. It is envisaged that the CU-UP identifier will not be known in the UE to prevent revealing internal network information such as network topology and internal addresses. Multiple ways can be done to hide the structure of the CU-UP, e.g. encrypting it, hashing or scrambling.
  • the CU-CP 125 informs the UE 110 in step S2 l4a about which CU- UP(s) store UE user plane context for the PDU session(s) that are ongoing for the UE 110 by sending one or more CU-UP identifiers accordingly.
  • the CU-CP 125 further in step S2 l4a identifies each UE user plane context stored in each CU-UP 126 for each ongoing PDU session in order for the UE 110 to designate each individual UE user plane context (and associated PDU session) at the CU-UP(s).
  • the associated PDU session may be identified with a PDU session identifier that is a unique identifier for different PDU sessions of the UE.
  • the UE 110 will in step S2 l4b store the information indicating with which CU-UP(s) the UE 110 has ongoing PDU session(s), and an identifier for each individual UE user plane context associated with the ongoing PDU sessions and PDU session identifier(s), for subsequent use. With this procedure, the UE 110 is prepared for entering the power-saving state according to an embodiment which advantageously facilitates battery-efficient infrequent data transmission.
  • the information received in step S2 l4a may further comprise security information, e.g. a security token and/ or a secure checksum for enabling subsequent authentication of the UE, Quality of Service (QoS), sequence numbers and/ or UE capability information such as frequency bands, data limitations, etc.
  • security information e.g. a security token and/ or a secure checksum for enabling subsequent authentication of the UE, Quality of Service (QoS), sequence numbers and/ or UE capability information such as frequency bands, data limitations, etc.
  • the user plane tunnels between CU-UP(s) and UPF(s) will be set into a temporarily disabled state.
  • the UE 110 when the UE 110 is in the power-saving state and needs to send uplink data it will contact the RAN and send the data. Together with the data the UE 110 will provide the CU-UP identifier from the stored
  • the UE 110 also identifies UE user plane context stored in the CU-UP which should receive the uplink data.
  • the CU-UP identifier and the identifier for UE user plane context stored in the CU-UP are retrieved from the stored information based on the PDU session associated with the uplink data.
  • the UE 110 could also provide additional information to the network e.g.
  • QoS information (allowing the RAN to apply correct priority to the data), sequence numbers (which can be used to ensure loss-less, in order delivery, input to data verification, as well as preventing replay attacks), UE capability information (indicating frequency bands, data limitations, etc.).
  • the data transmission could be performed without setting up a UE specific RAN control connection or without setting up an UE specific CN-RAN control plane connection.
  • the solution also makes it possible for the RAN to trigger the setup of the RAN and CN-RAN connection only when needed.
  • the RAN CP node (e.g. the CU-CP 125) receiving the uplink data will forward the uplink data to the RAN UP node (e.g. the CU-UP 126) as indicated by the CU-UP identifier provided by the UE 110.
  • the RAN CP node (e.g. CU-CP 125) also forwards the identification of the UE user plane context stored in the CU-UP provided by the UE 110.
  • the RAN UP node receives the uplink data and the identification of the UE user plane context stored in the CU-UP, it will verify the integrity of the uplink data and/ or verify the authenticity of the UE 110 which sent the uplink data.
  • This verification is done by comparing the security token or secure checksum provided by the UE 110 with a security token or secure checksum that the RAN UP node calculates based on UE specific key(s) (as well as other UE security related information such as ciphering/ integrity algorithms, counter values, etc.) stored in the RAN UP node. If the two tokens or checksums match the data is verified and can be forwarded to higher layers (e.g. to packet core functions such as UPF over the temporarily disabled user plane tunnel).
  • the calculation of the security token or secure checksum could be done using secure hash over the data, using various input parameters such as counters or sequence number included with the data, and/ or overflow counters
  • the CN For downlink data it is possible for the CN to page the UE 110 and then the UE 110 responds with information about CU-UP(s) the UE 110 has ongoing PDU session(s), and an identifier for each individual UE user plane context associated with the ongoing PDU sessions and PDU session identifier (s). This makes it possible for the network to know where the UE 110 is and send the downlink data towards the UE (via the RAN UP node, and RAN base station serving the UE).
  • the paging performed by CN includes information about the PDU session related to the downlink data, e.g. as a PDU session identifier.
  • the UE 110 selects, from the stored information, the CU-UP identifier and the identifier for UE user plane context stored in the CU-UP based on the PDU session indicated in the paging performed by CN.
  • the UE 110 It is also possible for the UE 110 to monitor paging channels when
  • the AMF 121 which may not be aware of that the UE 110 is in an active state sending/ receiving data, could page the UE 110 e.g. due to downlink signalling. In case the UE 110 receives a page in this state it may respond with signalling towards the AMF 121 (e.g. NAS signalling).
  • the UE 110 will perform a UE registration update. During this update it is possible for the network to move the RAN UP node serving the UE to a different network node or instance. This can be done proactively by the RAN CP node receiving the UE signalling, e.g. the RAN CP node re-configures the UE data radio bearers to change the termination point (i.e. the RAN UP node such as CU- UP).
  • the RAN UP node such as CU- UP
  • the CN may initiate a procedure to remove the old RAN UP node. It is also possible that the old RAN UP node deletes the old UE context when the UE has not been active in that RAN CP node during a time period.
  • UE initiated meaning that UE initiates signalling when a certain event occurs, e.g. a timer times out, the UE has sent or receives a predetermined number of packets or bytes of data.
  • a certain event e.g. a timer times out
  • the RAN CP node When the RAN CP node receives the signalling it will refresh the RAN UP context, e.g. by triggering a key change or refresh.
  • the RAN UP node initiated (e.g. due to timer or ongoing transmission).
  • the RAN UP node could trigger paging (via RAN CP node or via AMF) of the UE when a certain even occurs to initiate the security context refresh.
  • the key refresh is triggered during an ongoing data
  • CN initiated.
  • the CN could due to similar events as above initiate key refresh, e.g. by paging UE or by informing RAN using signalling.
  • Figure 6 shows a signalling diagram illustrating the UE 110 entering a power saving state according to an embodiment. As is indicated in Figure 6, the preparation signalling of Figure 5 is performed before the UE 110 can enter the power-saving state.
  • a first step S30 1 the CU-CP 125 makes a decision to set the UE 110 in the power-saving state, for instance due to inactivity of the UE 110.
  • the CU-CP 125 sends a UE context release message to the AMF 121 in step S302, which message further may include an indication that the power saving state is to be entered.
  • the AMF 121 responds in step S303 with a confirmation message whereupon the CU-CP 125 and the UE 110 performs an RRC Connection Release procedure in step S304 after which the UE 110 enters the power-saving state in step S305.
  • the CU-UP identifier and information about UE user plane context stored in the CU-UP is provided to the UE 110 in step S2 l4a of Figure 2a alternatively is provided to the UE 110 in step S304.
  • step S305 is similar to that performed in the art for having a UE 110 transit to a power-saving state.
  • the CU-CP 125 sends an instruction to the CU- UP 126 in step S306 to maintain the UE user plane context for the UE 110. If the CU-UP 126 handles a plurality of ongoing PDU sessions, the CU-UP 126 will hold (and maintain) a set of UE user plane context for each ongoing PDU session. Further, even though a single CU-CP 125 is shown in Figure 6, the UE 110 may in practice communicate via a plurality of CU-CPs.
  • the CU-CP 125 may send the instruction of step S306 to a plurality of CU-UPs, and not just to a single one ss shown in Figure 6.
  • the CU-UP 125 will actively decide in step S307 to that the UE user plane context(s) for the UE 110 should be maintained.
  • the CU-CP 125 sends the instruction to the CU-UP 126 to maintain the UE user plane context for the UE 110 already in step S212 described in Figure 5.
  • the CU-UP 126 sends a confirmation in step S308 to the CU-CP 125 that the instruction has been received.
  • step S309 the CU-CP 125 sends a message to the AMF 121 indicating that the UE RAN control plane context has been released (but that the UE RAN user plane context is maintained), which message in an embodiment further indicates that the UE 110 has entered the power-saving state, after which the CU-CP 125 releases the UE control plane context in step S3 10.
  • the AMF 121 sends a PDU session update message (which may comprise an indication that the UE 110 has entered the power-saving state) to the SMF 122 in step S311. It is noted that the AMF 121 may send PDU session update messages to a plurality of SMFs even though a single SMF 122 is illustrated in Figure 6.
  • the SMF 122 configures UPF functionality by sending a PDU session modification message to the UPF 112 in step S312 comprising an instruction to temporarily disable the UP tunnel carried over interface N3 between the UPF 112 and the CU-UP 126. Accordingly, the UPF 112 temporarily disables the N3 UP tunnel in step S313 and returns a confirmation to the SMF 122 in step S314. It is noted that the SMF 122 may send PDU session modification messages to a plurality of UPFs even though a single UPF 112 is illustrated in Figure 6.
  • This temporary disablement of the communication session carried over the N3 interface between the CU-UP 126 and the UPF 112 implies that UL traffic is allowed to be sent from the CU-UP 126 to the UPF 112, while DL traffic is suspended.
  • the UPF 112 needs to trigger paging of the UE 110 by sending a Data Notification to the SMF 122.
  • step S315 the request received from the AMF 121 in step S3 11, which AMF 121 in its turn in step S316 concludes that the UE 110 indeed is set in its power-saving state.
  • Figure 7a shows a signalling diagram illustrating UL data transmission when the UE 110 exits the power-saving state according to an embodiment.
  • step S40 1 the UE 110 being in the power-saving state determines that it is has uplink data to send and consequently engages in a Random Access procedure in step S402 with the CU-CP 125.
  • a connection is established between the UE 110 and the CU-CP 125 throughout steps S403-S405.
  • the UE 110 transmits the previously stored CU-UP identifier and the identifier of the UE user plane context in the CU-UP(s) (see step S2 l4b in Figure 5) to the CU-CP 125 in step S405 along with the data to be transmitted in a UL direction.
  • the UE 110 selects in step S405a the CU-UP identifier and the identifier of the UE user plane context associated with the PDU Session for which the uplink data is to be sent and uses it in the following steps.
  • both the data and the CU-UP identifier are forwarded to the CU-CP 125 which selects the CU-UP 126 based on the CU-UP identifier in step S406 and then forwards the data and the identifier for the UE user plane context associated with the PDU Session for which the UL data is sent to the CU-UP 126 in step S407,.
  • the CU-CP 125 enables the uplink data transmission directly from the DU 127 to the CU-UP 126, i.e. the uplink data is not transmitted via the CU-CP 125.
  • the CU-CP 125 becomes aware of the DU 127 currently used for the UE 110 as part of the initial communication, i.e. a DU address becomes known in the CU-CP 125.
  • the DU 127 buffers the data in the UL while waiting for a user plane association be created with the correct CU-UP 126.
  • the DU 127 may indicate a specific DU UE context identifier for uplink transmission to the CU-CP 125.
  • the UE 110 sends the CU-UP identifier and the identifier for the UE user plane context associated with the PDU Session for which the UL data is sent to the CU-CP 125.
  • the CU-CP 125 determines based on the CU-UP identifier which CU-UP 126 should be used in step S406 and enables the DU 127 (over the Fl-C interface) to forward the uplink data to the correct CU-UP 126 serving the PDU session of the UE 110.
  • the CU-UP 125 enabling the forwarding of uplink data by the DU 127 can be realized in different ways.
  • the CU-CP 125 informs the CU-UP 126 about the DU address, the specific DU UE context identifier for uplink transmission and the identifier for the UE user plane context associated with the PDU Session for which the UL data is sent.
  • the CU-UP 126 enables the uplink
  • the DU 127 uses the established user plane association to forward the uplink data to the CU- UP 126.
  • the CU-CP 125 informs the DU 127 about the CU-UP identifier and the identifier for the UE user plane context associated with the PDU Session in the CU-UP 125 identified by the CU-UP identifier.
  • the DU 127 enables the uplink transmission by establishing a user plane association with the CU-UP 126 identified by the CU-UP identifier and using the identifier for the UE user plane context associated with the PDU Session in the CU-UP 125 to create the user plane association.
  • the DU 127 uses the established user plane association to forward the uplink data to the CU-UP 126.
  • the CU-CP 126 may also activate an Fl-U tunnel between the DU 127 and the designated CU-UP 126 for transporting the UL data.
  • the uplink data transmission is enabled directly from the DU 127 to the CU-UP 126, i.e. the CU-CP 125 is not involved.
  • the UE 110 being in the power-saving state determines that it is has uplink data to send and consequently engages in a Random Access procedure in step S402’ with the DU 127.
  • a connection is established between the UE 110 and the DU 127 throughout steps S403’-S405’.
  • the UE 110 sends the CU-UP identifier and the identifier for the UE user plane context associated with the PDU Session for which the UL data is sent to the DU 127 in step S405’, wherein the DU 127 selects the CU-UP 126 based on the CU-UP identifier in step S406’ in line with what has previously been described.
  • the DU 127 enables the uplink transmission by establishing a user plane association with the CU-UP 126 identified by the CU-UP identifier and using the identifier for the UE user plane context associated with the PDU Session in the CU-UP 125 to create the user plane association.
  • the DU 127 uses the established user plane association to forward in step S407’ the uplink data and the identifier for the UE user plane context associated with the PDU Session for which the UL data is sent to the CU-UP 126, .
  • the CU-UP 126 when the CU-UP 126 receives the UL data, it may optionally verify the authenticity of the UE 110 and/ or the UL data based on the stored UE security context (in case such security context is included) in step S408. If the authentication is successful, the CU-UP 126 will forward the data to the UPF 112 managing the PDU session carrying the UL data of the UE 110 in step S409.
  • step S410 the UE 110 returns to the power-saving state, and any UE control plane context held in the CU-CP 125 is released, while any UE user plane context held in the CU-CP 126 is maintained, as previously described.
  • the UE 110 may remain in a semi-connected state (i.e. RRC_CONNECTED and CM-IDLE) for a time period, for instance to await further UL data or any DL data (since the UE 110 currently is not in its power-saving state and DL data transmissions thus are allowed over the N3 interface).
  • a semi-connected state i.e. RRC_CONNECTED and CM-IDLE
  • the UPF 112 will forward any DL data to the CU-UP 126 which in it turn will forward the DL data to the UE llo via DU 127. This means that the UPF 112 activates the temporarily disabled UP tunnel in a DL direction based on the UL data received on that UP tunnel.
  • the UE 110 returns to the power saving state in accordance with what has previously been described; again, the CU-CP 125 releases the UE control plane context, while the CU-UP 126 is instructed to maintain the UE user plane context. This may be triggered by an inactivity timer (with or without RAN-to-UE signalling). It may be envisaged that the UPF 112 detects that no DL data arrives within the time period and that the UPF 112 signals this over the N3 interface to the CU-UP 126 which in its turn accordingly informs the CU-CP 125. Another alternative is that either the CU-UP 126 or the DU 127 detect that no DL data arrives within the time period and inform the CU-CP 125.
  • the UPF 112 again sets the UP tunnel(s) carried over the N3 interface in the temporarily disabled state when the inactivity timer expires and thus stops forwarding DL data to the CU-UP 126 (and instead initiates paging or data notification procedure if DL data arrives as will be described in the following with reference to Figure 8).
  • the indication to the UPF 112 to set the UP tunnel over N3 in temporarily disabled state is sent from the CU-UP 126 to the UPF over the N3 interface.
  • Figure 8 shows a signalling diagram illustrating DL data reception at the UE 110 upon the UE 110 exiting the power-saving state.
  • the UPF 112 receives an indication that DL data should be transmitted to the UE 110 for a PDU session with a temporarily disabled N3 communication session, which UE-terminated traffic triggers a Data
  • Notification to be sent from the UPF 112 to the SMF 122 in step S502 (which confirms the Data Notification in in step S503) and the SMF 122 further forwards a message to the AMF 121 in step S504 that the UE 110 should be paged, which AMF 121 confirms the received message in step s505.
  • the AMF 121 triggers paging (step S506) of the UE 110 via the CU-CP 125 (step S507).
  • the AMF 121 includes in the paging message the PDU Session ID for the PDU session for which the downlink data was received for. This is enabled by the UPF and/ or SMF informing the AMF about the PDU Session ID in steps S502 and S504.
  • step S508 the UE 110 being in the power-saving state detects that it is being paged and consequently exits the power-saving state and engages in a Random Access procedure in step S508 with the CU-CP 125 which is followed by a connection being established between the UE 110 and the CU-CP 125 in steps S509-S511.
  • step S510 is similar to that in the prior art.
  • the UE 110 upon the UE 110 exiting the power saving- state and establishing a connection with the CU-CP 125, the UE 110 selects the previously stored CU-UP identifier (see step S2 l4b in Figure 5), and an identifier for each individual UE user plane context associated with the ongoing PDU sessions, in step S5 lla and transmits the selected identifiers to the CU-CP 125 in step S511.
  • the paging message of step S506 included the PDU Session ID for the PDU session for which the downlink data was received for and the UE 110 selects the CU-UP identifier and identifier for the UE user plane context based on the PDU Session ID.
  • step S512 the CU-CP 125 selects the appropriate CU-UP 126 based on the received CU-UP identifier and then sends an instruction in the step S513 to resume/ activate the temporarily disabled PDU session and the
  • this instruction may include an identifier of the UE user plane context associated with the PDU Session that was indicated in the paging message, and that this session should be resumed for DL traffic.
  • the UE 110 stores multiple CU-UP identifiers for different PDU sessions, the UE 110 selects the CU-UP identifier associated with the PDU Session to be resumed for transporting the DL data.
  • step S514 the CU-UP 126 will thus identify the PDU session to be resumed (and consequently acquire the stored UE user plane context for the particular PDU session to be resumed), as informed by the CU-CP 125 based on the CU- UP identifier in step S513.
  • the CU-UP 126 sends a request in step S515 to the UPF 112 to resume the identified suspended PDU session, wherein the DL data is sent towards the UE 110 in step S516 over the resumed UP tunnel over the N3 interface.
  • an identifier of the UE user plane context associated with each PDU Session may further be sent to the CU-UP 126 in step S513. If so, the CU-UP 126 identifies the PDU session(s) to be resumed and the UPF 112 with which the session was held. Accordingly, the
  • step S517 the UE 110 returns to the power-saving state, and any UE control plane context held in the CU-CP 125 is released, while any UE user plane context held in the CU-CP 126 is maintained, as previously described.
  • the UE 110 may remain in a semi-connected state (i.e. RRC_CONNECTED and CM-IDLE) for a time period, for instance to await further UL data or any DL data (since the UE 110 currently is not in its power-saving state and DL data transmissions thus are allowed over the N3 interface).
  • a semi-connected state i.e. RRC_CONNECTED and CM-IDLE
  • the UPF 112 will forward any DL data to the CU-UP 126 which in it turn will forward the DL data to the UE 110 via the DU 127. This means that the UPF 112 activates the temporarily disabled UP tunnel in a DL direction.
  • the UE 110 If no DL data arrives within the time period (potentially detected by the UPF 112, DU 127 or CU-UP 126 as previously discussed), the UE 110 returns to the power-saving state in accordance with what has previously been described; again, the CU-CP 125 releases the UE control plane context, while the CU-UP 126 is instructed to maintain the UE user plane context. This may be triggered by an inactivity timer (with or without RAN-to-UE signalling). Even though not shown in Figure 8 , the AMF 121 is generally informed that the paging is successful and thus can cease. The indication to the AMF 121 about the successful paging can be performed in different ways either from the UE 110 on NAS layer, from the CU-CP 125 or from the UPF 112.
  • the UE 110 can send a NAS-level indication about successful paging to the AMF 121.
  • the CU-CP 125 can also inform the AMF about the successful paging e.g. by including a Serving Temporary Mobile Subscriber Identity (S-TMSI) of the UE 110 in a connection-less NG-C/ N3 message.
  • S-TMSI Serving Temporary Mobile Subscriber Identity
  • the UPF 112 can also inform the SMF 122 about the successful resume/ activation of the PDU session over the UP tunnel and the SMF 122 can forward this information to the AMF 121 to indicate successful paging.
  • Figure 9 shows an embodiment, where a change of CU-UP from a first CU-UP l26a to a second CU-UP l26b occurs for any of the PDU sessions, for instance due to UE mobility.
  • the CU-CP 125 decides in step S60 1 that of change of CU-UP is to be performed and sends a request accordingly to the second CU-UP 126 in step S602, which acknowledges the request in step S603.
  • the CU-UP 125 informs the AMF 121 about the CU-UP change in step S604, wherein the AMF 121 informs the SMF 122 in step S605, which in its turn informs the UPF 112 of the CU-UP change in step S606.
  • the UPF 112 updates the DL addresses for the user plane tunnel as a result of the CU-UP change.
  • the CU-CP 125 informs the UE 110 of the CU-UP by sending the CU-UP identifier of the second CU-UP l26b in step S608 a, also including the identifier for the UE user plane context associated with the PDU Session.
  • the UE 110 stores the CU-UP identifier of the second CU-UP l26b, and the identifier for the UE user plane context associated with the PDU Session in step S608b for subsequent use, as has been discussed in detail hereinabove, whereupon the CU-CP 125 releases the first CU-UP l26a in step S609.
  • the CU-UP 126 is located as an individual functional entity in the NG-RAN, while the UPF 112 is located as an individual functional entity in the 5GC.
  • CRC-UPF Combined RAN and CN User Plane Function 128
  • CRC-UPF Combined RAN and CN User Plane Function 128
  • the tunnelled interface of the CRC-UPF 128 passes over the El, N2 and Nll interfaces.
  • This interface passing over E1-N2-N11 is“tunnelled” in the sense that a so called transparent data container is prepared at the SMF 122 and sent over the tunnelled interface via the AMF 121 and the CU-CP 125 which just forward the data container to the CRC-UPF being the final destination (which principle also applies for the opposite direction).
  • the AMF 121 and the CU-CP 125 do not process the data included in the container, but merely relay the data container to the UPF part of the CRC-UPF 128.
  • the main benefit with a CRC-UPF 128 is to reduce user plane latency and minimize the number of interfaces between control and user plane functions.
  • the combined user plane function also results in the removal of the user plane tunnel between the UPF 112 in 5GC and the CU-UP 126 in NG-RAN, as the N3 interface becomes an internal interface in the combined user plane function allowing different implementations.
  • the above described embodiments are applicable to such CRC-UPF, with the following additions : a.
  • the CU-UP identifier identifies both the CU-UP and the UPF in the CRC-UPF.
  • the identifier for the UE user plane context associated with the PDU Session identifies UE user plane context for both the CU-UP and the UPF.
  • the temporarily disabled user communication sessions/ UP tunnels ov3r the NG-U/ N3 interface become internal sessions/ UP tunnels for the CRC-UPF.
  • Figure 11 illustrates a CU-CP 125 according to an embodiment. The steps of the method performed by the CU-CP 125 of connecting a wireless
  • a processing unit 304 embodied in the form of one or more microprocessors arranged to execute a computer program 305 downloaded to a suitable storage volatile medium 306 associated with the microprocessor, such as a Random Access Memory (RAM), or a non-volatile storage medium such as a Flash memory or a hard disk drive.
  • the processing unit 304 is arranged to cause the CU-CP 125 to carry out the method according to embodiments when the appropriate computer program 305 comprising computer-executable instructions is downloaded to the storage medium 306 and executed by the processing unit 304.
  • the storage medium 306 may also be a computer program product comprising the computer program 305.
  • the computer program 305 may be transferred to the storage medium 306 by means of a suitable computer program product, such as a Digital Versatile Disc (DVD) or a memory stick.
  • a suitable computer program product such as a Digital Versatile Disc (DVD) or a memory stick.
  • the computer program 305 may be downloaded to the storage medium 306 over a network.
  • the processing unit 304 may alternatively be embodied in the form of a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), etc.
  • Figure 12 illustrates a CU-UP 126 according to an embodiment. The steps of the method performed by the CU-UP 126 of connecting a wireless
  • a processing unit 404 embodied in the form of one or more microprocessors arranged to execute a computer program 405 downloaded to a suitable storage volatile medium 406 associated with the microprocessor, such as a RAM, or a non-volatile storage medium such as a Flash memory or a hard disk drive.
  • the processing unit 404 is arranged to cause the CU-UP 126 to carry out the method according to embodiments when the appropriate computer program 405 comprising computer-executable instructions is downloaded to the storage medium 406 and executed by the processing unit 404.
  • the storage medium 406 may also be a computer program product comprising the computer program 405.
  • the computer program 405 may be transferred to the storage medium 406 by means of a suitable computer program product, such as a DVD or a memory stick.
  • the computer program 405 may be downloaded to the storage medium 406 over a network.
  • the processing unit 404 may alternatively be embodied in the form of a DSP, an ASIC, an FPGA, a CPLD, etc.
  • Figure 13 illustrates a wireless communication device 110 according to an embodiment. The steps of the method performed by the wireless
  • a processing unit 504 embodied in the form of one or more microprocessors arranged to execute a computer program 505 downloaded to a suitable storage volatile medium 506 associated with the microprocessor, such as a RAM, or a non volatile storage medium such as a Flash memory or a hard disk drive.
  • the processing unit 504 is arranged to cause the wireless communication device 110 to carry out the method according to embodiments when the appropriate computer program 505 comprising computer-executable instructions is downloaded to the storage medium 506 and executed by the processing unit 504.
  • the storage medium 506 may also be a computer program product comprising the computer program 505.
  • the computer program 505 may be transferred to the storage medium 506 by means of a suitable computer program product, such as a DVD or a memory stick.
  • the computer program 505 may be downloaded to the storage medium 506 over a network.
  • the processing unit 504 may alternatively be embodied in the form of a DSP, an ASIC, an FPGA, a CPLD, etc.
  • FIG 14 illustrates a UPF 112 according to an embodiment.
  • the steps of the method performed by the UPF 112 according to embodiments are in practice performed by a processing unit 604 embodied in the form of one or more microprocessors arranged to execute a computer program 605 downloaded to a suitable storage volatile medium 606 associated with the microprocessor, such as a RAM, or a non-volatile storage medium such as a Flash memory or a hard disk drive.
  • the processing unit 604 is arranged to cause the UPF 112 to carry out the method according to embodiments when the appropriate computer program 605 comprising computer-executable instructions is downloaded to the storage medium 606 and executed by the processing unit 604.
  • the storage medium 606 may also be a computer program product comprising the computer program 605.
  • the computer program 605 may be transferred to the storage medium 606 by means of a suitable computer program product, such as a DVD or a memory stick.
  • the computer program 605 may be downloaded to the storage medium 606 over a network.
  • the processing unit 604 may alternatively be embodied in the form of a DSP, an ASIC, an FPGA, a CPLD, etc.
  • FIG 15 illustrates a DU 127 according to an embodiment.
  • the steps of the method performed by the DU 127 according to embodiments are in practice performed by a processing unit 704 embodied in the form of one or more microprocessors arranged to execute a computer program 705 downloaded to a suitable storage volatile medium 706 associated with the microprocessor, such as a RAM, or a non-volatile storage medium such as a Flash memory or a hard disk drive.
  • the processing unit 704 is arranged to cause the DU 127 to carry out the method according to embodiments when the appropriate computer program 705 comprising computer-executable instructions is downloaded to the storage medium 706 and executed by the processing unit 704.
  • the storage medium 706 may also be a computer program product comprising the computer program 705.
  • the computer program 705 may be transferred to the storage medium 706 by means of a suitable computer program product, such as a DVD or a memory stick.
  • the computer program 705 may be downloaded to the storage medium 706 over a network.
  • the processing unit 704 may alternatively be embodied in the form of a DSP, an ASIC, an FPGA, a CPLD, etc.

Landscapes

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

Abstract

L'invention concerne des procédés et des dispositifs de connexion d'un dispositif de communication sans fil (110) à un réseau de communication (100). Selon un aspect, l'invention porte sur un procédé mis en œuvre par un nœud de réseau (125) qui fournit une fonctionnalité de plan de commande de réseau d'accès radio (RAN) dans un réseau de communication sans fil (100), le nœud de réseau (125) étant configuré pour connecter un dispositif de communication sans fil (110) à un plan de commande du réseau de communication sans fil (100). Le procédé consiste à ordonner à au moins un nœud de réseau fournissant une fonctionnalité de plan utilisateur de RAN dans le réseau de communication sans fil de maintenir un contexte de plan utilisateur d'équipement utilisateur (UE) lors du passage du dispositif de communication sans fil (110) dans un état d'économie d'énergie, et à libérer (S310) un contexte de plan de commande d'UE au niveau dudit nœud de réseau (125) qui fournit une fonctionnalité de plan de commande de RAN lors du passage du dispositif de communication sans fil (110) dans l'état d'économie d'énergie.
PCT/SE2018/051095 2018-10-26 2018-10-26 Solutions pour permettre une transmission de données à faible surdébit pour dispositifs cellulaires WO2020085964A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2018/051095 WO2020085964A1 (fr) 2018-10-26 2018-10-26 Solutions pour permettre une transmission de données à faible surdébit pour dispositifs cellulaires

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2018/051095 WO2020085964A1 (fr) 2018-10-26 2018-10-26 Solutions pour permettre une transmission de données à faible surdébit pour dispositifs cellulaires

Publications (1)

Publication Number Publication Date
WO2020085964A1 true WO2020085964A1 (fr) 2020-04-30

Family

ID=64267882

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2018/051095 WO2020085964A1 (fr) 2018-10-26 2018-10-26 Solutions pour permettre une transmission de données à faible surdébit pour dispositifs cellulaires

Country Status (1)

Country Link
WO (1) WO2020085964A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022045735A1 (fr) * 2020-08-24 2022-03-03 에스케이텔레콤 주식회사 Dispositif de réseau et procédé par lequel un dispositif transmet des informations de localisation de terminal
US20220256392A1 (en) * 2019-10-31 2022-08-11 Huawei Technologies Co., Ltd. Communication method and device
WO2024000191A1 (fr) * 2022-06-28 2024-01-04 Apple Inc. Architecture de réseau et conception sans état pour un réseau cellulaire

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160345261A1 (en) * 2014-10-28 2016-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes, a user equipment and methods therein for handling a connection between the user equipment and a wireless communications network
EP3340731A1 (fr) * 2015-08-17 2018-06-27 NTT DoCoMo, Inc. Système de communication sans fil, station de base sans fil, entité de gestion de mobilité, dispositif utilisateur, et procédé de commande de communication
US20180234838A1 (en) * 2016-05-20 2018-08-16 Telefonaktiebolaget Lm Ericsson (Publ) Storage of ue contexts in ran for inactive ues

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160345261A1 (en) * 2014-10-28 2016-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes, a user equipment and methods therein for handling a connection between the user equipment and a wireless communications network
EP3340731A1 (fr) * 2015-08-17 2018-06-27 NTT DoCoMo, Inc. Système de communication sans fil, station de base sans fil, entité de gestion de mobilité, dispositif utilisateur, et procédé de commande de communication
US20180234838A1 (en) * 2016-05-20 2018-08-16 Telefonaktiebolaget Lm Ericsson (Publ) Storage of ue contexts in ran for inactive ues

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220256392A1 (en) * 2019-10-31 2022-08-11 Huawei Technologies Co., Ltd. Communication method and device
WO2022045735A1 (fr) * 2020-08-24 2022-03-03 에스케이텔레콤 주식회사 Dispositif de réseau et procédé par lequel un dispositif transmet des informations de localisation de terminal
WO2024000191A1 (fr) * 2022-06-28 2024-01-04 Apple Inc. Architecture de réseau et conception sans état pour un réseau cellulaire

Similar Documents

Publication Publication Date Title
US11690130B2 (en) Network initiated release assistance information
EP3777280B1 (fr) Vérification de sécurité pour le cas d'une reprise d'une connection rrc
US12101740B2 (en) Signaling delivery in a wireless network
US11838891B2 (en) Paging of idle state wireless communication devices
WO2020085964A1 (fr) Solutions pour permettre une transmission de données à faible surdébit pour dispositifs cellulaires
US20240340995A1 (en) Communicating early and non-early data between a user device and a core network
WO2023154401A1 (fr) Gestion des configurations radio pour la transmission de petites données
WO2023154332A1 (fr) Gestion de transmission de petites données avec une configuration d'autorisation configurée
WO2023154445A1 (fr) Gestion de configurations radio pour un équipement utilisateur
WO2023009691A2 (fr) Gestion de mesures d'ue dans un état de repos ou inactif
US20230413372A1 (en) Early data communication with preconfigured resources
US20240022903A1 (en) Early data communication in an inactive state
WO2020197454A1 (fr) Radiomessagerie de dispositifs de communication sans fil à l'état inactif
US20240244700A1 (en) Early Data Communication on Bandwidth Parts
US20240155726A1 (en) Managing data communication in a distributed base station
US20240306248A1 (en) Managing an early data communication configuration
US20230379830A1 (en) Base station handling of transitioning wireless device to inactive state
WO2023133334A2 (fr) Gestion de contrôle d'accès dans une transmission de petites quantités de données
EP4454399A2 (fr) Gestion de contrôle d'accès dans une transmission de petites quantités de données
WO2023133335A1 (fr) Gestion de communication d'informations de système dans transmission de petites données
EP4454391A2 (fr) Gestion de mesure dans une transmission de petites quantités de données
WO2023163996A1 (fr) Retardement de demandes pour une transmission de petites données associée à des ressources
EP4454346A1 (fr) Gestion de communication d'informations de système dans transmission de petites données
WO2023133333A2 (fr) Gestion de mesure dans une transmission de petites quantités de données
WO2023196486A1 (fr) Gestion de transmission de petites données avec un réseau

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

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

Country of ref document: EP

Kind code of ref document: A1