CN115278603A

CN115278603A - Communication method, device and system

Info

Publication number: CN115278603A
Application number: CN202110478632.9A
Authority: CN
Inventors: 彭文杰
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-04-30
Filing date: 2021-04-30
Publication date: 2022-11-01
Also published as: WO2022228275A1

Abstract

A communication method, a device and a system are used for realizing communication interaction between a network node supporting communication with terminal equipment through a PC5 interface and the network equipment so as to realize that the network node can provide a sidelink relay service for the terminal equipment. The method comprises the following steps: receiving a first request message from a first device, the first request message indicating an identity of at least one PLMN of the first device; the first equipment carries out lateral communication with the remote terminal equipment and communicates with the network equipment through a network interface; and sending a first response message to the first device, wherein the first response message is used for indicating the PCI, the PCI is determined based on the identification of the first PLMN, and the identification of the first PLMN is one or more of the identifications of at least one PLMN. The first device may thus be associated with a cell serving the remote terminal device, such that the first device communicates with the remote terminal device sideways and with the network device via the network interface.

Description

Communication method, device and system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method, apparatus, and system.

Background

In a scenario of a terminal device and a network device relay (UE-to-network relay), a relay user equipment (relay UE) and a remote terminal device (remote UE) are connected through a proximity-based service communication 5 (pc5) interface. The Uu interface connection exists between the network equipment and the relay UE, and the relay UE can help the remote UE to access the network equipment to obtain services.

At present, a roadside unit (RSU) (also called a roadside unit) of a cellular vehicle networking (cellular to X, C-V2X) system is responsible for receiving real-time traffic information such as road condition information sent by a traffic signal lamp and an application server, and dynamically broadcasting the real-time traffic information to related vehicles, so as to avoid or reduce traffic accidents. The communication between the vehicle and the RSU employs PC5 or sidelink (sidelink) technology. The RSU can be accessed to the broadband directly through a wired mode and the like. In the above process, the UE establishes connection with the RSU only for V2X communication, and does not access the network through the RSU, which may cause waste of network resources.

Disclosure of Invention

The application provides a communication method, a communication device and a communication system, which are used for realizing communication interaction between a network node supporting communication with a terminal device through a PC5 interface and the network device, so that the network node can provide a side link relay service for the terminal device.

In a first aspect, the present application provides a communication method, which may be applied to a network device, or a processor, or a chip system, or a functional module in the network device. The method can comprise the following steps: receiving a first request message from a first device, and sending a first response message to the first device; wherein the first request message is used to indicate an identity of at least one Public Land Mobile Network (PLMN) of the first device; the first equipment carries out lateral communication with the remote terminal equipment and communicates with the network equipment through a network interface; the first response message is configured to indicate a Physical Cell Identifier (PCI), where the PCI is determined based on an identifier of a first PLMN, and the identifier of the first PLMN is one or more of the identifiers of the at least one PLMN.

By the method, the communication between the first device and the network device can be realized, the first device can be associated with a cell serving the remote terminal device, so that the first device and the remote terminal device perform side-line communication, and the first device and the network device communicate through a network interface, so that side-line link relay service is provided for the remote terminal device.

In one possible design, the PCI is determined based on the identifier of the first PLMN, which may specifically be: the cell corresponding to the PCI is associated with the first device. Therefore, the first equipment can be accurately associated with the cell serving the remote terminal equipment, so that the first equipment can provide the side link relay service for the remote terminal equipment.

In a possible design, the specific method for receiving the first request message from the first device may be: receiving the first request message from the first device through a first type network interface, the first type network interface being an interface of the network device for communicating with a Distributed Unit (DU); the first request message further comprises indication information, and the indication information is used for indicating the first device to carry out lateral communication with the remote terminal device and is communicated with the network device through a network interface; or receiving the first request message from the first device through a second type network interface, where the second type network interface is used for communication between the first device and the network device, and the second type network interface is different from the first type network interface. The communication between the first device and the network device can be realized by multiplexing the common network interface or the new network interface through the method.

In one possible design, a second request message is sent to the first DU, where the second request message is used to indicate the identity of the first device and the identity of the first PLMN; receiving a second response message from the first DU, where the second response message is used to indicate information of a first cell, and a correspondence relationship exists between the first cell and an identifier of the first PLMN; the information of the first cell includes the PCI. This may be determined by the first DU as the cell with which the first device is associated.

In one possible design, the first DU is determined based on an identity of the first PLMN. This allows the first device to be accurately associated with the first DU, so that the cell associated with the first device is determined by the first DU.

In one possible design, a first DU and a first cell are determined according to the identity of the first PLMN, where the first cell belongs to the first DU; sending a third request message to the first DU, where the third request message is used to indicate an identifier of the first device and information of the first cell, and the information of the first cell includes the PCI and/or a cell identifier; receiving a third response message from the first DU, the third response message including acknowledgement information. This allows to accurately associate the first device with the cell serving the remote terminal device.

In one possible design, the third request message is further used to indicate an identity of the first PLMN. Thus, the first DU may accurately determine whether to accept the selection of the first cell in combination with the identity of the first PLMN.

In one possible design, first information is sent to the first device, where the first information includes an identifier of a Data Radio Bearer (DRB) and a quality of service corresponding to the DRB; receiving second information from the first device, wherein the second information comprises a sideline configuration, and the sideline configuration is used for communication between the far-end terminal device and the first device through a nearby service communication 5 interface; and sending a first configuration message to the remote terminal equipment through the first equipment, wherein the first configuration message comprises DRB configuration, the sidestream configuration and a cell radio network temporary identifier C-RNTI. This may be done to configure the remote terminal device so that subsequent remote terminal devices may access the network device through the first device.

In one possible design, the sidelink configuration includes a Radio Link Control (RLC) configuration, a medium access control (mac) configuration, and a physical layer configuration of the sidelink; the RLC configuration includes an identification of the DRB; wherein the RLC bearer corresponds to the DRB. This enables sideways communication between the first device and the remote terminal device.

In one possible design, the DRB configuration includes a Packet Data Convergence Protocol (PDCP) configuration, and the PDCP configuration includes an identifier of the DRB.

In one possible design, a fourth request message is sent to the first DU, where the fourth request message is used to request the first DU to allocate a cell radio network temporary identifier (C-RNTI); receiving a fourth response message from the first DU, the fourth response message being used for indicating the C-RNTI. So that the network device can obtain the C-RNTI that makes up the first configuration message.

In one possible design, the fourth request message includes indication information of the first device; the C-RNTI is allocated to the cell corresponding to the first device by the first DU, and the cell corresponding to the first device is determined by the first DU according to the indication information of the first device. This may enable the first device to associate with the corresponding cell.

In one possible design, the DRB configuration is generated. This allows to determine the DRB configuration constituting said first configuration message.

In one possible design, determining a sideline configuration for the remote terminal device to communicate with the first device through an adjacent service communication 5 interface; sending the sidestream configuration to the first device through a first network interface message, the first network interface message corresponding to the first device; or sending a first message to the first device, where the first message includes the sidelink configuration and information identifying the first device. Therefore, the first device can be accurately provided with the side-line configuration for side-line communication with the remote terminal device.

In one possible design, the first response message is further to indicate third information, the third information including at least one of: tracking codes, radio access network notification area codes or cell identities; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identification is used to identify a cell within the first PLMN. This enables mobility management of the terminal device.

In a second aspect, the present application provides a communication method, which may be applied to a first device, or a processor in the first device, or a chip system, or a functional module, etc. The method can comprise the following steps: sending a first request message to a network device, the first request message indicating an identity of at least one PLMN of the first device; the first equipment carries out sideline communication with the remote terminal equipment and communicates with the network equipment through a network interface; receiving a first response message from the network device, the first response message including a PCI, the PCI determined based on an identity of a first PLMN, the identity of the first PLMN being one or more of the identities of the at least one PLMN.

By the method, the communication between the first device and the network device can be realized, and the first device can be associated with a cell serving the remote terminal device, so that the first device and the remote terminal device perform the sidelink communication, and the first device and the network device communicate through the network interface, so that the sidelink relay service is provided for the remote terminal device.

In a possible design, the PCI is determined based on an identifier of the first PLMN, which may specifically be: the cell corresponding to the PCI is associated with the first device. Therefore, the first equipment can be accurately associated with the cell serving the remote terminal equipment, so that the first equipment can provide the side link relay service for the remote terminal equipment.

In one possible design, the specific method for sending the first request message to the network device may be: sending the first request message to the network device through a first network type interface, which is an interface for the network device to communicate with a DU; the first request message further comprises indication information, and the indication information is used for indicating the first device to carry out lateral communication with the remote terminal device and is communicated with the network device through a network interface; or sending the first request message to the network device through a second network type interface, where the second type network interface is used for communication between the first device and the network device, and the second type network interface is different from the first type network interface. The method can realize the communication between the first equipment and the network equipment by multiplexing the common network interface or the new network interface.

In one possible design, a second message is sent over an adjacent serving communication 5 interface, the second message including an identification of the first PLMN and the PCI. Therefore, the remote terminal equipment can select the first equipment to realize the connection between the first equipment and the remote terminal equipment.

In one possible design, first information is received from the network device, where the first information includes an identifier of a DRB and a quality of service corresponding to the DRB; sending second information to the network device, where the second information includes a sidestream configuration, where the sidestream configuration is used for the far-end terminal device to communicate with the first device through an adjacent service communication 5 interface; receiving a first configuration message from the network device, the first configuration message comprising a DRB configuration, the sidelink configuration, and a C-RNTI; and sending the first configuration message to the far-end terminal equipment. In this way, the configuration of the remote terminal device can be completed, so that the subsequent remote terminal device can access the network device through the first device.

In one possible design, the sideline configuration is determined according to the identity of the DRB and the quality of service corresponding to the DRB. In this way, the sidestream configuration can be accurately determined to enable sidestream communication between the first device and the remote terminal device.

In one possible design, the sidelink configuration includes an RLC configuration, a medium access control configuration, and a physical layer configuration of the sidelink; the RLC configuration includes an identification of the DRB; wherein the RLC bearer corresponds to the DRB. This enables a side-line communication between the first device and the remote terminal device.

In one possible design, the DRB configuration includes a PDCP configuration that includes an identification of the DRB.

In one possible design, the DRB is configured to be generated by a Centralized Unit (CU).

In one possible design, a sidelink configuration from the network device is received via a first network interface message, the sidelink configuration being used for a remote terminal device to communicate with the first device via a proximity service communication 5 interface; the first network interface message corresponds to the first device; or, receiving a first message from the network device, the first message including the sidelink configuration and information identifying the first device. Therefore, the sidestream configuration for sidestream communication with the remote terminal equipment can be accurately acquired from the network equipment.

In one possible design, the first response message is further to indicate third information, the third information including at least one of: a tracking code, radio access network notification area code or cell identification; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identifier is used to identify a cell within the first PLMN. This enables mobility management of the terminal device.

In one possible design, the second message further includes at least one of: a tracking code, radio access network notification area code or cell identification; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identification is used to identify a cell within the first PLMN. This enables mobility management of the terminal device.

In a third aspect, the present application further provides a communication apparatus, which may be a network device, and which has the function of implementing the first aspect or each possible design example of the first aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, the structure of the communication apparatus includes a transceiver unit and a processing unit, and these units may perform corresponding functions in the first aspect or each possible design example of the first aspect, which specifically refers to the detailed description in the method example, and is not described herein again.

In one possible design, the communication apparatus includes a communication interface and a processor, and optionally a memory, in its structure, the communication interface is used for receiving and sending messages, information or data, and for performing communication interaction with other devices in the communication system, and the processor is configured to support the communication apparatus to perform corresponding functions in the first aspect or each possible design example of the first aspect. The memory is coupled to the processor and holds the program instructions and data necessary for the communication device.

In a fourth aspect, the present application further provides a communication apparatus, which may be a first device, having functionality to implement the first aspect or each of the possible design examples of the first aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the structure of the communication device includes a transceiver unit and a processing unit, and these units may perform corresponding functions in the second aspect or each possible design example of the second aspect, specifically refer to the detailed description in the method example, and are not described herein again.

In one possible design, the communication apparatus includes a communication interface and a processor, and optionally a memory, in its structure, the communication interface is used for receiving and sending messages, information or data, and for performing communication interaction with other devices in the communication system, and the processor is configured to support the communication apparatus to perform the corresponding functions in the second aspect or each possible design example of the second aspect. The memory is coupled to the processor and holds the program instructions and data necessary for the communication device.

In a fifth aspect, an embodiment of the present application provides a communication system, which may include the above-mentioned remote terminal device first device and network device.

In a sixth aspect, embodiments of the present application provide a computer-readable storage medium storing program instructions, which when executed on a computer, cause the computer to perform the method described in the first aspect, the second aspect, and any possible design thereof. By way of example, computer readable storage media may be any available media that can be accessed by a computer. Take this as an example but not limiting: the computer-readable medium may include a non-transitory computer-readable medium, a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In a seventh aspect, embodiments of the present application provide a computer program product including computer program code or instructions, which when run on a computer, causes the computer to implement the method described in the first aspect or any one of the possible designs of the first aspect, or any one of the possible designs of the second aspect or the second aspect.

In an eighth aspect, the present application further provides a chip, including a processor, coupled with a memory, and configured to read and execute program instructions stored in the memory, so as to enable the chip to implement the method described in the first aspect or any one of the possible designs of the first aspect, or in the second aspect or any one of the possible designs of the second aspect.

For each of the third to eighth aspects and possible technical effects of each aspect, please refer to the description of the possible technical effects for each possible solution in the first or second aspect, and no repeated description is given here.

Drawings

Fig. 1 is a schematic architecture diagram of a communication system provided in the present application;

fig. 2 is a schematic diagram of direct communication between terminal devices through a PC5 interface according to the present application;

fig. 3 is a schematic diagram illustrating that a remote UE may establish a connection with a network device through a relay UE according to the present application;

fig. 4 is a schematic flow chart of a communication method provided in the present application;

fig. 5 is a schematic diagram of a control plane protocol stack between a remote terminal device and a network device according to the present application;

fig. 6 is a schematic diagram of a user plane protocol stack between a remote terminal device and a network device according to the present application;

fig. 7 is a schematic flow chart of another communication method provided in the present application;

fig. 8 is a schematic flow chart of another communication method provided in the present application;

fig. 9 is a schematic flowchart of a remote terminal device accessing a network device through a first device according to the present application;

fig. 10 is a schematic flowchart of another remote terminal device accessing a network device through a first device according to the present application;

fig. 11 is a schematic diagram of a protocol stack for transmitting messages configured in a sideline between a first device and a network device according to the present application;

fig. 12 is a schematic structural diagram of a communication device provided in the present application;

fig. 13 is a block diagram of a communication device according to the present application.

Detailed Description

The present application will be described in further detail below with reference to the accompanying drawings.

The embodiment of the application provides a communication method, a communication device and a communication system, which are used for realizing communication interaction between a network node supporting communication with a terminal device through a PC5 interface and the network device, so that the network node can provide sidelink relay service for the terminal device. The method and the device are based on the same technical concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

Hereinafter, some terms in the present application are explained to facilitate understanding by those skilled in the art.

In the description of the present application, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance, nor order.

In the description of the present application, "at least one" means one or more, and a plurality means two or more.

The embodiment of the application can be applied to a sidelink UE-to-Network relay scene. Fig. 1 is a schematic diagram illustrating an architecture of a possible communication system to which an embodiment of the present application is applicable, where the architecture of the communication system includes a network device, a first device, and a terminal device. Wherein:

the network device is a device with a wireless transceiving function or a chip that can be set in the network device, and the network device includes but is not limited to: a base station (gbb), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved NodeB or home Node B, HNB), a Base Band Unit (BBU), an Access Point (AP) in a wireless fidelity (Wi-Fi) system, a wireless relay Node, a wireless backhaul Node, a transmission point (TRP or transmission point, TP), and the like, and may also be a network Node constituting the gbb or the transmission point, such as a baseband unit (BBU).

In some deployments, the gNB may include a Centralized Unit (CU) and a Distributed Unit (DU). The gNB may also include a Radio Unit (RU). The CU implements part of the function of the gNB, and the DU implements part of the function of the gNB, for example, the CU implements Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) layers, and the DU implements Radio Link Control (RLC), medium Access Control (MAC) and Physical (PHY) layers. Since the information of the RRC layer finally becomes or is converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling or PHCP layer signaling, can also be considered to be transmitted by the DU or by the DU + RU. It will be understood that the network device may be a CU node, or a DU node, or a device comprising a CU node and a DU node. The CU may be divided into network devices in the access network RAN, or may be divided into network devices in the core network CN, which is not limited to this.

Illustratively, a plurality of DUs may share a CU. In the RAN sharing scenario, one DU may also connect multiple CUs. The CU and the DU can be connected through an F1 interface. One DU may manage one or more cells, each having a corresponding cell identity.

In some embodiments, CU and DU may be physically separated except for the case where the base station is composed of CU and DU, i.e. except for the case where CU and DU are deployed together. That is to say the CU and DU can be considered as separate two nodes. In this case, the network device may be a CU.

The terminal equipment may also be referred to as User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user device. In this embodiment of the present application, the terminal device is a remote (remote) terminal device and needs to be provided with a relay (relay) service. The terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart wearing device (smart glasses, smart watch, smart headset, etc.), a wireless terminal in smart home (smart home), etc., and may also be a chip or a chip module (or a chip system) that can be installed in the above devices, etc. The embodiments of the present application do not limit the application scenarios. In the present application, a terminal device having a wireless transceiving function and a chip that can be installed in the terminal device are collectively referred to as a terminal device. The terminal equipment can communicate with the first equipment through a PC5 interface, and establishes connection with the network equipment through the first equipment to carry out data communication.

The first device is a network node which performs Sidelink (SL) communication with a remote terminal device and communicates with the network device through a network interface. The first device performs a sidelink (link) communication with the remote terminal device, which may be a PC5 interface communication between the first device and the remote terminal device. The first device can provide sidelink relay service (sidelink relay) for the remote terminal device. The first device can realize the data communication between the far-end terminal device and the network device, and can provide relay service for the far-end terminal device. For example, the first device may be, but is not limited to, an RSU or a DU or the like that supports communication with the terminal device via the PC 5.

The network interface according to the present application is an interface between a network device and a network device, for example, an F1 interface between a CU and a DU, an NG interface between a base station and a base station Xn, or between a base station and a core network device.

Currently, in a wireless communication system, data communication between terminal devices may be performed through a network, or communication between terminal devices may be directly performed without using a network device. The interface between the terminal device and the terminal device is called as a PC5 interface, and the Uu interface between the terminal device and the network device. As shown in fig. 2, a link between a terminal device and the terminal device is called a sidelink (sidelink), and a typical application scenario of sidelink communication is a vehicle-to-electrical (V2X) service (hereinafter referred to as a car networking). In the car networking, each car is a UE, and data transmission can be directly performed between the UEs through sidelink without passing through the network, so that communication delay can be effectively reduced.

Wherein, the Sidelink supports broadcasting, unicasting and multicasting. The sildelink broadcast communication is similar to a network device broadcasting system information. The sildelink unicast communication is similar to data communication performed after RRC connection is established between a terminal device and a network device, and requires a unicast connection to be previously established between two terminal devices. In unicast communication, in contrast to broadcasting, unicast communication can only be performed between two terminal devices that have established a unicast connection. The Sidelink multicast communication refers to communication between all terminal devices in a communication group, and the terminal devices in the group can receive and transmit data of the multicast service.

In the current UE-to-network relay scenario, as shown in fig. 3, a node performing a relay function in the middle is a UE type, that is, a relay UE. The relay UE is connected with the remote UE through a PC5 interface, the relay UE is connected with the network equipment through a Uu interface, and the remote UE can establish connection with the network equipment through the relay UE to perform data transmission.

At present, a Road Side Unit (RSU) (also called a roadside unit) in an internet of vehicles system is responsible for receiving real-time traffic information such as road condition information sent by traffic lights and application servers, and dynamically broadcasting the real-time traffic information to related vehicles, so as to avoid or reduce traffic accidents. The communication between the vehicle and the RSU employs PC5 or sidelink technology. The RSU can be accessed to the broadband directly through a wired mode and the like. In the above process, the UE establishes connection with the RSU only for V2X communication, and does not access the network through the RSU, which may cause waste of network resources. In order to avoid the waste of network resources and solve the problem of difficult network deployment, it is considered that the RSU can be reused to provide network access service for the terminal device, so that the RSU acts as a network node to act as a relay node.

However, the existing sidelink relay device is of a terminal device type, and communicates with the network device through the Uu interface, so the existing communication mechanism based on the Uu interface cannot be multiplexed to the communication mechanism based on the network interface, that is, the transmission mechanism in the scenario shown in fig. 3 cannot be directly applied to the scenario shown in fig. 1.

Based on this, an embodiment of the present application provides a communication method, so as to implement that a network node supporting communication with a terminal device through a PC5 interface interacts with a network device through network interface communication, so that the network node can provide a sidelink relay service for the terminal device. In the communication method provided by the embodiment of the present application, when the network node provides the sidelink relay service for the terminal device, the network node may be compatible with the remote terminal device in the current L2 relay, so that the flow of the remote terminal device is not changed.

It should be noted that, in the embodiment of the present application, what can implement the relay function may be the first device, or a processor in the first device, or a chip system, or a functional module, etc.; the network access service may be provided by a network device, or a processor in the network device, or a chip system, or a functional module, etc. In the following embodiments, the communication method provided in the present application is described in detail by taking only the first device and the network device as examples, but the present application is not limited thereto.

Based on the above description, the communication method provided in the embodiment of the present application is applicable to the communication system shown in fig. 1. Referring to fig. 4, a specific process of the method may include:

step 401: a first device sends a first request message to a network device, where the first request message is used to indicate an identity of at least one Public Land Mobile Network (PLMN) of the first device; the first device communicates with a remote terminal device in a sidestream mode and communicates with the network device through a network interface.

The first device serves as a network node, and a network interface needs to be established between the first device and the network node. In this embodiment of the present application, the first device provides an L2 sidelink relay service for a far-end terminal device, and a PDCP of the far-end terminal device is terminated on a network device behind the first device. Illustratively, a control plane protocol stack and a user plane protocol stack between the remote terminal device and the network device may be as shown in fig. 5 and fig. 6, respectively. The control plane protocol and the user plane protocol both use transmission protocols commonly used in current network nodes, such as Stream Control Transmission Protocol (SCTP) and user plane General Packet Radio Service (GPRS) tunneling protocol-user, GTP-U).

In an alternative embodiment, the network interface for communication between the first device and the network device may multiplex the current interface or introduce a new interface for communication between the first device and the network device. Illustratively, when the first device sends the first request message to the network device, the first request message may be specifically, but not limited to, implemented by the following two methods:

method a1: the first device sends the first request message to the network device through a first network type interface, wherein the first network type interface is an interface for the network device to communicate with the DU; the first request message further includes indication information, where the indication information is used to indicate that the first device performs lateral communication with the remote terminal device, and communicates with the network device through a network interface.

In the method a1, the first type network interface is a multiplexed interface through which the current network device communicates with the DU. For example, the first type network interface may be an F1 interface or other interfaces, which are not limited in this application.

In the method a1, since the first type network interface is a multiplexed interface between the current network device and the DU, in order to distinguish from the current DU (a DU that does not support communication with a terminal device via a PC5 interface), the indication information may be carried in the first request message, so that the network device knows that the first device is not a DU that does not support communication with a terminal device via a PC5 interface.

Method a2: the first device sends the first request message to the network device through a second network type interface, the second type network interface is used for communication between the first device and the network device, and the second type network interface is different from the first type network interface.

Exemplarily, in the method a2, the second network type interface may be a new interface introduced for implementing communication between the first device and the network device. In this method a2, the network device may communicate with the DU through a first type network interface and with the first device through a second type network interface.

In an optional implementation manner, the first request message is used to indicate an identity (PLMN ID) of at least one PLMN of the first device, and may be implemented by including, in the first request message, the identity of the at least one PLMN of the first device, or may also be implemented by including, in the first request message, information indicating the identity of the at least one PLMN of the first device, which may of course be implemented in other manners, and this is not limited in this application.

Illustratively, the identity of the at least one PLMN may be used to indicate the at least one PLMN to which the first device belongs. Here, the first device may be deployed by an operator, and thus the first device may indicate, through the identifier of the PLMN, information about an operator to which the first device belongs.

Step 402: the network device sends a first response message to the first device, where the first response message is used to indicate a Physical Cell Identity (PCI), the PCI is determined based on an identity of a first PLMN, and the identity of the first PLMN is one or more of the identities of the at least one PLMN.

In an optional implementation manner, the first response message is used to indicate the PCI, and may be implemented by including the PCI in the first response message, or may also be implemented by including information indicating the PCI in the first response message, and of course, may also be implemented by other ways, which is not limited in this application.

Illustratively, the PCI is one when the identity of the first PLMN is one of the identities of the at least one PLMN; when the identifier of the first PLMN is a plurality of identifiers of the at least one PLMN, the PCIs may include PCIs corresponding to the identifiers of the plurality of PLMNs, that is, the PCIs may be a plurality of PCIs; when the identifier of the first PLMN is a plurality of identifiers of the at least one PLMN, the PCI may also be one of PCIs corresponding to the identifiers of the plurality of PLMNs, that is, the PCI is one of the plurality of PCIs. It should be understood that when the identifier of the first PLMN is a plurality of identifiers of the at least one PLMN, the identifier may be a part or all of the identifiers of the at least one PLMN, and the application is not limited thereto.

Specifically, a network device may manage multiple cells, each cell having a PCI. In this embodiment, at least one cell needs to be associated when the first device needs to be able to work normally, because the remote terminal device needs to rely on the PCI to derive a key required for data communication after accessing the network through the first device, so as to complete encryption. Therefore, after receiving the first request message of the first device, the network device associates at least one cell with the first device, and notifies the PCI of the cell to the first device. Specifically, the associating, by the network device, at least one cell for the first device may specifically be: the network device selects at least one cell from a plurality of cells managed by the network device, and associates the selected at least one cell with the first device. It should be noted that, the above process of associating, by the network device, at least one cell for the first device may be an internal logic implementation of the network device.

In an optional embodiment, the PCI is determined based on an identifier of a first PLMN, and may be understood that the PCI is associated with the first PLMN, or a cell corresponding to the PCI is associated with the first device, or the PCI is associated with the first device.

In a specific embodiment, the specific method for determining, by the PCI based on the identifier of the first PLMN may be: the network device determines cells belonging to the first PLMN from cells managed by the network device, then judges the load condition of the determined cells or the condition of association with other first devices, selects cells with lower load or less association with other first devices from the cells based on the judgment result, and further determines the PCI of the selected cells, namely the PCI determined based on the identifier of the first PLMN. It should be noted that the implementation process of the network device determining the PCI based on the identifier of the first PLMN may be an internal logic implementation of the network device.

In an optional embodiment, the first response message may further be used to indicate third information, and the third information may include at least one of the following: a Tracking Area Code (TAC), a radio access network notification area code (RNAC), or a cell identity (cell identity); wherein the tracking code and the radio access network notification area code correspond to the PCI and the cell identification may be used to identify a cell within the first PLMN.

Optionally, the first response message may also be used to indicate third information, which may be implemented by the first response message including the third information, or may be implemented by the first response message including information indicating the third information, which may of course be implemented in other manners, and this is not limited in this application.

For example, when the identifier of the first PLMN is one, the cell identifier is one, and may be used to uniquely identify one cell in the one PLMN; and when the first PLNM has a plurality of identifiers, the cell identifiers are a plurality of identifiers, and each cell identifier is used for uniquely identifying one cell in the corresponding PLMN.

Illustratively, the tracking code and the radio access network notification area code may be information for terminal device mobility management. Optionally, the first device may support an IDLE terminal device (RRC _ IDLE) or an INACTIVE terminal device (RRC _ INACTIVE UE), and at this time, the first response message may be used to indicate information used for terminal device mobility management in the third information, that is, may indicate the tracking code and the radio access network notification area code.

Specifically, in order to support a remote terminal device to access the network device through the first device, the first device needs to provide necessary cell-related information for the remote terminal device. Since the first device does not provide a Uu interface, in this embodiment of the present application, the first device needs to acquire the cell-related information by using the network device, for example, the cell-related information may be acquired in the foregoing steps 401 and 402, and of course, the cell-related information may also be acquired in other manners.

In an embodiment, the processes of steps 401 and 402 may be implemented in an interface establishment process between the first device and the network device, or implemented in other flows, which is not limited in this embodiment of the present application. Optionally, in the interface establishment procedure between the first device and the network device, the first request message may be an interface establishment request message, and the first response message may be an interface establishment response message.

In an optional implementation manner, after the step 402, the first device may further perform a step 403: the first device sends a second message through a PC5 interface, where the second message may include the identity of the first PLMN and the PCI.

Optionally, the second message may further include at least one of: the tracking code, the radio access network notification area code, or the cell identification.

For example, when the first device sends the second message through the PC5 interface, the first device may send the second message in a broadcast manner on the PC5 interface, or send the second message in a unicast manner or a multicast manner to the remote terminal device, so as to assist the remote terminal device in selecting a suitable first device.

In an optional implementation manner, when there are multiple PCIs, the first device may determine one PCI as a cell for providing a service to a remote terminal device, and at this time, the first device may carry the determined one PCI in the second message.

In another optional implementation manner, when the number of PCIs is multiple and the first device carries all the PCIs in the second message, the remote terminal device may select one PCI from the PCIs as a cell to be accessed after receiving the second message.

In yet another optional implementation manner, when the number of PCIs is multiple, the first device generates one piece of the second message for each PCI, where each PCI is carried in a corresponding second message, that is, one PCI corresponds to one piece of the second message. And each second message corresponds to a different L2 ID. The remote terminal device may establish a connection with the first device using the L2 ID corresponding to the second message after receiving the second message.

In an alternative embodiment, the network device may be a base station, or the network device may be a CU. Optionally, when the network device is a base station and the base station is a distributed base station, the distributed base station may be composed of a CU and a DU.

Illustratively, when the network device is a CU, or when the network device is a distributed base station, the implementation of steps 401 and 402 may be implemented by the first device and the CU, as shown in fig. 7 or fig. 8.

When the above-described step 401 and step 402 are implemented by a CU, a flow as shown in fig. 7 or fig. 8 may also exist between the step 401 and step 402. Specifically, the method comprises the following steps:

in one example, as shown in fig. 7, a specific flow may include the following steps:

step 701: and the CU sends a second request message to the first DU, wherein the second request message is used for indicating the identification of the first device and the identification of the first PLMN.

Wherein the identity of the first device is used to uniquely identify the first device on an interface between the CU and the first DU. It may also be understood that the identity of the first device is an identity assigned by the CU to the first device for the interface between the CU and the first DU. In this application, the identity of the first device may also be referred to as the first identity of the first device.

In an optional implementation manner, the second request message is used to indicate the identity of the first device and the identity of the first PLMN, and may be implemented by the second request message including the identity of the first device and the identity of the first PLMN, and may further be implemented by the second request message including information indicating the identity of the first device and the identity of the first PLMN. Of course, the method can also be realized by other modes, and the method is not limited in the application.

In an alternative embodiment, the first DU may be a DU associated with the first device. Illustratively, before step 701, the CU may further perform step 700: and the CU determines the first DU according to the identifier of the first PLMN. Optionally, the step 700 may also be implemented by the CU internal logic.

Step 702: the CU receives a second response message from the first DU, wherein the second response message is used for indicating information of a first cell, and the first cell has a corresponding relation with the identifier of the first PLMN; the information of the first cell includes the PCI.

Optionally, the second response message may further include a second identifier of the first device, and the second identifier of the first device and the first identifier of the first device are used together to uniquely identify the first device on the interface between the CU and the first DU. Wherein, the first identifier of the first device is the identifier of the first device involved above. It can also be understood that the second identity of the first device is an identity that is allocated by the first DU to the first device and used for an interface between the CU and the first DU.

In an alternative embodiment, the second response message may further be used to indicate at least one of a tracking code, a radio access network notification area code, or a cell identification.

For example, when the second response message may also be used to indicate the tracking code or the radio access network notification area code, the first response message in step 402 above may also be used to indicate the tracking code or the radio access network notification area code. When the second response message does not indicate the tracking code or the radio access network notification area code, the CU determines the tracking code or the radio access network notification area code after receiving the PCI and indicates to the first device through the first response message in step 402.

In an alternative embodiment, the first cell may be determined by the first DU according to an identity of the first device and an identity of the first PLMN. It may also be understood that the first DU associates with the first cell for the first device. Optionally, before step 702, the first DU may perform step 702a: and the first DU determines the first cell according to the identifier of the first device and the identifier of the first PLMN. Optionally, the step 702a may be implementation logic inside the first DU.

In the above example, the CU selects the first DU, and selects a cell from the first DU.

In another example, it may be a procedure for a CU to select a first DU and a cell under the first DU. As shown in fig. 8, a specific process may include the following steps:

step 801: and the CU determines a first DU and a first cell according to the identification of the first PLMN, wherein the first cell belongs to the first DU.

Since an F1 interface is currently established between the CU and the at least one DU, and during the F1 interface establishment process, the CU knows which cells are included under the at least one DU, the CU can further determine the first cell after determining the first DU.

Step 802: the CU sends a third request message to the first DU, wherein the third request message is used for indicating the identification of the first device and the information of the first cell, and the information of the first cell comprises the PCI and/or the cell identification.

In an optional embodiment, the third request message is further used to indicate an identity of the first PLMN.

It should be noted that the third request message is used to indicate the identifier of the first device and the information of the first cell, or is also used to indicate the identifier of the first PLMN, and may be implemented by including the above information, or may be implemented by including the information indicating the above information, which is not limited in this application.

Step 803: the CU receives a third response message from the first DU, the third response message including acknowledgement information.

Specifically, when the third response message includes the confirmation information, it indicates that the first DU accepts the first cell determined by the CU.

In an optional implementation manner, the first DU may reject the CU, and at this time, the third response message may include rejection information.

By the communication method, the communication between the first device and the network device can be realized, the first device can be associated with a cell serving the remote terminal device, so that the first device and the remote terminal device perform side-line communication, and the first device and the network device communicate through a network interface, so that a side-line link relay service is provided for the remote terminal device.

The initialization of the first device is completed by the above-described fig. 4, fig. 7 or fig. 8. Of course, the above initialization process is only an example, and other initialization methods are also possible, and the present application does not limit this.

In one possible embodiment, the remote terminal device may access the network device through the first device after the first device completes initialization. Optionally, the process that the remote terminal device accesses the network device through the first device may be a process that the remote terminal device enters a connected state from an idle state, or may be a process that the remote terminal device enters a connected state from an inactive state, or may also be a process that the remote terminal device performs reestablishment through the first device, or may also be another process, which is not limited in this application.

Exemplarily, fig. 9 shows a schematic flowchart of a process in which a remote terminal device accesses a network device through a first device, which may specifically include:

step 901: the network device sends first information to the first device, where the first information includes an identifier of a Data Radio Bearer (DRB) and quality of service (QoS) corresponding to the DRB.

Illustratively, the DRB is a Uu DRB established between a remote terminal device and the network device, data of the DRB needs to be relayed between the remote terminal device and the network device through the first device, and the identity of the DRB and the QoS of the DRB are for the first device to determine a sidestream configuration, so as to implement sidestream transmission between the first device and the remote terminal device.

In an optional implementation manner, the network device determines the QoS corresponding to the DRB, and the specific method may be: the network device determines the QoS of the DRB based on the QoS of the QoS flow having a mapping relation with the DRB. Illustratively, at least one QoS flow has a mapping relationship with the DRB. If the at least one QoS flow is a QoS flow, the network device may use the QoS of the QoS flow as the QoS corresponding to the DRB; if the at least one QoS flow is a plurality of QoS flows, the network device may use the QoS of the QoS flow with the highest priority among the QoS flows as the QoS corresponding to the DRB, or may extract the parameter with the highest QoS requirement from the QoS parameters of different QoS flows to form the QoS corresponding to the DRB. Wherein the QoS requirements are highest with different understanding for different QoS parameters, e.g., for delay parameters, the QoS requirements are highest with shortest delay; for a rate parameter, the QoS requirement is highest, i.e., rate is highest; for reliability parameters, the QoS requirement is highest, i.e. the reliability requirement is highest; for the priority parameter, the QoS requirement is highest, i.e. the priority is highest.

Optionally, the first information may further include other information, which is not listed here.

Optionally, in a process that the remote terminal device enters a connected state from an idle state, the first information may be sent through a configuration request message sent by the network device to the first device.

Step 902: the first device sends second information to the network device, where the second information includes sideline configuration (sidelink configuration) used for the remote terminal device to communicate with the first device through a PC 5-based interface.

The sidestream configuration comprises a sidestream RLC configuration, a Media Access Control (MAC) configuration and a physical layer configuration; the sidelink RLC configuration includes an identification of the Uu DRB; wherein, the sidelink RLC bearer corresponds to the Uu DRB, that is, the sidelink RLC bearer has a mapping relationship with the Uu DRB.

Optionally, in a flow in which the remote terminal device enters the connected state from the idle state, the second information may be sent by a response message, which is sent by the first device to the network device and responds to the configuration request message.

In an alternative embodiment, the side-row configuration is generated by the first device for the remote device. Illustratively, before step 902, the first device may further perform step 902a: and the first equipment determines the sidestream configuration according to the identification of the DRB and the service quality corresponding to the DRB.

Step 903: the network device sends a first configuration message to the remote terminal device through the first device, where the first configuration message includes a DRB configuration, the sidelink configuration, and a cell radio network temporary identifier (C-RNTI).

The DRB configuration includes a PDCP configuration (i.e., a Uu PDCP configuration) including an identification of the DRB.

Illustratively, the network device generates the DRB configuration before step 903.

Optionally, the first configuration message may be an RRC reconfiguration message.

In an alternative embodiment, after step 903, the remote terminal device may perform step 904: and the remote terminal equipment sends a completion message to the network equipment through the first equipment.

Optionally, the complete message may be an RRC reconfiguration complete message.

Optionally, after receiving the completion message of the remote terminal device, the network device may further perform step 905: and the network equipment sends a completion instruction to the first equipment, and the completion instruction is used for indicating that the configuration of the remote terminal equipment is completed.

Illustratively, the protocol stack in the interaction between the remote terminal device and the network device through the first device in step 904 and step 905 may also use the protocol stack shown in fig. 5.

In an optional implementation manner, before step 901, the remote terminal device may further perform step 900: and the far-end terminal equipment sends a third message to the network equipment through the first equipment, wherein the third message is used for indicating that the far-end terminal equipment and the network equipment are connected.

Illustratively, the third message may be message 5 (msg 5), i.e. an RRC setup complete message, for confirming successful completion of an RRC setup connection.

Also, the network device may be a base station, or the network device may be a CU. Optionally, when the network device is a base station and the base station is a distributed base station, the distributed base station may be composed of a CU and a DU. For example, when the network device is a CU or when the network device is a distributed base station, the operations performed by the network device in fig. 9 may be implemented by a CU, as shown in fig. 10.

When the operations performed by the network device in fig. 9 are all performed by the CU, as shown in fig. 10, before step 901, the CU may further perform the following steps:

step 1001: and the CU sends a fourth request message to the first DU, wherein the fourth request message is used for requesting the first DU to allocate the C-RNTI.

Optionally, the fourth request message may include indication information of the first device; the indication information of the first device may be used to determine a cell associated with the first device.

Optionally, the indication information of the first device may be an identifier of the first device.

Step 1002: the CU receives a fourth response message from the first DU, the fourth response message indicating the C-RNTI.

For example, the C-RNTI is allocated by the first DU to the cell corresponding to the first device, and the cell corresponding to the first device is determined by the first DU according to the indication information of the first device.

Specifically, the network device generates the DRB configuration, and here, the CU generates the DRB configuration. For example, the CU may determine the first configuration message based on the DRB configuration determined by the CU itself, the C-RNTI determined by the DU, and the sidelink configuration determined by the first device, as shown in step 1003 in fig. 10.

In an optional implementation, when a CU receives the completion indication from the remote terminal device, the CU may also send the completion indication to the first DU, as shown in 1004 in fig. 10.

Through the processes shown in fig. 9 and fig. 10, the network device may complete configuration for the remote terminal device, so as to ensure that the remote terminal device completes communication with the network device through the first device.

It should be noted that the above-mentioned flows shown in fig. 9 and fig. 10 may be executed based on that the first device has been associated with a cell in advance. For example, the method of associating cells for the first device may be, but is not limited to, the manner as shown in fig. 4, fig. 7, or fig. 8. Of course, the flows shown in fig. 9 and fig. 10 may not depend on the first device having associated a cell, and in this case, when implemented, the first possible manner is: after receiving the third message of the remote terminal equipment, the CU selects a DU for the remote terminal equipment, and the selected DU is a first equipment associated cell; a second possibility is that a cell is selected by a CU and the selected DU is informed. It should be noted that, in a first possible manner, in the above step 1002, the fourth response message may further indicate cell information, such as a PCI, etc.; in a second possible manner, in step 1001, the fourth request message may further indicate cell information, such as a PCI or a cell identifier. Adaptively, the cell information may be further included in the first configuration message.

In the flow shown in fig. 9 or fig. 10, the first device may determine the sidestream configuration by itself. In one possible embodiment, the first device needs to rely on the network device to provide a side-row configuration to enable communication with the remote terminal device. In this case, it is necessary to transmit the sidestream configuration between the first device and the network device based on the network interface.

Illustratively, the network device determines a side-row configuration, where the side-row configuration is used for the remote terminal device to communicate with the first device through a PC5 interface; the network device sends the sidestream configuration to the first device through a first network interface message, wherein the first network interface message corresponds to the first device; or, the network device sends a first message to the first device, where the first message includes the sidelink configuration and information identifying the first device, and optionally, the information identifying the first device identifies the first device on an interface.

In an alternative embodiment, a protocol stack for transmitting messages of the sidelink configuration between the first device and the network device may be as shown in fig. 11. The interaction of the control plane signaling is performed between the first device and the network device based on SCTP, where the Uu PDCP layer is optional, that is, when a message configured for a sidelink is transmitted between the first device and the network device, the PDCP layer may not be processed.

In an alternative implementation, the message for transmitting sideline configuration may be an RRC configuration message. The same protocol stack is adopted when the first device and the network device interact RRC configuration messages for the remote terminal device. Therefore, it is necessary to distinguish on the interface whether the RRC configuration message is of the first device or is accessed by the first device to the remote terminal device of the network device. Therefore, one way is to introduce different interface messages on the network interface to carry the RRC configuration message of the first device and the RRC configuration message of the remote terminal device, for example, the RRC configuration message may be carried by the first network interface message corresponding to the first device. Another way is to use the same interface message, but introduce a default identifier for the first device in the message sent to the first device, for example, the default identifier may be sent to the first device through the same first message, where the first message includes information identifying the first device. Therefore, the sidestream configuration determined by the network equipment can be accurately sent to the first equipment, so that the first equipment realizes sidestream communication with the remote terminal equipment.

In a possible implementation manner, the first device in the foregoing embodiment may be replaced with the first device when the first device is an RSU, and in another possible implementation manner, the first device may also be a DU that supports communication with the UE based on a PC5 interface, where the DU internal association cell serves as a serving cell for sidelink relay association.

Based on the above embodiments, the present application further provides a communication apparatus, and referring to fig. 12, the communication apparatus 1200 may include a transceiving unit 1201 and a processing unit 1202. The transceiver 1201 is configured to receive information (message or data) or transmit information (message or data) to the communication apparatus 1200, and the processing unit 1202 is configured to control and manage actions of the communication apparatus 1200. The processing unit 1202 may also control the steps performed by the transceiving unit 1201.

The communication apparatus 1200 may specifically be the first device in the above embodiments, a processor in the first device, or a chip system, or a functional module; alternatively, the communication apparatus 1200 may specifically be the network device in the foregoing embodiments, a processor, a chip, a system of chips, or a functional module of the network device.

In an embodiment, when the communication apparatus 1200 is used to implement the functions of the network device (e.g., CU) in any one of the embodiments described in fig. 4 and fig. 7 to fig. 10, specifically, the method may include:

the transceiving unit 1201 is configured to receive a first request message from a first device, and send a first response message to the first device; the processing unit 1202 is configured to control the transceiving unit 1201 to perform the above operations; wherein the first request message is for indicating an identity of at least one PLMN of the first device; the first equipment carries out lateral communication with the remote terminal equipment and communicates with the network equipment through a network interface; the first response message is used to indicate PCIs, which are determined based on identities of first PLMNs, the identities of the first PLMNs being one or more of the identities of the at least one PLMN.

For example, the PCI is determined based on the identifier of the first PLMN, and specifically may be: the cell corresponding to the PCI is associated with the first device.

In an optional implementation manner, when receiving the first request message from the first device, the transceiving unit 1201 may specifically be configured to: receiving said first request message from said first device through a first type network interface, said first type network interface being an interface for said network device to communicate with a distribution unit, DU; the first request message further comprises indication information, and the indication information is used for indicating the first device to carry out lateral communication with the remote terminal device and is communicated with the network device through a network interface; or receiving the first request message from the first device through a second type network interface, where the second type network interface is used for communication between the first device and the network device, and the second type network interface is different from the first type network interface.

In an optional implementation manner, the transceiving unit 1201 may be further configured to: sending a second request message to the first DU, wherein the second request message is used for indicating the identification of the first device and the identification of the first PLMN; receiving a second response message from the first DU, where the second response message is used to indicate information of a first cell, and the first cell has a correspondence with an identifier of the first PLMN; the information of the first cell includes the PCI.

For example, the processing unit 1202 may be further configured to determine the first DU according to an identity of the first PLMN.

In another optional embodiment, the processing unit 1202 is further configured to determine a first DU and a first cell according to the identifier of the first PLMN, where the first cell belongs to the first DU; the transceiving unit 1201 may be further configured to: sending a third request message to the first DU, where the third request message is used to indicate an identifier of the first device and information of the first cell, and the information of the first cell includes the PCI and/or a cell identifier; and receiving a third response message from the first DU, the third response message including acknowledgement information.

Illustratively, the third request message may also be used to indicate an identity of the first PLMN.

In an exemplary embodiment, the transceiving unit 1201 may be further configured to: sending first information to the first device, where the first information includes an identifier of a Data Radio Bearer (DRB) and a quality of service corresponding to the DRB; receiving second information from the first device, wherein the second information comprises a sideline configuration, and the sideline configuration is used for communication between the far-end terminal device and the first device through a nearby service communication 5 interface; and sending a first configuration message to the remote terminal equipment through the first equipment, wherein the first configuration message comprises DRB configuration, the sideline configuration and C-RNTI.

Illustratively, the sidelink configuration may include an RLC configuration, a medium access control configuration, and a physical layer configuration of the sidelink; the RLC configuration includes an identification of the DRB; wherein the RLC bearer corresponds to the DRB.

Illustratively, the DRB configuration may comprise a PDCP configuration, which may comprise an identification of the DRB.

In an optional implementation manner, the transceiving unit 1201 may be further configured to: sending a fourth request message to a first Distribution Unit (DU), wherein the fourth request message is used for requesting the first DU to allocate a C-RNTI; and receiving a fourth response message from the first DU, the fourth response message being used to indicate the C-RNTI.

Illustratively, the fourth request message may include indication information of the first device; the C-RNTI is allocated to the cell corresponding to the first device by the first DU, and the cell corresponding to the first device is determined by the first DU according to the indication information of the first device.

Optionally, the processing unit 1202 may be further configured to generate the DRB configuration.

In an optional implementation, the processing unit 1202 may be further configured to determine a side configuration, where the side configuration is used for the far-end terminal device to communicate with the first device through a nearby service communication 5 interface; the transceiving unit 1201 may be further configured to: sending the sidestream configuration to the first device through a first network interface message, the first network interface message corresponding to the first device; or sending a first message to the first device, where the first message includes the sidelink configuration and information identifying the first device.

Illustratively, the first response message may be further configured to indicate third information, the third information including at least one of: a tracking code, radio access network notification area code or cell identification; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identifier is used to identify a cell within the first PLMN.

In another embodiment, when the communication apparatus 1200 is used to implement the function of the first device in any one of the embodiments described in fig. 4 and fig. 7 to fig. 10, specifically, the method may include:

the transceiving unit 1201 is configured to send a first request message to a network device, and receive a first response message from the network device; the processing unit 1202 is configured to control the transceiving unit 1201 to perform the above operations; wherein the first request message is for indicating an identity of at least one PLMN of the first device; the first equipment carries out sideline communication with the remote terminal equipment and communicates with the network equipment through a network interface; the first response message includes PCIs determined based on an identity of a first PLMN, the identity of the first PLMN being one or more of the identities of the at least one PLMN.

For example, the PCI is determined based on the identifier of the first PLMN, which may specifically be: the cell corresponding to the PCI is associated with the first device.

In an optional implementation manner, when the transceiving unit 1201 sends the first request message to the network device, the transceiving unit may specifically be configured to: sending the first request message to the network device through a first network type interface, where the first network type interface is an interface for the network device to communicate with a Distribution Unit (DU); the first request message further comprises indication information, and the indication information is used for indicating the first device to carry out collateral communication with the remote terminal device and is communicated with the network device through a network interface; or sending the first request message to the network device through a second network type interface, where the second type network interface is used for communication between the first device and the network device, and the second type network interface is different from the first type network interface.

In an example, the transceiving unit 1201 may be further configured to send a second message through an adjacent service communication 5 interface, where the second message includes the identity of the first PLMN and the PCI.

Optionally, the transceiver 1201 may be further configured to: receiving first information from the network equipment, wherein the first information comprises an identifier of a DRB and service quality corresponding to the DRB; sending second information to the network device, where the second information includes a sidestream configuration, where the sidestream configuration is used for the far-end terminal device to communicate with the first device through a neighboring service communication 5 interface; and receiving a first configuration message from the network equipment, wherein the first configuration message comprises DRB configuration, the sidelink configuration and a cell radio network temporary identity C-RNTI; and sending the first configuration message to the remote terminal equipment.

In an optional embodiment, the processing unit 1202 may be further configured to determine the sidestream configuration according to the identifier of the DRB and the service quality corresponding to the DRB.

Illustratively, the sidestream configuration may include RLC, MAC, and physical layer configurations of the sidestream; the RLC configuration includes an identification of the DRB; wherein the RLC bearer corresponds to the DRB.

Optionally, the DRB configuration may be generated for the CU.

In an exemplary embodiment, the transceiving unit 1201 may be further configured to: receiving a sidestream configuration from the network device through a first network interface message, wherein the sidestream configuration is used for a far-end terminal device and the first device to communicate through an adjacent service communication 5 interface; the first network interface message corresponds to the first device; or, receiving a first message from the network device, the first message including the sidelink configuration and information identifying the first device.

Illustratively, the first response message may be further configured to indicate third information, the third information including at least one of: a tracking code, radio access network notification area code or cell identification; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identification is used to identify a cell within the first PLMN.

Optionally, the second message may further include at least one of: tracking codes, radio access network notification area codes or cell identities; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identifier is used to identify a cell within the first PLMN.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. Each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, which are essential or contributing to the prior art, or all or part of the technical solutions may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a portable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

Based on the above embodiments, the present application further provides a communication device, and referring to fig. 13, a communication device 1300 may include a communication interface 1301 and a processor 1302. Optionally, the communication device 1300 may further include a memory 1303. The memory 1303 may be disposed inside the communication device 1300, or may be disposed outside the communication device 1300. The processor 1302 may control the communication interface 1301 to receive and transmit messages, information or data and the like.

Specifically, the processor 1302 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. The processor 1302 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

The communication interface 1301, the processor 1302 and the memory 1303 are connected to each other. Optionally, the communication interface 1301, the processor 1302, and the memory 1303 are connected to each other through a bus 1304; the bus 1304 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 13, but this is not intended to represent only one bus or type of bus.

In an alternative embodiment, the memory 1303 is used for storing programs and the like. In particular, the program may include program code comprising computer operating instructions. The memory 1303 may include RAM, and may also include non-volatile memory (non-volatile memory), such as one or more disk memories. The processor 1302 executes the application program stored in the memory 1303, so as to implement the above functions, thereby implementing the functions of the communication apparatus 1300.

Exemplarily, the communication apparatus 1300 may be the first device in the above embodiments; but also the network device in the above embodiment.

In one embodiment, when the communications apparatus 1300 implements the functions of the first device in the embodiment shown in any one of fig. 4 and fig. 7 to fig. 10, the communication interface 1301 may implement the transceiving operations performed by the first device in the embodiment shown in any one of fig. 4 and fig. 7 to fig. 10; the processor 1302 may perform operations other than transceiving operations performed by the first device in any of the embodiments illustrated in fig. 4, 7-10. The detailed description may refer to the description of any one of the embodiments shown in fig. 4, fig. 7 to fig. 10, and will not be described in detail here.

In another embodiment, when the communication apparatus 1300 implements the functions of the network device (e.g., CU) in any of the embodiments shown in fig. 4 and fig. 7-10, the communication interface 1301 may implement the transceiving operations performed by the network device (or CU) in any of the embodiments shown in fig. 4 and fig. 7-10; processor 1302 may perform operations other than transceiving operations performed by a network device (or CU) in any of the illustrated embodiments of FIGS. 4, 7-10. The specific related detailed description may refer to the related description in any one of the embodiments shown in fig. 4, fig. 7-fig. 10, and will not be described in detail here.

Based on the foregoing embodiments, an embodiment of the present application provides a communication system, where the communication system may include the remote terminal device, the first device, the network device, and the like related to the foregoing embodiments.

The embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium is used for storing a computer program, and when the computer program is executed by a computer, the computer may implement the communication method provided by the above method embodiment.

The embodiment of the present application further provides a computer program product, where the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer may implement the communication method provided by the above method embodiment.

The embodiment of the present application further provides a chip, which includes a processor, where the processor is coupled to a memory, and is configured to call a program in the memory, so that the chip implements the communication method provided in the foregoing method embodiment.

The embodiment of the present application further provides a chip, where the chip is coupled with a memory, and the chip is used to implement the communication method provided in the above method embodiment.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of communication, comprising:

receiving a first request message from a first device, the first request message indicating an identity of at least one public land mobile network, PLMN, of the first device; the first equipment carries out lateral communication with the remote terminal equipment and communicates with the network equipment through a network interface;

sending a first response message to the first device, the first response message being used to indicate a physical cell identity, PCI, determined based on an identity of a first PLMN, the identity of the first PLMN being one or more of the identities of the at least one PLMN.

2. The method of claim 1, wherein the PCI is determined based on an identity of the first PLMN, comprising:

the cell corresponding to the PCI is associated with the first device.

3. The method of claim 1 or 2, wherein receiving the first request message from the first device comprises:

receiving said first request message from said first device through a first type network interface, said first type network interface being an interface for said network device to communicate with a distribution unit, DU; the first request message further comprises indication information, and the indication information is used for indicating the first device to carry out lateral communication with the remote terminal device and is communicated with the network device through a network interface; or

Receiving the first request message from the first device through a second type network interface, the second type network interface being used for communication between the first device and the network device, the second type network interface being different from the first type network interface.

4. The method of any one of claims 1-3, further comprising:

sending a second request message to a first Distribution Unit (DU), wherein the second request message is used for indicating the identity of the first device and the identity of the first PLMN;

receiving a second response message from the first DU, where the second response message is used to indicate information of a first cell, and a correspondence exists between the first cell and an identifier of the first PLMN; the information of the first cell includes the PCI.

5. The method of claim 4, wherein the method further comprises:

and determining the first DU according to the identifier of the first PLMN.

6. The method of any one of claims 1-3, further comprising:

determining a first Distribution Unit (DU) and a first cell according to the identity of the first PLMN, wherein the first cell belongs to the first DU;

sending a third request message to the first DU, where the third request message is used to indicate an identifier of the first device and information of the first cell, and the information of the first cell includes the PCI and/or a cell identifier;

receiving a third response message from the first DU, the third response message including acknowledgement information.

7. The method of claim 6, wherein the third request message is further for indicating an identity of the first PLMN.

8. The method of any one of claims 1-7, further comprising:

sending first information to the first device, where the first information includes an identifier of a Data Radio Bearer (DRB) and quality of service corresponding to the DRB;

receiving second information from the first device, wherein the second information comprises a sideline configuration, and the sideline configuration is used for communication between the far-end terminal device and the first device through a nearby service communication 5 interface;

and sending a first configuration message to the remote terminal equipment through the first equipment, wherein the first configuration message comprises DRB configuration, the sidestream configuration and a cell radio network temporary identifier C-RNTI.

9. The method of claim 8, wherein the sidestream configuration comprises a radio link control, RLC, medium access control, and physical layer configuration of the sidestream; the RLC configuration includes an identification of the DRB; wherein the RLC bearer corresponds to the DRB.

10. The method of any one of claims 8-9, further comprising:

sending a fourth request message to a first Distribution Unit (DU), wherein the fourth request message is used for requesting the first DU to allocate a cell radio network temporary identifier (C-RNTI);

receiving a fourth response message from the first DU, the fourth response message being used for indicating the C-RNTI.

11. The method of claim 10, wherein the fourth request message includes indication information of the first device; the C-RNTI is allocated to the cell corresponding to the first device by the first DU, and the cell corresponding to the first device is determined by the first DU according to the indication information of the first device.

12. The method of any one of claims 1-7, further comprising:

determining a sideline configuration, wherein the sideline configuration is used for the communication between the far-end terminal equipment and the first equipment through an adjacent service communication 5 interface;

sending the sidestream configuration to the first device through a first network interface message, the first network interface message corresponding to the first device; or alternatively

Sending a first message to the first device, the first message including the sidelink configuration and information identifying the first device.

13. The method of any of claims 1-12, wherein the first response message is further for indicating third information, the third information comprising at least one of: tracking codes, radio access network notification area codes or cell identities; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identification is used to identify a cell within the first PLMN.

14. A method of communication, comprising:

sending a first request message to a network device, the first request message indicating an identity of at least one public land mobile network, PLMN, of the first device; the first equipment carries out sideline communication with the remote terminal equipment and communicates with the network equipment through a network interface;

receiving a first response message from the network device, the first response message including a Physical Cell Identity (PCI), the PCI being determined based on an identity of a first PLMN, the identity of the first PLMN being one or more of the identities of the at least one PLMN.

15. The method of claim 14, wherein the PCI is determined based on an identity of the first PLMN, comprising:

the cell corresponding to the PCI is associated with the first device.

16. The method of claim 14 or 15, wherein sending the first request message to the network device comprises:

sending the first request message to the network device through a first network type interface, where the first network type interface is an interface through which the network device communicates with a distribution unit DU; the first request message further comprises indication information, and the indication information is used for indicating the first device to carry out lateral communication with the remote terminal device and is communicated with the network device through a network interface; or

And sending the first request message to the network equipment through a second network type interface, wherein the second type network interface is used for communication between the first equipment and the network equipment, and the second type network interface is different from the first type network interface.

17. The method of any one of claims 14-16, further comprising:

sending a second message over an adjacent serving communication 5 interface, the second message including an identification of the first PLMN and the PCI.

18. The method of any one of claims 14-17, further comprising:

receiving first information from the network equipment, wherein the first information comprises an identifier of a Data Radio Bearer (DRB) and service quality corresponding to the DRB;

sending second information to the network device, where the second information includes a sidestream configuration, where the sidestream configuration is used for the far-end terminal device to communicate with the first device through an adjacent service communication 5 interface;

receiving a first configuration message from the network equipment, wherein the first configuration message comprises DRB configuration, the sidestream configuration and a cell radio network temporary identifier C-RNTI (cell radio network temporary identity);

and sending the first configuration message to the far-end terminal equipment.

19. The method of claim 18, wherein the method further comprises:

and determining the sidestream configuration according to the identification of the DRB and the service quality corresponding to the DRB.

20. The method of claim 18 or 19, wherein the sidestream configuration comprises a radio link control, RLC, medium access control, and physical layer configuration of the sidestream; the RLC configuration includes an identification of the DRB; wherein the RLC bearer corresponds to the DRB.

21. The method of any one of claims 14-17, further comprising:

receiving a sidelink configuration from the network device through a first network interface message, wherein the sidelink configuration is used for a far-end terminal device and the first device to communicate through a nearby service communication 5 interface; the first network interface message corresponds to the first device; or

Receiving a first message from the network device, the first message including the sidelink configuration and information identifying the first device.

22. The method of any of claims 14-21, wherein the first response message is further to indicate third information, the third information comprising at least one of: a tracking code, radio access network notification area code or cell identification; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identification is used to identify a cell within the first PLMN.

23. The method of claim 17, wherein the second message further comprises at least one of: a tracking code, radio access network notification area code or cell identification; wherein the tracking code and the radio access network notification area code correspond to the PCI, and the cell identification is used to identify a cell within the first PLMN.

24. A communications device comprising means or modules for performing the method of any of claims 1-13 or comprising means or modules for performing the method of any of claims 14-23.

25. A communication device comprising a communication interface and a processor, wherein:

the communication interface is used for receiving signals from other communication devices except the communication device and transmitting the signals to the processor or sending the signals from the processor to other communication devices except the communication device;

the processor, configured to cause, by program instructions, the communication device to implement the method of any one of claims 1-13, or to implement the method of any one of claims 14-23.

26. A communication system comprising a communication device according to claim 24 or 25.

27. A computer-readable storage medium having stored thereon computer-executable instructions, which, when invoked by the computer, are adapted to cause the computer to perform the method of any of the preceding claims 1 to 13, or to perform the method of any of the preceding claims 14 to 23.

28. A computer program product comprising instructions for causing a computer to perform the method of any one of claims 1 to 13 or the method of any one of claims 14 to 23 when the computer program product is run on the computer.

29. A chip coupled to a memory for reading and executing program instructions stored in the memory to implement the method of any one of claims 1 to 13 or to implement the method of any one of claims 14 to 23.