Relay management method and communication device

Abstract

The embodiment of the present application provides a relay management method and communication device, which relates to the field of communications. The network side can control the relay services requested by the remote device to prevent the remote device from excessively occupying relay resources and wireless resources. It includes: the network device obtains the identification of the first terminal device, and obtains the relay restriction information of the first terminal device according to the identification of the first terminal device; the relay restriction information is used to indicate the number of relay devices to which the first terminal device can be connected, and / or the aggregate maximum bit rate AMBR that the first terminal device can use for relaying; the network device determines whether to allow the first terminal device to access the network through the second terminal device according to the relay restriction information of the first terminal device; the second terminal device is a relay device of the first terminal device.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and in particular to a relay management method and a communication device. Background Art

[0002] In a communications network, a terminal device connected to a cellular network (referred to as a relay terminal device) can provide greater network coverage for the cellular network through a direct interface (e.g., a PC5 interface) with other terminal devices. For example, a remote device establishes a packet data unit (PDU) session, and the relay device uses the PDU session established by the remote device to provide relay services to the remote device. Alternatively, the relay device establishes a PDU session to provide relay services to the remote device.

[0003] In the above relay scenario, after the network side receives the relay service request from the remote device, it allocates relay resources to the remote device, but is unable to manage the relay service of the remote device. As a result, a remote device may occupy excessive relay resources and wireless resources. Summary of the Invention

[0004] The embodiments of the present application provide a relay management method and a communication device, by which the network side can manage and control the relay services requested by the remote device to prevent the remote device from excessively occupying relay resources and wireless resources.

[0005] In a first aspect, a relay management method is provided, including: a network device obtains an identifier of a first terminal device, and obtains relay restriction information of the first terminal device based on the identifier of the first terminal device; the relay restriction information is used to indicate the number of relay devices to which the first terminal device can be connected, and / or the aggregate maximum bit rate AMBR that the first terminal device can use for relaying; the network device can also determine whether to allow the first terminal device to access the network through a second terminal device based on the relay restriction information of the first terminal device; the second terminal device is a relay device of the first terminal device.

[0006] An embodiment of the present application provides a relay management method for configuring relay restriction information for a remote UE (e.g., a first terminal device in an embodiment of the present application) to indicate the number of relay devices (relay UEs) to which the remote UE can connect, and / or the AMBR that the remote UE can use for relaying. Whether the remote UE is allowed to connect to the core network through a certain relay UE can be determined based on the relay restriction information of the remote UE. When the number of relay devices connected to the remote UE reaches an upper limit, or the AMBR used by the remote UE for relaying reaches an upper limit, the remote UE's relay service request is rejected.

[0007] In combination with the first aspect, in a first possible implementation of the first aspect, the network device obtains the identifier of the first terminal device, including: the network device receives a first message from the first terminal device, the first message includes the identifier of the first terminal device and the identifier of the second terminal device, or the first message includes the identifier of the second terminal device, and the first message is used to represent that the first terminal device requests to access the network through the second terminal device.

[0008] In the present application, the remote UE can initiate a relay service request, and the network device receives a message (for example, a first message) in which the remote UE initiates a relay service, and can obtain the identifier of the remote UE, thereby obtaining the relay restriction information of the remote UE based on the identifier of the remote UE, so as to manage and control the relay service request of the remote UE and prevent the remote UE from occupying too many relay resources.

[0009] In combination with the first aspect, in a second possible implementation of the first aspect, the network device obtains the identifier of the first terminal device, including: the network device receives a first message from the second terminal device, the first message includes the identifier of the first terminal device and the identifier of the second terminal device, or the first message includes the identifier of the first terminal device, and the first message is used to represent that the first terminal device requests to access the network through the second terminal device.

[0010] In this application, a relay service request can be initiated by a relay UE. The message (e.g., a first message) in which the relay UE initiates the relay service includes the identifier of the remote UE. Upon receiving the message, the network device can obtain the identifier of the remote UE and, based on the identifier of the remote UE, obtain the relay restriction information of the remote UE to manage and control the relay service request of the remote UE and prevent the remote UE from occupying too many relay resources.

[0011] In combination with the first or second possible implementation of the first aspect, in a third possible implementation of the first aspect, the network device obtains the relay restriction information of the first terminal device based on the identifier of the first terminal device, including: sending a second message to a unified data management network element or a unified data storage network element in response to the first message; the second message is used to request the relay restriction information of the first terminal device, and the second message includes the identifier of the first terminal device; and receiving the relay restriction information of the first terminal device from the unified data management network element or the unified data storage network element.

[0012] This application provides a specific implementation method for a network device to obtain relay restriction information. A unified data management network element or a unified data storage network element can maintain the UE's subscription information, which includes the relay restriction information.

[0013] In combination with the first aspect or any one of the first to third possible implementations of the first aspect, in the fourth possible implementation of the first aspect, the network device determines whether to allow the first terminal device to access the network through the second terminal device based on the relay restriction information of the first terminal device, including: if the number of relay devices currently connected to the first terminal device does not exceed the number of relay devices that the first terminal device can connect to, allowing the first terminal device to access the network through the second terminal device; if the number of relay devices currently connected to the first terminal device is equal to the number of relay devices that the first terminal device can connect to, denying the first terminal device from accessing the network through the second terminal device; and / or, if the AMBR currently used for relaying by the first terminal device does not exceed the AMBR that the first terminal device can use for relaying, allowing the first terminal device to access the network through the second terminal device; if the AMBR currently used for relaying by the first terminal device is equal to the AMBR that the first terminal device can use for relaying, denying the first terminal device from accessing the network through the second terminal device.

[0014] This application provides a specific implementation method for determining whether a first terminal device is allowed to access a network through a second terminal device based on the relay restriction information of the first terminal device. It determines whether the current relay status of the first terminal device (for example, the number of connected relay devices, or the AMBR used for relay) exceeds an upper limit. If it does not exceed the upper limit, the first terminal device's current relay service request is allowed.

[0015] In combination with the fourth possible implementation manner of the first aspect, in the fifth possible implementation manner of the first aspect, the method also includes: the network device obtains the number of relay devices currently connected to the first terminal device from a unified data management network element or a unified data storage network element, and / or the AMBR currently used for relaying by the first terminal device.

[0016] This application provides a specific implementation for obtaining the current relay status of the remote UE. The current relay status of the remote UE can be obtained from a unified data management network element or a unified data storage network element, for example, the number of relay devices currently connected to the first terminal device, and / or the AMBR currently used for relay by the first terminal device.

[0017] In combination with the fourth or fifth possible implementation manner of the first aspect, in the sixth possible implementation manner of the first aspect, the method also includes: if the first terminal device is allowed to access the network through the second terminal device, the network device updates the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device; and sends the updated number of relay devices currently connected to the first terminal device and / or the updated AMBR currently used for relaying by the first terminal device to the unified data management network element or the unified data storage network element.

[0018] In this application, after allowing the remote UE to access the network through the relay device, the network device can also update the current relay status of the remote UE. After the remote UE subsequently initiates a new relay service request, it can be determined whether the remote UE is allowed to establish a non-direct connection with the network through the new relay device based on the remote UE's relay status and the remote UE's relay restriction information.

[0019] In combination with the fourth or fifth possible implementation manner of the first aspect, in the seventh possible implementation manner of the first aspect, the method also includes: if the network device allows the first terminal device to access the network through the second terminal device, it sends a third message to the unified data management network element or the unified data storage network element, so that the unified data management network element or the unified data storage network element updates the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device according to the third message. The third message is used to characterize that the network device allows the first terminal device to access the network through the second terminal device.

[0020] In this application, after allowing the remote UE to access the network through the relay device, the network device can also instruct the UDM / UDR to update the current relay status of the remote UE. After the remote UE subsequently initiates a new relay service request, it can be determined whether the remote UE is allowed to establish a non-direct connection with the network through the new relay device based on the relay status of the remote UE and the relay restriction information of the remote UE.

[0021] In combination with the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the third message includes an identifier of the second terminal device.

[0022] In this application, the UDM / UDR may also be instructed to store the identifier of the relay device to which the remote UE is currently connected.

[0023] In combination with the fourth or fifth possible implementation of the first aspect, in the ninth possible implementation of the first aspect, the method further includes: if the network device denies the first terminal device from accessing the network through the second terminal device, sending a fourth message to the first terminal device or the second terminal device; the fourth message is used to characterize that the network device denies the first terminal device from accessing the network through the second terminal device.

[0024] In this application, the network device may also notify the device that initiated the relay service that the relay service is rejected.

[0025] In combination with the ninth possible implementation manner of the first aspect, in the tenth possible implementation manner of the first aspect, the fourth message includes a failure reason value; the failure reason value is used to characterize that the failure reason is that the number of relay devices currently connected to the first terminal device is equal to the number of relay devices to which the first terminal device can be connected, or the AMBR currently used for relaying by the first terminal device is equal to the AMBR that the first terminal device can use for relaying.

[0026] In the present application, the network device may also indicate to the device that initiated the relay service the reason why the relay service was rejected.

[0027] In combination with the first aspect or any one of the first to tenth possible implementations of the first aspect, in the eleventh possible implementation of the first aspect, the relay restriction information includes first relay restriction information and second relay restriction information; the first relay restriction information includes the number of relay devices that can be connected when the first terminal device performs the first service, and / or, the AMBR that can be used for relaying when the first terminal device performs the first service; the second relay restriction information includes the number of relay devices that can be connected when the first terminal device performs the second service, and / or, the AMBR that can be used for relaying when the first terminal device performs the second service.

[0028] In this application, different relay restriction information can also be configured for different services of the remote UE, which is applicable to different service scenarios.

[0029] In combination with the first aspect or any one of the first to eleventh possible implementations of the first aspect, in the twelfth possible implementation of the first aspect, the network device is an access mobility management network element of the first terminal device, or a session management network element of the first terminal device, or an access mobility management network element of the second terminal device, or a session management network element of the second terminal device.

[0030] This application also provides a specific implementation of the network device.

[0031] In the second aspect, a relay management method is provided, including: UDM / UDR receives a second message from a network device; the second message is used to request relay restriction information of a first terminal device, and the second message includes an identifier of the first terminal device; the relay restriction information of the first terminal device is sent to the network device; the relay restriction information is used to indicate the number of relay devices to which the first terminal device can be connected, and / or the aggregate maximum bit rate AMBR that the first terminal device can use for relaying.

[0032] In combination with the second aspect, in a first possible implementation of the second aspect, the method further includes: sending to the network device the number of relay devices to which the first terminal device is currently connected, and / or the AMBR currently used for relaying by the first terminal device.

[0033] In combination with the second aspect or the first possible implementation of the second aspect, in the second possible implementation of the second aspect, the method also includes: receiving from the network device an updated number of relay devices to which the first terminal device is currently connected and / or an updated AMBR that the first terminal device is currently using for relaying.

[0034] In combination with the second aspect or the first possible implementation of the second aspect, in the second possible implementation of the second aspect, the method also includes: receiving a third message from the network device, the third message being used to characterize that the network device allows the first terminal device to access the network through the second terminal device; in response to the third message, updating the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device.

[0035] According to a third aspect, a communication device is provided, which may be the network device or a component of the network device described above. The device includes: a processing unit configured to obtain an identifier of a first terminal device and, based on the identifier of the first terminal device, obtain relay restriction information for the first terminal device; the relay restriction information indicates the number of relay devices to which the first terminal device can connect and / or the aggregate maximum bit rate (AMBR) that the first terminal device can use for relaying; and the processing unit is further configured to determine, based on the relay restriction information of the first terminal device, whether to allow the first terminal device to access the network through a second terminal device; the second terminal device being a relay device for the first terminal device.

[0036] In combination with the third aspect, in a first possible implementation of the third aspect, the communication device also includes a communication unit, and the processing unit is used to receive a first message from the first terminal device through the communication unit, the first message including an identifier of the first terminal device and an identifier of the second terminal device, or the first message including an identifier of the second terminal device, and the first message is used to characterize that the first terminal device requests to access the network through the second terminal device.

[0037] In the present application, a relay service request can be initiated by a remote UE, and the communication device receives a message (for example, a first message) in which the remote UE initiates a relay service, and can obtain an identifier of the remote UE, thereby obtaining the relay restriction information of the remote UE based on the identifier of the remote UE, so as to manage and control the relay service request of the remote UE and prevent the remote UE from occupying too many relay resources.

[0038] In combination with the third aspect, in a second possible implementation of the third aspect, the communication device obtains the identification of the first terminal device, including: the processing unit receives a first message from the second terminal device through the communication unit, the first message includes the identification of the first terminal device and the identification of the second terminal device, or the first message includes the identification of the first terminal device, and the first message is used to represent that the first terminal device requests to access the network through the second terminal device.

[0039] In this application, a relay service request can be initiated by a relay UE. The message (e.g., a first message) in which the relay UE initiates the relay service includes the identifier of the remote UE. Upon receiving the message, the communication device can obtain the identifier of the remote UE and, based on the identifier of the remote UE, obtain the relay restriction information of the remote UE to manage and control the relay service request of the remote UE and prevent the remote UE from excessively occupying relay resources.

[0040] In combination with the first or second possible implementation method of the third aspect, in the third possible implementation method of the third aspect, obtaining the relay restriction information of the first terminal device based on the identification of the first terminal device includes: the processing unit responds to the first message, sending a second message to the unified data management network element or the unified data storage network element through the communication unit; the second message is used to request the relay restriction information of the first terminal device, and the second message includes the identification of the first terminal device; and receiving the relay restriction information of the first terminal device from the unified data management network element or the unified data storage network element.

[0041] In this application, a specific implementation method for a communication device to obtain relay restriction information is provided. A unified data management network element or a unified data storage network element can maintain the subscription information of a UE, and the subscription information of the UE includes relay restriction information.

[0042] In combination with the third aspect or any one of the first to third possible implementations of the third aspect, in the fourth possible implementation of the third aspect, whether the first terminal device is allowed to access the network through the second terminal device is determined based on the relay restriction information of the first terminal device, including: if the number of relay devices currently connected to the first terminal device does not exceed the number of relay devices that the first terminal device can connect to, the processing unit allows the first terminal device to access the network through the second terminal device; if the number of relay devices currently connected to the first terminal device is equal to the number of relay devices that the first terminal device can connect to, the processing unit denies the first terminal device from accessing the network through the second terminal device; and / or, if the AMBR currently used for relaying by the first terminal device does not exceed the AMBR that the first terminal device can use for relaying, the processing unit allows the first terminal device to access the network through the second terminal device; if the AMBR currently used for relaying by the first terminal device is equal to the AMBR that the first terminal device can use for relaying, the processing unit denies the first terminal device from accessing the network through the second terminal device.

[0043] This application provides a specific implementation method for determining whether a first terminal device is allowed to access a network through a second terminal device based on the relay restriction information of the first terminal device. It determines whether the current relay status of the first terminal device (for example, the number of connected relay devices, or the AMBR used for relay) exceeds an upper limit. If it does not exceed the upper limit, the first terminal device's current relay service request is allowed.

[0044] In combination with the fourth possible implementation method of the third aspect, in the fifth possible implementation method of the third aspect, the processing unit obtains the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device from the unified data management network element or the unified data storage network element through the communication unit.

[0045] This application provides a specific implementation for obtaining the current relay status of the remote UE. The current relay status of the remote UE can be obtained from a unified data management network element or a unified data storage network element, for example, the number of relay devices currently connected to the first terminal device, and / or the AMBR currently used for relay by the first terminal device.

[0046] In combination with the fourth or fifth possible implementation manner of the third aspect, in the sixth possible implementation manner of the third aspect, the method also includes: if the first terminal device is allowed to access the network through the second terminal device, the processing unit updates the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device; the processing unit sends the updated number of relay devices currently connected to the first terminal device and / or the updated AMBR currently used for relaying by the first terminal device to the unified data management network element or the unified data storage network element through the communication unit.

[0047] In this application, after allowing the remote UE to access the network through the relay device, the communication device can also update the current relay status of the remote UE. After the remote UE subsequently initiates a new relay service request, it can be determined whether the remote UE is allowed to establish a non-direct connection with the network through the new relay device based on the relay status of the remote UE and the relay restriction information of the remote UE.

[0048] In combination with the fourth or fifth possible implementation manner of the third aspect, in the seventh possible implementation manner of the third aspect, if the first terminal device is allowed to access the network through the second terminal device, the processing unit sends a third message to the unified data management network element or the unified data storage network element, so that the unified data management network element or the unified data storage network element updates the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device according to the third message. The third message is used to characterize that the communication device allows the first terminal device to access the network through the second terminal device.

[0049] In this application, after allowing the remote UE to access the network through the relay device, the communication device can also instruct the UDM / UDR to update the current relay status of the remote UE. After the remote UE subsequently initiates a new relay service request, it can be determined whether the remote UE is allowed to establish a non-direct connection with the network through the new relay device based on the relay status of the remote UE and the relay restriction information of the remote UE.

[0050] In combination with the seventh possible implementation manner of the third aspect, in an eighth possible implementation manner of the third aspect, the third message includes an identifier of the second terminal device.

[0051] In this application, the UDM / UDR may also be instructed to store the identifier of the relay device to which the remote UE is currently connected.

[0052] In combination with the fourth or fifth possible implementation of the third aspect, in the ninth possible implementation of the third aspect, if the first terminal device is denied access to the network through the second terminal device, the processing unit sends a fourth message to the first terminal device or the second terminal device through the communication unit; the fourth message is used to indicate that the communication device denies the first terminal device access to the network through the second terminal device.

[0053] In the present application, the communication device may also notify the device initiating the relay service that the relay service is rejected.

[0054] In combination with the ninth possible implementation manner of the third aspect, in the tenth possible implementation manner of the third aspect, the fourth message includes a failure reason value; the failure reason value is used to characterize that the failure reason is that the number of relay devices currently connected to the first terminal device is equal to the number of relay devices to which the first terminal device can be connected, or the AMBR currently used for relaying by the first terminal device is equal to the AMBR that the first terminal device can use for relaying.

[0055] In the present application, the communication device may also indicate to the device that initiated the relay service the reason why the relay service was rejected.

[0056] In combination with the third aspect or any one of the first to tenth possible implementations of the third aspect, in the eleventh possible implementation of the third aspect, the relay restriction information includes first relay restriction information and second relay restriction information; the first relay restriction information includes the number of relay devices that can be connected when the first terminal device performs the first service, and / or, the AMBR that can be used for relaying when the first terminal device performs the first service; the second relay restriction information includes the number of relay devices that can be connected when the first terminal device performs the second service, and / or, the AMBR that can be used for relaying when the first terminal device performs the second service.

[0057] In this application, different relay restriction information can also be configured for different services of the remote UE, which is applicable to different service scenarios.

[0058] In combination with the third aspect or any one of the first to eleventh possible implementations of the third aspect, in the twelfth possible implementation of the third aspect, the communication device is an access mobility management network element of the first terminal device, or a session management network element of the first terminal device, or an access mobility management network element of the second terminal device, or a session management network element of the second terminal device.

[0059] This application also provides a specific implementation of the communication device.

[0060] In a fourth aspect, a relay management method is provided, including: UDM / UDR receives a second message from a network device; the second message is used to request relay restriction information of a first terminal device, and the second message includes an identifier of the first terminal device; the relay restriction information of the first terminal device is sent to the network device; the relay restriction information is used to indicate the number of relay devices to which the first terminal device can be connected, and / or the aggregate maximum bit rate AMBR that the first terminal device can use for relaying.

[0061] In combination with the fourth aspect, in a first possible implementation of the fourth aspect, the method further includes: sending to the network device the number of relay devices to which the first terminal device is currently connected, and / or the AMBR currently used for relaying by the first terminal device.

[0062] In combination with the fourth aspect or the first possible implementation of the fourth aspect, in the second possible implementation of the fourth aspect, the method also includes: receiving from the network device an updated number of relay devices to which the first terminal device is currently connected and / or an updated AMBR that the first terminal device is currently used for relaying.

[0063] In combination with the fourth aspect or the first possible implementation of the fourth aspect, in the second possible implementation of the fourth aspect, the method also includes: receiving a third message from the network device, the third message being used to characterize that the network device allows the first terminal device to access the network through the second terminal device; in response to the third message, updating the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device.

[0064] In a fifth aspect, a communication device is provided, comprising at least one processor and a memory, wherein the at least one processor is coupled to the memory; the memory is configured to store a computer program;

[0065] The at least one processor is used to execute the computer program stored in the memory so that the device performs the method described in the first aspect and any one of the implementations of the first aspect, or the method described in the second aspect and any one of the implementations of the second aspect.

[0066] In the sixth aspect, a computer-readable storage medium is provided, comprising: instructions stored in the computer-readable storage medium; when the computer-readable storage medium is run on the communication device described in the third aspect and any one of the implementation methods of the third aspect, the communication device executes the communication method described in the first aspect and any one of the implementation methods of the first aspect.

[0067] In the seventh aspect, a computer-readable storage medium is provided, comprising: instructions stored in the computer-readable storage medium; when the computer-readable storage medium is run on the communication device described in the above-mentioned fourth aspect and any one of the implementation methods of the fourth aspect, the communication device executes the communication method described in the above-mentioned second aspect and any one of the implementation methods of the second aspect.

[0068] In an eighth aspect, a wireless communication device is provided, comprising a processor, for example, a processor employed in the communication device, configured to implement the method described in the first aspect and any one of the implementations of the first aspect. The communication device may be, for example, a system-on-a-chip. In one feasible implementation, the system-on-a-chip further comprises a memory configured to store program instructions and data necessary to implement the functions of the method described in the first aspect.

[0069] In a ninth aspect, a wireless communication device is provided, comprising a processor, for example, a processor employed in the communication device, configured to implement the functions or methods described in the second aspect and any one of the implementations of the second aspect. The communication device may be, for example, a system-on-a-chip. In one feasible implementation, the system-on-a-chip further comprises a memory configured to store program instructions and data necessary to implement the functions of the method described in the second aspect.

[0070] The chip system in the above aspects may be a system on chip (SOC) or a baseband chip, etc., wherein the baseband chip may include a processor, a channel encoder, a digital signal processor, a modem and an interface module, etc.

[0071] In the tenth aspect, a communication system is provided, which includes a first terminal device, a second terminal device, the communication device described in the third aspect, any possible implementation of the third aspect, the fourth aspect and any possible implementation of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1 An architectural diagram of a communication system provided in an embodiment of the present application;

[0073] Figure 2 A schematic diagram of the protocol stack provided in an embodiment of the present application;

[0074] Figure 3 A schematic diagram of a relay provided in an embodiment of the present application;

[0075] Figure 4 Schematic diagram of the layer 2 relay protocol provided in an embodiment of the present application;

[0076] Figure 5Schematic diagram of a layer 2 relay session provided in an embodiment of the present application;

[0077] Figure 6 Schematic diagram of the layer 3 relay protocol provided in an embodiment of the present application;

[0078] Figure 7 Schematic diagram of a layer 3 relay session provided in an embodiment of the present application;

[0079] Figure 8a A structural block diagram of a communication device provided in an embodiment of the present application;

[0080] Figure 8b Another structural block diagram of a communication device provided in an embodiment of the present application;

[0081] Figure 9 A flowchart of the relay management method provided in an embodiment of the present application;

[0082] Figure 10 Another flowchart of the relay management method provided in an embodiment of the present application;

[0083] Figure 11 Another flowchart of communication management provided by an embodiment of the present application;

[0084] Figures 12 to 15 Another structural block diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0085] refer to Figure 1 , is a schematic diagram of a network architecture of a communication system applicable to an embodiment of the present application. The network architecture includes an access network device 10, terminal devices (only terminal devices 21 and 22 are shown in the figure), an access management network element 30, a session management network element 40, a user plane network element 50, a policy control network element 60, a network slice selection network element 70, a network storage function network element 80, a unified data management network element 90, a unified data storage network element 100, an authentication service function network element 110, an application function network element 120, a network data analysis network element 130, a network capability exposure network element 140, and a data network (DN) 150 connected to the operator's network. The terminal device can send service data to the data network and receive service data from the data network through the access network device and the user plane network element.

[0086] Among them, the terminal device is a device with wireless transceiver function, which can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal device can communicate with the core network via the radio access network (RAN) and exchange voice and / or data with the RAN. The terminal device can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a mobile internet device (MID), a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of this application do not limit the application scenarios. Terminal devices may also be referred to as user equipment (UE), mobile stations, and remote stations. The embodiments of this application do not limit the specific technology, device form, or name used by the terminal devices.

[0087] Access network equipment is a device in the network used to connect terminal devices to the wireless network. The access network equipment can be a node in the radio access network, also known as a base station, or a radio access network (RAN) node (or device). The network device may include an evolved base station (NodeB, eNB, or e-NodeB, evolutionary Node B) in a long term evolution (LTE) system or an evolved LTE system (LTE-Advanced, LTE-A), such as a traditional macro base station eNB and a micro base station eNB in ​​a heterogeneous network scenario, or may also include a next generation node B (gNB) in a fifth generation mobile communication technology (5G) new radio (NR) system, or may further include a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a transmission reception point (TRP), a home base station (e.g., a home evolved NodeB, or a home Node B, HNB), a base band unit (BBU), a base band pool BBU pool, or a WiFi access point (AP), etc., or may further include a cloud radio access network (CRN). The embodiments of the present application do not limit the centralized unit (CU) and distributed unit (DU) in the CloudRAN system. In the separate deployment scenario where the access network equipment includes the CU and DU, the CU supports protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); the DU mainly supports the radio link control layer (RLC), media access control layer (MAC), and physical layer protocols.

[0088] The access management network element (in this embodiment of the application, it may also be referred to as the access mobility management network element) is mainly used for the attachment, mobility management, and tracking area update processes of terminals in the mobile network. The access management network element terminates the non-access stratum (NAS) message, completes registration management, connection management, and reachability management, allocates the tracking area list (TA list) and mobility management, and transparently routes the session management (SM) message to the session management network element. In the fifth generation (5G) communication system, the access management network element may be the access and mobility management function (AMF). In future communication systems (such as 6G communication systems), the mobility management network element may still be the AMF network element, or may have other names, which is not limited by this application.

[0089] The session management network element is mainly used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol (IP) addresses to terminals and selecting user plane network elements that provide message forwarding functions. In 5G communication systems, the session management network element can be a session management function (SMF). In future communication systems (such as 6G communication systems), the session management network element can still be an SMF network element, or it can have other names, which are not limited by this application.

[0090] The user plane network element is mainly used to process user messages, such as forwarding, billing, and lawful interception. The user plane network element can also be called a protocol data unit (PDU) session anchor (PSA). In a 5G communication system, the user plane network element can be a user plane function (UPF). In future communication systems (such as a 6G communication system), the user plane network element can still be a UPF network element, or it can have other names, which are not limited in this application.

[0091] The policy control network element includes user subscription data management functions, policy control functions, billing policy control functions, quality of service (QoS) control, etc. In the 5G communication system, the policy control network element can be a policy control function (PCF). In future communication systems (such as 6G communication systems), the policy control network element can still be a PCF network element, or it can have other names, which is not limited in this application.

[0092] The network slice selection function network element is mainly used to select the appropriate network slice for the service of the terminal device. In the 5G communication system, the network slice selection network element can be a network slice selection function (NSSF) network element. In future communication systems (such as 6G communication systems), the network slice selection network element can still be an NSSF network element, or it can have other names, which is not limited by this application.

[0093] The network storage function network element is mainly used to provide registration and discovery functions for network elements or services provided by network elements. In 5G communication systems, the network storage function network element can be a network repository function (NRF). In future communication systems (such as 6G communication systems), the network storage function network element can still be an NRF network element, or it can have other names, which is not limited by this application.

[0094] The network data analysis network element can collect data from various network functions (NFs), such as policy control network elements, session management network elements, user plane network elements, access management network elements, and application function network elements (through network capability exposure function network elements), and perform analysis and prediction. In a 5G communication system, the network data analysis network element can be a network data analysis function (NWDAF). In future communication systems (such as 6G communication systems), the network data analysis network element can still be an NWDAF network element, or it can have other names, which is not limited by this application.

[0095] The unified data management network element is mainly used to manage the contract information of terminal devices. In the 5G communication system, the unified data management network element can be unified data management (UDM). In future communication systems (such as 6G communication systems), the unified data management network element can still be the UDM network element, or it can have other names, which is not limited by this application.

[0096] The unified data storage network element is mainly used to store structured data information, including contract information, policy information, and network data or business data defined in a standard format. In the 5G communication system, the unified data storage network element can be a unified data repository (UDR). In future communication systems (such as 6G communication systems), the unified data storage network element can still be a UDR network element, or it can have other names, which is not limited by this application.

[0097] The authentication service function network element is mainly used to perform security authentication on the terminal device. In the 5G communication system, the authentication service function network element can be the authentication server function (AUSF). In future communication systems (such as 6G communication systems), the authentication service function network element can still be the AUSF network element, or it can have other names, which is not limited by this application.

[0098] A network capability exposure network element can controllably expose some network functions to applications. In a 5G communication system, a network capability exposure network element can be a network exposure function (NEF). In future communication systems (such as a 6G communication system), the network capability exposure network element can still be an NEF network element, or it can have other names, which are not limited by this application.

[0099] The application function network element can provide service data of various applications to the control plane network elements of the operator's communication network, or obtain network data information and control information from the control plane network elements of the communication network. In the 5G communication system, the application function network element can be an application function (AF). In future communication systems (such as 6G communication systems), the application function network element can still be an AF network element, or it can have other names, which is not limited by this application.

[0100] Data networks are primarily used to provide data transmission services to terminal devices. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or proprietary networks deployed jointly by operators, such as those configured with IP multimedia corenetwork subsystem (IMS) services.

[0101] It should be understood that the above-mentioned network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network elements or functions can be implemented by a single device, or by multiple devices, or as a functional module within a single device, and this is not specifically limited in the embodiments of the present application.

[0102] For the convenience of explanation, this application will be described later using the access management network element as the AMF network element and the network slice selection function network element as the NSSF network element as an example. Furthermore, the AMF network element is referred to as AMF, and the NSSF network element is referred to as NSSF. That is, the AMF described later in this application can be replaced by the access management network element, and the NSSFF can be replaced by the network slice selection function network element.

[0103] although Figure 1 Not shown, the core network devices of the terminal devices 21 and 22 may be different. For example, different AMFs perform access and mobility management on the terminal devices 21 and 22, respectively, or different SMFs perform session management and control on the terminal devices 21 and 22, respectively.

[0104] First, the terms involved in the embodiments of this application are explained:

[0105] (1) Quality of service (QoS) parameters

[0106] QoS parameters can be used to modify network QoS to provide better services for network communications. For example, by modifying QoS parameters, problems such as network delay and congestion can be solved to ensure efficient operation of the network.

[0107] The UE can establish PDU sessions for different services, and different services require different QoS parameters. For example, video services require high bandwidth, while voice communications need to ensure reliable low latency. When the UE initiates a PDU session establishment request or a PDU session update request, the SMF can establish different QoS flows (QoS Flow) for different services based on the UE's service requirements, and can use QFI (QoS Flow Identifier) ​​to identify the QoS flow. The QoS requirements corresponding to the same QoS flow are the same, and these requirements can be quantified using QoS parameters. For example, QoS parameters can be latency, bandwidth, packet loss rate, etc. 5QI (5G QoS Identifier) ​​can also be used to identify these QoS parameters.

[0108] Depending on service requirements, QoS parameters may also include the aggregate maximum bitrate (AMBR). AMBR includes UE-AMBR and Session-AMBR. UE-AMBR refers to the maximum bandwidth achievable by all QoS flows corresponding to a UE, while Session-AMBR refers to the maximum bandwidth achievable by all QoS flows corresponding to a PDU session.

[0109] (2) Protocol Stack

[0110] Figure 2 This is a schematic diagram of the protocol stack provided in the embodiment of the present application. Different devices can communicate with each other through Figure 2 The protocol layers shown interact with each other. Figure 2 The protocol stack includes the application layer (application layer), protocol data unit (PDU) layer, internet protocol (IP) layer, new radio-service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer and physical layer (PHY layer).

[0111] (3) Relay

[0112] In the embodiments of the present application, relay can be understood as a terminal device accessing the network through another terminal device, establishing an indirect connection with the network. The terminal device providing the relay service can be referred to as a relay UE, and the terminal device accessing the network through the relay can be referred to as a remote UE.

[0113] Figure 3 This is a diagram of the relay architecture provided in the embodiment of this application. Figure 3 , a remote device (remote UE, also referred to as remote UE) can interact with an access network device, UPF, and an application server (AS) through a relay device (relay UE, also referred to as relay UE). Figure 1In the illustrated network architecture, terminal device 21 can function as a relay UE, and terminal device 22 can function as a remote UE. Specifically, terminal device 21 communicates with access network device 10 via a Uu link, and communication between terminal device 21 and terminal device 22 occurs via a direct link. Terminal device 21 can also provide relay services for terminal device 22. For example, terminal device 21 can receive data sent by terminal device 22 via the PC5 interface and forward the data to access network device 10. Alternatively, terminal device 21 can receive data sent by the access network device to terminal device 22 via the Uu link and forward the received data to terminal device 22 via the PC5 interface.

[0114] (4) Layer 2 relay

[0115] Figure 4 This is a diagram of the protocol stack for layer 2 relay. Figure 4 In the Layer 2 relay scenario, when the relay UE forwards a data packet for the remote UE, it only processes the data packet below the PDCP layer (no data packet processing is performed at the PDCP layer) and then forwards it to the access network device for processing. This ensures data security between the remote UE and the access network device and prevents excessive exposure of the remote UE's data to the relay UE.

[0116] Figure 5 This is a diagram of the connection of layer 2 relay. Figure 5 A relay UE can connect to multiple remote UEs and provide Layer 2 relay forwarding for these remote UEs. Remote UE 1 establishes PDU Session 1 through the relay UE. The relay UE can use remote UE 1's PDU Session 1 to provide relay services for remote UE 1. Remote UE 2 establishes PDU Session 2 through the relay UE. The relay UE can use remote UE 2's PDU Session 2 to provide relay services for remote UE 2. As can be seen, in the Layer 2 relay scenario, the remote UE's SMF performs session management for the relayed sessions.

[0117] For layer 2 relay, the core network element (for example, AMF) can learn that the remote UE is connected to the core network via relay when the remote UE is connected to the core network via relay, but the AMF will not control the relay service of the remote UE. For example, the AMF has no way of knowing whether the remote UE has been connected to the network through other relay UEs, nor will it control the relay service request this time. In this way, the same remote UE may occupy excessive relay resources (for example, relay equipment), bandwidth resources, etc.

[0118] (5) Layer 3 relay

[0119] Figure 6 This is a diagram of the protocol stack for layer 3 relay. Figure 6 In a Layer 3 relay scenario, when a relay UE forwards a data packet for a remote UE, it only processes the data below the IP layer (without processing the data packet content at the IP layer) and then forwards it to the access network device for processing. The access network device is unaware of whether the relay UE has forwarded the remote UE's data.

[0120] Figure 7 This is a diagram of the connection of layer 3 relay. Figure 7 A relay UE can connect to multiple remote UEs and provide Layer 3 relay forwarding for these remote UEs. Unlike Layer 2 relay, in Layer 3 relay scenarios, the relay UE uses its own PDU session to forward data to the remote UE. Therefore, in Layer 3 relay scenarios, the relay UE's SMF manages the relayed sessions.

[0121] For layer 3 relay, SMF establishes or modifies PDU session for relay UE so that relay UE can provide relay service for remote UE. Relay UE will send remote UE report to SMF, and SMF will know that remote UE is connected to core network through relay according to the report of remote UE. However, SMF will not control the relay service of remote UE. For example, SMF has no way of knowing whether remote UE has been connected to the network through other relay UEs, nor will it control the relay service request. In this way, the same remote UE may occupy excessive relay resources (for example, relay equipment) and bandwidth resources.

[0122] An embodiment of the present application provides a relay management method for configuring relay restriction information for a remote UE, indicating the number of relay devices to which the remote UE can connect and / or the AMBR that the remote UE can use for relaying. Based on the remote UE's relay restriction information, whether the remote UE is allowed to connect to the core network through a relay UE can be determined. If the number of relay devices connected to the remote UE reaches an upper limit, or the AMBR used by the remote UE for relaying reaches an upper limit, the remote UE's relay service request is rejected.

[0123] The terminal device described in the embodiment of the present application can be Figure 8a It is implemented by the communication device 810 in. Figure 8a FIG. 8 is a schematic diagram of the hardware structure of a communication device 810 provided in an embodiment of the present application. The communication device 810 includes a processor 8101 and at least one communication interface ( Figure 8a The example in the figure is merely exemplary and is described by taking the communication interface 8103 as an example), and optionally, further includes a memory 8102. The processor 8101, the memory 8102, and the communication interface 8103 are connected to each other.

[0124] The processor 8101 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0125] The communication interface 8103 uses any transceiver or other device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc.

[0126] The memory 8102 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently or be connected to the processor. The memory may also be integrated with the processor.

[0127] The memory 8102 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 8101. The processor 8101 is used to execute the computer-executable instructions stored in the memory 8102, thereby implementing the intention processing method provided in the following embodiments of the present application.

[0128] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0129] In a specific implementation, as an embodiment, the processor 8101 may include one or more CPUs, such as Figure 8a CPU0 and CPU1 in.

[0130] In a specific implementation, as an embodiment, the communication device 810 may include multiple processors, such as Figure 8a 8101 and processor 8106 in the . Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here can refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0131] In a specific implementation, as an embodiment, the communication device 810 may further include an output device 8104 and an input device 8105. The output device 8104 communicates with the processor 8101 and can display information in a variety of ways. For example, the output device 8104 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 8105 communicates with the processor 8101 and can receive user input in a variety of ways. For example, the input device 8105 can be a mouse, a keyboard, a touch screen device, or a sensor device.

[0132] The communication device 810 can be a general purpose device or a dedicated device. In a specific implementation, the communication device 810 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device or a computer with a Figure 8a The embodiment of the present application does not limit the type of the communication device 810.

[0133] It should be noted that the communication device 810 can be a terminal, a functional component or assembly implementing the terminal, or a communication chip, such as a baseband chip. When the communication device 810 is a terminal, the communication interface can be a radio frequency module. When the communication device 810 is a communication chip, the communication interface 8103 can be the chip's input / output interface circuit, which is used to read and output baseband signals.

[0134] Figure 8b The communication device 820 may be a network device as described in the embodiment of the present application, such as an AMF or SMF.

[0135] The communication device includes at least one processor 8201, at least one transceiver 8203, at least one network interface 8204, and one or more antennas 8205. Optionally, it also includes at least one memory 8202. The processor 8201, memory 8202, transceiver 8203, and network interface 8204 are connected, for example, via a bus. The antenna 8205 is connected to the transceiver 8203. The network interface 8204 is used to connect the communication device to other communication devices via a communication link, for example, the communication device is connected to a core network element via an S1 interface. In this embodiment of the present application, the connection may include various interfaces, transmission lines, or buses, etc., which are not limited in this embodiment.

[0136] The processor in the embodiment of the present application, such as the processor 8201, may include at least one of the following types: a general-purpose central processing unit (CPU), a digital signal processor (DSP), a microprocessor, an application-specific integrated circuit (ASIC), a microcontroller unit (MCU), a field programmable gate array (FPGA), or an integrated circuit for implementing logical operations. For example, the processor 8201 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. At least one processor 8201 may be integrated in one chip or located on multiple different chips.

[0137] The memory in the embodiments of the present application, such as memory 8202, may include at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0138] The memory 8202 can exist independently and be connected to the processor 8201. Optionally, the memory 8202 can also be integrated with the processor 8201, for example, integrated into a single chip. Among them, the memory 8202 can store program codes for executing the technical solutions of the embodiments of the present application, and the execution is controlled by the processor 8201. The various computer program codes executed can also be regarded as drivers for the processor 8201. For example, the processor 8201 is used to execute the computer program codes stored in the memory 8202, thereby implementing the technical solutions in the embodiments of the present application.

[0139] The transceiver 8203 can be used to support the reception or transmission of radio frequency signals between the communication device and the terminal device. The transceiver 8203 can be connected to the antenna 8205. Specifically, one or more antennas 8205 can receive radio frequency signals. The transceiver 8203 can be used to receive the radio frequency signals from the antennas, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 8201 so that the processor 8201 can further process the digital baseband signals or digital intermediate frequency signals, such as demodulation and decoding. In addition, the transceiver 8203 can be used to receive modulated digital baseband signals or digital intermediate frequency signals from the processor 8201, convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals via one or more antennas 8205. Specifically, the transceiver 8203 can selectively perform one or more stages of down-mixing and analog-to-digital conversion on the RF signal to obtain a digital baseband signal or a digital intermediate frequency signal, and the order of the down-mixing and analog-to-digital conversion processes is adjustable. The transceiver 8203 can selectively perform one or more stages of up-mixing and digital-to-analog conversion on the modulated digital baseband signal or digital intermediate frequency signal to obtain a RF signal, and the order of the up-mixing and digital-to-analog conversion processes is adjustable. Digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals. A transceiver can be referred to as a transceiver circuit, a transceiver unit, a transceiver device, a transmitting circuit, a transmitting unit, or a transmitting device, etc.

[0140] It should be noted that the communication device 820 can be a complete communication device, a component or assembly that implements the functions of the communication device, or a communication chip. When the communication device 820 is a communication chip, the transceiver 8203 can be an interface circuit of the chip, which is used to read and output baseband signals.

[0141] The present application embodiment provides a relay management method, such as Figure 9 As shown, the method includes the following steps:

[0142] 901. A network device obtains an identifier of a first terminal device from a first terminal device or a second terminal device.

[0143] The first terminal device may be a remote device, and the second terminal device may be a relay device for the first terminal device, providing relay services for the first terminal device. The first terminal device may access the network through the second terminal device, or the first terminal device may establish an indirect connection with the network through the second terminal device. For example, the first terminal device may send data to the access network device through the second terminal device, or the first terminal device may receive data sent by the access network device through the second terminal device. The network device may be an access mobility management network element (AMF) or a session management network element (SMF).

[0144] In a specific implementation, the remote UE and the relay UE first perform a relay discovery process. For example, when the first terminal device establishes a connection with the access network device, and the communication quality of the Uu interface between the first terminal device and the access network device cannot meet the communication requirements, or the first terminal device is in a non-connected state (connection management-idle, CM-IDLE), or the first terminal device is outside the network coverage, the first terminal device can initiate a relay connection to the second terminal device according to the relay discovery information pre-configured on the network side or the locally pre-configured relay discovery information to complete the relay discovery. The relay discovery information is used to establish a relay connection (for example, a direct connection between the first terminal device and the second terminal device, which can be a PC5 connection), including authorization information for using the relay to connect to the network, policy information for discovering relay nodes, spectrum information for relay communication, etc. The first terminal device can obtain the identification of the second terminal device in the relay discovery process. The remote UE obtains the identification information of the relay in the interactive message with the relay.

[0145] After the remote UE and the relay UE complete relay discovery, the remote UE initiates a relay service request, or the relay UE initiates a relay service request. Specifically, the remote UE or the relay UE may initiate a relay service request via a relay service request message. If the remote UE initiates the relay service request message, the relay service request message may carry the identifier of the relay UE. If the relay UE initiates the relay service request message, the relay service request message may carry the identifier of the remote UE.

[0146] For example, the first terminal device initiates a relay service request, and the first terminal device sends a first message to the AMF or SMF of the first terminal device, where the first message is used to indicate that the first terminal device requests to access the network through the second terminal device. The first message sent by the first terminal device includes the identifier of the first terminal device and the identifier of the second terminal device, or the first message sent by the first terminal device includes the identifier of the second terminal device. The AMF or SMF of the first terminal device can be considered as the network device described in step 901.

[0147] If the first message includes the identifier of the first terminal, the AMF or SMF of the first terminal device can obtain the identifier of the first terminal device from the first message. Alternatively, if the first message does not include the identifier of the first terminal device, the AMF or SMF can obtain the identifier of the first terminal device by receiving the first message from the first terminal device.

[0148] Alternatively, the second terminal device initiates a relay service request, and the second terminal device sends a first message to the AMF or SMF of the second terminal device, where the first message is used to indicate that the first terminal device requests to access the network through the second terminal device. The first message sent by the second terminal device includes the identifier of the first terminal device and the identifier of the second terminal device, or the first message sent by the second terminal device includes the identifier of the first terminal device. The AMF or SMF of the second terminal device can be considered as the network device described in step 901.

[0149] The AMF or SMF of the second terminal device receives the first message sent by the second terminal device and can obtain the identifier of the first terminal device from the first message.

[0150] 902. The network device obtains relay restriction information of the first terminal device from the UDM or UDR according to the identifier of the first terminal device.

[0151] The relay restriction information is used to limit the number of relay devices to which the remote UE is connected, thereby enabling the network side to control the use of relay devices by the remote UE and preventing the same remote UE from occupying too many relay resources and bandwidth resources. For example, the relay restriction information of the first terminal device indicates the number of relay devices to which the first terminal device can be connected, and / or the aggregate maximum bit rate (AMBR) that the first terminal device can use for relaying.

[0152] It should be noted that the relay restriction information of the remote UE can be configured at the UE granularity and is applicable to any service of the remote UE. The relay restriction information of the remote UE can be the UE-AMBR (UE granularity AMBR) that can be used when the remote UE performs relay services.

[0153] Alternatively, the relay restriction information of the remote UE is configured based on the granularity of the service, and the relay restriction information for different services is different. For example, the relay restriction information includes first relay restriction information and second relay restriction information; the first relay restriction information includes the number of relay devices to which the first terminal device can connect when performing the first service, and / or, the AMBR that can be used for relaying when the first terminal device performs the first service; the second relay restriction information includes the number of relay devices to which the first terminal device can connect when performing the second service, and / or, the AMBR that can be used for relaying when the first terminal device performs the second service.

[0154] In a specific implementation, the UDM or UDR can store the UE's subscription information. For example, the remote UE's subscription information can be stored, and the remote UE's subscription information includes the remote UE's relay restriction information. The remote UE's relay restriction information can include the number of relay devices to which the remote UE can connect, and can also include the remote UE's available AMBR for relay. The remote UE's available AMBR for relay can be adapted to various application scenarios of the remote UE, or the remote UE's available AMBR for relay can include the corresponding AMBR for relay when the remote UE uses different services.

[0155] In one possible implementation, the UDM or UDR may maintain a set of data, the data header (Key) may be the identifier of the remote UE, and the data content may be the relay restriction information of the remote UE. Optionally, the data content may also include the relay identifier (relay UE ID) to which the remote UE is connected, the capability information of the relay (layer 2 or layer 3 relay), the service information of the relay (RSC), and service-related information. The service-related information may be one or more of the Service ID, Application ID, data network name (DNN), and single network slice selection assistance information (S-NSSAI).

[0156] After receiving the first message from the first terminal device or the second terminal device, the network device may send the identifier of the first terminal device to the UDM or UDR to request relay restriction information of the first terminal device.

[0157] Specifically, the network device sends a second message to the unified data management network element or the unified data storage network element in response to the first message; the second message is used to request relay restriction information of the first terminal device, and the second message includes an identifier of the first terminal device.

[0158] The network device may also receive relay restriction information of the first terminal device from the unified data management network element or the unified data storage network element.

[0159] It should be noted that if the relay restriction information is configured for the UE based on the service granularity, different services correspond to different relay restriction information. When the first terminal device or the second terminal device initiates a relay service request through the first message, it is necessary to indicate the service information of the remote UE. For example, the first message includes service-related information, and the service-related information is used to describe the service of the remote UE this time. The explanation of the service information is referred to the previous text and will not be repeated here.

[0160] Accordingly, the network device may obtain relay restriction information corresponding to the service-related information from the UDM or UDR according to the service-related information. For example, the second message sent by the network device includes the service-related information.

[0161] In one possible implementation, the network device may use a data update service (e.g., Nudr_DM_Update service in TS 23.501) to obtain the relay restriction information of the first terminal device. Taking AMF as an example, AMF sends a data update service message to UDM or UDR, which carries the remote UEID. UDM or UDR receives the data update service message, determines the relay restriction information of the remote UE based on the UEID in the message, and sends the relay restriction information of the remote UE to AMF.

[0162] It should be noted that the identifier of the terminal device in the embodiment of the present application, the identifier of the UE may be a subscription permanent identifier (SUPI), a generic public subscription identifier (GPSI), or an identifier assigned by a third-party service provider. The identifier assigned by the third-party service provider may be an application layer user identifier (Application Layer User ID).

[0163] 903. The network device determines whether to allow the first terminal device to access the network through the second terminal device based on the relay restriction information of the first terminal device.

[0164] In a specific implementation, the network device needs to determine whether the current relay status of the first terminal device has exceeded the limit of the relay restriction information of the first terminal device. If it has exceeded the limit, the first terminal device is not allowed to connect to the relay device again, that is, the first terminal device is not allowed to access the network through the second terminal device, and the relay service request of the first terminal device is rejected. Whether the relay service request of the first terminal device is allowed can be determined by referring to the number of relay devices to which the first terminal device can be connected, or whether the relay service request of the first terminal device is allowed can be determined by referring to the AMBR that the first terminal device can use for relay.

[0165] It should be noted that if any one of the number of relay devices to which the first terminal device can connect or the AMBR that the first terminal device can use for relaying exceeds the limit, the relay service request of the first terminal device this time will be rejected. Once the AMBR currently used for relaying exceeds the AMBR that the first terminal device can use for relaying, the relay service request of the first terminal device this time will be rejected regardless of whether the number of relay devices currently connected to the first terminal device exceeds the number of relay devices to which the first terminal device can connect. Once the number of relay devices currently connected to the first terminal device exceeds the number of relay devices to which the first terminal can connect, the relay service request of the first terminal device this time will be rejected regardless of whether the AMBR currently used for relaying exceeds the AMBR that the first terminal device can use for relaying.

[0166] In one possible implementation, if the number of relay devices currently connected to the first terminal device does not exceed the number of relay devices to which the first terminal device can connect, the first terminal device is allowed to access the network through the second terminal device; if the number of relay devices currently connected to the first terminal device is equal to the number of relay devices to which the first terminal device can connect, the first terminal device is denied access to the network through the second terminal device.

[0167] For example, the number of relay devices to which the first terminal device can connect is M, and the number of relay devices to which the first terminal device is currently connected is x. When x is less than M, the first terminal device's current relay service request is allowed, and the first terminal device is allowed to access the network through the second terminal device. When x is equal to M, the first terminal device's current relay service request is rejected, and the first terminal device is not allowed to access the network through the second terminal device.

[0168] In another possible implementation, if the AMBR currently used for relaying by the first terminal device does not exceed the AMBR that the first terminal device can use for relaying, the first terminal device is allowed to access the network through the second terminal device; if the AMBR currently used for relaying by the first terminal device is equal to the AMBR that the first terminal device can use for relaying, the first terminal device is denied access to the network through the second terminal device.

[0169] For example, the AMBR that the first terminal device can use for relaying is 10 Mbps, and the AMBR currently used by the first terminal device for relaying is y Mbps. When y is less than 10, the first terminal device's current relay service request is allowed, and the first terminal device is allowed to access the network through the second terminal device. When y is equal to 10, the first terminal device's current relay service request is rejected, and the first terminal device is not allowed to access the network through the second terminal device.

[0170] In one possible implementation, the unified data management network element or the unified data storage network element also records the current relay status of the remote UE. Taking the first terminal device as an example, the unified data management network element or the unified data storage network element records the number of relay devices currently connected to the first terminal device, and / or the AMBR currently used for relaying by the first terminal device.

[0171] Optional, Figure 9 The method shown also includes: the network device obtains the number of relay devices currently connected to the first terminal device from a unified data management network element or a unified data storage network element, and / or the AMBR currently used for relaying by the first terminal device.

[0172] The network device obtains the number of relay devices to which the first terminal device is currently connected from the unified data management network element or the unified data storage network element, and / or the AMBR currently used for relay by the first terminal device, and can then determine whether to allow the first terminal device's relay service request based on the first terminal device's current relay status and the first terminal device's relay restriction information.

[0173] Optional, Figure 9 The method shown also includes: after allowing the first terminal device's current relay service request based on the relay restriction information of the first terminal device, a PDU session can be established for the first terminal device to access the core network. The PDU session can be a session of the first terminal device or a session of the second terminal device.

[0174] For example, if the network device allows the first terminal device to access the network through the second terminal device, a session of the first terminal device is established, or a session of the second terminal device is established.

[0175] Specifically, in a Layer 2 relay scenario, a session is established with a remote UE (e.g., a first terminal device), and a relay UE (e.g., a second terminal device) forwards the remote UE's session to provide relay services for the remote UE. In a Layer 3 relay scenario, a session is established with a relay UE, and the relay UE provides relay services for the remote UE.

[0176] If the network device is an AMF. After the AMF determines, based on the relay restriction information of the first terminal device, that the first terminal device is allowed to access the network through the second terminal device, the AMF sends a confirmation message to the first terminal device or the second terminal device, indicating that the second terminal device can establish or change a PDU session for the first terminal device, or indicating that the second terminal device can provide relay services for the first terminal device.

[0177] Subsequently, the first terminal device or the second terminal device may send a PDU session establishment request message or a PDU session change request message to the SMF.

[0178] It should be noted that the first terminal device or the second terminal device can send the first message and the PDU session change / establishment request message together to the AMF. After the AMF allows the first terminal device to access the network through the second terminal device based on the relay restriction information of the first terminal device, the AMF can forward the PDU session change / establishment request message to the SMF.

[0179] If the network device is SMF, SMF determines based on the relay restriction information of the first terminal device that the first terminal device is allowed to access the network through the second terminal device, and then establishes a PDU session for the remote UE, or allows relayUE to provide relay services for the remote UE.

[0180] Optional, Figure 9 The illustrated method may further include: upon granting the first terminal device's current relay service request, establishing a session for the first terminal device or a session for the second terminal device for the first terminal device's relay service. The network device may also record the first terminal device's most recent relay status. For example, this may include updating the number of relay devices currently connected to the first terminal device and / or updating the AMBR currently used for relaying by the first terminal device.

[0181] For example, the number of relay devices to which the first terminal device can connect is M, and the number of relay devices to which the first terminal device is currently connected is x. When x is less than M, the first terminal device's current relay service request is allowed, and the first terminal device is allowed to access the network through the second terminal device. The network device may also update the number of relay devices to which the first terminal device is currently connected to (x+1).

[0182] Alternatively, the AMBR that the first terminal device can use for relaying is 10Mbps, and the AMBR currently used for relaying by the first terminal device is y Mbps. When y is less than 10, the relay service request of the first terminal device is allowed, and the first terminal device is allowed to access the network through the second terminal device. A PDU session is established for the first terminal device or the second terminal device for the relay service of the first terminal device, and the session-AMBR of the PDU session is r. The network device may also update the AMBR currently used for relaying by the first terminal device to (y+r)Mbps, and (y+r)Mbps is less than or equal to 10Mbps.

[0183] In a specific implementation, the network device can also obtain the session-granularity AMBR (session-AMBR) from the UDM / UDR. In a layer 2 relay scenario, the first terminal device establishes or updates a PDU session, and the second terminal device forwards the PDU session to provide relay services for the first terminal device. The session-granularity AMBR is the session-AMBR corresponding to the first terminal device. In a layer 3 relay scenario, the second terminal device establishes or updates a PDU session to provide relay services for the first terminal device. The session-granularity AMBR is the session-AMBR corresponding to the second terminal device.

[0184] Optional, Figure 9 The method shown also includes: after the network device records the latest current relay status of the first terminal device, it can also send an updated number of relay devices to which the first terminal device is currently connected and / or an updated AMBR currently used for relaying by the first terminal device to the unified data management network element. For example, (y+r) and (x+1) are sent to the unified data management network element or the unified data storage network element.

[0185] Optional, Figure 9 The method shown also includes: the network device determines to allow the first terminal device's relay service request this time based on the relay restriction information of the first terminal device, and can also instruct the unified data management network element or the unified data storage network element to update the relay status of the first terminal device.

[0186] For example, if the network device allows the first terminal device to access the network through the second terminal device, it sends a third message to the unified data management network element, so that the unified data management network element updates the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device according to the third message. The third message is used to indicate that the network device allows the first terminal device to access the network through the second terminal device.

[0187] In one possible implementation, the third message includes the identifier of the second terminal device. After receiving the third message, the unified data management network element or the unified data storage network element may record the identifier of the relay device to which the first terminal device is currently connected (i.e., the second terminal device described in the embodiment of the present application) in addition to recording the number of relay devices currently connected to the first terminal device and the AMBR currently used for relaying by the first terminal device.

[0188] Optional, Figure 9 The method shown also includes: the network device determines to reject the relay service request of the first terminal device based on the relay restriction information of the first terminal device, and can also feed back rejection information to the device that initiated the relay service request.

[0189] For example, in a scenario where the first terminal device sends a first message requesting to access the network through the second terminal device, if the network device refuses the first terminal device to access the network through the second terminal device, it sends a fourth message to the first terminal device; the fourth message is used to indicate that the network device refuses the first terminal device to access the network through the second terminal device.

[0190] The second terminal device sends a first message, indicating that in a scenario where the first terminal device requests to access the network through the second terminal device, if the network device refuses the first terminal device to access the network through the second terminal device, it sends a fourth message to the second terminal device; the fourth message is used to indicate that the network device refuses the first terminal device to access the network through the second terminal device.

[0191] Optionally, the fourth message includes a failure reason value; the failure reason value is used to characterize that the failure reason is that the number of relay devices currently connected to the first terminal device is equal to the number of relay devices to which the first terminal device can be connected, or the AMBR currently used for relaying by the first terminal device is equal to the AMBR that the first terminal device can use for relaying.

[0192] In a possible implementation, the network device may further update the relay status of the first terminal device after the session is released.

[0193] For example, the number of relay devices that the first terminal device can connect to is M, and the number of relay devices that the first terminal device is currently connected to is x. When x is less than M, the first terminal device's relay service request is allowed, the first terminal device is allowed to access the network through the second terminal device, and a PDU session is established for the first terminal device or the second terminal device for the relay service of the first terminal device. The network device can also update the number of relay devices currently connected to the first terminal device to (x+1). When the PDU session is released, the network device can also update the number of relay devices currently connected to the first terminal device to x, and notify the UDM or UDR of the latest relay situation, for example, notifying the UDM or UDR that the number of relay devices currently connected to the first terminal device is x. Alternatively, after the PDU session is released, instruct the UDM or UDR to update the number of relay devices currently connected to the first terminal device.

[0194] Alternatively, the AMBR that the first terminal device can use for relaying is 10Mbps, and the AMBR currently used for relaying by the first terminal device is y Mbps. When y is less than 10, the relay service request of the first terminal device is allowed, and the first terminal device is allowed to access the network through the second terminal device. A PDU session is established for the first terminal device or the second terminal device for the relay service of the first terminal device, and the session-AMBR of the PDU session is r. The network device may also update the AMBR currently used for relaying by the first terminal device to (y+r)Mbps, and (y+r)Mbps is less than or equal to 10Mbps. When the PDU session is released, the network device may also update the AMBR currently used for relaying by the first terminal device to y Mbps, and notify the UDM or UDR that the AMBR currently used for relaying by the first terminal device is yMbps. Alternatively, after the PDU session is released, the UDM or UDR is instructed to update the AMBR currently used for relaying by the first terminal device.

[0195] In the implementation described above, the network device determines whether to allow the relay service request of the first terminal device this time. In another possible implementation, after the network device receives the first message from the first terminal device or the second terminal device, it sends a fifth message to the UDM or UDR. The fifth message includes relay authentication request information and the identifier of the first terminal device, which is used to request the UDM or UDR to determine whether the first terminal device is allowed to access the network through the second terminal device. The UDM or UDR can determine whether the number of relay devices currently connected to the first terminal device has reached the upper limit, specifically, whether the number of relay devices currently connected to the first terminal device exceeds the number of relay devices that the first terminal device can connect to, and / or whether the AMBR currently used by the first terminal device for relaying exceeds the AMBR that the first terminal device can use for relaying.

[0196] The UDM or UDR may also send a sixth message to the network device, indicating whether the first terminal device is allowed to access the network through the second terminal device. The UDM or UDR may also update the number of relay devices currently connected to the first terminal device, the identifier of the currently connected relay device, and the AMBR currently used for relaying.

[0197] refer to Figure 10 , an embodiment of the present application also provides a relay management method, taking the first terminal device as a remote UE, the second terminal device as a relay UE, and the network device as an AMF / SMF as an example. Figure 10The method shown is applicable to the layer 2 relay scenario. When a remote UE expects to access the network through a relay, the remote UE initiates a relay service request. The AMF / SMF can control the relay service request and allow or reject the relay service request initiated by the remote UE. Figure 10 As shown, the method includes the following steps:

[0198] 1001. A remote UE registers with the network through a base station.

[0199] When the remote UE is within the coverage of the cellular network, the remote UE needs to register with the core network before using the cellular network for communication. When the remote UE is connected to the network, the AMF / SMF can obtain the remote UE's subscription information from the UDM or UDR. The remote UE's subscription information includes the remote UE's capability information and the remote UE's relay restriction information. Among them, the remote UE's capability information is used to characterize the remote UE's ability to access the network through relay, and the remote UE's relay restriction information is used to indicate the number of relay devices to which the remote UE can connect, and / or the remote UE's AMBR that can be used for relaying.

[0200] 1002. The remote UE performs relay discovery with the relay UE and establishes a relay service connection.

[0201] When a remote UE is already connected to a cellular network and finds that the communication quality of the Uu interface between the remote UE and the base station does not meet communication requirements, the remote UE can request to connect to the network via a relay. The remote UE can initiate a relay service request, or the base station or core network can instruct the remote UE to connect to the network via a relay.

[0202] The relay discovery process is described above and will not be described here. The remote UE can obtain the relay UE's identifier in the interactive message with the relay UE. The relay service connection can be a PC5 connection.

[0203] 1003. After the remote UE establishes a relay service connection with the relay UE, the remote UE initiates a relay service request to the AMF / SMF through the base station.

[0204] In a specific implementation, taking the AMF as an example, the remote UE can initiate a relay service request to the AMF via a non-access stratum (NAS) message, requesting to establish a connection to the network via relay. The NAS message includes information about the relay device to which the remote UE is connected, which can be the relay device identifier (relay UE ID).

[0205] Alternatively, the remote UE sends an RRC message to the base station via the relay UE. The RRC message includes an NAS message. After receiving the RRC message, the base station forwards the NAS message to the AMF. The NAS message also includes the binding relationship between the remote UE and the relay UE. Based on the binding relationship between the remote UE and the relay UE, the AMF can determine which relay UE the remote UE needs to connect to the network through. The binding relationship between the remote UE and the relay UE can be a corresponding relationship between the identifiers of the remote UE and the relay UE.

[0206] Taking the SMF as an example, the remote UE sends a PDU Session Establishment Request message or a PDU Session Change Request message to the SMF to initiate a relay service request. The PDU Session Establishment Request message or the PDU Session Change Request message includes information about the relay device to which the remote UE is connected, requesting that a connection be established with the network through the relay device.

[0207] It should be noted that in step 1003, the remote UE sends a message to the base station for initiating a relay service. The message may include indication information indicating that the remote UE is connected to the network via a relay. After receiving the message, the base station initiates a relay service request to the AMF via an N2 message carrying the indication information; or, the base station initiates a relay service request to the SMF via an N2SM message carrying the indication information.

[0208] In another possible implementation, in step 1003, when the remote UE sends a message to the base station through the relay UE, such as a NAS message, a service request message, a PDU session establishment or change message, etc., the base station can determine that the remote UE is connected to the base station through the relay UE based on the received message. For example, the base station determines that the remote UE is connected to the base station through the relay UE through the message format, or information of the Uu interface protocol stack. After receiving these messages, the base station can also send a relay service request message to the AMF through the N2 message, which is used to notify the AMF that "the remote UE is connected to the network through a relay." For example, the N2 message carries indication information, which is used to indicate that "the remote UE is connected to the network through a relay." Alternatively, when the base station receives these messages and needs to forward them to the AMF, it can carry the above-mentioned indication information with the message.

[0209] Alternatively, after receiving these messages and determining that the remote UE is connected to the base station via a relay UE, the base station sends a relay service request message to the SMF via an N2SM message. This message is used to notify the SMF that the remote UE is connected to the network via a relay. For example, the N2SM message carries indication information indicating that the remote UE is connected to the network via a relay. Alternatively, when the base station receives these messages and needs to forward them to the SMF, it can carry the above indication information with the message.

[0210] In this way, AMF / SMF can learn that "the remote UE is connected to the network through relay", so that it can manage the remote UE's relay service based on the remote UE's relay restriction information, and prevent the remote UE from connecting to too many relay devices and excessively occupying relay resources.

[0211] 1004. AMF / SMF obtains the relay restriction information of the remote UE and the current relay status information of the remote UE.

[0212] The current relay situation information of the remote UE may be the number of relay devices to which the remote UE is currently connected, or may be the AMBR currently used for relay by the remote UE.

[0213] In the specific implementation, the AMF / SMF can store the remote UE's contract information locally. If the AMF / SMF does not have the remote UE's contract information locally, the AMF / SMF can obtain the remote UE's contract information from the UDM or UDR.

[0214] The subscription information of the remote UE includes the authorization information of whether the remote UE can use the relay access network, and the relay restriction information of the remote UE. At the same time, the AMF / SMF can obtain the current relay status information of the remote UE from the UDM or UDR or unstructured data storage function network element (UDSF). The current relay status information of the remote UE can be stored in the UE context. If the remote UE does not have a UE context in the core network, the AMF / SMF can create a UE context for the remote UE.

[0215] 1005. AMF / SMF determines whether remote UE access is allowed.

[0216] Specifically, the number of relay devices to which the remote UE is connected is compared with the number of relay devices to which the remote UE can be connected. If the number of relay devices to which the remote UE is connected does not exceed the number of relay devices to which the remote UE can be connected, the remote UE is allowed to access the network through the relay UE. If the number of relay devices to which the remote UE is connected is equal to the number of relay devices to which the remote UE can be connected, the remote UE is not allowed to access the network through the relay UE, and the remote UE's relay request is rejected.

[0217] And / or, the AMBR used by the remote UE for relaying is compared with the AMBR available for relaying by the remote UE. If the AMBR used by the remote UE for relaying does not exceed the AMBR available for relaying by the remote UE, the remote UE is allowed to access the network through the relay UE. If the AMBR used by the remote UE for relaying is equal to the AMBR available for relaying by the remote UE, the remote UE is not allowed to access the network through the relay UE, and the remote UE's relay request is rejected.

[0218] If the remote UE is allowed to connect to the network through the relay, step 1006 is executed. The AMF / SMF may also update the current relay information of the remote UE, i.e., increase the number of relays for the remote UE's new connection. Optionally, the identifier of the relay UE to which the remote UE is bound for the new connection may be added.

[0219] If the remote UE is not allowed to connect to the network through the relay, step 1007 is executed.

[0220] 1006. AMF / SMF sends the updated relay status information to UDM (or UDR or UDSF).

[0221] The UDM (or UDR or UDSF) stores the latest updated relay status information so that the latest relay status of the remote UE can be subsequently queried from the UDM (or UDR or UDSF) to determine whether the relay upper limit of the remote UE is exceeded.

[0222] 1007. Feedback an indication message to the remote UE, indicating that the remote UE is not allowed to establish a relay connection.

[0223] The indication message may further include that the reason for rejecting the establishment of the relay connection is that the upper limit of the relay connection of the remote UE is exceeded, that is, the number of relay devices currently connected to the remote UE has reached the upper limit.

[0224] 1008. When the remote UE is allowed to connect to the network through the relay UE, the remote UE initiates a PDU session establishment or modification process.

[0225] In one possible implementation, when the remote UE is disconnected from the relay, the AMF / SMF updates the UE context or performs the operation of step 5 to notify the UDM or UDR or UDSF to update the record information of the remote UE using the relay, or sends the updated information to the UDM or UDR or UDSF.

[0226] It should be noted that after executing step 1006, step 1008 is executed. That is, only when the remote UE's current relay service request is allowed, the remote UE will establish or modify the session, and the relay UE can forward the session to provide relay services to the remote UE. If step 1007 is executed, step 1008 is not required.

[0227] Figure 10 In the method shown, the network side (AMF / SMF) can limit the number of relays connected when the UE accesses the network via relay according to the relay restriction information in the UE subscription information, to prevent a remote UE from occupying too many relay resources and bandwidth resources.

[0228] refer to Figure 11 , an embodiment of the present application also provides a relay management method, taking the first terminal device as a remote UE, the second terminal device as a relay UE, and the network device as an AMF / SMF as an example. Figure 11 The method shown is applicable to layer 2 relay scenarios or layer 3 relay scenarios. When a remote UE expects to access the network through a relay, the relay UE initiates a relay service request. The AMF / SMF can control the relay service request and allow or reject the relay service request initiated by the relay UE. Figure 11 As shown, the method includes the following steps:

[0229] 1101. The remote UE performs relay discovery with the relay UE and establishes a relay service connection.

[0230] When a remote UE is already connected to a cellular network and finds that the communication quality of the Uu interface between the remote UE and the base station does not meet communication requirements, the remote UE can request to connect to the network via a relay. The remote UE can initiate a relay service request, or the base station or core network can instruct the remote UE to connect to the network via a relay.

[0231] When a remote UE accesses the network using a Layer 3 relay, there is no signaling interaction between the remote UE and the base station or core network. The relay UE can initiate a relay service request, and the core network can verify whether the remote UE is allowed to access the network through the relay UE. When a remote UE needs to access the network using a Layer 2 relay, it can initiate a relay service request to a core network element, and the core network can verify whether the remote UE is allowed to access the network through the relay UE. The relay UE obtains the remote UE's identity during its interaction with the remote UE.

[0232] The relay discovery process is described above and will not be described here. The remote UE can obtain the relay UE's identifier in the interactive message with the relay UE. The relay service connection can be a PC5 connection.

[0233] 1102. The relay UE sends a relay service request message to the AMF / SMF via a NAS message.

[0234] The relay service request message, i.e., the first message described in the embodiment of the present application, may include the identifier (remote UE ID) of the remote UE that needs to access the network via relay. Optionally, a relay service indication may be added to the NAS message. The relay service indication is used to notify the network side (AMF / SMF) that the relay UE needs to provide relay service for the remote UE.

[0235] In one possible implementation, the relay service request message can be sent to the AMF / SMF together with the PDU session establishment or change request message when the relay UE establishes or changes the PDU session for the remote UE.

[0236] Specifically, the relay UE sends the PDU session establishment or change request message as an N1 session management container (N1 SM container) to the AMF / SMF via a NAS message. The N1 SM container may include: the PDU session establishment or change request, the PDU session ID, etc. The NAS message may also include the ID of the remote UE.

[0237] 1103. AMF / SMF sends the remote UE ID to UDM or UDR.

[0238] Optionally, AMF / SMF can also send relay UE ID, relay UE capability information, and relay service information to UDM (or UDR).

[0239] In one possible implementation, the UDM or UDR may maintain a set of data, the data header (Key) may be the identifier of the remote UE, and the data content may be the relay restriction information of the remote UE. Optionally, the data content may also include the relay identifier (Relay ID) to which the remote UE is connected, the capability information of the relay (layer 2 or layer 3 relay), the service information (RSC) of the relay, service-related information (Service ID, Application ID, data network name (DNN) and / or single network slice selection assistance information (S-NSSAI).

[0240] 1104. The UDM (or UDR) verifies whether the remote UE is allowed to access the network through the relay UE.

[0241] Specifically, the UDM (or UDR) verifies whether the number of relay devices to which the remote UE is connected exceeds the limit of the relay restriction information of the remote UE.

[0242] The UDM (or UDR) checks the remote UE's subscription data based on the remote UE ID. Based on the relay restriction information, it determines whether the number of relay devices the remote UE is currently connected to exceeds the upper limit. For example, this may include whether the number of relay devices the remote UE is currently connected to exceeds the number of relay devices the remote UE can connect to, or whether the AMBR currently used by the remote UE for relaying exceeds the AMBR available for relaying by the remote UE.

[0243] If the upper limit is not exceeded, the UDM (or UDR) sends feedback information to the AMF / SMF, indicating that the relay connection is allowed to be established. The UDM (or UDR) can also update the relay situation information of the remote UE, for example, update the number of relay devices to which the remote UE is currently connected, or update the AMBR currently used for relay by the remote UE.

[0244] If the upper limit is exceeded, UDM (or UDR) sends feedback information to AMF / SMF, indicating that the relay connection establishment is rejected.

[0245] In another possible implementation, the AMF / SMF verifies whether the remote UE is allowed to access the network through the relay UE. When the AMF / SMF obtains the relay service request message, the AMF / SMF may use the data update service (e.g., Nudr_DM_Update service in TS23.501) to obtain the relay situation information of the remote UE and the relay restriction information of the remote UE from the UDM (or UDR). Verify whether the remote UE is allowed to access the network through the relay UE based on the relay situation information of the remote UE and the relay restriction information of the remote UE.

[0246] 1105. UDM (or UDR) sends feedback information to AMF / SMF.

[0247] The feedback information may indicate whether to allow the remote UE to establish the relay connection, or to deny the remote UE from establishing the relay connection.

[0248] Optionally, when the feedback information indicates that the remote UE is rejected from establishing a relay connection, the feedback information may further include a rejection reason value, where the rejection original value may indicate that the rejection reason is that the number of relay devices to which the remote UE is connected exceeds a limit.

[0249] 1106. Optionally, the AMF / SMF sends feedback information to the relay UE.

[0250] If in step 1102, the relay UE sends a relay service request message alone instead of initiating a relay service request through a PDU session establishment or change request message, the AMF / SMF sends feedback information to the relay UE based on the feedback information obtained from the UDM or UDR, indicating whether the remote UE is allowed to access the network through the relay UE.

[0251] 1107. Optionally, the relay UE forwards the feedback information from the AMF / SMF to the remote UE.

[0252] It should be noted that in step 1102, the relay UE carries the PDU session establishment or change message in the NAS message. When the feedback information received by the AMF / SMF indicates that the remote UE is allowed to access the network through the relay UE, the AMF / SMF directly forwards the PDU session establishment or change message of the relay UE to the SMF. Skip steps 1006 and 1007 and execute step 1008.

[0253] When the feedback information received by the AMF / SMF indicates that the remote UE is denied (not allowed) to access the network through the relay UE, the AMF / SMF executes step 1006 and the relay UE executes step 1007, indicating that the remote UE is not allowed to access the network through the relay UE.

[0254] 1108. The relay UE changes or establishes a PDU session for the remote UE.

[0255] It should be noted that Figure 11 The method shown is applicable to Layer 2 relay scenarios when the PDU session is modified or established by the remote UE.

[0256] 1109. When the remote UE is disconnected from the relay UE, the relay UE notifies the AMF / SMF that it has disconnected from the remote UE.

[0257] In the specific implementation, in the layer 3 relay scenario, the relay UE notifies the AMF or SMF that "the relay UE has disconnected from the remote UE".

[0258] In the Layer 2 relay scenario, the relay UE can notify the base station that "the relay UE has disconnected from the remote UE", and the base station then notifies the AMF or SMF that "the relay UE has disconnected from the remote UE". Alternatively, after the base station does not obtain any information about the remote UE within a certain period of time, it directly sends a message to the AMF or SMF to notify the AMF or SMF that "the relay UE has disconnected from the remote UE".

[0259] 1110. AMF / SMF instructs UDM / UDR to update the relay status information of the remote UE.

[0260] Specifically, UDM / UDR can reduce the number of relay devices that the remote UE has connected to by one, or reduce the AMBR that the remote UE has used for relay by p, where p can be the session granularity AMBR (session-AMBR) when the remote UE accesses the network through relay. In the layer 2 scenario, the remote UE establishes or updates a PDU session, and the relay UE forwards the PDU session to provide relay service for the remote UE. The session granularity AMBR can be the session-AMBR of the PDU session. In the layer 3 scenario, the relay UE establishes or updates a PDU session to provide relay service for the remote UE. The session granularity AMBR can be the session-AMBR of the PDU session.

[0261] Figure 11 In the method shown, the network side (AMF / SMF) can limit the number of relays connected when the UE accesses the network via relay according to the relay restriction information in the UE subscription information, to prevent a remote UE from occupying too many relay resources and bandwidth resources.

[0262] In the case of dividing each functional module into corresponding functional modules, Figure 12 A possible structural diagram of the communication device involved in the above embodiments is shown. Figure 12 The communication device shown may be the network device described in the embodiment of the present application, or may be a component in the network device that implements the above method, or may be a chip used in the network device. The network device may be Figure 9 The network device in the method shown, Figure 10 or Figure 11 The AMF / SMF in the method shown. The chip can be a system-on-a-chip (SOC) or a baseband chip with communication functions. Figure 12 As shown, the communication device includes a processing unit 1201 and a communication unit 1202. The processing unit may be one or more processors, and the communication unit may be a transceiver or a communication interface.

[0263] The processing unit 1201 , for example, may be configured to support the network device in executing step 903 , or step 1005 , and / or other processes for the technology described herein.

[0264] The communication unit 1202 is used to support communication between the network device and other communication devices, for example, to support the network device to execute one or more steps of step 901, step 901, step 1003, step 1004, step 1006 and step 1007, and / or other processes for the technology described in this document.

[0265] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0266] like Figure 13 As shown, the communication device may further include a storage unit 1203, and the storage unit 1203 is used to store program codes and / or data of the communication device.

[0267] The processing unit 1201 may include at least one processor, the communication unit 1202 may be a transceiver or a communication interface, and the storage unit 1203 may include a memory.

[0268] In the case of dividing each functional module into corresponding functional modules, Figure 14 A possible structural diagram of the communication device involved in the above embodiments is shown. Figure 14 The communication device shown can be the terminal device described in the embodiment of the present application, or a component in the terminal device that implements the above method, or a chip used in the terminal device. The chip can be a system-on-a-chip (SOC) or a baseband chip with communication functions. Figure 14 As shown, the communication device includes a processing unit 1401 and a communication unit 1402. The processing unit 1401 may be one or more processors, and the communication unit 1402 may be a transceiver or a communication interface.

[0269] The processing unit 1401 is used to support the terminal device to perform internal processing, generate messages, etc., and / or other processes for the technology described in this article.

[0270] The communication unit 1402 is used to support communication between the terminal device and other communication devices, for example, supporting the terminal device to execute step 901, step 1003, step 1007, step 1103, step 1107 and / or other processes for the technology described in this article.

[0271] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0272] like Figure 15 As shown, the communication device may further include a storage unit 1403, and the storage unit 1403 is used to store program codes and data of the communication device.

[0273] The processing unit 1401 may include at least one processor, the communication unit 1402 may be a transceiver or a communication interface, and the storage unit 1403 may include at least one memory.

[0274] It should be noted that, in the above-mentioned embodiments of the communication device, each unit may also be correspondingly referred to as a module, component, circuit, etc.

[0275] The embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions; the instructions are used to execute the following Figure 9 or Figure 10 or Figure 11 The method shown.

[0276] The embodiment of the present application provides a computer program product including instructions, which, when executed on a communication device, enables the communication device to perform the following Figure 9 or Figure 10 or Figure 11 The method shown.

[0277] The embodiment of the present application provides a wireless communication device, comprising: a wireless communication device storing an instruction; when the wireless communication device is in Figure 8a 、 Figure 8b 、 Figures 12 to 15 When the communication device shown is running, the communication device performs the following Figure 9 or Figure 10 or Figure 11 The wireless communication device may be a chip.

[0278] The embodiment of the present application also provides a communication system, including: a terminal device and a network device. For example, the terminal device may be Figure 8a 、 Figure 14 、 Figure 15 The communication device shown, the network device can be Figure 8b 、 Figure 12 、 Figure 13 The communication device shown.

[0279] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the communication device can be divided into different functional modules to complete all or part of the functions described above.

[0280] The processor in the embodiments of the present application may include but is not limited to at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., various types of computing devices that run software, each of which may include one or more cores for executing software instructions to perform operations or processing. The processor may be a separate semiconductor chip, or it may be integrated into a semiconductor chip together with other circuits. For example, it may form an SoC (system on chip) with other circuits (such as a codec circuit, a hardware acceleration circuit, or various bus and interface circuits), or it may be integrated into the ASIC as a built-in processor of an ASIC. The ASIC with the integrated processor may be packaged separately or with other circuits. In addition to the core for executing software instructions to perform operations or processing, the processor may further include necessary hardware accelerators, such as a field programmable gate array (FPGA), a PLD (programmable logic device), or a logic circuit that implements dedicated logic operations.

[0281] The memory in the embodiments of the present application may include at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0282] In the present application, "at least one" refers to one or more. "Multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different.

[0283] In the several embodiments provided in this application, it should be understood that the disclosed database access device and method can be implemented in other ways. For example, the above-described database access device embodiment is merely illustrative. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interface, and the indirect coupling or communication connection of the database access device or unit can be electrical, mechanical or other forms.

[0284] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0285] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0286] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0287] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A relay management method, characterized in that: include: The network device obtains an identifier of the first terminal device, and obtains relay restriction information of the first terminal device according to the identifier of the first terminal device; The relay restriction information is used to indicate the number of relay devices to which the first terminal device can connect, and / or the aggregate maximum bit rate AMBR that the first terminal device can use for relaying; The network device determines whether to allow the first terminal device to access the network through a second terminal device based on the relay restriction information of the first terminal device; the second terminal device is a relay device of the first terminal device.

2. The method according to claim 1, characterized in that The network device obtains the identifier of the first terminal device, including: The network device receives a first message from the first terminal device, where the first message includes an identifier of the first terminal device and an identifier of the second terminal device, or the first message includes an identifier of the second terminal device, and the first message is used to indicate that the first terminal device requests to access the network through the second terminal device.

3. The method according to claim 1, characterized in that The network device obtains the identifier of the first terminal device, including: The network device receives a first message from the second terminal device, where the first message includes an identifier of the first terminal device and an identifier of the second terminal device, or the first message includes an identifier of the first terminal device, and the first message is used to indicate that the first terminal device requests to access the network through the second terminal device.

4. The method according to claim 2 or 3, characterized in that The network device acquiring relay restriction information of the first terminal device according to the identifier of the first terminal device includes: In response to the first message, sending a second message to a unified data management network element or a unified data storage network element; the second message is used to request relay restriction information of the first terminal device, and the second message includes an identifier of the first terminal device; The relay restriction information of the first terminal device is received from the unified data management network element or the unified data storage network element.

5. The method according to any one of claims 1 to 3, characterized in that The network device determines, according to the relay restriction information of the first terminal device, whether to allow the first terminal device to access the network through the second terminal device, including: If the number of relay devices currently connected to the first terminal device does not exceed the number of relay devices that the first terminal device can connect to, allowing the first terminal device to access the network through the second terminal device; if the number of relay devices currently connected to the first terminal device is equal to the number of relay devices that the first terminal device can connect to, denying the first terminal device from accessing the network through the second terminal device; and / or, If the AMBR currently used by the first terminal device for relaying does not exceed the AMBR that the first terminal device can use for relaying, the first terminal device is allowed to access the network through the second terminal device; if the AMBR currently used by the first terminal device for relaying is equal to the AMBR that the first terminal device can use for relaying, the first terminal device is denied access to the network through the second terminal device.

6. The method according to claim 5, characterized in that The method further comprises: The network device obtains the number of relay devices to which the first terminal device is currently connected and / or the AMBR currently used for relaying by the first terminal device from a unified data management network element or a unified data storage network element.

7. The method according to claim 5, characterized in that The method further comprises: If the first terminal device is allowed to access the network through the second terminal device, the network device updates the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device; Send the updated number of relay devices currently connected to the first terminal device and / or the updated AMBR currently used for relaying by the first terminal device to the unified data management network element or the unified data storage network element.

8. The method according to claim 5, characterized in that The method further comprises: If the network device allows the first terminal device to access the network through the second terminal device, it sends a third message to the unified data management network element or the unified data storage network element, so that the unified data management network element or the unified data storage network element updates the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device according to the third message. The third message is used to indicate that the network device allows the first terminal device to access the network through the second terminal device.

9. The method according to claim 8, characterized in that The third message includes the identifier of the second terminal device.

10. The method according to claim 5, characterized in that The method further comprises: If the network device refuses the first terminal device to access the network through the second terminal device, it sends a fourth message to the first terminal device or the second terminal device; the fourth message is used to indicate that the network device refuses the first terminal device to access the network through the second terminal device.

11. The method according to claim 10, characterized in that The fourth message includes a failure reason value; the failure reason value is used to characterize that the failure reason is that the number of relay devices currently connected to the first terminal device is equal to the number of relay devices to which the first terminal device can be connected, or the AMBR currently used for relaying by the first terminal device is equal to the AMBR that can be used for relaying by the first terminal device.

12. The method according to any one of claims 1 to 3, characterized in that The relay restriction information includes first relay restriction information and second relay restriction information; the first relay restriction information includes the number of relay devices that can be connected when the first terminal device performs the first service, and / or the AMBR that can be used for relaying when the first terminal device performs the first service; the second relay restriction information includes the number of relay devices that can be connected when the first terminal device performs the second service, and / or the AMBR that can be used for relaying when the first terminal device performs the second service.

13. The method according to any one of claims 1 to 3, characterized in that The network device is an access mobility management network element of the first terminal device, or a session management network element of the first terminal device, or an access mobility management network element of the second terminal device, or a session management network element of the second terminal device.

14. A relay management method, characterized in that: include: receiving a second message from the network device; the second message is used to request relay restriction information of the first terminal device, and the second message includes an identifier of the first terminal device; Sending relay restriction information of the first terminal device to the network device; The relay restriction information is used to indicate the number of relay devices to which the first terminal device can connect, and / or the aggregate maximum bit rate AMBR that the first terminal device can use for relaying.

15. The method according to claim 14, characterized in that The method further comprises: Sending to the network device the number of relay devices to which the first terminal device is currently connected, and / or the AMBR currently used for relaying by the first terminal device.

16. The method according to claim 14 or 15, characterized in that The method further comprises: Receive from the network device an updated number of relay devices to which the first terminal device is currently connected and / or an updated AMBR currently used for relaying by the first terminal device.

17. The method according to claim 14 or 15, characterized in that The method further comprises: receiving a third message from the network device, where the third message is used to indicate that the network device allows the first terminal device to access the network through the second terminal device; In response to the third message, the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device are updated.

18. A communication device, characterized in that: include: a processing unit, configured to obtain an identifier of a first terminal device, and obtain relay restriction information of the first terminal device according to the identifier of the first terminal device; The relay restriction information is used to indicate the number of relay devices to which the first terminal device can connect, and / or the aggregate maximum bit rate AMBR that the first terminal device can use for relaying; The processing unit is further configured to determine whether the first terminal device is allowed to access the network through a second terminal device according to the relay restriction information of the first terminal device; the second terminal device is a relay device of the first terminal device.

19. The device according to claim 18, characterized in that Also includes a communication unit, The communication unit is used to receive a first message from the first terminal device, where the first message includes an identifier of the first terminal device and an identifier of the second terminal device, or the first message includes an identifier of the second terminal device, and the first message is used to indicate that the first terminal device requests to access the network through the second terminal device.

20. The communication device according to claim 18, wherein Also includes a communication unit, The communication unit is used to receive a first message from the second terminal device, where the first message includes an identifier of the first terminal device and an identifier of the second terminal device, or the first message includes an identifier of the first terminal device, and the first message is used to indicate that the first terminal device requests to access the network through the second terminal device.

21. The device according to claim 19 or 20, characterized in that The processing unit is configured to, in response to the first message, send a second message to the unified data management network element or the unified data storage network element through the communication unit; the second message is used to request relay restriction information of the first terminal device, and the second message includes an identifier of the first terminal device; The relay restriction information of the first terminal device is received from the unified data management network element or the unified data storage network element through the communication unit.

22. The device according to any one of claims 18 to 20, characterized in that The processing unit is specifically configured to allow the first terminal device to access the network through the second terminal device if the number of relay devices currently connected to the first terminal device does not exceed the number of relay devices connectable to the first terminal device; and deny the first terminal device from accessing the network through the second terminal device if the number of relay devices currently connected to the first terminal device is equal to the number of relay devices connectable to the first terminal device; and / or If the AMBR currently used by the first terminal device for relaying does not exceed the AMBR that the first terminal device can use for relaying, the first terminal device is allowed to access the network through the second terminal device; if the AMBR currently used by the first terminal device for relaying is equal to the AMBR that the first terminal device can use for relaying, the first terminal device is denied access to the network through the second terminal device.

23. The device according to claim 21, characterized in that The processing unit is used to obtain the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device from the unified data management network element or the unified data storage network element through the communication unit.

24. The device according to claim 22, characterized in that The processing unit is further configured to, if the first terminal device is allowed to access the network through the second terminal device, update the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device; The updated number of relay devices currently connected to the first terminal device and / or the updated AMBR currently used for relaying by the first terminal device are sent to the unified data management network element or the unified data storage network element through the communication unit.

25. The device according to claim 22, characterized in that The processing unit is also used to send a third message to the unified data management network element or the unified data storage network element through the communication unit if the first terminal device is allowed to access the network through the second terminal device, so that the unified data management network element or the unified data storage network element updates the number of relay devices currently connected to the first terminal device and / or the AMBR currently used for relaying by the first terminal device according to the third message. The third message is used to indicate that the network device allows the first terminal device to access the network through the second terminal device.

26. The device according to claim 25, characterized in that The third message includes the identifier of the second terminal device.

27. The device according to claim 22, characterized in that The processing unit is also used to send a fourth message to the first terminal device or the second terminal device through the communication unit if the first terminal device is denied access to the network through the second terminal device; the fourth message is used to indicate that the network device denies the first terminal device access to the network through the second terminal device.

28. The device according to claim 27, characterized in that The fourth message includes a failure reason value; the failure reason value is used to characterize that the failure reason is that the number of relay devices currently connected to the first terminal device is equal to the number of relay devices to which the first terminal device can be connected, or the AMBR currently used for relaying by the first terminal device is equal to the AMBR that can be used for relaying by the first terminal device.

29. The device according to any one of claims 18 to 20, characterized in that The relay restriction information includes first relay restriction information and second relay restriction information; the first relay restriction information includes the number of relay devices that can be connected when the first terminal device performs the first service, and / or the AMBR that can be used for relaying when the first terminal device performs the first service; the second relay restriction information includes the number of relay devices that can be connected when the first terminal device performs the second service, and / or the AMBR that can be used for relaying when the first terminal device performs the second service.

30. The device according to any one of claims 18 to 20, characterized in that The communication device is an access mobility management network element of the first terminal device, or a session management network element of the first terminal device, or an access mobility management network element of the second terminal device, or a session management network element of the second terminal device.

31. A communication device, characterized in that: include: a processing unit configured to receive a second message from the network device via the communication unit; the second message being used to request relay restriction information of the first terminal device, the second message including an identifier of the first terminal device; The processing unit is also used to send relay restriction information of the first terminal device to the network device through the communication unit; the relay restriction information is used to indicate the number of relay devices to which the first terminal device can be connected, and / or the aggregate maximum bit rate AMBR that the first terminal device can use for relaying.

32. The device according to claim 31, characterized in that The processing unit is further configured to send, via the communication unit, to the network device the number of relay devices to which the first terminal device is currently connected, and / or the AMBR currently used for relaying by the first terminal device.

33. The device according to claim 31 or 32, characterized in that The processing unit is further configured to receive, from the network device through the communication unit, an updated number of relay devices to which the first terminal device is currently connected and / or an updated AMBR currently used for relaying by the first terminal device.

34. The device according to claim 31 or 32, characterized in that The processing unit is further configured to receive a third message from the network device through the communication unit, where the third message is used to indicate that the network device allows the first terminal device to access the network through the second terminal device; The processing unit is further configured to, in response to the third message, update the number of relay devices to which the first terminal device is currently connected and / or the AMBR currently used for relaying by the first terminal device.

35. A communication device, characterized in that: comprising a processor coupled to a memory; memory for storing computer programs; A processor, configured to execute the computer program stored in the memory, so that the apparatus performs the method according to any one of claims 1 to 17.

36. A computer-readable storage medium, characterized in that The method comprises a program or an instruction, and when the program or the instruction is executed by a processor, the method according to any one of claims 1 to 17 is performed.

37. A computer program product, characterized in that The computer program product comprises instructions which, when executed, cause the method according to any one of claims 1 to 17 to be performed.

38. A chip, characterized in that: The chip includes a processor and an interface circuit, wherein the interface circuit is coupled to the processor, and the processor is configured to run a computer program or instruction so that the method according to any one of claims 1 to 17 is executed.

Images