WO2023142758A1 - Évaluation de qualité de liaison distincte pour trafic relayé et non relayé - Google Patents

Évaluation de qualité de liaison distincte pour trafic relayé et non relayé Download PDF

Info

Publication number
WO2023142758A1
WO2023142758A1 PCT/CN2022/139345 CN2022139345W WO2023142758A1 WO 2023142758 A1 WO2023142758 A1 WO 2023142758A1 CN 2022139345 W CN2022139345 W CN 2022139345W WO 2023142758 A1 WO2023142758 A1 WO 2023142758A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
host
relay
user data
network node
Prior art date
Application number
PCT/CN2022/139345
Other languages
English (en)
Inventor
Zhang Zhang
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023142758A1 publication Critical patent/WO2023142758A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/38—Transceivers, i.e. devices in which transmitter and receiver form a structural unit and in which at least one part is used for functions of transmitting and receiving

Definitions

  • Embodiments of the present disclosure relate to methods, user equipments and network nodes, and particularly methods, user equipments and network nodes for relaying traffic.
  • LTE Long Term Evolution
  • D2D device-to-device
  • SL sidelink
  • Rel-12 PC5 interface
  • UC Proximity Services
  • ProSe Proximity Services
  • Support was enhanced during Rel-13.
  • the LTE SL was extensively redesigned to support vehicular communications (including Vehicle-to-anything, V2X, and Vehicle-to-vehicle, V2V, communications) .
  • Support was again enhanced during Rel-15. From the point of view of the lowest radio layers, the LTE SL uses broadcast communication. That is, transmission from a User Equipment (UE) targets any receiver that is in range.
  • UE User Equipment
  • the 3GPP introduced SL for the 5G new radio (NR) .
  • the driving UC were vehicular communications with more stringent requirements than those typically served using the LTE SL.
  • the NR SL is capable of broadcast, groupcast, and unicast communications.
  • groupcast communication the intended receivers of a message are typically a subset of the vehicles near the transmitter, whereas in unicast communication, there is typically a single intended receiver.
  • Both the LTE SL and the NR SL can operate with and without network coverage and with varying degrees of interaction between the UEs and the NW (network) , including support for standalone, network-less operation.
  • NSPS National Security and Public Safety
  • 3GPP will specify enhancements related to NSPS use case taking NR Rel. 16 sidelink as a baseline.
  • NSPS services need to operate with partial or without NW coverage, such as indoor firefighting, forest firefighting, earthquake rescue, sea rescue, and so on where the infrastructure is (partially or fully) destroyed or not available.
  • coverage extension is a crucial enabler for NSPS, for both NSPS services communicated between UE and cellular NW and that communicated between UEs over sidelink.
  • the current Uu sidelink radio link failure (RLF) mechanism may not work properly for UE to NW relay.
  • Embodiments of the disclosure aim to provide methods and apparatus that alleviate some or all of the challenges identified herein.
  • An embodiment of the disclosure provides a method performed by a relay UE for link quality assessment.
  • the method comprises evaluating the quality of a first link.
  • the first link is used to transmit first traffic, the first traffic being relay traffic that is relayed by the relay UE between a remote UE and a network node.
  • the method further comprises evaluating the quality of a second link.
  • the second link is used to transmit second traffic, the second traffic being non-relay traffic between the relay UE and one of the remote UE and the network node.
  • a further embodiment of the disclosure provides a method performed by a remote UE for link quality assessment.
  • the method comprises evaluating the quality of a first direct radio link to a relay UE.
  • the first direct link is used to transmit relay traffic that is relayed by the relay UE between the remote UE and a network node.
  • the method further comprises evaluating the quality of a second direct radio link to a relay UE.
  • the second direct link is used to transmit non-relay traffic between the remote UE and the relay UE.
  • a further embodiment provides a method performed by a network node for link quality management.
  • the method comprises receiving notification that traffic relaying of traffic from a remote user equipment (UE) cannot be performed properly over an existing first link between the network node and a relay UE and/or an existing second link between the remote UE and the relay UE.
  • the method further comprises reconfiguring the existing first and/or second link or replacing the existing first and/or second link with a new link.
  • UE remote user equipment
  • a further embodiment of the disclosure provides a user equipment for link quality assessment.
  • the user equipment comprises processing circuitry configured to cause the user equipment to perform the method according to the above embodiment performed by the UE.
  • the user equipment further comprises power supply circuitry configured to supply power to the processing circuitry.
  • a further embodiment of the disclosure provides a network node for link quality management.
  • the network node comprises processing circuitry configured to cause the network node to perform the method according to the above embodiment performed by the network node.
  • the network node further comprises power supply circuitry configured to supply power to the processing circuitry.
  • a further embodiment of the disclosure provides a user equipment for link quality assessment.
  • the user equipment comprises an antenna configured to send and receive wireless signals.
  • the UE further comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry.
  • the user equipment further comprises processing circuitry being configured to perform the method according to the above embodiment performed by the UE.
  • the user equipment further comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry.
  • the user equipment further comprises an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry.
  • the user equipment comprises further a battery connected to the processing circuitry and configured to supply power to the UE.
  • a further embodiment of the disclosure provides a host configured to operate in a communication system to provide an over-the-top (OTT) service.
  • the host comprises processing circuitry configured to provide user data.
  • the host further comprises a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE) .
  • the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform the method according to the above embodiment performed by the UE to receive the user data from the host.
  • a further embodiment of the disclosure provides a method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE) .
  • the method comprises providing user data for the UE.
  • the method further comprises initiating a transmission carrying the user data to the UE via a cellular network comprising the network node.
  • the UE performs the method according to the above embodiment performed by the UE to receive the user data from the host.
  • a further embodiment of the disclosure provides a host configured to operate in a communication system to provide an over-the-top (OTT) service.
  • the host comprises processing circuitry configured to provide user data.
  • the host further comprises a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE) .
  • the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform the method according to the above embodiment performed by the UE to transmit the user data to the host.
  • a further embodiment of the disclosure provides a method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE) .
  • the method comprises at the host receiving user data transmitted to the host via the network node by the UE.
  • the UE performs the method according to the above embodiment performed by the UE to transmit the user data to the host.
  • a further embodiment of the disclosure provides a host configured to operate in a communication system to provide an over-the-top (OTT) service.
  • the host comprises processing circuitry configured to provide user data.
  • the host further comprises a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE) .
  • the network node has a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the method according to the above embodiment performed by the network node to transmit the user data from the host to the UE.
  • a further embodiment of the disclosure provides a method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE) .
  • the method comprises providing user data for the UE.
  • the method further comprises initiating a transmission carrying the user data to the UE via a cellular network comprising the network node.
  • the network node performs the method according to the above embodiment performed by the network node to transmit the user data from the host to the UE.
  • a further embodiment of the disclosure provides a communication system configured to provide an over-the-top service.
  • the communication system comprises a host.
  • the host comprises processing circuitry configured to provide user data for a user equipment (UE) , the user data being associated with the over-the-top service.
  • the host further comprises a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE.
  • the network node has a communication interface and processing circuitry.
  • the processing circuitry of the network node configured to perform the method according to the above embodiment performed by the network node to transmit the user data from the host to the UE.
  • a further embodiment of the disclosure provides a host configured to operate in a communication system to provide an over-the-top (OTT) service.
  • the host comprises processing circuitry configured to initiate receipt of user data.
  • the host further comprises a network interface configured to receive the user data from a network node in a cellular network.
  • the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the method according to the above embodiment performed by the network node to receive the user data from a user equipment (UE) for the host.
  • UE user equipment
  • a further embodiment of the disclosure provides a method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE) .
  • the method comprises at the host initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE.
  • the network node performs the method according to the above embodiment performed by the network node to receive the user data from the UE for the host.
  • Embodiments may allow more accurately and timely detection of whether relaying may be performed properly, and/or more precise actions may be taken depending on whether non-relayed traffic may be transmitted properly. As an example, there may be no need to release the whole Uu/PC5 link if non-relayed traffic may still be transmitted properly. Accordingly, improved performance for both relayed traffic and non-relayed traffic may be provided.
  • Figure 1 is a flowchart of a method in accordance with some embodiments.
  • Figure 2 is a flowchart of a further method in accordance with some embodiments.
  • Figure 3 is a flowchart of a still further method in accordance with some embodiments.
  • Figure 4 shows an example of a communication system QQ100 in accordance with some embodiments
  • Figure 5 shows a UE QQ200 in accordance with some embodiments
  • Figure 6 shows a network node QQ300 in accordance with some embodiments
  • Figure 7 is a block diagram of a host QQ400 in accordance with some embodiments.
  • Figure 8 is a block diagram illustrating a virtualization environment QQ500 in accordance with some embodiments.
  • Figure 9 is a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments;
  • Figure 10 schematically illustrates a telecommunication network connected via an intermediate network to a host computer
  • Figure 11 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection;
  • Figures 12 to 15 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.
  • the transmission (Tx) UE For sidelink unicast communication to a destination, the transmission (Tx) UE considers sidelink radio link failure (RLF) to be detected for the destination when any of the following conditions is met:
  • T400 is started upon transmission of RRCReconfigurationSidelink to the destination and stopped upon reception of RRCReconfigurationFailureSidelink or RRCReconfigurationCompleteSidelink from the destination.
  • MAC Medium Access Control
  • HARQ Hybrid Automatic Repeat Request
  • DTX Discontinuous Transmissions
  • PDCP sidelink Packet Data Convergence Protocol
  • SRB Sidelink Radio Bearers
  • the Tx UE When sidelink radio link failure is detected for a destination, the Tx UE releases all SLRBs of this destination, discards the NR sidelink related configuration of this destination, resets the sidelink specific MAC of this destination, and considers the PC5-RRC connection is released for the destination. If the Tx UE is in RRC connected, the UE reports to the network that a sidelink radio link failure has been declared.
  • the UE considers Uu radio link failure to be detected for the (source) Master Cell Group (MCG) , that is (source) MCG RLF, when any of the following conditions is met:
  • T310 is started upon detecting physical layer problems (for example, upon receiving N310 (where N310 is a number) consecutive out-of-sync indications from lower layers) for the PCell and stopped upon receiving N311 (where N311 is a number) consecutive in-sync indications from lower layers for the PCell or receiving of RRCReconfiguration or initiating the connection re-establishment procedure or initiating the MCG failure information procedure.
  • MCG MAC Upon random access problem indication from (source) MCG MAC. In MCG random access is only performed on PCell.
  • the UE When (source) MCG RLF is detected, the UE resets MAC for the (source) MCG and releases the (source) RRC connection.
  • DAPS Dual Active Protocol Stack
  • the UE also suspends the transmission and reception of all DRBs in the source MCG, otherwise the UE enters RRC_IDLE and performs RRC connection reestablishment.
  • a UE configured with split SRB1 or SRB3 may report MCG failures upon detection of MCG RLF when neither MCG nor Secondary Cell Group (SCG) transmission is suspended.
  • the UE may set the MCG failure type to inform the cause of RLF, e.g., whether it is due to T310 timer expiry or random access problem or maximum number of MCG RLC retransmissions has been reached or LBT failures, and so on.
  • the L3 UE to NW relay UE provides generic function that can relay any Internet Protocol (IP) Ethernet or Unstructured traffic for the remote UE where the relaying is performed in PDU layer.
  • IP Internet Protocol
  • the remote UE is invisible to the core NW, i.e., the remote UE does not have its own context and PDU session in the core NW, its traffic is forwarded in relay UE’s PDU session.
  • the L3 UE to NW relay UE allocates IPv6 prefix or IPv4 address for the remote UE.
  • remote UE traffic is only allowed to be relayed in SCell (s)
  • SCell (s) quality may already be bad while the PCell quality is still good, in this case the relay UE will not detect Uu RLF and will not provide any info about its Uu quality to the remote UE, the remote UE will continue communicating with the NW via the relay UE. This is likely to cause the remote UE performance to suffer.
  • Embodiments may provide one or more of the following technical advantage (s) .
  • Embodiments may allow more accurately and timely detection of whether relaying may be performed properly, and/or more precise actions may be taken depending on whether non-relayed traffic may be transmitted properly. As an example, there may be no need to release the whole Uu/PC5 link if non-relayed traffic may still be transmitted properly. Accordingly, improved performance for both relayed traffic and non-relayed traffic may be provided.
  • Figure 2 depicts a method in accordance with particular embodiments.
  • the method VV11 may be performed by a UE or wireless device (e.g. the UE QQ112 or UE QQ200 as described later with reference to Figures 4 and 5 respectively).
  • the method may be performed by a remote UE for link quality assessment.
  • the method begins at step VV112 with the evaluation of the quality of a first direct radio link to a relay UE, wherein the first direct link is used to transmit relay traffic that is relayed by the relay UE between the remote UE and a network node.
  • the method continues at step VV 114 with the evaluation of the quality of a second direct radio link to a relay UE, wherein the second direct link is used to transmit non-relay traffic between the remote UE and the relay UE
  • Figure 3 depicts a method in accordance with particular embodiments.
  • the method VV2 may be performed by a network node (e.g. the network node QQ110 or network node QQ300 as described later with reference to Figures 4 and 6 respectively).
  • the method may be performed by a network node for link quality management.
  • the method begins at step VV202 with the step of receiving at the network node notification that traffic relaying of traffic from a remote UE cannot be performed properly over an existing first link between the network node and a relay UE and/or an existing second link between the remote UE and the relay UE.
  • the method continues at step VV204 with the reconfiguring of the existing first and/or second link or replacing the existing first and/or second link with a new link.
  • Embodiments are described in the context of NR sidelink (SL) communications. However, most of the embodiments are in general applicable to any kind of direct communications between UEs involving device-to-device (D2D) communications such as LTE SL. Embodiments are described from a TX UE and RX UE point of view. Further, it is assumed that a SL UE and its serving gNB (if the UE is in NW coverage) operates with the same radio access technology (RAT) e.g., NR, LTE, and so on. However, all the embodiments apply without loss of meaning to any combination of RATs between the SL UE and its serving gNB.
  • RAT radio access technology
  • the link or radio link over which the signals are transmitted between at least two UEs for D2D operation is called herein as the sidelink (SL) .
  • the signals transmitted between the UEs for D2D operation are called herein as SL signals.
  • the term SL may also interchangeably be called as D2D link, V2X link, prose link, peer-to-peer link, PC5 link etc.
  • the SL signals may also interchangeably be called as V2X signals, D2D signals, prose signals, PC5 signals, peer-to-peer signals etc.
  • Embodiments are applicable to both L2 based and L3 based UE to NW relay.
  • the UE to NW relay UE is denoted as relay UE.
  • Embodiments related to PC5 interfaces are also applicable to UE to UE relay.
  • the relay UE may evaluate its Uu quality separately for Uu cell (s) /carrier (s) /bearer (s) /channel (s) where (at least) the remote UE’s Uu traffic is relayed and Uu cell (s) /carrier (s) /bearer (s) /channel (s) where (at least) the relay UE’s own Uu traffic is transmitted.
  • the relay UE may consider that its Uu link cannot be used for relaying if the Uu quality of Uu cell (s) /carrier (s) /bearer (s) /channel (s) where (at least) the remote UE’s Uu traffic is relayed becomes bad (of low quality) .
  • the relay UE may consider that its Uu link cannot be used for relaying if any one or more of the following Uu radio link conditions is met:
  • Random access problem indication from SCG MAC and the remote UE’s traffic is allowed/configured to be relayed in SCG cell (s) .
  • the LBT failure indication is from the SCell (s) on which the remote UE’s traffic is being relayed and/or allowed/configured to be relayed.
  • the relay UE may consider Uu RLF to be detected if the Uu quality of Uu cell (s) /carrier (s) /bearer (s) /channel (s) where (at least) the relay UE’s own Uu traffic is transmitted becomes bad (of low quality) .
  • the relay UE may consider MCG RLF to be detected if any one or more of the following Uu radio link conditions is met:
  • the relay UE may detect and consider separately for each of the connected remote UE (s) whether its Uu link can be used for relaying traffic from/to the remote UE. For instance, the relay UE may consider that its Uu link cannot be used for relaying traffic of a remote UE if any of the Uu radio link conditions listed above is met for that specific remote UE, while it may not consider that its Uu link cannot be used for relaying traffic of a remote UE if none of the Uu radio link conditions listed in the first embodiment is met for that specific remote UE.
  • the NW may inform the remote UE to release its Uu connection and/or the relay UE to release its Uu and/or PC5 bearer (s) /session (s) used to relay traffic for the remote UE (s) .
  • the relay UE when the relay UE detects that its Uu link cannot be used for relaying, the relay UE may inform its connected remote UE (s) using e.g., SidelinkUEAssistanceInformation message, that it cannot perform U2N relaying.
  • the relay UE may also indicate that this is due to the Uu link cannot be used for relaying, and the corresponding cause (s) .
  • the relay UE may also inform the remote UE (s) whether a suitable Uu configuration for the relay UE to perform relaying can be found.
  • the relay UE may only inform the remote UE (s) that it cannot perform relaying if the suitable Uu configuration cannot be provided.
  • the relay UE may only inform the remote UE (s) for which its Uu link cannot be used for relaying.
  • the remote UE may start to perform relay UE/cell reselection when informed by the relay UE that the relaying cannot be performed. It may start a timer when receiving such info or when starting the relay UE/cell reselection, it may stop relay UE/cell reselection, i.e., continue connects to the relay UE, if it is informed that a suitable Uu configuration can be found before the timer is expired and it has not selected another suitable relay UE or cell. If the remote UE does not find another suitable relay UE or cell and it is not informed that a suitable Uu configuration can be found before the timer is expired, the remote UE may drop its Uu connection and/or release the PC5 bearer (s) used to transmit its traffic via the relay UE.
  • PC5 bearer PC5 bearer
  • the LBT failure indication is from PC5 carrier (s) on which the remote UE is receiving/transmitting and/or allowed/configured to receive/transmit from/to the NW via relay UE.
  • the relay UE and/or the remote UE may consider that sidelink RLF to be detected for the direct link between them if the direct link quality of the carrier (s) /bearer (s) /channel (s) where (at least) the local traffic between the relay UE and the remote UE is transmitted becomes bad.
  • the relay UE/remote UE consider that sidelink RLF to be detected for the direct link between them if any of the following conditions is met (in the example conditions, the direct link is a PC5 link; other direct links may also be used) :
  • the LBT failure indication is from the PC5 carrier (s) on which the local traffic between the relay UE and the remote UE is being transmitted and/or allowed/configured to be transmitted.
  • relay UE1 when relay UE1 (or remote UE1) detects that the PC5 link to remote UE 2 (or relay UE 2) cannot be used for relaying traffic of remote UE2 (or remote UE1) , relay UE1 (or remote UE1) may report this to the NW.
  • the report may be sent in e.g. SidelinkUEinformation or UEAssistanceInformation message.
  • Relay UE1 (or remote UE1) may also indicate the cause due to which the PC5 link cannot be used for relaying, and the ID of remote UE2 (or the ID of relay UE2) associated to the PC5 link.
  • the NW may reconfigure the PC5 link and/or switch remote UE2 (or remote UE1) to another path so that remote UE2 (or remote UE1) can continue to communicate with the NW properly either via relay UE1 (or relay UE2) or via another different path.
  • the NW may only switch remote UE2 (or remote UE1) to another path if the NW cannot find a suitable PC5 configuration for relay UE1 (or relay UE2) to perform the relaying over the PC5 link.
  • the NW may inform remote UE2 (or remote UE1) to release its connection to the NW and/or relay UE1 (or relay UE2) to release its PC5 bearer (s) used to relay traffic for remote UE2 (or remote UE1) .
  • the relay UE may perform the reconfiguration on itself or according to configurations provided by the NW.
  • the relay UE may inform the remote UE whether such configuration can be found.
  • the relay UE may only do this if a suitable PC5 configuration for the remote UE to continue communication with the NW properly via the relay UE cannot be found.
  • the relay UE may also indicate that this is due to the PC5 link cannot be used for relaying and the corresponding cause (s) .
  • the relay UE may only send this info to the remote UE if the suitable PC5 configuration cannot be found.
  • the remote UE may start to perform relay UE/cell reselection when receiving an indication including information from the relay UE. It may start a timer when receiving the info or when starting the relay/cell reselection, it may stop relay UE/cell reselection, i.e., continue connects to the relay UE, if it is informed that a suitable PC5 configuration can be found before the timer is expired and it has not selected another suitable relay UE or cell. If the remote UE does not find another suitable relay UE or cell and it is not informed that a suitable PC5 configuration can be found before the timer is expired, the remote UE may release the PC5 bearer (s) used to transmit its traffic via the relay UE.
  • PC5 bearer s
  • the remote UE may perform the reconfiguration on itself or according to configurations provided by the NW.
  • PC5 bearer (s) used to transmit traffic of the remote UE via the relay UE.
  • the remote UE may only do this if a suitable PC5 configuration for the remote UE to continue communication with the NW properly via the relay UE cannot be found.
  • the remote UE may also indicate the corresponding cause (s) .
  • the remote UE may only send this info to the relay UE if the suitable PC5 configuration cannot be found. When receiving such info the relay UE may release the PC5 bearer (s) used to relay the traffic of the remote UE.
  • any signaling between UE and the gNB may include one or more of:
  • a protocol layer e.g., SDAP, PDCP, RLC, or an adaptation layer in case of SL relay
  • any signaling between UEs may include one or more of:
  • Figure 4 shows an example of a communication system QQ100 in accordance with some embodiments.
  • the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN) , and a core network QQ106, which includes one or more core network nodes QQ108.
  • the access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110) , or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes QQ110 facilitate direct or indirect connection of user equipment (UE) , such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes QQ110 and other communication devices.
  • the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network QQ102.
  • the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC) , Mobility Management Entity (MME) , Home Subscriber Server (HSS) , Access and Mobility Management Function (AMF) , Session Management Function (SMF) , Authentication Server Function (AUSF) , Subscription Identifier De-concealing function (SIDF) , Unified Data Management (UDM) , Security Edge Protection Proxy (SEPP) , Network Exposure Function (NEF) , and/or a User Plane Function (UPF) .
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and/or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider.
  • the host QQ116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system QQ100 of Figure 4 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LEW AN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long
  • the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC) /Massive IoT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs QQ112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104.
  • a UE may be configured for operating in single-or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC) , such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio –Dual Connectivity (EN-DC) .
  • MR-DC multi-radio dual connectivity
  • the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the processing circuitry QQ202 may be operable to provide, either alone or in conjunction with other UE QQ200 components, such as the memory QQ210, UE QQ200 functionality.
  • the processing circuitry QQ202 may be configured to cause the UE QQ202 to perform the methods as described with reference to Figure 1 or Figure 2.
  • the input/output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE QQ200.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source QQ208 is structured as a battery or battery pack.
  • Other types of power sources such as an external power source (e.g., an electricity outlet) , photovoltaic device, or power cell, may be used.
  • the power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.
  • the UICC may for example be an embedded UICC (eUICC) , integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card. ’
  • the memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.
  • the processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212.
  • the communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222.
  • the communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network) .
  • Each transceiver may include a transmitter QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth) .
  • the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • LoT Internet of Things
  • Non-limiting examples of such an loT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item ⁇ tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot.
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs) , sometimes referred to as Remote Radio Heads (RRHs) .
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS) .
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs) , Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs) ) , and/or Minimization of Drive Tests (MDTs) .
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location
  • the processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, network node QQ300 functionality.
  • the processing circuitry QQ302 may be configured to cause the network node to perform the methods as described with reference to Figure 3.
  • the processing circuitry QQ302 includes a system on a chip (SOC) .
  • the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314.
  • the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips) , boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.
  • the memory QQ304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM) , read-only memory (ROM) , mass storage media (for example, a hard disk) , removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD) ) , and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry QQ302.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM) , read-only memory (ROM) , mass storage media (for example, a hard disk) , removable storage media (for example, a flash drive, a Compact Disk (CD) or a
  • the memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300.
  • the memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306.
  • the processing circuitry QQ302 and memory QQ304 is integrated.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302.
  • the radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322.
  • the radio signal may then be transmitted via the antenna QQ310.
  • the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318.
  • the digital data may be passed to the processing circuitry QQ302.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown) , and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown) .
  • the antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.
  • the antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component) .
  • the power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein.
  • the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308.
  • the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • FIG 7 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 4, in accordance with various aspects described herein.
  • the host QQ400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host QQ400 may provide one or more services to one or more UEs.
  • the host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412.
  • processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures QQ2 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.
  • the memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE.
  • Embodiments of the host QQ400 may utilize only a subset or all of the components shown.
  • the host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC) , High Efficiency Video Coding (HEVC) , Advanced Video Coding (AVC) , MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC) , MPEG, G. 711) , including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems) .
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG MPEG
  • VP9 Video Coding
  • audio codecs e.g., FLAC, Advanced Audio Coding (AAC) , MPEG, G. 711
  • UEs e.g., handsets, desktop computers, wearable display systems, heads-up display systems
  • the host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP) , Real-Time Streaming Protocol (RTSP) , Dynamic Adaptive Streaming over HTTP (MPEG-DASH) , etc.
  • Figure 8 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.
  • VMs virtual machines
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • radio connectivity e.g., a core network node or host
  • Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc. ) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware QQ504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs) ) , provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508) , and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.
  • the VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506.
  • Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV) .
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.
  • Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas.
  • Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 9 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.
  • host QQ602 Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection QQ650.
  • the network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606.
  • the connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network QQ106 of Figure QQ1
  • one or more other intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602.
  • an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection QQ650 may transfer both the request data and the user data.
  • the UE's client application may interact with
  • the OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606.
  • the connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host QQ602 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE QQ606.
  • the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction.
  • the host QQ602 initiates a transmission carrying the user data towards the UE QQ606.
  • the host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606.
  • the request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606.
  • the transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.
  • the UE QQ606 executes a client application which provides user data to the host QQ602.
  • the user data may be provided in reaction or response to the data received from the host QQ602.
  • the UE QQ606 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604.
  • step QQ620 in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve link management and thereby provide benefits such as improved performance for relayed and non-relayed traffic.
  • factory status information may be collected and analyzed by the host QQ602.
  • the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights) .
  • the host QQ602 may store surveillance video uploaded by a UE.
  • the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices) , or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and/or UE QQ606.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.
  • a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE) 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown) .
  • the communication system of Figure 32 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • the host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311, which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Figure 33) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • connection 3360 may be direct or it may pass through a core network (not shown in Figure 33) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to.
  • Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 33 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of Figure 32, respectively.
  • the inner workings of these entities may be as shown in Figure 33 and independently, the surrounding network topology may be that of Figure 32.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the use equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network) .
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment.
  • the teachings of these embodiments may allow more accurately and timely detection of whether relaying may be performed properly, and/or more precise actions may be taken depending on whether non-relayed traffic may be transmitted properly. As an example, there may be no need to release the whole Uu/PC5 link if non-relayed traffic may still be transmitted properly. Accordingly, improved performance for both relayed traffic and non-relayed traffic may be provided.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • FIGURE 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • FIGURE 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section.
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 10 and 11. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Landscapes

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

Abstract

L'invention concerne des procédés et des appareils d'évaluation de qualité de liaison et/ou de gestion de qualité de liaison. Un procédé mis en œuvre par un EU relais comprend l'évaluation de la qualité d'une première liaison, la première liaison étant utilisée pour transmettre un premier trafic. Le premier trafic est un trafic de relais qui est relayé par l'EU relais entre un EU distant et un nœud de réseau. Le procédé comprend en outre l'évaluation de la qualité d'une seconde liaison, la seconde liaison étant utilisée pour transmettre un second trafic. Le second trafic est un trafic non relais entre l'EU relais et l'EU distant ou le nœud de réseau.
PCT/CN2022/139345 2022-01-29 2022-12-15 Évaluation de qualité de liaison distincte pour trafic relayé et non relayé WO2023142758A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2022075032 2022-01-29
CNPCT/CN2022/075032 2022-01-29

Publications (1)

Publication Number Publication Date
WO2023142758A1 true WO2023142758A1 (fr) 2023-08-03

Family

ID=87470377

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/139345 WO2023142758A1 (fr) 2022-01-29 2022-12-15 Évaluation de qualité de liaison distincte pour trafic relayé et non relayé

Country Status (1)

Country Link
WO (1) WO2023142758A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011101266A1 (fr) * 2010-02-17 2011-08-25 Alcatel Lucent Calibrage d'une liaison terrestre
CN107432049A (zh) * 2015-03-31 2017-12-01 株式会社Ntt都科摩 用户装置
CN113784385A (zh) * 2020-06-10 2021-12-10 华为技术有限公司 一种通信方法及相关装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011101266A1 (fr) * 2010-02-17 2011-08-25 Alcatel Lucent Calibrage d'une liaison terrestre
CN107432049A (zh) * 2015-03-31 2017-12-01 株式会社Ntt都科摩 用户装置
CN113784385A (zh) * 2020-06-10 2021-12-10 华为技术有限公司 一种通信方法及相关装置

Similar Documents

Publication Publication Date Title
CN111345061B (zh) 通过ran接口的通知控制
US12004250B2 (en) Packet data convergence protocol data recovery
WO2019097481A1 (fr) Échange d'informations pour un accès initial à un équipement utilisateur
US11792693B2 (en) Methods and apparatuses for redirecting users of multimedia priority services
WO2021029811A1 (fr) Défaillance de liaison radio de liaison latérale
EP4335138A1 (fr) Gestion de trafic de réseau
WO2023048628A1 (fr) Procédés, appareil et supports lisibles par ordinateur relatifs à des services à faible latence dans des réseaux sans fil
WO2023048627A1 (fr) Procédés, appareil et supports lisibles par ordinateur liés à des services à faible latence dans des réseaux sans fil
WO2023285937A1 (fr) Procédé et appareil de configuration inter-domaine de réseaux sensibles au temps
WO2023142758A1 (fr) Évaluation de qualité de liaison distincte pour trafic relayé et non relayé
WO2023221553A9 (fr) Procédé et appareil de gestion de défaillance de liaison radio pendant une commutation de trajet
CN115065440B (zh) 避免通过5g nas传输来传输的信令的多次重传
WO2024014998A1 (fr) Procédés et appareils pour améliorer l'agrégation de porteuses et la double connectivité pour une économie d'énergie de réseau
WO2023073643A1 (fr) Positionnement de liaison latérale basé sur la diffusion de groupe
WO2024028832A1 (fr) Signalisation de groupe pour économies d'énergie de réseau
WO2024096795A1 (fr) Procédés et appareils de gestion de groupe de cellules secondaires lors de l'exécution d'un commutateur de cellule de mobilité déclenché par couche 1/couche 2
WO2024072273A1 (fr) Coordination inter-nœuds de configurations rvqoe concurrentes dans mr-dc
WO2023156595A1 (fr) Gestion de communications multidiffusion
WO2023007022A1 (fr) Procédés et appareils de commande de rapport de charge
WO2023182910A1 (fr) Journalisation de mesure par un dispositif de communication
WO2023069006A1 (fr) Ue, nœuds de réseau et procédés de gestion de configurations de qualité d'expérience
WO2024005704A1 (fr) Gestion de configurations de référence
WO2024072280A1 (fr) Procédés et appareils pour fournir une indication de capacité restreinte d'un équipement utilisateur de module d'identité d'abonné multi-universel à un réseau
WO2023132768A1 (fr) Procédé et appareils pour gérer un fonctionnement à plusieurs porteuses lorsqu'un second groupe de cellules est désactivé
WO2023014266A1 (fr) Procédés et appareils permettant des transmissions de petites données à autorisation configurée dans un réseau de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22923544

Country of ref document: EP

Kind code of ref document: A1