[go: up one dir, main page]

WO2023025384A1 - Création de rapport d'état de ressource - Google Patents

Création de rapport d'état de ressource Download PDF

Info

Publication number
WO2023025384A1
WO2023025384A1 PCT/EP2021/073541 EP2021073541W WO2023025384A1 WO 2023025384 A1 WO2023025384 A1 WO 2023025384A1 EP 2021073541 W EP2021073541 W EP 2021073541W WO 2023025384 A1 WO2023025384 A1 WO 2023025384A1
Authority
WO
WIPO (PCT)
Prior art keywords
reporting
entity
satisfied
measurement value
condition
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2021/073541
Other languages
English (en)
Inventor
Magnus DEGERFALK
Stefan Johansson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/EP2021/073541 priority Critical patent/WO2023025384A1/fr
Publication of WO2023025384A1 publication Critical patent/WO2023025384A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0958—Management thereof based on metrics or performance parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/086—Load balancing or load distribution among access entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • This disclosure relates to resource status reporting.
  • a resource status reporting procedure is used by a first network entity to request a second network entity (e.g., a neighboring network node) (a.k.a., the “reporting entity”) to report the result of one or more measurements.
  • this procedure can be used by a fist Next Generation (NG) Radio Access Network (RAN) (NG-RAN) node to request a second NG-RAN node to report load measurements (e.g., the average number of active user equipments (UEs)) within a sampling period).
  • NG Next Generation
  • RAN Radio Access Network
  • load measurements e.g., the average number of active user equipments (UEs)
  • the first network entity can initiate the procedure by sending a resource status start message to the reporting entity requesting that the reporting entity periodically provide to the first network entity requested resource status information (i.e., one more measurement values). If, the second network entity is capable to provide the requested resource status information, the second network entity shall initiate the measurements as requested and respond with a response message. To periodically provide the requested information to the first network entity (a.k.a., the “requesting entity”), the reporting entity transmits periodically to the requesting entity a status update message comprising the requested information.
  • a requesting entity may request many reporting entities to periodically provide requested information, which means that the number of status update message transmitted to the requesting entity within a given window of time may be quite large. Additionally, the measurement values included in a status update message may be of little value to the requesting entity if the measurement values have not changed significantly since the last status update message was sent.
  • a method performed by a reporting entity for reporting one or more measurement values to a requesting entity includes obtaining a first measurement value, VI, for a first measurement object.
  • the method also includes obtaining a second measurement value, V2, for the first measurement object.
  • the method also includes determining that a reporting condition is satisfied.
  • the method further includes, as a result of determining that the reporting condition is satisfied, reporting V2 to the requesting entity.
  • the step of determining that the reporting condition is satisfied comprises comparing AV to a first reporting threshold, Tl, wherein AV is a function of a difference between V2 and VI.
  • a computer program comprising instructions which when executed by processing circuitry of a reporting entity causes the reporting entity to perform any of the methods disclosed herein.
  • a carrier containing the computer program wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.
  • a reporting entity In another aspect there is provided a reporting entity.
  • the reporting is operative to obtain a first measurement value, VI, for a first measurement object and to obtain a second measurement value, V2, for the first measurement object.
  • the reporting is further operative to determine whether a reporting condition is satisfied; and, as a result of determining that the reporting condition is satisfied, report V2 to the requesting entity.
  • the reporting entity is operative to determine whether the reporting condition is satisfied by performing a process that comprises comparing AV to a first reporting threshold, Tl, wherein AV is a function of a difference between V2 and VI.
  • a reporting entity comprises processing circuitry and a memory (642).
  • the memory contains instructions executable by the processing circuitry, wherein the reporting entity is operative to obtain a first measurement value, VI, for a first measurement object and to obtain a second measurement value, V2, for the first measurement object.
  • the reporting entity is further operative to determine whether a reporting condition is satisfied and, as a result of determining that the reporting condition is satisfied, report V2 to the requesting entity.
  • the reporting entity is operative to determine whether the reporting condition is satisfied by performing a process that comprises comparing AV to a first reporting threshold, Tl, wherein AV is a function of a difference between V2 and VI.
  • An advantage of the embodiments disclosed herein is that they provide a mechanism that gives needed precision and frequency of updates while using less resources to do so. It is adaptive and configurable to the specific need of precision for the user. This means that without sacrificing the precision or quality of measurements, updates can be sent less frequently when the measurement has not changed enough. This gives lower the network utilization for distributing resource utilization information between the nodes.
  • FIG. 1 illustrates a requesting entity communicating with a reporting entity.
  • FIG. 2 illustrates a system comprising a plurality of nodes where each node can be a reporting entity and/or a requesting entity.
  • FIG. 3 illustrates a system comprising a central unit communicating with a number of distributed units.
  • FIG. 4 is a flowchart illustrating a process according to some embodiments.
  • FIG. 5 is a flowchart illustrating a process according to some embodiments.
  • FIG. 6 is a block diagram of a reporting entity according to some embodiments.
  • FIG. 1 illustrates a requesting entity 102 communicating with a reporting entity 104.
  • Both the requesting entity and the reporting entity may be a network node of an access network (e.g., a radio access network (RAN), such as a Next Generation (NG) RAN specified by the Third Generation Partnership Project (3GPP)).
  • RAN radio access network
  • NG Next Generation
  • 3GPP Third Generation Partnership Project
  • the requesting entity is a first base station and the reporting entity is a second base station.
  • FIG. 2 illustrates a system 200 comprising a plurality of nodes (e.g., RAN nodes), where each node can be a reporting entity and/or a requesting entity.
  • nodes e.g., RAN nodes
  • each node is a reporting entity, it is possible that a large number of status update messages are transmitted within a certain window of time, which could overload or create congestion in the network 202 connecting the nodes together.
  • the requesting entity is a central unit (CU) of a base station and the reporting entity is distributed unit (DU) of the base station.
  • CU central unit
  • DU distributed unit
  • FIG. 3 shows a CU 302 communicating with many DUs. If each DU is a reporting entity, it is possible that a large number of status update messages are transmitted to CU 302 within a certain window of time, which could overload the network 302 connecting the DUs to CU 302.
  • FIG. 1 shows requesting entity 102 transmitting to reporting entity 104 a resource status request message 191 (or simply message 191 for short).
  • requesting entity 102 may transmit message 191 directly to reporting entity 104 (e.g., the entities may be connected to the same Local Area Network (LAN) segment) or requesting entity 102 may transmit message 191 indirectly to reporting entity 104 (i.e., one or more relay nodes may by employed to relay the message from requesting entity 102 to reporting entity 104).
  • reporting entity 104 transmits to requesting entity 102 a response message 192.
  • reporting entity 104 obtains the requested measurement value(s) (step si 99) and then transmits to requesting entity 102 a status update message 193 containing the obtained measurement value(s). These last two steps may be repeated on a periodic basis (e.g., between 500 milliseconds (ms) and 10 seconds (s)).
  • a problem with having the reporting entity perform the obtaining step and the status update message transmitting step on a periodic basis is that the resulting status update message may be of marginal value to the requesting entity.
  • the total resources are known, so multiplying that by AR (i.e., the available resource for the another user) gives an estimated number for the resources available for a new user.
  • AR (1/(1 + N)
  • requesting entity 102 may include in the resource status request message 191 first threshold information that specifies a first reporting threshold (Tl) or enables reporting entity 104 to calculate Tl, wherein reporting entity 104 should use Tl, the previously reported measurement value (denoted VI), and the newly obtained measurement value (V2) to determine whether or not the newly obtained measurement value (V2) should be reported to requesting entity 102.
  • first threshold information that specifies a first reporting threshold (Tl) or enables reporting entity 104 to calculate Tl, wherein reporting entity 104 should use Tl, the previously reported measurement value (denoted VI), and the newly obtained measurement value (V2) to determine whether or not the newly obtained measurement value (V2) should be reported to requesting entity 102.
  • reporting entity 104 refrains from sending a status update message that includes V2, where abs(N) is a function that returns the absolute value of N.
  • reporting entity 104 will send to requesting entity 102 a status update message that includes V2.
  • T2 second reporting threshold
  • reporting entity 104 refrains from sending a status update message that includes V2. In this manner, by introducing such a reporting threshold, reporting entity 104 will refrain some sending to requesting entity 102 a status update message that has little or no value to requesting entity 102.
  • FIG. 4 is a flowchart illustrating a process 400 according to some embodiments.
  • Process 400 is performed by reporting entity 104 and may begin with step [0025]
  • Step s402 comprises the reporting entity obtaining a measurement value, for a first measurement object.
  • Step s404 (optional) comprises the reporting entity reporting the obtained measurement value to requesting entity 102 (this reported measurement value is named VI).
  • Step s406 comprises the reporting entity obtaining a new measurement value (named V2) for the first measurement object.
  • Step s408 comprises the reporting entity determining whether a reporting condition is satisfied. If the reporting condition is not satisfied, then process 400 may return to step s406 where a new measurement value is obtained, otherwise process 400 proceeds to step s410.
  • Step s410 comprises the reporting entity, as a result of determining that the reporting condition is satisfied, reporting the new measurement value (i.e., the most recently obtained measurement value, which we denote asV2) to the requesting entity.
  • the step of determining that the reporting condition is satisfied comprises comparing AV to a first reporting threshold (Tl), wherein AV is a function of a difference between the most recently obtained measurement value (i.e., V2) and the most recently reported measurement value (i.e., VI).
  • Tl first reporting threshold
  • process 400 may go back to step 406, where a new measurement value is obtained.
  • the process further includes the reporting entity reporting VI to the requesting entity, wherein VI is reported to the requesting entity at a first point in time, tl, and determining that the reporting condition is satisfied further comprises comparing At to a second reporting threshold (T2), wherein At represents the amount of time between tl and t2, wherein t2 is the time at which V2 was obtained or a time after the time at which V2 was obtained, and the reporting condition is satisfied if At is greater than T2 and AV is greater than Tl .
  • T2 second reporting threshold
  • the process further includes receiving a status request or update message transmitted by the requesting entity, wherein the status request or update message indicates the first reporting threshold (Tl). In some embodiments, the status request or update message further indicates the second reporting threshold (T2). In some embodiments, the status request or update message further indicates the measurement object.
  • the requesting entity is a first radio access network, RAN, node; and the reporting entity is a second RAN node.
  • the requesting entity is a Central Unit, CU, of a radio access network, RAN, node; and the reporting entity is a Distributed Unit, DU, of the RAN node.
  • the reporting condition is satisfied if AV is greater than Tl.
  • AV is equal to one of: (V2 - VI), (V1-V2), abs(V2- VI), or abs(V2-Vl)/Vl.
  • FIG. 5 is a flowchart illustrating a process 500 according to some embodiments.
  • Process 500 is performed by reporting entity 104 and may begin with step s502.
  • Step s502 comprises reporting entity 104 receiving resource status request message 191 transmitted by requesting entity 102.
  • message 191 includes at least Tl and may also include T2 (or it may include information enabling reporting entity 104 to determine Tl and T2) and it includes information identifying a measurement object.
  • N a certain window of time
  • each measurement value is the number of UEs for a certain data radio bearer (DRB) and a certain cell for which there is downlink (DL) data available for transmission.
  • each measurement value is the number of UEs for the DRB and the cell for which there is uplink (UL) data available for transmission.
  • DRB data radio bearer
  • DL downlink
  • UL uplink
  • Step s508 comprises reporting entity 104 obtaining an average measurement value (Av).
  • Step s510 comprises reporting entity 104 determining whether a reporting condition is satisfied.
  • determining whether the reporting condition is satisfied comprises the reporting entity 104 determining whether (abs(Av - R))/R > Tl or (abs(Av - R))/R > Tl.
  • the reporting entity determines that the reporting condition is satisfied and process 500 goes to step s512, otherwise, if the reporting condition is not satisfied (e.g., abs(Av - R))/R ⁇ Tl), then process 500 goes back to step s506.
  • determining whether the reporting condition is satisfied further comprises the reporting entity 104 determining whether more than a threshold amount of time (T2) has elapsed since the last time that step s512 was performed. In some embodiments, the reporting condition is satisfied if more than the threshold amount of time (T2) has elapsed since the last time that step s512 was performed.
  • Step s512 comprises reporting entity 104 sending to requesting entity 102 a status update message containing Av.
  • message 191 may include the threshold values Tl and T2 (or it may include information enabling reporting entity 104 to determine Tl and T2) and information identifying one or more measurement objects.
  • message 191 may also include additional information.
  • message 191 may include any one of the information elements shown below in table 1 :
  • requesting entity 102 is a CU (e.g., CU 302) and reporting entity 104 is a DU.
  • requesting entity 102 is a first network node (e.g., a first base station) and reporting entity 104 is a second network node (e.g., a second base station) that comprises CU 302 and multiple DUs.
  • the resource status request message transmitted in step s502 may contain a request for measurements on many different cells, and the cells can belong to different DUs controlled by CU 302.
  • CU 302 must set up subscriptions to the DUs containing the cells that are to be measured (e.g., CU 302 sends a resource status request message to each DU that serves one of the cells that are to be measured).
  • CU 302 functions a requesting entity 102 with respect to the DUs and functions as a reporting entity with respect to the first network node.
  • CU 302 may receive such a request from multiple requesting entities 102, and must set up subscriptions to the DUs containing the cells that are to be measured (e.g., CU 302 sends a resource status request message to each DU that serves one of the cells that are to be measured).
  • These different requests received by CU 302 may contain different thresholds (e.g., each request may have a different T1 threshold). In this scenario, the CU keeps track of the different thresholds from all incoming requests. The one with the lowest threshold determines the threshold that CU 302 provides to the DUs.
  • CU 302 receives a first request from a first requesting entity with threshold Tla and a second request from a different requesting entity with threshold Tib, where Tla > Tib.
  • CU 302 will send to each DU serving a cell to be measured a request that contains the threshold Tib.
  • CU 302 when CU 302 receives from a DU a status update message containing the requested measurement value, CU 302 will send at least to the first requesting entity a status update message containing the measurement value received from the DU because the reporting condition will necessarily be satisfied for the first requesting entity, and CU 302 will send to the second requesting entity a status update message containing the measurement value only after CU 302 determines, based on the current measurement value and the measurement value most recently reported to the second requesting entity, that the second requesting entity’s reporting condition is satisfied. That is, when a DU sends an updated measurement CU must keep track of all receivers that wants this information, and apply the appropriate threshold condition and see what neighbor that should get the updated value. Additionally, CU may get one resource status update per DU and CU will aggregate these into a common resource status update to send to the requesting entity that requested the resource status update of cells from many DUs.
  • FIG. 6 is a block diagram of reporting entity 104, according to some embodiments.
  • reporting entity 104 may comprise: processing circuitry (PC) 602, which may include one or more processors (P) 655 (e.g., a general purpose microprocessor and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (i.e., reporting entity 104 may be a distributed computing apparatus); at least one network interface 648 comprising a transmitter (Tx) 645 and a receiver (Rx) 647 for enabling reporting entity 104 to transmit data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network) to which network interface 648 is connected (directly or indirectly) (e.g., network interface 648 may be wirelessly connected to the network 110, in which
  • IP Internet Protocol
  • the network interface 648 may be connected to the network 110 over a wired connection, for example over an optical fiber or a copper cable.
  • a computer program product (CPP) 641 may be provided.
  • CPP 641 includes a computer readable medium (CRM) 642 storing a computer program (CP) 643 comprising computer readable instructions (CRI) 644.
  • CRM 642 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like.
  • the CRI 644 of computer program 643 is configured such that when executed by PC 602, the CRI causes reporting entity 104 to perform steps of the methods described herein (e.g., steps described herein with reference to one or more of the flow charts).
  • reporting entity 104 may be operative to perform steps of the methods described herein without the need for code. That is, for example, PC 602 may consist merely of one or more ASICs.
  • the features of the embodiments described herein may be implemented in hardware and/or software.
  • the data storage system 608, the processing circuitry 602 and the network interface 648 are connected in series.
  • elements 608, 602 and 648 may be connected to a bus.
  • the reporting entity 104 is operative to obtain a first measurement value (VI) for a first measurement object.
  • Reporting entity 104 is further operative to obtain a second measurement value (V2) for the first measurement object.
  • Reporting entity 104 is further operative to determine whether a reporting condition is satisfied. Reporting entity 104 is further operative such that as a result of determining that the reporting condition is satisfied, reporting entity 104 reports V2 to the requesting entity. The reporting entity 104 is operative to determine whether the reporting condition is satisfied by performing a process that comprises comparing AV to a first reporting threshold (Tl), wherein AV is a function of a difference between V2 and VI.
  • Tl first reporting threshold

Landscapes

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

Abstract

Procédé (400) exécuté par une entité de création de rapport (104) pour créer un rapport relatif à une ou plusieurs valeurs de mesure pour une entité de demande (102). Le procédé consiste à obtenir (s402) une première valeur de mesure, V1, pour un premier objet de mesure. Le procédé consiste également à obtenir (s406) une seconde valeur de mesure, V2, pour le premier objet de mesure. Le procédé consiste également à déterminer (s408) qu'une condition de création de rapport est satisfaite. Le procédé consiste en outre, à la suite de la détermination selon laquelle la condition de création de rapport est satisfaite, à créer un rapport (s410) relatif à V2 pour l'entité de demande. L'étape de détermination selon laquelle la condition de création de rapport est satisfaite consiste à comparer ΔV à un premier seuil de création de rapport, T1, ΔV étant une fonction d'une différence entre V2 et V1.
PCT/EP2021/073541 2021-08-25 2021-08-25 Création de rapport d'état de ressource Ceased WO2023025384A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/073541 WO2023025384A1 (fr) 2021-08-25 2021-08-25 Création de rapport d'état de ressource

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/073541 WO2023025384A1 (fr) 2021-08-25 2021-08-25 Création de rapport d'état de ressource

Publications (1)

Publication Number Publication Date
WO2023025384A1 true WO2023025384A1 (fr) 2023-03-02

Family

ID=77640696

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/073541 Ceased WO2023025384A1 (fr) 2021-08-25 2021-08-25 Création de rapport d'état de ressource

Country Status (1)

Country Link
WO (1) WO2023025384A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025071456A1 (fr) * 2023-09-27 2025-04-03 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils de rapport périodique pour métriques à taux de génération variables
WO2025170497A1 (fr) * 2024-02-08 2025-08-14 Telefonaktiebolaget Lm Ericsson (Publ) Envoi d'un message à un nœud de réseau

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180367273A1 (en) * 2017-06-16 2018-12-20 Kyungmin Park Distributed Unit Status Information
WO2021089519A1 (fr) * 2019-11-07 2021-05-14 Nokia Technologies Oy Rapport basé sur un seuil à des fins de prise en charge de commande d'admission efficace de réseaux sans fil
WO2022031198A1 (fr) * 2020-08-05 2022-02-10 Telefonaktiebolaget Lm Ericsson (Publ) Signalement de ressources inter-systèmes

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180367273A1 (en) * 2017-06-16 2018-12-20 Kyungmin Park Distributed Unit Status Information
WO2021089519A1 (fr) * 2019-11-07 2021-05-14 Nokia Technologies Oy Rapport basé sur un seuil à des fins de prise en charge de commande d'admission efficace de réseaux sans fil
WO2022031198A1 (fr) * 2020-08-05 2022-02-10 Telefonaktiebolaget Lm Ericsson (Publ) Signalement de ressources inter-systèmes

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3 Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 16)", vol. RAN WG3, no. V16.6.0, 1 July 2021 (2021-07-01), pages 1 - 464, XP052029990, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/38_series/38.423/38423-g60.zip 38423-g60.doc> [retrieved on 20210701] *
HUAWEI: "Event triggered reporting for inter RAT MLB", 3GPP DRAFT; R3-103277 EVENTS FOR INTER RAT MLB, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Jacksonville, USA; 20101115, 8 November 2010 (2010-11-08), XP050466284 *
HUAWEI: "Event triggered reporting for MLB", 3GPP DRAFT; R3-102720 EVENTS FOR MLB SIGNALLING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Xi'an; 20101011, 1 October 2010 (2010-10-01), XP050453461 *
KYOCERA CORP: "Enhancements for cell load reporting", vol. RAN WG3, no. Chicago; 20130415 - 20130419, 6 April 2013 (2013-04-06), XP050700695, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_79bis/Docs/> [retrieved on 20130406] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025071456A1 (fr) * 2023-09-27 2025-04-03 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils de rapport périodique pour métriques à taux de génération variables
WO2025170497A1 (fr) * 2024-02-08 2025-08-14 Telefonaktiebolaget Lm Ericsson (Publ) Envoi d'un message à un nœud de réseau

Similar Documents

Publication Publication Date Title
US11026239B2 (en) Method and user equipment for predicting available throughput for uplink data
TWI643479B (zh) 網路切片方法和使用所述方法的用戶設備及基地台
US9648498B2 (en) Method and apparatus for controlling network access of UE in wireless communication system
TWI710279B (zh) 端到端傳輸數據的方法、設備和系統
JP6929974B2 (ja) 通信モード切り替え方法、ネットワーク側デバイスおよび端末デバイス
US10205668B2 (en) Video data transmission method and related device
US10314093B2 (en) Selection between cellular communication link and device-to-device (D2D) communication link for communication between user equipment (UE) devices
US9736702B2 (en) System and method for quality of service control
US20230239906A1 (en) Cooperative distributed scheduling for device-to-device (d2d) communication
US20160173408A1 (en) Data transmission method using multiple wireless networks
WO2023025384A1 (fr) Création de rapport d&#39;état de ressource
WO2018202137A1 (fr) Procédé de communication et dispositif
CN107371179B (zh) 测量结果上报方法、测量结果接收方法、相关设备和系统
EP4473781A1 (fr) Schémas de positionnement de liaison latérale dans des communications sans fil
CN109644393A (zh) 一种数据发送方法和装置
CN103095431B (zh) 参考信号处理的方法和装置
WO2020192766A1 (fr) Procédés, dispositif terminal et station de base utilisés pour l&#39;attribution de ressource
CN114978256B (zh) 一种无蜂窝大规模mimo系统、调整方法及调整装置
JP2018098699A (ja) 通信制御装置、通信システム、及び通信方法
US20230162006A1 (en) Server and agent for reporting of computational results during an iterative learning process
CN115811706B (zh) 信道状态参数的传输方法和通信装置
CN116489717A (zh) 资源选择方法、装置及设备
TWI687067B (zh) 無線通信方法和裝置
US20150372919A1 (en) Systems and methods for enhanced signaling for beacon load reduction
CN120548482A (zh) 用于联合通信和感知的设备、系统和方法

Legal Events

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

Ref document number: 21765940

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21765940

Country of ref document: EP

Kind code of ref document: A1