Method of UE backup and devices thereof
Patent Information
- Application Number
- PCT/CN2023/122301
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-09-27
- Publication Date
- 2024-11-14
Smart Images

Figure CN2023122301_14112024_PF_FP_ABST
Abstract
Description
METHOD OF UE BACKUP AND DEVICES THEREOFTECHNICAL FIELD
[0001] This document is directed generally to wireless communications, and in particular to 5G communications or wireless communications of later generations.BACKGROUND
[0002] As an integral part of overall industry 4.0 architecture, a wireless communication system is an important tool for providing timely and reliable message transmission and reception services. Typical industry use cases require the wireless communication system with ultra-reliability. In 3GPP (3rd generation partner project) , some mechanisms of ensuring high reliability are introduced in a 5G wireless communication system. 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. In FIG. 1, 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) . In addition, redundant transmissions are also supported over N3 / N9 interface (e.g., the transmissions on Tunnel 2) . Furthermore, 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) .
[0003] However, 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. On the other hand, 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.SUMMARY
[0004] 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.
[0005] The present disclosure relates to a wireless communication method for use in a first wireless terminal. The method comprises:
[0006] determining that a takeover event occurs, and
[0007] transmitting, 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,
[0008] wherein the first wireless terminal is configured as a backup terminal of the second wireless terminal.
[0009] Various embodiments may preferably implement the following features:
[0010] Preferably, transmitting, to the wireless network node, the service data in response to the occurred takeover event comprises:
[0011] transmitting, to the wireless network node, the service data in a buffer in response to the occurred takeover event, wherein the service data in the buffer is discarded if a discard timer of the service data expires.
[0012] Preferably, transmitting, to the wireless network node, the service data in response to the occurred takeover event comprises:
[0013] receiving, from the second wireless terminal, feedback information indicating successful transmissions of the service data, and
[0014] transmitting, to the wireless network node, the service data after a last successful transmission indicated by the feedback information in response to the occurred takeover event.
[0015] Preferably, transmitting, to the wireless network node, the service data in response to the occurred takeover event comprises:
[0016] receiving, from the wireless network node, a status report indicating reception status of the service data, and
[0017] transmitting, to the wireless network node, the service data associated with the reception status of unconfirmed successful receptions and the service data having not been transmitted in response to the occurred takeover event.
[0018] Preferably, the wireless communication method further comprises:
[0019] receiving, from the second wireless terminal or the wireless network node, a protocol data unit (PDU) session configuration and a data radio bearer (DRB) configuration of transmitting the service data, and
[0020] maintaining at least one dummy PDU session based on the received PDU session configuration,
[0021] maintaining at least one dummy DRB based on the received DRB configuration,
[0022] wherein 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.
[0023] Preferably, the wireless communication method further comprises:
[0024] receiving, from the wireless network node, a low layer configuration of at least one DRB configured to transmit the service data, and
[0025] activating at least one of the at least one dummy DRB based on the low layer configuration, to transmit the service data.
[0026] Preferably, the low layer configuration comprises at least one of a logic channel configuration, a media access control layer configuration or a physical layer configuration.
[0027] Preferably, 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.
[0028] Preferably, the wireless communication method further comprises:
[0029] transmitting, to the wireless network node, 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.
[0030] Preferably, 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.
[0031] Preferably, the wireless communication method further comprises:
[0032] 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.
[0033] Preferably, 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.
[0034] Preferably, 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:
[0035] an indication of being the backup terminal,
[0036] a terminal identifier configured for the backup terminal,
[0037] a serving cell identifier,
[0038] a range between the second wireless terminal and the backup terminal, or
[0039] a link quality of an interface between the backup terminal and the wireless network node.
[0040] Preferably, 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.
[0041] The present disclosure relates to a wireless communication method for use in a wireless network node. The method comprises:
[0042] receiving, 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.
[0043] Various embodiments may preferably implement the following features:
[0044] Preferably, the wireless communication method further comprises: transmitting, to the first wireless terminal, a status report indicating reception status of the service data.
[0045] Preferably, 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.
[0046] Preferably, the low layer configuration comprises at least one of a logic channel configuration, a media access control layer configuration or a physical layer configuration.
[0047] Preferably, 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.
[0048] Preferably, 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.
[0049] Preferably, 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.
[0050] Preferably, 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.
[0051] Preferably, 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.
[0052] Preferably, the wireless communication method further comprises:
[0053] receiving, from the core network, a PDU session resource setup request of the at least one third PDU session for the second wireless terminal, wherein 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.
[0054] Preferably, 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.
[0055] Preferably, the wireless communication method further comprises:
[0056] receiving, from the first wireless terminal, 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.
[0057] Preferably, 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.
[0058] Preferably, 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.
[0059] Preferably, the wireless communication method further comprises:
[0060] receiving, from the second wireless terminal, at least one of a request for a backup terminal or a list of backup terminal candidates, and
[0061] transmitting, to the second wireless terminal, a backup terminal configuration associated with the first wireless terminal.
[0062] Preferably, 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.
[0063] Preferably, 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.
[0064] Preferably, 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.
[0065] Preferably, 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.
[0066] Preferably, the wireless communication method further comprises: transmitting, to the first wireless terminal, an indication of taking over the second wireless terminal.
[0067] Preferably, the wireless communication method further comprises: detecting link failure associated with the second wireless terminal.
[0068] Preferably, 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.
[0069] Preferably, 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.
[0070] The present disclosure relates to a wireless communication method for use in a second wireless terminal. The method comprises:
[0071] transmitting, to a wireless network node, at least one of a request for a backup terminal or a list of backup terminal candidates, and
[0072] receiving, from the wireless network node, a backup terminal configuration associated with a first wireless terminal.
[0073] Various embodiments may preferably implement the following features:
[0074] Preferably, 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.
[0075] Preferably, 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.
[0076] Preferably, 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.
[0077] Preferably, 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.
[0078] Preferably, 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.
[0079] Preferably, the wireless communication method further comprises:
[0080] receiving, from the first wireless terminal, a second discovery message of being a backup terminal, wherein 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.
[0081] Preferably, 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.
[0082] Preferably, 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.
[0083] Preferably, the wireless communication method further comprises: detecting a link failure associated with an interface between the second wireless terminal and the wireless network node.
[0084] Preferably, 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.
[0085] Preferably, 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.
[0086] The present disclosure relates to a first terminal. The first terminal comprises:
[0087] a processor, configured to determine that a takeover event occurs, and
[0088] 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.
[0089] Various embodiments may preferably implement the following feature:
[0090] Preferably, the processor is further configured to perform any of the aforementioned wireless communication methods.
[0091] The present disclosure relates to a wireless network node. The wireless network node comprises:
[0092] 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.
[0093] Various embodiments may preferably implement the following feature:
[0094] Preferably, the wireless network node further comprises a processor configured to perform any of the aforementioned wireless communication methods.
[0095] The present disclosure relates to a second wireless terminal. The second wireless terminal comprises:
[0096] 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.
[0097] Various embodiments may preferably implement the following feature:
[0098] Preferably, the second wireless terminal further comprises a processor configured to perform any of the aforementioned wireless communication methods.
[0099] 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.
[0100] The exemplary embodiments disclosed herein are directed to providing features that will become readily apparent by reference to the following description when taken in conjunction with the accompany drawings. In accordance with various embodiments, exemplary systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of the present disclosure.
[0101] Thus, 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.
[0102] The invention is specified by the independent claims. Preferred embodiments are defined in the dependent claims. In the following description, although numerous features may be designated as optional, it is nevertheless acknowledged that all features comprised in the independent claims are not to be read as optional.
[0103] The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.BRIEF DESCRIPTION OF THE DRAWINGS
[0104] FIG. 1 shows a schematic diagram of DC / CA based duplication transmission.
[0105] FIG. 2 shows a schematic diagram of UE backup according to an embodiment of the present disclosure.
[0106] FIG. 3 shows a schematic diagram of UE backup according to an embodiment of the present disclosure.
[0107] FIG. 4 shows a schematic diagram of UE backup for multiple UEs according to an embodiment of the present disclosure.
[0108] FIG. 5 shows a schematic diagram of data transmission of UE backup according to an embodiment of the present disclosure.
[0109] FIG. 6 shows a schematic diagram of UE backup according to an embodiment of the present disclosure.
[0110] FIG. 7 shows an example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure.
[0111] FIG. 8 shows an example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure.
[0112] FIG. 9 shows a flowchart of a method according to an embodiment of the present disclosure.
[0113] FIG. 10 shows a flowchart of a method according to an embodiment of the present disclosure.
[0114] FIG. 11 shows a flowchart of a method according to an embodiment of the present disclosure.
[0115] FIG. 12 shows a flowchart of a method according to an embodiment of the present disclosure.
[0116] FIG. 13 shows a flowchart of a method according to an embodiment of the present disclosure.
[0117] FIG. 14 shows a flowchart of a method according to an embodiment of the present disclosure.
[0118] FIG. 15 shows a flowchart of a method according to an embodiment of the present disclosure.DETAILED DESCRIPTION
[0119] In the present disclosure, the term “info” or “Info” may refer to information.
[0120] In the present disclosure, more than one terminal can be deployed as a backup for another terminal (i.e., UE backup) and utilized to receive repetitive content, to ensure the reliability and to address the UE reliability issue. FIG. 2 shows a schematic diagram of the UE backup according to an embodiment of the present disclosure. In FIG. 2, UE2 is deployed as a backup of UE1. In an embodiment, 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) . In an embodiment, the UE1 and UE2 are respectively responsible for different services. In an embodiment, 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) . Under such conditions, only one set of radio resources, transport resources and processing resources is needed. Therefore, the resource efficiency is increased. To achieve this high efficiency UE backup scheme, 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.
[0121] In the present disclosure, the UE1 may refer to the master UE, and vice versa.
[0122] In the present disclosure, the UE2 may refer to the backup UE of the master UE, and vice versa.
[0123] Backup UE Association
[0124] In an embodiment, to use / enable the UE backup scheme in FIG. 2, 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.
[0125] The following cases / embodiments may be considered for (configuring) the association of the backup UE:
[0126] 1) In an embodiment, the association of the backup UE may be configured by the gNB (e.g., BS (base station) , RAN (radio access network) , or RAN node) .
[0127] In an embodiment, the master UE may send a backup UE request or high reliability requirement or capability to the gNB. In addition or as an alternative, the master UE may send a list of candidate backup UEs to the gNB. For each candidate backup UE, 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. For each configured backup 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) . If the link between the master UE and the backup UE is via PC5 interface / SL (sidelink) , the master UE may reuse an SL discovery procedure to discover the candidate backup UEs. In an embodiment, a discovery message transmitted by the master UE may comprises an indication / interest / high reliability requirement / capability to find a backup UE. In an embodiment, 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.
[0128] In an embodiment, the backup UE (candidate) 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) .
[0129] 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.
[0130] In an embodiment, 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) .
[0131] In an embodiment, to configure the backup UE association, 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. In addition, if the UE ID for the backup UE is assigned by the 5GC, the gNB may obtain the UE ID for a given UE from the AMF. Moreover, if the UE has the backup UE association in subscription info in the 5GC, the gNB may obtain the backup UE association from the AMF. On the other hand, when / if the gNB determines the backup UE association, it may send the info to the AMF.
[0132] In an embodiment, the master UE may send the backup UE association to its end devices / PLCs.
[0133] In an embodiment, the master UE may send the information of its end devices / PLCs to the backup UE.
[0134] 2) In an embodiment, the association of the backup UE may be included in the subscription info in the 5GC.
[0135] During a registration or service request procedure, the 5GC may send the backup UE association to the UE via NAS message (s) . For example, for the master UE, 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. For the 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. In addition, the 5GC may send the backup UE association to the gNB.
[0136] 3) In an embodiment, the backup UE association is stationary and preconfigured. For instance, the backup UE is regarded as a dedicated backup module of the UE1. When detecting link / communication failure of the UE1, the backup UE uses the identity and configuration of the UE1 to perform RRC connection reestablishment with the gNB. In an embodiment, an additional indication indicates that it is a backup UE is included in the RRC reestablishment request message.
[0137] Note that, the master UE and the backup UE may be backup UE of each other. As an alternative or in addition, a UE3 may be a backup UE of the UE2. That is the UE2 is the master UE of the UE3.
[0138] Fast Failure Detection
[0139] In an embodiment, 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.
[0140] 1) The gNB detects / obtains failure info and indicates the backup UE to take over the service (s) of the master UE.
[0141] In an embodiment, if the Uu link quality between the gNB and the master UE is worsened (e.g., below a threshold) or Uu RLF (radio link failure) occurs or the master UE is broken down, the gNB is able to detect / determine these failures or the change in the link quality.
[0142] In an embodiment, if the link quality between the master UE and its end device / PLC becomes worsened (e.g., below a threshold) or link failure occurs between the mater UE and its device / PLC, the master UE sends an indication to the gNB. In this embodiment, 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.
[0143] In an embodiment, 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.
[0144] 2) The backup UE detects / obtains failure info and (autonomously) decides to take over the service (s) of the master UE.
[0145] In an embodiment, the master UE sends an indication to the backup UE when / if:
[0146] -detecting / determining Uu RLF or that the link quality over Uu interface (i.e., the interface between the master UE and the gNB) becomes worsened, or
[0147] -detecting / determining link failure or the link quality between master UE and its end devices / PLCs becomes worsened.
[0148] In an embodiment, a new link keep alive / failure detection mechanism is proposed for the master UE and the backup UE. For example, 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.
[0149] 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.
[0150] In an embodiment, when / if the master UE detects the Uu RLF or the Uu link quality becoming worse, the master UE may send indication to its end devices / PLCs. When 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.
[0151] Low Latency and Seamless Take Over Mechanism
[0152] In an embodiment, 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. To ensure no impact on traffic continuity, 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.
[0153] In an embodiment, the service data from the end device / PLC of the master UE may be transmitted to both the master UE and the backup UE. In this embodiment, the master UE is the only one to transmit the received data to the network. At an abnormal state (e.g., the abnormal shown in FIG. 2, detecting the link failure of master UE or receiving the indication of taking over the service (s) of the master UE from the gNB) , 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.
[0154] In an embodiment, 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. To achieve this purpose, the following ways can be considered:
[0155] 1) 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.Specifically, 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. In addition, 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. Under such conditions, 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. Note that, without logical channel / MAC / PHY configuration for these DRBs, the UE2 does not transmit data over the Uu interface before taking over the services of the UE1.
[0156] In an embodiment, 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.
[0157] In an embodiment, when / if receiving the RLC feedback from the gNB, the UE1 forwards the RLC feedback to the UE2. When / If taking over the services of the UE1, 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. In addition, when / if indicating the UE2 to take over the services of the UE1, the gNB may also indicate the UE2 to perform PDCP re-establishment or PDCP data recovery for these DRBs.
[0158] In an embodiment, if / when indicating the UE2 to take over the services of the UE1, the gNB may send the PDCP status report for uplink data of the UE1 to the UE2. In this embodiment, 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.
[0159] In an embodiment, if / when taking over the services of the UE1, 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.
[0160] 2) 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.
[0161] For both the two ways, if the backup UE2 is regarded as a dedicated backup module of the UE1, when detecting failure of the UE1, the backup UE2 uses the identity and configuration of the UE1 to perform RRC connection reestablishment to the gNB. In an embodiment, 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.
[0162] If the UE2 has its own services (e.g., end device (s) / PLC (s) ) and / or the UE2 is also acted as a backup UE of another UE (e.g., UE3) . As discussed in the above embodiments, the UE2 may obtain PDU sessions (QoS rules / packet filter sets) / DRB (SDAP / PDCP / RLC) configuration of UE1 and UE3. The UE2 maintains the PDU sessions / DRBs for the UE1, UE3 and itself respectively, as shown in FIG. 4. When / if the UE2 takes over the UE1 and / or the UE3, the gNB provides the corresponding logical channel / MAC / PHY configuration of the related DRBs to the UE2.
[0163] For DRBs of different UEs, the same DRB ID may be configured. In order to allow the gNB to identify the DRBs from different UEs, 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. Similarly, the gNB configures LCID5 and LCID6 respectively for the DRB1 and DRB2 of the UE3 When / if receiving data packets over logical channel with the LCID2, the gNB can identify the data is for the DRB2 of the UE1. When receiving data packet over logical channel with the LCID4, the gNB can identify the data is for the DRB2 of the UE2.
[0164] Low Latency and Seamless Take Over Mechanism
[0165] 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:
[0166] 1) 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) .
[0167] In this case, 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.
[0168] In an embodiment, 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. As an alternative, when the gNB configures the DRB configuration of the UE1, 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.
[0169] 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.
[0170] 2) The gNB transmits the service data to the 5GC via PDU sessions owned by the UE2.
[0171] 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. To increase resource efficiency, when / if the AMF initiates the PDU session establishment of the UE2 to the gNB, the AMF may indicate that the PDU session is inactivated. 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.
[0172] 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.
[0173] In an embodiment, 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) .
[0174] 3) The gNB transmits the service data to the 5GC via shared PDU session (s) for the UE1 and the UE2.
[0175] The 5GC (e.g., AMF) may know the backup UE association of the UE1 (e.g., the backup UE of the UE1 is the UE2) . When / if initiating the PDU session establishment of the UE1, the 5GC may indicate the PDU session is shared by the UE1 and the UE2. Specifically, when / if the AMF sends the PDU session resource setup request for the UE1 to the gNB, 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) .
[0176] In addition, when / if the UE2 takes over services of the UE1, 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) . To allow the AMF to know / distinguish that it is the backup UE to be associated to the PDU session / shared PDU session of the UE1, 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.
[0177] Low Latency and Seamless Takeover Mechanism
[0178] In an embodiment, 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. In the abnormal state (e.g., detecting link failure associated with the UE1 or receiving the takeover indication from the gNB) , 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.
[0179] As discussed in above embodiments, 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.
[0180] In an embodiment, the end device and / or the backup UE can periodically send empty packets to each other, to maintain the link connection.
[0181] As an alternative or in addition, if the link connection between the end device / PLC of the UE1 and the UE2 is a sidelink / PC5 interface, an SL inactive state can be introduced.
[0182] In an embodiment, 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. In another way, 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.
[0183] 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. 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. In an embodiment, the communication unit 720 transmits and receives the signals via at least one antenna 722 shown in FIG. 7.
[0184] In an embodiment, 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.
[0185] 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.
[0186] 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) .
[0187] 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. In addition, 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. In an example, the communication unit 820 transmits and receives the signals via at least one antenna 822 shown in FIG. 8.
[0188] In an embodiment, the storage unit 810 and the program code 812 may be omitted. The processor 800 may include a storage unit with stored program code.
[0189] 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.
[0190] 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) .
[0191] 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:
[0192] Step 901: Determine that a takeover event occurs.
[0193] 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.
[0194] In FIG. 9, 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.
[0195] In an embodiment, the first wireless terminal transmits the service data in a buffer if the takeover event occurs. In this embodiment, the service data in the buffer is discarded if a discard timer of the service data expires. In other words, if taking over the second wireless terminal and / or the takeover event occurs, the first wireless terminal transmits the service data within a period which is before taking over the second wireless terminal.
[0196] In an embodiment, 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.
[0197] In an embodiment, 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.
[0198] In an embodiment, 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. 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) . Note that 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.
[0199] In an embodiment, 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.
[0200] In an embodiment, to allow the wireless network node to distinguish the DRBs from the first wireless terminal and the second wireless terminal, the DRBs from different wireless terminals are configured with different LCIDs (see, e.g., FIG. 4) .
[0201] In an embodiment, the first wireless terminal transmits assisting information associated with being a backup terminal to the wireless terminal. As above discussed, 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.
[0202] In an embodiment, 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.
[0203] In an embodiment, 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) .
[0204] In an embodiment, 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. For example, the first discovery message may comprise an indication of searching the backup terminal.
[0205] In an embodiment, 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. For instance, 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.
[0206] In an embodiment, the takeover event comprises at least one of:
[0207] - determining to take over the second wireless terminal,
[0208] - receiving, from the wireless network node, a takeover indication of taking over the second wireless terminal,
[0209] - detecting link failure associated with the second wireless terminal,
[0210] - failing to receive a link alive indication from the second wireless terminal,
[0211] - receiving, from the second wireless terminal, a takeover indication of taking over the second wireless terminal,
[0212] - receiving, from an end device of the second wireless terminal, the service data configured to be transmitted via the second wireless terminal, or
[0213] - 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.
[0214] 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:
[0215] Step 1001: Receive, from a first wireless terminal, service data configured to be transmitted via a second wireless terminal
[0216] In this embodiment, the first wireless terminal is configured as a backup terminal of a second wireless terminal (e.g., master terminal) . In response to a takeover event, the first wireless terminal takes over (services of) the second wireless terminal. Under such conditions, the wireless network node receives service data which is configured to be transmitted via the second wireless terminal from the first wireless terminal.
[0217] In an embodiment, 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.
[0218] In an embodiment, 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.
[0219] In an embodiment, the low layer configuration comprises at least one of a logic channel configuration, a MAC layer configuration or a PHY layer configuration.
[0220] In an embodiment, 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) .
[0221] In an embodiment, 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:
[0222] - first PDU session (s) of the first wireless terminal;
[0223] - second PDU session (s) of the second wireless terminal; or
[0224] - third PDU session (s) shared by the first wireless terminal and the second wireless terminal.
[0225] In an embodiment, the wireless network node may transmit a PDU session configuration and a DRB configuration of the second wireless terminal to the first wireless terminal.
[0226] In an embodiment, 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.
[0227] In an embodiment, 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.
[0228] In an embodiment, 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. For example, 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.
[0229] In an embodiment, the wireless network node transmits information of the second wireless terminal (e.g., the backup UE association) to the first wireless terminal. For instance, the information of the second wireless terminal comprises at least one of: a terminal ID, an AMBR or QoS parameter (s) .
[0230] In an embodiment, 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.
[0231] In an embodiment, 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.
[0232] In an embodiment, 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. Specifically, the backup authorization may comprise:
[0233] - an authorization of allowing the first wireless terminal to act as a backup terminal, and / or
[0234] - an authorization of allowing the second wireless terminal to use a backup terminal.
[0235] In an embodiment, 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) .
[0236] In an embodiment, the wireless network node transmits an indication of taking over the second wireless terminal to the first wireless terminal. For example, the wireless network node may transmit the indication if / when:
[0237] - detecting link failure associated with the second wireless terminal,
[0238] - determining that a link quality between the second wireless terminal and the wireless network node is lower than a threshold, or
[0239] - receiving, from the first wireless terminal or from the second wireless terminal, a takeover indication of taking over the second wireless terminal.
[0240] Note that, 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) .
[0241] 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:
[0242] Step 1101: Transmit, to a wireless network node, a request for a backup terminal and / or a list of backup terminal candidates.
[0243] Step 1102: Receive, from the wireless network node, a backup terminal configuration associated with a first wireless terminal.
[0244] In FIG. 11, 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.
[0245] In an embodiment of the first wireless terminal is configured as the backup terminal of 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.
[0246] In an embodiment, the second wireless terminal transmits a PDU session configuration and a DRB configuration of transmitting the service data.
[0247] In an embodiment, the DRBs of the first wireless terminal and the second wireless terminal may be configured with different LCIDs (and the same DRB ID) .
[0248] In an embodiment, 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.
[0249] In an embodiment, 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. For example, the first discovery message comprises an indication of searching the backup terminal.
[0250] In an embodiment, 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. For instance, 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.
[0251] In an embodiment, 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.
[0252] In an embodiment, 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) .
[0253] 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:
[0254] Step 1201: Transmit, to a second wireless terminal, service data configured to be transmitted by the second wireless terminal.
[0255] 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.
[0256] In FIG. 12, the end device is configured to transmit service data to the second wireless terminal. In response to 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) .
[0257] In an embodiment, the takeover event comprises at least one of:
[0258] - detecting link failure associated with the second wireless terminal, or
[0259] - receiving, from the first wireless terminal or the second wireless terminal, a takeover indication of the first wireless terminal taking over services of the second wireless terminal.
[0260] In an embodiment, 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.
[0261] 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:
[0262] Step 1301: Transmit, to the wireless network node, assisting information associated with being a backup terminal.
[0263] In FIG. 13, 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. In this embodiment, 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.
[0264] In an embodiment, 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.
[0265] In an embodiment, 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.
[0266] In an embodiment, 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.
[0267] In an embodiment, 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) .
[0268] In an embodiment, 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. For example, the first discovery message may comprise an indication of searching the backup terminal.
[0269] In an embodiment, 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. For instance, 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.
[0270] 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:
[0271] Step 1401: Detect a takeover event associated with a second wireless terminal.
[0272] Step 1402: Transmit, to a wireless network node, service data configured to be transmitted via the second wireless terminal if detecting takeover event.
[0273] In FIG. 14, 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. When determining / detecting the takeover event, 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.
[0274] In an embodiment, the takeover event comprises at least one of:
[0275] - determining to take over the second wireless terminal,
[0276] - receiving, from the wireless network node, a takeover indication of taking over the second wireless terminal,
[0277] - detecting link failure associated with the second wireless terminal,
[0278] - failing to receive a link alive indication from the second wireless terminal,
[0279] - receiving, from the second wireless terminal, a takeover indication of taking over (services of) the second wireless terminal,
[0280] - receiving, from an end device of the second wireless terminal, the service data configured to be transmitted via the second wireless terminal, or
[0281] - 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.
[0282] 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:
[0283] Step 1501: Receive, from a first wireless terminal, service data configured to be transmitted via a second wireless terminal.
[0284] 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.
[0285] In FIG. 15, 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:
[0286] - first PDU session (s) of the first wireless terminal;
[0287] - second PDU session (s) of the second wireless terminal; or
[0288] - third PDU session shared by the first wireless terminal and the second wireless terminal.
[0289] In an embodiment, the wireless network node may transmit a PDU session configuration and a DRB configuration of the second wireless terminal to the first wireless terminal.
[0290] In an embodiment, 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.
[0291] In an embodiment, 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.
[0292] While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand exemplary features and functions of the present disclosure. Such persons would understand, however, that the present disclosure is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any one of the above-described exemplary embodiments.
[0293] It is also understood that 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.
[0294] Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any one of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0295] A skilled person would further appreciate that 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.
[0296] To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, units, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure. In accordance with various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein. The term “configured to” or “configured for” as used herein with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed and / or arranged to perform the specified operation or function.
[0297] Furthermore, a skilled person would understand that various illustrative logical blocks, units, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. 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.
[0298] 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. By way of example, and not limitation, 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.
[0299] In this document, the term "unit" as used herein, 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.
[0300] Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present disclosure. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, 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.
[0301] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of the claims. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.
Claims
1.A wireless communication method for use in a first wireless terminal, the method comprising:determining that a takeover event occurs, andtransmitting, 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.2.The wireless communication method of claim 1, wherein 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 a buffer in response to the occurred takeover event,wherein the service data in the buffer is discarded if a discard timer of the service data expires.3.The wireless communication method of claim 1, wherein transmitting, to the wireless network node, the service data in response to the occurred takeover event comprises:receiving, from the second wireless terminal, feedback information indicating successful transmissions of the service data, andtransmitting, to the wireless network node, the service data after a last successful transmission indicated by the feedback information in response to the occurred takeover event.4.The wireless communication method of claim 1, wherein transmitting, to the wireless network node, the service data in response to the occurred takeover event comprises:receiving, from the wireless network node, a status report indicating reception status of the service data, andtransmitting, to the wireless network node, the service data associated with the reception status of unconfirmed successful receptions and the service data having not been transmitted in response to the occurred takeover event.5.The wireless communication method of any of claims 1 to 4, further comprising:receiving, from the second wireless terminal or the wireless network node, a protocol data unit (PDU) session configuration and a data radio bearer (DRB) configuration of transmitting the service data, andmaintaining at least one dummy PDU session based on the received PDU session configuration,maintaining at least one dummy DRB based on the received DRB configuration,wherein 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.6.The wireless communication method of claim 5, further comprising:receiving, from the wireless network node, a low layer configuration of at least one DRB configured to transmit the service data, andactivating at least one of the at least one dummy DRB based on the low layer configuration, to transmit the service data.7.The wireless communication method of claim 6, wherein the low layer configuration comprises at least one of a logic channel configuration, a media access control layer configuration or a physical layer configuration.8.The wireless communication method of any of claims 1 to 7, wherein 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.9.The wireless communication method of any of claims 1 to 8, further comprising:transmitting, to the wireless network node, 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.10.The wireless communication method of claim 9, wherein 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.11.The wireless communication method of any of claims 1 to 10, further comprising: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.12.The wireless communication method of any of claims 1 to 11, further comprising at least one of: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, ortransmitting, to the second wireless terminal, a second discovery message for being the backup terminal, wherein 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, ora link quality of an interface between the backup terminal and the wireless network node.13.The wireless communication method of any of claims 1 to 12, wherein 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, ortransmitting, 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.14.A wireless communication method for use in a wireless network node, the method comprising:receiving, 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.15.The wireless communication method of claim 14, further comprising:transmitting, to the first wireless terminal, a status report indicating reception status of the service data.16.The wireless communication method of claim 14 or 15, further comprising:transmitting, to the first wireless terminal, a low layer configuration of at least one DRB configured to transmit the service data.17.The wireless communication method of claim 16, wherein the low layer configuration comprises at least one of a logic channel configuration, a media access control layer configuration or a physical layer configuration.18.The wireless communication method of any of claims 14 to 17, wherein 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.19.The wireless communication method of any of claims 14 to 18, further comprising:transmitting, to a core network, the service data via at least one first PDU session of the first wireless terminal.20.The wireless communication method of any of claims 14 to 19, further comprising:transmitting, to a core network, the service data via at least one second PDU session of the second wireless terminal.21.The wireless communication method of claim 20, further comprising:transmitting, to the first wireless terminal, a PDU session configuration and a DRB configuration of the second wireless terminal.22.The wireless communication method of any of claims 14 to 21, further comprising: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.23.The wireless communication method of claim 22, further comprising:receiving, from the core network, a PDU session resource setup request of the at least one third PDU session for the second wireless terminal,wherein 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.24.The wireless communication method of claim 23, wherein 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.25.The wireless communication method of any of claims 14 to 24, further comprising:receiving, from the first wireless terminal, 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.26.The wireless communication method of claim 25, wherein 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.27.The wireless communication method of any of claims 14 to 26, further comprising: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.28.The wireless communication method of any of claims 14 to 27, further comprising:receiving, from the second wireless terminal, at least one of a request for a backup terminal or a list of backup terminal candidates, andtransmitting, to the second wireless terminal, a backup terminal configuration associated with the first wireless terminal.29.The wireless communication method of claim 28, wherein 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, orcapability information of each backup terminal candidate.30.The wireless communication method of any of claims 14 to 29, further comprising:receiving, from an access and mobility management function, a backup authorization of the first wireless terminal and / or the second wireless terminal,wherein the backup authorization comprises at least one of:an authorization of allowing the first wireless terminal to act as a backup terminal, oran authorization of allowing the second wireless terminal to use a backup terminal.31.The wireless communication method of any of claims 14 to 30, further comprising:transmitting, to an access and mobility management function, backup association information indicating an association between the first wireless terminal and the second wireless terminal.32.The wireless communication method of any of claims 14 to 31, further comprising:transmitting, to the first wireless terminal, an indication of taking over the second wireless terminal.33.The wireless communication method of claim 32, further comprising at least one of:detecting link failure associated with the second wireless terminal,determining that a link quality between the second wireless terminal and the wireless network node is lower than a threshold, orreceiving, from the first wireless terminal or from the second wireless terminal, a takeover indication of taking over the second wireless terminal.34.A wireless communication method for use in a second wireless terminal, the method comprising:transmitting, to a wireless network node, at least one of a request for a backup terminal or a list of backup terminal candidates, andreceiving, from the wireless network node, a backup terminal configuration associated with a first wireless terminal.35.The wireless communication method of claim 34, further comprising:transmitting, to the first wireless terminal, feedback information indicating successful transmissions of service data configured to be transmitted via the second wireless terminal.36.The wireless communication method of claim 34 or 35, further comprising: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.37.The wireless communication method of any of claims 34 to 36, wherein 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.38.The wireless communication method of any of claims 34 to 37, wherein 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, orcapability information of each backup terminal candidate.39.The wireless communication method of any of claims 34 to 38, further comprising at least one of: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, or`receiving, from the first wireless terminal, a second discovery message of being a backup terminal, wherein 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, ora link quality of an interface between the backup terminal and the wireless network node.40.The wireless communication method of any of claims 34 to 39, further comprising:stopping transmitting, to the first wireless terminal, a link alive indication which is configured to be periodically transmitted to the first wireless terminal, ortransmitting, to the first wireless terminal and / or a wireless network node, a takeover indication of taking over the second wireless terminal.41.The wireless communication method of claim 40, further comprising:detecting a link failure associated with an interface between the second wireless terminal and the wireless network node,determining that link quality of a first link between the wireless network node and the second wireless terminal is lower than a first threshold, ordetermining that link quality of a second link between an end device and the second wireless terminal is lower than a second threshold.42.A first wireless terminal, comprising:a processor, configured to determine that a takeover event occurs, anda 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.43.The first wireless terminal of claim 42, wherein the processor is further configured to perform the wireless communication method of any of claims 2 to 13.44.A wireless network node, comprising: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.45.The wireless network node of claim 44, further comprising a processor configured to perform the wireless communication method of any of claims 15 to 33.46.A second wireless terminal, comprising: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, andreceive, from the wireless network node, a backup terminal configuration associated with a first wireless terminal.47.The second wireless terminal of claim 46, further comprising a processor configured to perform the wireless communication method of any of claims 35 to 41.48.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 claims 1 to 41.
Citation Information
Patent Citations
Method for protecting communication and devices for the same
CN102598587A
Smart home equipment management system and equipment management method
CN110109371A
Method and device switching main and standby terminals, server and system for switching the main and standby terminals
CN110890980A
Method for sidelink relay communication under dual connectivity
CN115699816A
Method for setting standby machine for cluster terminal
CN116033371A
