WO2020154855A1 - Amélioration de la mobilité d'un dispositif terminal - Google Patents

Amélioration de la mobilité d'un dispositif terminal Download PDF

Info

Publication number
WO2020154855A1
WO2020154855A1 PCT/CN2019/073456 CN2019073456W WO2020154855A1 WO 2020154855 A1 WO2020154855 A1 WO 2020154855A1 CN 2019073456 W CN2019073456 W CN 2019073456W WO 2020154855 A1 WO2020154855 A1 WO 2020154855A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
access network
source
target
connection resume
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/073456
Other languages
English (en)
Inventor
Haitao Li
Srinivasan Selvaganapathy
Jussi-Pekka Koskinen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to CN201980090448.8A priority Critical patent/CN113348698B/zh
Priority to PCT/CN2019/073456 priority patent/WO2020154855A1/fr
Publication of WO2020154855A1 publication Critical patent/WO2020154855A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks
    • 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/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface

Definitions

  • Example embodiments of the present disclosure generally relate to the field of communications, and in particular, to methods, devices, apparatuses and computer readable storage media for mobility enhancement of a terminal device.
  • LTE Long Term Evolution
  • 5G-CN Fifth Generation Core Network
  • RAN radio access network
  • MTC Machine-type communication
  • NB-IoT Narrow Band Internet of thing
  • 3GPP Third Generation Partnership Project
  • Inter-RAT inter-radio access technology
  • MTC or NB-IoT user equipment which is served by an evolved LTE (eLTE) eNodeB (eNB) connected to the 5G-CN, may enter an INACTIVE state after data transmission. If the UE wants to access the eLTE cell or a different eLTE cell, the UE may trigger a radio resource control (RRC) resume procedure.
  • RRC radio resource control
  • the UE may enter a suspended or IDLE state after data transmission, and a RRC resume procedure may be triggered when the UE intends to access a LTE cell which may or may not be the same as the currently serving LTE cell.
  • the detailed processes of the two RRC resume procedures are different, for example, which may include different security related information elements (IEs) in the RRC messages.
  • IEs security related information elements
  • TAU tracking area update
  • MME Mobile Management Entity
  • NAS Network Attached Storage
  • DL downlink
  • AS Attached Storage
  • UE power consumption would be significant high when UE is moving between the eLTE coverage and the LTE coverage.
  • example embodiments of the present disclosure provide methods, devices, apparatuses and computer readable storage media for mobility enhancement of a terminal device.
  • a method is provided.
  • a terminal device is served by a source access network device connected to a source core network device and determines cell reselection from a source cell of the source access network device to a target cell of a target access network device connected to a target core network device. If a connectivity indication is received from the target access network device to enable a connection resume procedure for data forwarding through a source backhaul link between the source access network device and the source core network device, the terminal device sends to the target access network device a connection resume request for initiating a connection resume procedure. The terminal device receives, from the target access network device, a connection resume response for indicating whether a connection setup procedure is to be initiated.
  • a target access network device receives, from a terminal device served by a source access network device connected to a source core network device, a connection resume request for initiating a connection resume procedure.
  • the target access network device sends, to the source access network device, a handover request for retrieving context of the terminal device.
  • the target access network device receives, from the source access network device, a handover response for indicating whether backhaul switching from a source backhaul link between the source access network device and the source core network device to a target backhaul link between the target access network device and the target core network device is required.
  • the target access network device sends, to the terminal device, a connection resume response based on the handover response.
  • a source access network device is connected to a source core network device and is serving a terminal device.
  • the source access network device receives, from a target access network device connected to a target core network device, a handover request for retrieving context of the terminal device.
  • the source access network device determines whether backhaul switching from a source backhaul link between the source access network device and the source core network device to a target backhaul link between the target access network device and the target core network device is required.
  • the source access network device sends, to the target access network device, a handover response based on the determining.
  • a device comprising at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the device to the method according to the first, second or third aspect.
  • an apparatus comprising means for performing the method according to the first, second or third aspect.
  • a computer readable storage medium that stores a computer program thereon.
  • the computer program when executed by a processor of a device, causes the device to perform the method according to the first, second or third aspect.
  • FIG. 1 illustrates an example environment in which example embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates an example signaling procedure in the mobility of a terminal device from a source access network device to a target access network device according to some example embodiments of the present disclosure
  • FIG. 3 illustrates an example signaling procedure where a connection setup procedure is not initiated in accordance with some example embodiments of the present disclosure
  • FIG. 4 illustrates an example signaling procedure where a connection setup procedure is initiated in accordance with some example embodiments of the present disclosure
  • FIG. 5 illustrates a flowchart of an example method in accordance with some example embodiments of the present disclosure
  • FIG. 6 illustrates a flowchart of an example method in accordance with some other example embodiments of the present disclosure
  • FIG. 7 illustrates a flowchart of an example method in accordance with yet other example embodiments of the present disclosure
  • FIG. 8 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure.
  • the term “access network device” refers to a device via which a terminal device or UE can access a communication network.
  • the BS include a relay, an access point (AP) , a transmission point (TRP) , a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a gigabit NodeB (gNB) , a Remote Radio Module (RRU) , a radio header (RH) , a remote radio head (RRH) , a low power node such as a femto, a pico, and the like.
  • AP access point
  • TRP transmission point
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • gNB gigabit NodeB
  • RRU Remote Radio Module
  • RH radio header
  • RRH remote radio head
  • a low power node such as a femto, a pico, and
  • source access network device refers to an access network device currently serving a terminal device when the terminal device is moving towards another access network device.
  • target access network device refers to an access network device to which the terminal device is moving and thus will be handed over.
  • the term “core network device” refers to a device capable of communicating with the access network device and providing services to the terminal device in a core network.
  • Examples of the core network device may include Mobile Switching Centers (MSCs) , MMEs, Operation and Management (O&M) nodes, Operation Support System (OSS) nodes, Self-Organization Network (SON) nodes, positioning nodes, such as Enhanced Serving Mobile Location Centers (E-SMLCs) , and/or Mobile Data Terminals (MDTs) .
  • MSCs Mobile Switching Centers
  • MMEs Mobility Management
  • O&M Operation and Management
  • OSS Operation Support System
  • SON Self-Organization Network
  • positioning nodes such as Enhanced Serving Mobile Location Centers (E-SMLCs)
  • E-SMLCs Enhanced Serving Mobile Location Centers
  • MDTs Mobile Data Terminals
  • source core network device refers to a core network device currently serving a terminal device when the terminal device is moving towards another core network device.
  • target core network device refers to a core network device to which the terminal device is moving and thus will be handed over.
  • terminal device or “user equipment” (UE) refers to any terminal device capable of wireless communications with each other or with the base station.
  • the communications may involve transmitting and/or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and/or other types of signals suitable for conveying information over air.
  • the UE may be configured to transmit and/or receive information without direct human interaction. For example, the UE may transmit information to the network device on predetermined schedules, when triggered by an internal or external event, or in response to requests from the network side.
  • Examples of the UE include, but are not limited to, user equipment (UE) such as smart phones, wireless-enabled tablet computers, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , and/or wireless customer-premises equipment (CPE) .
  • UE user equipment
  • LME laptop-embedded equipment
  • CPE wireless customer-premises equipment
  • circuitry may refer to one or more or all of the following:
  • combinations of hardware circuits and software such as (as applicable) : (i) a combination of analog and/or digital hardware circuit (s) with software/firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.
  • first As used herein, the terms “first” , “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be referred to as a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • Example embodiments of the present disclosure provide a modified signaling scheme for inter-cell and inter-core network mobility of a terminal device.
  • a terminal device is currently served by a source access network device which is connected to a source core network device and determines cell reselection to a target cell of a target access network device connected to a target core network device as the terminal device moves.
  • the terminal device sends a connection resume request to the target access network device to initiate a connection resume procedure.
  • the target access network device sends a handover request to the source access network device.
  • the source access network device determines whether to switch a source backhaul link between the source access network device and the source core network device to a target backhaul link between the target access network device and the target core network device.
  • the source access network device sends a handover response to the target access network device based on the determining of the backhaul switching.
  • the target access network device sends a connection resume response based on the handover response. Accordingly, the terminal device determines whether to initiate a connection setup procedure.
  • the terminal device may establish connection with the target access network device in a more flexible and efficient way. As such, the mobility of the terminal device in particular between different core networks may be enhanced.
  • FIG. 1 shows an example environment 100 in which example embodiments of the present disclosure can be implemented.
  • the environment 100 which is a part of a communication network, includes a terminal device 105 which is currently served by a source access network device 110 connected to a source core network device 115.
  • the terminal device 105 is moving from a source cell 120 of the source access network device 110 to a target cell 125 of a target access network device 130 connected to a target core network device 135.
  • the access network devices and the core network devices may be implemented by any suitable devices and may comply with any suitable communication standards or protocols.
  • the source access network device 110 may be implemented by an eLTE eNB
  • the source core network device 130 may be implemented by a device or entity in the 5G-CN.
  • the target access network device 130 may be implemented by a LTE eNB
  • the target core network device 135 may be implemented by a MME in the EPC.
  • the environment 100 may include any suitable number of terminal devices, access network devices, and core network devices.
  • the terminal device 105 may communicate with the source access network device 110 and the target access network device 130 or with another terminal device (not shown) directly or via the source access network device 110 or the target access network device 130.
  • the communication may follow any suitable communication standards or protocols such as Universal Mobile Telecommunications System (UMTS) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , evolved Long Term Evolution (eLTE) , the fifth generation (5G) NR, Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employs any suitable communication technologies, including, for example, Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiplexing (OFDM) , time division multiplexing (TDM) , frequency division multiplexing (FDM) , code division multiplexing (CDM) , Bluetooth, ZigBee, and machine type communication (MTC) , enhanced mobile broadband (eMBB) , massive machine type
  • the access network device can communicate with the corresponding core network device in a wired or wireless way.
  • the access network devices may communicate with each other via a communication interface such as an X2 interface.
  • the core network devices may communicate with each other via a dedicated interface. These communications may use any suitable communication technologies that are already known or to be developed in the future.
  • the terminal device 105 when the terminal device 105 is moving into the target cell 125 of the target access network device 130, the terminal device 105 can reselect to the target access network device 130 by cell reselection, for example.
  • the terminal device 105 sends a connection resume request (for example, a RRC-Connection-Resume-Request message) to the target access network device 130 to initiate a connection resume request.
  • a connection resume request for example, a RRC-Connection-Resume-Request message
  • the target access network device 130 Upon the reception of the connection resume request, the target access network device 130 sends a handover request to the source access network device 110 to cause the source access network device 110 to determine whether a source backhaul link between the source access network device 110 and the source core network device 115 is to be switched to a target backhaul link between the target access network device 130 and the target core network device 135.
  • the source access network device 110 may release context of the terminal device 105. If the backhaul switching is unrequired or determined not to be performed, the source access network device 110 may continue to communicate with the terminal device 105 using the source backhaul link by forwarding of the target access network device 130.
  • FIG. 2 shows an example signaling procedure 200 in the mobility of the terminal device 105 from the source access network device 110 to the target access network device 130 according to some example embodiments of the present disclosure.
  • the terminal device 105 determines (205) cell reselection to the target cell 125 of the target access network device 130. For example, when moving from the source cell 120 to the target cell 125, the terminal device 105 may reselect to the target access network device 130 by cell reselection. In some example embodiments, the cell reselection may be performed from the 5G-CN to the EPC. For example, the terminal device 105 in an INACTIVE state is currently served by the 5G-CN, and reselects a LTE cell in the EPC. The terminal device 105 may obtain the information about the target CN connectivity from system information broadcasted by the target access network device 130.
  • the terminal device 105 receives (210) , from the target access network device, a connectivity indication to enable a connection resume procedure for data forwarding through a source backhaul link between the source access network device 110 and the source core network device 115, that is, backhaul switching from the source backhaul link to a target backhaul link between the target access network device 130 and the target core network device 135 is not required. As such, the terminal device 105 may determine whether the data forwarding is enabled by the target access network device 130.
  • the target access network device 130 may broadcast the connectivity indication in a system information block (SIB) to indicate the connection resume procedure to be enabled for the data forwarding. If the target access network device 130 does not enable the use of the connection resume procedure for the data forwarding, the terminal device 105 enters an IDLE state and triggers the connection setup procedure. If the use of the connection resume procedure is allowed, the terminal device 105 may send the connection resume request to the target access network device 130.
  • SIB system information block
  • the terminal device 105 sends (215) a connection resume request to the target access network device 130 to initiate a connection resume procedure.
  • the connection resume procedure may comprises any suitable suspend or resume procedure that is already known or to be developed in the future.
  • the connection resume procedure may be implemented by a RRC Resume procedure.
  • the connection resume request may be implemented by a RRC-Connection-Resume-Request message.
  • the terminal device 105 may defer the sending of the connection resume request until a paging time window (PTW) if extended discontinuous reception (eDRX) is activated.
  • PGW paging time window
  • eDRX extended discontinuous reception
  • the connection resume request may be sent by the terminal device 105 upon arrival of uplink (UL) data, so as to save power consumption of the terminal device 105.
  • UL uplink
  • the terminal device 105 may defer the sending of the connection resume request until the arrival of the UL data.
  • PSM power saving mode
  • the terminal device 105 may determine whether to initiate the connection resume procedure based on a time from the arrival of the UL data to triggering opportunity of a connection setup procedure, to further reduce the UL transmission latency. For example, if UL data (for example, NAS data) arrives, the terminal device 105 may determine whether a time from arriving of the UL data to an available triggering opportunity of a connection setup procedure (for example, a TAU procedure) is greater than a predetermined threshold. The threshold may be predefined based on actual service requirements such as latency requirements. If the time is greater than the predetermined threshold, which means that the triggering opportunity is relatively late, the terminal device 105 may send the connection resume request to the target access network device 130. Otherwise, the terminal device 105 may enter an IDLE state and initiate a connection setup procedure in the triggering opportunity.
  • UL data for example, NAS data
  • a time from arriving of the UL data to an available triggering opportunity of a connection setup procedure for example, a TAU procedure
  • the threshold may be predefined based
  • the connection resume request may contain information about the source access network device 110.
  • the connection resume request may contain resume identification (ID) and a security ID based on the context of the terminal device 105 in the source eLTE cell.
  • the connection resume request may contain an indication to indicate the mobility of the terminal device 105 from the source cell 120.
  • the indication may be implemented by a flag to indicate the mobility from the 5GC.
  • the target access network device 130 Upon reception of the connection resume request, the target access network device 130 sends (220) to the source access network device 110 a handover request for retrieving context of the terminal device 105.
  • the handover request may be sent via an X2 interface between the two access network devices.
  • the handover request may be carried in an X2 Application Protocol (X2AP) message.
  • X2AP X2 Application Protocol
  • the target access network device 130 may indicate to the source access network device 110 that terminal device 105 has moved out to the EPC area.
  • the source access network device 110 determines (225) whether to perform the backhaul switching from the source backhaul link between the source access network device 110 and the source core network device 115 to the target backhaul link between the target access network device 130 and the target core network device 135. For example, the source access network device 110 may validate the security of the handover request and make a decision of whether to enable the backhaul switching based on the validation. If the backhaul switching is determined, the source access network device 110 may move a session of the terminal device 105 out.
  • the source access network device 110 may inform the source core network device 115 of the mobility of the terminal device 105. For example, the source access network device 110 may send an indication to the source core network device 115 to indicate that the terminal device 105 has moved out of the source cell 120. The source core network device 115 may further send an indication to the target core network device 135 to inform that the terminal device 105 is moving into the target cell 125.
  • the source access network device 110 sends (230) a handover response to the target access network device 130 to indicate whether the backhaul switching is required. Similar to the handover request, the handover response may be sent via the X2 interface between the two access network devices. In the case that the source access network device 110 is an eLTE eNB and the target access network device 130 is a LTE eNB, the handover response may be carried in an X2AP message.
  • the source access network device 110 may release the context of the terminal device 105. In addition, the source access network device 110 may inform the source core network device 115 that the terminal device 105 has moved out of the source coverage are 115 and is unreachable for paging. If the backhaul switching is unrequired, the source access network device 110 will continue to communicate with the terminal device 105 by forwarding of the target access network device 130.
  • the target access network device 130 sends (235) a connection resume response to the terminal device 110 such that the terminal device 105 may determine whether a connection setup procedure is to be initiated.
  • the connection setup procedure may be any suitable setup procedure that is already known or to be developed in the future.
  • the connection setup procedure may be implemented by a TAU procedure.
  • the terminal device 105 may determine that the connection setup procedure is to be initiated. In this case, the terminal device 105 may first enter an IDLE state and then initiate a connection setup procedure for setup of new context in the target cell 125. In some example embodiments, the target access network device 130 may inform the target core network device 135 of the CN change.
  • the target access network device 130 may send the connection resume response to indicate that the connection resume request is allowed. In this case, the target access network device 130 may determine to forward communications between the terminal device 105 and the source access network device 110.
  • the target access network device 130 may configure the terminal device 110 to switch only the functions on lower layers such as Radio Link Control (RLC) , Media Access Control (MAC) and Physical (PHY) layers to the target cell 125.
  • RLC Radio Link Control
  • MAC Media Access Control
  • PHY Physical
  • the source access network device 110 is an eLTE eNB and the target access network device 130 is a LTE eNB
  • 5G security and Packet Data Convergence Protocol (PDCP) functions can still be used by the terminal device 105 and the related context of 5G is maintained.
  • PDCP Packet Data Convergence Protocol
  • UP User-Plane
  • UPGW 5G User-Plane Gateway
  • the terminal device 105 may send the UL data to the target access network device 130. Then, the target access network device 130 forwards the UL data to the source access network device 110. Upon the completion of the UL data transmission, the UE enters an IDLE state and will trigger a further connection resume procedure or a connection setup procedure (for example, the TAU procedure or a service request procedure) for a future service request.
  • a further connection resume procedure or a connection setup procedure for example, the TAU procedure or a service request procedure
  • the terminal device 105 may trigger a RRC Connection Resume procedure upon reselecting a LTE cell connecting to the EPC to enable the source eLTE eNB to decide whether to release the context of the terminal device 105 or to enable data forwarding via the target cell while maintaining the 5GC connectivity.
  • the terminal device 105 may have new configurations for RLC, MAC and PHY layers of the target LTE cell and old configurations for PDCP and security of the source eLTE cell.
  • data of a 5GC cell may be forwarded via an EPC cell, and 5G PDCP and security may still be used for the data transmission.
  • the 5GC may be informed about the UE mobility to the EPC when the source eLTE eNB decides to release the context and the UE enters an IDLE state in the new cell.
  • the terminal device 105 may initiate a connection setup procedure upon UL data available for transmission.
  • the source access network device 110 and the source core network device 115 are 5G (or eLTE) devices
  • the target access network device 130 and the target core network device 135 are LTE devices.
  • FIG. 3 shows an example signaling procedure 300 where the connection setup procedure is not initiated in accordance with some example embodiments of the present disclosure.
  • the target access network device 130 (for example, a LTE eNB) broadcasts (305) support of a connection resume procedure for data forwarding through a source backhaul link between the source access network device 110 and the source core network device 115 (that is, no backhaul switching) .
  • the terminal device 105 (for example, a UE) served by the source access network device 110 (for example, an eLTE eNB) reselects (310) the target cell 125 (for example, a target cell) upon UL NAS data arrival.
  • the terminal device 105 sends (315) a connection resume request (for example, a RRC-Connection-Resume-Request message) to the target access network device 130 to indicate the mobility from 5GC, for example.
  • the target access network device 130 sends (320) a handover request to the source access network device 110 to indicate the mobility from 5GC.
  • the source access network device 110 decides (325) not to perform the backhaul switching.
  • the source access network device 110 indicates (330) to the source core network device 115 (for example, in 5GC) that the terminal device 105 is moving out of 5GC, for example.
  • the source core network device 115 indicates (335) to the target core network device 135 (for example, in EPC) that the terminal device 105 is moving into the EPC, for example.
  • the source access network device 110 sends (340) a handover response to the target access network device 130 to require forwarding of 5G-PDCP packets via LTE RLC/MAC/PHY layers.
  • the target access network device 120 sends (345) a connection resume response (for example, RRC-Connection-Resume message) to the terminal device 105 to switch only the functions on the RLC/MAC/PHY layers while maintaining the PDCP and security context of 5G.
  • a connection resume response for example, RRC-Connection-Resume message
  • the target access network device 130 forwards (350) the data transmission between the terminal device 105 and the source access network device 110. After the data transmission is completed, the target access network device 130 sends (355) a connection release message (for example, a RRC-Connection-Release message) to the terminal device 105.
  • a connection release message for example, a RRC-Connection-Release message
  • FIG. 4 shows an example signaling procedure 400 where the connection setup procedure is initiated in accordance with some example embodiments of the present disclosure.
  • the actions (or operations) 405 to 420 in the procedure 400 are the same as the actions (or operations) 305-320, and the details thereof will be omitted.
  • the source access network device 110 decides (425) to perform the backhaul switching.
  • the actions 430 and 435 same as the actions 330 and 335, are performed such that the source and target core network devices can be aware of the mobility of the terminal device 105.
  • the source access network device 110 sends (440) a handover response to the target access network device 130 to indicate the release of the UE context.
  • the terminal device 105 sends (450) a connection setup request (for example, a RRC-Connection-Request) to the target access network device 130 to initiate a connection setup procedure (for example, the TAU procedure) .
  • a connection setup request for example, a RRC-Connection-Request
  • FIG. 5 shows a flowchart of an example method 500 in accordance with some example embodiments of the present disclosure.
  • the method 500 can be implemented at the terminal device 105 as shown in FIG. 1. For the purpose of discussion, the method 500 will be described with reference to FIG. 1.
  • the terminal device 105 determines cell reselection from the source cell 120 of the source access network device 110 to the target cell 125 of the target access network device 130.
  • the terminal device 105 receives, from the target access network device 130, a connectivity indication to enable a connection resume procedure for data forwarding through a source backhaul link between the source access network device and the source core network device.
  • the terminal device 105 sends to the target access network device 130 a connection resume request for initiating a connection resume procedure.
  • the terminal device 105 receives, from the target access network device 130, a connection resume response for indicating whether a connection setup procedure is to be initiated.
  • the connectivity indication may be broadcast from the target access network device 130.
  • the terminal device 105 may send the connection resume request in response to arrival of uplink data. In some example embodiments, the terminal device 105 may defer the sending of the connection resume request until the arrival of the uplink data if a power saving mode is activated.
  • the terminal device 105 may determine whether a time from the arrival of the uplink data to an available triggering opportunity of a connection setup procedure is greater than a predetermined threshold. If it is determine that the time is greater than the predetermined threshold, the terminal device 105 may send the connection resume request to the target access network device 130.
  • the terminal device 105 may defer the sending of the connection resume request until a paging time window if extended discontinuous reception is activated.
  • the terminal device 105 may determine that the connection setup procedure is unrequired if the connection resume response indicates that the connection resume request is allowed. The terminal device 105 may further transmit uplink data to the target access network device.
  • the terminal device 105 may determine that the connection setup procedure is to be initiated if the connection resume response indicates that the connection resume request is rejected.
  • the terminal device 105 may send, to the target access network device 130, a connection setup request to initiate the connection setup procedure.
  • the terminal device 105 may enter an idle state.
  • the terminal device 105 may send the connection setup request in the idle state.
  • the terminal device 105 may send the connection setup request to initiate the connection setup procedure in response to uplink data to be transmitted.
  • the connection resume request contains an indication for mobility of the terminal device from the source cell 120 of the source access network device 110.
  • the connection resume procedure may comprise a radio resource control connection resume procedure.
  • the connection setup procedure may comprise a tracking area update procedure.
  • the source core network device may comprise a fifth generation core network device, and the target core network device may comprise an evolved packet core network device.
  • FIG. 6 shows a flowchart of an example method 600 in accordance with some other example embodiments of the present disclosure.
  • the method 600 can be implemented at the target access network device 130 as shown in FIG. 1. For the purpose of discussion, the method 600 will be described with reference to FIG. 1.
  • the target access network device 130 receives, from the terminal device 105, a connection resume request for initiating a connection resume procedure.
  • the target access network device 130 sends, to the source access network device 110, a handover request for retrieving context of the terminal device 105.
  • the target access network device 130 receives, from the source access network device 110, a handover response for indicating whether backhaul switching from a source backhaul link between the source access network device 110 and the source core network device 115 to a target backhaul link between the target access network device 130 and the target core network device 135 is required.
  • the target access network device 130 sends, to the terminal device 105, a connection resume response based on the handover response.
  • the target access network device 130 may broadcast a connectivity indication to enable a connection resume procedure for data forwarding through the source backhaul link (that is, no backhaul switching) .
  • the target access network device 130 may send the connection resume response to indicate that that the connection resume request is allowed if the handover response indicates that the backhaul switching is unrequired.
  • the target access network device 130 may receive uplink data from the terminal device 105.
  • the target access network device 130 may defer the sending of the connection resume request until a paging time window if extended discontinuous reception is activated.
  • the target access network device 130 may further forward the uplink data to the source access network device 110.
  • the target access network device 130 may send the connection resume response to indicate that that the connection resume request is rejected.
  • the target access network device 130 may receive, from the terminal device 105, a connection setup request to initiate a connection setup procedure.
  • the connection setup procedure may comprise a tracking area update procedure.
  • connection resume request and the handover request may contain an indication for mobility of the terminal device 105 from a source cell of the source access network device 110.
  • connection resume procedure may comprise a radio resource control connection resume procedure.
  • the source core network device may comprise a fifth generation core network device, and the target core network device comprises an evolved packet core network device.
  • FIG. 7 shows a flowchart of an example method 700 in accordance with yet other example embodiments of the present disclosure.
  • the method 700 can be implemented at the source access network device 110 as shown in FIG. 1.
  • the method 700 will be described with reference to FIG. 1.
  • the source access network device 110 receives, from the target access network device 130, a handover request for retrieving context of the terminal device 105.
  • the source access network device 110 determines whether backhaul switching from the source backhaul link between the source access network device 110 and the source core network device 115 to the target backhaul link between the target access network device 130 and the target core network device 135 is required.
  • the source access network device 110 sends, to the target access network device 130, a handover response based on the determining.
  • the source access network device 110 may receive uplink data from the terminal device 105 via the target access network device 130 in response to the backhaul switching is disabled.
  • the source access network device 110 may send the connection resume response to indicate that that the connection resume request is allowed if the handover response indicates that the backhaul switching is disabled.
  • the source access network device 110 may send, to the source core network device 130, a switching indication to indicate that the source backhaul link is to be switched to the target backhaul link if the backhaul switching is required.
  • the source access network device 110 may release context of the terminal device.
  • the source access network device 110 may send, to the source core network device 115, an indication for mobility of the terminal device 105 from the source cell 120 of the source access network device 115.
  • the handover request contains an indication for mobility of the terminal device 105 from the source cell 120 of the source access network device 115.
  • the source core network device may comprise a fifth generation core network device
  • the target core network device comprises an evolved packet core network device
  • an apparatus capable of performing the method 500, 600 or 700 may comprise means for performing the respective steps of the method 500, 600 or 700.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus capable of performing the method 500 comprises: means for determining, at a terminal device served by a source access network device connected to a source core network device, cell reselection from a source cell of the source access network device to a target cell of a target access network device connected to a target core network device; means for receiving, from the target access network device, a connectivity indication to enable a connection resume procedure for data forwarding through a source backhaul link between the source access network device and the source core network device; means for sending, to the target access network device, a connection resume request for initiating a connection resume procedure; and means for receiving, from the target access network device, a connection resume response for indicating whether a connection setup procedure is to be initiated.
  • the connectivity indication may be broadcast by the target access network device.
  • means for sending the connection resume request may comprise: means for sending the connection resume request in response to arrival of uplink data.
  • means for sending the connection resume request in response to the arrival of the uplink data may comprise: means for deferring the sending of the connection resume request until the arrival of the uplink data if a power saving mode is activated.
  • means for sending the connection resume request in response to the arrival of the uplink data may comprise: means for determining whether a time from the arrival of the uplink data to an available triggering opportunity of a connection setup procedure is greater than a predetermined threshold; and means for in response to determining that the time is greater than the predetermined threshold, sending the connection resume request to the target access network device.
  • means for sending the connection resume request may comprise: means for deferring the sending of the connection resume request until a paging time window if extended discontinuous reception is activated.
  • the apparatus may further comprise: means for in response to the connection resume response indicating that the connection resume request is allowed, determining that the connection setup procedure is unrequired; and means for transmitting uplink data to the target access network device.
  • the apparatus may further comprise: means for in response to the connection resume response indicating that the connection resume request is rejected, determining that the connection setup procedure is to be initiated; and means for sending, to the target access network device, a connection setup request to initiate the connection setup procedure.
  • means for sending the connection setup request may comprise: means for entering an idle state; and means for sending the connection setup request in the idle state.
  • means for sending the connection setup request may comprise: means for in response to uplink data to be transmitted, sending the connection setup request to initiate the connection setup procedure.
  • the connection resume request may contain an indication for mobility of the terminal device from a source cell of the source access network device.
  • connection resume procedure may comprise a radio resource control connection resume procedure.
  • connection setup procedure may comprise a tracking area update procedure.
  • the source core network device may comprise a fifth generation core network device
  • the target core network device may comprise an evolved packet core network device
  • the apparatus capable of performing the method 600 comprises: means for receiving, at a target access network device connected to a target core network device, a connection resume request for initiating a connection resume procedure from a terminal device served by a source access network device connected to a source core network device; means for sending, to the source access network device, a handover request for retrieving context of the terminal device; means for receiving, from the source access network device, a handover response for indicating whether backhaul switching from a source backhaul link between the source access network device and the source core network device to a target backhaul link between the target access network device and the target core network device is required; and means for sending, to the terminal device, a connection resume response based on the handover response.
  • the apparatus may further comprise: means for broadcasting a connectivity indication to enable a connection resume procedure for data forwarding through the source backhaul link.
  • the means for sending the connection resume response may comprise: means for in response to the handover response indicating that the backhaul switching is unrequired, sending the connection resume response to indicate that that the connection resume request is allowed.
  • the apparatus may further comprise: means for receiving uplink data from the terminal device; and means for forwarding the uplink data to the source access network device.
  • means for sending the connection resume response may comprise: means for in response to the handover response indicating that the backhaul switching is required, sending the connection resume response to indicate that that the connection resume request is rejected.
  • the apparatus may further comprise: means for receiving, from the terminal device, a connection setup request to initiate a connection setup procedure.
  • connection setup procedure may comprise a tracking area update procedure.
  • At least one of the connection resume request and the handover request may contain an indication for mobility of the terminal device from a source cell of the source access network device.
  • connection resume procedure may comprise a radio resource control connection resume procedure.
  • the source core network device may comprise a fifth generation core network device
  • the target core network device may comprise an evolved packet core network device
  • the apparatus capable of performing the method 700 comprises: means for receiving, at a source access network device connected to a source core network device, from a target access network device connected to a target core network device, a handover request for retrieving context of a terminal device served by the source access network device; means for determining whether backhaul switching from a source backhaul link between the source access network device and the source core network device to a target backhaul link between the target access network device and the target core network device is required; and means for sending, to the target access network device, a handover response based on the determining.
  • the apparatus may further comprise: means for in response to the backhaul switching being unrequired, receiving uplink data from the terminal device via the target access network device.
  • the apparatus may further comprise: means for in response to the backhaul switching being required, sending, to the source core network device, a switching indication to indicate that the source backhaul link is to be switched to the target backhaul link.
  • the apparatus may further comprise: means for releasing context of the terminal device.
  • the apparatus may further comprise: means for sending, to the source core network device, an indication for mobility of the terminal device from a source cell of the source access network device.
  • the handover request may contain an indication for mobility of the terminal device from a source cell of the source access network device.
  • the source core network device may comprise a fifth generation core network device
  • the target core network device may comprise an evolved packet core network device
  • FIG. 8 is a simplified block diagram of a device 800 that is suitable for implementing example embodiments of the present disclosure.
  • the device 800 can be implemented at or as a part of the terminal device 105, the target access network device 130 or the source access network device as shown in FIG. 1.
  • the device 800 includes a processor 810, a memory 820 coupled to the processor 810, a communication module 830 coupled to the processor 810, and a communication interface (not shown) coupled to the communication module 830.
  • the memory 820 stores at least a program 840.
  • the communication module 830 is for bidirectional communications, for example, via multiple antennas.
  • the communication interface may represent any interface that is necessary for communication.
  • the program 840 is assumed to include program instructions that, when executed by the associated processor 810, enable the device 800 to operate in accordance with the example embodiments of the present disclosure, as discussed herein with reference to FIGS. 1-7.
  • the example embodiments herein may be implemented by computer software executable by the processor 810 of the device 800, or by hardware, or by a combination of software and hardware.
  • the processor 810 may be configured to implement various example embodiments of the present disclosure.
  • the memory 820 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 820 is shown in the device 800, there may be several physically distinct memory modules in the device 800.
  • the processor 810 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the processor 810 and the communication module 830 may cooperate to implement the method 500 as described above with reference to FIG 5.
  • the processor 810 and the communication module 830 may cooperate to implement the method 600 as described above with reference to FIG. 6.
  • the processor 810 and the communication module 830 may cooperate to implement the method 700 as described above with reference to FIG 7.
  • various example embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of example embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method 500, 600 or 700 as described above with reference to FIGS. 1-7.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various example embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable media.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , Digital Versatile Disc (DVD) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • DVD Digital Versatile Disc
  • an optical storage device a magnetic storage device, or any suitable combination of the foregoing.

Landscapes

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

Abstract

Des modes de réalisation de la présente invention concernent des procédés, des dispositifs, des appareils, et un support de stockage lisible par ordinateur pour améliorer la mobilité d'un dispositif terminal. Dans des modes de réalisation donnés à titre d'exemple, un dispositif terminal est desservi par un dispositif de réseau d'accès source connecté à un dispositif de réseau central source et détermine la resélection de cellule d'une cellule source du dispositif de réseau d'accès source à une cellule cible d'un dispositif de réseau d'accès cible connecté à un dispositif de réseau central cible. Si une indication de connectivité est reçue en provenance du dispositif de réseau d'accès cible pour permettre une procédure de reprise de connexion pour un transfert de données par l'intermédiaire d'une liaison terrestre source entre le dispositif de réseau d'accès source et le dispositif de réseau central source, le dispositif terminal envoie au dispositif de réseau d'accès cible une demande de reprise de connexion pour lancer une procédure de reprise de connexion. Le dispositif de terminal reçoit, en provenance du dispositif de réseau d'accès cible, une réponse de reprise de connexion pour indiquer si une procédure d'établissement de connexion doit être initiée.
PCT/CN2019/073456 2019-01-28 2019-01-28 Amélioration de la mobilité d'un dispositif terminal Ceased WO2020154855A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980090448.8A CN113348698B (zh) 2019-01-28 2019-01-28 终端设备的移动增强
PCT/CN2019/073456 WO2020154855A1 (fr) 2019-01-28 2019-01-28 Amélioration de la mobilité d'un dispositif terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/073456 WO2020154855A1 (fr) 2019-01-28 2019-01-28 Amélioration de la mobilité d'un dispositif terminal

Publications (1)

Publication Number Publication Date
WO2020154855A1 true WO2020154855A1 (fr) 2020-08-06

Family

ID=71839914

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/073456 Ceased WO2020154855A1 (fr) 2019-01-28 2019-01-28 Amélioration de la mobilité d'un dispositif terminal

Country Status (2)

Country Link
CN (1) CN113348698B (fr)
WO (1) WO2020154855A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115589585A (zh) * 2021-07-05 2023-01-10 北京小米移动软件有限公司 数据卡控制方法、装置、终端设备和存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20250048484A1 (en) * 2021-12-09 2025-02-06 Nokia Technologies Oy Control for non-sdt data transmission
CN117320094B (zh) * 2023-11-29 2024-03-08 上海卫星互联网研究院有限公司 一种空间核心网切换方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170332431A1 (en) * 2016-05-12 2017-11-16 Lg Electronics Inc. Method and apparatus for resuming rrc connection in wireless communication system
KR101802076B1 (ko) * 2016-06-17 2017-11-27 한국과학기술원 초광역 무선 백홀망 내 핸드오버 지원 방법 및 이를 수행하는 장치
US20180020382A1 (en) * 2016-07-13 2018-01-18 Samsung Electronics Co., Ltd. Access control method and apparatus for use in mobile communication
CN107734573A (zh) * 2016-08-12 2018-02-23 华为技术有限公司 切换方法、基站及通信系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2081324B1 (fr) * 2008-01-21 2013-01-09 Alcatel Lucent Procédé et système pour la sélection d'une plate-forme d'accès radio.
CN101466128A (zh) * 2009-01-12 2009-06-24 华为技术有限公司 接入点小区接入控制方法、设备及系统
CN101815284B (zh) * 2010-02-10 2015-06-10 中兴通讯股份有限公司 一种实现网络融合的割接方法及系统
AU2012294284A1 (en) * 2011-08-11 2014-02-27 Interdigital Patent Holdings, Inc. Mobile relay handover
US9603060B2 (en) * 2011-11-04 2017-03-21 Mitsubishi Electric Corporation Mobile communication system
CN103384396B (zh) * 2012-05-04 2018-02-27 中兴通讯股份有限公司 移动终端重定向到目标网络的方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170332431A1 (en) * 2016-05-12 2017-11-16 Lg Electronics Inc. Method and apparatus for resuming rrc connection in wireless communication system
KR101802076B1 (ko) * 2016-06-17 2017-11-27 한국과학기술원 초광역 무선 백홀망 내 핸드오버 지원 방법 및 이를 수행하는 장치
US20180020382A1 (en) * 2016-07-13 2018-01-18 Samsung Electronics Co., Ltd. Access control method and apparatus for use in mobile communication
CN107734573A (zh) * 2016-08-12 2018-02-23 华为技术有限公司 切换方法、基站及通信系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115589585A (zh) * 2021-07-05 2023-01-10 北京小米移动软件有限公司 数据卡控制方法、装置、终端设备和存储介质

Also Published As

Publication number Publication date
CN113348698A (zh) 2021-09-03
CN113348698B (zh) 2023-01-13

Similar Documents

Publication Publication Date Title
JP2021048635A (ja) 基地局、コアネットワーク装置、及びこれらの方法
JP2019198100A (ja) 基地局及び方法
US11716779B2 (en) User equipment context relocation at radio access network notification area edge
US12610298B2 (en) Method, device and computer storage medium of communication during a switch among communication networks
US12507306B2 (en) Method, device and computer storage medium of communication
WO2020029173A1 (fr) Procédé, dispositif et support lisible par ordinateur destiné à un accès aléatoire
EP3183922B1 (fr) Activation d'atténuation d'interférences pour une synchronisation dynamique
JP7616382B2 (ja) 方法、ｍｕｓｉｍ端末装置及びマスタノード（ｍｎ）
US20220408402A1 (en) Method, device and computer storage medium of communication
EP3994917B1 (fr) Commutation proactive de communication v2x d'une connexion en liaison latérale à une connexion cellulaire
EP3928578B1 (fr) Configuration de ressources concernant le nb-ido
WO2020154855A1 (fr) Amélioration de la mobilité d'un dispositif terminal
US20230292191A1 (en) Mechanism for cell identity management
US12507251B2 (en) Scheduling request and random access triggering for SDTN
US12520219B2 (en) Methods, devices, and computer readable medium for communication
US20210243705A1 (en) Methods for Adapting Over-the-Air Synchronization to Radio Conditions
US20240129989A1 (en) Method, device and computer storage medium of communication
CN119999163A (zh) 小区激活或去激活的方法和装置
JP2025520481A (ja) 通信の方法、装置及びコンピュータ記憶媒体
WO2022150994A1 (fr) Mécanisme de récupération après défaillance de faisceau
WO2022170520A1 (fr) Configuration de faisceau axée sur la mobilité, pour signal de référence de positionnement
WO2025209722A1 (fr) Procédures de mobilité pour cellules à sib1 à la demande

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

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

Country of ref document: EP

Kind code of ref document: A1