Sidelink Settings for Dual Connectivity

Abstract

To provide a method for sidelink configuration in dual connectivity in a wireless communication system, a wireless device, and a network node.SOLUTION: In a wireless communication network, a wireless device (12A) receives sidelink configurations from each of a plurality of network nodes (20A, 20B) serving the wireless device (12A), selects a sidelink configuration (16A) that matches or conforms to the sidelink configuration (16B) of another wireless device (12B) with which the wireless device (12A) will communicate via the sidelink from the received sidelink configurations, and transmits an indication of the selected sidelink configuration (16A) to each of one or more of the network nodes (20A, 20B) serving the wireless device (12A).SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present application relates generally to dual connectivity in wireless communication systems, and more particularly to sidelink configuration in dual connectivity. [Background technology]

[0002] A sidelink is a link between wireless devices that enables device-to-device (D2D) discovery and / or communication. When the wireless device is in network coverage, the network may configure a sidelink for the wireless device, e.g., with respect to Quality of Service (QoS) parameters associated with each sidelink QoS flow, sidelink radio bearer configuration, sidelink QoS flow-to-sidelink radio bearer mapping, etc. However, network control of sidelink configuration has proven to be complex in some contexts. For example, if wireless devices that are to communicate over the sidelink are served by different network nodes, the wireless devices are at risk of ending up with incompatible sidelink configurations. Summary of the Invention

[0003] Some embodiments herein control, coordinate, select or otherwise provide sidelink configurations of wireless devices that are to communicate with each other via a sidelink, e.g., such that the sidelink configurations of the wireless devices are aligned or compatible with each other. For example, some embodiments centrally control the sidelink configurations of the wireless devices from the same network node. For example, when at least one of the wireless devices has multiple serving nodes in a multi-connectivity operation, some embodiments control the sidelink configuration of the wireless device from any of the serving nodes that also serve the other wireless device(s) with which the sidelink communication is to be performed. In contrast, in other embodiments, which may be applicable even when the wireless devices do not have a common serving node, the serving nodes for the respective wireless devices may coordinate with each other regarding the sidelink configuration to be used, e.g., in a distributed manner. In still other embodiments, the wireless devices may receive different expected sidelink configurations from different respective network nodes and select any of those sidelink configurations that are aligned or compatible with the sidelink configuration of another wireless device with which the sidelink communication is to be performed. Ensuring consistency or compatibility between sidelink configurations of wireless devices in this manner may advantageously avoid configuration failures and service latency.

[0004] More specifically, embodiments herein include a method implemented by a wireless device. The method includes receiving a sidelink configuration from each of a plurality of network nodes serving the wireless device. The method also includes selecting, from the received sidelink configurations, a sidelink configuration that matches or fits a sidelink configuration of another wireless device with which the wireless device is to communicate over the sidelink. The method also includes, in some embodiments, transmitting an indication of the selected sidelink configuration to one or more of each of the network nodes serving the wireless device.

[0005] In some embodiments, the sidelink configuration includes a radio link control (RLC) mode configuration that includes a configuration of an RLC unacknowledged mode or an RLC acknowledged mode. In one or more of these embodiments, selecting a sidelink configuration includes selecting from the received sidelink configurations a sidelink configuration that includes an RLC mode setting that is the same as an RLC mode setting of a sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink.

[0006] In some embodiments, the sidelink configuration includes a Logical Channel ID to RLC mode mapping. In this case, selecting a sidelink configuration includes selecting, from the received sidelink configurations, a sidelink configuration that includes the same Logical Channel ID to RLC mode mapping as a sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink.

[0007] In some embodiments, the sidelink configuration includes at least one of any one or more of a sidelink radio bearer configuration, a quality of service flow to sidelink radio bearer mapping, configuration of a resource pool for sidelink communication, a Radio Link Control (RLC) mode configuration including configuration of RLC unacknowledged or RLC acknowledged mode, a logical channel ID to RLC mode mapping, and default sidelink configuration parameters.

[0008] In some embodiments, at least one of the network nodes acts as a master node for multi-connectivity operations and at least one other of the network nodes acts as a secondary node for said multi-connectivity operations.

[0009] In some embodiments, the method further includes requesting a sidelink configuration from each of the plurality of network nodes.

[0010] In some embodiments, the method further includes receiving, from each of one or more of the network nodes serving the wireless device, information identifying one or more other wireless devices to which the network node has sent the same sidelink configuration received from the network node.

[0011] Other embodiments herein include a method implemented by a network node, the method including receiving, from a wireless device, an indication of a sidelink configuration selected by the wireless device as matching or adapting to a sidelink configuration of another wireless device with which the wireless device is to communicate over a sidelink.

[0012] In some embodiments, the sidelink configuration includes a radio link control (RLC) mode configuration that includes a configuration of an RLC unacknowledged mode or an RLC acknowledged mode. In one or more of these embodiments, the indication includes an indication of a sidelink configuration selected by the wireless device as having the same RLC mode setting as an RLC mode setting of a sidelink configuration of another wireless device with which the wireless device will communicate over the sidelink.

[0013] In some embodiments, the sidelink configuration includes a logical channel ID-to-RLC mode mapping, and the indication includes an indication of the sidelink configuration selected by the wireless device as having the same logical channel ID-to-RLC mode mapping as a logical channel ID-to-RLC mode mapping of a sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink.

[0014] In some embodiments, the sidelink configuration includes at least one of any one or more of a sidelink radio bearer configuration, a quality of service flow-to-sidelink radio bearer mapping, a resource pool configuration for sidelink communications, a radio link control (RLC) mode configuration including configuration of an RLC unacknowledged mode or an RLC acknowledged mode, a logical channel ID-to-RLC mode mapping, and default sidelink configuration parameters.

[0015] In some embodiments, the network node acts as a master node for multi-connectivity operations.

[0016] In some embodiments, the network node acts as a secondary node for multi-connectivity operations.

[0017] In some embodiments, the method further comprises transmitting, to the wireless device, information identifying one or more other wireless devices to which the network node has sent the same sidelink configuration as the sidelink configuration transmitted to the wireless device.

[0018] Other embodiments herein include a wireless device configured to receive a sidelink configuration from each of a plurality of network nodes serving the wireless device. The wireless device is also configured to select from the received sidelink configurations a sidelink configuration that matches or fits a sidelink configuration of another wireless device with which the wireless device is to communicate over the sidelink. The wireless device is also configured to transmit an indication of the selected sidelink configuration to each of one or more of the network nodes serving the wireless device.

[0019] In some embodiments, the wireless device is configured to perform the steps described above for the wireless device.

[0020] Other embodiments herein include a network node configured to receive, from a wireless device, an indication of a sidelink configuration selected by the wireless device as matching or adapting to a sidelink configuration of another wireless device with which the wireless device is to communicate via a sidelink.

[0021] In some embodiments, the network node is configured to perform the steps described above for the network node.

[0022] Other embodiments herein include a computer program comprising instructions that, when executed by at least one processor of a wireless device, cause the wireless device to perform the steps described above for the wireless device. Other embodiments herein include a computer program comprising instructions that, when executed by at least one processor of a network node, cause the network node to perform the steps described above for the network node. Other embodiments herein include a carrier comprising any of the computer programs described above, the carrier being one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

[0023] Other embodiments herein include a wireless device comprising a communication circuit and a processing circuit. The processing circuit is configured to receive a sidelink configuration from each of a plurality of network nodes serving the wireless device. The processing circuit is also configured to select, from the received sidelink configurations, a sidelink configuration that matches or adapts to a sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink. The processing circuit is also configured in some embodiments to transmit an indication of the selected sidelink configuration to each of one or more of the network nodes serving the wireless device.

[0024] In some embodiments, the processing circuitry is configured to perform the steps described above for the wireless device.

[0025] Other embodiments herein include a network node comprising a communication circuit and a processing circuit configured to receive, from a wireless device, an indication of a sidelink configuration selected by the wireless device as matching or adapting to a sidelink configuration of another wireless device with which the wireless device is to communicate over a sidelink.

[0026] In some embodiments, the processing circuitry is configured to perform the steps described above for the network node.

[0027] Of course, the present invention is not limited to the above features and advantages, and indeed those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings. [Brief description of the drawings]

[0028] [Figure 1] 1 is a block diagram of a wireless communication network according to some embodiments. [Diagram 2] 4 is a block diagram of a wireless communication network according to another embodiment. [Diagram 3] FIG. 2 is a logic flow diagram of a method implemented by a network node according to some embodiments. [Figure 4] FIG. 11 is a logic flow diagram of a method implemented by a network node according to another embodiment. [Diagram 5] FIG. 11 is a logic flow diagram of a method performed by a network node according to yet another embodiment. [Figure 6] 4 is a logic flow diagram of a method implemented by a wireless device according to some embodiments. [Figure 7A] 11 is a logic flow diagram of a method implemented by a wireless device according to another embodiment. [Figure 7B] FIG. 11 is a logic flow diagram of a method implemented by a network node according to another embodiment. [Figure 8]1 is a block diagram of a wireless device according to some embodiments. [Figure 9] FIG. 2 is a block diagram of a network node according to some embodiments. [Figure 10] 1 is a block diagram of different ways to deploy 5G networks with or without interworking with LTE, according to some embodiments. [Figure 11] FIG. 1 is a block diagram of a control plane architecture for LTE DC and EN-DC, according to some embodiments. [Figure 12] FIG. 2 is a block diagram of a user plane (UP) architecture for an EN-DC, according to some embodiments. [Figure 13] FIG. 2 is a block diagram of a control plane (CP) architecture for an EN-DC, according to some embodiments. [Figure 14] FIG. 1 is a block diagram of a system with short-range and long-range V2X service transmission, according to some embodiments. [Figure 15] FIG. 13 is a block diagram of a process for sidelink radio bearer setup according to some embodiments. [Figure 16A] FIG. 1 is a block diagram illustrating centrally controlling sidelink configuration of wireless devices from the same network node according to some embodiments. [Figure 16B] FIG. 1 is a block diagram illustrating coordination between wireless devices regarding a sidelink configuration to be used, according to some embodiments. [Figure 16C] FIG. 13 is a block diagram illustrating selection by a wireless device of a sidelink configuration that matches or is compatible with a sidelink configuration of another wireless device, according to some embodiments. [Figure 17] 1 is a block diagram of a wireless communication network according to some embodiments. [Figure 18] FIG. 2 is a block diagram of a user equipment according to some embodiments. [Figure 19] FIG. 1 is a block diagram of a virtualization environment, according to some embodiments. [Figure 20] 1 is a block diagram of a communications network having a host computer according to some embodiments. [Figure 21] FIG. 2 is a block diagram of a host computer, according to some embodiments. [Figure 22] 1 is a flow chart illustrating a method implemented in a communication system according to one embodiment. [Diagram 23] 1 is a flow chart illustrating a method implemented in a communication system according to one embodiment. [Figure 24] 1 is a flow chart illustrating a method implemented in a communication system according to one embodiment. [Diagram 25] 1 is a flow chart illustrating a method implemented in a communication system according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] 1 illustrates a wireless communication system 10, e.g., a Long Term Evolution (LTE) system or a New Radio (NR) system, according to some embodiments. In this example, a wireless device 12A will communicate with a wireless device 12B over a sidelink 14. Communication over the sidelink 14 means that the wireless devices 12A, 12B communicate directly with each other, rather than over a path that traverses any network node (e.g., a base station). Such communication may include, for example, user plane communication, e.g., in the form of Proximity Services (ProSe) direct communication.

[0030] The wireless devices 12A, 12B will communicate with each other over the sidelink 14 according to respective sidelink configurations 16A, 16B. The sidelink configuration 16A configures the configuration of the sidelink 14 at or from the perspective of the wireless device 12A, while the sidelink configuration 16B configures the configuration of the sidelink 14 at or from the perspective of the wireless device 12B. Each of the sidelink configurations 16A, 16B may include, for example, one or more of: (i) sidelink radio bearer configuration, (ii) quality of service flow-to-sidelink radio bearer mapping, (iii) configuration of a resource pool for sidelink communications, (iv) radio link control (RLC) mode configuration, including configuration of RLC unacknowledged or RLC acknowledged mode, (v) logical channel ID-to-RLC mode mapping, or (vi) default sidelink configuration parameters.

[0031] Some embodiments herein control, coordinate, select or otherwise provide the sidelink configurations 16A, 16B of the wireless devices 12A, 12B to be consistent or compatible with each other. The sidelink configurations 16A, 16B are consistent or compatible with each other if those sidelink configurations 16A, 16B enable the wireless devices 12A, 12B to establish sidelink connectivity without error and thus avoid configuration failures. The consistency or compatibility mentioned in some embodiments may thereby mean that the sidelink configurations 16A, 16B are fully consistent or compatible with each other. In some embodiments, for example, the sidelink configurations 16A, 16B are consistent or compatible with each other if, for each of one or more parameters, that parameter has the same value in both sidelink configurations 16A, 16B. For example, in embodiments where the sidelink configuration 16A, 16B includes an RLC mode configuration for the sidelink 14, the sidelink configurations 16A, 16B are consistent or compatible with each other if the sidelink configurations 16A, 16B configure the same RLC mode for the sidelink 14, e.g. if the sidelink configurations 16A and 16B both configure an RLC unacknowledged mode for the sidelink 14 or both configure an RLC acknowledged mode for the sidelink 14. Additionally or alternatively, in embodiments where the sidelink configuration 16A, 16B includes a logical channel ID to RLC mode mapping for the sidelink 14, the sidelink configurations 16A, 16B are consistent or compatible with each other if the sidelink configurations 16A, 16B configure the same logical channel ID to RLC mode mapping.As yet another example, in embodiments in which the sidelink configurations 16A, 16B include default sidelink configuration parameters, the sidelink configurations 16A, 16B are consistent or compatible with each other if the sidelink configurations 16A, 16B additionally or alternatively configure the same values ​​for the default sidelink configuration parameters, e.g., both sidelink configurations 16A, 16B configure PDCP Replication to be “on” by default or both sidelink configurations 16A, 16B configure SDAP headers to be “present” by default. Regardless of the nature of the consistency or compatibility, ensuring consistency or compatibility between sidelink configurations of the wireless devices in this manner may advantageously avoid configuration failures and service latency.

[0032] For example, some embodiments centrally control sidelink configuration of wireless devices 12A, 12B from the same network node. As shown in one example, wireless device 12A is served by multiple radio network nodes 20A, 20B, e.g., in multi-connectivity operation. In particular, radio network node 20A serves as a master node (MN) for wireless device 12A, and radio network node 20B serves as a secondary node (SN) for wireless device 12B. Wireless device 12B, in contrast, may be served only by radio network node 20B, as shown, or may also operate in multi-connectivity. In either case, some embodiments control sidelink configuration of wireless devices 12A, 12B from whichever of radio network nodes 20A, 20B typically serves both wireless devices 12A, 12B. In this example, the radio network node 20B then controls the sidelink configurations of both the wireless devices 12A and 12B on the basis that the radio network node 20B serves both the wireless devices 12A and 12B, which means that the radio network node 20B may centrally control the sidelink configurations 16A, 16B to be consistent or compatible with each other.

[0033] It should be noted that the radio network node 20B may in some embodiments control the sidelink configurations 16A, 16B in the sense that the radio network node 20B governs, defines or otherwise controls the parameters of those configurations. The radio network node 20B does not necessarily have to generate or even transmit the sidelink configurations 16A, 16B to the wireless devices 12A, 12B. In some embodiments, for example, the radio network node 20B generates a sidelink configuration 16A for the wireless device 12A, but transmits it to the radio network node 20A for relaying to the wireless device 12A, for example, in an encapsulated RRC message.

[0034] 3 illustrates a method implemented by the network node 20B according to a particular embodiment. The method includes controlling (block 320) the sidelink configurations 16A, 16B of each of a plurality of wireless devices 12A, 12B that are to communicate with each other via the sidelink 14. In some embodiments, this controlling includes controlling the sidelink configurations 16A, 16B of the plurality of wireless devices 12A, 12B to be consistent or compatible with each other.

[0035] In some embodiments, such control is based on the network node 20B serving each of a plurality of wireless devices 12A, 12B.

[0036] In some embodiments, the method may previously include determining (block 310) to control sidelink configurations of each of the multiple wireless devices 12A, 12B by the network node 20B based on the network node 20B serving each of the multiple wireless devices 12A, 12B.

[0037] In some embodiments, at least one of the plurality of wireless devices 12A, 12B is served by a network node and one or more other network nodes.

[0038] In some embodiments, the network node 20B acts as a master node for at least one of the plurality of wireless devices 12A, 12B in multi-connectivity operation. In one such embodiment, the network node 20B acts as a secondary node for at least one other of the plurality of wireless devices 12A, 12B in multi-connectivity operation.

[0039] In other embodiments, at least one of the multiple wireless devices 12A, 12B is not configured for multi-connectivity or is not operating in multi-connectivity.

[0040] In either case, the method, in some embodiments, further includes determining that the multiple wireless devices 12A, 12B will be communicating with one another over the sidelink based at least in part on information received from another network node (block 300). The information received from the other network node may include, for example, identifying information, e.g., Layer 2 identity, that identifies at least one of the multiple wireless devices 12A, 12B.

[0041] In some embodiments, the method further includes sending an indication to each of one or more of the multiple wireless devices 12A, 12B instructing the network node 20B to control a sidelink configuration of the wireless device or instructing the network node 20B to control a sidelink configuration of each of the multiple wireless devices 12A, 12B (block 330).

[0042] In some embodiments, the network node 20B is a central or distributed unit of a wireless network node.

[0043] In some embodiments, the controlling includes generating a sidelink configuration for each of the plurality of wireless devices 12A, 12B and transmitting the sidelink configuration to the wireless device or to another network node for relay to the wireless device.

[0044] In some embodiments, the controlling includes controlling sidelink configurations of the multiple wireless devices 12A, 12B to match or adapt to one another.

[0045] In some embodiments, the sidelink configuration of the wireless device includes one or more of a sidelink radio bearer configuration, a quality of service flow-to-sidelink radio bearer mapping, a resource pool configuration for sidelink communications, a radio link control (RLC) mode configuration including configuration of an RLC unacknowledged mode or an RLC acknowledged mode, a logical channel ID-to-RLC mode mapping, or default sidelink configuration parameters.

[0046] In some embodiments, multiple wireless devices 12A, 12B are requesting or have requested a sidelink configuration for the purpose of communicating with each other via the sidelink.

[0047] 4 illustrates a method implemented by a network node according to another particular embodiment. The method includes selecting a network node from among a plurality of candidate network nodes to control sidelink configurations of each of a plurality of wireless devices 12A, 12B that will communicate with each other via a sidelink (block 410). In some embodiments, the selecting includes selecting a network node that serves each of the plurality of wireless devices 12A, 12B.

[0048] In some embodiments, the method also includes transmitting information to one or more of the candidate network nodes and / or to one or more of the wireless devices 12A, 12B indicating the network node selected to control the sidelink configuration of each of the multiple wireless devices 12A, 12B (block 420).

[0049] In some embodiments, at least one of the multiple wireless devices 12A, 12B is served by multiple network nodes in multi-connectivity operation.

[0050] In some embodiments, the selected network node serves as a master node for at least one of the multiple wireless devices 12A, 12B in multi-connectivity operation.

[0051] In some embodiments, the selected network node serves as a secondary node for at least one other of the plurality of wireless devices 12A, 12B in multi-connectivity.

[0052] In some embodiments, at least one of the multiple wireless devices 12A, 12B is not configured for multi-connectivity or is not operating in multi-connectivity.

[0053] In some embodiments, the method includes determining, based at least in part on information received from another network node, that the multiple wireless devices 12A, 12B will be communicating with each other over a sidelink (block 400). In some embodiments, for example, the information received from the other network node includes identification information that identifies at least one of the multiple wireless devices 12A, 12B. For example, the identification information may include Layer 2 identification information of at least one of the multiple wireless devices 12A, 12B.

[0054] In some embodiments, the method further includes sending an indication to each of one or more of the multiple wireless devices 12A, 12B indicating a network node selected to control a sidelink configuration of the wireless device or indicating a network node selected to control a sidelink configuration of each of the multiple wireless devices 12A, 12B.

[0055] In some embodiments, the selected network node is a central unit or a distributed unit of a radio network node.

[0056] In some embodiments, the network node selected to control the sidelink configuration of each of the plurality of wireless devices 12A, 12B is selected to generate, for each of the plurality of wireless devices 12A, 12B, a sidelink configuration and to transmit the sidelink configuration to the wireless device.

[0057] In some embodiments, the network node selected to control the sidelink configuration of each of the multiple wireless devices 12A, 12B is selected to control the sidelink configurations of the multiple wireless devices to be consistent or compatible with each other.

[0058] In some embodiments, the sidelink configuration of the wireless device includes one or more of a sidelink radio bearer configuration, a quality of service flow-to-sidelink radio bearer mapping, a resource pool configuration for sidelink communications, a radio link control (RLC) mode configuration including configuration of an RLC unacknowledged mode or an RLC acknowledged mode, a logical channel ID-to-RLC mode mapping, or default sidelink configuration parameters.

[0059] In some embodiments, multiple wireless devices 12A, 12B are requesting or have requested a sidelink configuration for the purpose of communicating with each other via the sidelink.

[0060] In some embodiments, the selecting is performed in response to receiving a request for sidelink configuration from one or more of the multiple wireless devices 12A, 12B.

[0061] In some embodiments, the selecting is performed in response to receiving a query from one of the candidate network nodes inquiring as to which network node will control the sidelink configuration of each of the multiple wireless devices 12A, 12B.

[0062] In some embodiments, the selecting is performed as part of setting up a sidelink between the wireless devices 12A, 12B, as part of a procedure for modifying which network node serves as a master node for multi-connectivity operation of at least one of the wireless devices, or as part of a procedure for adding or modifying which network node serves as a secondary node for multi-connectivity operation of at least one of the wireless devices 12A, 12B.

[0063] In contrast, in other embodiments, which may be applicable even in the embodiment shown in Figure 2 where the wireless devices 12A, 12B do not have a common serving node, the serving nodes 24A, 24B for the respective wireless devices 12A, 12B may coordinate with each other (e.g., via a node-to-node interface) regarding the sidelink configuration 16A, 16B to be used, e.g., in a distributed manner 22. That is, rather than one of the network nodes 24A, 24B centrally controlling both sidelink configurations 16A, 16B, the network nodes 24A, 24B coordinate with each other such that the sidelink configurations 16A, 16B are consistent or compatible with each other.

[0064] 5, for example, illustrates a method implemented by a network node 24A according to these other embodiments. The method includes coordinating with a second network node 24B regarding sidelink configuration for each of a plurality of wireless devices 12A, 12B that will communicate with each other via the sidelink (block 500).

[0065] In some embodiments, the coordinating includes sending information to the second network node 24B indicating one or more sidelink configurations that may be used at the first network node 24A and / or receiving information from the second network node 24B indicating one or more sidelink configurations that may be used at the second network node 24B. Alternatively or additionally, in some embodiments, the coordinating includes sending information to the second network node 24B indicating one or more sidelink configurations that the second network node 24B is to use and / or receiving information from the second network node 24B indicating one or more sidelink configurations that the first network node 24A is to use. Alternatively or additionally, in some embodiments, the coordinating includes sending information to the second network node 24B indicating one or more sidelink configurations that the first network node 24A proposes to use and / or receiving information from the second network node 24B indicating one or more sidelink configurations that the second network node 24B proposes to use. Alternatively or additionally, in some embodiments, this coordinating includes sending information to the second network node 24B indicating one or more sidelink configurations that the first network node 24A will accept or reject for use, and / or receiving information from the second network node 24B indicating one or more sidelink configurations that the second network node 24B will accept or reject for use.

[0066] In some embodiments, the method further includes determining a sidelink configuration 16A, 16B for each of one or more of the plurality of wireless devices 12A, 12B served by the first network node 24A based on the coordinating (block 510). In this case, the method may also include transmitting the determined sidelink configuration towards each of the one or more of the plurality of wireless devices 12A, 12B served by the first network node 24A (block 520).

[0067] For example, in some embodiments, the first network node 24A determines a sidelink configuration 16A for the wireless device 12A based on information received from the second network node 24B indicating a sidelink configuration 16B that the second network node 24B is able to use, proposes to use, or allows for use. This sidelink configuration 16B may, for example, be a sidelink configuration that the second network node 24B proposes to use for other wireless devices 12B served by the second network node 24B.

[0068] In some embodiments, the first network node acts as a master node for at least one of the plurality of wireless devices 12A, 12B in multi-connectivity operation, and the second network node acts as a secondary node for at least one other of the plurality of wireless devices 12A, 12B in multi-connectivity operation.

[0069] In some embodiments, at least two of the wireless devices 12A, 12B do not have a common serving network node.

[0070] In some embodiments, the coordinating is performed during or as part of a procedure for adding or modifying a second node for at least one of the multiple wireless devices 12A, 12B in multi-connectivity.

[0071] In some embodiments, the coordinating is performed during or as part of a procedure for handover of one or more of the multiple wireless devices 12A, 12B.

[0072] In some embodiments, at least one of the multiple wireless devices 12A, 12B is served by multiple network nodes.

[0073] In some embodiments, the sidelink configuration of the wireless device includes one or more of a sidelink radio bearer configuration, a quality of service flow-to-sidelink radio bearer mapping, a resource pool configuration for sidelink communications, a radio link control (RLC) mode configuration including configuration of an RLC unacknowledged mode or an RLC acknowledged mode, a logical channel ID-to-RLC mode mapping, or default sidelink configuration parameters.

[0074] In some embodiments, multiple wireless devices 12A, 12B are requesting or have requested a sidelink configuration for the purpose of communicating with each other via the sidelink.

[0075] 6 illustrates a method implemented by a wireless device according to yet another particular embodiment. The method includes receiving an indication from a network node indicating which network node controls a sidelink configuration of the wireless device (block 600).

[0076] In some embodiments, at least one of the network nodes acts as a master node for multi-connectivity operations and at least one other of the network nodes acts as a secondary node for said multi-connectivity operations.

[0077] In some embodiments, the sidelink configuration includes one or more of a sidelink radio bearer configuration, a quality of service flow-to-sidelink radio bearer mapping, a resource pool configuration for sidelink communication, a radio link control (RLC) mode configuration including configuration of RLC unacknowledged or RLC acknowledged mode, a logical channel ID-to-RLC mode mapping, or default sidelink configuration parameters.

[0078] In yet other embodiments not shown, the wireless device 12A may receive different expected sidelink configurations from different respective network nodes 24A, 24B and select any of those sidelink configurations that match or fit the sidelink configuration 16B of the wireless device 12B over which sidelink communication is to be performed. In this case, the wireless device 12A may then itself evaluate and / or ensure the consistency or compatibility of the sidelink configurations 16A, 16B with each other. The wireless device 12A may also, in some embodiments, report the selected sidelink configuration to one or more of the network nodes 24A, 24B, e.g., for use by the network node(s) in sidelink configuration or otherwise.

[0079] 7A illustrates a method implemented by a wireless device 12A according to yet another particular embodiment. The method includes receiving a sidelink configuration from each of a plurality of network nodes 24A, 24B serving the wireless device 12A (block 700). The method also includes selecting a sidelink configuration 16A from the received sidelink configurations that matches or fits a sidelink configuration 16B of another wireless device 12B with which the wireless device 12A is to communicate via the sidelink 14 (block 710). The method may further include transmitting an indication of the selected sidelink configuration 16A to each of one or more of the network nodes 24A, 24B serving the wireless device 12A (block 720).

[0080] In some embodiments, the method further includes requesting a sidelink configuration from each of the multiple network nodes 24A, 24B.

[0081] In some embodiments, the method further includes receiving, from each of one or more of the network nodes 24A, 24B serving the wireless device 12A, information identifying one or more other wireless devices to which the network node sent the same sidelink configuration received from that network node.

[0082] In some embodiments, at least one of the network nodes 24A, 24B acts as a master node for multi-connectivity operations and at least one other of the network nodes acts as a secondary node for said multi-connectivity operations.

[0083] In some embodiments, the sidelink configuration includes one or more of a sidelink radio bearer configuration, a quality of service flow-to-sidelink radio bearer mapping, a resource pool configuration for sidelink communication, a radio link control (RLC) mode configuration including configuration of RLC unacknowledged or RLC acknowledged mode, a logical channel ID-to-RLC mode mapping, or default sidelink configuration parameters.

[0084] 7B illustrates a method implemented by a network node according to yet another particular embodiment. The method includes receiving (block 750) from a wireless device 12A an indication of a sidelink configuration 16A selected by the wireless device 12A as matching or adapting to a sidelink configuration 16B of another wireless device 12B with which the wireless device 12A is to communicate via the sidelink 14. In some embodiments, the method further includes controlling a sidelink configuration of the wireless device 12A and / or the other wireless device 12B based on the received indication (block 760).

[0085] In some embodiments, the method further includes transmitting to the wireless device 12A information identifying one or more other wireless devices to which the network node sent the same sidelink configuration.

[0086] In some embodiments, a network node acts as a master node for multi-connectivity operations and at least one other of the network nodes acts as a secondary node for said multi-connectivity operations.

[0087] In some embodiments, the sidelink configuration includes one or more of a sidelink radio bearer configuration, a quality of service flow-to-sidelink radio bearer mapping, a resource pool configuration for sidelink communication, a radio link control (RLC) mode configuration including configuration of RLC unacknowledged or RLC acknowledged mode, a logical channel ID-to-RLC mode mapping, or default sidelink configuration parameters.

[0088] The embodiments herein also include corresponding apparatus, for example, a wireless device configured to perform any of the steps of any of the embodiments described above for the wireless device.

[0089] The embodiments also include a wireless device 12A or 12B comprising a processing circuit and a power supply circuit. The processing circuit is configured to perform any of the steps of any of the embodiments described above for the wireless device 12A or 12B. The power supply circuit is configured to supply power to the wireless device 12A or 12B.

[0090] The embodiments further include the wireless device 12A or 12B comprising a processing circuit configured to perform any of the steps of any of the embodiments described above for the wireless device 12A or 12B. In some embodiments, the wireless device 12A or 12B further comprises a communication circuit.

[0091] The embodiments further include a wireless device 12A or 12B comprising a processing circuit and a memory, the memory including instructions executable by the processing circuit to configure the wireless device 12A or 12B to perform any of the steps of any of the embodiments described above for the wireless device 12A or 12B.

[0092] The embodiments further include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises a radio front-end circuit connected to the antenna and the processing circuit and configured to condition signals communicated between the antenna and the processing circuit. The processing circuit is configured to perform any of the steps of any of the embodiments described above for the wireless device 12A or 12B. In some embodiments, the UE also comprises an input interface connected to the processing circuit and configured to allow input of information to the UE to be processed by the processing circuit. The UE may comprise an output interface connected to the processing circuit and configured to output information from the UE processed by the processing circuit. The UE may also comprise a battery connected to the processing circuit and configured to provide power to the UE.

[0093] Embodiments herein also include the radio network node 20A or 20B configured to perform any of the steps of any of the embodiments described above for the radio network node 20A or 20B.

[0094] The embodiments also include a radio network node 20A or 20B comprising a processing circuit and a power supply circuit. The processing circuit is configured to perform any of the steps of any of the embodiments described above for the radio network node 20A or 20B. The power supply circuit is configured to supply power to the radio network node 20A or 20B.

[0095] The embodiments further include the radio network node 20A or 20B comprising processing circuitry configured to perform any of the steps of any of the embodiments described above for the radio network node 20A or 20B. In some embodiments, the radio network node 20A or 20B further comprises communications circuitry.

[0096] The embodiments further include the radio network node 20A or 20B comprising a processing circuit and a memory, the memory including instructions executable by the processing circuit such that the radio network node 20A or 20B is configured to perform any of the steps of any of the embodiments described above for the radio network node 20A or 20B.

[0097] More specifically, the apparatus described above may perform the methods and any other processes herein by implementing any functional means, module, unit, or circuit. In one embodiment, for example, the apparatus comprises a respective circuit or circuitry configured to perform the steps illustrated in the method diagrams. The circuit or circuitry in this regard may comprise one or more microprocessors along with circuits and / or memories dedicated to performing certain functional processes. For example, the circuitry may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory may include, in some embodiments, program instructions for performing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In embodiments that employ memory, the memory stores program code that, when executed by one or more processors, performs the techniques described herein.

[0098] FIG. 8 illustrates, for example, a wireless device 800 (e.g., wireless device 12A or 12B) implemented according to one or more embodiments. As illustrated, the wireless device 800 includes a processing circuit 810 and a communication circuit 820. The communication circuit 820 (e.g., a radio circuit) is configured, for example, to transmit information to and / or receive information from one or more other nodes via any communication technology. Such communication may occur via one or more antennas either internal or external to the wireless device 800. The processing circuit 810 is configured to perform the processing described above, for example, in FIG. 3, FIG. 4, and / or FIG. 5, such as by executing instructions stored in a memory 830. The processing circuit 810 may implement several functional means, units, or modules in this regard.

[0099] FIG. 9 illustrates a network node 900 (e.g., radio network node 20A or 20B) implemented in accordance with one or more embodiments. As shown, the network node 900 includes a processing circuit 910 and a communication circuit 920. The communication circuit 920 is configured to transmit information to and / or receive information from one or more other nodes, e.g., via any communication technology. The processing circuit 910 is configured to perform the processing described above, e.g., in FIG. 6 or FIG. 7, such as by executing instructions stored in a memory 930. The processing circuit 910 may implement several functional means, units, or modules in this regard.

[0100] Those skilled in the art will also appreciate that the embodiments herein further include corresponding computer programs.

[0101] The computer program comprises instructions which, when executed on at least one processor of the apparatus, cause the apparatus to perform any of the respective operations described above. The computer program may in this respect comprise one or more code modules which correspond to the means or units described above.

[0102] Embodiments further include a carrier containing such a computer program, which may comprise one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0103] In this regard, embodiments herein also include a computer program product comprising instructions stored on a non-transitory computer-readable (storage or recording) medium that, when executed by a processor of the device, causes the device to perform as described above.

[0104] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. The computer program product may be stored on a computer-readable recording medium.

[0105] Next, additional embodiments are described, at least some of which may be described, for purposes of explanation, as applicable in certain contexts and / or wireless network types, although the embodiments are likewise applicable in other contexts and / or wireless network types not explicitly described.

[0106] Some embodiments herein are applicable to multi-connectivity. Multi-connectivity in this regard refers to simultaneous connection of a wireless device (e.g., at a radio resource control (RRC) layer) to multiple different radio network nodes or to multiple different cells provided by different radio network nodes. The multiple different radio network nodes or cells may use the same radio access technology (e.g., both may use Enhanced Universal Terrestrial Radio Access (E-UTRA) or both may use New Radio (NR)). Alternatively, the multiple different radio network nodes or cells may use different radio access technologies, for example, one may use E-UTRA and another may use NR.

[0107] An example of multi-connectivity is dual connectivity (DC), where a wireless device is simultaneously connected to two different radio network nodes or to two different cells provided by two different radio network nodes. In this case, a so-called master cell group (MCG) and a secondary cell group (SCG) may be configured in the wireless device, where the MCG includes one or more cells provided by a radio network node acting as a master node (MN), and the SCG includes one or more cells served by a radio network node acting as a secondary node (SN). The master node may be a master in the sense that it controls the secondary nodes and / or provides a control plane connection to the core network. For example, E-UTRA-NR(EN)DC refers to the case where the master node uses E-UTRA and the secondary node uses NR, while NR-E-UTRA(NE) refers to the case where the master node uses NR and the secondary node uses E-UTRA.

[0108] For example, in multi-connectivity operation, a wireless device with multiple receivers (Rx) and / or transmitters (Tx) may utilize radio resources in one or more radio access technologies (e.g., New Radio (NR) and / or E-UTRA) provided by multiple separate schedulers connected via a non-ideal backhaul. Multi-Radio Dual Connectivity (MR-DC) is a generalization of intra-E-UTRA DC in this regard, where a multi-Rx / Tx wireless device may be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, one providing NR access and the other providing either E-UTRA or NR access. One node serves as a master node (MN) and the other serves as a SN. E-UTRAN supports MR-DC via E-UTRA-NR Dual Connectivity (EN-DC), for example, where a wireless device is connected to one eNB serving as a MN and one en-gNB serving as a secondary node (SN). Either way, in MR-DC, the wireless device may have a single radio resource control (RRC) state based on the MN RRC and a single control plane connection towards the core network.

[0109] More specifically, some embodiments herein are applicable to multi-connectivity (e.g., dual connectivity) specified by the 3rd Generation Partnership Project (3GPP), for example, for Long Term Evolution (LTE) or between LTE and New Radio (NR). In dual connectivity (DC), two nodes are involved, namely, a master node (MN or MeNB) and a secondary node (SN, or SeNB). Multi-connectivity (MC) generally captures the case where there are two or more nodes involved. Also, in 3GPP, DC is proposed to be used in the case of ultra-reliable low-latency communication (URLLC) to improve robustness and avoid connection interruption.

[0110] The embodiments herein are applicable to any of several different ways to deploy 5G networks with or without interworking with LTE (also called E-UTRA) and Evolved Packet Core (EPC), as illustrated in FIG. 10. In principle, NR and LTE can be deployed without interworking, as indicated by NR Standalone (SA) operation, i.e., gNB in ​​NR can be connected to 5G Core Network (5GC) and eNB can be connected to EPC without interconnection between the two (options 1 and 2 in FIG. 10). Meanwhile, the first supported version of NR is so-called EN-DC (E-UTRAN-NR dual connectivity), as indicated by option 3 in FIG. 10. In such deployment, dual connectivity between NR and LTE is applied, with LTE as the master and NR as the secondary node. Radio Access Network (RAN) nodes (gNBs) supporting NR may not have a control plane connection to the core network (EPC), instead, the RAN nodes rely on LTE as the master node (MeNB). This is also called "non-standalone NR". Note that in this case, the functionality of the NR cells is limited and they are used for connected mode UEs as booster and / or diversity legs, but RRC_IDLE UEs cannot camp on these NR cells.

[0111] With the introduction of 5GC, other options are also valid and may be applicable to the embodiments herein. As mentioned above, option 2 supports standalone NR deployments where gNBs are connected to 5GC. Similarly, LTE may also be connected to 5GC using option 5 in FIG. 10 (also known as eLTE, E-UTRA / 5GC, or LTE / 5GC, where the node may be referred to as ng-eNB). In these cases, both NR and LTE are seen as part of the NG-RAN (and both ng-eNB and gNB may be referred to as NG-RAN nodes). It is worth noting that option 4 and option 7 in FIG. 10 are other variants of dual connectivity between LTE and NR that will be standardized as part of NG-RAN connected to 5GC, as indicated by MR-DC (Multiple Radio Dual Connectivity). In that case, under the MR-DC umbrella, the embodiments herein may be applicable as follows: EN-DC (Option 3): LTE is the master node and NR is the secondary (EPC CN adopted) NE-DC (Option 4): NR is the master node and LTE is the secondary (5GCN adopted) NGEN-DC (Option 7): LTE is the master node and NR is the secondary (5GCN adopted) NR-DC (variant of option 2): Dual connectivity (adopted by 5GCN), where both master and secondary are NR.

[0112] Since the migration for these options may be different for different operators, it is possible to have deployments with multiple options in parallel in the same network, for example, there may be an eNB base station supporting options 3, 5, and 7 in the same network as an NR base station supporting options 2 and 4. In combination with the dual connectivity solution between LTE and NR, it is also possible to support CA (carrier aggregation) in each cell group (i.e., master cell group (MCG) and secondary cell group (SCG)) and dual connectivity between nodes on the same radio access technology (RAT) (e.g., NR-NR DC). For LTE cells, the consequence of these different deployments is the coexistence of LTE cells associated with eNBs connected to EPC, 5GC, or both EPC / 5GC.

[0113] LTE DC and EN-DC are designed differently with regards to which node controls what. Essentially there are two options: (1) a centralized solution (like LTE-DC) and (2) a distributed solution (like EN-DC).

[0114] Figure 11 shows a schematic control plane architecture for LTE DC and EN-DC according to some embodiments. The main difference here is that in EN-DC, the secondary node (SN) has a separate radio resource control (RRC) entity (NR RRC). This means that the SN can sometimes also control the user equipment (UE) without the master node (MN)'s knowledge, but often the SN needs to coordinate with the MN. In LTE-DC, the RRC decision always comes from the MN (MN to UE). However, it should be noted that the SN still decides the configuration of the SN, since only the SN itself has knowledge of what kind of resources, capabilities, etc. the SN has.

[0115] In EN-DC, the main changes compared to LTE DC are the introduction of a split bearer from the SN (known as SCG split bearer), the introduction of a split bearer for RRC, and the introduction of direct RRC from the SN (also called SCG SRB).

[0116] Figures 12 and 13 show UP and control plane (CP) architectures for EN-DC according to some embodiments. In particular, Figure 12 shows network side protocol termination options for MCG bearers, SCG bearers, and split bearers in MR-DC with EPC (EN-DC). Figure 13 shows a network architecture for the control plane in EN-DC, where RRC layer and PDCP layer are upper layers, while RLC layer, MAC layer, and PHY layer are lower layers.

[0117] Note that when LTE is the master node and NR is the secondary node, the SN may be referred to as an SgNB (where a gNB is an NR base station) and the MN may be referred to as an MeNB. In other cases where NR is the master and LTE is the secondary node, the corresponding terms are SeNB and MgNB.

[0118] Split RRC messages are mainly used to create diversity, and the sender can either decide to choose one of the links to schedule the RRC message, or the sender can duplicate the message over both links. In the downlink, the route switching between the MCG leg or the SCG leg or the duplication on both is left to the network implementation. On the other hand, for the UL, the network configures the UE to use the MCG leg, the SCG leg or both legs. The terms "leg", "path" and "RLC bearer" are used interchangeably in this specification.

[0119] Inter-node RRC messages are RRC messages sent over either the X2, Xn, or NG interfaces, either to or from the gNB, i.e., a single "logical channel" is used for all RRC messages forwarded across network nodes. Information may originate from or be destined for another RAT.

[0120] The RRC operation in this respect depends on the UE specific state. The UE is either in RRC_CONNECTED, RRC_INACTIVE or RRC_IDLE state. Different RRC states have different amounts of radio resources associated with them and that the UE may use in a given specific state. In RRC_INACTIVE and RRC_IDLE states, UE controlled mobility based on network (NW) configuration is adopted, i.e. the UE acquires System Information Blocks (SIBs), performs neighboring cell measurements and cell (re)selection, and monitors paging occasions. Inactive UEs store UE inactive access stratum (AS) context and perform RAN-based notification area (RNA) updates.

[0121] However, in the RRC_CONNECTED state, network (NW) controlled mobility is implemented. Indeed, the RAN node may receive paging assistance information related to potential paging triggers, such as QoS flows or signaling, from the 5G Core Network (CN). The UE is thus known by the NW at the node / cell level, and UE-specific bearers are established over which UE-specific data and / or control signaling may be communicated. For example, the RAN may configure a UE-specific RNA that allows reducing the total signaling load by configuring a small RNA for stationary UEs (optimized for low paging load) and a larger RNA for moving UEs (optimized for vehicular UEs).

[0122] Further, for example, if there is traffic transmission and / or reception for a certain timer period, the network may initiate an RRC connection release procedure to move the UE in RRC_CONNECTED to RRC_IDLE or, if SRB2 and at least one DRB were set up in RRC_CONNECTED, to RRC_INACTIVE.

[0123] Some embodiments herein are applicable to vehicular communications. Consider, for example, NR V2X (Vehicle-to-Everything). Cellular Intelligent Transportation Systems (ITS) aim to define a new cellular ecosystem for the delivery of vehicular services and their distribution. Such an ecosystem includes both short-range and long-range V2X service transmissions, as illustrated in FIG. 14. In particular, short-range communications involve transmissions over a device-to-device (D2D) link, also defined in 3GPP as a sidelink or PC5 interface, towards other vehicular UEs or roadside units (RSUs). Meanwhile, long-range transmissions consider transmissions over the Uu interface between UEs and base stations, where packets can be distributed to different ITS service providers, which may be road traffic authorities, road operators, automotive OEMs, cellular operators, etc.

[0124] In particular, some embodiments herein are applicable to V2X communications, including any combination of direct communications between vehicles (V2V), pedestrians (V2P), and infrastructure (V2I). While LTE V2X is primarily aimed at road safety services, NR V2X has a much broader scope that not only includes basic safety services but also targets non-safety applications, such as enhanced sensor / data sharing between vehicles to enhance the perception of the vehicle's surrounding environment. Thus, some embodiments herein may support a new set of applications captured in TR22.886v16.2.0, such as advanced driving, vehicle platooning, cooperative operation between vehicles, and remote driving, which require an enhanced NR system and a new NR sidelink framework.

[0125] In this context, some embodiments are applicable for QoS management of the radio interface including both Uu (i.e., network-to-vehicle UE communication) and sidelink (i.e., vehicle UE-to-vehicle UE communication) used for V2X operation. The QoS management may take into account different performance requirements of different V2X services.

[0126] In NR, for example, a sidelink (SL) QoS flow model is adopted: At the non-access stratum (NAS) layer, the UE maps one V2X packet to a corresponding SL QoS flow, and then at the service data adaptation protocol (SDAP) layer, to a SL radio bearer.

[0127] In NR, the SL Radio Bearer (SLRB) configuration, including the QoS flow-to-SLRB mapping, is either pre-configured or configured by the network (NW) when the UE is in coverage. For example, as shown in FIG. 15, when the UE wants to establish a new SL QoS flow / SLRB for a new service, the UE can send a request to the associated gNB. The request can include the QoS information of the service. The gNB then determines the appropriate SLRB configuration to support such SL QoS flow. After receiving the SLRB configuration from the gNB, the UE establishes a local SLRB accordingly and prepares for data transmission over SL. It should be noted that to enable successful reception at the receiving (RX) UE side, the transmitting (TX) UE may need to inform the RX UE about the necessary parameters, e.g., sequence number space for PDCP / RLC, before data transmission starts.

[0128] In some embodiments, there are two different resource allocation (RA) procedures for V2X on sidelink: NW-controlled RA (so-called "Mode 3" in LTE and "Mode 1" in NR) and autonomous RA (so-called "Mode 4" in LTE and "Mode 2" in NR). Transmission resources are selected within a resource pool that is predefined or configured by the network (NW).

[0129] In NW controlled RA, the NG-RAN is responsible for scheduling the SL resource(s) to be used by the UE for the SL transmission(s). The UE sends a SL Buffer Status Report (BSR) to the NW to inform about the SL data available for transmission in the SL buffer associated with the Medium Access Control (MAC) entity. The NW then signals the resource allocation to the UE using Downlink Control Information (DCI). NW controlled (or Mode 1) resource allocation can be realized via dynamic scheduling signaling over the Physical Downlink Control Channel (PDCCH) or by semi-persistent scheduling where the gNB provides one or more configured SL grants. Both Type 1 configured SL grants and Type 2 configured SL grants are supported.

[0130] In autonomous RA, each device independently decides, e.g., based on sensing, which SL radio resources it should use for SL operation. For both RA modes, sidelink control information (SCI) is transmitted on the physical sidelink control channel (PSCCH) to indicate the allocated sidelink resources for the physical sidelink shared channel (PSSCH). Unlike NW-controlled RA, which can only be implemented when the UE is in RRC_CONNECTED state, autonomous RA (or mode 2) is implemented both when the UE is in RRC_CONNECTED mode and when the UE is in inactive / idle state, and can also be implemented when the UE is under Uu coverage and out of coverage. In particular, when the UE is in RRC_CONNECTED mode, the SL resource pool may be configured with dedicated RRC signaling, whereas for idle / inactive mode operation, the UE shall rely on the SL resource pool provisioned in the broadcasting signal, i.e., SIB.

[0131] In some embodiments, a UE under some conditions, e.g., for groupcast SL communications, is enabled to provision other UEs with a Mode 2 pool to be used for SL communications, e.g., for SL communications within a group of UEs, such as a platoon of vehicles.

[0132] Configured grants are supported for the NR sidelink for both Type 1 and Type 2. With configured grants, the gNB can allocate sidelink resources for multiple (periodic) transmissions to the UE. Type 1 configured grants are configured and activated directly via dedicated RRC signaling, while Type 2 configured grants are configured via dedicated RRC signaling but activated / released only via Downlink Control Information (DCI) transmitted on the PDCCH.

[0133] Some embodiments herein address issues that arise when a sidelink (SL) UE is under the coverage of two different gNBs, i.e., the gNB may send two different configurations to the SL UE. One example may be with respect to RLC mode configuration. If one SL UE is configured to operate in RLC acknowledged mode (AM) and the other SL UE is configured to operate in RLC unacknowledged mode (UM), there may be a configuration mismatch issue. This situation is not only linked to the RLC mode, but it may also occur in situations where two SLRB configurations sent to two SL UEs require some coordination. Moreover, there may be other configuration mismatches that may affect SL operation.

[0134] Some aspects of the present disclosure and their embodiments may provide solutions to these or other problems. Some embodiments mitigate or avoid SL configuration inconsistency. Some embodiments overcome the configuration inconsistency problem for different DC scenarios, for example, by either keeping the same logical node as the SL configuration node for a group of SL UEs and / or proactively exchanging information between different nodes.

[0135] Some embodiments may provide one or more of the following technical advantages(s): Some embodiments aim to avoid conflicts in SL configurations of two SL UEs when the SL configurations come from two different gNBs, which will enable the SL UEs to establish SL connectivity without errors and thus avoid configuration failures.

[0136] In the following embodiments, UE1 is referred to as a TX (transmitter) UE and UE2 is referred to as a RX (receiver) UE. However, the terms UE1 and UE2 can be interchanged without losing meaning in what is described. Furthermore, although the solution disclosed below concerns two gNBs in a DC scenario, it can also be applied to a non-DC scenario (e.g., a handover scenario) as long as there is an X2 / Xn interface between the two gNBs, or a scenario in which one SL UE is configured with DC and the other is not configured with DC.

[0137] Consider first an example of an embodiment of centrally controlling the sidelink configuration of the wireless devices 12A, 12B in FIG. 1 from the same network node. FIG. 16A shows an example where UE1 and UE2 are both controlled by BS1 for SL configuration. For example, if dual connectivity (DC) is configured for at least one of the SL UEs, the SL configuration is managed by a logical node that is common to the SL UEs. This node can be a master node (MN) for one of the SL UEs and a master node (MN) or secondary node (SN) or simply a single connected node for the other SL UE, although this node is logically the same node. For example, BS1 can be a MN for UE1 and an SN for UE2. Anyway, this means that when the SL is set up, the SL configuration RRC entity should be located in the same logical node, and this (i.e., SL control RRC entity information) can be (optionally) indicated to at least one of the SL UEs, for example, when the SN will control / generate / configure the SL configuration.

[0138] In further embodiments, the Layer 2 (L2) ID (source or destination ID) of the SL UEs requesting to have SL communication / transmission and / or SL configuration (or any other ID that may identify these UEs, such as a combination of International Mobile Subscriber Identity (IMSI), Physical Cell Identity (PCI), and Cell Radio Network Temporary Identifier (C-RNTI)) is used and / or, in some embodiments, exchanged between nodes to identify the SL UEs and / or control / generate the SL configuration. The UE identifier for one or more UEs may be indicated in the SL request or in a separate message from the UE to the network node. The network node may also obtain the UE identifier information from a core network node / database (e.g., a third network node that is not another base station).

[0139] In some embodiments, this may be such that the node (either MN or SN) receiving the SL request (i.e., an SL connection / transmission setup related message) may make a decision on whether to generate an SL configuration and / or initiate inter-node coordination regarding the SL configuration.

[0140] In some embodiments, the node (e.g., MN of UE1) that receives the request for SL configuration or connection from one of the UEs (e.g., UE1) makes the decision. In some embodiments, this node may be the node to which the other SL UE (e.g., UE2) is connected or at least in an inactive or dormant state. The decision may be to generate the SL configuration using an already available RRC entity located in the same logical node. This logical node may be the node that received the SL request or another node. In some embodiments, when the decision is made, the other node(s) are informed by using an inter-node message. In further embodiments, the other node(s) may be identified based on the UE identifier / cell identifier received in the SL request message and / or with the help of a database available in the same or a third node. In some embodiments, if the SL configuration(s) for one (or more) UEs is (are) to be (determined to be) generated by another node, the SL configuration message may be queried / requested and fetched / received by the node that received the SL request message. After receiving the (fetched) configuration, the SL configuration may be encapsulated within an RRC message of the node that received the SL request message.

[0141] In some embodiments, the decision is made after inter-node coordination, such that a node (e.g., SN of UE2) receiving a request for SL setup / connection from one of the UEs (e.g., UE2) queries which node should generate SL setup for the SL UEs (e.g., UE1 and UE2) together with the other node (e.g., this node can be MN / SN of UE1 and MN of UE2 at the same time). The query may be based on / include the received UE identifier(s) and the query message may be responded to by a message (from the queried node) regarding which logical node will control / generate the SL setup(s) for one of the UEs (e.g., UE2) or both UEs. In some embodiments, the query message may include a SL request message received from the SL UE (e.g., UE2). In some embodiments, the query response message may already include the generated SL setup, which may be encapsulated with an RRC message of another node.

[0142] In further embodiments, this indication (i.e., which logical node controls / generates the SL configuration) may be sent via an RRC reconfiguration message. The indication may be explicit or implicit. In case of an implicit indication, the SL configuration is generated, for example, by the SN, which means that the SN is the controlling RRC entity of the SL configuration. Note that the respective logical node may be the SN for one of the SL UEs and the MN for the other SL UE in this example. In the absence of explicit and implicit indications, the configuration is determined and / or generated by the same logical node in the background, but who generated the configuration may not be visible to the UE. In case of implicit indication, the decision to generate the SL configuration in the same logical node may be visible since at least one of the UEs may receive the configuration in an RRC information element or an RRC PDU / message encapsulated / embedded in another RRC message, even if those configurations are conveyed by different nodes using different signaling radio bearers (SRBs).

[0143] In a further embodiment, when the logical node needs to be changed by setting up a DC (i.e., MN / SN is modified / changed or SN is added), the SL UE may also be reconfigured with new SL control RRC entity information.

[0144] In further embodiments, the logical node may refer to a central unit (CU) in some architecture options (i.e., gNB CU / DU split architecture), and in other embodiments, the logical node may refer to a distributed unit (DU) in some architecture options (i.e., gNB CU / DU split architecture).

[0145] Consider now an example of an embodiment in which the respective wireless devices 12A, 12B in FIG. 1 cooperate with each other regarding the sidelink configuration 16A, 16B to be used 22. FIG. 16B shows one such example. In FIG. 16B, instead of selecting a common logical node to control / generate the SL configuration, the nodes exchange information about what SL configuration may be used as described in further embodiments below (focusing on DC modification / change / addition procedures). Here, not to be confused with the previous embodiment, the MN and SN may be different nodes, serving at least one of the SL UEs at the same time. In FIG. 16B, for example, UE1 and UE2 are controlled by BS1 and BS2, respectively, regarding the SL configuration. BS1 may be the MN for both UE1 and UE2, and BS2 may be the SN for both UEs.

[0146] In one of the embodiments, when adding a standalone gNB (i.e., MN), the MN shares with the SN the SL configuration that the MN plans to use to configure SL UEs. In another embodiment, when adding a standalone gNB (i.e., MN), the MN sends to the SN the SL configuration that the SN should use to configure capable SL UEs, or vice versa, i.e., from the SN to the MN.

[0147] In another embodiment, the coordination for SL configuration between the MN and the SN occurs during an SN addition procedure. Also, in one embodiment, the coordination for SL configuration between the MN and the SN occurs during an SN modification procedure. In another embodiment, the coordination for SL configuration between the MN and the SN occurs during an SN change procedure. Furthermore, in one of the embodiments, the coordination for SL configuration between the MN and the SN occurs during an intra-RAT or inter-RAT handover procedure.

[0148] In another embodiment, the SL configuration refers to the logical channel ID (LCID) to RLC mode mapping to be used (e.g., LCID1->RLC AM, LCID2->RLC UM, etc.). In another embodiment, the SL configuration refers to the full set of SLRB configurations that the MN wants to configure for the SL UE. In another embodiment, the SL configuration refers to the default parameters (e.g., RLC mode, PDCP duplication on / off, SDAP header present / absent, etc.) used to configure the SL UE under MN or SN coverage.

[0149] In one embodiment, upon receiving the SL configuration from the MN, the SN stores the SL configuration and uses the SL configuration when a new SL UE needs to be configured.

[0150] In another embodiment, upon receiving the SL configuration from the MN, the SN sends back to the MN a set of acceptable SL parameters / configurations for configuring possible SL UEs (i.e., if the configuration received by the MN is not applicable on the SN). Also, in another embodiment, upon receiving the SL configuration from the MN, the SN sends an acknowledgement that the received configuration is accepted / rejected.

[0151] Consider now an example of an embodiment in which the wireless device 12A receives different expected sidelink configurations from different respective network nodes and selects which of those sidelink configurations matches or fits the sidelink configuration 16B of the wireless device 12B through which the sidelink communication is to be performed. Figure 16C shows one such example, for example, where UE1 and UE2 are controlled by BS2 with respect to SL configuration, BS1 is either MN or SN for UE1, and UE2 is connected to a single node (BS2). If one of the two SL UEs is under the coverage of two gNBs (i.e., MN and SN of its respective SL UE), it asks for SL configurations from both gNBs and then selects one that complies with the SL configuration of the peer UE. In another embodiment, after receiving SL configurations from the two gNBs, the UE sends an acknowledgement to the two gNBs (or at least one of the two gNBs) by saying whether the received SL configuration is to be used or not (acceptance or rejection of the received SL configuration).

[0152] In one embodiment, upon receiving a request for SL configuration from a UE, an NG-RAN node (e.g., MN or SN) includes in the sidelink configuration the source L2 ID and destination L2 ID to which the same SL configuration has already been sent, which will help the UE understand whether its peer UEs are using a similar SL configuration or not.

[0153] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a wireless network, such as the exemplary wireless network shown in FIG. 17. For simplicity, the wireless network of FIG. 17 illustrates only the network 1706, the network nodes 1760 and 1760b, and the WDs 1710, 1710b, and 1710c. 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, a service provider, or any other network node or end device. Of the components shown, the network node 1760 and the wireless device (WD) 1710 are illustrated with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device's access to the wireless network and / or use of services provided by or via the wireless network.

[0154] The wireless network may include and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network, or other similar type of system. In some embodiments, the wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement a communications standard, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-IoT), and / or other suitable 2G, 3G, 4G, or 5G standards, a wireless local area network (WLAN) standard, such as the IEEE 802.11 standard, and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0155] The network 1706 may comprise 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.

[0156] The network node 1760 and the WD 1710 comprise various components, which are described in more detail below. These components cooperate to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may 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 may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections.

[0157] A network node, as used herein, refers to a device capable of, set up, configured, and / or operable to communicate directly or indirectly with wireless devices and / or other network nodes or devices in a wireless network to enable and / or provide wireless access to wireless devices and / or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, in other words, their transmit power levels), and may then be referred to as femto, pico, micro, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A part of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Still further examples of a network node include MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below.More generally, however, a network node may represent any suitable device (or group of devices) capable of, configured 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 have accessed the wireless network.

[0158] In FIG. 17, the network node 1760 includes a processing circuit 1770, a device readable medium 1780, an interface 1790, ancillary equipment 1784, a power source 1786, a power circuit 1787, and an antenna 1762. Although the network node 1760 shown in the example wireless network of FIG. 17 may represent a device including the shown combination of hardware components, other embodiments may comprise a network node with a different combination of components. It should be understood that a network node comprises any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of the network node 1760 are illustrated as a single box located within a larger box or nested within multiple boxes, in reality the network node may comprise multiple different physical components that make up a single shown component (e.g., the device readable medium 1780 may comprise multiple separate hard drives as well as multiple RAM modules).

[0159] Similarly, the network node 1760 may be assembled from multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have their own respective components. In some scenarios in which the network node 1760 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control several Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node in some instances. In some embodiments, the network node 1760 may be configured to support several radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 1780 for different RATs) and some components may be reused (e.g., the same antenna 1762 may be shared by the RATs). Network node 1760 may also include multiple sets of the various shown components for different wireless technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, integrated into network node 1760. These wireless technologies may be integrated in the same or different chips or sets of chips and other components within network node 1760.

[0160] The processing circuit 1770 is configured to perform any decision, computation, or similar operations (e.g., some acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuit 1770 may include processing information acquired by the processing circuit 1770, for example, by transforming the acquired information into other information, comparing the acquired or transformed information to information stored in the network node, and / or performing one or more operations based on the acquired or transformed information and as a result of the processing making a decision.

[0161] The processing circuit 1770 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resources, or combinations of hardware, software, and / or coded logic operable to provide network node 1760 functionality, either alone or in conjunction with other network node 1760 components, such as device readable medium 1780. For example, the processing circuit 1770 may execute instructions stored on the device readable medium 1780 or in memory within the processing circuit 1770. Such functionality may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, the processing circuit 1770 may include a system on a chip (SOC).

[0162] In some embodiments, the processing circuitry 1770 may include one or more of a radio frequency (RF) transceiver circuitry 1772 and a baseband processing circuitry 1774. In some embodiments, the radio frequency (RF) transceiver circuitry 1772 and the baseband processing circuitry 1774 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuitry 1772 and the baseband processing circuitry 1774 may be on the same chip or set of chips, board, or unit.

[0163] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 1770 executing instructions stored in a device-readable medium 1780, or in a memory within the processing circuitry 1770. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 1770 without executing instructions stored in a separate or distinct device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuitry 1770 may be configured to perform the described functionality, whether or not it executes instructions stored in a device-readable storage medium. Benefits provided by such functionality are enjoyed by the processing circuitry 1770 alone, or by other components of the network node 1760, but by the network node 1760 as a whole, and / or by end users and wireless networks generally.

[0164] The device readable medium 1780 may comprise any form of volatile or non-volatile computer readable memory, including but not limited to persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 1770. The device readable medium 1780 may store any suitable instructions, data or information, including applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 1770 and utilized by the network node 1760. The device readable medium 1780 may be used to store calculations performed by the processing circuit 1770 and / or data received via the interface 1790. In some embodiments, the processing circuit 1770 and the device readable medium 1780 may be considered to be integrated.

[0165] The interface 1790 is used in wired or wireless communication of signaling and / or data between the network node 1760, the network 1706, and / or the WD 1710. As shown, the interface 1790 comprises a port(s) / terminal(s) 1794 for sending and receiving data to and from the network 1706, for example over a wired connection. The interface 1790 also includes a wireless front-end circuit 1792 that is coupled to the antenna 1762 or, in some embodiments, may be part of the antenna 1762. The wireless front-end circuit 1792 comprises a filter 1798 and an amplifier 1796. The wireless front-end circuit 1792 may be connected to the antenna 1762 and the processing circuit 1770. The wireless front-end circuit may be configured to condition signals communicated between the antenna 1762 and the processing circuit 1770. The wireless front-end circuit 1792 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1792 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1798 and / or amplifiers 1796. The radio signal may then be transmitted via the antenna 1762. Similarly, when receiving data, the antenna 1762 may collect the radio signal, which is then converted into digital data by the radio front-end circuit 1792. The digital data may be passed to the processing circuit 1770. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0166] In some alternative embodiments, the network node 1760 may not include a separate radio front-end circuit 1792; instead, the processing circuit 1770 may comprise a radio front-end circuit and be connected to the antenna 1762 without a separate radio front-end circuit 1792. Similarly, in some embodiments, all or a portion of the RF transceiver circuit 1772 may be considered part of the interface 1790. In still other embodiments, the interface 1790 may include one or more ports or terminals 1794, the radio front-end circuit 1792, and the RF transceiver circuit 1772 as part of a radio unit (not shown), and the interface 1790 may communicate with a baseband processing circuit 1774 that is part of a digital unit (not shown).

[0167] The antenna 1762 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. The antenna 1762 may be coupled to the wireless front-end circuitry 1790 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 1762 may comprise one or more omni-directional, sector or panel antennas operable to transmit / receive wireless signals, for example, between 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit / receive wireless signals in any direction, a sector antenna may be used to transmit / receive wireless signals from devices in a particular area, and a panel antenna may be a line-of-sight antenna used to transmit / receive wireless signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, the antenna 1762 may be separate from the network node 1760 and may be connectable to the network node 1760 through an interface or port.

[0168] The antenna 1762, the interface 1790, and / or the processing circuit 1770 may be configured to perform any receiving operation and / or some obtaining operation described herein as being performed by a network node. Any information, data, and / or signal may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna 1762, the interface 1790, and / or the processing circuit 1770 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0169] The power circuit 1787 may comprise or be coupled to a power management circuit and is configured to supply power to the components of the network node 1760 for performing the functions described herein. The power circuit 1787 may receive power from a power source 1786. The power source 1786 and / or the power circuit 1787 may be configured to provide power to the various components of the network node 1760 in a form suitable for the respective components (e.g., at voltage and current levels required for each respective component). The power source 1786 may either be included in the power circuit 1787 and / or the network node 1760 or may be external to the power circuit 1787 and / or the network node 1760. For example, the network node 1760 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source supplies power to the power circuit 1787. As a further example, power supply 1786 may include a power source in the form of a battery or battery pack connected to or integrated into power circuit 1787. The battery may provide backup power in the event that an external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0170] Alternative embodiments of network node 1760 may include additional components other than those shown in FIG. 17 that may be responsible for providing some aspects of the network node's functionality, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, network node 1760 may include user interface devices to enable input of information into network node 1760 and output of information from network node 1760. This may enable a user to perform diagnostics, maintenance, repair, and other administrative functions for network node 1760.

[0171] A wireless device (WD) as used herein refers to a device capable of, configured to, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information over the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predefined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), in-vehicle wireless terminal devices, etc. A WD may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and V2X, in which case it may be referred to as a D2D communications device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another WD and / or network node. The WD in this case may be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context.As one particular example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other equipment capable of monitoring and / or reporting on its operational status or other functions related to its operation. The WD described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Additionally, the WD described above may be mobile, in which case the device may be referred to as a mobile device or mobile terminal.

[0172] As shown, wireless device 1710 includes antenna 1711, interface 1714, processing circuitry 1720, device readable medium 1730, user interface equipment 1732, auxiliary equipment 1734, power source 1736, and power circuitry 1737. WD 1710 may include multiple sets of one or more of the shown components for different wireless technologies supported by WD 1710, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-IoT, or Bluetooth wireless technologies, just to name a few. These wireless technologies may be integrated on the same or different chip or set of chips as other components in WD 1710.

[0173] The antenna 1711 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to the interface 1714. In some alternative embodiments, the antenna 1711 may be separate from the WD 1710 and connectable to the WD 1710 through an interface or port. The antenna 1711, the interface 1714, and / or the processing circuit 1720 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, the wireless front-end circuit and / or the antenna 1711 may be considered an interface.

[0174] As shown, the interface 1714 comprises a radio front-end circuit 1712 and an antenna 1711. The radio front-end circuit 1712 comprises one or more filters 1718 and an amplifier 1716. The radio front-end circuit 1714 is connected to the antenna 1711 and the processing circuit 1720 and is configured to condition signals communicated between the antenna 1711 and the processing circuit 1720. The radio front-end circuit 1712 may be coupled to the antenna 1711 or may be part of the antenna 1711. In some embodiments, the WD 1710 may not include a separate radio front-end circuit 1712, rather the processing circuit 1720 may comprise a radio front-end circuit and be connected to the antenna 1711. Similarly, in some embodiments, some or all of the RF transceiver circuit 1722 may be considered part of the interface 1714. The radio front-end circuit 1712 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1712 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1718 and / or amplifiers 1716. The radio signal may then be transmitted via the antenna 1711. Similarly, when receiving data, the antenna 1711 may collect the radio signal, which is then converted into digital data by the radio front-end circuit 1712. The digital data may be passed to the processing circuit 1720. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0175] The processing circuitry 1720 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resources, or combinations of hardware, software, and / or coded logic operable to provide WD1710 functionality, either alone or in conjunction with other WD1710 components, such as device readable medium 1730. Such functionality may include providing any of the various wireless features or benefits described herein. For example, the processing circuitry 1720 may execute instructions stored on the device readable medium 1730 or in a memory within the processing circuitry 1720 to provide the functionality disclosed herein.

[0176] As shown, the processing circuit 1720 includes one or more of an RF transceiver circuit 1722, a baseband processing circuit 1724, and an application processing circuit 1726. In other embodiments, the processing circuit may comprise different components and / or different combinations of components. In some embodiments, the processing circuit 1720 of the WD 1710 may comprise a SOC. In some embodiments, the RF transceiver circuit 1722, the baseband processing circuit 1724, and the application processing circuit 1726 may be on separate chips or sets of chips. In alternative embodiments, some or all of the baseband processing circuit 1724 and the application processing circuit 1726 may be combined into one chip or set of chips, and the RF transceiver circuit 1722 may be on a separate chip or set of chips. In yet alternative embodiments, some or all of the RF transceiver circuit 1722 and the baseband processing circuit 1724 may be on the same chip or set of chips, and the application processing circuit 1726 may be on a separate chip or set of chips. In yet other alternative embodiments, some or all of the RF transceiver circuitry 1722, the baseband processing circuitry 1724, and the application processing circuitry 1726 may be combined in the same chip or set of chips. In some embodiments, the RF transceiver circuitry 1722 may be part of the interface 1714. The RF transceiver circuitry 1722 may condition RF signals for the processing circuitry 1720.

[0177] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by the processing circuitry 1720 executing instructions stored on a device-readable medium 1730, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 1720 without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, the processing circuitry 1720 may be configured to perform the described functionality, regardless of whether it executes instructions stored on a device-readable storage medium. Benefits provided by such functionality are enjoyed by the WD 1710 as a whole, and / or by end users and wireless networks in general, but not limited to the processing circuitry 1720 alone or other components of the WD 1710.

[0178] The processing circuit 1720 may be configured to perform any of the decision, calculation, or similar operations (e.g., some of the acquisition operations) described herein as being performed by a WD. These operations as performed by the processing circuit 1720 may include processing information acquired by the processing circuit 1720, for example, by transforming the acquired information into other information, comparing the acquired or transformed information with information stored by the WD 1710, and / or performing one or more operations based on the acquired or transformed information and as a result of the processing making a decision.

[0179] The device-readable medium 1730 may be operable to store applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 1720. The device-readable medium 1730 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 1720. In some embodiments, the processing circuit 1720 and the device-readable medium 1730 may be considered to be integrated.

[0180] The user interface device 1732 may provide components that allow a human user to interact with the WD 1710. Such interaction may be of many forms, such as visual, auditory, tactile, etc. The user interface device 1732 may be operable to produce output to the user and to allow the user to provide input to the WD 1710. The type of interaction may vary depending on the type of user interface device 1732 installed on the WD 1710. For example, if the WD 1710 is a smartphone, the interaction may be via a touch screen, and if the WD 1710 is a smart meter, the interaction may be through a screen that provides usage (e.g., number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 1732 may include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface device 1732 is configured to allow input of information to the WD 1710 and is connected to the processing circuit 1720 to allow the processing circuit 1720 to process the input information. The user interface device 1732 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device 1732 is also configured to enable output of information from the WD 1710 and to enable the processing circuitry 1720 to output information from the WD 1710. The user interface device 1732 may include, for example, a speaker, a display, vibration circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface device 1732, the WD 1710 may communicate with an end user and / or a wireless network and enable the end user and / or the wireless network to benefit from the functionality described herein.

[0181] The auxiliary device 1734 is operable to provide more specific functionality that may not generally be performed by a WD. It may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device 1734 may vary depending on the embodiment and / or scenario.

[0182] The power source 1736 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The WD 1710 may further comprise a power circuit 1737 for delivering power from the power source 1736 to various parts of the WD 1710 that require power from the power source 1736 to perform any of the functions described or indicated herein. The power circuit 1737 may comprise a power management circuit in some embodiments. The power circuit 1737 may additionally or alternatively be operable to receive power from an external power source, in which case the WD 1710 may be connectable to an external power source (such as an electrical outlet) via an input circuit or interface, such as a power cable. The power circuit 1737 may also be operable in some embodiments to deliver power from the external power source to the power source 1736. This may be for charging the power source 1736, for example. The power circuitry 1737 may perform any formatting, conversion, or other modification on the power from the power source 1736 to make the power suitable for the respective components of the WD 1710 that are being powered.

[0183] FIG. 18 illustrates an embodiment of a UE according to various aspects described herein. User equipment or UE as used herein does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not be initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. The UE 1800 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. The UE 1800 shown in Figure 18 is an example of a WD configured for communication according to one or more communications standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the 3GPP GSM, UMTS, LTE, and / or 5G standards. As mentioned above, the terms WD and UE may be used interchangeably. Thus, although Figure 18 is a UE, the components described herein are equally applicable to a WD and vice versa.

[0184] In FIG. 18, a UE 1800 includes a processing circuit 1801 operatively coupled to an input / output interface 1805, a radio frequency (RF) interface 1809, a network connection interface 1811, memory 1815 including random access memory (RAM) 1817, read only memory (ROM) 1819, storage medium 1821, etc., a communication subsystem 1831, a power source 1833, and / or other components, or any combination thereof. The storage medium 1821 includes an operating system 1823, application programs 1825, and data 1827. In other embodiments, the storage medium 1821 may include other similar types of information. Some UEs may utilize all of the components shown in FIG. 18 or only a subset of those components. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0185] In Fig. 18, the processing circuit 1801 may be configured to process computer instructions and data. The processing circuit 1801 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more pre-programmed, general-purpose processors, such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit 1801 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0186] In the illustrated embodiment, the input / output interface 1805 may be configured to provide an input device, an output device, or a communication interface to an input / output device. The UE 1800 may be configured to use an output device via the input / output interface 1805. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 1800. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 1800 may be configured to use an input device via the input / output interface 1805 to allow a user to capture information on the UE 1800. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0187] In FIG. 18, the RF interface 1809 may be configured to provide a communication interface to RF components, such as a transmitter, a receiver, and an antenna. The network connection interface 1811 may be configured to provide a communication interface to a network 1843a. The network 1843a may encompass a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network 1843a may comprise a Wi-Fi network. The network connection interface 1811 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 1811 may implement receiver and transmitter functions appropriate for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software or firmware, or may alternatively be implemented separately.

[0188] The RAM 1817 may be configured to interface to the processing circuit 1801 via the bus 1802 to provide storage or caching of data or computer instructions during execution of software programs, such as an operating system, application programs, and device drivers. The ROM 1819 may be configured to provide computer instructions or data to the processing circuit 1801. For example, the ROM 1819 may be configured to store unchanging low-level system code or data for basic system functions, such as basic input / output (I / O), booting, or receiving keystrokes from a keyboard, stored in non-volatile memory. The storage medium 1821 may be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, the storage medium 1821 may be configured to include an operating system 1823, an application program 1825, such as a web browser application, a widget or gadget engine, or another application, and data files 1827. The storage medium 1821 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 1800.

[0189] The storage medium 1821 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-Ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 1821 may enable the UE 1800 to access computer executable instructions, application programs, etc. stored in a temporary or non-transitory memory medium, offload data, or upload data. An article of manufacture, such as an article of manufacture utilizing the communication system, may be tangibly embodied in the storage medium 1821, and the storage medium 1821 may comprise a device-readable medium.

[0190] In FIG. 18, the processing circuit 1801 may be configured to communicate with the network 1843b using the communication subsystem 1831. The networks 1843a and 1843b may be the same network or networks or different networks or networks. The communication subsystem 1831 may be configured to include one or more transceivers used to communicate with the network 1843b. For example, the communication subsystem 1831 may 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.18, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver may include a transmitter 1833 and / or a receiver 1835 for implementing a transmitter function or a receiver function, respectively, appropriate for a RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter 1833 and receiver 1835 of each transceiver may share circuit components, software or firmware, or may alternatively be implemented separately.

[0191] In the illustrated embodiment, the communication functions of the communication subsystem 1831 may include data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, near-field communications, location-based communications such as using a global positioning system (GPS) to determine location, another similar communication function, or any combination thereof. For example, the communication subsystem 1831 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. The network 1843b may 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 communications network, another similar network, or any combination thereof. For example, the network 1843b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power source 1813 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1800.

[0192] The features, benefits and / or functions described herein may be implemented in one of the components of the UE 1800 or distributed across multiple components of the UE 1800. Furthermore, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1831 may be configured to include any of the components described herein. Furthermore, the processing circuit 1801 may be configured to communicate with any of such components over the bus 1802. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuit 1801, perform the corresponding functions described herein. In another example, the functions of any of such components may be distributed between the processing circuit 1801 and the communication subsystem 1831. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0193] FIG. 19 is a schematic block diagram illustrating a virtualization environment 1900 in which functions implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization as used herein may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device, or any other type of communication device) or a component of that device, and relates to implementations in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0194] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1900 hosted by one or more of the hardware nodes 1930. Furthermore, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0195] The functionality may be implemented by one or more applications 1920 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 1920 are run in a virtualization environment 1900, which provides hardware 1930 comprising a processing circuit 1960 and a memory 1990. The memory 1990 includes instructions 1995 executable by the processing circuit 1960 such that the applications 1920 are operable to provide one or more of the features, benefits, and / or functions disclosed herein.

[0196] The virtualization environment 1900 includes a general purpose or dedicated network hardware device 1930 including a set of one or more processors or processing circuitry 1960, which may be a commercial off-the-shelf (COTS) processor, a dedicated application specific integrated circuit (ASIC), or any other type of processing circuitry including digital or analog hardware components or dedicated processors. Each hardware device may include a memory 1990-1, which may be a non-persistent memory for temporarily storing instructions 1995 or software executed by the processing circuitry 1960. Each hardware device may include one or more network interface controllers (NICs) 1970, also known as network interface cards, which include a physical network interface 1980. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 1990-2 having stored thereon software 1995 and / or instructions executable by the processing circuitry 1960. The software 1995 may include any type of software, including software for instantiating one or more virtualization layers 1950 (also called hypervisors), software for running virtual machines 1940, and software that enables it to perform the functions, features and / or benefits described in connection with some of the embodiments described herein.

[0197] The virtual machines 1940 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1950 or hypervisor. Different embodiments of the virtual appliance 1920 instances may be implemented on one or more of the virtual machines 1940, and the implementations may be done in different ways.

[0198] During operation, the processing circuitry 1960 executes software 1995 to instantiate a hypervisor or virtualization layer 1950, which is sometimes referred to as a virtual machine monitor (VMM). The virtualization layer 1950 may present to the virtual machines 1940 a virtual operating platform that looks like networking hardware.

[0199] 19, the hardware 1930 may be a standalone network node with general or specific components. The hardware 1930 may include an antenna 19225 and may implement some functions via virtualization. Alternatively, the hardware 1930 may be part of a larger cluster of hardware (e.g., as in the case of a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed via a management and orchestration (MANO) 19100 that, among other things, oversees the lifecycle management of the applications 1920.

[0200] Hardware virtualization is referred to in some contexts 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 that may be located in data centers and customer premises equipment.

[0201] In the context of NFV, virtual machines 1940 may be software implementations of physical machines that run programs as if they were running on a physical, non-virtualized machine. Each virtual machine 1940 and the portion of hardware 1930 on which it runs, whether hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other ones of virtual machines 1940, form a separate Virtual Network Element (VNE).

[0202] Further in the context of NFV, a Virtual Network Function (VNF) is responsible for handling a specific network function running in one or more virtual machines 1940 on top of the hardware networking infrastructure 1930 and corresponds to application 1920 in FIG. 19.

[0203] In some embodiments, one or more radio units 19200, each including one or more transmitters 19220 and one or more receivers 19210, may be coupled to one or more antennas 19225. The radio units 19200 may communicate directly with a hardware node 1930 via one or more suitable network interfaces and may be used in combination with a virtualization component to provide a virtual node with wireless capabilities, such as a wireless access node or base station.

[0204] In some embodiments, some signaling may be accomplished using a control system 19230, which may alternatively be used for communication between the hardware nodes 1930 and the wireless unit 19200.

[0205] Figure 20 illustrates a communication network connected to a host computer via an intermediate network, according to some embodiments. In particular, referring to Figure 20, according to one embodiment, a communication system includes a communication network 2010, such as a 3GPP type cellular network, comprising an access network 2011, such as a wireless access network, and a core network 2014. The access network 2011 comprises a number of base stations 2012a, 2012b, 2012c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 2013a, 2013b, 2013c. Each base station 2012a, 2012b, 2012c is connectable to the core network 2014 over a wired or wireless connection 2015. A first UE 2091 located in the coverage area 2013c is configured to wirelessly connect to or be paged by the corresponding base station 2012c. A second UE 2092 in the coverage area 2013a can wirelessly connect to the corresponding base station 2012a. Although multiple UEs 2091, 2092 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or connects to the corresponding base station 2012.

[0206] The communication network 2010 is itself connected to a host computer 2030, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 2030 may be owned or under the control of a service provider, or may be operated by or on behalf of the service provider. The connections 2021 and 2022 between the communication network 2010 and the host computer 2030 may extend directly from the core network 2014 to the host computer 2030, or may proceed via an optional intermediate network 2020. The intermediate network 2020 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 2020 may be a backbone network or the Internet, if any, and in particular the intermediate network 2020 may comprise two or more sub-networks (not shown).

[0207] The communication system of FIG. 20 as a whole enables connectivity between connected UEs 2091, 2092 and a host computer 2030. The connectivity may be described as an over-the-top (OTT) connection 2050. The host computer 2030 and connected UEs 2091, 2092 are configured to communicate data and / or signaling via the OTT connection 2050 using the access network 2011, the core network 2014, any intermediate networks 2020, and possible further infrastructure (not shown) as intermediaries. The OTT connection 2050 may be transparent in the sense that the participating communication devices through which the OTT connection 2050 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 2012 may not be or need not be informed of the past routing of incoming downlink communications involving data originating from the host computer 2030 to be forwarded (e.g., handed over) to the connected UE 2091. Similarly, the base station 2012 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 2091 and destined for the host computer 2030 .

[0208] Next, an exemplary implementation of the UE, base station and host computer described in the previous paragraph according to an embodiment will be described with reference to FIG. 21. FIG. 21 illustrates a host computer communicating with user equipment via a base station over a partially wireless connection according to some embodiments. In the communication system 2100, the host computer 2110 comprises hardware 2115 including a communication interface 2116 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 2100. The host computer 2110 further comprises a processing circuit 2118, which may have storage and / or processing capabilities. In particular, the processing circuit 2118 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 2110 further comprises software 2111, which is stored in or accessible by the host computer 2110 and is executable by the processing circuit 2118. The software 2111 includes a host application 2112. The host application 2112 may be operable to provide services to a remote user, such as the UE 2130 connecting via an OTT connection 2150 that terminates at the UE 2130 and the host computer 2110. In providing services to the remote user, the host application 2112 may provide user data that is transmitted using the OTT connection 2150.

[0209] The communication system 2100 further includes a base station 2120 provided in the communication system, the base station 2120 comprising hardware 2125 enabling the base station 2120 to communicate with the host computer 2110 and the UE 2130. The hardware 2125 may include a communication interface 2126 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 2100, as well as a wireless interface 2127 for setting up and maintaining at least a wireless connection 2170 with a UE 2130 located in a coverage area (not shown in FIG. 21) served by the base station 2120. The communication interface 2126 may be configured to facilitate a connection 2160 to the host computer 2110. The connection 2160 may be direct or alternatively the connection 2160 may pass through a core network (not shown in FIG. 21) of the communication system and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, the hardware 2125 of the base station 2120 further includes processing circuitry 2128, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 2120 further has software 2121 stored internally or accessible via an external connection.

[0210] The communication system 2100 further includes the UE 2130 already mentioned. The hardware 2135 of the UE 2130 may include a wireless interface 2137 configured to set up and maintain a wireless connection 2170 with a base station serving a coverage area in which the UE 2130 is currently located. The hardware 2135 of the UE 2130 further includes a processing circuit 2138, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 2130 further includes software 2131 stored in or accessible by the UE 2130 and executable by the processing circuit 2138. The software 2131 includes a client application 2132. The client application 2132 may be operable to provide services to a human or non-human user via the UE 2130 with the support of the host computer 2110. At the host computer 2110, a running host application 2112 may communicate with a running client application 2132 via an OTT connection 2150 that terminates at the UE 2130 and the host computer 2110. In providing services to a user, the client application 2132 may receive request data from the host application 2112 and provide user data in response to the request data. The OTT connection 2150 may transfer both the request data and the user data. The client application 2132 may interact with the user to generate the user data that the client application 2132 provides.

[0211] It should be noted that the host computer 2110, base station 2120 and UE 2130 shown in Figure 21 may be similar or equivalent to the host computer 2030, one of the base stations 2012a, 2012b, 2012c, and one of the UEs 2091, 2092, respectively, of Figure 20. That is, the inner workings of these entities may be as shown in Figure 21, and separately, the surrounding network topology may be that of Figure 20.

[0212] 21, the OTT connection 2150 is depicted abstractly to show communication between the host computer 2110 and the UE 2130 via the base station 2120, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 2130 or from the service provider that operates the host computer 2110, or both. The network infrastructure may also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network) while the OTT connection 2150 is active.

[0213] The wireless connection 2170 between the UE 2130 and the base station 2120 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 2130 using the OTT connection 2150 of which the wireless connection 2170 forms the final segment.

[0214] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 2150 between the host computer 2110 and the UE 2130 in response to fluctuations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 2150 may be implemented in the software 2111 and hardware 2115 of the host computer 2110 or in the software 2131 and hardware 2135 of the UE 2130, or both. In an embodiment, sensors (not shown) may be deployed in or in association with the communication device through which the OTT connection 2150 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 2111, 2131 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 2150 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 2120, and the reconfiguration may be unknown or imperceptible to the base station 2120. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 2110 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 2111 and 2131 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 2150 while the software 2111 and 2131 monitors propagation times, errors, etc.

[0215] FIG. 22 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 20 and FIG. 21. For simplicity of the disclosure, only drawing references to FIG. 22 are included in this section. In step 2210, the host computer provides user data. In sub-step 2211 (which may be optional) of step 2210, the host computer provides the user data by executing a host application. In step 2220, the host computer initiates a transmission carrying the user data to the UE. In step 2230 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE, according to the teachings of the embodiments described throughout this disclosure. In step 2240 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0216] FIG. 23 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 20 and FIG. 21. For simplicity of the disclosure, only drawing references to FIG. 23 are included in this section. In step 2310 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 2320, the host computer initiates a transmission carrying the user data to the UE. The transmission may proceed via the base station according to the teachings of the embodiments described throughout this disclosure. In step 2330 (which may be optional), the UE receives the user data carried in the transmission.

[0217] FIG. 24 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 20 and FIG. 21. For simplicity of the disclosure, only drawing reference to FIG. 24 is included in this section. In step 2410 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2420, the UE provides user data. In sub-step 2421 (which may be optional) of step 2420, the UE provides the user data by executing a client application. In sub-step 2411 (which may be optional) of step 2410, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 2430 (which may be optional). In method step 2440, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0218] FIG. 25 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 20 and FIG. 21. For simplicity of the disclosure, only drawing references to FIG. 25 are included in this section. In step 2510 (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 2520 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2530 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0219] Any suitable steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0220] In view of the above, then, embodiments herein generally include a communication system including a host computer. The host computer may comprise processing circuitry configured to provide user data. The host computer may also comprise a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network may comprise a base station having a radio interface and processing circuitry, the processing circuitry of the base station configured to perform any of the steps of any of the embodiments described above for the base station.

[0221] In some embodiments, the communication system further includes a base station.

[0222] In some embodiments, the communication system further includes a UE, the UE configured to communicate with the base station.

[0223] In some embodiments, the processing circuitry of the host computer is configured to execute a host application and thereby provide user data, in which case the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0224] Embodiments herein also include a method implemented in a communication system including a host computer, a base station, and a user equipment (UE). The method includes providing user data at the host computer. The method may also include initiating a transmission at the host computer conveying the user data to the UE over a cellular network that includes the base station. The base station performs any of the steps of any of the embodiments described above for the base station.

[0225] In some embodiments, the method further includes transmitting, at the base station, the user data.

[0226] In some embodiments, the user data is provided by executing, at the host computer, a host application, in which case the method further includes executing, at the UE, a client application associated with the host application.

[0227] Embodiments herein also include a user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to implement any of the embodiments described above for the UE.

[0228] Embodiments herein further include a communication system including a host computer comprising a processing circuit configured to provide user data and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), the UE comprising a wireless interface and a processing circuit, the components of the UE configured to perform any of the steps of any of the embodiments described above for the UE.

[0229] In some embodiments, the cellular network further includes a base station configured to communicate with the UE.

[0230] In some embodiments, the processing circuitry of the host computer is configured to execute a host application thereby providing user data, and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0231] Embodiments also include a method implemented in a communications system including a host computer, a base station, and a user equipment (UE), the method including providing user data at the host computer and initiating a transmission conveying the user data to the UE over a cellular network including the base station, the UE performing any of the steps of any of the embodiments described above for the UE.

[0232] In some embodiments, the method further includes receiving, at the UE, user data from the base station.

[0233] Embodiments herein further include a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the UE comprising a wireless interface and processing circuitry, the processing circuitry of the UE configured to perform any of the steps of any of the embodiments described above for the UE.

[0234] In some embodiments, the communication system further includes a UE.

[0235] In some embodiments, the communication system further includes a base station, where the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.

[0236] In some embodiments, the processing circuitry of the host computer is configured to execute a host application, and the processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data therewith.

[0237] In some embodiments, processing circuitry of the host computer is configured to execute a host application thereby providing requested data, and processing circuitry of the UE is configured to execute a client application associated with the host application thereby providing user data in response to the requested data.

[0238] Embodiments herein also include a method implemented in a communications system including a host computer, a base station, and a user equipment (UE), the method including receiving, at the host computer, user data transmitted from the UE to the base station, the UE performing any of the steps of any of the embodiments described above for the UE.

[0239] In some embodiments, the method further includes providing, at the UE, user data to the base station.

[0240] In some embodiments, the method also includes executing, at the UE, a client application to provide user data to be transmitted thereby. The method may further include executing, at the host computer, a host application associated with the client application.

[0241] In some embodiments, the method further includes executing, at the UE, a client application and receiving, at the UE, input data for the client application, the input data being provided by executing, at the host computer, a host application associated with the client application, the user data to be transmitted being provided by the client application in response to the input data.

[0242] An embodiment also includes a communication system including a host computer, the host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the base station comprising a wireless interface and processing circuitry, the processing circuitry of the base station configured to perform any of the steps of any of the embodiments described above for the base station.

[0243] In some embodiments, the communication system further includes a base station.

[0244] In some embodiments, the communication system further includes a UE, the UE being configured to communicate with the base station.

[0245] In some embodiments, the processing circuitry of the host computer is configured to execute a host application, and the UE is configured to execute a client application associated with the host application to thereby provide user data to be received by the host computer.

[0246] Additionally, embodiments include a method implemented in a communications system including a host computer, a base station, and a user equipment (UE), the method including receiving, at the host computer, from the base station, user data originating from a transmission received by the base station from the UE, the UE performing any of the steps of any of the embodiments described above for the UE.

[0247] In some embodiments, the method further includes receiving, at the base station, user data from the UE.

[0248] In some embodiments, the method further includes initiating, at the base station, a transmission of the received user data to the host computer.

[0249] Generally, all terms used herein should be interpreted according to the ordinary meaning of those terms in the relevant technical field, unless a different meaning is expressly given and / or implied from the context in which the term is used. All references to a / an / the element, apparatus, component, means, step, etc. should be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is expressly described as following or preceding another step, and / or if it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will become apparent from the description thereof.

[0250] The term unit may have its conventional meaning in the field of electronics, electrical devices, and / or electronic devices and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logical solid and / or discrete devices, computer programs or instructions, etc., for performing a respective task, procedure, computation, output, and / or display function, such as those described herein.

[0251] Some of the embodiments contemplated herein are more fully described with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein. The subject matter disclosed should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0252] In particular, modifications and other embodiments of the disclosed invention(s) will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. It is to be understood, therefore, that the invention(s) is not to be limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the present disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0253] With this limitation in mind, the following group of embodiments recite various aspects of the present specification. Group A Embodiments A1. A method implemented by a wireless device, the method comprising: receiving an indication from a network node indicating which network node controls a sidelink configuration of the wireless device; A method comprising: A2. A method implemented by a wireless device, the method comprising: receiving a sidelink configuration from each of a plurality of network nodes serving the wireless device; selecting from the received sidelink configurations a sidelink configuration that matches or is compatible with a sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink; A method comprising: A3. The method of embodiment A2, further comprising sending to each of one or more of the network nodes serving the wireless device an indication of the selected sidelink configuration and / or an indication of whether the wireless device accepts or rejects the sidelink configuration received from the network node. A4. The method of embodiment A2 or A3, further comprising requesting a sidelink configuration from each of a plurality of network nodes. A5. The method of any one of embodiments A2 to A4, further comprising receiving, from each of one or more of the network nodes serving the wireless device, information identifying one or more other wireless devices to which the network node has sent the same sidelink configuration received from that network node. A6. A method according to any one of embodiments A1 to A5, wherein at least one of the network nodes acts as a master node for multi-connectivity operations and at least one other of the network nodes acts as a secondary node for the multi-connectivity operations. A7. Side link settings are Sidelink radio bearer setup, Quality of Service flow to sidelink radio bearer mapping; Configuring a resource pool for sidelink communications; Radio Link Control (RLC) mode configuration, including configuration of RLC unacknowledged or RLC acknowledged mode; Logical channel ID to RLC mode mapping, or Default Sidelink Configuration Parameters The method of any one of embodiments A1 to A6, comprising one or more of: A.A. Providing user data; forwarding user data to a host computer via transmission to a base station; The method of any one of embodiments A1 to A7, further comprising: Group B Embodiments B1. A method implemented by a network node, the method comprising: Controlling a sidelink configuration of each of a plurality of wireless devices that are to communicate with each other via a sidelink A method comprising: B2. The method of embodiment B1, in which the controlling is based on a network node serving each of a plurality of wireless devices. B3. The method of embodiment B1 or B2, further comprising determining, by the network node, to control a sidelink configuration of each of the plurality of wireless devices based on the network node serving each of the plurality of wireless devices. B4. The method of any one of embodiments B1 to B3, wherein at least one of the plurality of wireless devices is served by the network node and one or more other network nodes. B5. The method of any one of embodiments B1 to B4, wherein the network node serves as a master node for at least one of the plurality of wireless devices in a multi-connectivity operation. B6. The method of embodiment B5, in which the network node serves as a secondary node for at least one other of the plurality of wireless devices in multi-connectivity. B7. The method of any one of embodiments B1 to B6, wherein at least one of the plurality of wireless devices is not configured with multi-connectivity or is not operating in multi-connectivity. B8. The method of any one of embodiments B1 to B7, further comprising determining, based at least in part on information received from another network node, that a plurality of wireless devices will communicate with one another over a sidelink. B9. The method of embodiment B8, wherein the information received from the other network node includes identification information that identifies at least one of the plurality of wireless devices. B10. The method of embodiment B9, wherein the identification information includes a Layer 2 identification information of at least one of the plurality of wireless devices. B11. The method of any one of embodiments B1 to B10, further comprising sending an indication to each of one or more of the plurality of wireless devices instructing the network node to control a sidelink configuration of the wireless device or instructing the network node to control a sidelink configuration of each of the plurality of wireless devices. B12. The method of any one of embodiments B1-B4 and B7-B11, wherein the network node is a central unit or a distributed unit of a radio network node. B13. The method of any one of embodiments B1 to B12, wherein the controlling includes generating, for each of a plurality of wireless devices, a sidelink configuration and transmitting the sidelink configuration to the wireless device or to another network node for relaying to the wireless device. B14. The method of any one of embodiments B1 to B13, wherein the controlling includes controlling sidelink configurations of a plurality of wireless devices to be consistent or compatible with one another. B15. The sidelink setting of the wireless device is Sidelink radio bearer setup, Quality of Service flow to sidelink radio bearer mapping; Configuring a resource pool for sidelink communications; Radio Link Control (RLC) mode configuration, including configuration of RLC unacknowledged or RLC acknowledged mode; Logical channel ID to RLC mode mapping, or Default Sidelink Configuration Parameters The method of any one of embodiments B1 to B14, comprising one or more of: B16. The method of any one of embodiments B1 to B15, in which a plurality of wireless devices are requesting or have requested a sidelink configuration for purposes of communicating with each other via the sidelink. Group BB embodiment BB1. A method implemented by a network node, the method comprising: selecting a network node from among a plurality of candidate network nodes to control a sidelink configuration of each of a plurality of wireless devices that will communicate with each other via a sidelink; A method comprising: BB2. The method of embodiment BB1, wherein the selecting includes selecting a network node to serve each of the plurality of wireless devices. BB3. The method of embodiment BB1 or BB2, further comprising transmitting, to one or more of the candidate network nodes and / or to one or more of the wireless devices, information indicating the network node selected to control the sidelink configuration of each of the plurality of wireless devices. BB4. The method of any one of embodiments BB1 to BB3, wherein at least one of the plurality of wireless devices is served by a plurality of network nodes in a multi-connectivity operation. BB5. The method of any one of embodiments BB1 to BB4, wherein a selected network node serves as a master node for at least one of a plurality of wireless devices in a multi-connectivity operation. BB6. The method of embodiment BB5, in which the selected network node serves as a secondary node for at least one other of the plurality of wireless devices in multi-connectivity. BB7. The method of any one of embodiments BB1 to BB6, wherein at least one of the plurality of wireless devices is not configured with multi-connectivity or is not operating in multi-connectivity. BB8. The method of any one of embodiments BB1 to BB7, further comprising determining, based at least in part on information received from another network node, that a plurality of wireless devices will communicate with one another over a sidelink. BB9. The method of embodiment BB8, wherein the information received from the other network node includes identification information that identifies at least one of the plurality of wireless devices. BB10. The method of embodiment BB9, wherein the identification information includes Layer 2 identification information of at least one of the plurality of wireless devices. BB11. The method of any one of embodiments BB1 to BB10, further comprising: sending an indication to each of one or more of the plurality of wireless devices indicating a selected network node to control a sidelink configuration of the wireless device or indicating a selected network node to control a sidelink configuration of each of the plurality of wireless devices. BB12. The method of any one of embodiments BB1 to BB4 and BB7 to BB11, wherein the selected network node is a central unit or a distributed unit of a radio network node. BB13. The method of any one of embodiments BB1 to BB12, wherein a network node selected to control a sidelink configuration of each of a plurality of wireless devices is selected to generate, for each of the plurality of wireless devices, a sidelink configuration and transmit the sidelink configuration to the wireless device. BB14. The method of any one of embodiments BB1 to BB13, wherein the network node selected to control the sidelink configuration of each of the plurality of wireless devices is selected to control the sidelink configurations of the plurality of wireless devices to be consistent or compatible with each other. BB15. The sidelink settings of the wireless device are Sidelink radio bearer setup, Quality of Service flow to sidelink radio bearer mapping; Configuring a resource pool for sidelink communications; Radio Link Control (RLC) mode configuration, including configuration of RLC unacknowledged or RLC acknowledged mode; Logical channel ID to RLC mode mapping, or Default Sidelink Configuration Parameters The method of any one of embodiments BB1 to BB14, including one or more of: BB16. The method of any one of embodiments BB1 to BB15, wherein a plurality of wireless devices are requesting or have requested a sidelink configuration for purposes of communicating with each other via the sidelink. BB17. The method of any one of embodiments BB1 to BB16, wherein the selecting is performed in response to receiving a request for sidelink configuration from one or more of a plurality of wireless devices. BB18. The method of any one of embodiments BB1 to BB16, wherein the selecting is performed in response to receiving a query from one of the candidate network nodes inquiring as to which network node will control a sidelink configuration of each of a plurality of wireless devices. BB19. The method of any one of embodiments BB1 to BB18, wherein the selecting is performed as part of setting up a sidelink between the wireless devices, as part of a procedure for modifying which network node serves as a master node for multi-connectivity operation of at least one of the wireless devices, or as part of a procedure for adding or modifying which network node serves as a secondary node for multi-connectivity operation of at least one of the wireless devices. Group BBB embodiment BBB1. A method implemented by a first network node, the method comprising: and coordinating with a second network node regarding sidelink configuration of each of a plurality of wireless devices that are to communicate with each other via the sidelink. A method comprising: BBB2. Said cooperation is transmitting information to the second network node indicating one or more sidelink configurations that may be used in the first network node; and / or receiving information from a second network node indicating one or more sidelink configurations that may be used at the second network node; The method of embodiment BBB1, comprising: BBB3. Said cooperation is transmitting information to the second network node indicating one or more sidelink configurations that the second network node is to use; and / or receiving information from a second network node indicating one or more sidelink configurations to be used by the first network node; The method of embodiment BBB1 or BBB2, comprising: BBB4. Said cooperation is transmitting information to the second network node indicating one or more sidelink configurations that the first network node proposes to use; and / or receiving information from a second network node indicating one or more sidelink configurations that the second network node proposes to use; The method of embodiment BBB1 or BBB2, comprising: BBB5. Said cooperation is transmitting information to the second network node indicating one or more sidelink configurations that the first network node will accept or reject for use; and / or receiving information from a second network node indicating one or more sidelink configurations that the second network node will accept or reject for use; The method of embodiment BBB1 or BBB2, comprising: BBB6. The method of any one of embodiments BBB1 to BBB5, wherein a first network node serves as a master node for at least one of a plurality of wireless devices in multi-connectivity operation, and a second network node serves as a secondary node for at least one other of the plurality of wireless devices in multi-connectivity operation. BBB7. The method of any one of embodiments BBB1 to BBB6, wherein at least two of the wireless devices do not have a common serving network node. BBB8. The method of any one of embodiments BBB1 to BBB7, further comprising determining a sidelink configuration for each of one or more of a plurality of wireless devices served by the first network node based on the coordinating. BBB9. The method of any one of embodiments BBB1 to BBB8, wherein the coordinating is performed during or as part of a procedure for adding or modifying a second node for at least one of a plurality of wireless devices in multi-connectivity. BBB10. The method of any one of embodiments BBB1 to BBB8, wherein the coordinating is performed during or as part of a procedure for handover of one or more of the plurality of wireless devices. BBB11. The method of any one of embodiments BBB1 to BBB10, wherein at least one of the plurality of wireless devices is served by a plurality of network nodes. BBB12. The method of embodiment BBB8, further comprising transmitting the determined sidelink configuration towards each of one or more of a plurality of wireless devices served by the first network node. BBB13. The sidelink setting of the wireless device is Sidelink radio bearer setup, Quality of Service flow to sidelink radio bearer mapping; Configuring a resource pool for sidelink communications; Radio Link Control (RLC) mode configuration, including configuration of RLC unacknowledged or RLC acknowledged mode; Logical channel ID to RLC mode mapping, or Default Sidelink Configuration Parameters The method of any one of embodiments BBB1 to BBB13, comprising one or more of: BBB14. The method of any one of embodiments BBB1 to BBB14, wherein a plurality of wireless devices are requesting or have requested a sidelink configuration for purposes of communicating with each other via the sidelink. B.B. Obtaining user data; Forwarding user data to a host computer or wireless device; The method of any one of embodiments BBB1 to BBB14, further comprising: Group C Embodiments C1. A wireless device configured to perform any of the steps recited in any one of the embodiments of Group A. C2. A wireless device comprising processing circuitry configured to perform any of the steps recited in any one of the embodiments of Group A. C3. A wireless device, comprising: A communication circuit; a processing circuit configured to perform any of the steps recited in any one of the embodiments of Group A; A wireless device comprising: C4. A wireless device, A processing circuit configured to perform any of the steps recited in any one of the embodiments of Group A; and a power delivery circuit configured to provide power to a wireless device; A wireless device comprising: C5. A wireless device, comprising: A wireless device comprising a processing circuit and a memory, the memory including instructions executable by the processing circuit, whereby the wireless device is configured to perform any of the steps recited in any one of the embodiments of group A. C6. A user equipment (UE), an antenna configured to transmit and receive radio signals; a radio front-end circuit coupled to an antenna and to a processing circuit and configured to condition a signal communicated between the antenna and the processing circuit, a processing circuit configured to perform any of the steps recited in any one of the embodiments of group A. A radio front-end circuit; an input interface coupled to the processing circuitry and configured to enable input of information to the UE to be processed by the processing circuitry; an output interface coupled to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; a battery connected to the processing circuit and configured to power the UE; A user equipment (UE) comprising: C7. A computer program comprising instructions that, when executed by at least one processor of a wireless device, cause the wireless device to perform the steps recited in any one of the embodiments of group A. C8. A carrier containing the computer program of embodiment C7, the carrier being one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. C9. A radio network node configured to perform any of the steps recited in any one of the embodiments of Group B. C10. A radio network node comprising processing circuitry configured to perform any of the steps recited in any one of the embodiments of Group B. C11. A radio network node, comprising: A communication circuit; a processing circuit configured to perform any of the steps recited in any one of the embodiments of Group B; A wireless network node comprising: C12. A radio network node, comprising: a processing circuit configured to perform any of the steps recited in any one of the embodiments of Group B; a power supply circuit configured to supply power to the wireless network node; A wireless network node comprising: C13. A radio network node, comprising: A radio network node comprising a processing circuit and a memory, the memory including instructions executable by the processing circuit, whereby the radio network node is configured to perform any of the steps recited in any one of the embodiments of Group B. C14. The radio network node of any one of embodiments C9 to C13, wherein the radio network node is a base station. C15. A computer program comprising instructions that, when executed by at least one processor of a radio network node, cause the radio network node to perform the steps recited in any one of the embodiments of group B. C16. The computer program product of embodiment C14, wherein the radio network node is a base station. C17. A carrier containing the computer program of embodiment C15 or C16, the carrier being one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. Group D embodiment D1. A communication system including a host computer, the host computer comprising: processing circuitry configured to provide user data; a communications interface configured to forward user data to a cellular network for transmission to a user equipment (UE); Equipped with A communications system in which a cellular network comprises a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps recited in any one of the embodiments of Group B. D2. The communications system of embodiment D1, further comprising a base station. D3. The communications system of any one of embodiments D1 to D2, further comprising a UE, the UE configured to communicate with the base station. D4. Processing circuitry of the host computer is configured to execute a host application and thereby provide user data; the UE comprising processing circuitry configured to execute a client application associated with the host application; A communication system as described in embodiments D1 to D3. D5. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at a host computer; Initiating, at the host computer, a transmission conveying user data to the UE via a cellular network comprising a base station, the base station performing any of the steps recited in any one of the embodiments of Group B; A method comprising: D6. The method of embodiment D5, further comprising transmitting user data at the base station. D7. The method of embodiment D5 or D6, wherein the user data is provided by executing a host application at the host computer, and the method further includes executing, at the UE, a client application associated with the host application. D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to implement any one of embodiments D5 to D7. D9. A communication system including a host computer, the host computer: processing circuitry configured to provide user data; a communications interface configured to forward user data to a cellular network for transmission to a user equipment (UE); Equipped with a UE comprising a radio interface and a processing circuit, the components of the UE being configured to perform any of the steps described in any one of the embodiments of group A; Communication systems. D10. The communications system of embodiment D9, wherein the cellular network further includes a base station configured to communicate with the UE. D11. A processing circuit of a host computer is configured to execute a host application and thereby provide user data; a processing circuit in the UE configured to execute a client application associated with the host application; A communication system as described in embodiment D9 or D10. D12. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at a host computer; Initiating, at the host computer, a transmission conveying user data to a UE via a cellular network comprising a base station, the UE performing any of the steps recited in any one of the embodiments of group A; A method comprising: D13. The method of embodiment D12, further comprising receiving, at the UE, user data from the base station. D14. A communication system including a host computer, the host computer: A communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station Equipped with a UE comprising a radio interface and a processing circuit, the processing circuit of the UE configured to perform any of the steps described in any one of the embodiments of group A; Communication systems. D15. The communication system of embodiment D14, further comprising a UE. D16. The communications system of any one of embodiments D14 to D15, further comprising a base station, the base station having a wireless interface configured to communicate with the UE and a communications interface configured to forward user data carried by transmissions from the UE to the base station to a host computer. D17. The processing circuitry of a host computer is configured to execute a host application; a processing circuit in the UE configured to execute a client application associated with the host application and thereby provide user data; A communication system as described in embodiments D14 to D16. D18. Processing circuitry of a host computer is configured to execute a host application and thereby provide requested data; processing circuitry of the UE configured to execute a client application associated with the host application, thereby providing user data in response to the request data; A communication system as described in embodiments D14 to D17. D19. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: receiving, at the host computer, user data transmitted from the UE to the base station, wherein the UE performs any of the steps recited in any one of the embodiments of group A; A method comprising: D20. The method of embodiment D19, further comprising, at the UE, providing user data to the base station. D21. Executing, in a UE, a client application and providing user data to be transmitted thereby; executing, at the host computer, a host application associated with the client application; The method of embodiment D19 or D20, further comprising: D22. Running a client application in a UE; receiving, at the UE, input data for a client application, the input data being provided at a host computer by executing a host application associated with the client application; Further comprising: The method of embodiments D19 to D21, wherein the user data to be transmitted is provided by a client application in response to the input data. D23. A communications system including a host computer, the host computer having a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the base station having a wireless interface and processing circuitry, the processing circuitry of the base station configured to perform any of the steps described in any one of the embodiments of Group B. D24. The communications system of embodiment D23, further comprising a base station. D25. The communications system of any one of embodiments D23 to D24, further comprising a UE, the UE configured to communicate with the base station. D26. The processing circuitry of a host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer; A communication system as described in embodiments D23 to D25. D27. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: receiving, at the host computer, from a base station, user data originating from a transmission received by the base station from the UE, wherein the UE performs any of the steps recited in any one of the Group A embodiments. A method comprising: D28. The method of embodiment D27, further comprising receiving, at the base station, user data from the UE. D29. The method of embodiment D27 or D28, further comprising initiating, at the base station, transmission of the received user data to the host computer.

Claims

1. A method implemented by a wireless device (12A), the method comprising: receiving (700) a sidelink configuration from each of a plurality of network nodes (20A, 20B) serving the wireless device (12A); selecting (710) from the received sidelink configurations a sidelink configuration (16A) that matches or is compatible with a sidelink configuration (16B) of another wireless device (12B) with which the wireless device (12A) is to communicate via a sidelink; sending (720) an indication of the selected sidelink configuration (16A) to each of one or more of the network nodes (20A, 20B) serving the wireless device (12A); Including, the sidelink configuration comprises a radio link control (RLC) mode configuration, which comprises a configuration of an RLC unacknowledged mode or an RLC acknowledged mode; The method of claim 1, wherein the selecting step comprises selecting, from the received sidelink configurations, a sidelink configuration that includes an RLC mode setting that is the same as an RLC mode setting of the sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink.

2. 2. The method of claim 1 , wherein a sidelink configuration includes a logical channel ID-to-RLC mode mapping, and wherein the selecting comprises selecting, from the received sidelink configurations, a sidelink configuration that includes a same logical channel ID-to-RLC mode mapping as a logical channel ID-to-RLC mode mapping of the sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink.

3. Sidelink settings are Sidelink radio bearer setup, Quality of Service flow to sidelink radio bearer mapping; Configuring a resource pool for sidelink communications; Radio Link Control (RLC) mode configuration, including configuration of RLC unacknowledged mode or RLC acknowledged mode; Logical Channel ID to RLC Mode Mapping, and Default Sidelink Configuration Parameters The method of claim 1 or 2, comprising at least one of any one or more of:

4. 4. The method according to claim 1, wherein at least one of the network nodes (20A, 20B) acts as a master node for multi-connectivity operations and at least one other of the network nodes (20A, 20B) acts as a secondary node for the multi-connectivity operations.

5. 5. The method of claim 1, further comprising requesting a sidelink configuration from each of the plurality of network nodes.

6. 6. The method of claim 1, further comprising: receiving, from each of one or more of the network nodes serving the wireless device, information identifying one or more other wireless devices that have sent the same sidelink configuration as received by the wireless device from that network node.

7. A method implemented by a network node (20A, 20B), comprising the steps of: receiving an indication from a wireless device (12A) of a sidelink configuration (16A) selected by the wireless device (12A) as matching or adapting to a sidelink configuration (16B) of another wireless device (12B) with which the wireless device (12A) is to communicate via a sidelink; A method comprising:

8. 8. The method of claim 7, wherein the sidelink configuration comprises a radio link control (RLC) mode configuration, including configuration of an RLC unacknowledged mode or an RLC acknowledged mode.

9. 9. The method of claim 8, wherein the indication comprises an indication of a sidelink configuration selected by the wireless device as having the same RLC mode setting as an RLC mode setting of the sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink.

10. 10. The method of claim 7, wherein a sidelink configuration comprises a logical channel ID to RLC mode mapping, and the indication comprises an indication of a sidelink configuration selected by the wireless device as having the same logical channel ID to RLC mode mapping as a logical channel ID to RLC mode mapping of the sidelink configuration of another wireless device with which the wireless device is to communicate via the sidelink.

11. Sidelink settings are Sidelink radio bearer setup, Quality of Service flow to sidelink radio bearer mapping; Configuring a resource pool for sidelink communications; Radio Link Control (RLC) mode configuration, including configuration of RLC unacknowledged mode or RLC acknowledged mode; Logical Channel ID to RLC Mode Mapping, and Default Sidelink Configuration Parameters 11. The method of claim 7, further comprising at least one of any one or more of:

12. The method according to any one of claims 7 to 11, wherein the network nodes (20A, 20B) act as master nodes for multi-connectivity operations.

13. The method according to any one of claims 7 to 11, wherein the network nodes (20A, 20B) act as secondary nodes for multi-connectivity operations.

14. 14. The method according to claim 7, further comprising transmitting to the wireless device information identifying one or more other wireless devices to which the network node has sent a sidelink configuration identical to the sidelink configuration transmitted to the wireless device.

15. A wireless device (12A), receiving a sidelink configuration from each of a plurality of network nodes (20A, 20B) serving the wireless device (12A); selecting from the received sidelink configurations a sidelink configuration that matches or is compatible with a sidelink configuration of another wireless device with which the wireless device is to communicate via a sidelink; sending an indication of the selected sidelink configuration (16A) to each of one or more of the network nodes (20A, 20B) serving the wireless device (12A); It is set to do the sidelink configuration comprises a radio link control (RLC) mode configuration, which comprises a configuration of an RLC unacknowledged mode or an RLC acknowledged mode; The selecting includes selecting from the received sidelink configurations a sidelink configuration (16A) that includes an RLC mode setting that is the same as an RLC mode setting of the sidelink configuration (16B) of another wireless device (12B) with which the wireless device (12A) is to communicate via the sidelink.

16. A radio device (12A) according to claim 15, arranged to carry out the method according to any one of claims 2 to 6.

17. A network node (20A, 20B), receiving an indication from a wireless device (12A) of a sidelink configuration (16A) selected by the wireless device (12A) as matching or adapting to a sidelink configuration (16B) of another wireless device (12B) with which the wireless device (12A) is to communicate via a sidelink; A network node (20A, 20B) configured to perform the following:

18. A network node (20A, 20B) according to claim 17, configured to implement a method according to any one of claims 8 to 14.

19. A computer program comprising instructions which, when executed by at least one processor of a wireless device (12A), cause said wireless device (12A) to perform a method according to any one of claims 1 to 6.

20. A computer program comprising instructions which, when executed by at least one processor of a network node (20A, 20B), cause said network node (20A, 20B) to perform a method according to any one of claims 7 to 14.

Images