A communication method and device

Abstract

A communication method and device are applied in the field of Internet of Things, wherein an edge relay node integrates a first CU-UP entity and a first UPF entity; a user device initiates a first PDU session request to a core network, and the first PDU session request carries a local communication type identifier; and the user device sends the identifier of the edge relay node to the access network, and the access network device can select the first CU-UP entity according to the identifier of the edge relay node to establish a first DRB; the core network device can select the first UPF according to the local communication type identifier to establish a first PDU session, and the core network device sends the first PDU session information to the edge relay node through the first DRB; the first PDU session information is used by the first UPF entity to serve the first PDU session, and the first PDU session is used to carry the transmission data between the edge relay node and the terminal device. The edge relay node can also have the function of an edge computing device, which can reduce the deployment of edge computing devices and reduce data transmission delay.

Description

Technical Field

[0001] The present application relates to the field of Internet of Things, and in particular to a communication method and device. Background Art

[0002] With the rapid development of IoT technology, the number of IoT devices has increased rapidly. The cloud computing-based approach cannot meet the actual needs of many scenarios, so edge computing has emerged. More and more IoT has changed from the architecture of end, pipe, and cloud to the architecture of end, edge, pipe, and cloud. Figure 1 As shown in the figure, the end refers to the local terminal, which is used to collect data. The edge refers to the device with edge computing capabilities, which is used to collect information from the local terminal, perform edge computing on the acquired information, and implement local management and control. The pipe refers to the local communication pipeline between the end and the edge, and the remote communication pipeline between the edge and the cloud. The cloud refers to the IoT platform or application.

[0003] The end and the edge need to support local communication (that is, the end can directly access local applications), and there is no need to use remote communication to forward data through the access network and core network to the IoT platform for processing. The edge computing architecture improves communication efficiency.

[0004] In some cases, due to the complexity of the device deployment environment, multiple relay nodes are required between the end and the edge to support relay in local communication to ensure reliable communication between the end and the edge. In other words, in this case, in order to achieve the reliability of edge computing and communication of the Internet of Things, both edge computing devices and relay node devices must be deployed, which increases the cost of device deployment. Summary of the invention

[0005] The embodiments of the present application provide a communication method and apparatus for enabling relay nodes and terminal devices to achieve local communication, thereby reducing the deployment of edge computing devices, reducing costs, and reducing data transmission delays.

[0006] In the first aspect, the present application provides a communication method, which is applied to an edge relay node, where the edge relay node refers to a relay node that can support local communication; the edge relay node includes a first centralized unit user plane CU-UP entity and a first user plane function UPF entity; the edge relay node sends an identifier of the edge relay node to an access network device, so that the access network device selects a first CU-UP entity according to the identifier of the edge relay node, and establishes a first data bearer DRB between the access network device and the CU-UP entity; then, the edge relay node can receive a first PDU session information from a core network device through the first DRB, and the first PDU session information comes from the core network device and is forwarded by the access network device; the first PDU session information is used to serve the first PDU session; wherein, the first PDU session is established by: after the terminal device initiates a first PDU session request to the core network, the core network selects a first UPF entity according to the local communication type identifier and the identifier of the edge relay node; wherein the first PDU session request includes the identifier of the edge relay node and the local communication type identifier; the first PDU session is used to carry the service data to be transmitted between the edge relay node and the terminal device.

[0007] In this embodiment, the edge relay node integrates the first CU-UP entity and the first UPF entity. The first CU-UP entity and the first UPF entity are used to implement the user plane function of the edge relay node. The core network device selects the first UPF entity according to the local communication identifier to establish a first PDU session. The first UPF entity is used to serve the first PDU session, and the first PDU session is used to carry the transmission data between the edge relay node and the terminal device. In this application, the edge relay node and the terminal device can realize local communication. The edge relay node in the Internet of Things communication system can also have the function of an edge computing device, which can reduce the deployment of edge computing devices and reduce costs, and can also reduce data transmission delays.

[0008] In an optional implementation, the edge relay node can also initiate a second PDU session request to the core network to establish its own second PDU session; the second PDU session request includes a remote communication type identifier, and the remote communication type identifier indicates that the second PDU session to be established is a PDU session for remote communication; and the remote communication type identifier instructs the core network device to select a second UPF entity deployed in the core network for the second PDU session to be established, so as to establish a second PDU session from the edge relay node and the access network device to the core network, and the second UPF entity is used to serve the second PDU session.

[0009] In this example, the edge relay node can establish a second PDU session with the second UPF in the core network to support remote communication, and the terminal device can establish a first PDU session with the first UPF in the edge relay node to support local communication. The core network device can select the first UPF to serve the first PDU session based on the local communication type identifier, and select the second UPF to serve the second PDU session based on the remote communication type identifier. In this way, the terminal can switch the service from remote communication to local communication, or switch local communication to remote communication as needed. In this example, the edge relay node can implement the function of local communication and can be flexibly applied to different application scenarios. The edge relay node can be used in relay forwarding scenarios as well as in edge computing application scenarios, which saves equipment costs while increasing the flexibility of application scenarios.

[0010] In an optional implementation, after the edge relay node receives the first PDU session information from the core network device, the edge relay node transmits the service data between the edge relay node and the terminal device through the first PDU session, and the terminal device can communicate locally with the edge relay node (ie, local application access).

[0011] In an optional implementation, the first PDU session information includes a quality of service QoS flow list, and the transmission of service data between the edge relay node and the terminal device through the first PDU session may include: the edge relay node receives the first service data sent by the terminal device; then, the first service data is mapped to the corresponding QoS flow based on the first PDU session information through the first UPF and the first CU-UP; according to the mapping relationship between the first service data and the QoS flow, the second service data is transmitted, and the second service data may be service data obtained according to the first service data. For example, the edge relay node may output the second service data to a display device, and display the second service data through the display device, or the edge relay node may transmit the second service data to the terminal.

[0012] In an optional implementation, the edge relay node may broadcast a system message, the system message including an identifier of the edge relay node. The edge relay node may broadcast the identifier of the edge relay node by broadcasting the system message, so that the terminal device receives the identifier of the edge relay node, so that the terminal device can select an edge relay node that supports local communication to access the cell.

[0013] In an optional implementation, the edge relay node may be a power line communication PLC central coordinator, and the identifier of the edge relay node is a PLC network identifier NID. In this example, the edge relay node may also be applied to a PLC wireless dual-mode scenario to meet the requirements of a specific application scenario.

[0014] In an optional implementation, the first PDU session information includes a second DRB list, and the QoS flow and packet detection rule PDR corresponding to each second DRB in the second DRB list; the second DRB is the bearer between the terminal device and the edge relay node.

[0015] In the second aspect, an embodiment of the present application provides a communication method, which is applied to an access network device, the access network device receives the identifier of an edge relay node sent by a terminal device; wherein the edge relay node includes a first UPF entity and a first CU-UP entity; then, a first PDU session request initiated by the terminal device is received, and the first PDU session request is forwarded to the core network device, the first PDU session request includes the identifier of the edge relay node and the local communication type identifier; the local communication type is used to indicate that the core network device selects the first UPF according to the identifier of the relay node to establish a first PDU session; then, the access network device receives the first PDU session information and the identifier of the edge relay node sent by the core network; the access network device selects the first CU-UP according to the ID of the edge relay node to establish a first DRB; and sends the first PDU session information to the edge relay node through the first DRB, the first PDU session information is used by the first UPF entity to serve the first PDU session, and the first PDU session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

[0016] In this embodiment, the edge relay node integrates the first CU-UP entity and the first UPF entity. The first CU-UP entity and the first UPF entity are used to implement the user plane function of the edge relay node. The core network device selects the first UPF entity according to the local communication identifier to establish a first PDU session. The first UPF entity is used to serve the first PDU session, and the first PDU session is used to carry the transmission data between the edge relay node and the terminal device. In this application, the edge relay node and the terminal device can realize local communication, and the edge relay node in the Internet of Things system can also have the function of an edge computing device, which can reduce the deployment of edge computing devices, reduce costs, and reduce data transmission delays.

[0017] In an optional implementation, the first PDU session information includes a second DRB list, and the QoS flow and PDR corresponding to each second DRB in the second DRB list; the second DRB is the bearer between the terminal device and the edge relay node.

[0018] In an optional implementation, the access network device receives a second PDU session request initiated by the edge relay node, and forwards the second PDU session request to the core network device, wherein the second PDU session request includes an identifier of the edge relay node and a remote communication type identifier; so that the core network device selects a second UPF entity to establish a second PDU session for the edge relay node.

[0019] In this example, the edge relay node can establish a second PDU session with the second UPF in the core network to support remote communication, and the terminal device can establish a first PDU session with the first UPF in the edge relay node to support local communication. The core network can select the first UPF to serve the first PDU session based on the local communication type identifier, and select the second UPF to serve the second PDU session based on the remote communication type identifier. In this way, the terminal can switch the service from remote communication to local communication, or switch local communication to remote communication as needed. In this example, the edge relay node can implement the function of local communication and can be flexibly applied to different application scenarios. The edge relay node can be used in relay forwarding scenarios as well as in edge computing application scenarios, which saves equipment costs while increasing the flexibility of application scenarios.

[0020] In a third aspect, the present application provides a communication method, which is applied to a core network device, and the method includes:

[0021] The core network device receives a first PDU session request from the terminal device, where the first PDU session request is initiated by the terminal device, and includes an edge relay node identifier and a local communication type identifier; the local communication type identifier is used to inform the core network device that the first PDU session is used for local communication, and the edge relay node includes a first CU-UP entity and a first UPF entity; then, the core network device selects the first UPF entity in the edge relay node according to the local communication type identifier to establish a first PDU session; the core network device sends first PDU session information to the access network device, and the first PDU session information includes the edge relay node identifier; so that the access network device selects the first CU-UP entity according to the edge relay node identifier to establish a first DRB, and sends the first PDU session information to the edge relay node through the first DRB, the first UPF entity is used to serve the PDU session according to the first PDU session information, and the first PDU session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

[0022] In this embodiment, the edge relay node integrates the first CU-UP entity and the first UPF entity. The first CU-UP entity and the first UPF entity are used to implement the user plane function of the edge relay node. The core network device selects the first UPF entity according to the local communication identifier to establish a first PDU session. The first UPF entity is used to serve the first PDU session, and the first PDU session is used to carry the transmission data between the edge relay node and the terminal device. In this application, the edge relay node and the terminal device can realize local communication, and the edge relay node in the Internet of Things system can also have the function of an edge computing device, which can reduce the deployment of edge computing devices, reduce costs, and reduce data transmission delays.

[0023] In an optional implementation, the method also includes: the core network device can also receive a second PDU session request initiated by the edge relay node, the second PDU session request includes the identifier of the edge relay node and the remote communication type identifier; then select a second UPF entity deployed in the core network according to the remote communication type identifier to establish a second PDU session, the second UPF entity is used to serve the second PDU session, and the second PDU session is used to carry the business data to be transmitted between the edge relay node and the core network device.

[0024] In an optional implementation, the core network device sends a PDR to the edge relay node. Each PDR can also be used to detect data packets in a specific transmission direction, for example, an uplink direction or a downlink direction. In this example, the edge relay node is used to support both local communications and remote communications. For example, when the relay node receives the first service data sent by the terminal device, the second service data can be processed locally to obtain the second service data. The relay node can detect which second service data needs to be processed locally, which second service data (downlink data) needs to be sent to the terminal, and which second service data (uplink data) needs to be sent to the access network device based on the PDR.

[0025] In the fourth aspect, an embodiment of the present application provides a communication device, which can be used to implement the method performed by the edge relay node in the above-mentioned first aspect, and the communication device integrates a first CU-UP entity and a first UPF entity; the communication device also includes: a transceiver module, used to send the identifier of the edge relay node to the access network device, so that the access network device selects the first CU-UP entity according to the identifier of the edge relay node, and establishes a first data bearer DRB between the access network device and the CU-UP entity; the transceiver module is also used to receive the first PDU session information from the core network through the first DRB, and the first PDU session information is used to serve the first PDU session; wherein, the first PDU session is established by: after the terminal device initiates a first PDU session request to the core network, the core network device selects the first UPF entity according to the local communication type identifier and the identifier of the edge relay node; wherein the first PDU session request includes the identifier of the edge relay node and the local communication type identifier; the first PDU session is used to carry the service data to be transmitted between the edge relay node and the terminal device.

[0026] In an optional implementation, the transceiver module is also used to initiate a second PDU session request to the core network device to establish a second PDU session; the second PDU session request includes a remote communication type identifier; the remote communication type identifier is used by the core network to select a second UPF entity for the second PDU session to be established, and the second UPF entity is a UPF entity deployed in the core network; the second UPF entity is used to serve the second PDU session.

[0027] In an optional implementation, the transceiver module is also used to transmit business data between the edge relay node and the terminal device through the first PDU session.

[0028] In an optional implementation, the first PDU session information includes a quality of service QoS flow list, and the device also includes a processing module; a transceiver module, which is also used to receive the first business data sent by the terminal device; the processing module is used to map the first business data to the corresponding QoS flow based on the first PDU session information through the first UPF and the first CU-UP; the transceiver module is also used to transmit the second business data according to the mapping relationship between the first business data and the QoS flow, and the second business data is the business data obtained based on the first business data.

[0029] In an optional implementation, the transceiver module is further used to broadcast a system message, where the system message includes an identifier of the edge relay node, so that the terminal device receives the identifier of the edge relay node.

[0030] In an optional implementation manner, the edge relay node is a power line communication PLC central coordinator, and the identifier of the edge relay node is a PLC network identifier NID.

[0031] In an optional implementation, the first PDU session information includes a second DRB list, and the QoS flow and packet detection rule PDR corresponding to each second DRB in the second DRB list; the second DRB is the bearer between the terminal device and the edge relay node.

[0032] In the fifth aspect, an embodiment of the present application provides a communication device, which is used to implement the method executed by the access network device in the second aspect above, and the device includes: a transceiver module, which is used to receive the identifier of the edge relay node sent by the terminal device; wherein the edge relay node includes a first UPF entity and a first CU-UP entity; the transceiver module is also used to receive a first PDU session request initiated by the terminal device, and forward the PDU session request to the core network device, the first PDU session request includes the identifier of the edge relay node and the local communication type identifier; the local communication type is used for the core network device to select the first UPF according to the identifier of the relay node to establish a first PDU session; the transceiver module is also used to receive the first PDU session information and the identifier of the edge relay node sent by the core network device; the processing module is used to select CU-UP to establish a first DRB according to the ID of the edge relay node received by the transceiver module; the transceiver module is also used to send the first PDU session information to the edge relay node through the first DRB established by the processing module, the first UPF entity is used to serve the PDU session according to the first PDU session information, and the first PDU session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

[0033] In an optional implementation, the transceiver module is also used to receive a second PDU session request initiated by the edge relay node, and forward the second PDU session request to the core network device, the second PDU session request includes the identifier of the edge relay node and the remote communication type identifier; the remote communication type identifier is used to instruct the core network device to select a second UPF entity to establish a second PDU session for the edge relay node.

[0034] In the sixth aspect, an embodiment of the present application provides a communication device, which is used to implement the method executed by the core network device in the third aspect above, and the device includes: a transceiver module, which is used to receive a first PDU session request sent by an access network device, the first PDU session request includes an identifier of an edge relay node and a local communication type identifier; the edge relay node includes a first CU-UP entity and a first UPF entity; a processing module, which is used to select a first UPF entity in the edge relay node according to the local communication type identifier received by the transceiver module to establish a first PDU session; the transceiver module is used to send first PDU session information to the access network device, the first PDU session information includes an identifier of the edge relay node; so that the access network device selects the first CU-UP entity according to the identifier of the edge relay node to establish a first DRB, and sends the first PDU session information to the edge relay node through the first DRB, the first PDU session information is used by the first UPF entity to serve the PDU session according to the first PDU session information, and the first PDU session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

[0035] In an optional implementation, the transceiver module is also used to receive a second PDU session request initiated by the edge relay node, and the second PDU session request includes an identifier of the edge relay node and a remote communication type identifier; the processing module is also used to select a second UPF entity according to the remote communication type identifier received by the transceiver module to establish a second PDU session, and the second UPF entity is a UPF entity deployed in the core network; the second UPF entity is used to serve the second PDU session, and the second PDU session is used to carry business data to be transmitted between the edge relay node and the core network device.

[0036] In an optional implementation, the transceiver module is further configured to send the PDR to the edge relay node.

[0037] In the seventh aspect, an embodiment of the present application provides a communication device, comprising a processor, wherein the processor is coupled to at least one memory, and the processor is used to read a computer program stored in the at least one memory, so that the device executes the method described in the first aspect above, or the device executes the method described in the second aspect above, or the device executes the method described in the third aspect above.

[0038] In an eighth aspect, an embodiment of the present application provides a computer-readable medium, wherein the computer-readable storage medium is used to store a computer program. When the computer program runs on a computer, the computer executes the method described in the first aspect above; or, the computer executes the method described in the second aspect above; or, the computer executes the method described in the third aspect above.

[0039] In a ninth aspect, the present application provides a chip system, which includes a processor for supporting an edge relay node to implement the functions involved in the above aspects, or for supporting an access network device to implement the functions involved in the above aspects, or for supporting a core network device to implement the functions involved in the above aspects, for example, sending or processing the data and / or information involved in the above methods. In one possible design, the chip system also includes a memory, which is used to store program instructions and data necessary for edge relay nodes, or for storing program instructions and data necessary for access network devices, or for storing program instructions and data necessary for core network devices. The chip system may be composed of chips, or may include chips and other discrete devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 This is a schematic diagram of the architecture of the Internet of Things communication system;

[0041] Figure 2 It is a schematic diagram of the architecture of each device in the IoT communication system in the traditional method;

[0042] Figure 3 A schematic diagram of the user plane protocol stack of each device in the IoT communication system in the traditional method;

[0043] Figure 4 This is a schematic diagram of the architecture of each device in the Internet of Things communication system in the embodiment of the present application;

[0044] Figure 5 This is a schematic diagram of the user plane protocol stack of each device in the Internet of Things communication system in the embodiment of the present application;

[0045] Figure 6 A schematic diagram of a step flow of an embodiment of a communication method in an embodiment of the present application;

[0046] Figure 7 A schematic diagram of a relay node broadcasting a system message in an embodiment of the present application;

[0047] Figure 8 A schematic diagram of a step flow chart of another embodiment of a communication method in an embodiment of the present application;

[0048] Fig. 9A schematic diagram of the structure of an embodiment of a communication device in the embodiments of the present application;

[0049] Fig.10 This is a structural diagram of another embodiment of a communication device in the embodiments of the present application. DETAILED DESCRIPTION

[0050] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than that illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0051] In the IoT communication system, in some cases, due to the complexity of the device deployment environment, multiple relay nodes are required between the end and the edge to support multi-hop relay to ensure reliable communication between the end and the edge. In other words, in this case, in order to achieve the reliability of edge computing and communication of the IoT, both edge computing devices and relay node devices must be deployed, which increases the cost of device deployment.

[0052] In order to solve the above problems, the solution of the present application is to enable the relay node to have the ability of an edge computing device (also called an edge computing device), so that in the Internet of Things communication system, the relay node can realize both the function of relay and the function of an edge computing device. The distance between the relay node and the terminal device is relatively close, and it is more appropriate to deploy the relay node as an edge computing device, which can further reduce the data transmission delay and save the deployment cost of the device. Since the current relay node can only forward data (i.e., relay), the relay node cannot directly transmit data with the terminal device. Therefore, the relay node in the current technology cannot realize the function of an edge computing device. Compared with the current relay node, the communication of the relay node is enhanced in the present application, and the relay node adds a centralized unit user plane (central unit user plane, CU-UP) entity and a user plane function (user plane function, UPF) entity, so that the relay node can realize data transmission with the terminal device, and the relay node realizes the function of an edge computing device.

[0053] In order to better understand the present solution, the relay node architecture in the traditional method is first described below.

[0054] Currently, the 3rd Generation Partnership Project (3GPP) is exploring the relay solution for 5G communication systems (5th generation, 5G). In TR38.874, the relay is called IAB (integrated access and backhaul), which supports access links and backhaul links. Among them, the link between the terminal device and the relay is the access link, and the link between the relay and the relay or access network equipment (such as a base station) is the backhaul link.

[0055] See also Figure 2 As shown, the architecture of IAB utilizes a distributed unit (DU) and a centralized unit (CU) separation architecture, and IAB is composed of DU and mobile terminal (MT). The CU in the access network equipment manages one or more DUs, and the interface between the CU and the DU is the F1 interface. The DU of IAB provides air interface access services for user equipment (UE) and the MT of the child relay node, and the DU of IAB is used to implement RLC and lower layer protocols. The MT of IAB cooperates with the parent relay node or access network equipment (such as IAB Donor) to implement the backhaul link of the relay. DU and MT work together to implement the relay function. IAB Donor is the base station accessed by UE and relay IAB, and IAB Donor is composed of DU and CU.

[0056] The user plane protocol stack of the traditional relay node is as follows: Figure 3As shown in the figure, CU is used to implement the radio resource control (RRC) protocol, packet data convergence protocol (PDCP) and service data adaptation protocol (SDAP). DU is used to implement the radio link control (RLC) protocol, media access control (MAC) protocol and physical layer (PHY) protocol (not shown in the figure). An adaptation protocol (adapt) is added to the RLC protocol, and the adaptation protocol supports multi-hop relay forwarding. The adaptation protocol only exists on the backhaul link between relays and does not exist on the access link. The IAB relay solution forwards data at the RLC layer (belonging to the air interface layer 2), and the data needs to be sent to the access network device to complete the air interface user plane protocol processing. Since the access network device in the 3GPP architecture does not support the data forwarding function between UEs, the data needs to be further sent to the core network to complete the data forwarding between UEs. Therefore, the IAB relay solution cannot support local communication, that is, the relay node cannot directly parse and process the data packets of the terminal device, and the current relay node does not have the ability to implement edge computing devices.

[0057] The present application provides a communication method, which is used to enable a terminal device and a relay node to support direct communication (i.e., direct local application access), that is, the terminal device and the relay node can realize local communication, so that the relay node can realize the function of an edge computing device. In this embodiment, the edge relay node integrates a first CU-UP entity and a first UPF entity. The first CU-UP entity and the first UPF entity are used to implement the user plane function of the edge relay node. The user equipment initiates a first protocol data unit (PDU) session request to the core network, and the first PDU session request carries a local communication type identifier. In addition, the user equipment sends the identifier of the edge relay node to the access network, so that the access network device selects the first CU-UP entity according to the identifier of the edge relay node, and establishes a first DRB between the access network device and the first CU-UP entity. The core network device can select the first UPF according to the local communication type identifier to establish a first PDU session, and the core network device generates the first PDU session information for the PDU session requested by the user equipment, and sends the first PDU session information to the edge relay node through the first DRB. The first PDU session information is used by the first UPF entity to serve the first PDU session, and the first PDU session is used to carry the transmission data between the edge relay node and the terminal device. In this application, the edge relay node in the IoT communication system can also have the function of an edge computing device, which can reduce the deployment of edge computing devices, reduce costs, and reduce data transmission delays.

[0058] First, the terms used in this application are explained.

[0059] Edge relay node: In order to distinguish between relays that do not support local communication and relays that support local communication, the relays that support local communication are referred to as "edge relay nodes" in this application. Edge relay nodes have both the ability to relay ordinary relay nodes (such as IAB) and the ability to communicate locally (equivalent to local communication of edge computing devices). In this application, when an edge relay node supports local communication, the edge relay node can be equivalent to an edge computing device. In this application, an edge relay node is also referred to as direct local application access (DLAA) IAB. In this application, a relay node that only supports relay functions can be illustrated by taking IAB as an example. An edge relay node that supports both local communication and relay functions can be illustrated by taking DLAA IAB as an example.

[0060] Local communication: Communication between local terminals (also called user devices) and edge computing devices within a small range.

[0061] Long-range communication: Long-range, wide-area communication between edge computing devices and IoT platforms (or applications).

[0062] In order to distinguish the CU-UP in the edge relay node from the CU-UP in the base station, the CU-UP in the edge relay node is called the "first CU-UP" and the CU-UP in the base station is called the "second CU-UP". In order to distinguish the UPF in the edge relay node from the UPF deployed in the core network, the UPF in the relay node is called the "first UPF" and the UPF deployed in the core network is called the "second UPF".

[0063] The communication method is applied to the Internet of Things communication system, which includes but is not limited to the 5G communication system, the 5.5G communication system, the 6G communication system, the system integrating multiple communication systems, or the communication system evolved in the future. For example, the new radio (NR) system, the wireless-fidelity (WiFi) system, the 3GPP-related communication system, and other such communication systems. Please refer to Figure 4 As shown, the IoT communication system includes a terminal device (also called a user device), an edge relay node (such as DLAA IAB), an access network device (such as an IAB donor) and a core network. Optionally, it may also include multiple relay nodes (such as IAB). Among them, the edge relay node integrates the user plane functional entities required to realize local communication, namely the first CU-UP and the first UPF. The relay IAB includes DU, MT and the first CU-UP. The first CU-UP can manage one or more DUs, and the interface between the first CU-UP and the DU is the F1 interface. Since DLAA IAB needs to implement the CU-UP function, an E1 interface needs to be added between the DLAA IAB and the access network device. The interface is a control plane interface, which is used to realize the control plane signaling interaction between the edge relay node and the access network device. Its protocol is the E1 Application Protocol (AP). The second CU-UP in the access network device interacts with the first CU-UP in the edge relay node through the E1 interface. The user plane protocol stack in the system is as follows Figure 5 As shown, the first CU-UP includes a PDCP protocol layer and an SDAP protocol layer. The first CU-UP in the edge relay node is used to implement the SDAP and PDCP protocols, and SDAP is responsible for completing the mapping from the quality of service (QoS) flow to the radio bearer (DRB). The first UPF completes the mapping of the received IP data packet to the QoS flow, that is, marking the QoS flow to which the received IP data packet belongs. Therefore, the first UPF and the first CU-UP jointly complete the mapping of data to the radio bearer.

[0064] In this application, the terminal is a terminal with a data collection function. The terminal can be various sensors, mobile phones, tablet computers, computers with wireless transceiver functions, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, terminals in industrial control (industrialcontrol), vehicle-mounted terminal devices, terminals in unmanned driving, terminals in assisted driving, terminals in remote medical, terminals in smart grids (smartgrid), terminals in transportation safety (transportationsafety), terminals in smart cities (smart cities), terminals in smart homes (smart homes), etc. The embodiments of this application do not limit the application scenarios. The terminal may sometimes also be referred to as a terminal device, a terminal equipment (userequipment, UE), an access terminal device or a UE device, etc. The terminal may be fixed or mobile.

[0065] The access network device can be a base station (gNodeB or gNB) or a transmission receiving point (transmission receiving point / transmission reception point, TRP) in NR, a base station of subsequent evolution of 3GPP. The base station can be a macro base station, a micro base station, etc. The base station can communicate with the terminal device, and can also communicate with the terminal device through a relay node. The terminal device can communicate with multiple base stations of different technologies. For example, the terminal device can communicate with a base station that supports a 5G network, and can also support dual connections with a base station of a long term evolution (LTE) network and a base station of a 5G network. In an embodiment of the present application, the access network device is illustrated by taking a base station as an example. The base station is a base station (IAB donor) accessed by an edge relay node.

[0066] The edge relay node may be a device with data processing capability. For example, the edge relay node may be a gateway, a router, a road test unit, a micro base station, a small base station, a pico base station, etc. The edge relay node may also be a terminal device, or the edge relay node may also be a server.

[0067] The present application embodiment provides a communication method, which is used to implement local communication between an edge relay node and a terminal device. Figure 6 As shown, an embodiment of a communication method includes:

[0068] Step 601: An edge relay node sends an identifier of the edge relay node to an access network device. Correspondingly, the access network device receives the identifier of the edge relay node sent by the edge relay node.

[0069] After the edge relay node (DLAA IAB) successfully accesses the network, it sends a message to the access network device, which carries the edge relay node's own identifier (such as ID or index, etc.), which is pre-assigned by the access network device. Optionally, the edge relay node can send the edge relay node's identifier to the access network device by establishing a related message of the E1 interface to reduce signaling overhead. The purpose of the edge relay node sending its own identifier to the access network device is to enable the access network device to identify the edge relay node. In subsequent steps, the access network device can select the first CU-UP in the DLAA IAB based on the identifier.

[0070] Step 602: After receiving the identifier of the edge relay node, the access network device saves the identifier of the edge relay node.

[0071] The identifier of the DLAA IAB is used to inform the access network device that the relay node is an edge relay node (a relay node that can support local communication) and is used to distinguish different edge relay nodes. For example, the system may include multiple IABs and multiple DLAA IABs. The identifier of the relay node may include a type identifier and a sequence number identifier, wherein the type identifier is used to indicate whether the relay node is an ordinary relay node (IAB) or an edge relay node (DLAA IAB). The IDs of multiple IABs may be: 0-1, 0-2, 0-3, etc. The IDs of multiple DLAA IABs may be: 1-1, 1-2, 1-3, etc. The access network device can determine whether the node is an IAB or a DLAA IAB based on the identifier, and which DLAA IAB it is. It should be noted that the ID of the DLAA IAB in this example is only an example for the convenience of explanation, and does not limit the ID of the DLAA IAB.

[0072] Step 603: The edge relay node broadcasts a system message.

[0073] See also Figure 7As shown, the system information (SI) broadcast by the DLAA IAB can be directly received by the terminal device, or the system information can be received by other IABs in the system, and then received by the terminal device after being relayed and broadcast by the IAB. The system message includes a communication type identifier (flag) and an identifier of an edge relay node (DLAA IABID). Optionally, the system message may also include the DLAA IAB hop count and session type (such as IPv4, IPv6, IPv4v6, etc.). Among them, the communication type identifier is used to indicate the communication type. Exemplarily, when the flag bit in the flag is set to true, it indicates that the communication type identifier is a local communication type identifier, and the DLAA IAB supports local communication. When the flag bit in the flag is set to false, it indicates that the communication type identifier is a remote communication type identifier.

[0074] Step 604: The terminal device obtains the identifier of the edge relay node from the system message of the edge relay node, and selects a cell supporting DLAA IAB to reside in.

[0075] When the terminal device selects and resides in a cell, it chooses to reside in a cell that supports DLAA. For example, when searching for a cell, the terminal device searches for a system message broadcast by DLAA, which contains a local communication type identifier, indicating that the cell supports DLAA. Optionally, the terminal device also needs to select DLAA IAB access (i.e., reside in a cell) with a small number of hops. This can reduce the transmission delay from the terminal device to the edge relay node.

[0076] Exemplary, for a scenario where a terminal device needs to access a specified DLAA IAB. For example, a power line communication (PLC) wireless dual-mode scenario. PLC technology refers to a communication method that uses power lines to transmit data and media signals. This technology converts the original signal into a high-frequency signal by modulation and loads it into the power line for transmission. At the receiving end, the modulated signal is taken out and demodulated through a filter to obtain the original signal, thereby realizing information transmission. In the PLC wireless dual-mode scenario, within the transformer station area (the power supply range or area of ​​the transformer), multiple terminals connected to the transformer can be wirelessly accessed to the DLAA IAB. At this time, the DLAA IAB is equivalent to the PLC central coordinator (CCo), and the DLAA IAB sets its DLAA IAB ID as the PLC network identifier (NID), and the DLAA IAB broadcasts the PLC NID in the system message.

[0077] The local terminal (such as an electric meter) needs to access the specified DLAA IAB. For example, multiple electric meters are covered in a certain geographical area (such as Building No. 1). Building No. 1 corresponds to 50 users, each of which corresponds to an electric meter. These 50 electric meters are connected to Transformer No. 1. In order to avoid the 50 electric meters from being mistakenly connected to other edge relay nodes, each local terminal (electric meter) presets the DLAA IABID. When the local terminal receives a system message, it needs to match the preset DLAA IAB ID with the received PLC NID. The electric meter determines the PLC NID that matches the preset DLAA IAB ID and selects the DLAA IAB access corresponding to the PLC NID, which can ensure that the terminal accesses the corresponding transformer area and meets the requirements of specific application scenarios.

[0078] It should be noted that step 601 and step 602 may also be performed after step 604, and the specific sequence is not limited.

[0079] Step 605: The terminal device initiates a first PDU session request. Correspondingly, the core network device receives the first PDU session request from the terminal device.

[0080] The terminal device initiates a first PDU session establishment request (PDU session establishment request) to the core network device. The first PDU session request is forwarded by the base station to the core network device. The first PDU session request includes an identifier of an edge relay node and a local communication type identifier. In the embodiment of the present application, the core network device is also referred to as the core network.

[0081] Step 606: The core network device identifies the first PDU session as a local communication PDU session according to the local communication type identifier.

[0082] The first PDU session request is used to request the core network device to establish a PDU session. The first PDU session request carries a local communication type identifier. The core network device identifies the first PDU session as a PDU session for local communication based on the local communication type identifier. The DLAA IAB in this application includes a first UPF. When the core network identifies that the first PDU session is a PDU session for local communication, the core network device selects a first UPF, and the first UPF is used to serve the first PDU session to be established.

[0083] Step 607: The core network device sends a context establishment request to the access network device, where the context establishment request (initial context setup request) includes the first PDU session information.

[0084] The first PDU session information includes: PDU session ID, PDU type (Type) and second DRB to setup list (DRB to setup list). Among them, each DRB in the second DRB establishment list contains the corresponding QoS flow list (QoS flow list) and packet detection rule (packet detection rule, PDR), etc. Among them, PDR is used to map data and QoS flow, and map the data to the corresponding second DRB, and the second DRB is the bearer between the terminal device and the edge relay node. The second DRB is pre-established. Since the first CU-UP and the first UPF are integrated in the edge relay node (DLAA IAB), the interface between the first CU-UP and the first UPF can be simplified, such as without the use of the standard general packet radio service tunnelling protocol-userplane (GTP-U) protocol, the first PDU session information does not include the IP address of the first UPF and the GTP-U tunnel endpoint identifier (tunnel end point identifier, TEID).

[0085] Step 608: The access network device selects a first CU-UP located in the DLAA IAB based on the identifier of the edge relay node (DLAA IAB ID).

[0086] Step 609: The access network device sends a bearer context setup request (bearer context setup request) to the first CU-UP.

[0087] The access network device initiates the establishment of the first DRB to the edge relay node (DLAA IAB), and the bearer context establishment request carries the first PDU session information, and the first PDU session information includes: PDU session ID, PDU type (Type) and second DRB establishment list (DRB to setup list), wherein each DRB in the second DRB establishment list contains a corresponding QoS flow list (QoS flow list) and PDR, and the PDR is used to map the received data packet to the corresponding second DRB, and the second DRB is the bearer between the terminal device and the edge relay node. The second DRB is pre-established.

[0088] Step 610: The edge relay node establishes a corresponding first DRB, and the edge relay node (such as DLAA IAB) receives the first PDU session information through the first DRB.

[0089] The purpose of steps 608-610 is: the access network device selects the first CU-UP, establishes the first DRB between the access network device and the edge relay node, and the edge relay node (such as DLAA IAB) receives the first PDU session information through the DRB and saves the QoS flow list and the packet detection rule PDR.

[0090] The first UPF entity serves the first PDU session according to the first PDU session information to establish a first PDU session between the user device and the edge relay node, and the first PDU session is used to carry the transmission data between the edge relay node and the terminal device. The number of the first PDU session is not limited and is determined according to the actual business situation.

[0091] Step 611: The edge relay node feeds back a bearer context setup response message to the base station.

[0092] The bearer context establishment response is used to inform the base station that the DRB establishment is completed. Step 611 is an optional step and may not be performed.

[0093] Step 612: The base station returns an initial context setup response message to the core network. The response may not include the IP address and GTP-U TEID transmitted by the user plane of the base station.

[0094] Step 612 is an optional step and may not be performed.

[0095] It should be noted that in the embodiment of the present application, the data bearer between the terminal device and the edge computing device has been pre-established. Therefore, in the embodiment of the present application, the process of establishing the data bearer between the terminal device and the edge computing device is not reflected. In the embodiment of the present application, the terminal and the edge relay node can be directly connected, or the information transmitted between the relay node and the terminal device can be forwarded by at least one relay node. The relay node (such as IAB) only plays the role of relay and forwards the information transmitted between the relay node and the terminal device.

[0096] In this embodiment, the edge relay node integrates the first CU-UP entity and the first UPF entity. The user equipment initiates a first PDU session request to the core network, and the first PDU session request carries a local communication type identifier. In addition, the user equipment sends the identifier of the edge relay node to the access network, so that the access network device selects the first CU-UP entity according to the identifier of the edge relay node, and establishes the first DRB between the access network device and the CU-UP entity. The core network can select the first UPF according to the local communication type identifier to establish the first PDU session, and the core network generates the first PDU session information for the PDU session requested by the user equipment, and sends the first PDU session information to the edge relay node. The first UPF entity can serve the first PDU session according to the first PDU session information, and the first PDU session is used to carry the transmission data between the edge relay node and the terminal device. It can be understood that the first UPF entity and the first CU-UP entity in the edge relay node are "activated" by the method provided in the present application, so that the edge relay node supports local communication with the user equipment. In the IoT communication system, edge relay nodes can also function as edge computing devices, which can reduce the deployment of edge computing devices and reduce costs, as well as reduce data transmission delays.

[0097] After step 612, the edge relay node and the user equipment may perform service data transmission via the first PDU session.

[0098] In an embodiment of the present application, the first CU-UP entity includes a PDCP layer and an SDAP layer. The SDAP layer is located in the user plane and is responsible for completing the mapping from the QoS flow to the DRB; the PDCP layer provides the SDAP layer with a radio bearer-level service, and the SDAP layer provides the upper layer with a QoS flow-level service. The terminal sends data to the edge relay node, and the first CU-UP in the edge relay node is used to implement the SDAP and PDCP protocols, and SDAP is responsible for completing the mapping from the QoS flow to the radio bearer (DRB). The first UPF completes the mapping of data to the QoS flow, that is, marks the QoS flow to which the data belongs. Therefore, the first UPF and the first CU-UP jointly complete the mapping of the first service data to the radio bearer. The edge relay node processes the received data to obtain the second service data. Optionally, the edge relay node can output the second service data. For example, the edge relay node can output the second service data to a display device, display the second service data through the display device, or the edge relay node transmits the second service data to the terminal.

[0099] See also Figure 8 As shown, the present application provides another embodiment of a communication method. Figure 6 The main difference between the corresponding embodiments is that the edge relay node can realize local communication and also supports remote communication.

[0100] Step 801: The edge relay node initiates a second PDU session request to the core network device.

[0101] The edge relay node establishes its own PDU session. In order to distinguish the PDU session request initiated by the terminal, the PDU session initiated by the edge relay node is called the "second PDU session". The second PDU session request includes a remote communication type identifier (flag is set to false). The remote communication type identifier is used to indicate that the second PDU session to be established by the core network is a remote communication PDU session. The remote communication type identifier indicates that the second PDU session is a non-local communication PDU session, but supports local communication. Optionally, the second PDU session request may not carry the communication type identifier, and not carrying the communication type identifier may also indicate that the second PDU session request is a non-local communication (remote communication) PDU session request.

[0102] Step 802: The core network device allocates an IP address to the edge relay node (DLAA IAB), and stores the correspondence between the edge relay node identifier (DLAA IAB ID), the base station global identifier (global RAN ID), and the DLAA IAB IP address.

[0103] The core network device may specifically be a session management function (SMF) entity, and the SMF entity allocates an IP address to the DLAA IAB, and saves the DLAA IAB ID, and the corresponding relationship between the base station global identifier (global RAN ID) and the DLAA IAB IP address.

[0104] Step 803: The core network device selects a second UPF according to the remote communication type identifier to establish a second PDU session.

[0105] The SMF identifies the second PDU session as a remote communication PDU session according to the remote communication identifier, and then the SMF selects a second UPF deployed in the core network to establish a connection for the second PDU session between the second UPF, the base station, and the DLAA IAB. The second UPF serves the second PDU session. The second PDU session is used to carry the service data transmitted between the DLAA IAB and the core network.

[0106] In this example, the purpose of steps 801 to 803 is to establish a second PDU session between the edge relay node and the core network, and the second PDU session can be used for remote communication. The number of the second PDU session is not limited and is determined according to actual business conditions.

[0107] The next steps are the same as above Figure 6The steps in the corresponding examples are roughly the same. It can be understood that in this example, the edge relay node can realize remote communication and also support local communication through the following steps.

[0108] Step 804: The edge relay node broadcasts a system message.

[0109] See also Figure 6 The description of step 603 in the corresponding embodiment is not repeated here.

[0110] Step 805: The terminal device obtains the identifier of the edge relay node from the system message of the edge relay node, and selects a cell supporting the edge relay node (such as DLAA IAB) to reside in.

[0111] See also Figure 6 The description of step 604 in the corresponding embodiment is not repeated here.

[0112] Step 806: The terminal device initiates a first PDU session request.

[0113] See also Figure 6 The description of step 605 in the corresponding embodiment is not repeated here.

[0114] Step 807: The core network device receives a first PDU session request from the terminal device, and identifies the first PDU session as a local communication PDU session according to the local communication type.

[0115] See also Figure 6 The description of step 606 in the corresponding embodiment is not repeated here.

[0116] Step 808: The core network device searches for the IP address of the DLAA IAB based on the identifier of the edge relay node (DLAA IAB ID) and the Global RAN ID.

[0117] Step 809: The core network sends a PDR to the DLAA IAB according to the IP address of the DLAA IAB.

[0118] The core network initiates the N4 session establishment process to the DLAA IAB and provides the PDR to the DLAA IAB.

[0119] The PDR may contain information required to classify data packets. Each PDR may also be used to detect data packets in a specific transmission direction, for example, an uplink direction or a downlink direction. In this example, the DLAA IAB is used to support both local and remote communications. For example, when the DLAA IAB receives first service data sent by a user device, the second service data may be processed locally to obtain second service data. The DLAA IAB may detect, based on the PDR, which second service data needs to be processed locally, which second service data (downlink data) needs to be sent to the terminal, and which second service data (uplink data) needs to be sent to the base station.

[0120] Step 810: The core network sends a context establishment request to the access network device, where the context establishment request (initial context setup request) includes the first PDU session information.

[0121] Please refer to the description of step 607 in the embodiment corresponding to step 6, which will not be repeated here. Since in step 809, the core network device has sent the PDR to the DLAA IAB, the difference between this step and step 607 is that the first PDU session information does not include the PDR.

[0122] Step 811: The access network device selects the first CU-UP located in the DLAA IAB based on the DLAA IAB ID.

[0123] Step 812: The access network device initiates bearer establishment to the DLAA IAB, and the base station sends a bearer context setup request (bearer context setup request) to the first CU-UP.

[0124] Please refer to the description of step 609 in the embodiment corresponding to step 6, which will not be repeated here. The difference between this step and step 609 is that the bearer context setup request does not include the PDR.

[0125] Step 813: The edge relay node establishes a corresponding first DRB. The edge relay node (DLAA IAB) receives the first PDU session information through the first DRB and saves the QoS flow list.

[0126] It should be noted that steps 808 and 809 are optional steps, and the PDR may also be carried in the context establishment request in step 810, and the PDR may also be carried in step 812. There is no time sequence limitation between steps 801 to 803 and subsequent steps, for example, steps 801 to 803 may also be at any position after step 804.

[0127] Optionally, in this example, the two steps of "the edge relay node feeds back a bearer context setup response message to the base station from the access network device" and "the base station returns an initial context setup response message to the core network device".

[0128] In this example, the edge relay node can establish a second PDU session with the second UPF in the core network to support remote communication, and the user device can establish a first PDU session with the first UPF in the edge relay node to support local communication. The core network can select the first UPF to serve the first PDU session based on the local communication type identifier, and select the second UPF to serve the second PDU session based on the remote communication type identifier. For example, the user device sends the first service data to the edge relay node through the first PDU session, the edge relay node can process the first service data to obtain the second service data, and the edge relay node can send the second service data to the terminal device through local communication. At this time, the edge relay node is equivalent to an edge computing device. Alternatively, in different application scenarios, the edge relay node can also send the second service data to the Internet of Things platform through remote communication, process the second service data through the Internet of Things platform, etc. At this time, the edge relay node is equivalent to an ordinary relay node (such as IAB) and is used to implement relay forwarding functions. The terminal can initiate the establishment of a local communication PDU session or a remote communication PDU session according to business needs, or initiate the establishment of both local communication and remote communication PDU sessions at the same time. Different types of services are carried through different PDU sessions. The PDU session initiated by the terminal device for remote communication is the same as the traditional method and is not repeated here. The terminal can switch the service from remote communication to local communication, or switch local communication to remote communication as needed. In this example, the edge relay node can realize the function of local communication and can be flexibly applied to different application scenarios. The edge relay node can be used in relay forwarding scenarios as well as in edge computing application scenarios, which saves equipment costs while increasing the flexibility of application scenarios.

[0129] Corresponding to the method provided in the above method embodiment, the present application embodiment also provides a corresponding device, including a module for executing the corresponding module of the above embodiment. The module can be software, hardware, or a combination of software and hardware.

[0130] Fig. 9A schematic diagram of the structure of a communication device is given. The communication device 900 may be an edge relay node, an access network device, a core network device, or a terminal device. It may also be a chip, a chip system, or a processor that supports the edge relay node to implement the above method, or a chip, a chip system, or a processor that supports the access network device to implement the above method. It may also be a chip, a chip system, or a processor that supports the core network device to implement the above method. It may also be a chip, a chip system, or a processor that supports the terminal device to implement the above method. The communication device may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment. The communication device 900 may include one or more processors 901, which may also be called a processing unit, and may implement certain control functions. The processor 901 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and communication data, and the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal, a terminal chip, a DU or a CU, etc.), execute the software program, and process the data of the software program.

[0131] In an optional design, the processor 901 may also store instructions and / or data 903, and the instructions and / or data 903 can be executed by the processor so that the communication device 900 executes the method described in the above method embodiment.

[0132] In another optional design, the processor 901 may include a transceiver unit for implementing the receiving and sending functions. For example, the transceiver unit may be a transceiver circuit, or an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0133] In yet another possible design, the communication device 900 may include a circuit, which may implement the functions of sending, receiving, or communicating in the aforementioned method embodiments.

[0134] Optionally, the communication device 900 may include one or more memories 902, on which instructions 904 may be stored, and the instructions may be executed on the processor, so that the communication device 900 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory. Optionally, instructions and / or data may also be stored in the processor. The processor and memory may be provided separately or integrated together. For example, the corresponding relationship described in the above method embodiment may be stored in a memory or in a processor.

[0135] Optionally, the communication device 900 may further include a transceiver 905 and / or an antenna 906. The processor 901 may be referred to as a processing unit, which controls the communication device 900. The transceiver 905 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transceiver communication device or a transceiver module, etc., which is used to implement a transceiver function.

[0136] Optionally, the communication device 900 in the embodiment of the present application can be used to execute the embodiment of the present application. Figure 6 and Figure 8 The method executed by the middle-edge relay node may also be used to execute the method executed by the access network device, or may also be used to execute the method executed by the core network device, or may also be used to execute the method executed by the terminal.

[0137] like Fig.10 As shown, another embodiment of the present application provides a communication device 1000. The communication device can be a terminal, or a component of a terminal (for example, an integrated circuit, a chip, etc.). Alternatively, the communication device can be an edge relay node, or a component of an edge relay node (for example, an integrated circuit, a chip, etc.). Alternatively, the communication device can be an access network device, or a component of an access network device (for example, an integrated circuit, a chip, etc.). The communication device can be a core network device, or a component of a core network device (for example, an integrated circuit, a chip, etc.). The communication device can also be other communication modules for implementing the method in the method embodiment of the present application. The communication device 1000 may include: a processing module 1002 (or referred to as a processing unit) and a transceiver module 1001 (or referred to as a transceiver unit).

[0138] In one possible design, Fig.10 One or more modules in the may be implemented by one or more processors, or by one or more processors and memories; or by one or more processors and transceivers; or by one or more processors, memories and transceivers, which are not limited in the embodiments of the present application. The processor, memory, and transceiver may be provided separately or integrated.

[0139] The communication device has the function of implementing the edge relay node described in the embodiment of the present application. For example, the communication device includes a module or unit or means corresponding to the steps involved in the edge relay node described in the embodiment of the present application, and the function or unit or means can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. Alternatively, the communication device has the function of implementing the access network device described in the embodiment of the present application. For example, the communication device includes the module or unit or means corresponding to the steps involved in the network device described in the embodiment of the present application, and the function or unit or means can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. Alternatively, the communication device has the function of implementing the access network device described in the embodiment of the present application. Alternatively, the communication device has the function of implementing the core network device described in the embodiment of the present application. For example, the communication device includes a module or unit or means corresponding to the steps involved in the network device described in the embodiment of the present application for the core network device to execute. The function or unit or means can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. For details, please refer to the corresponding description in the aforementioned corresponding method embodiment.

[0140] Optionally, each module in the communication device 1000 in the embodiment of the present application can be used to execute the embodiment of the present application. Figure 6 and Figure 8 The method performed by the middle edge relay node.

[0141] In one possible design, a communication device 1000 may include: a processing module 1002 and a transceiver module 1001.

[0142] Specifically, the transceiver module 1001 is configured to send an identifier of an edge relay node to an access network device, so that the access network device selects a first CU-UP entity according to the identifier of the edge relay node, and establishes a first DRB between the access network device and the CU-UP entity;

[0143] The transceiver module 1001 is also used to receive the first PDU session information from the core network through the first DRB, and the first PDU session information is used to serve the first PDU session; wherein, the first PDU session is established by: after the terminal device initiates a first PDU session request to the core network, the core network selects the first UPF entity based on the local communication type identifier and the identifier of the edge relay node; wherein, the first PDU session request includes the identifier of the edge relay node and the local communication type identifier; the first PDU session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

[0144] Optionally, the transceiver module 1001 is also used to initiate a second PDU session request to the core network to establish a second PDU session; the second PDU session request includes a remote communication type identifier; the remote communication type identifier is used to instruct the core network to select a second UPF entity for the second PDU session to be established, and the second UPF entity is a UPF entity deployed in the core network; the second UPF entity is used to serve the second PDU session.

[0145] Optionally, the transceiver module 1001 is also used to transmit business data between the edge relay node and the terminal device through the first PDU session.

[0146] Optionally, the first PDU session information includes a quality of service QoS flow list;

[0147] The transceiver module 1001 is further configured to receive first service data sent by a terminal device;

[0148] The processing module 1002 is configured to map the first service data to the corresponding QoS flow based on the first PDU session information through the first UPF and the CU-UP;

[0149] The transceiver module 1001 is further used to transmit second service data according to the mapping relationship between the first service data and the QoS flow, where the second service data is service data obtained according to the first service data.

[0150] Optionally, the transceiver module 1001 is further used to broadcast a system message, where the system message includes an identifier of the edge relay node, so that the terminal device receives the identifier of the edge relay node.

[0151] Optionally, the edge relay node is a power line communication PLC central coordinator, and the identifier of the edge relay node is a PLC network identifier NID.

[0152] Optionally, the first PDU session information includes a second DRB list, and the QoS flow and packet detection rule PDR corresponding to each second DRB in the second DRB list; the second DRB is the bearer between the terminal device and the edge relay node.

[0153] Optionally, each module in the communication device 1000 in the embodiment of the present application can be used to execute the embodiment of the present application. Figure 6 and Figure 8 A method executed by an access network device.

[0154] The transceiver module 1001 is used to receive an identifier of an edge relay node sent by a terminal device; wherein the edge relay node includes a first UPF entity and a first CU-UP entity;

[0155] The transceiver module 1001 is also used to receive a first PDU session request initiated by a terminal device, and forward the first PDU session request to a core network device, where the first PDU session request includes an identifier of an edge relay node and a local communication type identifier; the local communication type is used by the core network device to select a first UPF according to the identifier of the relay node to establish a first PDU session;

[0156] The transceiver module 1001 is further configured to receive the first PDU session information and the identifier of the edge relay node sent by the core network;

[0157] The processing module 1002 is configured to select a first CU-UP to establish a first DRB according to the ID of the edge relay node received by the transceiver module 1001;

[0158] The transceiver module 1001 is used to send the first PDU session information to the edge relay node through the first DRB established by the processing module 1002. The first UPF entity is used to serve the PDU session according to the first PDU session information. The first PDU session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

[0159] Optionally, the transceiver module 1001 is also used to receive a second PDU session request initiated by the edge relay node, and forward the second PDU session request to the core network, wherein the second PDU session request includes an identifier of the edge relay node and a remote communication type identifier; so that the core network selects a second UPF entity to establish a second PDU session for the edge relay node.

[0160] Optionally, each module in the communication device 1000 in the embodiment of the present application can be used to execute the embodiment of the present application. Figure 6 and Figure 8 A method executed by a core network device in the network.

[0161] The transceiver module 1001 is configured to receive a first PDU session request sent by an access network device, where the first PDU session request includes an identifier of an edge relay node and a local communication type identifier; the edge relay node includes a first CU-UP entity and a first UPF entity;

[0162] The processing module 1002 is used to select a first UPF entity in the edge relay node to establish a first PDU session according to the local communication type identifier received by the transceiver module 1001;

[0163] The transceiver module 1001 is used to send the first PDU session information to the access network device, and the first PDU session information includes the identifier of the edge relay node; so that the access network device selects the first CU-UP entity according to the identifier of the edge relay node to establish a first DRB, and sends the first PDU session information to the edge relay node through the first DRB, the first UPF entity is used to serve the PDU session according to the first PDU session information, and the first PDU session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

[0164] Optionally, the transceiver module 1001 is further configured to receive a second PDU session request initiated by the edge relay node, where the second PDU session request includes an identifier of the edge relay node and a remote communication type identifier;

[0165] The processing module 1002 is also used to select a second UPF entity according to the remote communication type identifier received by the transceiver module 1001 to establish a second PDU session, and the second UPF entity is a UPF entity deployed in the core network; the second UPF entity is used to serve the second PDU session, and the second PDU session is used to carry the business data to be transmitted between the edge relay node and the core network device.

[0166] Optionally, the transceiver module 1001 is used to send a PDR to an edge relay node.

[0167] The present application also provides a computer-readable medium having a computer program stored thereon, which, when executed by a computer, implements the function of the edge relay node in any of the above method embodiments. Alternatively, when executed by a computer, the computer program implements the function of the access network device in any of the above method embodiments. Alternatively, when executed by a computer, the computer program implements the function of the core network device in any of the above method embodiments.

[0168] The present application also provides a computer program product, which, when executed by a computer, implements the function of the edge relay node in any of the above method embodiments. Alternatively, when the computer program is executed by a computer, it implements the function of the access network device in any of the above method embodiments. Alternatively, when the computer program is executed by a computer, it implements the function of the core network device in any of the above method embodiments.

[0169] Those skilled in the art can also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art can use various methods to implement the functions for corresponding applications, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.

[0170] It is understood that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0171] In another possible design, when the device is a chip in a terminal, the chip includes: a processing unit and a communication unit, the processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, a pin or a circuit, etc. The processing unit may execute the computer execution instructions stored in the storage unit so that the chip in the terminal executes the wireless communication method of any one of the above-mentioned first aspects. Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the terminal, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc. Among them, the processor mentioned in any of the above places may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the wireless communication method of the first aspect.

[0172] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0173] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method, characterized in that: Applied to an edge relay node, the edge relay node comprises a first centralized unit user plane entity and a first user plane function entity; Sending the identifier of the edge relay node to the access network device, so that the access network device selects the first centralized unit user plane entity according to the identifier of the edge relay node, and establishes a first data bearer between the access network device and the first centralized unit user plane entity; The first protocol data unit session information is received from the core network device through the first data bearer, and the first protocol data unit session information is used to serve the first protocol data unit session; wherein the first protocol data unit session is established by: after the terminal device initiates a first protocol data unit session request to the core network, the core network device selects the first user plane functional entity according to the local communication type identifier and the identifier of the edge relay node; wherein the first protocol data unit session request includes the identifier of the edge relay node and the local communication type identifier; the first protocol data unit session is used to carry the service data to be transmitted between the edge relay node and the terminal device.

2. The method according to claim 1, characterized in that The method further comprises: A second protocol data unit session request is initiated to the core network to establish a second protocol data unit session; the second protocol data unit session request includes a remote communication type identifier; the remote communication type identifier is used to instruct the core network device to select a second user plane function entity deployed in the core network to establish a second protocol data unit session; the second user plane function entity is used to serve the second protocol data unit session.

3. The method according to claim 1, characterized in that After receiving the first protocol data unit session information from the core network device, the method further includes: The service data between the edge relay node and the terminal device is carried through the first protocol data unit session.

4. The method according to claim 3, characterized in that The first protocol data unit session information includes a service quality flow list, and the carrying of service data between the edge relay node and the terminal device through the first protocol data unit session includes: Receiving first service data sent by a terminal device; Mapping the first service data to the corresponding quality of service flow based on the first protocol data unit session information through the first user plane function entity and the first centralized unit user plane entity; According to the mapping relationship between the first service data and the service quality flow, the second service data is transmitted, where the second service data is service data obtained according to the first service data.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: A system message is broadcast, where the system message includes the identifier of the edge relay node, so that the terminal device receives the identifier of the edge relay node.

6. The method according to any one of claims 1 to 4, characterized in that The edge relay node is a power line communication central coordinator, and the identifier of the edge relay node is a power line communication network identifier.

7. The method according to any one of claims 1 to 4, characterized in that The first protocol data unit session information includes a second data bearer list, and a service quality flow and a packet detection rule corresponding to each second data bearer in the second data bearer list; the second data bearer is a bearer between the terminal device and the edge relay node.

8. A communication method, characterized in that: Applied to access network equipment, the method comprises: Receiving an identifier of an edge relay node sent by a terminal device; wherein the edge relay node includes a first user plane function entity and a first centralized unit user plane entity; receiving a first protocol data unit session request initiated by a terminal device, and forwarding the protocol data unit session request to a core network device, wherein the first protocol data unit session request includes an identifier of the edge relay node and a local communication type identifier; the local communication type is used to instruct the core network device to select the first user plane function entity according to the identifier of the relay node to establish a first protocol data unit session; Receiving the first protocol data unit session information and the identifier of the edge relay node sent by the core network device; Selecting the first centralized unit user plane entity to establish a first data bearer according to the identifier of the edge relay node; The first protocol data unit session information is sent to the edge relay node via the first data bearer, the first user plane function entity is used to serve the protocol data unit session according to the first protocol data unit session information, and the first protocol data unit session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

9. The method according to claim 8, characterized in that The first protocol data unit session information includes a second data bearer list, and a service quality flow and a packet detection rule corresponding to each second data bearer in the second data bearer list; the second data bearer is a bearer between the terminal device and the edge relay node.

10. The method according to claim 8 or 9, characterized in that: The method further comprises: Receive a second protocol data unit session request initiated by the edge relay node, and forward the second protocol data unit session request to the core network, wherein the second protocol data unit session request includes an identifier of the edge relay node and a remote communication type identifier; the remote communication type identifier is used to instruct the core network device to select a second user plane functional entity to establish a second protocol data unit session.

11. A communication method, characterized in that: Applied to core network equipment, including: receiving a first protocol data unit session request from a terminal device, wherein the first protocol data unit session request includes an identifier of an edge relay node and a local communication type identifier; the edge relay node includes a first centralized unit user plane entity and a first user plane function entity; Selecting a first user plane function entity in the edge relay node according to the local communication type identifier to establish a first protocol data unit session; Sending first protocol data unit session information to an access network device, wherein the first protocol data unit session information includes an identifier of an edge relay node; so that the access network device selects the first centralized unit user plane entity according to the identifier of the edge relay node to establish a first data bearer, and sends the first protocol data unit session information to the edge relay node through the first data bearer, the first protocol data unit session information is used by the first user plane function entity to serve the first protocol data unit session, and the first protocol data unit session is used to carry business data to be transmitted between the edge relay node and the terminal device.

12. The method according to claim 11, characterized in that The method further comprises: receiving a second protocol data unit session request initiated by the edge relay node, wherein the second protocol data unit session request includes an identifier of the edge relay node and a remote communication type identifier; A second user plane function entity deployed in the core network is selected according to the remote communication type identifier to establish a second protocol data unit session, wherein the second user plane function entity is used to serve the second protocol data unit session, and the second protocol data unit session is used to carry business data to be transmitted between the edge relay node and the core network device.

13. The method according to claim 12, characterized in that The method further comprises: Send packet detection rules to edge relay nodes.

14. A communication device, characterized in that: The device integrates a first centralized unit user plane entity and a first user plane functional entity; the device also includes: A transceiver module, configured to send an identifier of an edge relay node to an access network device, so that the access network device selects the first centralized unit user plane entity according to the identifier of the edge relay node, and establishes a first data bearer between the access network device and the first centralized unit user plane entity; The transceiver module is also used to receive first protocol data unit session information from the core network through the first data bearer, and the first protocol data unit session information is used to serve the first protocol data unit session; wherein, the first protocol data unit session is established by: after the terminal device initiates a first protocol data unit session request to the core network, the core network device selects the first user plane functional entity according to the local communication type identifier and the identifier of the edge relay node; wherein, the first protocol data unit session request includes the identifier of the edge relay node and the local communication type identifier; the first protocol data unit session is used to carry the service data to be transmitted between the edge relay node and the terminal device.

15. The device according to claim 14, characterized in that The transceiver module is further used to initiate a second protocol data unit session request to the core network to establish a second protocol data unit session; the second protocol data unit session request includes a remote communication type identifier; the remote communication type identifier is used by the core network to select a second user plane function entity deployed in the core network for the second protocol data unit session to be established, so as to establish the second protocol data unit session; The second user plane function entity is used to serve the second protocol data unit session.

16. The device according to claim 14, characterized in that The transceiver module is also used to carry the business data between the edge relay node and the terminal device through the first protocol data unit session.

17. The device according to claim 16, characterized in that The first protocol data unit session information includes a quality of service flow list, and the apparatus further includes a processing module; The transceiver module is further used to receive the first service data sent by the terminal device; The processing module is used to map the first service data to the corresponding quality of service flow based on the first protocol data unit session information through the first user plane function and the first centralized unit user plane; The transceiver module is further used to transmit second service data according to the mapping relationship between the first service data and the service quality flow, where the second service data is service data obtained according to the first service data.

18. The device according to any one of claims 14 to 17, characterized in that The transceiver module is further used to broadcast a system message, wherein the system message includes an identifier of the edge relay node, so that the terminal device receives the identifier of the edge relay node.

19. The device according to any one of claims 14 to 17, characterized in that The edge relay node is a power line communication central coordinator, and the identifier of the edge relay node is a power line communication network identifier.

20. The device according to any one of claims 14 to 17, characterized in that The first protocol data unit session information includes a second data bearer list, and a service quality flow and a packet detection rule corresponding to each second data bearer in the second data bearer list; the second data bearer is a bearer between the terminal device and the edge relay node.

21. A communication device, characterized in that: include: A transceiver module, configured to receive an identifier of an edge relay node sent by a terminal device; wherein the edge relay node includes a first user plane function entity and a first centralized unit user plane entity; The transceiver module is further used to receive a first protocol data unit session request initiated by a terminal device, and forward the protocol data unit session request to the core network, wherein the first protocol data unit session request includes an identifier of the edge relay node and a local communication type identifier; the local communication type is used to instruct the core network device to select the first user plane function according to the identifier of the relay node to establish a first protocol data unit session; The transceiver module is further used to receive the first protocol data unit session information and the identifier of the edge relay node sent by the core network device; A processing module, configured to select the first centralized unit user plane entity to establish a first data bearer according to the identifier of the edge relay node received by the transceiver module; The transceiver module is used to send the first protocol data unit session information to the edge relay node through the first data bearer established by the processing module, the first user plane function entity is used to serve the protocol data unit session according to the first protocol data unit session information, and the first protocol data unit session is used to carry the business data to be transmitted between the edge relay node and the terminal device.

22. The device according to claim 21, characterized in that The transceiver module is also used to receive a second protocol data unit session request initiated by the edge relay node, and forward the second protocol data unit session request to the core network device, wherein the second protocol data unit session request includes an identifier of the edge relay node and a remote communication type identifier; the remote communication type identifier is used to instruct the core network device to select a second user plane function entity to establish a second protocol data unit session.

23. A communication device, characterized in that: include: A transceiver module, configured to receive a first protocol data unit session request sent by an access network device, wherein the first protocol data unit session request includes an identifier of an edge relay node and a local communication type identifier; the edge relay node includes a first centralized unit user plane entity and a first user plane function entity; A processing module, configured to select a first user plane function entity in the edge relay node according to the local communication type identifier received by the transceiver module to establish a first protocol data unit session; A transceiver module, configured to send first protocol data unit session information to an access network device, wherein the first protocol data unit session information includes an identifier of an edge relay node; So that the access network device selects the first centralized unit user plane entity according to the identifier of the edge relay node to establish a first data bearer, and sends the first protocol data unit session information to the edge relay node through the first data bearer, the first protocol data unit session information is used by the first user plane function entity to serve the first protocol data unit session, and the first protocol data unit session is used to carry the service data to be transmitted between the edge relay node and the terminal device.

24. The device according to claim 23, characterized in that The transceiver module is further configured to receive a second protocol data unit session request initiated by the edge relay node, wherein the second protocol data unit session request includes an identifier of the edge relay node and a remote communication type identifier; The processing module is also used to select a second user plane function entity according to the remote communication type identifier received by the transceiver module to establish a second protocol data unit session, the second user plane function entity is a user plane function entity deployed in the core network; the second user plane function entity is used to serve the second protocol data unit session, and the second protocol data unit session is used to carry the business data to be transmitted between the edge relay node and the core network device.

25. The device according to claim 24, characterized in that The transceiver module is used to send the packet detection rule to the edge relay node.

26. A communication device, characterized in that: The device comprises a processor coupled to at least one memory, wherein the processor is used to read a computer program stored in the at least one memory, so that the device executes the method described in any one of claims 1 to 7, or the method described in any one of claims 8 to 10, or the method described in any one of claims 11 to 13.

27. A computer readable medium, characterized in that The computer-readable storage medium is used to store a computer program. When the computer program is run on a computer, the computer executes the method as described in any one of claims 1 to 7; or, the computer executes the method as described in any one of claims 8 to 10; or, the computer executes the method as described in any one of claims 11 to 13.

28. A communication device, characterized in that: include: A unit that performs the method according to any one of claims 1 to 7, or a unit that performs the method according to any one of claims 8 to 10, or a unit that performs the method according to any one of claims 11 to 13.

29. A computer program product, characterized in that The computer program product contains computer-readable instructions, which, when executed by a processor, implement the method described in any one of claims 1 to 7; or, implement the method described in any one of claims 8 to 10; or, implement the method described in any one of claims 11 to 13.

Images