WO2024057075A1 - Systèmes et procédés permettant une configuration d'ue adaptative lors d'un transfert entrant sur la base d'un ou de plusieurs services entrants - Google Patents

Systèmes et procédés permettant une configuration d'ue adaptative lors d'un transfert entrant sur la base d'un ou de plusieurs services entrants Download PDF

Info

Publication number
WO2024057075A1
WO2024057075A1 PCT/IB2022/058781 IB2022058781W WO2024057075A1 WO 2024057075 A1 WO2024057075 A1 WO 2024057075A1 IB 2022058781 W IB2022058781 W IB 2022058781W WO 2024057075 A1 WO2024057075 A1 WO 2024057075A1
Authority
WO
WIPO (PCT)
Prior art keywords
ran node
handover
node
ran
cell
Prior art date
Application number
PCT/IB2022/058781
Other languages
English (en)
Inventor
Mateusz PRZETOCKI
Christer Gustafsson
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/IB2022/058781 priority Critical patent/WO2024057075A1/fr
Publication of WO2024057075A1 publication Critical patent/WO2024057075A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters

Definitions

  • the present disclosure relates to service-triggered handover in a cellular communications system.
  • Japanese telecom operators are regulated to run VoLTE services on Frequency Division Duplexing (FDD) frequency bands. Therefore, when a UE establishes VoLTE service in Time Division Duplexing (TDD) frequency band, the evolved NodeB (eNB) initiates a handover towards the FDD frequency bands.
  • TDD Time Division Duplexing
  • eNB evolved NodeB
  • Another specific example is starting a voice service for a UE located at or near the cell edge. In this example, at call setup, handover may be initiated to move the UE to more stable carrier.
  • MC Mission Critical
  • a method performed by a first Radio Access Network (RAN) node comprises receiving a setup request that requests setup of a service bearer for one or more incoming services for a UE and determining, based on the setup request, that a triggering condition for a handover of the UE from a first cell operated by the first RAN node to a second cell operated by a second RAN node has occurred.
  • RAN Radio Access Network
  • the method further comprises, responsive to determining that the triggering condition for the handover has occurred, sending a handover request to the second RAN node to request handover of the UE to the second cell operated by the second RAN node, the handover request comprising information about the one or more incoming services.
  • the incoming service(s) can be setup without disruption.
  • the first RAN node and the second RAN node are separate RAN nodes. In another embodiment, the first RAN node and the second RAN node are a same RAN node.
  • sending the handover request to the second RAN node comprises either sending the handover request to the second RAN node via an interface between the first RAN node and the second RAN node or sending the handover request to the second RAN node via a core network node.
  • the handover is either an inter-frequency handover with a same Radio Access Technology (RAT) or an inter-RAT handover.
  • RAT Radio Access Technology
  • the triggering condition is a rejection of the request to setup the service bearer for the one or more incoming services for the UE.
  • the one or more incoming services are one or more services from a predefined or preconfigured set of services for which a handover is required.
  • the one or more incoming services are one or more services for which a service bearer has not yet been setup for the UE in the first cell.
  • the information about the one or more incoming services comprises information that identifies or describes the one or more incoming services.
  • the information about the one or more incoming services is comprised in a source RAN node to target RAN node transparent container Information Element (IE) that is comprised in the handover request.
  • IE transparent container Information Element
  • the service bearer is a radio bearer or a Quality of Service (QoS) flow.
  • QoS Quality of Service
  • a first RAN node is adapted to receive a setup request that requests setup of a service bearer for one or more incoming services for a UE and determine, based on the setup request, that a triggering condition for a handover of the UE from a first cell operated by the first RAN node to a second cell operated by a second RAN node has occurred.
  • the first RAN node is further adapted to, responsive to determining that the triggering condition for the handover has occurred, send a handover request to the second RAN node to request handover of the UE to the second cell operated by the second RAN node, the handover request comprising information about the one or more incoming services.
  • a first RAN node comprises processing circuitry configured to cause the first RAN node to receive a setup request that requests setup of a service bearer for one or more incoming services for a UE and determine, based on the setup request, that a triggering condition for a handover of the UE from a first cell operated by the first RAN node to a second cell operated by a second RAN node has occurred.
  • the processing circuitry is further configured to cause the first RAN node to, responsive to determining that the triggering condition for the handover has occurred, send a handover request to the second RAN node to request handover of the UE to the second cell operated by the second RAN node, the handover request comprising information about the one or more incoming services.
  • a method performed by a second RAN node comprises receiving a handover request from a first RAN node that requests handover of a UE from a first cell operated by the first RAN node to a second cell operated by the second RAN node, the handover request comprising information about one or more incoming services for which the UE should be expected to receive a setup request of one or more service bearers in the second cell.
  • the method further comprises performing a set of actions related to handover of the UE to the second cell, the set of actions comprising one or more actions based on the information about the one or more incoming services.
  • the first RAN node and the second RAN node are separate RAN nodes.
  • the first RAN node and the second RAN node are a same RAN node.
  • the one or more actions based on the information about the one or more incoming services comprises optimizing configuration of the UE based on the information about the one or more incoming services.
  • the one or more actions based on the information about the one or more incoming services comprises refraining from performing radio resource control signaling for one or more features that are not needed or desired for providing the one or more incoming services for the UE.
  • the one or more actions based on the information about the one or more incoming services comprises disabling one or more features of the second cell with respect to the UE.
  • the one or more features of the second cell comprise one or more features that disturb an ability of the second cell to provide the one or more incoming services for the UE.
  • the one or more features of the second cell comprise one or more features that delay setup of a service bearer for the UE in the second cell for the one or more incoming services.
  • the one or more features of the second cell comprise carrier aggregation, dual -connectivity, or both carrier aggregation and dual-connectivity.
  • the one or more actions based on the information about the one or more incoming services comprises enabling one or more features of the second cell with respect to the UE.
  • the one or more features of the second cell comprise one or more features that are desirable in the second cell when providing the one or more incoming services for the UE.
  • the one or more features of the second cell comprise carrier aggregation, dual-connectivity, or both carrier aggregation and dual-connectivity.
  • the one or more actions based on the information about the one or more incoming services comprises applying one or more service-specific configurations for one or more features of the second cell with respect to the UE.
  • the one or more actions based on the information about the one or more incoming services comprises refraining from configuring the UE to perform one or more measurements or one or more types of measurements.
  • the one or more measurements or the one or more types of measurements comprise measurements that require measurement gaps.
  • the method further comprises starting a timer at or after receiving the handover request, determining that the timer has expired before a setup request for one or more service bearers for the one or more incoming services has been received, and restoring a default configuration responsive to determining that the timer has expired before a setup request for one or more service bearers for the one or more incoming services has been received.
  • the handover is either an inter-frequency handover with a same RAT or an inter-RAT handover.
  • the one or more incoming services are one or more services from a predefined or preconfigured set of services for which a handover is required.
  • the one or more incoming services are one or more services for which a service bearer has not yet been setup for the UE in the first cell.
  • the information about the one or more incoming services comprises information that identifies or describes the one or more incoming services.
  • the information about the one or more incoming services is comprised in a source RAN node to target RAN node transparent container IE that is comprised in the handover request.
  • a second RAN node is adapted to receive a handover request from a first RAN node that requests handover of a UE from a first cell operated by the first RAN node to a second cell operated by the second RAN node, the handover request comprising information about one or more incoming services for which the UE should be expected to receive a setup request for one or more service bearers in the second cell.
  • the second RAN node is further adapted to perform a set of actions related to handover of the UE to the second cell, the set of actions comprising one or more actions based on the information about the one or more incoming services.
  • a second RAN node comprises processing circuitry configured to cause the second RAN node to receive a handover request from a first RAN node that requests handover of a UE from a first cell operated by the first RAN node to a second cell operated by the second RAN node, the handover request comprising information about one or more incoming services for which the UE should be expected to receive a setup request for one or more service bearers in the second cell.
  • the processing circuitry is further configured to cause the second RAN node to perform a set of actions related to handover of the UE to the second cell, the set of actions comprising one or more actions based on the information about the one or more incoming services.
  • Figure 1 illustrates one example of a cellular communications system in which embodiments of the present disclosure may be implemented
  • Figures 2A and 2B illustrate a procedure in which information about an incoming service(s) is provided to the target cell during a handover in accordance with one embodiment of the present disclosure
  • Figure 3 is a schematic block diagram of a network node according to some embodiments of the present disclosure.
  • Figure 4 is a schematic block diagram that illustrates a virtualized embodiment of the network node of Figure 3 according to some embodiments of the present disclosure
  • Figure 5 is a schematic block diagram of the network node of Figure 3 according to some other embodiments of the present disclosure.
  • FIG. 6 is a schematic block diagram of a User Equipment device (UE) according to some embodiments of the present disclosure
  • Figure 7 is a schematic block diagram of the UE of Figure 6 according to some other embodiments of the present disclosure.
  • Figure 8 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments of the present disclosure
  • Figure 9 is a generalized block diagram of a host computer communicating via a base station with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure
  • Figure 10 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment of the present disclosure
  • Figure 11 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment of the present disclosure
  • Figure 12 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment of the present disclosure
  • Figure 13 is a flowchart illustrating a method implemented in a communication system in accordance with one embodiment of the present disclosure.
  • Radio Node As used herein, a "radio node” is either a radio access node or a wireless communication device.
  • Radio Access Node As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN Radio Access Network
  • a radio access node examples include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 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), a relay node, a network node that implements part of the functionality of a base station or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.
  • a base station e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B
  • Core Network Node is any type of node in a core network or any node that implements a core network function.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like.
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • SCEF Service Capability Exposure Function
  • HSS Home Subscriber Server
  • a core network node examples include a node implementing an Access and Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.
  • AMF Access and Mobility Function
  • UPF User Plane Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • NSSF Network Slice Selection Function
  • NEF Network Exposure Function
  • NRF Network Exposure Function
  • NRF Network Exposure Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • Communication Device is any type of device that has access to an access network.
  • Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC).
  • the communication device may be a portable, hand-held, computer-comprised, or vehiclemounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.
  • Wireless Communication Device One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network).
  • a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device.
  • UE User Equipment
  • MTC Machine Type Communication
  • LoT Internet of Things
  • Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC.
  • the wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.
  • Network Node As used herein, a "network node” is any node that is either part of the RAN or the core network of a cellular communications network/system. [0054] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.
  • a RAN node may configure Carrier Aggregation (CA), Dual Connectivity (e.g., Evolved Universal Terrestrial Radio Access (EUTRA)/New Radio (NR) Dual Connectivity (EN-DC)), or another service-disturbing feature for a UE.
  • CA Carrier Aggregation
  • EUTRA Evolved Universal Terrestrial Radio Access
  • NR New Radio
  • EN-DC Dual Connectivity
  • a dedicated bearer request arrives at the RAN node for an incoming service (e.g., a service that triggered the handover), and several of these configured features may need to be de-configured, e.g., as per non-disturbing service policy.
  • a "service-disturbing feature” is a RAN feature (e.g., CA, DU, Discontinuous Reception (DRX), or the like) that is desired or required (e.g., via a defined or configured policy) to be disabled for a particular service.
  • a voice service e.g., a Voice over LTE (VoLTE) or Voice over NR (VoNR) service
  • MC Mission Critical
  • multiple UE re-configurations may need to be performed where these multiple UE re-configurations extend setup time for the voice call or affect voice retainability and may also potential causing the voice call to be dropped.
  • a RAN node that serves a source cell of the handover sends, to a RAN node that serves a target cell of the handover, information about the incoming service(s) or service set.
  • an "incoming service” is a service that has not yet been established for the UE in the source cell, but has been requested for the UE in the source cell.
  • the information about the incoming service(s) is used to perform one or more actions such as, e.g., optimizing UE configurations of the UE for the incoming service(s).
  • Embodiments of the present disclosure may provide any one or more of the following advantages.
  • Embodiments of the present disclosure may provide faster voice setup with less disruption from, for example, Mobile Broadband (MBB) services configuration.
  • Embodiments of the present disclosure may make voice calls more stable and reliable.
  • Embodiments of the present disclosure may allow having a robust, service-adaptive configuration that is best suited for UE services at the particular moment.
  • Embodiments of the present disclosure may be applicable to various types of incoming services such as, e.g., voice, MC (e.g., MC Push to Talk (PTT)), and/or Time-Critical Communication (TCC) services.
  • voice e.g., voice
  • MC e.g., MC Push to Talk (PTT)
  • TCP Time-Critical Communication
  • FIG. 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented.
  • the cellular communications system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC), an Evolved Packet System (EPS) including an Evolved Universal Terrestrial RAN (E-UTRAN) and an Evolved Packet Core (EPC), a combination thereof.
  • 5GS 5G system
  • NG-RAN Next Generation RAN
  • 5GC 5G Core
  • EPS Evolved Packet System
  • E-UTRAN Evolved Universal Terrestrial RAN
  • EPC Evolved Packet Core
  • the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC) and in the EPS include eNBs, controlling corresponding (macro) cells 104-1 and 104-2.
  • the base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102.
  • the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104.
  • the RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4.
  • the low power nodes 106-1 through 106-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like. Notably, while not illustrated, one or more of the small cells 108-1 through 108-4 may alternatively be provided by the base stations 102.
  • the low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106.
  • the small cells 108-1 through 108-4 are generally referred to herein collectively as small cells 108 and individually as small cell 108.
  • the cellular communications system 100 also includes a core network 110, which in the 5G System (5GS) is referred to as the 5GC.
  • the base stations 102 (and optionally the low power nodes 106) are connected to the core network 110.
  • the base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108.
  • the wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112.
  • the wireless communication devices 112 are oftentimes UEs and as such are sometimes referred to herein as UEs 112, but the present disclosure is not limited thereto.
  • FIGS 2A and 2B illustrate a procedure in which information about an incoming service(s) is provided to the target cell during a handover in accordance with one embodiment of the present disclosure. As illustrated, this procedure involves a UE 200, a target RAN node 202, a source RAN node 204, and a network node 206.
  • the UE 200 may, for example, correspond to one of the wireless communication devices 112 of Figure 1, the target RAN node 202 may correspond to one of the base stations 102 of Figure 1 or alternatively a RAN node (e.g., a gNB-DU) that performs some of the functionality of a base station 102, and the source RAN node 204 may also correspond to one of the base stations 102 of Figure 1 or alternatively a RAN node (e.g., gNB-DU) that performs some of the functionality of a base station 102.
  • the network node 206 may be, for example, a core network node in the core network 110 of Figure 1 such as, e.g., an MME or AMF. It should also be noted that, in one embodiment, the source RAN node 204 and the target RAN node 202 are separate (i.e., different) RAN nodes.
  • the source RAN node 204 and the target RAN node 202 are the same RAN node (e.g., in the case of the source cell and target cell being operated by the same RAN node, in which case the handover described below is internal to that RAN node).
  • the network node 206 sends, to the source RAN node 204, a setup request for one or more incoming services for the UE 200 (step 208).
  • the incoming service(s) are services not yet established for the UE 200 in a source cell operated by the source RAN node 204.
  • the setup request of step 208 is a request to setup a service bearer(s) (e.g., a radio bearer(s) or Quality of Service (QoS) flow(s)) for the incoming service(s).
  • a service bearer(s) e.g., a radio bearer(s) or Quality of Service (QoS) flow(s)
  • the source RAN node 204 determines that a trigger condition for a service-triggered handover has occurred, based on the setup request (step 210).
  • the trigger condition for the service-triggered handover is a condition that a handover to a different cell (e.g., different cell on the same frequency, different cell on a different frequency, different cell of the same RAT, different cell of a different RAT, or the like) is required for any of a predefined or configured set of incoming services.
  • This set of incoming services may include, for example, VoLTE, VoNR, MC service, or the like.
  • the set of incoming services may be identified by a set of respective identifiers such as, e.g., a set of 5 th Generation (5G) QoS Indicators (5QIs) or a set of QoS Class Identifiers (QCIs), or the like.
  • the source RAN node 204 sends, to the network node 106, a reject message that indicates the setup request is rejected (step 211).
  • the reject message may include a flag or cause indicator that indicates that the rejection is due to handover.
  • the trigger condition for the service-triggered handover is the rejection of the setup request, e.g., with a cause being that a handover is needed or desired, e.g., due to the associated incoming service(s).
  • the source RAN node 204 sends, to the target RAN node 202 that operates a target cell for the handover, a handover request (step 212).
  • the handover request includes information about the incoming service(s) such as, e.g., information that identifies or describes the incoming service(s).
  • the information about the incoming service(s) may include one or more predefined or configured values that identify the incoming service(s).
  • the information about the incoming service(s) may include information that describes the incoming service(s) such as, e.g., a QCI or 5QI.
  • the information about the incoming service(s) is included within an information element (IE) within the handover request.
  • This information element may be, for example, a Source to Target Transparent Container IE.
  • the handover may, depending on the particular embodiment, be an inter-frequency handover where the target cell is on a different frequency than the source cell, an intra -frequency handover where the target cell is on a same frequency of the source cell, an intra-Radio Access Technology (RAT) handover where the target cell and source cell are of the same RAT, or an inter-RAT handover where the target cell and the source cell are of different RATs.
  • RAT Radio Access Technology
  • the source RAN node 204 may perform action(s) related to the handover prior to step 212 such as, e.g., scheduling measurements for the UE 200 so that the UE 200 can find a suitable target cell and report it to the source RAN node 204.
  • action(s) related to the handover such as, e.g., scheduling measurements for the UE 200 so that the UE 200 can find a suitable target cell and report it to the source RAN node 204.
  • such measurements may not be needed, e.g., if the source RAN node 204 can perform a blind handover.
  • these actions are well-known in the art and, as such, not shown in Figure 2A for conciseness.
  • the target RAN node 202 responds with a handover request acknowledgment (step 214).
  • the source RAN node 204 sends a Radio Resource Control (RRC) reconfiguration and handover command to the UE 200 (step 216).
  • RRC Radio Resource Control
  • the UE 200 processes the RRC reconfiguration and handover command and responds to the source RAN node 204 with an RRC reconfiguration complete message (step 218).
  • the handover procedure is then continued, e.g., in the conventional manner defined in 3GPP specifications (step 220).
  • the target RAN node 202 optionally starts a timer (step 222).
  • the timer may be initialized to a predefined or configured amount of time.
  • the target RAN node 202 also performs a set of actions including one or more actions based on the information about the incoming service(s) included in the handover request of step 212 (step 224).
  • the one or actions of step 224 are performed based on the information about the incoming service(s) prior to any setup request for the incoming service(s) is received by the target RAN node 202 for the UE 200.
  • the one or more actions include one or more actions to optimize configuration of the UE 200 to support the incoming service(s) (e.g., optimize for a certain incoming service or a certain combination of incoming services) (step 224A).
  • This optimization may include, for example:
  • the disabled feature(s) may include any feature(s) of the target RAN node 202 that are undesirable for (e.g., disturb) the incoming service(s).
  • Such features may be any features that delay setup of a service bearer(s) for the incoming service(s).
  • the disabled feature(s) may include, e.g., Carrier Aggregation (CA), Dual Connectivity (DC), Discontinuous Reception (DRX), or the like.
  • the enabled feature(s) may include any feature(s) of the target RAN node 202 that are desirable or required for the incoming service(s).
  • the enabled feature(s) may include, e.g., Carrier Aggregation (CA), Dual Connectivity (DC), Discontinuous Reception (DRX), or the like.
  • the target RAN node 202 may apply a service-specific DRX configuration, a service-specific inactivity timer configuration, or the like.
  • step 224E Refraining from performing unnecessary RRC signaling (or delaying performance of such RRC signaling) (step 224E); o For example, if CA and/or DC is disabled, then the target RAN node 202 may refrain from performing RRC signaling related to CA and/or DC.
  • step 224F Refraining from configuring the UE 200 with one or more certain measurements or measurement types (or delaying configuration of the UE 200 with such measurements or measurement types) (step 224F); o For example, if CA and/or DC is disabled, then the target RAN node 202 may refrain from configuring the UE 200 to perform measurements related to CA and/or DC.
  • the UE configuration for the UE 200 is service-adaptive.
  • the target RAN node 202 may receive a setup request for the incoming services (step 226). In response to such a setup request, the target RAN node 202 stops the timer and proceeds to process the setup request for the incoming service(s) (step 228A). Conversely, if no setup request for the incoming service(s) is received before the timer expires, then, upon expiry of the timer, the target RAN node 202 restores a default UE configuration (e.g., a configuration that is not necessarily optimized for the incoming service(s)) (step 228B).
  • a default UE configuration e.g., a configuration that is not necessarily optimized for the incoming service(s)
  • the information about the incoming service(s) included in the handover request of step 212 may be in the form of an Information Element (IE).
  • this IE is a source RAN node to target RAN node transparent container that contains the information about the incoming service(s).
  • this source RAN node to target RAN node transparent container may be the source NG-RAN node to target NG-RAN node transparent container specified in 3GPP TS 38.413, but modified to further include information about the incoming service(s), which in the example below is referred to as "Incoming Service Information".
  • This IE is produced by the source NG-RAN node and is transmitted to the target NG-RAN node.
  • the IE is transmitted from the external handover source to the target NG-RAN node.
  • This IE is transparent to the 5GC. Table 1 below gives one example embodiment of this IE.
  • the new IE can additionally or alternatively be added to, as an example, the EUTRAN Source eNB to Target eNB Transparent Container IE defined in 3GPP TS 36.413.
  • the new IE Incoming Service Information can be defined as exemplified in Table 2 below.
  • the purpose of the Incoming Service IE is to indicate the Incoming Service at the Source Side.
  • the Incoming Service Information can provide information describing the service by means of QCI or 5QI.
  • 3GPP TS 38.413 and 3GPP TS 36.413 in relation to the Incoming Service Information IE usage definitions:
  • the target gNB shall if supported, save the Incoming Services information and may use it for service-suited configuration after receiving the RRC Reconfiguration Complete from the UE.
  • the target eNB shall if supported, save the Incoming Services information and may use it for service-suited configuration after receiving the RRC Connection Reconfiguration Complete from the UE.
  • FIG. 3 is a schematic block diagram of a network node 300 according to some embodiments of the present disclosure.
  • the network node 300 may be, for example, a RAN node (e.g., the target RAN node 202 or the source RAN node 204), which may be, e.g., a base station 102 or 106 or a network node that implements all or part of the functionality of the base station 102, eNB, or gNB described herein.
  • a RAN node e.g., the target RAN node 202 or the source RAN node 204
  • a base station 102 or 106 e.g., a base station 102 or 106 or a network node that implements all or part of the functionality of the base station 102, eNB, or gNB described herein.
  • the network node 300 includes a control system 302 that includes one or more processors 304 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 306, and a network interface 308.
  • the one or more processors 304 are also referred to herein as processing circuitry.
  • the network node 300 may include one or more radio units 310 that each includes one or more transmitters 312 and one or more receivers 314 coupled to one or more antennas 316.
  • the radio units 310 may be referred to or be part of radio interface circuitry.
  • the radio unit(s) 310 is external to the control system 302 and connected to the control system 302 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 310 and potentially the antenna(s) 316 are integrated together with the control system 302.
  • the one or more processors 304 operate to provide one or more functions of the network node 300 as described herein (e.g., one or more functions of the target RAN node 202 or source RAN node 204 described herein). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 306 and executed by the one or more processors 304.
  • FIG. 4 is a schematic block diagram that illustrates a virtualized embodiment of the network node 300 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes.
  • a "virtualized" network node is an implementation of the network node 300 in which at least a portion of the functionality of the network node 300 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • the network node 300 may include the control system 302 and/or the one or more radio units 310, as described above.
  • the control system 302 may be connected to the radio unit(s) 310 via, for example, an optical cable or the like.
  • the network node 300 includes one or more processing nodes 400 coupled to or included as part of a network(s) 402. If present, the control system 302 or the radio unit(s) are connected to the processing node(s) 400 via the network 402.
  • Each processing node 400 includes one or more processors 404 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 406, and a network interface 408.
  • functions 410 of the network node 300 described herein are implemented at the one or more processing nodes 400 or distributed across the one or more processing nodes 400 and the control system 302 and/or the radio unit(s) 310 in any desired manner.
  • some or all of the functions 410 of the network node 300 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) 400.
  • additional signaling or communication between the processing node(s) 400 and the control system 302 is used in order to carry out at least some of the desired functions 410.
  • the control system 302 may not be included, in which case the radio unit(s) 310 communicate directly with the processing node(s) 400 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 300 or a node (e.g., a processing node 400) implementing one or more of the functions 410 of the network node 300 in a virtual environment according to any of the embodiments described herein is provided.
  • a carrier comprising 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 5 is a schematic block diagram of the network node 300 according to some other embodiments of the present disclosure.
  • the network node 300 includes one or more modules 500, each of which is implemented in software.
  • the module(s) 500 provide the functionality of the network node 300 described herein. This discussion is equally applicable to the processing node 400 of Figure 4 where the modules 500 may be implemented at one of the processing nodes 400 or distributed across multiple processing nodes 400 and/or distributed across the processing node(s) 400 and the control system 302.
  • FIG. 6 is a schematic block diagram of a wireless communication device 112 (e.g., UE 200) according to some embodiments of the present disclosure.
  • the wireless communication device 112 includes one or more processors 602 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 604, and one or more transceivers 606 each including one or more transmitters 608 and one or more receivers 610 coupled to one or more antennas 612.
  • the transceiver(s) 606 includes radio-front end circuitry connected to the antenna(s) 612 that is configured to condition signals communicated between the antenna(s) 612 and the processor(s) 602, as will be appreciated by on of ordinary skill in the art.
  • the processors 602 are also referred to herein as processing circuitry.
  • the transceivers 606 are also referred to herein as radio circuitry.
  • the functionality of the wireless communication device 112 (or UE) described above may be fully or partially implemented in software that is, e.g., stored in the memory 604 and executed by the processor(s) 602.
  • the wireless communication device 112 may include additional components not illustrated in Figure 6 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 112 and/or allowing output of information from the wireless communication device 112), a power supply (e.g., a battery and associated power circuitry), etc.
  • user interface components e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 112 and/or allowing output of information from the wireless communication device 112
  • a power supply e.g., a battery and associated power circuitry
  • 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 communication device 112 according to any of the embodiments described herein is provided.
  • a carrier comprising 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. 7 is a schematic block diagram of the wireless communication device 112 according to some other embodiments of the present disclosure.
  • the wireless communication device 112 includes one or more modules 700, each of which is implemented in software.
  • the module(s) 700 provide the functionality of the wireless communication device 112 (or UE) described herein.
  • a communication system includes a telecommunication network 800, such as a 3GPP-type cellular network, which comprises an access network 802, such as a RAN, and a core network 804.
  • the access network 802 comprises a plurality of base stations 806A, 806B, 806C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 808A, 808B, 808C.
  • Each base station 806A, 806B, 806C is connectable to the core network 804 over a wired or wireless connection 810.
  • a first UE 812 located in coverage area 808C is configured to wirelessly connect to, or be paged by, the corresponding base station 806C.
  • a second UE 814 in coverage area 808A is wirelessly connectable to the corresponding base station 806A. While a plurality of UEs 812, 814 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 806.
  • the telecommunication network 800 is itself connected to a host computer 816, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm.
  • the host computer 816 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 818 and 820 between the telecommunication network 800 and the host computer 816 may extend directly from the core network 804 to the host computer 816 or may go via an optional intermediate network 822.
  • the intermediate network 822 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 822, if any, may be a backbone network or the Internet; in particular, the intermediate network 822 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 8 as a whole enables connectivity between the connected UEs 812, 814 and the host computer 816.
  • the connectivity may be described as an Over-the-Top (OTT) connection 824.
  • the host computer 816 and the connected UEs 812, 814 are configured to communicate data and/or signaling via the OTT connection 824, using the access network 802, the core network 804, any intermediate network 822, and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 824 may be transparent in the sense that the participating communication devices through which the OTT connection 824 passes are unaware of routing of uplink and downlink communications.
  • the base station 806 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 816 to be forwarded (e.g., handed over) to a connected UE 812. Similarly, the base station 806 need not be aware of the future routing of an outgoing uplink communication originating from the UE 812 towards the host computer 816.
  • a host computer 902 comprises hardware 904 including a communication interface 906 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 900.
  • the host computer 902 further comprises processing circuitry 908, which may have storage and/or processing capabilities.
  • the processing circuitry 908 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the host computer 902 further comprises software 910, which is stored in or accessible by the host computer 902 and executable by the processing circuitry 908.
  • the software 910 includes a host application 912.
  • the host application 912 may be operable to provide a service to a remote user, such as a UE 914 connecting via an OTT connection 916 terminating at the UE 914 and the host computer 902. In providing the service to the remote user, the host application 912 may provide user data which is transmitted using the OTT connection 916.
  • the communication system 900 further includes a base station 918 provided in a telecommunication system and comprising hardware 920 enabling it to communicate with the host computer 902 and with the UE 914.
  • the hardware 920 may include a communication interface 922 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 900, as well as a radio interface 924 for setting up and maintaining at least a wireless connection 926 with the UE 914 located in a coverage area (not shown in Figure 9) served by the base station 918.
  • the communication interface 922 may be configured to facilitate a connection 928 to the host computer 902.
  • connection 928 may be direct or it may pass through a core network (not shown in Figure 9) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 920 of the base station 918 further includes processing circuitry 930, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the base station 918 further has software 932 stored internally or accessible via an external connection.
  • the communication system 900 further includes the UE 914 already referred to.
  • the UE's 914 hardware 934 may include a radio interface 936 configured to set up and maintain a wireless connection 926 with a base station serving a coverage area in which the UE 914 is currently located.
  • the hardware 934 of the UE 914 further includes processing circuitry 938, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the UE 914 further comprises software 940, which is stored in or accessible by the UE 914 and executable by the processing circuitry 938.
  • the software 940 includes a client application 942.
  • the client application 942 may be operable to provide a service to a human or non-human user via the UE 914, with the support of the host computer 902.
  • the executing host application 912 may communicate with the executing client application 942 via the OTT connection 916 terminating at the UE 914 and the host computer 902.
  • the client application 942 may receive request data from the host application 912 and provide user data in response to the request data.
  • the OTT connection 916 may transfer both the request data and the user data.
  • the client application 942 may interact with the user to generate the user data that it provides.
  • the host computer 902, the base station 918, and the UE 914 illustrated in Figure 9 may be similar or identical to the host computer 816, one of the base stations 806A, 806B, 806C, and one of the UEs 812, 814 of Figure 8, respectively.
  • the inner workings of these entities may be as shown in Figure 9 and independently, the surrounding network topology may be that of Figure 8.
  • the OTT connection 916 has been drawn abstractly to illustrate the communication between the host computer 902 and the UE 914 via the base station 918 without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the network infrastructure may determine the routing, which may be configured to hide from the UE 914 or from the service provider operating the host computer 902, or both. While the OTT connection 916 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 926 between the UE 914 and the base station 918 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 914 using the OTT connection 916, in which the wireless connection 926 forms the last segment. More precisely, the teachings of these embodiments may improve the reliability and/or latency (e.g., at handover) and thereby provide benefits such as, e.g., better user experience.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 916 may be implemented in the software 910 and the hardware 904 of the host computer 902 or in the software 940 and the hardware 934 of the UE 914, or both.
  • sensors may be deployed in or in association with communication devices through which the OTT connection 916 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 910, 940 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 916 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 918, and it may be unknown or imperceptible to the base station 918. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer's 902 measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 910 and 940 causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 916 while it monitors propagation times, errors, etc.
  • FIG. 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section.
  • the host computer provides user data.
  • sub-step 1002 (which may be optional) of step 1000, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 1006 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1008 the UE executes a client application associated with the host application executed by the host computer.
  • FIG 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1104 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG. 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • step 1200 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1202, the UE provides user data.
  • sub-step 1204 (which may be optional) of step 1200, the UE provides the user data by executing a client application.
  • sub-step 1206 (which may be optional) of step 1202
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in sub-step 1208 (which may be optional), transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 1304 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

Landscapes

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

Abstract

L'invention concerne des systèmes et des procédés destinés à permettre une configuration d'équipement utilisateur (UE) adaptative lors d'un transfert intercellulaire entrant sur la base d'un ou de plusieurs services entrants. Dans un mode de réalisation, un procédé mis en œuvre par un premier nœud de réseau d'accès radio (RAN) comprend la réception d'une demande d'établissement qui demande l'établissement d'un support de service pour un ou plusieurs services entrants pour un UE et la détermination, sur la base de la demande d'établissement, qu'une condition de déclenchement pour un transfert intercellulaire de l'UE d'une première cellule actionnée par le premier nœud RAN à une seconde cellule actionnée par un second nœud RAN a été respectée. Le procédé comprend en outre, en réponse à la détermination que la condition de déclenchement pour le transfert intercellulaire a été remplie, l'envoi d'une demande de transfert intercellulaire au second nœud RAN pour demander un transfert intercellulaire de l'UE à la seconde cellule actionnée par le second nœud RAN, la demande de transfert intercellulaire comprenant des informations concernant lesdits un ou plusieurs services entrants.
PCT/IB2022/058781 2022-09-16 2022-09-16 Systèmes et procédés permettant une configuration d'ue adaptative lors d'un transfert entrant sur la base d'un ou de plusieurs services entrants WO2024057075A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2022/058781 WO2024057075A1 (fr) 2022-09-16 2022-09-16 Systèmes et procédés permettant une configuration d'ue adaptative lors d'un transfert entrant sur la base d'un ou de plusieurs services entrants

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2022/058781 WO2024057075A1 (fr) 2022-09-16 2022-09-16 Systèmes et procédés permettant une configuration d'ue adaptative lors d'un transfert entrant sur la base d'un ou de plusieurs services entrants

Publications (1)

Publication Number Publication Date
WO2024057075A1 true WO2024057075A1 (fr) 2024-03-21

Family

ID=83558297

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2022/058781 WO2024057075A1 (fr) 2022-09-16 2022-09-16 Systèmes et procédés permettant une configuration d'ue adaptative lors d'un transfert entrant sur la base d'un ou de plusieurs services entrants

Country Status (1)

Country Link
WO (1) WO2024057075A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8929927B1 (en) * 2012-10-10 2015-01-06 Sprint Spectrum L.P. Adjustment of communication parameters in a coverage area based on prevalence of eCSFB devices in the coverage area
US10142800B2 (en) * 2013-11-29 2018-11-27 Lg Electronics Inc. Method and apparatus for transmitting unicast request indication in wireless communication system
US10257234B2 (en) * 2013-12-09 2019-04-09 Samsung Electronics Co., Ltd. Method and apparatus for controlling handover procedure in wireless communication system
WO2022048375A1 (fr) * 2020-09-07 2022-03-10 华为技术有限公司 Système de réseau et équipement utilisateur

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8929927B1 (en) * 2012-10-10 2015-01-06 Sprint Spectrum L.P. Adjustment of communication parameters in a coverage area based on prevalence of eCSFB devices in the coverage area
US10142800B2 (en) * 2013-11-29 2018-11-27 Lg Electronics Inc. Method and apparatus for transmitting unicast request indication in wireless communication system
US10257234B2 (en) * 2013-12-09 2019-04-09 Samsung Electronics Co., Ltd. Method and apparatus for controlling handover procedure in wireless communication system
WO2022048375A1 (fr) * 2020-09-07 2022-03-10 华为技术有限公司 Système de réseau et équipement utilisateur

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP TS 36.413
3GPP TS 38.413

Similar Documents

Publication Publication Date Title
EP2896264B1 (fr) Déclenchement de communication inter-dispositif dans des systèmes de communication sans fil
US20190141586A1 (en) Nodes and method for determining target plmn id and target cell id
US11284468B2 (en) Suspending/resuming measurements in RRC inactive state
EP3811645B1 (fr) Rapport d'événement de réseau pour connectivité à un réseau de données par paquets (pdn)
US11937113B2 (en) Flexible early measurement reporting
US11792698B2 (en) Handling of inactive/idle measurement configurations and inactive/idle measurements upon inter-RAT cell reselection
US20220408518A1 (en) Multi-sim dynamic capabilities
WO2019214741A1 (fr) Amélioration de performance sur une fonction ps_data_off
US20230044291A1 (en) RRC SEGMENTATION AND QoE
US20220394519A1 (en) Systems and methods for validating parameters
WO2019066712A1 (fr) Rapport de mesure flexible dans des scénarios à technologies d'accès radio multiples
WO2020254968A1 (fr) Systèmes et procédés se rapportant à une suspension de connexion initiée par un réseau et à une libération initiale de rrc
US20240080787A1 (en) Redirection and retry of registration
CN114586402B (zh) 用于执行空闲模式测量的方法和装置
US20220256407A1 (en) Handling of ue in cm-connected state with rrc inactive state
WO2024057075A1 (fr) Systèmes et procédés permettant une configuration d'ue adaptative lors d'un transfert entrant sur la base d'un ou de plusieurs services entrants
EP4023034A1 (fr) Indication de relation pour dispositifs à sim multiples
WO2020176025A1 (fr) Systèmes et procédés pour déterminer la validité de mesures de mode de repos
EP4233449B1 (fr) Commutation de branche ul en mode de double connectivité avec agrégation de porteuses
US20220217564A1 (en) Relaxed inter-frequency measurements
WO2024058704A1 (fr) Équipement utilisateur, nœud de réseau, et procédés de traitement de communications
WO2023147066A1 (fr) Découpage de réseau pour dispositifs de liaison latérale

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

Country of ref document: EP

Kind code of ref document: A1