Method and apparatus for connection setup for sidelink relaying

Abstract

A method implemented by a first user equipment (UE) includes the first UE receiving, from a second UE, a first sidelink message including a UE-to-network relay setup request to set up a sidelink between the first UE and the second UE, the first UE transmitting, to an access node, a relay UE setup request, the first UE receiving, from the access node, a relay UE setup response, and the first UE transmitting, to the second UE, a second sidelink message including a UE-to-network relay setup response.

Description

[0001] Priority Statement

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 061,547, filed August 5, 2020, entitled “Methods and Apparatus for Protocol Stack and Connection Setup of Sidelink Relay,” which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to methods and apparatus for digital communications, and in particular embodiments to methods and apparatus for setting up a connection for a side link relay. Background Technology

[0004] Generally, user equipment (UE) can communicate directly with the radio access network (RAN). A UE can also communicate with other UEs via sidelink. If a UE is outside the RAN's coverage area, it cannot communicate with the RAN. However, a UE that communicates directly with the RAN can act as a relay UE for UEs outside the RAN's coverage area. In other words, a relay UE allows a UE to communicate indirectly with the RAN, acting as an intermediary between the UE and the RAN. This type of relay UE is called a sidelink relay.

[0005] Methods and apparatus are needed for setting up connections for side link relays. Summary of the Invention

[0006] An advantage of the preferred embodiment is that the first UE within the RAN coverage area can support communication between the second UE and the sidelink connection between the two UEs. The sidelink connection also supports QoS requirements. Attached Figure Description

[0007] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings.

[0008] Figure 1 A first example communication system is shown;

[0009] Figure 2 This illustrates a UE-to-network connection communication system that highlights the support of a relay UE;

[0010] Figure 3 The example user plane (UP) protocol stack of the example communication system is shown;

[0011] Figure 4 The example control plane (CP) protocol stack of the example communication system is shown;

[0012] Figure 5 The protocol stack of an example communication system with Layer 3 side link relay is shown;

[0013] Figure 6 A schematic diagram illustrating entity exchange communication and execution processes involved in an example connection setup process from a UE to a network relay according to an example embodiment presented herein;

[0014] Figure 7 A flowchart is shown illustrating example operations occurring in a remote UE involved in establishing a UE-to-network relay connection, according to an example embodiment presented herein;

[0015] Figure 8 A flowchart illustrating example operations occurring in a relay UE involved in establishing a UE-to-network relay connection, according to an example embodiment presented herein;

[0016] Figure 9 A flowchart is shown illustrating example operations occurring in a serving access node involved in establishing a UE-to-network relay connection, according to an example embodiment presented herein.

[0017] Figure 10 A flowchart is shown illustrating example operations occurring in a network control function involved in establishing a UE-to-network relay connection, according to an example embodiment presented herein;

[0018] Figure 11 An example communication system according to the example embodiments presented herein is shown;

[0019] Figure 12A and Figure 12B An example device is shown that can implement the methods and teachings according to this disclosure;

[0020] Figure 13 It is a block diagram of a computing system that can be used to implement the devices and methods disclosed herein;

[0021] Figure 14 A block diagram of an embodiment of a processing system for performing the methods described herein is shown. The processing system may be installed in a host device.

[0022] Figure 15 A block diagram of a transceiver suitable for sending and receiving signaling over a telecommunications network, according to an example embodiment presented herein, is shown. Detailed Implementation

[0023] The structure and use of the disclosed embodiments are discussed in detail below. However, it should be understood that this disclosure provides many applicable concepts that can be embodied in various specific contexts. The specific embodiments discussed are merely illustrative of specific structures and uses of embodiments and do not limit the scope of this disclosure.

[0024] Figure 1 A first example communication system 100 is illustrated. Communication system 100 includes an access node 110 with a coverage area 101, serving a user equipment (UE), such as UE 120. Access node 110 is connected to a backhaul network 115, which provides connectivity to services and the Internet. In a first operating mode, communication with the UE traverses access node 110. In a second operating mode, communication with the UE does not traverse access node 110; however, access node 110 typically allocates resources for UE communication when certain conditions are met. Communication between a pair of UEs in the second operating mode occurs on a sidelink 125, which includes device-to-device or end-to-end communication links. Communication between the UE and access node pair also occurs on unidirectional communication links, wherein the communication link from the UE to the access node is referred to as uplink 130, and the communication link from the access node to the UE is referred to as downlink 135.

[0025] Access nodes are also commonly referred to as NodeB, evolved NodeB (eNB), next generation (NG) NodeB (gNB), master or primary eNB (MeNB), secondary eNB (SeNB), master or primary gNB (MgNB), secondary gNB (SgNB), network controller, control node, base station, access point, transmission point (TP), transmission-reception point (TRP), cell, carrier, macro cell, femtocell, picocell, etc. UEs are also commonly referred to as mobile stations, handsets, terminals, users, subscribers, stations, etc. Access nodes can provide wireless access based on one or more wireless communication protocols, such as the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE), LTE Advanced (LTE-A), 5G, 5G LTE, 5G NR, Sixth Generation (6G), High Speed ​​Packet Access (HSPA), and the IEEE 802.11 standard family (e.g., 802.11a / b / g / n / ac / ad / ax / ay / be).

[0026] Figure 2 A communication system 200 for UE-to-network connectivity, highlighting relay UE support, is shown. The communication system 200 has a coverage area 201. The communication system 200 includes an access node 205 serving a first UE 210. Figure 2 The diagram also shows a second UE 215. The second UE 215 is outside the coverage area 201 of the communication system 201, therefore the second UE 215 cannot connect to the access node 205. The first UE 210 is able to operate as a relay UE.

[0027] The second UE 215 is connected to the first UE 210 via PC5 interface 217 on the sidelink. The first UE 210 operates as a relay UE in this case, and is therefore referred to as a relay UE. Furthermore, the second UE 215 operates as a remote UE, and is therefore referred to as a remote UE. The relay UE 210 is connected to the access node 205 via Uu interface 219. Therefore, the relay UE 210 can forward packets received from the remote UE 215 to the access node 205 on the uplink. Conversely, the relay UE 210 can forward packets received from the access node 205 to the remote UE 215. Thus, with the assistance of the relay UE 210, an indirect connection path is established between the remote UE 215 and the access node 205.

[0028] In 3GPP RP-193253, “New SID: Study on NR sidelink relay”, which is incorporated herein by reference in its entirety, specifies “the architecture of the end-to-end packet data convergence protocol (PDCP) and hop-by-hop radio link control (RLC) for Layer 2 UE to network relay, for example, as recommended in TR 36.746, as a starting point.”

[0029] Figure 3 An example user plane (UP) protocol stack 300 of an example communication system is shown. The UP protocol stack 300 includes entities at the remote UE 215, relay UE 210, access node 205, and user plane function (UPF) 305. Entities at the adaptation layer 310 of relay UE 210 reside on the PC5 RLC entity 315 and UuRLC entity 316 of relay UE 210, wherein packets carried by the remote UE 215 in the RLC channel from the remote UE 215 to the relay UE 210 are mapped to the RLC channel from the relay UE 210 to the access node 205, and vice versa. Similarly, the adaptation layer 311 of access node 205 resides on the RLC entity 317 of access node 205, wherein adaptation layer 311 maps packets carried by remote UE 215 in the RLC channel from relay UE 210 to access node 205 to the radio bearer of the remote UE, and vice versa. Since adaptation layers 310 and 311 are applicable to the RLC channels of all radio bearers, adaptation layers 310 and 311 support both the signaling radio bearer (SRB) and data radio bearer (DRB) of remote UE 215.

[0030] Figure 4 An example control plane (CP) protocol stack 400 of an example communication system is shown. The CP protocol stack 400 includes entities at a remote UE 215, a relay UE 210, an access node 205, and an access and mobility management function (AMF) 405. An adaptation layer 410 of the relay UE 210 resides on RLC entities 415 and 416 of the relay UE 210, wherein the entities at the adaptation layer map packets of the remote UE 215 between the RLC channels of the remote UE 215 and the relay UE 210. Similarly, an entity at the adaptation layer 411 of the access node 205 resides on the RLC layer 417 of the access node 205, wherein packets of radio bearers of the remote UE 215 are mapped to or from the RLC channel 417 between the relay UE 210 and the access node 205. Since the entities at adaptation layers 410 and 411 are applicable to RLC channels of all radio bearers, the entities at adaptation layers 410 and 411 support both SRB and DRB for remote UE 215.

[0031] Generally, Layer 3 side-link relay can relay unicast traffic (uplink and downlink) between a remote UE and the network (as described in 3GPP TR 23.752, which is incorporated herein by reference in its entirety):

[0032] Internet Protocol (IP) traffic at the PC5 interface reference point, ProSe UE to network relay uses IP-type Protocol Data Unit (PDU) sessions oriented towards the Fifth Generation Core (5GC).

[0033] Ethernet traffic at the PC5 interface reference point, ProSe UE to network trunk can use either an Ethernet-type PDU session or an IP-type PDU session for 5GC.

[0034] - For unstructured traffic at the 5GC interface reference point, ProSe UE to network relay can use unstructured type PDU sessions or IP type PDU sessions oriented towards 5GC (i.e., IP encapsulation or decapsulation performed by UE to network relay).

[0035] Figure 5A protocol stack 500 of an example communication system with a Layer 3 side walkway relay is shown. The communication system includes a remote UE 215, a relay UE 210 (i.e., a Layer 3 side walkway relay), an access node 205, and a UPF 505.

[0036] In the Layer 3 UE-to-network relay method, the 5G Quality of Service (QoS) flow is initially mapped to a PC5 QoS flow for sidelink transmission. Then, the PC5 QoS flow is mapped to the 5G QoS flow of relay UE 210 for transmission via the Uu interface. Finally, at UPF 505, the 5G QoS flow of relay UE 210 is mapped back to the 5G QoS flow associated with remote UE 215. These flow mappings occur in adaptation layers, such as adaptation layer 507 for remote UE 215, adaptation layer 509 for relay UE 210, and adaptation layer 511 for UPF 505.

[0037] Because Layer 3 side hop relay operates at the PDU connection level, it does not relay control plane data between remote UE 215 and access node 205 via relay UE 210. On the other hand, Layer 2 side hop relay operates at the RLC channel level and is therefore independent of SRB or DRB. Therefore, both control plane data and data plane data between remote UE 215 and access node 205 can be relayed via relay UE 210.

[0038] According to an example embodiment, a method and apparatus for setting up an indirect connection between a remote UE and an access node are provided. A relay UE acts as a sidelink relay, relaying control plane data and user plane data between the remote UE and the access node. Various techniques can be used to set up the indirect connection. For example, sidelink unicast communication can be used.

[0039] Figure 6 A schematic diagram 600 illustrates the entities involved in exchanging communication and performing processing during an example connection setup process from a UE to a network relay. The entities exchanging communication and performing processing include the remote UE 605, the relay UE 607, the serving access node 609, the AMF / session management function (SMF) / policy control function (PCF) 611, and the UPF 613. Figure 6 The connection setup process for the Layer 2 and Layer 3 side walkway relay model is shown.

[0040] For both Layer 2 and Layer 3 side walkway relay models

[0041] - Requires PC5 RRC connection configuration for sidelink bearer for unicast transmission between remote UE 605 and trunk UE 607.

[0042] -The RAN uses the RRC connection between the relay UE 607 and the RAN to provide the relay UE 607 with the side link bearer configuration for the PC5 segment of the UE-to-network trunk connection.

[0043] The RRC connection between the relay UE 607 and the RAN is also configured with the adaptation layer in the Layer 2 side mobile link relay model.

[0044] Discovery and authorization of relay UE 607 are performed (block 615). Remote UE 605, serving access node 609, AMF / SMF / PCF 611, and relay UE 607 perform discovery and authorization to discover the relay UE (i.e., relay UE 607), which is a suitable relay for remote UE 605 and is authorized to be used as a relay UE for remote UE 605. In the Layer 2 and Layer 3 relay UE models, the discovery and authorization of relay UE 607 includes the authorization of relay UE 607. Furthermore, remote UE 605 provides information associated with serving access node 609, including the public land mobile network (PLMN) identifier and cell identifier of serving access node 609.

[0045] Relay UE 607 and remote UE 605 establish a PC5 RRC connection (block 617). For example, the PC5 RRC connection supports unicast communication between remote UE 605 and relay UE 607. For example, the establishment of the PC5 RRC connection is accomplished by relay UE 607 and remote UE 605 exchanging messages.

[0046] After successfully discovering and authorizing relay UE 607, remote UE 605 sends a UE to network connection setup request to relay UE 607 (Event 619). Remote UE 605 requests to establish a UE to network relay by sending a request to relay UE 607. This request includes information such as the PLMN of serving access node 609 and the identifier of remote UE 605. In the case of a Layer 3 relay model, remote UE 605 also provides information about the PC5 QoS flow used by the UE to network relay. Relay UE 607 forwards this request to serving access node 609 (Event 621). Relay UE 607 forwards the request to serving access node 609, along with the information included (e.g., the PLMN of serving access node 609 and the identifier of remote UE 605).

[0047] Serving access node 609 and AMF / SMF / PCF 611 perform admission control (block 623). Serving access node 609 and AMF / SMF / PCF 611 perform policy checks and admission control to allow remote UE 605 to connect indirectly to 5G via relay UE 607. Policy checks and admission control are performed based on information associated with remote UE 605 and relay UE 607. In the case of a Layer 2 relay model, serving access node 609 also provides QoS information for remote UE 605.

[0048] Serving Access Node 609 sends a Relay UE Setup Response (Event 625) to Relay UE 607. Serving Access Node 609 provides the Relay UE 607 with the RLC configuration of the Remote UE's DRB through the PC5 interface between Remote UE 605 and Relay UE 607. In the case of a Layer 2 relay model, Serving Access Node 609 also provides the Relay UE 607 with an adaptation configuration to map the RLC channels of the Uu interface between Relay UE 607 and Serving Access Node 609, as well as the RLC channels of the PC5 interface between Remote UE 605 and Relay UE 607, and provides a container for the DRB configuration of Remote UE 605. The DRB configuration may include Service Data Application Protocol (SDAP) configuration and PDCP configuration, including the mapping of 5G QoS flows to the DRB. In the case of a Layer 3 relay model, the serving access node 609 also provides the relay UE 607 with SDAP and PDCP configurations for the sidelink DRB through the PC5 interface between the remote UE 605 and the relay UE 607, including the mapping of PC5 QoS flows to the DRB.

[0049] Dashed box 627 illustrates the control plane and user plane connections of remote UE 607 in the Layer 2 relay model. Dashed box 629 illustrates the user plane connection of remote UE 607 in the Layer 3 relay model. The control plane and user plane connections are currently suspended at relay UE 607.

[0050] Relay UE 607 sends a UE-to-Network Relay Setup Response (Event 631) to remote UE 605. Relay UE 607 configures the RLC entity for the sidelink bearer. In the Layer 2 relay model, relay UE 607 also forwards the signaling container of the bearer configuration of remote UE 605 to remote UE 605. The signaling container for the bearer configuration includes, for example, SDAP and PDCP configurations, including the mapping of 5G QoS flows to the DRB. In the Layer 3 relay model, relay UE 607 configures the SDAP and PDCP configurations of the sidelink DRB for remote UE 605 through the PC5 interface between remote UE 605 and relay UE 607, including the mapping of PC5 QoS flows to the DRB.

[0051] Remote UE 605 sends a UE-to-network relay setup complete message (Event 633) to relay UE 607. After establishing the RLC entity of the sidelink bearer, remote UE 605 provides establishment confirmation to relay UE 607. Remote UE 605 can also update the RLC configuration of the sidelink bearer. In the case of a Layer 2 relay model, remote UE 605 also provides signaling to relay UE 607 containing confirmation of the correct configuration of the SDAP entity and PDCP entity of the UE to the network DRB. In the case of a Layer 3 relay model, remote UE 605 also provides confirmation of the SDAP configuration and PDCP configuration of the sidelink DRB to relay UE 607. Remote UE 605 can also provide possible updates to the SDAP configuration and PDCP configuration of the sidelink bearer.

[0052] Relay UE 607 forwards a relay UE setup complete message (event 635) to serving access node 609. For example, relay UE 607 notifies serving access node 609 that a sidelink RLC channel from the UE to the network relay has been established. In the Layer 2 relay model, relay UE 607 also notifies serving access node 609 that a mapping has been established between the sidelink RLC channel and the Uu RLC channel carrying the same packets at the adaptation layer for remote UEs. Relay UE 607 also forwards a container confirming the correct configuration of the SDAP and PDCP entities carried by the UE to the network. In the Layer 3 relay model, relay UE 607 also notifies serving access node 609 that the SDAP and PDCP entities carried by the sidelink have been established.

[0053] Dashed box 637 illustrates the control plane and user plane connections of remote UE 607 in the Layer 2 relay model. Dashed box 639 illustrates the user plane connection of remote UE 607 in the Layer 3 relay model. The control plane and user plane connections extend to remote UE 605.

[0054] Table 1 details the steps involved in setting up an example UE-to-network relay connection for both Layer 2 and Layer 3 relay models.

[0055] Table 1: Steps for Setting Up Relay UE Connections in Layer 2 and Layer 3

[0056]

[0057]

[0058]

[0059] Although UE-to-network trunk connections can be established for Layer 2 and Layer 3 trunk models as described above, remote UEs of Layer 2 trunk services establish control plane and user plane connections with the service access node and enter the RRC_Connected state, while remote UEs of Layer 3 trunk services will not exist in the RAN.

[0060] Furthermore, once the aforementioned UE-to-network relay setup process is complete, the Layer 2 relay can operate its adaptation layer through the correct configuration of the RLC channel mapping between the PC5 and Uu interfaces.

[0061] Figure 7 A flowchart illustrating an example operation 700 occurring in a remote UE participating in establishing a UE-to-network relay connection is shown. Operation 700 can indicate the operations that occur in a remote UE when the remote UE participates in establishing a UE-to-network relay connection. Layer 2 and Layer 3 relay model connections can be established.

[0062] Operation 700 begins with the remote UE performing relay UE discovery and authorization (block 705). Relay UE discovery and authorization is performed to detect relay UEs that are suitable candidates to operate as relay UEs of the remote UE. For example, to be a suitable candidate to operate as a relay UE of the remote UE, the relay UE may need to be located within a specified distance from the remote UE (or the channel between the relay UE and the remote UE may have sufficient signal quality), and the relay UE may be able to act as a relay UE of the remote UE, and the relay UE may be authorized to act as a relay UE of the remote UE. As part of the relay UE discovery and authorization, the remote UE provides information related to the serving access node (e.g., the PLMN and cell identifier of the serving access node).

[0063] The remote UE establishes an RRC connection (block 707). An RRC connection is established between the remote UE and the relay UE. For example, the RRC connection supports unicast communication. The remote UE sends a UE-to-network relay connection setup request (block 709). The UE-to-network relay connection setup request is a request sent via the RLC channel on the sidelink to establish a UE-to-network relay connection. This request includes information including the PLMN selected by the remote UE and the identifier of the remote UE. In the case of a Layer 3 relay model, the request also includes information about the PC5 QoS flow used by the UE to establish the network relay connection.

[0064] The remote UE receives a UE-to-network relay setup response (block 711). This response can indicate to the remote UE that the UE-to-network relay setup is complete. This response can be received from the relay UE, which has configured the RLC entity for the sidelink radio bearer. In the case of a Layer 2 relay model, the remote UE also receives signaling containing bearer configuration, including SDAP and PDCP configurations, such as the mapping of 5G QoS flows to the DRB. In the case of a Layer 3 relay model, the remote UE has configured the SDAP and PDCP configurations for the sidelink DRB via the PC5 interface between the remote UE and the relay UE. These configurations can include the mapping of PC5 QoS flows to the DRB.

[0065] The remote UE sends a confirmation to the relay UE that the network relay setup is complete (block 713). The remote UE provides the relay UE with an acknowledgment that the network relay setup is complete. The remote UE may also provide updates to the RLC configuration of the sidelink bearer. In the Layer 2 relay model, the remote UE also provides the relay UE with signaling confirming the correct configuration of the SDAP and PDCP entities of the network bearer. In the Layer 3 relay model, the remote UE also provides the relay UE with confirmations of the SDAP and PDCP configurations of the sidelink DRB (along with possible updates).

[0066] Figure 8 A flowchart illustrating an example operation 800 occurring in a relay UE participating in establishing a UE-to-network relay connection is shown. Operation 800 can indicate the operations that occur in a relay UE when the relay UE participates in establishing a UE-to-network relay connection. Layer 2 and Layer 3 relay model connections can be established.

[0067] Operation 800 begins with the relay UE performing relay UE discovery and authorization (block 805). Relay UE discovery and authorization is performed to identify relay UEs that are suitable candidates for operation as relay UEs of remote UEs. For example, to be a suitable candidate for operation as a relay UE of a remote UE, the relay UE may need to be located within a specified distance from the remote UE (or the channel between the relay UE and the remote UE may have sufficient signal quality), and the relay UE may be capable of being used as a relay UE of the remote UE, and the relay UE may be authorized to be used as a relay UE of the remote UE. As part of relay UE discovery and authorization, the relay UE provides information related to the serving access node (e.g., the PLMN and cell identifier of the serving access node).

[0068] The relay UE establishes an RRC connection (block 807). An RRC connection is established between the remote UE and the relay UE. For example, the RRC connection supports unicast communication. The relay UE receives a UE-to-network relay connection setup request (block 809). The relay UE receives the UE-to-network relay connection setup request from the remote UE. The UE-to-network relay connection setup request is a request to establish a UE-to-network relay connection. This request includes information including the PLMN information received by the remote UE from the relay UE and the identifier of the remote UE. In the case of a Layer 3 relay model, the request also includes information about the PC5 QoS flow used by the UE to establish the network relay connection.

[0069] The relay UE forwards the UE-to-network relay connection setup request (block 811). For example, the UE-to-network relay connection setup request can be forwarded to the serving access node serving the relay UE. The relay UE receives the UE-to-network relay connection setup response (block 813). The UE-to-network relay connection setup response can be received from the serving access node. The relay UE receives RLC configuration through the PC5 interface between the remote UE and the relay UE. In the Layer 2 relay model, the relay UE also provides an adaptation configuration to map the RLC channels of the Uu interface (between the serving access node and the relay UE) and the PC5 interface (between the relay UE and the remote UE) for packets of the corresponding radio bearer for the remote UE, and provides signaling containing the radio bearer configuration of the remote UE, including SDAP configuration and PDCP configuration (e.g., mapping of 5G QoS flows to DRB). The relay UE sends the UE-to-network relay connection setup response (block 815). For example, the relay UE sends the UE-to-network relay connection setup response to the remote UE.

[0070] The relay UE receives a UE-to-network setup complete message (block 817). For example, this message can be received from a remote UE. The relay UE receives signaling confirming the UE's network relay setup is complete. The relay UE can also provide updates to the RLC configuration of the sidelink radio bearer. In the Layer 2 relay model, the relay UE receives signaling confirming the correct configuration of the SDAP and PDCP entities of the network radio bearer. In the Layer 3 relay model, the relay UE receives confirmations (and possible updates) of the SDAP and PDCP configurations of the sidelink DRB.

[0071] The relay UE forwards a network setup completion message (block 819). For example, the relay UE notifies the serving access node that a sidelink RLC channel from the UE to the network relay has been established. In the Layer 2 relay model, the relay UE notifies the serving access node that a mapping has been established between the sidelink RLC channel and the Uu RLC channel for packets on the corresponding radio bearer at the adaptation layer for remote UEs. The relay UE forwards signaling confirming the correct configuration of the SDAP and PDCP entities from the UE to the network radio bearer. In the Layer 3 relay model, the relay UE notifies the serving access node that the SDAP and PDCP entities for the sidelink DRB have been established.

[0072] Figure 9 A flowchart illustrating an example operation 900 occurring in a serving access node participating in establishing a UE-to-network relay connection is shown. Operation 900 can indicate the operations that occur in the serving access node when it participates in establishing a UE-to-network relay connection. Layer 2 and Layer 3 relay model connections can be established.

[0073] Operation 900 begins with the serving access node performing relay UE discovery and authorization (block 905). Relay UE discovery and authorization is performed to detect relay UEs that are suitable candidates for operation as relay UEs of remote UEs. For example, to be a suitable candidate for operation as a relay UE of a remote UE, a relay UE may need to be located within a specified distance from the remote UE (or the channel between the relay UE and the remote UE may have sufficient signal quality), and the relay UE may be capable of acting as a relay UE of the remote UE, and the relay UE may be authorized to act as a relay UE of the remote UE. As part of the relay UE discovery and authorization, the remote UE provides information related to the serving access node (e.g., the serving access node's PLMN and cell identifier).

[0074] The serving access node receives a UE-to-network relay connection setup request (block 907). The UE-to-network relay connection setup request is a request to establish a UE-to-network relay connection. This request includes information including the PLMN selected by the remote UE and the identifier of the remote UE. In the case of a Layer 3 relay model, the request also includes information about the PC5 QoS flow used by the UE to establish the network relay connection.

[0075] The serving access node performs admission control (block 909). Based on information from the remote UE and the relay UE, the serving access node and network control functions (e.g., AMF, SMF, or PCF) perform policy checks and admission control to allow the remote UE to connect to 5G indirectly through the relay UE. In the case of a Layer 2 relay model, the serving access node provides QoS flow information for the remote UE.

[0076] The serving access node sends a UE-to-network relay connection setup response (block 911). This response can indicate to the remote UE that the UE-to-network relay connection setup has been approved. This response can be received from the relay UE, which has already configured the RLC entity for the sidelink radio bearer. In the case of a Layer 2 relay model, the remote UE also receives signaling containing bearer configuration, including SDAP and PDCP configurations, such as the mapping of 5G QoS flows to the DRB. In the case of a Layer 3 relay model, the remote UE has configured the SDAP and PDCP configurations for the sidelink DRB via the PC5 interface between the remote UE and the relay UE. These configurations can include the mapping of PC5 QoS flows to the DRB.

[0077] The serving access node receives a UE-to-network relay connection setup complete message (block 913). This message includes confirmation that the UE-to-network relay connection setup configuration (e.g., the configuration of the RLC channel on the Uu interface and the sidelink interface) is complete. The serving access node may also receive updates to the RLC configuration of the sidelink radio bearer. The serving access node also receives signaling from the relay UE containing confirmation that the SDAP entity and PDCP entity for the remote UE used for the UE-to-network relay connection are correctly configured.

[0078] Figure 10 A flowchart illustrating an example operation 1000 occurring during a network control function involved in establishing a UE-to-network relay connection is shown. Operation 1000 can indicate operations that occur within a network function when the network function is involved in establishing a UE-to-network relay connection. Layer 2 and Layer 3 relay model connections can be established. Examples of network control functions include AMF, SMF, or PCF.

[0079] Operation 1000 begins with the network control function performing relay UE discovery and authorization (block 1005). Relay UE discovery and authorization is performed to detect relay UEs that are suitable candidates for operation as relay UEs of remote UEs. For example, to be a suitable candidate for operation as a relay UE of a remote UE, a relay UE may need to be located within a specified distance from the remote UE (or the channel between the relay UE and the remote UE may have sufficient signal quality), and the relay UE may be able to act as a relay UE of the remote UE, and the relay UE may be authorized to act as a relay UE of the remote UE. As part of relay UE discovery and authorization, the remote UE provides information related to the serving access node (e.g., the PLMN and cell identifier of the serving access node).

[0080] The network control function performs admission control (block 1007). Based on information from the remote UE and the relay UE, the network control function and the service access node perform policy checks and admission control to allow the remote UE to connect to 5G indirectly through the relay UE. In the case of a Layer 2 relay model, the network control function provides QoS flow information for the remote UE.

[0081] Figure 11 An example communication system 1100 is illustrated. Generally, system 1100 enables multiple wireless or wired users to send and receive data and other content. System 1100 can implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0082] In this example, the communication system 1100 includes electronic devices (EDs) 1110a to 1110c, radio access networks (RANs) 1120a and 1120b, a core network 1130, a public switched telephone network (PSTN) 1140, the Internet 1150, and other networks 1160. Although Figure 11A certain number of these components or elements are shown, but system 1100 may include any number of these components or elements.

[0083] EDs 1110a to 1110c are configured to operate or communicate within system 1100. For example, EDs 1110a to 1110c are configured to transmit or receive via a wireless communication channel or a wired communication channel. EDs 1110a to 1110c represent any suitable end-user equipment and may include (or be referred to as) devices such as: user equipment (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, personal digital assistant (PDA), smartphone, laptop computer, computer, touchpad, wireless sensor, or consumer electronic device.

[0084] RAN 1120a and 1120b here include base stations 1170a and 1170b, respectively. Base stations 1170a and 1170b are configured to have a radio connection with one or more of ED 1110a to 1110c in order to access the core network 1130, PSTN 1140, Internet 1150, or other networks 1160. For example, base stations 1170a and 1170b may include (or may be) one or more of several well-known devices, such as a base transceiver station (BTS), a Node B, an evolved Node B (eNodeB), a Next Generation (NG) Node B (gNB), a Home Node B, a Home eNode B, a site controller, an access point (AP), or a wireless router. ED 1110a to 1110c are configured to connect and communicate with the Internet 1150 and can access the core network 1130, PSTN 1140 or other networks 1160.

[0085] exist Figure 11In the illustrated embodiment, base station 1170a constitutes part of RAN 1120a, which may include other base stations, components, or devices. Similarly, base station 1170b constitutes part of RAN 1120b, which may include other base stations, components, and / or devices. Both base stations 1170a and 1170b operate to transmit or receive radio signals within a specific geographic area (sometimes referred to as a "cell"). In some embodiments, multiple-input multiple-output (MIMO) technology may be employed, with each cell having multiple transceivers.

[0086] Base stations 1170a and 1170b communicate with one or more of ED 1110a to 1110c via a wireless communication link on one or more air interfaces 1190. Air interface 1190 can use any suitable wireless access technology.

[0087] It is conceivable that system 1100 can use multi-channel access capabilities, including the schemes described above. In specific embodiments, the base station and ED implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and radio protocols can be used.

[0088] RANs 1120a and 1120b communicate with the core network 1130 to provide voice, data, application, Voice over Internet Protocol (VoIP), or other services to EDs 1110a through 1110c. It is understood that RANs 1120a and 1120b or the core network 1130 can communicate directly or indirectly with one or more other RANs (not shown). The core network 1130 can also serve as a gateway access for other networks (e.g., PSTN 1140, Internet 1150, and other networks 1160). Additionally, some or all of EDs 1110a through 1110c may include the ability to communicate with different wireless networks via different wireless links using different wireless technologies or protocols. Instead of wireless communication (or other than wireless communication), EDs can communicate with service providers or switches (not shown) and with the Internet 1150 via wired communication channels.

[0089] Although Figure 11 An example of a communication system is shown, but it is possible to... Figure 11 Various modifications can be made. For example, the communication system 1100 can include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0090] Figure 12A and Figure 12BExample devices are shown that can implement various methods and teachings according to this disclosure. In particular, Figure 12A Example ED 1210 is shown. Figure 12B Example base station 1270 is shown. These components can be used in system 1100 or any other suitable system.

[0091] like Figure 12A As shown, ED 1210 includes at least one processing unit 1200. The processing unit 1200 implements various processing operations of ED 1210. For example, the processing unit 1200 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables ED 1210 to operate within system 1100. The processing unit 1200 also supports the methods and teachings described in detail above. Each processing unit 1200 includes any suitable processing device or computing device configured to perform one or more operations. Each processing unit 1200 may, for example, include a microprocessor, microcontroller, digital signal processor, field-programmable gate array, or application-specific integrated circuit.

[0092] ED 1210 also includes at least one transceiver 1202. Transceiver 1202 is configured to modulate data or other content for transmission by at least one antenna or Network Interface Controller (NIC) 1204. Transceiver 1202 is also configured to demodulate data or other content received by at least one antenna 1204. Each transceiver 1202 includes any suitable structure for generating signals for wireless or wired transmission or for processing signals received wirelessly or wiredly. Each antenna 1204 includes any suitable structure for transmitting or receiving wireless or wired signals. One or more transceivers 1202 may be used in ED 1210, and one or more antennas 1204 may be used in ED 1210. Although shown as a single functional unit, transceiver 1202 can also be implemented using at least one transmitter and at least one separate receiver.

[0093] ED 1210 also includes one or more input / output devices 1206 or interfaces (e.g., a wired interface connected to the Internet 1150). Input / output devices 1206 facilitate interaction with users or other devices on the network (network communication). Each input / output device 1206 includes any suitable structure for providing or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network interface communication.

[0094] Additionally, ED 1210 includes at least one memory 1208. Memory 1208 stores instructions and data used, generated, or acquired by ED 1210. For example, memory 1208 may store software or firmware instructions executed by processing unit 1200, as well as data used to reduce or eliminate interference in incoming signals. Each memory 1208 includes any suitable volatile or non-volatile storage and retrieval device. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, etc.

[0095] like Figure 12B As shown, base station 1270 includes at least one processing unit 1250, at least one transceiver 1252 (including transmitter and receiver functions), one or more antennas 1256, at least one memory 1258, and one or more input / output devices or interfaces 1266. A scheduler, as will be understood by those skilled in the art, is coupled to the processing unit 1250. The scheduler may be included within base station 1270 or may operate separately from base station 1270. The processing unit 1250 implements various processing operations of base station 1270, such as signal encoding, data processing, power control, input / output processing, or any other functions. The processing unit 1250 may also support the methods and teachings described in detail above. Each processing unit 1250 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 1250 may, for example, include a microprocessor, microcontroller, digital signal processor, field-programmable gate array, or application-specific integrated circuit.

[0096] Each transceiver 1252 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 1252 also includes any suitable structure for processing signals received wirelessly or wired from one or more EDs or other devices. Although shown as a combination of transceiver 1252, the transmitter and receiver may be separate components. Each antenna 1256 includes any suitable structure for transmitting or receiving wireless or wired signals. Although a common antenna 1256 coupled to transceiver 1252 is shown here, one or more antennas 1256 may be coupled to transceiver 1252, allowing individual antennas 1256 to be coupled to transmitters and receivers (if configured as separate components). Each memory 1258 includes any suitable volatile or non-volatile storage and retrieval device. Each input / output device 1266 facilitates interaction with users or other devices in the network (network communication). Each input / output device 1266 includes any suitable structure for providing information to or receiving information from a user, including network interface communication.

[0097] Figure 13 This is a block diagram of a computing system 1300 that can be used to implement the various devices and methods disclosed herein. For example, the computing system can be any entity in a UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). A particular device may use all of the components shown or only a subset of those components, and the degree of integration between devices may vary. Furthermore, a device may contain multiple instances of components, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 1300 includes a processing unit 1302. The processing unit includes a central processing unit (CPU) 1314, memory 1308, and may also include a mass storage device 1304 connected to a bus 1320, a video adapter 1310, and an I / O interface 1312.

[0098] Bus 1320 can be one or more of several bus architectures of any type, including a memory bus or memory controller, a peripheral bus, or a video bus. CPU 1314 can include any type of electronic data processor. Memory 1308 can include any type of non-transitory system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In one embodiment, memory 1308 can include ROM used at power-on and DRAM storing programs and data used during program execution.

[0099] Mass storage 1304 may include any type of non-transitory storage device, configured to store data, programs, and other information, and to make such data, programs, and other information accessible via bus 1320. Mass storage 1304 may, for example, include one or more of a solid-state drive, hard disk drive, disk drive, or optical disk drive.

[0100] Video adapter 1310 and I / O interface 1312 provide interfaces to couple external input and output devices to processing unit 1302. Examples of input and output devices, as shown, include a display 1318 coupled to video adapter 1310 and a mouse, keyboard, or printer 1316 coupled to I / O interface 1312. Other devices may be coupled to processing unit 1302, and other or fewer interface cards may be used. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for external devices.

[0101] The processing unit 1302 also includes one or more network interfaces 1306, which may include a wired link, such as an Ethernet cable, or a wireless link, to access nodes or different networks. The network interface 1306 allows the processing unit 1302 to communicate with remote units over a network. For example, the network interface 1306 may provide wireless communication via one or more transmitter / transmit antennas and one or more receiver / receive antennas. In one embodiment, the processing unit 1302 is coupled to a local area network 1322 or a wide area network to perform data processing and communication with other processing units, the Internet, or remote devices such as remote storage facilities.

[0102] Figure 14A block diagram of an example processing system 1400 for performing the methods described herein is shown. The processing system 1400 can be installed in a host device. As shown, the processing system 1400 includes a processor 1404, a memory 1406, and interfaces 1410 to 1414, which may or may not be as described... Figure 14 The configuration is as shown. Processor 1404 can be any component or set of components adapted to perform computational and / or other processing-related tasks, and memory 1406 can be any component or set of components adapted to store programming and / or instructions for execution by processor 1404. In one embodiment, memory 1406 includes a non-transitory computer-readable medium. Interfaces 1410, 1412, and 1414 can be any component or set of components that allows processing system 1400 to communicate with other devices / components and / or users. For example, one or more of interfaces 1410, 1412, and 1414 can be adapted to communicate data, control, or management messages from processor 1404 to applications installed on host devices and / or remote devices. As another example, one or more of interfaces 1410, 1412, and 1414 can be adapted to allow a user or user device (e.g., a personal computer (PC)) to interact / communicate with processing system 1400. Processing system 1400 may include... Figure 14 Other components not shown include long-term memory (e.g., non-volatile memory).

[0103] In some embodiments, the processing system 1400 is included in a network device that is connected to or part of a telecommunications network. In one example, the processing system 1400 is located in a network-side device in a wireless or wired telecommunications network, such as a base station, relay station, scheduler, controller, gateway, router, application server, or any other device in the telecommunications network. In other embodiments, the processing system 1400 is located in a user-side device connected to a wireless or wired telecommunications network, such as a mobile station, user equipment (UE), personal computer (PC), tablet computer, wearable communication device (e.g., smartwatch), or any other device suitable for accessing the telecommunications network.

[0104] In some embodiments, one or more of interfaces 1410, 1412, and 1414 connect the processing system 1400 to a transceiver adapted to send and receive signaling over a telecommunications network. Figure 15A block diagram of a transceiver 1500 suitable for sending and receiving signaling over a telecommunications network is shown. The transceiver 1500 can be installed in a host device. As shown, the transceiver 1500 includes a network-side interface 1502, a coupler 1504, a transmitter 1506, a receiver 1508, a signal processor 1510, and a device-side interface 1512. The network-side interface 1502 may include any component or set of components suitable for sending or receiving signaling over a wireless or wired telecommunications network. The coupler 1504 may include any component or set of components suitable for facilitating bidirectional communication over the network-side interface 1502. The transmitter 1506 may include any component or set of components (e.g., an up-converter, a power amplifier, etc.) suitable for converting a baseband signal into a modulated carrier signal suitable for transmission over the network-side interface 1502. The receiver 1508 may include any component or set of components (e.g., a down-converter, a low-noise amplifier, etc.) suitable for converting a carrier signal received through the network-side interface 1502 into a baseband signal. Signal processor 1510 may include any component or set of components adapted to convert baseband signals into data signals suitable for communication via one or more device-side interfaces 1512, and vice versa. Device-side interface 1512 may include any component or set of components adapted to communicate data signals between signal processor 1510 and components within a host device (e.g., processing system 1400, local area network (LAN) port, etc.).

[0105] Transceiver 1500 can send and receive signaling via any type of communication medium. In some embodiments, transceiver 1500 sends and receives signaling via a wireless medium. For example, transceiver 1500 may be a wireless transceiver adapted to communicate according to wireless communication protocols (e.g., cellular protocols such as Long-Term Evolution (LTE), Wireless Local Area Network (WLAN) protocols such as Wi-Fi, or any other type of wireless protocol such as Bluetooth, Near Field Communication (NFC)). In these embodiments, network-side interface 1502 includes one or more antenna / radiating elements. For example, network-side interface 1502 may include a single antenna, multiple independent antennas, or a multi-antenna array configured for multi-layer communication, such as single-input multiple-output (SIMO), multiple-input single-output (MISO), multiple-input multiple-output (MIMO), etc. In other embodiments, transceiver 1500 transmits and receives signaling via wired media such as twisted-pair cable, coaxial cable, or optical fiber. A particular processing system and / or transceiver may utilize all of the components shown, or only a subset of these components, and the degree of integration may vary from device to device.

[0106] It should be understood that one or more steps in the methods of the embodiments provided herein can be performed by corresponding circuits, units, or modules. For example, a signal can be transmitted by a transmitting circuit, unit, or module. A signal can be received by a receiving circuit, unit, or module. A signal can be processed by a processing circuit, unit, or module. Other steps can be performed by participating circuits, units, or modules. The corresponding circuits, units, or modules can be hardware, software, or a combination thereof. For example, one or more of these circuits, units, or modules can be integrated circuits, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0107] Although the present disclosure and its advantages have been described in detail, it should be understood that various modifications, substitutions and alterations may be made herein without departing from the scope of the disclosure as defined by the appended claims.

Claims

1. A communication method applied to a first user equipment (UE), characterized in that, The method includes: Receive network relay connection setup request from the second UE; Send a relay connection configuration request to the access node; Receive a relay connection setup response from the access node; and Send the UE to network relay connection setup response to the second UE; The relay connection setup response includes configuration information for the Radio Link Control (RLC) channel of the sidelink between the first UE and the second UE, and the RLC channel between the first UE and the access node, mapped by the adaptation layer.

2. The method according to claim 1, characterized in that, Also includes: The second UE participates in the RLC connection establishment process.

3. The method according to claim 2, characterized in that, The RLC connection establishment process establishes a sidelink RLC connection for UE-to-network communication.

4. The method according to any one of claims 1 to 3, characterized in that, Also includes: The second UE participates in the discovery and authorization process.

5. The method according to claim 2, characterized in that, The RLC connection establishment process establishes an RLC connection between the first UE and the access node.

6. The method according to any one of claims 1 to 3, characterized in that, The relay connection setup response includes the configuration of the radio bearer for the UE-to-network connection.

7. The method according to claim 6, characterized in that, The relay connection setup response includes information on the Service Data Application Protocol (SDAP) configuration and Packet Data Convergence Protocol (PDCP) configuration of the Data Radio Bearer (DRB), as well as the mapping of Quality of Service (QoS) flows to the DRB.

8. The method according to claim 1, characterized in that, The UE-to-network relay connection setup response includes the configuration of the first UE for the RLC entity of the side link to the second UE and the RLC entity of the connection to the access node.

9. A communication method applied to a first user equipment (UE), characterized in that, The method includes: Send a UE to network relay connection setup request to the second UE; and After the second UE receives the relay connection setting response from the access node, the second UE receives the UE-to-network relay connection setting response. The relay connection setup response includes configuration information for the Radio Link Control (RLC) channel of the sidelink between the first UE and the second UE and the RLC channel between the second UE and the access node, which are mapped by the adaptation layer.

10. The method according to claim 9, characterized in that, Also includes: The second UE participates in the Radio Link Control (RLC) connection establishment process.

11. The method according to claim 10, characterized in that, The RLC connection establishment process establishes a sidelink RLC connection for UE-to-network communication.

12. The method according to any one of claims 9 to 11, characterized in that, Also includes: The second UE participates in the discovery and authorization process.

13. The method according to any one of claims 9 to 11, characterized in that, The UE-to-network relay connection setup request includes Public Land Mobile Network (PLMN) information and the identification information of the first UE.

14. The method according to any one of claims 9 to 11, characterized in that, The UE-to-network relay connection setup response includes information on the radio bearer configuration.

15. The method according to claim 14, characterized in that, The radio bearer configuration includes the configuration of the RLC channel for the sidelink between the first UE and the second UE.

16. The method according to any one of claims 9 to 11, characterized in that, The UE-to-network relay connection setup response includes information on the Service Data Application Protocol (SDAP) configuration and Packet Data Convergence Protocol (PDCP) configuration of the Data Radio Bearer (DRB), as well as the mapping of Quality of Service (QoS) flow information to the DRB.

17. A first user equipment (UE), characterized in that, include: One or more processors; as well as Includes non-transitory memory for instructions, which, when executed by the one or more processors, cause the first UE to: Receive a first sidelink message from the second UE, which includes a request to set up a sidelink between the first UE and the second UE to establish a network relay connection. Send a relay connection configuration request to the access node; Receive a relay connection setup response from the access node; and Send a second-side walkway message, including the UE's response to the network relay connection setup, to the second UE; The relay connection setup response includes configuration information for the Radio Link Control (RLC) channel of the sidelink between the first UE and the second UE, and the RLC channel between the first UE and the access node, mapped by the adaptation layer.

18. The first UE according to claim 17, characterized in that, The instruction causes the first UE and the second UE to participate in the Radio Resource Control (RRC) connection establishment process.

19. The first UE according to claim 18, characterized in that, The RRC connection establishment process establishes a sidelink connection for unicast communication.

20. The first UE according to any one of claims 17 to 19, characterized in that, The instruction causes the first UE and the second UE to participate in the discovery and authorization process.

21. The first UE according to any one of claims 17 to 19, characterized in that, The relay connection setup response includes the configuration of the data radio bearer (DRB) for the side link.

22. The first UE according to claim 21, characterized in that, The UE-to-network relay connection setup request includes Quality of Service (QoS) flow information.

23. The first UE according to claim 22, characterized in that, The relay connection setup response includes the Service Data Application Protocol (SDAP) configuration and Packet Data Convergence Protocol (PDCP) configuration of the DRB, as well as the mapping of QoS flow information to the DRB.

24. The first UE according to claim 17, characterized in that, The UE-to-network relay connection setup response includes Service Data Application Protocol (SDAP) entity configuration and Packet Data Convergence Protocol (PDCP) entity configuration.

25. A first user equipment (UE), characterized in that, include: One or more processors; Includes non-transitory memory for instructions, which, when executed by the one or more processors, cause the first UE to: Sending a first sidelink message to the second UE, including a UE-to-network relay connection setup request to establish a sidelink between the first UE and the second UE; and After the second UE receives the relay connection setup response from the access node, it receives a second-side cross-link message including the UE-to-network relay connection setup response; The relay connection setup response includes configuration information for the Radio Link Control (RLC) channel of the sidelink between the first UE and the second UE and the RLC channel between the second UE and the access node, which are mapped by the adaptation layer.

26. The first UE according to claim 25, characterized in that, The instruction causes the first UE and the second UE to participate in the Radio Resource Control (RRC) connection establishment process.

27. The first UE according to claim 26, characterized in that, The RRC connection establishment process establishes a sidelink connection for unicast communication.

28. The first UE according to any one of claims 25 to 27, characterized in that, The instruction causes the first UE and the second UE to participate in the discovery and authorization process.

29. The first UE according to any one of claims 25 to 27, characterized in that, The UE-to-network relay connection setup request includes Quality of Service (QoS) flow information.

30. The first UE according to claim 29, characterized in that, The UE-to-network relay connection setup response includes the Service Data Application Protocol (SDAP) configuration and Packet Data Convergence Protocol (PDCP) configuration for the Data Radio Bearer (DRB), as well as the mapping of QoS flow information to the DRB.

31. The first UE according to any one of claims 25 to 27, characterized in that, The UE-to-network relay connection setup response includes a Data Radio Bearer (DRB) configuration container.

32. The first UE according to claim 31, characterized in that, The DRB configuration container includes Service Data Application Protocol (SDAP) configuration and Packet Data Convergence Protocol (PDCP) configuration.

33. A non-transitory computer-readable medium, characterized in that, The computer-readable medium stores instructions that, when executed by a processor, implement the communication method as described in any one of claims 1 to 8.

34. A non-transitory computer-readable medium, characterized in that, The computer-readable medium stores instructions that, when executed by a processor, implement the communication method as described in any one of claims 9 to 16.

35. A communication system, characterized in that, It includes the first user equipment (UE) as described in any one of claims 17 to 24 and the first user equipment (UE) as described in any one of claims 25 to 32.

Images