WO2022269324A1 - Réseau de périphérie de spectre - Google Patents

Réseau de périphérie de spectre Download PDF

Info

Publication number
WO2022269324A1
WO2022269324A1 PCT/IB2021/055716 IB2021055716W WO2022269324A1 WO 2022269324 A1 WO2022269324 A1 WO 2022269324A1 IB 2021055716 W IB2021055716 W IB 2021055716W WO 2022269324 A1 WO2022269324 A1 WO 2022269324A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
spectrum
nodes
spectrum edge
operator
Prior art date
Application number
PCT/IB2021/055716
Other languages
English (en)
Inventor
Ali Khayrallah
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/IB2021/055716 priority Critical patent/WO2022269324A1/fr
Publication of WO2022269324A1 publication Critical patent/WO2022269324A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • Radio access networks are networks of radio access points, e.g., base stations, that communicate wirelessly with end user terminals and provide connectivity between the end user terminals and a core network, which may interconnect multiple networks and provide further connectivity to public data networks such as the internet.
  • access networks have predominately used exclusive licensed spectrum or unlicensed spectrum. In the former case, which applies to most mobile telephone networks, an operator is given exclusive use of a particular frequency band or bands in a given area.
  • Networks using unlicensed spectrum allow spectrum to be shared by unlicensed users, typically according to sharing rules that ensure fairness.
  • LAA licensed-assisted access
  • Increasing demand for spectrum has led to the development of new hybrid spectrum modes, beyond the previous two, where licenses may be shorter term and the use of spectrum not exclusive but shared. This may be applicable to, for example, the Citizens Broadband Radio Service (CBRS) in the United States, which the U.S.
  • CBRS citizens Broadband Radio Service
  • Federal Communications Commission has established as a band to be shared by licensed “priority access” users, lightly regulated “general authorized access” users, and “incumbent” users, which include fixed satellite service users.
  • This approach to opening up the use of the 3.5 GHz to 3.7 GHz band in the United States allows a new band to be put in use for radio access networks, while protecting the incumbent users.
  • These new sharing modes speed up access to new spectrum for radio access, for instance, without having to wait for legacy incumbents to be completely vacated first.
  • “Dimensioning” a network refers to the process of selecting and deploying suitable quantities of network resources (e.g., base stations, backhaul capacity, processing power) to serve the anticipated number of users and traffic.
  • network resources e.g., base stations, backhaul capacity, processing power
  • an operator would dimension radio access network equipment to the allocated spectrum, since the number of users that can be served and the maximum traffic that can be supported is directly related to the available radio spectrum. Everything from base station front ends all the way to transport equipment can then be scaled accordingly.
  • this dimensioning exercise becomes difficult, because the amount of spectrum that is actually available for the radio access network is variable. This difficulty in properly dimensioning a radio access network under these circumstances is especially difficult if the expected lifetime of the equipment is longer than the spectrum license.
  • Network equipment is less flexible the closer it is to the air. That is, antennas and radio front ends are designed for a certain frequency band and bandwidth, and interfaces between the front end and baseband are designed for a certain bandwidth.
  • Baseband processing which is one step further away from the air interface, typically requires specialized hardware accelerators for computationally intensive functions like decoding.
  • Baseband is also designed to handle a certain load, which relates to bandwidth, but it can be scaled somewhat, or be organized as a pool of resources serving multiple cells, which also increases scaling flexibility.
  • MVNO mobile virtual network operator
  • MNO classical mobile network operator
  • the MNO may even handle billing to customers, under the MVNO brand.
  • the MNO also handles its own direct customers, which typically make up the majority of its users.
  • MVNO multiple-operator core network
  • MOCN multiple-operator core network
  • This arrangement works well when the participating operators also have their own radio access networks in other geographical areas, where they act as a mainstream MNO, which justifies their having separate core networks (serving both radio access networks).
  • the MOCN sharing arrangement is typically done for cost reasons, often to provide service in a sparsely populated rural area where traffic is limited and revenue potential is low.
  • the participating operators may form a joint venture to obtain spectrum licenses and own the common network assets.
  • a spectrum edge network SEN
  • the SEN is separate from an operator network and is capable of serving packets to users belonging to multiple operators.
  • the SEN can be dimensioned to match the entirety of a particular spectrum band or a part of it, and is not susceptible to spectrum licenses changing over time.
  • the SEN can trace usage to different operators and charge the operators accordingly.
  • the SEN can be transparent to traffic and allow obfuscation of information including the terminal identity, the messages content and their source and destination outside the SEN.
  • the SEN can accommodate licensed or unlicensed operation, as well as a mix.
  • an SEN comprises a plurality of radio access nodes, each being configured to communicate wirelessly with one or more access terminals using a frequency band.
  • the SEN also includes one or more network nodes configured to schedule uplink and downlink communications to access terminals, where these one or more network nodes are configured to route data between the access terminals and a plurality of operator networks external to the spectrum edge network, via respective operator interface nodes. Also described below are operator networks configured to operate with an SEN.
  • An example of such an operator communications network comprises one or more network nodes configured to provide data services to access terminals, via at least a spectrum edge network comprising a plurality of radio access nodes configured to communicate wirelessly with access terminals using a first frequency band.
  • the operator communications network further comprises an operator interface configured to connect the one or more network nodes to the spectrum edge network, for routing data to and from access terminals.
  • the SEN approach is well suited for the case with simultaneous connectivity to operator networks and the SEN, where an operator can rely on some dedicated spectrum, but also has access to spectrum shared with other operators, which it uses via a SEN.
  • the SEN as described herein enables operators to accommodate new resource sharing modes by relying on the SEN for radio connectivity to their users, in an efficient, secure manner.
  • Figure 1 illustrates an LTE radio access network (RAN) and an Evolved Packet Core (EPC).
  • Figure 2 illustrates a spectrum edge network (SEN) and an operator core network.
  • Figure 3 illustrates an example scenario where operators 1 and 2 are connected to an SEN via operator interface node (OIN) 1 and 2, respectively.
  • Figure 4 shows an example of scheduler queues and resource allocations for operators 1 and 2.
  • Figure 5 illustrates an obfuscation and clearing function behind the OIN on the operator side.
  • Figure 6 shows a message with source and destination addresses and the encryption by the operator, on the downlink, of the message and source address.
  • Figure 7 shows a message with source and destination addresses and the encryption by the terminal, on the uplink, of the message and destination address.
  • Figure 8 illustrates an example of simultaneous connectivity to operator networks and SEN, using carrier aggregation (CA).
  • CA carrier aggregation
  • Radio Node As used herein, a “radio node” can be either a “radio access node” or a “wireless device.”
  • Radio Access Node As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN radio access network
  • a radio access node examples include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB/en-gNB) in a 3GPP fifth-generation (5G) NR network or an enhanced or evolved Node B (eNB/ng- eNB) in a 3GPP LTE network), base station distributed components (e.g., CU and DU), base station control- and/or user-plane components (e.g., CU-CP, CU-UP), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point, a remote radio unit (RRU or RRH), and a relay node.
  • a base station e.g., a New Radio (NR) base station (gNB/en-gNB) in a 3GPP fifth-generation (5G)
  • RAN node may apply to any of, for example: gNB, eNB, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, gNB- CU-UP, eNB-CU, eNB-CU-CP, eNB-CU-UP, IAB-node, IAB-donor DU, IAB-donor- CU, IAB-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O-eNB.
  • Core Network Node As used herein, a “core network node” is any type of node in a core network.
  • a core network node examples include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a Packet Data Network Gateway (P-GW), an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a Service Capability Exposure Function (SCEF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW Packet Data Network Gateway
  • AMF access and mobility management function
  • AMF access and mobility management function
  • AMF access and mobility management function
  • AMF session management function
  • UPF user plane function
  • SCEF Service Capability Exposure Function
  • Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a wireless device include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (IoT) devices, vehicle-mounted wireless terminal devices, etc.
  • VoIP voice over IP
  • PDAs personal digital assistants
  • MTC mobile-type communication
  • IoT Internet-of-Things
  • Network Node is any node that is either part of the radio access network (e.g., a radio access node or equivalent name discussed above) or of the core network (e.g., a core network node discussed above) of a cellular communications network.
  • a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.
  • Figure 1 illustrates elements of a conventional wireless telecommunications network, including a radio access network (RAN), which in this case is an LTE RAN 100, formally known as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), coupled to a core network 130, in this case an Evolved Packet Core (EPC).
  • RAN radio access network
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • EPC Evolved Packet Core
  • E-UTRAN 100 includes one or more evolved Node B’s (eNB), such as eNBs 105, 110, and 115, and one or more user equipment (UE), such as UE 120.
  • eNB evolved Node B
  • UE user equipment
  • “user equipment” or “UE” means any wireless communication device (e.g., smartphone or computing device) that is capable of communicating with 3GPP-standard- compliant network equipment, including E-UTRAN as well as UTRAN and/or GERAN, as the third-generation (“3G”) and second-generation (“2G”) 3GPP RANs are commonly known.
  • 3G third-generation
  • 2G second-generation
  • E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in uplink and downlink, as well as security of the communications with the UE.
  • These functions reside in the eNBs, such as eNBs 105, 110, and 115.
  • Each of the eNBs can serve a geographic coverage area including one more cells, including cells 106, 111, and 116 served by eNBs 105, 110, and 115, respectively.
  • the eNBs in the E-UTRAN communicate with each other via the X2 interface, as shown in Figure 1.
  • the eNBs also are responsible for the E-UTRAN interface to the EPC 130, specifically the S1 interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW), shown collectively as MME/S-GWs 134 and 138 in Figure 1.
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the MME/S-GW handles both the overall control of the UE and data flow between the UE and the rest of the EPC.
  • the MME processes the signaling (e.g., control plane) protocols between the UE and the EPC, which are known as the Non-Access Stratum (NAS) protocols.
  • NAS Non-Access Stratum
  • the S-GW handles all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and serves as the local mobility anchor for the data bearers when the UE moves between eNBs, such as eNBs 105, 110, and 115.
  • EPC 130 can also include a Home Subscriber Server (HSS) 131, which manages user- and subscriber-related information.
  • HSS 131 can also provide support functions in mobility management, call and session setup, user authentication and access authorization.
  • the functions of HSS 131 can be related to the functions of legacy Home Location Register (HLR) and Authentication Centre (AuC) functions or operations.
  • HSS 131 can also communicate with MMEs 134 and 138 via respective S6a interfaces.
  • a spectrum edge network is a new type of radio access network that facilitates the shared use of spectrum, particularly spectrum that allows a mix of licensed, “lightly” licensed, and regulated but unlicensed usage.
  • the SEN may be a geographically expansive network, like a mainstream wide area network, or it may be geographically local network, such as an in building, campus, factory etc. In either case, it may be assumed that the SEN is assigned the spectrum licenses needed to operate in the band of interest. The licenses may belong to other entities, and by assigning them to the SEN, the issues of re-dimensioning or over-dimensioning the network are avoided. The nature of the commercial agreements to assign the spectrum licenses are out of scope of this document.
  • FIG 2 illustrates an example of an SEN 200, in this case coupled to a single operator’s core network 150 through an operator interface node (OIN) 210.
  • the SEN 200 comprises multiple eNBs, such that the air interface between the eNBs 105, 110, 115 and the UE 120 is an LTE interface.
  • an NR air interface or some other air interface, might be used instead.
  • the operator’s core network is an Evolved Packet Core (EPC) 130. Again, this might be different, in other embodiments or implementations.
  • EPC Evolved Packet Core
  • each of the access points in the SEN which in this case are eNBs, are individually connected to the OIN 210, using the LTE S1 interface, or some variation or mimic thereof.
  • the OIN 210 is connected to MMEs/S-GWs 134, 138 through an S1 interface, or some variation or mimic thereof.
  • Other suitable interfaces including those developed specifically for coupling an SEN to an operator network, might be used instead.
  • the illustrated example has the multiple access points (eNBs) connected to an OIN 210 that is external to the SEN. In some embodiments, this OIN 210 may form part of the SEN 200.
  • the multiple access points in the SEN 200 might connect to another node, internal to the SEN 200, with that other node providing a single point of connectivity for an OIN. Variations of these schemes are possible, as well.
  • the nature of the spectrum regulation in the band used by the SEN establishes how the SEN behaves. To illustrate, if the band allows exclusive operation, then the SEN will behave accordingly. An example of exclusive operation is 5G NR. If the band is regulated to be shared with other entities, say other uncoordinated networks or radar, then, again, the SEN has to behave accordingly. An example of shared spectrum operation is 5G NR-U. Later in this document, the case involving parallel use by operators of exclusive networks and SEN is discussed.
  • a terminal can connect to a base station in the SEN using an initial access procedure. This may be similar to the random access procedures defined for NR and/or LTE networks, for example. At the end of this access procedure, the SEN knows a terminal ID, and can inform the operators of its presence at a certain location.
  • the terminal can remain camped on its serving base station, or move to another base station, e.g., using mobility (handover) procedures like those defined for NR and/or LTE networks.
  • the serving base station can inform the terminal, via a downlink control channel, about a scheduled downlink message, or the terminal can request to send a message via random access on the uplink, after which it is informed via signaling on the downlink control channel about its scheduled uplink transmission.
  • any or all the usual transmission modes defined for conventional radio access networks may be available in the SEN, including, for example, a range of modulation and coding formats, support for MIMO and/or beamforming, retransmission (ARQ) schemes, etc.
  • a scheduler function may be included in the SEN.
  • the base stations within the SEN may be directly connected, or indirectly via intermediate nodes, for the purposes of synchronization, load balancing, coordination, multi-site connectivity, handover etc.
  • the scheduler function may reside in one or more nodes separate from the base stations, or the scheduler functionality might be distributed among the base stations themselves.
  • the scheduler functionality may be distributed among the eNBs 105, 110, 115, with each eNB being responsible for scheduling uplink and downlink transmissions in its respective cell(s).
  • a given scheduler function or a given node in which a scheduler function is implemented may handle the scheduling for multiple access nodes, or for only a single access node, or even for only one of several carriers provided by a single access node, in various embodiments.
  • the scheduler may be considered the boundary of the SEN.
  • a virtual connection is established via the OIN, with the SEN operating in the middle.
  • the operator can send messages tagged with a terminal ID to the SEN through the OIN.
  • the message may also be tagged with a quality-of-service (QoS) requirement, or assume a generic profile otherwise.
  • QoS quality-of-service
  • the operator may also provide the SEN with a QoS profile for uplink messages from the terminal.
  • the SEN receives messages from the operator, over the OIN, it takes over and handles the rest.
  • uplink messages from terminal are handled by the SEN and delivered to the operator via the OIN.
  • the core network of the operator can be placed behind the OIN.
  • Some other functions not directly addressing connectivity but relating to provisioning and managing base stations may be delegated to the SEN, with exchange of information via the OIN or some other interface, but they are outside the scope of this discussion.
  • the SEN will deal with multiple operators, and will have an OIN dedicated to each one. This affects both downlink and uplink operations.
  • the scheduler may treat the messages without accounting for their originating operator.
  • the scheduler acts like its counterpart in a mainstream radio access network: It may consider the arrival time of the message, its QoS requirement, the channel quality of the terminal, the recent share of access allocated to the terminal, etc.
  • the SEN can account for the capacity share of each operator since it knows their terminals. However, it cannot directly control the share of each operator.
  • the SEN scheduler may operate multiple queues, e.g., one per operator. Each queue has a nominal share of the available resource elements, and orders messages belonging to one operator the same way as a mainstream scheduler. Access to resource elements may be static, in the sense that each queue gets its share of resources.
  • FIG. 4 illustrates an example multi-queue setup, where a scheduler function/node 410 includes separate queues for operators 1 and 2, accessing resources for operators 1 and 2, respectively. In this example, a larger allocation is shown for operator 2.
  • an SEN might have one or several scheduling functions, implemented in one or many scheduling nodes (not necessarily in a one-to-one mapping), where each scheduling function services one access node, several access nodes, or even only some resources associated with a given access node.
  • proxy ID for a terminal
  • the proxy ID differing from a “true” or “actual” identifier for the terminal, such as a telephone number, subscriber identifier, or the like.
  • the usual ID information may include the phone number, which makes it possible to identify the corresponding operator. If this information is considered too intrusive, then a proxy ID may be used instead to obfuscate the true identity as much as possible. This requires a prior agreement between the terminal and its operator.
  • the proxy ID may be fixed and stored by the terminal, or it may be a seed for an algorithm that changes the proxy ID over time.
  • the terminal provides its proxy ID to the SEN when it attaches to it, then the SEN checks on its corresponding operator, which will recognize the proxy ID.
  • Another important aspect of transparency is how message contents are handled.
  • the message content can be encrypted with prior agreement between the terminal and the operator about encryption keys.
  • the SEN need not de-crypt the messages for any reason, and just conveys them between the terminal and the OIN.
  • the message can be scrambled, and the choice of scrambling mask is made by prior agreement between the terminal and the operator. Scrambling may be considered a special case or an alternative to encryption, and is mentioned explicitly here for clarity.
  • Another aspect of transparency operation is about what the terminal is connecting to via the operator network.
  • the terminal may connect to a server or to another terminal.
  • the SEN need not know the eventual destination, and treats the OIN as a proxy for it. For example, if a message is sent to the terminal from a source in the operator network or connected via the operator network, then its source address may be obfuscated to the SEN by the operator. The SEN receives the message through the OIN and sends it to the terminal, which can de-crypt the source address and the message content. Alternatively, the operator may scramble the source address, and the receiving terminal will need to descramble it.
  • the terminal wants to send a message to a destination (again in the operator network or via the operator network)
  • the address of the destination may be obfuscated to the SEN by encrypting it in the terminal.
  • the SEN sends the message to the OIN of the operator, and the operator can take over, decrypt the destination address and route the message accordingly.
  • the terminal may scramble the destination address, and the operator will need to descramble it.
  • Figure 6 illustrates obfuscation on the downlink, where the source address and the message content are encrypted, and the destination address (representing the terminal) is in the clear.
  • Figure 7 illustrates obfuscation on the uplink, where the source address (representing the terminal) is in the clear and the message content and the destination address are encrypted.
  • the sending terminal operates on the uplink as in Figure 7, obfuscating the destination address of the receiving terminal. Its corresponding operator will uncover the destination address. For now we assume that the operator leaves the message content encrypted. If the receiving terminal is in the same operator network, then the operator will proceed as in Figure 6 for the downlink.
  • the proxy ID of the receiving terminal is attached to the message, the source address is encrypted, and the message content is already encrypted.
  • the SEN is oblivious to the fact that the terminals are communicating with one another. If the receiving terminal belongs to a different operator connected to the same SEN, then the sending and receiving operators can communicate between them in the usual way. The receiving operator handles the downlink and communicates the message through its own OIN to the SEN. If the sending or receiving operator (which may be the same) needs to decrypt the message content for legal reasons (e.g., legal intercept) or for operational reasons (e.g., transcoding speech), then it may do so in the same mainstream ways they would if the terminal was connected directly to that operator. This will be completely transparent to the SEN.
  • legal reasons e.g., legal intercept
  • operational reasons e.g., transcoding speech
  • both terminals are connected to the SEN, even when the message content is not decrypted, the encrypted version will appear twice in the SEN, on the uplink then on the downlink. Thus, it is conceivable that the SEN will be able to tell that the message is between these terminals. If this is undesirable, then it can be alleviated for instance by the operator encrypting the message content a second time during the downlink process.
  • the receiving terminal will need to decrypt a first time to remove the encryption by the operator, then a second time to remove the encryption by the sending terminal. Alternatively, the operator may scramble the message, and the receiving terminal will need to descramble it before decrypting it to remove the encryption by the sending terminal.
  • CA there is a general notion of a carrier acting as a primary cell or secondary cell from the viewpoint of the terminal.
  • the primary cell carries the high-level control channel (HLCC) for that terminal, which enables the network to allocate resources to serve data to and from the terminal on the primary and secondary cells, and direct the terminal to act accordingly.
  • the low-level control channel (LLCC) on the primary cell supports the data for the terminal on that carrier.
  • the LLCC on the secondary cell supports the data for the terminal on that carrier.
  • Operator 1 has one anchor carrier A1 in its dedicated spectrum and one carrier B in the SEN spectrum.
  • Operator 2 has one anchor carrier A2 in dedicated spectrum, and the same carrier B.
  • a terminal for operator 1 connects to A1 as its primary cell, and to B as its secondary cell.
  • a terminal for operator 2 connects to A2 as its primary cell and B as its secondary cell.
  • the role of the SEN becomes focused on handling carrier B, acting as the secondary cell to terminals from both operators. From each operator’s viewpoint, it gets access to the resources of carrier B via the OIN, as before.
  • Each carrier directs its terminals to use carrier B via its HLCC. That is, operators 1 communicates to its terminals via the HLCC on A1, and similarly for operator 2 on A2. From the terminal’s viewpoint, it connects to its own operator’s network and communicates over its HLCC. It also connects to carrier B when directed to do so.
  • a terminal for operator 1 connects to the HLCC on A1, and connects to carrier B as its secondary cell when directed to do so.
  • a terminal for operator 2 This example extends readily to more than two carriers in the shared SEN, or more than two networks connecting to the SEN in CA mode.
  • a spectrum edge network may comprise, in some embodiments, a plurality of radio access nodes, each being configured to communicate wirelessly with one or more access terminals using a frequency band.
  • the SEN may also comprise one or more network nodes configured to schedule uplink and downlink communications to access terminals, where the one or more network nodes are configured to route data between the access terminals and a plurality of operator networks external to the spectrum edge network, via respective operator interface nodes.
  • the one or more network nodes may be separate from the radio access nodes.
  • the one or more network nodes are one or more of the radio access nodes.
  • the one or more network nodes (the scheduling nodes) are configured to allocate a respective share of spectrum edge network resources to each of the external operator networks. The respective shares may differ for at least two external operator networks, for example.
  • the resources available for use by the spectrum edge network vary, outside of the control of the spectrum edge network.
  • the respective shares allocated to the external operator networks are shares of available resources, as opposed to shares of a fixed capacity.
  • the one or more network nodes communicate with each of one or more access terminals using a respective proxy identifier, such that a true identifier for each of the one or more access terminals is unknown to the spectrum edge network.
  • the nodes of the spectrum edge network are configured to route encrypted data between access terminals and one or more of the plurality of operator networks, without any decryption of the data in the spectrum edge network.
  • the nodes of the spectrum edge network are configured to route data associated with encrypted external server addresses between access terminals and one or more of the plurality of operator networks, without any decryption of the external server addresses in the spectrum edge network.
  • a communications network managed by an operator and connected to an SEN may comprise one or more network nodes configured to provide data services to access terminals, via at least a spectrum edge network comprising a plurality of radio access nodes configured to communicate wirelessly with access terminals using a first frequency band.
  • These embodiments may further comprise an operator interface configured to connect the one or more network nodes to the spectrum edge network, for routing data to and from access terminals.
  • the one or more network nodes of the communications network are further configured to provide data services to access terminals via a radio access network, distinct from the spectrum edge network, where the radio access network is controlled by one or more network nodes of the communications network.
  • the one or more network nodes are configured to communicate with an access terminal simultaneously through the spectrum edge network and the radio access network, using carrier aggregation of a first carrier in the radio access network and a second carrier in the spectrum edge network.
  • the one or more network nodes may be configured to control the access terminal via the first carrier to establish carrier aggregation of the first and second carriers.
  • one or more network nodes are configured to communicate with each of one or more access terminals through the spectrum access network using a respective proxy identifier, differing from a respective true identifier used for each of the one or more access terminals in the communications network, such that each true identifier is unknown to the spectrum edge network.
  • the one or more network nodes are configured to encrypt data routed to access terminals via the spectrum edge network.
  • the one or more network nodes are configured to encrypt source address associated with data routed to access terminals via the spectrum edge network.
  • encrypt as used here should be understood broadly, to refer to encryption and/or scrambling of data in such a way that the original data cannot readily be obtained without knowledge of an encryption key, scrambling sequence, or the like.

Landscapes

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

Abstract

Un réseau de périphérie de spectre comprend une pluralité de nœuds d'accès radio, chacun étant configuré pour communiquer de manière non filaire avec un ou plusieurs terminaux d'accès à l'aide d'une bande de fréquences. Le réseau de périphérie de spectre comprend également un ou plusieurs nœuds de réseau configurés pour planifier des communications de liaison montante et de liaison descendante vers des terminaux d'accès, le ou les nœuds de réseau étant configurés pour acheminer des données entre les terminaux d'accès et une pluralité de réseaux d'opérateur externes vers le réseau de périphérie de spectre, par l'intermédiaire de nœuds interfaces d'opérateur respectifs.
PCT/IB2021/055716 2021-06-25 2021-06-25 Réseau de périphérie de spectre WO2022269324A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2021/055716 WO2022269324A1 (fr) 2021-06-25 2021-06-25 Réseau de périphérie de spectre

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2021/055716 WO2022269324A1 (fr) 2021-06-25 2021-06-25 Réseau de périphérie de spectre

Publications (1)

Publication Number Publication Date
WO2022269324A1 true WO2022269324A1 (fr) 2022-12-29

Family

ID=77021673

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2021/055716 WO2022269324A1 (fr) 2021-06-25 2021-06-25 Réseau de périphérie de spectre

Country Status (1)

Country Link
WO (1) WO2022269324A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2521401A1 (fr) * 2009-12-30 2012-11-07 Huawei Technologies Co., Ltd. Procédé et appareil de partage de réseau radiophonique
US20170135095A1 (en) * 2015-11-11 2017-05-11 Verizon Patent And Licensing Inc. Allocating resources of an unlicensed radio frequency spectrum band among multiple operator networks for carrier aggregation
US20170311255A1 (en) * 2014-10-09 2017-10-26 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic Multi-Operator Spectrum Activation
US20210029702A1 (en) * 2011-05-20 2021-01-28 Nec Corporation Network sharing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2521401A1 (fr) * 2009-12-30 2012-11-07 Huawei Technologies Co., Ltd. Procédé et appareil de partage de réseau radiophonique
US20210029702A1 (en) * 2011-05-20 2021-01-28 Nec Corporation Network sharing
US20170311255A1 (en) * 2014-10-09 2017-10-26 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic Multi-Operator Spectrum Activation
US20170135095A1 (en) * 2015-11-11 2017-05-11 Verizon Patent And Licensing Inc. Allocating resources of an unlicensed radio frequency spectrum band among multiple operator networks for carrier aggregation

Similar Documents

Publication Publication Date Title
US20190150208A1 (en) Cloud based access solution for enterprise deployment
US8948768B2 (en) Radio communication device and method for controlling resource allocations
CN110366207B (zh) 分类和路由与用户设备相关联的网络流量的系统和方法
US9386480B2 (en) Systems and methods for providing LTE-based backhaul
US10098002B2 (en) Integrated wireless local area network for spectrum sharing
JP6304788B2 (ja) 無線ローカルエリアネットワークにおいてユーザ機器（ｕｅ）の通信をセキュアにする装置、システム及び方法
WO2018069852A1 (fr) Réseau d'accès adapté à la segmentation de réseau
US20150215162A1 (en) System and Method of Radio Bearer Management for Multiple Point Transmission
US8804619B2 (en) Methods for assigning radio resources for mobile devices connected to a mobile communication module and related systems and devices
JP2017538383A (ja) Ｄ２ｄ通信システムにおいてサイドリンク無線ベアラに対する暗号化指示を示す方法及びその装置
KR20170042293A (ko) 디바이스-투-디바이스 근접 서비스 통신에 대한 액세스 클래스 차단
US11399307B2 (en) Service authorization method, terminal device and network device
Al Agha et al. Mobile and wireless networks
US20210084538A1 (en) Systems and Methods for Providing LTE-Based Backhaul
CN113810989B (zh) 一种通信方法及相关设备
Remy et al. LTE standards
Irving et al. Evolutionary analysis of GSM, UMTS and LTE mobile network architectures
EP3952374A1 (fr) Procédé et appareil de communication
US20220377541A1 (en) Key Management Method and Communication Apparatus
US12089225B2 (en) Reduced spectrum allocation in CBRS networks
US20230262715A1 (en) Adaptive unlicensed spectrum revocation
CN103298077B (zh) GSM/GPRS网络与Wi-Fi网络异构方法及系统
WO2022269324A1 (fr) Réseau de périphérie de spectre
US11564105B2 (en) Multilink uplink grant management method
US20170026347A1 (en) Ultra Dense Network Security Architecture and Method

Legal Events

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

Ref document number: 21745417

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21745417

Country of ref document: EP

Kind code of ref document: A1