Sidelink configuration in dual connectivity

Abstract

A wireless device (12A) receives a sidelink configuration from each of a plurality of network nodes (20A, 20B) serving the wireless device (12A). The wireless device (12A) selects a sidelink configuration (16A) from the received sidelink configurations that is consistent or compatible with a sidelink configuration (16B) of another wireless device (12B) with which the wireless device (12A) is to communicate over a sidelink. In some embodiments, the wireless device (12A) 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).

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

[0002] A sidelink is a link enabling device-to-device (D2D) discovery and / or communication between wireless devices. When the wireless devices are in network coverage, the network can configure the wireless devices for sidelink, e.g., according to 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 proves to be complex in certain contexts. For example, if the wireless devices that are to communicate over sidelink are served by different network nodes, the wireless devices risk ending up with incompatible sidelink configurations. SUMMARY

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

[0004] More particularly, embodiments herein include a method performed 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 is consistent or compatible with a sidelink configuration of another wireless device with which the wireless device is to communicate over a sidelink. In some embodiments, the method further includes transmitting, to each of one or more of the network nodes serving the wireless device, an indication of the selected sidelink configuration.

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

[0006] In some embodiments, the sidelink configuration includes a logical channel ID to RLC mode mapping. In this case, selecting the sidelink configuration includes selecting, from the received sidelink configurations, a sidelink configuration that includes a logical channel ID to RLC mode mapping that is the same 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 over 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; a resource pool configuration for sidelink communications; a radio link control, RLC, mode configuration including a configuration of a RLC unacknowledged mode or a RLC acknowledged mode; a logical channel ID to RLC mode mapping; and a default sidelink configuration parameter.

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

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

[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 transmitted the same sidelink configuration received from that network node.

[0011] Other embodiments herein include a method performed by a network node. The method includes receiving, from a wireless device, an indication that the wireless device selects a sidelink configuration that is consistent or compatible with 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 including a configuration of an RLC unacknowledged mode or an RLC acknowledged mode. In one or more of these embodiments, the indication includes an indication that the wireless device selects a sidelink configuration that has a same RLC mode configuration as a sidelink configuration of another wireless device with which the wireless device is to communicate over the sidelink.

[0013] In some embodiments, the sidelink configuration includes a logical channel ID to RLC mode mapping, and wherein the indication includes an indication that the wireless device selects a sidelink configuration that has a same logical channel ID to RLC mode mapping as a sidelink configuration of another wireless device with which the wireless device is to communicate over 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 a configuration of an RLC unacknowledged mode or an RLC acknowledged mode; a logical channel ID to RLC mode mapping; and a default sidelink configuration parameter.

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

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

[0017] In some embodiments, the method further includes transmitting, to the wireless device, information identifying one or more other wireless devices to which the network node has transmitted a 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 further configured to select, from the received sidelink configurations, a sidelink configuration that is consistent or compatible with a sidelink configuration of another wireless device with which the wireless device is to communicate over a sidelink. The wireless device is further 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 a wireless device.

[0020] Other embodiments herein include a network node configured to receive, from a wireless device, an indication that the wireless device selected a sidelink configuration that is consistent or compatible with a sidelink configuration of another wireless device with which the wireless device is to communicate over a sidelink.

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

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

[0023] Other embodiments herein include a wireless device comprising communication circuitry and processing circuitry. The processing circuitry is configured to receive a sidelink configuration from each of a plurality of network nodes serving the wireless device. The processing circuitry is further configured to select, from the received sidelink configurations, a sidelink configuration that is consistent or compatible with a sidelink configuration of another wireless device with which the wireless device is to communicate over a sidelink. In some embodiments, the processing circuitry is further configured 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 a wireless device.

[0025] Other embodiments herein include a network node comprising communication circuitry and processing circuitry. The processing circuitry is configured to receive, from a wireless device, an indication that the wireless device selects a sidelink configuration that is consistent or compatible with 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] The application is of course not limited to the features and advantages described above. Indeed, a person skilled in the art will recognize additional features and advantages upon reading the following detailed description and viewing the attached drawings. BRIEF DESCRIPTION OF DRAWINGS

[0028] Figure 1 is a block diagram of a wireless communication network according to some embodiments.

[0029] Figure 2 is a block diagram of a wireless communication network according to other embodiments.

[0030] Figure 3 is a logic flow diagram of a method performed by a network node according to some embodiments.

[0031] Figure 4 is a logic flow diagram of a method performed by a network node according to other embodiments.

[0032] Figure 5 is a logic flow diagram of a method performed by a network node according to still other embodiments.

[0033] Figure 6 is a logic flow diagram of a method performed by a wireless device according to some embodiments.

[0034] Figure 7A is a logic flow diagram of a method performed by a wireless device according to other embodiments.

[0035] Figure 7B is a logic flow diagram of a method performed by a network node according to other embodiments.

[0036] Figure 8 is a block diagram of a wireless device according to some embodiments.

[0037] Figure 9 is a block diagram of a network node according to some embodiments.

[0038] Figure 10 is a block diagram of different ways of deploying a 5G network with or without interworking with LTE according to some embodiments.

[0039] Figure 11 is a block diagram of a control plane architecture for LTE DC and EN-DC according to some embodiments.

[0040] Figure 12 and 13 is a block diagram of a user plane (UP) and control plane (CP) architecture for EN-DC according to some embodiments.

[0041] Figure 14 is a block diagram of a system with short-range and long-range V2X service transmission according to some embodiments.

[0042] Figure 15 is a block diagram for sidelink radio bearer configuration according to some embodiments.

[0043] Figure 16A is a block diagram illustrating centralized control of sidelink configuration for a wireless device from the same network node according to some embodiments.

[0044] Figure 16B is a block diagram illustrating coordination between wireless devices regarding sidelink configuration to be used according to some embodiments.

[0045] Figure 16C is a block diagram illustrating a wireless device selecting a sidelink configuration that is consistent or compatible with a sidelink configuration of another wireless device according to some embodiments.

[0046] Figure 17 is a block diagram of a wireless communication network according to some embodiments.

[0047] Figure 18 is a block diagram of a user equipment according to some embodiments.

[0048] Figure 19 is a block diagram of a virtualization environment according to some embodiments.

[0049] Figure 20 is a block diagram of a communication network with a host computer according to some embodiments.

[0050] Figure 21 is a block diagram of a host computer according to some embodiments.

[0051] Figure 22 is a flowchart illustrating a method implemented in a communication system, according to one embodiment.

[0052] Figure 23 is a flowchart illustrating a method implemented in a communication system, according to one embodiment.

[0053] Figure 24 is a flowchart illustrating a method implemented in a communication system, according to one embodiment.

[0054] Figure 25 is a flow diagram illustrating a method implemented in a communication system according to one embodiment. DETAILED DESCRIPTION

[0055] Figure 1 A wireless communication system 10 according to some embodiments, e.g., a Long Term Evolution (LTE) system or a New Radio (NR) system, is shown. In this example, a wireless device 12A is to 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 via a path through any network node, e.g., a base station. Such communication can for example include user plane communication in the form of Proximity Service (ProSe) direct communication.

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

[0057] Some embodiments herein control, coordinate, select, or otherwise dictate sidelink configurations 16A, 16B of wireless devices 12A, 12B to be consistent or compatible with each other. Sidelink configurations 16A, 16B are consistent or compatible with each other if they allow wireless devices 12A, 12B to establish sidelink connectivity without any errors, and thereby avoid configuration failures. Consistency or compatibility referred to in some embodiments can thus mean that sidelink configurations 16A, 16B are identical or fully compatible with each other. For example, in some embodiments, sidelink configurations 16A, 16B are consistent or compatible with each other if, for each of one or more parameters, the parameter has the same value in both sidelink configurations 16A, 16B. For example, in embodiments where sidelink configurations 16A, 16B include RLC mode configurations for sidelink 14, sidelink configurations 16A, 16B are consistent or compatible with each other if they configure the same RLC mode for sidelink 14, e.g., if both sidelink configurations 16A and 16B configure RLC unacknowledged mode for sidelink 14, or both configure RLC acknowledged mode for sidelink 14. Additionally or alternatively, in embodiments where sidelink configurations 16A, 16B include logical channel ID to RLC mode mappings for sidelink 14, sidelink configurations 16A, 16B are consistent or compatible with each other if they configure the same logical channel ID to RLC mode mappings. As yet another example, in embodiments where sidelink configurations 16A, 16B include default sidelink configuration parameters, sidelink configurations 16A, 16B are consistent or compatible with each other if they additionally or alternatively configure the same values for the default sidelink configuration parameters, e.g., both sidelink configurations 16A, 16B default to configuring PDCP duplication as “on”, or both default to configuring SDAP header as “present”. Regardless of the nature of the consistency or compatibility, ensuring consistency or compatibility between sidelink configurations of wireless devices in this way can advantageously avoid configuration failures and service latency.

[0058] For example, some embodiments centrally control sidelink configurations 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 a multi-connectivity operation. In particular, radio network node 20A acts as a master node (MN) for wireless device 12A, while radio network node 20B acts as a secondary node (SN) for wireless device 12B. In contrast, as shown, wireless device 12B can be served by radio network node 20B only, or in other embodiments, can also be in a multi-connectivity operation. In any case, some embodiments centrally control sidelink configurations of wireless devices 12A, 12B from any of the radio network nodes 20A, 20B that collectively serve both wireless devices 12A, 12B. In this example, then, radio network node 20B will control sidelink configurations of both wireless device 12A and wireless device 12B based on radio network node 20B serving both wireless device 12A and wireless device 12B. This means that radio network node 20B can centrally control sidelink configurations 16A, 16B to be consistent or compatible with each other.

[0059] Note that in some embodiments, radio network node 20B can control sidelink configurations 16A, 16B in the sense that radio network node 20B dictates, prescribes, or otherwise controls parameters of those sidelink configurations 16A, 16B. Radio network node 20B does not necessarily need to generate or even transmit sidelink configurations 16A, 16B to wireless devices 12A, 12B. For example, in some embodiments, radio network node 20B generates a sidelink configuration 16A for wireless device 12A, but transmits that sidelink configuration 16A to radio network node 20A for relaying to wireless device 12A, e.g., within an encapsulated RRC message.

[0060] Figure 3 A method performed by a network node 20B is depicted in accordance with certain embodiments. The method includes controlling sidelink configurations 16A, 16B of each of a plurality of wireless devices 12A, 12B that are to communicate with each other over a sidelink 14 (block 320). In some embodiments, this control includes controlling sidelink configurations 16A, 16B of the plurality of wireless devices 12A, 12B to be consistent or compatible with each other.

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

[0062] In some embodiments, the method can previously include deciding, by the network node 20B, to control sidelink configuration of each of the plurality of wireless devices 12A, 12B based on the network node 20B serving each of the plurality of wireless devices 12A, 12B (block 310).

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

[0064] 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 a multi-connectivity operation. In one such embodiment, the network node 20B acts as a secondary node for at least one other wireless device of the plurality of wireless devices 12A, 12B in the multi-connectivity.

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

[0066] In any event, in some embodiments, the method further includes determining that the plurality of wireless devices 12A, 12B are to communicate with each other over a sidelink based at least in part on information received from another network node (block 300). The information received from the other network node may, for example, include identification information, such as Layer 2 identification, identifying at least one of the plurality of wireless devices 12A, 12B.

[0067] In some embodiments, the method further includes transmitting an indication to each of one or more of the plurality of wireless devices 12A, 12B, the indication indicating that the network node 20B controls sidelink configuration of the wireless device or that the network node 20B controls sidelink configuration of each of the plurality of wireless devices 12A, 12B (block 330).

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

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

[0070] In some embodiments, the controlling includes controlling sidelink configurations of the plurality of wireless devices 12A, 12B to be consistent or compatible with each other.

[0071] In some embodiments, the sidelink configuration of the wireless device consists of 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 mode or RLC acknowledged mode; a logical channel ID to RLC mode mapping; or a default sidelink configuration parameter.

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

[0073] Figure 4 A method performed by a network node according to other particular embodiments is depicted. The method includes selecting, from a plurality of candidate network nodes, a network node to control sidelink configuration for each of a plurality of wireless devices 12A, 12B that are to communicate with each other over a sidelink (block 410). In some embodiments, this selection includes selecting a network node that serves each of the plurality of wireless devices 12A, 12B.

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

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

[0076] In some embodiments, the selected network node acts as a primary node for at least one of the plurality of wireless devices 12A, 12B in a multi-connectivity operation.

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

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

[0079] In some embodiments, the method includes determining that the plurality of wireless devices 12A, 12B are to communicate with each other over a sidelink based at least in part on information received from another network node (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 plurality of wireless devices 12A, 12B. For example, the identification information can include a layer 2 identification of at least one of the plurality of wireless devices 12A, 12B.

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

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

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

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

[0084] In some embodiments, the sidelink configuration of a wireless device consists of 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, the RLC mode configuration including a configuration of RLC unacknowledged mode or RLC acknowledged mode; a logical channel ID to RLC mode mapping; or a default sidelink configuration parameter.

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

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

[0087] In some embodiments, the selection is performed in response to receiving a query from one of the candidate network nodes as to which network node is to control the sidelink configuration for each of the plurality of wireless devices 12A, 12B.

[0088] In some embodiments, the selection 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 acts as a master node for a multi-connectivity operation of at least one of the wireless devices, or as part of a procedure for adding or modifying which network node acts as a secondary node for a multi-connectivity operation of at least one of the wireless devices 12A, 12B.

[0089] In contrast, in other embodiments, this can be applicable even in embodiments as shown in Figure 2 where the wireless devices 12A, 12B do not have a common serving node, the serving nodes 24A, 24B of the respective wireless devices 12A, 12B can e.g. coordinate 22 with each other (e.g. over an inter-node interface) in a distributed manner as to the sidelink configuration 16A, 16B to be used. That is, instead of one of the network nodes 24A, 24B centrally controlling both of the sidelink configurations 16A, 16B, the network nodes 24A, 24B coordinate with each other in such a way that the sidelink configurations 16A, 16B will be consistent or compatible with each other.

[0090] For example, Figure 5 A method performed by a network node 24A in accordance with these other embodiments is depicted. The method comprises coordinating with a second network node 24B as to a sidelink configuration for each of a plurality of wireless devices 12A, 12B that are to communicate with each other over a sidelink (block 500).

[0091] In some embodiments, such coordination comprises transmitting, to the second network node 24B, information indicating one or more sidelink configurations that can be used at the first network node 24A; and / or receiving, from the second network node 24B, information indicating one or more sidelink configurations that can be used at the second network node 24B. Alternatively or additionally, in some embodiments, such coordination comprises transmitting, to the second network node 24B, information indicating one or more sidelink configurations that the second network node 24B is to use; and / or receiving, from the second network node 24B, information indicating one or more sidelink configurations that the first network node 24A is to use. Alternatively or additionally, in some embodiments, such coordination comprises transmitting, to the second network node 24B, information indicating one or more sidelink configurations that the first network node 24A suggests to use; and / or receiving, from the second network node 24B, information indicating one or more sidelink configurations that the second network node 24B suggests to use. Alternatively or additionally, in some embodiments, such coordination comprises transmitting, to the second network node 24B, information indicating one or more sidelink configurations that the first network node 24A accepts or rejects to use; and / or receiving, from the second network node 24B, information indicating one or more sidelink configurations that the second network node 24B accepts or rejects to use.

[0092] In some embodiments, the method further comprises deciding, based on said coordination, a sidelink configuration 16A, 16B for each of one or more of the wireless devices 12A, 12B served by the first network node 24A (block 510). In such cases, the method can also comprise transmitting the decided sidelink configuration towards each of one or more of the wireless devices 12A, 12B served by the first network node 24A (block 520).

[0093] For example, in some embodiments, the first network node 24A decides the 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 can use, suggests to use, or accepts to use. The sidelink configuration 16B may, for example, be a sidelink configuration that the second network node 24B suggests for another wireless device 12B served by the second network node 24B to use.

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

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

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

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

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

[0099] In some embodiments, the sidelink configuration of the wireless device consists of 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 mode or RLC acknowledged mode; a logical channel ID to RLC mode mapping; or a default sidelink configuration parameter.

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

[0101] Figure 6 A method performed by a wireless device according to still other particular embodiments is depicted. The method includes receiving an indication from a network node indicating which network node controls a sidelink configuration of the wireless device (block 600).

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

[0103] In some embodiments, the sidelink configuration consists of 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 mode or RLC acknowledged mode; a logical channel ID to RLC mode mapping; or a default sidelink configuration parameter.

[0104] In still other embodiments not shown, wireless device 12A can receive different intended sidelink configurations from different respective network nodes 24A, 24B, and select any one of the sidelink configurations that is consistent or compatible with a sidelink configuration 16B of a wireless device 12B with which it is to perform sidelink communication. In this case, wireless device 12A itself can then evaluate and / or ensure consistency or compatibility between sidelink configurations 16A, 16B. In some embodiments, wireless device 12A can also report the selected sidelink configuration to one or more of network nodes 24A, 24B, e.g., for use by the network node(s) in or otherwise with the sidelink configuration.

[0105] Figure 7A A method performed by a wireless device 12A is depicted in accordance with still other particular embodiments. 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 is consistent or compatible with a sidelink configuration 16B of another wireless device 12B with which the wireless device 12A is to communicate over a sidelink 14 (block 710). The method can 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).

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

[0107] 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 has sent the same sidelink configuration received from the network node.

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

[0109] In some embodiments, the sidelink configuration consists of 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 a configuration of RLC unacknowledged mode or RLC acknowledged mode; a logical channel ID to RLC mode mapping; or a default sidelink configuration parameter.

[0110] Figure 7B A method performed by a network node according to still other particular embodiments is depicted. The method includes receiving, from a wireless device 12A, an indication of a sidelink configuration 16A selected by the wireless device 12A to be consistent or compatible with a sidelink configuration 16B of another wireless device 12B with which the wireless device 12A is to communicate over a sidelink 14 (block 750). In some embodiments, the method further includes controlling the sidelink configuration of the wireless device 12A and / or the other wireless device 12B based on the received indication (block 760).

[0111] 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 has sent the same sidelink configuration.

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

[0113] In some embodiments, the sidelink configuration consists of 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, the RLC mode configuration including a configuration of RLC unacknowledged mode or RLC acknowledged mode; a logical channel ID to RLC mode mapping; or a default sidelink configuration parameter.

[0114] Embodiments herein also include corresponding devices. Embodiments herein for example include a wireless device configured to perform any of the steps of any of the embodiments described above for a wireless device.

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

[0116] Embodiments further include a wireless device 12A or 12B including processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for a wireless device 12A or 12B. In some embodiments, the wireless device 12A or 12B further includes communication circuitry.

[0117] Embodiments further include a wireless device 12A or 12B including processing circuitry and a memory. The memory contains instructions executable by the processing circuitry whereby the wireless device 12A or 12B is configured to perform any of the steps of any of the embodiments described above for the wireless device 12A or 12B.

[0118] Embodiments also include a user equipment (UE). The UE includes an antenna configured to send and receive wireless signals. The UE also includes radio front-end circuitry connected to the antenna and processing circuitry and configured to condition signals passing between the antenna and the processing circuitry. The processing circuitry 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 includes an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE can include an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE can also include a battery connected to the processing circuitry and configured to supply power to the UE.

[0119] Embodiments herein also include a 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.

[0120] Embodiments also include a radio network node 20A or 20B including processing circuitry and power supply circuitry. The processing circuitry 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 circuitry is configured to supply power to the radio network node 20A or 20B.

[0121] Embodiments further include a radio network node 20A or 20B including processing circuitry. The processing circuitry is 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 includes communication circuitry.

[0122] Embodiments further include a radio network node 20A or 20B including processing circuitry and a memory. The memory contains instructions executable by the processing circuitry whereby 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.

[0123] More particularly, the apparatus described above can perform the methods herein and any other processing by implementing any of the functional means, modules, units or circuitry. In one embodiment, for example, the apparatus includes respective circuitry or circuitry configured to perform the steps shown in the method figures. The circuitry or circuitry in this regard can include circuitry dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For example, the circuitry can include one or more microprocessor(s) or microcontroller(s), as well as other digital hardware, which can include digital signal processors (DSPs), special-purpose computer chips, etc. The processing circuitry can be configured to execute program code stored in memory, which can include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in memory can include program instructions for implementing one or more telecommunication and / or data communication protocols and instructions for carrying out one or more of the techniques described herein. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

[0124] Figure 8 A wireless device 800 (e.g., wireless device 12A or 12B) implemented in accordance with one or more embodiments is illustrated, for example. As shown, the wireless device 800 includes processing circuitry 810 and communication circuitry 820. The communication circuitry 820 (e.g., radio circuitry) is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. Such communication can occur via one or more antennas that are internal or external to the wireless device 800. The processing circuitry 810 is configured to perform processing in accordance with the techniques described above, e.g., in Figure 3 , Figure 4 and / or Figure 5 . In this regard, the processing circuitry 810 can implement certain functional means, units, or modules.

[0125] Figure 9 A network node 900 (e.g., radio network node 20A or 20B) implemented in accordance with one or more embodiments is illustrated, for example. As shown, the network node 900 includes processing circuitry 910 and communication circuitry 920. The communication circuitry 920 is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. The processing circuitry 910 is configured to perform processing in accordance with the techniques described above, e.g., in Figure 6or the process described in Figure 7. In this regard, the processing circuitry 910 can implement certain functional means, units or modules.

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

[0127] A computer program comprises instructions which, when executed on at least one processor of a device, cause the device to carry out any of the above described corresponding processes. A computer program in this regard can comprise one or more code modules corresponding to the means or units described above.

[0128] Embodiments further include a carrier containing such a computer program which is in itself known. The carrier can comprise one of an electronic signal, optical signal, radio signal or computer readable storage medium.

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

[0130] 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. This computer program product can be stored on a computer-readable recording medium.

[0131] Additional embodiments will now be described. At least some of these embodiments can be described for illustrative purposes as applicable to certain contexts and / or wireless network types, but these embodiments are similarly applicable to other contexts and / or wireless network types not explicitly described.

[0132] Some embodiments herein can be applicable to multi-connectivity. In this regard, multi-connectivity refers to a wireless device being connected to multiple different radio network nodes (e.g., at the radio resource control, RRC, layer) simultaneously, or to multiple different cells provided by different radio network nodes. The multiple different radio network nodes or cells can use the same radio access technology (e.g., both can use evolved universal terrestrial radio access (E-UTRA) or both can use new radio (NR)). Alternatively, the multiple different radio network nodes or cells can use different radio access technologies, e.g., one can use E-UTRA while the other can use NR.

[0133] One example of multi-connectivity is dual connectivity (DC), in which 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, the wireless device can be configured with a so-called master cell group (MCG) and a secondary cell group (SCG), where the MCG comprises one or more cells provided by a radio network node acting as a master node (MN) and the SCG comprises one or more cells served by a radio network node acting as a secondary node (SN). The master node can be primary in the sense that it controls the secondary node and / or provides a control plane connection to a core network. For example, E-UTRA-NR (EN) DC refers to a case where the master node uses E-UTRA and the secondary node uses NR, while NR-E-UTRA (NE) refers to a case where the master node uses NR and the secondary node uses E-UTRA.

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

[0135] More specifically, some embodiments herein can be applicable to multi-connectivity (e.g., dual connectivity) as specified by the Third Generation Partnership Project (3GPP), e.g., for Long Term Evolution (LTE) or between LTE and New Radio (NR). In dual connectivity (DC), two nodes are involved: a master node (MN or MeNB) and a secondary node (SN or SeNB). Multi-connectivity (MC) generally captures the case when more than two nodes are involved. Further, it has been proposed in 3GPP to use DC in ultra-reliable low latency communication (URLLC) cases in order to enhance robustness and avoid connection interruptions.

[0136] As Figure 10As depicted in the middle, embodiments herein can be applicable in any of a number of different ways to deploy a 5G network with or without interworking with LTE (also known as E-UTRA) and an evolved packet core (EPC). In principle, NR and LTE can be deployed without any interworking, denoted by NR standalone (SA) operation; that is, gNBs in NR can be connected to a 5G core network (5GC), while eNBs can be connected to an EPC, with no interworking between the two Figure 10 Option 1 and Option 2. On the other hand, the first supported version of NR is the so-called EN-DC (E-UTRAN-NR Dual Connectivity), as shown in Option 3 in the middle. In such a deployment, dual connectivity between NR and LTE is applied, with LTE as the master node and NR as the secondary node. The radio access network (RAN) node (gNB) supporting NR can have no control plane connection to the core network (EPC); instead, it relies on LTE as the master node (MeNB). This is also referred to as "non-standalone NR." Note that in this case, the functionality of the NR cell is limited and will be used as a booster and / or diversity leg for connected mode UEs, but RRC_IDLE UEs cannot camp on these NR cells. Figure 10

[0137] With the introduction of 5GC, other options can also be valid and can be applicable to embodiments herein. As mentioned above, Option 2 supports standalone NR deployment where the gNB is connected to the 5GC. Similarly, LTE can also be connected to the 5GC using Option 5 in the middle (also known as eLTE, E-UTRA / 5GC, or LTE / 5GC, and the node can 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 can be referred to as NG-RAN nodes). Notably, Option 4 and Option 7 in the middle are other variants of dual connectivity between LTE and NR, which will be standardized as part of the NG-RAN connected to the 5GC, denoted by MR-DC (Multi-Radio Dual Connectivity). Then, under the MR-DC umbrella, embodiments herein can be used as: Figure 10 Figure 10

[0138] EN-DC (Option 3): LTE is the master node and NR is the secondary node (with EPC CN)

[0139] NE-DC (Option 4): NR is the master node and LTE is the secondary node (with 5G CN)

[0140] ​​​NGEN-DC (option 7): LTE is the master node and NR is the secondary node (with 5GCN)

[0141] NR-DC (variant of option 2): Dual connectivity, where both the master and secondary nodes are NR (with 5GCN).

[0142] Since migration of these options can differ from one operator to another, it is possible to have multiple options deployed in parallel in the same network, for example, there can be eNB base stations supporting options 3, 5 and 7 in the same network as NR base stations supporting options 2 and 4. In combination with the dual connectivity solutions 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). The result of these different deployments for LTE cells is the coexistence of LTE cells associated with eNBs connected to EPC, 5GC or both EPC / 5GC.

[0143] When it comes to which node controls what, the LTE DC and EN-DC designs are different. Basically, there are two options: (1) a centralized solution (like LTE-DC); (2) a decentralized solution (like EN-DC).

[0144] Figure 11 An illustrative control plane architecture for LTE DC and EN-DC is shown in accordance with 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 also control the user equipment (UE); sometimes without the master node (MN) being aware, but the SN often needs to coordinate with the MN. In LTE-DC, the RRC decisions always come from the MN (MN to UE). Note, however, that the SN still decides the configuration of the SN, since only the SN itself knows what kind of resources, capabilities, etc. it has.

[0145] For EN-DC, the main changes compared to LTE DC are the introduction of split bearers (called SCG split bearers) from the SN, the introduction of split bearers for RRC; and the introduction of direct RRC from the SN (also called SCG SRB).

[0146] Figure 12 And 13 An UP and control plane (CP) architecture for EN-DC is shown in accordance with some embodiments. In particular, Figure 12Network side protocol termination options for MCG, SCG and split bearers in MR-DC with EPC (EN-DC) are shown. Figure 13 Network architecture for the control plane in EN-DC is shown. Here, RRC and PDCP layers are higher layers, while RLC, MAC and PHY layers are lower layers.

[0147] Note that in the case where LTE is the master node and NR is the secondary node, the SN is sometimes referred to as SgNB (where gNB is the NR base station), and the MN is referred to as MeNB. In another case where NR is the master node and LTE is the secondary node, the corresponding terms are SeNB and MgNB.

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

[0149] Inter-node RRC messages are RRC messages sent to or from a gNB across X2-, Xn- or NG-interfaces, i.e. a single "logical channel" is used for all RRC messages transmitted across network nodes. The information can originate from or be destined to another RAT.

[0150] In this respect, the RRC operation depends on the UE specific state. The UE is in either RRC CONNECTED state, RRC INACTIVE state or RRC IDLE state. Different RRC states have different amounts of radio resources associated with them and that the UE can use in a given specific state. In RRC INACTIVE and RRC IDLE state, a network (NW) configured UE controlled mobility is employed, i.e. the UE acquires system information blocks (SIBs), performs neighbor cell measurements and cell (re)selection, and monitors paging occasions. An inactive UE stores the UE inactive access stratum (AS) context and performs RAN-based notification area (RNA) update.

[0151] However, in RRC CONNECTED state, network (NW) controlled mobility is performed. Indeed, the RAN node can receive from the 5G core network (CN) paging assistance information related to potential paging triggers, such as QoS flows or signaling. Thus, the NW is aware of the UE at node / cell level and establishes a UE specific bearer on which UE specific data and / or control signaling can be transferred. For example, the RAN can configure a UE specific RNA that makes it possible to reduce the total signaling load by configuring small RNAs for stationary UEs (optimized for low paging load) and larger RNAs for mobile UEs (optimized for vehicular UEs) in particular.

[0152] Furthermore, for example, if there is no traffic transmission and / or reception for a certain timer period, the network can initiate an RRC connection release procedure to transition the UE in RRC CONNECTED to RRC IDLE or to RRC INACTIVE if SRB2 and at least one DRB are setup under RRC CONNECTED.

[0153] Some embodiments herein can be applicable to vehicular communications. For example, consider NR Vehicle-to-Everything (V2X). Cellular Intelligent Transport Systems (ITS) aims at defining a new cellular ecosystem for the delivery of vehicular services and their dissemination. This ecosystem includes both short-range and long-range V2X service transmissions, as depicted in Figure 14 In particular, short-range communications involve transmissions towards other vehicular UEs or Road Side Units (RSUs) over a device-to-device (D2D) link (also defined in 3GPP as a sidelink or PC5 interface). On the other hand, for long-range transmissions, it considers transmissions between a UE and a base station over the Uu interface, in which case the packets can be disseminated to different ITS service providers, who can be road traffic authorities, road operators, car OEMs, cellular operators, etc.

[0154] In particular, some embodiments herein can be applicable to V2X communications, which include any combination of direct communications between vehicles (V2V), pedestrians (V2P) and infrastructure (V2I). While LTE V2X mainly targets traffic safety services, NR V2X has a broader scope, including not only basic safety services but also non-safety applications, such as extended sensor / data sharing between vehicles, with the aim of enhancing the perception of the vehicle’s surrounding environment. Thus, some embodiments herein can support a new set of applications captured in TR 22.886 v16.2.0, such as advanced driving, vehicle platooning, cooperative maneuvers between vehicles and remote driving, which require enhanced NR systems and new NR sidelink framework.

[0155] In this context, some embodiments can be applicable to QoS management including both Uu (i.e., network-to-vehicle UE communication) and sidelink (i.e., vehicle UE-to-vehicle UE communication) radio interfaces for V2X operation. QoS management can take into account different performance requirements of different V2X services.

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

[0157] In NR, when a UE is in coverage, SL radio bearer (SLRB) configuration including QoS flow to SLRB mapping is pre-configured or configured by the network (NW). For example, as shown in Figure 15 When a UE wants to establish a new SL QoS flow / SLRB for a new service, it 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 the local SLRB accordingly, and is ready for data transmission over SL. Note that in order to enable successful reception at the receiving (RX) UE side, the transmitting (TX) UE can have to inform the RX UE about the necessary parameters, e.g., sequence number space for PDCP / RLC, before the data transmission starts.

[0158] In some embodiments, for V2X over sidelink, there are two different resource allocation (RA) procedures, namely NW-controlled RA (referred to as “Mode 3” in LTE and “Mode 1” in NR) and autonomous RA (referred to as “Mode 4” in LTE and “Mode 2” in NR). Transmission resources are selected within a resource pool pre-defined or configured by the network (NW).

[0159] With NW-controlled RA, the NG-RAN is responsible for scheduling SL resource(s) to be used by the UE for SL transmission(s). The UE sends a SL buffer status report (BSR) to the NW to inform about 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 through dynamic scheduling signaling via physical downlink control channel (PDCCH), or through semi-persistent scheduling where the gNB provides one or more configured SL grants. Both Type 1 and Type 2 configured SL grants are supported.

[0160] With autonomous RA, each device decides independently which SL radio resources to use for SL operation based on, e.g., sensing. For both RA modes, sidelink control information (SCI) is transmitted on the physical sidelink control channel (PSCCH) to indicate the sidelink resources assigned for the physical sidelink shared channel (PSSCH). Unlike NW-controlled RA, which can only be performed when the UE is in RRC CONNECTED state, autonomous RA (or Mode-2) can be performed when the UE is in RRC CONNECTED mode and when the UE is in INACTIVE / IDLE state, and also when the UE is in Uu coverage and out of coverage. In particular, when the UE is in RRC CONNECTED mode, the SL resource pool can be configured with dedicated RRC signaling, while for IDLE / INACTIVE mode operation, the UE should rely on the SL resource pool provided in the broadcast signal (i.e., SIB).

[0161] In some embodiments, under certain conditions, e.g., for groupcast SL communication, a UE is allowed to provide a Mode-2 pool to other UEs for SL communication, e.g., for SL communication within a group of UEs, such as a platoon of vehicles.

[0162] For NR sidelink, for both Type 1 and Type 2, configured grant is supported. With configured grant, the gNB can allocate sidelink resources for multiple (periodic) transmissions to a UE. Type 1 configured grant is directly configured and activated via dedicated RRC signaling, and Type 2 configured grant is configured via dedicated RRC signaling but only activated / released via downlink control information (DCI) transmitted on PDCCH.

[0163] Some embodiments herein address the challenges that arise when a sidelink (SL) UE is under the coverage of two different gNBs; that is, the gNBs can send two different configurations to the SL UE. One example can be with respect to RLC mode configuration. If one SL UE is configured to operate in RLC acknowledged mode (AM) and the other in RLC unacknowledged mode (UM), there can be a configuration inconsistency issue. This situation is not only related to RLC mode, but can also occur in those cases where two SLRB configurations sent to two SL UEs need some kind of coordination. In addition, there can be other configuration mismatches that can impact SL operation.

[0164] Certain aspects of the present disclosure, and their embodiments, can provide solutions to these or other challenges. Some embodiments mitigate or avoid SL configuration inconsistency. Some embodiments overcome the configuration inconsistency issue for different DC scenarios, e.g., by keeping the same logical node for SL configuration for a group of SL UEs and / or actively exchanging information between different nodes.

[0165] Certain embodiments can provide one or more of the following technical advantages. Some embodiments aim at avoiding conflicts in SL configurations of two SL UEs when the SL configurations come from two different gNBs. This will allow the SL UEs to establish SL connectivity without any error and thus avoid configuration failure.

[0166] In the following embodiments, UE1 is referred to as TX (transmitter) UE and UE2 is referred to as RX (receiver) UE. However, the terms UE1 and UE2 are interchangeable without losing any of the described meaning. In addition, the solution disclosed below involves two gNBs in a DC scenario, but it can also be applied to a non-DC scenario as long as there is an X2 / Xn interface between the two gNBs (e.g., a handover scenario) or a scenario where one SL UE is configured with DC and the other is not.

[0167] First consider centralized control Figure 1 An example of embodiments of the in-band link configuration of wireless devices 12A, 12B from the same network node. Figure 16A One example is shown where both UE1 and UE2 are controlled by BS 1 in terms of SL configuration. For example, if at least one of the SL UEs is configured with dual connectivity (DC), the SL configuration is managed by a logical node that is common to the SL UEs. This node can be the master node (MN) of one of the SL UEs and the master node (MN) or secondary node (SN) of the other SL UE or just a single node of the connection even if it is logically the same node. For example, BS 1 can be the MN of UE1 and the SN of UE2. Regardless, this means that when setting up the SL, the SL configuration RRC entity should be located at the same logical node and can (optionally) indicate this (i.e., SL control RRC entity information) to at least one of the SL UEs, for example, when the SN is to control / generate / configure the SL configuration.

[0168] In further embodiments, the layer 2 (L2) ID (source or destination ID) of the SL UEs that are requesting SL communication / transmission and / or SL configuration (or possibly any other ID that identifies these UEs, such as a combination of international mobile subscriber identity (IMSI), physical cell identity (PCI), and cell radio network temporary identity (C-RNTI)) is used and / or exchanged between the nodes in some embodiments in order to identify the SL UEs and / or control / generate the SL configuration. The UE identifier(s) for one or more UEs can be indicated in the SL request or in another message from the UE to the network node. In addition, the network node can obtain the UE identifier information from a core network node / database (e.g., a third network node, rather than another base station).

[0169] In some embodiments, the node (MN or SN) receiving the SL request (i.e., SL connection / transmission setup related message) can decide whether to generate the SL configuration; and / or the node initiating the inter-node coordination regarding the SL configuration.

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

[0171] In some embodiments, the decision occurs after the inter-node coordination, such that the node (e.g., SN of UE2) receiving the request regarding the SL configuration / connection from one of the UEs (e.g., UE2) queries another node (e.g., the node can be simultaneously the MN / SN of UE1 and the MN of UE2) which node should generate the SL configuration of the SL UEs (e.g., UE1 and UE2). The query can be based on / included the received UE identifier(s), and the query message can be responded by a message (from the queried node) regarding which logical node will control / generate the SL configuration(s) of one of the UEs (e.g., UE2) or both UEs. In some embodiments, the query message can include the SL request message received from the SL UE (e.g., UE2). In some embodiments, the query response message can already include the generated SL configuration, which can be encapsulated with the RRC message of another node.

[0172] In a further embodiment, the indication (i.e. which logical node is controlling / generating the SL configuration) can be sent via a RRC reconfiguration message. The indication can be explicit or implicit. In case of implicit indication, the SL configuration is for example generated by the SN and this means that the SN belongs to the controlling RRC entity of the SL configuration. It should be noted that while in this example the corresponding logical node is the SN for one of the SL UEs, it can be the MN for the other SL UE. If there is no explicit and implicit indication, who generated the configuration can not be visible to the UEs, even if in the background the configuration is decided and / or generated by the same logical node. In case of implicit indication, the decision to generate the SL configuration in the same logical node can be visible, as at least one of the UEs can receive the configuration in a RRC PDU / message or RRC information element that is encapsulated / embedded in another RRC message, even if the configuration is conveyed by different nodes using different Signaling Radio Bearers (SRBs).

[0173] In a further embodiment, when a logical node needs to be changed (i.e. modify / change the MN / SN or add a SN) due to the setup of a DC, it is also possible to reconfigure the SL UEs with a new SL of the controlling RRC entity information.

[0174] In a further embodiment, in some architecture options (i.e. gNB CU / DU split architecture), the logical node can refer to a Central Unit (CU). However, in another embodiment, in some architecture options (i.e. gNB CU / DU split architecture), the logical node can refer to a Distributed Unit (DU).

[0175] Next consider an example of embodiments in which the respective wireless devices 12A, 12B in Figure 1 coordinate 22 with each other regarding the sidelink configuration 16A, 16B to be used. Figure 16B One such example is illustrated. In Figure 16B , instead of selecting a common logical node for controlling / generating the SL configuration, the nodes exchange information about what SL configuration can be used, as described in further embodiments below (focusing on the DC modification / change / addition procedure). Here, to not confuse with the previous embodiments, the MN and the SN can be different nodes and can simultaneously serve at least one of the SL UEs. For example, in Figure 16B , UE1 and UE2 are controlled by BS 1 and BS 2 respectively in terms of SL configuration. For both UE 1 and UE 2, BS1 can be the MN, while for both UEs, BS 2 can be the SN.

[0176] In one of the embodiments, the standalone gNB (i.e. MN) shares its SL configuration which it is planning to use for configuring SL UE with the SN when adding the SN. In another embodiment, the standalone gNB (i.e. MN) sends to the SN the SL configuration which the SN should use for configuring possible SL UE or the other way around (i.e. from SN to MN) when adding the SN.

[0177] In another embodiment, the coordination of SL configuration between MN and SN happens during SN addition procedure. However, in one embodiment, the coordination of SL configuration between MN and SN happens during SN modification procedure. In another embodiment, the coordination of SL configuration between MN and SN happens during SN change procedure. Further, in one of the embodiments, the coordination of SL configuration between MN and SN happens during intra- or inter-RAT handover procedure.

[0178] In another embodiment, the SL configuration refers to the logical channel ID (LCID) to RLC mode mapping (e.g. LCID 1 RLC AM, LCID 2 RLC UM, etc.) that will be used. However, in another embodiment, the SL configuration refers to the complete 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 presence / absence, etc.) that will be used to configure the SL UE under the MN or SN coverage.

[0179] In one embodiment, upon receiving the SL configuration from the MN, the SN stores it and uses it once it needs to configure a new SL UE.

[0180] In another embodiment, upon receiving the SL configuration from the MN, the SN sends back to the MN a set of SL parameters / configurations that will be acceptable for configuring possible SL UE (i.e. in case the configuration received by the MN is not applicable for the SN). However, in another embodiment, upon receiving the SL configuration from the MN, the SN sends an acknowledgement that the received configuration is accepted / rejected.

[0181] Next consider an example of an embodiment in which the wireless device 12A receives different intended sidelink configurations from different respective network nodes, and selects any one of the sidelink configurations that is consistent or compatible with the sidelink configuration 16B of the wireless device 12B with which it is to perform sidelink communication. Figure 16COne such example is shown, for example, where in terms of SL configuration, UE1 and UE2 are controlled by BS 2, and for UE1, BS 1 is either MN or SN, 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 the respective SL UE), it requests SL configuration from both gNBs and then selects the configuration that complies with the configuration of the peer UE. In another embodiment, after receiving the SL configuration from both gNBs, the UE sends an acknowledgement to both gNBs (or at least one of them) by informing whether to use the received SL configuration (accept or reject the received SL configuration).

[0182] In one of the embodiments, upon receiving the request for SL configuration from the UE, the NG-RAN node (e.g., MN or SN) includes in the sidelink configuration the source and destination L2 IDs to which the same SL configuration has been sent. This will help the UE to understand whether its peer UE is using a similar SL configuration or not.

[0183] Although the subject matter described herein can be implemented in any appropriate type of system, embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIG. 1. For simplicity, the wireless network of FIG. 1 only depicts network nodes 160 and 160b, and wireless devices (WDs) 110, 110b, and 110c. In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or end device). In the illustrated implementation, network node 160 and wireless device (WD) 110 are depicted as including additional detail. Figure 17 Figure 17 For simplicity, the wireless network of FIG. 1 only depicts network nodes 160 and 160b, and wireless devices (WDs) 110, 110b, and 110c. In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or end device). In the illustrated implementation, network node 160 and wireless device (WD) 110 are depicted as including additional detail.

[0184] ​The wireless network can comprise and / or interface with any type of network that is suitable to transmit and receive data, including, but not limited to a core network, a public switched telephone network (PSTN), the Internet, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN) such as a wireless LAN (WLAN) or a metropolitan area network (MAN), a broadband network, and the like, or any combination thereof. In some embodiments, the wireless network can include a wireless wide area network (WW AN) configured to communicate data at reduced power consumption and / or increased battery life. In some embodiments, the wireless network can include a narrowband network, such as a narrowband internet of things (NB-IoT) network. In some embodiments, the wireless network can include a 5G network.

[0185] The network 1706 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), 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 that are suitable for communication of data among devices.

[0186] The network node 1760 and the WD 1710 include various components described in greater detail below. These components can work together to provide network node and / or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in communication of data whether via wired or wireless connections.

[0187] As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other equipment within the wireless network to enable and / or provide wireless access to the wireless device and / or to perform other functions relating to the operation of the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations can be categorized based on the amount of coverage they provide (or, stated differently, the transmit power at which they operate) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node controlling a relay. Network nodes can also include one or more (or all) parts of a Distributed Radio Base Station, such as a centralized

[0188] In Figure 17 , the network node 1760 includes processing circuitry 1770, device readable medium 1780, interface 1790, auxiliary equipment 1784, power source 1786, power circuitry 1787, and antenna 1762. Although shown as a single unit in Figure 17The network node 1760 illustrated in the example wireless network of FIG. 18 can represent a device including a combination of hardware components that are illustrated, but other embodiments can include network nodes with different combinations of components. It is contemplated that a network node includes any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of the network node 1760 are depicted as single boxes located within a larger box or nested within multiple boxes, as context requires, in practice, a network node can comprise multiple different physical components being used together to implement a single illustrated component (e.g., the device readable medium 1780 can comprise multiple individual disk drives as well as multiple RAM modules).

[0189] Similarly, the network node 1760 can be composed of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), which can each have their own respective components. In certain scenarios in which the network node 1760 includes multiple separate components (e.g., BTS and BSC components), one or more of the individual components can be shared among several network nodes. For example, a single RNC can control multiple NodeB’s. In such scenarios, each unique pair of a NodeB and an RNC, in some instances, can be considered a single separate network node. In some embodiments, the network node 1760 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components (e.g., individual device readable medium 1780 for

[0190] The processing circuitry 1770 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by the processing circuitry 1770 can include, for example, converting information obtained by the processing circuitry 1770 into other information, comparing the information it has obtained with information that is stored in the network node, and / or performing any of the methods described herein, based on the information it has obtained. Determining by the processing circuitry 1770 can include as an outcome of the processing that it performs, causing a result to be stored in the storage medium 1772 or causing a result to be implemented.

[0191] The processing circuitry 1770 can include a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other processing circuitry, combinations of such processing circuitry, or other processing circuitry suitable for the functions described herein. The processing circuitry 1770, alone or in combination, can be a means for carrying out the functions described herein. For example, the processing circuitry 1770 can execute instructions stored in the device readable medium 1780 or in memory within the processing circuitry 1770 to provide the functionality described herein. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 1770 can include a system on a chip (SoC).

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

[0193] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device can be performed by the processing circuitry 1770 executing instructions as stored on a memory or device readable medium 1780 within the processing circuitry 1770. In alternative embodiments, some or all of the functionality can be provided by the processing circuitry 1770 without executing instructions stored on a separate or discrete device readable medium (such as, e.g., in a hardwired device). In any of those embodiments, whether the functionality is provided by the processing circuitry 1770 executing instructions stored on a device readable medium or by hardwired circuitry, the processing circuitry 1770 can be said to perform (or execute) that functionality. The benefits provided by such functionality are not limited to the processing circuitry 1770 alone or to other components of the network node 1760, but are enjoyed by network node 1760 as a whole, and / or by end users and the wireless network generally.

[0194] Device readable medium 1780 can include any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic materials, optical materials, random access memory (RAM), read only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a compact disk (CD), or a digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer-executable memory devices that store information, data, and / or instructions that can be used with processing circuitry 1770. Device readable medium 1780 can store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and / or other instructions capable of being executed by processing circuitry 1770 and utilized by network node 1760. Device readable medium 1780 can be used to store any calculations made by processing circuitry 1770 and / or any data received via interface 1790. In some embodiments, processing circuitry 1770 and device readable medium 1780 can be considered to be integrated.

[0195] Interface 1790 is used in the wired or wireless communication of signaling and / or data between network node 1760, network 1706, and / or WDs 1710. As illustrated, interface 1790 comprises port(s) / terminal(s) 1794 to send and receive data, for example, to and from network 1706 over a wired connection. Interface 1790 also includes radio front end circuitry 1792 that can be coupled to, or in some embodiments a part of, antenna 1762. Radio front end circuitry 1792 comprises filters 1798 and amplifiers 1796. Radio front end circuitry 1792 can be connected to antenna 1762 and processing circuitry 1770. Radio front end circuitry 1792 can be configured to condition signals

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

[0197] Antenna 1762 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1762 can be coupled to radio-front end circuitry 1790 and can be any type of antenna and / or antenna array capable of transmitting and / or receiving wireless

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

[0199] Power circuitry 1787 can comprise, or be coupled to, power management circuitry and be configured to supply the components of network node 1760 with power for performing the functionality described herein. Power circuitry 1787 can receive power from power source 1786. Power source 1786 and / or power circuitry 1787 can be configured to provide power to the

[0200] Alternative embodiments of network node 1760 can include additional components Figure 17 responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1760 can include user interface devices to allow input of information into network node 1760 and to allow output of information from network node 1760. This can allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1760.

[0201] As used herein, wireless device (WD) refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD is used interchangeably herein with user equipment (UE) and / or subscriber unit. Wireless communication can involve the transmission and / or reception of wireless signals using electromagnetic, radio, infrared and / or other types of signals suitable for conveying information over an air interface. In some embodiments, a WD can be configured to transmit and / or receive information without direct human interaction (e.g., automatically). For example, a WD can be designed to transmit information to a network on a predetermined schedule, in response to detected events, and / or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-mounted device (LEE), a laptop-mounted embedded equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD can support device-to-device (D2D) communication, e.g., using

[0202] As illustrated, 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 can include multiple sets of one or more of the illustrated 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 mention a few. These wireless technologies can be integrated into the same or different chip sets as other components within WD 1710.

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

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

[0205] Processing circuitry 1720 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware and / or software, operable to provide, either alone or in connection with other WD 1710 components, such as device readable medium 1730, WD 1710 functionality. Such functionality can include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1720 can execute instructions stored in device readable medium 1730 or in memory within processing circuitry 1720 to provide the functionality disclosed herein.

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

[0207] In certain embodiments, some or all of the functionality described herein as being performed by a WD can be performed by processing circuitry 1720 executing instructions stored on device readable medium 1730, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be performed by processing circuitry 1720 without executing instructions stored on a separate or discrete device readable medium (such as, for example, in a hard-wired device). In any of those embodiments, whether executing instructions stored on a device readable medium or not, processing circuitry 1720 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1720 alone or to WD 1710, but extend to its users, to other devices on the network, and to the network as a whole.

[0208] Processing circuitry 1720 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1720, can include, for example, converting information obtained by processing circuitry 1720 from one form to another, comparing or

[0209] Device readable medium 1730 can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and / or other instructions capable of being executed by processing circuitry 1720. Device readable medium 1730 can include computer memory (e.g., Random Access Memory

[0210] User interface equipment 1732 can provide components that allow for interaction with a human user of the WD 1710. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 1732 can be operable to produce output to the user and allow the user to provide input to the WD 1710. The type of interaction can vary depending on the type of user interface equipment 1732 installed in WD 1710. For example, if WD 1710 is a smart phone, interaction can be done via a touch screen; if WD 1710 is a smart meter, interaction can be done via a screen that provides usage (e.g., the number of gallons used) or a speaker that provides audible alerts (e.g., if smoke is detected). User interface equipment 1732 can include input interfaces, devices, and circuits, and output interfaces, devices, and circuits. User interface equipment 1732 is configured to allow input of information into WD 1710, and is connected to processing circuitry 1720 to allow processing circuitry 1720 to process input information. User interface equipment 1732 can include, for example, a microphone, a proximity or other sensor, keys / buttons, a touch display, one or more cameras, a USB port or other input circuitry. User interface equipment 1732 is also configured to allow output of information from WD 1710, and to allow processing circuitry 1720 to output information from WD 1710. User interface equipment 1732 can include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone

[0211] Auxiliary equipment 1734 is operable to provide more specialized functionality that can not be performed by WD. This can include specialized sensors for making measurements for various purposes, interfaces for additional types of communication, etc. The inclusion and type of components of auxiliary equipment 1734 can vary depending on the embodiment and / or scenario.

[0212] In some embodiments, power source 1736 can be in the form of a battery or battery pack. Other types of power sources, such as an external power supply (e.g., an electricity outlet), photovoltaic devices or power cells, can also be used. WD 1710 can further comprise power circuitry 1737 for delivering power from power source 1736 to the various parts of WD 1710 which need power from power source 1736 to carry out any of the functionality described or indicated herein. In some embodiments, power circuitry 1737 can include power management circuitry. Power circuitry 1737 can additionally or alternatively be operable to receive power from an external power source; in which case WD 1710 can be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical cable. Power circuitry 1737 can also be operable to deliver power from an external power source to power source 1736. This can be used, for example, for charging battery or battery pack 1736. Power circuitry 1737 can perform any formatting, converting, or other modification of power from power source 1736 as necessary to supply power to the respective components of WD 1710 which power from power source 1736 is supplied to.

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

[0214] In Figure 18In particular embodiments, the UE 1800 includes processing circuitry 1801 that is operatively coupled to the input / output interface 1805, the radio frequency (RF) interface 1809, the network connection interface 1811, the memory 1815 including the random access memory (RAM) 1817, the read-only memory (ROM) 1819, and the storage medium 1821, the communication subsystem 1831, the power source 1833, and / or any other component or any combination thereof. The storage medium 1821 includes an operating system 1823, application program 1825, and data 1827. In other embodiments, the storage medium 1821 can include other similar types of information. Some of the components in the Figure 18 In particular embodiments, the UE 1800 includes processing circuitry 1801 that is operatively coupled to the input / output interface 1805, the radio frequency (RF) interface 1809, the network connection interface 1811, the memory 1815 including the random access memory (RAM) 1817, the read-only memory (ROM) 1819, and the storage medium 1821, the communication subsystem 1831, the power source 1833, and / or any other component or any combination thereof. The storage medium 1821 includes an operating system 1823, application program 1825, and data 1827. In other embodiments, the storage medium 1821 can include other similar types of information. Some of the components in the

[0215] In Figure 18 In particular embodiments, the processing circuitry 1801 can be configured to process computer instructions and data. The processing circuitry 1801 can be configured as any sequential state machine coupled to memory that is capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken and from that specify the operational steps of the machine. Note that the set of instructions can not specify every aspect or step of the machine's operation. For example, the set of instructions can specify actions, from which the machine software-implementation can derive the actual operational steps, but the set of instructions can not specify the operational steps themselves. The machine can be a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other processing logic that can fetch and execute a set of instructions from instructions storage that configure the machine to perform operations. The instructions can be software instructions stored in memory or in another computer readable medium, hardware logic that can be configured to perform the operations, or some combination thereof. The software can be software modules that implement one or more applications or software tools, software drivers, firmware, microcode, or any other software that can be stored in memory and executed by the machine. The software can also include, at least in part, hardware logic, such as, for example, a hardware implementation of all or part of one or more software modules or tools. The software can also include, at least in part, some combination of hardware logic and software.

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

[0217] In Figure 18 RF interface 1809 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1811 can be configured to provide a communication interface to network 1843a. Network 1843a can encompass

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

[0219] The storage medium 1821 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), soft disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High-Density Digital Versatile Disc (DVD) disc drive, internal hard disk drive, Blu-Ray disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, 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 can allow the UE 1800 to access computer-executable instructions, application programs or the like, stored on a transitory or non-transitory storage medium to off-load data or to store data in excess of the internal memory capacity of the UE 1800. An article of manufacture, such as one utilizing a communication system can be tangibly embodied in the storage medium 1821, which can comprise a device readable medium.

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

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

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

[0223] Figure 19 is a schematic block diagram illustrating a virtualization environment 1900 in which functions implemented by some embodiments can be virtualized. In this context, virtualization means the creation of a virtual version of the device or device comprising the virtualization of hardware platforms, storage devices and networking resources. As used herein, virtualization can apply to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as a virtual component (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[0224] In some embodiments, some or all of the functionality described herein can 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 hardware nodes 1930. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be entirely virtualized.

[0225] These functions can be implemented by one or more applications 1920 (which alternatively can be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. An application 1920 runs in the virtualization environment 1900 which provides hardware 1930 including processing circuitry 1960 and memory 1990. The memory 1990 contains instructions 1995 executable by the processing circuitry 1960 whereby the application 1920 is operative to provide one or more of the features, benefits, and / or functions disclosed herein.

[0226] Virtualization environment 1900 comprises general-purpose or special-purpose network hardware devices 1930 comprising a set of one or more processors or processing circuitry 1960, which can be commercial off-the-shelf (COTS) processors, dedicated Application-Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise memory 1990-1 which can be non-persistent memory for temporarily storing instructions 1995 or software executed by processing circuitry 1960. Each hardware device can comprise one or more network interface controllers (NICs) 1970 (also known as network interface cards) that include physical network interfaces 1980. Each hardware device can further comprise non-transitory, persistent, machine-readable storage media 1990-2 having stored therein software 1995 or

[0227] Virtual machines 1940 comprise virtual processing, virtual storage, virtual networking or interface, and virtual storage devices, and can be run by a corresponding virtualization layer 1950 or hypervisor. Different embodiments of the instance of virtual appliance 1920 can be implemented on one or more of the virtual machines 1940, and the implementation can be made in different ways.

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

[0229] As Figure 19As shown in FIG. 19B, hardware 1930 can be a standalone network node with generic or specific components. Hardware 1930 can comprise antenna 19225 and can implement some functions via virtualization. Alternatively, hardware 1930 can be part of a larger cluster of hardware, such as in a data center or customer premise equipment (CPE), where many hardware nodes work together as part of an infrastructure and are managed via management and orchestration (MANO) 19100, which, among others, oversees lifecycle management of applications 1920.

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

[0231] In the context of NFV, virtual machine 1940 can be a software implementation of a physical machine that runs programs just as if they were executing on a physical, non-virtualized machine. Each of virtual machines 1940, and that part of hardware 1930 that executes that virtual machine, be it hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with others of the virtual machines 1940, forms a separate virtual network element (VNE).

[0232] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that are run in one or more virtual machines 1940 on top of hardware networking infrastructure 1930 and corresponds to Figure 19 application 1920 in FIG. 19A.

[0233] In some embodiments, one or more radio units 19200 that each include one or more transmitters 19220 and one or more receivers 19210 can be coupled to one or more antennas 19225. Radio units 19200 can communicate directly with hardware nodes 1930 via one or more appropriate network interfaces and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0234] In some embodiments, some signaling can be effected with the use of control system 19230, which can alternatively be used for communication between hardware nodes 1930 and radio units 19200.

[0235] Figure 20 FIG. 19B illustrates a telecommunications network connected via an intermediate network to a host computer according to some embodiments. In particular, reference is made to Figure 20According to an embodiment, the communication system includes a telecommunication network 2010, such as a 3GPP-type cellular network, which comprises access networks 2011, such as radio access networks, and a core network 2014. The access network 2011 comprises a plurality 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, within which wireless devices can typically communicate with the base station 2012a, 2012b, 2012c. 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 coverage area 2013c is configured to wirelessly connect to, or be paged by, the corresponding base station 2012c. A second UE 2092 in coverage area 2013a is wirelessly connectable to the corresponding base station 2012a. While a plurality of UEs 2091, 2092 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 2012.

[0236] The telecommunication network 2010 is itself connected to a host computer 2030, which can be embodied in hardware and / or software, in a standalone server, an on-cloud server, a distributed server, or a processing resource in a server farm. The host computer 2030 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider. Connections 2021 and 2022 between the telecommunication network 2010 and the host computer 2030 can extend directly from the core network 2014 to the host computer 2030 or can go via an optional intermediate network 2020. The intermediate network 2020 can be one or more of a public, private, or hosted networks, and can include backbone networks, the Internet, or a combination of these. In particular, the intermediate network 2020 can include one or more of the same networks as the access network 2011.

[0237] Figure 20The communication system as a whole enables connectivity between the connected UEs 2091, 2092 and the host computer 2030. The connectivity can be described as an over-the-top (OTT) connection 2050. The host computer 2030 and the connected UEs 2091, 2092 are configured to communicate data and / or signaling over the OTT connection 2050 using the access network 2011, the core network 2014, any intermediate network 2020, and possible further infrastructure (not shown) as intermediaries. The OTT connection 2050 can be transparent in the sense that the participating communication devices through which the OTT connection 2050 passes are unaware of the routing of uplink and downlink communications. For example, a base station 2012 can not or need not be informed about on a message incoming from the host computer 2030 that was source by a UE 2091 to which the base station 2012 will transfer (or has transferred) the message. Similarly, the base station 2012 need not be aware of where or how a message coming to the UE 2091 from the base station 2012 will be further routed to.

[0238] Reference will now be made to Figure 21 Example implementations of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to the following Figure 21 Fig. 13 illustrates a host computer communicating via a base station with a user equipment according to some embodiments. In communication system 1300, host computer 1310 comprises hardware 1315 including communication interface 1316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1300. Host computer 1310 further comprises processing circuitry 1318, which can have storage and / or processing capabilities. In particular, processing circuitry 1318 can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1310 further comprises software 1311, which is stored in or accessible by host computer 1310 and executable by processing circuitry 1318. Software 1311 includes host application 1312. Host application 1312 can be operable to provide a service to a remote user, such as UE 1330 connecting via OTT connection 1350 terminating at UE 1330 and host computer 1310. In providing the service, host application 1312 can provide user data which is transmitted using OTT connection 1350. The user data can be transmitted in the form of data packets.

[0239] The communication system 2100 further includes a base station 2120, which is disposed in the telecommunications system and includes hardware 2125 enabling it to communicate with a host computer 2110 and a UE 2130. Hardware 2125 may include a communication interface 2126 for establishing and maintaining a wired or wireless connection to different communication devices of the communication system 2100, and for establishing and maintaining at least a connection with the coverage area served by the base station 2120. Figure 21 The radio interface 2127 of the UE 2130 (not shown) is for the wireless connection 2170. The communication interface 2126 can be configured to facilitate a connection 2160 to the host computer 2110. The connection 2160 can be direct, or it can be via the core network of the telecommunications system (…). Figure 21 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 2125 of base station 2120 further includes a processing circuitry system 2128, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Base station 2120 further has software 2121 stored internally or accessible via an external connection.

[0240] The communication system 2100 further includes the previously mentioned UE 2130. The hardware 2135 of the UE 2130 may include a radio interface 2137 configured to establish and maintain a wireless connection 2170 with a base station serving a coverage area where the UE 2130 is currently located. The hardware 2135 of the UE 2130 further includes a processing circuitry system 2138, which may include 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, which is stored in or accessible to the UE 2130 and executable by the processing circuitry system 2138. The software 2131 includes a client application 2132. The client application 2132 may be operable to provide services to human or non-human users via the UE 2130 with the support of the host computer 2110. In host computer 2110, the executing host application 2112 can communicate with the executing client application 2132 via an OTT connection 2150 terminated between UE 2130 and host computer 2110. In providing services to the user, client application 2132 can receive request data from host application 2112 and provide user data in response to the request data. OTT connection 2150 can transmit both request data and user data. Client application 2132 can interact with the user to generate the user data it provides.

[0241] Notice, Figure 21 The host computer 2110, base station 2120, and UE 2130 shown in the diagram can respectively connect with...Figure 20 one of the host computer 2030, the base station 2012a, 2012b, 2012c, and one of the UEs 2091, 2092 are similar or identical to those of FIG. 13. That is, the inner workings of these entities can be as shown in FIG. 14 and independently, the surrounding network topology can be that of FIG. 13. Figure 21 Figure 20

[0242] In FIG. 14, OTT connection 2150 has been drawn abstractly to illustrate the communication between host computer 2110 and UE 2130 via base station 2120, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure can determine the routing, which it can be configured to hide from UE 2130 or from the service provider operating host computer 2110, or both. While OTT connection 2150 is active, the network infrastructure can further take decisions that change the routing (e.g., in response to changes in load balancing considerations or in configuration of the network). Figure 21

[0243] Wireless connection 2170 between UE 2130 and base station 2120 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 2130 using OTT connection 2150, in which wireless connection 2170 forms the last segment.

[0244] ​​​For the purposes of monitoring data rates, latency, and other factors on which one or more embodiments improve, a measurement procedure can be provided. There can further be an optional network functionality for reconfiguring the OTT connection 2150 between the host computer 2110 and the UE 2130, in response to measurements results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 2150 can be implemented in software 2111 and the hardware 2115 of the host computer 2110 or in software 2131 and the hardware 2135 of the UE 2130, or both. In embodiments, sensors (not shown) can be deployed in or in association with the communication devices through which the OTT connection 2150 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 2111, 2131 can compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2150 can include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 2120, and it can be unknown or unnoticed by the base station 2120. Such procedures and functionality can be known and practiced in the art. In certain embodiments, measurements can involve proprietary UE signaling facilitating the host computer's 2110 measurements of throughput, propagation times, latency, and the like. The measurements can be implemented in that the software 2111, 2131 causes messages to be transmitted, using the OTT connection 2150, while it monitors propagation times, errors, and so on.

[0245] Figure 22 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a UE in accordance with one embodiment. The host computer, base station, and UE can be those described with reference to Figure 20 and 21 for simplicity of the present disclosure, only reference will be made in this section to the accompanying drawings of Figure 22 . In step 2210, the host computer provides user data. In substep 2211 (which can 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 can be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2240 (which can also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0246] Figure 23is a flow chart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described earlier with reference to Figure 20 and 21 Fig. 1. In the interest of simplicity, in this section we will only include references to the Figure 23 Fig. 1. In step 2310 of the method, the host computer provides user data. In an optional substep (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 can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2330 (which can be optional), the UE receives the user data carried in the transmission.

[0247] Figure 24 is a flow chart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described earlier with reference to Figure 20 and 21 Fig. 1. In the interest of simplicity, in this section we will only include references to the Figure 24 Fig. 1. In step 2410 (which can be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2420, the UE provides user data. In substep 2421 of step 2420 (which can be optional), the UE provides the user data by executing a client application. In substep 2411 of step 2410 (which can be optional), the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application can further consider user input received from the user. Regardless of the specific manner in which the user data is provided, in substep 2430 (which can be optional), the UE initiates a transmission of the user data to the host computer. In step 2440 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0248] Figure 25 is a flow chart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described earlier with reference to Figure 20 and 21 Fig. 1. In the interest of simplicity, in this section we will only include references to the Figure 25with reference to the accompanying drawings. In step 2510, which can be optional, the base station receives user data from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2520, which can be optional, the base station initiates transmission of the received user data to the host computer. In step 2530, which can be optional, the host computer receives the user data carried in the transmission initiated by the base station.

[0249] Any appropriate steps, methods, features, functions, or benefits expressly listed herein can be performed by one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus can comprise a number of these functional units. These functional units can be implemented via processing circuitry and other digital hardware, which can include one or more microprocessors or microcontrollers, other digital hardware, including digital signal processors (DSPs), special-purpose computer chips, etc. The processing circuitry can be configured to execute program code stored in memory, which can 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, etc. The program code stored in memory includes program instructions for executing one or more telecommunication and / or data communication protocols and instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry can be used to cause the respective functional units to perform corresponding functions according to one or more embodiments of the present disclosure.

[0250] Embodiments herein then typically include a communication system including a host computer, in view of the above. The host computer can include processing circuitry configured to provide user data. The host computer can further include a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network can include a base station having a radio interface and processing circuitry configured to perform any of the steps of any of the embodiments described above for a base station.

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

[0252] In some embodiments, the communication system further includes the UE, wherein the UE is configured to communicate with the base station.

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

[0254] The embodiments herein also include methods implemented in a communication system including a host computer, a base station, and a user equipment (UE). The method comprises at the host computer, providing user data. The method can further comprise initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The base station performs any of the steps of any of the embodiments described above for a base station.

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

[0256] In some embodiments, the user data is provided at the host computer by executing a host application. In such case, the method further comprises executing, at the UE, a client application associated with the host application.

[0257] The embodiments herein also include a user equipment (UE) configured to communicate with a base station. The UE includes processing circuitry configured to perform any of the steps of any of the embodiments described above for a UE, and a radio interface.

[0258] The embodiments herein further include a communication system including a host computer. The host computer includes processing circuitry 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 includes a radio interface and processing circuitry. The components of the UE are configured to perform any of the steps of any of the embodiments described above for a UE.

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

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

[0261] The embodiments also include methods implemented in a communication system including a host computer, a base station, and a user equipment (UE). The method comprises, at the host computer: providing user data; and initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The UE performs any of the steps of any of the embodiments described above for a UE.

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

[0263] The embodiments herein further include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The UE includes a radio interface and processing circuitry. The UE's processing circuitry is configured to perform any of the steps of any of the embodiments described above for the UE.

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

[0265] In some embodiments, the communication system further includes the base station. In such case, the base station includes a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer user data carried by a transmission from the UE to the base station.

[0266] In some embodiments, the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

[0267] In some embodiments, the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

[0268] The 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 comprises, at the host computer, receiving user data to be transmitted to the UE. The UE performs any of the steps of any of the embodiments described above for the UE.

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

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

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

[0272] Embodiments also include a communication system including a host computer. The host computer includes a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The base station includes a radio interface and processing circuitry. The base station's processing circuitry is configured to perform any of the steps of any of the embodiments described above for a base station.

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

[0274] In some embodiments, the communication system further includes the UE. The UE is configured to communicate with the base station.

[0275] In some embodiments, the host computer's processing circuitry is configured to execute a host application. And, 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.

[0276] Further, embodiments include a method implemented in a communication system including a host computer, a base station, and a user equipment (UE). The method includes, at the host computer, receiving user data originating from a transmission from a UE to a base station. The UE performs any of the steps of any of the embodiments described above for a UE.

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

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

[0279] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the technology to which they belong, unless a different meaning is explicitly given and / or is apparent from the context in which it is used. All references to a / an / the item, device, component, means, step, etc. are to be interpreted openly as referring to at least one instance of whatever is referred to unless otherwise indicated. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed unless explicitly stated. Any of the embodiments of any of the methods disclosed herein can be performed in any order unless otherwise indicated. Any feature of any of the embodiments of the disclosure can be applied to any of the other embodiments, wherever it makes technical sense. Likewise, any advantage of any of the embodiments can be applied to any of the other embodiments, and vice versa. Other objectives, features and advantages of the embodiments will be apparent from this description.

[0280] The term "unit" can have the conventional meaning in the field of electronics, electrical devices, and / or electronic devices, and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer program instructions, or instructions for carrying out various tasks, processes, computations, outputs, and / or displays, etc., as described herein.

[0281] Some embodiments of what is envisioned herein are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the disclosed subject matter. The disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, they are provided for purposes of example and to convey the scope of the subject matter to the skilled artisan.

[0282] It is noted that modifications and other embodiments of the disclosed application(s) are intended to be included within the scope of the disclosed subject matter. Therefore, it is to be understood that the present application(s) are not to be limited to the particular embodiments disclosed in this specification. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0283] With this limitation in mind, the following sets of embodiments enumerate various aspects herein.

[0284] Group A embodiments

[0285] A1. A method performed by a wireless device, the method comprising:

[0286] receiving, from a network node, an indication indicating which network node controls sidelink configuration of the wireless device.

[0287] A2. A method performed by a wireless device, the method comprising:

[0288] receiving a sidelink configuration from each of a plurality of network nodes serving the wireless device; and

[0289] selecting, from the received sidelink configurations, a sidelink configuration that is consistent or compatible with a sidelink configuration of another wireless device with which the wireless device is to communicate over a sidelink.

[0290] A3. The method of embodiment A2, further comprising transmitting, 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.

[0291] A4. The method of any of embodiments A2-A3, further comprising requesting a sidelink configuration from each of the plurality of network nodes.

[0292] A5. The method of any of embodiments A2-A4, further comprising receiving, from each of one or more of the network nodes serving a wireless device, information identifying one or more other wireless devices to which the network node has transmitted a same sidelink configuration received from that network node.

[0293] A6. The method of any of embodiments A1-A5, wherein at least one of the network nodes acts as a master node for a multi-connectivity operation and at least one other of the network nodes acts as a secondary node for the multi-connectivity operation.

[0294] A7. The method of any of embodiments A1-A6, wherein the sidelink configuration consists of one or more of:

[0295] a sidelink radio bearer configuration;

[0296] a quality of service flow to sidelink radio bearer mapping;

[0297] a resource pool configuration for sidelink communication;

[0298] a radio link control, RLC, mode configuration, the RLC mode configuration comprising a configuration of RLC unacknowledged mode or RLC acknowledged mode;

[0299] a logical channel ID to RLC mode mapping; or

[0300] a default sidelink configuration parameter.

[0301] AA. The method of any of the preceding embodiments, further comprising:

[0302] providing user data; and

[0303] forwarding the user data to the host computer via a transmission to a base station.

[0304] Group B embodiments

[0305] B1. A method performed by a network node, the method comprising:

[0306] controlling a sidelink configuration of each of a plurality of wireless devices that are to communicate with each other over a sidelink.

[0307] B2. The method of embodiment B1, wherein the controlling is based on the network node serving each of the plurality of wireless devices.

[0308] B3. The method of any of embodiments B1-B2, further comprising deciding, by the network node, to control the sidelink configuration of each of the plurality of wireless devices based on the network node serving each of the plurality of wireless devices.

[0309] B4. The method of any of embodiments B1-B3, wherein at least one of the plurality of wireless devices is served by the network node and one or more other network nodes.

[0310] B5. The method of any of embodiments B1-B4, wherein the network node acts as a master node for at least one of the plurality of wireless devices in a multiple connectivity operation.

[0311] B6. The method of embodiment B5, wherein the network node acts as a secondary node for at least one other of the plurality of wireless devices in the multiple connectivity.

[0312] B7. The method of any of embodiments B1-B6, wherein at least one of the plurality of wireless devices is not configured for multiple connectivity or is not operating in multiple connectivity.

[0313] B8. The method of any of embodiments B1-B7, further comprising determining that the plurality of wireless devices are to communicate with each other over a sidelink based at least in part on information received from another network node.

[0314] B9. The method of embodiment B8, wherein the information received from the another network node comprises identification information identifying at least one of the plurality of wireless devices.

[0315] B10. The method of embodiment B9, wherein the identification information comprises a layer 2 identification of the at least one of the plurality of wireless devices.

[0316] B11. The method of any of embodiments B1-B10, further comprising transmitting an indication to each of one or more of the plurality of wireless devices, the indication indicating that the network node controls the sidelink configuration of the wireless device or indicating that the network node controls the sidelink configuration of each of the plurality of wireless devices.

[0317] B12. The method of any of embodiments B1-B4 and B7-B11, wherein the network node is a central unit or a distributed unit of a radio network node.

[0318] B13. The method of any of embodiments B1-B12, wherein the controlling comprises, for each of the plurality of wireless devices, generating a sidelink configuration and transmitting the sidelink configuration to the wireless device or to another network node for relaying to the wireless device.

[0319] B14. The method of any of embodiments B1-B13, wherein the controlling comprises controlling sidelink configurations of the plurality of wireless devices to be consistent or compatible with each other.

[0320] B15. The method of any of embodiments B1-B14, wherein the sidelink configuration of a wireless device consists of one or more of:

[0321] a sidelink radio bearer configuration;

[0322] a quality of service flow to sidelink radio bearer mapping;

[0323] a resource pool configuration for sidelink communication;

[0324] a radio link control, RLC, mode configuration, the RLC mode configuration comprising a configuration of RLC unacknowledged mode or RLC acknowledged mode;

[0325] a logical channel ID to RLC mode mapping; or

[0326] a default sidelink configuration parameter.

[0327] B16. The method of any of embodiments B1-B15, wherein the plurality of wireless devices are requesting or have requested sidelink configurations for the purpose of communicating with each other over sidelinks.

[0328] Group BB embodiments

[0329] BB1. A method performed by a network node, the method comprising:

[0330] selecting, from a plurality of candidate network nodes, a network node for controlling a sidelink configuration of each of a plurality of wireless devices that are to communicate with each other over sidelinks.

[0331] BB2. The method of embodiment BB1, wherein the selecting comprises selecting a network node that serves each of the plurality of wireless devices.

[0332] BB3. The method of any of embodiments BB1-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 that is selected to control the sidelink configuration of each of the plurality of wireless devices.

[0333] BB4. The method of any of embodiments BB1-BB3, wherein at least one of the plurality of wireless devices is served by multiple network nodes in a multiple connectivity operation.

[0334] BB5. The method of any of embodiments BB1-BB4, wherein the selected network node acts as a master node for at least one of the plurality of wireless devices in a multiple connectivity operation.

[0335] BB6. The method of embodiment BB5, wherein the selected network node acts as a secondary node for at least one other wireless device of the plurality of wireless devices in a multiple connectivity.

[0336] BB7. The method of any of embodiments BB1-BB6, wherein at least one of the plurality of wireless devices is not configured for multiple connectivity or is not operating in multiple connectivity.

[0337] BB8. The method of any of embodiments BB1-BB7, further comprising determining that the plurality of wireless devices are to communicate with each other over a sidelink based at least in part on information received from another network node.

[0338] BB9. The method of embodiment BB8, wherein the information received from the other network node comprises identification information identifying at least one of the plurality of wireless devices.

[0339] BB10. The method of embodiment BB9, wherein the identification information comprises a layer 2 identification of the at least one of the plurality of wireless devices.

[0340] BB11. The method of any of embodiments BB1-BB10, further comprising transmitting an indication to each of one or more of the plurality of wireless devices, the indication 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 plurality of wireless devices.

[0341] BB12. The method of any of embodiments BB1-BB4 and BB7-BB11, wherein the selected network node is a central unit or a distributed unit of a radio network node.

[0342] BB13. The method of any of embodiments BB1-BB12, wherein the network node selected to control a sidelink configuration of each of the plurality of wireless devices is selected to, for each of the plurality of wireless devices, generate the sidelink configuration and transmit the sidelink configuration to the wireless device.

[0343] BB14. The method of any of embodiments BB1-BB13, wherein the network node selected to control a 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.

[0344] BB15. The method of any of embodiments BB1-BB14, wherein the sidelink configuration of the wireless device consists of one or more of:

[0345] a sidelink radio bearer configuration;

[0346] a quality of service flow to sidelink radio bearer mapping;

[0347] a resource pool configuration for sidelink communication;

[0348] a radio link control, RLC, mode configuration, the RLC mode configuration comprising a configuration of RLC unacknowledged mode or RLC acknowledged mode;

[0349] a logical channel ID to RLC mode mapping; or

[0350] a default sidelink configuration parameter.

[0351] BB16. The method of any of embodiments BB1-BB15, wherein a plurality of wireless devices are requesting or have requested a sidelink configuration for the purpose of communicating with each other over a sidelink.

[0352] BB17. The method of any of embodiments BB1-BB16, wherein the selecting is performed in response to receiving a request for a sidelink configuration from one or more of the plurality of wireless devices.

[0353] BB18. The method of any of embodiments BB1-BB16, wherein the selecting is performed in response to receiving a query from one of the candidate network nodes querying about which network node is to control the sidelink configuration of each of the plurality of wireless devices.

[0354] BB19. The method of any of embodiments BB1-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 primary node for a 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 a multi-connectivity operation of at least one of the wireless devices.

[0355] Group BBB embodiments

[0356] BBB1. A method performed by a first network node, the method comprising:

[0357] coordinating, with a second network node, a sidelink configuration for each of a plurality of wireless devices that are to communicate with each other over a sidelink.

[0358] BBB2. The method of embodiment BBB1, wherein the coordinating comprises:

[0359] transmitting, to the second network node, information indicating one or more sidelink configurations that can be used at the first network node; and / or

[0360] receiving, from the second network node, information indicating one or more sidelink configurations that can be used at the second network node.

[0361] BBB3. The method of any of embodiments BBB1-BBB2, wherein the coordinating comprises:

[0362] transmitting, to the second network node, information indicating one or more sidelink configurations that the second network node is to use; and / or

[0363] receiving, from the second network node, information indicating one or more sidelink configurations that the first network node is to use.

[0364] BBB4. The method of any of embodiments BBB1-BBB2, wherein the coordinating comprises:

[0365] transmitting, to the second network node, information indicating one or more sidelink configurations that the first network node suggests using; and / or

[0366] receiving, from the second network node, information indicating one or more sidelink configurations that the second network node suggests using.

[0367] BBB5. The method of any of embodiments BBB1-BBB2, wherein the coordinating comprises:

[0368] transmitting, to the second network node, information indicating one or more sidelink configurations that the first network node accepts or rejects using; and / or

[0369] receiving, from the second network node, information indicating one or more sidelink configurations that the second network node accepts or rejects using.

[0370] BBB6. The method of any of embodiments BBB1-BBB5, wherein the first network node acts as a master node for at least one of the plurality of wireless devices in a multi-connectivity operation, and wherein the second network node acts as a secondary node for at least one other wireless device in the multi-connectivity operation.

[0371] BBB7. The method of any of embodiments BBB1-BBB6, wherein at least two of the wireless devices do not have a common serving network node.

[0372] BBB8. The method of any of embodiments BBB1-BBB7, further comprising deciding, based on the coordination, a sidelink configuration for each of one or more of the plurality of wireless devices served by the first network node.

[0373] BBB9. The method of any of embodiments BBB1-BBB8, wherein the coordination is performed during or as part of a procedure for adding or modifying a second node for at least one of the plurality of wireless devices in multi-connectivity.

[0374] BBB10. The method of any of embodiments BBB1-BBB8, wherein the coordination is performed during or as part of a handover procedure for one or more of the plurality of wireless devices.

[0375] BBB11. The method of any of embodiments BBB1-BBB10, wherein at least one of the plurality of wireless devices is served by a plurality of network nodes.

[0376] BBB12. The method of embodiment BBB8, further comprising transmitting the decided sidelink configuration towards each of one or more of the plurality of wireless devices served by the first network node.

[0377] BBB13. The method of any of embodiments BBB1-BBB13, wherein the sidelink configuration for a wireless device consists of one or more of:

[0378] a sidelink radio bearer configuration;

[0379] a quality of service flow to sidelink radio bearer mapping;

[0380] a resource pool configuration for sidelink communication;

[0381] a radio link control, RLC, mode configuration, the RLC mode configuration comprising a configuration of RLC unacknowledged mode or RLC acknowledged mode;

[0382] a logical channel ID to RLC mode mapping; or

[0383] a default sidelink configuration parameter.

[0384] BBB14. The method of any of embodiments BBB1-BBB14, wherein the plurality of wireless devices are requesting or have requested a sidelink configuration for the purpose of communicating with each other over a sidelink.

[0385] BB. The method of any of the preceding embodiments, further comprising:

[0386] obtaining user data; and

[0387] forwarding user data to a host computer or a wireless device.

[0388] Group C embodiments

[0389] C1. A wireless device configured to perform any of the steps of any of the embodiments of Group A.

[0390] C2. A wireless device comprising processing circuitry configured to perform any of the steps of any of the embodiments of Group A.

[0391] C3. A wireless device, comprising:

[0392] communication circuitry; and

[0393] processing circuitry configured to perform any of the steps of any of the embodiments of Group A.

[0394] C4. A wireless device, comprising:

[0395] processing circuitry configured to perform any of the steps of any of the embodiments of Group A; and

[0396] power supply circuitry configured to supply power to the wireless device.

[0397] C5. A wireless device, comprising:

[0398] processing circuitry and a memory, the memory containing instructions executable by the processing circuitry, whereby the wireless device is configured to perform any of the steps of any of the embodiments of Group A.

[0399] C6. A user equipment (UE), comprising:

[0400] an antenna configured to transmit and receive wireless signals;

[0401] radio front-end circuitry connected to the antenna and processing circuitry, and configured to condition signals passed between the antenna and the processing circuitry;

[0402] the processing circuitry configured to perform any of the steps of any of the embodiments of Group A;

[0403] an input interface connected to the processing circuitry, and configured to allow input of information into the UE to be processed by the processing circuitry;

[0404] an output interface connected to the processing circuitry and configured to output information, which has been processed by the processing circuitry, from the UE; and

[0405] a battery connected to the processing circuitry and configured to supply power to the UE.

[0406] C7. A computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to carry out the steps of any of the Group A embodiments.

[0407] C8. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0408] C9. A radio network node configured to perform any of the steps of any of the Group B embodiments.

[0409] C10. A radio network node comprising processing circuitry configured to perform any of the steps of any of the Group B embodiments.

[0410] C11. A radio network node comprising:

[0411] communication circuitry; and

[0412] processing circuitry configured to perform any of the steps of any of the Group B embodiments.

[0413] C12. A radio network node comprising:

[0414] processing circuitry configured to perform any of the steps of any of the Group B embodiments;

[0415] power supply circuitry configured to supply power to the radio network node.

[0416] C13. A radio network node comprising:

[0417] processing circuitry and a memory containing instructions executable by said processing circuitry, whereby said radio network node is configured to perform any of the steps of any of the Group B embodiments.

[0418] C14. The radio network node of any of embodiments C9-C13, wherein the radio network node is a base station.

[0419] C15. A computer program comprising instructions which, when executed by at least one processor of a radio network node, causes the radio network node to carry out the steps of any of the Group B embodiments.

[0420] C16. The computer program of embodiment C14, wherein the radio network node is a base station.

[0421] C17. A carrier containing the computer program of any of embodiments C15-C16, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0422] Group D embodiments

[0423] D1. A communication system including a host computer comprising:

[0424] processing circuitry configured to provide user data; and

[0425] a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

[0426] wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

[0427] D2. The communication system of the previous embodiment, further including the base station.

[0428] D3. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

[0429] D4. The communication system of the previous 3 embodiments, wherein:

[0430] the host computer’s processing circuitry is configured to execute a host application, thereby providing the user data; and

[0431] the UE includes processing circuitry configured to execute a client application associated with said host application.

[0432] D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0433] providing user data at the host computer; and

[0434] initiating a transmission carrying the user data from the host computer to the UE via the cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

[0435] D6. The method of the preceding embodiment, further comprising transmitting, at the base station, the user data.

[0436] D7. The method of the preceding 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising executing, at the UE, a client application associated with the host application.

[0437] D8. A user equipment (UE) configured to communicate with a base station, the UE comprising processing circuitry configured to perform any of the preceding 3 embodiments and a radio interface.

[0438] D9. A communication system including a host computer comprising:

[0439] processing circuitry configured to provide user data; and

[0440] a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

[0441] wherein the UE comprises a radio interface and processing circuitry, the components of the UE being configured to perform any of the steps of any of the embodiments of Group A.

[0442] D10. The communication system of the preceding embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0443] D11. The communication system of the preceding 2 embodiments, wherein:

[0444] the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

[0445] the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0446] D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0447] providing, at the host computer, user data; and

[0448] initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the embodiments of Group A.

[0449] D13. The method of the preceding embodiment, further comprising receiving, at the UE from the base station, the user data.

[0450] D14. A communication system including a host computer comprising:

[0451] a communication interface configured to receive user data originating from a user equipment (UE) to a base station,

[0452] wherein the UE includes a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.

[0453] D15. The communication system of the previous embodiment, further including the UE.

[0454] D16. The communication system of the previous 2 embodiments, further including the base station, wherein the base station includes a radio interface configured to communicate with the UE and a communication interface configured to forward the user data carried by transmissions from the UE to the base station to the host computer.

[0455] D17. The communication system of the previous 3 embodiments, wherein:

[0456] the host computer’s processing circuitry is configured to execute a host application; and

[0457] the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

[0458] D18. The communication system of the previous 4 embodiments, wherein:

[0459] the host computer’s processing circuitry is configured to execute a host application, thereby providing request data; and

[0460] the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

[0461] D19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0462] at the host computer, receiving user data transmitted from the UE to the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

[0463] D20. The method of the previous embodiment, further comprising:

[0464] at the UE, providing the user data to the base station.

[0465] at the UE, executing a client application, thereby providing the user data to be transmitted; and

[0466] At the host computer, a host application associated with the client application is executed.

[0467] D22. The method of the preceding 3 embodiments, further including:

[0468] executing the client application at the UE; and

[0469] receiving input data at the UE for the client application, the input data being provided at the host computer by executing the host application associated with the client application,

[0470] wherein user data is provided by the client application in response to the input data.

[0471] D23. A communication system including a host computer comprising communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps of any of the Group B embodiments.

[0472] D24. The communication system of the preceding embodiment, further including the base station.

[0473] D25. The communication system of the preceding 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

[0474] D26. The communication system of the preceding 3 embodiments, wherein:

[0475] the processing circuitry of the host computer is configured to execute the host application;

[0476] the UE is configured to execute a client application associated with the host application, thereby providing user data for reception by the host computer.

[0477] D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

[0478] at the host computer, receiving from the base station user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

[0479] D28. The method of the preceding embodiment, further comprising: at the base station, receiving the user data from the UE.

[0480] D29. The method of the preceding 2 embodiments, further comprising: at the base station, initiating transmission of the received user data to the host computer.

Claims

1. A method performed by a first wireless device (12A), the method comprising: receiving (700) a sidelink configuration from each of a plurality of network nodes (20A, 20B) serving the first wireless device (12A); and selecting (710), from the received sidelink configurations, a sidelink configuration (16A) that is consistent or compatible with a sidelink configuration (16B) of a second wireless device (12B) with which the first wireless device (12A) is to communicate over a sidelink, including selecting a sidelink configuration (16A) from the received sidelink configurations that includes a radio link control, RLC, mode configuration that is the same as the RLC mode configuration of the sidelink configuration (16B) of the second wireless device (12B); and transmitting (720) an indication of the selected sidelink configuration (16A) to each of one or more of the network nodes (20A, 20B) serving the first wireless device (12A), wherein the RLC mode configuration includes a configuration of a RLC unacknowledged mode or a RLC acknowledged mode.

2. The method of claim 1, wherein, The sidelink configuration includes a logical channel ID to RLC mode mapping, and wherein the selecting (710) further includes selecting a sidelink configuration (16A) from the received sidelink configurations that includes a logical channel ID to RLC mode mapping that is the same as the logical channel ID to RLC mode mapping of the sidelink configuration (16B) of the second wireless device (12B).

3. The method of any one of claims 1-2, wherein, 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 communication; a radio link control, RLC, mode configuration, the RLC mode configuration including a configuration of a RLC unacknowledged mode or a RLC acknowledged mode; a logical channel ID to RLC mode mapping; and a default sidelink configuration parameter.

4. The method of any one of claims 1-3, wherein, At least one of the network nodes (20A, 20B) acts as a master node for a multi-connectivity operation and at least one other network node of the network nodes (20A, 20B) acts as a secondary node for the multi-connectivity operation.

5. The method of any one of claims 1-4, further comprising: requesting a sidelink configuration from each of the plurality of network nodes (20A, 20B).

6. The method of any one of claims 1-5, further comprising: receiving, from each of one or more of the network nodes (20A, 20B) serving the first wireless device (12A), information identifying one or more other wireless devices (12B) to which the network node has transmitted the same sidelink configuration received from the network node.

7. A method performed by a network node (20A, 20B), the method comprising: receiving (XX), from a first wireless device (12A), an indication that the first wireless device (12A) has selected a sidelink configuration (16A) that is consistent or compatible with a sidelink configuration (16B) of a second wireless device (12B) with which the first wireless device (12A) is to communicate over a sidelink, wherein the indication comprises an indication of the first wireless device (12A) selecting a sidelink configuration (16A) having a same radio link control, RLC, mode configuration as a sidelink configuration (16B) of the second wireless device (12B), wherein the RLC mode configuration comprises a configuration of a RLC unacknowledged mode or a RLC acknowledged mode.

8. The method of claim 7, wherein, the sidelink configuration comprises a logical channel ID to RLC mode mapping, and wherein the indication further comprises an indication of the first wireless device (12A) selecting a sidelink configuration (16A) having a same logical channel ID to RLC mode mapping as a logical channel ID to RLC mode mapping of the sidelink configuration (16B) of the second wireless device (12B).

9. The method of any one of claims 7-8, wherein, the sidelink configuration comprises 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 communication; a radio link control, RLC, mode configuration, the RLC mode configuration comprising a configuration of a RLC unacknowledged mode or a RLC acknowledged mode; a logical channel ID to RLC mode mapping; and a default sidelink configuration parameter.

10. The method of any one of claims 7-9, wherein, the network node (20A, 20B) acting as a master node for a multi-connectivity operation.

11. The method of any one of claims 7-10, wherein, the network node (20A, 20B) acting as a secondary node for a multi-connectivity operation.

12. The method of any one of claims 7-11, further comprising: transmitting, to the first wireless device (12A), information identifying one or more other wireless devices (12B) to which the network node (20A, 20B) has sent a same sidelink configuration (16B) as a sidelink configuration (6B) transmitted to the first wireless device (12A, 12B).

13. A first wireless device (12A) configured to: receive a sidelink configuration from each of a plurality of network nodes (20A, 20B) serving the first wireless device (12A); and From the received sidelink configurations, selecting a sidelink configuration (16A) that is consistent or compatible with a sidelink configuration (16B) of a second wireless device (12B) with which the first wireless device (12A) is to communicate over a sidelink, including: select, from the received sidelink configurations, a sidelink configuration (16A) comprising a same radio link control, RLC, mode configuration as a RLC mode configuration of a sidelink configuration (16B) of the second wireless device (12B); and transmit, to each of one or more of the network nodes (20A, 20B) serving the first wireless device (12A), an indication of the selected sidelink configuration (16A), wherein the RLC mode configuration comprises a configuration of a RLC unacknowledged mode or a RLC acknowledged mode.

14. The first wireless device (12A) of claim 13, configured to perform the method of any one of claims 2-6.

15. A network node (20A, 20B) configured to: receive, from a first wireless device (12A), an indication of a sidelink configuration (16A) selected by the first wireless device (12A) to be consistent or compatible with a sidelink configuration (16B) of a second wireless device (12B) with which the first wireless device (12A) is to communicate over a sidelink, wherein the indication comprises an indication of the sidelink configuration (16A) selected by the first wireless device (12A) to have a radio link control, RLC, mode configuration that is the same as a RLC mode configuration of the sidelink configuration (16B) of the second wireless device (12B), wherein the RLC mode configuration comprises a configuration of a RLC unacknowledged mode or a RLC acknowledged mode.

16. The network node (20A, 20B) of claim 15, configured to perform the method of any of claims 8-12.

17. A computer program product having stored thereon a computer program comprising instructions which, when executed by at least one processor of a first wireless device (12A), cause the first wireless device (12A) to carry out the method of any of claims 1-6.

18. A computer program product having stored thereon a computer program comprising instructions which, when executed by at least one processor of a network node (20A, 20B), cause the network node (20A, 20B) to carry out the method of any of claims 7-12.

19. A computer-readable storage medium having stored therein a computer program comprising instructions which, when executed by a processor, cause the processor to carry out the method of any of claims 1-12.

20. A first wireless device (12A), comprising: communication circuitry (820); and processing circuitry (810) configured to: receive, from each of a plurality of network nodes (20A, 20B) serving the first wireless device (12A), a sidelink configuration; and select, from the received sidelink configurations, a sidelink configuration (16A) that is consistent or compatible with a sidelink configuration (16B) of a second wireless device (12B) with which the first wireless device (12A) is to communicate over a sidelink, including selecting, from the received sidelink configurations, a sidelink configuration (16A) that includes a radio link control, RLC, mode configuration that is the same as a RLC mode configuration of the sidelink configuration (16B) of the second wireless device (12B); and transmit, to each of one or more of the network nodes (20A, 20B) serving the first wireless device (12A), an indication of the selected sidelink configuration (16A), wherein the RLC mode configuration comprises a configuration of a RLC unacknowledged mode or a RLC acknowledged mode.

21. The first wireless device (12A, 12B) of claim 20, the processing circuitry (810) configured to perform the method of any of claims 2-6.

22. A network node (20A, 20B), comprising: communication circuitry (920); and processing circuitry (910) configured to receive, from a first wireless device (12A), an indication of a sidelink configuration (16A) selected by the first wireless device (12A) to be consistent or compatible with a sidelink configuration (16B) of a second wireless device (12B) with which the first wireless device (12A) is to communicate over a sidelink, wherein the indication comprises an indication of the sidelink configuration (16A) selected by the first wireless device (12A) to have a same radio link control, RLC, mode configuration as a RLC mode configuration of the sidelink configuration (16B) of the second wireless device (12B), wherein the RLC mode configuration comprises a configuration of a RLC unacknowledged mode or a RLC acknowledged mode.

23. The network node (20A, 20B) of claim 22, the processing circuitry (910) being configured to perform the method of any one of claims 8-12.

Images