[go: up one dir, main page]

WO2025011809A1 - Acquisition d'informations d'interconnectivité de nœuds de réseau - Google Patents

Acquisition d'informations d'interconnectivité de nœuds de réseau Download PDF

Info

Publication number
WO2025011809A1
WO2025011809A1 PCT/EP2024/064330 EP2024064330W WO2025011809A1 WO 2025011809 A1 WO2025011809 A1 WO 2025011809A1 EP 2024064330 W EP2024064330 W EP 2024064330W WO 2025011809 A1 WO2025011809 A1 WO 2025011809A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
network
node
nodes
connectivity information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2024/064330
Other languages
English (en)
Inventor
Martin Kollár
Hakon Helmers
Ling Yu
Irina-Mihaela BALAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Solutions and Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Publication of WO2025011809A1 publication Critical patent/WO2025011809A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/026—Multicasting of data during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • Various example embodiments relate to wireless communications.
  • a network deployment may comprise, in general, a master node connected to a core network and set of secondary nodes. Each secondary node may be connected to the master node directly. But after the change of master node due to e.g. mobility, the previous secondary node may not have direct connection with the latest master node. In such a scenario, the master node may not be aware of the previous secondary nodes not directly connected to it, that is, it may only have knowledge of its neighboring secondary nodes, but not the connectivity with the neighboring secondary nodes and the connected network nodes of the secondary nodes.
  • the master node needs to transmit information (e.g., a random access channel, RACH, report or other self-organizing network, SON, related report) to any one of the secondary nodes in the second set, the master node needs to transmit the information to all of the neighboring secondary nodes to ensure that the information will eventually be forwarded to the targeted secondary node.
  • information e.g., a random access channel, RACH, report or other self-organizing network, SON, related report
  • This way of communication is not only inefficient but may also lead to problems at the targeted secondary node especially if there exists multiple ways of forming a connection from the master node to the targeted secondary node and thus multiple instances of the same information are received at the targeted secondary node.
  • Figure 1 illustrates a system to which some embodiments may be applied
  • Figure 2 illustrates an exemplary network deployment for dual connectivity to which some embodiments may be applied
  • Figures 3A, 3B, 4A, 4B and 5 illustrate processes according to some embodiments
  • Figures 6 illustrates signalling between a master node and secondary nodes according to some embodiments.
  • Figure 7 illustrates an apparatus according to some embodiments.
  • the term “tree structure” may refer to a (hierarchical) tree structure comprising a set of connected nodes.
  • the tree structure has a root node which is a node which has no parent nodes (i.e., the root node is the top-most node in the tree hierarchy).
  • Each node in the tree structure may be connected to one or more children nodes.
  • the tree structure as used in connection with embodiments may, in general, correspond to a generalized tree structure where each node in the tree structure, apart from the root node, may be connected to one or more parent nodes (as opposed to strictly a single parent node).
  • the generalized tree structure may be equally called a graph (data) structure.
  • the tree structure may correspond to a non-generalized tree data structure where each node, apart from the root node, is connected only to a single parent nodes.
  • UMTS universal mobile telecommunications system
  • UTRAN radio access network
  • LTE long term evolution
  • WLAN wireless local area network
  • WiFi worldwide interoperability for microwave access
  • Bluetooth® personal communications services
  • PCS personal communications services
  • WCDMA wideband code division multiple access
  • UWB ultra-wideband
  • sensor networks mobile ad- hoc networks
  • IMS Internet Protocol multimedia subsystems
  • Figure 1 depicts examples of simplified system architectures only showing some elements and functional entities, all being logical units, whose implementation may differ from what is shown.
  • the connections shown in Figure 1 are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the system typically comprises also other functions and structures than those shown in Figure 1.
  • Figure 1 shows a part of an exemplifying radio access network.
  • a communications system typically comprises more than one (e/g)NodeB in which case the (e/g)NodeBs may also be configured to communicate with one another over links, wired or wireless, designed for the purpose. These links may be used for signaling purposes.
  • the (e/g)NodeB is a computing device configured to control the radio resources of communication system it is coupled to.
  • the NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wireless environment.
  • the (e/g)NodeB includes or is coupled to transceivers. From the transceivers of the (e/g)NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to user devices.
  • the antenna unit may comprise a plurality of antennas or antenna elements.
  • the (e/g)NodeB is further connected to core network 110 (CN or next generation core NGC).
  • core network 110 CN or next generation core NGC.
  • the counterpart on the CN side can be a serving gateway (S-GW, routing and forwarding user data packets), packet data network gateway (P-GW), for providing connectivity of user devices (UEs) to external packet data networks, or mobile management entity (MME), etc.
  • S-GW serving gateway
  • P-GW packet data network gateway
  • MME mobile management entity
  • the core network 110 may comprise an access and mobility management function (AMF) and/or a location management function (LMF).
  • the AMF is a control plane function which performs access and mobility management for the terminal devices 100, 102. Further functions implemented at the AMF may comprise, for example, device registration, policy enforcement, session management, user plane function selection, subscriber data management, security management, network slicing, network integration, control plane management, fault management, policy control, location management and/or network optimization.
  • the AMF may be connected to one or more clients for implementing said functions.
  • the LMF is a network entity for providing positioning functionality.
  • the LMF may be configured to receive measurements and assistance information from the radio access network (RAN) and one or more terminal devices via the AMF for determining the positions of the one or more terminal devices.
  • the LMF may employ, at least in some embodiments, NR positioning protocol A (NRPPa) for transfering the positioning information between the RAN and the LMF.
  • NRPPa NR positioning protocol A
  • the user device also called UE, user equipment, user terminal, terminal device, etc.
  • UE user equipment
  • user terminal terminal device
  • any feature described herein with a user device may be implemented with a corresponding apparatus, such as a relay node.
  • a relay node is a layer 3 relay (self-backhauling relay) towards the base station.
  • the user device typically refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and/or touch screen computer, tablet, game console, notebook, and multimedia device.
  • SIM subscriber identification module
  • a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • a user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.
  • the user device (or in some embodiments a layer 3 relay node) is configured to perform one or more of user equipment functionalities.
  • the user device may also be called a subscriber unit, mobile station, remote terminal, access terminal, user terminal or user equipment (UE) just to mention but a few names or apparatuses.
  • CPS cyber-physical system
  • ICT devices sensors, actuators, processors microcontrollers, etc.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.
  • 5G enables using multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and/or spectrum available.
  • MIMO multiple input - multiple output
  • 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors and real-time control.
  • 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integradable with existing legacy radio access technologies, such as the LTE.
  • Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE.
  • 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave).
  • inter-RAT operability such as LTE-5G
  • inter-RI operability inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave.
  • One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.
  • the current architecture in LTE networks is fully distributed in the radio and fully centralized in the core network.
  • the low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC).
  • MEC multi-access edge computing
  • 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors.
  • MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time.
  • Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analytics, time- critical control, healthcare applications).
  • the communication system is also able to communicate with other networks, such as a public switched telephone network or the Internet 112, or utilize services provided by them.
  • the communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Figure 1 by “cloud” 114).
  • the communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.
  • Edge cloud may be brought into the RAN by utilizing network function virtualization (NVF) and software defined networking (SDN).
  • Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or unit (RU) or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts.
  • Application of cloudRAN architecture enables RAN real time functions being carried out at the RAN side (in a distributed unit, DU 104) and non-real time functions being carried out in a centralized manner (in a central or centralized unit, CU 108).
  • the RAN may comprise at least one distributed access node comprising a central unit, one or more distributed units communicatively connected to the central unit and one or more (remote) radio heads or units, each of which is communicatively connected to at least one of the one or more distributed units.
  • 5G may also utilize satellite communication to enhance or comple-ment the coverage of 5G service, for example by providing backhauling.
  • Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future rail-way/maritime/aeronautical communications.
  • Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed).
  • GEO geostationary earth orbit
  • LEO low earth orbit
  • mega-constellations systems in which hundreds of (nano)satellites are deployed.
  • Each satellite 106 in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells.
  • the on-ground cells may be created through an on-ground relay node 104 or by a gNB located on-ground or in
  • the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (e/g)NodeBs, the user device may have an access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the (e/g)NodeBs or may be a Home(e/g)nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided.
  • Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells.
  • the (e/g)NodeBs of Figure 1 may provide any kind of these cells.
  • a cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of (e/g)NodeBs are required to provide such a network structure.
  • a network which is able to use “plug-and-play” (e/g)Node Bs includes, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in Figure 1).
  • HNB-GW HNB Gateway
  • a HNB Gateway (HNB-GW) which is typically installed within an operator’s network may aggregate traffic from a large number of HNBs back to a core network.
  • Some 5G or 6G systems may support dual connectivity for enabling a terminal device (or a UE) to be communicatively connected to two serving access nodes (e.g., eNBs) at the same time.
  • a terminal device or a UE
  • two serving access nodes e.g., eNBs
  • dual connectivity a given terminal device is capable of transmitting and/or receiving signals to/from two different access nodes simultaneously.
  • the first access node is acting as a Master Node (abbreviated as MN) and the second one as a Secondary Node (abbreviated as SN).
  • MN Master Node
  • SN Secondary Node
  • the dual connectivity may be, e.g., Multi Radio Access Technology (Multi-RAT) Dual Connectivity (MR-DC).
  • Multi-RAT Multi Radio Access Technology
  • MR-DC Dual Connectivity
  • Examples of MR-DC configurations comprise, e.g., EN-DC (Evolved Universal Terrestrial Radio Access, E-UTRA (Evolved UMTS Terrestrial Radio Access), New Radio, NR, Dual Connectivity, DC), NR-DC (New Radio Dual Connectivity), NGEN-DC (Next Generation Radio Access Network, NG-RAN, E-UTRA Dual Connectivity) and NE-DC (NR - E- UTRA Dual Connectivity).
  • EN-DC Evolved Universal Terrestrial Radio Access
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • New Radio NR
  • Dual Connectivity DC
  • NR-DC New Radio Dual Connectivity
  • NGEN-DC Next Generation Radio Access Network
  • NG-RAN Next Generation Radio Access Network
  • E-UTRA Dual Connectivity NR - E- UTRA Dual Connectivity
  • NE-DC NR - E- UTRA Dual Connectivity
  • the terminal device has a single Radio Resource Control (RRC) state defined by a master node.
  • the master node is configured to provide a (direct) control plane connection between the terminal device and core network in a dual connectivity communication scenario.
  • the master node may be, for example, a master eNB in EN-DC or a Master ng-eNB in NGEN-DC or a master gNB in NR-DC and NE-DC.
  • the master node 201 may be associated with a master cell group (MCG) which is a group of serving cells comprising a primary cell (PCell) and optionally one or more secondary cells (Scells).
  • MCG master cell group
  • PCell primary cell
  • Scells secondary cells
  • the mapping of the master and secondary nodes for a given terminal device in DC communication scenario is typically not fixed.
  • the master node for a terminal device may be changed, e.g., for enabling mobility of the terminal device. It should be noted that, following a change of the master node for a terminal device, one or more of the secondary nodes connected to the previous master node may not have a direct connection to the new master node.
  • Figure 2 illustrates an example of a network deployment for a dual connectivity scenario from the perspective of possible interconnectivity between master and secondary nodes.
  • the illustrated network deployment may form a part of the communications system of Figure 1.
  • the network deployment of Figure 2 comprises a master node 201 and six secondary nodes 211 to 216, for example.
  • the master node 201 represents a node to which a terminal device may be RRC connected and may require forwarding of some information to a secondary node.
  • the first secondary node 211 is connected to the third, fourth and fifth secondary nodes 213, 214, 215, and the second secondary node 212 is connected to the fourth, fifth and sixth secondary nodes 214, 215, 216.
  • both the fourth and fifth secondary nodes 214, 215 are connected to both of the first and second secondary nodes 211, 212.
  • the connections between the nodes 201, 211 to 216 may be Xn/X2 connections.
  • the master node 201 does not have any direct Xn/X2 connectivity to the fourth secondary node 214 and the master node 201 is not aware of which secondary nodes are connected to the first and secondary nodes 211, 212, the master node 201 has to forward a message (e.g., an access and mobility indication) comprising the RACH report and a list of primary secondary cells (list of PSCells) to both the first and second secondary nodes 211, 212 (SN1 & SN2). It is assumed here that the list of PSCells comprises at least the PSCell ID associated with the fourth secondary node 214.
  • a message e.g., an access and mobility indication
  • list of PSCells comprises at least the PSCell ID associated with the fourth secondary node 214.
  • each of the first and second secondary nodes 211, 212 determine based on the RACH report that the RACH report is to be forwarded to the fourth secondary node 214. It means that, in this example, duplicated forwarding will be done to the fourth secondary node 214.
  • the fourth secondary node 214 will not be able to detect in any way that the two RACH reports correspond to two copies of the same RACH report. Consequently, both of the copies of the RACH report may be subsequently used for RACH optimization which may lead to inappropriate/incorrect RACH optimization results.
  • the embodiments to be discussed below seek to overcome the aforementioned problems by providing means for the master node to gather information on the secondary node connectivity and to perform transmission of messages (e.g., a RACH report or other SON-based report) based on said gathered information.
  • messages e.g., a RACH report or other SON-based report
  • Figure 2 illustrates a relatively simple example of a network deployment for dual connectivity.
  • the number of interconnected secondary nodes may be, in practice, much larger than what is depicted in Figure 2.
  • the secondary nodes may not be arranged in clearly distinct sets or layers which are only connected to the preceding and following sets/layers of secondary nodes. Instead, the secondary nodes may form a more complicated network of secondary nodes where any secondary node may potentially be connected to any other secondary node.
  • Figures 3 A and 3B illustrates processes according to embodiments for enabling forwarding of relevant information (e.g., the RACH report) from a master node to a relevant secondary node.
  • the illustrated processes of Figures 3 A & 3B may be performed by two different network nodes. Specifically, the illustrated processes of Figure 3A & 3B may be performed, respectively, by a first network node being or acting as a master node and a second network node being or acting as a secondary node (which may or may not neighbour the first network node).
  • the first network node may be the master node 201 of Figure 2 and/or the second network node may be any of the secondary network nodes 211 to 216.
  • the first network node receives, in block 301, one or more messages (respectively) from one or more second network nodes neighboring the first network node.
  • Each (or one or at least one) of the one or more messages comprises network node connectivity information related to at least one or more connections between one of the one or more second network nodes and one or more third network nodes neighboring that second network node.
  • the network node connectivity information defines at least the one or more connections between a second network node from which a message (of the one or more messages) was received and one or more third network nodes neighboring that second network node.
  • the first network node may be a master node (as described above) while the second and third network nodes (and any other possibly further network nodes) may be secondary network nodes.
  • the network node connectivity information may equally called interconnectivity tree information, at least in some embodiments.
  • the one or more second network nodes may comprise a plurality of second network nodes.
  • the one or more connections between the second network node from which the message was received and the one or more third network nodes neighboring the second network node may be Xn/X2 interface connections.
  • the network node connectivity information may be or at least comprise Xn/X2 connectivity information (of secondary nodes).
  • At least one of the one or more messages may comprise network node connectivity information pertaining to further connections of the one or more third network nodes to one or more fourth network nodes and possibly even further connections between the one or more fourth network nodes and beyond, as will be described in further detail in connection with following embodiments.
  • the data transmitted in block 302 may be or comprise an access and mobility indication.
  • the data (or the access and mobility indication) may comprise a random access report or a RACH report or other SON-based report(s).
  • the data transmitted in block 302 may comprise a terminal device context (i.e., UE context) information. This latter alternative may be used, e.g., for enabling inactive UE context retrieval during RAN notification area update (RNAU).
  • UE context i.e., UE context
  • the data (or the access and mobility indication) transmitted in block 302 may comprise an identification information for the target network node (e.g., a list of PSCells).
  • the network node connectivity information received, in block 301, from a second network node indicates connections for levels 0 to n of a tree structure of interconnected network nodes having a root node corresponding to the second network node.
  • the network node connectivity information defines an interconnectivity tree of network nodes (or more specifically an interconnectivity tree of secondary nodes).
  • n is a positive integer and the root node corresponds to level 0 (i.e., the Oth level).
  • the network node is aware of how data should be forwarded to reach the target network node (or target secondary node) without having to rely on sending to all connected second network nodes.
  • the first network node may perform the transmission in block 302 specifically based on the received interconnectivity tree (or information for forming the interconnectivity tree).
  • the target network node of block 302 may be any network node (or secondary node) comprised in a level m of the tree structure, where m is a positive integer smaller than or equal to n (i.e., 1 ⁇ m ⁇ ri).
  • n may be larger than 1 (i.e., the network node connectivity information may relate to levels 0, 1,. . n of the tree structure of interconnected network nodes). In other words, n may be any integer larger than or equal to 2.
  • the tree structure of interconnected network nodes (or equally interconnectivity tree) received in block 301 may be formed by either the first secondary node 211 and the third, fourth and fifth secondary nodes 213, 214, 215 connected to it or the second secondary network node 212 and the fourth, fifth and sixth secondary nodes 214, 215, 216 connected to it.
  • the master node 201 is made aware that the third, fourth and fifth secondary nodes 213, 214, 215 are reachable via the first secondary node 211.
  • the target network node is a secondary network node on the 1st level of the tree structure (i.e., one of the third, fourth and fifth secondary network nodes 213 to 215 for which network node connectivity information was received).
  • the master node 201 may, for example, determine that the first secondary node 211 will further forward the RACH report (or other transmitted data) to the fourth secondary node 214, being the intended target, and thus the master node 201 will include the list of secondary nodes (including the fourth secondary node 214) only in the access and mobility indication sent to the first secondary node 211.
  • the second network node transmits, in block 311, a message to a first network node neighboring the second network node.
  • the message comprises network node connectivity information (of at least the second network node) related to at least one or more connections between the second network node and one or more third network nodes neighboring the second network node.
  • the network node connectivity information comprises at least information on one or more third network nodes connected (directly) to the second network node.
  • the network node connectivity information of at least the second network node may be maintained in a memory of the second network node.
  • the second network node may be a secondary node while the first network node may be a master node (as described above) or another secondary network node (which may be connected to the master node or it is at least closer to the master node compared to the second network node).
  • Figures 4A and 4B illustrate further processes according to embodiments for enabling forwarding of relevant information (e.g., the RACH report) from a master node to a relevant secondary node.
  • the illustrated processes of Figures 4A & 4B may be performed by two different network nodes. Specifically, the illustrated processes of Figure 4A & 4B may be performed, respectively, by a first network node being or acting as a master node and a second network node being or acting as a secondary node (which may or may not neighbour the first network node).
  • the first network node may be the master node 201 of Figure 2 and/or the second network node may be any of the secondary network nodes 211 to 216.
  • Figures 4A and 4B correspond, to a large extent, to the processes of Figures 3 A and 3B. Any of the features and/or definitions discussed in connection with Figures 3 A and 3B may apply, mutatis mutandis, in connection with the processes of Figures 4A and 4B.
  • the first network node being, e.g., a master node
  • the first network node initially transmits, in block 401, one or more requests requesting network node connectivity information, respectively, to one or more second network nodes neighboring the first network node.
  • the one or more second network nodes may be secondary nodes.
  • the one or more requests may comprise each an indication defining that the network node connectivity information is requested to be provided for levels 0 to n of a tree structure of interconnected network nodes.
  • each of the one or more requests may comprise a value of the parameter n.
  • n may be, in general, any positive integer. For example, if n is equal to 1, the request concerns the network connectivity information relating to a secondary node receiving the request (i.e., a second network node) and any secondary nodes connected to it. If n is equal to 2, the request concerns the network connectivity information relating to a secondary node receiving the request (i.e., a second network node), any secondary nodes connected to it and any further secondary nodes to those secondary nodes.
  • the first network node (being a master node) may determine, before the transmission in block 401, the value n based on a configuration received from an operator, i.e., from an O&M (operation & maintenance) entity or node. For instance, by deploying the network nodes and corresponding cell coverage ranges, the operator is aware of the number of network nodes that serve the certain coverage area and therefore capable of configuring the master node to request the network node connectivity information accordingly.
  • O&M operation & maintenance
  • the first network node (being a master node) may determine the value n based on the purpose of use of the network node connectivity information (i.e., based on which purpose the network node connectivity information is to be used). For instance, if the network node connectivity information is requested for forwarding a RACH report (for which a longer forwarding delay can typically be tolerated), the first network node may determine that a larger n (e.g., at least n > 1 or n > 2) may be employed.
  • a larger n e.g., at least n > 1 or n > 2
  • the determining may be based, e.g., on the maximum delay which can be still tolerated for the terminal device context retrieval.
  • the one or more requests may comprise each an identifier of the node to which the request is transmitted.
  • the identifier may be, e.g., a Global NG-RAN Node ID.
  • Global NG-RAN Node ID is an IE which may be used for globally identifying an NG-RAN node.
  • the first network node receives, in block 402, one or more responses (to the one or more requests) from the one or more second network nodes (or from at least one of them).
  • the one or more responses may correspond to the one or more messages discussed in connection with block 301 of Figure 3 A.
  • each of the one or more responses comprise network node connectivity information relating to at least one or more connections between a second network node from which a response was received (and to which a request was transmitted earlier) and one or more third network nodes neighboring that second network node.
  • the network connectivity information comprised in each response may comprise a tree structure of interconnected network nodes (or interconnected secondary nodes) having a root node corresponding to a second network node which received a request.
  • the one or more requests in block 401 are Xn/X2 setup requests and the one or more responses in block 402 are Xn/X2 setup responses.
  • the one or more requests in block 401 are NG-RAN node configuration update messages and the one or more responses in block 402 are NG- RAN node configuration update acknowledge messages.
  • the one or more requests in block 401 are first dedicated Xn/X2 application protocol messages and the one or more responses in block 402 are second dedicated Xn/X2 application protocol messages.
  • the one or more responses may comprise each an identifier of the node to which the response is transmitted.
  • the identifier may be, e.g., a Global NG-RAN Node ID.
  • the first network node transmits, in block 403, data via one of the one or more second network nodes to a target network node based on the received network node connectivity information.
  • the target network node may be a target secondary node.
  • Block 403 may correspond to block 302 of Figure 3A.
  • the second network node (being, e.g., a secondary node) initially receives, in block 411, a request requesting network node connectivity information. Said request may be equally called an SN connectivity request (at least in some embodiments).
  • the request is received from a first network node which may be a master node or a secondary node (which is closer to the master node than the second network node).
  • the request may be defined as described in connection with block 401 of Figure 4A.
  • the second network node transmits, in block 412, a response to the first network node.
  • the response comprises network node connectivity information of at least the second network node indicating (or related to) at least one or more connections between the second network node and one or more third network nodes neighboring the second network node. Said response may be equally called an SN connectivity answer (at least in some embodiments).
  • the Block 412 may correspond to block 311 of Figure 3A (with the response of block 412 corresponding to the message of block 311).
  • the request and the response discussed in connection with block 411 & 412 of Figure 4B may be equally called, respectively, the first request and the first response (to differentiate them from possible further or second requests/responses which will be described in further detail in connection with Figure 5).
  • Figure 5 illustrates a further process according to embodiments for enabling forwarding of relevant information (e.g., the RACH report) from a master node to a relevant secondary node.
  • the illustrated process of Figure 5 may be performed by a second network node being or acting as a secondary node (which may or may not neighbour the first network node).
  • the second network node may be any of the secondary network nodes 211 to 216.
  • Figure 5 corresponds, to a large extent, to the processes of Figures 3B and/or 4B. Any of the features and/or definitions discussed in connection with Figures 3B and/or 4B may apply, mutatis mutandis, in connection with the process of Figure 5.
  • the second network node (being, e.g., a secondary node) initially receives, in block 501, a request requesting network node connectivity information.
  • the request is received from a first network node which may be a master node or a secondary node.
  • the request may be defined as described in connection with block 401 of Figure 4A.
  • the request received in block 411 comprises an indication defining that the network node connectivity information is requested to be provided for levels 0 to n of a tree structure of interconnected network nodes having a root node corresponding to the second network node.
  • the request may comprises a value of the parameter n.
  • n may be, in general, any positive integer.
  • n is equal to 1 or larger than 1 (i.e., 2, 3, 4,).
  • n indicated in the request is equal to one in block 502 (i.e., network node connectivity information only for levels 0 and 1 of an interconnectivity tree is requested)
  • the process may proceed as described previously in connection with Figure 4B.
  • n indicated in the request is larger than one in block 502 (i.e., network node connectivity information for at least three levels of an interconnectivity tree including the Oth level is requested)
  • the second network node transmits, in block 503, to one or more third network nodes (being, e.g., secondary nodes) neighboring the second network node, one or more requests requesting network node connectivity information.
  • the one or more requests comprise a second indication defining that the network node connectivity information is requested to be provided for levels 0 to n-1 of a tree structure of interconnected network nodes having a root node corresponding to a respective third network node.
  • the one or more third network nodes may be configured also to perform the process of Figure 5 though, obviously, now the n value considered by the one or more third network nodes is reduced compared to the n value considered by the second network node.
  • the second network node receives, in block 504, from the one or more third network nodes, one or more responses (to the one or more requests) comprising the requested network node connectivity information.
  • the second network node transmits, in block 505, a response comprising network node connectivity information to the first network node.
  • the network connectivity information comprises both network node connectivity information of the second network node itself (as described, e.g., in connection with blocks 311, 412 of Figure 3B & 4B) as well as the network node connectivity information received in block 504.
  • the network node connectivity information of the second network node itself and the network node connectivity information received from the one or more third network nodes may be transmitted as two or more separate responses.
  • the request of block 501 and the one or more requests of block 503 are Xn/X2 setup requests and the response of block 505 and the one or more responses of block 504 are Xn/X2 setup responses.
  • the request of block 501 and the one or more requests of block 503 are NG-RAN node configuration update messages and the response of block 505 and the one or more responses of block 504 are NG-RAN node configuration update messages.
  • the request of block 501 and the one or more requests of block 503 are first dedicated Xn/X2 application protocol messages and the response of block 505 and the one or more responses of block 504 are second dedicated Xn/X2 application protocol messages.
  • the request of block 501 and the one or more requests of block 503 may be equally called the first request and the one or more second requests, respectively.
  • the response of block 505 and the one or more responses of block 504 may be equally called the first response and the one or more second responses, respectively.
  • Figure 6 illustrates signalling between a master node and a set of secondary nodes according to embodiments for enabling forwarding of relevant information (e.g., the RACH report) from a master node to a relevant secondary node.
  • Figure 6 serves to further illustrate the operation discussed previously in connection with Figure 4A for the master node and Figure 5 for the secondary nodes as well as depicting the process of forwarding data to the target secondary node.
  • the master node initially transmits, in message 601, a first SN connectivity request (REQ) to one or more first secondary nodes (SN1, SN2, SN3,).
  • Each first SN connectivity request may comprise an identifier of a node to which the first SN connectivity request is transmitted (i.e., an identifier of the intended recipient of the first SN connectivity request) and the parameter n having a value of 3.
  • each of the one or more first secondary nodes determine that, as the value of n communicated with the first SN connectivity request is larger than 1, a further transmission of an SN connectivity request is in order.
  • each of the one or more first secondary nodes transmit, in message 602, a second SN connectivity request to one or more second secondary nodes (SN1-1, SN1-2, SN1-3,).
  • second secondary nodes SN1-1, SN1-2, SN1-3, only one of the one or more second secondary nodes is shown for simplicity of presentation.
  • each of the one or more third secondary nodes Upon receiving the third SN connectivity request, each of the one or more third secondary nodes determine that, as the value of n communicated with the third SN connectivity request is equal to 1, no further transmission of an SN connectivity request is to be carried out. Instead, each of the one or more third secondary nodes transmit, in message 604, a first SN connectivity answer (ANS) back to a second secondary node from which the third SN connectivity request was received.
  • Each first SN connectivity answer may comprise an identifier of a second secondary node (i.e., the node to which the first SN connectivity answer is transmitted) and a list of fourth secondary nodes (directly) connected to the third secondary node.
  • each of the one or more second secondary nodes transmit, in message 605, a second SN connectivity answer back to a first secondary node from which the second SN connectivity request was received.
  • Each second SN connectivity answer may comprise an identifier of a first secondary node (i.e., the node to which the second SN connectivity answer is transmitted) and a list of secondary nodes.
  • the list of secondary nodes may define third secondary nodes (directly) connected to the second secondary node in question as well as any lists of fourth secondary nodes received from the third secondary nodes.
  • each of the one or more first secondary nodes transmit, in message 606, a third SN connectivity answer back to the master node.
  • Each third SN connectivity answer may comprise an identifier of the master node and a list of secondary nodes.
  • the list of secondary nodes may define second secondary nodes (directly) connected to the first secondary node in question as well as any lists of third and/or fourth secondary nodes received from the second secondary nodes.
  • the master node is capable of determining how the secondary nodes are connected to each other in block 607. For example, the master node is able to obtain or derive, in block 607, a tree structure of the interconnected network nodes based on the received one or more SN connectivity ANS messages.
  • the master node may need to transmit a RACH report to a particular second secondary node (SN1-1). Based on the received information on connections between the secondary nodes, the master node transmits, in message 608, the RACH report along with a list of PSCells identifying the targeted second secondary node to a particular first secondary node (SN1) known to be connected to the targeted second secondary node. The first secondary node then determines based on the list of PSCells that it is itself not the targeted secondary node for the RACH report and consequently forwards, in message 609, the RACH report and the list of PSCells to the targeted secondary node (being here SN1-1 mostly for simplicity of presentation).
  • any of the SN connectivity requests 601 to 603 may be defined to comprise information elements (IEs)/groups defined in the following Table.
  • M stands for mandatory.
  • the Message Type information element (IE) uniquely identifies the message being sent.
  • Global NG-RAN Node ID is an IE which may be used for globally identifying an NG-RAN node (here specifically the targeted NG-RAN node).
  • the level of inter-connectivity indication IE indicates a value n representing levels of a tree structure of interconnected network nodes, as described above.
  • the level of inter-connectivity indication IE is indicated as mandatory in the above Table, this may not be the case in all embodiments.
  • any of the SN connectivity answers 604 to 606 may be defined to comprise lEs/groups defined in the following Table.
  • the Message Type, Global NG-RAN Node ID and the level of interconnectivity indication IES may be defined as described above.
  • the above Table comprises Neighbour NG-RAN Node List IE comprising the Global NG-RAN Node ID IE as well as an Xn connection availability indication indicating whether or not there exists an Xn connection to each of the (known) neighbor nodes.
  • the Xn connection availability indication may be included as a part of the Neighbour NG-RAN Node List.
  • the Xn connection availability indication IE is one example of the network node connectivity information discussed in connection with previous embodiments. [0098] In some alternative embodiments, any of the SN connectivity answers 604 to
  • 606 (or the response of block 412 of Figure 4 or the response of block 505 of Figure 5) may be defined to comprise lEs/groups defined in the following Table.
  • the X2 connection availability indication for indicating
  • E-UTRA Neighbor Information IE (as defined 3GPP TS 38.423, 9.2.2.14) which is an IE containing cell configuration information of E-UTRA cells that a neighbor NG-RAN node may need to properly operate its own served cells.
  • the X2 connection availability indication IE is one example of the network node connectivity information discussed in connection with previous embodiments
  • ECGI stands for EUTRA Cell Global Identifier
  • EARFCN stands for E- UTRA Absolute Radio Frequency Channel Number
  • TAC stands for tracking area code
  • RANAC stands for RAN area code
  • FDD stands for frequency division duplex
  • TDD time division duplex.
  • the existing Xn Setup procedure messages i.e. Xn setup request may be extended to include the IES of the above SN connectivity REQ message Table and/or the Xn setup response message may be extended to include the IEs of the above SN connectivity answer message Table.
  • the existing NG-RAN node configuration update procedure messages i.e., NG-RAN node configuration update message
  • the NG-RAN node configuration update acknowledge message may be extended to include the IEs of the above SN connectivity answer message Table.
  • the existing Xn/X2 application protocol (AP) procedure and associated messages may be extended to indicate the interconnectivity tree information (i.e., the tree structure of interconnected network nodes or secondary nodes).
  • the existing Xn setup procedure in Xn/X2 AP may be used to exchange configuration data needed for two NG-RAN nodes to interoperate correctly.
  • the existing NG- RAN node configuration update procedure may be used to update the configuration data needed for two NG-RAN nodes to interoperate correctly.
  • any of the messages of block 301 of Figure 3 A, block 311 of Figure 3B, block 402 of Figure 4A, block 412 of Figure 4B and/or block 505 of Figure 5 may be defined to comprise the neighbor information NR IE comprising cell configuration information of neighboring cells to provide the necessary interconnectivity tree information.
  • an additional IE is introduced to the neighbor information NR IE to include, in the neighbor information NR IE, an indication whether Xn connection is available to the neighboring nodes or not (see final row of the table below).
  • an IE (called here “Xn connection availability indication”) corresponding to the network node connectivity information discussed in connection with previous embodiments is added to the neighbor information NR IE.
  • the neighbour information NR may be defined to comprise the lEs/groups defined in the following table.
  • O stands for optional
  • CGI cell global identifier
  • TAC stands for tracking area code
  • RANAC stands for RAN area code
  • FDD frequency division duplex
  • TDD time division duplex.
  • the Xn connection availability indication IE indicates whether or not there exists an Xn connection to each of the (known) neighbor NG- RAN nodes.
  • the Xn connection availability indication IE is one example of the network node connectivity information discussed in connection with previous embodiments.
  • the Xn setup procedure can provide the neighbor nodes the Xn connection availability indication during the setup of Xn interface.
  • the NG-RAN node configuration update procedure may be used to update the Xn connection availability information whenever the new Xn connection is established or released with the neighboring node.
  • Figure 6 illustrates a particular exemplary communication scenario, e.g., where the parameter n has an initial value of 3, the features discussed in connection with Figure 6 are not limited to use in connection only with this particular communication scenario.
  • Figure 7 provides an apparatus 701 according to some embodiments. Specifically, Figure 7 may illustrate a network node 701 or a part thereof. Said network node 701 may be either a master node or a secondary node.
  • the apparatus 701 may comprise one or more communication control circuitry 720, such as at least one processor, and at least one memory 740, including one or more algorithms 731 (instructions), such as a computer program code (software) wherein the at least one memory and the computer program code (software) are configured, with the at least one processor, to cause the apparatus 701 to carry out any one of the exemplified functionalities of the network node (being, e.g., the master node or the secondary node) described above.
  • Said at least one memory 740 may also comprise at least one database 732.
  • the apparatus 701 may be a distributed device wherein processing of tasks takes place in more than one physical unit.
  • Each of the at least one processor may comprise one or more processor cores.
  • a processing core may comprise, for example, a Cortex-A8 processing core manufactured by ARM Holdings or a Zen processing core designed by Advanced Micro Devices Corporation.
  • the one or more communication control circuitry 720 may comprise at least one Qualcomm Snapdragon and/or Intel Atom processor.
  • the one or more communication control circuitry 720 may comprise at least one applicationspecific integrated circuit (ASIC).
  • the one or more control circuitry 720 may comprise at least one field-programmable gate array (FPGA).
  • the one or more communication control circuitry 720 of the apparatus 701 are configured to carry out functionalities described above by means of any of Figures 3 A, 3B, 4A, 4B, 5 and/or 6 using one or more individual circuitries. It is also feasible to use specific integrated circuits, such as ASIC (Application Specific Integrated Circuit) or other components and devices for implementing the functionalities in accordance with different embodiments.
  • ASIC Application Specific Integrated Circuit
  • the apparatus 701 may further comprise different interfaces 710 such as one or more communication interfaces comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols (e.g., Xn/X2 AP).
  • the one or more communication interfaces 710 may comprise, for example, communication interfaces providing a connection between the apparatus 701 and one or more further network nodes (e.g., one or more secondary nodes and optionally a master node if the apparatus 701 corresponds to a secondary node).
  • the one or more communication interfaces 710 may comprise also communication interfaces between the apparatus 701 and one or more core network nodes.
  • the one or more communication interfaces 710 may comprise standard well-known components such as an amplifier, filter, frequency-converter, (de)modulator, and encoder/decoder circuitries, controlled by the corresponding controlling units, and one or more antennas.
  • the apparatus 701 may also comprise one or more user interfaces.
  • the memory 740 may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • circuitry may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of hardware circuits and software (and/or firmware), such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with soft- war e/firm ware and (ii) any portions of hardware processor(s) with software, including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus, such as a terminal device or an access node, to perform various functions, and (c) hardware circuit(s) and processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g.
  • circuitry for operation, but the software may not be present when it is not needed for operation.
  • This definition of ‘circuitry’ applies to all uses of this term in this application, including any claims.
  • the term ‘circuitry’ also covers an implementation of merely a hard-ware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • At least some of the processes described in connection with Figures 3A, 3B, 4A, 4B, 5 and 6 may be carried out by an apparatus comprising corresponding means for carrying out at least some of the described processes.
  • Some example means for carrying out the processes may include at least one of the following: detector, processor (including dual-core and multiple-core processors), digital signal processor, controller, receiver, transmitter, encoder, decoder, memory, RAM, ROM, software, firmware, display, user interface, display circuitry, user interface circuitry, user interface software, display software, circuit, filter (low-pass, high-pass, bandpass and/or bandstop), sensor, circuitry, inverter, capacitor, inductor, resistor, operational amplifier, diode and transistor.
  • the at least one processor, the memory, and the computer program code form processing means or comprises one or more computer program code portions for carrying out one or more operations according to any one of the embodiments of Figures 3A, 3B, 4A, 4B, 5 and 6 or operations thereof.
  • at least some of the processes may be implemented using discrete components.
  • a first network node e.g., a master node comprising means for performing: receiving one or more messages from one or more second network nodes neighboring the first network node, wherein one of the one or more messages comprises network node connectivity information related to at least one or more connections between one of the one or more second network nodes and one or more third network nodes neighboring the one of the one or more second network nodes; and transmitting data via the one of the one or more second network nodes to a target network node based on the received network node connectivity information.
  • a master node comprising means for performing: receiving one or more messages from one or more second network nodes neighboring the first network node, wherein one of the one or more messages comprises network node connectivity information related to at least one or more connections between one of the one or more second network nodes and one or more third network nodes neighboring the one of the one or more second network nodes; and transmitting data via the one of the one or more second network nodes to a target network node based on the received network no
  • a second network node (e.g., a secondary node) comprising means for performing: transmitting a message to a first network node neighboring the second network node, wherein the message comprises network node connectivity information related to at least one or more connections between the second network node and one or more third network nodes neighboring the second network node.
  • Embodiments as described may also be carried out, fully or at least in part, in the form of a computer process defined by a computer program or portions thereof.
  • Embodiments of the methods described in connection with Figures 3 A, 3B, 4A, 4B, 5 and 6 may be carried out by executing at least one portion of a computer program comprising corresponding instructions.
  • the computer program may be provided as a computer readable medium comprising program instructions stored thereon or as a non-transitory computer readable medium comprising program instructions stored thereon.
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
  • the computer program may be stored on a computer program distribution medium readable by a computer or a processor.
  • the computer program medium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program medium may be a non-transitory medium. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art.
  • non-transitory is a limitation of the medium itself (that is, tangible, not a signal) as opposed to a limitation on data storage persistency (for example, RAM vs. ROM).
  • At least some embodiments find industrial application in wireless communications.

Landscapes

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

Abstract

Selon un aspect, l'invention concerne un nœud de réseau permettant d'effectuer les opérations suivantes dans lesquelles : le nœud de réseau reçoit un ou plusieurs messages de la part d'un ou plusieurs deuxièmes nœuds de réseau voisins du premier nœud de réseau. L'un desdits un ou plusieurs messages contient des informations de connectivité de nœud de réseau relatives à au moins une ou plusieurs connexions entre l'un desdits un ou plusieurs deuxièmes nœuds de réseau et un ou plusieurs troisièmes nœuds de réseau voisins du deuxième nœud de réseau. Le nœud de réseau transmet des données par l'intermédiaire desdits un ou plusieurs deuxièmes nœuds de réseau à un nœud de réseau cible sur la base des informations de connectivité de nœud de réseau reçues.
PCT/EP2024/064330 2023-07-07 2024-05-24 Acquisition d'informations d'interconnectivité de nœuds de réseau Pending WO2025011809A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FI20235808 2023-07-07
FI20235808 2023-07-07

Publications (1)

Publication Number Publication Date
WO2025011809A1 true WO2025011809A1 (fr) 2025-01-16

Family

ID=91276834

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2024/064330 Pending WO2025011809A1 (fr) 2023-07-07 2024-05-24 Acquisition d'informations d'interconnectivité de nœuds de réseau

Country Status (1)

Country Link
WO (1) WO2025011809A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2974172B1 (fr) * 2013-03-15 2020-05-20 Cisco Technology, Inc. Capacité de routage sélectif activée de manière dynamique

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2974172B1 (fr) * 2013-03-15 2020-05-20 Cisco Technology, Inc. Capacité de routage sélectif activée de manière dynamique

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL: "Introducing X2 TNL Address discovery for en-gNBs for EN-DC", vol. RAN WG3, no. Chengdu, P.R. China; 20181008 - 20181012, 29 September 2018 (2018-09-29), XP051529182, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG3%5FIu/TSGR3%5F101bis/Docs/R3%2D185914%2Ezip> [retrieved on 20180929] *

Similar Documents

Publication Publication Date Title
US11696197B2 (en) Determination for conditional handover failure
US11412424B2 (en) Conditional handover
EP3874856B1 (fr) Appareil et procédé d&#39;utilisation de ressources de liaison montante
CN116438838A (zh) 波束失败报告
EP3857951B1 (fr) Restriction de cellule de canal logique
US12185360B2 (en) Processing rules for resource elements
US12432623B2 (en) Method and apparatus for system providing multicast services
US20240340714A1 (en) Method, apparatus, and computer program for enhancing dual connectivity
US12445923B2 (en) Managing multiple subscriber identities in cellular network
US20230262563A1 (en) Managing multiple subscriber identities in cellular network
WO2025011809A1 (fr) Acquisition d&#39;informations d&#39;interconnectivité de nœuds de réseau
WO2023217377A1 (fr) Nœud iab mobile
US20250159578A1 (en) Managing reconfiguration identifiers
US12363594B2 (en) Frequency prioritization for terminal devices receiving a multicast broadcast service
EP4550886A1 (fr) Hiérarchisation de fréquence pour des dispositifs terminaux recevant un service de diffusion multidiffusion
US20250106668A1 (en) Measurements for one or more inter-cell purposes
US20250038825A1 (en) Defining a timeline for fast uplink beam and/or panel selection
US20250056369A1 (en) Measurement relaxation for dual-connectivity
US20250254642A1 (en) Positioning of collaborating devices with sidelink
WO2025093152A1 (fr) Priorisation de fréquence pour dispositifs à capacité réduite recevant un service de diffusion/multidiffusion
WO2022219060A1 (fr) Réacheminement dans un réseau d&#39;accès et de raccordement intégrés

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

Country of ref document: EP

Kind code of ref document: A1