5G New Radio Load Balancing and Mobility Robustness

Abstract

Apparatus, system and method for implementing load balancing and mobility robustness in a cellular system. A network entity such as a near-RT RIC may receive a range of handover (HO) parameters and / or a performance target of a mobility robustness optimization (MRO) function and / or a load balancing optimization (LBO) function from a service management and orchestration framework (SMOFW), and receive HO-related performance measurements and / or cell load measurements from an open RAN (O‑RAN) distributed unit (O‑DU) or a centralized unit (O‑CU) and analyze the HO-related performance measurements and / or cell load measurements. Based on the analysis, the near-RT RIC may request the SMOFW to change virtualized resources, request the O‑DU to update HO parameters, and / or request the O‑DU / O‑CU to update UE selection, cell selection and / or handover parameters.

Description

Technical Field

[0001] The present application relates to wireless communications, including apparatus, systems, and methods for load balancing and mobility robustness in cellular systems.

[0002] Related technical description

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating sophisticated applications that utilize these functions.

[0004] Long Term Evolution (LTE) has become the technology of choice for most wireless network operators around the world to provide mobile broadband data and high-speed Internet access to their user base. LTE defines a number of downlink (DL) physical channels classified as transport or control channels to carry information blocks received from the medium access control (MAC) and higher layers. LTE also defines the number of physical layer channels for the uplink (UL).

[0005] For example, LTE defines the Physical Downlink Shared Channel (PDSCH) as a DL transport channel. PDSCH is the primary data bearing channel allocated to users on a dynamic and opportunistic basis. PDSCH carries data in a transport block (TB) corresponding to a MAC protocol data unit (PDU), which is passed from the MAC layer to the physical (PHY) layer once per transmission time interval (TTI). PDSCH is also used to transmit broadcast information such as system information blocks (SIBs) and paging messages.

[0006] As another example, LTE defines the physical downlink control channel (PDCCH) as a DL control channel that carries the resource allocation of the UE contained in the downlink control information (DCI) message. Multiple PDCCHs can be transmitted in the same subframe using control channel elements (CCEs), each of which is nine groups of four resource elements called resource element groups (REGs). PDCCH uses quadrature phase shift keying (QPSK) modulation, where four QPSK symbols are mapped to each REG. In addition, depending on the channel conditions, 1, 2, 4, or 8 CCEs can be used to ensure sufficient robustness.

[0007] In addition, LTE defines the Physical Uplink Shared Channel (PUSCH) as a UL channel shared by all devices (user equipment, UE) in a radio cell to transmit user data to the network. The scheduling of all UEs is under the control of the LTE base station (enhanced Node B or eNB). The eNB uses an uplink scheduling grant (DCI format 0) to inform the UE of the resource block (RB) allocation and the modulation and coding scheme to be used. PUSCH typically supports QPSK and orthogonal amplitude modulation (QAM). In addition to user data, PUSCH also carries any control information required to decode the information, such as a transport format indicator and multiple-input multiple-output (MIMO) parameters. The control data is multiplexed with the information data before the digital Fourier transform (DFT) is expanded.

[0008] The next telecommunication standard proposed to go beyond the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is called the 5th Generation Mobile Network or 5th Generation Wireless System, or 5G for short (also called 5G-NR for 5G New Radio, also referred to as NR for short). 5G-NR offers higher capacity for a higher density of mobile broadband users while supporting ultra-reliable and massive machine-type communications from device to device, as well as lower latency and / or lower battery consumption. In addition, 5G-NR may allow for more flexible UE scheduling compared to current LTE. Therefore, efforts are underway to take advantage of the higher throughput possible at higher frequencies in the ongoing development of 5G-NR. Summary of the invention

[0009] Embodiments relate to apparatus, systems, and methods for load balancing and mobility robustness in cellular systems.

[0010] In some embodiments, a near real-time (RT) radio access network (RAN) intelligent controller (RIC) may be configured to receive a range of handover (HO) parameters and / or a performance target of a mobility robustness optimization (MRO) function from a service management and orchestration framework (SMOFW). The near RT-RIC may be configured to receive HO-related performance measurements from an open RAN (O-RAN) distributed unit (O-DU) and analyze the HO-related performance measurements. In some embodiments, the analysis may include comparing the HO-related performance measurements with the performance targets of the MRO function received from the SMOFW. In some embodiments, the near RT-RIC may be configured to perform an action based at least in part on an analysis indicating that the performance targets of the MRO function have not been achieved. In some embodiments, the action may include a near RT RIC requesting the SMOFW to change virtualized resources when necessary, for example, based on an analysis and / or determination of the near RTRIC to change virtualized resources. In some embodiments, the action may include a near RT RIC receiving a notification from an infrastructure and management framework (IMFW) indicating that a virtualized resource has been changed.

[0011] In some embodiments, the near-RT RIC may be configured to receive cell load measurements from the O-DU and / or the O-RAN Central Unit (O-CU) and analyze the cell load measurements. In some embodiments, based on the analysis, the near-RT RIC may be configured to perform at least one load balancing optimization (LBO) action, including:

[0012] Request the O-DU and / or O-CU to update UE selection, cell selection and / or handover parameters;

[0013] Request SMOFW to change virtualized resources; and / or

[0014] Receives notification from IMFW indicating that a virtualized resource has changed.

[0015] In some embodiments, the near-RT RIC may be configured to set a performance target for a distributed LBO function and activate a distributed LBO (D-LBO) function. The near-RT RIC may be configured to receive performance measurements to evaluate D-LBO function performance, analyze the measurements, and perform one or more actions to balance traffic loads between neighboring base stations based at least in part on the D-LBO performance not meeting the performance target.

[0016] In some embodiments, the near RT RIC may be configured to receive handover parameters from the SMOFW, receive handover-related performance measurements from the O-CU, and generate a request based on the performance measurements. In some embodiments, the request may be a request to the O-DU to update handover parameters and / or a request to the SMOFW to change virtualized resources.

[0017] In some embodiments, the near RT RIC may be configured to receive load measurements from the O-CU and / or O-DU and may generate a request based on the load measurements. In some embodiments, the request may be a request for the SMOFW to change virtualized resources and / or a request for the O-DU to update switching parameters.

[0018] The techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, any of unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), base stations, access points, cellular telephones, tablet computers, wearable computing devices, portable media players, automobiles and / or motor vehicles, and a variety of other computing devices.

[0019] This disclosure is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be construed as narrowing the scope or essence of the topics described herein in any way. Other features, aspects and advantages of the topics described herein will become apparent through the following detailed description, drawings and claims.

[0020] It should be noted that the following specific embodiments relate to the accompanying drawings. The same figure numbers may be used in different drawings to identify the same or similar elements. In the following description, for the purpose of illustration rather than limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are described to provide a thorough understanding of various aspects of various embodiments. However, it is obvious to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the descriptions of various embodiments are not obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B) or (A and B). Architecture includes, but is not limited to, network topology. Examples of architecture include, but are not limited to, networks, network topologies, and systems. Examples of networks include, but are not limited to, time-sensitive networks (TSNs), core networks (CNs), any other suitable networks known in the field of wireless communications, or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] A better understanding of the present subject matter may be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0022] A better understanding of the present subject matter may be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0023] Figure 1A An exemplary wireless communication system is shown in accordance with some embodiments.

[0024] Figure 1B Examples of base stations (BSs) and access points in communication with user equipment (UE) devices are shown in accordance with some embodiments.

[0025] Figure 2 An exemplary simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.

[0026] Figure 3 An exemplary block diagram of a BS according to some embodiments is shown.

[0027] Figure 4 An exemplary block diagram of a server according to some embodiments is shown.

[0028] Figure 5A An exemplary block diagram of a UE according to some embodiments is shown.

[0029] Figure 5B An exemplary block diagram of cellular communication circuitry according to some embodiments is shown.

[0030] Fig. 6A An example of the connection between the EPC network, LTE base stations (eNBs), and 5G NR base stations (gNBs) is shown.

[0031] Figure 6B An example of a protocol stack for eNB and gNB is shown.

[0032] Fig. 7A An example of a 5G network architecture according to some embodiments is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access in the 5G CN.

[0033] Figure 7B An example of a 5G network architecture in accordance with some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5G NR) and non-3GPP access to the 5G CN.

[0034] Figure 8 An example of a baseband processor architecture for a UE according to some embodiments is shown.

[0035] Fig. 9 An example of an open RAN (O-RAN) management architecture is shown in accordance with some embodiments.

[0036] Fig. 10A An example of signaling for mobility stability optimization (MRO) according to some embodiments is shown.

[0037] Fig. 10B An example of signaling for load balancing optimization (LBO) is shown according to some embodiments.

[0038] Fig.11A A block diagram of an example of a method for mobility stability optimization (MRO) according to some embodiments is shown.

[0039] Fig. 11B A block diagram illustrating an example of a method for load balancing optimization (LBO) according to some embodiments.

[0040] Fig. 11C A block diagram illustrating another example of a method for load balancing optimization (LBO) according to some embodiments.

[0041] Fig.11DA block diagram illustrating an example of a method for updating handover parameters according to some embodiments is shown.

[0042] Fig.11E A block diagram of an example of a method for generating a request based on cell load measurements according to some embodiments is shown.

[0043] Fig.12 An exemplary architecture of a system of networks according to some embodiments is shown.

[0044] Fig.13 An exemplary architecture of a system including a first CN according to some embodiments is shown.

[0045] Fig.14 The architecture of a system including a second CN according to some embodiments is shown.

[0046] Fig.15 An example of basic equipment is shown according to some embodiments.

[0047] Fig.16 An example of a platform according to some embodiments is shown.

[0048] Fig.17 Exemplary components of a baseband circuit and a radio front end module are shown according to some embodiments.

[0049] Fig.18 Various protocol functions that may be implemented in a wireless communication device according to some embodiments are shown.

[0050] Fig.19 Components of a core network are shown according to some embodiments.

[0051] Fig. 20 is a block diagram illustrating components of a NFV-enabled system according to some embodiments.

[0052] Fig.21 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some embodiments.

[0053] Although the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to limit this document to the specific forms disclosed, but on the contrary, their purpose is to cover all modifications, equivalents and alternatives that fall within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0054] Acronyms

[0055] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms used that may appear throughout this disclosure are as follows:

[0056] 3GPP: Third Generation Partnership Project

[0057] TS: Technical Specification

[0058] RAN: Radio Access Network

[0059] RAT: Radio Access Technology

[0060] UE: User Equipment

[0061] RF: Radio Frequency

[0062] BS: Base Station

[0063] DL: Downlink

[0064] UL: Uplink

[0065] LTE: Long Term Evolution

[0066] NR: New Radio

[0067] 5GS: 5G system

[0068] 5GMM: 5GS Mobility Management

[0069] 5GC: 5G core network

[0070] IE: Information Element

[0071] the term

[0072] The following is a glossary of terms used in this disclosure:

[0073] Storage media—Any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, such as CD-ROM, floppy disk or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, for example, hard disk drive or optical storage device; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or their combinations. In addition, the memory medium may be located in the first computer system executing the program, or may be located in a different second computer system connected to the first computer system through a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, through a network. The memory medium may store program instructions (e.g., expressed as a computer program) that can be executed by one or more processors.

[0074] Carrier medium —Memory media as described above, and physical transmission media such as buses, networks and / or other physical transmission media that transmit signals such as electrical signals, electromagnetic signals or digital signals.

[0075] Programmable hardware components — includes various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can vary from fine-grained (combinational logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0076] Computer system (or computer) —Any of various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, Internet appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0077] User Equipment (UE) (or "UE Device") —Any of various types of computer system devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smart phones (e.g., iPhone TM , based on AndroidTM phones), portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices, other handheld devices, cars and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. In general, the term "UE" or "UE device" can be broadly defined as covering any electronic, computing and / or telecommunication device (or combination of devices) that is easily transported by a user (or with a user) and capable of wireless communication. In addition, the term "user equipment" or "UE" refers to a device of a remote user having radio communication capabilities and that can describe network resources in a communication network. In addition, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" can include any type of wireless / wired device or any computing device including a wireless communication interface.

[0078] Base Station - The term "base station" has the full breadth of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0079] Network Components —The term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN equipment, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, etc.

[0080] Processing element (or processor)—refers to various elements or combinations of elements capable of performing functions in a device such as a user device or a cellular network device. A processing element may include, for example, a processor and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as ASICs (application specific integrated circuits), programmable hardware elements such as field programmable gate arrays (FPGAs), and any of the above combinations.

[0081] Circuit —The term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0082] Processor circuit —The term “processor circuitry” means, is part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes). The terms “application circuitry” and / or “baseband circuitry” may be considered synonymous with “processor circuitry” and may be referred to as “processor circuitry”.

[0083] Interface Circuit —The term "interface circuit" refers to, is a part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0084] Channel—A medium used to transmit information from a sender (transmitter) to a receiver. It should be noted that since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" used in the present invention may be considered to be used in a manner that conforms to the standards of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel may be 22 MHz wide, while a Bluetooth channel may be 1 MHz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0085] bring - The term "band" has the full breadth of its ordinary meaning and includes at least a segment of the spectrum (eg, radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0086] Transmission Scheduling —refers to the scheduling of transmissions such as wireless transmissions. In some specific implementations of cellular radio communications, signals and data transmissions may be organized according to designated time units of a specific duration for which transmissions are performed. As used herein, the term "time slot" has the full range of its usual meaning and refers at least to the minimum (or shortest) scheduling time unit in wireless communications. For example, in 3GPP LTE / LTE-A, transmissions are divided into radio frames, each of which has an equal (time) duration (e.g., 10ms). The radio frames in 3GPP LTE / LTE-A may be further divided into a specified number (e.g., ten) of subframes, each of which has an equal duration, and the subframes are designated as the minimum (shortest) scheduling unit, or a designated time unit for transmission. In this 3GPP LTE example, a "subframe" is an example of a "time slot" as defined above. Similarly, the minimum (or shortest) scheduling time unit for 5G NR (or simply NR) transmissions is referred to as a "time slot."

[0087] resource—The term "resource" has the full range of its usual meaning and may refer to frequency resources and time resources used during wireless communication. As used herein, a resource element (RE) refers to a specific amount or number of resources. For example, in the context of time resources, a resource element may be a time period of a specific length. In the context of frequency resources, a resource element may be a specific frequency bandwidth or a specific amount of frequency bandwidth centered on a specific frequency. As a specific example, a resource element may refer to a resource unit having at least one symbol (with reference to a time resource, such as a time period of a specific length) per at least one subcarrier (with reference to a frequency resource, such as a specific frequency bandwidth, which may be centered on a specific frequency).

[0088] Resource Element Group —The term "resource element group" or "REG" has the full range of its usual meaning and refers to at least a specified number of consecutive resource elements. In some implementations, a resource element group may not include resource elements reserved for reference signals. A control channel element (CCE) refers to a group of a specified number of consecutive REGs. A resource block (RB) refers to a specified number of resource elements consisting of a specified number of subcarriers per a specified number of symbols. Each RB may include a specified number of subcarriers. A resource block group (RBG) refers to a unit including multiple RBs. The number of RBs within an RBG may vary depending on the system bandwidth.

[0089] Wi-Fi —The term "Wi-Fi" has the full scope of its ordinary meaning and includes at least wireless communication networks or RATs that are served by Wireless LAN (WLAN) access points and provide connectivity to the Internet through these access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi". Wi-Fi (WLAN) networks are distinct from cellular networks.

[0090] automatic—refers to an action or operation performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the need for user input to directly specify or perform the action or operation. Thus, the term "automatically" is contrasted with a user manually performing or specifying an action, where the user provides input to directly perform the action. An automatic process may be initiated by input provided by a user, but the subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing in information, selecting check boxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to user actions. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the answers to the fields. As indicated above, a user may invoke the automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions taken by a user.

[0091] About —refers to a value that is close to a correct or exact value. For example, approximately may refer to a value that is within 1% to 10% of an exact (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may depend on the application. For example, in some embodiments, "approximately" may mean within 0.1% of some specified value or desired value, while in various other embodiments, the threshold value may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of a particular application.

[0092] concurrent —refers to parallel execution or implementation, in which tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, in which tasks are executed (at least partially) in parallel on corresponding computing elements, or using "weak parallelism", in which tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0093] Various components may be described as being "configured to" perform one or more tasks. In such environments, "configured to" is a broad statement that generally means "having a structure" that performs one or more tasks during operation. Thus, even when the component is not currently performing the task, the component can be configured to perform the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, "configured to" can be a broad statement that generally means "having a structure" that performs one or more tasks during operation. Thus, even when the component is not currently turned on, the component can be configured to perform the task. Typically, the circuitry that forms the structure corresponding to "configured to" may include hardware circuitry.

[0094] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The description of a component being configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation of that component.

[0095] The titles used herein are only for organizational purposes and are not intended to be used to limit the scope of the specification. As used throughout this application, the word "may" is used in an allowed sense (e.g., meaning with possibility) rather than a mandatory sense (e.g., meaning must). The word "includes" indicates an open relationship, and therefore indicates including but not limited to. Similarly, the word "have" also indicates an open relationship, and therefore indicates having but not limited to. The terms "first", "second", "third", etc. used here are used as labels for the nouns after them, and unless otherwise clearly indicated, do not imply any type of ordering (e.g., space, time, logic, etc.). For example, unless otherwise specified, "a third component electrically connected to a module substrate" does not exclude the situation where "a fourth component electrically connected to a module substrate" is connected before the third component. Similarly, unless otherwise specified, the "second" feature portion does not require the "first" feature portion to be implemented before the "second" feature portion.

[0096] Figure 1A and Figure 1B :Communication System

[0097] Figure 1A A simplified exemplary wireless communication system according to some embodiments is shown. Note that Figure 1A The system is merely one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems, as desired.

[0098] As shown, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipment 106A, user equipment 106B to user equipment 106N, etc. through a transmission medium. Each user equipment may be referred to as a "user equipment" (UE) in this article. Therefore, user equipment 106 is referred to as UE or UE device.

[0099] Base station (BS) 102A may be a base transceiver station (BTS) or a cell site (cellular base station) and may include hardware to enable wireless communications with UEs 106A through 106N.

[0100] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), which are also referred to as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, Advanced LTE (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB".

[0101] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a cellular service provider's core network, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100. In particular, cellular base station 102A may provide UE 106 with various communication capabilities, such as voice, SMS, and / or data services.

[0102] Base station 102A and other similar base stations (such as base stations 102B to base station 102N) operating according to the same or different cellular communication standards can therefore provide a network as a cell that can provide continuous or nearly continuous overlapping service to UE 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0103] Thus, while base station 102A may act as a "serving cell" for UEs 106A-N as shown in FIG. 1 , each UE 106 may also be able to receive signals from (and possibly within communication range of) one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), such cells may be referred to as "neighboring cells". Such cells may also be able to facilitate communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any various other granularity that provide service area sizes. For example, base stations 102A-B shown in FIG. 1 may be macro cells, while base station 102N may be a micro cell. Other configurations are also possible.

[0104] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G-NR) base station or "gNB". In some embodiments, a gNB may be connected to a legacy Evolved Packet Core (EPC) network and / or to a New Radio Core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating in accordance with 5GNR may be connected to one or more TRPs within one or more gNBs.

[0105] It should be noted that the UE 106 is capable of communicating using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interface), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.), the UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, the UE 106 can also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0106] Figure 1B A user device 106 (e.g., one of device 106A through device 106N) is shown in communication with base station 102 and access point 112 according to some embodiments. UE 106 may be a device with cellular communication capabilities and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0107] UE 106 may include a processor configured to execute program instructions stored in a memory. UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein or any portion of any of the method embodiments described herein.

[0108] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR using a single shared radio component and / or GSM, LTE, Advanced LTE, or 5G Nr using a single shared radio component. The shared radio may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Typically, the radio component may include any combination of a baseband processor, an analog radio frequency (RF) signal processing circuit (e.g., including filters, mixers, oscillators, amplifiers, etc.), or a digital processing circuit (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more parts of a receive chain and / or transmit chain between multiple wireless communication technologies such as those discussed above.

[0109] In some embodiments, UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate with it. As another possibility, UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0110] Figure 2 : Access Point Block Diagram

[0111] Figure 2 An exemplary block diagram of an access point (AP) 112 is shown. Note that Figure 2The block diagram of the AP 112 is only one example of a possible system. As shown, the AP 112 may include a processor 204 that may execute program instructions for the AP 112. The processor 204 may also be coupled (directly or indirectly) to a memory management unit (MMU) 240 or other circuit or device, which may be configured to receive addresses from the processor 204 and convert these addresses to locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0112] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide access to the Internet to multiple devices such as UE 106. For example, network port 270 (or an additional network port) may be configured to couple to a local network, such as a home network or an enterprise network. For example, port 270 may be an Ethernet port. The local network may provide a connection to an additional network such as the Internet.

[0113] The AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with the UE 106 via the wireless communication circuit 230. The antenna 234 communicates with the wireless communication circuit 230 via a communication chain 232. The communication chain 232 may include one or more receive chains, one or more transmit chains, or both. The wireless communication circuit 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, when the AP is co-located with a base station in the case of a small cell, or in other cases where it may be desirable for the AP 112 to communicate via a variety of different wireless communication technologies, the wireless communication circuit 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, 5G NR, Long Term Evolution (LTE), Advanced LTE (LTE-A), Global System for Mobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000, etc.

[0114] In some embodiments, as further described below, AP 112 may be configured to perform methods for load balancing and mobility robustness in cellular systems as further described herein.

[0115] Figure 3 :Block diagram of base station

[0116] Figure 3 An exemplary block diagram of a base station 102 according to some embodiments is shown. Note that Figure 3The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuit or device, which may be configured to receive addresses from the processor 404 and convert these addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0117] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access to the network as described above in FIG. Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0118] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0119] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or "gNB". In such embodiments, base station 102 may be connected to a legacy Evolved Packet Core (EPC) network and / or to an NR Core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0120] The base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with the UE device 106 via the radio component 430. The antenna 434 communicates with the radio component 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0121] Base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5GNR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communications according to any one of multiple wireless communication technologies (e.g., 5GNR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0122] As further described later herein, the base station 102 may include hardware and software components for implementing or supporting the implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement or support a portion or all of the implementation of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition thereto), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the base station 102 may be configured to implement or support a portion or all of the implementation of the features described herein.

[0123] In addition, as described herein, processor 404 may be composed of one or more processing elements. In other words, one or more processing elements may be included in processor 404. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. In addition, each integrated circuit may include circuits (e.g., first circuits, second circuits, etc.) configured to perform the functions of one or more processors 404.

[0124] Additionally, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0125] Figure 4 :Block diagram of the server

[0126] Figure 4 An exemplary block diagram of a server 104 according to some embodiments is shown. Note that Figure 4 The base station is only one example of a possible server. As shown, the server 104 may include a processor 444 that can execute program instructions for the server 104. The processor 444 may also be coupled to a memory management unit (MMU) 474, which may be configured to receive addresses from the processor 444 and convert these addresses to locations in memory (e.g., memory 464 and read-only memory (ROM) 454) or to other circuits or devices.

[0127] Base station 104 may be configured to provide access network functionality to a plurality of devices, such as base station 102 and / or UE device 106 , for example, as further described herein.

[0128] In some embodiments, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some embodiments, server 104 may be connected to a legacy Evolved Packet Core (EPC) network and / or to a NR Core (NRC) network.

[0129] As further described later herein, the server 104 may include hardware and software components for implementing or supporting the features described herein. The processor 444 of the server 104 may be configured to implement or support implementing part or all of the methods described herein, for example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, the processor 444 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition thereto), in combination with one or more of the other components 454, 464, and / or 474, the processor 444 of the server 104 may be configured to implement or support implementing part or all of the features described herein.

[0130] In addition, as described herein, processor 444 may be composed of one or more processing elements. In other words, one or more processing elements may be included in processor 444. Therefore, processor 444 may include one or more integrated circuits (ICs) configured to perform the functions of processor 444. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 444.

[0131] Figure 5A :UE block diagram

[0132] Figure 5A1 shows an exemplary simplified block diagram of a communication device 106 according to some embodiments. Note that Figure 5A The block diagram of the communication device is only an example of a possible communication device. According to the embodiment, the communication device 106 can be a user equipment (UE) device, a mobile device or a mobile station, a wireless device or a wireless station, a desktop computer or a computing device, a mobile computing device (e.g., a laptop, a notebook or a portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and / or a combination of devices and other devices. As shown in the figure, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components may be implemented as a system on a chip (SOC), which may include parts for various purposes. Alternatively, the group of components 300 may be implemented as a separate component or a group of components for various purposes. This group of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0133] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; an input device such as a microphone, a camera, a keyboard; an output device such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device 106, and cellular communication circuits 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuits 329 (e.g., Bluetooth TM In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0134] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335 and 336 as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 337 and 338 as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input-multiple-output (MIMO) configuration.

[0135] In some embodiments, as further described below, the cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). In addition, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can switch between radio components dedicated to specific RATs. For example, a first radio component may be dedicated to a first RAT, such as LTE, and may communicate with a dedicated receive chain and a transmit chain shared with an additional radio component, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and may communicate with the dedicated receive chain and the shared transmit chain.

[0136] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include various elements such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0137] The communication device 106 may also include one or more smart cards 345 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more Universal Integrated Circuit Cards) 345. Note that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functionality, such as one or more UICC cards 345, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or implement SIM functionality in other ways. Thus, each SIM may be a single smart card that may be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 310 may be implemented as a removable smart card. Thus, the SIM may be one or more removable smart cards (such as a UICC card, sometimes referred to as a "SIM card"), and / or the SIM 310 may be one or more embedded cards (such as an embedded UICC (eUICC), sometimes referred to as an "eSIM" or "eSIM card").

[0138] In some embodiments (such as when the SIM includes an eUICC), one or more of the SIMs may implement embedded SIM (eSIM) functionality; in such embodiments, a single SIM in the SIM may execute multiple SIM applications. Each SIM may include components such as a processor and / or a memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE 106 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards that implement eSIM functionality) as needed. For example, the UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also contemplated.

[0139] As described above, in some embodiments, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 may allow UE 106 to support two different phone numbers, and may allow UE 106 to communicate on corresponding two or more corresponding networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM 310 may support a second RAT such as 5G NR. Of course, other implementations and RATs are also possible. In some embodiments, when UE 106 includes two SIMs, UE 106 may support a dual card dual communication (DSDA) function. The DSDA function may allow UE 106 to be connected to two networks (and use two different RATs) at the same time, or allow two connections supported by two different SIMs using the same or different RATs to be maintained on the same or different networks at the same time. The DSDA function may also allow UE 106 to receive voice calls or data traffic on any phone number at the same time. In some embodiments, voice calls may be packet-switched communications. In other words, voice calls may be received using voice over LTE (VoLTE) technology and / or voice over NR (VoNR) technology. In some embodiments, the UE 106 may support dual SIM dual standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE 106 to standby for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some embodiments, the DSDx functionality (DSDA or DSDS functionality) may be implemented using a single SIM (e.g., eUICC) that executes multiple SIM applications for different carriers and / or RATs.

[0140] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The one or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from the one or more processors 302 and convert those addresses to locations in a memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or to other circuits or devices (such as display circuit 304, short-range to medium-range wireless communication circuit 329, cellular communication circuit 330, connector I / F 320, and / or display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0141] As described above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuitry.The communication device 106 may be configured to perform a method for load balancing and mobility robustness in a cellular system as further described herein.

[0142] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features of the communication device 106 to send a scheduling profile for power saving to the network. The processor 302 of the communication device 106 may be configured to implement some or all of the features described in the present invention, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement some or all of the features described in the present invention.

[0143] In addition, as described in the present invention, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. In addition, each integrated circuit may include circuits (e.g., first circuits, second circuits, etc.) configured to perform the functions of one or more processors 302.

[0144] Further, as described herein, the cellular communication circuit 330 and the short-range to medium-range wireless communication circuit 329 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-range to medium-range wireless communication circuit 329. Thus, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. Furthermore, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330. Similarly, the short-range to medium-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-range to medium-range wireless communication circuit 329. Furthermore, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range to medium-range wireless communication circuit 329.

[0145] Figure 5B : Block diagram of a cellular communication circuit

[0146] Figure 5B An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. Note that Figure 5B The block diagram of the cellular communication circuitry of is only one example of possible cellular communication circuitry. According to an embodiment, the cellular communication circuitry 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0147] Cellular communication circuitry 330 may be (eg, communicatively; directly or indirectly) coupled to one or more antennas, such as ( Figure 5A 335a-335b and antenna 336 as shown in FIG. 335b and antenna 336 as shown in FIG. 335b. In some embodiments, cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, Figure 5B As shown, cellular communication circuitry 330 may include modem 510 and modem 520. Modem 510 may be configured for communication according to a first RAT, such as, for example, LTE or LTE-A, and modem 520 may be configured for communication according to a second RAT, such as, for example, 5G NR.

[0148] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuits for transmitting and receiving radio signals. For example, the RF front end 530 may include a receiving circuit (RX) 532 and a transmitting circuit (TX) 534. In some embodiments, the receiving circuit 532 may communicate with a downlink (DL) front end 550, which may include circuits for receiving radio signals via an antenna 335a.

[0149] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with the RF front end 540. The RF front end 540 may include circuits for transmitting and receiving radio signals. For example, the RF front end 540 may include a receiving circuit 542 and a transmitting circuit 544. In some embodiments, the receiving circuit 542 may communicate with the DL front end 560, which may include circuits for receiving radio signals via the antenna 335b.

[0150] In some embodiments, the switch 570 may couple the transmit circuit 534 to an uplink (UL) front end 572. In addition, the switch 570 may couple the transmit circuit 544 to the UL front end 572. The UL front end 572 may include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuit 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572) supported by the modem 510, the switch 570 may be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572). Similarly, when the cellular communication circuit 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572) supported by the modem 520, the switch 570 may be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572).

[0151] In some embodiments, the cellular communication circuit 330 may be configured to perform a method for load balancing and mobility robustness in a cellular system as further described herein.

[0152] As described herein, the modem 510 may include hardware and software components for implementing the above-described features or for time-division multiplexing UL data for NSA NR operations and various other techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 512 may be configured to implement part or all of the features described herein. Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement part or all of the feature parts described herein.

[0153] In addition, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0154] As described herein, the modem 520 may include hardware and software components intended to implement the above-described features for transmitting a power-saving scheduling profile to a network, as well as various other techniques described herein. The processor 522 may be configured to implement part or all of the feature parts described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or additionally), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement part or all of the feature parts described herein.

[0155] In addition, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0156] FIG. 6A to FIG. 6B : 5G NR architecture using LTE

[0157] In some implementations, fifth generation (5G) wireless communications will initially be deployed concurrently with current wireless communications standards (e.g., LTE). For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) has been specified as part of the initial deployment of NR. FIG. 6A to FIG. 6B As shown, the evolved packet core (EPC) network 600 may continue to communicate with the current LTE base station (e.g., eNB 602). In addition, the eNB 602 may communicate with the 5G NR base station (e.g., gNB 604), and data may be transferred between the core network 600 and the gNB 604. Thus, the EPC network 600 may be used (or reused), and the gNB 604 may serve as additional capacity for the user equipment, for example, to provide increased downlink throughput for the UE. In other words, LTE may be used for control plane signaling, and NR may be used for user plane signaling. Thus, LTE may be used to establish a connection with the network, and NR may be used for data services.

[0158] Figure 6B The proposed protocol stack for the eNB 602 and the gNB 604 is shown. As shown, the eNB 602 may include a medium access control (MAC) layer 632 that interfaces with the radio link control (RLC) layers 622a-622b. The RLC layer 622a may also interface with the packet data convergence protocol (PDCP) layer 612a, and the RLC layer 622b may interface with the PDCP layer 612b. Similar to the dual connectivity specified in LTE-Advanced Release 12, the PDCP layer 612a may interface with the EPC network 600 via a master cell group (MCG) bearer, while the PDCP layer 612b may interface with the EPC network 600 via a separate bearer.

[0159] In addition, as shown, the gNB 604 may include a MAC layer 634 that interfaces with the RLC layers 624a-624b. The RLC layer 624a may interface with the PDCP layer 612b of the eNB 602 via an X2 interface for information exchange and / or coordination (e.g., scheduling UEs) between the eNB 602 and the gNB 604. In addition, the RLC layer 624b may interface with the PDCP layer 614. Similar to the dual connectivity specified in Advanced LTE Release 12, the PDCP layer 614 may interface with the EPC network 600 via a secondary cell group (SCG) bearer. Therefore, the eNB 602 may be considered a master node (MeNB) and the gNB 604 may be considered a secondary node (SgNB). In some cases, the UE may be required to maintain a connection with both the MeNB and the SgNB. In such a scenario, the MeNB may be used to maintain a radio resource control (RRC) connection with the EPC, while the SgNB may be used for capacity (e.g., additional downlink and / or uplink throughput).

[0160] Fig. 7A , Figure 7B and Figure 8 : 5G core network architecture—interworking with Wi-Fi

[0161] In some embodiments, the 5G core network (CN) can be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non-cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as a Wi-Fi connection). Fig. 7A An example of a 5G network architecture according to some embodiments is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to 5G CN. As shown, a user equipment device (e.g., UE 106) can access 5G CN through both a radio access network (RAN, such as a gNB or base station 604) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP interworking function (N3IWF) 702 network entity. N3IWF may include a connection to a core access and mobility management function (AMF) 704 of the 5G CN. AMF 704 may include an instance of a 5G mobility management (5G MM) function associated with UE 106. In addition, RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, 5G CN can support unified authentication on two connections and allow UE 106 access to be registered simultaneously via gNB 604 and AP 112. As shown, the AMF 704 may include one or more functional entities associated with the 5G CN (e.g., a network slice selection function (NSSF) 720, a short message service function (SMSF) 722, an application function (AF) 724, a unified data management (UDM) 726, a policy control function (PCF) 728, and / or an authentication server function (AUSF) 730). Note that these functional entities may also be supported by the session management function (SMF) 706a and SMF 706b of the 5G CN. The AMF 706 may be connected to (or communicate with) the SMF 706a. In some embodiments, such functional entities may reside on (and / or be executed by and / or supported by) one or more servers 104 located within the RAN and / or core network. In addition, the gNB 604 may communicate with (or be connected to) a user plane function (UPF) 708a, which may also communicate with the SMF 706a. Similarly, N3IWF 702 can communicate with UPF 708b, which can also communicate with SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and IMS core network 710.

[0162] Figure 7BAn example of a 5G network architecture according to some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5G NR) and non-3GPP access to 5G CN. As shown, a user equipment device (e.g., UE 106) can access 5G CN through both a radio access network (RAN, such as gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 may include an instance of a 5G MM function associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, 5G CN can support unified authentication on two connections and allow UE 106 access to be registered simultaneously via gNB 604 and AP 112. In addition, the 5G CN may support dual registration of UEs on both a traditional network (e.g., LTE via base station 602) and a 5G network (e.g., via base station 604). As shown, the base station 602 may have connections to a mobility management entity (MME) 742 and a serving gateway (SGW) 744. The MME 742 may have connections to both the SGW 744 and the AMF 704. In addition, the SGW 744 may have connections to both the SMF 706a and the UPF 708a. As shown, the AMF 704 may include one or more functional entities associated with the 5G CN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728, and / or AUSF 730). It should be noted that the UDM 726 may also include a home subscriber server (HSS) function, and the PCF may also include a policy and charging rules function (PCRF). It should also be noted that these functional entities may also be supported by the SMF 706a and SMF 706b of the 5G CN. AMF 706 may be connected to (or communicate with) SMF 706a. In some embodiments, such functional entities may reside on (and / or be executed by and / or supported by) one or more servers 104 located within the RAN and / or core network. In addition, gNB 604 may communicate with (or be connected to) UPF 708a, which may also communicate with SMF 706a. Similarly, N3IWF 702 may communicate with UPF 708b, which may also communicate with SMF 706b. Both UPFs may communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0163] Note that in various embodiments, one or more of the above-described network entities may be configured to perform methods for improving security checks in 5G NR networks, including, for example, mechanisms for load balancing and mobility robustness in cellular systems as further described herein.

[0164] Figure 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some embodiments is shown. As described above, Figure 8 The baseband processor architecture 800 described in the figure can be implemented on one or more radio components (e.g., the radio components 329 and / or 330 described above) or modems (e.g., modems 510 and / or 520) as described above. As shown in the figure, the non-access layer 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access layer (AS) 870. The 5G NAS 820 may include a communication connection with a 5G AS 840 and a non-3GPP AS 830 and a Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with two access layers. Therefore, the 5G NAS820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The traditional NAS 850 may include functional entities such as a short message service (SMS) entity 852, an evolved packet system (EPS) session management (ESM) entity 854, a session management (SM) entity 856, an EPS mobility management (EMM) entity 858, and a mobility management (MM) / GPRS mobility management (GMM) entity 860. In addition, the traditional AS 870 may include functional entities such as an LTE AS 872, a UMTS AS 874, and / or a GSM / GPRS 876.

[0165] Thus, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that, as shown, 5G MM can maintain a separate connection management and registration management state machine for each connection. In addition, a device (e.g., UE 106) can register to a single PLMN (e.g., 5G CN) using 5G cellular access as well as non-cellular access. In addition, a device can be in a connected state in one access and in an idle state in another access, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0166] It should be noted that in various embodiments, one or more of the above-mentioned functional entities of the 5G NAS and / or 5G AS may be configured to perform, for example, methods for load balancing and mobility robustness in cellular systems as further described herein.

[0167] Fig. 9 :O-RAN Management Architecture

[0168] Fig. 9 An example of an open RAN (O-RAN) management architecture according to some embodiments is shown. Note that Fig. 9 The architecture of is only one example of possible architectures, and features of the present disclosure may be implemented in any of a variety of architectures as desired.

[0169] As shown, a service management and orchestration framework (SMOFW) 900 (which may be a computer system and / or server, such as server 104) may include a non-real-time RAN intelligent controller (RIC) 902 (which may be a software entity, a computer system and / or server, such as server 104) and various other functions and / or entities. The non-real-time RIC 902 may control functions at greater than 1 second, while a near real-time (near RT) RIC 910 may control RAN functions at less than 1 second. In some embodiments, the trained models and real-time control functions generated in the non-real-time RIC 902 may be assigned to the near real-time RIC 910 for runtime execution. In other words, in some embodiments, the non-real-time RIC 902 may be a logical function that is capable of non-real-time control and optimization of RAN elements and resources, AI / ML workflows (including model training and updates), and policy-based guidance of applications / features in the near real-time RIC 910.

[0170] In some embodiments, the SMOFW 900 may interface with the near real-time RCI 910 via an A1 interface. In other words, the SMOFW 900 including (e.g., comprising) the non-real-time RIC 902 may interface with a base station (e.g., base station 102) including (e.g., comprising) the near real-time RIC 910 via an A1 interface. In some embodiments, the A1 interface may enable the network management application in the non-real-time RIC 902 to receive and react to highly reliable data from the modular control units (e.g., O-CU UP 912 and 914) and distributed units (e.g., O-DU 916a-b) in a standardized format. Note that messages generated from AI-enabled policies and ML-based training models in the non-real-time RIC 902 may be transmitted to the near real-time RIC 910. The core algorithms of the non-real-time RIC 902 may be developed and owned by the operator, and the A1 interface may provide the ability to modify RAN behavior by deploying different models optimized for individual operator policies and optimization objectives (e.g., such as methods for load balancing and mobility robustness in cellular systems, for example, as further described herein).

[0171] In addition, SMOFW 900 may interface with various entities via O1 and O1* interfaces. In some embodiments, the O1 interface may be located between SMOFW 900 and management entities in the O-RAN management element, such as for operations and management (OAM), through which FCAPS (fault, configuration, counting, performance, security) management, software management, and / or file management may be implemented. In some embodiments, the O1* interface may be located between SMOFW 900 and the infrastructure management framework (IMFW) 920, for example, to support O-RAN virtual network functions. In some embodiments, IMFW 920 may interface with various infrastructure entities such as infrastructure 930 via a network function virtualization infrastructure (NfVi) interface.

[0172] As shown, the near-RT RIC 910 may be a management entity (e.g., a software entity, a computer system, and / or a server, such as server 104) that is responsible for collecting RAN performance measurements and controlling RAN network functions in a near real-time manner (e.g., in time increments of less than one second). In other words, in some embodiments, the near-real-time RIC 910 may be a logical function that allows near-real-time control and optimization of O-RAN elements and resources via fine-grained data collection and actions on the E2 interface (e.g., near-real-time control and optimization of O-CU CP 912 and O-DU 916a-b). In some embodiments, the near-RT RIC 910 may be used to implement centralized 5G self-organizing network (SON) functions. In some embodiments, the near-RT RIC 910 is capable of controlling one or more O-RAN central units (O-CU) 912 and 914. In some embodiments, the O-CU may be a logical node that hosts the Radio Resource Control (RRC) protocol, the Service Data Adaptation Protocol (SDAP), and / or the Packet Data Convergence Protocol (PDCP). In some embodiments, the O-CU may be divided between control plan and user plane functions. Thus, as shown, the O-CU control plane (CP) 914 may be a logical node hosting the RRC protocol and the control plane portion (or portions) of the PDCP. Similarly, the O-CU user plane (UP) 912 may be a logical node hosting the user plane portion (or portions) of the PDCP and SDAP. In addition, the O-CU UP 912 and the O-CU CP 914 may be handover (and communication) via an E1 interface, as shown.

[0173] In addition, the O-CU UP 912 and the O-CU CP 914 may be interfaced with the O-RAN distributed unit (O-DU) 916a-b via a user plane F1 interface (e.g., F1-U) and a control plane F1 interface (e.g., F1-C). The O-DU 916a-b may be a logical node that hosts a radio link control (RLC) layer, a medium access control (MAC) layer, and / or a higher physical layer based on the lower layer functional division. In addition, the O-DU 916a-b may be coupled to each other via the O1 interface. In addition, the O-DU 916a-b may be interfaced with the O-RAN radio unit (O-RU) 918a-b via an open fronthaul interface. The O-RU 918a-b may be a logical node that hosts a lower physical layer and / or radio frequency (RF) processing based on the lower layer functional division. In addition, the O-RU 918a-b may be interfaced with each other via the O1 interface.

[0174] It is noted that in various embodiments, one or more of the above-mentioned functional entities of the O-RAN management architecture may be configured to perform, for example, the method for load balancing and mobility robustness in a cellular system as further described herein.

[0175] Load balancing and mobility robustness

[0176] In current implementations, the investments necessary to deploy new generations of mobile networks, such as fifth generation new radio (5G NR), have increased dramatically in order to meet the ever-increasing capacity demands. However, the monthly fees paid by each mobile user remain more or less stagnant, and as a result, mobile operators are under pressure to find ways to reduce deployment costs. The advent of software-defined networking (SDN) and network function virtualization (NFV) has enabled the construction of more agile and cheaper core networks. However, the radio access network (RAN), which represents approximately 70% of the total cost of ownership of a network in construction and operation, remains roughly the same. Therefore, organizations like the Open RAN (“O-RAN”) Alliance have been formed to open up the RAN architecture with standard interfaces, enabling multi-vendor deployments and a more competitive and distinct vendor ecosystem. In addition, O-RAN aims to add more intelligence to RAN nodes by defining a RAN Intelligent Controller (RIC) to automate network operations and reduce operating expenses. In addition, when the handover parameters are not set correctly, the 5G NR cell may experience various problems, such as handover occurring too early or too late, handover to the wrong cell, ping-pong handover, and other problems, which not only affect the user experience but also waste network resources.

[0177] Embodiments described herein provide solutions for load balancing optimization (LBO) and mobility robustness optimization (MRO). For example, in some embodiments, MRO may automatically configure handover parameters in a cell to improve handover performance. Additionally, in some embodiments, LBO may automatically distribute (and / or redistribute) user traffic between adjacent cells to ensure that radio resources are used efficiently while providing high-quality end-user experience and performance. In some embodiments, LBO may collect and analyze load information from a cell to determine an LBO action, which may include:

[0178] (a) UE selection, in which a base station (e.g., such as base station 102) selects and commands some UEs to handover to a non-congested neighboring cell (e.g., neighboring base station 102);

[0179] (b) cell selection, where the base station instructs some UEs to camp on less congested neighboring cells; and / or

[0180] (c) Mobility setup, where the base station modifies handover parameters to change the coverage of a congested cell.

[0181] In some embodiments, LBO may redistribute UE traffic between distributed units (DUs) in the same or different central units (CUs), or between two CUs.

[0182] In some embodiments, the MRO solution may include multiple network entities and / or resources. For example, the MRO solution may include a service management and orchestration framework (SMOFW) (such as SMOFW 900), an infrastructure management framework (IMFW) (such as IMFW920), a near real-time RIC (such as near real-time RIC 910) and / or an O-RAN distributed unit (O-DU) (such as O-DU 916a-b). In some embodiments, the SMOFW may set (and / or specify / determine) a range for a handover parameter (e.g., such as a 5G NR handover parameter). In addition, in some embodiments, the SMOFW may set (and / or specify / determine) a performance target for a handover parameter (e.g., a 5G NR handover parameter) and / or an MRO solution (e.g., an MRO function). In some embodiments, the near real-time RIC may collect handover-related performance measurements from one or more O-DUs. In addition, the near real-time RIC may analyze handover-related performance measurements. In some embodiments, analyzing handover-related performance measurements may include comparing the MRO function performance with the target to determine whether (and / or when) the handover parameter needs to be changed. In some embodiments, the near real-time RIC may request the O-DU to update the handover parameters if (and / or when) a change is needed (e.g., based on the analysis). Additionally, in some embodiments, the near real-time RIC may request the SMOFW to change (adjust) the virtualized resources if (and / or when) needed, e.g., as needed. Thus, in some embodiments, the SMOFW may request the IMFW to change (adjust) the virtualized resources, e.g., based on a request from the near real-time RIC.

[0183] For example, Fig. 10A An example of signaling for mobility stability optimization (MRO) according to some embodiments is shown. Among other devices, Fig. 10A The signaling shown in the figure can also be used with any of the systems, methods or devices shown in the figure. In various embodiments, some of the signaling shown can be executed concurrently in an order different from the order shown, or can be omitted. Additional signaling can also be performed as needed. As shown in the figure, the signaling can adopt the following process.

[0184] As shown, signaling may begin with a service management and orchestration framework (SMOFW) (such as SMOFW 900) setting (and / or specifying / determining) a handover parameter range (e.g., a 5G NR handover parameter range) and / or a performance target for an MRO solution (e.g., a performance target for an MRO function). Thus, the SMOFW 900 may send a handover parameter range 1002 and an MRO function performance target 1004 to a near real-time RIC 910. Additionally, the near real-time RIC 910 may receive handover-related performance measurements 1006 from the O-DU 916.

[0185] At 1008, the near real-time RIC 910 may analyze the handover-related performance measurements. For example, the real-time RIC 910 may compare the handover (HO)-related performance measurements received from the O-DU 916 (e.g., O-DU 916a and / or O-DU 916b) with the handover parameter ranges and / or MRO function performance targets received from the SMOFW 900 to determine whether (and / or when) the handover parameters need to be changed.

[0186] At 1010, the near real-time RIC 910 may determine whether the handover parameters need to be changed and / or adjusted, e.g., based on the analysis at 1008. In some embodiments, if (and / or when) the handover parameters do not need to be changed and / or adjusted, the signaling may continue with the near real-time RIC 910 receiving another set of handover-related performance measurements 1006 from the O-DU 916. Alternatively, if (and / or when) the handover parameters do need to be changed and / or adjusted (e.g., based on the analysis at 1008), the signaling may continue with the near real-time RIC 910 sending a change handover parameter request 1012 to the O-DU 916.

[0187] In some embodiments, when the near real-time RIC 910 determines that the handover parameters do need to be changed, the near real-time RIC 910 may determine whether a virtualized resource (VR) needs to be changed and / or adjusted at 1014. In some embodiments, if (and / or when) the VR does not need to be changed and / or adjusted, signaling may continue, wherein the near real-time RIC 910 receives another set of handover-related performance measurements 1006 from the O-DU 916. Alternatively, if (and / or when) the VR needs to be changed and / or adjusted, the near real-time RIC 910 may send a change VR request 1016 to the SMOFW 900.

[0188] The SMOFW 900 may send a VR change request message 1018 to the IMFW 920 in response to receiving the change VR request 1016 from the near real-time RIC 910. The IMFW 920 may then change and / or adjust the VR at 1020. Finally, the IMFW 920 may send a VR change notification 1022 to the SMOFW 900.

[0189] In some embodiments, the LBO scheme may include multiple network entities and / or resources. For example, the LBO scheme may include a service management and orchestration framework (SMOFW) (such as SMOFW 900), an infrastructure management framework (IMFW) (such as IMFW 920), a near real-time RIC (such as near real-time RIC 910), an O-RAN distributed unit (such as O-DU 916a-b) and / or an O-RAN central unit (such as O-CU 912 and 914). In some embodiments, the SMOFW may set (and / or determine) the performance target of the LBO function. The SMOFW may send the performance target to the near real-time RIC, which may collect cell load measurements from one or more O-DUs and / or O-CUs. In some embodiments, the cell load measurements may include radio resources (e.g., such as PRBs), transport network loads (e.g., on F1, Xn and / or E2 interfaces and other network interfaces) and / or virtualized resource usage of each RAN network function. The near real-time RIC may analyze the measurements. In some embodiments, the analysis may include comparing the measured LBO performance with performance targets (e.g., received from SMOFW) to determine whether (and / or when) the cell has been loaded (e.g., overloaded) and may require load balancing. In some embodiments, when the cell requires load balancing, the near real-time RIC may request the O-DU and / or O-CU to update UE selection parameters, cell selection parameters, and / or handover parameters. In addition, in some embodiments, if (and / or when) necessary, for example, as needed, the near real-time RIC may request the SMOFW to change (adjust) virtualized resources. Therefore, in some embodiments, the SMOFW may request the IMFW to change (adjust) virtualized resources, for example, based on a request from the near real-time RIC.

[0190] For example, Fig. 10B An example of signaling for load balancing optimization (LBO) according to some embodiments is shown. Among other devices, Fig. 10B The signaling shown in the figure can also be used with any of the systems, methods or devices shown in the figure. In various embodiments, some of the signaling shown can be executed concurrently in an order different from the order shown, or can be omitted. Additional signaling can also be performed as needed. As shown in the figure, the signaling can adopt the following process.

[0191] As shown, signaling may begin with a service management and orchestration framework (SMOFW), such as SMOFW 900, setting (and / or specifying / determining) a load balancing optimization (LBO) target for an LBO scheme (e.g., an LBO function, such as an LBO management and control function, a distributed LBO function, and / or a centralized LBO function). Thus, SMOFW 900 may send an LBO performance target 1050 to a near real-time RIC 910. Additionally, the near real-time RIC 910 may receive a cell load measurement 1052 from the O-DU 916a.

[0192] At 1054, the near real-time RIC 910 may analyze the cell load measurements. For example, the real-time RIC 910 may compare the cell load measurements received from the O-DU 916a with the LBO performance targets received from the SMOFW 900 to determine whether (and / or when) load balancing may need to be performed.

[0193] At 1056, the near real-time RIC 910 may determine, for example, based on the analysis at 1054, whether load balancing optimization needs to be performed. In some embodiments, if (and / or when) load balancing optimization does not need to be performed, signaling may continue to the near real-time RIC 910 receiving the cell load measurement received from the O-DU 916a. Alternatively, if (and / or when) load balancing optimization does need to be performed (e.g., based on the analysis at 1056), signaling may continue to the near real-time RIC 910 sending messages 1058a-c to the O-DUs 916a-b and the O-CUs 912 / 914, wherein the messages 1058a-c indicate modifications to cell selection / reselection parameters and / or changes to handover parameters.

[0194] In some embodiments, when the near real-time RIC 910 determines that it is indeed necessary to perform load balancing optimization, at 1060, the near real-time RIC 910 may determine whether a virtualized resource (VR) needs to be changed and / or adjusted. In some embodiments, if (and / or when) the VR does not need to be changed and / or adjusted, the signaling may continue to the near real-time RIC 910 receiving the cell load measurement received from the O-DU 916a. Alternatively, if (and / or when) it is indeed necessary to change and / or adjust the VR, the near real-time RIC 910 may send a change VR request 1062 to the SMOFW 900.

[0195] In response to receiving the change VR request 1062 from the near real-time RIC 910, the SMOFW 900 may send a VR change request message 1064 to the IMFW 920. Then, at 1066, the IMFW 920 may change and / or adjust the VR. Finally, the IMFW 920 may send a VR change notification 1068 to the SMOFW 900.

[0196] In some embodiments, the LBO function may collect and / or analyze cell load information to determine actions for load balancing. For example, the actions for load balancing may include: UE selection, in which the base station may select and / or command some UEs (e.g., a portion of the UEs served by the base station) to switch to non-congested neighboring cells; cell reselection, in which the base station may instruct some UEs to camp on less congested neighboring cells; and / or mobility settings, in which the base station may modify switching parameters to change the coverage of congested cells.

[0197] In some embodiments, the LBO scheme may be implemented as distributed LBO (eg, for base stations without functional partitioning) and / or centralized LBO (eg, for base stations with functional partitioning).

[0198] For example, in some embodiments, the LBO management and control function may set a target for a distributed LBO (D-LBO) function, and may activate the D-LBO function to automatically balance cell loads between base stations (e.g., such as gNB 604 and / or base station 102). In some embodiments, the LBO management and control function may initiate a change in virtualized resources upon receiving a notification from the D-LBO function indicating that a change in virtualized resources is required. In some embodiments, the LBO management and control function may collect performance measurements (e.g., performance measurements such as multiple RRC connection establishment / release, abnormal release, handover failure, and / or call drop) to evaluate the performance of the D-LBO. In some embodiments, the LBO management and control function may analyze the performance measurements and, for example, perform one or more corrective actions if (and / or when) the D-LBO performance does not meet the target. In some embodiments, the one or more corrective actions may include:

[0199] (a) updating the objectives of the D-LBO function; and / or

[0200] (b) Disable the D-LBO function and determine whether any additional (corrective) action is required.

[0201] In some embodiments, additional (corrective) actions may include configuration (and / or reconfiguration) of switching parameters and / or reselection parameters of the cell or its neighboring cells and / or initiation of changes to virtualized resources, e.g. to optimize traffic load distribution between neighboring cells. In some embodiments, when the D-LBO functionality is active, the LBO management and control functionality may not configure (and / or reconfigure) switching parameters and / or reselection parameters for load balancing purposes.

[0202] As another example, in some embodiments, the LBO management and control function may receive the target of LBO from the consumer. In addition, in some embodiments, the centralized LBO (C-LBO) function may collect load performance measurements (e.g., such radio resource usage, hardware load indicator, virtualized resource load indicator, transport network layer (TNL) load indicator, composite available capacity PRB, TNL measurement, etc.) and / or notifications from CU-CP, CU-UP and / or DU (e.g., threshold crossing of certain measurements). In some embodiments, the C-LBO function may analyze the load measurements to determine when to perform corrective actions. In some embodiments, the corrective action may include the configuration (and / or reconfiguration) of switching parameters and / or reselection parameters and / or the initiation of changes to virtualized resources, for example, to optimize the traffic load distribution between adjacent cells. In some embodiments, the C-LBO function may collect performance measurements (e.g., multiple RRC connection establishments, multiple RRC connection releases, multiple abnormal releases, multiple switching failures and / or call drops, and other performance measurements) to evaluate LBO performance, and may update the switching parameters and / or reselection parameters of the cell or its adjacent cells.

[0203] In some embodiments, the LBO management and control function may have the ability to set and update LBO targets and / or initiate changes to virtualized resources of the D-LBO. In some embodiments, the LBO management and control function may have the ability to collect performance measurements necessary to evaluate the performance of the D-LBO.

[0204] In some embodiments, the C-LBO function may have the capability to collect load performance measurements and / or notifications necessary for the LBO function. In some embodiments, the C-LBO function may have the capability to determine corrective actions, including the initiation of configuration of handover parameters and / or reselection parameters and / or changes to virtualized resources, such as to optimize traffic load distribution between neighboring cells. In some embodiments, the C-LBO function may have the capability to collect performance measurements to evaluate C-LBO performance.

[0205] Fig.11A A block diagram of an example of a method for mobility stability optimization (MRO) according to some embodiments is shown. Among other devices, Fig.11A The method shown in can also be used together with any one of the system, method or device shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as required. As shown in the figure, the method can be operated as follows.

[0206] At 1102, ranges of handover (HO) parameters and / or performance targets for MRO functions may be received by a near real-time (RT) radio access network (RAN) intelligent controller (RIC) (e.g., such as the near-RT RIC 910) from a service management and orchestration framework (SMOFW) (e.g., such as the SMOFW 900).

[0207] At 1104, HO-related performance measurements may be received by the near-RT RIC from at least one (and / or one or more) open RAN (O-RAN) distributed units (O-DUs), such as the O-DU 916.

[0208] At 1106, the HO-related performance measurements may be analyzed by the near RT-RIC. For example, the HO-related performance measurements may be compared to the performance targets of the MRO function received from the SMOFW. In other words, the near RT RIC may compare the MRO function performance to the targets to determine if (and / or when or if) a change in handover parameters is required.

[0209] At 1108, at least one (and / or one or more) corrective actions may be performed by the near-RT RIC based at least in part on an analysis indicating that a performance target for the MRO function was not achieved (e.g., the HO-related performance measurements do not meet the target MRO function performance). In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC requesting the SMOFW to change the virtualized resources when (and / or when) needed, for example, based on the analysis and / or determination of the near-RT RIC to change the virtualized resources. In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC receiving a notification from an infrastructure and management framework (IMFW) indicating that the virtualized resources have been changed. In some embodiments, the SMOFW may forward the request to change the virtualized resources to the IMFW. In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC sending updated handover parameters to the O-DU, wherein the updated handover parameters are configured to improve the MRO function performance.

[0210] In some embodiments, the near-RT RIC may receive cell load measurements from at least one O-DU and / or O-RAN Central Unit (O-CU) and analyze the cell load measurements. In some embodiments, based on the analysis, the near-RT RIC may perform at least one load balancing optimization (LBO) action. In some embodiments, the at least one LBO action may include any one, any combination, and / or all of the following:

[0211] Request the O-DU and / or O-CU to update UE selection, cell selection and / or handover parameters;

[0212] Request SMOFW to change virtualized resources; and / or

[0213] Receives notification from IMFW indicating that a virtualized resource has changed.

[0214] In some embodiments, the cell load measurements may include radio resources (e.g., physical resource blocks (PRBs)), transport network load (e.g., on F1 interfaces, Xn interfaces, E2 interfaces, etc.), and / or virtualized resource usage per RAN network function. In some embodiments, analysis of the cell load measurements may include comparing LBO performance to a target to determine if (and / or when) a cell is loaded and requires load balancing.

[0215] In some embodiments, the near-RT RIC may set a performance target for the distributed LBO function and activate the distributed LBO (D-LBO) function. In some embodiments, the near-RT RIC may receive performance measurements to evaluate the D-LBO function performance, analyze the measurements, and perform one or more (corrective) actions to balance the traffic load between adjacent base stations based at least in part on the D-LBO performance not meeting the performance target. In some embodiments, the performance measurements may include multiple RRC connection establishment / releases, multiple abnormal releases, multiple handover failures, and / or multiple call drops. In some embodiments, one or more actions may include updating the performance target of the D-LBO function, disabling the D-LBO function, and / or determining an action to optimize the traffic load distribution between adjacent cells. In some embodiments, one or more actions may include configuring the switching of a cell or an adjacent cell and / or reselecting parameters and / or initiating changes to virtualized resources.

[0216] In some embodiments, the near RT RIC may be to receive handover parameters from the SMOFW, receive handover-related performance measurements from the O-CU, and generate a request based on the performance measurements. In some embodiments, the request may be a request from the O-DU to update the handover parameters. In some embodiments, the request may be a request from the SMOFW to change virtualized resources.

[0217] In some embodiments, the near-RT RIC may receive load measurements from the O-CU and / or O-DU and may generate a request based on the load measurements. In some embodiments, the request may be to change virtualized resources for SMOFW. In some embodiments, the request may be a request for the O-DU to update handover parameters. In some embodiments, the load measurements may include indications of radio resources, transport network load, and / or virtualized resource usage.

[0218] Fig. 11B A block diagram illustrating an example of a method for load balancing optimization (LBO) according to some embodiments. Among other devices, Fig. 11B The method shown in can also be used together with any one of the system, method or device shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as required. As shown in the figure, the method can be operated as follows.

[0219] At 1112, cell load measurements may be received from at least one open RAN (O-RAN) distributed unit (O-DU) (such as O-DU 916) and / or an O-RAN central unit (O-CU) (such as O-CU 912 or 914) by a near real-time (RT) radio access network (RAN) intelligent controller (RIC) (e.g., such as near RT RIC 910). In some embodiments, the cell load measurements may include radio resources (e.g., physical resource blocks (PRBs)), transport network load (e.g., on F1 interface, Xn interface, E2 interface, etc.), and / or virtualized resource usage per RAN network function.

[0220] At 1114, the cell load measurements may be analyzed by the near-RT RIC. In some embodiments, the analysis of the cell load measurements may include comparing the LBO performance to a target to determine if (and / or when) the cell is loaded and requires load balancing.

[0221] At 1116, at least one (load balancing optimization (LBO) and / or correction) action may be performed by the near-RT RIC (e.g., based on the analysis). In some embodiments, the at least one action may include any, any combination, and / or all of the near-RT RIC:

[0222] Request the O-DU and / or O-CU to update UE selection, cell selection and / or handover parameters;

[0223] Request SMOFW to change virtualized resources; and / or

[0224] Receives notification from IMFW indicating that a virtualized resource has changed.

[0225] In some embodiments, the near-RT RIC may receive a range of handover (HO) parameters and / or a performance target for a mobility robustness optimization (MRO) function from a service management and orchestration framework (SMOFW) (e.g., such as SMOFW 900). The near-RT RIC may receive HO-related performance measurements from at least one (and / or one or more) O-DUs and analyze the HO-related performance measurements. In some embodiments, the analysis may include comparing the HO-related performance measurements with the performance targets of the MRO function received from the SMOFW. In other words, the near-RT RIC may compare the MRO function performance with the targets to determine whether (and / or when or whether) the handover parameters need to be changed. In some embodiments, the near-RT-RIC may perform at least one (and / or one or more) corrective actions based at least in part on an analysis indicating that the performance targets of the MRO function have not been achieved (e.g., the HO-related performance measurements do not meet the target MRO function performance). In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC requesting the SMOFW to change the virtualized resource when (and / or when) needed, for example, based on an analysis and / or determination of the near-RT RIC to change the virtualized resource. In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC receiving a notification from the infrastructure and management framework (IMFW) indicating that the virtualized resource has been changed. In some embodiments, the SMOFW may forward the request to change the virtualized resource to the IMFW.

[0226] In some embodiments, the near-RT RIC may set a performance target for the distributed LBO function and activate the distributed LBO (D-LBO) function. In some embodiments, the near-RT RIC may receive performance measurements to evaluate the D-LBO function performance, analyze the measurements, and perform one or more (corrective) actions to balance the traffic load between adjacent base stations based at least in part on the D-LBO performance not meeting the performance target. In some embodiments, the performance measurements may include multiple RRC connection establishment / releases, multiple abnormal releases, multiple handover failures, and / or multiple call drops. In some embodiments, one or more actions may include updating the performance target of the D-LBO function, disabling the D-LBO function, and / or determining an action to optimize the traffic load distribution between adjacent cells. In some embodiments, one or more actions may include configuring the switching of a cell or an adjacent cell and / or reselecting parameters and / or initiating changes to virtualized resources.

[0227] In some embodiments, the near RT RIC may be to receive handover parameters from the SMOFW, receive handover-related performance measurements from the O-CU, and generate a request based on the performance measurements. In some embodiments, the request may be a request from the O-DU to update the handover parameters. In some embodiments, the request may be a request from the SMOFW to change virtualized resources.

[0228] In some embodiments, the near-RT RIC may receive load measurements from the O-CU and / or O-DU and may generate a request based on the load measurements. In some embodiments, the request may be to change virtualized resources for SMOFW. In some embodiments, the request may be a request for the O-DU to update handover parameters. In some embodiments, the load measurements may include indications of radio resources, transport network load, and / or virtualized resource usage.

[0229] Fig. 11C A block diagram of another example of a method for load balancing optimization (LBO) according to some embodiments is shown. Among other devices, Fig. 11C The method shown in can also be used together with any one of the system, method or device shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as required. As shown in the figure, the method can be operated as follows.

[0230] At 1122 , a performance target for a distributed LBO function and activation of a distributed LBO (D-LBO) function may be set by a near real-time (RT) radio access network (RAN) intelligent controller (RIC) (eg, such as the near-RT RIC 910 ).

[0231] At 1124 , the D-LBO function may be activated by the near-RT RIC 910 .

[0232] At 1126, performance measurements for evaluating the performance of the D-LBO function may be received by the near RT RIC. In some embodiments, the performance measurements may include multiple RRC connection establishments / releases, multiple abnormal releases, multiple handover failures, and / or multiple call drops.

[0233] At 1128, measurements may be made via near-RT RIC analysis.

[0234] At 1130, one or more (corrective) actions for balancing the traffic load between neighboring base stations may be performed by the near RTRIC, for example, based at least in part on the D-LBO performance not meeting the performance target. In some embodiments, the one or more actions may include updating the performance target of the D-LBO function, disabling the D-LBO function, and / or determining actions to optimize the traffic load distribution between neighboring cells. In some embodiments, the one or more actions may include configuring switching and / or reselection parameters of a cell or neighboring cells and / or initiating changes to virtualized resources.

[0235] In some embodiments, the near-RT RIC may receive a range of handover (HO) parameters and / or a performance target for a mobility robustness optimization (MRO) function from a service management and orchestration framework (SMOFW) (e.g., such as SMOFW 900). The near-RT RIC may receive HO-related performance measurements from at least one (and / or one or more) O-DUs and analyze the HO-related performance measurements. In some embodiments, the analysis may include comparing the HO-related performance measurements with the performance targets of the MRO function received from the SMOFW. In other words, the near-RT RIC may compare the MRO function performance with the targets to determine whether (and / or when or whether) the handover parameters need to be changed. In some embodiments, the near-RT-RIC may perform at least one (and / or one or more) corrective actions based at least in part on an analysis indicating that the performance targets of the MRO function have not been achieved (e.g., the HO-related performance measurements do not meet the target MRO function performance). In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC requesting the SMOFW to change the virtualized resource when (and / or when) needed, for example, based on an analysis and / or determination of the near-RT RIC to change the virtualized resource. In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC receiving a notification from the infrastructure and management framework (IMFW) indicating that the virtualized resource has been changed. In some embodiments, the SMOFW may forward the request to change the virtualized resource to the IMFW.

[0236] In some embodiments, the near-RT RIC may receive cell load measurements from at least one O-DU and / or O-RAN Central Unit (O-CU) and analyze the cell load measurements. In some embodiments, based on the analysis, the near-RT RIC may perform at least one load balancing optimization (LBO) action. In some embodiments, the at least one LBO action may include any one, any combination, and / or all of the following:

[0237] Request the O-DU and / or O-CU to update UE selection, cell selection and / or handover parameters;

[0238] Request SMOFW to change virtualized resources; and / or

[0239] Receives notification from IMFW indicating that a virtualized resource has changed.

[0240] In some embodiments, the cell load measurements may include radio resources (e.g., physical resource blocks (PRBs)), transport network load (e.g., on F1 interfaces, Xn interfaces, E2 interfaces, etc.), and / or virtualized resource usage per RAN network function. In some embodiments, analysis of the cell load measurements may include comparing LBO performance to a target to determine if (and / or when) a cell is loaded and requires load balancing.

[0241] In some embodiments, the near RT RIC may be to receive handover parameters from the SMOFW, receive handover-related performance measurements from the O-CU, and generate a request based on the performance measurements. In some embodiments, the request may be a request from the O-DU to update the handover parameters. In some embodiments, the request may be a request from the SMOFW to change virtualized resources.

[0242] In some embodiments, the near-RT RIC may receive load measurements from the O-CU and / or O-DU and may generate a request based on the load measurements. In some embodiments, the request may be to change virtualized resources for SMOFW. In some embodiments, the request may be a request for the O-DU to update handover parameters. In some embodiments, the load measurements may include indications of radio resources, transport network load, and / or virtualized resource usage.

[0243] Fig.11D A block diagram illustrating an example of a method for updating handover parameters according to some embodiments. Fig.11D The method shown in can also be used together with any one of the system, method or device shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as required. As shown in the figure, the method can be operated as follows.

[0244] At 1142, handover (HO) related parameters may be received from a service management and orchestration framework (SMOFW) (e.g., such as SMOFW 900) via a near real-time (RT) radio access network (RAN) intelligent controller (RIC) (e.g., such as near RT RIC 910).

[0245] At 1144 , HO-related performance measurements may be received from at least one (and / or one or more) open RAN (O-RAN) central unit (O-CU), such as O-CU 912 or 914 .

[0246] At 1146, a request may be generated by the near RT RIC, for example, based on performance measurements. In some embodiments, the request may be a request for the O-DU to update handover parameters. In some embodiments, the request may be a request for the SMOFW to modify virtualized resources.

[0247] In some embodiments, the near-RT RIC may receive a range of handover (HO) parameters and / or a performance target for a mobility robustness optimization (MRO) function from a service management and orchestration framework (SMOFW) (e.g., such as SMOFW 900). The near-RT RIC may receive HO-related performance measurements from at least one (and / or one or more) O-DUs and analyze the HO-related performance measurements. In some embodiments, the analysis may include comparing the HO-related performance measurements with the performance targets of the MRO function received from the SMOFW. In other words, the near-RT RIC may compare the MRO function performance with the targets to determine whether (and / or when or whether) the handover parameters need to be changed. In some embodiments, the near-RT-RIC may perform at least one (and / or one or more) corrective actions based at least in part on an analysis indicating that the performance targets of the MRO function have not been achieved (e.g., the HO-related performance measurements do not meet the target MRO function performance). In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC requesting the SMOFW to change the virtualized resource when (and / or when) needed, for example, based on an analysis and / or determination of the near-RT RIC to change the virtualized resource. In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC receiving a notification from the infrastructure and management framework (IMFW) indicating that the virtualized resource has been changed. In some embodiments, the SMOFW may forward the request to change the virtualized resource to the IMFW.

[0248] In some embodiments, the near-RT RIC may receive cell load measurements from at least one O-DU and / or O-RAN Central Unit (O-CU) and analyze the cell load measurements. In some embodiments, based on the analysis, the near-RT RIC may perform at least one load balancing optimization (LBO) action. In some embodiments, the at least one LBO action may include any one, any combination, and / or all of the following:

[0249] Request the O-DU and / or O-CU to update UE selection, cell selection and / or handover parameters;

[0250] Request SMOFW to change virtualized resources; and / or

[0251] Receives notification from IMFW indicating that a virtualized resource has changed.

[0252] In some embodiments, the cell load measurements may include radio resources (e.g., physical resource blocks (PRBs)), transport network load (e.g., on F1 interfaces, Xn interfaces, E2 interfaces, etc.), and / or virtualized resource usage per RAN network function. In some embodiments, analysis of the cell load measurements may include comparing LBO performance to a target to determine if (and / or when) a cell is loaded and requires load balancing.

[0253] In some embodiments, the near-RT RIC may set a performance target for the distributed LBO function and activate the distributed LBO (D-LBO) function. In some embodiments, the near-RT RIC may receive performance measurements to evaluate the D-LBO function performance, analyze the measurements, and perform one or more (corrective) actions to balance the traffic load between adjacent base stations based at least in part on the D-LBO performance not meeting the performance target. In some embodiments, the performance measurements may include multiple RRC connection establishment / releases, multiple abnormal releases, multiple handover failures, and / or multiple call drops. In some embodiments, one or more actions may include updating the performance target of the D-LBO function, disabling the D-LBO function, and / or determining an action to optimize the traffic load distribution between adjacent cells. In some embodiments, one or more actions may include configuring the switching of a cell or an adjacent cell and / or reselecting parameters and / or initiating changes to virtualized resources.

[0254] In some embodiments, the near-RT RIC may set a performance target for the distributed LBO function and activate the distributed LBO (D-LBO) function. In some embodiments, the near-RT RIC may receive performance measurements to evaluate the D-LBO function performance, analyze the measurements, and perform one or more (corrective) actions to balance the traffic load between adjacent base stations based at least in part on the D-LBO performance not meeting the performance target. In some embodiments, the performance measurements may include multiple RRC connection establishment / releases, multiple abnormal releases, multiple handover failures, and / or multiple call drops. In some embodiments, one or more actions may include updating the performance target of the D-LBO function, disabling the D-LBO function, and / or determining an action to optimize the traffic load distribution between adjacent cells. In some embodiments, one or more actions may include configuring the switching of a cell or an adjacent cell and / or reselecting parameters and / or initiating changes to virtualized resources.

[0255] In some embodiments, the near-RT RIC may receive load measurements from the O-CU and / or O-DU and may generate a request based on the load measurements. In some embodiments, the request may be to change virtualized resources for SMOFW. In some embodiments, the request may be a request for the O-DU to update handover parameters. In some embodiments, the load measurements may include indications of radio resources, transport network load, and / or virtualized resource usage.

[0256] Fig.11E A block diagram of an example of a method for generating a request based on a cell load measurement according to some embodiments is shown. Among other devices, Fig.11E The method shown in can also be used together with any one of the system, method or device shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as required. As shown in the figure, the method can be operated as follows.

[0257] At 1152, cell load measurements (e.g., load measurements) may be received by a near real-time (RT) radio access network (RAN) intelligent controller (RIC) (e.g., such as near-RT RIC 910) from at least one (and / or one or more) open RAN (O-RAN) central unit (O-CU) (e.g., O-CU 912 or 914) and / or O-RAN distributed unit (O-DU) (e.g., O-DU 916a-b). In some embodiments, the cell load measurements may include an indication of radio resources, transport network load, and / or virtualized resource usage.

[0258] At 1154, a load measurement based request may be generated by the near RT RIC. In some embodiments, the request may be used by a service management and orchestration framework (SMOFW), such as SMOFW 900, to modify virtualized resources. In some embodiments, the request may be a request by the O-DU to update handover parameters.

[0259] In some embodiments, the near-RT RIC may receive a range of handover (HO) parameters and / or a performance target of a mobility robustness optimization (MRO) function from the SMOFW. The near-RT RIC may receive HO-related performance measurements from at least one (and / or one or more) O-DUs and analyze the HO-related performance measurements. In some embodiments, the analysis may include comparing the HO-related performance measurements with the performance targets of the MRO function received from the SMOFW. In other words, the near-RT RIC may compare the MRO function performance with the target to determine whether (and / or when or whether) the handover parameters need to be changed. In some embodiments, the near-RT-RIC may perform at least one (and / or one or more) corrective actions based at least in part on an analysis indicating that the performance target of the MRO function is not achieved (e.g., the HO-related performance measurements do not meet the target MRO function performance). In some embodiments, at least one corrective action (and / or action) may include the near-RT RIC requesting the SMOFW to change the virtualized resources when (and / or when) needed, for example, based on the analysis and / or determination of the near-RT RIC to change the virtualized resources. In some embodiments, at least one corrective action (and / or action) may include the near RT RIC receiving a notification from the infrastructure and management framework (IMFW) indicating that the virtualized resource has been changed. In some embodiments, the SMOFW may forward a request to change the virtualized resource to the IMFW.

[0260] In some embodiments, the near-RT RIC may receive cell load measurements from at least one O-DU and / or O-RAN Central Unit (O-CU) and analyze the cell load measurements. In some embodiments, based on the analysis, the near-RT RIC may perform at least one load balancing optimization (LBO) action. In some embodiments, the at least one LBO action may include any one, any combination, and / or all of the following:

[0261] Request the O-DU and / or O-CU to update UE selection, cell selection and / or handover parameters;

[0262] Request SMOFW to change virtualized resources; and / or

[0263] Receives notification from IMFW indicating that a virtualized resource has changed.

[0264] In some embodiments, the cell load measurements may include radio resources (e.g., physical resource blocks (PRBs)), transport network load (e.g., on F1 interfaces, Xn interfaces, E2 interfaces, etc.), and / or virtualized resource usage per RAN network function. In some embodiments, analysis of the cell load measurements may include comparing LBO performance to a target to determine if (and / or when) a cell is loaded and requires load balancing.

[0265] In some embodiments, the near-RT RIC may set a performance target for the distributed LBO function and activate the distributed LBO (D-LBO) function. In some embodiments, the near-RT RIC may receive performance measurements to evaluate the D-LBO function performance, analyze the measurements, and perform one or more (corrective) actions to balance the traffic load between adjacent base stations based at least in part on the D-LBO performance not meeting the performance target. In some embodiments, the performance measurements may include multiple RRC connection establishment / releases, multiple abnormal releases, multiple handover failures, and / or multiple call drops. In some embodiments, one or more actions may include updating the performance target of the D-LBO function, disabling the D-LBO function, and / or determining an action to optimize the traffic load distribution between adjacent cells. In some embodiments, one or more actions may include configuring the switching of a cell or an adjacent cell and / or reselecting parameters and / or initiating changes to virtualized resources.

[0266] In some embodiments, the near-RT RIC may set a performance target for the distributed LBO function and activate the distributed LBO (D-LBO) function. In some embodiments, the near-RT RIC may receive performance measurements to evaluate the D-LBO function performance, analyze the measurements, and perform one or more (corrective) actions to balance the traffic load between adjacent base stations based at least in part on the D-LBO performance not meeting the performance target. In some embodiments, the performance measurements may include multiple RRC connection establishment / releases, multiple abnormal releases, multiple handover failures, and / or multiple call drops. In some embodiments, one or more actions may include updating the performance target of the D-LBO function, disabling the D-LBO function, and / or determining an action to optimize the traffic load distribution between adjacent cells. In some embodiments, one or more actions may include configuring the switching of a cell or an adjacent cell and / or reselecting parameters and / or initiating changes to virtualized resources.

[0267] In some embodiments, the near RT RIC may be to receive handover parameters from the SMOFW, receive handover-related performance measurements from the O-CU, and generate a request based on the performance measurements. In some embodiments, the request may be a request from the O-DU to update the handover parameters. In some embodiments, the request may be a request from the SMOFW to change virtualized resources.

[0268] Exemplary Embodiments

[0269] Example 1 may include an apparatus of a near real-time (RT) radio access network (RAN) intelligent controller (RIC), the near RT RIC configured to operate in a 3GPP network and support mobility robustness optimization (MRO), the apparatus comprising one or more processors configured to:

[0270] receiving a range of 5G New Radio (NR) handover parameters from the Service Management and Orchestration Framework (SMOFW); and

[0271] Receive performance targets for the MRO function from SMOFW; and

[0272] receiving handover related performance measurements from an open distributed unit (O-DU);

[0273] Analytical measurements; and

[0274] Do one of the following:

[0275] If (and / or when) the handover parameters need to be changed, requesting the open distributed unit (O-DU) to update the handover parameters;

[0276] Request SMOFW to modify virtualized resources if (and / or when) necessary; and / or

[0277] Receives a notification from the Infrastructure and Management Framework (IMFW) indicating that a virtualized resource has been changed.

[0278] Example 2 may include an apparatus according to Example 1 or some other examples herein, wherein the close RT RIC analyzes handover-related performance measurements, including comparing MRO functional performance to a target to determine whether (and / or when or whether) handover parameters need to be changed.

[0279] Example 3 may include an apparatus according to Example 1 or 2 or some other example herein, wherein the SMOFW requests the IMFW to change an infrastructure management framework (IMFW) virtualized resource.

[0280] Example 4 may include an apparatus of a near-RT RIC configured to operate in a 3GPP network and support load balancing optimization (LBO), the apparatus comprising one or more processors configured to:

[0281] receiving cell load measurements from an open distributed unit (O-DU) and an open central unit (O-CU);

[0282] Analytical measurements; and

[0283] Do one of the following:

[0284] If (and / or when) load balancing is required, request the O-DU and O-CU to update UE selection, cell selection and / or handover parameters; or

[0285] Request the Service Management and Orchestration Framework (SMOFW) to change virtualized resources if (and / or when) necessary; or

[0286] Receive a notification from an infrastructure management framework (IMFW) indicating that a virtualized resource has been changed.

[0287] Example 5 may include an apparatus according to Example 4 or some other examples herein, wherein the cell load measurement may include radio resources (e.g., physical resource blocks (PRBs)), transport network load (e.g., on an F1 interface, an Xn interface, an E2 interface, etc.), and / or virtualized resource usage for each RAN network function.

[0288] Example 6 may include an apparatus according to Example 4 or some other examples herein, wherein the near-RT RIC analyzes cell load measurements including comparing LBO performance to a target to determine whether (and / or when) a cell is loaded and requires load balancing.

[0289] Example 7 may include an apparatus for load balancing optimization (LBO) management and control functionality, the apparatus comprising one or more processors configured to:

[0290] Set the target of the distributed LBO function;

[0291] Activate the distributed LBO function;

[0292] Receive performance measurements required to evaluate the performance of distributed LBO functions;

[0293] Analytical measurements; and

[0294] If (and / or when) the distributed LBO performance does not meet the target, actions are taken to balance the traffic load between neighboring base stations (gNBs).

[0295] Example 8 may include an apparatus according to Example 7 or some other examples herein, wherein the performance measurements may include multiple RRC connection establishment / releases, multiple abnormal releases, multiple handover failures, and / or multiple call drops.

[0296] Example 9 may include an apparatus according to Example 7 or some other example herein, wherein the actions may include:

[0297] Updated the target of distributed LBO function;

[0298] Disable the D-LBO feature; and / or

[0299] Actions for optimizing traffic load distribution between neighboring cells are determined.

[0300] Example 10 may include an apparatus according to Example 9 or some other Example 9 or some other examples herein, wherein the actions may include:

[0301] configuring handover and / or reselection parameters for a cell or neighboring cells; and

[0302] Initiate changes to virtualized resources.

[0303] Example 11 includes a method comprising:

[0304] receiving switching parameters from the Service Management and Orchestration Framework (SMOFW);

[0305] receiving handover related performance measurements from an open central unit (O-CU); and

[0306] Generate requests based on performance measurements.

[0307] Example 12 may include the method of Example 11 and / or some other examples herein, wherein the request may be a request for an open distributed unit (O-DU) to update a handover parameter.

[0308] Example 13 may include the method of Example 11 and / or some other examples herein, wherein the request may be a request to a service management and orchestration framework (SMOFW) to change a virtualized resource.

[0309] Example 14 may include the method of Example 11 and / or some other examples herein, wherein the method further comprises receiving a mobility robustness optimization (MRO) performance target from the SMOFW.

[0310] Example 15 may include the method of Example 11 and / or some other examples herein, wherein the method further comprises receiving a notification from an infrastructure management framework (IMFW) indicating a change in the virtualized resource.

[0311] Example 16 includes a method comprising:

[0312] receiving load measurements from an open central unit (O-CU) or an open distributed unit (O-DU); and

[0313] Generate requests based on load measurements.

[0314] Example 17 includes a method according to Example 16 and / or some other examples herein, wherein the request may be a request to a service management and orchestration framework (SMOFW) to change a virtualized resource.

[0315] Example 18 includes a method according to Example 16 and / or some other examples herein, wherein the request may be a request for an open distributed unit (O-DU) to update a switching parameter.

[0316] Example 19 includes a method according to Example 16 and / or some other examples herein, wherein the method further comprises receiving a notification indicating a change in the virtualized resource from an infrastructure management framework (IMFW).

[0317] Example 20 includes a method according to Example 16 and / or some other examples herein, wherein the load measurement may include an indication of: radio resources, transport network load, and / or virtualized resource usage.

[0318] Example 21 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of Examples 1 to 20, or any other method or process described herein.

[0319] Example 22 may include one or more non-transitory computer-readable media that include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described or related to any of Examples 1 to 20 or any other method or process described herein.

[0320] Example 23 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Examples 1 to 20, or any other method or process described herein.

[0321] Example 24 may include a method, technique, or process as described or related to any of Examples 1 to 20, or a portion or component thereof.

[0322] Example 25 may include a device comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, as described or related to any of Examples 1 to 20.

[0323] Example 26 may include a signal as described or related to any of Examples 1 to 20, or a portion or component thereof.

[0324] Example 27 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any of Examples 1 to 20, or a portion or component thereof, or otherwise described in the present disclosure.

[0325] Example 28 may include a signal encoded with data as described or related to any one of Examples 1 to 20, or a portion or component thereof, or otherwise described in the present disclosure.

[0326] Example 29 may include a signal encoding a datagram, packet, frame, segment, protocol data unit (PDU) or message as described or associated with any of Examples 1 to 20, or a portion or component thereof, or otherwise described in the present disclosure.

[0327] Example 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any of Examples 1 to 20.

[0328] Example 31 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Examples 1 to 20, or a portion thereof.

[0329] Example 32 may include signals in a wireless network as shown and described herein.

[0330] Example 33 may include a method of communicating in a wireless network as shown and described herein.

[0331] Example 34 may include a system for providing wireless communications as shown and described herein.

[0332] Example 35 may include an apparatus for providing wireless communications as shown and described herein.

[0333] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0334] System and implementation

[0335] Fig.12An exemplary architecture of a system 1200 of a network according to various embodiments is shown. The following description is provided for an exemplary system 1200 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0336] like Fig.12 As shown, system 1200 includes UE 1201a and UE 1201b (collectively referred to as "UE 1201"). In this example, multiple UEs 1201 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument panels (ICs), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0337] In some embodiments, any of the UEs 1201 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0338] UE 1201 may be configured to connect, e.g., be communicatively coupled, to RAN 1210. In an embodiment, RAN 1210 may be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to RAN 1210 operating in NR or 5G system 1200, while the term "E-UTRAN" or the like may refer to RAN 1210 operating in LTE or 4G system 1200. UE 1201 utilizes connections (or channels) 1203 and 1204, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0339] In this example, connections 1203 and 1204 are shown as air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 1201 may directly exchange communication data via a ProSe interface 1205. The ProSe interface 1205 may alternatively be referred to as a SL interface 1205, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0340] UE 1201b is shown as being configured to access AP 1206 (also referred to as "WLAN node 1206," "WLAN 1206," "WLAN terminal 1206," "WT 1206," etc.) via connection 1207. Connection 1207 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 1206 would include Wireless Fidelity. router. In this example, AP 1206 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 1201b, RAN 1210, and AP 1206 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 1201b in an RRC_CONNECTED state configured by RAN nodes 1211a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 1201b using WLAN radio resources (e.g., connection 1207) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 1207. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0341] The RAN 1210 includes one or more AN nodes or RAN nodes 1211a and 1211b (collectively referred to as "RAN nodes 1211") that enable connections 1203 and 1204. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to a RAN node 1211 (e.g., a gNB) operating in an NR or 5G system 1200, while the terms "E-UTRAN node" and the like may refer to a RAN node 1211 (e.g., an eNB) operating in an LTE or 4G system 1200. According to various embodiments, the RAN node 1211 may be implemented as one or more of dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0342] In some embodiments, all or part of the RAN node 1211 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splitting, such as PDCP splitting, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 1211; MAC / PHY splitting, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 1211; or "lower PHY" splitting, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes 1211. This virtualization framework allows idle processor cores of the RAN node 1211 to execute other virtualized applications. In some specific implementations, a separate RAN node 1211 may be represented via a separate F1 interface ( Fig.12 In these embodiments, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Fig.15), and the gNB-CU may be operated by a server (not shown) located in the RAN 1210 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 1211 may be a next generation eNB (ng-eNB), which is a next generation eNB that provides E-UTRA user plane and control plane protocol terminals to the UE 1201 and is connected to the 5GC (e.g., NG-eNB) via an NG interface (discussed below). Fig.14 RAN node of CN 1420).

[0343] In a V2X scenario, one or more of the RAN nodes 1211 may be an RSU or act as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 1201 (vUE 1201). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. In addition or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0344] Any of the RAN nodes 1211 may terminate the air interface protocol and may be the first point of contact for the UE 1201. In some embodiments, any of the RAN nodes 1211 may perform various logical functions of the RAN 1210, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0345] In an embodiment, multiple UEs 1201 may be configured to communicate with each other or with any of multiple RAN nodes 1211 on a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as but not limited to OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0346] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 1211 to the UE 1201, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0347] According to various embodiments, UE 1201 and RAN node 1211 communicate data (e.g., send data and receive data) through a licensed medium (also referred to as "licensed spectrum" and / or "licensed frequency band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and / or "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0348] To operate in the unlicensed spectrum, the UE 1201 and the RAN node 1211 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 1201 and the RAN node 1211 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0349] LBT is a mechanism by which equipment (e.g., UE 1201, RAN node 1211, etc.) senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include a CCA that utilizes at least an ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0350] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 1201, AP 1206, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0351] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0352] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL, and may handle activities related to RRC and NAS. Other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require UE 1201 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0353] The PDSCH carries user data and higher layer signaling to the UE 1201. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It may also inform the UE 1201 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 1201b within a cell) may be performed at any of the RAN nodes 1211 based on channel quality information fed back from any of the UEs 1201. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UEs 1201.

[0354] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0355] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0356] RAN nodes 1211 may be configured to communicate with each other via interface 1212. In the case where system 1200 is an LTE system (eg, when CN 1220 is Fig.13 In an implementation scheme of the EPC 1320 in the MeNB, the interface 1212 may be an X2 interface 1212. The X2 interface may be defined between two or more RAN nodes 1211 (e.g., two or more eNBs, etc.) connected to the EPC 1220, and / or between two eNBs connected to the EPC 1220. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-sequence delivery of PDCP PDUs from the SeNB to the UE 1201 for user data; information about PDCP PDUs that were not delivered to the UE 1201; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0357] When system 1200 is a 5G or NR system (e.g., when CN 1220 is Fig.14In an implementation scheme of the 5GC 1420 in the 5GC 1420, the interface 1212 may be an Xn interface 1212. The Xn interface is defined between two or more RAN nodes 1211 (e.g., two or more gNBs, etc.) connected to the 5GC 1220, between a RAN node 1211 (e.g., a gNB) and an eNB connected to the 5GC 1220, and / or between two eNBs connected to the 5GC 1220. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for the UE 1201 in a connected mode (e.g., a CM connection) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 1211. Mobility support may include context transfer from the old (source) service RAN node 1211 to the new (target) service RAN node 1211; and control of the user plane tunnel between the old (source) service RAN node 1211 and the new (target) service RAN node 1211. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and / or IP layer for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0358] RAN 1210 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to a core network (CN) 1220. CN 1220 may include a plurality of network elements 1222 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 1201) connected to CN 1220 via RAN 1210. The components of CN 1220 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 1220 may be referred to as a network slice, and a logical instance of a portion of CN 1220 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0359] Generally speaking, the application server 1230 may be an element that provides an application program that uses IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). The application server 1230 may also be configured to support one or more communication services for the UE 1201 via the EPC 1220 (e.g., VoIP session, PTT session, group communication session, social network service, etc.).

[0360] In an embodiment, CN 1220 may be a 5GC (referred to as "5GC 1220" or the like), and RAN 1210 may be connected to CN 1220 via an NG interface 1213. In an embodiment, NG interface 1213 may be divided into two parts: an NG user plane (NG-U) interface 1214, which carries traffic data between RAN node 1211 and UPF; and an S1 control plane (NG-C) interface 1215, which is a signaling interface between RAN node 1211 and AMF. Fig.14 An implementation of CN 1220 as 5GC 1220 is discussed in more detail.

[0361] In an embodiment, CN 1220 may be a 5G CN (referred to as "5GC 1220", etc.), while in other embodiments, CN 1220 may be an EPC. In the case where CN 1220 is an EPC (referred to as "EPC 1220", etc.), RAN 1210 may be connected to CN 1220 via an S1 interface 1213. In an embodiment, S1 interface 1213 may be divided into two parts: an S1 user plane (S1-U) interface 1214, which carries traffic data between RAN node 1211 and S-GW; and an S1-MME interface 1215, which is a signaling interface between RAN node 1211 and MME.

[0362] Fig.13 FIG. 1 shows an exemplary architecture of a system 1300 including a first CN 1320 according to various embodiments. In this example, the system 1300 may implement the LTE standard, where the CN 1320 is a Fig.12 In addition, UE 1301 can communicate with Fig.12 The UE 1201 is the same as or similar to the UE 1201, and the E-UTRAN 1310 may be Fig.12 The CN 1320 may be a RAN that is the same as or similar to the RAN 1210 of the mobile station, and may include the RAN node 1211 discussed previously. The CN 1320 may include an MME 1321, an S-GW 1322, a P-GW 1323, an HSS 1324, and an SGSN 1325.

[0363] MME 1321 may be similar in function to the control plane of a traditional SGSN, and may implement MM functions to track the current location of UE 1301. MME 1321 may perform various MM procedures to manage mobility aspects in access, such as gateway selection and tracking area list management. MM (also referred to as "EPS MM" or "EMM" in E-UTRAN systems) may refer to all applicable procedures, methods, data storage, etc. for maintaining knowledge of the current location of UE 1301, providing user identity confidentiality, and / or performing other similar services to users / subscribers. Each UE 1301 and MME 1321 may include an MM or EMM sublayer, and when the attachment procedure is successfully completed, an MM context may be established in UE 1301 and MME 1321. An MM context may be a data structure or database object that stores MM-related information of UE 1301. The MME 1321 may be coupled to the HSS 1324 via an S6a reference point, to the SGSN 1325 via an S3 reference point, and to the S-GW 1322 via an S11 reference point.

[0364] SGSN 1325 may be a node that serves UE 1301 by tracking the location of individual UE 1301 and performing security functions. In addition, SGSN 1325 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 1321; handling of UE 1301 time zone functions as specified by MME 1321; and MME selection for handover to E-UTRAN 3GPP access network. The S3 reference point between MME 1321 and SGSN 1325 may enable user and bearer information exchange for inter-3GPP access network mobility in an idle state and / or an active state.

[0365] The HSS 1324 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. The EPC 1320 may include one or several HSSs 1324, depending on the number of mobile users, the capacity of the equipment, the organization of the network, etc. For example, the HSS 1324 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. The S6a reference point between the HSS 1324 and the MME 1321 may enable the transmission of subscription data and authentication data for authenticating / authorizing user access to the EPC 1320 between the HSS 1324 and the MME 1321.

[0366] The S-GW 1322 may terminate the S1 interface 1213 towards the RAN 1310 (at Fig.13 1321) and routes data packets between RAN 1310 and EPC 1320. In addition, S-GW 1322 can be a local mobility anchor for inter-RAN node handovers and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies. The S11 reference point between S-GW 1322 and MME 1321 can provide a control plane between MME 1321 and S-GW 1322. S-GW 1322 can be coupled to P-GW 1323 via an S5 reference point.

[0367] P-GW 1323 may terminate the SGi interface toward PDN 1330. P-GW 1323 may route data packets between EPC 1320 and external networks such as a network including an application server 1230 (alternatively referred to as "AF") via IP interface 1225 (see, e.g. Fig.12 In an embodiment, P-GW 1323 can communicate with the user via IP communication interface 1225 (see, e.g. Fig.12 ) is communicatively coupled to an application server ( Fig.12Application server 1230 or Fig.13 The S5 reference point between the P-GW 1323 and the S-GW 1322 may provide user plane tunneling and tunnel management between the P-GW 1323 and the S-GW 1322. The S5 reference point may also be used for S-GW 1322 relocation due to UE 1301 mobility and if the S-GW 1322 needs to be connected to a non-co-located P-GW 1323 for required PDN connectivity. The P-GW 1323 may also include nodes for policy implementation and charging data collection, such as a PCEF (not shown). In addition, the SGi reference point between the P-GW 1323 and the packet data network (PDN) 1330 may be an operator-external public, private PDN, or an internal operator packet data network, such as for providing IMS services. The P-GW 1323 may be coupled to the PCRF 1326 via a Gx reference point.

[0368] PCRF 1326 is a policy and charging control element of EPC 1320. In a non-roaming scenario, there may be a single PCRF 1326 in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of UE 1301. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of UE 1301: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). PCRF 1326 may be communicatively coupled to application server 1330 via P-GW 1323. Application server 1330 may signal PCRF 1326 to indicate a new service flow and select appropriate QoS and charging parameters. PCRF 1326 may configure the rule to a PCEF (not shown) with the appropriate TFT and QCI, which initiates QoS and charging specified by application server 1330. The Gx reference point between PCRF 1326 and P-GW 1323 may allow QoS policies and charging rules to be transferred from PCRF 1326 to the PCEF in P-GW 1323. The Rx reference point may reside between PDN 1330 (or "AF 1330") and PCRF 1326.

[0369] Fig.14The architecture of a system 1400 including a second CN 1420 according to various embodiments is shown. The system 1400 is shown to include a UE 1401, which may be the same or similar to the UE 1201 and UE 1301 discussed previously; a (R) AN 1410, which may be the same or similar to the RAN 1210 and RAN 1310 discussed previously, and which may include the RAN node 1211 discussed previously; and a DN 1403, which may be, for example, an operator service, Internet access, or a 3rd party service; and a 5GC 1420. The 5GC 1420 may include an AUSF 1422; an AMF 1421; an SMF 1424; an NEF 1423; a PCF 1426; an NRF 1425; an UDM 1427; an AF 1428; an UPF 1402; and an NSSF 1429.

[0370] The UPF 1402 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the DN 1403, and a branch point to support multi-host PDU sessions. The UPF 1402 may also perform packet routing and forwarding, perform packet inspection, perform the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1402 may include an uplink classifier for supporting routing of traffic to a data network. The DN 1403 may represent various network operator services, Internet access, or third-party services. The DN 1403 may include or be similar to the application server 1230 discussed previously. UPF 1402 may interact with SMF 1424 via the N4 reference point between SMF 1424 and UPF 1402.

[0371] AUSF 1422 may store data for authenticating UE 1401 and handle authentication-related functions. AUSF 1422 may facilitate a common authentication framework for various access types. AUSF 1422 may communicate with AMF 1421 via the N12 reference point between AMF 1421 and AUSF 1422; and may communicate with UDM 1427 via the N13 reference point between UDM 1427 and AUSF 1422. In addition, AUSF 1422 may present an interface based on Nausf services.

[0372] AMF 1421 may be responsible for registration management (e.g., responsible for registering UE 1401, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 1421 may be the termination point of the N11 reference point between AMF 1421 and SMF 1424. AMF 1421 may provide transport for SM messages between UE 1401 and SMF 1424, and act as a transparent proxy for routing SM messages. AMF 1421 may also provide a transport for UE 1401 and SMSF ( Fig.14 401). The AMF 1421 may provide transport for SMS messages between the (R)AN 1410 and the AMF 1421 (not shown). The AMF 1421 may act as a SEAF, which may include interaction with the AUSF 1422 and the UE 1401, receiving intermediate keys established as a result of the UE 1401 authentication process. In the case of using USIM-based authentication, the AMF 1421 may retrieve security material from the AUSF 1422. The AMF 1421 may also include an SCM function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 1421 may be a termination point for the RAN CP interface, which may include or be the N2 reference point between the (R)AN 1410 and the AMF 1421; and the AMF 1421 may be a termination point for NAS (N1) signaling, and perform NAS encryption and integrity protection.

[0373] The AMF 1421 may also support NAS signaling with the UE 1401 over the N3 IWF interface. The N3IWF may be used to provide access to untrusted entities. The N3IWF may be the termination point for the N2 interface between the (R)AN 1410 and the AMF 1421 for the control plane, and may be the termination point for the N3 reference point between the (R)AN 1410 and the UPF 1402 for the user plane. Thus, the AMF 1421 may process N2 signaling for PDU sessions and QoS from the SMF 1424 and the AMF 1421, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 1401 and the AMF 1421 via the N1 reference point between the UE 1401 and the AMF 1421, and relay uplink and downlink user plane packets between the UE 1401 and the UPF 1402. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 1401. The AMF 1421 may present an interface based on the Namf service and may be an N14 reference point between the two AMFs 1421 and the AMF 1421 and the 5G-EIR ( Fig.14 The termination point of the N17 reference point between the two (not shown).

[0374] UE 1401 may need to register with AMF 1421 in order to receive network services. RM is used to register or deregister UE 1401 with the network (e.g., AMF 1421) and establish a UE context in the network (e.g., AMF 1421). UE 1401 may operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE 1401 is not registered with the network, and the UE context in AMF 1421 does not maintain valid location or routing information for UE 1401, so UE 1401 is not accessible by AMF 1421. In the RM-REGISTERED state, UE 1401 is registered with the network, and the UE context in AMF 1421 may maintain valid location or routing information for UE 1401, so UE 1401 is accessible by AMF 1421. In the RM-REGISTERED state, UE 1401 can perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (for example, to notify the network that UE 1401 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0375] AMF 1421 may store one or more RM contexts for UE 1401, each RM context being associated with a specific access right of the network. An RM context may be a data structure, a database object, etc., which indicates or stores, among other things, the registration status and periodic update timer for each access type. AMF 1421 may also store a 5GC MM context which may be the same or similar to the (E)MM context discussed previously. In various embodiments, AMF 1421 may store CE mode B restriction parameters for UE 1401 in an associated MM context or RM context. AMF 1421 may also derive values ​​from the UE's usage setting parameters already stored in the UE context (and / or MM / RM context) when necessary.

[0376] The CM may be used to establish and release a signaling connection between the UE 1401 and the AMF 1421 over the N1 interface. The signaling connection is used to implement NAS signaling exchanges between the UE 1401 and the CN 1420, and includes both a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and an N2 connection of the UE 1401 between the AN (e.g., the RAN 1410) and the AMF 1421. The UE 1401 may operate in one of two CM states (i.e., a CM-idle mode or a CM-connected mode). When the UE 1401 is operating in the CM-idle state / mode, the UE 1401 may not have a NAS signaling connection established with the AMF 1421 over the N1 interface, and there may be a (R)AN 1410 signaling connection (e.g., an N2 and / or N3 connection) for the UE 1401. When the UE 1401 is operating in the CM-connected state / mode, the UE 1401 can have a NAS signaling connection established with the AMF 1421 through the N1 interface, and there may be a (R)AN 1410 signaling connection (e.g., N2 and / or N3 connection) for the UE 1401. The establishment of the N2 connection between the (R)AN 1410 and the AMF 1421 may cause the UE 1401 to transition from the CM-idle mode to the CM-connected mode, and when the N2 signaling between the (R)AN 1410 and the AMF 1421 is released, the UE 1401 may transition from the CM-connected mode to the CM-idle mode.

[0377] SMF 1424 may be responsible for SM (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering of UPF to route traffic to the correct destination; terminating the interface toward the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN via AMF over N2; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between a UE 1401 and a data network (DN) 1403 identified by a data network name (DNN). The PDU session may be established at the request of UE 1401, modified at the request of UE 1401 and 5GC 1420, and released at the request of UE 1401 and 5GC 1420 using NAS SM signaling exchanged over the N1 reference point between UE 1401 and SMF 1424. Upon request by the application server, 5GC 1420 may trigger a specific application in UE 1401. In response to receiving the trigger message, UE 1401 may pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 1401. The identified application in UE 1401 may establish a PDU session to a specific DNN. SMF 1424 may check whether the UE 1401 request complies with the user subscription information associated with UE 1401. In this regard, SMF 1424 may retrieve and / or request to receive update notifications about SMF 1424 level subscription data from UDM 1427.

[0378] SMF 1424 may include the following roaming functions: handling local execution to apply QoS SLA (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interface with LI system, in VPLMN); and support interaction with external DN to transmit signaling for PDU session authorization / authentication through external DN. In a roaming scenario, an N16 reference point between two SMFs 1424 may be included in the system 1400, which may be located between another SMF 1424 in the visited network and the SMF 1424 in the home network. In addition, SMF 1424 may present an interface based on Nsmf services.

[0379] NEF 1423 may provide components for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 1428), edge computing or fog computing systems, etc. In such embodiments, NEF 1423 may authenticate, authorize and / or restrict AF. NEF 1423 may also convert information exchanged with AF 1428 and information exchanged with internal network functions. For example, NEF 1423 may convert between AF service identifiers and internal 5GC information. NEF 1423 may also receive information from other network functions (NFs) based on the exposure capabilities of other network functions. The information may be stored at NEF 1423 as structured data, or stored at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 1423, and / or used for other purposes such as analysis. In addition, NEF 1423 may present an interface based on Nnef services.

[0380] NRF 1425 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 1425 also maintains information of available NF instances and the services they support. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of a program code. In addition, NRF 1425 may present an interface based on Nnrf services.

[0381] The PCF 1426 may provide for control plane functions to enforce their policy rules, and may also support a unified policy framework for managing network behavior. The PCF 1426 may also implement a FE to access subscription information related to policy decisions in the UDR of the UDM 1427. The PCF 1426 may communicate with the AMF 1421 via the N15 reference point between the PCF 1426 and the AMF 1421, which may include the PCF 1426 in the visited network and the AMF 1421 in the case of a roaming scenario. The PCF 1426 may communicate with the AF 1428 via the N5 reference point between the PCF 1426 and the AF 1428; and communicate with the SMF 1424 via the N7 reference point between the PCF 1426 and the SMF 1424. The system 1400 and / or the CN 1420 may also include an N24 reference point between the PCF 1426 (in the home network) and the PCF 1426 in the visited network. Additionally, PCF 1426 may present an interface based on Npcf services.

[0382] UDM 1427 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data of UE 1401. For example, subscription data may be transmitted between UDM 1427 and AMF via an N8 reference point between UDM 1427 and AMF 1421. UDM 1427 may include two parts: application FE and UDR ( Fig.14 FE and UDR are not shown). UDR can store subscription data and policy data of UDM 1427 and PCF 1426, and / or structured data for exposure and application data of NEF 1423 (including PFD for application detection, application request information of multiple UEs 1401). Nudr service-based interfaces can be presented by UDR 221 to allow UDM 1427, PCF 1426 and NEF 1423 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of related data changes in UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends may serve the same user. UDM-FE accesses subscription information stored in UDR, and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. UDR can interact with SMF 1424 via the N10 reference point between UDM 1427 and SMF 1424. UDM 1427 may also support SMS management, where SMS-FE implements similar application logic as described above. In addition, UDM 1427 may present an interface based on Nudm services.

[0383] AF 1428 can provide the influence of applications on traffic routing, provide access to NCE, and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC 1420 and AF 1428 to provide information to each other via NEF 1423, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 1401 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementation, 5GC can select UPF 1402 near UE 1401 and perform traffic steering from UPF 1402 to DN 1403 via the N6 interface. This can be based on UE subscription data, UE location and information provided by AF 1428. In this way, AF 1428 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 1428 is considered a trusted entity, the network operator can allow AF 1428 to interact directly with the relevant NF. In addition, AF 1428 can present an interface based on Naf services.

[0384] NSSF 1429 may select a set of network slice instances to serve UE 1401. If necessary, NSSF 1429 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI. NSSF 1429 may also determine the AMF set, or a list of candidate AMFs 1421, to serve UE 1401 based on appropriate configuration and possibly by querying NRF 1425. The selection of a set of network slice instances for UE 1401 may be triggered by AMF 1421, where UE 1401 registers by interacting with NSSF 1429, which may result in changes to AMF 1421. NSSF 1429 may interact with AMF 1421 via the N22 reference point between AMF 1421 and NSSF 1429; and may communicate via the N31 reference point ( Fig.14 The NSSF 1429 may communicate with another NSSF 1429 in the visited network (not shown). In addition, the NSSF 1429 may present an interface based on the Nnssf service.

[0385] As previously described, CN 1420 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from other entities, such as SMS-GMSC / IWMSC / SMS-Router, to / from UE 1401. SMS may also interact with AMF 1421 and UDM 1427 for notification procedures so that UE 1401 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 1427 when UE 1401 is available for SMS).

[0386] CN 120 may also include Fig.14 Other elements not shown, such as data storage system / architecture, 5G-EIR, SEPP, etc. The data storage system may include SDSF, UDSF, etc. Any NF may communicate with any NF and UDSF ( Fig.14 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data in or from the UDSF (e.g., UE context). Individual NFs may share a UDSF for storing their respective unstructured data, or individual NFs may each have their own UDSF located at or near a single NF. In addition, the UDSF may present an interface based on the Nudsf service ( Fig.14 (not shown). The 5G-EIR may be a NF that checks the status of the PEI to determine whether to blacklist a specific equipment / entity from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0387] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Fig.14 These interfaces and reference points are omitted. In one embodiment, CN 1420 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 1321) and AMF 1421 to enable interworking between CN 1420 and CN 1320. Other example interfaces / reference points may include an interface based on N5g-EIR services presented by 5G-EIR, an N27 reference point between an NRF in a visited network and an NRF in a home network; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0388] Fig.15 An example of infrastructure equipment 1500 according to various embodiments is shown. Infrastructure equipment 1500 (or "system 1500") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 1211 and / or AP 1206 shown and described previously), an application server 1230, and / or any other element / device discussed herein. In other examples, system 1500 can be implemented in or by a UE.

[0389] System 1500 includes: application circuit 1505, baseband circuit 1510, one or more radio front end modules (RFEM) 1515, memory circuit 1520, power management integrated circuit (PMIC) 1525, power tee circuit 1530, network controller circuit 1535, network interface connector 1540, satellite positioning circuit 1545 and user interface 1550. In some embodiments, device 1500 may include additional elements, such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the following components may be included in more than one device. For example, the circuit may be included separately in more than one device for CRAN, vBBU or other similar implementations.

[0390] The application circuit 1505 includes, for example, but not limited to, one or more processors (or processor cores), cache memory and one or more low dropout regulators (LDO), an interrupt controller, a serial interface such as SPI, I2C or a general programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, a general input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC) or similar products, a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of the application circuit 1505 may be coupled to or may include a memory / storage element, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 1500. In some implementations, the memory / storage element can be an on-chip memory circuit that can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0391] The processor of the application circuit 1505 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 1505 may include or may be a dedicated processor / controller for operating in accordance with various embodiments herein. As an example, the processor of the application circuit 1505 may include one or more Apple processors, Intel processors, or other processors. or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium(TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, system 1500 may not utilize application circuit 1505, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0392] In some implementations, the application circuit 1505 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), and the like; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), and the like; ASICs, such as structured ASICs, and the like; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of the application circuit 1505 may include logic blocks or logic architectures, as well as other interconnected resources that may be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such an embodiment, the circuitry of application circuit 1505 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in a lookup table (LUT), etc.

[0393] Baseband circuit 1510 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Fig.17 The various hardware electronic components of baseband circuit 1510 are discussed.

[0394] User interface circuitry 1550 may include one or more user interfaces designed to enable a user to interact with system 1500 or a peripheral component interface designed to enable a peripheral component to interact with system 1500. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0395] The radio front end module (RFEM) 1515 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Fig.17 Antenna array 17111), and RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 1515 combining both millimeter wave antennas and sub-millimeter waves.

[0396] The memory circuit 1520 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), and a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 1520 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0397] The PMIC 1525 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 1530 may provide electrical power extracted from a network cable to provide both power and data connections for the infrastructure equipment 1500 using a single cable.

[0398] The network controller circuit 1535 may provide a connection to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 1500 via a network interface connector 1540, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 1535 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some specific implementations, the network controller circuit 1535 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0399] The positioning circuit 1545 includes circuits for receiving and decoding signals transmitted / broadcasted by the positioning network of the global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc. for navigation), etc. The positioning circuit 1545 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 1545 may include a micro technology (micro PNT) IC for positioning, navigation, and timing, which uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 1545 may also be part of or interact with the baseband circuit 1510 and / or RFEM 1515 to communicate with nodes and components of the positioning network. The positioning circuit 1545 may also provide location data and / or time data to the application circuit 1505, which may use the data to synchronize operations with various infrastructures (e.g., RAN node 1211, etc.), etc.

[0400] Fig.15 The components shown can communicate with each other using interface circuits that can include any number of bus and / or interconnect (IX) technologies, such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX can be a proprietary bus, for example, used in a SoC-based system. Other bus / IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, etc.

[0401] Fig.16 An example of a platform 1600 (or "device 1600") according to various embodiments is shown. In an embodiment, the computer platform 1600 may be suitable for use as a UE 1201, 1301, 1401, an application server 1230, and / or any other element / device discussed herein. The platform 1600 may include any combination of components shown in the example. The components of the platform 1600 may be implemented as an integrated circuit (IC), part of an IC, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 1600, or as components otherwise incorporated within the chassis of a larger system. Fig.16The block diagram is intended to show a high-level view of the components of computer platform 1600. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0402] The application circuit 1605 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of an LDO, an interrupt controller, a serial interface (such as SPI), I2C or a general programmable serial interface module, an RTC, a timer-counter (including an interval timer and a watchdog timer), a general I / O, a memory card controller (such as an SDMMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 1605 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 1600. In some specific implementations, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0403] The processor of the application circuit 1505 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit 1505 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0404] As an example, the processor of the application circuit 1605 may include Inc's A series processors, based on Architecture TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 1605 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 1605 can be part of a system on a chip (SoC), in which the application circuit 1605 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0405] Additionally or alternatively, the application circuit 1605 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 1605 may include logic blocks or logic structures, and other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 1605 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in look-up tables (LUTs), etc.

[0406] Baseband circuit 1610 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Fig.17 The various hardware electronic components of baseband circuit 1610 are discussed.

[0407] The RFEM 1615 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Fig.17 Antenna array 17111), and RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 1615 combining both millimeter wave antennas and sub-millimeter waves.

[0408] The memory circuit 1620 may include any number and type of memory devices for providing a quantitative system memory. For example, the memory circuit 1620 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 1620 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 1620 may be implemented as one or more of a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP), or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 1620 may be an on-chip memory or register associated with the application circuit 1605. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 1620 may include one or more mass storage devices, which may include, among others, a solid state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 1600 may be combined with a computer system obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0409] Removable memory circuitry 1623 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 1600. These portable data storage devices may be used for mass storage, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0410] The platform 1600 may further include an interface circuit (not shown) for connecting external devices to the platform 1600. External devices connected to the platform 1600 via the interface circuit include a sensor circuit 1621 and an electromechanical component (EMC) 1622, and a removable memory device coupled to a removable memory circuit 1623.

[0411] Sensor circuitry 1621 includes a device sensor, module, or subsystem that is intended to detect events or changes in its environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, gyroscope, and / or magnetometer; a microelectromechanical system (MEMS) or nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0412] EMC 1622 includes devices, modules or subsystems that are intended to enable platform 1600 to change its state, position and / or orientation or to move or control mechanisms or (sub) systems. In addition, EMC 1622 can be configured to generate messages / signaling and send messages / signaling to other components of platform 1600 to indicate the current state of EMC 1622. EMC 1622 includes one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components. In an embodiment, platform 1600 is configured to operate one or more EMC 1622 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients.

[0413] In some specific implementations, the interface circuit may connect the platform 1600 to the positioning circuit 1645. The positioning circuit 1645 includes a circuit for receiving and decoding signals transmitted / broadcasted by the positioning network of the GNSS. Examples of navigation satellite constellations (or GNSS) may include the GPS of the United States, the GLONASS of Russia, the Galileo system of the European Union, the Beidou navigation satellite system of China, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, QZSS of Japan, DORIS of France, etc.), etc. The positioning circuit 1645 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. that facilitate OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 1645 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 1645 may also be part of the baseband circuit 1510 and / or the RFEM 1615 or interact with it to communicate with nodes and components of the positioning network. Positioning circuitry 1645 may also provide position data and / or time data to application circuitry 1605, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0414] In some implementations, the interface circuit may connect the platform 1600 with a near field communication (NFC) circuit 1640. The NFC circuit 1640 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, wherein magnetic field induction is used to enable communication between the NFC circuit 1640 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 1600. The NFC circuit 1640 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 1640 by executing an NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 1640, or initiate data transfer between the NFC circuit 1640 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) proximate to the platform 1600.

[0415] The driver circuit 1646 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 1600. The driver circuit 1646 may include various drivers to allow other components of the platform 1600 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 1600. For example, the driver circuit 1646 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 1600, a sensor driver for obtaining sensor readings of the sensor circuit 1621 and controlling and allowing access to the sensor circuit 1621, an EMC driver for obtaining an actuator position of the EMC 1622 and / or controlling and allowing access to the EMC 1622, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0416] A power management integrated circuit (PMIC) 1625 (also referred to as “power management circuit 1625”) may manage power provided to various components of the platform 1600. Specifically, the PMIC 1625 may control power selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuit 1610. When the platform 1600 is capable of being powered by a battery 1630, for example, when the device is included in UE 1201, 1301, 1401, the PMIC 1625 may be generally included.

[0417] In some embodiments, the PMIC 1625 may control or otherwise be part of various power saving mechanisms of the platform 1600. For example, if the platform 1600 is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 1600 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 1600 may transition to the RRC_Idle state, in which the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 1600 enters a very low power state and performs paging, in which the device wakes up again periodically to listen to the network and then powers off again. The platform 1600 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0418] The battery 1630 can power the platform 1600, but in some examples, the platform 1600 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 1630 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in V2X applications, the battery 1630 can be a typical lead-acid car battery.

[0419] In some implementations, the battery 1630 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 1600 to track the state of charge (SoCh) of the battery 1630. The BMS may be used to monitor other parameters of the battery 1630, such as the state of health (SoH) and state of function (SoF) of the battery 1630 to provide fault prediction. The BMS may transmit information about the battery 1630 to the application circuit 1605 or other components of the platform 1600. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 1605 to directly monitor the voltage of the battery 1630 or the current from the battery 1630. The battery parameters may be used to determine actions that the platform 1600 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0420] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 1630. In some examples, the power block XS30 can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 1600. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 1630 and therefore the current required. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0421] The user interface circuit 1650 includes various input / output (I / O) devices present in or connected to the platform 1600, and includes one or more user interfaces designed to implement user interaction with the platform 1600 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 1600. The user interface circuit 1650 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of platform 1600. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, sensor circuitry 1621 may be used as an input device circuit (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as output device circuits (e.g., actuators for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, etc.

[0422] Although not shown, the components of platform 1600 can communicate with each other using a suitable bus or interconnect (IX) technology, which can include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, time-triggered protocol (TTP) systems, FlexRay systems, or any number of other technologies. The bus / IX can be a proprietary bus / IX, for example, used in a SoC-based system. Other bus / IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, etc.

[0423] Fig.17 Exemplary components of a baseband circuit 17110 and a radio front end module (RFEM) 17115 are shown according to various embodiments. The baseband circuit 17110 corresponds to Fig.15 The baseband circuit 1510 and Fig.16 Baseband circuit 1610. RFEM17115 corresponds to Fig.15 RFEM 1515 and Fig.16 RFEM 1615. As shown, RFEM 17115 may include radio frequency (RF) circuit 17106, front end module (FEM) circuit 17108, and antenna array 17111 coupled together at least as shown.

[0424] The baseband circuit 17110 includes circuits and / or control logic components configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuit 17106. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 17110 may include a fast Fourier transform (FFT), precoding, or constellation mapping / demapping function. In some embodiments, the encoding / decoding circuit of the baseband circuit 17110 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments. The baseband circuit 17110 is configured to process the baseband signal received from the receiving signal path of the RF circuit 17106 and generate a baseband signal for the transmitting signal path of the RF circuit 17106. The baseband circuit 17110 is configured to communicate with the application circuit 1505 / 1605 (see Fig.15 and Fig.16 ) are connected to generate and process baseband signals and control the operation of RF circuit 17106. Baseband circuit 17110 can handle various radio control functions.

[0425] The aforementioned circuits and / or control logic components of the baseband circuit 17110 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 17104A, a 4G / LTE baseband processor 17104B, a 5G / NR baseband processor 17104C, or some other baseband processors 17104D for other existing generations, generations under development or generations to be developed in the future (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 17104A-D may be included in a module stored in the memory 17104G and may be executed via a central processing unit (CPU) 17104E. In other embodiments, some or all of the functions of the baseband processors 17104A-17104D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with an appropriate bitstream or logic block stored in a corresponding memory unit. In various embodiments, the memory 17104G may store program code of a real-time OS (RTOS), which, when executed by the CPU 17104E (or other baseband processor), will enable the CPU 17104E (or other baseband processor) to manage resources of the baseband circuit 17110, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-Time Executive (VRTX) provided by Express Provided by ThreadX TM ,Depend on FreeRTOS and REX OS provided by Open Kernel (OK) OKL4 provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 17110 includes one or more audio digital signal processors (DSPs) 17104F. The audio DSP 17104F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0426] In some embodiments, each of processors 17104A-17104E includes a corresponding memory interface to send data to / receive data from memory 17104G. Baseband circuit 17110 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 17110; an interface for sending data to / receiving data from a memory external to the baseband circuit; Figure 15-17 An application circuit interface for sending data to / receiving data from the application circuit 1505 / 1605; Fig.17 RF circuit 17106 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 1625.

[0427] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 17110 includes one or more digital baseband systems, which are coupled to each other and to the CPU subsystem, the audio subsystem and the interface subsystem via an interconnect subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 17110 may include a protocol processing circuit with one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., the radio front end module 17115).

[0428] although Fig.17Not shown, but in some embodiments, the baseband circuit 17110 includes various processing devices (e.g., "multi-protocol baseband processor" or "protocol processing circuit") to operate one or more wireless communication protocols and various processing devices to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuit operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuit 17110 and / or the RF circuit 17106 are part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit may operate LTE protocol entities and / or 5G / NR protocol entities. In a first example, the protocol processing circuit will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuit 17110 and / or the RF circuit 17106 are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In a second example, the protocol processing circuit will operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuit may include one or more memory structures (e.g., 17104G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuit 17110 may also support radio communications of more than one wireless protocol.

[0429] The various hardware elements of the baseband circuit 17110 discussed herein may be implemented as, for example, a solder-in substrate, which includes one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuit 17110 may be appropriately combined in a single chip or a single chipset, or arranged on the same circuit board. In another example, some or all of the components of the baseband circuit 17110 and the RF circuit 17106 may be implemented together, such as, for example, a system on a chip (SOC) or a system-level package (SiP). In another example, some or all of the components of the baseband circuit 17110 may be implemented as a separate SoC coupled to the RF circuit 17106 (or multiple instances of the RF circuit 17106) in communication. In yet another example, some or all of the components of the baseband circuit 17110 and the application circuit 1505 / 1605 may be implemented together as a separate SoC (e.g., a "multi-chip package") mounted to the same circuit board.

[0430] In some embodiments, baseband circuit 17110 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuit 17110 may support communications with E-UTRAN or other WMAN, WLAN, WPAN. Embodiments in which baseband circuit 17110 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0431] RF circuit 17106 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 17106 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 17106 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 17108 and providing baseband signals to baseband circuit 17110. RF circuit 17106 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 17110 and providing RF output signals for transmission to FEM circuit 17108.

[0432] In some embodiments, the receive signal path of the RF circuit 17106 may include a mixer circuit 17106a, an amplifier circuit 17106b, and a filter circuit 17106c. In some embodiments, the transmit signal path of the RF circuit 17106 may include a filter circuit 17106c and a mixer circuit 17106a. The RF circuit 17106 may also include a synthesizer circuit 17106d for synthesizing a frequency used by the mixer circuit 17106a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 17106a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 17108 based on the synthesized frequency provided by the synthesizer circuit 17106d. The amplifier circuit 17106b may be configured to amplify the down-converted signal, and the filter circuit 17106c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 17110 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required. In some embodiments, the mixer circuit 17106a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0433] In some embodiments, mixer circuit 17106a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 17106d to generate an RF output signal for FEM circuit 17108. The baseband signal may be provided by baseband circuit 17110 and may be filtered by filter circuit 17106c.

[0434] In some embodiments, the mixer circuit 17106a of the receive signal path and the mixer circuit 17106a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and quadrature up-conversion, respectively. In some embodiments, the mixer circuit 17106a of the receive signal path and the mixer circuit 17106a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 17106a of the receive signal path and the mixer circuit 17106a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 17106a of the receive signal path and the mixer circuit 17106a of the transmit signal path may be configured for superheterodyne operation.

[0435] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 17106 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 17110 may include a digital baseband interface to communicate with the RF circuit 17106.

[0436] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0437] In some embodiments, synthesizer circuit 17106d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 17106d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0438] Synthesizer circuit 17106d may be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit 17106a of RF circuit 17106. In some embodiments, synthesizer circuit 17106d may be a fractional-N / N+1 synthesizer.

[0439] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. The divider control input may be provided by baseband circuit 17110 or application circuit 1505 / 1605 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuit 1505 / 1605.

[0440] The synthesizer circuit 17106d of the RF circuit 17106 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0441] In some embodiments, the synthesizer circuit 17106d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 17106 can include an IQ / polarity converter.

[0442] The FEM circuitry 17108 may include a receive signal path that may include circuitry configured to operate on RF signals received from the antenna array 17111, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 17106 for further processing. The FEM circuitry 17108 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 17106 for transmission by one or more antenna elements in the antenna array 17111. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 17106, only in the FEM circuitry 17108, or in both the RF circuitry 17106 and the FEM circuitry 17108.

[0443] In some embodiments, the FEM circuit 17108 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 17108 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 17108 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 17106). The transmit signal path of the FEM circuit 17108 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by the RF circuit 17106), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 17111.

[0444] The antenna array 17111 includes one or more antenna elements, each of which is configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 17110 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of the antenna array 17111 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed into a variety of arrangements as known and / or discussed herein. The antenna array 17111 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 17111 may be formed into a patch of metal foil (e.g., a patch antenna) of various shapes, and may be coupled to the RF circuit 17106 and / or the FEM circuit 17108 using a metal transmission line or the like.

[0445] The processor of the application circuit 1505 / 1605 and the processor of the baseband circuit 17110 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 17110 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, and the processor of the application circuit 1505 / 1605 can use the data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include a PHY layer of a UE / RAN node, which will be described in further detail below.

[0446] Fig.18 Various protocol functions that may be implemented in a wireless communication device according to some embodiments are shown. Specifically, Fig.18An arrangement 1800 is included to show the interconnection between various protocol layers / entities. Various protocol layers / entities operating in conjunction with 5G / NR system standards and LTE system standards are provided. Fig.18 The following description, but Fig.18 Some or all aspects of the invention may also be applicable to other wireless communication network systems.

[0447] In addition to other higher layer functions not shown, the protocol layers of arrangement 1800 may also include one or more of PHY 1810, MAC 1820, RLC 1830, PDCP 1840, SDAP 1847, RRC 1855, and NAS layer 1857. These protocol layers may include one or more service access points (e.g., Fig.18 Items 1859, 1856, 1850, 1849, 1845, 1835, 1825 and 1815).

[0448] PHY 1810 can send and receive physical layer signals 1805, which can be received or sent from one or more other communication devices to one or more other communication devices. Physical layer signals 1805 may include one or more physical channels, such as those discussed herein. PHY 1810 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and switching purposes) and other measurements used by higher layers (such as, RRC1855). PHY 1810 may also further perform error detection on transmission channels, forward error correction (FEC) encoding / decoding of transmission channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels and MIMO antenna processing. In an embodiment, an instance of PHY 1810 may process a request from an instance of MAC 1820 and provide an indication thereof via one or more PHY-SAP 1815. According to some embodiments, the request and indication transmitted via PHY-SAP 1815 may include one or more transmission channels.

[0449] An instance of MAC 1820 may process requests from an instance of RLC 1830 and provide indications thereto via one or more MAC-SAPs 1825. These requests and indications transmitted via MAC-SAP 1825 may include one or more logical channels. MAC 1820 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 1810 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 1810 via transport channels to one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0450] An instance of RLC 1830 may process requests from an instance of PDCP 1840 and provide indications thereto via one or more radio link control service access points (RLC-SAPs) 1835. These requests and indications transmitted via RLC-SAPs 1835 may include one or more logical channels. RLC 1830 may operate in a variety of operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 1830 may perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 1830 may also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0451] An instance of PDCP 1840 may process requests from an instance of RRC 1855 and / or an instance of SDAP 1847 and provide indications thereto via one or more Packet Data Convergence Protocol Service Points (PDCP-SAPs) 1845. These requests and indications transmitted via PDCP-SAPs 1845 may include one or more radio bearers. PDCP 1840 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-order delivery of upper layer PDUs when lower layers are reestablished, eliminate duplication of lower layer SDUs when lower layers are reestablished for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0452] An instance of SDAP 1847 may process requests from one or more higher layer protocol entities and provide instructions thereto via one or more SDAP-SAPs 1849. These requests and instructions transmitted via SDAP-SAPs 1849 may include one or more QoS flows. SDAP 1847 may map QoS flows to DRBs and vice versa, and may also mark QFIs in DL and UL packets. A single SDAP entity 1847 may be configured for a separate PDU session. In the UL direction, NG-RAN 1210 may control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, SDAP 1847 of UE 1201 may monitor the QFI of DL packets for each DRB, and may apply the same mapping to packets flowing in the UL direction. For DRBs, SDAP 1847 of UE 1201 may map UL packets belonging to a QoS flow corresponding to the QoS flow ID and PDU session observed in the DL packets of the DRB. To implement reflective mapping, NG-RAN 1410 may mark DL packets with a QoS flow ID over the Uu interface. Explicit mapping may involve RRC 1855 configuring SDAP 1847 with explicit mapping rules for QoS flows to DRBs, which may be stored and followed by SDAP 1847. In an embodiment, SDAP 1847 may be used only in NR implementations and may not be used in LTE implementations.

[0453] The RRC 1855 may configure aspects of one or more protocol layers, which may include one or more instances of PHY 1810, MAC 1820, RLC 1830, PDCP 1840, and SDAP 1847, via one or more Management Service Access Points (M-SAPs). In an embodiment, an instance of the RRC 1855 may process requests from one or more NAS entities 1857 and provide instructions thereto via one or more RRC-SAPs 1856. The main services and functions of the RRC 1855 may include broadcasting of system information (e.g., included in a MIB or SIB related to NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of an RRC connection between the UE 1201 and the RAN 1210 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.

[0454] NAS 1857 may form the highest layer of the control plane between UE 1201 and AMF 1421. NAS 1857 may support mobility and session management procedures of UE 1201 to establish and maintain an IP connection between UE 1201 and P-GW in the LTE system.

[0455] According to various embodiments, one or more protocol entities of arrangement 1800 may be implemented in UE 1201, RAN node 1211, AMF 1421 in NR implementation or MME 1321 in LTE implementation, UPF 1402 in NR implementation or S-GW 1322 and P-GW 1323 in LTE implementation, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of UE 1201, gNB 1211, AMF 1421, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using services of corresponding lower layer protocol entities to perform such communication). In some embodiments, the gNB-CU of gNB 1211 may host the gNB's RRC 1855, SDAP 1847, and PDCP 1840 that control operations of one or more gNB-DUs, and the gNB-DUs of gNB 1211 may each host the RLC 1830, MAC 1820, and PHY 1810 of gNB 1211.

[0456] In a first example, the control plane protocol stack may include, in order from the highest layer to the lowest layer, NAS 1857, RRC 1855, PDCP 1840, RLC 1830, MAC 1820, and PHY 1810. In this example, an upper layer 1860 may be built on top of NAS 1857, which includes an IP layer 1861, SCTP 1862, and an application layer signaling protocol (AP) 1863.

[0457] In a NR specific implementation, AP 1863 can be an NG application protocol layer (NGAP or NG-AP) 1863 for the NG interface 1213 defined between the NG-RAN node 1211 and the AMF 1421, or AP 1863 can be an Xn application protocol layer (XnAP or Xn-AP) 1863 for the Xn interface 1212 defined between two or more RAN nodes 1211.

[0458] The NG-AP 1863 may support the functionality of the NG interface 1213 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN point 1211 and the AMF 1421. The NG-AP 1863 services may include two groups: UE-associated services (e.g., services related to the UE 1201) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 1211 and the AMF 1421). These services may include the following functions, which include but are not limited to: a paging function for sending a paging request to the NG-RAN node 1211 involved in a specific paging area; a UE context management function for allowing the AMF 1421 to establish, modify and / or release the UE context in the AMF 1421 and the NG-RAN node 1211; a mobility function for the UE 1201 in ECM-connected mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signaling transport function for transmitting or rerouting NAS messages between the UE 1201 and the AMF 1421; a NAS signaling transport function for determining whether the AMF 1421 and the UE 1201; an NG interface management function for setting up an NG interface and monitoring errors through the NG interface; a warning message sending function for providing a means for transmitting a warning message via the NG interface or cancelling an ongoing warning message broadcast; a configuration transmission function for requesting and transmitting RAN configuration information (e.g., SON information, performance measurement (PM) data, etc.) between two RAN nodes 1211 via CN1220; and / or other similar functions.

[0459] XnAP 1863 may support the functions of Xn interface 1212 and may include XnAP basic mobility procedures and XnAP global procedures. XnAP basic mobility procedures may include procedures for handling UE mobility within NG RAN 1211 (or E-UTRAN 1310), such as handover preparation and cancellation procedures, SN state transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, procedures related to dual connectivity, etc. XnAP global procedures may include procedures unrelated to a specific UE 1201, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, etc.

[0460] In an LTE specific implementation, AP 1863 can be an S1 application protocol layer (S1-AP) 1863 for an S1 interface 1213 defined between an E-UTRAN node 1211 and an MME, or AP 1863 can be an X2 application protocol layer (X2AP or X2-AP) 1863 for an X2 interface 1212 defined between two or more E-UTRAN nodes 1211.

[0461] The S1 application protocol layer (S1-AP) 1863 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be an interaction unit between the E-UTRAN node 1211 and the MME 1321 within the LTE CN 1220. The S1-AP 1863 services may include two groups: UE-associated services and non-UE-associated services. The functions performed by these services include, but are not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.

[0462] The X2AP 1863 may support the functions of the X2 interface 1212 and may include an X2AP basic mobility procedure and an X2AP global procedure. The X2AP basic mobility procedure may include a procedure for handling UE mobility within the E-UTRAN 1220, such as a handover preparation and cancellation procedure, an SN state transfer procedure, a UE context retrieval and a UE context release procedure, a RAN paging procedure, a procedure related to dual connectivity, etc. The X2AP global procedure may include a procedure that is not related to a specific UE 1201, such as an X2 interface setup and reset procedure, a load indication procedure, an error indication procedure, a cell activation procedure, etc.

[0463] The SCTP layer (alternatively referred to as the SCTP / IP layer) 1862 may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). SCTP 1862 may ensure reliable delivery of signaling messages between the RAN node 1211 and the AMF 1421 / MME 1321 based in part on the IP protocol supported by IP 1861. The Internet Protocol layer (IP) 1861 may be used to perform packet addressing and routing functions. In some implementations, the IP layer 1861 may deliver and transmit PDUs using point-to-point transport. In this regard, the RAN node 1211 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0464] In a second example, the user plane protocol stack may include SDAP 1847, PDCP 1840, RLC 1830, MAC 1820, and PHY 1810 in order from the highest layer to the lowest layer. The user plane protocol stack may be used for communication between UE 1201, RAN node 1211, and UPF 1402 in NR implementation, or communication between S-GW 1322 and P-GW 1323 in LTE implementation. In this example, the upper layer 1851 may be built on top of SDAP 1847 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 1852, a general packet radio service (GPRS) tunneling protocol for a user plane layer (GTP-U) 1853, and a user plane PDU layer (UP PDU) 1863.

[0465] The transport network layer 1854 (also referred to as the "transport layer") may be built on top of the IP transport, and the GTP-U 1853 may be used on top of the UDP / IP layer 1852 (including the UDP layer and the IP layer) to carry the user plane PDU (UP-PDU). The IP layer (also referred to as the "Internet layer") may be used to perform packet addressing and routing functions. The IP layer may assign IP addresses to user data packets, for example, in any of the IPv4, IPv6, or PPP formats.

[0466] GTP-U 1853 may be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data may be packets in any of the IPv4, IPv6, or PPP formats. UDP / IP 1852 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 1211 and the S-GW 1322 may utilize the S1-U interface to exchange user plane data via a protocol stack including an L1 layer (e.g., PHY 1810), an L2 layer (e.g., MAC 1820, RLC 1830, PDCP 1840, and / or SDAP 1847), a UDP / IP layer 1852, and GRP-U 1853. S-GW 1322 and P-GW 1323 may utilize an S5 / S8a interface to exchange user plane data via a protocol stack including an L1 layer, an L2 layer, a UDP / IP layer 1852, and a GTP-U 1853. As previously discussed, the NAS protocol may support the mobility and session management procedures of UE 1201 to establish and maintain an IP connection between UE 1201 and P-GW 1323.

[0467] In addition, despite Fig.18Not shown, but an application layer may exist above the AP 1863 and / or transport network layer 1854. The application layer may be a layer where a user of the UE 1201, RAN node 1211, or other network element interacts with a software application, for example, executed by the application circuit 1505 or the application circuit 1605, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system (such as the baseband circuit 17110) of the UE 1201 or RAN node 1211. In some specific implementations, the IP layer and / or the application layer may provide the same or similar functionality as layers 5 to 7 of the open system interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

[0468] Fig.19 Components of a core network according to various embodiments are shown. The components of CN 1320 may be implemented in one physical node or separate physical nodes, including components that read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In an embodiment, the components of CN 1420 may be implemented in the same or similar manner as discussed herein with respect to the components of CN 1320. In some embodiments, NFV is used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 1320 may be referred to as a network slice 1901, and each logical instance of CN 1320 may provide specific network functions and network characteristics. A logical instance of a portion of CN 1320 may be referred to as a network sub-slice 1902 (e.g., network sub-slice 1902 is shown as including P-GW 1323 and PCRF 1326).

[0469] As used herein, the terms "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the concrete occurrence of an object, which may occur, for example, during the execution of program code. A network instance may refer to information identifying a domain, which may be used for traffic detection and routing in different IP domains or in the case of overlapping IP addresses. A network slice instance may refer to a set of network function (NF) instances and the resources (e.g., computing, storage, and network resources) required to deploy a network slice.

[0470] Compared to 5G systems (see e.g. Fig.14), a network slice always includes a RAN part and a CN part. Support for network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. The network can implement different network slices by scheduling and also by providing different L1 / L2 configurations. If the UE 1401 has been provided by NAS, it provides auxiliary information for network slice selection in the appropriate RRC message. Although the network can support a large number of slices, the UE does not need to support more than 8 slices at the same time.

[0471] The network slice may include the CN 1420 control plane and user plane NF, the NG-RAN 1410 in the serving PLMN, and the N3IWF function in the serving PLMN. Each network slice may have a different S-NSSAI and / or may have a different SST. The NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by the S-NSSAI. The network slice may differ in terms of supported features and network function optimizations, and / or multiple network slice instances may deliver the same service / feature, but differ for different UE 1401 groups (e.g., enterprise users). For example, each network slice may deliver different committed services and / or may be dedicated to a specific customer or enterprise. In this example, each network slice may have a different S-NSSAI with the same SST but with a different slice differentiator. In addition, a single UE may be served simultaneously by one or more network slice instances via a 5G AN and be associated with eight different S-NSSAIs. In addition, an AMF 1421 instance serving a single UE 1401 may belong to each network slice instance serving the UE.

[0472] Network slicing in NG-RAN 1410 involves RAN slice sensing. RAN slice sensing includes differentiated processing of traffic for different network slices that have been pre-configured. Slice sensing in NG-RAN 1410 is introduced at the PDU session level by indicating the S-NSSAI corresponding to the PDU session in all signaling including PDU session resource information. How NG-RAN 1410 supports slices enabled in terms of NG-RAN functions (e.g., a set of network functions including each slice) is implementation-dependent. NG-RAN 1410 selects the RAN portion of the network slice using auxiliary information provided by UE 1401 or 5GC 1420, which explicitly identifies one or more network slices in the pre-configured network slices in the PLMN. NG-RAN 1410 also supports resource management and policy enforcement between slices according to SLA. A single NG-RAN node can support multiple slices, and NG-RAN 1410 can also apply appropriate RRM policies for SLAs in appropriate locations to each supported slice. NG-RAN 1410 can also support QoS differences within a slice.

[0473] If available, the NG-RAN 1410 may also use UE assistance information to select an AMF 1421 during the initial attach. The NG-RAN 1410 routes the initial NAS to the AMF 1421 using the assistance information. If the NG-RAN 1410 cannot select an AMF 1421 using the assistance information, or the UE 1401 does not provide any such information, the NG-RAN 1410 sends the NAS signaling to a default AMF 1421, which may be in the AMF 1421 pool. For subsequent access, the UE 1401 provides the temperature ID assigned to the UE 1401 by the 5GC 1420 to enable the NG-RAN 1410 to route the NAS message to the appropriate AMF 1421, as long as the temperature ID is valid. The NG-RAN 1410 senses and can reach the AMF 1421 associated with the temperature ID. Otherwise, the method for initial attach applies.

[0474] The NG-RAN 1410 supports resource isolation between slices. NG-RAN 1410 resource isolation can be achieved through RRM policies and protection mechanisms that should avoid starvation of shared resources if one slice disrupts the service level agreement of another slice. In some implementations, NG-RAN 1410 resources can be fully specified to a slice. How the NG-RAN 1410 supports resource isolation depends on the specific implementation.

[0475] Some slices may be only partially available in the network. Sensing in the NG-RAN 1410 of supported slices in its neighboring cells may be beneficial for inter-frequency mobility in connected mode. Slice availability may not change within the registration area of ​​the UE. The NG-RAN 1410 and 5GC 1420 are responsible for handling service requests for slices that are available or unavailable in a given area. The admission or denial of access to a slice may depend on factors such as support for the slice, availability of resources, and support of the requested service by the NG-RAN 1410.

[0476] UE 1401 may be associated with multiple network slices simultaneously. In the case where UE 1401 is associated with multiple slices simultaneously, only one signaling connection is maintained and for intra-frequency cell reselection, UE 1401 attempts to camp on the best cell. For inter-frequency cell reselection, dedicated priorities may be used to control the frequency on which UE 1401 camps. 5GC 1420 is used to verify that UE 1401 has the right to access the network slice. Prior to receiving the initial context setup request message, NG-RAN 1410 may be allowed to apply some temporary / local policies based on sensing of the specific slice that UE 1401 requests access to. During the initial context setup, NG-RAN 1410 is informed of the slice for which resources are being requested.

[0477] The NFV architecture and infrastructure can be used to virtualize one or more NFs onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system can be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0478] Fig. 20 2006, VNF 2008, EM 2010, NFVO 2012, and NM 2014.

[0479] VIM 2002 manages resources of NFVI 2004. NFVI 2004 may include physical or virtual resources and applications (including hypervisors) for executing system 2000. VIM 2002 may utilize NFVI 2004 to manage the lifecycle of virtual resources (e.g., creation, maintenance, and removal of VMs associated with one or more physical resources), track VM instances, track performance, failures, and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0480] VNFM 2006 can manage VNF 2008. VNF 2008 can be used to perform EPC components / functions. VNFM 2006 can manage the life cycle of VNF 2008 and track the performance, failures, and security of VNF 2008 in virtual aspects. EM 2010 can track the performance, failures, and security of VNF 2008 in functional aspects. Tracking data from VNFM 2006 and EM 2010 can include, for example, PM data used by VIM 2002 or NFVI 2004. VNFM 2006 and EM 2010 can both scale up / down the number of VNFs of system 2000.

[0481] NFVO 2012 can coordinate, authorize, release, and engage resources of NFVI 2004 to provide requested services (e.g., execute EPC functions, components, or slices). NM 2014 can provide an end-user functional grouping responsible for network management, which may include network elements with VNFs, non-virtualized network functions, or both (management of VNFs can occur via EM 2010).

[0482] Fig.21 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig.21 A schematic diagram of hardware resources 2100 is shown, including one or more processors (or processor cores) 2110, one or more memory / storage devices 2120, and one or more communication resources 2130, each of which may be communicatively coupled via a bus 2140. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 2102 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 2100.

[0483] Processor 2110 may include, for example, processor 2112 and processor 2114. Processor 2110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0484] The memory / storage device 2120 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 2120 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0485] The communication resources 2130 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 2104 or one or more databases 2106 via the network 2108. For example, the communication resources 2130 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0486] The instructions 2150 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 2110 to perform any one or more of the methods discussed herein. The instructions 2150 may reside in whole or in part in at least one of the processors 2110 (e.g., in a cache memory of the processor), the memory / storage device 2120, or any suitable combination thereof. In addition, any portion of the instructions 2150 may be transferred to the hardware resources 2100 from any combination of the peripheral device 2104 or the database 2106. Therefore, the memory of the processor 2110, the memory / storage device 2120, the peripheral device 2104, and the database 2106 are examples of computer-readable and machine-readable media.

[0487] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments shown in the example section below.

[0488] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0489] The embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0490] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system is caused to perform a method, such as any one of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein or any combination of such subsets.

[0491] In some embodiments, a device (e.g., UE 106) may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any of the method implementations described herein, or any combination of such subsets). The device may be implemented in any of various forms.

[0492] By interpreting each message / signal X received by a user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any of the methods for operating a UE described herein may become the basis for the corresponding method for operating a base station.

[0493] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A network entity, comprising: Memory; at least one communication interface; as well as one or more processors communicatively coupled to the memory and the at least one communication interface; The one or more processors are configured to cause the network entity to perform the following operations: receiving, from a service management and orchestration framework SMOFW for the network, a performance target for a mobility robustness optimization (MRO) function of the network; receiving handover related performance measurements from an open radio access network, O-RAN, distributed unit, O-DU, of said network; as well as One or more actions are performed based on an analysis of the switching-related performance measurements relative to the performance target of the MRO function, wherein the analysis of the switching-related performance measurements includes comparing the MRO function performance with the performance target of the MRO function, wherein the MRO function performance is based on the switching-related performance measurements.

2. The network entity according to claim 1, Wherein the one or more processors are further configured to receive a range of switching parameters from the SMOFW of the network.

3. The network entity according to claim 1, The one or more functions include at least one of the following: Sending updated handover parameters to the O-DU; Determining to change the virtualized resource based on the network entity, sending a request to the SMOFW to change the virtualized resource; or A notification is received from the SMOFW indicating that the infrastructure and management framework IMFW has changed the virtualized resource.

4. The network entity according to claim 1, wherein the one or more processors are further configured to: receiving cell load measurements from the O-DU or an O-RAN centralised unit O-CU; and Based on the cell load measurement, request the SMOFW to change virtualized resources or request the O-DU to update switching parameters.

5. The network entity according to claim 4, The cell load measurement includes at least one of the following: Radio resources; the transport network load on one or more of the F1 interface, the Xn interface, or the E2 interface; or Virtualized resource usage of network functions.

6. The network entity according to claim 4, wherein the one or more processors are further configured to: At least one load balancing optimization (LBO) action is performed based on the analysis of the cell load measurement, wherein the at least one LBO action comprises requesting the O-DU or the O-CU to update a user equipment (UE) selection or cell selection parameter.

7. The network entity according to claim 1, The network entity comprises a near real-time intelligent RAN controller.

8. An apparatus for communication, comprising: Memory; as well as at least one processor in communication with the memory, wherein the at least one processor is configured to: Receive switching related parameters from the service management and orchestration framework SMOFW; receiving handover related performance measurements from an open radio access network O-RAN distributed unit O-DU or an O-RAN central unit O-CU; generating one or more requests, including a request for the O-DU to update a switching parameter or a request for the SMOFW to update a virtualized resource; as well as The handover related performance is analyzed by comparing the performance of the mobility robustness optimization MRO function with the performance target of the MRO function received from SMOFW.

9. The device according to claim 8, Wherein the request is generated based at least in part on the handover-related performance measurement.

10. The device according to claim 8, wherein the at least one processor is further configured to: receiving a cell load measurement from an open radio access network O-RAN distributed unit O-DU or an O-RAN central unit O-CU; analyzing the cell load measurements; and Based on the analysis, at least one load balancing optimization (LBO) action is performed.

11. The device according to claim 10, Wherein the at least one LBO action comprises at least one of the following: Requesting the O-DU and / or the O-CU to update one or more of a user equipment UE selection parameter, a cell selection parameter or a handover parameter; Request the Service Management and Orchestration Framework SMOFW to change virtualized resources; or A notification is received from the SMOFW indicating that the infrastructure management framework IMFW has changed a virtualized resource.

12. The device according to claim 8, wherein the at least one processor is further configured to: Setting performance targets for the distributed LBO, or D-LBO, function; activating the D-LBO function; and Receiving performance measurements to evaluate the D-LBO, wherein the performance measurements include one or more of: Multiple RRC connections are established; Multiple RRC connections released; Multiple exception releases; Multiple switch failures; or Multiple calls dropped.

Images