System, method and apparatus for managing network resources

Abstract

A system, method and apparatus for managing network resources are provided. The system includes a plurality of wireless entities, the plurality of wireless entities including mobile wireless entities and fixed-location wireless entities. The system also includes a plurality of computing devices, each of the plurality of computing devices including a processor and a memory storing instructions; the instructions, when executed by the processor, enable the plurality of computing devices to provide a location based media access (LOMA) map manager and a LOMA path manager; the LOMA map manager is used to generate and maintain a plurality of LOMA maps, each of the plurality of LOMA maps including a plurality of LOMA areas; a plurality of wireless communication resources for communicating between the plurality of wireless entities are associated with each of the plurality of LOMA areas; the LOMA path manager is used to manage communications between the wireless entities using the wireless communication resources. The technical effect of this embodiment may be to provide semi-static management of communication resources and dynamic autonomous access to communication resources.

Description

Technical Field

[0001] The present invention relates to the field of cellular networks, and in particular to a system, method and device for managing network resources so as to organize network entities to perform resource management and control. Background Art

[0002] The most prominent characteristic of today's cellular network topology is its "cell-centric" nature, organized around base stations, which provide network coverage for a geographic area. Multiple base stations may exist in a given area, and a network of cellular base stations can provide coverage for a wide geographic area. Base stations handle a variety of wireless traffic, including voice and data, each with distinct traffic patterns and requirements.

[0003] However, the traffic requirements of each wireless entity connected to the base station may vary depending on: the entity itself; the type, speed, and amount of traffic to be sent and received; quality of service (QoS) requirements; and any number of other factors.

[0004] Future networks are expected to leverage new technologies such as artificial intelligence (AI) and big data services, and incorporate new devices such as the Internet of Things (IoT). These future transformations will benefit from new and flexible network topologies, such as peer-to-peer (P2P), mobile peer-to-peer (MP2P), and point-to-multipoint (P-MP). This will also increase the types of traffic patterns, such as bursty and session-based traffic. Using the current cell-centric approach, it may be difficult to efficiently manage and control these evolving future networks and entities.

[0005] Therefore, there is a need for an improved method of organizing wireless entities for resource management and control in cellular networks that is not subject to one or more limitations of the prior art.

[0006] This background information is provided to reveal information believed by the applicant to be potentially relevant to the present invention. It is not necessary to admit, nor should it be construed, that any of the foregoing information constitutes prior art against the present invention. Summary of the Invention

[0007] According to one aspect of the present invention, a system for managing network resources is provided. The system includes a plurality of wireless entities, and the plurality of wireless entities include mobile wireless entities and fixed-position wireless entities. The system also includes a plurality of computing devices, each of the plurality of computing devices includes a processor and a memory storing instructions; when the instructions are executed by the processor, the plurality of computing devices provide a location-based media access (LOMA) map manager and a LOMA path manager; the LOMA map manager is used to generate and maintain a plurality of LOMA maps, each of the plurality of LOMA maps includes a plurality of LOMA areas; a plurality of wireless communication resources for communication between the plurality of wireless entities are associated with each of the plurality of LOMA areas; the LOMA path manager is used to manage communication between the wireless entities using the wireless communication resources. The technical effect of this embodiment may be to provide semi-static management of communication resources and dynamic autonomous access to communication resources.

[0008] In some embodiments, the LOMA map manager communicates with the plurality of wireless entities to send and receive management messages to update the plurality of LOMA maps. In some embodiments, the LOMA path manager is used to manage network path routing of traffic data between network nodes and user equipment (UE).

[0009] According to another aspect of the present invention, a method for managing transmission resources of a communication network is provided. The method includes: a plurality of second wireless entities detecting one or more of high-power pilot transmissions and low-power pilot transmissions sent from a plurality of first wireless entities; the method also includes: each of the second wireless entities transmitting a message to a location-based media access (LOMA) map manager, the message including information indicating the following aspects: the signal strength of the detected high-power pilot transmission and the signal strength of the detected low-power pilot transmission. The technical effect of this embodiment may be to provide semi-static management of communication resources and dynamic autonomous access to communication resources based on the location of the wireless entity and the transmission detectable by the wireless entity.

[0010] In some embodiments, each of the plurality of first wireless entities is a network node (NN), and each of the plurality of second wireless entities is a user equipment (UE), and the message transmitted by the specific UE includes: a location where the specific UE detected the high power pilot transmission and a location where the specific UE detected the low power pilot transmission. In some embodiments, the method further comprises: the LOMA map manager allocating downlink (DL) transmission resources to each of a plurality of zones; the allocation being based at least in part on the detected signal strength of the high power pilot transmission, the detected signal strength of the low power pilot transmission and the locations of the plurality of UEs, the allocation of the plurality of DL transmission resources being stored in one or more LOMA maps; wherein the location of the specific UE indicates the one or more zones in which the specific UE detected the high power pilot transmission and the low power pilot transmission. In some embodiments, each of the LOMA maps includes a NN DL map and a UE DL map; wherein the NN DL map associates the DL transmission resources with the one or more zones; the UE DL map associates DL reception resources with the one or more zones; and the specific UE monitors the DL reception resources allocated to the one or more zones associated with the specific UE. In some embodiments, when the specific UE detects one or more data packets in the DL reception resources allocated to the one or more zones associated with the specific UE, the specific UE also decodes the one or more data packets. The technical effect of one or more of these embodiments may be to provide semi-static management of downlink communication resources and uplink communication resources, and dynamic access to the downlink communication resources and the uplink communication resources.

[0011] In some embodiments, when the gateway of the communication network receives one or more data packets sent to the specific UE, the method further includes: for the specific UE, the gateway communicates with the LOMA path manager; the LOMA path manager determines the location information of the specific UE. The method also includes: the gateway receives the current location of the specific UE or the NN associated with the specific UE; the gateway routes the one or more data packets to the NN associated with the specific UE, wherein the route is determined by checking the associated LOMA map. The technical effect of one or more of these embodiments may be to provide semi-static management of downlink communication resources and uplink communication resources, and dynamic access to the downlink communication resources and the uplink communication resources.

[0012] In some embodiments, when the specific UE enters a new zone or a new LOMA zone, the specific UE transmits a location declaration message, wherein the location declaration message indicates a change in zone or a change in LOMA zone. In some embodiments, upon receiving the location declaration message, the method further comprises: the LOMA path manager updates the UE location information. A technical effect of one or more of these embodiments may be to provide semi-static management of downlink communication resources and uplink communication resources, and dynamic access to the downlink communication resources and the uplink communication resources.

[0013] In some embodiments, each of the multiple first wireless entities is a user equipment (UE), and each of the multiple second wireless entities is a network node (NN), and the method further includes: each of the multiple UEs transmits a message to the LOMA map manager, the message including information indicating the following aspects: the location of the specific UE, the high power pilot ID associated with the high power pilot transmission sent by the specific UE, and the low power pilot ID associated with the low power pilot transmission sent by the specific UE. In some embodiments, the method further includes: the LOMA map manager allocating uplink (UL) transmission resources to each of a plurality of zones; the allocation is based at least in part on the detected signal strength of the high-power pilot transmission, the detected signal strength of the low-power pilot transmission and the positions of the plurality of UEs, and the allocation of the plurality of UL transmission resources is stored in a LOMA map; wherein the position of a specific UE indicates the one or more zones associated with the specific UE; and according to the high-power pilot ID and the low-power pilot ID, the detected specific signal strength of the high-power pilot transmission and the detected specific signal strength of the low-power pilot transmission are associated with the specific UE. The technical effect of one or more of these embodiments may be to provide semi-static management of downlink communication resources and uplink communication resources, and dynamic access to the downlink communication resources and the uplink communication resources.

[0014] In some embodiments, the LOMA map includes a NN UL map and a UE UL map; wherein the NN UL map associates UL receive resources with one or more zones; and the UE UL map associates UL transmit resources with the one or more zones. In some embodiments, the NN UL map is used by a specific NN to identify one or more UL resources to be monitored for transmission from one or more of the multiple UEs. In some embodiments, the UE UL map is used by a specific UE to identify one or more UL resources to be used for transmission. A technical effect of one or more of these embodiments may be to provide semi-static management of uplink communication resources and dynamic access to the uplink communication resources.

[0015] According to another aspect of the present invention, an apparatus for managing transmission resources of a communication network is provided, the apparatus comprising a processor and a memory having machine-executable instructions stored thereon. The instructions, when executed by the processor, configure the apparatus to perform the following operations: detecting one or more of high-power pilot transmissions and low-power pilot transmissions sent from a plurality of first wireless entities; and transmitting a message to a location-based media access (LOMA) map manager, the message including information indicating the detected signal strength of the high-power pilot transmission and the detected signal strength of the low-power pilot transmission.

[0016] In some embodiments, the message transmitted by the apparatus includes: the location at which the apparatus detected the high-power pilot transmission and the location at which the apparatus detected the low-power pilot transmission. In some embodiments, a user equipment (UE) DL map associates DL receive resources with one or more zones, and the apparatus monitors the DL receive resources, the DL receive resources being allocated to the one or more zones associated with the apparatus. In some embodiments, when the apparatus enters a new zone or a new LOMA zone, the apparatus transmits a location announcement message indicating a change in zone or a change in LOMA zone.

[0017] The embodiments of the present invention provide methods, systems and devices for implementing a location-based media access (LOMA) solution, as well as a network architecture for implementing the LOMA solution. A LOMA map (LOMA MAP) is created to manage uplink (UL) and downlink (DL) resource units (RU), and methods are provided for network nodes (NN) and user equipment (UE) to determine the DL resources and the UL resources to be used when transmitting and receiving data. LOMA provides flexible areas such as coverage areas and tracking areas to better allocate network resources (such as DL and UL resources). LOMA provides a point-to-point (P2P) protocol to distribute LOMA MAP and network information within the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Further, the features and advantages of the present invention will be readily understood by reading the following detailed description taken in conjunction with the accompanying drawings, in which:

[0019] Figure 1A The LOMA network architecture provided by the embodiment is shown;

[0020] Figure 1B shows an alternative view of the LOMA network architecture provided by an embodiment;

[0021] Figure 2 The electronic equipment used in the embodiment is shown;

[0022] Figure 3 The process of generating LOMA MAP provided by the embodiment is shown;

[0023] Figure 4 The present invention shows a process of establishing a connection between multiple wireless entities provided by an embodiment;

[0024] Figure 5A The process of transmitting data between wireless entities provided by the embodiment is shown;

[0025] Figure 5B The method for DL ​​data transmission using LOMA MAP provided by the embodiment is shown;

[0026] Figure 5C The method for UL data transmission using LOMA MAP provided by an embodiment is shown;

[0027] Figure 6 Shows one-hop transmission and multi-hop transmission provided by the embodiment;

[0028] Figure 7A An example is shown in which a NN according to an embodiment transmits at high power to a UE located at the edge of a coverage area, where the coverage area includes an overlapping area.

[0029] Figure 7B An example is shown in which a NN according to an embodiment transmits at low power to a UE located at the edge of a coverage area, where the coverage area includes a non-overlapping area.

[0030] Figure 8 FIG. 2 shows a Tx MAP provided by an embodiment;

[0031] Figure 9 FIG2 shows a Tx MAP provided by another embodiment;

[0032] Figure 10 FIG. 2 shows an Rx MAP provided by an embodiment;

[0033] Figure 11A An example is shown in which a wireless entity such as a UE transmits UL data to a NN located at the edge of the coverage area at high power, as provided by the embodiment;

[0034] Figure 11B An example is shown in which a wireless entity such as a UE transmits UL data to a NN located at the edge of the coverage area at low power, as provided by the embodiment;

[0035] Figure 12 An example of a wireless entity such as a UE transmitting UL data to a NN located at the center of the coverage area provided by the embodiment is shown;

[0036] Figure 13 shows the Tx MAP provided by the embodiment;

[0037] Figure 14 The Tx MAP provided by the embodiment is shown;

[0038] Figure 15 The Rx MAP provided by the embodiment is shown;

[0039] Figure 16 A point-to-point (P2P) LOMA MAP embodiment provided by the embodiment is shown.

[0040] It should be noted that in all the drawings, the same features are identified by the same reference numerals. DETAILED DESCRIPTION

[0041] Embodiments of the present invention relate to a location-based method for network management, wherein the method utilizes location information available from wireless entities for resource management and control. The location-based multiple access (LOMA) method includes a combined semi-static resource management and dynamic autonomous resource access technology.

[0042] As a general introduction, in this document, any device with wireless transmitter or receiver functionality is referred to as a wireless “entity.” Wireless entities share a common need for wireless network resources to communicate with other entities.

[0043] An example of a wireless entity is user equipment (UE). In this context, UE includes any type of mobile phone, sensor, vehicle, drone, etc. that can be operated or owned by a user or network service subscriber. UE can be mobile or fixed in one location.

[0044] Wireless entities may also include infrastructure network nodes (NNs), such as base stations, sensors, relays, roadside entities, or client or user equipment (e.g., mobile phones, sensors, vehicles, etc.). NNs may be network infrastructure deployed as network nodes for communicating with UEs and are typically fixed in a certain location. Embodiments relate to managing the common functionality of wireless entities in an organized and orderly manner, regardless of how different their individual functions may be.

[0045] In an embodiment, the wireless entity may include both a UE and a NN, both of which participate in wireless communications in the network.

[0046] In an embodiment, a downlink resource unit (DL-RU) may be used to define a pool of one or more DL resources for downlink communication. In an embodiment, an uplink resource unit (UL-RU) may be used to define a pool of one or more UL resources for uplink communication. In an embodiment, a signaling resource unit (S-RU) may be used to define a pool of one or more resource units for control signaling transmission. In an embodiment, a peer to peer resource unit (P2P-RU) may be used to define a pool of one or more resources for P2P communication. In an embodiment, a geographic area may be considered as the smallest cell associated with a zone, and a LOMA zone may be a single geographic area or multiple adjacent geographic areas.

[0047] In an embodiment, both DL and UL communications utilize RUs, which provide parameters for controlling the signaling transmission used by wireless entities for communication. For management purposes, RUs can be organized into resource pools. RUs can also be used for P2P communication between wireless entities.

[0048] A RU is associated with a small geographical area or a small 3D space, which is referred to herein as a LOMA zone. A LOMA zone refers to one or more adjacent zones to which the same RU or the same set of RUs are allocated.

[0049] Embodiments using the LOMA method use location information as the basis for resource management. Location can be absolute or relative and can include two dimensions (e.g., north-south and east-west), three dimensions (e.g., north-south, east-west, and elevation), or other geographic coordinate systems.

[0050] LOMA is a zone-centric design. A geographic area with wireless network coverage is divided into one or more zones of arbitrary size and shape. Zones do not need to be centralized at base stations, access points, or other cellular network infrastructure. Instead, the number, size, and shape of zones can be based on many criteria, including the number of devices, traffic volume, traffic characteristics, size and shape of buildings, etc. Zones can be fixed in location, size, or shape until updated or modified. Zones can also be changed dynamically based on any number of parameters, such as the devices using the zone, traffic volume, burstiness, QoS requirements, etc. A special case of zones is one that is very large, or covers an entire geographic area, and all wireless entities utilize the resources of a single zone.

[0051] In an embodiment, one or more LOMA MAPs are used to manage resources in each LOMA zone. Static MAPs are managed by the network and are used to define and organize network resources. Wireless entities can dynamically access autonomous resources based on the MAP and the wireless entity's location. Each zone can have multiple MAPs, each containing multiple sets of preconfigured Tx RUs and Rx RUs. All entities maintain and access a MAP, which provides instructions on how to access required network resources. It will be readily understood that for the present invention, LOMA MAP and MAP are used interchangeably.

[0052] In an embodiment, LOMA includes techniques and methods for: DL transmissions from a NN to one or more UEs; UL transmissions from a UE to a NN, and P2P communication between two wireless entities (e.g., between two UEs). The techniques described herein may also generally be used to communicate between other combinations of two or more wireless entities. The wireless entities are located within a geographic area, which may be divided into LOMA zones. LOMA may be used for and support a variety of different applications, including but not limited to satellite communications, internet of vehicle (IoV) applications, and other readily understood applications.

[0053] DL transmissions from the NN use the strength of the DL radio signal received or measured by the UE at each UE location. The NN can be used to transmit at different power levels, and the received DL signal strength depends on many factors, including the transmission power of the NN, the receiver of the UE, and the relative and absolute positions of the UE and NN. The available DL radio resources are divided or grouped into resource units, which may be abbreviated as "DL-RUs". The DL-RUs may be allocated to each of these LOMA areas based on an interference avoidance algorithm, which may use AI-based, inter-node interference management techniques. The LOMA MAP describes the DL-RU allocations to the LOMA areas, and wireless entities such as NN and UE may access the LOMA MAP. The NN uses a MAP to perform DL transmissions, which is called the NN-DL-MAP. The UE uses a MAP to perform DL reception, which is called the UE-DL-MAP.

[0054] According to an embodiment, to create the NN-DL-MAP and UE-DL-MAP, the NN can be configured to transmit its pilot transmissions using a number of power levels. The UE is instructed to detect these pilot transmissions and report the corresponding received signaling strength of the pilot transmissions at different power levels. Based on the reports from the UE, the LOMA MAP manager can determine the LOMA area.

[0055] The UL transmission is performed from the UE to the NN using the strength of the DL radio signal at each UE location received or measured by the NN, based on the strength of the UL radio signal transmitted by the UE as received at a specific location NN. The UL signal strength depends on many factors, including the transmission power level of the UE and the location of the UE and the NN. As in the case of DL transmission, the geographical area is divided into LOMA areas. The available UL radio resources are divided into resource units, which are called UL-RUs. The UL-RUs can be allocated to the LOMA areas based on an interference avoidance algorithm, which can use AI-based or inter-node interference management techniques. The MAP describes the UL-RU allocation to the LOMA area, and the MAP is called NN-UL-MAP. The NN uses the NN-UL-MAP to determine which UL-RUs to use for UL reception. The UE uses the UE-UL-MAP to determine which UL-RUs to use for UE transmission.

[0056] According to an embodiment, to create the NN-UL-MAP and UE-UL-MAP, the UE is configured to transmit its UL pilot transmissions (or equivalent UL RUs) using multiple power levels. The NN is configured to detect all possible UL pilot transmissions. The NN reports the received signal strength of all detected UL pilot transmissions to the LOMA MAP manager. The LOMA MAP manager then determines the LOMA region.

[0057] In an embodiment, control signaling transmission may use resource units called S-RUs.

[0058] P2P communication, such as between UEs, uses P2P network resources, which are divided and organized into P2P RUs. The P2P RUs are allocated to zones and described in a MAP called a P2P-MAP.

[0059] Figure 1A The network architecture provided by one embodiment is shown. The architecture includes a LOMA manager 102, which can serve as a network function for managing the LOMA MAP; and a LOMA path manager 104, which can serve as a network function for managing data routing between network nodes (NNs) and client entities. Wireless entities, such as entity 106a and entity 106b, communicate with the LOMA manager 102 and the LOMA path manager 104. The wireless entities can communicate with each other and with a core network user plane function (UPF) 108.

[0060] In an embodiment, the LOMA manager 102 and the LOMA path manager both act as network functions. Network functions are instantiated on the underlying resources of a data center. Functions use the hardware and software resources in the resource pool where they are instantiated. Functions act as independent entities and, from a logical perspective, are indistinguishable from physical nodes that perform the same function. It should also be understood that in a slice network where the data center provides the underlying resources for creating slices, a single network can have slices that support different versions of the network. Therefore, for example, in addition to having a virtualized network that supports 5G services, separate network slices can be created to support 4G networks. Traffic from wireless entities can be routed to a gateway through a network function, which provides access to packet data networks such as the Internet. Wireless access services are typically provided by a RAN. Traditional RAN architectures are designed to consist of discrete components such as eNodeBs, which are connected to the core network via a backhaul network; C-RAN uses functional virtualization to virtualize the access nodes of the network. Much like physical access nodes such as eNodeBs connect to antennas via fronthaul links, in one embodiment, C-RAN access nodes such as gNodeBs also connect to antennas (or remote radio heads (RRHs)) via fronthaul connections, but as functionality instantiated within the network's computing resources. If the gNodeB is divided into a central unit and multiple distributed units, in some embodiments, the virtualized distributed units can be instantiated at or near the antennas or RRHs, while the central unit can be instantiated in a data center to connect and serve multiple geographically dispersed distributed units. UEs can connect to the network via access nodes, which can provide wireless access services via antennas. The access nodes can be instantiated within the computing and storage resources provided by the data center. Other access nodes can connect to the same set of antennas and can also be instantiated within the resources of the data center. It should be understood that the fronthaul connections connecting the virtualized access nodes to the antennas or RRHs can be direct connections or form a fronthaul network. Integrating the CRAN into the core network can eliminate or reduce issues associated with backhaul connections because the access node functionality can be co-located with the core network functionality. A function may be instantiated in more than one data center as part of a function migration process that moves the function within the network, or one of the instantiations may be intentionally redundant. Two functions may be instantiated and configured with only one active at a time, or both functions may be active with only one transmitting data to the UE.

[0061] The virtualization of the network functions allows functions to be located in the network topologically close to the demand for the service provided by the function. Thus, an access node associated with an antenna can be instantiated in data center resources within the data center closest to the antenna. Functions such as the LOMA manager 102 can be instantiated remotely (topologically and / or physically) from the LOMA path manager 104. Thus, the LOMA manager can be instantiated in one data center and the LOMA path manager can be located in another data center that is topologically closer to the UPF 108. In some network implementations, the data centers can be arranged in a hierarchy and different functions can be placed at different levels of the hierarchy.

[0062] Network slicing can be supported, allowing the creation of network slices from underlying network resources. Within a slice, the slice appears as its own unique network, and it can be used as a set of underlying resources for any number of virtual networks. The resources of a slice can also be further sliced ​​to create sub-slices. Network slicing allows the resources of a slice to be dedicated, ensuring that two different slices relying on the same underlying resources do not affect each other. These technologies can also enable the network to support network slicing to create isolated sub-networks with characteristics suitable for the traffic requirements they support. The network can include multiple computing hardware resources to provide processing, memory, and storage resources to functions within the network. Connections can be established using logical links between nodes hosted within a slice in the network. Therefore, the topology of the network, as well as the services and functions provided within the network, can be changed to provide different network connectivity options that connect the computing resources to each other and enable the provision of services to mobile devices.

[0063] The LOMA manager 102 serves as a network function for managing the LOMA MAP. It is responsible for MAP generation and closed-loop adaptation. The LOMA manager 102 interacts with wireless entities using LOMA-related messages. For example, the LOMA manager 102 sends environment learning requests and receives environment report messages from wireless entities. The LOMA manager 102 transmits MAPs to wireless entities and the LOMA path manager 104.

[0064] In an embodiment, the LOMA manager 102 manages the generation of the LOMA MAP with the participation of wireless entities. The LOMA MAP generation process is initialized by a learning MAP that includes multiple zones. For each zone in the MAP, one or more sets of Tx resources are defined for use with Tx Announce messages. Another set of resources is defined for Environment Report messages. In some embodiments, the resource set includes definitions of the resources required by the wireless entity to transmit or receive data. Examples include time, carrier, code, spatial parameters, power, etc.

[0065] The LOMA manager 102 uses the Tx resource information in the learning MAP to send an environment learning request to the area of ​​interest. The environment learning request also distributes the learning MAP to wireless entities in the area of ​​interest. Wireless entities that successfully receive the environment MAP respond to the LOMA manager with an environment report message, which includes wireless environment observation information detected by the wireless entity. The LOMA manager analyzes the received wireless environment observation information and uses this observation information to generate one or more LOMA MAPs.

[0066] For a fixed wireless entity, for example, a network node (eg, a base station, a network relay node) having a fixed wireless or wired connection to the network, its entity ID is included in the MAP entry of the area where it is located.

[0067] The LOMA path manager 104, as a network function, manages traffic data routing between network nodes (NN) and customer entities (e.g., UEs). The LOMA path manager 104 receives a MAP from the LOMA manager 102, receives and maintains location information of wireless entities (e.g., UEs) at the zone level or LOMA zone level, and instructs the DL UPF 108 to forward data to a selected network node based on the known location of the target wireless entity. The LOMA path manager 104 also interacts with core network functions such as the user plane function (UPF) 108 and the control plane function. The LOMA path manager 104 also interacts with wireless entities using location declaration messages, which may be encrypted in some embodiments.

[0068] In order to achieve efficient traffic data communication between entities, wireless entities such as 106a and 106b (such as NN and UE) include LOMA functions inside, and can maintain the location information of the target entity and the location information of the source entity to optimize the use of wireless resources. The information can be obtained by using control messages transmitted between wireless entities, or obtained from the LOMA path manager 104. The LOMA functions within the wireless entities can report their locations at the zone level or LOMA zone level to assist in DL traffic routing. The wireless entity can send a transmission notification (Tx notification) message to the LOMA manager 102. The wireless entity can transmit a location declaration message to the LOMA104 path manager or other wireless entities. The wireless entity can transmit a discovery message to other wireless entities.

[0069] When generating a LOMA MAP, the wireless entity collects and reports wireless environment observation information and transmits the information to the LOMA manager 102. Examples of the collected information include the interference status within the area of ​​interest of the LOMA manager 102. In some embodiments, this operation is completed in two phases: a learning phase and a reporting phase. In the learning phase, a fixed entity (e.g., a network node) or a mobile entity (e.g., a UE) accesses its Tx MAP (transmit map) when moving to a new area and selects a set of Tx resources from the listed resources for the area. In some cases, there may be multiple sets of Tx resources to choose from, and the wireless entity may select a set of resources based on any number of algorithms, such as randomly selecting a set of Tx resources. The wireless entity then uses the Tx resources to transmit a Tx notification message, which includes a zone ID. All wireless entities monitor designated Rx resources to obtain Tx notification messages and record physical layer data related to the received Tx notification messages. The recorded data may include parameters such as received signal strength.

[0070] During the reporting phase, the wireless entity selects one of the Tx resource groups from the Tx resources indicated in its MAP for reporting purposes, and then sends an environment report message. The environment report message includes the zone ID of the zone where the sender is currently located and the recorded physical layer reception and detection results. In some cases, the environment report message can be transmitted directly to the NN, or to another wireless entity, which can then relay the message to the NN. The wireless entity that receives the environment report can decide whether to relay the environment report based on the zone ID. The decision can be made based on a number of different criteria. For example, it can compare the zone ID of the environment report message with its own zone, and only relay the environment report message if it is closer to the target NN than the sender of the environment report message. The relay process can be repeated until the environment report message reaches the network node.

[0071] To avoid network congestion during the learning and reporting phases of this process, wireless entities may selectively choose to participate in or delay participation in the process using random number checking or other methods.

[0072] For the reporting process, the wireless entity may use the appropriate Tx MAP to decide whether to use one-hop transmission or multi-hop transmission to send the report.

[0073] An initial LOMA MAP may also be generated to be used as a learning MAP seed or loaded into the wireless entity until a generated MAP is available. The initial MAP may be generated offline based on historical data or by emulating or simulating the network topology through training equipment.

[0074] In an embodiment, MAP is adjusted as part of a continuous closed loop process.

[0075] In an embodiment, an environment learning request, an environment report message, a MAP transmission message, a location declaration message, a transmission notification, a location declaration, and a discovery message are all referred to as "control messages."

[0076] Figure 1B An alternative view of the LOMA network architecture provided by one embodiment is shown, and in particular, the functions performed by the LOMA MAP manager 102 are shown. Figure 1B A geographical area is shown divided into zones 114, in this case, the zones 114 forming a grid over the geographical area. A plurality of LOMA zones 116 are shown as dashed ovals. Although the LOMA zones 116 can correspond to the zones 114, they do not have to, and in this illustration, the LOMA zones 116 are formed within the geographical area in accordance with the LOMA requirements described herein. For example, a geographical area can be considered as the smallest area unit, and a LOMA zone can be a single geographical area or a plurality of adjacent geographical areas. The LOMA MAP manager 102 is responsible for performing the generation, closed-loop adaptation, maintenance, and management of the MAP; interacting with wireless entities such as the UE 106a and the NN 106b using LOMA messages; and interacting with the LOMA path manager 104 to update the LOMA MAP.

[0077] In an embodiment, the LOMA path manager 104 can be implemented as a network function, responsible for managing the routing of traffic data between the NN and the UE for transmission from the NN to the UE. The LOMA path manager 104 receives and maintains the location information of the UE at the zone 114 level, the LOMA zone 116 level, or both the zone 114 and the LOMA zone 116 level. The LOMA path manager 104 provides control to DL user plane functions (UPF) such as DL data gateways, so that data can be forwarded to the selected NN based on the known target UE location. The LOMA path manager 104 can also interact with core network functions or control plane functions such as UPF. The LOMA path manager 104 also interacts with the UE using messages. For example, the UE transmits a control message called a "location declaration message" to the LOMA path manager 104, and the location declaration message may be encrypted.

[0078] Wireless entities such as UE 106a and NN 106b also include functionality to implement LOMA functionality. Wireless entities provide information that enables the LOMA path manager to obtain interference status within the area where the LOMA manager is being used. For DL ​​traffic routing, the UE reports its location at the level of the zone 114, the level of the LOMA zone 116, or both. Mobile UEs transmit location announcement messages to the LOMA path manager or other entities.

[0079] Figure 2A block diagram of an electronic computing device 200 in a computing and communication environment is shown, which may be wireless entities 106a and 106b for implementing the devices and methods disclosed herein. In some embodiments, the electronic device may be an element of a communication network infrastructure for implementing the LOMA manager 102 or the LOMA path manager 104. Examples of network infrastructure include base stations (e.g., NodeBs, enhanced NodeBs (eNodeBs), next generation NodeBs (sometimes referred to as gNodeBs or gNBs)), home subscriber servers (HSSs), gateways (GWs) such as packet gateways (PGWs) or serving gateways (SGWs), or various other nodes or functions within an evolved packet core (EPC). In other embodiments, the electronic device may be wireless entities 106a and 106b that are connected to the network infrastructure via a wireless interface, such as mobile phones, smartphones, or other such devices that may be classified as user equipment (UEs). It can be an Internet of Things (IoT) device, a wearable device, a vehicle device, a vehicle-mounted device, an on-board device, and other easily understood terminal devices. In some embodiments, the electronic device 200 can be a Machine Type Communication (MTC) device (also known as a machine-to-machine (m2m) device), or other such devices that can be classified as UEs even though they do not provide direct services to users. In some references, electronic devices may also be referred to as "mobile devices," which reflects devices that are connected to a mobile network, regardless of whether the device itself is designed for mobility or is capable of movement. A particular device may use all of the components shown or only a subset of the components, and the degree of integration between devices may vary. In addition, a device may include multiple instances of components, such as multiple processors, memories, transmitters, receivers, and the like.

[0080] The electronic device 200 typically includes a processor 210, such as a central processing unit (CPU), and may also include a dedicated processor, such as a graphics processing unit (GPU) or other such processor, a memory 220, a network interface 250, and a bus for connecting the components of the electronic device 200. The electronic device 200 may also optionally include components such as a mass storage device 230, a video adapter 240, and an I / O interface 260 (shown in dashed lines).

[0081] The memory 220 may include any type of non-transitory system memory readable by the processor 210, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In one embodiment, the memory 220 may include more than one type of memory, such as ROM used at boot time and DRAM used to store programs and data during program execution. The bus may be one or more of any of several types of bus architectures, including a memory bus or a memory controller bus, a peripheral bus, or a video bus.

[0082] The electronic device 200 may further include one or more network interfaces 250, and the network interface 250 may include at least one of a wired network interface and a wireless network interface. Figure 2 As shown, the network interface 250 may include a wired network interface to connect to the network 202, and may also include a wireless access network interface 290 for connecting to other devices via a wireless link. When the electronic device 200 is a network infrastructure, the wireless access network interface 290 may be omitted for nodes or functions that act as core network (CN) elements rather than nodes or functions located at the wireless edge (e.g., eNB). When the electronic device 200 is an infrastructure located at the wireless edge of the network, it may include both wired and wireless network interfaces. When the electronic device 200 is a wirelessly connected device (e.g., user equipment), the wireless access network interface 290 may be present, and other wireless interfaces such as a Wi-Fi network interface may be used as a supplement. The network interfaces 250 and 290 allow the electronic device 200 to communicate with remote entities (e.g., those connected to the wired network and wireless network 202 and 204).

[0083] The mass storage 230 may include any type of non-transient storage device for storing data, programs, and other information, and making these data, programs, and other information accessible via a bus. The mass storage 230 may include, for example, one or more of a solid-state drive, a hard disk drive, a magnetic disk drive, or an optical disk drive. In some embodiments, the mass storage 230 may be remote from the electronic device 200 and may be accessed via a network interface such as an interface 250. In the illustrated embodiment, the mass storage 230 is different from the memory 220 comprising it, and may typically perform storage tasks that are compatible with higher latency, but typically provides less volatility or no volatility. In some embodiments, the mass storage 230 may be integrated with the heterogeneous memory 220.

[0084] The optional video adapter 240 and the I / O interface 260 (shown in dotted lines) provide interfaces to couple the electronic device 200 to external input and output devices. Examples of input and output devices include a display 270 coupled to the video adapter 240 and an I / O device 280 coupled to the I / O interface 260, such as a touch screen. Other devices can be coupled to the electronic device 200, and more or fewer interfaces can be used. For example, a serial interface such as a universal serial bus (USB) (not shown) can be used to provide an interface for external devices. It will be appreciated by those skilled in the art that in embodiments where the electronic device 200 is part of a data center, the I / O interface 260 and the video adapter 240 can be virtualized and provided via the network interface 250.

[0085] In some embodiments, the electronic device 200 may be a standalone device, while in other embodiments, the electronic device 200 may reside within a data center. As will be understood by those skilled in the art, a data center is a collection of computing resources (typically in the form of servers) that can be used as collective computing and storage resources. Within a data center, multiple servers can be connected together to provide a computing resource pool, within which virtualized entities can be instantiated. Data centers can be interconnected to form a network that includes pools of computing and storage resources connected to each other via connection resources. The connection resources can take the form of physical connections such as Ethernet or optical communication links, and in some cases, they can also include wireless communication channels. If two different data centers are connected via multiple different communication channels, the links can be grouped together using any of a variety of techniques, such as establishing a link aggregation group (LAG). It should be understood that any or all of the computing, storage, and connectivity resources (along with other resources within the network) can be divided between different subnetworks, in some cases in the form of resource slicing. If resources are sliced ​​across multiple interconnected data centers or other sets of nodes, different network slices can be created.

[0086] As used herein, a “network” or “communication network” may serve a variety of devices, including but not necessarily limited to wireless devices. Such a network may include a wireless access portion, a backhaul portion, and a core network portion. It will be apparent in this document that the network may also include various virtualized components. Although networks that comply with the Long Term Evolution (LTE) network standard and networks that comply with the Evolved Packet Core (EPC) requirements can be implemented using network slicing, their basic design does not utilize network slicing and virtualization functions, nor does it provide control over the use of network slicing and virtualization functions. Discussions on the standardization of future mobile network designs and architectures, including the so-called Fifth Generation (5G) networks, have begun. New network architectures and functional elements are currently being discussed to utilize technologies such as network slicing, network function virtualization, and software-defined networks, topologies, and protocols. Using these different technologies, a flexible network can be established so that the core network used by 5G networks can be built using a variety of network technologies, thereby achieving reconfigurability to meet a variety of different needs.

[0087] Figure 3A LOMA MAP generation process 300 performed by the LOMA manager 102, according to one embodiment, is illustrated. The process begins with the LOMA manager 102 receiving a learning MAP, which provides a starting point for creating the MAP. The learning MAP includes a list of zones and multiple sets of Tx resources (RUs) available for transmission to wireless entities within the zones. In step 304, the LOMA manager 102 selects wireless entities to transmit Tx advertisements to the wireless entities located in the zone of interest using the Tx resources listed in the learning MAP. In step 306, wireless entities such as 106a and 106b monitor the Rx resources listed in the learning MAP for their zones. In step 308, wireless entities that successfully receive the Tx advertisements reply to the originating wireless entity using an Environment Report message, reporting their observations of the received Tx advertisements. The LOMA manager uses the received observations to create or update any required MAPs. Wireless entities continue to monitor the Rx resources indicated for their zones in their locally accessible MAPs to receive new or updated MAPs.

[0088] Embodiments include a method for creating a DL MAP (e.g., NN-DL-MAP) using a multi-level power transmission scheme, which may be a two-level scheme. When high-power pilot transmission is used, the NN transmits at higher power on the pilot channel, or uses other equivalent resource units (RU). The UE monitors these pilot channels or RUs and reports the received signal strength and the current location of the UE (area ID or LOMA area) to the LOMA MAP manager. When low-power pilot transmission is used, the NN transmits at lower power on the pilot channel, or uses other equivalent resource units (RU). The UE monitors these pilots or RUs and reports the received signal strength and the current location of the UE (area ID or LOMA area) to the LOMA MAP manager. Based on the received signal strength and the received location information, the LOMA MAP manager allocates resource units (RU) to the area according to a specified algorithm. The LOMA MAP manager may determine the LOMA area and the DL RU allocation to the LOMA area. Various alternatives can be used, for example, NNs can transmit their pilot signals in sequence using multiple levels of power, or use S-RU to transmit Tx announcement messages. The UE can then report the received signal strength to the LOMA MAP manager, including a list of NN IDs or pilot IDs, power level IDs, received signal strength, etc.

[0089] Embodiments include methods for creating MAPs, such as NN-DL-MAP, UE-DL-MAP, NN-UL-MAP, UE-UL-MAP, and P2P-MAP. For the DL MAP, the NN performs multiple pilot transmissions to one or more UEs using two or more transmission power levels. The pilot transmission may include information such as a transmission NN ID, a pilot ID, or a transmission power level ID. In an embodiment, the following two levels may be used: a high power level and a low power level. The high power pilot transmission may use a pilot channel or an equivalent RU. The UE is configured to monitor a known pilot channel or an equivalent RU and report the received signal strength and the current location of the UE (e.g., a zone ID) to the LOMA MAP manager 102. The low power pilot may use the same or different pilot channel or an equivalent RU. The UE is configured to monitor a known pilot channel or an equivalent RU and report the received signal strength and the current location of the UE (e.g., a zone ID) to the LOMA MAP manager 102. Based on the information received from the UE, the LOMA MAP manager 102 may allocate RUs to zones according to a specific algorithm. In an embodiment, the NNs may send their pilot transmissions sequentially using multiple levels of power, or using S-RUs to send what is known as a " Tx notification message " transmission control message. The UE reports the received signal strength to the LOMA MAP manager 102, and the content of the report includes a list of NN IDs or pilot IDs, a power level ID and the received signal strength.

[0090] Figure 4 A process 400 for establishing a connection between multiple wireless entities (e.g., between wireless entity 106a and wireless entity 106b) is shown. The process 400 begins at step 402, where a sending wireless entity transmits a discovery message using the Tx resources indicated by its MAP. At step 404, the wireless entities monitor the Rx resources indicated by the MAP for the LOMA region in which they are located. At step 406, the wireless entities that have received the discovery message respond to the sending wireless entity with a location announcement message.

[0091] Figure 5A A process 500 for transmitting data between wireless entities is shown. In step 502, a transmitting wireless entity accesses its MAP to determine the Tx resources for transmission. In step 504, the transmitting wireless entity transmits a data packet. In step 506, the receiving wireless entity receives the data packet using the Rx resources specified in the MAP for the zone in which the transmitting entity resides.

[0092] The embodiment supports multiple MAP types, which can be roughly divided into MAPs for fixed wireless entities such as cellular base stations and MAPs for mobile wireless entities such as UEs. Separate MAPs may also exist for DL ​​and UL communications and P2P communications between wireless entities.

[0093] In an embodiment, a NN such as a cellular base station with a fixed location (which may correspond to a cellular network "cell") may use MAPs such as NN-DL-MAP and NN-UL-MAP. The MAP used by the base station includes an entry for each zone accessible to the base station. The entries in the MAP for each zone include a set of Tx RUs and a set of Rx RUs that the base station uses when transmitting to or from the zone. For transmission, the base station determines the Tx resource unit group based on the LOMA zone where the target entity is located. The base station randomly selects one or more Tx resource units for transmission. For reception, the base station determines the Rx resource unit group for monitoring based on the LOMA zone where the sending entity is located. The base station then monitors all resource units in the group. Other fixed-location wireless entities may also use the NN-UL-MAP and the NN-DL-MAP.

[0094] Mobile devices and other wireless entities, such as UEs, use the LOMA MAP, which can be referred to as the UE-DL-MAP and UE-UL-MAP. The MAP used by the wireless entity includes an entry for each zone accessible to the wireless entity. For transmission, a set of Tx resource units is indicated for each zone. For reception, a set of Rx resource units is indicated for each zone. For transmission, the wireless entity determines the set of Tx resource units based on the zone in which the wireless entity is currently located. The entity randomly selects one or more Tx resource units for transmission. For reception, the wireless entity determines the set of Rx resource units to monitor based on the zone in which the entity is currently located. The wireless entity monitors all resource units in the set.

[0095] In other embodiments, a first type and a second type of MAP are used to indicate transmissions. The first type of MAP is used to facilitate transmissions. A Tx resource map may be used, wherein multiple sets of Tx resources are defined for each defined zone. The wireless entity may store the Tx MAP for uplink (UL) traffic. In some embodiments, the mobile wireless entity references the zone in which it is located.

[0096] The second type of MAP is an Rx MAP (Receive Map) used to facilitate reception. The Rx Resource MAP can be used to indicate to wireless entities which Rx resources must be monitored for each zone in order to receive data. For downlink (DL) transmissions, each network node uses the Rx Resource MAP when the location of the target wireless entity is known. In some embodiments, mobile wireless entities reference the zone in which they are currently located.

[0097] The third and fourth types of MAPs are used to indicate reception. The third type of MAP is a Tx resource-based MAP, where multiple sets of Tx resources are indicated for each zone. This type of MAP is retained by the NN and is used when the location of the transmitting entity is known and available to the NN for uplink data. In some embodiments, a fixed-location wireless entity references the zone of the target entity that will receive traffic.

[0098] The fourth type of MAP is an Rx resource-based MAP, in which, for each zone, multiple groups of resources that need to be monitored are indicated. This type of MAP can be reserved by the client entity for downlink (DL) data transmission. This fourth type of MAP, also known as a BMS MAP, can also be used for broadcast or multicast transmission and reception. In this case, the BMS MAP includes multiple zones where the broadcast or multicast transmission is targeted, and the MAP specifies that all zones use the same set of Tx resources.

[0099] In some embodiments, multiple MAPs of the above type may be provided based on other criteria such as transmission power, etc. For example, there may be different MAPs for different slices, services, or groups.

[0100] In some embodiments, cellular or wireless network coverage areas and tracking areas (TAs) are defined based on geographic regions. For each NN node, the LOMA system indicates a list of zone IDs that define the default coverage area for that NN. If the NN needs to perform broadcast services, it needs to verify that it can provide adequate communication coverage for these zones.

[0101] A tracking area (TA) can be defined in the form of a list of zone IDs. If a paging service is indicated, the network needs to ensure that all zones within the TA can receive the message.

[0102] Figure 5BA process for DL ​​data transmission using MAP provided by an embodiment is shown. In step 508, the UE uses the UE-DL-MAP for the LOMA area in which it is currently located to determine the DL RUs to monitor and decode the data packets detected using those DL RUs. Subsequently, the mobile UE enters the new area. In step 510, the UE updates its LOMA area location by sending a location declaration message to the LOMA path manager 104. The location declaration message includes information such as the ID of the UE and the ID of the new LOMA area. In step 512, in response to receiving the location declaration message, the LOMA path manager 104 updates its location table by updating the entry that matches the ID of the UE in the message, so that the ID of the UE is associated with the LOMA area ID. At a certain point in time, the UP GW 108 uses the router function to receive data packets sent to the UE from a wider network. The UP GW 108 may not have an entry for the UE in its local routing table, so in step 514, the UP GW 108 (router) requests the location information of the UE from the LOMA path manager 104. In response to the location request message received from the UP GW 108, the LOMA path manager 104 accesses the relevant DL MAP to determine the NN that is most suitable for forwarding the data packet to the target UE. In step 516, the LOMA path manager sends an ACK in the form of a location response message, which includes the ID of the UE and the ID of the selected NN. In step 518, the UP GW 108 sends a DL data packet to the NN indicated in the location response message. The NN receives the DL data packet from the UP GW 108 and accesses its NN-DL-MAP to determine the DL-RU to use for communication with the UE. In step 520, the NN transmits the data packet to the UE using the DL-RU assigned to the LOMA zone where the target UE is currently located.

[0103] Figure 5CA method for UL data transmission using MAP provided by an embodiment is shown. In step 522, based on the NN-UL-MAP of the NN, the NN continuously monitors the UL-RU assigned to the LOMA area to detect the transmitted signal. In step 524, the UE determines that it will transmit a data packet. Based on the LOMA area currently occupied by the UE, the UE checks its UE-UL-MAP and selects the UL-RU assigned to the LOMA area. In step 526, the UE uses the UL-RU for the area to transmit the data packet. The UE can also retransmit the data packet according to specific rules (for example, no response is received from the NN within a certain time). In step 528, the NN detects and decodes the data packet transmitted by the UE using the UL-RU that the NN is monitoring. In step 530, after the NN successfully receives and decodes the data packet, the NN sends a response message to the UE.

[0104] The following will be combined Figure 6 An embodiment is described to illustrate data communication using LOMA over a one-hop path and a multi-hop path. Wireless entities with a fixed location or wireless entities without a fixed location, such as mobile UEs, can use one-hop communication and multi-hop communication. Communication is performed between a sending entity 602 and a receiving entity 604. Any message or traffic data between 602 and 604 can be performed using a one-hop method 600 or a multi-hop method 601. In one embodiment, the location of the target entity is known to the sender. Based on QoS and interference conditions, the sender can decide to use a one-hop path 610 to meet low latency requirements or a multi-hop path through intermediate nodes 606 and 608 to meet interference limitation requirements. Other requirements can be used to determine whether to use a one-hop path 610 or multi-hop paths 612, 614 and 618.

[0105] For a one-hop path 610, transmitting entity 602 selects resource units using an appropriate LOMA MAP, such as a high-power MAP, which allows for long-range communication. Note that if low-power transmission is sufficient to transmit data from UE 602 to UE 604, either a high-power MAP or a low-power MAP can be used. Transmitting entity 602 transmits data along path 610 to target entity 604 without relaying the data through intermediate nodes 606 or 608. Transmitter 602 first queries the appropriate Tx MAP for high-power transmission, randomly selects one of the multiple groups of resource units, and transmits a message to target entity 604. During this transmission, it can use the ID of the current zone of transmitter 602 and the sender's code (associated with the sender's ID) to process the transmitted signal. Target entity 604 receives the signal and can detect the received signal using information about the intended sender. Target entity 604 checks the target entity's ID and, if necessary, further processes the payload data. Target entity 604 can send an ACK message back to transmitting entity 602.

[0106] For the multi-hop path through 612, 614, and 618, the transmitting entity 602 uses the resources indicated in the Tx MAP with the low power level to determine the Tx resources to use. The transmitting entity 602 may add the ID of the target zone, the ID of the intermediate zone, or both, to the message and transmit the message via the first hop 612. At an intermediate entity such as 606 or 608, if the message is received and includes the ID of the intermediate entity's current zone, the entity forwards the message. This process repeats until the message reaches the target zone. The operation at the target entity 604 is the same as in the single-hop process.

[0107] In both the one-hop 600 and multi-hop 601 cases, certain fields in the message, such as zone ID, entity ID, etc., can be encrypted or signed using configured encryption keys, which can be organized by slices, groups or other principles.

[0108] The LOMA MAP generated by the LOMA manager 102 is distributed to the wireless entities using a MAP transfer procedure and a MAP transfer message. With the one-hop method 600, a NN that receives a MAP transfer message directly from the LOMA manager 102 can directly transfer the received MAP to other wireless entities using a broadcast or multicast service (BMS) MAP.

[0109] If the MAP is received using the multi-hop method 601, the NN that receives the MAP transfer message can use the target area ID in the MAP transfer message to transmit the MAP to nearby entities. Wireless entities receiving the MAP can determine whether they need to relay the MAP transfer message based on the relationship between their current location and the location of the target area. If a wireless entity receives the MAP transfer message and one of the target area IDs matches the area ID of its current location, the wireless entity does not need to relay the MAP transfer message.

[0110] The location information of the transmitting wireless entity may be transmitted to other wireless entities using a location declaration message. In some embodiments, mobile wireless entities and wireless entities without a fixed location perform this process. In some embodiments, the LOMA MAP includes a set of dedicated Tx resources for transmitting location declaration messages.

[0111] In an embodiment, for location declaration, the mobile wireless entity can use different methods, including an "autonomous" method and an "on-demand" method. Using the autonomous method, when entering a new area, the mobile wireless entity selects a LOMA MAP (or a pre-configured MAP for location declaration purposes can be used) and transmits a location declaration message to the LOMA path manager 104 through the NN. The transmission can use a specific low power Tx MAP, starting with a low transmission power. If an ACK is not received, the sender can increase the transmission power of the location declaration message using a higher power Tx MAP. The sending wireless entity can progressively select a higher power Tx MAP until an ACK is received from the NN. If an ACK is not received using the Tx resources of the highest available power level Tx MAP, the process ends. The location declaration message includes an R-ID and the area ID of the wireless entity sender, wherein the R-ID identifies the device within the area or service or slice.

[0112] Using the on-demand method, a wireless entity first receives a discovery message from another wireless entity. The wireless entity selects a LOMA MAP to use based on the zone ID indicated in the discovery message and transmits a location announcement message containing the zone ID and R-ID of its current zone. When using either the autonomous or on-demand process, certain fields in the message, such as the zone ID and target entity ID, can be encrypted or signed using a configured key. Keys can be specified by slice, group, or other organizational principle.

[0113] For fixed entities, the position declaration process only needs to be performed once.

[0114] As part of the location declaration process, after receiving a location declaration message from a wireless entity, the NN may forward the location declaration message to the LOMA path manager 104, retain the location information for the mobile entity, or both. After receiving a location declaration message forwarded by the NN from a wireless entity, the LOMA path manager updates the location record of the wireless entity. The location record may include information such as the entity ID and zone ID.

[0115] An embodiment includes the following process: a transmitting wireless entity discovers a target wireless entity or a group of target wireless entities so that data traffic can be communicated between the wireless entities. Each zone listed in the LOMA MAP may include a set of dedicated Tx resources for transmitting discovery messages. The wireless entity starts transmitting a discovery message at the lowest power (using the LOMA MAP with the lowest transmission power level) and waits to receive the resulting location declaration message. If the location declaration message is not received, the wireless entity increases the transmission power (using the next LOMA MAP with higher transmission power) and waits again to receive the location declaration message. This process of increasing transmission power is repeated until the expected location declaration message (including the zone ID and R-ID) is received, a stop / NACK is received, or the highest available power level is reached (using the LOMA MAP with the highest transmission power). The discovery message includes the following information: the ID and / or network slice ID of the target entity, and the ID of the transmitting entity. In the case of multiple target wireless entities, the transmitting entity will receive multiple location declaration messages, corresponding to the number of target wireless entities in the area of ​​interest. In some embodiments, this discovery process can be used to discover all nearby targets belonging to a specific slice or other group of wireless entities. After the location announcement message of the target entity is available, the transmission power between the entities is determined and recorded based on the transmission power of the discovery message for subsequent data transmission, so that the sending wireless entity successfully receives the location announcement message in response. Note that other power control mechanisms may also be used. At the end of the target discovery process, traffic data communication between the wireless entities may begin.

[0116] In some embodiments of the target discovery process, some fields in the message, such as zone ID, target entity ID, slice ID, sender ID, etc., can be encrypted or signed using a configured encryption key, and the configured encryption key can be defined by slice or by group.

[0117] After the described power control procedure between the entities, traffic data communication may begin.

[0118] In an embodiment, a network node (NN) may be a fixed entity located in an area that does not change or rarely changes. For example, when the NN is a cellular base station. The NN typically communicates with multiple wireless entities, many of which may be mobile, such as cell phones. The MAP used by the NN includes entries based on the location of the target wireless entity with which the NN wants to communicate. In contrast, the MAP used by a non-fixed wireless entity may be based on the location of the wireless entity.

[0119] In the DL MAP for the NN, for example from the NN to the UE, for each zone, the transmission resources available to the NN are indicated. Based on the location information of the target entity obtained from the LOMA path manager 104 or directly from the mobile entity, the NN node selects Tx resources to transmit to the target entity.

[0120] In the UL MAP for a NN, for example, from a UE to the NN, the receive resources available to the NN are indicated for each zone. Based on the location information of the transmitting entity, the NN node monitors and attempts to detect signals using the Rx resources specified for the zone in which the transmitting entity is located. Furthermore, for UL reception, if the NN is unaware of the UE's incoming UL transmissions, the NN needs to monitor all UL-RUs within its NN-UL-MAP.

[0121] In an embodiment, client entities and mobile entities can use a MAP to indicate transmission resources and reception resources for each zone. For transmission, the entity checks the MAP entry for its current zone to determine the transmission resources to use based on its current location, and then transmits. For reception, the wireless entity checks the MAP entry for its current zone and determines the Rx resources it must monitor to receive the transmission.

[0122] Figure 7A An embodiment is shown in which NNs transmit to UEs at the edge of a coverage area. The coverage area has an irregular deployment of NNs and is limited to areas where the received SNR is above the high power transmission threshold of the NNs. Within a zone, the locations of the NNs are fixed. For example, NN1 702 is located in zone 2 710; NN2 704 is located in zone 4 714; and NN3 706 is located in zone 12 718. In this embodiment, the Tx MAP 800 used by the NNs (see Figure 8) includes the Rx resources of the target wireless entity in each zone. In some cases, some zones are covered by multiple NNs, for example, zone 3 712 is covered by NN1 702 and NN2 704, and these zones allocate different sets of Tx resources to the NNs. For example, in overlapping areas, the Tx resources and Rx resources can be orthogonal to each other to avoid interference. Each of the NNs stores a set of LOMA MAPs. When a NN wants to transmit to a wireless entity, it first determines the zone where the target entity is located. The NN accesses the available Tx resources in the zone where the target wireless entity is located and selects the Tx resources for transmission. The Tx resources can be randomly selected from multiple available Tx resources. The target wireless entity knows which zone it is located in and queries its Rx MAP to know which Rx resources to use to detect the DL message sent to it. Communication between two NNs can use this same method.

[0123] Figure 7A An embodiment is shown in which NNs transmit at sufficiently high power levels to establish overlapping LOMA zones. NNs can use RUs R1 through R5 (referenced at 720, 722, 724, 726, and 728, respectively) to communicate with UEs in their coverage areas. RUs can be used by multiple NNs as long as any mutual interference is within tolerable levels. Figure 7B An embodiment is shown where the NNs transmit at sufficiently low power levels to establish non-overlapping LOMA areas. In this case, RU group R0 can be reused by all NNs with non-overlapping LOMA areas to serve UEs within their coverage areas.

[0124] Figure 8 Shown for Figure 7A 800 for NN1 702 in Zone 3. NN1 has MAP entries for Z1, Z2, Z3, Z9, and Z10. Zones 1, 2, and 10 are not overlapping zones because only NN1 covers them. Zone 3 overlaps with NN2 704, and Zone 9 overlaps with NN 708. To transmit to a wireless entity located in Zone 3, NN1 will use Tx resource R1 indicated in MAP 800.

[0125] Figure 9 Shown for Figure 7A Figure 9 shows the Tx MAP 900 for NN2 704 in the figure. NN2 has MAP entries for Z3, Z4, and Z5. Zones 3, 4, and 5 are overlapping zones. Zone 3 overlaps with NN1 702, Zone 4 overlaps with NN3 706, and Zone 5 overlaps with another NN. To transmit to a wireless entity located in Zone 4, NN2 will use Tx resource R5 indicated in the MAP 900. Note that if a region defines zones above Z3, Z4, and Z5, these zones will not be overlapping zones.

[0126] Figure 10 An Rx MAP 1000 is shown for a target wireless entity within the coverage area. The target wireless entity knows the zone in which it is located and can monitor the resources indicated in the Rx MAP 1000 so that the zone receives transmissions from the NN. For example, see Figure 7A If the target wireless entity is located in zone 3 712, it monitors Rx resources R1 720 and R2 722. For example, the UE-DL-MAP may define substantially all UEs that may be transmission targets. The UE-DL-MAP may include a basic area, which may cover multiple LOMA areas.

[0127] Figure 7A An embodiment is also shown in which the NN transmits to a UE located at the center of the coverage area. The coverage area has an irregular deployment of NNs. Within a zone, the location of the NNs is fixed. For example, NN1 702 is located in zone 2 710; NN2 704 is located in zone 4 714; and NN3 706 is located in zone 12 718. In this embodiment, for any zone where there is no coverage overlap between NNs, the same multiple sets of transmission resources are allocated to each NN. Each of the NNs stores a set of LOMA MAPs. When a NN wants to transmit to a wireless entity, the NN first determines the zone where the target entity is located. The NN accesses the available Tx resources in the zone where the target wireless entity is located and selects a Tx resource for transmission. The Tx resource to be used can be randomly selected from multiple available Tx resources. The target wireless entity knows which zone it is located in and queries its Rx MAP to know which Rx resources to use to detect the DL message sent to it. Communication between two NNs can use this same method.

[0128] Figure 11A An embodiment is shown in which a wireless entity such as a UE transmits UL data to a NN located at the edge of the coverage area. The coverage area has an irregular deployment of NNs. In a certain zone, the location of the target NN is fixed. For example, NN1 702 is located in zone 2 1112, NN2 704 is located in zone 3 1114, and NN3 706 is located in zone 7 1118. In this embodiment, the wireless entity accesses a MAP containing records that indicate Tx resources for use by edge NNs by zone. Based on the zone in which the target NN is located, the wireless entity randomly selects a set of Tx resources from the available Tx resources in the zone and transmits data. Based on its Rx MAP, the target NN monitors Rx resources for possible UL transmissions from the wireless entity. This same method can be used for communication between two NNs.

[0129] Figure 11A This also illustrates an embodiment in which a UE transmits at a higher power level. NNs 1 through NN 4 are distributed across different geographic regions. UEs in Region 2 1112, Region 3 1114, and Region 4 1116 transmit at a higher power level. The allocated UL-RUs overlap, and RUs 1 through 6 (referenced at 720, 722, 732, 716, 728, and 730, respectively) are allocated to the edges of the coverage area. Figure 11B The situation is shown when the UE uses lower power transmission and the UL RUs are allocated in non-overlapping zones. Assume that there are UEs in each of zone 1 1110 and zone 7 1118. R0 is a set of UL-RUs that can be reused by UEs that are closer to the NN where the LOMA zone does not overlap.

[0130] Figure 7A An embodiment is shown in which the NNs transmit at sufficiently high power levels to establish overlapping LOMA zones. The NNs can use RUs R1 to R5 to communicate with UEs in their coverage areas. RUs can be used by multiple NNs as long as any mutual interference is within tolerable levels. Figure 7B An embodiment is shown where the NNs transmit at sufficiently low power levels to establish non-overlapping LOMA areas. In this case, RU group R0 can be reused by all NNs with non-overlapping LOMA areas to serve UEs within their coverage areas.

[0131] Figure 12 An embodiment is shown in which a wireless entity such as a UE transmits UL data to a NN located at the center of the coverage area. The coverage area has an irregular deployment of NNs. In a certain zone, the location of the target NN is fixed. For example, NN1 702 is located in zone 1 1110, NN2 704 is located in zone 3 1114, and NN3 706 is located in zone 7 1118. In this embodiment, the UL MAP of the wireless entity located at the center of the zone uses a low-power MAP. The wireless entity accesses a MAP containing a record that indicates Tx resources for use by NN by zone. Based on the zone in which the target NN is located, the wireless entity randomly selects a set of Tx resources from the available Tx resources in the zone and transmits data. Based on its Rx MAP, the target NN monitors Rx resources for possible UL transmissions from the wireless entity. This same method can be used for communication between two NNs.

[0132] Figure 13 A Tx MAP 1300 is shown for a Tx MAP from Figure 12UL data for the wireless entity shown. NN1 has MAP entries for regions 1 to 8. To transmit to a NN located in region 3, the wireless entity may utilize either Tx resources R5 or R6 as defined in the UE-UL-MAP, etc. In some embodiments, the wireless entity randomly selects resources between R5 and R6 for UL transmission.

[0133] Figure 14 An Rx MAP 1400 is shown, which is used to Figure 12 NN1 702 in zone 1 receives UL transmissions from wireless entities. NN1 has MAP entries for Z1, Z2, and Z5, as defined in the NN-DL-MAP for NN1, etc. NN1 must monitor R0 for transmissions from wireless entities in zone 1 and R2 for transmissions from wireless entities in zones 2 or 5.

[0134] Figure 15 An Rx MAP 1500 is shown, which is used to Figure 12 NN2 704 in zone 2 receives UL transmissions from wireless entities. NN2 has MAP entries for Z2, Z3, and Z4. NN2 must monitor R2 for transmissions from wireless entities in zone 2, R5 for transmissions from wireless entities in zone 3, and R4 for transmissions from wireless entities in zone 4.

[0135] Figure 16 An embodiment of a point-to-point MAP (P2P-MAP) is shown, which can be used by fixed wireless entities and mobile wireless entities. The P2P-MAP is populated according to the target discovery process described above. The P2P-MAP 1600 includes multiple groups of Tx RUs and Rx RUs for the area of ​​interest or LOMA area. Multiple Tx RUs and Rx RUs can be specified for each area ID. Each resource group includes parameters such as power, beamforming, time, carrier, and resource blocks.

[0136] In one embodiment, any number of methods may be used to discover a target wireless entity, such as a UE, including: a transmitting wireless entity discovering a target wireless entity and the target wireless entity autonomously or on-demand announcing its location in response to a request. For example, the discovery and location announcing may be used to establish a pier-to-pier (P2P) connection.

[0137] When a transmitting UE discovers a target wireless entity, the transmitting UE transmits a discovery message including the target R-ID and the transmitting UE ID. The transmitting UE starts with the lowest transmission power (using the S-RU with the lowest transmission power level) and then increases the transmission power using the S-RU with the next higher transmission power until one of the following events occurs: the expected location announcement message is received from the target UE, a stop message is received, or the transmitting UE reaches the highest power level (using the S-RU with the highest power level).

[0138] The discovery message may include the following information, such as R-ID (which may be the UE ID of the target entity), slice ID (used to discover all nearby targets belonging to the slice), the ID of the sending entity, or any combination of the above.

[0139] Once the location of the target entity is known, the transmission power between these entities is negotiated using a power control procedure for P2P communication for subsequent data transmission.

[0140] In an embodiment, messages between wireless entities may be encrypted or signed using a configured encryption key, which may be set per slice, group, etc. In some cases, only selected fields are encrypted, such as zone ID, target entity ID, slice ID, sender ID, etc.

[0141] For fixed target entities, it may be sufficient to perform the discovery process only once.

[0142] In an embodiment, a mobile wireless entity such as a UE may declare its location through a location declaration procedure. Two examples of location declaration procedures are "autonomous location updating" and "on-demand location updating".

[0143] For autonomous location updating, when a mobile wireless entity enters a new area, the wireless entity transmits a location declaration message starting with a low transmission power using an S-RU with low power, and then increases its transmission power using an S-RU with the next higher transmission power until one of the following events occurs: an ACK message is received, a stop message is received, or the wireless entity reaches the highest transmission power level (using the S-RU with the highest transmission power). The location declaration message may include the R-ID of the wireless entity and the area ID of the area that the wireless entity has entered. In this case, the R-ID can be any type of ID that can be used to identify a UE in a region, an ID that identifies the slice to which the wireless entity belongs, the service of the wireless entity, or any combination of the above.

[0144] For on-demand location updating, a wireless entity, such as a UE, receives a request, such as a discovery message, requesting the wireless entity to perform location declaration. In response to the request, the wireless entity transmits a location declaration message, which may include either a zone ID or an R-ID, as described for the declaration message in the case of autonomous location updating.

[0145] During the above process, some fields in the exchanged messages may be encrypted or signed using encryption keys configured on a per-slice, per-group, or other basis. Examples of fields that may be encrypted include the zone ID and the target entity ID. For wireless entities with a fixed location, these location declaration procedures may be performed once.

[0146] refer to Figure 6 In an embodiment, one-hop or multi-hop P2P data communication can be performed between the transmitting wireless entity 602 and the target wireless entity 604. If necessary, a discovery process such as a target UE discovery process or a location declaration process can be performed to determine the location of the target wireless entity 604. At this time, the location of the target wireless entity 604 is known or can be determined by the transmitting wireless entity 602, and the required transmission power level is also known or can be determined. Based on QoS requirements and interference conditions, the transmitting wireless entity 602 determines whether to use one-hop transmission (for example, low latency requirements) or multi-hop transmission. One-hop transmission reduces latency, while multi-hop transmission can be used to avoid or alleviate interference limitations in an area.

[0147] In the case where the transmitting wireless entity 602 uses a one-hop transmission, the transmitting wireless entity 102 accesses the P2P-MAP and selects a resource unit that matches the required appropriate power level. The transmitting wireless entity 602 can access the P2P-MAP using its current zone ID and the transmitter code associated with its own ID, and randomly selects a transmission RU based on the P2P-MAP entry. The data can then be transmitted directly to the target wireless entity 604 without being relayed through an intermediate wireless entity such as wireless entity 606 or wireless entity 608. The target wireless entity 604 uses the information of the intended transmitting wireless entity to detect and receive the signal. It can verify the target entity ID of the transmission and further process any received payload if necessary. Optionally, an ACK message can be returned to the transmitting wireless entity 602.

[0148] If the sending wireless entity 602 uses multi-hop transmission, it can choose to use a P2P RU with lower power. In the transmitted message, the sending wireless entity 602 can indicate the target zone ID and the IDs of any intermediate zones along path 610. When intermediate wireless entities such as wireless entity 606 or wireless entity 608 receive the multi-hop message, they check the zone ID in the message to determine whether they are in one of the listed intermediate zones. If they are, they forward the message along path 610. The wireless entities in the intermediate zones repeat this process until the message reaches the target zone. When the target wireless entity 604 receives the data transmission message, it is processed as in the single-hop transmission scenario described above.

[0149] For single-hop and multi-hop P2P transmission, some fields in the transmitted message can be encrypted or signed using a configured encryption key, which can be configured on a per-slice, per-group, or other basis. Examples of fields that can be encrypted include zone ID, entity ID, etc.

[0150] In an embodiment, the sending wireless entity accesses the MAP entry for the zone where the target wireless entity is located. If multiple Tx resources are listed for the zone, the Tx resource can be randomly selected from the listed Tx resources. Data is then transmitted to the target entity using the selected Tx resource. The transmission may include information that helps identify the sending entity, such as an entity ID, a zone ID, etc. The target entity may also use the MAP to monitor the Rx resources for its zone in order to receive the message from the sending entity. Both single-hop transmission and multi-hop transmission can be performed using a P2P map, in which case if an intermediate entity receives the message and it is closer to the target entity than the sending entity, it can relay the message to the target entity.

[0151] Embodiments of the present invention provide a method and apparatus for managing network resources in a wireless network. According to embodiments of the present invention, a method for managing network resources is provided, comprising: a transmitting wireless entity accessing a location-based MAP to select a Tx resource for transmitting to a target wireless entity. The transmitting wireless entity transmits a message to the target wireless entity using the Tx resource.

[0152] In another embodiment, the Tx resource is selected from a plurality of Tx resources for the zone. In another embodiment, the Tx resource is selected based on the zone where the target wireless entity is located. In another embodiment, the Tx resource is selected based on the zone where the sending wireless entity is located.

[0153] In other embodiments, the MAP corresponds to a power level. In further embodiments, the Tx resource is randomly selected from the plurality of Tx resources. In further embodiments, the MAP also includes an Rx resource for receiving a transmission from the target wireless entity, wherein the sending wireless entity and the target wireless entity form a P2P network.

[0154] According to another embodiment of the present invention, a method for managing network resources is provided, the method comprising: a target wireless entity accessing a location-based MAP to select an Rx resource for receiving a transmission from a sending wireless entity, the target wireless entity monitoring the Rx resource to receive a message from the sending wireless entity.

[0155] In a further embodiment, the Rx resource is one of a plurality of Rx resources for the zone. In a further embodiment, the Rx resource is based on the zone in which the target wireless entity is located. In a further embodiment, the Rx resource is based on the zone in which the transmitting wireless entity is located. In a further embodiment, the Rx resource is randomly selected from the plurality of Rx resources.

[0156] In other embodiments, the method further includes: the target wireless entity determining that the final destination of the message is another wireless entity and transmitting the message to the final destination of the message. In further embodiments, the target wireless entity accesses a location-based Tx MAP to determine Tx resources for the final destination of the message.

[0157] According to another embodiment of the present invention, a method for managing network resources is provided, the method comprising: a LOMA manager sending an environment learning request to a plurality of wireless entities. Each of the plurality of wireless entities is located in one of a plurality of zones within a coverage area. In response to the environment learning request, the LOMA manager receives an environment report message from the plurality of wireless entities. Each of the environment report messages includes wireless environment observation information of the plurality of wireless entities. The LOMA manager generates a MAP using the environment report message. The MAP includes a communication resource record for each of the plurality of zones. The LOMA manager distributes the MAP to each of the plurality of wireless entities.

[0158] In a further embodiment, each of the records includes Tx resources used when transmitting to a wireless entity in the area indicated by the record. In other embodiments, each of the records includes a transmit power level. In other embodiments, the MAP includes a Tx MAP and an Rx MAP. In other embodiments, the MAP is customized for use by one of the plurality of wireless entities based on characteristics of the one of the plurality of wireless entities. In a further embodiment, each of the records includes Rx resources monitored by the wireless entity when receiving communications in the area indicated by the record.

[0159] The term "about" as used herein should be understood to include variations relative to the nominal value, for example, variations of + / - 10% relative to the nominal value. It should be understood that given values ​​provided herein always include such variations, whether specifically mentioned or not.

[0160] Unless defined otherwise, all technical and / or scientific terms used herein have the same meanings as commonly understood by one of ordinary skill in the art.

[0161] Through the description of the above embodiments, the present invention can be implemented only by hardware, or by software and necessary general hardware platforms. Based on such understanding, the technical solution of the present invention can be embodied in the form of a software product. The software product can be stored in a non-volatile or non-transient storage medium, which can be a compact disk read-only memory (CD-ROM), a USB flash drive, or a mobile hard disk. The software product includes many instructions that enable a computer device (a personal computer, a server, or a network device) to execute the method provided in the embodiment of the present invention. For example, such execution can correspond to a simulation of a logical operation as described herein. According to an exemplary embodiment, the software product may additionally or alternatively include a plurality of instructions that enable a computer device to execute the operation of configuring or programming a digital logic device.

[0162] Although the present invention has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations of the present invention may be made without departing from the present invention. Therefore, the specification and drawings are to be regarded only as illustrative of the present invention as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations or equivalents that fall within the scope of the present invention.

Claims

1. A method for managing transmission resources of a communication network, characterized in that The method comprises: The plurality of second wireless entities detect one or more of high power pilot transmissions and low power pilot transmissions sent from the plurality of first wireless entities; Each of the second wireless entities transmits a message to a location based media access (LOMA) map manager, the message including information indicative of a detected signal strength of the high power pilot transmission and a detected signal strength of the low power pilot transmission.

2. The method according to claim 1, characterized in that Each of the multiple first wireless entities is a network node (NN), and each of the multiple second wireless entities is a user equipment (UE), and the message transmitted by the specific UE includes: the location where the specific UE detects the high-power pilot transmission and the location where the specific UE detects the low-power pilot transmission.

3. The method according to claim 2, characterized in that The method further comprises: The LOMA map manager allocates downlink (DL) transmission resources to each of a plurality of zones; the allocation is based at least in part on the detected signal strength of the high-power pilot transmission, the detected signal strength of the low-power pilot transmission and the locations of a plurality of UEs, and the allocation of a plurality of DL transmission resources is stored in one or more LOMA maps; wherein the location of the particular UE indicates the one or more zones in which the particular UE detects the high-power pilot transmission and the low-power pilot transmission.

4. The method according to claim 3, characterized in that Each of the LOMA maps includes a NN DL map and a UE DL map; wherein the NN DL map associates the DL transmission resources with the one or more zones; the UE DL map associates DL reception resources with the one or more zones; and the specific UE monitors the DL reception resources allocated to the one or more zones associated with the specific UE.

5. The method according to claim 4, characterized in that When the specific UE detects one or more data packets in the DL reception resources allocated to the one or more zones associated with the specific UE, the specific UE further decodes the one or more data packets.

6. The method according to claim 4 or 5, characterized in that When the gateway of the communication network receives one or more data packets sent to the specific UE, the method further includes: For the specific UE, the gateway communicates with a LOMA path manager; The LOMA path manager determines the location information of the specific UE; The gateway receives a current location of the specific UE or a NN associated with the specific UE; The gateway routes the one or more data packets to the NN associated with the particular UE, wherein the routing is determined by examining an associated LOMA map.

7. The method according to any one of claims 3 to 6, characterized in that When the specific UE enters a new area or a new LOMA area, the specific UE transmits a location declaration message, where the location declaration message indicates a change of area or a change of LOMA area.

8. The method according to claim 7, characterized in that Upon receiving the location declaration message, the method further includes: the LOMA path manager updating the UE location information.

9. The method according to claim 1, characterized in that Each of the plurality of first wireless entities is a user equipment (UE), and each of the plurality of second wireless entities is a network node (NN), and the method further includes: Each of the multiple UEs transmits a message to the LOMA map manager, the message including information indicating the following aspects: the location of the specific UE, the high power pilot ID associated with the high power pilot transmission sent by the specific UE, and the low power pilot ID associated with the low power pilot transmission sent by the specific UE.

10. The method according to claim 9, characterized in that The method further comprises: The LOMA map manager allocates uplink (UL) transmission resources to each of a plurality of zones; the allocation is at least partially based on the detected signal strength of the high-power pilot transmission, the detected signal strength of the low-power pilot transmission and the positions of the plurality of UEs, and the allocation of a plurality of UL transmission resources is stored in a LOMA map; wherein the position of a specific UE indicates the one or more zones associated with the specific UE; according to the high-power pilot ID and the low-power pilot ID, the detected specific signal strength of the high-power pilot transmission and the detected specific signal strength of the low-power pilot transmission are associated with the specific UE.

11. The method according to claim 10, characterized in that The LOMA map includes a NN UL map and a UE UL map; wherein the NN UL map associates UL reception resources with one or more zones; and the UE UL map associates UL transmission resources with the one or more zones.

12. The method according to claim 11, characterized in that The NN UL map is used by a particular NN to identify one or more UL resources to monitor for transmissions from one or more of the plurality of UEs.

13. The method according to claim 11 or 12, characterized in that The UE UL map is used by a particular UE to identify one or more UL resources to use for transmission.

14. A device for managing transmission resources of a communication network, characterized in that The apparatus comprises a processor and a memory having machine-executable instructions stored thereon, the instructions, when executed by the processor, configuring the apparatus to: detecting one or more of high power pilot transmissions and low power pilot transmissions sent from a plurality of first wireless entities; A message is sent to a location based media access (LOMA) map manager, the message including information indicative of a detected signal strength of the high power pilot transmission and a detected signal strength of the low power pilot transmission.

15. The device according to claim 14, characterized in that The message transmitted by the apparatus includes a location where the apparatus detected the high power pilot transmission and a location where the apparatus detected the low power pilot transmission.

16. The device according to claim 15, characterized in that A user equipment (UE) DL map associates DL reception resources with one or more zones, and the apparatus monitors the DL reception resources, which are allocated to the one or more zones associated with the apparatus.

17. The device according to claim 15 or 16, characterized in that When the device enters a new zone or a new LOMA zone, the device transmits a location declaration message indicating the change of zone or the change of LOMA zone.

18. A system for managing network resources, characterized in that: The system comprises: a plurality of wireless entities, the plurality of wireless entities comprising mobile wireless entities and fixed location wireless entities; Multiple computing devices, each of the multiple computing devices includes a processor and a memory storing instructions; when the instructions are executed by the processor, the multiple computing devices provide a location-based media access (LOMA) map manager and a LOMA path manager; the LOMA map manager is used to generate and maintain multiple LOMA maps, each of the multiple LOMA maps includes multiple LOMA areas; multiple wireless communication resources for communication between the multiple wireless entities are associated with each of the multiple LOMA areas; the LOMA path manager is used to manage communication between the wireless entities using the wireless communication resources.

19. The system according to claim 18, wherein: The LOMA map manager communicates with the plurality of wireless entities to send and receive management messages to update the plurality of LOMA maps.

20. The system according to claim 18 or 19, characterized in that The LOMA path manager is used to manage network path routing of traffic data between network nodes and user equipment (UE).

21. A system, characterized in that The system comprises one or more devices according to any one of claims 14-17.

22. The system according to claim 18, wherein: The system also includes a LOMA map manager and / or a LOMA route manager.

23. A non-transitory storage medium storing instructions, characterized in that: The instructions are used to execute the method according to any one of claims 1-13.

Images