Terminal Device, Network Device and Methods Therein

Abstract

The present disclosure provides a method (400) in a first terminal device. The method (400) includes: transmitting (410) a first message indicating a first sidelink Access Stratum, AS, configuration to a second terminal device; receiving (420) from the second terminal device a second message indicating a failure of the first sidelink AS configuration; and transmitting (430) to a network device a report regarding the failure of the first sidelink AS configuration. The report contains one or more of: an indicator indicating the failure of the first sidelink AS configuration, or an identification of the second terminal device.

Claims

1.-59. (canceled)

60. A method in a first terminal device, the method comprising: transmitting to a second terminal device a first message indicating a first sidelink Access Stratum (AS) configuration; receiving from the second terminal device a second message indicating a failure of the first sidelink AS configuration; and transmitting to a network device a report regarding the failure of the first sidelink AS configuration, wherein the report contains one or more of the following: an indicator indicating the failure of the first sidelink AS configuration, or an identification of the second terminal device.

61. The method of claim 60, wherein: the second message also indicates one or more configuration parameters, of the first sidelink AS configuration, that the second terminal device is not able to comply with; and the report includes the one or more configuration parameters.

62. The method of claim 61, wherein the one or more configuration parameters include a Sidelink Radio Bearer (SLRB) configuration parameter.

63. The method of claim 61, wherein the report also includes identification of one or more of the following: the first terminal device; and a Sidelink Radio Bearer (SLRB) associated with the failure.

64. The method of claim 60, further comprising, in response to the second message, transmitting to the second terminal device a third message indicating a second sidelink AS configuration.

65. The method of claim 64, wherein the second sidelink AS configuration contains one of the following: a full sidelink AS configuration, or a difference from the first sidelink AS configuration.

66. The method of claim 64, wherein: the second message also indicates one or more configuration parameters, of the first sidelink AS configuration, that the second terminal device is not able to comply with; and the method further comprises determining the second sidelink AS configuration based on the one or more configuration parameters indicated by the second message.

67. The method of claim 66, wherein the one or more configuration parameters include a Sidelink Radio Bearer (SLRB) configuration parameter.

68. The method of claim 64, wherein: the second message further indicates at least one candidate sidelink AS configuration that the second terminal device is able to comply with; and the method further comprises selecting the second sidelink AS configuration from the at least one candidate sidelink AS configuration.

69. The method of claim 64, further comprising receiving from the network device a fourth message indicating the second sidelink AS configuration.

70. A method in a first terminal device, the method comprising: transmitting to a second terminal device a first message indicating a sidelink Access Stratum (AS) configuration; receiving from the second terminal device a second message indicating a failure of the sidelink AS configuration; and releasing one of the following associated with the failure: a sidelink connection, or a Sidelink Radio Bearer (SLRB).

71. The method of claim 70, further comprising determining that no other sidelink AS configuration is usable for the sidelink connection or the SLRB associated with the failure, wherein releasing the sidelink connection or the SLRB is responsive to the determining.

72. The method of claim 71, wherein the second message also indicates one or more configuration parameters, of the sidelink AS configuration, that the second terminal device is not able to comply with, and the determining is based on the one or more configuration parameters indicated by the second message.

73. The method of claim 72, wherein the one or more configuration parameters include an SLRB configuration parameter.

74. The method of claim 71, wherein the second message also indicates at least one candidate sidelink AS configuration that the second terminal device is able to comply with, and the determining is based on the at least one candidate sidelink AS configuration.

75. The method of claim 70, further comprising transmitting to a network device a notification that the sidelink connection or the SLRB has been released.

76. The method of claim 71, further comprising: transmitting to a network device a report regarding the failure of the sidelink AS configuration; and receiving from the network device an indication that no other sidelink AS configuration is usable for the sidelink connection or the SLRB, wherein releasing the sidelink connection or the SLRB is responsive to receiving the indication from the network device.

77. The method of claim 76, wherein: the second message also indicates one or more configuration parameters, of the sidelink AS configuration, that the second terminal device is not able to comply with; and the report includes the one or more configuration parameters.

78. A method in a second terminal device, the method comprising: receiving from a first terminal device a first message indicating a sidelink Access Stratum (AS) configuration; and transmitting to the first terminal device a second message indicating a failure of the sidelink AS configuration, wherein the second message also indicates one of the following: one or more configuration parameters, of the sidelink AS configuration, that the second terminal device is not able to comply with, or at least one candidate sidelink AS configuration that the second terminal device is able to comply with.

79. A method in a second terminal device, the method comprising: receiving from a first terminal device a first message indicating a sidelink Access Stratum (AS) configuration; detecting a failure of the sidelink AS configuration at the second terminal device; and releasing a sidelink connection or a Sidelink Radio Bearer (SLRB) associated with the failure.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0115] The above and other objects, features and advantages will be more apparent from the following description of embodiments with reference to the figures, in which:

[0116] FIG. 1 is a schematic diagram showing an architecture of a V2X system;

[0117] FIG. 2 is a schematic diagram showing an example of PC5 unicast links between UEs;

[0118] FIG. 3 is a sequence diagram of an example of a sidelink AS configuration procedure;

[0119] FIG. 4 is a flowchart illustrating a method in a terminal device according to an embodiment of the present disclosure;

[0120] FIG. 5 is a flowchart illustrating a method in a terminal device according to another embodiment of the present disclosure;

[0121] FIG. 6 is a flowchart illustrating a method in a terminal device according to yet another embodiment of the present disclosure;

[0122] FIG. 7 is a flowchart illustrating a method in a terminal device according to still another embodiment of the present disclosure;

[0123] FIG. 8 is a flowchart illustrating a method in a network device according to an embodiment of the present disclosure;

[0124] FIG. 9 is a flowchart illustrating a method in a network device according to another embodiment of the present disclosure;

[0125] FIG. 10 is a block diagram of a terminal device according to an embodiment of the present disclosure;

[0126] FIG. 11 is a block diagram of a terminal device according to another embodiment of the present disclosure;

[0127] FIG. 12 is a block diagram of a terminal device according to yet another embodiment of the present disclosure;

[0128] FIG. 13 is a block diagram of a terminal device according to still another embodiment of the present disclosure;

[0129] FIG. 14 is a block diagram of a terminal device according to still yet another embodiment of the present disclosure;

[0130] FIG. 15 is a block diagram of a network device according to an embodiment of the present disclosure;

[0131] FIG. 16 is a block diagram of a network device according to another embodiment of the present disclosure;

[0132] FIG. 17 schematically illustrates a telecommunication network connected via an intermediate network to a host computer;

[0133] FIG. 18 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection; and

[0134] FIGS. 19 to 22 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.

DETAILED DESCRIPTION

[0135] As used herein, the term “wireless communication network” refers to a network following any suitable communication standards, such as NR, LTE-Advanced (LTE-A), LTE, Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and so on. Furthermore, the communications between a terminal device and a network device in the wireless communication network may be performed according to any suitable generation communication protocols, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 1G (the first generation), 2G (the second generation), 2.5G, 2.75G, 3G (the third generation), 4G (the fourth generation), 4.5G, 5G (the fifth generation) communication protocols, wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, and/or ZigBee standards, and/or any other protocols either currently known or to be developed in the future.

[0136] The term “network node” or “network device” refers to a device in a wireless communication network via which a terminal device accesses the network and receives services therefrom. The network node or network device refers to a base station (BS), an access point (AP), or any other suitable device in the wireless communication network. The BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), or a (next) generation (gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth. Yet further examples of the network device may include multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes. More generally, however, the network device may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a terminal device access to the wireless communication network or to provide some service to a terminal device that has accessed the wireless communication network.

[0137] The term “terminal device” refers to any end device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the terminal device refers to a mobile terminal, user equipment (UE), or other suitable devices. The UE may be, for example, a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, tablets, personal digital assistants (PDAs), wearable terminal devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE) and the like. In the following description, the terms “terminal device”, “terminal”, “user equipment” and “UE” may be used interchangeably. As one example, a terminal device may represent a UE 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 used herein, a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device. In some embodiments, a terminal device may be configured to transmit and/or receive information without direct human interaction. For instance, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the wireless communication network. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.

[0138] The terminal device may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, and may in this case be referred to as a D2D communication device.

[0139] As yet another example, in an Internet of Things (IOT) scenario, a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device. As one particular example, the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, for example refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

[0140] As used herein, a downlink transmission refers to a transmission from the network device to a terminal device, and an uplink transmission refers to a transmission in an opposite direction.

[0141] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0142] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed terms. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and/or “including”, when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

[0143] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0144] FIG. 4 is a flowchart illustrating a method 400 according to an embodiment of the present disclosure. The method 400 can be performed at a first terminal device, e.g., UE 1 in FIG. 3.

[0145] At block 410, a first message (referred to as e.g., RRCReconfigurationSidelink) indicating a first sidelink AS configuration is transmitted to a second terminal device (e.g., UE 2 in FIG. 3). The first sidelink AS configuration can be a sidelink AS configuration the first terminal device intends to use for a sidelink connection between the first and second terminal devices. As described above, a sidelink AS configuration may include configuration parameters such as SLRB configuration parameters and/or PDCP/RLC configuration parameters. The first message can be transmitted via RRC signaling over a PC5 link (i.e., a sidelink connection).

[0146] Here, the first sidelink AS configuration can be obtained by the first terminal device from a network device (e.g., a gNB) via dedicated signaling (e.g., while the first terminal device is in an RRC_CONNECTED state) or via System Information Broadcast (SIB) (e.g., while the first terminal device is in an RRC_IDLE or RRC_INACTIVE state). Alternatively, a set of candidate AS configurations can be configured by a network device via dedicated signaling or SIB, or can be predefined in the first terminal device (and the second terminal device). In this case, the first terminal device can autonomously select one of the candidate AS configurations in the set based on e.g., its capability, configuration and/or network condition.

[0147] At block 420, a second message (referred to as e.g., RRCReconfigurationFailureSidelink) indicating a failure of the first sidelink AS configuration is received from the second terminal device, e.g., via RRC signaling over a PC5 link. The failure of the first sidelink AS configuration means that the second terminal device is not able to comply with at least one of the configuration parameters in the first sidelink AS configuration, depending on its capability, configuration and/or network condition.

[0148] At block 430, a report regarding the failure of the first sidelink AS configuration is transmitted to a network device (e.g., a gNB), e.g., via RRC signaling over a Uu interface. The report may be transmitted using a new RRC signaling message (referred to as e.g., FailureInformation) or an existing RRC signaling message (e.g., SidelinkUEInformation). The report may be transmitted after a predetermined number of sidelink AS configuration failures between the first and second terminal devices. The report may indicate one or more configuration parameters (which may include an SLRB configuration parameter) the second terminal device is not able to comply with in the first sidelink AS configuration. In an example, the report contains one or more of: [0149] an indicator indicating the failure of the first sidelink AS configuration, which can be e.g., a one-bit indicator indicating the failure when set to 1; [0150] or [0151] an identification of the second terminal device, e.g., a source L2 ID or a destination L2 ID of a PC5 unicast link.

[0152] In an example, the report may further contain one or more of: [0153] an indication of a specific failure type, e.g., an SLRB configuration failure, which can be indicated in, or derived from, the second message; [0154] an indication of the one or more configuration parameters the second terminal device is not able to comply with (or one or more configuration parameters the second terminal device is able to comply with); [0155] an identification of the first terminal device, e.g., a source L2 ID or a destination L2 ID of a PC5 unicast link; [0156] an identification of an SLRB, e.g., an SLRB ID, associated with the failure; [0157] or [0158] an indication of all configuration parameters in the first sidelink AS configuration, with indication of the one or more configuration parameters the second terminal device is not able to comply with (or one or more configuration parameters the second terminal device is able to comply with).

[0159] In an example, the first terminal device may transmit a third message (e.g., a new RRCReconfigurationSidelink) indicating a second sidelink AS configuration to the second terminal device in response to the second message.

[0160] Here, the second sidelink AS configuration may contain a full sidelink AS configuration (i.e., including a full set of information elements or fields) or a difference from the first sidelink AS configuration.

[0161] In an example, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the first sidelink AS configuration. In an example, the one or more configuration parameters may include an SLRB configuration parameter. For example, the second message may contain all the configuration parameters in the first sidelink AS configuration and identify which of these configuration parameters the second terminal device is not able to comply with. Accordingly, the first terminal device can determine the second sidelink AS configuration based on the one or more configuration parameters. For example, the second sidelink AS configuration can be determined in such a manner that the one or more configuration parameters are changed when compared with the first sidelink AS configuration. As an alternative, the second message may indicate one or more configuration parameters that the second terminal device is able to comply with in the first sidelink AS configuration.

[0162] In another example, the second message may further include capability information of the second terminal device. Accordingly, the second sidelink AS configuration can be determined based on the capability information. For example, the second sidelink AS configuration can be determined in such a manner that the one or more configuration parameters can be replaced with one or more configuration parameters determined, based on the capability information, to be supported by the second terminal device.

[0163] Alternatively, when a set of candidate AS configurations has been configured or predefined in the first and second terminal devices as described above, the second message may further indicate at least one candidate sidelink AS configuration that the second terminal device is able to comply with. In this case, the second sidelink AS configuration can be selected, e.g., autonomously by the first terminal device, from the at least one candidate sidelink AS configuration.

[0164] In an example, the first terminal device may receive from the network device a fourth message (referred to as e.g., RRCReconfiguration) indicating the second sidelink AS configuration, as a response to the report, and can then signal the second sidelink AS configuration to the second terminal device.

[0165] FIG. 5 is a flowchart illustrating a method 500 according to an embodiment of the present disclosure. The method 500 can be performed at a first terminal device, e.g., UE 1 in FIG. 3.

[0166] At block 510, a first message (e.g., RRCReconfigurationSidelink) indicating a sidelink AS configuration is transmitted to a second terminal device (e.g., UE 2 in FIG. 3). For further details of the first message in the block 510, reference can be made to the first message described above in connection with the method 400.

[0167] At block 520, a second message (e.g., RRCReconfigurationFailureSidelink) indicating a failure of the sidelink AS configuration is received from the second terminal device. For further details of the second message in the block 520, reference can be made to the second message described above in connection with the method 400.

[0168] At block 530, a sidelink connection or an SLRB associated with the failure is released.

[0169] In an example, in the block 530, the sidelink connection or the SLRB may be released in response to determining that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0170] For example, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration. The one or more configuration parameters may include an SLRB configuration parameter. In this case, the first terminal device can determine based on the one or more configuration parameters that no other sidelink AS configuration is usable for the sidelink connection or the SLRB. For example, the sidelink connection may include a set of SLRBs. If the second message indicates that the second terminal device is not able to comply with an SLRB configuration parameter associated with a particular SLRB only, the particular SLRB, instead of the entire sidelink connection, can be released in the block 530.

[0171] Alternatively, the second message may further indicate at least one candidate sidelink AS configuration that the second terminal device is able to comply with. In this case, the first terminal device can determine based on the at least one candidate sidelink AS configuration that no other sidelink AS configuration is usable for the sidelink connection or the SLRB, e.g., when the first terminal device is not able to comply with any of the at least one candidate sidelink AS configuration.

[0172] In an example, the first terminal device may transmit to a network device (e.g., a gNB) a notification that the sidelink connection or the SLRB has been released. The notification may also indicate a cause of the release as sidelink AS configuration failure. The notification can be transmitted via RRC signaling over a Uu interface, using e.g., FailureInformation or SidelinkUEInformation as described above.

[0173] Alternatively, the first terminal device may transmit to a network device (e.g., a gNB) a report regarding the failure of the sidelink AS configuration, e.g., via RRC signaling over a Uu interface. The report may be transmitted using a new RRC signaling message (e.g., FailureInformation) or an existing RRC signaling message (e.g., SidelinkUEInformation). The report may be transmitted after a predetermined number of sidelink AS configuration failures between the first and second terminal devices. The report may indicate the one or more configuration parameters (which may include an SLRB configuration parameter) the second terminal device is not able to comply with. The report may contain one or more of: an indicator indicating the failure of the sidelink AS configuration, an identification of the first terminal device and an identification of the second terminal device, or an identification of the SLRB (for further details, reference can be made to the report described above in connection with the method 400). Then, the first terminal device can receive from the network device an indication that no other sidelink AS configuration is usable for the sidelink connection or the SLRB. In this case, in the block 530, the first terminal device can release the sidelink connection or SLRB in response to receiving the indication.

[0174] FIG. 6 is a flowchart illustrating a method 600 according to an embodiment of the present disclosure. The method 600 can be performed at a second terminal device, e.g., UE 2 in FIG. 3.

[0175] At block 610, a first message (e.g., RRCReconfigurationSidelink) indicating a sidelink AS configuration is received from a first terminal device (e.g., UE 1 in FIG. 3), e.g., via RRC signaling over a PC5 interface. For further details of the first message in the block 610, reference can be made to the first message described above in connection with the method 400.

[0176] At block 620, a second message (e.g., RRCReconfigurationFailureSidelink) indicating a failure of the sidelink AS configuration is transmitted to the first terminal device, e.g., via RRC signaling over a PC5 interface. The second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration. The one or more configuration parameters may include an SLRB configuration parameter. Alternatively, the second message may further indicate at least one candidate sidelink AS configuration that the second terminal device is able to comply with. In another example, the second message may further include capability information of the second terminal device. For further details of the second message in the block 620, reference can be made to the second message described above in connection with the method 400.

[0177] FIG. 7 is a flowchart illustrating a method 700 according to an embodiment of the present disclosure. The method 700 can be performed at a second terminal device, e.g., UE 2 in FIG. 3.

[0178] At block 710, a first message (e.g., RRCReconfigurationSidelink) indicating a sidelink AS configuration is received from a first terminal device (e.g., UE 1 in FIG. 3), e.g., via RRC signaling over a PC5 interface. For further details of the first message in the block 710, reference can be made to the first message described above in connection with the method 400.

[0179] At block 720, a failure of the sidelink AS configuration is detected at the second terminal device. For example, in the block 720, the second terminal device may determine that it is not able to comply with at least one of the configuration parameters in the sidelink AS configuration, depending on its capability, configuration and/or network condition.

[0180] At block 730, a sidelink connection or an SLRB associated with the failure is released. For example, the sidelink connection may include a set of SLRBs. If the second terminal device is not able to comply with an SLRB configuration parameter associated with a particular SLRB only in the sidelink AS configuration, the particular SLRB, instead of the entire sidelink connection, can be released in the block 730.

[0181] In an example, the second terminal device can transmit to the first terminal device a second message (e.g., RRCReconfigurationFailureSidelink) indicating that the sidelink connection or the SLRB has been released, e.g., via RRC signaling over a PC5 interface.

[0182] FIG. 8 is a flowchart illustrating a method 800 according to an embodiment of the present disclosure. The method 800 can be performed at a network device, e.g., a gNB serving UE1 in FIG. 3.

[0183] At block 810, a report regarding a failure of a first sidelink AS configuration for a sidelink connection between a first terminal device (e.g., UE 1 in FIG. 3) and a second terminal device (e.g., UE 2 in FIG. 3) is received from the first terminal device, e.g., via RRC signaling over a Uu interface. The report may use a new RRC signaling message (e.g., FailureInformation) or an existing RRC signaling message (e.g., SidelinkUEInformation). The report contains one or more of: an indicator indicating the failure of the sidelink AS configuration, or an identification of the second terminal device.

[0184] The report may further contain one or more of: an identification of the first terminal device, or an identification of the SLRB (for further details, reference can be made to the report described above in connection with the method 400).

[0185] In an example, the second terminal device can transmit a message (e.g., RRCReconfiguration) indicating a second sidelink AS configuration for the sidelink connection to the first terminal device.

[0186] In an example, the second sidelink AS configuration may contain a full sidelink AS configuration or a difference from the first sidelink AS configuration.

[0187] In an example, the report may indicate one or more configuration parameters (which may include an SLRB configuration parameter) the second terminal device is not able to comply with in the first sidelink AS configuration. The second sidelink AS configuration can be determined by the network device based on the one or more configuration parameters. As an alternative, the report may indicate one or more configuration parameters that the second terminal device is able to comply with in the first sidelink AS configuration.

[0188] FIG. 9 is a flowchart illustrating a method 900 according to an embodiment of the present disclosure. The method 900 can be performed at a network device, e.g., a gNB serving UE1 in FIG. 3.

[0189] At block 910, a report regarding a failure of a sidelink AS configuration for a sidelink connection between a first terminal device (e.g., UE 1 in FIG. 3) and a second terminal device (e.g., UE 2 in FIG. 3) is received from the first terminal device, e.g., via RRC signaling over a Uu interface. The report may use a new RRC signaling message (e.g., FailureInformation) or an existing RRC signaling message (e.g., SidelinkUEInformation).

[0190] At block 920, an indication that no other sidelink AS configuration is usable for the sidelink connection or the SLRB is transmitted to the first terminal device.

[0191] In an example, the report may indicate the one or more configuration parameters (which may include an SLRB configuration parameter) the second terminal device is not able to comply with in the sidelink AS configuration. The network device can determine based on the one or more configuration parameters that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0192] The report may contain one or more of: an indicator indicating the failure of the sidelink AS configuration, an identification of the first terminal device and an identification of the second terminal device, or an identification of the SLRB (for further details, reference can be made to the report described above in connection with the method 400).

[0193] In an example, the network device can receive from the first terminal device a notification that the sidelink connection or the SLRB has been released.

[0194] Correspondingly to the method 400 as described above, a first terminal device is provided. FIG. 10 is a block diagram of a first terminal device 1000 according to an embodiment of the present disclosure.

[0195] As shown in FIG. 10, the first terminal device 1000 includes a transmitting unit 1010 configured to transmit a first message indicating a first sidelink AS configuration to a second terminal device. The first terminal device 1000 further includes a receiving unit 1020 configured to receive from the second terminal device a second message indicating a failure of the first sidelink AS configuration. The transmitting unit 1010 is further configured to transmit to a network device a report regarding the failure of the first sidelink AS configuration. The report contains one or more of: an indicator indicating the failure of the first sidelink AS configuration, or an identification of the second terminal device.

[0196] In an embodiment, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the first sidelink AS configuration, and the report may contain the one or more configuration parameters.

[0197] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0198] In an embodiment, the report may further contain one or more of: an identification of the first terminal device; or an identification of an SLRB associated with the failure.

[0199] In an embodiment, the transmitting unit 1010 can be further configured to transmit to the second terminal device a third message indicating a second sidelink AS configuration in response to the second message.

[0200] In an embodiment, the second sidelink AS configuration may contain a full sidelink AS configuration or a difference from the first sidelink AS configuration.

[0201] In an embodiment, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the first sidelink AS configuration, and the second sidelink AS configuration may be determined based on the one or more configuration parameters.

[0202] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0203] In an embodiment, the second message may further indicate at least one candidate sidelink AS configuration that the second terminal device is able to comply with, and the second sidelink AS configuration may be selected from the at least one candidate sidelink AS configuration.

[0204] In an embodiment, the receiving unit 1020 can be further configured to receive a fourth message indicating the second sidelink AS configuration from the network device.

[0205] The units 1010 and 1020 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in FIG. 4.

[0206] Correspondingly to the method 500 as described above, a first terminal device is provided. FIG. 11 is a block diagram of a first terminal device 1100 according to another embodiment of the present disclosure.

[0207] As shown in FIG. 11, the first terminal device 1100 includes a transmitting unit 1110 configured to transmit first message indicating a sidelink AS configuration to a second terminal device. The first terminal device 1100 includes a receiving unit 1120 configured to receive from the second terminal device a second message indicating a failure of the sidelink AS configuration. The first terminal device 1100 further includes a releasing unit 1130 configured to release a sidelink connection or an SLRB associated with the failure.

[0208] In an embodiment, the sidelink connection or the SLRB may be released in response to determining that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0209] In an embodiment, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration. It can be determined based on the one or more configuration parameters that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0210] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0211] In an embodiment, the second message may further indicate at least one candidate sidelink AS configuration that the second terminal device is able to comply with. It can be determined based on the at least one candidate sidelink AS configuration that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0212] In an embodiment, the transmitting unit 1110 can be further configured to transmit to a network device a notification that the sidelink connection or the SLRB has been released.

[0213] In an embodiment, the transmitting unit 1110 can be further configured to transmit to a network device a report regarding the failure of the sidelink AS configuration. The receiving unit 1120 can be further configured to receive from the network device an indication that no other sidelink AS configuration is usable for the sidelink connection or the SLRB. The sidelink connection or the SLRB may be released in response to receiving the indication.

[0214] In an embodiment, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration. The report may contain the one or more configuration parameters.

[0215] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0216] In an embodiment, the report may contain one or more of: an indicator indicating the failure of the sidelink AS configuration, an identification of the first terminal device and an identification of the second terminal device, or an identification of the SLRB.

[0217] The units 1110˜1130 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in FIG. 5.

[0218] Correspondingly to the method 600 as described above, a second terminal device is provided. FIG. 12 is a block diagram of a second terminal device 1200 according to an embodiment of the present disclosure.

[0219] As shown in FIG. 12, the second terminal device 1200 includes a receiving unit 1210 configured to receive from a first terminal device a first message indicating a sidelink AS configuration. The second terminal device 1200 further includes a transmitting unit 1220 configured to transmit to the first terminal device a second message indicating a failure of the sidelink AS configuration. The second message further indicates one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration, or at least one candidate sidelink AS configuration that the second terminal device is able to comply with.

[0220] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0221] The units 1210 and 1220 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in FIG. 6.

[0222] Correspondingly to the method 700 as described above, a second terminal device is provided. FIG. 13 is a block diagram of a second terminal device 1300 according to another embodiment of the present disclosure.

[0223] As shown in FIG. 13, the second terminal device 1300 includes a receiving unit 1310 configured to receive from a first terminal device a first message indicating a sidelink AS configuration. The second terminal device 1300 further includes a detecting unit 1320 configured to detect a failure of the sidelink AS configuration at the second terminal device. The second terminal device 1300 further includes a releasing unit 1330 configured to release a sidelink connection or an SLRB associated with the failure.

[0224] In an embodiment, the second terminal device 1300 may further include a transmitting unit configured to transmit to the first terminal device a second message indicating that the sidelink connection or the SLRB has been released.

[0225] The units 1310˜1330 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in FIG. 7.

[0226] FIG. 14 is a block diagram of a terminal device 1400 according to another embodiment of the present disclosure.

[0227] The terminal device 1400 includes a transceiver 1410, a processor 1420 and a memory 1430. The memory 1430 may contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to perform, as a first terminal device, the actions, e.g., of the procedure described earlier in conjunction with FIG. 4. Particularly, the memory 1430 contains instructions executable by the processor 1420 whereby the terminal device 1400 is operative to, as a first terminal device: transmit a first message indicating a first sidelink AS configuration to a second terminal device; receive from the second terminal device a second message indicating a failure of the first sidelink AS configuration; and transmit to a network device a report regarding the failure of the first sidelink AS configuration. The report contains one or more of: an indicator indicating the failure of the first sidelink AS configuration, or an identification of the second terminal device.

[0228] In an embodiment, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the first sidelink AS configuration, and the report may contain the one or more configuration parameters.

[0229] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0230] In an embodiment, the report may further contain one or more of: an identification of the first terminal device; or an identification of an SLRB associated with the failure.

[0231] In an embodiment, the memory 1430 may further contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to: transmit to the second terminal device a third message indicating a second sidelink AS configuration in response to the second message.

[0232] In an embodiment, the second sidelink AS configuration may contain a full sidelink AS configuration or a difference from the first sidelink AS configuration.

[0233] In an embodiment, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the first sidelink AS configuration, and the second sidelink AS configuration may be determined based on the one or more configuration parameters.

[0234] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0235] In an embodiment, the second message may further indicate at least one candidate sidelink AS configuration that the second terminal device is able to comply with, and the second sidelink AS configuration may be selected from the at least one candidate sidelink AS configuration.

[0236] In an embodiment, the memory 1430 may further contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to: receive a fourth message indicating the second sidelink AS configuration from the network device.

[0237] Alternatively, the memory 1430 may contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to perform, as a first terminal device, the actions, e.g., of the procedure described earlier in conjunction with FIG. 5. Particularly, the memory 1430 contains instructions executable by the processor 1420 whereby the terminal device 1400 is operative to, as a first terminal device: transmit a first message indicating a sidelink AS configuration to a second terminal device; receive from the second terminal device a second message indicating a failure of the sidelink AS configuration; and release a sidelink connection or an SLRB associated with the failure.

[0238] In an embodiment, the sidelink connection or the SLRB may be released in response to determining that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0239] In an embodiment, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration. It can be determined based on the one or more configuration parameters that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0240] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0241] In an embodiment, the second message may further indicate at least one candidate sidelink AS configuration that the second terminal device is able to comply with. It can be determined based on the at least one candidate sidelink AS configuration that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0242] In an embodiment, the memory 1430 may further contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to: transmit to a network device a notification that the sidelink connection or the SLRB has been released.

[0243] In an embodiment, the memory 1430 may further contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to: transmit to a network device a report regarding the failure of the sidelink AS configuration; and receive from the network device an indication that no other sidelink AS configuration is usable for the sidelink connection or the SLRB. The sidelink connection or the SLRB may be released in response to receiving the indication.

[0244] In an embodiment, the second message may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration. The report may contain the one or more configuration parameters.

[0245] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0246] In an embodiment, the report may contain one or more of: an indicator indicating the failure of the sidelink AS configuration, an identification of the first terminal device and an identification of the second terminal device, or an identification of the SLRB.

[0247] Alternatively, the memory 1430 may contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to perform, as a second terminal device, the actions, e.g., of the procedure described earlier in conjunction with FIG. 6. Particularly, the memory 1430 contains instructions executable by the processor 1420 whereby the terminal device 1400 is operative to, as a second terminal device: receive from a first terminal device a first message indicating a sidelink AS configuration; and transmit to the first terminal device a second message indicating a failure of the sidelink AS configuration. The second message further indicates one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration, or at least one candidate sidelink AS configuration that the second terminal device is able to comply with.

[0248] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0249] Alternatively, the memory 1430 may contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to perform, as a second terminal device, the actions, e.g., of the procedure described earlier in conjunction with FIG. 7. Particularly, the memory 1430 contains instructions executable by the processor 1420 whereby the terminal device 1400 is operative to, as a second terminal device: receive from a first terminal device a first message indicating a sidelink AS configuration; detect a failure of the sidelink AS configuration at the second terminal device; and release a sidelink connection or an SLRB associated with the failure.

[0250] In an embodiment, the memory 1430 may further contain instructions executable by the processor 1420 whereby the terminal device 1400 is operative to: transmit to the first terminal device a second message indicating that the sidelink connection or the SLRB has been released.

[0251] Correspondingly to the method 800 or 900 as described above, a network device is provided. FIG. 15 is a block diagram of a network device 1500 according to an embodiment of the present disclosure.

[0252] The network device 1500 can be configured to perform the method 800 as shown in FIG. 8. The network device 1500 includes a receiving unit 1510 configured to receive from a first terminal device a report regarding a failure of a first sidelink AS configuration for a sidelink connection between the first terminal device and a second terminal device. The report contains one or more of: an indicator indicating the failure of the first sidelink AS configuration, or an identification of the second terminal device.

[0253] In an embodiment, the report may further contain one or more of: an identification of the first terminal device, or an identification of an SLRB associated with the failure.

[0254] In an embodiment, the network device 1500 may further include a transmitting unit 1520 configured to transmit to the first terminal device a message indicating a second sidelink AS configuration for the sidelink connection.

[0255] In an embodiment, the second sidelink AS configuration may contain a full sidelink AS configuration or a difference from the first sidelink AS configuration.

[0256] In an embodiment, the report may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the first sidelink AS configuration, and the second sidelink AS configuration may be determined based on the one or more configuration parameters.

[0257] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0258] Alternatively, the network device 1500 can be configured to perform the method 900 as shown in FIG. 9. The network device 1500 includes a receiving unit 1510 configured to receive from a first terminal device a report regarding a failure of a sidelink AS configuration for a sidelink connection or an SLRB between the first terminal device and a second terminal device. The network device 1500 further includes a transmitting unit 1520 configured to transmit to the first terminal device an indication that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0259] In an embodiment, the report may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration. The network device 1500 may further include: a determining unit configured to determine that no other sidelink AS configuration is usable for the sidelink connection or the SLRB based on the one or more configuration parameters.

[0260] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0261] In an embodiment, the report may contain one or more of: an indicator indicating the failure of the sidelink AS configuration, an identification of the first terminal device and an identification of the second terminal device, or an identification of the SLRB.

[0262] In an embodiment, the receiving unit 1510 can be further configured to receive from the first terminal device a notification that the sidelink connection or the SLRB has been released.

[0263] The units 1510 and 1520 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in FIG. 8 or 9.

[0264] FIG. 16 is a block diagram of a network device 1600 according to another embodiment of the present disclosure.

[0265] The network device 1600 includes a transceiver 1610, a processor 1620 and a memory 1630. The memory 1630 may contain instructions executable by the processor 1620 whereby the network device 1600 is operative to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 8. Particularly, the memory 1630 contains instructions executable by the processor 1620 whereby the network device 1600 is operative to: receive from a first terminal device a report regarding a failure of a first sidelink AS configuration for a sidelink connection between the first terminal device and a second terminal device. The report contains one or more of: an indicator indicating the failure of the first sidelink AS configuration, or an identification of the second terminal device.

[0266] In an embodiment, the report may further contain one or more of: an identification of the first terminal device, or an identification of an SLRB associated with the failure.

[0267] In an embodiment, the memory 1630 may further contain instructions executable by the processor 1620 whereby the network device 1600 is operative to: transmit to the first terminal device a message indicating a second sidelink AS configuration for the sidelink connection.

[0268] In an embodiment, the second sidelink AS configuration may contain a full sidelink AS configuration or a difference from the first sidelink AS configuration.

[0269] In an embodiment, the report may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the first sidelink AS configuration, and the second sidelink AS configuration may be determined based on the one or more configuration parameters.

[0270] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0271] Alternatively, the memory 1630 may contain instructions executable by the processor 1620 whereby the network device 1600 is operative to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 9. Particularly, the memory 1630 contains instructions executable by the processor 1620 whereby the network device 1600 is operative to: receive from a first terminal device a report regarding a failure of a sidelink AS configuration for a sidelink connection or an SLRB between the first terminal device and a second terminal device; and transmit to the first terminal device an indication that no other sidelink AS configuration is usable for the sidelink connection or the SLRB.

[0272] In an embodiment, the report may further indicate one or more configuration parameters that the second terminal device is not able to comply with in the sidelink AS configuration. The memory 1630 may further contain instructions executable by the processor 1620 whereby the network device 1600 is operative to: determine that no other sidelink AS configuration is usable for the sidelink connection or the SLRB based on the one or more configuration parameters.

[0273] In an embodiment, the one or more configuration parameters may include an SLRB configuration parameter.

[0274] In an embodiment, the report may contain one or more of: an indicator indicating the failure of the sidelink AS configuration, an identification of the first terminal device and an identification of the second terminal device, or an identification of the SLRB.

[0275] In an embodiment, the memory 1630 may further contain instructions executable by the processor 1620 whereby the network device 1600 is operative to: receive from the first terminal device a notification that the sidelink connection or the SLRB has been released.

[0276] The present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a flash memory and a hard drive. The computer program product includes a computer program. The computer program includes: code/computer readable instructions, which when executed by the processor 1420 causes the terminal device 1400 to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 4, 5, 6, or 7; or code/computer readable instructions, which when executed by the processor 1620 causes the network device 1600 to perform the actions, e.g., of the procedure described earlier in conjunction with FIG. 8 or 9.

[0277] The computer program product may be configured as a computer program code structured in computer program modules. The computer program modules could essentially perform the actions of the flow illustrated in FIG. 4, 5, 6, 7, 8, or 9.

[0278] The processor may be a single CPU (Central Processing Unit), but could also comprise two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuits (ASICs). The processor may also comprise board memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may comprise a non-transitory computer readable storage medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random-Access Memory (RAM), a Read-Only Memory (ROM), or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories.

[0279] With reference to FIG. 17, in accordance with an embodiment, a communication system includes a telecommunication network 1710, such as a 3GPP-type cellular network, which comprises an access network 1711, such as a radio access network, and a core network 1714. The access network 1711 comprises a plurality of base stations 1712a, 1712b, 1712c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1713a, 1713b, 1713c. Each base station 1712a, 1712b, 1712c is connectable to the core network 1714 over a wired or wireless connection 1715. A first user equipment (UE) 1791 located in coverage area 1713c is configured to wirelessly connect to, or be paged by, the corresponding base station 1712c. A second UE 1792 in coverage area 1713a is wirelessly connectable to the corresponding base station 1712a. While a plurality of UEs 1791, 1792 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 1712.

[0280] The telecommunication network 1710 is itself connected to a host computer 1730, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 1730 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 1721, 1722 between the telecommunication network 1710 and the host computer 1730 may extend directly from the core network 1714 to the host computer 1730 or may go via an optional intermediate network 1720. The intermediate network 1720 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 1720, if any, may be a backbone network or the Internet; in particular, the intermediate network 1720 may comprise two or more sub-networks (not shown).

[0281] The communication system of FIG. 17 as a whole enables connectivity between one of the connected UEs 1791, 1792 and the host computer 1730. The connectivity may be described as an over-the-top (OTT) connection 1750. The host computer 1730 and the connected UEs 1791, 1792 are configured to communicate data and/or signaling via the OTT connection 1750, using the access network 1711, the core network 1714, any intermediate network 1720 and possible further infrastructure (not shown) as intermediaries. The OTT connection 1750 may be transparent in the sense that the participating communication devices through which the OTT connection 1750 passes are unaware of routing of uplink and downlink communications. For example, a base station 1712 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 1730 to be forwarded (e.g., handed over) to a connected UE 1791. Similarly, the base station 1712 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1791 towards the host computer 1730.

[0282] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 18. In a communication system 1800, a host computer 1810 comprises hardware 1815 including a communication interface 1816 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1800. The host computer 1810 further comprises processing circuitry 1818, which may have storage and/or processing capabilities. In particular, the processing circuitry 1818 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 1810 further comprises software 1811, which is stored in or accessible by the host computer 1810 and executable by the processing circuitry 1818. The software 1811 includes a host application 1812. The host application 1812 may be operable to provide a service to a remote user, such as a UE 1830 connecting via an OTT connection 1850 terminating at the UE 1830 and the host computer 1810. In providing the service to the remote user, the host application 1812 may provide user data which is transmitted using the OTT connection 1850.

[0283] The communication system 1800 further includes a base station 1820 provided in a telecommunication system and comprising hardware 1825 enabling it to communicate with the host computer 1810 and with the UE 1830. The hardware 1825 may include a communication interface 1826 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1800, as well as a radio interface 1827 for setting up and maintaining at least a wireless connection 1870 with a UE 1830 located in a coverage area (not shown in FIG. 18) served by the base station 1820. The communication interface 1826 may be configured to facilitate a connection 1860 to the host computer 1810. The connection 1860 may be direct or it may pass through a core network (not shown in FIG. 18) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 1825 of the base station 1820 further includes processing circuitry 1828, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 1820 further has software 1821 stored internally or accessible via an external connection.

[0284] The communication system 1800 further includes the UE 1830 already referred to. Its hardware 1835 may include a radio interface 1837 configured to set up and maintain a wireless connection 1870 with a base station serving a coverage area in which the UE 1830 is currently located. The hardware 1835 of the UE 1830 further includes processing circuitry 1838, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 1830 further comprises software 1831, which is stored in or accessible by the UE 1830 and executable by the processing circuitry 1838. The software 1831 includes a client application 1832. The client application 1832 may be operable to provide a service to a human or non-human user via the UE 1830, with the support of the host computer 1810. In the host computer 1810, an executing host application 1812 may communicate with the executing client application 1832 via the OTT connection 1850 terminating at the UE 1830 and the host computer 1810. In providing the service to the user, the client application 1832 may receive request data from the host application 1812 and provide user data in response to the request data. The OTT connection 1850 may transfer both the request data and the user data. The client application 1832 may interact with the user to generate the user data that it provides.

[0285] It is noted that the host computer 1810, base station 1820 and UE 1830 illustrated in FIG. 18 may be identical to the host computer 1730, one of the base stations 1712a, 1712b, 1712c and one of the UEs 1791, 1792 of FIG. 17, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 18 and independently, the surrounding network topology may be that of FIG. 17.

[0286] In FIG. 18, the OTT connection 1850 has been drawn abstractly to illustrate the communication between the host computer 1810 and the use equipment 1830 via the base station 1820, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 1830 or from the service provider operating the host computer 1810, or both. While the OTT connection 1850 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0287] The wireless connection 1870 between the UE 1830 and the base station 1820 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 the UE 1830 using the OTT connection 1850, in which the wireless connection 1870 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time.

[0288] A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1850 between the host computer 1810 and UE 1830, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 1850 may be implemented in the software 1811 of the host computer 1810 or in the software 1831 of the UE 1830, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 1850 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1811, 1831 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 1820, and it may be unknown or imperceptible to the base station 1820. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer's 1810 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 1811, 1831 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1850 while it monitors propagation times, errors etc.

[0289] FIG. 19 is a flowchart 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 may be those described with reference to FIGS. 17 and 18. For simplicity of the present disclosure, only drawing references to FIG. 19 will be included in this section. In a first step 1910 of the method, the host computer provides user data. In an optional substep 1911 of the first step 1910, the host computer provides the user data by executing a host application. In a second step 1920, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 1930, 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 an optional fourth step 1940, the UE executes a client application associated with the host application executed by the host computer.

[0290] FIG. 20 is a flowchart 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 may be those described with reference to FIGS. 17 and 18. For simplicity of the present disclosure, only drawing references to FIG. 20 will be included in this section. In a first step 2010 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 a second step 2020, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step 2030, the UE receives the user data carried in the transmission.

[0291] FIG. 21 is a flowchart 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 may be those described with reference to FIGS. 17 and 18. For simplicity of the present disclosure, only drawing references to FIG. 21 will be included in this section. In an optional first step 2110 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 2120, the UE provides user data. In an optional substep 2121 of the second step 2120, the UE provides the user data by executing a client application. In a further optional substep 2111 of the first step 2110, 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 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third substep 2130, transmission of the user data to the host computer. In a fourth step 2140 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.

[0292] FIG. 22 is a flowchart 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 may be those described with reference to FIGS. 17 and 18. For simplicity of the present disclosure, only drawing references to FIG. 22 will be included in this section. In an optional first step 2210 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In an optional second step 2220, the base station initiates transmission of the received user data to the host computer. In a third step 2230, the host computer receives the user data carried in the transmission initiated by the base station.

[0293] The disclosure has been described above with reference to embodiments thereof. It should be understood that various modifications, alternations and additions can be made by those skilled in the art without departing from the spirits and scope of the disclosure. Therefore, the scope of the disclosure is not limited to the above particular embodiments but only defined by the claims as attached.