open radio access network near-real-time radio access network intelligent controller

Abstract

A first network node located in a communication network comprising a second network node can receive information associated with a communication device connected to the second network node. The first network node can further determine a configuration of the second network node relative to the communication device based on the information. The first network node can further transmit an indication of the configuration to the second network node via an intent-based interface.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communication systems, and more particularly, to Open Radio Access Network (“ORAN”) near-Real-Time (“RT”) Radio Access Network Intelligent Controller (“RIC”). BACKGROUND

[0002] Figure 1 An example of a Fifth Generation (“5G”) network is shown, including a network node 120 (e.g., a 5G base station (“gNB”)) and a plurality of communication apparatuses 110 (also known as user equipment (“UE”)).

[0003] In some examples, an operator configures radio access network (“RAN”) functionality for a set of UEs (or users) to use, which are identified by a Quality of Service Class Indicator (“QCI”) or a Service Profile Identifier (“SPID”). SUMMARY

[0004] According to some embodiments, a method of operating a first network node in a communication network including a second network node is provided. The method can include receiving information associated with a communication apparatus connected to the second network node. The method can further include determining a configuration of the second network node relative to the communication apparatus based on the information. The method can further include transmitting an indication of the configuration to the second network node via an intent-based interface.

[0005] According to other embodiments, a method of operating a second network node in a communication network including a first network node is provided. The method can include communicating with a communication apparatus based on a first configuration. The method can further include receiving an indication of a second configuration from the first network node via an intent-based interface. The method can further include, in response to receiving the indication of the second configuration, communicating with the communication apparatus based on the second configuration.

[0006] According to other embodiments, a first network node, a second network node, a computer program, and / or a computer program product for performing one or more of the above methods are provided.

[0007] The various embodiments described herein allow an operator to perform RAN functionality-agnostic policy guidance and directly guide additional functionality to be applied to communications with a communication apparatus. As a result, the operator can enable faster innovation by experimenting with configurations of individual communication apparatuses to achieve a desired behavior without relying on product update delays. BRIEF DESCRIPTION OF DRAWINGS

[0008] The accompanying drawings, which are incorporated herein by reference to provide further understanding of the disclosure and constitute part of the application, illustrate certain non-limiting embodiments of the inventive concept. The drawings, in which:

[0009] Figure 1 is a schematic diagram illustrating an example of a Fifth Generation (“5G”) network;

[0010] Figure 2 is a block diagram illustrating an example of a 5G network configured to provide Open Radio Access Network (“ORAN”) near-Real-Time (“RT”) Radio Access Network Intelligent Controller (“RIC”) functional control, in accordance with some embodiments;

[0011] Figure 3 is a block diagram illustrating an example of a communication device, in accordance with some embodiments;

[0012] Figure 4 is a block diagram illustrating an example of a Radio Access Network (“RAN”) node, in accordance with some embodiments;

[0013] Figure 5 is a block diagram illustrating an example of a Core Network (“CN”) node, in accordance with some embodiments;

[0014] Figure 6 is a flow diagram illustrating an example of operations performed by a first network node, in accordance with some embodiments;

[0015] Figure 7 is a flow diagram illustrating an example of operations performed by a second network node, in accordance with some embodiments;

[0016] Figure 8 is a block diagram of a wireless network, in accordance with some embodiments;

[0017] Figure 9 is a block diagram of a user equipment, in accordance with some embodiments;

[0018] Figure 10 is a block diagram of a virtualization environment, in accordance with some embodiments;

[0019] Figure 11 is a block diagram of a telecommunication network connected via an intermediate network to a host computer, in accordance with some embodiments;

[0020] Figure 12 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, in accordance with some embodiments;

[0021] Figure 13 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment, in accordance with some embodiments;

[0022] Figure 14 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;

[0023] Figure 15 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;

[0024] Figure 16 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;

[0025] Figure 17 is a block diagram illustrating an example of an ORAN architecture according to some embodiments; and

[0026] Figure 18 is a block diagram illustrating an example of a game strategy according to some embodiments. DETAILED DESCRIPTION

[0027] The present inventive concept will now be described more fully with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are shown. The inventive concept may, however, be implemented in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment can be assumed by default to be present / in use in another embodiment.

[0028] Figure 2An example of a 5G network configured to provide open radio access network (“ORAN”) near-real-time (“RT”) radio access network intelligent controller (“RIC”) functional control is shown in accordance with some embodiments. The 5G network can include a radio access network (“RAN”) node, an operations support system (“OSS”) node 230, and a core network (“CN”) node 240. A management interface (shown here as an O1 interface) can exist between the OSS node 230 and the RAN node 220. An intent-based interface (shown here as an Al interface) can exist between the OSS node 230 and the RAN node 220. The O1 interface is an interface for operations and management (to enable, for example, management of faults, configuration, billing, performance, security, software, and files), and is compatible with the relevant ORAN specification that defines the O1 interface (e.g., a specification defined by the O-RAN Alliance or the Telecom Infrastructure Project). The Al interface is an intent-based interface for configuring intent-based policies. By intent-based, it is meant, for example, that the interface allows configuration of policies independent of the implementation of the policies’ functionality within a particular RAN node. Further, the Al interface is compatible with the relevant ORAN specification that defines the Al interface. The Al interface can additionally include aspects not specified by the ORAN specification.

[0029] The service server 250 can be part of the 5G network or connected to the 5G network via the OSS node 230 and / or the CN node 240. A communication device (here referred to as UE 210) can be connected to the 5G network through the RAN node 220 and can communicate directly with the OSS node 230 and / or the service server 250 (e.g., via a direct logical communication link that is opaque to the RAN node 220).

[0030] Further description of examples of 5G networks is shown in the various figures and descriptions of Figure 17 , which are similar to Figure 2 , which are similar to Figure 17 , which are similar to

[0031] The game server 250 can be part of the 5G network or connected to the 5G network via the OSS node 230 and / or the CN node 240. A communication device, referred to here as the UE 210, can connect to the 5G network through the RAN node 220 and can communicate with the OSS node 230 and / or the service server 250 directly or through the RAN node 220. External data 1760 can be provided to the non-RT RIC 1736 of the OSS node 230.

[0032] The UE 210 can operate a game 1712 and a game platform 1714. The game 1712 can communicate with the non-RT RIC 1736 of the OSS node 230 via the game server 250 and the CN node 240. The game platform 1714 can communicate with the non-RT RIC 1736 via the SMO 1734 of the OSS node 230.

[0033] The RAN node 220 can include a near-RT RIC 1722 and a RAN radio resource manager (“RRM”) 1724. The RAN RRM 1724 can provide RRM data and events to the near-RT RIC 1722. The near-RT RIC 1724 can determine actions, automatically / dynamically control advanced subscriber group handling within the RAN node 220, and control how to react to configured policies.

[0034] The RAN node 220 can perform some actions in near real time, such as beamforming, scheduling, CoMP, and fast spectrum management. The RAN node 220 can perform other actions with a little less in real time, e.g., within 50-200 ms, such as handover decisions, traffic steering (e.g., carriers, dynamic path selection), carrier selection (affinity), QoS resource assignment (e.g., scheduling parameters, PRBs, frequency bands, etc.).

[0035] The SMO 1734 and the non-RT RIC 1736 of the OSS node 230 can perform some actions over larger time scales, e.g., greater than 1 second, such as orchestration, programmability, optimization, analytics, automated management, and SON.

[0036] Figure 18An example is shown of a RAN node 220 with a corresponding near-RT RIC 1810 and feature activation policy 1820. The near-RT RIC 1810 controls, for example, L3 UE access, L3 UE application, RAN area control, RAN logic control, NG2, MAC resource control, L2 UE control, L2 resource control, L2 logic control, ESS, as shown. The near-RT RIC 1810 can also be referred to as a RAN infrastructure controller. The near-RT RIC 1810 1810 can receive as input (e.g., from an OSS node such as the OSS node 230 in FIG. 1) game policies including a connection policy and a boost policy via an Al interface. The connection policy can include an indication of traffic selection carrier status, carrier allocation, and traffic steering. The boost policy can include an indication of a latency value, jitter, jitter intensity, and feature activation policy 1820 (for UL and / or DL). Figure 17

[0037] In an example application of embodiments of the invention, an operator can prefer certain RAN features to be turned on (or off) independently of the intent policies received via the Al interface. For example, to enhance latency for a user(s) for which power limitations are not an issue, the operator can direct that DTX is not turned on for such users independently of (or overriding) any other intent-based policies. Another example feature that the operator can want to control directly in addition to DTX is dual active protocol stack (DAPS). To enhance mobility, the operator can direct that DAPS is activated for a user(s) in the RAN node regardless of what other intent-based policies can be configured in the RAN node.

[0038] Open Radio Access Network (“ORAN”) can include an intent-based interface (e.g., Al interface) between an OSS node and a network node (e.g., RAN node 220), whereby an operator (hereinafter “operator”) of the ORAN can communicate policies to the network node. These policies can direct the behavior of the network node and allow each UE to perform radio access network (“RAN”) functions individually. Thus, communicating these policies does not allow the operator to directly determine the actual functionality that the network node is to use when setting the policies (e.g., by a near-real-time (“RT”) RAN intelligent controller (“RIC”) or other ORAN component), as this is the responsibility of the RAN and near-RT RIC.

[0039] ​In some examples, the operator wants to no longer configure exact functionality for a group of users, as this can be cumbersome. Instead, the operator can want to use a higher level of UE individual policy steering via the Al interface. This can add flexibility of UE and service control and reduce their workload in RAN configuration. However, this can shift significant responsibility to the RAN node to determine how the user should be handled (e.g., which functionality to apply and which configuration to use).

[0040] Furthermore, the operator can lose almost all ability to influence which functionality should be applied. Thus, if the operator has an idea or insight that a certain functionality should be applied, it cannot direct that the functionality should be applied for that user, but instead becomes dependent on the RAN node vendor to perform updates of its product, or the operator must revert to detailed and cumbersome configuration of the entire connection.

[0041] The various embodiments described herein allow for transmission of function control Al policies, whereby the operator can be enabled to point out specific RAN functionality that should be applied for a user. Thus, the operator can complement the overall high level policy steering in order to also pinpoint specific functionality to be applied for a specific UE (or user), if wanted. This can allow the operator to combine both policy steering that is RAN functionality agnostic and direct steering of one or more additional functions that should be applied for one or more UEs. Thus, the operator can innovate and try or achieve wanted behavior more quickly without having to rely on product updates.

[0042] Figure 3is a block diagram illustrating elements of a communication device 300 (also referred to as a mobile terminal, mobile communication terminal, wireless device, wireless communication device, wireless terminal, mobile device, wireless communication terminal, user equipment, UE, user equipment node / terminal / device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. The communication device 300 can be provided. As shown, the communication device 300 can include an antenna 307 and transceiver circuitry 301 (also referred to as a transceiver) including transmitters and receivers configured to provide uplink and downlink radio communications with base station(s) (also referred to as RAN nodes) of a radio access network (RAN). The communication device 300 can also include processing circuitry 303 (also referred to as a processor) coupled to the transceiver circuitry, and memory circuitry 305 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 305 can include computer readable program code that, when executed by the processing circuitry 303, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuitry 303 can be defined to include the memory, such that a separate memory circuitry is not required. The communication device 300 can also include an interface (such as a user interface) coupled with the processing circuitry 303, and / or the communication device UE can be incorporated in a vehicle.

[0043] As discussed herein, operations for the communication device 300 can be performed by the processing circuitry 303 and / or the transceiver circuitry 301. For example, the processing circuitry 303 can control the transceiver circuitry 301 to transmit communications through the transceiver circuitry 301 to a radio access network node (also referred to as a base station) over a radio interface, and / or to receive communications from the RAN node over the radio interface through the transceiver circuitry 301. Moreover, modules can be stored in the memory circuitry 305, and these modules can provide instructions so that when the instructions of the modules are executed by the processing circuitry 303, the processing circuitry 303 performs respective operations.

[0044] Figure 4is a block diagram illustrating elements of a radio access network ("RAN") node 400 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) configured to provide a cellular communication in accordance with embodiments of inventive concepts. As shown, the RAN node 400 can include transceiver circuitry 401 (also referred to as a transceiver) including transmitters and receivers configured to provide uplink and downlink wireless radio communications with mobile terminals. The RAN node 400 can include network interface circuitry 407 (also referred to as a network interface) configured to provide communications with other nodes of the RAN and / or core network CN (e.g., with other base stations). The RAN node 400 can also include processing circuitry 403 (also referred to as a processor) coupled to the transceiver circuitry and memory circuitry 405 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 405 can include computer readable program code that, when executed by the processing circuitry 403, causes the processing circuitry to perform operations in accordance with embodiments disclosed herein. According to other embodiments, the processing circuitry 403 can be defined to include the memory such that a separate memory circuitry is not required.

[0045] As discussed herein, operations of the RAN node 400 can be performed by the processing circuitry 403, the network interface 407, and / or the transceiver 401. For example, the processing circuitry 403 can control the transceiver 401 to transmit downlink communications through the transceiver 401 to one or more mobile terminals UEs over a radio interface and / or to receive uplink communications from one or more mobile terminals UEs over the radio interface through the transceiver 401. Similarly, the processing circuitry 403 can control the network interface 407 to transmit communications to one or more other network nodes over the network interface 407 and / or to receive communications from one or more other network nodes over the network interface. Moreover, modules can be stored in the memory circuitry 405, and these modules can provide instructions so that when the instructions of the modules are executed by the processing circuitry 403, the processing circuitry 403 performs respective operations.

[0046] According to some other embodiments, a network node can be implemented as a core network CN node without a transceiver. In such embodiments, a transmission can be initiated by the network node to a wireless communication device UE so that the transmission is provided to the wireless communication device UE by a network node that includes a transceiver (e.g., by a base station or RAN node). According to embodiments in which the network node is a RAN node that includes a transceiver, initiating the transmission can include transmitting through the transceiver.

[0047] Figure 5is a block diagram illustrating elements of a core network ("CN") node 500 (e.g., an SMF node, an AMF node, an AUSF node, a UDM node, etc.) of a communication network configured to provide cellular communications according to embodiments of inventive concepts. As shown, the CN node 500 can include network interface circuitry 507 (also referred to as a network interface) configured to provide communications with other nodes of the core network and / or RAN. The CN node 500 can also include processing circuitry 503 (also referred to as a processor) coupled to the network interface circuitry, as well as memory circuitry 505 (also referred to as a memory) coupled to the processing circuitry. The memory circuitry 505 can include computer-readable program code that, when executed by the processing circuitry 503, causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuitry 503 can be defined to include the memory, such that a separate memory circuitry is not required.

[0048] As discussed herein, the operations of the CN node 500 can be performed by the processing circuitry 503 and / or the network interface circuitry 507. For example, the processing circuitry 503 can control the network interface circuitry 507 to transmit communications through the network interface circuitry 507 to one or more other network nodes and / or to receive communications through the network interface circuitry from one or more other network nodes. Moreover, modules can be stored in the memory circuitry 505, and these modules can provide instructions so that when the instructions of the modules are executed by the processing circuitry 503, the processing circuitry 503 performs respective operations.

[0049] In some embodiments, an operator can configure a RAN node through another network node by having the other network node transmit configuration information to the RAN node via the Ol interface. In additional or alternative embodiments, the configuration information can include a mapping of functionality control values to certain functionality in the RAN. In some examples, the mapping can include functionality control value 1 mapped to discontinuous reception ("DRX") on, functionality control value 2 mapped to carrier aggregation ("CA") on, functionality control value 3 mapped to packet data convergence protocol ("PDCP") on. In one embodiment, a single functionality control value is used to turn on multiple configuration features. Thus, one-to-one, one-to-many, and / or many-to-many mappings of functionality control values to configuration features can be implemented.

[0050] In additional or alternative embodiments, an operator can configure a RAN node for certain functionality via another network node by having the other network node transmit an indication of the configuration via the Al interface. In additional or alternative embodiments, the indication can include one or more functionality control values that indicate the certain functionality based on a mapping. The indication can further include other Al policies for the certain UE.

[0051] In additional or alternative embodiments, the near-RT RIC of the RAN node can receive indications via the A1 interface and determine specific RAN function configurations (e.g., corresponding to functional control values ​​transmitted via the A1 interface). Additionally, the RAN and near-RT RIC are fully free to apply any other functionalities to satisfy other A1 policies.

[0052] Now refer to Figure 6 The flowchart below discusses the operation of the first network node based on some embodiments of the inventive concept. Figure 6 Described as being used Figure 4 The block diagram structure is implemented for RAN node 400 execution. For example, modules can be stored in... Figure 4 The memory 405 contains these modules, and these modules provide instructions such that when the instructions of the modules are executed by the processing circuit 403, the processing circuit 403 performs the corresponding operation of the flowchart. However, Figure 6 The operations within can be performed by any suitable network node.

[0053] exist Figure 6 In this context, the first network node communicates configuration information with the second network node associated with a specific communication device.

[0054] In block 610, processing circuitry 403 transmits configuration information to a second network node via a management interface through network interface 407. In some embodiments, transmitting configuration information includes transmitting a mapping of multiple functional control values ​​to the functionality of the second network node.

[0055] In block 620, processing circuitry 403 receives information associated with a communication device connected to a second network node via network interface 407. In some embodiments, the information associated with the communication device may include information associated with at least one of the following: the context of the communication device, a Quality of Service (QoS) category identifier associated with the communication device, the characteristics of the service between the communication device and the second network node, and the services provided to the user equipment.

[0056] In additional or alternative embodiments, receiving information associated with the communication device includes receiving a first portion of the information from a service server associated with a service provided to the communication device via a second network node.

[0057] In additional or alternative embodiments, receiving information associated with the communication device includes receiving a second portion of the information from a core network node associated with the second network node.

[0058] In block 630, processing circuit 403 determines the configuration of the second network node relative to the communication device based on the information.

[0059] At block 640, processing circuitry 403 transmits a configuration instruction to a second network node via an intent-based interface through network interface 407. In some embodiments, transmitting the configuration instruction includes transmitting a plurality of functional control values ​​previously provided to the second network node. In additional or alternative embodiments, the instruction may include a configuration strategy associated with a communication device.

[0060] In some embodiments, the communication network is a fifth-generation (“5G”) network. In additional or alternative embodiments, the first network node is a first radio access network (“RAN”) node. In additional or alternative embodiments, the second network node is a second RAN node.

[0061] In an additional or alternative embodiment, the first network node includes a non-real-time (“RT”) RAN Intelligent Controller (“RIC”). In an additional or alternative embodiment, the second network node includes a near-RT RIC. In an additional or alternative embodiment, a management interface is located between the non-RT RIC and the near-RT RIC. In an additional or alternative embodiment, an intent-based interface is located between the non-RT RIC and the near-RT RIC. In an additional or alternative embodiment, the management interface includes an O1 interface. In an additional or alternative embodiment, the intent-based interface includes an A1 interface.

[0062] Figure 6 Various operations may be optional for some embodiments of network nodes and related methods. For example, regarding the method of Example Embodiment 1 below, for example, Figure 6 The operation of box 610 may be optional.

[0063] Now refer to Figure 7 The flowchart below discusses the operation of the second network node based on some embodiments of the inventive concept. Figure 7 Described as being used Figure 4 The block diagram structure is implemented for RAN node 400 execution. For example, modules can be stored in... Figure 4 The memory 405 contains these modules, and these modules provide instructions such that when the instructions of the modules are executed by the processing circuit 403, the processing circuit 403 performs the corresponding operation of the flowchart. However, Figure 7 The operations within can be performed by any suitable network node.

[0064] exist Figure 7 In this process, the second network node receives configuration information associated with a specific communication device from the first network node.

[0065] At block 710, processing circuitry 403 receives configuration information from the first network node via a management interface via network interface 407. In some embodiments, receiving the configuration information comprises receiving a mapping of a plurality of functionality control values to functionality of the second network node.

[0066] At block 720, processing circuitry 403 communicates with the communication device via transceiver 401 based on the configuration information.

[0067] At block 730, processing circuitry 403 receives an indication of a second configuration from the first network node via an intent-based interface via network interface 407. In some embodiments, receiving the indication of the second configuration comprises receiving a certain functionality control value of the plurality of functionality control values. In additional or alternative embodiments, receiving the indication of the second configuration comprises receiving an indication of a configuration policy associated with the communication device.

[0068] At block 740, processing circuitry 403 communicates with the communication device via transceiver 401 based on the second configuration.

[0069] In some embodiments, the communication network is a fifth generation (“5G”) network. In additional or alternative embodiments, the first network node is a first radio access network (“RAN”) node. In additional or alternative embodiments, the second network node is a second RAN node.

[0070] In additional or alternative embodiments, the first network node comprises a non- real-time (“RT”) RAN intelligent controller (“RIC”). In additional or alternative embodiments, the second network node comprises a near-RT RIC. In additional or alternative embodiments, the management interface is between the non-RT RIC and the near-RT RIC. In additional or alternative embodiments, the intent-based interface is between the non-RT RIC and the near-RT RIC. In additional or alternative embodiments, the management interface comprises an O1 interface. In additional or alternative embodiments, the intent-based interface comprises an A1 interface.

[0071] Figure 7 Various operations of Example 1 can be optional for some embodiments of network nodes and related methods. For example, with respect to the method of Example Embodiment 11 below, for example, the operations of block 710 can be optional.

[0072] The following includes example embodiments.

[0073] Example 1. A method of operating a first network node in a communication network comprising a second network node, the method comprising:

[0074] receiving (620) information associated with a communication device connected to the second network node;

[0075] determining (630), based on the information, a configuration of the second network node relative to the communication device; and

[0076] communicating (640), to the second network node via the intent-based interface, an indication of the configuration.

[0077] Embodiment 2. The method of embodiment 1, further comprising:

[0078] communicating (610), to the second network node via the management interface, configuration information prior to receiving the information associated with the communication device.

[0079] Embodiment 3. The method of embodiment 2, wherein communicating the configuration information comprises communicating a mapping of a plurality of functionality control values to functionality of the second network node, and

[0080] wherein communicating the indication of the configuration comprises communicating a certain functionality control value of the plurality of functionality control values.

[0081] Embodiment 4. The method of any of embodiments 2-3, wherein communicating the indication of the configuration comprises communicating an indication of a configuration policy associated with the communication device.

[0082] Embodiment 5. The method of any of embodiments 1-4, wherein the information associated with the communication device comprises information associated with at least one of: a context of the communication device, a quality of service class identifier associated with the communication device, a characteristic of traffic between the communication device and the second network node, and a service provided to the user equipment.

[0083] Embodiment 6. The method of any of embodiments 1-5, wherein receiving the information associated with the communication device comprises receiving a first portion of the information from a service server associated with a service provided to the communication device via the second network node.

[0084] Embodiment 7. The method of any of embodiments 1-6, wherein receiving the information associated with the communication device comprises receiving a second portion of the information from a core network node associated with the second network node.

[0085] Embodiment 8. The method of any of embodiments 1-7, wherein the communication network is a fifth generation, 5G, network,

[0086] wherein the first network node is a first radio access network, RAN, node, and

[0087] wherein the second network node is a second RAN node.

[0088] Embodiment 9. The method of any of embodiments 1-8, wherein the first network node comprises a non-real-time, RTRAN, intelligent controller, RIC.

[0089] wherein the second network node comprises a near-RT RIC,

[0090] wherein the management interface is between the non-RT RIC and the near-RT RIC, and

[0091] wherein the intent-based interface is between the non-RT RIC and the near-RT RIC.

[0092] Embodiment 10. The method of any of embodiments 1-9, wherein the management interface comprises an O1 interface, and

[0093] wherein the intent-based interface comprises an A1 interface.

[0094] Embodiment 11. A method of operating a second network node in a communication network comprising a first network node, the method comprising:

[0095] communicating (720) with the communication device based on the first configuration;

[0096] receiving (730), from the first network node via an intent-based interface, an indication of a second configuration; and

[0097] in response to receiving the indication of the second configuration, communicating (740) with the communication device based on the second configuration.

[0098] Embodiment 12. The method of embodiment 11, further comprising:

[0099] receiving (710), from the first network node via a management interface, configuration information,

[0100] wherein communicating with the communication device based on the first configuration comprises determining the first configuration based on the configuration information.

[0101] Embodiment 13. The method of embodiment 12, wherein receiving the configuration information comprises receiving a mapping of a plurality of functionality control values to functionality of the second network node, and

[0102] wherein receiving the indication of the second configuration comprises receiving a certain functionality control value of the plurality of functionality control values.

[0103] Embodiment 14. The method of any of embodiments 12-13, wherein receiving the indication of the second configuration comprises receiving an indication of a configuration policy associated with the communication device.

[0104] Embodiment 15. The method of any of embodiments 11-14, wherein the communication network is a Fifth Generation, 5G, network,

[0105] wherein the first network node is a first radio access network, RAN, node, and

[0106] wherein the second network node is a second RAN node.

[0107] Embodiment 16. The method of any of embodiments 11-15, wherein the first network node comprises a non-Real-Time RTRAN, RIC,

[0108] wherein the second network node comprises a near-RT RIC,

[0109] wherein a management interface is between the non-RT RIC and the near-RT RIC, and

[0110] wherein an intent-based interface is between the non-RT RIC and the near-RT RIC.

[0111] Embodiment 17. The method of any of embodiments 11-16, wherein the management interface comprises an O1 interface, and

[0112] wherein the intent-based interface comprises an Al interface.

[0113] Embodiment 18. A first network node (400) operating in a communication network comprising a second network node, the first network node comprising:

[0114] processing circuitry (403); and

[0115] a memory (405) coupled to the processing circuitry, having stored therein instructions executable by the processing circuitry to cause the first network node to perform operations comprising:

[0116] receiving (620) information associated with a communication device connected to the second network node;

[0117] determining (630), based on the information, a configuration of the second network node relative to the communication device; and

[0118] transmitting (640), to the second network node via an intent-based interface, an indication of the configuration.

[0119] Embodiment 19. The first network node of embodiment 18, the operations further comprising:

[0120] transmitting (610), to the second network node via a management interface, configuration information prior to receiving the information associated with the communication device.

[0121] Embodiment 20. The first network node of embodiment 19, wherein transmitting the configuration information comprises transmitting a mapping of a plurality of functionality control values to functionality of the second network node, and

[0122] wherein the indication of the transmission configuration comprises transmitting an indication of a certain functional control value of the plurality of functional control values.

[0123] Embodiment 21. The first network node of any of embodiments 19-20, wherein the indication of the transmission configuration comprises transmitting an indication of a configuration policy associated with the communication device.

[0124] Embodiment 22. The first network node of any of embodiments 18-21, wherein the information associated with the communication device comprises information associated with at least one of: a context of the communication device, a quality of service class identifier associated with the communication device, a characteristic of traffic between the communication device and the second network node, and a service provided to the user equipment.

[0125] Embodiment 23. The first network node of any of embodiments 18-22, wherein receiving the information associated with the communication device comprises receiving a first portion of the information from a service server associated with a service provided to the communication device via the second network node.

[0126] Embodiment 24. The first network node of any of embodiments 18-23, wherein receiving the information associated with the communication device comprises receiving a second portion of the information from a core network node associated with the second network node.

[0127] Embodiment 25. The first network node of any of embodiments 18-24, wherein the communication network is a Fifth Generation, 5G, network,

[0128] wherein the first network node is a first Radio Access Network, RAN, node, and

[0129] wherein the second network node is a second RAN node.

[0130] Embodiment 26. The first network node of any of embodiments 18-25, wherein the first network node comprises a non-Real-Time, RT, RAN Intelligent Controller, RIC,

[0131] wherein the second network node comprises a near-RT RIC,

[0132] wherein the management interface is between the non-RT RIC and the near-RT RIC, and

[0133] wherein the intent-based interface is between the non-RT RIC and the near-RT RIC.

[0134] Embodiment 27. The first network node of any of embodiments 18-26, wherein the management interface comprises an O1 interface, and

[0135] wherein the intent-based interface comprises an Al interface.

[0136] Embodiment 28. A first network node (400) operating in a communication network comprising a second network node, the first network node adapted to perform operations comprising:

[0137] receiving (620) information associated with a communication device connected to the second network node;

[0138] determining (630) a configuration of the second network node relative to the communication device based on the information; and

[0139] transmitting (640) an indication of the configuration to the second network node via an intent-based interface.

[0140] Embodiment 29. The first network node of embodiment 28, the operations further comprising any of the operations of embodiments 2-10.

[0141] Embodiment 30. A computer program comprising program code to be executed by a processing circuit (403) of a first network node (400) operating in a communication network comprising a second network node, whereby execution of the program code causes the first network node to perform operations comprising:

[0142] receiving (620) information associated with a communication device connected to the second network node;

[0143] determining (630) a configuration of the second network node relative to the communication device based on the information; and

[0144] transmitting (640) an indication of the configuration to the second network node via an intent-based interface.

[0145] Embodiment 31. The computer program product of embodiment 30, the operations further comprising any of the operations of embodiments 2-10.

[0146] Embodiment 32. A computer program product comprising a non-transitory storage medium including program code, the program code to be executed by a processing circuit (403) of a first network node (400) operating in a communication network comprising a second network node, whereby execution of the program code causes the first network node to perform operations comprising:

[0147] receiving (620) information associated with a communication device connected to the second network node;

[0148] determining (630) a configuration of the second network node relative to the communication device based on the information; and

[0149] transmit (640), to the second network node via the intent-based interface, an indication of the configuration.

[0150] Embodiment 33. The computer program product of embodiment 32, the operations further comprising any of the operations of embodiments 2-10.

[0151] Embodiment 34. A second network node (400) operating in a communication network comprising a first network node, the second network node comprising:

[0152] processing circuitry (403); and

[0153] a memory (405) coupled to the processing circuitry, having stored therein instructions executable by the processing circuitry to cause the second network node to perform operations comprising:

[0154] communicating (720) with the communication device based on the first configuration;

[0155] receiving (730), from the first network node via the intent-based interface, an indication of a second configuration; and

[0156] in response to receiving the indication of the second configuration, communicating (740) with the communication device based on the second configuration.

[0157] Embodiment 35. The second network node of embodiment 34, the operations further comprising:

[0158] receiving (710), from the first network node via a management interface, configuration information prior to communicating with the communication device based on the first configuration,

[0159] wherein communicating with the communication device based on the first configuration comprises determining the first configuration based on the configuration information.

[0160] Embodiment 36. The second network node of embodiment 35, wherein receiving the configuration information comprises receiving a mapping of a plurality of functionality control values to functionality of the second network node, and

[0161] wherein receiving the indication of the second configuration comprises receiving a certain functionality control value of the plurality of functionality control values.

[0162] Embodiment 37. The second network node of any of embodiments 35-36, wherein receiving the indication of the second configuration comprises receiving an indication of a configuration policy associated with the communication device.

[0163] Embodiment 38. The second network node of any of embodiments 34-37, wherein the communication network is a Fifth Generation, 5G, network,

[0164] wherein the first network node is a first Radio Access Network, RAN, node, and

[0165] wherein the second network node is a second RAN node.

[0166] Embodiment 39. The second network node of any of embodiments 34-38, wherein the first network node comprises a non-Real-Time, RT, RAN Intelligent Controller, RIC,

[0167] wherein the second network node comprises a near-RT RIC,

[0168] wherein the management interface is between the non-RT RIC and the near-RT RIC, and

[0169] wherein the intent-based interface is between the non-RT RIC and the near-RT RIC.

[0170] Embodiment 40. The second network node of any of embodiments 34-39, wherein the management interface comprises an O1 interface, and

[0171] wherein the intent-based interface comprises an Al interface.

[0172] Embodiment 41. A second network node (400) operating in a communication network comprising a first network node, the second network node adapted to perform operations comprising:

[0173] communicating (720) with the communication device based on the first configuration;

[0174] receiving (730), from the first network node via an intent-based interface, an indication of a second configuration; and

[0175] in response to receiving the indication of the second configuration, communicating (740) with the communication device based on the second configuration.

[0176] Embodiment 42. The second network node of embodiment 41, the operations further comprising any of the operations of embodiments 12-17.

[0177] Embodiment 43. A computer program comprising program code to be executed by a processing circuit (403) of a second network node (400) operating in a communication network comprising a first network node, whereby execution of the program code causes the second network node to perform operations comprising:

[0178] communicating (720) with the communication device based on the first configuration;

[0179] receiving (730), from the first network node via an intent-based interface, an indication of a second configuration; and

[0180] in response to receiving the indication of the second configuration, communicating (740) with the communication device based on the second configuration.

[0181] Example 44. The computer program of Example 43, the operations further comprising any of the operations of Examples 12-17.

[0182] Example 45. A computer program product comprising a non-transitory storage medium including program code, the program code to be executed by a processing circuit (403) of a second network node (400) operating in a communication network comprising a first network node, whereby execution of the program code causes the second network node to perform operations comprising:

[0183] communicating (720) with the communication device based on the first configuration;

[0184] receiving (730), from the first network node via the intent-based interface, an indication of a second configuration; and

[0185] communicating (740) with the communication device based on the second configuration in response to receiving the indication of the second configuration.

[0186] Example 46. The computer program of Example 45, the operations further comprising any of the operations of Examples 12-17.

[0187] Additional explanation is provided below.

[0188] In general, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the disclosure, unless a different meaning is clearly given and / or is implied by the context of their use. All references to a thing by the indefinite article "a" or "an" are to be interpreted as including one or more things, unless explicitly stated otherwise. The steps of any methods disclosed herein need not be performed in the exact order disclosed, unless explicitly stated otherwise. Any feature of any of the disclosed embodiments can be applied to any other embodiment, where suitable. Likewise, any advantage of any of the disclosed embodiments can apply to any other embodiment, and vice- versa. Other objects, features and advantages of the disclosed embodiments will become apparent from the description herein.

[0189] Some embodiments of what is envisaged herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, they are provided for illustrative purposes. Embodiments are provided as examples to convey the substance of the subject matter.

[0190] Figure 8A wireless network according to some embodiments is shown.

[0191] While the topics described herein can be implemented in any suitable type of system using any appropriate components, the embodiments disclosed herein are relative to wireless networks (such as...). Figure 8 The example wireless network shown is used for description. For the sake of brevity, Figure 8 The wireless network depicted only includes network 4106, network nodes 4160 and 4160b, and WD 4110, 4110b, and 4110c (also referred to as mobile terminals). In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (such as a landline telephone, service provider, or any other network node or terminal device). Among the components shown, network node 4160 and wireless device (WD) 4110 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access and / or use of services provided by or via the wireless network.

[0192] Wireless networks may include any type of communication, telecommunications, data, cellular and / or radio network or other similar system and / or connected to it via an interface. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement: communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G or 5G standards; wireless local area network (WLAN) standards such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave and / or ZigBee standards.

[0193] Network 4106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0194] The network node 4160 and the WD 4110 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality such as providing wireless connections in a wireless network. In different embodiments, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in communications (whether direct or indirect) between wireless devices and / or between wireless devices and other nodes communicating in the wireless network.

[0195] As used herein, “network node” refers to equipment that is able, configured to, arranged to, and / or operable to communicate directly or indirectly with a wireless device and / or with other equipment in the wireless network that is able to implement and / or provide wireless access to the wireless device and / or perform other functions in the wireless network, such as management functions. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations can be categorized based on the amount of coverage they provide (or, stated differently, the transmission power at which they operate) and can then be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node controlling a relay. Network nodes can also include one or more (or all) parts of a distributed radio base station, such as a centralized base station controller and / or a remote radio unit (RRU), sometimes called a remote radio head (RRH). Such remote radio units can or can not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS). Still further examples of network nodes include multi-standard radio (MSR) devices, network controllers (such as radio network controllers (RNCs) or base station controllers (BSCs)), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and / or MDTs. As another example, a network node can be a virtual network node as described in more detail below. More generally, however, network nodes can represent any suitable apparatus (or grouping of apparatuses) that is able to, configured to, arranged to, and / or operable to enable and / or provide wireless devices with access to a wireless network or to provide some service to wireless devices that are already

[0196] In Figure 8In particular embodiments, network node 4160 includes processing circuitry 4170, device readable medium 4180, interface 4190, auxiliary equipment 4184, power source 4186, power circuitry 4187, and antenna 4162. While these components 4170, 4180, 4190, 4184, 4186, 4187, and 4162 are each shown as a single component, in other embodiments, any number (including zero) of these components can be used, and these components can be arranged Figure 8 Network node 4160 shown in the example wireless network of FIG. 16 can represent a device that includes the illustrated combination of hardware components, but other embodiments can include network nodes with different combinations of components, or a single component not shown. It is to be understood that a network node includes any suitable combination of hardware and / or software needed to perform the tasks described herein. Moreover, while the components 4170, 4180, 4190, 4184, 4186, 4187, and 4162 of network node 4160 are shown as single boxes, in practice, they can each comprise multiple physical components.

[0197] Similarly, network node 4160 can be composed of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, just to name a few), which can each have their own respective components. In certain scenarios where network node 4160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB’s. In such scenarios, each unique NodeB and RNC pair, in some cases, can be considered a single separate network node. In some embodiments, network node 4160 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components (e.g., a separate device readable medium 4180

[0198] Processing circuitry 4170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 4170 can include processing information obtained by processing circuitry 4170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing, making a determination.

[0199] The processing circuit 4170 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other processing circuit, resource, or combination of hardware, software, and / or encoded logic operable to provide functionality of the network node 4160, such as the device readable medium 4180. For example, the processing circuit 4170 might execute instructions stored in the device readable medium 4180 or in memory within the processing circuit 4170. Such functionality might include providing various wireless features, functions, or benefits described herein. In some embodiments, the processing circuit 4170 can comprise a system on a chip (SOC).

[0200] In some embodiments, the processing circuit 4170 can include one or more of radio frequency (RF) transceiver circuitry 4172 and baseband processing circuitry 4174. In some embodiments, the radio frequency (RF) transceiver circuitry 4172 and the baseband processing circuitry 4174 can be on separate chips (or sets of chips), boards, or units, such as radio and digital units. In alternative embodiments, part or all of RF transceiver circuitry 4172 and baseband processing circuitry 4174 can be on the same chip or set of chips, boards, or units.

[0201] In certain embodiments, part or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device might be provided by the processing circuit 4170 executing instructions stored on the device readable medium 4180 or memory within the processing circuit 4170. In alternative embodiments, part or all of the functionality might be provided by processing circuit 4170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, the processing circuit 4170 is configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuit 4170 alone or to the network node 4160, but are enjoyed by network node 4160 users and wireless networks generally.

[0202] Device readable medium 4180 can include any form of volatile or non-volatile computer readable memory including, by way of non-limiting example, volatile RAM, static (non- volatile) RAM, ROM, EEPROM, optical storage, magnetic storage, flash memory, electrical storage, solid state storage, or any other non-transitory device readable and / or computer executable memory that stores information, data, and / or instructions that can be used by processing circuitry 4170. Device readable medium 4180 can be used to store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and / or other instructions capable of being executed by processing circuitry 4170 and utilized by network node 4160. Device readable medium 4180 can be used to store any calculations made by processing circuitry 4170 and / or any data received via interface 4190. In some embodiments, processing circuitry 4170 and device readable medium 4180 can be considered to be integrated.

[0203] Interface 4190 is used in the wired or wireless communication of signaling or data between network node 4160, network 4106, and / or WDs 4110. As illustrated, interface 4190 comprises port(s) / terminal(s) 4194 to send and receive data, for example to and from network 4106 over a wired connection. Interface 4190 also includes radio front end circuitry 4192 that can be coupled to, or in some embodiments a part of, antenna 4162. Radio front end circuitry 4192 comprises filters 4198 and amplifiers 4196. Radio front end circuitry 4192 can be connected to antenna 4162 and processing circuitry 4170. Radio front end circuitry can be configured to condition signals communicated between antenna 4162 and processing circuitry 4170. Radio front end circuitry 4192 can receive digital data that is to be sent

[0204] In certain alternative embodiments, network node 4160 can not include standalone radio front-end circuitry 4192, but rather can include radio front-end circuitry that is part of interface 4190 and can be connected to antenna 4162 without standalone radio front-end circuitry 4192. Similarly, in some embodiments, all or part of RF transceiver circuitry 4172 can be considered part of interface 4190. In still other embodiments, interface 4190 can include one or more ports or terminals 4194 that are part of a radio (not shown), radio front-end circuitry 4192, and RF transceiver circuitry 4172, and interface 4190 can be in communication with baseband processing circuitry 4174, which is part of a digital unit (not shown).

[0205] Antenna 4162 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 4162 can be coupled to radio front-end circuitry 4192 and can be any type of antenna and / or antenna array capable of transmitting and receiving wireless data and / or signals. In some embodiments, antenna 4162 can include one or more omni-directional, sector or panel antennas operable to transmit / receive radio signals between, for example, 2 Ghz and 66 Ghz. An omni-directional antenna can be used to transmit / receive radio signals along any

[0206] Antenna 4162, interface 4190, and / or processing circuitry 4170 can be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signals can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 4162, interface 4190, and / or processing circuitry 4170 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and / or signals can be transmitted to a wireless device, another network node and / or any other network equipment.

[0207] Power circuitry 4187 can comprise, or be coupled to, power management circuitry and is configured to supply the components of the network node 4160 with power for performing the functionality described herein. Power circuitry 4187 can receive power from power source 4186. Power source 4186 and / or power circuitry 4187 can be configured to provide power to the various components of the network node 4160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 4186 can be incorporated into, or external to, power circuitry 4187 and / or the network node 4160. For example, network node 4160 can be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 4187. As a further example, power source 4186 can comprise a power source attached to, or incorporated into power circuitry 4187, such as a battery or battery pack. The battery can provide backup power should the external power source fail, allowing the network node 4160 to perform a graceful shutdown in the event of failure of the external power source. Other types of power sources, such as photovoltaic devices, can also be used.

[0208] Alternative embodiments of the network node 4160 can include additional components Figure 8 in addition to those shown, which can be responsible for providing certain aspects of the network node's functionality, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 4160 can include user interface devices so as to allow intake of information into the network node 4160 and to allow output of information from the network node 4160. This can allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 4160.

[0209] A wireless device (WD) as used herein refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise mentioned, the term "WD" is used synonymously with user equipment (UE) herein. The wireless communication can involve transmitting and / or receiving wireless signals to and / or from a network node or another WD. In some embodiments, a WD can be configured to transmit and / or receive information without direct human interaction. For instance, a WD can be designed to transmit information to a network on a predetermined schedule, when triggered, or in response to a request. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a game console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD can support device-to-device (D2D) communication, e.g., using a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), and can in this case be called a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or another device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another WD and / or a network node. The WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be called an MTC device. As a particular example, the WD can be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or home or personal appliances (e.g., refrigerators, TVs, etc.), personal wearables (such as watches, fitness trackers, etc.). In other scenarios, a WD can represent a vehicle or other equipment that is capable of monitoring and / or reporting on operating conditions or other functions associated with its operation. The WD as described above can represent the endpoint of a wireless connection, in which case the device can be called a wireless terminal. Further, the WD as described above can be mobile, in which case it can also be called a mobile device or mobile terminal.

[0210] As illustrated, wireless device 4110 includes antenna 4111, interface 4114, processing circuitry 4120, device readable medium 4130, user interface equipment 4132, auxiliary equipment 4134, power source 4136 and power circuitry 4137. WD 4110 can include multiple sets of one or more of the illustrated components of WD 4110 for different wireless technologies supported by WD 4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD 4110.

[0211] Antenna 4111 can include one or more antennas or antenna arrays, configured to send and / or receive wireless signals, and is connected to interface 4114. In some embodiments, antenna 4111 can be separate from WD 4110 and be connectable to WD 4110 through an interface or port. Antenna 4111, interface 4114, and / or processing circuitry 4120 can be configured to perform any receiving or transmitting described herein as being performed by a WD. Any information, data and / or signals can be received from a network node and / or another WD. In some embodiments, radio front end and / or antenna 4111 can be considered an interface.

[0212] As illustrated, interface 4114 includes radio front end circuitry 4112 and antenna 4111. Radio front end circuitry 4112 includes one or more filters 4118 and amplifiers 4116. Radio front end circuitry 4112 is connected to antenna 4111 and processing circuitry 4120 and is configured to condition signals communicated between antenna 4111 and processing circuitry 4120. Radio front end circuitry 4112 can be coupled to or a part of antenna 4111. In some embodiments, WD 4110 can not include separate radio front end circuitry 4112, and processing circuitry 4120 can be configured to condition signals

[0213] Processing circuitry 4120 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other processing circuitry, 4130), working alone or in combination, to provide WD 4110 functionality. Such functionality can include providing any of the various wireless features or benefits described herein. For example, processing circuitry 4120 can execute instructions stored in device readable medium 4130 or in memory within processing circuitry 4120 to provide the functionality disclosed herein.

[0214] As illustrated, processing circuitry 4120 includes one or more of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126. In other embodiments, the processing circuitry can comprise different components and / or different combinations of components. In certain embodiments, processing circuitry 4120 of WD 4110 can comprise a SOC. In some embodiments, RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 can be on separate chips or sets of chips. In alternative embodiments, parts of baseband processing circuitry 4124 and application processing circuitry 4126 can be combined into one chip or set of chips and RF transceiver circuitry 4122 can be on a separate chip or set of chips. In still alternative embodiments, parts of RF transceiver circuitry 4122 and baseband processing circuitry 4124 can be on the same chip or set of chips and application processing circuitry 4126 can be on a separate chip or set of chips. In yet other alternative embodiments, parts of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 4122 can be part of interface 4114. RF transceiver circuitry 4122 can condition RF signals for processing circuitry 4120.

[0215] In certain embodiments, some or all of the functionality described herein as being performed by a WD can be performed by processing circuitry 4120 executing instructions stored on device readable medium 4130, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 4120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired device or in a device configured with hard-wired logic and / or circuitry. In yet other embodiments, the functionality can be provided by a combination of

[0216] Processing circuitry 4120 can be configured to perform any determining, calculating, or similar operations (e.g., some obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 4120, can include processing information obtained by processing circuitry 4120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 4110, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing, making a determination.

[0217] Device readable medium 4130 can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and / or other instructions (i.e., instructions that can be executed by processing circuitry 4120). Device readable medium 4130 can include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory devices that store information, data, and / or instructions that can be used by processing circuitry 4120. In some embodiments, processing circuitry 4120 and device readable medium 4130 can be considered to be integrated.

[0218] User interface devices 4132 can provide means by which a human user can interact with WD 4110. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface devices 4132 can be operable to generate output to the user and to

[0219] Auxiliary equipment 4134 is operable to provide more specific functionality which can not be generally performed by WDs. This can comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication, etc. The inclusion and type of components of auxiliary equipment 4134 can vary depending on the embodiment and / or scenario.

[0220] In some embodiments, power source 4136 can take the form of a battery or battery pack. Other types of power sources, such as an external power supply (e.g., an electricity outlet), photovoltaic devices or power cells, can also be used. WD 4110 can further comprise power circuitry 4137 for delivering power from power source 4136 to the various components of WD 4110 that require power to carry out any of the functionality described or indicated herein. Power circuitry 4137 can in some embodiments comprise power management circuitry. Additionally or alternatively, power circuitry 4137 can be operable to receive power from an external power source; in which case WD 4110 can be connectable to the external power source (such as an electricity outlet) via an input circuitry or interface (such as an electrical cable). Power circuitry 4137 can also in some embodiments be operable to deliver power from an external power source to power source 4136. This can be, for example, for the charging of power source 4136. Power circuitry 4137 can perform any formatting, converting, or other modification of the power from power source 4136 in order to make the power suitable for use by the respective components of WD 4110 to which power is supplied.

[0221] Figure 9 A user equipment is shown in accordance with some embodiments.

[0222] Figure 9 One embodiment of a UE in accordance with various aspects described herein is shown. As used herein, a "user equipment" or "UE" can not necessarily have a user in the sense of a human being that owns and / or operates the relevant device. The UE can instead represent a device that is intended for sale to, or operation by, an end user, but can not, or initially can not, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, the UE can represent a device that is not intended for sale to, or operation by, an end user, but can be associated with or operated for the benefit of a user (e.g., a smart power meter). The UE 42200 can be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As described elsewhere herein, a UE can also be an IAB node or an IAB donor. Figure 9 As shown, the UE 4200 is one example of a WD configured to communicate according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. The term "WD" and "UE" can be used interchangeably herein. Accordingly, although the specification can refer to a "WD," "UE," or "IAB node," in some embodiments, the description applies equally to WDs, UEs, and / or IAB nodes. Figure 9 While the specification can refer to a "UE," the components described herein are equally applicable to a WD, and vice versa.

[0223] In Figure 9In some embodiments, the UE 4200 includes: processing circuitry 4201 operatively coupled to input / output interface 4205; radio frequency (RF) interface 4209; network connection interface 4211; memory 4215, including random access memory (RAM), read-only memory (ROM), and storage medium 4221 or the like; communication subsystem 4231; power source 4213; and / or any other component, or any combination thereof. Storage medium 4221 includes operating system 4223, application program 4225, and data 4227. In other embodiments, storage medium 4221 can include other similar types of information. Certain UEs can utilize all of the aforementioned components, or only a subset of such components. The level of integration between the components can vary from one UE model to another. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. Figure 9

[0224] In Figure 9 In some embodiments, processing circuitry 4201 can be configured to process computer instructions and data. Processing circuitry 4201 can be configured to implement any sequential state machine operative to

[0225] ​In the depicted embodiment, input / output interface 4205 can be configured to provide a communication interface to either an input device, an output device, or both. UE 4200 can be configured to use output device via input / output interface 4205. The output device can use a same type of interface port as the input device. For example, a USB port can be used to provide input / output to / from UE 4200. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 4200 can be configured to use input device via input / output interface 4205 to allow a user to capture information into UE 4200. The input device can include a touch- or presence-sensitive display, a camera (for example, a digital still or motion camera), a microphone, a sensor, a mouse, a trackball, a directional pad, a directional pad, a scroll wheel, a smartcard, and the like. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a

[0226] In Figure 9 RF interface 4209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 4211 can be configured to provide a communication interface to network 4243a. Network 4243a can encompass

[0227] The RAM 4217 can be configured to interface to the processing circuitry 4201 via the bus 4202 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. The ROM 4219 can be configured to provide computer instructions or data to the processing circuitry 4201. For example, the ROM 4219 can be configured to store invariant low-level system code or data

[0228] The storage medium 4221 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), soft disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High-Density Digital Versatile Disc (DVD) optical drive, internal hard disk drive, Blu-Ray optical drive, holographic data storage optical drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 4221 can allow the UE 4200 to access computer-executable instructions, application programs or the like, stored on non-transitory or transitory memory media, to off-load data, or to store information into memory media. An article of manufacture, such as one utilizing a communication system can be tangibly embodied in the storage medium 4221, which can comprise a device readable medium.

[0229] In Figure 9In particular embodiments, processing circuitry 4201 can be configured to use communication subsystem 4231 to communicate with network 4243b. Network 4243a and network 4243b can be one or more of the same network or one or more different networks. Communication subsystem 4231 can be configured to include one or more transceivers used to communicate with network 4243b. For example, communication subsystem 4231 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or base station of a radio access network (RAN), according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver can include transmitter 4233 and / or receiver 4235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 4233 and receiver 4235 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0230] In the illustrated embodiment, communication functions of communication subsystem 4231 can include data communication, voice communication, multimedia communication, short-range communications, such as Bluetooth, near-field communication, location-based communication, such as the use of the global positioning system (GNSS / GPS) to determine a location, another like function, or any combination thereof. For example, communication subsystem 4231 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GNSS / GPS communication. Network 4243b can encompass wired and / or wireless networks, such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof. For example, network 4243b can be a cellular network, a Wi-Fi network, and / or a near-field network. Power source 4213 can be configured to supply alternating current (AC) or direct current (DC) power to components of UE 4200.

[0231] The features, benefits and / or functions described herein can be implemented in one or more components of the UE 4200, or elsewhere. Further, the features, benefits and / or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 4231 can be configured to include any of the components described herein. Further, processing circuitry 4201 can be configured to communicate with any of such components over bus 4202. In another example, any of such components can be represented by

[0232] Figure 10 A virtualization environment, in accordance with some embodiments, is shown.

[0233] Figure 10 is a schematic block diagram illustrating a virtualization environment 4300 in which functions implemented by some embodiments can be virtualized. In this context, virtualization means the creation of virtual versions of devices or devices, which can include the virtualization of hardware platforms, storage devices and networking resources. As used herein, "virtualization" can apply to nodes (e.g., virtualized base stations or virtualized radio access nodes) or to devices (e.g., UEs, wireless devices or any other type of communication device) or components thereof, and relates to implementations in which at least a portion of the functionality is implemented as a virtual component(s) (e.g., an application, component, function, virtual machine, or container executing on one or more physical processing nodes in one or more networks).

[0234] In some embodiments, portions or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more of virtual environments 4300 hosted by one or more of hardware nodes 4330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node can be entirely virtualized.

[0235] The functions can be implemented by one or more applications 4320 (which alternatively can be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. An application 4320 runs in the virtualization environment 4300 which provides hardware 4330 including processing circuitry 4360 and memory 4390. The memory 4390 contains instructions 4395 executable by the processing circuitry 4360 whereby the application 4320 is operative to provide one or more of the features, benefits, and / or functions disclosed herein.

[0236] Virtualization environment 4300 comprises general-purpose or special-purpose network hardware devices 4330 comprising a set of one or more processors or processing circuitry 4360, which can be commercial off-the-shelf (COTS) processors, dedicated Application-Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise memory 4390-1 which can be non-persistent memory for storing instructions 4395 or software to be executed by processing circuitry 4360. Each hardware device can include one or more network interfaces 4370, also referred to as network interface controllers (NICs), for communicating with various other devices via a computer network. Each hardware device can also include non-transitory, persistent, machine-readable storage media 4390-2 having software 4395 or instructions 4395 stored thereon to be executed by processing circuitry 4360.

[0237] Virtual machines 4340 comprise virtual processing, virtual storage, virtual networking or interface, and virtual storage devices, and can be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of the instances of virtual appliances 4320 can be implemented on one or more of virtual machines 4340, and the implementations can be made in different ways.

[0238] During operation, processing circuitry 4360 executes software 4395 to instantiate the hypervisor or virtualization layer 4350, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 4350 can provide a virtual operating platform that appears like networking hardware to virtual machine 4340.

[0239] As Figure 10As shown, hardware 4330 can be a standalone network node with generic or specific components. Hardware 4330 can comprise antenna 43225 and some functionality can be implemented in software. Alternatively, hardware 4330 can be part of a larger cluster of hardware, e.g., such as in a data center or customer premises equipment (CPE), where many hardware nodes work together and are managed via management and orchestration (MANO) 43100, which also oversees lifecycle management of applications 4320 among other things.

[0240] Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches and physical storage, which can be located in data centers, and customer premise equipment.

[0241] In the context of NFV, virtual machine 4340 can be a software implementation of a physical machine, which executes programs, as if they were running in the physical, non-virtualized machine. Each of virtual machines 4340, and that part of hardware 4330 which executes that virtual machine, if it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with others of the virtual machines 4340, form a separate virtual network elements (VNE).

[0242] Also in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions which are executed in one or more virtual machines 4340 on top of hardware networking infrastructure 4330, and correspond to Figure 10 applications 4320 in

[0243] In some embodiments, one or more radio units (RFU) 43220 which each include one or more transmitters 43220 and one or more receivers 43210 can be coupled to one or more antennas 43225. Radio units 43200 can communicate directly with hardware nodes 4330 via one or more appropriate network interfaces, and can be combined with the virtual components to provide virtual nodes that have radio capabilities, such as Radio Access Nodes or Base Stations.

[0244] In some embodiments, some signaling can be able to influence the operation of radio units 43200, e.g., modulation schemes, power control, etc. In these embodiments, some functionality can be offloaded from core network to radio units 43200.

[0245] Figure 11 A telecommunication network is shown connected via an intermediate network to a host computer, according to some embodiments.

[0246] Reference is made to Figure 11According to an embodiment, the communication system includes a telecommunication network 4410, such as a 3GPP-type cellular network, which comprises a access network 4411, such as a radio access network, and a core network 4414. The access network 4411 comprises a plurality of base stations 4412a, 4412b, 4412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c is connectable to the core network 4414 over a wired or wireless connection 4415. A first UE 4491 located in coverage area 4413c is configured to wirelessly connect to, or be paged by, the corresponding base station 4412c. A second UE 4492 in coverage area 4413a is wirelessly connectable to the corresponding base station 4412a. While a plurality of UEs 4491, 4492 are illustrated in this example, the

[0247] The telecommunication network 4410 is itself connected to a host computer 4430, which can be implemented as a server, a cloud

[0248] Figure 11The communication system as a whole enables connectivity between the connected UEs 4491, 4492 and the host computer 4430. The connectivity can be described as an over-the-top (OTT) connection 4450. The host computer 4430 and the connected UEs 4491, 4492 are configured to communicate data and / or signaling over the OTT connection 4450 using the access network 4411, the core network 4414, any intermediate network 4420, and possible further infrastructure (not shown) as intermediaries. The OTT connection 4450 can be transparent in the sense that the participating communication devices through which the OTT connection 4450 passes are unaware of the routing of data and / or signaling that they carry for the OTT connection 4450. For example, the base station 4412 can not or need not be aware that the data it transmits to a UE 4491 originates from or is destined to the host computer 4430. Similarly, the UE 4491 can not or need not be aware that the data it transmits to the host computer 4430 passes through the base station 4412. The OTT connection 4450 can be configured to use a single protocol, or a combination of protocols, as well as different protocols at different times or locations.

[0249] Figure 12 A host computer is shown that communicates via a base station with a user equipment over a partially wireless connection, in accordance with some embodiments.

[0250] Example implementations, in accordance with an embodiment, of the UE, the base station and the host computer, described in the preceding paragraphs will now be described, with reference to Figure 12 the communication system 4500. The host computer 4510 includes hardware 4515 that includes a communication interface 4516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 4500. The host computer 4510 further comprises processing circuitry 4518, which can have storage and / or processing capabilities. In particular, the processing circuitry 4518 can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 4510 further comprises software 4511, which is stored in the host computer 4510 and executable by the processing circuitry 4518. The software 4511 includes a host application 4512. The host application 4512 can be operable to provide a service to a remote user, such as a UE 4530 connecting via an OTT connection 4550 terminating at the UE 4530 and the host computer 4510. In providing the service to the remote user, the host application 4512 can provide user data which is transmitted using the OTT connection 4550.

[0251] The communication system 4500 further includes the base station 4520 provided in a telecommunication system and comprising hardware 4525 enabling it to communicate with the host computer 4510 and with the UE 4530. The hardware 4525 can include a communication interface 4526 for wired or wireless connection to the host computer 4510 and a radio interface 4527 for wired or wireless connection to the UE 4530 within the coverage area 4551 of the base station 4520. The communication interface 4526 can be configured to facilitate connection 4560 to the host computer 4510. The connection 4560 can be direct or it can pass through the core network (not shown) of the telecommunication system and / or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 4525 of the base station 4520 further includes processing circuitry 4528, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 4520 further has software 4521 stored internally or accessible via an external connection. Figure 12 Figure 12 The communication system 4500 further includes the UE 4530 already referred to. Its hardware 4535 can include a radio interface 4537 configured to set up and maintain a wireless connection 4570 with a base station serving a coverage area in which the UE 4530 is currently located. The hardware 4535 of the UE 4530 further includes processing circuitry 4538, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 4530 further comprises software 4531 stored internally or accessible via an external connection.

[0252] The communication system 4500 further includes the UE 4530 already referred to. Its hardware 4535 can include a radio interface 4537 configured to set up and maintain a wireless connection 4570 with a base station serving a coverage area in which the UE 4530 is currently located. The hardware 4535 of the UE 4530 further includes processing circuitry 4538, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 4530 further comprises software 4531 stored internally or accessible via an external connection. ​

[0253] It is noted that Figure 12 The host computer 4510, base station 4520, and UE 4530 illustrated in Figure 17 can be similar or identical to the host computer 4510, base station 4520, and UE 4530 of the embodiment of Figure 16, respectively. That is, the inner workings of these entities can be as shown in Figure 17 and the surrounding network topology can be as shown in Figure 16. Figure 11 The host computer 4430, one of the base stations 4412a, 4412b, and 4412c, and one of the UEs 4491 and 4492 of the embodiment of Figure 18 can be similar or identical to the host computer 4510, one of the base stations 4520, and one of the UEs 4530 of the embodiment of Figure 17, respectively. That is, the inner workings of these entities can be as shown in Figure 18 and the surrounding network topology can be as shown in Figure 17. Figure 12 The host computer 4510, base station 4520, and UE 4530 illustrated in Figure 17 can be similar or identical to the host computer 4510, base station 4520, and UE 4530 of the embodiment of Figure 16, respectively. That is, the inner workings of these entities can be as shown in Figure 17 and the surrounding network topology can be as shown in Figure 16. Figure 11 The host computer 4510, base station 4520, and UE 4530 illustrated in Figure 17 can be similar or identical to the host computer 4510, base station 4520, and UE 4530 of the embodiment of Figure 16, respectively. That is, the inner workings of these entities can be as shown in Figure 17 and the surrounding network topology can be as shown in Figure 16.

[0254] Figure 12 The OTT connection 4550 has been drawn abstractly to illustrate the

[0255] The wireless connection 4570 between the UE 4530 and the base station 4520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments teach improvements to the performance of OTT services provided to the UE 4530 using the OTT connection 4550, in which the wireless connection 4570 forms the last segment. More precisely, the teachings of these embodiments can improve random access speed, and / or reduce random access failure rate, and thereby provide benefits such as faster and / or more reliable random access.

[0256] A measurement process may be provided for the purpose of monitoring data rate, latency, and other factors for improvement in one or more of the embodiments. Optional network functionality may further exist for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to changes in the measurement results. The measurement process and / or the network functionality for reconfiguring the OTT connection 4550 may be implemented in the software 4511 and hardware 4515 of the host computer 4510, or in the software 4531 and hardware 4535 of the UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 4550 passes; the sensors may participate in the measurement process by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which the software 4511, 4531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 4550 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not affect the base station 4520, and it may be unknown or undetectable to the base station 4520. Such processes and functionalities may be known and practiced in the art. In some embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, and the like by the host computer 4510. Measurements are possible because software 4511 and 4531 use the OTT connection 4550 to transmit messages, particularly empty or 'false' messages, while it monitors propagation time, errors, etc.

[0257] Figure 13 The present invention illustrates a method implemented in a communication system according to some embodiments, the communication system including a host computer, a base station, and a user equipment.

[0258] Figure 13 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 11 and Figure 12 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only include descriptions of... Figure 13 Referring to the accompanying drawings. In step 4610, the host computer provides user data. In sub-step 4611 of step 4610 (which may be optional), the host computer provides user data by executing a host application. In step 4620, the host computer initiates a transmission carrying user data to the UE. Following the teachings of the embodiments described throughout this disclosure, in step 4630 (which may be optional), the base station transmits user data to the UE, the user data being carried in the transmission initiated by the host computer. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0259] Figure 14 The present invention illustrates a method implemented in a communication system according to some embodiments, the communication system including a host computer, a base station, and a user equipment.

[0260] Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 11 and Figure 12 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only include descriptions of... Figure 14 Refer to the accompanying drawings. In step 4710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 4720, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via a base station. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0261] Figure 15 The present invention illustrates a method implemented in a communication system according to some embodiments, the communication system including a host computer, a base station, and a user equipment.

[0262] Figure 15 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 11 and Figure 12 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only include descriptions of... Figure 15 Referring to the accompanying drawings. In step 4810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 4820, the UE provides user data. In sub-step 4821 of step 4820 (which may be optional), the UE provides user data by executing a client application. In sub-step 4811 of step 4810 (which may be optional), the UE executes a client application that responds to the received input data provided by the host computer to provide user data. In providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in sub-step 4830 (which may be optional). According to the teachings of the embodiments described throughout this disclosure, in step 4840 of the method, the host computer receives user data transmitted from the UE.

[0263] Figure 16The present invention illustrates a method implemented in a communication system according to some embodiments, the communication system including a host computer, a base station, and a user equipment.

[0264] Figure 16 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 11 and Figure 12 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only include descriptions of... Figure 16 Refer to the accompanying drawings. In step 4910 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step 4920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0265] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers and may include digital signal processors (DSPs), application-specific digital logic, and other digital hardware such as these. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0266] The term “unit” may have the conventional meaning in the field of electronic devices, electrical apparatus and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., as described herein.

[0267] abbreviation

[0268] At least some of the following abbreviations may be used in this disclosure. In the event of any inconsistency between the abbreviations, the usage described above shall prevail. If abbreviations are listed multiple times below, the first listing shall be preferred over any subsequent listing(s).

[0269] 1x RTT CDMA2000 1x Radio Transmission Technology

[0270] 3GPP Third Generation Partnership Project

[0271] 5G Fifth Generation

[0272] ABS Almost Blank Subframe

[0273] ARQ Automatic Repeat reQuest

[0274] AWGN Additive White Gaussian Noise

[0275] BCCH Broadcast Control Channel

[0276] BCH Broadcast Channel

[0277] CA Carrier Aggregation

[0278] CC Carrier Component

[0279] CCCH SDU Common Control Channel SDU CDMA Code Division Multiple Access

[0280] CGI Cell Global Identifier

[0281] CIR Channel Impulse Response

[0282] CP Cyclic Prefix

[0283] CPICH Common Pilot Channel

[0284] CPICH Ec / No Received energy per chip divided by power density in the frequency band

[0285] CQI Channel Quality Information

[0286] C-RNTI Cell RNTI CSI Channel State Information

[0287] DCCH Dedicated Control Channel

[0288] DL Downlink

[0289] DM Demodulation

[0290] DMRS Demodulation Reference Signal

[0291] DRX Discontinuous Reception

[0292] DTX Discontinuous Transmission

[0293] DTCH Dedicated Traffic Channel

[0294] DUT Device Under Test

[0295] E-CID Enhanced Cell-ID (positioning method)

[0296] E-SMLC Evolved- Serving Mobile Location Center

[0297] ECGI Evolved CGI eNB E-UTRAN NodeB PDCCH Physical Downlink Control Channel

[0298] E-SMLC Evolved Serving Mobile Location Center

[0299] E-UTRA Evolved UTRA

[0300] E-UTRAN Evolved UTRAN FDD Frequency Division Duplex

[0301] FFS For Further Study GERAN GSM EDGE Radio Access Network gNB Base station in NR GNSS Global Navigation Satellite System GSM Global System for Mobile communication HARQ Hybrid Automatic Repeat Request HO Handover

[0302] HSPA High Speed Packet Access HRPD High Rate Packet Data LOS Line of Sight

[0303] LPP LTE Positioning Protocol LTE Long Term Evolution

[0304] MAC Medium Access Control MBMS Multimedia Broadcast Multicast Service MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MIB Master Information Block

[0305] MME Mobile Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio

[0306] OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access

[0307] OSS Operation Support System

[0308] OTDOA Observed Time Difference of Arrival

[0309] O&M Operation and Maintenance

[0310] PBCH Physical Broadcast Channel

[0311] P-CCPCH Primary Common Control Physical Channel

[0312] PCell Primary Cell

[0313] PCFICH physical control format indicator channel

[0314] PDCCH physical downlink control channel

[0315] PDP profile delay profile

[0316] PDSCH physical downlink shared channel

[0317] PGW packet gateway

[0318] PHICH physical hybrid-ARQ indicator channel

[0319] PLMN public land mobile network

[0320] PMI precoding matrix indicator

[0321] PRACH physical random access channel

[0322] PRS positioning reference signal

[0323] PSS primary synchronization signal

[0324] PUCCH physical uplink control channel

[0325] PUSCH physical uplink shared channel

[0326] RACH random access channel

[0327] QAM quadrature amplitude modulation

[0328] RAN radio access network

[0329] RAT radio access technology

[0330] RLM radio link management

[0331] RNC radio network controller

[0332] RNTI radio network temporary identifier

[0333] RRC radio resource control

[0334] RRM radio resource management

[0335] RS reference signal RSCP received signal code power RSPR reference symbol received power; or

[0336] reference signal received power RSRQ reference signal received quality; or

[0337] Reference Symbol Received Quality, RSSI Received Signal Strength Indicator, RSTD Reference Signal Time Difference, SCH Synchronization Channel, SCHell Secondary Cell, SDU Service Data Unit, SFN System Frame Number, SGW Serving Gateway, SI System Information, SIB System Information Block, SNR Signal to Noise Ratio, SON Self-Optimizing Network, SS Synchronization Signal, SSS Secondary Synchronization Signal, TDD Time Division Duplex, TDOA Time Difference of Arrival, TOA Time of Arrival, TSS Tertiary Synchronization Signal, TTI Transmission Time Interval, UE User Equipment, UL Uplink, UMTS Universal Mobile Telecommunications System, USIM Universal Subscriber Identity Module, UTDOA Uplink Time Difference of Arrival

[0338] UTRA Universal Terrestrial Radio Access

[0339] UTRAN Universal Terrestrial Radio Access Network

[0340] WCDMA Wide CDMA, WLAN Wide Area Network

[0341] Further definitions and embodiments are discussed below.

[0342] In the above-description of various embodiments of the present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0343] When an element is said to be "connected," "coupled," "responsive," or "in communication" (or variations thereof) to another element, it can be directly connected, coupled, responsive, or in communication to the other element, or intervening elements can be present. In contrast, when an element is said to be "directly connected," "directly coupled," "directly responsive," or "directly in communication" (or variations thereof) to another element, there are no intervening elements present. Like reference numbers refer to like elements throughout. Furthermore, "coupled," "connected," "responsive," or variations thereof, as used herein, can include wireless coupling, connection, or response. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions can not be described in detail for brevity and / or clarity. The term "and / or" (abbreviated as " / ") includes any and all combinations of one or more of the associated listed items.

[0344] It will be understood that, although the terms "first", "second", "third", and the like can be used herein to describe various elements / operations, these elements / operations should not be limited by these terms. These terms are only used to distinguish one element / operation from another. Thus, a first element / operation in some embodiments could be termed a second element / operation in other embodiments without departing from the teachings of the present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

[0345] As used herein the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein the common shorthand "e.g.", derived from the Latin phrase "exempli gratia", can be used to introduce or expressly state one or more examples of a preceding statement to provide an indication of the nature of the items being described, and is not intended to be limiting of such items. The common shorthand "i.e.", derived from the Latin phrase "id est", can be used to explicitly specify a particular item from a more general recitation.

[0346] The computer program instructions can also be loaded onto a computer and / or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and / or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer and / or other programmable apparatus provide steps for implementing the functions / acts specified in the block diagrams and / or flowchart block or blocks. Alternatively, computer program instmctions can be uploaded to the computer and / or other programmable data processing apparatus by the

[0347] These computer program instructions can also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions / acts specified in the block diagrams and / or flowchart illustrations. Accordingly, embodiments of the present inventive concepts can be embodied in hardware and / or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which can collectively be referred to as "circuitry," "module" or variants thereof.

[0348] It should also be noted that in some alternative implementations, the functions / acts shown in the blocks can be performed in an order different than that which is illustrated. For example, two blocks shown in succession can in fact be executed substantially concurrently or the actions of a block can be performed more or less concurrently than shown. Also, the functionality of given blocks can be split between multiple blocks and / or combinations of blocks and / or spread out amongst the blocks in a manner which differs from that which is described. Finally, the functionality of the blocks of the flowcharts and / or diagrams can be combined with the functionality of other blocks in a manner which is not explicitly described. In addition, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication can occur in the opposite direction to the arrows depicted. For example, if the top of a block has an arrow pointing downward, communication can be sent from the bottom of that block to the top of it.

[0349] Many modifications and variations of the described embodiments are possible without departing from the principles of the present inventive concepts. All such modifications and variations are intended to be included herein within the scope of the present inventive concepts. Accordingly, it should be understood that the above-disclosed subject matter is illustrative only and not restrictive. The examples of the embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of the present inventive concepts. Thus, to the maximum extent allowed by law, the scope of the present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of the embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims

1. A method for operating a first network node in a communication network including a second network node, the method comprising: Receive information associated with a communication device connected to the second network node; Based on the information, determine the configuration of the second network node relative to the communication device; as well as The configuration instruction is transmitted to the second network node via an intent-based interface, wherein the intent-based interface includes the A1 interface. The method further includes: transmitting configuration information to the second network node via a management interface before receiving the information associated with the communication device. The transmission of the configuration information includes transmitting a mapping of multiple functional control values ​​to the functionality of the second network node, and The instruction to transmit the configuration includes transmitting one of the plurality of functional control values.

2. The method of claim 1, wherein, The instruction to transmit the configuration includes an instruction to transmit a configuration policy associated with the communication device.

3. The method as described in claim 1, wherein, The information associated with the communication device includes information associated with at least one of the following: the context of the communication device, the quality of service category identifier associated with the communication device, the characteristics of the service between the communication device and the second network node, and the services provided to the communication device.

4. The method of claim 1, wherein, Receiving the information associated with the communication device includes receiving a first portion of the information from a service server associated with a service provided to the communication device via the second network node.

5. The method according to any one of claims 1-4, wherein, Receiving the information associated with the communication device includes receiving a second portion of the information from a core network node associated with the second network node.

6. The method according to any one of claims 1-4, wherein, The communication network is a fifth-generation 5G network. The first network node is an Operation Support System (OSS) node, and The second network node is a RAN node.

7. The method according to any one of claims 1-4, wherein, The first network node includes a non-real-time RAN intelligent controller. The second network node includes a near-real-time RAN intelligent controller, and The intent-based interface is located between the non-real-time RAN intelligent controller and the near-real-time RAN intelligent controller.

8. The method according to any one of claims 1-4, wherein, The management interface includes the O1 interface.

9. A method for operating a second network node in a communication network including a first network node, the method comprising: Communicating with the communication device based on the first configuration; Receive an indication of a second configuration from the first network node via an intent-based interface, wherein the intent-based interface includes an A1 interface; as well as In response to receiving the instruction of the second configuration, communicate with the communication device based on the second configuration. The method further includes: receiving configuration information from the first network node via a management interface before communicating with the communication device based on the first configuration. Specifically, communicating with the communication device based on the first configuration includes determining the first configuration based on the configuration information. Receiving the configuration information includes receiving a mapping of multiple functional control values ​​to the functionality of the second network node, and The instruction to receive the second configuration includes receiving one of the plurality of functional control values.

10. The method of claim 9, wherein, Receiving the instruction for the second configuration includes receiving an instruction for a configuration policy associated with the communication device.

11. The method of claim 9, wherein, The communication network is a fifth-generation 5G network. The first network node is an Operation Support System (OSS) node, and The second network node is the second RAN node.

12. The method according to any one of claims 9-11, wherein, The first network node includes a non-real-time RAN intelligent controller. The second network node includes a near-real-time RAN intelligent controller, and The intent-based interface is located between the non-real-time RAN intelligent controller and the near-real-time RAN intelligent controller.

13. The method according to any one of claims 9-11, wherein, The management interface includes the O1 interface.

14. A first network node operating in a communication network including a second network node, the first network node comprising: Processing circuitry; as well as A memory coupled to the processing circuit has instructions stored therein, which can be executed by the processing circuit to cause the first network node to perform the method as described in any one of claims 1-8.

15. A first network node operating in a communication network including a second network node, the first network node being adapted to perform the method as described in any one of claims 1-8.

16. A computer program product comprising program code to be executed by processing circuitry of a first network node operating in a communication network including a second network node, wherein execution of the program code causes the first network node to perform the method as described in any one of claims 1-8.

17. A non-transitory storage medium storing program code to be executed by processing circuitry of a first network node operating in a communication network including a second network node, wherein execution of the program code causes the first network node to perform the method as described in any one of claims 1-8.

18. A second network node operating in a communication network including a first network node, the second network node comprising: Processing circuitry; as well as A memory coupled to the processing circuit has instructions stored therein, which can be executed by the processing circuit to cause the second network node to perform the method as described in any one of claims 9-13.

19. A second network node operating in a communication network including a first network node, the second network node being adapted to perform the method as described in any one of claims 9-13.

20. A computer program product comprising program code to be executed by processing circuitry of a second network node operating in a communication network including a first network node, wherein execution of the program code causes the second network node to perform the method as described in any one of claims 9-13.

21. A non-transitory storage medium storing program code to be executed by processing circuitry of a second network node operating in a communication network including a first network node, wherein execution of the program code causes the second network node to perform the method as described in any one of claims 9-13.

Images