Signaling port information of a user equipment port in a wireless communication system including a radio access network
By receiving and generating port information, and derive the network topology between UEs using LLDP and signaling technology, the problem of difficult to determine the network topology in wireless communication systems is solved, and network configuration and management efficiency is improved.
Patent Information
- Application Number
- CN202080013338.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-02-13
- Filing Date
- 2020-02-14
- Publication Date
- 2025-07-18
- Estimated Expiration
- 2040-02-14
AI Technical Summary
In wireless communication systems, it is difficult for the prior art to effectively deduce network topology information between user equipment (UE), resulting in inefficient network configuration and management.
By receiving and generating port information, using Link Layer Discovery Protocol (LLDP) and access/non-access layer signaling, a connectivity network topology between UEs, including identifier information for standard ports and intermediate ports, is derived, and a response message is generated to realize the configuration of network nodes.
It improves the configuration efficiency of network nodes in wireless communication systems, ensures the accuracy of network topology and efficient management, and is suitable for heterogeneous networks and distributed radio access networks.
Smart Images

Figure CN113424495B_ABST
Abstract
Description
[0001] Cross - Reference to Related Applications
[0002] This application claims priority to U.S. Application No. 16 / 790,374, filed on February 13, 2020, which claims the benefit and priority of U.S. Provisional Application No. 62 / 806,431, filed on February 15, 2019. Both of these applications are assigned to the assignee of this application and are hereby incorporated by reference in their entirety and for all applicable purposes as if fully set forth hereinbelow.
[0003] Background
[0004] Field of Disclosure
[0005] Aspects of the present disclosure relate to wireless communication, and more particularly to techniques for signaling port information of a user equipment port in a wireless communication system including a radio access network.
[0006] Description of Related Art
[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasting, etc. These wireless communication systems may employ multiple access technologies that are capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name just a few examples.
[0008] In some examples, a wireless multi-access communication system may include several base stations (BSs), each capable of supporting communications for multiple communication devices (also referred to as user equipment (UE)) simultaneously. In an LTE or LTE-A network, a set including one or more base stations may define an evolved Node B (eNB). In other examples (e.g., in a next-generation, New Radio (NR), or 5G network), a wireless multi-access communication system may include several distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with several central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set including one or more DUs in communication with the CU may define an access node (e.g., it may be referred to as a BS, 5G NB, next-generation Node B (gNB or gNodeB), transmission reception point (TRP), etc.). The BS or DU may communicate with a set of UEs on a downlink channel (e.g., for transmission from the BS or DU to the UE) and an uplink channel (e.g., for transmission from the UE to the BS or DU).
[0009] These multi-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. NR (e.g., New Radio or 5G) is an example of an emerging telecommunication standard. NR is an enhanced set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, leveraging new spectrums, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on the downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
[0010] Overview
[0011] The systems, methods, and devices of the present disclosure each have several aspects, where no single aspect is solely responsible for their desirable attributes. Without limiting the scope of the present disclosure as expressed by the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of the present disclosure provide certain advantages.
[0012] Some aspects provide a method for wireless communication. The method includes: receiving, at a network node, port information of one or more ports of one or more user equipments (UEs). The method further includes: the network node deriving, based on the port information of the one or more ports, a network topology indicating connectivity between devices including the one or more UEs.
[0013] Some aspects provide a method for wireless communication. The method includes: the network node generating port information for one or more ports of one or more user equipments (UEs). The method further includes: for a Link Layer Discovery Protocol (LLDP) received by a UE of the one or more UEs on a first port of the UE, the network node generating a response message using the port information generated for the first port.
[0014] Some aspects provide a method for wireless communication. The method includes: transmitting, from the UE to the network node, port information of one or more ports of the user equipment (UE) using one or more of Access Stratum (AS) signaling or Non-Access Stratum (NAS) signaling. The method further includes: the UE generating a response message for a Link Layer Discovery Protocol (LLDP) received by the UE.
[0015] Some aspects provide a user equipment (UE) configured for wireless communication. The UE includes: a memory, and a processor communicatively coupled to the memory. In some examples, the processor is configured to: transmit, using one or more of Access Stratum (AS) signaling or Non-Access Stratum (NAS) signaling, port information of one or more ports of the UE to a network node. In some examples, the processor is configured to: generate a response message for a Link Layer Discovery Protocol (LLDP) received by the UE.
[0016] Some aspects provide a network node for wireless communication. The network node includes: a memory and a processor communicatively coupled to the memory. In some examples, the processor is configured to: receive port information of one or more ports of one or more user equipments (UEs). In some examples, the processor is configured to: derive, based on the port information of the one or more ports, a network topology indicating connectivity between devices including the one or more UEs.
[0017] Some aspects provide a network node for wireless communication. In some examples, the network node includes: means for receiving port information of one or more ports of one or more user equipments (UEs). In some examples, the network node includes: means for deriving, based on the port information of the one or more ports, a network topology indicating connectivity between devices including the one or more UEs.
[0018] Certain aspects provide a non - transitory computer - readable storage medium storing instructions that, when executed by a processor of a network node, cause the network node to perform a wireless communication method. In some examples, the method includes: receiving port information of one or more ports of one or more user equipments (UEs). In some examples, the method includes: deriving a network topology indicating connectivity between devices including the one or more UEs based on the port information of the one or more ports.
[0019] Certain aspects provide a network node for wireless communication. In some examples, the network node includes a memory and a processor communicatively coupled to the memory. In some examples, the processor is configured to: generate port information for one or more ports of one or more user equipments (UEs). In some examples, the processor is configured to: for a Link Layer Discovery Protocol (LLDP) received by a UE of the one or more UEs on a first port of the UE, use the port information generated for the first port to generate a response message.
[0020] Certain aspects provide a network node for wireless communication. In some examples, the network node includes means for generating port information for one or more ports of one or more user equipments (UEs). In some examples, the network node includes means for using the port information generated for a first port to generate a response message for a Link Layer Discovery Protocol (LLDP) received by a UE of the one or more UEs on the first port of the UE.
[0021] Certain aspects provide a non - transitory computer - readable storage medium storing instructions that, when executed by a processor of a network node, cause the network node to perform a wireless communication method. In some examples, the method includes: generating port information for one or more ports of one or more user equipments (UEs). In some examples, the method includes: for a Link Layer Discovery Protocol (LLDP) received by a UE of the one or more UEs on a first port of the UE, using the port information generated for the first port to generate a response message.
[0022] Certain aspects provide a user equipment (UE) for wireless communication. In some examples, the UE includes means for transmitting port information of one or more ports of the UE to a network node using one or more of Access Stratum (AS) signaling or Non - Access Stratum (NAS) signaling. In some examples, the UE includes means for generating a response message for a Link Layer Discovery Protocol (LLDP) received by the UE.
[0023] Certain aspects provide a non-transitory computer-readable storage medium storing instructions that, when executed by a processor of a user equipment (UE), cause the UE to perform a wireless communication method. In some examples, the method includes: transmitting port information of one or more ports of the UE to a network node using one or more of access stratum (AS) signaling or non-access stratum (NAS) signaling. In some examples, the network node includes: generating a response message for a link layer discovery protocol (LLDP) received by the UE.
[0024] In certain aspects, the port information of a port includes one or more of the following: identifier information of the port, or identifier information of one or more adjacent ports of the port.
[0025] In certain aspects, the identifier information includes one or more of the following: one or more media access control (MAC) addresses, or one or more chassis identifiers.
[0026] In certain aspects, the port information is received via one or more of access stratum (AS) signaling or non-access stratum (NAS) signaling.
[0027] In certain aspects, the network node receives the port information from the one or more UEs via one or more intermediate nodes.
[0028] In certain aspects, the one or more intermediate nodes include one or more of the following: radio access network (RAN) nodes, access and mobility management function (AMF), session management function (SMF), or policy control function (PCF).
[0029] In certain aspects, the port information of the one or more ports includes port information of ports associated with multiple different protocol data unit (PDU) sessions, wherein the port information of ports associated with multiple different PDU sessions is received via separate signaling for each of the multiple different PDU sessions.
[0030] In certain aspects, the port information is received via signaling during one or more of protocol data unit (PDU) session establishment, PDU session modification, or UE registration.
[0031] In certain aspects, at least one port of the one or more ports includes an intermediate port configured to carry traffic having a final destination that is not local to the UE associated with the at least one port.
[0032] In some aspects, a response message to a Link Layer Discovery Protocol (LLDP) received by one of the one or more UEs is generated by one of the UE, a UE adapter associated with the UE, the network node, or an intermediate node.
[0033] Aspects of the present disclosure provide apparatuses, devices, processors, and computer-readable media for performing the methods described herein.
[0034] To achieve the foregoing and related purposes, these one or more aspects include the features that are fully described below and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of these one or more aspects. However, these features are merely indicative of the various ways in which the principles of the various aspects may be employed, and this description is not to be construed as limiting the scope of the various aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] For a more particular understanding of the manner in which the above-recited features of the present disclosure can be obtained, reference may be made to the aspects described in more detail below, some of which are illustrated in the drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.
[0037] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.
[0038] Figure 2 is a block diagram illustrating an example architecture of a distributed radio access network (RAN) in accordance with certain aspects of the present disclosure.
[0039] Figure 3 is a block diagram showing an example of a communication protocol stack for implementing an example RAN architecture in accordance with certain aspects of the present disclosure.
[0040] Figure 4 is a block diagram conceptually illustrating the design of an example base station (BS) and user equipment (UE) in accordance with certain aspects of the present disclosure.
[0041] Figure 5 illustrates an example system architecture for interworking between a 5G system (5GS) and an evolved universal mobile telecommunications system network (E-UTRAN) system in accordance with certain aspects of the present disclosure.
[0042] Figure 6 illustrates an example of a frame format for a telecommunications system in accordance with certain aspects of the present disclosure.
[0043] Figure 7 illustrates an example Ethernet network including an example wireless communication system switch (WCS-SW) in accordance with certain aspects.
[0044] Figure 8 is a flowchart illustrating example operations for wireless communication in accordance with certain aspects of the present disclosure.
[0045] Figure 9 is a flowchart illustrating example operations for wireless communication in accordance with certain aspects of the present disclosure.
[0046] Figure 10 is a flowchart illustrating example operations for wireless communication in accordance with certain aspects of the present disclosure.
[0047] Figure 11 illustrates a communication device in accordance with aspects of the present disclosure that may include various components configured to perform operations for the techniques disclosed herein.
[0048] Figure 12 illustrates a communication device in accordance with aspects of the present disclosure that may include various components configured to perform operations for the techniques disclosed herein.
[0049] For ease of understanding, wherever possible, the same reference numerals have been used to designate identical elements common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation.
[0050] Detailed Description
[0051] Aspects of the present disclosure provide an apparatus, method, processing system, and computer-readable medium for signaling port information of a user equipment port in a wireless communication system including a radio access network.
[0052] In a conventional wired Ethernet network, different devices can be conventionally interconnected via wired lines (e.g., wired links, wired cables). Some devices can be directly connected to each other because a port on one device is directly connected via a wired line to a port on another device. Additionally, some devices can be connected via one or more intermediate devices such as network bridges or switches. Examples can be further described with respect to network bridges, although the aspects discussed herein can similarly apply to other types of intermediate devices. For example, a network bridge includes multiple ports, and a port of one device can be connected via a wired line to a port of the network bridge, while a port of another device can be connected via a wired line to another port of the network bridge, thereby connecting these devices together via the network bridge. In some aspects, since traffic is sent in an Ethernet network from one source device to another destination device, and the bridge acts as an intermediary because the ultimate destination of such traffic is not the bridge itself, the port of the bridge that passes such traffic from the source to the destination is referred to as an intermediate port. Additionally, there may be several bridges between the source device and the destination device, and the ports of the bridges can be interconnected via wired lines as part of the Ethernet network. Thus, devices can exchange Ethernet frames with each other, including via one or more bridges, which can forward these Ethernet frames to appropriate ports based on the addressing in the Ethernet frames.
[0053] As shown in certain embodiments discussed herein, it may be desirable to replace a network bridge or direct connection and its conventional wired connection with a wireless communication system (WCS), such as a WCS corresponding to the 3GPP 5G NR standard or the 3GPP 4G LTE standard. Accordingly, in certain embodiments of the present disclosure, a network bridge or direct wired connection used in a wired Ethernet network can be replaced with what is referred to herein as a WCS switch (WCS-SW). With the WCS-SW, the wired connection associated with the network bridge or direct connection can be replaced with a wireless connection. This can be useful in several scenarios, such as those cases where a wired connection is not practical or infeasible. For example, such use of the WCS-SW may be useful for Internet of Things (IoT) applications where there are a large number of devices over a large area and for industrial IoT applications where cable management associated with a wired solution is not desired.
[0054] To enable the proper operation of devices, network bridges, and / or in some cases WCS-SW, they need to be configured. For example, in certain embodiments of the present disclosure, a central entity (such as a centralized network configuration (CNC)) may operate to configure any entity in the network (such as a device, network bridge, and / or WCS-SW), such as using appropriate forwarding tables, bandwidth reservation, etc. To enable the central entity to configure these entities, it may be necessary to derive a network topology indicating the connectivity between entities in the network. The network topology may relate to the layout of the network. For example, the network topology may describe one or more of the following: how different nodes in a communication network are connected to each other (e.g., link attributes, channel attributes, and / or node attributes) and how they communicate (e.g., communication protocols).
[0055] To derive the network topology, the central entity may receive port information associated with each of the ports (e.g., only intermediate ports or only standard ports, or intermediate ports and standard ports) of the entities in the network. The port information for a given port may include identifier information of the port itself (e.g., chassis identifier and / or media access control (MAC) address), and / or identifier information of the adjacent ports of the port. In some aspects, an adjacent port of a port is a port that is connected to the port via N or fewer hops (e.g., N or fewer Ethernet links, where an Ethernet link is between the ports with no other ports in between), and N is a positive integer. Based on this port information, the central entity can derive the network topology.
[0056] In some aspects, a device or network bridge having a port uses the Link Layer Discovery Protocol (LLDP) (e.g., station and MAC connectivity discovery) to determine the identifier information of the adjacent ports of the port. As part of LLDP, a device or network bridge having a port may send a message on the port and receive a response including the identifier information of the adjacent ports from the device or network bridge of the adjacent port. After the device or network bridge has collected the identifier information of the adjacent ports, it may send the port information of its port to the central entity.
[0057] WCS-SW includes one or more UEs, and one or more ports of the UEs (e.g., intermediate ports of the UEs) correspond to the ports of the WCS-SW. Accordingly, some aspects herein relate to techniques for signaling port information about one or more such ports of one or more UEs to a central entity (such as for the central entity to derive the network topology).
[0058] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the functionality and arrangement of the elements discussed without departing from the scope of the disclosure. Various examples may appropriately omit, substitute, or add various procedures or components. For example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with reference to some examples may be combined in some other examples. For instance, any number of the aspects set forth herein may be used to implement an apparatus or practice a method. Additionally, the scope of the disclosure is intended to cover such apparatus or methods practiced using other structures, functionality, or a combination of structures and functionality that complement or are additional to the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be implemented by one or more elements of the claims. The term "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any aspect described herein as "exemplary" need not be construed as superior or better than other aspects.
[0059] The techniques described herein may be used for various wireless communication technologies such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. Cdma2000 covers the IS-2000, IS-95, and IS-856 standards. A TDMA network may implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network may implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).
[0060] New Radio (NR) is an emerging wireless communication technology being developed in cooperation with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the wireless networks and radio technologies mentioned above and other wireless networks and radio technologies. For clarity, while aspects may be described herein using terms commonly associated with 3G and / or 4G wireless technologies, aspects of the present disclosure can be applied in communication systems of other generations, including NR technology, such as 5G and later generations.
[0061] New Radio (NR) access (e.g., 5G technology) can support various wireless communication services, such as enhanced mobile broadband (eMBB) targeted at wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) targeted at high carrier frequencies (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) targeted at non-backward compatible MTC technology, and / or mission critical targeted at ultra-reliable low latency communication (URLLC). These services can include latency and reliability requirements. These services can also have different transmission time intervals (TTIs) to meet the corresponding quality of service (QoS) requirements. Additionally, these services can coexist in the same subframe.
[0062] Example wireless communication system
[0063] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure can be implemented. For example, the wireless communication network 100 can be a New Radio (NR) or 5G network. In some aspects, the UE 120 and / or a network node (such as, in one example, a core network (CN) node 134) is configured to signal port information in accordance with the various aspects discussed herein. Additionally, in some aspects, the UE 120 and / or the CN node 134 is configured to respond to LLDP messages in accordance with the various aspects discussed herein. As shown, the wireless communication network 100 can be in communication with a CN 132. The CN 132 can include one or more CN nodes 134 that are in communication with one or more base stations (BSs) 110 and / or user equipment (UEs) 120 in the wireless communication network 100 via one or more interfaces.
[0064] As Figure 1As explained, the wireless communication network 100 may include several base stations (BSs) 110 and other network entities. A BS may be a station that communicates with user equipment (UE). Each BS 110 may provide communication coverage for a specific geographical area. In 3GPP, the term "cell" may refer to the coverage area of a Node B (NB) and / or the NB subsystem serving that coverage area, depending on the context in which the term is used. In an NR system, the terms "cell" and next-generation Node B (gNB or gNodeB), NR BS, 5G NB, access point (AP), or transmission reception point (TRP) may be interchangeable. In some examples, a cell may not have to be stationary, and the geographical area of a cell may move according to the location of a mobile BS. In some examples, base stations may be interconnected with each other and / or interconnected to one or more other base stations or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces, such as direct physical connections, wireless connections, virtual networks, or analogs using any suitable transmission network.
[0065] Generally, any number of wireless networks may be deployed in a given geographical area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency may support a single RAT in a given geographical area to avoid interference between wireless networks of different RATs. In some cases, an NR or 5G RAT network may be deployed.
[0066] A BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unconstrained access by UEs with a service subscription. A pico cell may cover a relatively small geographical area and may allow unconstrained access by UEs with a service subscription. A femto cell may cover a relatively small geographical area (e.g., a residence) and may allow constrained access by UEs associated with that femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). The BS for a macro cell may be referred to as a macro BS. The BS for a pico cell may be referred to as a pico BS. The BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1In the example shown, BSs 110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for pico cell 102x. BSs 110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can support one or more (e.g., three) cells.
[0067] Wireless communication network 100 may also include relay stations. A relay station is a station that receives a transmission of data and / or other information from an upstream station (e.g., a BS or a UE) and sends the transmission of the data and / or other information to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that relays transmissions for other UEs. In Figure 1 the example shown, relay station 110r can communicate with BS 110a and UE 120r to facilitate communication between BS 110a and UE 120r. A relay station can also be referred to as a relay BS, a relay, etc.
[0068] Wireless communication network 100 can be a heterogeneous network that includes different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relays, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference in wireless communication network 100. For example, a macro BS can have a high transmit power level (e.g., 20 watts), while pico BSs, femto BSs, and relays can have lower transmit power levels (e.g., 1 watt).
[0069] Wireless communication network 100 can support synchronous or asynchronous operation. For synchronous operation, each BS can have similar frame timing, and transmissions from different BSs can be approximately aligned in time. For asynchronous operation, each BS can have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein can be used for both synchronous and asynchronous operations.
[0070] Network controller 130 can be coupled to a set of BSs and provide coordination and control for these BSs. Network controller 130 can communicate with BS 110 via a backhaul. BSs 110 can also communicate with each other via a wireless or wired backhaul (e.g., directly or indirectly).
[0071] UE 120 (e.g., 120x, 120y, etc.) can be dispersed throughout the wireless communication network 100, and each UE can be stationary or mobile. A UE can also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premise equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or equipment, biometric sensor / device, wearable device (such as a smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired media. Some UEs can be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can, for example, provide connectivity to a network (such as a wide area network (e.g., the Internet) or a cellular network) or provide connectivity to the network via a wired or wireless communication link. Some UEs can be considered Internet of Things (IoT) devices, which can be narrowband IoT (NB-IoT) devices.
[0072] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency tones, frequency bins, etc. Each subcarrier can be modulated with data. Generally speaking, the modulation symbols are transmitted in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (referred to as a "resource block" (RB)) can be 12 subcarriers (or 180 kHz). Thus, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.
[0073] While aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may be applicable to other wireless communication systems such as NR. NR can utilize OFDM with a cyclic prefix (CP) on both the uplink and downlink and includes support for half-duplex operation using TDD. Beamforming can be supported and the beam direction can be configured dynamically. MIMO transmission with precoding can also be supported. The MIMO configuration in the DL can support up to 8 transmit antennas (multi-layer DL transmission with up to 8 streams) and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells can be supported using up to 8 serving cells.
[0074] In some examples, access to the air interface can be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication among some or all of the devices and equipment within its service area or cell. The scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for the scheduled communication, the subordinate entities utilize the resources allocated by the scheduling entity. The base station is not the only entity that can be used as a scheduling entity. In some examples, a UE can be used as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs can use the resources scheduled by the UE for wireless communication. In some examples, a UE can act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In the mesh network example, UEs can communicate directly with each other in addition to communicating with the scheduling entity.
[0075] According to some aspects, the CN node 134 and the UE 120 may be configured to signal port information of UE ports in a wireless communication system, such as a radio access network (RAN). As Figure 1 shown, the CN node 134 includes a port manager 112. According to aspects of the present disclosure, the port manager 112 may be configured to receive port information of one or more ports of one or more UEs, and derive a network topology indicating connectivity between devices including the one or more UEs based on the port information of the one or more ports. In some examples, the port manager 112 may optionally receive port information from the one or more UEs via one or more intermediate nodes. In some cases, the one or more intermediate nodes include one or more of the following: radio access network (RAN) nodes, access and mobility management function (AMF), session management function (SMF), or policy control function (PCF).
[0076] In some examples, the port manager 112 may be configured to generate port information for one or more ports of one or more UEs; and for Link Layer Discovery Protocol (LLDP) received by a UE on a first port of the UE, use the port information generated for the first port to generate a response message.
[0077] As Figure 1 shown, the UE 120a includes a port manager 122. According to aspects of the present disclosure, the port manager 122 may be configured to transmit port information of one or more ports of the UE to a network node (such as a core network node) using one or more of access stratum (AS) signaling (e.g., radio resource control (RRC) signaling and / or MAC control element (MAC-CE)) or non-access stratum (NAS) signaling, and generate a response message for Link Layer Discovery Protocol (LLDP) received by the UE. In some examples, the port information of a port includes one or more of the following: identifier information of the port, or identifier information of one or more adjacent ports of the port. For example, the identifier information includes one or more of the following: one or more MAC addresses, or one or more chassis identifiers.
[0078] In some examples, the functionality and communication between the core network node 134 and the UE 120a is sometimes referred to as NAS, which is contrasted with the AS corresponding to the functionality and communication between the UE and the RAN node. That is, in some examples, NAS relates to the communication protocol for communication between the UE 120a and the CN node 134, which can be transparently relayed by the RAN. Examples of NAS messages include update or attachment messages, authentication messages, service requests, etc. Accordingly, the AS can relate to the communication protocol for communication between the UE 120a and the BS 110a.
[0079] The term "network node" is widely used and, unless otherwise specifically indicated, is intended to describe a core network node (e.g., CN node 134), a RAN network node (e.g., BS 110a), or a central entity (e.g., Figure 2 ) such as the CNC 717 below Figure 1 that is capable of performing the various functions described in the present disclosure when connected and configured, outside of a distributed RAN (e.g., see below Figure 7 and the core network (e.g.,
[0080] In Figure 1 , the solid line with double arrows indicates the desired transmission between the UE and the serving BS, which is the BS designated to serve the UE on the downlink and / or uplink. The thin dashed line with double arrows indicates the interfering transmission between the UE and the BS.
[0081] Figure 2 Illustrates an example architecture of a distributed radio access network (RAN) 200, which can be implemented in the Figure 1 wireless communication network 100 illustrated in Figure 2 As shown in Figure 1 , the distributed RAN includes a core network (CN) 132 (e.g., Figure 1 CN132 of
[0082] The CN 132 can host core network functions. The CN 132 can be centrally deployed. The CN 132 functionality can be offloaded (e.g., to advanced wireless services (AWS)) to attempt to handle peak capacity. The CN 132 can include an access and mobility management function (AMF) 204 and a user plane function (UPF) 206. The AMF 204 and the UPF 206 can perform one or more core network functions.
[0083] According to certain aspects, CN 132 can be used to perform the various techniques and methods described herein. For example, according to aspects of the present disclosure, as Figure 2 shown, CN 132 has a port manager 112, which can be configured to receive port information of one or more ports of one or more UEs (e.g., Figure 1 UE 120), and derive a network topology indicating the connectivity between devices including the one or more UEs based on the port information of the one or more ports. In some examples, the port manager 112 can optionally receive port information from the one or more UEs via one or more intermediate nodes. In some cases, the one or more intermediate nodes include one or more of the following: RAN nodes (e.g., AN 208 and / or gNB 226), AMF 204, SMF, or PCF.
[0084] In some examples, the port manager 112 can be configured to generate port information for one or more ports of one or more UEs; and for a Link Layer Discovery Protocol (LLDP) received by a UE of the one or more UEs on a first port of the UE, use the port information generated for the first port to generate a response message. Although not shown, components of CN132 (such as a computer program product including a computer-readable medium having instructions stored (and / or encoded) thereon configured to be executable by one or more processors) can perform the various operations described herein.
[0085] AN 208 can communicate with CN 132 (e.g., via a backhaul interface). AN 208 can communicate with AMF 204 via an N2 (e.g., NG-C) interface. AN 208 can communicate with UPF 208 via an N3 (e.g., NG-U) interface. AN 208 can include a Central Unit Control Plane (CU-CP) 210, one or more Central Unit User Planes (CU-UP) 212, one or more Distributed Units (DU) 214-218, and one or more Antenna / Remote Radio Units (AU / RRU) 220-224. The CU and DU can also be referred to as gNB-CU and gNB-DU, respectively. One or more components of AN 208 can be implemented in gNB 226. AN 208 can communicate with one or more adjacent gNBs.
[0086] CU-CP 210 can be connected to one or more DUs 214-218. CU-CP 210 and DUs 214-218 can be connected via an F1-C interface. As Figure 2 shown, CU-CP 210 can be connected to multiple DUs, but a DU can be connected to only one CU-CP. Although Figure 2Only one CU-UP 212 is illustrated, but the AN 208 may include multiple CU-UPs. The CU-CP 210 selects an appropriate CU-UP(s) for the requested service (e.g., for a UE).
[0087] (The) CU-UP 212(s) may be connected to the CU-CP 210. For example, (the) DU-UP 212 and the CU-CP 210 may be connected via an E1 interface. The CU-CP 212 may be connected to one or more DUs 214-218. The CU-UP 212 and the DUs 214-218 may be connected via an F1-U interface. As Figure 2 shown, the CU-CP 210 may be connected to multiple CU-UPs, but a CU-UP may be connected to only one CU-CP.
[0088] A DU (such as DUs 214, 216, and / or 218) may host one or more TRPs (Transmit / Receive Points, which may include Edge Nodes (ENs), Edge Units (EUs), Radio Heads (RHs), Smart Radio Heads (SRHs), etc.). The DU may be located at the edge of a network with radio frequency (RF) functionality. The DU may be connected to multiple CU UPs that are connected to the same CU-CP (e.g., under the control of the same CU-CP) (e.g., for RAN sharing, Radio as a Service (RaaS), and service-specific deployments). The DU may be configured to serve traffic to a UE individually (e.g., dynamic selection) or jointly (e.g., joint transmission). Each of DUs 214-216 may be connected to one of AUs / RRUs 220-224.
[0089] The CU-CP 210 may be connected to multiple DUs that are connected to the same CU-UP 212 (e.g., under the control of the same CU-UP 212). The connectivity between the CU-UP 212 and the DUs may be established by the CU-CP 210. For example, a bearer context management function may be used to establish the connectivity between the CU-UP 212 and the DUs. Data forwarding between CU-UPs 212 may be via an Xn-U interface.
[0090] The distributed RAN 200 may support fronthaul solutions across different deployment types. For example, the RAN 200 architecture may be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter). The distributed RAN 200 may share features and / or components with LTE. For example, the AN 208 may support dual connectivity with NR and may share a common fronthaul for LTE and NR. The distributed RAN200 may, for example, implement cooperation between DUs 214-218 and within DUs 214-218 via the CU-CP 212. An inter-DU interface may not be used.
[0091] Each logical function can be dynamically distributed in the distributed RAN 200. As will be described in more detail with reference to Figure 3 the radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, physical (PHY) layer, and / or radio frequency (RF) layer can be adaptively placed at the AN and / or UE.
[0092] Figure 3 illustrates a diagram showing an example of a communication protocol stack 300 for implementing communication in a RAN (e.g., such as RAN 200) according to aspects of the present disclosure. The illustrated communication protocol stack 300 can be implemented by a device operating in a wireless communication system (such as a 5G NR system) (e.g., wireless communication network 100). In various examples, these layers of the protocol stack 300 can be implemented as separate software modules, parts of a processor or ASIC, parts of non-collocated devices connected by a communication link, or various combinations thereof. Collocated and non-collocated implementations can be used, for example, in the protocol stack for network access devices or UEs. As Figure 3 shown, the system can support various services over one or more protocols. One or more protocol layers of the protocol stack 300 can be implemented by the AN and / or UE.
[0093] As Figure 3 shown, the protocol stack 300 is split in the AN ( Figure 2 AN 208 in ). The RRC layer 305, PDCP layer 310, RLC layer 315, MAC layer 320, PHY layer 325, and RF layer 330 can be implemented by the AN. For example, CU-CP (e.g., Figure 2 CU-CP 210 in ) and CU-UP (e.g., Figure 2 CU-UP 212 in ) can each implement the RRC layer 305 and PDCP layer 310. The DU (e.g., Figure 2 DU 214-218 in ) can implement the RLC layer 315 and MAC layer 320. The AU / RRU (e.g., Figure 2 AU / RRU220-224 in ) can implement the (s)PHY layer 325 and the (s)RF layer 330. The PHY layer 325 can include a high PHY layer and a low PHY layer.
[0094] The UE can implement the entire protocol stack 300 (e.g., RRC layer 305, PDCP layer 310, RLC layer 315, MAC layer 320, the (s)PHY layer 325, and the (s)RF layer 330).
[0095] Figure 4 is an illustration (as Figure 1Block diagram of example components 400 of BS 110a and UE 120a (depicted in [FIGURE REFERENCE]) that can be used to implement aspects of the present disclosure. For example, antennas 452, processors 466, 458, 464, and / or controller / processor 480 of UE 120a and / or antennas 434, processors 420, 430, 438, and / or controller / processor 440 of BS 110a can be used to perform various techniques and methods described herein.
[0096] At BS 110a, the transmit processor 420 may receive data from data source 412 and control information from controller / processor 440. The control information may be used for physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), etc. The data may be used for physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols (e.g., primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, and / or reference symbols, if applicable, and may provide the output symbol streams to modulators (MOD) 432a to 432t. Each modulator 432 may process its respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a to 432t may be transmitted via antennas 434a to 434t, respectively.
[0097] At UE 120a, antennas 452a through 452r may receive downlink signals from base station 110 and may provide the received signals to demodulators (DEMOD) 454a through 454r in the transceiver, respectively. Each demodulator 454 may condition (e.g., filter, amplify, down-convert, and digitize) its respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 456 may obtain the received symbols from all demodulators 454a through 454r, perform MIMO detection on the received symbols when applicable, and provide detected symbols. The receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide the decoded data for UE 120a to data sink 460, and provide the decoded control information to controller / processor 480.
[0098] On the uplink, at UE 120a, the transmit processor 464 may receive and process data from data source 462 (e.g., for physical uplink shared channel (PUSCH)) and control information from controller / processor 480 (e.g., for physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for reference signals (e.g., sounding reference signal (SRS)). The symbols from the transmit processor 464 may be precoded by TX MIMO processor 466 when applicable, further processed by demodulators 454a through 454r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to base station 110. At BS 110a, the uplink signal from UE 120a may be received by antenna 434, processed by modulator 432, detected by MIMO detector 436 when applicable, and further processed by receive processor 438 to obtain the decoded data and control information transmitted by UE 120a. The receive processor 438 may provide the decoded data to data sink 439 and provide the decoded control information to controller / processor 440.
[0099] Controllers / processors 440 and 480 may direct operations at BS 110a and UE 120a, respectively. The processor 440 at BS 110 and / or other processors and modules may perform or direct the execution of the processes of the techniques described herein. The processor 480 at UE 120a and / or other processors and modules may perform or direct the execution of the processes for the techniques described herein. Memories 442 and 482 may store data and program code for BS 110 and UE 120, respectively. The scheduler 444 may schedule the UE for data transmission on the downlink and / or uplink.
[0100] For example, the antenna 452, processors 466, 458, 464, and / or the controller / processor 480 of the UE 120a can be used to perform the various techniques and methods described herein. As Figure 4 shown, the controller / processor 480 of the UE 120a has a port manager 122, which can be configured to transmit port information of one or more ports of the UE 120a to a network node (such as a core network node) using one or more of AS signaling (e.g., RRC signaling and / or MAC-CE) or NAS signaling. According to aspects of the present disclosure, the port manager 122 can also be configured to generate a response message for an LLDP received by the UE 120a. In some examples, the port information of a port includes one or more of the following: identifier information of the port, or identifier information of one or more adjacent ports of the port. For example, the identifier information can include one or more of the following: one or more MAC addresses, or one or more chassis identifiers. Although shown at the controller / processor 480, other components of the UE 120a can also be used to perform the operations described herein.
[0101] Figure 5 illustrates an example system architecture 500 for interworking between 5GS (e.g., such as the distributed RAN 200) and E-UTRAN-EPC according to certain aspects of the present disclosure. As Figure 5 shown, the UE 502 can be served by separate RANs 504A and 504B controlled by separate core networks 506A and 506B, where the RAN 504A provides E-UTRA service and the RAN 504B provides 5G NR service. The UE can operate under only one RAN / CN or two RANs / CNs at a time.
[0102] In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe. In NR, a subframe is still 1 ms, but the basic TTI is called a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16... slots), which depends on the subcarrier spacing. An NR RB is 12 consecutive frequency subcarriers. NR can support a base subcarrier spacing of 15 KHz, and other subcarrier spacings can be defined relative to the base subcarrier spacing, e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. The symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.
[0103] Figure 6It is a diagram showing an example of frame format 600 for NR. The transmission timeline for each of the downlink and uplink can be divided into radio frames. Each radio frame can have a predetermined duration (e.g., 10 ms), and can be divided into 10 subframes with indices 0 to 9, each subframe being 1 ms. Each subframe can include a variable number of time slots, depending on the subcarrier spacing. Each time slot can include a variable number of symbol periods (e.g., 7 or 14 symbols), depending on the subcarrier spacing. Indices can be assigned to the symbol periods in each time slot. A mini-slot (which can be referred to as a sub-slot structure) refers to a transmission time interval having a duration less than that of a time slot (e.g., 2, 3, or 4 symbols).
[0104] Each symbol in a time slot can indicate a link direction for data transmission (e.g., DL, UL, or flexible), and the link direction for each subframe can be switched dynamically. The link direction can be based on the time slot format. Each time slot can include DL / UL data as well as DL / UL control information.
[0105] In NR, a synchronization signal (SS) block is transmitted. The SS block includes PSS, SSS, and a two-symbol PBCH. The SS block can be transmitted in fixed time slot positions (such as Figure 6 symbol 0 - 3 shown). PSS and SSS can be used by the UE for cell search and capture. PSS can provide half-frame timing, SSS can provide CP length and frame timing. PSS and SSS can provide cell identity. PBCH carries some basic system information, such as downlink system bandwidth, timing information within a radio frame, SS burst set periodicity, system frame number, etc. The SS block can be organized into SS bursts to support beam sweeping. Further system information (such as, remaining minimum system information (RMSI), system information block (SIB), other system information (OSI)) can be transmitted on the physical downlink shared channel (PDSCH) in certain subframes. The SS block can be transmitted up to 64 times, e.g., up to 64 different beam directions for mmW. The up to 64 transmissions of the SS block are called an SS burst set. The SS blocks in an SS burst set are transmitted in the same frequency region, while the SS blocks in different SS burst sets can be transmitted at different frequency positions.
[0106] In some cases, two or more lower-level entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communication may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Everything (IoE) communication, IoT communication, mission-critical mesh, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal that is conveyed from one lower-level entity (e.g., UE1) to another lower-level entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even though the scheduling entity may be used for scheduling and / or control purposes. In some examples, sidelink signals may be conveyed using licensed spectrum (different from wireless local area networks, which typically use unlicensed spectrum).
[0107] A UE may operate in various radio resource configurations, including configurations associated with transmitting pilots using a dedicated resource set (e.g., radio resource control (RRC) dedicated state, etc.) or configurations associated with transmitting pilots using a common resource set (e.g., RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated resource set for transmitting pilot signals to the network. When operating in the RRC common state, the UE may select a common resource set for transmitting pilot signals to the network. In either case, the pilot signals transmitted by the UE may be received by one or more network access devices (such as an AN, or a DU, or parts thereof). Each receiving network access device may be configured to receive and measure the pilot signals transmitted on the common resource set and also receive and measure the pilot signals transmitted on the dedicated resource set allocated to the UE, where the network access device is a member of the set of monitoring network access devices for the UE. One or more receiving network access devices or the CU to which the receiving network access device transmits the pilot signal measurements may use these measurements to identify the serving cell of the UE or initiate a change to the serving cell for one or more UEs.
[0108] Example port information signaling
[0109] As discussed, some aspects herein relate to techniques for signaling port information of one or more ports of one or more UEs regarding WCS-SW to a central entity (such as for the central entity to deduce network topology). In some aspects, the central entity is a Centralized Network Configuration (CNC). In some aspects, the one or more ports of the one or more UEs are intermediate ports of the UE. For example, a UE may include one or more standard ports and one or more intermediate ports. In some aspects, a standard port is defined as a port that sends / receives traffic having an initial source address or a final destination address local to the UE including the port. In some aspects, an intermediate port is defined as a port that is used to forward traffic in an Ethernet network, where the traffic has an initial source address or a final destination address not local to the UE including the port. Thus, such intermediate ports are functionally similar to ports of gateways or switches in a conventional wired network.
[0110] Figure 7 An example Ethernet network 700 including an example WCS-SW 705 is illustrated in accordance with some aspects. WCS-SW 705 includes one or more functions of a core network (e.g., Figure 1 the CN 132). In some embodiments, WCS-SW 705 includes one or more core network nodes (e.g., or other suitable network nodes), such as one or more of the following: an AMF 707, a Time-Sensitive Networking (TSN) translator 703 including one or more of a Control Plane (CP) component 715 and a User Plane (UP) component 716 (e.g., as described in 3GPP TR 23.734), an Ethernet adapter 723, a UPF 709, and a Session Management Function (SMF) and a Policy Control Function (PCF) (collectively shown as SMF,PCF 708). In some examples, the AMF 707 may operate similarly to Figure 2 the AMF 204, and the UPF 709 may operate similarly to Figure 2 the UPF 206.
[0111] WCS-SW 705 further includes a plurality of UEs 711a - 711n (e.g., Figure 1UE 120, where n is a positive integer). Each UE 711 is coupled to one or more corresponding UE adapters 713, which serve as the network interface of the UE 711 to the Ethernet network and include one or more ports 714a - 714d. As used herein, multiple UEs and multiple UE adapters may sometimes be collectively referred to as UE 711 and UE adapter 713, respectively. The UE adapter 713 of the UE 711 may be integrated as hardware in the UE 711, configured as software in the UE 711, and / or externally coupled to the UE 711 (e.g., coupled via a wired line). The ports 714a - 714d of the UE adapter 713 may not be physical ports configured to couple to a physical line, but may include hardware and corresponding software components configured to implement the functionality of a physical port for a wireless connection.
[0112] WCS - SW 705 may include fewer or more UEs 711 and / or UE adapters 713. As shown, the first UE 711a includes a first UE adapter 713a, which includes a first port 714a corresponding to a first port identifier (ID 1). In some examples, ID 1 may include one or more of a first MAC identifier, a first chassis identifier, and / or include other port identifier information. In the example shown, the first port 714a provides a wireless connection between the first UE 711a and the first network 733 (e.g., an intermediate port of a bridge of network 2) via the first adapter 713a.
[0113] The second UE 711b includes a second UE adapter 713b, which includes a second port 714b corresponding to a second port identifier (ID 2). In some examples, ID 2 may include one or more of a second MAC identifier, a second chassis identifier, and / or include other port identifier information. In the example shown, the second port 714b provides a wireless connection between the second UE 711b and the first device 735 (e.g., a standard port of another UE) via the second adapter 713b.
[0114] The third UE 711n includes a third UE adapter 713n, which includes: (i) a third port 714c corresponding to a third port identifier (ID 3), and (ii) a fourth port 714d corresponding to a fourth port identifier (ID 4). In some examples, ID 3 and ID 4 may each include one or more of a third / fourth MAC identifier, a third / fourth chassis identifier, and / or include other port identifier information. In the illustrated example, the third port 714c provides a wireless connection between the third UE 711n and the second network 737 (e.g., an intermediate port of a bridge of network 3) via the third adapter 713n. The illustrated example also shows that the fourth port 714d provides a wireless connection between the third UE 711n and the second device 739 (e.g., a standard port of another UE) via the third adapter 713n. Although not shown, it will be appreciated that in some embodiments, one or more network nodes of the WCS-SW 705 (such as one or more core network nodes) are coupled to the UEs 711a-711n via a RAN (e.g., including a BS, such as BS 110). In certain aspects, each of the ports 714a-714d is an intermediate port of the corresponding UE 711a-711n.
[0115] One or more network nodes of the WCS-SW 705 (such as one or more core network nodes) may be communicatively coupled (e.g., via a wired line, wirelessly, etc.) to a central entity, shown as the CNC 717. For example, the CP component 715 of the TSN translator 703 may be coupled to the CNC 717 to provide a communication interface between the CNC 717 and one or more components of the WCS-SW 705 (such as the SMF, PCF 708, AMF 707, UE 711, etc.). As discussed, the CNC 717 may be configured to determine a network topology indicating the connectivity between devices including the UE 711. To enable the CNC 717 to determine such a network topology, port information for each of the ports 714a-714d (e.g., intermediate ports) of the UE 711 may be required. Such port information for a given port may include identifier information of the port itself (e.g., a chassis identifier, a media access control (MAC) address, and / or other port identifier information), and / or identifier information of adjacent ports. In certain aspects, an adjacent port of a port is a port that is connected to the port via N or fewer hops (e.g., N or fewer Ethernet links, where an Ethernet link is located between the ports with no other ports therebetween), and N is a positive integer.
[0116] Accordingly, in some aspects, the UEs 711 are configured to signal their port information to a core network node of the WCS-SW 705 that is coupled to the CNC 717. This core network node then sends the port information to the CNC 717. For example, the UEs 711 may signal the port information via the RAN (e.g., BS 110), and the RAN directly sends the port information to this core network node. In some aspects, in addition to the RAN, the UEs 711 also signal the port information via one or more additional intermediate nodes.
[0117] In some examples, the UEs 711 are configured to signal their port information to the TSN translator 703 that is a core network node coupled to the CNC 717. In some aspects, the UEs 711 signal the port information to the AMF 707 via the RAN, and the AMF 707 directly signals the port information to the TSN translator 703. In some aspects, the AMF 707 signals the port information to the TSN translator 703 via intermediate nodes (such as the SMF, PCF 708). In some aspects, the UEs 711 signal the port information to one or more core network nodes using one or more of access stratum (AS) signaling (e.g., radio resource control (RRC) signaling and / or MAC control element (MAC-CE)), or non-access stratum (NAS) signaling.
[0118] Figure 8 is a flow chart illustrating an example operation 800 for wireless communication in accordance with some aspects of the present disclosure. Operation 800 may be performed, for example, by a central network node (e.g., Figure 2 a node of the CN 132 such as Figure 7 the TSN translator 703, the CNC 717, etc.) of. Operation 800 may be a complementary operation to an operation performed by the UE (such as operation 900 described with respect to Figure 9 ). Operation 800 may be implemented as a software component executed and run on one or more processors.
[0119] Operation 800 may begin at block 805, where a network node receives port information of one or more ports of one or more user equipments (UEs). For example, block 805 may be performed by the TSN translator 703. Operation 800 continues at block 810, where the network node derives a network topology indicating connectivity between devices including the one or more UEs based on the port information of the one or more ports. For example, block 810 may be performed by the CNC 717.
[0120] In some aspects, the port information of a port includes one or more of the following: identifier information of the port, or identifier information of one or more adjacent ports of the port.
[0121] In some aspects, the identifier information includes one or more of the following: one or more media access control (MAC) addresses, or one or more chassis identifiers.
[0122] In some aspects, the port information is received via one or more of access stratum (AS) signaling or non-access stratum (NAS) signaling.
[0123] In some aspects, the network node receives the port information from the one or more UEs via one or more intermediate nodes.
[0124] In some aspects, the one or more intermediate nodes include one or more of the following: radio access network (RAN) nodes, access and mobility management function (AMF), session management function (SMF), or policy control function (PCF).
[0125] In some aspects, the port information of the one or more ports includes the port information of ports associated with multiple different protocol data unit (PDU) sessions, wherein the port information of ports associated with multiple different PDU sessions is received via separate signaling for each of the multiple different PDU sessions.
[0126] In some aspects, the port information is received via signaling during one or more of protocol data unit (PDU) session establishment, PDU session modification, or UE registration.
[0127] In some aspects, at least one port of the one or more ports includes an intermediate port configured to carry traffic having a final destination that is not local to the UE associated with the at least one port.
[0128] In some aspects, a response message for a link layer discovery protocol (LLDP) received by a UE of the one or more UEs is generated by one of the UE, a UE adapter associated with the UE, the network node, or an intermediate node.
[0129] Figure 9 is a flow chart illustrating an example operation 900 for wireless communication in accordance with some aspects of the present disclosure. Operation 900 may be performed, for example, by a UE (such as, for example Figure 1 UE 120 in the wireless communication network 100, Figure 7 UE 711, etc.). Operation 900 may be implemented on one or more processors (e.g., Figure 4software components that are executed and run on a processor 480). Additionally, signal transmission and reception performed by the UE in operation 900 can be implemented, for example, by one or more antennas (e.g., Figure 4 antenna 452) of. In some aspects, signal transmission and / or reception performed by the UE can be implemented by obtaining and / or outputting signals via a bus interface of one or more processors (e.g., processor 480).
[0130] Operation 900 can begin at block 905 by transmitting port information of one or more ports of a user equipment (UE) to a network node (e.g., Figure 2 a node of CN 132 such as Figure 7 TSN translator 703, CNC 717, etc.) of using one or more of access stratum (AS) signaling or non-access stratum (NAS) signaling. Operation 900 continues at block 910 by generating a response message for a link layer discovery protocol (LLDP) received by the UE.
[0131] In some aspects, the port information of a port includes one or more of the following: identifier information of the port, or identifier information of one or more adjacent ports of the port.
[0132] In some aspects, the identifier information includes one or more of the following: one or more media access control (MAC) addresses, or one or more chassis identifiers.
[0133] In some aspects, the port information is transmitted via one or more intermediate nodes.
[0134] In some aspects, the one or more intermediate nodes include one or more of the following: a radio access network (RAN) node, an access and mobility management function (AMF), a session management function (SMF), or a policy control function (PCF).
[0135] In some aspects, the port information of the one or more ports includes port information of ports associated with multiple different protocol data unit (PDU) sessions, where the port information of ports associated with multiple different PDU sessions is transmitted / received via separate signaling for each of the multiple different PDU sessions. For example, UE 711 can have multiple different PDU sessions, and accordingly, separately transmit the port information of ports for different PDU sessions.
[0136] In some aspects, the port information is transmitted / received via signaling during one or more of PDU session establishment, PDU session modification, or user equipment registration.
[0137] As discussed, in an Ethernet network, a device (e.g., UE 711) can use LLDP message exchange to obtain identifier information of an adjacent port, such as reporting the identifier information to the CNC 717 for it to determine the network topology. In some aspects, when the UE 711 receives an LLDP message requesting the identifier information of a port (e.g., from an external network) on the port, the UE 711 itself is configured to generate a response message including the identifier information of the port and transmit the response message to the device that sent the LLDP message. In some aspects, the UE adapter 713 associated with the UE 711 generates and transmits a response message in response to the LLDP message. In some aspects, as discussed, the LLDP message is forwarded in the network (e.g., by the UE 711) to a network node or an intermediate node (e.g., the TSN translator 703, the AMF 707, the UPF 709, etc.), and the network node or the intermediate node is configured to generate a response message and transmit the response message to the device that sent the LLDP message (instead of the UE 711).
[0138] In some aspects, the UEs 711 are not configured to signal their port information to a network node of the WCS-SW 705 that is coupled to the CNC 717. Instead, in some aspects, the network node is configured to generate identifier information for each of the ports of the UEs of the WCS-SW 705. For example, the TSN translator 703 can be configured to generate identifier information (e.g., randomly, according to an algorithm, etc.) for each of ports 1-4 of the UE 711 of the WCS-SW 705. The generated identifier information may be different from the actual identifier information of the ports used for routing traffic in the network. This can help reduce the network bandwidth for the UEs to signal port information to the network node. In some aspects, the network node further sends the port information (including the generated identifier information) of the port to the CNC 717 to generate the network topology.
[0139] In some aspects, the port information of the one or more ports includes the port information of the ports associated with multiple different PDU sessions, wherein the port information of the ports associated with multiple different PDU sessions is transmitted / received via separate signaling for each of the multiple different PDU sessions (e.g., transmitted by the UE and received by the CN). In some aspects, the port information is transmitted / received via signaling during one or more of PDU session establishment, PDU session modification, or user equipment registration.
[0140] In some aspects, when the UE 711 receives a Link Layer Discovery Protocol (LLDP) message (e.g., from an external network) requesting identifier information for a port from a device (e.g., UE 711, network node, etc.) on the port, the UE 711 forwards the LLDP message to the network node (or the message is otherwise sent to the network node in the network and the UE 711 ignores the LLDP message). The network node is then configured to generate a response message and transmit the response message to the device (instead of the UE 711). The network node is configured to include the generated identifier information for the port in the response message, rather than the actual identifier information for the port. In other aspects, the network node sends the generated identifier information for the port to the UE 711, such that the UE 711 or its corresponding UE adapter 713 can generate a response message and transmit the response message to the device. In other aspects, the network node sends the generated identifier information for the port to an intermediate node, such that the intermediate node can generate a response message and transmit the response message to the device. Accordingly, the adjacent port information ultimately sent to the CNC 717 also includes generated identifier information, rather than actual identifier information, such that the CNC 717 can generate a network topology based on the generated identifier information.
[0141] In some aspects, at least one of the one or more ports includes an intermediate port that is configured to carry traffic having a final destination that is not local to the UE.
[0142] In some aspects, the response message is generated by one of the UE, the intermediate node, the network node, or a UE adapter associated with the UE.
[0143] Figure 10 is a flow chart illustrating an example operation 1000 for wireless communication in accordance with some aspects of the present disclosure. Operation 1000 may be performed, for example, by a central network node (e.g., Figure 2 a node of the CN 132 such as Figure 7 the TSN translator 703, CNC 717, etc.). Operation 1000 may be implemented as a software component that is executed and run on one or more processors.
[0144] Operation 1000 may begin at block 1005, where a network node generates port information for one or more ports of one or more user equipments (UEs). Operation 1000 continues at block 1010, where the network node uses the port information generated for a first port to generate a response message for a Link Layer Discovery Protocol (LLDP) received by a UE of the one or more UEs on the first port of the UE.
[0145] In some aspects, the port information of a single port includes one or more of the following: identifier information of the port, or identifier information of one or more adjacent ports of the port.
[0146] In some aspects, the identifier information includes one or more of the following: one or more media access control (MAC) addresses, or one or more chassis identifiers.
[0147] In some aspects, the generated port information associated with a UE among the one or more UEs is sent to the UE.
[0148] In some aspects, the port information of the one or more ports includes the port information of ports associated with multiple different protocol data unit (PDU) sessions, where the port information of ports associated with multiple different PDU sessions is generated separately for each of the multiple different PDU sessions.
[0149] In some aspects, the port information is generated during one or more of protocol data unit (PDU) session establishment, PDU session modification, or UE registration.
[0150] In some aspects, the response message is generated by one of the UE, an intermediate node, the network node, or a UE adapter associated with the UE.
[0151] Figure 11 Illustrated is a communication device 1100 that may include various components (e.g., corresponding to apparatus plus function components) configured to perform operations (such as Figure 8 and / or Figure 10 the operations illustrated therein). The communication device 1100 includes a processing system 1102 coupled to a transceiver 1108. The transceiver 1108 is configured to transmit and receive signals (such as various signals described herein) for the communication device 1111 via an antenna 1100. The processing system 1102 may be configured to perform processing functions for the communication device 1100, including processing signals received and / or to be transmitted by the communication device 1100.
[0152] The processing system 1102 includes a processor 1104 coupled to a computer-readable medium / memory 1112 via a bus 1106. In some aspects, the computer-readable medium / memory 1112 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1104, cause the processor 1104 to perform Figure 8 and / or Figure 10The operations illustrated therein or other operations for performing the various techniques for port information signaling discussed herein. In some aspects, the computer-readable medium / memory 1112 stores code 1114 for receiving port information, code 1116 for deriving a network topology, code 1118 for generating port information, and code 1120 for generating a response message. In some aspects, the processor 1104 has circuitry configured to implement the code stored in the computer-readable medium / memory 1112. The processor 1104 includes circuitry 1124 for receiving port information, circuitry 1126 for deriving a network topology, circuitry 1128 for generating port information, and circuitry 1130 for generating a response message.
[0153] Figure 12 illustrates a communication device 1200 that may include various components (e.g., corresponding to apparatus plus function components) configured to perform operations (such as Figure 9 the operations illustrated therein) disclosed herein. The communication device 1200 includes a processing system 1202 coupled to a transceiver 1208. The transceiver 1208 is configured to transmit and receive signals (such as the various signals described herein) for the communication device 1200 via an antenna 1210. The processing system 1202 may be configured to perform processing functions for the communication device 1200, including processing signals received and / or to be transmitted by the communication device 1200.
[0154] The processing system 1202 includes a processor 1204 coupled to a computer-readable medium / memory 1212 via a bus 1206. In some aspects, the computer-readable medium / memory 1212 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1204, cause the processor 1204 to perform Figure 9 the operations illustrated therein or other operations for performing the various techniques for port information signaling discussed herein. In some aspects, the computer-readable medium / memory 1212 stores code 1214 for transmitting port information and code 1220 for generating a response message. In some aspects, the processor 1204 has circuitry configured to implement the code stored in the computer-readable medium / memory 1212. The processor 1204 includes circuitry 1224 for transmitting port information and circuitry 1230 for generating a response message.
[0155] Example aspects
[0156] In a first aspect, a method for wireless communication includes: receiving, at a network node, port information of one or more ports of one or more user equipments (UEs); and deriving, by the network node based on the port information of the one or more ports, a network topology indicating connectivity between devices including the one or more UEs. This can provide the network node with the ability to determine a network topology indicating connectivity between network entities (e.g., UEs) having one or more standard ports and one or more intermediate ports.
[0157] In a second aspect, separately or in combination with the first aspect, the port information of a port includes one or more of the following: identifier information of the port, or identifier information of one or more adjacent ports of the port. This can provide the network node with the information required to determine a network topology indicating connectivity between entities in the network.
[0158] In a third aspect, separately or in combination with one or more of the first and second aspects, the identifier information includes one or more of the following: one or more media access control (MAC) addresses, or one or more chassis identifiers. This can provide the network node with the information required to determine a network topology indicating connectivity between entities in the network via layer 2 (L2) communication.
[0159] In a fourth aspect, separately or in combination with one or more of the first to third aspects, the port information is received via one or more of access stratum (AS) signaling or non-access stratum (NAS) signaling. This can provide the network node with the information required to determine a network topology indicating connectivity between entities in the network via communication at different layers.
[0160] In a fifth aspect, separately or in combination with one or more of the first to fourth aspects, the network node receives the port information from the one or more UEs via one or more intermediate nodes. This can reduce the communication timeline between the UE and the network.
[0161] In a sixth aspect, separately or in combination with one or more of the first to fifth aspects, the one or more intermediate nodes include one or more of the following: radio access network (RAN) nodes, access and mobility management function (AMF), session management function (SMF), or policy control function (PCF). This provides a communication path between the UE and the network.
[0162] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the port information of the one or more ports includes the port information of ports associated with a plurality of different protocol data unit (PDU) sessions, wherein the port information of ports associated with a plurality of different PDU sessions is received via separate signaling for each of the plurality of different PDU sessions. This provides a basis for providing port information.
[0163] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the port information is received via signaling during one or more of protocol data unit (PDU) session establishment, PDU session modification, or UE registration. This provides a mechanism for providing port information.
[0164] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, at least one port of the one or more ports includes an intermediate port configured to carry traffic having a final destination that is not local to the UE associated with the at least one port. This can provide a network node with the information needed to determine the network topology indicating connectivity between entities in the network via a port having an initial source address and / or a final destination address that is not local to the UE.
[0165] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, a response message for a Link Layer Discovery Protocol (LLDP) received by a UE of the one or more UEs is generated by one of the UE, a UE adapter associated with the UE, the network node, or an intermediate node. This provides a mechanism for responding to LLDP.
[0166] In an eleventh aspect, a method for wireless communication includes: generating, by a network node, port information for one or more ports of one or more user equipments (UEs); and generating, by the network node, a response message for a Link Layer Discovery Protocol (LLDP) received by a UE of the one or more UEs on a first port of the UE using the port information generated for the first port. This can provide the network node with the ability to determine the network topology indicating connectivity between network entities (e.g., UEs) having one or more standard ports and one or more intermediate ports.
[0167] In a twelfth aspect, either alone or in combination with the eleventh aspect, the port information of a port includes one or more of the following: identifier information of the port, or identifier information of one or more adjacent ports of the port. This can provide a network node with the information needed to determine the network topology indicating connectivity between entities in the network.
[0168] In a thirteenth aspect, either alone or in combination with the eleventh and / or twelfth aspects, the identifier information includes one or more of the following: one or more Media Access Control (MAC) addresses, or one or more chassis identifiers. This can provide the network node with the information needed to determine the network topology indicating connectivity between entities in the network via layer 2 (L2) communication.
[0169] In a fourteenth aspect, either alone or in combination with one or more of the eleventh to thirteenth aspects, the generated port information associated with a UE of the one or more UEs is sent to the UE. This provides the network node with a mechanism for communicating the generated port information to the UE.
[0170] In a fifteenth aspect, either alone or in combination with one or more of the eleventh to fourteenth aspects, the port information of the one or more ports includes the port information of ports associated with a plurality of different Protocol Data Unit (PDU) sessions, wherein the port information of the ports associated with the plurality of different PDU sessions is generated separately for each of the plurality of different PDU sessions. This provides a basis for providing port information.
[0171] In a sixteenth aspect, either alone or in combination with one or more of the eleventh to fifteenth aspects, the port information is generated during one or more of Protocol Data Unit (PDU) session establishment, PDU session modification, or UE registration. This provides a basis for generating port information.
[0172] In a seventeenth aspect, either alone or in combination with one or more of the eleventh to sixteenth aspects, the response message is generated by one of the UE, an intermediate node, the network node, or a UE adapter associated with the UE. This provides the source of the response message.
[0173] In an eighteenth aspect, a method for wireless communication includes: transmitting, from a user equipment (UE) to a network node, port information of one or more ports of the UE using one or more of access stratum (AS) signaling or non-access stratum (NAS) signaling; and generating, by the UE, a response message for a Link Layer Discovery Protocol (LLDP) received by the UE. This can provide the network node with the ability to determine the network topology indicating connectivity between network entities (e.g., UEs) having one or more standard ports and one or more intermediate ports.
[0174] In a nineteenth aspect, either alone or in combination with the eighteenth aspect, the port information of a port includes one or more of the following: the identifier information of the port, or the identifier information of one or more adjacent ports of the port. This can provide the network node with the information needed to determine the network topology indicating connectivity between entities in the network.
[0175] In a twentieth aspect, either alone or in combination with the eighteenth aspect and / or the nineteenth aspect, at least one of the one or more ports includes an intermediate port that is configured to carry traffic having a final destination that is not local to the UE. This can provide a network node with the information needed to determine the network topology indicating connectivity between entities in the network via a port having an initial source address and / or a final destination address that is not local to the UE.
[0176] In a twenty - first aspect, either alone or in combination with the eighteenth to twentieth aspects, the port information is transmitted via one or more intermediate nodes. This can reduce the communication timeline between the UE and the network.
[0177] In a twenty - second aspect, either alone or in combination with the eighteenth to twenty - first aspects, the one or more intermediate nodes include one or more of the following: a radio access network (RAN) node, an access and mobility management function (AMF), a session management function (SMF), or a policy control function (PCF). This provides a communication path between the UE and the network.
[0178] In a twenty - third aspect, either alone or in combination with the eighteenth to twenty - second aspects, the port information of the one or more ports includes the port information of ports associated with multiple different protocol data unit (PDU) sessions, wherein the port information of ports associated with multiple different PDU sessions is transmitted via separate signaling for each of the multiple different PDU sessions. This provides a basis for providing port information.
[0179] In a twenty - fourth aspect, either alone or in combination with the eighteenth to twenty - third aspects, the port information is transmitted via signaling during one or more of protocol data unit (PDU) session establishment, PDU session modification, or UE registration. This provides a mechanism for providing port information.
[0180] In a twenty - fifth aspect, either alone or in combination with the eighteenth to twenty - fourth aspects, at least one of the one or more ports includes an intermediate port that is configured to carry traffic having a final destination that is not local to the UE. This can provide a network node with the information needed to determine the network topology indicating connectivity between entities in the network via a port having an initial source address and / or a final destination address that is not local to the UE.
[0181] In a twenty - sixth aspect, either alone or in combination with the eighteenth to twenty - fifth aspects, the response message is generated by one of the UE, an intermediate node, the network node, or a UE adapter associated with the UE. This provides the source of the response message.
[0182] Additional Considerations
[0183] Each of the methods disclosed herein includes one or more steps or acts for implementing the method. These method steps and / or acts may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of the steps or acts is specified, the order and / or use of the specific steps and / or acts may be altered without departing from the scope of the claims.
[0184] As used herein, the phrase "at least one of" in reference to a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a - b, a - c, b - c, and a - b - c, as well as any combination having multiple of the same element (e.g., a - a, a - a - a, a - a - b, a - a - c, a - b - b, a - c - c, b - b, b - b - b, b - b - c, c - c, and c - c - c, or any other ordering of a, b, and c).
[0185] As used herein, the term "determine" covers a variety of acts. For example, "determine" may include computing, calculating, processing, deriving, researching, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Also, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determine" may include parsing, selecting, choosing, establishing, and the like.
[0186] The foregoing description has been provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims, wherein the recitation of a singular element is not intended to mean "one and only one" (unless specifically so stated) but "one or more." Unless specifically stated otherwise, the term "some / a" refers to one or more. Elements of the various aspects described throughout this disclosure that are presently known or later come to be known to those of ordinary skill in the art as all structural and functional equivalents are hereby expressly incorporated by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. No element of a claim should be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the element is recited using the phrase "step for."
[0187] The various operations of the methods described above can be performed by any suitable means capable of performing the corresponding functions. These means may include various hardware and / or software components and / or modules, including but not limited to circuitry, application specific integrated circuits (ASICs), or processors. Generally, where operations illustrated in the figures are present, these operations may have corresponding paired apparatus plus function components with similar numbers.
[0188] The various illustrative logical blocks, modules, and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0189] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented with a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, machine-readable media, and a bus interface. The bus interface may be used to connect a network adapter, etc. to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of user terminal 120 (see Figure 1 ), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as a timing source, peripherals, voltage regulators, power management circuits, and similar circuits, which are well known in the art and will not be described further herein. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry capable of executing software. Depending on the specific application and overall design constraints imposed on the overall system, those of ordinary skill in the art will recognize how best to implement the functionality described with respect to the processing system.
[0190] If implemented in software, each function may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Software should be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including execution of software modules stored on a machine-readable storage medium. The computer-readable storage medium may be coupled to the processor such that the processor can read from and write to the storage medium. In an alternative, the storage medium may be integrated into the processor. By way of example, machine-readable media may include transmission lines, carrier waves modulated with data, and / or computer-readable storage media separate from a wireless node having instructions stored thereon, all of which may be accessed by the processor via a bus interface. Alternatively or additionally, machine-readable media or any part thereof may be integrated into the processor, such as may be the case with a cache and / or a general register file. By way of example, examples of machine-readable media may include RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read Only Memory), EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. Machine-readable media may be embodied in a computer program product.
[0191] Software modules may include a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. Computer-readable media may include several software modules. These software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. These software modules may include a transmission module and a reception module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, when a triggering event occurs, a software module may be loaded from a hard drive into RAM. During execution of the software module, the processor may load some instructions into a cache to improve access speed. One or more cache lines may then be loaded into the general register file for execution by the processor. When referring to the functionality of a software module hereinafter, it will be understood that such functionality is implemented by the processor when executing instructions from the software module.
[0192] Any connection is also properly termed a computer-readable medium. For example, if the software is delivered from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technology such as infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology such as infrared, radio, and microwave is included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and disc, where disk typically magnetically reproduces data, while disc optically reproduces data with a laser. Thus, in some aspects, a computer-readable medium may include a non-transitory computer-readable medium (e.g., a tangible medium). Additionally, for other aspects, a computer-readable medium may include a transitory computer-readable medium (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.
[0193] Accordingly, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored thereon (and / or encoded thereon) that can be executed by one or more processors to perform the operations described herein. For example, instructions for performing the operations described and illustrated in Figures 8 - 10 are provided.
[0194] Furthermore, it should be appreciated that modules and / or other suitable means for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by a user terminal and / or a base station, where applicable. For example, such devices can be coupled to a server to facilitate transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.) such that once the storage device is coupled to or provided to the user terminal and / or base station, the device can obtain the various methods. Additionally, any other suitable technology can be utilized that is adapted to provide the methods and techniques described herein to a device.
[0195] It will be understood that the claims are not limited to the exact configurations and components set forth above. Various modifications, substitutions, and alterations can be made to the layout, operation, and details of the methods and apparatuses described above without departing from the scope of the claims.
Claims
1. A method for wireless communication at a first network node external to a Wireless Communication System Switch (WCS-SW), the WCS-SW including a User Equipment (UE) among one or more UEs and at least one core network node of a cellular network, the method comprising: Receiving, via the at least one core network node, port information of the following ports from the UE: (i) a port of the UE and (ii) an intermediate port adjacent to the port of the UE, wherein the intermediate port belongs to an intermediate node for carrying traffic from the UE to a final destination not local to the UE, and wherein each of the one or more UEs, the core network node, and the intermediate node form at least a part of the WCS-SW; And Deriving, based on the received port information, a network topology indicating connectivity between devices including the one or more UEs and the intermediate node.
2. The method according to claim 1, wherein the port information includes identifier information of the port and the intermediate port.
3. The method according to claim 2, wherein the identifier information includes one or more of the following: one or more Media Access Control (MAC) addresses, or one or more chassis identifiers.
4. The method according to claim 1, wherein the port information is received via one or more of Access Stratum (AS) signaling or Non-Access Stratum (NAS) signaling.
5. The method according to claim 1, wherein the first network node receives the port information via the intermediate node.
6. The method according to claim 5, wherein the intermediate node includes one of the following: a Radio Access Network (RAN) node, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), or a Policy Control Function (PCF).
7. The method according to claim 1, wherein each of the port of the UE and the intermediate port of the intermediate node is associated with a plurality of different protocol data unit (PDU) sessions, and wherein receiving the port information further comprises: Receiving, from the UE, port information associated with each of the plurality of different PDU sessions via separate signaling for each of the plurality of different PDU sessions.
8. The method according to claim 1, wherein the port information is received during one or more of Protocol Data Unit (PDU) session establishment, PDU session modification, or UE registration.
9. The method according to claim 1, wherein the WCS-SW is an intermediate switch between (i) at least one of a first device or a first network and (ii) at least one of a second device or a second network; and The final destination is external to the WCS-SW.
10. A method for wireless communication by a network node, comprising: Receiving a forwarded Link Layer Discovery Protocol (LLDP) message from a first network entity, the LLDP message being configured to request port information of a first port of the first network entity, the LLDP message being transmitted to the first port of the first network entity via a second port of a second network entity, the first port being adjacent to the second port, the first network entity and the second network entity forming a part of a Wireless Communication System Switch (WCS-SW); Generate port information for one or more ports of the first network entity, the one or more ports including the first port; and Generate an LLDP response message and transmit it to the second network entity, the LLDP response message indicating the port information generated for the one or more ports of the first network entity.
11. The method according to claim 10, wherein the port information of the one or more ports includes identifier information for each of the one or more ports.
12. The method according to claim 11, wherein the identifier information includes one or more of the following: one or more media access control (MAC) addresses, or one or more chassis identifiers.
13. The method according to claim 10, wherein the first network entity is a first user equipment (UE), and wherein the second network entity is a second UE.
14. The method according to claim 10, wherein the port information of the one or more ports includes port information of ports associated with multiple different protocol data unit (PDU) sessions, and wherein the port information of the ports associated with multiple different PDU sessions is generated separately for each of the multiple different PDU sessions.
15. The method according to claim 10, wherein the port information is generated during one or more of protocol data unit (PDU) session establishment, PDU session modification, or UE registration.
16. A method for wireless communication at a user equipment (UE), comprising: Transmit first port information of a port belonging to the UE to a core network node using one or more of access stratum (AS) signaling or non-access stratum (NAS) signaling; Receive a Link Layer Discovery Protocol (LLDP) message from a first port of a first network node, the LLDP message being configured to request second port information of a port belonging to the UE and adjacent to the first port, the UE and the first network node forming a first part of a wireless communication system switch (WCS-SW); Generate a response message to the received LLDP message, the response message including the second port information; and Transmit the response message to the first network node.
17. The method according to claim 16, wherein the first port information and the second port information include identifier information for each corresponding port.
18. The method according to claim 17, wherein the identifier information includes one or more of the following: one or more media access control (MAC) addresses, or one or more chassis identifiers.
19. The method according to claim 16, wherein the response message to the received LLDP message is transmitted to the first network node via one or more intermediate nodes, the one or more intermediate nodes forming a second part of the WCS-SW.
20. The method according to claim 19, wherein the one or more intermediate nodes comprise one or more of the following: a radio access network (RAN) node, an access and mobility management function (AMF), a session management function (SMF), or a policy control function (PCF).
21. The method according to claim 16, wherein the first port information and the second port information each include port information associated with a plurality of different protocol data unit (PDU) sessions, wherein the first port information is transmitted via separate signaling for each of the plurality of different PDU sessions, and wherein transmitting the response message to the first network node comprises: Transmit the second port information via separate signaling for each of the plurality of different PDU sessions.
22. The method according to claim 16, wherein the first port information and the second port information are transmitted via signaling during one or more of a protocol data unit (PDU) session establishment, a PDU session modification, or a UE registration.
23. The method according to claim 16, further comprising: Transmit the response message to the first network node via an intermediate port of an intermediate node, the intermediate port being configured to carry traffic to the first network node that is not local to the UE.
24. The method according to claim 16, wherein the response message is generated by a UE adapter associated with the UE, the UE adapter providing an interface between the WCS-SW and a device outside the WCS-SW.
25. A user equipment (UE) configured for wireless communication, comprising: A memory; And A processor communicatively coupled to the memory, wherein the processor is configured to: Transmit first port information of a port belonging to the UE to a core network node using one or more of access stratum (AS) signaling or non-access stratum (NAS) signaling; Receive a link layer discovery protocol (LLDP) message from a first port of a first network node, the LLDP message being configured to request second port information of a port belonging to the UE and adjacent to the first port, the UE and the first network node forming a first part of a wireless communication system switch (WCS-SW); Generate a response message to the received LLDP message, the response message including the second port information; And Transmit the response message to the first network node.
26. The UE according to claim 25, wherein the first port information and the second port information include identifier information of each corresponding port.
27. The UE according to claim 26, wherein the processor is further configured to: transmit the response message to the first network node via an intermediate port of an intermediate node, the intermediate port being configured to carry traffic to the first network node that is not local to the UE.
28. The UE according to claim 25, wherein the response message to the received LLDP message is transmitted to the first network node via one or more intermediate nodes, the one or more intermediate nodes forming a second part of the WCS-SW.
Citation Information
Patent Citations
Topology determination method, message response method, controller and switch
CN107566277A