[go: up one dir, main page]

WO2024230053A1 - Procédé de sauvegarde d'ue et dispositifs associés - Google Patents

Procédé de sauvegarde d'ue et dispositifs associés Download PDF

Info

Publication number
WO2024230053A1
WO2024230053A1 PCT/CN2023/122301 CN2023122301W WO2024230053A1 WO 2024230053 A1 WO2024230053 A1 WO 2024230053A1 CN 2023122301 W CN2023122301 W CN 2023122301W WO 2024230053 A1 WO2024230053 A1 WO 2024230053A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
wireless
wireless terminal
backup
network node
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.)
Pending
Application number
PCT/CN2023/122301
Other languages
English (en)
Inventor
Mengzhen WANG
Lin Chen
Weiqiang DU
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.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2023/122301 priority Critical patent/WO2024230053A1/fr
Publication of WO2024230053A1 publication Critical patent/WO2024230053A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/03—Reselecting a link using a direct mode connection
    • H04W36/033—Reselecting a link using a direct mode connection in pre-organised networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • This document is directed generally to wireless communications, and in particular to 5G communications or wireless communications of later generations.
  • FIG. 1 shows a schematic diagram of DC/CA (dual connectivity/carrier aggregation) based duplication transmission for ensuring high reliability in the 5G wireless communication system.
  • DC/CA dual connectivity/carrier aggregation
  • the DC/CA based duplication transmissions (e.g., transmissions on component carrier CC2/CC3/CC4) of the transmissions on the component carrier CC1 are designed to ensure high reliability of Uu transmissions (i.e., transmissions between UE (user equipment) and RAN (radio access network) node 1/2) .
  • redundant transmissions are also supported over N3/N9 interface (e.g., the transmissions on Tunnel 2) .
  • an additional/redundant user plane path e.g., the path of UE -RAN node 2 -UPF2 –DN (data network) is supported to improve equipment reliability of the RAN node and the UPF (user plane function) .
  • the duplication transmissions and/or the redundant paths shown in FIG. 1 may reduce resource efficiency. Specifically, double UE power resources, radio resources, transport resources and processing resources are needed for implementing the duplication transmissions and/or the redundant paths. In addition, network capacity may also be impacted/reduced.
  • the system shown in FIG. 1 relies on only one terminal (i.e., UE) for receptions/transmissions of service data. Once the UE is broken accidentally or due to ageing or hardware/software failure, the data from this UE would be missing and the reliability of the wireless communication system may be downgraded. Therefore, more resource efficient mechanism for high reliability may be expected while taking the UE reliability into account.
  • This document relates to methods, systems, and devices for a backup mechanism, and in particular to methods, systems, and devices for a backup mechanism with high reliability.
  • the present disclosure relates to a wireless communication method for use in a first wireless terminal.
  • the method comprises:
  • the first wireless terminal is configured as a backup terminal of the second wireless terminal.
  • transmitting, to the wireless network node, the service data in response to the occurred takeover event comprises:
  • transmitting, to the wireless network node, the service data in response to the occurred takeover event comprises:
  • transmitting, to the wireless network node, the service data in response to the occurred takeover event comprises:
  • the wireless communication method further comprises:
  • PDU protocol data unit
  • DRB data radio bearer
  • the at least one dummy PDU session and the at least one dummy DRB are configured to transmit the service data if the takeover event occurs.
  • the wireless communication method further comprises:
  • the low layer configuration comprises at least one of a logic channel configuration, a media access control layer configuration or a physical layer configuration.
  • At least one first DRB between the wireless network node and the first wireless terminal and at least one second DRB between the wireless network node and the second wireless terminal are configured with different logic channel identifiers.
  • the wireless communication method further comprises:
  • assisting information associated with being a backup terminal which is configured to transmit service data configured to be transmitted by at least one master terminal if at least one takeover event associated with the at least one master terminal occurs, wherein the assisting information comprises at least one of willingness of being the backup terminal, interest of being the backup terminal or capability indication of being the backup terminal.
  • the capability indication comprises at least one of: capability of being the backup terminal, a power limitation, radio capability, an uplink aggregate maximum bit rate (AMBR) , a downlink AMBR, a terminal AMBR, at least one quality-of-service (QoS) parameter, or a maximum number of master terminals.
  • ABR uplink aggregate maximum bit rate
  • QoS quality-of-service
  • the wireless communication method further comprises:
  • the wireless network node receiving, from the wireless network node, information of the second wireless terminal, wherein the information of the second wireless terminal comprises at least one of: a terminal identifier, an aggregate maximum bit rate or at least one quality-of-service (QoS) parameter.
  • QoS quality-of-service
  • the wireless communication method further comprises: receiving, from the second wireless terminal, a first discovery message for the backup terminal, wherein the first discovery message comprises an indication of searching the backup terminal.
  • the wireless communication method further comprises: transmitting, to the second wireless terminal, a second discovery message for being the backup terminal, wherein the second discovery message comprises at least one of:
  • a terminal identifier configured for the backup terminal
  • the takeover event comprises at least one of: determining to take over the second wireless terminal, receiving, from the wireless network node, a takeover indication of taking over the second wireless terminal, detecting link failure associated with the second wireless terminal, failing to receive a link alive indication from the second wireless terminal, receiving, from the second wireless terminal, a takeover indication of taking over the second wireless terminal, receiving, from an end device of the second wireless terminal, the service data configured to be transmitted via the second wireless terminal, or transmitting, to the end device of the second wireless terminal or to the wireless network node, a takeover indication of taking over the second wireless terminal.
  • the present disclosure relates to a wireless communication method for use in a wireless network node.
  • the method comprises:
  • the wireless communication method further comprises: transmitting, to the first wireless terminal, a status report indicating reception status of the service data.
  • the wireless communication method further comprises: transmitting, to the first wireless terminal, a low layer configuration of at least one DRB configured to transmit the service data.
  • the low layer configuration comprises at least one of a logic channel configuration, a media access control layer configuration or a physical layer configuration.
  • At least one first DRB between the wireless network node and the first wireless terminal and at least one second DRBs between the wireless network node and the second wireless terminal are configured with different logic channel identifiers.
  • the wireless communication method further comprises: transmitting, to a core network, the service data via at least one first PDU session of the first wireless terminal.
  • the wireless communication method further comprises: transmitting, to a core network, the service data via at least one second PDU session of the second wireless terminal.
  • the wireless communication method further comprises: transmitting, to the first wireless terminal, a PDU session configuration and a DRB configuration of the second wireless terminal.
  • the wireless communication method further comprises: transmitting, to a core network, the service data via at least one third PDU session shared by the first wireless terminal and the second wireless terminal.
  • the wireless communication method further comprises:
  • the PDU session resource setup request comprises at least one of an indication of at least one third PDU session being shared by the first wireless terminal and the second wireless terminal or a terminal identifier of the first wireless terminal.
  • the terminal identifier of the first wireless terminal comprises at least one of: an identifier used to identify the first wireless terminal in an access and mobility management function, an identifier used to identify the first wireless terminal in the wireless network node or an identifier used to identify the first wireless terminal in the core network.
  • the wireless communication method further comprises:
  • assisting information associated with being a backup terminal which is configured to transmit service data configured to be transmitted by at least one master terminal if at least one takeover event associated with the at least one master terminal occurs, wherein the assisting information comprises at least one of willingness of being the backup terminal, interest of being the backup terminal or capability indication of being the backup terminal.
  • the capability indication comprises at least one of: capability of being the backup terminal, a power limitation, radio capability, an uplink aggregate maximum bit rate (AMBR) , a downlink AMBR, a terminal AMBR, at least one QoS parameter, or a maximum number of master terminals.
  • ABR uplink aggregate maximum bit rate
  • the wireless communication method further comprises: transmitting, to the first wireless terminal, information of the second wireless terminal, wherein the information of the second wireless terminal comprises at least one of: a terminal identifier, an aggregate maximum bit rate or at least one quality-of-service (QoS) parameter.
  • the information of the second wireless terminal comprises at least one of: a terminal identifier, an aggregate maximum bit rate or at least one quality-of-service (QoS) parameter.
  • QoS quality-of-service
  • the wireless communication method further comprises:
  • the list of backup terminal candidates comprises at least one of: a backup terminal identifier of each backup terminal candidate, a serving cell identifier of each backup terminal candidate, a range between the second wireless terminal and each backup terminal candidate, a link quality between the wireless network node and each backup terminal candidate, or capability information of each backup terminal candidate.
  • the wireless communication method further comprises: receiving, from an access and mobility management function, a backup authorization of the first wireless terminal and/or the second wireless terminal.
  • the backup authorization comprises at least one of: an authorization of allowing the first wireless terminal to act as a backup terminal, or an authorization of allowing the second wireless terminal to use a backup terminal.
  • the wireless communication method further comprises: transmitting, to an access and mobility management function, backup association information indicating an association between the first wireless terminal and the second wireless terminal.
  • the wireless communication method further comprises: transmitting, to the first wireless terminal, an indication of taking over the second wireless terminal.
  • the wireless communication method further comprises: detecting link failure associated with the second wireless terminal.
  • the wireless communication method further comprises: determining that a link quality between the second wireless terminal and the wireless network node is lower than a threshold.
  • the wireless communication method further comprises: receiving, from the first wireless terminal or from the second wireless terminal, a takeover indication of taking over the second wireless terminal.
  • the present disclosure relates to a wireless communication method for use in a second wireless terminal.
  • the method comprises:
  • the wireless communication method further comprises: transmitting, to the first wireless terminal, feedback information indicating successful transmissions of service data configured to be transmitted via the second wireless terminal.
  • the wireless communication method further comprises: transmitting, to the first wireless terminal, a protocol data unit (PDU) session configuration and a data radio bearer (DRB) configuration of transmitting service data configured to be transmitted via the second wireless terminal.
  • PDU protocol data unit
  • DRB data radio bearer
  • At least one first DRB between the wireless network node and the first wireless terminal and at least one second DRBs between the wireless network node and the second wireless terminal are configured with different logic channel identifiers.
  • the list of backup terminal candidates comprises at least one of: a backup terminal identifier of each backup terminal candidate, a serving cell identifier of each backup terminal candidate, a range between the second wireless terminal and each backup terminal candidate, a link quality between the wireless network node and each backup terminal candidate, or capability information of each backup terminal candidate.
  • the wireless communication method further comprises: transmitting, to the first wireless terminal, a first discovery message for a backup terminal, wherein the first discovery message comprises an indication of searching the backup terminal.
  • the wireless communication method further comprises:
  • the second discovery message comprises at least one of: an indication of being the backup terminal, a terminal identifier configured for the backup terminal, a serving cell identifier, a range between the second wireless terminal and the backup terminal, or a link quality of an interface between the backup terminal and the wireless network node.
  • the wireless communication method further comprises: stopping transmitting, to the first wireless terminal, a link alive indication which is configured to be periodically transmitted to the first wireless terminal.
  • the wireless communication method further comprises: transmitting, to the first wireless terminal and/or a wireless network node, a takeover indication of taking over the second wireless terminal.
  • the wireless communication method further comprises: detecting a link failure associated with an interface between the second wireless terminal and the wireless network node.
  • the wireless communication method further comprises: determining that link quality of a first link between the wireless network node and the second wireless terminal is lower than a first threshold.
  • the wireless communication method further comprises: determining that link quality of a second link between an end device and the second wireless terminal is lower than a second threshold.
  • the present disclosure relates to a first terminal.
  • the first terminal comprises:
  • a processor configured to determine that a takeover event occurs
  • a communication unit configured to transmit, to a wireless network node, service data in response to the occurred takeover event, wherein the service data is configured to be transmitted via a second wireless terminal, wherein the first wireless terminal is configured as a backup terminal of the second wireless terminal.
  • Various embodiments may preferably implement the following feature:
  • the processor is further configured to perform any of the aforementioned wireless communication methods.
  • the present disclosure relates to a wireless network node.
  • the wireless network node comprises:
  • a communication unit configured to receive, from a first wireless terminal configured as a backup terminal of a second wireless terminal, service data configured to be transmitted via the second wireless terminal.
  • Various embodiments may preferably implement the following feature:
  • the wireless network node further comprises a processor configured to perform any of the aforementioned wireless communication methods.
  • the present disclosure relates to a second wireless terminal.
  • the second wireless terminal comprises:
  • a communication unit configured to: transmit, to a wireless network node, at least one of a request for a backup terminal or a list of backup terminal candidates, and receive, from the wireless network node, a backup terminal configuration associated with a first wireless terminal.
  • Various embodiments may preferably implement the following feature:
  • the second wireless terminal further comprises a processor configured to perform any of the aforementioned wireless communication methods.
  • the present disclosure relates to a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a wireless communication method recited in any one of foregoing methods.
  • the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
  • FIG. 1 shows a schematic diagram of DC/CA based duplication transmission.
  • FIG. 2 shows a schematic diagram of UE backup according to an embodiment of the present disclosure.
  • FIG. 3 shows a schematic diagram of UE backup according to an embodiment of the present disclosure.
  • FIG. 4 shows a schematic diagram of UE backup for multiple UEs according to an embodiment of the present disclosure.
  • FIG. 5 shows a schematic diagram of data transmission of UE backup according to an embodiment of the present disclosure.
  • FIG. 6 shows a schematic diagram of UE backup according to an embodiment of the present disclosure.
  • FIG. 7 shows an example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure.
  • FIG. 8 shows an example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure.
  • FIG. 9 shows a flowchart of a method according to an embodiment of the present disclosure.
  • FIG. 10 shows a flowchart of a method according to an embodiment of the present disclosure.
  • FIG. 11 shows a flowchart of a method according to an embodiment of the present disclosure.
  • FIG. 12 shows a flowchart of a method according to an embodiment of the present disclosure.
  • FIG. 13 shows a flowchart of a method according to an embodiment of the present disclosure.
  • FIG. 14 shows a flowchart of a method according to an embodiment of the present disclosure.
  • FIG. 15 shows a flowchart of a method according to an embodiment of the present disclosure.
  • info may refer to information.
  • FIG. 2 shows a schematic diagram of the UE backup according to an embodiment of the present disclosure.
  • UE2 is deployed as a backup of UE1.
  • the UE2 may or may not have its own services.
  • the link between the UE1/UE2 and its corresponding end device/PLC (Programmable Logic Controller) may be a wired connection or a wireless connection (e.g., short range communication such as WIFI/Bluetooth/D2D/PC5/SL) .
  • the UE1 and UE2 are respectively responsible for different services.
  • the associated backup UE (e.g., UE2) takes over the services of a master UE (e.g., UE1) only when the master UE is failed (e.g., UE failure or link failure) .
  • a master UE e.g., UE1
  • the resource efficiency is increased.
  • certain aspects are required to be considered, such as how to configure/identify the backup UE association, fast failure detection, and a low latency and lossless take over mechanism.
  • the UE1 may refer to the master UE, and vice versa.
  • the UE2 may refer to the backup UE of the master UE, and vice versa.
  • the UE may have/be configured with backup UE (s) . That is the UE may obtain an association between the UE and its backup UE (s) . The involved UEs/nodes may also need to know the association.
  • the association of the backup UE may be configured by the gNB (e.g., BS (base station) , RAN (radio access network) , or RAN node) .
  • the gNB e.g., BS (base station) , RAN (radio access network) , or RAN node
  • the master UE may send a backup UE request or high reliability requirement or capability to the gNB.
  • the master UE may send a list of candidate backup UEs to the gNB.
  • the list of candidate backup UEs may include at least one of: backup UE ID (identifier) , serving cell ID of the backup UE, a range between the backup UE and the master UE, a Uu link quality of the backup UE, or capability of the backup UE.
  • the gNB may accordingly configure the backup UE (s) to the master UE.
  • the corresponding configuration may include at least one of: a backup UE ID or a valid time interval (e.g., the backup UE association is valid in this time interval) .
  • the master UE may reuse an SL discovery procedure to discover the candidate backup UEs.
  • a discovery message transmitted by the master UE may comprises an indication/interest/high reliability requirement/capability to find a backup UE.
  • a discovery message transmitted by a backup UE may comprises at least one of an indication of willingness/interest/capability to act as a backup UE, a UE ID for backup, a serving cell ID, a range/distance between the UE and the peer UE, or Uu link quality.
  • the backup UE may indicate the willingness/interest/capability to act as a backup UE to the gNB. If the gNB configures the backup (UE) (candidate) as a backup UE for a master UE, the gNB informs master UE info to the backup UE (candidate) .
  • the master UE info may include at least one of: UE ID, AMBR (Aggregate Maximum Bit Rate) or QoS (Quality-of-Service) parameters (e.g., QoS profile of each QoS flow, including at least one of PQI (PC5 QoS identifier) , resource type, priority level, PDB (Packet Delay Budget) , PER (packet error rate) , averaging window, or the maximum data burst volume) .
  • AMBR Access Maximum Bit Rate
  • QoS Quality-of-Service parameters
  • the capability of backup/master UE may further include at least one of: the capability to be a backup UE, the capability to use a backup UE, power limitation, radio capability, UL/DL/UE AMBR, QoS parameters (allowed for Uu communication) , the maximum number of master UEs it can serve, or the maximum number of backup UEs it can use/be configured.
  • the UE ID of the master UE/backup UE may be one of the following: C-RNTI, S-TMSI, L2 ID or other newly assigned ID by the gNB or 5GC (5G core) .
  • the gNB may obtain/need/have/acquire backup authorization of a specific UE from the AMF.
  • the backup authorization may include at least one of: (an indication of) authorized to use backup UE (to act as a master UE) or (an indication of) authorized to act/be used as a backup UE.
  • the gNB may obtain the UE ID for a given UE from the AMF.
  • the gNB may obtain the backup UE association from the AMF.
  • the gNB may send the info to the AMF.
  • the master UE may send the backup UE association to its end devices/PLCs.
  • the master UE may send the information of its end devices/PLCs to the backup UE.
  • the association of the backup UE may be included in the subscription info in the 5GC.
  • the 5GC may send the backup UE association to the UE via NAS message (s) .
  • the backup UE association may include at least one of: a list of possible/allowed backup UEs, the UE ID of each backup UE or the capability of each backup UE.
  • the backup UE association may include at least one of: a list of possible/allowed master UEs, UE ID of each master UE or the capability of each master UE.
  • the 5GC may send the backup UE association to the gNB.
  • the backup UE association is stationary and preconfigured.
  • the backup UE is regarded as a dedicated backup module of the UE1.
  • the backup UE uses the identity and configuration of the UE1 to perform RRC connection reestablishment with the gNB.
  • an additional indication indicates that it is a backup UE is included in the RRC reestablishment request message.
  • the master UE and the backup UE may be backup UE of each other.
  • a UE3 may be a backup UE of the UE2. That is the UE2 is the master UE of the UE3.
  • a fast failure detection mechanism may be designed for the master UE, such that the backup UE can timely take over services of the master UE.
  • the following two cases may be considered for the fast failure detection mechanism.
  • the gNB detects/obtains failure info and indicates the backup UE to take over the service (s) of the master UE.
  • the gNB is able to detect/determine these failures or the change in the link quality.
  • the master UE sends an indication to the gNB.
  • the gNB may configure a threshold of the link quality to the master UE, wherein the threshold is used for determining whether the link quality between the master UE and its end device/PLC is worsened.
  • the gNB when/if the gNB receives the indication (e.g., of the link quality between the master UE and its end devices/PLCs becomes worsened (e.g. below a threshold) and/or the link failure) from the master UE or detects/determines a link problem (e.g., the Uu link quality between the gNB and UE1 becomes worsened (e.g. below a threshold) or Uu RLF occurs or the master UE is broken down) by itself, the gNB informs the backup UE to take over the service (s) of the master UE and configures necessary configuration (s) for the backup UE to transmit service data of the master UE to the network.
  • the indication e.g., of the link quality between the master UE and its end devices/PLCs becomes worsened (e.g. below a threshold) and/or the link failure
  • the gNB informs the backup UE to take over the service (s) of the master UE and configures
  • the backup UE detects/obtains failure info and (autonomously) decides to take over the service (s) of the master UE.
  • the master UE sends an indication to the backup UE when/if:
  • a new link keep alive/failure detection mechanism is proposed for the master UE and the backup UE.
  • the master UE may periodically send a dedicated signal (e.g., empty packets) to the backup UE, to indicate that the path/link where the master UE resides (e.g., the Uu link between the UE1 and the gNB and/or the link between the UE1 and its end device/PLC) works properly/normally. If/When the master UE detects any interface failure or link quality becoming worse than a threshold, the master UE stops sending the dedicated signal to the backup UE. In an embodiment of the master UE broken down, the master UE cannot send the dedicated signal.
  • a dedicated signal e.g., empty packets
  • the backup UE If the backup UE does not receive the dedicated signal as expected/normally or receives the indication of (e.g., of the link quality between the master UE and its end devices/PLCs becomes worsened (e.g. below a threshold) and/or the link failure) from the master UE, the backup UE considers/determines that the master UE link/path is faulty and may decide to take over the service (s) (e.g., the service (s) from the end devices/PLCs of the master UE) . In addition, the backup UE may send an indication (indicating that the backup UE takes over the services of the master UE) to the gNB and acquires necessary configuration (s) for transmit the service data to the network/gNB.
  • the service e.g., the service (s) from the end devices/PLCs of the master UE
  • the master UE may send indication to its end devices/PLCs.
  • the end device/PLC detects the link failure or link quality towards UE1 becoming worse, or receives the link failure indications from the UE1
  • the end device/PLC may initiate the link connection towards the backup UE and/or send the link/path indication to the backup UE.
  • the backup UE then may decide to take over the services associated with the end devices/PLCs of the UE1.
  • the backup UE takes over the service (s) of the master UE (e.g., the service (s) from the devices/PLCs of the master UE) when/if detecting/determining that the link failure of the master UE or receives the indication of taking over the services of the master UE from the gNB.
  • the procedure of taking over the service (s) of the master UE may need to be finished within significantly short time and without data loss.
  • the service data from the end device/PLC of the master UE may be transmitted to both the master UE and the backup UE.
  • the master UE is the only one to transmit the received data to the network.
  • the backup UE takes over the master UE to successively transmit the service data to the network as shown in FIG. 3. Note that the end device/PLC of the UE1 may not transmit the service data to the UE1 in the abnormal state.
  • the backup UE when/if the backup UE takes over the service (s) of the master UE (no matter the gNB indicates the backup UE to take over the master UE or the backup UE autonomously decides to take over the master UE) , the backup UE needs to know a starting point of packets/data to be transmitted to the network.
  • the following ways can be considered:
  • the master UE provides the PDU session configuration (e.g., QoS rules/packet filter sets) and corresponding DRB configuration (e.g., SDAP (Service Data Adaption Protocol) , PDCP (Packet Data Convergence Protocol) and RLC (Radio Link Control) configuration) acquired from the 5GC/gNB to the backup UE.
  • the master UE provides the QoS rules/packet filter sets in the PDU session configuration to backup UE. to make the backup UE to have the same principles as the master UE1 and to filter packets to QoS flows.
  • the UE1 provides DRB configuration (e.g., SDAP, PDCP and RLC configuration) to the UE2, to make the UE2 to have the same mapping between QoS flow (s) to DRB (s) as the UE1.
  • DRB configuration e.g., SDAP, PDCP and RLC configuration
  • the UE2 can maintain the same inactivated/dummy PDU sessions and DRBs as the UE1 and maintain the same PDCP SN (Sequence Number) and RLC SN for the same packet as the UE1.
  • PDCP SN Sequence Number
  • RLC SN Service Number
  • the UE2 discards packets based on PDCP discard timer. In this embodiment, when/if taking over the services of the UE1, the UE2 may transmit all packets in the PDCP buffer in an ascending order.
  • the UE1 when/if receiving the RLC feedback from the gNB, the UE1 forwards the RLC feedback to the UE2.
  • the UE2 transmits packets starting from the first packet for which the successful delivery has not been confirmed by lower layers or the UE2 re-transmits all packets for which the successful delivery has not been confirmed by lower layers in ascending order and starts transmitting packets that have not been transmitted by the UE1.
  • the gNB may also indicate the UE2 to perform PDCP re-establishment or PDCP data recovery for these DRBs.
  • the gNB may send the PDCP status report for uplink data of the UE1 to the UE2.
  • the UE2 (re) transmits the data to the gNB based on the PDCP status report. For example, the UE2 firstly re-transmits the packets for which the successful delivery has not been confirmed by the PDCP status report and then transmits the packets that have not been transmitted by the UE1 in the buffer.
  • the UE2 needs to obtain logical channel/MAC/PHY configuration for these DRBs from the gNB, to activate the DRBs and transmit data on the DRBs.
  • the UE1 maintains a receiving buffer for the data received from end device/PLC at Rx (reception) side as well as a transmitting buffer of the Uu interface at Tx (transmission) side. If a packet is successfully sent on the Uu interface (e.g., receiving the RLC acknowledge (message) for the packet from the gNB) , the Tx side notifies the Rx side and the packet is deleted from the receiving buffer.
  • the backup UE2 maintains the same receiving buffer for the data received from the end device/PLC of the UE1 as the UE1.
  • the UE1 periodically sends the status of the receiving buffer to the UE2, to update the receiving buffer accordingly (e.g., discard packets in the buffer accordingly) . When/If the UE2 takes over the UE1, the UE2 transmits the data/packets in the receiving buffer.
  • the backup UE2 when detecting failure of the UE1, uses the identity and configuration of the UE1 to perform RRC connection reestablishment to the gNB.
  • an additional indication indicates that it is a backup UE is included in the RRC reestablishment request message. If the backup UE2 is an individual UE, and if the UE2 does not have its own data/services and/or only serves as the backup UE of the UE1 (does not serve other UEs) , the UE2 may be kept in RRC (radio resource control) connected state.
  • RRC radio resource control
  • the UE2 may obtain PDU sessions (QoS rules/packet filter sets) /DRB (SDAP/PDCP/RLC) configuration of UE1 and UE3.
  • PDU sessions QoS rules/packet filter sets
  • DAP/PDCP/RLC DAP/PDCP/RLC
  • the UE2 maintains the PDU sessions/DRBs for the UE1, UE3 and itself respectively, as shown in FIG. 4.
  • the gNB provides the corresponding logical channel/MAC/PHY configuration of the related DRBs to the UE2.
  • the same DRB ID may be configured.
  • the gNB configures different LCIDs (logic channel ID) to the DRBs with the same DRB ID. For example, in FIG. 4, the gNB configures LCID1 and LCID2 for the DRB1 and DRB2 of the UE1 respectively. For the DRB1 and DRB2 of the UE2, the gNB respectively configures LCID3 and LCID4.
  • the gNB configures LCID5 and LCID6 respectively for the DRB1 and DRB2 of the UE3
  • the gNB can identify the data is for the DRB2 of the UE1.
  • the gNB can identify the data is for the DRB2 of the UE2.
  • the UE2 After the UE2 transmits the data of end device/PLC of the UE1 to the gNB, there may be three options for the gNB to transmit the data to 5GC, as shown in FIG. 5:
  • the gNB transmits the service data to the 5GC via the original PDU session (s) of the UE1. (Note that, the data are not transmitted on DRBs of the UE1 over Uu) .
  • the gNB needs to know the relationship between DRBs of the UE2 and DRB (s) /PDU session (s) of the UE1 and deliver the packets from DRB (s) of the UE2 to the correct PDU session (s) of the UE1.
  • the UE1 may provide the PDU session configuration (QoS rules/packet filter sets) and corresponding DRB configuration (SDAP, PDCP and RLC configuration) acquiring from the 5GC/gNB to the backup UE.
  • the gNB may also send at least part of the DRB configuration (SDAP/PDCP/RLC configuration) of the UE1 and NAS message (s) for PDU session configuration of the UE1 to the backup UE.
  • the UE2 After obtaining the associated information, the UE2 can maintain the same inactivated/dummy PDU sessions and DRBs as the UE1. Thereby the gNB is clear about the relationship between the DRB (s) of the UE2 and the DRB (s) /PDU session (s) of the UE1.
  • the gNB transmits the service data to the 5GC via PDU sessions owned by the UE2.
  • the UE2 When/If the UE2 receives the service data from/of the end device/PLC of the UE1, the UE2 initiates a service request procedure.
  • the 5GC/AMF initiates PDU session establishment of the UE2. In this case, the 5GC established PDU session for the UE2 and no data is transmitted before the UE2 takes over the services of the UE1.
  • the AMF may indicate that the PDU session is inactivated.
  • the gNB When/if receiving the PDU session establishment of the UE2 from the AMF, the gNB can configure the corresponding DRBs over the Uu interface to the UE2, wherein the DRB configuration may include only SDAP/PDCP/RLC configuration.
  • the UE2 establishes the PDU session and DRBs and does not transmit the data over Uu. Since the service data transmitted from the end device/PLC of the UE1 to the UE1 and the UE2 is actually the same, the PDU session configuration and DRB configuration for the UE1 and the UE2 can be the same, so that the PDCP SN and RLC SN for the same packet can be kept the same at the UE1 and the UE2. Based on the above embodiments for the low latency and seamless take over mechanism, the UE2 is able to know the packets to be transmitted when/if taking over the services of the UE1.
  • the gNB When/If deciding that the UE2 takes over the services of the UE1, the gNB provides the logical channel/MAC/PHY configuration of the related DRBs to UE2. In addition, the gNB may indicate the AMF to activate the corresponding PDU session of the UE2. For instance, the gNB may include/transmit an activation indication in the PDU session resource modify indication message of the UE2.
  • the 5GC when/if receiving the service request of the UE1, the 5GC is aware of the backup UE association of the UE1 and initiates both PDU session establishment of the UE1 and the PDU session establishment of the UE2 (the same configuration) .
  • the gNB transmits the service data to the 5GC via shared PDU session (s) for the UE1 and the UE2.
  • the 5GC may know the backup UE association of the UE1 (e.g., the backup UE of the UE1 is the UE2) .
  • the 5GC may indicate the PDU session is shared by the UE1 and the UE2.
  • the AMF may further include at least one of the following info in the message: an indication of the shared PDU session or a backup UE ID (e.g., at least one of AMF UE NGAP ID/RAN UE NGAP ID/5G-S-TMSI of the UE2) .
  • the gNB sends the PDU session resource modify indication message of the UE1 to the AMF, to change the UE1 associated PDU session/shared PDU session to be associated to the UE2 (e.g., to replace AMF UE NGAP ID and RAN UE NGAP ID of the UE1 to that of the UE2 in the PDU session resource modify indication message) .
  • the message may also include at least one of: master UE info (e.g., AMF UE NGAP ID/RAN UE NGAP ID/5G-S-TMSI of the UE1) , a shared PDU session indication or a backup UE indication.
  • master UE info e.g., AMF UE NGAP ID/RAN UE NGAP ID/5G-S-TMSI of the UE1
  • shared PDU session indication e.g., a shared PDU session indication or a backup UE indication.
  • the end device/PLC of the UE1 may only keep control plane connection with the UE2 and/or does not transmit the service data to the backup UE in the normal state.
  • the UE2 takes over the UE1 to receive service data from the end device/PLC of the UE1 and successively transmits the service data to the network, as shown in FIG. 6.
  • the end device/PLC of the UE1 or the UE2 may obtain the information of the backup UE association and the end device/PLC of the UE1 or UE2 may initiate a link connection between the end device/PLC of the UE1 and the UE2. Since the end device/PLC of the UE1 and the UE2 keep the link connection without data transmissions, how to maintain the link connection under such conditions needs to be considered.
  • the end device and/or the backup UE can periodically send empty packets to each other, to maintain the link connection.
  • an SL inactive state can be introduced.
  • the end device needs to know when to transmit service data to the backup UE2. In one way, if the end device detects/determines that the UE1 is breakdown or has the link failure or that link quality towards the UE1 is below a threshold or receives a notification from the UE1, the end device starts to transmit service data to the UE2. Specifically, the end device firstly (re-) transmits packets for which the successful delivery has not been confirmed by the UE1 and then transmits packets in the buffer/received from upper layer.
  • the notification from the UE1 may include at least one of: a backup indication (indicates to transmit the data to the backup UE) , Uu RLF, or an indication of Uu link quality below a threshold.
  • the UE2 when/if the UE2 decides or is configured to take over the UE1 (see, e.g., embodiments of section “Fast Failure Detection” ) , the UE2 indicates/instructs the end device to start transmitting the data to the UE2.
  • FIG. 7 relates to a schematic diagram of a wireless terminal 70 according to an embodiment of the present disclosure.
  • the wireless terminal 70 may be a user equipment (UE) , a mobile phone, a laptop, a tablet computer, an electronic book or a portable computer system and is not limited herein.
  • the wireless terminal 70 may include a processor 700 such as a microprocessor or Application Specific Integrated Circuit (ASIC) , a storage unit 710 and a communication unit 720.
  • the storage unit 710 may be any data storage device that stores a program code 712, which is accessed and executed by the processor 700.
  • Embodiments of the storage unit 710 include but are not limited to a subscriber identity module (SIM) , read-only memory (ROM) , flash memory, random-access memory (RAM) , hard-disk, and optical data storage device.
  • SIM subscriber identity module
  • ROM read-only memory
  • RAM random-access memory
  • the communication unit 720 may a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 700.
  • the communication unit 720 transmits and receives the signals via at least one antenna 722 shown in FIG. 7.
  • the storage unit 710 and the program code 712 may be omitted and the processor 700 may include a storage unit with stored program code.
  • the processor 700 may implement any one of the steps in exemplified embodiments on the wireless terminal 70, e.g., by executing the program code 712.
  • the communication unit 720 may be a transceiver.
  • the communication unit 720 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless network node (e.g., a base station) .
  • a wireless network node e.g., a base station
  • FIG. 8 relates to a schematic diagram of a wireless network node 80 according to an embodiment of the present disclosure.
  • the wireless network node 80 may be a satellite, a base station (BS) , a network entity, a Mobility Management Entity (MME) , Serving Gateway (S-GW) , Packet Data Network (PDN) Gateway (P-GW) , a radio access network (RAN) node, a next generation RAN (NG-RAN) node, a gNB, an eNB, a gNB central unit (gNB-CU) , a gNB distributed unit (gNB-DU) a data network, a core network or a Radio Network Controller (RNC) , and is not limited herein.
  • BS base station
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • RAN radio access network
  • NG-RAN next generation RAN
  • gNB next generation RAN
  • gNB next generation RAN
  • the wireless network node 80 may comprise (perform) at least one network function such as an access and mobility management function (AMF) , a session management function (SMF) , a user place function (UPF) , a policy control function (PCF) , an application function (AF) , etc.
  • the wireless network node 80 may include a processor 800 such as a microprocessor or ASIC, a storage unit 810 and a communication unit 820.
  • the storage unit 810 may be any data storage device that stores a program code 812, which is accessed and executed by the processor 800. Examples of the storage unit 810 include but are not limited to a SIM, ROM, flash memory, RAM, hard-disk, and optical data storage device.
  • the communication unit 820 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 800.
  • the communication unit 820 transmits and receives the signals via at least one antenna 822 shown in FIG. 8.
  • the storage unit 810 and the program code 812 may be omitted.
  • the processor 800 may include a storage unit with stored program code.
  • the processor 800 may implement any steps described in exemplified embodiments on the wireless network node 80, e.g., via executing the program code 812.
  • the communication unit 820 may be a transceiver.
  • the communication unit 820 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless terminal (e.g., a user equipment or another wireless network node) .
  • a wireless terminal e.g., a user equipment or another wireless network node
  • FIG. 9 shows a flowchart of a method according to an embodiment of the present disclosure.
  • the method shown in FIG. 9 may be used in a first wireless terminal (e.g., backup UE or UE2 in FIG. 2) and comprises the following steps:
  • Step 901 Determine that a takeover event occurs.
  • Step 902 Transmit, to a wireless network node, service data in response to the occurred takeover event, wherein the service data is configured to be transmitted via a second wireless terminal.
  • the first wireless terminal is configured as a back terminal (i.e., backup UE) of a second wireless terminal (e.g., master UE or UE1 in FIG. 2) . That is the first wireless terminal is configured to take over (services of) the second wireless terminal if/when takeover event (s) occurs. Specifically, if/when determining the takeover event occurs, the first wireless terminal is configured to transmit service data to a wireless network node (e.g., BS, gNB, RAN (node) or UPF or DN) , wherein the transmitted service data is originally configured to be transmitted by the second wireless terminal. Since the first wireless terminal can use the same transmission resources to transmit the service data, the resource usage efficiency is increased. In addition, the system reliability is also enhanced because multiple wireless terminals are utilized for support the services.
  • a wireless network node e.g., BS, gNB, RAN (node) or UPF or DN
  • the first wireless terminal transmits the service data in a buffer if the takeover event occurs.
  • the service data in the buffer is discarded if a discard timer of the service data expires.
  • the first wireless terminal transmits the service data within a period which is before taking over the second wireless terminal.
  • the first wireless terminal receives feedback information indicating successful transmissions of the service data from the second wireless terminal. Based on the feedback information, the first wireless terminal transmits the service data after the last successful transmission indicated by the feedback information in response to the occurred takeover event.
  • the first wireless terminal receives a status report indicating reception status of the service data from the wireless network node. Based on the status report, the first wireless terminal acknowledges which service data is successfully received by the wireless network node. In response to the occurred takeover event, the first wireless terminal transmits the service data which has not been successfully received by the wireless network node.
  • the first wireless terminal receives a PDU session configuration and a DRB configuration of transmitting the service data or a PDU session configuration and a DRB configuration of the second wireless terminal.
  • the PDU session configuration and the DRB configuration may be received from the second wireless terminal or the wireless network node.
  • the first wireless terminal Based on the received PDU session configuration and the received DRB configuration, the first wireless terminal maintains dummy PDU session (s) and dummy DRB(s) .
  • the dummy PDU session (s) and dummy DRB (s) are configured to transmit the service data of the second wireless terminal after/if the takeover event occurs. The first wireless terminal does not transmit the service data before the takeover event occurs.
  • the first wireless terminal receives a low layer configuration (e.g., the configuration of at least one of logic channel MAC layer or PHY layer) of DRB (s) configured to transmit the service data (e.g., DRB (s) of the second wireless terminal) . Based on the received low layer configuration, the first wireless terminal activates at least one of the dummy DRB (s) , to transmit the service data.
  • a low layer configuration e.g., the configuration of at least one of logic channel MAC layer or PHY layer
  • the first wireless terminal activates at least one of the dummy DRB (s) , to transmit the service data.
  • the DRBs from different wireless terminals are configured with different LCIDs (see, e.g., FIG. 4) .
  • the first wireless terminal transmits assisting information associated with being a backup terminal to the wireless terminal.
  • the backup terminal is configured to transmit service data configured to be transmitted by master terminal (s) if takeover event (s) associated with the master terminal (s) occurs.
  • the assisting information comprises at least one of willingness of being the backup terminal, interest of being the backup terminal or capability indication of being the backup terminal.
  • the capability indication comprises at least one of: capability of being the backup terminal, a power limitation, radio capability, an uplink AMBR, a downlink AMBR, a terminal AMBR, QoS parameter (s) or a maximum number of master terminals.
  • the first wireless terminal receives information of the second wireless terminal from the wireless network node, to acknowledge that which terminal (s) is configured as its master terminal.
  • the information of the second wireless terminal may comprise at least one of: a terminal ID, an AMBR or QoS parameter (s) .
  • the first wireless terminal may receive a first discovery message from the second wireless terminal.
  • the first discovery message is for searching a backup terminal.
  • the first discovery message may comprise an indication of searching the backup terminal.
  • the first wireless terminal may transmit a second discovery message to the second wireless terminal.
  • the second discovery message is used to indicate willingness/interest/capability of being the backup terminal.
  • the second discover message may comprise at least one of an indication of being the backup terminal, a terminal ID configured for the backup terminal, a serving cell ID, a range between the second wireless terminal (master terminal) and the backup terminal, or a link quality of an interface between the backup terminal and the wireless network node.
  • the takeover event comprises at least one of:
  • FIG. 10 shows a flowchart of a method according to an embodiment of the present disclosure.
  • the method shown in FIG. 10 may be used in a wireless network node (e.g., BS or RAN (node) ) and comprises the following step:
  • a wireless network node e.g., BS or RAN (node)
  • Step 1001 Receive, from a first wireless terminal, service data configured to be transmitted via a second wireless terminal
  • the first wireless terminal is configured as a backup terminal of a second wireless terminal (e.g., master terminal) .
  • the first wireless terminal takes over (services of) the second wireless terminal.
  • the wireless network node receives service data which is configured to be transmitted via the second wireless terminal from the first wireless terminal.
  • the wireless network node transmits a status report indicating reception status of the service data to the first wireless terminal, to inform the first wireless terminal the reception status of the service data transmitted by the second wireless terminal and/or to allow the first wireless terminal to know which service data should be transmitted after the first wireless terminal takes over the second wireless terminal.
  • the wireless network node transmits a low layer configuration of at least one DRB configured to transmit the service data (e.g., low layer configuration of the second wireless terminal) to the first wireless terminal, to activate dummy DRB (s) maintained by the first wireless terminal and/or to make/allow/activate the first wireless terminal to transmit the service data.
  • the service data e.g., low layer configuration of the second wireless terminal
  • the low layer configuration comprises at least one of a logic channel configuration, a MAC layer configuration or a PHY layer configuration.
  • the wireless network node configures different LCIDs to DRBs of different terminals (see, e.g., FIG. 4) , to distinguish the DRBs from different terminals (e.g., master terminal and backup terminal) .
  • the wireless network node transmits the service data which is configured to be transmitted via the second wireless terminal and is received from the first wireless terminal to the CN (e.g., UPF) .
  • These transmissions may be on:
  • the wireless network node may transmit a PDU session configuration and a DRB configuration of the second wireless terminal to the first wireless terminal.
  • the wireless network node may receive a PDU session resource setup request of the third PDU session (s) for the second wireless terminal from the CN.
  • the PDU session resource setup request comprises at least one of an indication of the third PDU session (s) being shared by the first wireless terminal and the second wireless terminal or a terminal ID of the first wireless terminal.
  • the terminal ID of the first wireless terminal comprises at least one of: an ID used to identify the first wireless terminal in an AMF, an identifier used to identify the first wireless terminal in the wireless network node or an identifier used to identify the first wireless terminal in the CN.
  • the wireless network node may receive assisting information associated with (willingness/interest/capability of) being a backup terminal.
  • the assisting information comprises at least one of willingness of being the backup terminal, interest of being the backup terminal or capability indication of being the backup terminal.
  • the capability indication comprises at least one of: capability of being the backup terminal, a power limitation, radio capability, an uplink AMBR, a downlink AMBR, a terminal AMBR, QoS parameter (s) or a maximum number of master terminals.
  • the wireless network node transmits information of the second wireless terminal (e.g., the backup UE association) to the first wireless terminal.
  • the information of the second wireless terminal comprises at least one of: a terminal ID, an AMBR or QoS parameter (s) .
  • the wireless network node may receive 1) a request for a backup terminal and/or 2) list of backup terminal candidates from the second wireless terminal. Accordingly, the wireless network node may configure backup terminal (s) for the second wireless terminal. In this embodiment, the wireless network node may transmit a backup terminal configuration associated with the first wireless terminal to the second wireless terminal, to inform the second wireless terminal that the first wireless terminal is configure as the backup terminal for the second wireless terminal.
  • the list of backup terminal candidates comprises at least one of: a backup terminal ID of each backup terminal candidate, a serving cell ID of each backup terminal candidate, a range between the second wireless terminal and each backup terminal candidate, a link quality between the wireless network node and each backup terminal candidate, or capability information of each backup terminal candidate.
  • the wireless network node may receive a backup authorization from the CN (e.g., AMF) , wherein the backup authorization may be for the first wireless terminal and/or the second wireless terminal.
  • the backup authorization may comprise:
  • the wireless network node may transmit to the CN (e.g., AMF) , backup association information indicating an association between the first wireless terminal and the second wireless terminal (i.e., indicating that the first wireless terminal acts as a backup terminal of the second wireless terminal or that the second wireless terminal is a master terminal of the first wireless terminal) .
  • the CN e.g., AMF
  • backup association information indicating an association between the first wireless terminal and the second wireless terminal (i.e., indicating that the first wireless terminal acts as a backup terminal of the second wireless terminal or that the second wireless terminal is a master terminal of the first wireless terminal) .
  • the wireless network node transmits an indication of taking over the second wireless terminal to the first wireless terminal.
  • the wireless network node may transmit the indication if/when:
  • the indication of taking over the second wireless terminal received from the second wireless terminal may indicate that the link failure (e.g., between the second wireless terminal and its end device/PLC) occurs or that link quality of the link between the second wireless terminal and its end device/PLC is worsened (e.g., below a threshold) .
  • FIG. 11 shows a flowchart of a method according to an embodiment of the present disclosure.
  • the method shown in FIG. 11 may be used in a second wireless terminal (e.g., master UE or UE1 in FIG. 2) and comprises the following steps:
  • Step 1101 Transmit, to a wireless network node, a request for a backup terminal and/or a list of backup terminal candidates.
  • Step 1102 Receive, from the wireless network node, a backup terminal configuration associated with a first wireless terminal.
  • the second wireless terminal request a backup terminal by sensing a request (message) for the backup terminal and/or a list of backup terminal candidates to the wireless network node.
  • the second wireless terminal may receive a backup terminal configuration from the wireless network node, wherein the backup terminal configuration indicates an association with a first wireless terminal. That is the first wireless terminal is configured as the backup terminal of the second wireless terminal and the second wireless terminal is informed about the association/configuration between the first wireless terminal and the second wireless terminal.
  • the second wireless terminal transmits feedback information indicating successful transmissions of service data configured to be transmitted via the second wireless terminal, to inform the first wireless terminal about the transmission results of the service data.
  • the second wireless terminal transmits a PDU session configuration and a DRB configuration of transmitting the service data.
  • the DRBs of the first wireless terminal and the second wireless terminal may be configured with different LCIDs (and the same DRB ID) .
  • the list of backup terminal candidates comprises at least one of: a backup terminal ID of each backup terminal candidate, a serving cell ID of each backup terminal candidate, a range between the second wireless terminal and each backup terminal candidate, ⁇ alink quality between the wireless network node and each backup terminal candidate, or capability information of each backup terminal candidate.
  • the second wireless terminal transmits a first discovery message to the first wireless terminal, wherein the first discovery message is for (requesting) a backup terminal.
  • the first discovery message comprises an indication of searching the backup terminal.
  • the second wireless terminal receives a second discovery message from the first wireless terminal, wherein the second discovery message indicates willingness/interest/capability of being a backup terminal.
  • the second discovery message comprises at least one of: an indication of being the backup terminal, a terminal ID configured for the backup terminal, a serving cell ID, a range between the second wireless terminal and the backup terminal, or a link quality of an interface between the backup terminal and the wireless network node.
  • the second wireless terminal may periodically transmit a link alive indication to the first wireless terminal. If/when detecting link failure or determining that link quality between the second wireless terminal and the wireless network node/end device/PLC is worsened (e.g., below a threshold) , the second wireless terminal stops transmitting the link alive indication.
  • the second wireless terminal may transmit a takeover indication of taking over the second wireless terminal to the wireless network node and/or the first wireless terminal.
  • the takeover indication may be transmitted when/if the second wireless terminal detects link failure or determines that link quality between the second wireless terminal and the wireless network node/end device/PLC is worsened (e.g., below a threshold) .
  • FIG. 12 shows a flowchart of a method according to an embodiment of the present disclosure.
  • the method shown in FIG. 12 may be used in an end device (e.g., PLC) and comprises the following steps:
  • Step 1201 Transmit, to a second wireless terminal, service data configured to be transmitted by the second wireless terminal.
  • Step 1202 If a takeover event occurs, stop transmitting, to the second wireless terminal, the service data configured to be transmitted by the second wireless terminal; and start transmitting, to a first wireless terminal, the service data configured to be transmitted by the second wireless terminal.
  • the end device is configured to transmit service data to the second wireless terminal.
  • a takeover event i.e., if the takeover event occurs
  • the end device stops transmitting the service data to the second wireless terminal and starts transmitting the service data to a first wireless terminal (i.e., a backup terminal of the second wireless terminal) .
  • the takeover event comprises at least one of:
  • the end device receives backup association information from the second wireless terminal, wherein the backup association information indicates that the first wireless terminal is a backup terminal of the second wireless terminal and/or that the first wireless terminal is configured to take over the second wireless terminal if the takeover event occurs.
  • FIG. 13 shows a flowchart of a method according to an embodiment of the present disclosure.
  • the method shown in FIG. 13 may be used in a first wireless terminal (e.g., UE or backup UE) and comprises the following step:
  • Step 1301 Transmit, to the wireless network node, assisting information associated with being a backup terminal.
  • the first wireless terminal transmits assisting information associated with being a backup terminal to the wireless network node, to help the wireless network node to make decision on assigning/configuring backup terminals.
  • the backup terminal may be defined as a terminal which is configured to transmit service data configured to be transmitted by at least one master terminal if at least one takeover event associated with the at least one master terminal occurs.
  • the assisting information comprises at least one of willingness of being the backup terminal, interest of being the backup terminal or capability indication of being the backup terminal.
  • the capability indication comprises at least one of: capability of being the backup terminal, a power limitation, radio capability, an uplink AMBR, a downlink AMBR, a terminal AMBR, at least one QoS parameter, or a maximum number of master terminals.
  • the first wireless terminal receives information of the second wireless terminal from the wireless network node.
  • the information of the second wireless terminal comprises at least one of: a terminal ID, an AMBR or at least one QoS parameter.
  • the first wireless terminal receives information of the second wireless terminal from the wireless network node, to acknowledge that which terminal (s) is configured as its master terminal.
  • the information of the second wireless terminal may comprise at least one of: a terminal ID, an AMBR or QoS parameter (s) .
  • the first wireless terminal may receive a first discovery message from the second wireless terminal.
  • the first discovery message is for searching a backup terminal.
  • the first discovery message may comprise an indication of searching the backup terminal.
  • the first wireless terminal may transmit a second discovery message to the second wireless terminal.
  • the second discovery message is used to indicate willingness/interest/capability of being the backup terminal.
  • the second discover message may comprise at least one of an indication of being the backup terminal, a terminal ID configured for the backup terminal, a serving cell ID, a range between the second wireless terminal (master terminal) and the backup terminal, or a link quality of an interface between the backup terminal and the wireless network node.
  • FIG. 14 shows a flowchart of a method according to an embodiment of the present disclosure.
  • the method shown in FIG. 14 may be used in a first wireless terminal (e.g., UE or backup UE) and comprises the following steps:
  • Step 1401 Detect a takeover event associated with a second wireless terminal.
  • Step 1402 Transmit, to a wireless network node, service data configured to be transmitted via the second wireless terminal if detecting takeover event.
  • the first wireless terminal is configured as a backup terminal of the second wireless terminal and is configured to detect/determine a takeover event associated with a second wireless terminal.
  • the first wireless terminal takes over the second wireless terminal and transmits service data configured to be transmitted via the second wireless terminal to the wireless network node.
  • the takeover event comprises at least one of:
  • FIG. 15 shows a flowchart of a method according to an embodiment of the present disclosure.
  • the method shown in FIG. 15 may be used in a wireless network node (e.g., BS or RAN (node) ) and comprises the following steps:
  • a wireless network node e.g., BS or RAN (node)
  • Step 1501 Receive, from a first wireless terminal, service data configured to be transmitted via a second wireless terminal.
  • Step 1502 Transmit, to a CN, the service data via at least one of first PDU session (s) of the first wireless terminal, second PDU session (s) of the second wireless terminal or third PDU session (s) shared by the first wireless terminal and the second wireless terminal.
  • the first wireless terminal is configured as a backup terminal of a second wireless terminal. If/when a takeover event occurs, the first wireless terminal takes over the second wireless terminal, to successively transmits service data for the second wireless terminal.
  • the wireless network node may transmit the service data which is configured to be transmitted via the second wireless terminal and received from the first wireless terminal via at least one of:
  • the wireless network node may transmit a PDU session configuration and a DRB configuration of the second wireless terminal to the first wireless terminal.
  • the wireless network node may receive a PDU session resource setup request of the third PDU session (s) for the second wireless terminal from the CN.
  • the PDU session resource setup request comprises at least one of an indication of the third PDU session (s) being shared by the first wireless terminal and the second wireless terminal or a terminal ID of the first wireless terminal.
  • the terminal ID of the first wireless terminal comprises at least one of: an ID used to identify the first wireless terminal in an AMF, an identifier used to identify the first wireless terminal in the wireless network node or an identifier used to identify the first wireless terminal in the CN.
  • any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any one of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a “software unit” ) , or any combination of these techniques.
  • a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • unit refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according to embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

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

Abstract

Un procédé de communication sans fil à utiliser dans un terminal sans fil est divulgué. Le procédé consiste à : déterminer qu'un événement de prise en charge se produit, transmettre, à un nœud de réseau sans fil, des données de service en réponse à l'événement de prise en charge survenu, les données de service étant configurées pour être transmises par l'intermédiaire d'un second terminal sans fil, le premier terminal sans fil étant configuré en tant que terminal de sauvegarde du second terminal sans fil.
PCT/CN2023/122301 2023-09-27 2023-09-27 Procédé de sauvegarde d'ue et dispositifs associés Pending WO2024230053A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/122301 WO2024230053A1 (fr) 2023-09-27 2023-09-27 Procédé de sauvegarde d'ue et dispositifs associés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/122301 WO2024230053A1 (fr) 2023-09-27 2023-09-27 Procédé de sauvegarde d'ue et dispositifs associés

Publications (1)

Publication Number Publication Date
WO2024230053A1 true WO2024230053A1 (fr) 2024-11-14

Family

ID=93431869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/122301 Pending WO2024230053A1 (fr) 2023-09-27 2023-09-27 Procédé de sauvegarde d'ue et dispositifs associés

Country Status (1)

Country Link
WO (1) WO2024230053A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102598587A (zh) * 2011-11-03 2012-07-18 华为技术有限公司 通信保护的方法和装置
US20190028938A1 (en) * 2017-07-24 2019-01-24 Electronics And Telecommunications Research Institute Communication node for performing handover in wireless communication system and method therefor
CN110109371A (zh) * 2019-06-05 2019-08-09 珠海格力电器股份有限公司 智能家居设备管理系统和设备管理方法
CN110890980A (zh) * 2019-11-15 2020-03-17 深圳明心科技有限公司 一种主备终端切换方法、装置、服务器和系统
CN115699816A (zh) * 2020-05-15 2023-02-03 中兴通讯股份有限公司 用于在双连接下进行侧行链路中继通信的方法
CN116033371A (zh) * 2022-12-30 2023-04-28 海能达通信股份有限公司 一种集群终端设置备机的方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102598587A (zh) * 2011-11-03 2012-07-18 华为技术有限公司 通信保护的方法和装置
US20190028938A1 (en) * 2017-07-24 2019-01-24 Electronics And Telecommunications Research Institute Communication node for performing handover in wireless communication system and method therefor
CN110109371A (zh) * 2019-06-05 2019-08-09 珠海格力电器股份有限公司 智能家居设备管理系统和设备管理方法
CN110890980A (zh) * 2019-11-15 2020-03-17 深圳明心科技有限公司 一种主备终端切换方法、装置、服务器和系统
CN115699816A (zh) * 2020-05-15 2023-02-03 中兴通讯股份有限公司 用于在双连接下进行侧行链路中继通信的方法
CN116033371A (zh) * 2022-12-30 2023-04-28 海能达通信股份有限公司 一种集群终端设置备机的方法

Similar Documents

Publication Publication Date Title
RU2770842C1 (ru) Системы, устройства и способы для обработки отказов линии радиосвязи в беспроводных ретрансляционных сетях
JP2023155461A (ja) デバイスツーデバイス（ｄ２ｄ）通信のモバイル中継器の実現
EP3461219B1 (fr) Station de base pour la gestion d'une défaillance de groupe de cellules secondaire
JP7522797B2 (ja) 通信制御方法
US20220095194A1 (en) Systems, devices, and methods for handling radio link failures in wireless relay networks
TWI755581B (zh) 附加上行鏈路故障處理
CN104640232A (zh) 处理无线链路失败的方法
JP7322230B2 (ja) 通信制御方法
US11265838B2 (en) User equipment, control device, and communication control method
CN113424652B (zh) 无线电网络节点、无线装置以及在其中执行的方法
CN118945749A (zh) 通信控制方法
CN116567853A (zh) 控制用户设备的网络接入
US20240397357A1 (en) Service continuity of sidelink relay communication
US20140219198A1 (en) Method for switching communication connection mode, communication system, base station, transmitter and receiver
JP2023554677A (ja) Ｓｌリレーの場合の障害監視および回復機構
US20250048166A1 (en) Path switch for ue-to-ue relay communication
EP4224902B1 (fr) Procédé de commande de communication
JP7765643B2 (ja) 情報を送受信する方法、装置及び通信システム
JP2024156993A (ja) 通信制御方法、中継ノード、プロセッサ、プログラム及びシステム
WO2024230053A1 (fr) Procédé de sauvegarde d'ue et dispositifs associés
CN109804708B (zh) 控制通信的方法、无线通信设备、接入点和无线通信系统
US11265777B2 (en) WLAN termination U-plane relocation without C-plane relocation
WO2023140334A1 (fr) Procédé de commande de communication
CN112703766A (zh) 由无线通信节点执行的方法、无线通信节点
CN119586092A (zh) 通过促进切换来确保服务连续性

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

Country of ref document: EP

Kind code of ref document: A1