Method and apparatus for service assurance

Abstract

The embodiment of the present application provides a service guarantee method and device, the service guarantee method is applied to the scene that a remote terminal device accesses a network through a relay device, and the method comprises the following steps: a policy control network element generates a second quality of service (QoS) parameter of a second communication interface between the remote terminal device and the relay device in a PCC rule generated based on subscription data of the remote terminal device, so that a session management network element can generate a second QoS rule corresponding to the second communication interface based on the received PCC rule, and the session management network element can send the second QoS rule to the relay device. By generating the QoS rule required by the second communication interface based on the subscription data of the remote terminal device, the performance of the remote terminal device in accessing services through the relay device can be guaranteed.

Description

[0001] This application claims priority from the Chinese patent application No. 202010303982.7 filed on April 17, 2020, and entitled "Method and apparatus for service guarantee", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication, and more particularly, to a method and apparatus for service guarantee. BACKGROUND

[0003] In the fourth generation (4th generation, 4G) communication protocol, a proximity-based services (ProSe) relay communication scheme is defined. At present, the protocol stipulates that the ProSe relay communication scheme is only used for accessing public safety services, so the communication interface (such as PC5 interface) established between the remote terminal device and the relay device only needs to support the quality of service (QoS) guarantee for the public safety service to execute.

[0004] In the currently discussed ProSe relay communication scenario, the remote terminal device can access various services in the network (such as accessing augmented reality (AR) or virtual reality (VR) services, etc.) through the relay device, and is no longer limited to public safety services. Therefore, the QoS rules stipulated in the current protocol may no longer meet the actual QoS guarantee required by the service. Therefore, how to enable the remote terminal device to access different services through the relay device becomes a problem to be solved. SUMMARY

[0005] The present application provides a method and apparatus for service guarantee, in order to improve the performance of the remote terminal device accessing services through the relay device.

[0006] In a first aspect, a method for service guarantee is provided. The method for service guarantee can be executed by a policy control network element, or can also be executed by a chip or circuit disposed in the policy control network element, and the present application does not make any limitation in this regard.

[0007] The method for service guarantee is applied to the case where the remote terminal device accesses the network through the relay device, and the method comprises the following steps.

[0008] The policy control network element obtains a first identifier of the remote terminal device, the first identifier being used to obtain subscription data of the remote terminal device; the policy control network element generates a policy and charging control (PCC) rule based on the subscription data of the remote terminal device, and sends the PCC rule to the session management network element, wherein the PCC rule includes a first quality of service (QoS) parameter of a first communication interface and a second QoS parameter of a second communication interface, the first communication interface is a communication interface between the relay device and the access network device, and the second communication interface is a communication interface between the relay device and the remote terminal device, the first QoS parameter is used to generate a first QoS rule corresponding to the first communication interface, and the second QoS parameter is used to generate a second QoS rule corresponding to the second communication interface.

[0009] The method for service guarantee provided by the embodiments of the present application can enable the core network device side (for example, the policy control network element) to obtain the subscription data of the remote terminal device based on the received first identifier of the remote terminal device, and generate a PCC rule based on the subscription data of the remote terminal device, wherein the second QoS parameter in the PCC rule is used to generate a QoS rule corresponding to the second communication interface between the relay device and the remote terminal device, and the QoS rule generated in consideration of the subscription data of the remote terminal device is more in line with the actual QoS guarantee of the remote terminal device accessing services than the QoS rule set only based on the subscription data of the relay service type or the relay device.

[0010] Specifically, the session management network element can generate the above-mentioned second QoS rule because it receives the PCC rule including the second QoS parameter from the policy control network element, and the second QoS parameter is used to generate the second QoS rule, so that the QoS rule generated by the session management network element meets the requirements of the second communication interface.

[0011] With reference to the first aspect, in some implementations of the first aspect, the method further includes: the policy control network element obtaining Internet protocol (IP) address information of the remote terminal device; and the policy control network element determining flow description information based on the IP address information, and the flow description information is carried in the PCC rule.

[0012] The method for service guarantee provided by the embodiments of the present application can enable the policy control network element to determine the flow description information in the PCC rule based on the obtained IP address information.

[0013] With reference to the first aspect, in some implementations of the first aspect, the policy control network element obtaining the first identifier of the remote terminal device comprises: the policy control network element receiving a second message from a session management network element, the second message comprising the first identifier of the remote terminal device; or the policy control network element receiving a policy authorization request message from an application network element, the policy authorization request message comprising a second identifier of the remote terminal device, wherein the second identifier is used to determine the first identifier.

[0014] In the embodiments of the present application, the policy control network element can obtain the first identifier of the remote terminal device in different ways, thereby improving the flexibility of the scheme.

[0015] With reference to the first aspect, in some implementations of the first aspect, the second identifier comprises at least one of the following identifiers: a general public user identity (GPSI) of the remote terminal device, a third-party assigned user identifier of the remote terminal device, an IPv6 address of the remote terminal device, an IPv6 address prefix of the remote terminal device, an IPv4 address of the relay device, and an identifier composed of a TCP / UDP port number.

[0016] In the embodiments of the present application, the second identifier of the remote terminal device has various specific forms, thereby improving the flexibility of the scheme.

[0017] With reference to the first aspect, in some implementations of the first aspect, the second message further comprises session management subscription data of the remote terminal device, the session management subscription data comprising an aggregate maximum bit rate (AMBR) of the remote terminal device, and the second QoS parameter comprising an AMBR available to the remote terminal device.

[0018] With reference to the first aspect, in some implementations of the first aspect, the policy authorization request message further comprises: an identifier of a service and / or a QoS parameter requirement, the identifier of the service being used to indicate a service type, and the QoS parameter requirement being used to assist the policy control network element in generating the PCC rule based on.

[0019] In addition to the second identifier of the remote terminal device, the policy authorization request message sent by the application network element to the policy control network element can further comprise a QoS parameter requirement to assist the policy control network element in generating the PCC rule based on.

[0020] In some implementations of the first aspect, the identity of the service includes at least one of the following: a first Relay Service Code (Relay Service Code or Relay Service Filter, hereinafter referred to as Relay Service Code), a second Relay Service Code, an application identity APP ID, a Proximity Service application name ProSe APP ID; wherein the first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device.

[0021] There are various specific forms of the identity of the service in the embodiments of the present application, which improves the flexibility of the scheme.

[0022] In some implementations of the first aspect, before the policy control network element receives the policy authorization request message from the application network element, the method further includes: the policy control network element receiving a subscription message from the application network element, the subscription message being used to subscribe to whether the remote terminal device is online; and the policy control network element sending a notification message to the application network element, the notification message being used to indicate that the remote terminal device is online.

[0023] The application network element sends the policy authorization request message to the policy control network element because the application network element learns that the remote terminal device is online.

[0024] In some implementations of the first aspect, the notification message includes the first identity and an identity of a service, and the identity of the service is used to identify a service type.

[0025] The notification message includes the first identity and the identity of the service, so as to facilitate the application network element to issue a policy authorization request message corresponding to the service, and improve the accuracy of the scheme.

[0026] In some implementations of the first aspect, the second message and / or the policy authorization request message further comprises: a first Relay Service Code and / or a second Relay Service Code, wherein the first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device; and the policy control network element generates a policy and charging control (PCC) rule based on subscription data of the remote terminal device.

[0027] Further, the policy control network element can also obtain the Relay Service Code configured for the relay device and / or the remote terminal device, so that the policy control network element knows the service type of the service currently initiated when generating the second QoS rule, generates the second QoS rule that is more in line with the requirements of the service based on the service type, and further guarantees the performance of the remote terminal device accessing the service through the relay device.

[0028] In some implementations of the first aspect, the method further comprises: the policy control network element determining a service type based on the first Relay Service Code and / or the second Relay Service Code; or the policy control network element obtaining the service type from a 5G proximity service name management function (DDNMF) network element based on the first Relay Service Code and / or the second Relay Service Code.

[0029] The policy control network element in the embodiments of the present application can directly determine the service type of the service currently initiated based on the first Relay Service Code and / or the second Relay Service Code, and can also obtain the service type of the service currently initiated from the DDNMF network element after signaling interaction with the DDNMF network element. The service type of the service currently initiated is determined through the above two different ways, which can effectively improve the network configuration flexibility.

[0030] In some implementations of the first aspect, the first identifier of the remote terminal device comprises: a general public subscription identity (GPSI) or a user ID allocated for the remote terminal device by a third-party application.

[0031] The first identifier of the remote terminal device in the embodiments of the present application has various specific forms, which can improve the flexibility of the scheme.

[0032] In a second aspect, a service guarantee method is provided, which can be executed by an application network element or a chip or circuit arranged in the application network element, and the present application does not limit this.

[0033] The service guarantee method includes:

[0034] The application network element determines a policy authorization request message, and sends the policy authorization request message to a policy control network element, wherein the policy authorization request message includes a second identifier of a remote terminal device, the remote terminal device is a terminal device accessing a network through another terminal device, and the second identifier of the remote terminal device is used to determine a first identifier of the remote terminal device, the first identifier of the remote terminal device is used to obtain subscription data of the remote terminal device, the subscription data of the remote terminal device is used to determine a second quality of service (QoS) rule, and the second QoS rule is a QoS rule corresponding to a second communication interface between the relay device and the remote terminal device.

[0035] The service guarantee method provided in the embodiments of the present application can enable a core network device side (for example, a policy control network element) to obtain subscription data of a remote terminal device based on a received first identifier of the remote terminal device, generate a PCC rule based on the subscription data of the remote terminal device, and use a second QoS parameter in the PCC rule to generate a QoS rule corresponding to a second communication interface between a relay device and the remote terminal device. The QoS rule generated in consideration of the subscription data of the remote terminal device is more in line with the QoS guarantee of actual access services of the remote terminal device than a QoS rule set only based on the subscription data of the relay device or the relay service type.

[0036] In combination with the second aspect, in some implementations of the second aspect, before the application network element determines the policy authorization request message, the method further includes: the application network element sends a subscription message to the policy control network element, the subscription message is used to subscribe whether the remote terminal device is online; the application network element receives a notification message from the policy control network element, the notification message is used to indicate that the remote terminal device is online; or the application network element obtains information of the policy control network element through a query request message.

[0037] In the embodiments of the present application, before the application network element determines the policy authorization request message, the remote terminal device online event can be subscribed first, or the information of the policy control network element can be actively queried, and then the policy authorization request message is sent to the policy control network element, thereby providing different schemes for triggering the application network element to send the policy authorization request message, and improving the flexibility of the scheme.

[0038] With reference to the second aspect, in some implementations of the second aspect, the application network element determines the policy authorization request message based on the first identifier and a service identifier, the service identifier being used to indicate a service type, wherein the first identifier and the service identifier are carried in the notification message, or the first identifier and the service identifier are obtained by the application network element through user plane perception.

[0039] In the embodiments of the present application, the application network element can determine the policy authorization request message based on the first identifier and the service identifier, and the first identifier and the service identifier can be obtained in different ways, thereby improving the flexibility of the scheme.

[0040] With reference to the second aspect, in some implementations of the second aspect, in the case that the application network element obtains the first identifier and the service identifier through user plane perception, the method further comprises: the application network element perceives that the remote terminal device is online.

[0041] In the embodiments of the present application, the application network element can perceive whether the remote terminal device is online through user plane perception, thereby obtaining the first identifier and the service identifier.

[0042] With reference to the second aspect, in some implementations of the second aspect, the policy authorization request message further comprises: an identifier of a service and / or a QoS parameter requirement, the identifier of the service being used to indicate a service type, and the QoS parameter requirement being used to assist the policy control network element in generating the PCC rule.

[0043] In addition to the second identifier of the remote terminal device, the policy authorization request message sent by the application network element to the policy control network element can further comprise a QoS parameter requirement to assist the policy control network element in generating the PCC rule.

[0044] With reference to the second aspect, in some implementations of the second aspect, the identifier of the service comprises at least one of the following information: a first Relay Service Code, a second Relay Service Code, an application identifier APPID, and a ProSe APP ID, wherein the first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device.

[0045] In the embodiments of the present application, there are various specific forms of the identifier of the service, thereby improving the flexibility of the scheme.

[0046] In some implementations of the second aspect, the second identifier of the remote terminal device includes at least one of the following: a general public user identity (GPSI) of the remote terminal device, a user ID of the remote terminal device assigned by a third party, an IPv6 address of the remote terminal device, an IPv6 address prefix of the remote terminal device, an IPv4 address of the relay device, and an identifier composed of a TCP / UDP port number.

[0047] There are various specific forms of the second identifier of the remote terminal device in the embodiments of the present application, which improves the flexibility of the solutions.

[0048] In a third aspect, a service guarantee method is provided. The service guarantee method can be executed by a session management network element or a chip or circuit disposed in the session management network element, and the present application does not limit this.

[0049] The service guarantee method is applied to a case where a remote terminal device accesses a network through a relay device. The method includes the following steps.

[0050] The session management network element receives a first message from the relay device, and the first message includes a first identifier of the remote terminal device. The session management network element sends a second message to a policy control network element, and the second message includes the first identifier of the remote terminal device. The first identifier of the remote terminal device is used to obtain subscription data of the remote terminal device. The subscription data of the remote terminal device is used to determine a second QoS rule. The second QoS rule is a QoS rule corresponding to a second communication interface between the relay device and the remote terminal device.

[0051] The service guarantee method provided in the embodiments of the present application enables the core network device (e.g., the policy control network element) to obtain the subscription data of the remote terminal device based on the received first identifier of the remote terminal device, and to generate the QoS rule corresponding to the second communication interface between the relay device and the remote terminal device based on the subscription data of the remote terminal device. The QoS rule generated in consideration of the subscription data of the remote terminal device is more consistent with the QoS guarantee of the actual access service of the remote terminal device than the QoS rule set for the public safety service.

[0052] In some implementations of the third aspect, the method further includes: receiving, by the session management network element, a policy and charging control (PCC) rule from the policy control network element, the PCC rule including a first QoS parameter of the first communication interface and a second QoS parameter of the second communication interface, wherein the first communication interface is a communication interface between the relay device and the access network device, and wherein the first QoS parameter is used to generate the first QoS rule corresponding to the first communication interface, and the second QoS parameter is used to generate the second QoS rule.

[0053] In particular, the session management network element is able to generate the two QoS rules described above because it receives the PCC rule including the second QoS parameter from the policy control network element, and the second QoS parameter is used to generate the second QoS rule, so that the QoS rules generated by the session management network element meet the requirements of the second communication interface.

[0054] In some implementations of the third aspect, the method further includes: assigning, by the session management network element, a QoS flow identifier (QFI) to the PCC rule, the QFI being used to uniquely identify a QoS flow corresponding to the PCC rule; and sending, by the session management network element, a third message to the access network device, the third message including the QFI, the first QoS rule, and the second QoS rule.

[0055] Further, after the session management network element receives the PCC rule including the second QoS parameter from the policy control network element, it assigns a QFI to the PCC rule to identify a QoS flow corresponding to the PCC rule, and sends the QFI to the relay device and the remote terminal device through the access network device, so that the relay device, the remote terminal device, and the access network device can identify the QoS flow and perform QoS guarantee corresponding to the QFI.

[0056] In some implementations of the third aspect, the first message and the second message further include a first relay service code (Relay Service Code) and / or a second Relay Service Code, the first Relay Service Code or the second Relay Service Code being used to determine the second QoS rule, wherein the first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device.

[0057] Further, the relay device can also report the Relay Service Code configured for the relay device or the remote terminal device to the core network device through the access network device, so that the core network device knows the service type of the current initiated service when generating the second QoS rule, generates the second QoS rule more in line with the service requirement based on the service type, and further guarantees the performance of the remote terminal device accessing the service through the relay device.

[0058] In some implementations of the third aspect, the second message further includes: an identifier of the relay device and / or an Internet Protocol (IP) address of the remote terminal device.

[0059] The second message can further include the identifier of the relay device and / or the IP address of the remote terminal device.

[0060] In some implementations of the third aspect, the first identifier of the remote terminal device includes a Generic Public Subscription Identifier (GPSI) or a user ID assigned by a third-party application to the remote terminal device.

[0061] The first identifier of the remote terminal device in the embodiments of the present application has various specific forms, which can improve the flexibility of the scheme.

[0062] In a fourth aspect, a service guarantee method is provided, which can be executed by a relay device or a chip or circuit arranged in the relay device, and the present application does not limit this.

[0063] The service guarantee method is applied to the case where a remote terminal device accesses a network through a relay device, and the method includes the following steps.

[0064] The relay device sends a first message to a session management network element, and the first message includes a first identifier of the remote terminal device; the relay device receives a second Quality of Service (QoS) rule from the session management network element, and the second QoS rule is generated based on subscription data of the remote terminal device corresponding to the first identifier; and the relay device performs QoS guarantee on a second communication interface between the relay device and the remote terminal device based on the second QoS rule.

[0065] The method for service guarantee provided in the embodiments of the present application, the relay device reports the first identifier of the remote terminal device to the core network device (for example, a policy control network element) through the access network device, so that the core network device can obtain the subscription data of the remote terminal device based on the received first identifier of the remote terminal device, and generate the QoS rule corresponding to the second communication interface between the relay device and the remote terminal device based on the subscription data of the remote terminal device. The QoS rule generated in the case of considering the subscription data of the remote terminal device is more in line with the QoS guarantee of the actual access service of the remote terminal device than the QoS rule set only for the subscription data of the relay service type or the relay device.

[0066] With reference to the fourth aspect, in some implementations of the fourth aspect, the method further includes: the relay device sending the second QoS rule to the remote terminal device.

[0067] After the relay device receives the second QoS rule from the core network device side through the access network device, the relay device needs to transmit the second QoS rule to the remote terminal device, so that the remote terminal device can also know the second QoS rule, and provide QoS guarantee for the remote terminal device to access services through the relay device.

[0068] With reference to the fourth aspect, in some implementations of the fourth aspect, the first identifier of the remote terminal device includes a general public user identifier GPSI or a user identifier user ID allocated by a third-party application for the remote terminal device.

[0069] The specific forms of the first identifier of the remote terminal device in the embodiments of the present application are various, which can improve the flexibility of the scheme.

[0070] With reference to the fourth aspect, in some implementations of the fourth aspect, the first message further includes: a first relay service code Relay Service Code and / or a second Relay Service Code, the first Relay Service Code or the second Relay Service Code is used to determine the second QoS rule; wherein the first Relay Service Code is the Relay Service Code configured for the remote terminal device, and the second Relay Service Code is the Relay Service Code configured for the relay device.

[0071] Further, the relay device can also report the relay service code configured for itself or the remote terminal device to the core network device through the access network device, so that the core network device learns the service type of the service currently initiated when generating the second QoS rule, generates the second QoS rule more in line with the service requirement based on the service type, and further guarantees the performance of the remote terminal device accessing the service through the relay device.

[0072] In some implementations of the fourth aspect, the first relay service code and / or the second relay service code are associated with session management subscription data of the remote terminal device.

[0073] In some implementations of the fourth aspect, the method further includes: receiving, by the relay device, a fourth message from the session management network element, the fourth message including session management subscription data of the remote terminal device, the session management subscription data including an AMBR of the remote terminal device; and determining, by the relay device, the AMBR of the PC5 link between the relay device and the remote terminal device based on the AMBR of the remote terminal device.

[0074] In some implementations of the fourth aspect, the remote terminal device accessing the network through the relay device includes: establishing a communication connection between the relay device and the remote terminal device; and establishing a protocol data unit (PDU) session between the relay device and the data network, the PDU session being used to transmit the service of the remote terminal device.

[0075] In the embodiments of the present application, the remote terminal device can access the network through the relay device because a communication connection (e.g., a PC5 connection) is established between the remote terminal device and the relay device, and a PDU session for transmitting the service of the remote terminal device is established between the relay device and the data network, so that the remote terminal device can access the service through the relay device.

[0076] In some implementations of the fourth aspect, the relay device includes a terminal device.

[0077] In the embodiments of the present application, the relay device is a terminal device, that is, the remote terminal device and the relay device can both be terminal devices, and in this case, the communication interface between the relay device and the remote terminal device can be referred to as a PC5 interface.

[0078] In a fifth aspect, a service guarantee method is provided, which can be executed by a remote terminal device or a chip or circuit disposed in the remote terminal device, and the present application does not limit this.

[0079] The method for service guarantee is applied to a case that a remote terminal device accesses a network through a relay device, and the method comprises the following steps: the remote terminal device receives a second quality of service (QoS) rule from the relay device, the second QoS rule is generated based on subscription data of the remote terminal device, and the remote terminal device performs QoS guarantee on a second communication interface between the relay device and the remote terminal device based on the second QoS rule.

[0080] The method for service guarantee provided in the embodiments of the present application is that the remote terminal device receives a QoS rule corresponding to a second communication interface between a relay device and the remote terminal device, which is generated based on subscription data of the remote terminal device. The QoS rule generated by considering the subscription data of the remote terminal device is more in line with the actual QoS guarantee of the remote terminal device accessing services than a QoS rule set only according to the subscription data of the relay device or the relay service type.

[0081] In a sixth aspect, a method for service guarantee is provided. The method for service guarantee can be executed by a session management network element or a chip or circuit disposed in the session management network element, which is not limited in the present application.

[0082] The method for service guarantee is applied to a case that a remote terminal device accesses a network through a relay device, and the method comprises the following steps: the remote terminal device receives a second quality of service (QoS) rule from the relay device, the second QoS rule is generated based on subscription data of the remote terminal device, and the remote terminal device performs QoS guarantee on a second communication interface between the relay device and the remote terminal device based on the second QoS rule.

[0083] In the embodiments of the present application, if the session management network element obtains the AMBR of the remote terminal device, the session management network element can determine the maximum bandwidth in the QER of the remote terminal device based on the AMBR of the remote terminal device in the N4 session configuration. Therefore, in the process of performing data packet transmission of the remote terminal device by the user plane network element, the rate of data sent to the remote terminal device can be limited according to the maximum bandwidth of the remote terminal device.

[0084] In combination with the sixth aspect, in some implementations of the sixth aspect, the method further comprises the following step: the session management network element sends a fourth message to the relay device, and the fourth message comprises the AMBR of the remote terminal device.

[0085] In the embodiments of the present application, the session management network element can send the AMBR of the remote terminal device to the relay device, so that the relay device can update the AMBR of the PC5 link to the AMBR of the remote terminal device.

[0086] In combination with the sixth aspect, in some implementations of the sixth aspect, the AMBR of the remote terminal device includes at least one of: a subscribed session-AMBR of the remote terminal device, a UE-PC5-AMBR of the remote terminal device, and a PC5 Link-AMBR of the remote terminal device.

[0087] In combination with the sixth aspect, in some implementations of the sixth aspect, the maximum bandwidth in the QER is the minimum value of the subscribed session-AMBR of the remote terminal device and the UE-PC5-AMBR / PC5 Link-AMBR of the remote terminal device.

[0088] In combination with the sixth aspect, in some implementations of the sixth aspect, the method further includes: the session management network element sending a second message to a policy control network element, the second message including the session management subscription data; the session management network element receiving session-related policies and / or policy and charging control (PCC) rules from the policy control network element, the session-related policies and / or PCC rules including a second QoS parameter of a second communication interface, wherein the second communication interface is a communication interface between the relay device and the remote terminal device, and the second QoS parameter includes an AMBR available to the remote terminal device; and the maximum bandwidth in the QER is the minimum value of the AMBR of the remote terminal device and the AMBR available to the remote terminal device.

[0089] In combination with the sixth aspect, in some implementations of the sixth aspect, the session management network element obtaining the session management subscription data of the remote terminal device includes: the session management network element receiving a first message from the relay device, the first message including a first identifier of the remote terminal device; and the session management network element obtaining the session management subscription data according to the first identifier.

[0090] In combination with the sixth aspect, in some implementations of the sixth aspect, the session management network element obtaining the session management subscription data according to the first identifier includes: the session management network element sending a second request message to a data management network element / data repository network element, the second request message being used to request the session management subscription data, the second request message including the first identifier; and the session management network element receiving a second response message from the data management network element / data repository network element, the second response message including the session management subscription data.

[0091] In some implementations of the sixth aspect, the second request message further includes first indication information, the first indication information being used to indicate that the remote terminal device accesses the network through the relay device.

[0092] In some implementations of the sixth aspect, the session management network element obtaining the session management subscription data according to the first identifier includes: the session management network element sending a third request message to a data network-authentication authorization and accounting (DN-AAA) server, the third request message being used to request the session management subscription data, the third request message including the first identifier; the session management network element receiving a third response message from the DN-AAA server, the third response message including the session management subscription data.

[0093] In some implementations of the sixth aspect, the session management network element obtaining the session management subscription data of the remote terminal device includes: the session management network element receiving a first relay service code and / or a second relay service code from the relay device, the first relay service code and / or the second relay service code being associated with the session management subscription data; the session management network element sending a third request message to a data management network element / data repository network element, the third request message being used to request the session management subscription data, the third request message including the first relay service code and / or the second relay service code; the session management network element receiving a third response message from the data management network element / data repository network element, the third response message including the session management subscription data.

[0094] In some implementations of the sixth aspect, the session management network element obtaining the session management subscription data of the remote terminal device includes: the session management network element receiving a first message from the relay device, the first message including the session management subscription data.

[0095] A seventh aspect provides a service assurance method, which can be executed by a user plane network element or a chip or circuit disposed in the user plane network element, and the present application does not limit this.

[0096] The service assurance method is applied to a case where a remote terminal device accesses a network through a relay device, and the method includes: a user plane network element receiving a PDR from a session management network element, the PDR corresponding to the remote terminal device, the PDR including a QER, a maximum bandwidth in the QER being determined based on an AMBR of the remote terminal device; and the user plane network element determining a rate of data sent to the remote terminal device according to the maximum bandwidth in the QER.

[0097] In the embodiment of the present application, after the user plane network element receives the PDR from the session management network element, the maximum bandwidth in the QER can be obtained from the PDR, so that in the process of performing packet transmission of the remote terminal device by the user plane network element, the rate of data sent to the remote terminal device can be limited according to the maximum bandwidth of the remote terminal device.

[0098] With reference to the seventh aspect, in some implementations of the seventh aspect, the AMBR of the remote terminal device includes at least one of: a subscription session AMBR of the remote terminal device, a PC5 interface AMBR of the remote terminal device, and a PC5 link AMBR of the remote terminal device.

[0099] With reference to the seventh aspect, in some implementations of the seventh aspect, the maximum bandwidth in the QER is the minimum value of the subscription session AMBR of the remote terminal device and the PC5 interface AMBR / PC5 link AMBR of the remote terminal device.

[0100] An eighth aspect provides a method for obtaining a relay service code, which can be executed by a policy control network element or a chip or circuit disposed in the policy control network element, and the present application does not limit this.

[0101] The method for obtaining the relay service code is applied to the case where the remote terminal device accesses a network through a relay device, and the method includes: a policy control network element obtaining session management subscription data of the remote terminal device, the session management subscription data including an AMBR of the remote terminal device; the policy control network element deciding a relay service code according to the subscription data, the relay service code being associated with the session management subscription data; and the policy control network element sending the relay service code to the remote terminal device and the relay device.

[0102] The embodiment of the present application provides a method for obtaining a relay service code, which associates session management subscription data of a remote terminal device with a relay service code, so that the remote terminal device can match a relay device that can provide relay service for the remote terminal device according to the relay service code.

[0103] With reference to the eighth aspect, in some implementations of the eighth aspect, the method further includes: the policy control network element sending the relay service code and second indication information to a data management network element / data repository network element, the second indication information being used to indicate that the relay service code is associated with the session management subscription data.

[0104] With reference to the eighth aspect, in some implementations of the eighth aspect, the method further includes: the policy control network element sending the session management subscription data to the remote terminal device and the relay device.

[0105] In some implementations of the eighth aspect, the AMBR of the remote terminal device includes at least one of: a subscription session AMBR of the remote terminal device, a PC5 interface AMBR of the remote terminal device, and a PC5 link AMBR of the remote terminal device.

[0106] In a ninth aspect, an apparatus for service assurance is provided. The apparatus includes a processor configured to implement the functions of the policy control network element in the method described in the first aspect.

[0107] In particular, the apparatus for service assurance includes:

[0108] a receiving unit configured to obtain a first identifier of the remote terminal device, the first identifier being used to obtain subscription data of the remote terminal device;

[0109] a processing unit configured to generate a policy and charging control (PCC) rule based on the subscription data of the remote terminal device, the PCC rule including a first QoS parameter of a first communication interface and a second QoS parameter of a second communication interface,

[0110] a sending unit configured to send the PCC rule to a session management network element;

[0111] wherein the first communication interface is a communication interface between the relay device and an access network device, and the second communication interface is a communication interface between the relay device and the remote terminal device, the first QoS parameter is used to generate a first QoS rule corresponding to the first communication interface, and the second QoS parameter is used to generate a second QoS rule corresponding to the second communication interface.

[0112] In some implementations of the ninth aspect, the receiving unit is further configured to obtain Internet Protocol (IP) address information of the remote terminal device, and the processing unit is further configured to determine flow description information based on the IP address information, the flow description information being carried in the PCC rule.

[0113] In some implementations of the ninth aspect, the receiving unit obtaining the identifier of the remote terminal device includes:

[0114] the receiving unit receiving a second message from a session management network element, the second message including the identifier of the remote terminal device; or

[0115] the receiving unit receiving a policy authorization request message from an application network element, the policy authorization request message including a second identifier of the remote terminal device, wherein the second identifier is used to determine the first identifier.

[0116] In some implementations of the ninth aspect, in conjunction with the ninth aspect, the second message further comprises session management subscription data of the remote terminal device, the session management subscription data comprising an AMBR of the remote terminal device, and the second QoS parameter comprises the AMBR available to the remote terminal device.

[0117] In some implementations of the ninth aspect, in conjunction with the ninth aspect, the policy authorization request message further comprises:

[0118] an identity of a service, the identity of the service being used to indicate a service type, and / or a QoS parameter requirement, the QoS parameter requirement being used to assist the policy control network element to generate the PCC rule based on the PCC rule.

[0119] In some implementations of the ninth aspect, in conjunction with the ninth aspect, the identity of the service comprises at least one of the following information:

[0120] a first Relay Service Code, a second Relay Service Code, an application identity (APP ID), and a Proximity Service (ProSe) APP ID.

[0121] The first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device.

[0122] In some implementations of the ninth aspect, in conjunction with the ninth aspect, before the receiving unit receives the policy authorization request message from the application network element, the receiving unit is further configured to receive a subscription message from the application network element, the subscription message being used to subscribe to whether the remote terminal device is online.

[0123] The sending unit is further configured to send a notification message to the application network element, the notification message being used to indicate that the remote terminal device is online.

[0124] In some implementations of the ninth aspect, in conjunction with the ninth aspect, the second message and / or the policy authorization request message further comprises:

[0125] a first Relay Service Code and / or a second Relay Service Code,

[0126] The first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device.

[0127] The processing unit generates a policy and charging control (PCC) rule based on the subscription data of the remote terminal device. The policy control network element includes:

[0128] The processing unit generates the PCC rule based on the subscription data of the remote terminal device and the first Relay Service Code and / or the second Relay Service Code.

[0129] With reference to the ninth aspect, in some implementations of the ninth aspect, the processing unit is further configured to determine a service type based on the first Relay Service Code and / or the second Relay Service Code; or

[0130] The processing unit is further configured to obtain the service type from a 5G proximity service name management function (DDNMF) network element based on the first Relay Service Code and / or the second Relay Service Code.

[0131] With reference to the ninth aspect, in some implementations of the ninth aspect, the first identifier of the remote terminal device includes

[0132] A general public subscription identity (GPSI) or a user ID assigned to the remote terminal device by a third-party application.

[0133] Optionally, the service assurance apparatus can further include a memory coupled to the processor, and the processor is configured to implement the functions of the policy control network element in the method described in the first aspect.

[0134] In a possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor can invoke and execute the program instructions stored in the memory to implement the functions of the policy control network element in the method described in the first aspect.

[0135] Optionally, the service assurance apparatus can further include a communication interface configured to enable the service assurance apparatus to communicate with other devices. When the service assurance apparatus is a user equipment, the communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0136] In a possible design, the service assurance apparatus includes a processor and a communication interface,

[0137] The processor communicates with the outside through the communication interface.

[0138] The processor is configured to run a computer program to enable the service assurance apparatus to implement any of the methods described in the first aspect.

[0139] It can be understood that the external object can be an object other than the processor, or an object other than the apparatus.

[0140] In another possible design, the apparatus for service assurance is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry on the chip or the chip system. The processor can also be implemented as a processing circuit or a logic circuit.

[0141] In a tenth aspect, an apparatus for service assurance is provided, which includes a processor configured to implement the function of the network element in the method described in the second aspect.

[0142] In particular, the apparatus for service assurance includes:

[0143] a processing unit configured to determine a policy authorization request message;

[0144] a sending unit configured to send the policy authorization request message to a policy control network element, the policy authorization request message including a second identifier of a remote terminal device, the remote terminal device being a terminal device accessing a network through another terminal device;

[0145] The second identifier of the remote terminal device is used to determine a first identifier of the remote terminal device, the identifier of the remote terminal device is used to obtain subscription data of the remote terminal device, the subscription data of the remote terminal device is used to determine a second quality of service (QoS) rule, and the second QoS rule is a QoS rule corresponding to a second communication interface between the relay device and the remote terminal device.

[0146] In combination with the tenth aspect, in some implementations of the tenth aspect, before the processing unit determines the policy authorization request message, the apparatus further includes:

[0147] a sending unit configured to send a subscription message to the policy control network element, the subscription message being used to subscribe to whether the remote terminal device is online;

[0148] a receiving unit configured to receive a notification message from the policy control network element, the notification message being used to indicate that the remote terminal device is online; or

[0149] The apparatus further includes:

[0150] a querying unit configured to obtain information of the policy control network element through a querying request message.

[0151] In some implementations of the tenth aspect, in conjunction with the tenth aspect, the processing unit determining the policy authorization request message includes: the processing unit determining the policy authorization request message based on the first identifier and a service identifier, the service identifier being used to identify a service type, wherein the first identifier and the service identifier are carried in the notification message, or the first identifier and the service identifier are obtained by the processing unit through user plane perception.

[0152] In some implementations of the tenth aspect, in conjunction with the tenth aspect, the policy authorization request message further includes:

[0153] an identifier of a service, the identifier of the service being used to indicate a service type, and / or a QoS parameter requirement, the QoS parameter requirement being used to assist the policy control network element in generating the PCC rule.

[0154] In some implementations of the tenth aspect, in conjunction with the tenth aspect, the identifier of the service includes at least one of the following information:

[0155] a first Relay Service Code, a second Relay Service Code, an application identifier (APP ID), and a Proximity Service (ProSe) APP ID.

[0156] The first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device.

[0157] In some implementations of the tenth aspect, in conjunction with the tenth aspect, the identifier of the remote terminal device includes at least one of the following identifiers:

[0158] a general public subscription identifier (GPSI) of the remote terminal device, a third-party assigned user identifier (user ID) of the remote terminal device, an Internet Protocol version 6 (IPv6) address of the remote terminal device, an IPv6 address prefix of the remote terminal device, an Internet Protocol version 4 (IPv4) address of the relay device, and a Transmission Control Protocol / User Datagram Protocol (TCP / UDP) port number combination.

[0159] Optionally, the service assurance apparatus can further include a memory coupled to the processor, and the processor is configured to implement the functions of the application network element in the method described in the second aspect.

[0160] In a possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor can invoke and execute the program instructions stored in the memory to implement the functions of the application network element in the method described in the second aspect.

[0161] Optionally, the service assurance apparatus further includes a communication interface configured to enable the service assurance apparatus to communicate with other devices. When the service assurance apparatus is an application network element, the communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0162] In a possible design, the service assurance apparatus includes a processor and a communication interface,

[0163] The processor is configured to run a computer program to enable the service assurance apparatus to implement any of the methods described in the second aspect.

[0164] The processor communicates with the outside via the communication interface.

[0165] It can be understood that the outside can be an object other than the processor, or an object other than the apparatus.

[0166] In another possible design, the service assurance apparatus is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on the chip or chip system. The processor can also be implemented as a processing circuit or a logic circuit.

[0167] In an eleventh aspect, a service assurance apparatus is provided, which includes a processor configured to implement the functions of the session management network element in the method described in the third aspect.

[0168] In particular, the service assurance apparatus includes:

[0169] A receiving unit configured to receive a first message from the relay device, the first message including an identifier of the remote terminal device;

[0170] A sending unit configured to send a second message to a policy control network element, the second message including the first identifier of the remote terminal device, wherein the first identifier of the remote terminal device is used to obtain subscription data of the remote terminal device, and the subscription data of the remote terminal device is used to determine a second quality of service (QoS) rule corresponding to a second communication interface between the relay device and the remote terminal device.

[0171] In some implementations of the eleventh aspect, in conjunction with the eleventh aspect, the receiving unit is further configured to receive a policy and charging control (PCC) rule from the policy control network element, the PCC rule including a first QoS parameter of the first communication interface and a second QoS parameter of the second communication interface,

[0172] The first communication interface is a communication interface between the relay device and the access network device.

[0173] The device for service assurance further includes:

[0174] The processing unit is configured to generate a first QoS rule corresponding to the first communication interface according to the first QoS parameter and generate a second QoS rule according to the second QoS parameter.

[0175] In some implementations of the eleventh aspect, in conjunction with the eleventh aspect, the device further includes:

[0176] The processing unit is configured to assign a QoS flow identifier (QFI) to the PCC rule, the QFI being used to uniquely identify a QoS flow corresponding to the PCC rule.

[0177] The sending unit is further configured to send a third message to the access network device, the third message including the QFI, the first QoS rule, and the second QoS rule.

[0178] In some implementations of the eleventh aspect, in conjunction with the eleventh aspect, the identifier of the remote terminal device includes:

[0179] A general public subscriber identity (GPSI) or a user identifier (userID) assigned to the remote terminal device by a third party application.

[0180] In some implementations of the eleventh aspect, in conjunction with the eleventh aspect, the first message and the second message further include:

[0181] A first relay service code (Relay Service Code) and / or a second Relay Service Code, the first Relay Service Code or the second Relay Service Code being used to determine the second QoS rule.

[0182] The first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device.

[0183] In some implementations of the eleventh aspect, in conjunction with the eleventh aspect, the second message further includes:

[0184] an identifier of the relay device and / or an Internet Protocol (IP) address information of the remote terminal device.

[0185] Optionally, the service assurance apparatus further includes a memory coupled to the processor, and the processor is configured to implement the functions of the session management network element in the method described in the third aspect.

[0186] In a possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor is configured to invoke and execute the program instructions stored in the memory, so as to implement the functions of the session management network element in the method described in the third aspect.

[0187] Optionally, the service assurance apparatus further includes a communication interface, configured to enable the service assurance apparatus to communicate with other devices. When the service assurance apparatus is a session management network element, the communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0188] In a possible design, the service assurance apparatus includes a processor and a communication interface,

[0189] The processor communicates with the outside through the communication interface.

[0190] The processor is configured to run a computer program, so that the service assurance apparatus implements any one of the methods described in the third aspect.

[0191] It can be understood that the outside can be an object other than the processor, or an object other than the apparatus.

[0192] In another possible design, the service assurance apparatus is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0193] In a twelfth aspect, a service assurance apparatus is provided, and the service assurance apparatus includes a processor, configured to implement the functions of the relay device in the method described in the fourth aspect.

[0194] Specifically, the service assurance apparatus includes:

[0195] a sending unit, configured to send a first message to a session management network element, and the first message includes a first identifier of the remote terminal device;

[0196] receive, from the session management network element, a second quality of service (QoS) rule, the second QoS rule being generated based on a first identifier corresponding to subscription data of the remote terminal device;

[0197] determine, by the processing unit, a second communication interface between the relay device and the remote terminal device based on the second QoS rule.

[0198] In some implementations of the twelfth aspect, the sending unit is further configured to send the second QoS rule to the remote terminal device.

[0199] In some implementations of the twelfth aspect, the first identifier of the remote terminal device comprises:

[0200] a general public subscription identifier (GPSI) or a user identifier (userID) assigned to the remote terminal device by a third party application.

[0201] In some implementations of the twelfth aspect, the first message further comprises:

[0202] a first relay service code (Relay Service Code) and / or a second Relay Service Code, the first Relay Service Code or the second Relay Service Code being used to determine the second QoS rule.

[0203] In some implementations of the twelfth aspect, the first Relay Service Code is a Relay Service Code configured for the remote terminal device, and the second Relay Service Code is a Relay Service Code configured for the relay device.

[0204] In some implementations of the twelfth aspect, the first relay service code and / or the second relay service code are associated with session management subscription data of the remote terminal device.

[0205] In some implementations of the twelfth aspect, the receiving unit is further configured to receive, from the session management network element, a fourth message, the fourth message comprising session management subscription data of the remote terminal device, the session management subscription data comprising an AMBR of the remote terminal device; and the processing unit is further configured to determine, according to the AMBR of the remote terminal device, an AMBR of a PC5 link between the remote terminal device.

[0206] Optionally, the service assurance apparatus further includes a memory coupled to the processor, and the processor is configured to implement the functions of the relay device in the method described in the fourth aspect.

[0207] In one possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor is configured to invoke and execute the program instructions stored in the memory to implement the functions of the relay device in the method described in the fourth aspect.

[0208] Optionally, the service assurance apparatus further includes a communication interface configured to enable the service assurance apparatus to communicate with other devices. When the service assurance apparatus is a relay device, the communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0209] In one possible design, the service assurance apparatus includes a processor and a communication interface,

[0210] The processor is configured to run a computer program to enable the service assurance apparatus to implement any of the methods described in the fourth aspect.

[0211] The processor communicates with the outside via the communication interface.

[0212] It can be understood that the outside can be an object other than the processor, or an object other than the apparatus.

[0213] In another possible design, the service assurance apparatus is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on the chip or chip system. The processor can also be implemented as a processing circuit or a logic circuit.

[0214] In a thirteenth aspect, a service assurance apparatus is provided, and the service assurance apparatus includes a processor configured to implement the functions of the remote terminal device in the method described in the fifth aspect.

[0215] In particular, the service assurance apparatus includes:

[0216] a receiving unit configured to receive a second quality of service (QoS) rule from the relay device, the second QoS rule being generated based on subscription data of the remote terminal device;

[0217] a processing unit configured to perform QoS assurance on a second communication interface between the relay device and the remote terminal device based on the second QoS rule.

[0218] Optionally, the service assurance apparatus further includes a memory coupled to the processor, and the processor is configured to implement the functions of the remote terminal device in the method described in the fifth aspect.

[0219] In one possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor is configured to invoke and execute the program instructions stored in the memory to implement the functions of the remote terminal device in the method described in the fifth aspect.

[0220] Optionally, the service assurance apparatus further includes a communication interface configured to enable the service assurance apparatus to communicate with other devices. When the service assurance apparatus is a remote terminal device, the communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0221] In one possible design, the service assurance apparatus includes a processor and a communication interface,

[0222] The processor is configured to communicate with the outside via the communication interface.

[0223] The processor is configured to run a computer program to enable the service assurance apparatus to implement any of the methods described in the fifth aspect.

[0224] It can be understood that the outside can be an object other than the processor, or an object other than the apparatus.

[0225] In another possible design, the service assurance apparatus is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on the chip or chip system. The processor can also be implemented as a processing circuit or a logic circuit.

[0226] The fourteenth aspect provides a service assurance apparatus, which includes a processor configured to implement the functions of the session management network element in the method described in the sixth aspect.

[0227] Specifically, the service assurance apparatus includes:

[0228] a receiving unit configured to obtain session management subscription data of the remote terminal device, the session management subscription data including an AMBR of the remote terminal device;

[0229] a processing unit configured to generate a PDR corresponding to the remote terminal device, the PDR including a QER, and a maximum bandwidth in the QER being determined based on the AMBR of the remote terminal device;

[0230] a sending unit configured to send the PDR to a user plane network element.

[0231] In some implementations of the fourteenth aspect, the sending unit is further configured to send a fourth message to the relay device, the fourth message comprising the AMBR of the remote terminal device.

[0232] In some implementations of the fourteenth aspect, the AMBR of the remote terminal device comprises at least one of a subscription session AMBR of the remote terminal device, a PC5 interface AMBR of the remote terminal device, and a PC5 link AMBR of the remote terminal device.

[0233] In some implementations of the fourteenth aspect, the maximum bandwidth in the QER is the minimum of the subscription session AMBR of the remote terminal device and the PC5 interface AMBR / PC5 link AMBR of the remote terminal device.

[0234] In some implementations of the fourteenth aspect, the sending unit is further configured to send a second message to a policy control network element, the second message comprising the session management subscription data; the receiving unit is further configured to receive session-related policy and / or policy and charging control (PCC) rules from the policy control network element, the session-related policy and / or PCC rules comprising a second QoS parameter of a second communication interface, the second communication interface being a communication interface between the relay device and the remote terminal device, the second QoS parameter comprising an AMBR available to the remote terminal device; and the maximum bandwidth in the QER is the minimum of the AMBR of the remote terminal device and the AMBR available to the remote terminal device.

[0235] In some implementations of the fourteenth aspect, the receiving unit is further configured to receive a first message from the relay device, the first message comprising a first identifier of the remote terminal device; and the session management subscription data is obtained according to the first identifier.

[0236] In some implementations of the fourteenth aspect, the sending unit is further configured to send a second request message to a data management network element / data repository network element, the second request message being used to request the session management subscription data, the second request message comprising the first identifier; and the receiving unit is further configured to receive a second response message from the data management network element / data repository network element, the second response message comprising the session management subscription data.

[0237] In some implementations of the fourteenth aspect, the second request message further comprises first indication information, the first indication information being used to indicate that the remote terminal device accesses a network through the relay device.

[0238] In some implementations of the fourteenth aspect, the sending unit is further configured to send a third request message to the DN-AAA server, the third request message being used to request the session management subscription data, the first identifier being included in the third request message; and the receiving unit is further configured to receive a third response message from the DN-AAA server, the session management subscription data being included in the third response message.

[0239] In some implementations of the fourteenth aspect, the receiving unit is further configured to receive a first relay service code and / or a second relay service code from the relay device, the first relay service code and / or the second relay service code being associated with the session management subscription data; the sending unit is further configured to send a third request message to a data management network element / data repository network element, the third request message being used to request the session management subscription data, the first relay service code and / or the second relay service code being included in the third request message; and the receiving unit is further configured to receive a third response message from the data management network element / data repository network element, the session management subscription data being included in the third response message.

[0240] In some implementations of the fourteenth aspect, the receiving unit is further configured to receive a first message from the relay device, the first message including the session management subscription data.

[0241] Optionally, the service assurance apparatus can further include a memory coupled to the processor, the processor being configured to implement the functions of the session management network element in the method described in the sixth aspect.

[0242] In one possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor can invoke and execute the program instructions stored in the memory to implement the functions of the session management network element in the method described in the sixth aspect.

[0243] Optionally, the service assurance apparatus can further include a communication interface configured to enable the service assurance apparatus to communicate with other devices. When the service assurance apparatus is a remote terminal device, the communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0244] In one possible design, the service assurance apparatus includes a processor and a communication interface,

[0245] The processor communicates with the outside through the communication interface.

[0246] The processor is configured to run a computer program to enable the service assurance apparatus to implement any of the methods described in the sixth aspect.

[0247] It can be understood that the external object can be an object other than the processor, or an object other than the apparatus.

[0248] In another possible design, the apparatus for service assurance is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry on the chip or chip system. The processor can also be implemented as a processing circuit or a logic circuit.

[0249] In a fifteenth aspect, an apparatus for service assurance is provided. The apparatus for service assurance includes a processor configured to implement the function of a user plane network element in the method described in the seventh aspect.

[0250] In particular, the apparatus for service assurance includes:

[0251] a receiving unit configured to receive a PDR from a session management network element, the PDR corresponding to a remote terminal device, the PDR including a QER, a maximum bandwidth in the QER being determined based on an AMBR of the remote terminal device;

[0252] a processing unit configured to determine a rate of data sent to the remote terminal device according to the maximum bandwidth in the QER.

[0253] With reference to the fifteenth aspect, in some implementations of the fifteenth aspect, the AMBR of the remote terminal device includes at least one of: a subscription session AMBR of the remote terminal device, a PC5 interface AMBR of the remote terminal device, and a PC5 link AMBR of the remote terminal device.

[0254] With reference to the fifteenth aspect, in some implementations of the fifteenth aspect, the maximum bandwidth in the QER is a minimum value of a subscription session AMBR of the remote terminal device and a PC5 interface AMBR / PC5 link AMBR of the remote terminal device.

[0255] Optionally, the apparatus for service assurance can further include a memory coupled to the processor, and the processor is configured to implement the function of a user plane network element in the method described in the seventh aspect.

[0256] In a possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor can invoke and execute the program instructions stored in the memory to implement the function of a user plane network element in the method described in the seventh aspect.

[0257] Optionally, the apparatus for service assurance can further include a communication interface configured to enable the apparatus for service assurance to communicate with other devices. When the apparatus for service assurance is a remote terminal device, the communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0258] In a possible design, the service assurance apparatus includes a processor and a communication interface,

[0259] The processor communicates with the outside via the communication interface.

[0260] The processor is configured to run a computer program, so that the service assurance apparatus implements any method described in the seventh aspect.

[0261] It can be understood that the outside can be an object other than the processor, or an object other than the apparatus.

[0262] In another possible design, the service assurance apparatus is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry on the chip or chip system. The processor can also be implemented as a processing circuit or a logic circuit.

[0263] The sixteenth aspect provides an apparatus for obtaining a relay service code, the apparatus including a processor configured to implement the function of the policy control network element in the method described in the eighth aspect.

[0264] Specifically, the apparatus for obtaining a relay service code includes:

[0265] A receiving unit configured to obtain session management subscription data of the remote terminal device, the session management subscription data including an AMBR of the remote terminal device.

[0266] A processing unit configured to decide a relay service code according to the subscription data, the relay service code being associated with the session management subscription data.

[0267] A sending unit configured to send the relay service code to the remote terminal device and the relay device.

[0268] With reference to the sixteenth aspect, in some implementations of the sixteenth aspect, the sending unit is further configured to send the relay service code and second indication information to a data management network element / data repository network element, the second indication information being used to indicate that the relay service code is associated with the session management subscription data.

[0269] With reference to the sixteenth aspect, in some implementations of the sixteenth aspect, the sending unit is further configured to send the session management subscription data to the remote terminal device and the relay device.

[0270] In a possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor is configured to invoke and execute the program instructions stored in the memory to implement the function of the policy control network element in the method described in the eighth aspect.

[0271] Optionally, the service assurance apparatus further includes a memory coupled to the processor, and the processor is configured to implement the function of the policy control network element in the method described in the eighth aspect.

[0272] In a possible implementation, the memory is configured to store program instructions and data. The memory is coupled to the processor, and the processor is configured to invoke and execute the program instructions stored in the memory to implement the function of the policy control network element in the method described in the eighth aspect.

[0273] Optionally, the service assurance apparatus further includes a communication interface configured to enable the service assurance apparatus to communicate with other devices. When the service assurance apparatus is a remote terminal device, the communication interface can be a transceiver, an input / output interface, or a circuit, etc.

[0274] In a possible design, the service assurance apparatus includes a processor and a communication interface,

[0275] The processor is configured to communicate with the outside via the communication interface.

[0276] The processor is configured to run a computer program to enable the service assurance apparatus to implement any of the methods described in the eighth aspect.

[0277] It can be understood that the outside can be an object other than the processor, or an object other than the apparatus.

[0278] In another possible design, the service assurance apparatus is a chip or a chip system. The communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on the chip or chip system. The processor can also be implemented as a processing circuit or a logic circuit.

[0279] In a seventeenth aspect, the present application provides a computer readable storage medium, which stores instructions, and when the instructions are run on a computer, the computer is enabled to perform the method described in the above aspects.

[0280] In an eighteenth aspect, the present application provides a computer program product including instructions, and when the instructions are run on a computer, the computer is enabled to perform the method described in the above aspects.

[0281] In a nineteenth aspect, a communication system is provided, comprising the service assurance apparatus of the ninth aspect and the service assurance apparatus of the tenth aspect.

[0282] Further, the communication system further comprises the service assurance apparatus of the eleventh aspect or the fourteenth aspect.

[0283] Further, the communication system further comprises the service assurance apparatus of the twelfth aspect and the service assurance apparatus of the thirteenth aspect.

[0284] Further, the communication system further comprises the service assurance apparatus of the fifteenth aspect.

[0285] Further, the communication system further comprises the service assurance apparatus of the sixteenth aspect.

[0286] In a twentieth aspect, a chip system is provided, comprising a memory for storing a computer program and a processor for invoking and running the computer program from the memory, so that a communication device installed with the chip system executes the method in any possible implementation manner of the first to eighth aspects. BRIEF DESCRIPTION OF DRAWINGS

[0287] Figure 1 is a network architecture suitable for embodiments of the present application.

[0288] Figure 2 is a ProSe relay communication architecture diagram provided by the present application.

[0289] Figure 3 is a ProSe relay communication architecture diagram provided by the present application.

[0290] Figure 4 is a schematic flowchart of a remote terminal device accessing a network through a relay device.

[0291] Figure 5 is a service assurance method schematic flowchart provided by embodiments of the present application.

[0292] Figure 6 is another service assurance method schematic flowchart provided by embodiments of the present application.

[0293] Figure 7 is still another service assurance method schematic flowchart provided by embodiments of the present application.

[0294] Figure 8 is still another service assurance method schematic flowchart provided by embodiments of the present application.

[0295] Figure 9 is a schematic flowchart of another method for service assurance provided by embodiments of the present application.

[0296] Figure 10 is a schematic diagram of an apparatus 8000 for service assurance provided by the present application.

[0297] Figure 11 is a schematic diagram of a structure of a relay device or a remote terminal device 900 suitable for use in embodiments of the present application.

[0298] Figure 12 is a schematic diagram of an apparatus 1000 for service assurance provided by the present application.

[0299] Figure 13 is a schematic diagram of a structure of a session management network element 1100 suitable for use in embodiments of the present application.

[0300] Figure 14 is a schematic diagram of an apparatus 1200 for service assurance provided by the present application.

[0301] Figure 15 is a schematic diagram of a structure of a policy control network element 1200 suitable for use in embodiments of the present application.

[0302] Figure 16 is a schematic diagram of an apparatus 1400 for service assurance provided by the present application.

[0303] Figure 17 is a schematic diagram of a structure of an application network element 1500 suitable for use in embodiments of the present application.

[0304] Figure 18 is a schematic diagram of an apparatus 1600 for service assurance provided by the present application.

[0305] Figure 19 is a schematic diagram of an apparatus 1900 for service assurance provided by the present application.

[0306] Figure 20 is a schematic diagram of a structure of a user plane network element 2000 suitable for use in embodiments of the present application. DETAILED DESCRIPTION

[0307] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0308] Figure 1 is a network architecture suitable for use in embodiments of the present application. As shown, the various parts involved in this network architecture are described below separately. Figure 1

[0309] ​1. User equipment (UE) 110: can include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to wireless modems, and various forms of terminals, mobile stations (MS), terminals or soft terminals, and the like. For example, water meters, electricity meters, sensors, and the like.

[0310] By way of example, and not limitation, a user equipment in embodiments of the present application can refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal device, a wireless communication device, a user agent, or a user device. The user equipment can also be a cellular telephone, a cordless telephone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless communication functions, a computing device, or other processing devices connected to a wireless modem, an in-vehicle device, a wearable device, a user equipment in a future 5G network, or a user equipment in a future evolved public land mobile network (PLMN), or a user equipment in a future Internet of Vehicles, and the like. Embodiments of the present application are not limited thereto.

[0311] By way of example, and not limitation, a wearable device in embodiments of the present application can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes, etc. A wearable device is a portable device that is directly worn on the body or integrated into a user's clothing or accessories. A wearable device is not only a hardware device, but also a device that realizes powerful functions through software support and data interaction and cloud interaction. Broadly, a wearable smart device includes a device with full functions and large size, which can realize complete or partial functions without relying on a smart phone, such as a smart watch or smart glasses, and a device that focuses on a certain application function and needs to be used in cooperation with other devices, such as a smart phone, such as various smart wristbands and smart jewelry for monitoring vital signs.

[0312] In addition, in the embodiments of the present application, the user equipment can also be user equipment in an Internet of Things (IoT) system. The IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network to realize the intelligent network of man-machine interconnection and object-object interconnection. In the embodiments of the present application, the IOT technology can achieve mass connection, deep coverage and terminal power saving through, for example, narrow band (NB) technology. In addition, in the embodiments of the present application, the user equipment can also include intelligent printers, train detectors, gas station sensors, and the like, and the main functions include collecting data (for some user equipment), receiving control information and downlink data of the access network equipment, and transmitting electromagnetic waves to transmit uplink data to the access network equipment.

[0313] 2. (Radio) access network (R)AN 120: used to provide network access functions for authorized user equipment in a specific area, and can use different quality transmission tunnels according to the level of the user equipment, the demand of the service, etc.

[0314] The (R)AN can manage radio resources, provide access services for user equipment, and further complete the forwarding of control signals and user equipment data between user equipment and a core network. The (R)AN can also be understood as a base station in a traditional network.

[0315] Exemplarily, the access network device in the embodiments of the present application can be any kind of communication device with wireless transceiving function for communicating with the user equipment. The access network device includes but is not limited to: evolved NodeB (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB (HeNB, or home Node B, HNB), baseBand unit (BBU), access point (AP) in a wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP), etc., and can also be gNB or transmission point (TRP or TP) in a 5G, such as NR, system, or one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or a network node constituting the gNB or transmission point, such as baseBand unit (BBU), or distributed unit (DU), etc.

[0316] In some deployments, a gNB can include a centralized unit (CU) and a DU. The gNB can also include an active antenna unit (AAU). The CU implements part of the functions of the gNB, and the DU implements part of the functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, implements the radio resource control (RRC), and the functions of the packet data convergence protocol (PDCP) layer. The DU is responsible for processing the physical layer protocol and real-time services, and implements the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements part of the physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since the information of the RRC layer eventually becomes the information of the PHY layer, or is transformed from the information of the PHY layer, under this architecture, high-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU, or by the DU+AAU. It can be understood that the access network device can be a device including one or more of the CU node, the DU node, and the AAU node. In addition, the CU can be divided into an access network device in the radio access network (RAN), or can be divided into an access network device in the core network (CN), which is not limited in the present application.

[0317] 3. User plane network element 130: used for packet routing and forwarding, QoS processing of user plane data, completing user plane data forwarding, session / stream level-based charging statistics, bandwidth limitation, and the like.

[0318] In the 5G communication system, the user plane network element can be a user plane function (UPF) network element. In the future communication system, the user plane network element can still be a UPF network element, or can have other names, which are not limited in the present application.

[0319] 4. Data network network element 140: used for providing a network for transmitting data.

[0320] In the 5G communication system, the data network network element can be a data network (DN) network element. In the future communication system, the data network network element can still be a DN network element, or can have other names, which are not limited in the present application.

[0321] 5. Access management network element 150: mainly used for mobility management and access management, responsible for transferring user policies between user equipment and policy control function (PCF) network elements, etc., and can be used to implement other functions in the mobility management entity (MME) function except session management, such as lawful interception, access authorization / authentication, etc.

[0322] In the 5G communication system, the access management network element can be an access and mobility management function (AMF). In future communication systems, the access management network element can still be an AMF, or can also have other names, which are not limited in the present application.

[0323] 6. Session management network element 160: mainly used for session management, internet protocol (IP) address allocation and management of user equipment, selection of manageable user plane functions, termination of policy control and charging function interfaces, and downlink data notification, etc.

[0324] In the 5G communication system, the session management network element can be a session management function (SMF) network element. In future communication systems, the session management network element can still be an SMF network element, or can also have other names, which are not limited in the present application.

[0325] 7. Policy control network element 170: a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (such as AMF, SMF network elements, etc.), etc.

[0326] In the 4G communication system, the policy control network element can be a policy and charging rules function (PCRF) network element. In the 5G communication system, the policy control network element can be a policy control function (PCF) network element. In future communication systems, the policy control network element can still be a PCF network element, or can also have other names, which are not limited in the present application.

[0327] Specifically, the PCF network element is mainly responsible for charging, QoS bandwidth guarantee and mobility management at the session and service flow level, user equipment policy decision, etc. policy control functions. Figure 1In the illustrated network architecture, the PCF connected to the AMF corresponds to an AM PCF (PCF for access and mobility control), and the PCF connected to the SMF corresponds to an SM PCF (PCF for session management). In actual deployment scenarios, the AM PCF and the SM PCF can not be the same PCF entity.

[0328] 8. Data repository network element 180: responsible for access functions of subscription data, policy data, application data, and the like.

[0329] In the 5G communication system, the data repository network element can be a unified data repository (UDR) network element. In future communication systems, the data repository network element can still be a UDR network element, or can have other names, which are not limited in the present application.

[0330] 9. Data management network element 190: used for processing user equipment identification, access authentication, registration, and mobility management, and the like.

[0331] In the 5G communication system, the data management network element can be a unified data management (UDM) network element; in the 4G communication system, the data management network element can be a home subscriber server (HSS) network element. In future communication systems, the unified data management can still be a UDM network element, or can have other names, which are not limited in the present application.

[0332] 10. Application network element 1100: used for transmitting application-side requirements for the network side, accessing network exposure function network elements, interacting with the policy framework for policy control, and the like.

[0333] In the 5G communication system, the application network element can be an application function (AF) network element. In future communication systems, the application network element can still be an AF network element, or can have other names, which are not limited in the present application. The AF network element mainly transmits application-side requirements for the network side, such as QoS requirements or user equipment state event subscription, and the like.

[0334] Exemplarily, the AF can be a third-party function entity or an application service (such as an internet protocol multimedia system (IMS) voice call service) deployed by an operator. For the application function entity of the third-party application, when interacting with the core network, the application function entity can also perform authorization processing via a network exposure function (NEF) network element, for example, the third-party application function directly sends a request message to the NEF, the NEF judges whether the AF is allowed to send the request message, and if the verification is passed, the request message is forwarded to the corresponding PCF or UDM.

[0335] It should also be understood that Figure 1 This is only an example and does not constitute any limitation on the protection scope of the present application. The service guarantee method provided by the embodiments of the present application can also involve network elements not shown in the foregoing embodiments, for example, the service guarantee method provided by the embodiments of the present application also involves a network exposure network element, wherein the network exposure network element is used for QoS capability exposure, traffic steering requested by an AF, and the like. Figure 1

[0336] In the 5G communication system, the network exposure network element can be the NEF network element described above. In future communication systems, the network storage network element can still be the NEF network element, or can have other names, which are not limited in the present application.

[0337] It can be understood that the above network elements or functions can be network elements in a hardware device, or software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). The above network elements or functions can be implemented by one device, or can be implemented by multiple devices together, or can be a functional module in one device, and the embodiments of the present application do not make specific limitations. For convenience of description, the access management network element is taken as the AMF network element, the network exposure network element is taken as the NEF network element, the session management network element is taken as the SMF network element, the policy control network element is taken as the PCF network element, and the application network element is taken as the AF network element in the following description of the present application.

[0338] Further, the AMF network element is referred to as AMF, the NEF network element is referred to as NEF, the SMF network element is referred to as SMF, the PCF network element is referred to as PCF, and the AF network element is referred to as AF. That is, the AMF described in the following description of the present application can be replaced by an access management network element, the NEF can be replaced by a network exposure network element, the SMF can be replaced by a session management network element, the PCF can be replaced by a policy control network element, and the AF can be replaced by an application network element.

[0339] ​For convenience of description, in the embodiments of the present application, the device is taken as an AMF entity, an SMF entity, a PCF entity, an AF entity, and an NEF entity, and the device for service assurance is described. For the implementation method of the device for service assurance as a chip in the AMF entity, a chip in the SMF entity, a chip in the PCF entity, a chip in the AF entity, and a chip in the NEF entity, reference can be made to the specific description of the device as the AMF entity, the SMF entity, the PCF entity, the AF entity, and the NEF entity, and no repeated introduction is made.

[0340] In Figure 1 In the network architecture shown in the figure, communication interfaces between different network elements are involved, and specifically Figure 1 The functions of each interface shown in the figure are described as follows:

[0341] 1. N7: interface between the PCF and the SMF, used for issuing protocol data unit (PDU) session granularity and service data flow granularity control policies.

[0342] 2. N15: interface between the PCF and the AMF, used for issuing user equipment policies and access control related policies.

[0343] 3. N5: interface between the AF and the PCF, used for application service request issuance and network event reporting.

[0344] 4. N4: interface between the SMF and the UPF, used for information transmission between the control plane and the user plane, including issuance of control plane forwarding rules, QoS control rules, and traffic statistics rules to the user plane, and information reporting of the user plane.

[0345] 5. N11: interface between the SMF and the AMF, used for transmission of PDU session tunnel information between the RAN and the UPF, transmission of control messages sent to the UE, transmission of radio resource control information sent to the RAN, etc.

[0346] 6. N2: interface between the AMF and the RAN, used for transmission of radio bearer control information from the core network side to the RAN, etc.

[0347] 7. N1: interface between the AMF and the UE, access independent, used for transmission of QoS control rules to the UE, etc.

[0348] 8. N8: interface between the AMF and the UDM, used for the AMF to obtain access and mobility management related subscription data and authentication data from the UDM, and for the AMF to register UE current mobility management related information to the UDM, etc.

[0349] 9. N10: The interface between SMF and UDM, used by SMF to obtain session management-related subscription data from UDM, and by SMF to register UE current session-related information with UDM.

[0350] 10. N35: The interface between UDM and UDR, used by UDM to obtain user subscription data information from UDR.

[0351] 11. N36: The interface between PCF and UDR, used by PCF to obtain policy-related contract data and application data related information from UDR.

[0352] It should be understood that Figure 1 The names of the various network elements and communication interfaces involved are given as examples based on current protocols, but this does not limit the embodiments of this application to only known communication systems. Therefore, the standard names that appear when describing the current protocols are functional descriptions. This application does not limit the specific names of network elements, interfaces, or signaling, but only indicates the function of the network element, interface, or signaling, which can be extended to other systems, such as 2G, 3G, 4G, or future communication systems.

[0353] It should also be understood that the above Figure 1 The network architecture shown in the embodiments of this application is merely an example. The network architecture applicable to the embodiments of this application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0354] For example, in some network architectures, network function elements such as AMF, SMF, PCF, and UDM are all called network function (NF) elements; or, in other network architectures, a collection of elements such as AMF, SMF, PCF, and UDM can be called control plane function elements.

[0355] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) system, a new radio (NR) or a future network, and the like. The 5G mobile communication system described in the present application includes a non-standalone (NSA) 5G mobile communication system or a standalone (SA) 5G mobile communication system. The technical solutions provided in the present application can also be applied to a future communication system, such as a 6th generation mobile communication system. The communication system can also be a public land mobile network (PLMN) network, a device-to-device (D2D) communication system, a machine to machine (M2M) communication system, an internet of Things (IoT) communication system or other communication systems.

[0356] In the embodiments of the present application, the user equipment or the access network equipment comprises a hardware layer, an operating system layer running above the hardware layer, and an application layer running on the operating system layer. The hardware layer comprises hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as a main memory). The operating system can be any one or more computer operating systems that implement service processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address book, word processing software, and instant messaging software. Moreover, the embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application, as long as the execution subject can communicate according to the method provided by the embodiments of the present application by running a program in which the code of the method provided by the embodiments of the present application is recorded. For example, the execution subject of the method provided by the embodiments of the present application can be user equipment or an access network equipment, or a functional module of the user equipment or the access network equipment that can invoke and execute a program.

[0357] In addition, various aspects or features of the disclosure can be realized as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used in the application is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, or key drive, etc.). Additionally, various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable storage media" can include, without being limited to, wireless channels and various other media capable of storing, containing, and / or carrying instruction and / or data.

[0358] Further, the method for service guarantee provided by the embodiments of the present application also involves ProSe relay communication. It should be understood that in order to improve the utilization of wireless spectrum and provide cellular network services for remote terminal equipment outside the coverage of the cellular network, the cellular communication network introduces ProSe relay communication. The application scenarios of the ProSe relay communication mode can include: signal enhancement at the edge of the base station coverage, relay access to operator network in the non-coverage area, and the like.

[0359] The enhancement of base station coverage edge signal can be understood as the signal strength of remote terminal devices in the base station coverage edge area being unable to meet the high bandwidth requirements of services due to signal attenuation. Therefore, remote terminal devices in the base station coverage edge area can access the network through relay devices. In this embodiment, the relay device can be called a ProSeUE-to-NW Relay device, which means a device in the proximity-based services user equipment to network relay, ProSe UE-to-NW Relay mode. The relay device can also be a terminal device, so it can also be called a relay terminal device, which is simply referred to as a relay device below.

[0360] In areas without coverage, relay access to the operator's network can be understood as remote terminal devices indirectly accessing the 5G network through relay devices when they are outside the operator's network coverage area.

[0361] In summary, in ProSe communication, two user equipments that are close to each other (e.g., a remote terminal equipment and a relay equipment) can directly establish a communication link (e.g., a sidelink), also known as using the PC5 interface to realize communication between user equipment. This allows the remote terminal equipment to access the operator's network at the edge of the base station or in areas without network coverage through the relay equipment.

[0362] 3GPP defined the ProSe relay communication architecture in the 4G communication protocol for public safety only. This communication architecture can be extended in 5G networks to support other services besides public safety services. Figure 2 This is a schematic diagram of a ProSe relay communication architecture provided in this application.

[0363] from Figure 2 As can be seen, remote user equipment (UE) can access the 5G network through a relay device (ProSe UE-to-NW Relay). Specifically, this access process includes:

[0364] The remote UE communicates through a communication interface (such as...) Figure 2 The PC5 interface shown establishes a connection with the relay device, and the relay device establishes a connection through the communication interface (such as...). Figure 2 The N1 interface (as shown) establishes a connection with the base station; the base station can establish a connection with the core network equipment; the core network equipment connects via (e.g., the N1 interface). Figure 2The N6 interface (shown) establishes a connection with the user application service network element. Both the remote UE and the relay device can be understood as user equipment, so the communication interface between the remote UE and the relay device can be understood as the PC5 interface.

[0365] To facilitate differentiation, the remote UE is referred to as the remote terminal device and the ProSe UE-to-NW Relay as the relay device in the following embodiments. In this application, the remote terminal device can access the network through the relay device and establish a packet data unit (PDU) session to ensure the normal operation of services.

[0366] It should be noted that this application does not limit how remote terminal devices access the network through relay devices or how they establish PDU sessions to ensure normal service operation. Reference can be made to the provisions of current protocols or future protocols regarding this process. This application mainly concerns how the core network equipment configures different QoS guarantees based on different services after a remote terminal device accesses the network through a relay device and establishes a PDU session.

[0367] Figure 3 This application provides a standard-defined architecture diagram for a ProSe relay communication scenario.

[0368] The PCF is responsible for providing relevant authorization information when user equipment accesses the 5G network. For example, it authorizes whether the user equipment is allowed to use the ProSe function to access specific services, allows the ProSe function to be enabled in which PLMNs, and provides information such as the ProSe discovery user identifier (PDUID) in restricted ProSe scenarios. This process can be implemented during the user equipment registration process. The specific process can refer to the provisions of the current agreement on the PCF providing authorization information. This application does not limit this.

[0369] In addition, ProSe relay communication may also involve 5G Direct Discovery Name Management (DDNMF) network elements. The 5G DDNMF network element is responsible for allocating the corresponding Relay Service Code / Filter information to the user equipment after receiving a discovery request from the user equipment. For ease of description, the Relay Service Code / Filter information will be referred to as Relay Service Code in the following text.

[0370] Optionally, the 5G DDNMF can also issue the above-mentioned relay service code to the relay device and the remote terminal device through static configuration without the active triggering of the ProSe discovery request process.

[0371] Further, the 5G DDNMF network element assigns the Relay Service Code to the user equipment, so that the user equipment can detect the connection establishment request sent by other user equipment through a broadcast message, trigger the establishment of a communication connection (such as a PC5 connection) with other user equipment. In actual deployment, the 5G DDNMF network element can be combined with other network elements, such as PCF, UDR, or UDM.

[0372] It should be noted that the present application does not limit how the 5G DDNMF network element assigns the Relay Service Code to the user equipment, and reference can be made to the current protocol. The specific content of the Relay Service Code is not limited, for example, the Relay Service Code includes service information, security policy, etc.

[0373] Exemplarily, Figure 3 The UE#B shown in the figure can be understood as a remote UE, and the UE#A can be understood as a ProSe UE-to-NW Relay. For ease of description, the UE#B is referred to as a remote terminal device, and the UE#A is referred to as a relay device in the present application. The remote terminal device also needs to be configured with the Relay Service Code and other information required by the ProSe relay service before establishing a communication connection (such as a PC5 connection) with the relay device. After the relay device and the remote terminal device complete the above-mentioned information configuration process, the discovery process between them can be triggered.

[0374] Specifically, the above-mentioned discovery process can be divided into two modes:

[0375] Mode one:

[0376] The relay device broadcasts according to the Relay Service Code and related frequency point information received from the PCF, and the remote terminal device listens to the broadcast signal. When the remote terminal device listens to the Relay Service Code that meets the conditions, it can initiate a PC5 connection establishment request. In this mode, the broadcast information initiated by the relay device can specifically include:

[0377] 1) Relay device ID: link layer ID;

[0378] 2) Announcer Info: relay device information;

[0379] 3) Relay Service Code.

[0380] In particular, the Relay Service Code can contain specific service information, security policy, and optionally also contain a list of authorized users allowed to access, etc.

[0381] Mode Two:

[0382] The remote terminal device broadcasts according to the Relay Service Code and related frequency point information received from the PCF, and the relay device listens to the broadcast signal. When the relay device listens to the Relay Service Code that meets the conditions, the relay device can return a response message to the remote terminal device. In this mode two, the broadcast information initiated by the remote terminal device can specifically include:

[0383] 1) Discoverer Info: Remote terminal device information;

[0384] 2) Relay Service Code: Can contain specific service information, security policy, and optionally also contain a list of authorized users allowed to access, etc.

[0385] 3) Relay device information (optional).

[0386] In this mode two, the response message returned by the relay device can specifically include:

[0387] 1) Relay device ID: Link layer ID;

[0388] 2) Discoveree Info: Relay device information.

[0389] It should be noted that for the mode one scenario, the remote terminal device can parse the Relay Service Code obtained by listening to determine whether the relay device supports providing the relay service required by itself; for the mode two scenario, the relay device parses the Relay Service Code obtained by listening to determine whether itself supports providing the relay service required by the user device.

[0390] Optionally, in the above two scenarios, the monitor UE (e.g., a remote terminal device in Mode 1 or a relay device in Mode 2) can also directly determine whether the monitored Relay Service Code is available according to the locally received Relay Service Code. Specifically, the Relay Service Code configured by the monitor UE and the announcer UE (e.g., a relay device in Mode 1 or a remote terminal device in Mode 2) can be the same, equivalent, or obtainable through a specific encryption / decryption algorithm, such as corresponding to the same application ID.

[0391] Further, in order to facilitate understanding of the above-mentioned process of the remote terminal device accessing the network through the relay device, the following describes the process in detail. Figure 4 The access process is described in detail as follows. Figure 4 FIG. 1 is a schematic flowchart of a process of a remote terminal device accessing a network through a relay device.

[0392] Figure 4 The main bodies include a remote terminal device (remote UE), a relay device (ProSe UE-to-NW Relay), a base station (evolved Node B, eNB), a mobility management entity (MME), a service gateway (S-GW), and a packet data network gateway (P-GW).

[0393] Figure 4 FIG. 4 is a flowchart of a process of a remote terminal device accessing a network through a relay device in a 4G protocol. Figure 4 The steps shown in FIG. 4 are not described in detail herein, and can be referred to the current protocol.

[0394] For example, S420 can be understood as the remote terminal device or the relay device performing broadcasting or monitoring according to the locally configured Relay Service Code, thereby establishing a communication connection (e.g., a PC5 connection).

[0395] S430 can be understood as the case where the current packet data network (PDN) connection is not available, and the relay device can trigger the remote terminal device to establish a new PDN connection.

[0396] The main flow of the communication between the remote terminal device and the relay device can be: after the relay device registers to the core network, the relay device and the remote terminal device discover each other (as described above in mode one and mode two), and establish a communication connection (such as a PC5 connection). When the relay device and the remote terminal device establish a connection, the relay device can request the network device to establish a PDN connection in order to transmit the relay data of the remote terminal device. Wherein, which PDN connection is used to transmit the relay data is determined by the relay device. Generally, the relay device can use all the relay data to transmit in a special PDN connection. If the communication address between the relay device and the remote terminal device is an internet protocol (IP) address, the relay device can also allocate an IP address for the remote terminal device, and then the relay device and the remote terminal device can perform service transmission.

[0397] Further, Figure 4 The method flowchart also includes S450, the relay device sends a remote terminal device report (remote UE report) to the MME, the remote UE report includes an identifier of the remote terminal device (such as remote UE ID) and the relay device can also allocate IP address information (IP info) for the remote terminal device. After the MME learns the remote UE report, the MME can forward the remote UE report to the P-GW, so that the P-GW learns the remote UE ID and the IP info, wherein the remote UE ID and the IP info are used for the PCF to make a policy decision to establish a relay connection.

[0398] In the current 4G protocol, the Relay Service Code is defined as a peer-to-peer configuration parameter on the remote terminal device and the relay device in the ProSe relay communication scheme related to public safety, and the remote terminal device and the relay device discover each other according to the Relay Service Code configured by each other.

[0399] The above combination Figures 1-4 The network architecture to which the embodiments of the present application can be applied is described in detail, and the ProSe relay communication related in the embodiments of the present application is described in detail.

[0400] From the above, in the ProSe relay solution defined by the 4G, since it is only used for public safety services, the communication connection (e.g., PC5 connection) established by the remote terminal device and the relay device only needs to support the QoS guarantee according to the public safety services. However, in the current ProSe relay scenario, the remote terminal device can access various services through the relay device, such as the VR headset accessing the VR service through the relay device to access the 5GC, and is no longer limited to the public safety scenario. In the current process, the 5GC may not be aware of the specific service initiated in the session establishment process, and therefore the QoS rule determined may not meet the actual service quality guarantee required by the service.

[0401] In addition, when the remote terminal device initiates a service through the relay device, the PDU session established by the relay device for the service is based on the QoS rule received by the relay device, that is, the rule determined according to the service at this time is the rule configured by the core network device according to the subscription information of the relay device and the current regional network load information. For the remote terminal device, the remote terminal device may have opened a corresponding value-added service or subscribed to a value-added package, so that the operator may configure a higher QoS rule for the remote terminal device, such as a larger bandwidth, a higher scheduling priority, and the like. If based on the existing scheme, the PDU session established by the relay device for the remote terminal device triggered will not meet the subscription of the remote terminal device. Of course, it is also possible that the service quality guarantee subscribed by the relay device exceeds the service quality guarantee subscribed by the remote terminal device.

[0402] In order to solve the defects of the remote terminal device initiating a service through the relay device in the 4G protocol, the present application provides a service guarantee method. By enabling the core network device side to be aware of the specific service initiated by the remote terminal device, and providing a service quality guarantee that meets the actual needs of the service, the performance of the remote terminal device accessing different services through the relay device is improved.

[0403] It should be understood that the method provided by the embodiments of the present application can be applied to a 5G communication system, for example, Figure 1 the communication system shown in the foregoing.

[0404] The embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application, as long as it can communicate according to the method provided by the embodiments of the present application by running the program in which the code of the method provided by the embodiments of the present application is recorded, for example, the execution subject of the method provided by the embodiments of the present application can be a terminal device or a core network device, or a functional module in the terminal device or the core network device that can call and execute the program.

[0405] The following describes the method for service guarantee provided by the embodiments of the present application in detail by taking the interaction between a terminal device and a core network device as an example without loss of generality.

[0406] In order to facilitate understanding of the embodiments of the present application, the following points are explained.

[0407] First, in the present application, "for indicating" can include direct indication and indirect indication. When describing that certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, and it does not mean that A must be carried in the indication information.

[0408] The information indicated by the indication information is referred to as to-be-indicated information, and there are many ways to indicate the to-be-indicated information in the specific implementation process, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or the index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be indicated only by a part of the to-be-indicated information, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, the protocol stipulates), thereby reducing the indication overhead to a certain extent. At the same time, the common part of each information can be identified and uniformly indicated to reduce the indication overhead caused by separately indicating the same information.

[0409] Second, the first, second, and various numerical numbers (for example, "#1", "#2", etc.) shown in the present application are only for convenience of description, used for distinguishing objects, and do not limit the scope of the embodiments of the present application. For example, different messages are distinguished. Instead of being used to describe a specific order or sequence. It should be understood that the objects thus described can be interchanged under appropriate circumstances, so as to be able to describe schemes other than the embodiments of the present application.

[0410] Third, the "storage" involved in the embodiments of the present application can refer to storage in one or more memories. The one or more memories can be separately arranged or integrated in the encoder or decoder, processor, or communication device. The one or more memories can also be partially separately arranged and partially integrated in the decoder, processor, or communication device. The type of memory can be any form of storage medium, which is not limited in the present application.

[0411] Fourth, the "protocol" involved in the embodiments of the present application can refer to a standard protocol in the communication field, which can include a 5G protocol, a new radio (NR) protocol, and a related protocol applied to a future communication system, which is not limited in the present application.

[0412] Figure 5 is a schematic flowchart of a service guarantee method provided by an embodiment of the present application. The service guarantee method comprises at least the following steps:

[0413] S501, a communication connection is established between the remote terminal device and the relay device.

[0414] Exemplarily, in the embodiment of the present application, the remote terminal device and the relay device are both terminal devices, and the communication connection established between the remote terminal device and the relay device can be understood as a PC5 connection, or a sidelink connection.

[0415] It should be noted that in the embodiment of the present application, how the communication connection is established between the remote terminal device and the relay device is not limited, for example, in the ProSe relay communication scheme specified in the current protocol, the remote terminal device is at the edge of the base station, or the remote terminal device is in a network coverage area, and the remote terminal device needs to access the operator network through the relay device.

[0416] The specific process of establishing the communication connection between the remote terminal device and the relay device is not described in detail in the embodiment of the present application, and reference can be made to the related provisions in the current protocol about the remote terminal device accessing the network through the relay device.

[0417] S502, a PDU session is established between the relay device and the data network (data network, DN).

[0418] The relay device can establish a PDU session between the user plane device (such as UPF) and the DN, and the PDU session involved in the present application mainly refers to the user plane link between the relay device and the DN, which is used to transmit service data.

[0419] It should be understood that the service data of the remote terminal device needs to be relayed through the relay device, and the service data of the relay device also needs to be transmitted through the relay device, and the service data needs to be transmitted using the PDU session to ensure the normal operation of the service. Therefore, the PDU session needs to be established between the relay device and the policy control network element to ensure the normal operation of the service.

[0420] It should be noted that in the embodiment of the present application, the specific process of establishing the PDU session between the relay device and the data network is not limited, and reference can be made to the provisions in the current protocol about the process of establishing the PDU session between the relay device and the data network. The specific process is not described in detail in the embodiment of the present application.

[0421] Specifically, after the PDU session is established between the relay device and the data network, the policy control network element in the embodiment of the present application can make a policy decision to provide a QoS guarantee that is more in line with the actual access service of the remote terminal device.

[0422] In the 5G communication system, the policy control network element can be a PCF. In future communication systems, the policy control network element can still be a PCF network element, or can also have other names. In this application, the name of the policy control network element is not limited, and network elements that can provide policy rule information for control plane function network elements can be understood as the policy control network element.

[0423] In order to enable the policy control network element to provide QoS guarantee that is more in line with the actual access service of the remote terminal device in the process of policy decision, Figure 5 The method flowchart also includes:

[0424] S510, the relay device sends a first message to the session management network element.

[0425] The session management network element is used for session management.

[0426] In the 5G communication system, the session management network element can be an SMF network element. In future communication systems, the session management network element can still be an SMF network element, or can also have other names. In this application, the name of the session management network element is not limited, and network elements that can implement session management and IP address allocation and management of user equipment can be understood as the session management network element.

[0427] The first message includes a first identifier of the remote terminal device (remote UE ID).

[0428] Further, the first message also includes IP address information (IPinfo) allocated by the relay device for the remote terminal device.

[0429] The first identifier of the remote terminal device is used to identify the remote terminal device. The IP information allocated by the relay device for the remote terminal device can be referred to as the IP address information of the remote terminal device, and can be used to indicate the port corresponding to the remote terminal device (for example, the same PDU session carries service data of multiple remote terminal devices (remote terminal device #1 and remote terminal device #2), IP address information #1 (such as port A) corresponds to remote terminal device #1, and IP address information #2 (such as port B) corresponds to remote terminal device #2).

[0430] Optionally, the first message can multiplex the remote terminal device report (remote UE report) message specified in the current protocol, or the first message can be other signaling that the relay device needs to send to the session management network element in the current protocol, or the first message can also be new signaling between the relay device and the session management network element. It can be understood that when the first message multiplexes the signaling that the existing relay device needs to send to the session management network element, the signaling overhead can be saved.

[0431] Exemplarily, the first identity of the remote terminal device can be a generic public subscription identity (GPSI), can also be a user identifier (user ID) assigned to the remote terminal device by a third-party application, for example, account name information of the remote terminal device in the third-party application, can also be a unique user permanent identifier (SUPI) of the remote terminal device, and the like.

[0432] It should be understood that the GPSI, the user ID, and the SUPI described above are only examples and do not constitute any limitation on the protection scope of the present application. The specific implementation form of the first identity of the remote terminal device in the embodiments of the present application is not limited, and information capable of identifying the remote terminal device is within the protection scope of the present application.

[0433] Optionally, the first message can further include a first Relay Service Code configured for the remote terminal device and / or a second Relay Service Code configured for the relay device, wherein the first Relay Service Code and the second Relay Service Code can correspond to a same ProSe Application. It can be understood that the first Relay Service Code and the second Relay Service Code correspond to each other, that is, if the Relay Service Code needs to be carried in the first message, at least one of the first Relay Service Code and the second Relay Service Code can be used to determine the service type of the specific service currently initiated.

[0434] The above-mentioned correspondence between the first Relay Service Code and the second Relay Service Code can be understood as: the first Relay Service Code and the second Relay Service Code are the same, the first Relay Service Code and the second Relay Service Code are equivalent, or the first Relay Service Code and the second Relay Service Code can obtain equivalent information through a specific encryption or decryption algorithm, and the like.

[0435] In addition, it should be understood that in the embodiments of the present application, the relay device sending the first message to the session management network element includes:

[0436] Firstly, the relay device sends the first message to the access network device;

[0437] Secondly, the access network device forwards the first message to the access management function network element after receiving the first message;

[0438] Then, the access management function network element forwards the received first message to the session management network element.

[0439] Since the roles played by the access network device and the access management function network element in the first message transmission process can be understood as transparently transmitting the first message, the first message transmission process is simply described as the relay device sending the first message to the session management network element in the embodiments of the present application.

[0440] In the 5G communication system, the access management network element can be an AMF, and in future communication systems, the access management network element can still be an AMF, or it can also have other names. The name of the access management network element is not limited in the present application, and the network element capable of transmitting user policy between the user equipment and the PCF network element can be understood as the access management network element. Further, after the session management network element receives the first message, it needs to send the first identifier of the remote terminal device, the IP address information included in the received first message, and possibly the Relay Service Code to the policy control network element, i.e. Figure 5 The method flowchart also includes S520, the session management network element sends a second message to the policy control network element.

[0441] The second message includes the first identifier of the remote terminal device, wherein the specific form of the first identifier of the remote terminal device can refer to the first identifier of the remote terminal device carried in the above-mentioned first message, which will not be described here.

[0442] Optionally, the second message can also include the identifier of the relay device, for example, the SUPI or GPSI of the relay device.

[0443] Optionally, the second message can also include the IP address information allocated by the relay device for the remote terminal device as described above.

[0444] Optionally, when the first Relay Service Code is carried in the above-mentioned first message, the second message can also include the first Relay Service Code; similarly, when the second Relay Service Code is carried in the above-mentioned first message, the second message can also include the second Relay Service Code.

[0445] It should be noted that when the first Relay Service Code and / or the second Relay Service Code are included in the second message, the policy control network element can determine the service type of the currently initiated service after receiving the second message. For example, the first Relay Service Code and / or the second Relay Service Code are used to determine that the currently initiated service is a video service, an audio service, a VR service, or the like.

[0446] Optionally, the second message can multiplex a session management policy association create or update request message defined in the current protocol, or the second message can be other signaling defined in the current protocol and required to be sent by the session management network element to the policy control network element.

[0447] In the embodiments of the present application, the subsequent steps performed by the policy control network element after receiving the second message include the following possibilities:

[0448] Possibility one: the policy control network element can obtain the subscription data of the remote terminal device based on the information element carried in the second message after receiving the second message. In this possibility one Figure 5 The method flowchart shown also includes S531, in which the policy control network element obtains the subscription data of the remote terminal device.

[0449] The process of obtaining the subscription data of the remote terminal device specifically includes:

[0450] The policy control network element obtains the subscription data of the remote terminal device from the UDR network element based on the first identifier of the remote terminal device in the second message.

[0451] Further, in this possibility one, if the first Relay Service Code and / or the second Relay Service Code are carried in the second message, the policy control network element can determine the service type of the currently initiated service based on the first Relay Service Code and / or the second Relay Service Code and the local configuration of the policy control network element.

[0452] The mapping relationship between the part or all information included in the Relay Service Code (e.g., the first Relay Service Code or the second Relay Service Code) and the service type, that is, the policy control network element can determine the service type of the current initiated service on the premise that the Relay Service Code and the mapping relationship between the information in the Relay Service Code and the service type are known.

[0453] Optionally, the policy control network element can determine the service type of the current initiated service in the possible one can also be: the policy control network element and the 5G DDNMF network element signaling interaction, to parse the mapping relationship between the first Relay Service Code and / or the second Relay Service Code and the service, so that the policy control network element can determine the service type of the current initiated service based on the first Relay Service Code and / or the second Relay Service Code.

[0454] The signaling interaction between the policy control network element and the 5G DDNMF involved in the embodiments of the present application can include:

[0455] The policy control network element sends a query request message to the 5G DDNMF, and the query request message carries the Relay Service Code (e.g., the first Relay Service Code and / or the second Relay Service Code); the 5G DDNMF receives the query request message, determines the service type of the current initiated service based on the Relay Service Code carried in the query request message, and then sends the information related to the determined service type to the policy control network element in a query response message, so that the policy control network element can determine the service type of the current initiated service.

[0456] Optionally, the query request message can also carry the first identifier of the remote terminal device and / or the identifier of the relay device.

[0457] Possibility two, after the policy control network element receives the second message, when the first identifier of the remote terminal device included in the second message is the user ID, the policy control network element can interact with the application network element according to the user ID to determine the QoS guarantee required by the current initiated service, in the possible two Figure 5 The method flowchart also includes S532, the policy control network element receives the policy authorization request message sent by the application network element.

[0458] It should be noted that when the first identifier of the remote terminal device included in the second message described above is allocated to the third-party application, the policy control network element cannot obtain the subscription data corresponding to the remote terminal device based on the first identifier of the remote terminal device, so in this case the policy control network element can interact with the application network element to determine the actual first identifier of the remote terminal device (such as the SUPI or GPSI of the remote terminal device, etc.).

[0459] The signaling interaction between the policy control network element and the application network element can be implemented via a network exposure network element.

[0460] In the 5G communication system, the application network element can be an AF network element. In future communication systems, the application network element can still be an AF network element, or it can also have other names, and the name of the application network element is not limited in this application. The network element that can deliver the demand of the application side to the network side can be understood as the application network element.

[0461] The policy authorization request message includes the identifier of the service, the second identifier of the remote terminal device, and the QoS parameter requirement.

[0462] Exemplarily, the service identifier can be an APP ID, or the service identifier can also be a ProSe APP ID, which refers to the APP ID corresponding to the ProSe service. The APP ID, i.e. APP Name, can be specifically understood as a unified application name configured between the application network element and the policy control network element, which is used to identify the specific application corresponding to the application network element that initiates the current request.

[0463] The ProSe APP ID refers to the application name corresponding to the proximity service, which can be specifically understood as a unified application name configured on the remote terminal device, the application network element and the policy control network element, which is used to identify the specific application corresponding to the proximity service that is currently initiated.

[0464] Exemplarily, the identifier of the service can also be the first Relay Service Code and / or the second Relay Service Code described above.

[0465] The second identifier of the remote terminal device included in the policy authorization request message includes at least one of the following identifiers:

[0466] The second identity of the remote terminal device carried in the policy authorization request message is an identity composed of a GPSI of the remote terminal device, a user ID allocated to the remote terminal device by a third-party application, an Internet Protocol Version 6 (IPv6) address of the remote terminal device, an IPv6 prefix of the remote terminal device, an Internet Protocol Version 4 (IPv4) address of the relay device, and a transmission control protocol (TCP) or user datagram protocol (UDP) port number.

[0467] It should be noted that the specific form of the second identity of the remote terminal device included in the policy authorization request message can be any one of an identity composed of an IPv6 address of the remote terminal device, an IPv6 prefix of the remote terminal device, an IPv4 address of the relay device, and a TCP / UDP port number, because:

[0468] The first identity of the remote terminal device included in the second message received by the policy control network element from the session management network element is, for example, a GPSI of the remote terminal device or a user ID allocated to the remote terminal device by a third-party application. The IP address information included in the second message is, for example, an IPv6 address of the remote terminal device, an IPv6 prefix of the remote terminal device, an IPv4 address of the relay device, or a TCP / UDP port number. When the policy control network element receives a policy authorization request message from the application network element, if the IP address information included in the policy authorization request message is the same as the IP address information included in the second message, it can be understood that the policy authorization request message corresponds to the remote terminal device corresponding to the first identity of the remote terminal device. Therefore, the specific form of the second identity of the remote terminal device carried in the policy authorization request message can be the IP address information.

[0469] When the second identity of the remote terminal device carried in the policy authorization request message is IP address information, the IP address information and the IP address information carried in the second message have a one-to-one correspondence. For example, if the IP address information carried in the second message is an IPv6 prefix, the second identity of the remote terminal device carried in the policy authorization request message is an IPv6 prefix. If the IP address information carried in the second message is a TCP / UDP port number, the second identity of the remote terminal device carried in the policy authorization request message is an identity composed of an IPv4 address of the relay device and a TCP / UDP port number.

[0470] The QoS parameter requirement included in the policy authorization request message is optional, used to indicate the QoS guarantee required by the current service as input information for the policy control network element to perform policy decision, and assist the policy control network element to perform policy decision. The QoS parameter requirement can include bandwidth guarantee, scheduling priority and other information corresponding to the service.

[0471] It should be noted that, in the second possible implementation, the premise for the policy control network element to interact with the application network element to determine the QoS guarantee required by the current initiated service is that the application network element subscribes to the remote terminal device online event, and therefore, before S532 is performed in the second possible implementation, Figure 5 The method flowchart also includes that the application network element subscribes to the remote terminal device online event.

[0472] The flowchart of the application network element subscribing to the remote terminal device online event specifically includes:

[0473] S533, the application network element sends a subscription message to the policy control network element, and the subscription message is used to subscribe to the remote terminal device online event. The subscription message includes the identity of the service and a notification uniform resource identifier (Notification URI) of the application network element receiving notification. The Notification URI can be understood as the address information of the application network element receiving the event report, used to indicate the destination of receiving the event report information from the policy control network element, and the identity of the service is used for the policy control network element to perform capability verification, event matching and determine whether the event needs to be reported to the application network element.

[0474] The specific form of the identity of the service carried in the subscription message can refer to the identity of the service included in the policy authorization request message sent by the application network element in S532, which will not be described here.

[0475] Optionally, the remote terminal device online event subscribed by the application network element can be identified by an event identifier (event ID), that is, the subscription message carries the event ID, the identity of the service and the event notification address Notification URI.

[0476] It should be noted that the application network element sending the subscription message to the policy control network element means that the application network element sends the subscription message to the policy control network element through a network exposure function network element. The network exposure function network element plays a role of transparent transmission, so it can be simply described that the application network element sends the subscription message to the policy control network element.

[0477] Further, after the policy control network element receives the subscription message, a subscription response message needs to be sent by the network exposure function network element to the application network element, for responding whether the subscription of the application network element is successful.

[0478] In the case that the application network element subscribes to the remote terminal device online event, the process of signaling interaction between the policy control network element and the application network element specifically includes:

[0479] S534, the policy control network element sends a notification message to the application network element, and the notification message is used to notify the remote terminal device online event. The notification message carries the first identifier of the remote terminal device and the identifier of the service, and the identifier of the service is used to identify the service type of the current initiated service.

[0480] After the application network element receives the notification message, a notification response message needs to be sent to the policy control network element, for responding whether the notification message sent by the policy control network element is successful.

[0481] As a possible implementation manner, the policy authorization request message sent by the application network element to the policy control network element is carried in the notification response message, that is, the notification response message and the policy authorization request message are sent to the policy control network element through the same message;

[0482] As another possible implementation manner, the policy authorization request message and the notification response message are sent by the application network element to the policy control network element respectively.

[0483] In the embodiment of the application, the sequence of sending the policy authorization request message and the notification response message is not limited, and whether the same message is sent is also not limited.

[0484] It should be noted that the possible one and the possible two can be executed simultaneously.

[0485] Possibility three, after the policy control network element receives the second message, a second response message is sent to the relay device, and the second response message is used to indicate the PDU session establishment or update response. In this possibility three Figure 5 The method flowchart also includes S535, the policy control network element sends a second response message to the relay device.

[0486] In the embodiment of the application, how the policy control network element returns the second response message after receiving the second message is not limited, and it is understood that the response made by the policy control network element after receiving the second message can be referred to the existing protocol.

[0487] The policy control network element sends the second response message to the relay device, including:

[0488] Firstly, the policy control network element sends the second response message to the session management network element;

[0489] Secondly, the session management network element forwards the second response message to the access network device after receiving the second response message;

[0490] Then, the access network device forwards the second response message to the relay device after receiving the second response message.

[0491] Since the roles of the access network device and the session management network element in the transmission of the second response message can be understood as transparently transmitting the second response message, the transmission process of the second response message is simply described as the policy control network element sending the second response message to the relay device in the embodiments of the present application.

[0492] In the third possibility, the application network element can query the information of the policy control network element that provides services for the PDU session established in the above process through the policy control network element. Therefore, in the third possibility Figure 5 The method flow shown in the third possibility further includes S536, the application network element queries the information of the policy control network element.

[0493] Specifically, the application network element can query the information of the policy control network element that provides services for the PDU session according to the IP address, data network name (DNN), and other information in the message sent by the remote terminal device through the BSF.

[0494] It should be noted that for the current ProSe relay scenario, the message delivered by the remote terminal device presents the IP address of the relay device to the outside, that is, the IP address information carried in the information query request of the policy control network element initiated by the application network element actually indicates the IP address corresponding to the relay device.

[0495] Further, in the third possibility, the application network element can send a policy authorization request message to the policy control network element according to the information of the policy control network element queried in S536, and in the third possibility Figure 5 The method flow shown in the third possibility further includes S537, the application network element sends a policy authorization request message to the policy control network element. The policy authorization request message is used to instruct the policy control network element to perform context association, that is, to associate the policy authorization request to the service initiated by the specific remote terminal device under the specific PDU session. Specifically, the policy control network element can associate to the corresponding user context according to the second identifier of the remote terminal device carried in the policy authorization request message, so as to perform policy decision.

[0496] The difference between the policy authorization request message sent by the application network element to the policy control network element in the third possibility and the policy authorization request message sent by the application network element to the policy control network element in the second possibility shown in step S532 is that:

[0497] The third possible step S537 is initiated by the application network element, and therefore the policy control request message sent by the application network element needs to carry the second identifier of the remote terminal device, and also needs to carry the identifier of the service, and optionally carries the QoS parameter requirement.

[0498] The third possible step S537 is initiated by the application network element, and therefore the policy control request message sent by the application network element needs to carry the second identifier of the remote terminal device, and also needs to carry the identifier of the service, and optionally carries the QoS parameter requirement.

[0499] In addition, it should be noted that the third possible application network element can obtain the second identifier of the remote terminal device and the identifier of the service through the user plane channel, for example, the user plane message sent by the remote terminal device after being online includes the second identifier of the remote terminal device and the identifier of the service, and then the application network element can obtain the second identifier of the remote terminal device and the identifier of the service through the user plane sensing. In the embodiment of the application, how the application network element senses through the user plane is not limited, and can refer to the related provisions in the current protocol or the next generation protocol, which will not be described here.

[0500] Further, after the policy control network element learns the service guarantee requirement from the application network element, and / or, after the policy control network element learns the current initiated service type and the subscription data of the remote terminal device, the policy control network element can generate a policy charging control (PCC) rule based on the learned information, that is Figure 5 The method flowchart also includes S540, the policy control network element generates a PCC rule.

[0501] The PCC rule includes the first QoS parameter of the first communication interface and the second QoS parameter of the second communication interface.

[0502] The first QoS parameter can include 5G interface QoS indicator (5G QoS Indicator, 5QI), address resolution protocol (address resolution protocol, ARP), guaranteed bitrate (guaranteed bitrate, GBR), maximum bitrate (maximum bitrate, MBR), session aggregated maximum bitrate (session aggregated maximum bitrate, Session AMBR), etc.

[0503] The second QoS parameter can include PC5 interface QoS indicator (PC5 QoS Indicator, PQI), ARP, GBR, MBR, total maximum bitrate (total maximum bitrate, TMBR), etc.

[0504] The first communication interface is a communication interface (such as a Uu interface) between the relay device and the access network device, and the second communication interface is a communication interface (such as a PC5 interface) between the relay device and the remote terminal device.

[0505] The first QoS parameter is used to generate a first QoS rule, and the second QoS parameter is used to generate a second QoS rule. The first QoS rule and the first QoS profile correspond to the QoS rule of the first communication interface between the relay device and the access network device, and the second QoS rule corresponds to the QoS rule of the second communication interface between the relay device and the remote terminal device.

[0506] It should be noted that the first QoS profile mainly includes the quality of service guarantee parameters required to be executed by the service flow (such as one or more of the parameter information of 5QI, ARP, AMBR, GBR, MBR, etc.), and the first QoS rule or the second QoS rule can include part or all of the above-mentioned quality of service guarantee parameters, and can also include the flow description information corresponding to the service flow, which is used for the remote terminal device and / or the relay device to perform uplink flow matching. The flow description information can be determined based on the IP address information of the remote terminal device.

[0507] In addition, it should be noted that the QoS information determined by the policy control network element based on the subscription data of the remote terminal device is only at the terminal device granularity, and is not determined to the specific service granularity, i.e., when the service type is not perceived, the parameters such as 5QI, ARP, and Session-AMBR corresponding to the default QoS Flow can be determined. Therefore, in order to determine the QoS information corresponding to different services by the policy control network element for different services, the identifier of the service (such as the first Relay Service Code and / or the second Relay Service Code) needs to be carried in the second message and / or the policy authorization request message.

[0508] Exemplarily, in the process of generating the PCC rule by the policy control network element, the first QoS parameter and the second QoS parameter that can be used can be determined according to the subscription data corresponding to the relay device and the remote terminal device, respectively, so as to avoid violating the subscription policy of the relay device and the remote terminal device.

[0509] After the PCC rule is generated by the policy control network element in the embodiment of the present application, the PCC rule is sent to the session management network element, and then Figure 5 The method flowchart also includes S550, in which the policy control network element sends the PCC rule to the session management network element.

[0510] After the session management network element receives the PCC rule, the QoS Flow binding is performed according to the received PCC rule, and the PCC rule is associated with a specific QoS Flow, wherein the QoS Flow is uniquely identified by a QoS Flow Identifier (QFI).

[0511] The session management network element can allocate the QFI for the QoS Flow by itself, and the QFI is unique within the PDU session granularity. The main function of the QFI is to uniquely identify a specific QoS Flow within the PDU session, so that the relay device, the remote terminal device, and the access network device can identify and perform the QoS guarantee corresponding to the QFI for the QoS Flow.

[0512] Specifically, the session management network element generates a first QoS Rule, and the manner in which the first QoS Profile and the first QoS Rule are generated includes:

[0513] The first QoS Rule is determined according to the first QoS parameter and the second QoS parameter in the PCC rule and the flow description information, and the corresponding information elements in the first QoS Profile and the first QoS Rule are valued.

[0514] The first QoS profile is information provided by the session management network element to the access network device, and mainly includes first QoS parameter related information.

[0515] The first QoS rule is information provided by the session management network element to the relay device, and the second QoS rule is information provided by the session management network element to the remote terminal device. In addition to including part or all of the first QoS parameter and the second QoS parameter, respectively, the first QoS rule and the second QoS rule can also include flow description information, which is used to associate the service flow to a specific QoS flow when the relay device and the remote terminal device perform uplink flow matching.

[0516] The session management network element sends a third message to the access network device, Figure 5 The method flowchart also includes S560, the session management network element sends a third message to the access network device, and the third message is used to instruct the access network device to perform resource reservation. The resources include, for example, bandwidth resources, scheduling resources, etc. For GBR services, the access network device needs to provide bandwidth guarantee for the GBR services to avoid the impact of other services on the user service experience.

[0517] The third message includes the QFI, the first QoS profile, the first QoS rule, and the second QoS rule described above. Specifically, the relay device, the remote terminal device, or the UPF needs to add a QFI tag in the uplink / downlink packet header, that is, to identify that a service flow belongs to the QoS Flow corresponding to the QFI, and the access network device needs to execute the QoS profile corresponding to the QoS Flow according to the QFI.

[0518] Further, after the access network device receives the third message described above, the access network device performs resource reservation based on the third message, and sends the first QoS rule and the second QoS rule included in the third message to the relay device. After the relay device receives the second QoS rule, the relay device can forward the second QoS rule to the remote terminal device through the second communication interface (such as the PC5 interface) between the relay device and the remote terminal device, so that Figure 5 The method flowchart also includes:

[0519] S570, the access network device sends the second QoS rule to the relay device; and S571, the relay device sends the second QoS rule to the remote terminal device. After receiving the information, the remote terminal device can perform resource reservation for the service, and perform the quality of service QoS guarantee required by the second QoS rule for the service flow.

[0520] In particular, the quality of service (QoS) guarantee performed by the remote terminal device and the relay device can include: performing mapping between uplink and / or downlink traffic flows and QoS flows in the PC5 interface according to traffic flow information in the second QoS rule, and performing QoS guarantee strategies such as bandwidth control, scheduling priority, packet loss rate, and latency of uplink and / or downlink traffic flows in the PC5 interface according to one or more parameters such as TMBR, PQI, and GBR in the second QoS rule.

[0521] Figure 5 In the illustrated embodiment, the relevant information of the remote terminal device (e.g., the identifier of the remote terminal device described above) and the service-related information (e.g., the service identifier described above) are provided to the policy control network element, so that the policy control network element performs more reasonable policy decisions and improves the service quality guarantee between the remote terminal device and the relay device.

[0522] For ease of understanding, the method for guaranteeing services provided by the embodiments of the present application will be described in detail below. Figure 6 and Figure 7 For ease of understanding, the method for guaranteeing services provided by the embodiments of the present application will be described in detail below.

[0523] As Figure 6 illustrated, Figure 6 is a schematic flowchart of another method for guaranteeing services provided by the embodiments of the present application. The method for guaranteeing services includes at least the following steps:

[0524] S601, a remote (Remote) UE and a relay device (Relay) establish a PC5 connection.

[0525] Similar to step S501 in Figure 5 , it can be understood that the remote terminal device and the relay device illustrated in step S501 are both terminal devices, so the communication connection between the Remote UE and the Relay is a PC5 connection.

[0526] S602, the Relay establishes a PDU session.

[0527] Similar to step S502 in Figure 5 , further description is not given here.

[0528] S610, the Relay sends a Remote UE report to an SMF.

[0529] In this embodiment, the Relay sends a Remote UE report (report) to the SMF through a RAN and an AMF, where the RAN is an access network device accessed by the Relay.

[0530] The Remote UE report includes a user identifier of the Remote UE, and the user identifier of the Remote UE is associated withFigure 5 The first identifier shown in step S510 is the same, and thus will not be described again here.

[0531] Further, the Remote UE report can also include IP info allocated by the Relay for the Remote UE, which is the same as the IP info shown in step S510, and thus will not be described again here. Figure 5 The IP info shown in step S510 is the same, and thus will not be described again here.

[0532] Further, the Remote UE report can also include the Relay Service Code corresponding to the Remote UE and / or the Relay Service Code corresponding to the Relay, wherein the Relay Service Code corresponding to the Remote UE is the same as the first Relay Service Code shown in step S510, and the Relay Service Code corresponding to the Relay is the same as the second Relay Service Code shown in step S510, and thus will not be described again here. Figure 5 The first Relay Service Code shown in step S510 is the same, and thus will not be described again here. Figure 5 The second Relay Service Code shown in step S510 is the same, and thus will not be described again here.

[0533] S620, the SMF sends an SM association policy creation or update message to the PCF.

[0534] After the SMF receives the Remote UE report described above in this embodiment, the information carried in the Remote UE report can be sent to the PCF through the SM association policy creation or update message.

[0535] For example, the user identifier of the Remote UE carried in the Remote UE report can be sent to the PCF through the SM association policy creation or update message; or,

[0536] When the Remote UE report carries the Relay Service Code corresponding to the Remote UE and / or the Relay Service Code corresponding to the Relay, after the SMF receives the Remote UE report described above, the Relay Service Code corresponding to the Remote UE and / or the Relay Service Code corresponding to the Relay carried in the Remote UE report can be sent to the PCF through the SM association policy creation or update message.

[0537] Further, the SM association policy creation or update message also carries the user identifier of the Relay and the IP info mentioned above.

[0538] After the PCF receives the SM association policy creation or update message in this embodiment, the steps that can be performed by the PCF based on the information carried in the association policy creation or update message include the following two possibilities:

[0539] Possibility one:

[0540] The method flow shown in this embodiment also includes S621, in which the PCF acquires the subscription data of the Remote UE. The specific way of acquiring the subscription data of the Remote UE can refer to the way shown in step S531 in Figure 5 , which will not be repeated here.

[0541] Possibility two:

[0542] The method flow shown in this embodiment also includes S622, in which the AF sends a message for subscribing to the Remote UE online event to the PCF. This message is called a Remote UE subscription message. The specific subscription process can refer to the process shown in step S533 in Figure 5 , which will not be repeated here.

[0543] After the PCF receives the SM association policy creation or update message mentioned above, the PCF can interact with the AF to obtain the QoS guarantee required by the current initiated service. The method flow shown in this embodiment also includes:

[0544] S623, the PCF sends a notification message for notifying the Remote UE online event to the AF. The notification message carries the user identifier of the Remote UE and the service identifier of the current initiated service. The specific notification method can refer to the method shown in step S534 in Figure 5 , which will not be repeated here.

[0545] S624, the AF sends a policy authorization request message to the PCF. The specific description of the policy authorization request message can refer to the description shown in step S532 in Figure 5 , which will not be repeated here.

[0546] It should be understood that the above-mentioned possibility one and possibility two can be executed, that is, the PCF can acquire the subscription data of the Remote UE and can also receive the policy authorization request message from the AF.

[0547] Further, after the above steps are performed, the PCF in this embodiment can perform policy decision, that is, the method flow shown in this embodiment also includes S630, in which the PCF performs policy decision.

[0548] Specifically, the way that the PCF makes a policy decision to generate a PCC rule can refer to Figure 5 In step S540 shown in the foregoing embodiment, the details are not repeated here.

[0549] The PCF sends the generated PCC rule to the SMF, and the SMF generates, based on the QoS parameter in the PCC rule, a QoS rule corresponding to the Uu interface between the Relay and the RAN (which can be referred to as a Uu QoS rule for short) and a QoS rule corresponding to the PC5 interface between the Remote UE and the Relay (which can be referred to as a PC5 QoS rule for short); further, the SMF sends the Uu QoS rule and the PC5 QoS rule to the RAN, and the RAN sends the PC5 QoS rule to the Relay, and the Relay sends the PC5 QoS rule to the Remote UE, so the method flow shown in this embodiment further includes:

[0550] S640, the PCF sends the PCC rule to the SMF; S650, the SMF generates the Uu QoS rule and the PC5 QoS rule; S660, the SMF sends the Uu QoS rule and the PC5 QoS rule to the RAN;

[0551] S670, the RAN sends the PC5 QoS rule to the Relay;

[0552] S680, the Relay sends the PC5 QoS rule to the Remote UE. Specifically, S640-S680 can refer to the description of S540-S571 in Figure 7

[0553] As shown in Figure 7 , Figure 6 is another method flow diagram of service assurance provided by the embodiment of the application. The service assurance method includes at least the following steps:

[0554] S701, a Remote UE and a Relay device establish a PC5 connection.

[0555] The same as step S601 in Figure 6 , the details are not repeated here.

[0556] S702, the Relay establishes a PDU session.

[0557] The same as step S602 in Figure 6 , the details are not repeated here.

[0558] S710, the Relay sends a Remote UE report to the SMF. ​

[0559] As step S610 in Figure 6 , which will not be repeated here.

[0560] S720, the SMF sends an SM associated policy creation or update message to the PCF.

[0561] As step S620 in Figure 7 , which will not be repeated here.

[0562] After the SMF receives the SM associated policy creation or update message described above in this embodiment, instead of obtaining the subscription data of the Remote UE according to the received SM associated policy creation or update message or sending a notification to the AF to notify that the Remote UE is online, the SMF performs a regular policy session establishment process to send an SM associated policy creation or update response to the SMF, and the SMF sends a confirmation message to the Relay to confirm the session establishment, and the method flowchart shown in this embodiment further includes:

[0563] S721, the PCF sends an SM associated policy creation or update response to the SMF; and S722, the SMF sends a confirmation message to the Relay.

[0564] Further, in this embodiment, the AF can learn the PCF that provides services for the PDU session established in the above process through the PCF, and in this embodiment Figure 7 , the method flowchart further includes S730, the AF queries the information of the PDU.

[0565] Also, in this embodiment, the AF can perceive that the Remote UE is online through the user plane, and obtain the user identifier of the Remote UE and the service identifier of the currently initiated service through the user plane perception.

[0566] After the AF learns the information of the PCF, the user identifier of the Remote UE, and the service identifier of the currently initiated service, the AF can send a policy authorization request message to the PCF, and in this embodiment Figure 5 , the method flowchart further includes S740, the AF sends a policy authorization request message to the PCF, and specifically, the information included in the policy authorization request message can refer to that shown in step S537 in Figure 5 , which will not be repeated here.

[0567] Further, after performing the above steps, the method flowchart shown in this embodiment further includes S750, the PCF makes a policy decision; S760, the PCF sends a PCC rule to the SMF; S770, the SMF generates a Uu QoS rule and a PC5 QoS rule; S780, the SMF sends the Uu QoS rule and the PC5 QoS rule to the RAN; S790, the RAN sends the PC5 QoS rule to the Relay; and S791, the Relay sends the PC5 QoS rule to the Remote UE. Specifically, S750-S791 can refer to the description of S540-S571 in Figure 8

[0568] As shown in Figure 8 , Figure 5 is another method flowchart of service guarantee provided by the embodiments of the present application. The method of service guarantee includes at least the following steps:

[0569] S801, a Remote UE (an example of a remote terminal device) and a Relay (an example of a relay device) establish a PC5 connection.

[0570] The same as S501 in Figure 5 , which will not be repeated here.

[0571] S802, the Relay establishes a PDU session.

[0572] The same as S502 in Figure 5 , which will not be repeated here.

[0573] S803, the Relay sends a first message to an SMF (an example of a session management network element).

[0574] The same as S510 in Figure 8 , which will not be repeated here.

[0575] In order to enable the SMF to provide a maximum bit rate (MBR) that is more consistent with the actual available bandwidth of the Remote UE in the process of establishing a PDR, Figure 8 the method flowchart shown in this embodiment further includes:

[0576] S810, the SMF obtains session management subscription data of the Remote UE.

[0577] ​The session management subscription data of the Remote UE can include an AMBR of the Remote UE. The AMBR of the Remote UE can include a subscription session AMBR of the Remote UE. Optionally, the AMBR of the Remote UE can further include a PC5 interface AMBR of the Remote UE or a PC5 link AMBR of the Remote UE.

[0578] Embodiments of the present application do not limit the method for the SMF to obtain the session management subscription data of the Remote UE.

[0579] As an example, if the SMF pre-stores or pre-configures the session management subscription data of the Remote UE, the SMF can obtain the session management subscription data of the Remote UE from the local database according to the first identifier.

[0580] As another example, if the SMF does not pre-store or pre-configure the session management subscription data of the Remote UE, the SMF can request the session management subscription data of the Remote UE from the UDM / UDR, or the SMF obtains the session management subscription data of the Remote UE from the DN-AAA server in the process of secondary authentication with the Remote UE.

[0581] For example, the SMF obtains the subscription session management data of the Remote UE from the UDM / UDR at S811.

[0582] The SMF can send a second request message to the UDM (an example of a data management network element) / UDR (an example of a data warehouse network element), the second request message being used to request the session management subscription data of the Remote UE, the second request message including the first identifier of the Remote UE. Further, the UDM / UDR obtains the session management subscription data of the Remote UE from the local database according to the first identifier, and sends a second response message to the SMF, the second response message including the session management subscription data of the Remote UE.

[0583] For example, the second request message can reuse the Nudm_SDM_Get request service specified in the current protocol, that is, the SMF can use the Nudm_SDM_Get signaling to request the session management subscription data of the Remote UE from the UDM.

[0584] For another example, the second request message can also reuse the Nudm_SDM_Subscribe signaling specified in the current protocol, that is, the SMF can use the Nudm_SDM_Subscribe signaling to subscribe to the session management subscription data update notification of the Remote UE from the UDM.

[0585] Optionally, if the UDM does not pre-store the session management subscription data of the Remote UE, the UDM can send a request message to the UDR (an example of a data warehouse network element) to obtain the session management subscription data of the Remote UE. For example, the UDM can use Nudr_DM_Query signaling to obtain the session management subscription data of the Remote UE from the UDR, or the UDM can use Nudr_DM_Subscribe signaling to subscribe to the update notification of the session management subscription data of the Remote UE from the UDR.

[0586] Optionally, if the first identifier of the Remote UE obtained by the SMF from the Relay is a SUPI, the SMF can include the SUPI in the second request message sent to the UDM / UDR; further, the UDM / UDR can feed back the session management subscription data corresponding to the SUPI to the SMF according to the SUPI, that is, the UDM / UDR includes the session management subscription data corresponding to the SUPI in the second response message sent to the SMF.

[0587] Optionally, if the first identifier of the Remote UE obtained by the SMF from the Relay is a GPSI or a user identifier (referred to as a third-party identifier) allocated by a third-party application server for the Remote UE, the SMF can obtain the SUPI corresponding to the GPSI or the third-party identifier of the Remote UE from the UDM / UDR; further, the SMF carries the SUPI of the Remote UE obtained from the UDM / UDR in the second request message to send to the UDM / UDR to obtain the session management subscription data of the Remote UE.

[0588] Optionally, if the first identifier of the Remote UE obtained by the SMF from the Relay is a GPSI or a third-party identifier, the SMF can carry the GPSI or the third-party identifier in the second request message to send to the UDM / UDR to obtain the session management subscription data of the Remote UE. Further, after receiving the second request message from the SMF, the UDM / UDR can find the corresponding SUPI information according to the GPSI or the third-party identifier in the second request message, further, obtain the session management subscription data corresponding to the SUPI from the local database according to the SUPI information, and feed back the session management subscription data corresponding to the SUPI to the SMF. Optionally, the UDM / UDR can also feed back the SUPI corresponding to the GPSI or the third-party identifier of the Remote UE to the SMF, that is, the UDM / UDR can include the SUPI corresponding to the GPSI or the third-party identifier of the Remote UE in the second response message sent to the SMF.

[0589] Optionally, the first indication information can also be included in the second request message, and the first indication information is used to indicate that the Remote UE accesses the network through the Relay. For example, if the second request message sent by the SMF to the UDM / UDR further includes a third identifier of the Relay, the UDM / UDR cannot distinguish the Remote UE and the Relay, and further, the UDM / UDR cannot determine whether to feed back the session management subscription data corresponding to the first identifier to the SMF or feed back the session management subscription data corresponding to the third identifier to the SMF. In this case, if the third request message further includes the first indication information, the UDM / UDR can distinguish the Remote UE and the Relay according to the first indication information, and further, the UDM / UDR can feed back the session management subscription data corresponding to the first identifier to the SMF, i.e., feed back the session management subscription data of the Remote UE to the SMF.

[0590] For another example, the SMF obtains the session management subscription data of the Remote UE from the DN-AAA server.

[0591] The SMF can send a third request message to the DN-AAA server, the third request message is used to request the session management subscription data of the Remote UE, and the third request message includes the first identifier of the Remote UE. Further, the DN-AAA server obtains the session management subscription data of the Remote UE from the local database according to the first identifier, and sends a third response message to the SMF, and the third response message includes the session management subscription data of the Remote UE.

[0592] As a further example, the SMF can obtain the session management subscription data of the Remote UE from the PCF.

[0593] The method flow that the SMF obtains the session management subscription data of the Remote UE from the PCF can include S821 to S823:

[0594] S821, the SMF sends a second message to the PCF.

[0595] The description of the SMF sending the second message to the PCF can refer to the description in S520 above.

[0596] Optionally, if the SMF has obtained the session management subscription data of the Remote UE from the UDM / UDR or the DN-AAA server in advance, the second message can further include the session management subscription data of the Remote UE.

[0597] S822, the PCF generates PCC rules and / or session-related policies.

[0598] The PCF can generate session-related policies and / or PCC rules according to subscription data corresponding to the Remote UE and the Relay. The subscription data corresponding to the Remote UE and the Relay can include policy-related subscription data and session management subscription data.

[0599] Optionally, if the PCF does not pre-store or pre-configure the subscription data of the Remote UE, before S822, the method can further include S8221, the PCF obtains the subscription data of the Remote UE from the UDM / UDR.

[0600] Specifically, the PCF can send a fourth request message to the UDM / UDR, the fourth request message being used to request the subscription data of the Remote UE, and the fourth request message including the first identifier of the Remote UE; further, the UDM / UDR feeds back a fourth response message to the PCF, and the fourth response message includes the subscription data of the Remote UE.

[0601] If the first message received by the PCF includes the session management subscription data of the Remote UE, in S8221, the PCF obtains the policy-related subscription data of the Remote UE from the UDM / UDR. Optionally, the PCF can also obtain the session management subscription data of the Remote UE from the UDM / UDR to verify the session management subscription data included in the second message.

[0602] Optionally, the fourth request message can include first indication information, the first indication information being used to indicate that the Remote UE accesses the network through the Relay.

[0603] The PCC rules and / or the session-related policies generated by the PCF can include the session management subscription data of the Remote UE.

[0604] For example, the PCC rules can include a second QoS parameter of a second communication interface, the second communication interface being a communication interface between the Remote UE and the Relay, and the second QoS parameter can include an AMBR that can be used by the Remote UE.

[0605] For another example, the session-related policies can include an AMBR that can be used by the Remote UE.

[0606] The AMBR that can be used by the Remote UE is determined according to the session management subscription data of the Remote UE, for example, the AMBR that can be used by the Remote UE is the minimum value of a subscription session AMBR of the Remote UE and a PC5 interface AMBR / PC5 link AMBR.

[0607] More description about PCF generating session related policy and / or PCC rule can refer to the description in S540 above.

[0608] S823, the PCF sends the session related policy and / or PCC rule to the SMF.

[0609] After the SMF receives the session related policy and / or PCC rule, the SMF obtains the session management subscription data of the Remote UE according to the session related policy and / or PCC rule.

[0610] S820, the SMF generates a PDR.

[0611] After the SMF obtains the session management subscription data of the Remote UE, the SMF can establish a separate PDR for the Remote UE, i.e., the SMF generates a PDR corresponding to the Remote UE. The SMF can generate the PDR corresponding to the Remote UE according to at least one of the IP address, the port number or the MAC address of the Remote UE.

[0612] The PDR includes a QER, and the maximum bandwidth in the QER is determined based on the AMBR of the Remote UE. The maximum bandwidth in the QER can also be referred to as MBR.

[0613] As an example, if the AMBR of the Remote UE obtained by the SMF is the subscription session AMBR of the Remote UE, the maximum bandwidth in the QER is the subscription session AMBR of the Remote UE.

[0614] As another example, if the AMBR of the Remote UE obtained by the SMF is the PC5 interface AMBR of the Remote UE, the maximum bandwidth in the QER is the PC5 interface AMBR of the Remote UE.

[0615] As yet another example, if the AMBR of the Remote UE obtained by the SMF is the PC5 link AMBR of the Remote UE, the maximum bandwidth in the QER is the PC5 link AMBR of the Remote UE.

[0616] As a further example, if the AMBR of the Remote UE obtained by the SMF is the subscription session AMBR of the Remote UE and the PC5 interface AMBR / PC5 link AMBR, the maximum bandwidth in the QER is the minimum value of the subscription session AMBR of the Remote UE and the PC5 interface AMBR / PC5 link AMBR, i.e., the maximum bandwidth in the QER = min (the subscription session AMBR of the Remote UE, the PC5 interface AMBR / PC5 link AMBR).

[0617] As a further example, if the PCC rule and / or session-related policy received by the SMF from the PCF (an example of a policy control network element) includes the AMBR that can be used by the Remote UE, the maximum bandwidth in the QER is the minimum value of the AMBR of the Remote UE and the AMBR that can be used by the Remote UE.

[0618] S830, the SMF sends the PDR to the UPF.

[0619] Correspondingly, after receiving the PDR from the SMF, the UPF can send a feedback information to the SMF to indicate that the PDR has been received.

[0620] Optionally, Figure 8 The method shown can also include S840 and S850:

[0621] S840, the SMF sends a fourth message to the Relay, and the fourth message includes the session management subscription data of the terminal device.

[0622] Optionally, the AMBR of the Remote terminal device can be included in the fourth message. In the case that the AMBR of the Remote terminal device is not the same as the AMBR of the Relay, the SMF can send the fourth message to the Relay.

[0623] Optionally, the maximum bandwidth in the QER can be included in the fourth message, i.e., the fourth message includes the MBR. If the QER of the Remote UE is different from the subscription session AMBR of the Relay, the SMF sends the fourth message to the Relay.

[0624] S850, the Remote UE performs PC5 link update with the Relay.

[0625] Specifically, after receiving the fourth message from the SMF, the Relay adjusts the AMBR of the PC5 link according to the session management subscription data of the Remote UE included in the fourth message and the Remote UE. That is, the AMBR of the PC5 link is updated to the AMBR of the Remote UE.

[0626] For example, the Remote UE and the Relay update the AMBR of the PC5 link to the minimum of the subscription session AMBR of the Remote UE and the PC5 interface AMBR / PC5 link AMBR.

[0627] Figure 9 The method shown can also include S860: the UPF transmits data to the Remote UE through the Relay according to the received PDR.

[0628] Specifically, the UPF can filter out the data to be sent to the Remote UE according to the PDR, and send the data to the Remote UE at a rate limited by the maximum bandwidth in the QER included in the PDR, i.e., the rate at which the UPF sends the data to the Remote UE through the Relay cannot exceed the maximum bandwidth in the QER.

[0629] In the embodiments of the present application, if the SMF obtains the AMBR (subscription session AMBR and / or PC5 interface AMBR / PC5 link AMBR) of the Remote UE, the SMF can determine the MBR in the QER of the Remote UE based on the AMBR of the Remote UE in the N4 session configuration. Thus, in the process of the UPF transmitting the data packets of the Remote UE, the rate at which the data is sent to the Remote UE can be limited according to the MBR of the Remote UE. At the same time, the SMF can send the MBR of the Remote UE to the Relay, so that the Relay can update the AMBR of the PC5 link to the MBR of the Remote UE.

[0630] As shown in Figure 9 , Figure 5 is another method for service assurance provided by the embodiments of the present application. The service assurance method includes at least the following steps:

[0631] S901, the PCF (an example of a policy control network element) obtains the session management subscription data of the Remote UE (an example of a remote terminal device).

[0632] In the case where the PCF needs to configure the UE policy information for the Remote UE, the PCF can obtain the session management subscription data of the Remote UE from the UDM (an example of a data management network element) / UDR (an example of a data warehouse network element).

[0633] The session management subscription data of the Remote UE can comprise PDU session related information, such as DNN, slice information, PDU session type, etc. The session management subscription data of the Remote UE can also comprise an AMBR of the Remote UE. The AMBR of the Remote UE can comprise a subscribed session AMBR of the Remote UE. Optionally, the AMBR of the Remote UE can also comprise a PC5 interface AMBR of the Remote UE or a PC5 link AMBR of the Remote UE.

[0634] S902, the PCF decides a relay service code (RSC).

[0635] Specifically, the PCF decides the RSC according to the session management subscription data of the Remote UE, i.e., the RSC decided by the PCF is associated with the session management subscription data of the Remote UE. Specifically, the PCF can decide the RSC according to the AMBR of the Remote UE, i.e., the RSC decided by the PCF is associated with the AMBR of the Remote UE.

[0636] The PCF can decide a first RSC and / or a second RSC according to the session management subscription data of the Remote UE, the first RSC being a RSC configured for the Remote UE, and the second RSC being a RSC configured for a Relay (an example of a relay device). The first RSC and / or the second RSC is associated with the session management subscription data of the Remote UE.

[0637] Optionally, the PCF can decide the first RSC and / or the second RSC according to the AMBR of the Remote UE.

[0638] Optionally, the PCF can decide the first RSC and / or the second RSC according to the minimum value of the subscribed session AMBR and the PC5 interface AMBR / PC5 link AMBR of the Remote UE.

[0639] Optionally, the PCF can save the RSC in association with the session management subscription data of the Remote UE.

[0640] Optionally, the method can further comprise S903, the PCF sends the RSC and second indication information to the UDM / UDR, the second indication information being used to indicate that the RSC is associated with the session management subscription data of the Remote UE. Accordingly, after receiving the RSC from the PCF, the UDM / UDR saves the RSC in association with the session management subscription data of the Remote UE, i.e., the session management subscription data of the Remote UE can be determined according to the RSC.

[0641] S904, the PCF sends the RSC to the Remote UE and the Relay.

[0642] Specifically, if the PCF decides the first RSC in S902, the PCF can send the first RSC to the Remote UE and the Relay; further, the Remote UE and the Relay can establish the PC5 connection based on the first RSC.

[0643] If the PCF decides the second RSC in S902, the PCF can send the second RSC to the Remote UE and the Relay; further, the Remote UE and the Relay can establish the PC5 connection based on the second RSC.

[0644] If the PCF decides the first RSC and the second RSC in S902, the PCF can send the first RSC to the Remote UE and the second RSC to the Relay; further, the Remote UE and the Relay can establish the PC5 connection based on the first RSC and the second RSC. Alternatively, the PCF can send the first RSC and the second RSC to the Remote UE and the Relay.

[0645] Alternatively, in S904, the PCF can send the session management subscription data of the Remote UE to the Remote UE and the Relay.

[0646] S911, the Remote UE and the Relay establish the PC5 connection.

[0647] The Remote UE and the Relay can establish the PC5 connection based on the first RSC and / or the second RSC received from the PCF.

[0648] Alternatively, if the Remote UE and the Relay receive the session management subscription data of the Remote UE from the PCF, the Remote UE and the Relay can determine the AMBR of the PC5 link according to the session management subscription data of the Remote UE.

[0649] For example, if the session management subscription data of the Remote UE includes the subscription session AMBR of the Remote UE, the Remote UE and the Relay can determine the subscription session AMBR of the Remote UE as the AMBR of the PC5 link.

[0650] If the session management subscription data of the Remote UE includes the PC5 interface AMBR of the Remote UE, the Remote UE and the Relay can determine the PC5 interface AMBR of the Remote UE as the AMBR of the PC5 link.

[0651] If the session management subscription data of the Remote UE includes the PC5 link AMBR of the Remote UE, the Remote UE and the Relay can determine the PC5 link AMBR of the Remote UE as the AMBR of the PC5 link.

[0652] If the session management subscription data of the Remote UE includes the subscription session AMBR and the PC5 interface AMBR / PC5 link AMBR of the Remote UE, the Remote UE and the Relay can determine the minimum value of the subscription session AMBR and the PC5 interface AMBR / PC5 link AMBR of the Remote UE as the AMBR of the PC5 link.

[0653] S912, the Relay establishes a PDU session.

[0654] The same as S502 in the method 500, which will not be repeated here. Figure 9

[0655] S913, the Relay sends a first message to an SMF (an example of a session management network element).

[0656] In an implementation manner, the first message can include the first RSC and / or the second RSC.

[0657] In another implementation manner, if the Remote UE and the Relay have previously received the session management subscription data of the Remote UE from a PCF, the first message can include the session management subscription data of the Remote UE.

[0658] In order to enable the SMF to provide a QER that is more consistent with the actual available bandwidth of the Remote UE in the process of establishing a PDR, Figure 8 The method flowchart also includes:

[0659] S910, the SMF obtains the session management subscription data of the Remote UE.

[0660] As described above, if the first message includes the first RSC and / or the second RSC, the SMF can obtain the session management subscription data of the Remote UE according to the following manner:

[0661] S921, the SMF obtains the subscription session management data of the Remote UE from a UDM / UDR.​

[0662] The SMF can send a third request message to the UDM (an example of a data management network element) / UDR (an example of a data warehouse network element). This third request message requests session management subscription data for the Remote UE and includes a first RSC and / or a second RSC. As described above, the PCF can send the decision RSC to the UDM / UDR, and the UDM / UDR can associate and save this RSC with the Remote UE's session management subscription data. Therefore, after receiving the third request message from the SMF, the UDM / UDR can retrieve the Remote UE's session management subscription data from its local database based on the first and / or second RSC in the third request message, and send a third response message to the SMF, which includes the Remote UE's session management subscription data.

[0663] S922, the SMF obtains the subscription session management data of the Remote UE from the PCF.

[0664] The SMF can send a fifth request message to the PCF, which requests the session management subscription data of the Remote UE. This fifth request message includes a first RSC and / or a second RSC. As mentioned above, the PCF can associate and save the decided RSC with the Remote UE's session management subscription data. Therefore, after receiving the fifth request message from the SMF, the PCF can retrieve the Remote UE's session management subscription data from its local database based on the first and / or second RSC in the fifth request message, and then send a fifth response message to the SMF, which includes the Remote UE's session management subscription data.

[0665] If the first message includes session management subscription data for the Remote UE, the SMF can obtain the session management subscription data for the Remote UE from the first message.

[0666] S920, SMF generates PDR.

[0667] and Figure 8 The S820 is the same as the one in the series, so I won't go into details here.

[0668] S930, SMF sends PDR to UPF.

[0669] and Figure 9 The S830 is the same as the one in the series, so I won't go into details here.

[0670] Optionally, if in S904, the PCF does not send the session management subscription data of the Remote UE to the Remote UE and the Relay, thenFigure 8 The method shown can further include S940 and S950:

[0671] S940, the SMF sends a fourth message to the Relay, and the fourth message includes the AMBR of the Remote UE.

[0672] The same as S840 in Figure 8 The same as S840 in

[0673] S950, the Remote UE performs PC5 link update with the Relay.

[0674] The same as S850 in Figure 9 The same as S850 in

[0675] Figure 8 The method shown can further include S960: the UPF performs data transmission with the Remote UE through the Relay according to the received PDR.

[0676] The same as S860 in Figures 5-9 The same as S860 in

[0677] In the embodiments of the present application, the PCF can decide the RSC related to the session management subscription data of the Remote UE according to the session management subscription data of the Remote UE, and send the decided RSC and / or the session management subscription data of the Remote UE to the Remote UE and the Relay; further, the SMF can determine the MBR value in the QER in the N4 session according to the RSC and / or the session management subscription data of the Remote UE reported by the Relay. Thus, in the process of the UPF performing the data packet transmission of the Remote UE, the data rate of the Remote UE can be limited according to the MBR of the Remote UE.

[0678] It should be understood that the subject performing the above method embodiments (such as core network elements) can perform part or all of the steps in the examples, and these steps or operations are only examples, and the embodiments of the present application can also include performing other operations or various modifications of the operations.

[0679] It should also be understood that in various embodiments of the present application, the terms and / or descriptions of different embodiments can be consistent and can be mutually referred to if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0680] It should also be understood that the size of the sequence number of each process in the above method embodiments does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0681] The above is described in combination with Figures 10-20 The method for service guarantee provided by the embodiments of the present application is described in detail below in combination with Figure 10 The device for service guarantee provided by the embodiments of the present application is described in detail.

[0682] Referring to Figure 10 , Figure 10 is a schematic diagram of the device 8000 for service guarantee proposed by the present application. As shown in Figures 5-9 , the device 8000 includes a receiving unit 8100, a sending unit 8200, and a processing unit 8300.

[0683] The device 8000 for service guarantee can be used to implement the functions of the relay device involved in any of the above method embodiments. For example, the device 8000 for service guarantee can be a relay device.

[0684] The device 8000 for service guarantee can serve as a relay device and perform the steps performed by the relay device in the above method embodiments. The receiving unit 8100 and / or the sending unit 8200 can be used to support the device 8000 for service guarantee to communicate, for example, to perform the sending and / or receiving actions performed by the relay device in the above method embodiments, and the processing unit 8300 can be used to support the device 8000 for service guarantee to perform the processing actions in the above method embodiments, for example, to perform the processing actions performed by the relay device in the above method embodiments. Figures 5-9 Figure 10

[0685] Optionally, the device 8000 for service guarantee can also include a storage unit (not shown in the figure) for storing the program code and data of the device 8000 for service guarantee. Specifically, reference can be made to the following description: the sending unit 8200 is configured to send a first message to a session management network element, the first message including a first identifier of the remote terminal device; Figures 5-9

[0686] The receiving unit 8100 is configured to receive a second quality of service (QoS) rule from the session management network element, the second QoS rule being generated based on the subscription data of the remote terminal device, and the subscription data of the remote terminal device being obtained based on the first obtaining;

[0687] The processing unit 8300 is configured to perform QoS guarantee on a second communication interface between the relay device and the remote terminal device based on the second QoS rule.

[0688] ​​​The relay device in the apparatus 8000 and the method embodiment corresponds completely, the apparatus 8000 can be the relay device in the method embodiment, or the chip or functional module inside the relay device in the method embodiment. The corresponding units of the apparatus 8000 are used for executing the steps performed by the relay device in the method embodiment. Figures 5-7 The corresponding steps performed by the relay device in the method embodiment are shown.

[0689] Among them, the receiving unit 8100 in the apparatus 8000 performs the steps received by the relay device in the method embodiment. For example, the steps of Figures 8-9 receiving the second QoS Rule sent by the access network device in step S570, or Figures 5-9 receiving the fourth message sent by the session management network element.

[0690] The sending unit 8200 in the apparatus 8000 is used to realize the function of sending messages to other devices. For example, the steps of Figure 11 sending the first message to the session management network element.

[0691] The processing unit 8300 in the apparatus 8000 performs the steps implemented or processed inside the relay device in the method embodiment.

[0692] The receiving unit 8100 and the sending unit 8200 can constitute a transceiver unit, which has the functions of receiving and sending. Among them, the processing unit 8300 can be a processor. The sending unit 8200 can be a transmitter. The receiving unit 8100 can be a receiver. The receiver and the transmitter can be integrated together to form a transceiver.

[0693] Referring to Figure 11 , Figure 2 is a structural schematic diagram of a relay device and a remote terminal device 900 suitable for the embodiments of the present application. The relay device or the remote terminal device 900 can be applied to Figure 11 the system shown. In order to facilitate the description, Figure 11 only the main components of the relay device or the remote terminal device are shown. As Figure 11 shown, the relay device or the remote terminal device includes a processor, a memory, a control circuit, an antenna, and an input and output device. The processor is used to control the antenna and the input and output device to transceive signals, and the memory is used to store a computer program. The processor is used to call and run the computer program from the memory to execute the corresponding processes and / or operations performed by the user equipment in the service guarantee method proposed in the present application. Here, no longer be described.

[0694] Those skilled in the art can understand that, in order to facilitate the description, Figure 12Only one memory and one processor are shown. In an actual relay device, there can be multiple processors and memories. The memory can also be referred to as a storage medium or a storage device, and the like, and the embodiments of the present application do not limit this.

[0695] Referring to Figure 12 , Figure 12 is a schematic diagram of the service assurance apparatus 1000 proposed in the present application. As shown in Figures 5-9 , the apparatus 1000 includes a receiving unit 1010 and a sending unit 1020. The service assurance apparatus 1000 can be used to implement the functions of the session management network element involved in any of the above method embodiments. For example, the service assurance apparatus 1000 can be an SMF. The network element or network function can be a network element in a hardware device, a software function running on a special hardware, or a virtualized function instantiated on a platform (for example, a cloud platform).

[0696] The service assurance apparatus 1000 can serve as a session management network element and perform the steps performed by the session management network element in the above method embodiments. The receiving unit 1010 and / or the sending unit 1020 can be used to support the service assurance apparatus 1000 to communicate, for example, to perform the sending and / or receiving actions performed by the session management network element in the above method embodiments. Figure 12

[0697] Optionally, the service assurance apparatus 1000 can further include a processing unit (not shown in the figure) that can be used to support the service assurance apparatus 1000 to perform the processing actions in the above method embodiments, for example, to perform the processing actions performed by the session management network element in the above method embodiments. Figures 5-9 Figure 12

[0698] Optionally, the service assurance apparatus 1000 can further include a storage unit (not shown in the figure) for storing the program code and data of the service assurance apparatus 1000. Specifically, reference can be made to the following description: Figures 5-9 The receiving unit 1010 is configured to receive a first message from the relay device, the first message including a first identifier of the remote terminal device;

[0699] The sending unit 1020 is configured to send a second message to a policy control network element, the second message including the first identifier of the remote terminal device, wherein the first identifier of the remote terminal device is used to obtain subscription data of the remote terminal device, and the subscription data of the remote terminal device is used to determine a second quality of service (QoS) rule, and the second QoS rule is a QoS rule corresponding to a second communication interface between the relay device and the remote terminal device.

[0700] Alternatively,

[0701] ​​​​

[0702] The receiving unit 1010 is used to acquire the session management subscription data of the remote terminal device, the session management subscription data including the AMBR of the remote terminal device;

[0703] Processing unit 1030 is used to generate a PDR corresponding to the remote terminal device. The PDR includes a QER, and the maximum bandwidth in the QER is determined based on the AMBR of the remote terminal device.

[0704] The sending unit 1020 is used to send the PDR to the user plane network element.

[0705] The device 1000 corresponds completely to the session management network element in the method embodiment. The device 1000 can be the session management network element in the method embodiment, or a chip or functional module within the session management network element in the method embodiment. The corresponding unit of the device 1000 is used to execute... Figure 5 The corresponding steps performed by the session management network element in the method embodiment shown.

[0706] In this embodiment, the receiving unit 1010 in device 1000 performs the step of the session management network element receiving messages sent by other devices in the method embodiment. For example, it performs... Figure 5 Step S510: Receive the first message sent by the relay device. Figure 5 Step S550: Receiving PCC rules sent by the policy control network.

[0707] The transmitting unit 1020 in device 1000 executes the steps of the session management network element transmission in the method embodiment. For example, it executes... Figure 12 Step S520: Sending the second message to the policy control network element.

[0708] The service assurance apparatus shown in apparatus 1000 may also include a processing unit ( Figure 13 (not shown in the text) The processing unit executes the steps implemented or processed within the session management network element in the method embodiment.

[0709] The receiving unit 1010 and the transmitting unit 1020 can form a transceiver unit, which has both receiving and transmitting functions. The processing unit can be a processor. The transmitting unit 1020 can be a transmitter. The receiving unit 1010 can be a receiver. The receiver and transmitter can be integrated together to form a transceiver unit.

[0710] like Figure 12As shown in the illustration, this application embodiment also provides a session management network element 1100, which includes a processor 1110, a memory 1120, and a transceiver 1130. The memory 1120 stores instructions or programs, and the processor 1110 executes the instructions or programs stored in the memory 1120. When the instructions or programs stored in the memory 1120 are executed, the transceiver 1130 executes... Figure 14 The operations performed by the receiving unit 1010 and the transmitting unit 1020 in the illustrated device 1000.

[0711] See Figure 14 , Figure 14 This is a schematic diagram of the service assurance device 1200 proposed in this application. Figure 5 As shown, the device 1200 includes a receiving unit 1210, a processing unit 1220, and a transmitting unit 1230.

[0712] The service assurance device 1200 can be used to implement the functions of the policy control network element involved in any of the above method embodiments. For example, the service assurance device 1200 can be a PCF. The network element or network function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform).

[0713] The service assurance device 1200 can function as a policy control network element and execute the steps performed by the policy control network element in the above method embodiments. The receiving unit 1210 and / or the sending unit 1230 can be used to support communication with the service assurance device 1200, for example, by performing... Figure 5 The transmission and / or reception actions are performed by the policy control network element. The processing unit 1220 can be used by the device 1200 supporting service assurance to perform the processing actions in the above method embodiments, such as executing... Figure 14 The processing actions executed by the policy-controlled network elements.

[0714] Optionally, the business assurance device 1200 may also include a storage unit ( Figure 5 (Not shown in the image), the program code and data of the device 1200 used for storing business assurance. Specifically, please refer to the following description:

[0715] The receiving unit 1210 is used to obtain the first identifier of the remote terminal device, and the first identifier of the remote terminal device is used to obtain the subscription data of the remote terminal device.

[0716] Processing unit 1220 is configured to generate Policy Billing Control (PCC) rules based on the subscription data of the remote terminal device. The PCC rules include first QoS parameters of the first communication interface and second QoS parameters of the second communication interface.

[0717] The sending unit 1230 is used to send the PCC rule to the session management network element.

[0718] The first communication interface is the communication interface between the relay device and the access network device, the second communication interface is the communication interface between the relay device and the remote terminal device, the first QoS parameter is used to generate the first QoS rule corresponding to the first communication interface, and the second QoS parameter is used to generate the second QoS rule corresponding to the second communication interface.

[0719] Alternatively, the device for ensuring service availability can also function as a device for obtaining relay service codes. In this case, the device 1200 for obtaining relay service codes can specifically be used for:

[0720] The receiving unit 1210 is used to acquire the session management subscription data of the remote terminal device, the session management subscription data including the AMBR of the remote terminal device;

[0721] Processing unit 1220 is configured to determine a relay service code based on the subscription data, the relay service code being associated with the session management subscription data;

[0722] The sending unit 1230 is used to send the relay service code to the remote terminal device and the relay device.

[0723] The device 1200 corresponds completely to the policy control network element in the method embodiment. The device 1200 can be the policy control network element in the method embodiment, or a chip or functional module within the policy control network element in the method embodiment. The corresponding unit of the device 1200 is used to execute... Figure 5 The corresponding steps executed by the policy control network element in the method embodiment shown.

[0724] In this embodiment, the receiving unit 1210 in device 1200 performs the steps of receiving the policy control network element in the method embodiment. For example, it performs... Figure 5 Step S520: Receive the second message from the session management network element. Figure 5 Steps S532 and S537 of receiving the policy authorization request message from the application network element are executed. Figure 5 Step S533: Receiving subscription messages from application network elements.

[0725] Processing unit 1220 executes the steps implemented or processed internally by the policy control network element in the method embodiment. For example, it executes... Figure 5 Step S540 in generating PCC rules.

[0726] The transmitting unit 1230 in device 1200 executes the steps of policy control network element transmission in the method embodiment. For example, it executes...Figure 5 Step S550, performing Figure 15 Step S534, sending a notification message to the application network element.

[0727] The receiving unit 1210 and the sending unit 1230 can constitute a transceiver unit, and have both receiving and sending functions. The processing unit 1220 can be a processor. The receiving unit 1210 can be a receiver. The sending unit 1230 can be a transmitter. The receiver and the transmitter can be integrated together to constitute a transceiver.

[0728] As shown in Figure 14 , the present application embodiment further provides a policy control network element 1300, which comprises a processor 1310, a memory 1320 and a transceiver 1330, wherein the memory 1320 stores instructions or programs, and the processor 1310 is configured to execute the instructions or programs stored in the memory 1320. When the instructions or programs stored in the memory 1320 are executed, the transceiver 1330 is configured to perform the operations of the receiving unit 1210 and the sending unit 1230 in the device 1200 shown in Figure 16 .

[0729] Referring to Figure 16 , Figure 16 , Fig. 14 is a schematic diagram of a service assurance device 1400 according to the present application. As shown in Figures 5-7 , the device 1400 comprises a sending unit 1410 and a processing unit 1420.

[0730] The service assurance device 1400 can be used to implement the functions of the application network element involved in any of the above method embodiments. For example, the service assurance device 1400 can be an AF. The network element or network function can be a network element in a hardware device, a software function running on a special hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform).

[0731] The service assurance device 1400 can serve as an application network element and perform the steps performed by the application network element in the above method embodiments. The sending unit 1410 can be used to support the service assurance device 1400 to communicate, for example, to perform the sending actions performed by the application network element in Figures 5-7 . The processing unit 1420 can be used to support the service assurance device 1400 to perform the processing actions in the above method embodiments, for example, to perform the processing actions performed by the application network element in Figure 16 .

[0732] Optionally, the service assurance device 1400 can further comprise a receiving unit (not shown in Figure 16 ) to support the sending actions performed by the service assurance device 1400.

[0733] Optionally, the service assurance apparatus 1400 can further include a storage unit (not shown in the figure) for storing program codes and data of the service assurance apparatus 1400. For details, please refer to the following description: Figures 5-7 The processing unit 1420 is configured to determine a policy authorization request message.

[0734] The sending unit 1410 is configured to send the policy authorization request message to a policy control network element, wherein the policy authorization request message includes a second identifier of a remote terminal device, and the remote terminal device is a terminal device accessing a network through another terminal device.

[0735] The second identifier is used to determine a first identifier of the remote terminal device, the first identifier is used for identifying the remote terminal device, the first identifier is used to obtain subscription data of the remote terminal device, and the subscription data of the remote terminal device is used to determine a second quality of service (QoS) rule, and the second QoS rule is a QoS rule corresponding to a second communication interface between the relay device and the remote terminal device.

[0736] The application network element in the apparatus embodiment and the method embodiment corresponds completely, the apparatus 1400 can be the application network element in the method embodiment, or a chip or a functional module inside the application network element in the method embodiment. The corresponding unit of the apparatus 1400 is used for executing the corresponding steps in the method embodiment shown by the application network element.

[0737] Figure 5 The sending unit 1410 in the apparatus 1400 executes the steps of sending by the application network element in the method embodiment. For example, the steps S532 and S537 of sending the policy authorization request message to the policy control network element in the method embodiment, and the step S533 of sending the subscription message to the policy control network element in the method embodiment.

[0738] The processing unit 1420 executes the steps of implementation or processing inside the application network element in the method embodiment. Figure 5 Figure 16 The processing unit 1420 executes the steps of implementation or processing inside the application network element in the method embodiment.

[0739] The service assurance apparatus shown in the apparatus 1400 can further include a receiving unit (not shown in the figure), and the sending unit executes the steps of receiving by the policy control network element in the method embodiment. For example, the step S534 of receiving the notification message sent by the session management network element in the method embodiment.

[0740] The receiving unit in the apparatus 1400 executes the steps of receiving by the policy control network element in the method embodiment. Figure 5 Figure 17 The receiving unit in the apparatus 1400 executes the steps of receiving by the policy control network element in the method embodiment.

[0741] ​​​The receiving unit and the sending unit 1410 can constitute a transceiver unit, and have the functions of receiving and sending. The processing unit 1420 can be a processor. The sending unit 1410 can be a transmitter. The receiving unit can be a receiver. The receiver and the transmitter can be integrated together to constitute a transceiver.

[0742] As shown in Figure 16 , the embodiment of the present application further provides an application network element 1500, which comprises a processor 1510, a memory 1520 and a transceiver 1530, wherein the memory 1520 stores instructions or programs, and the processor 1530 is used for executing the instructions or programs stored in the memory 1520. When the instructions or programs stored in the memory 1520 are executed, the transceiver 1530 is used for executing the operations of the receiving unit and the sending unit 1410 in the apparatus 1400 as shown in Figure 18 .

[0743] Referring to Figure 18 , Figure 18 , FIG. 16 is a schematic diagram of a service guaranteeing apparatus 1600 provided by the present application. As shown in Figures 5-9 , the apparatus 1600 comprises a receiving unit 1610 and a processing unit 1620.

[0744] The service guaranteeing apparatus 1600 can be used to realize the functions of the remote terminal device in any of the above method embodiments. For example, the service guaranteeing apparatus 1600 can be a remote terminal device.

[0745] The service guaranteeing apparatus 1600 can be used as a remote terminal device, and perform the steps performed by the remote terminal device in the above method embodiments. The receiving unit 1610 can be used to support the service guaranteeing apparatus 1600 to communicate, for example, perform the receiving actions performed by the remote terminal device in the above method embodiments. Figures 5-9 The processing unit 1620 can be used to support the service guaranteeing apparatus 1600 to perform the processing actions in the above method embodiments, for example, perform the processing actions performed by the remote terminal device in the above method embodiments. Figure 18

[0746] Optionally, the service guaranteeing apparatus 1600 can further comprise a sending unit (not shown in the figure) which can be used to support the service guaranteeing apparatus 1600 to perform the sending actions in the above method embodiments, for example, perform the sending actions performed by the remote terminal device in the above method embodiments. Figures 5-9 Figure 18

[0747] Optionally, the service guaranteeing apparatus 1600 can further comprise a storage unit (not shown in the figure) which can be used to support the service guaranteeing apparatus 1600 to perform the storing actions in the above method embodiments, for example, perform the storing actions performed by the remote terminal device in the above method embodiments. Figures 5-9 ​​​(Not shown in the image), the program code and data of the device 1600 used for storing service assurance. Specifically, please refer to the following description: The receiving unit 1610 is used to receive a second Quality of Service (QoS) rule from the relay device, the second QoS rule being generated based on the subscription data of the remote terminal device;

[0748] The processing unit 1620 is used to perform QoS guarantee on the second communication interface between the relay device and the remote terminal device based on the second QoS rule.

[0749] The device 1600 corresponds completely to the remote terminal device in the method embodiment. The device 1600 can be the remote terminal device in the method embodiment, or a chip or functional module within the remote terminal device in the method embodiment. The corresponding unit of the device 1600 is used to execute... Figure 5 The corresponding steps in the method embodiment shown are performed by the remote terminal device.

[0750] In this embodiment, the receiving unit 1610 in device 1600 performs the steps of receiving data from the remote terminal device in the method embodiment. For example, it performs... Figure 19 Step S571 of receiving the second QoS Rule sent by the relay device.

[0751] The processing unit 1620 in the device 1600 executes the steps implemented or processed internally by the remote terminal device in the method embodiment.

[0752] The service assurance apparatus shown in device 1600 may also include a transmission unit ( Figure 19 (Not shown in the image) This device enables the sending of messages to other devices.

[0753] The receiving unit 1610 and the transmitting unit can form a transceiver unit, which has both receiving and transmitting functions. The processing unit 1620 can be a processor. The transmitting unit can be a transmitter. The receiving unit 1610 can be a receiver. The receiver and transmitter can be integrated together to form a transceiver unit.

[0754] See Figure 19 , Figures 8-9 This is a schematic diagram of the service assurance device 1900 proposed in this application. Figures 8-9 As shown, the device 1900 includes a receiving unit 1910 and a processing unit 1920.

[0755] The service assurance device 1900 can be used to implement the functions of user plane network elements in any of the above method embodiments. For example, the service assurance device 1900 can be a UPF.

[0756] The service assurance device 1900 can function as a user plane network element and execute the steps performed by the user plane network element in the above method embodiments. The receiving unit 1910 can be used to support communication with the service assurance device 1900, for example, by performing... Figure 19 The receiving action is performed by the user plane network element. The processing unit 1920 can be used by the device 1900 supporting service assurance to perform the processing actions in the above method embodiments, such as executing... Figure 19 The processing actions performed by the user plane network elements.

[0757] Optionally, the service assurance device 1900 may also include a transmission unit ( Figures 8-9 (Not shown in the image), the transmission action performed by the device 1900 that supports service assurance.

[0758] Optionally, the business assurance device 1900 may also include a storage unit ( Figure 8 (Not shown in the image), the program code and data of the device 1900 used for storing business assurance. For details, please refer to the following description:

[0759] The receiving unit 1910 is used to receive a PDR from a session management network element. The PDR corresponds to the remote terminal device. The PDR includes a QER, and the maximum bandwidth in the QER is determined based on the AMBR of the remote terminal device.

[0760] Processing unit 1920 is used to determine the rate at which data is sent to the remote terminal device based on the maximum bandwidth in the QER.

[0761] The device 1900 corresponds completely to the user plane network element in the method embodiment. The device 1900 can be the user plane network element in the method embodiment, or a chip or functional module within the user plane network element in the method embodiment. The corresponding unit of the device 1900 is used to execute... Figure 19 The corresponding steps performed by the user plane network element in the method embodiment shown.

[0762] In this embodiment, the transmitting unit in device 1900 performs the steps of user plane network element transmission in the method embodiment. For example, it performs... Figure 8 The steps involved in sending data to a remote terminal device via a relay device.

[0763] The processing unit 1920 executes the steps implemented or processed within the user plane network element in the method embodiment.

[0764] The service assurance apparatus shown in device 1900 may also include a receiving unit ( Figure 20 (Not shown in the image), the receiving unit executes the steps of the user plane network element receiving messages sent by other devices in the method embodiment. For example, executing... Figures 5-9 The PDR sent by the session management network element is received in the middle.

[0765] The receiving unit 1910 and the sending unit can constitute a transceiver unit, and have the functions of receiving and sending. The processing unit 1920 can be a processor. The receiving unit 1910 can be a receiver. The sending unit can be a transmitter. The receiver and the transmitter can be integrated together to constitute a transceiver.

[0766] As shown in Figures 5-9 The embodiments of the present application also provide a user plane network element 2000, which comprises a processor 2010, a memory 2020 and a transceiver 2030. The memory 2020 stores instructions or programs. The processor 2010 is configured to execute the instructions or programs stored in the memory 2020. When the instructions or programs stored in the memory 2020 are executed, the transceiver 2030 is configured to perform the operations of the receiving unit and the sending unit in the apparatus 1900 as shown in Figures 5-9 As shown in

[0767] The embodiments of the present application also provide a communication system, which comprises the aforementioned relay device, the remote terminal device, the session management network element, the policy control network element, the user plane network element and the application network element.

[0768] The embodiments of the present application also provide a computer readable storage medium, which stores instructions. When the instructions are run on a computer, the computer performs the steps of the remote terminal device in the method as shown in Figures 5-9 As shown in

[0769] The embodiments of the present application also provide a computer readable storage medium, which stores instructions. When the instructions are run on a computer, the computer performs the steps of the relay device in the method as shown in Figures 5-7 As shown in

[0770] The embodiments of the present application also provide a computer readable storage medium, which stores instructions. When the instructions are run on a computer, the computer performs the steps of the session management network element in the method as shown in Figures 8-9 As shown in

[0771] The embodiments of the present application also provide a computer readable storage medium, which stores instructions. When the instructions are run on a computer, the computer performs the steps of the policy control network element in the method as shown in Figures 5-9 As shown in

[0772] The embodiments of the present application also provide a computer readable storage medium, which stores instructions. When the instructions are run on a computer, the computer performs the steps of the application network element in the method as shown in Figures 5-7The steps performed by the application function in the method shown.

[0773] The application further provides a computer readable storage medium, wherein instructions are stored in the computer readable storage medium, and when the instructions are run on a computer, the computer is caused to perform the above method. Figures 5-9 The steps performed by the user plane network element in the method shown.

[0774] The application further provides a computer program product containing instructions, and when the computer program product is run on a computer, the computer is caused to perform the above method. Figures 5-9 The steps performed by the remote terminal device in the method shown.

[0775] The application further provides a computer program product containing instructions, and when the computer program product is run on a computer, the computer is caused to perform the above method. Figures 5-9 The steps performed by the relay device in the method shown.

[0776] The application further provides a computer program product containing instructions, and when the computer program product is run on a computer, the computer is caused to perform the above method. Figures 8-9 The steps performed by the session management network element in the method shown.

[0777] The application further provides a computer program product containing instructions, and when the computer program product is run on a computer, the computer is caused to perform the above method. ​ The steps performed by the policy control network element in the method shown.

[0778] The application further provides a computer program product containing instructions, and when the computer program product is run on a computer, the computer is caused to perform the above method. ​ The steps performed by the application function in the method shown.

[0779] The application further provides a computer program product containing instructions, and when the computer program product is run on a computer, the computer is caused to perform the above method. ​ The steps performed by the user plane network element in the method shown.

[0780] The application further provides a chip comprising a processor. The processor is configured to read and execute a computer program stored in a memory to perform corresponding operations and / or procedures performed by a remote terminal device in the method for service assurance provided by the application. Optionally, the chip further comprises a memory connected to the processor via a circuit or a wire. The processor is configured to read and execute a computer program stored in the memory. Further optionally, the chip further comprises a communication interface connected to the processor. The communication interface is configured to receive data and / or information to be processed. The processor obtains the data and / or information from the communication interface and processes the data and / or information. The communication interface can be an input / output interface.

[0781] The application further provides a chip comprising a processor. The processor is configured to read and execute a computer program stored in a memory to perform corresponding operations and / or procedures performed by a relay device in the method for service assurance provided by the application. Optionally, the chip further comprises a memory connected to the processor via a circuit or a wire. The processor is configured to read and execute a computer program stored in the memory. Further optionally, the chip further comprises a communication interface connected to the processor. The communication interface is configured to receive data and / or information to be processed. The processor obtains the data and / or information from the communication interface and processes the data and / or information. The communication interface can be an input / output interface.

[0782] The application further provides a chip comprising a processor. The processor is configured to read and execute a computer program stored in a memory to perform corresponding operations and / or procedures performed by a relay device in the method for service assurance provided by the application. Optionally, the chip further comprises a memory connected to the processor via a circuit or a wire. The processor is configured to read and execute a computer program stored in the memory. Further optionally, the chip further comprises a communication interface connected to the processor. The communication interface is configured to receive data and / or information to be processed. The processor obtains the data and / or information from the communication interface and processes the data and / or information. The communication interface can be an input / output interface.

[0783] The application further provides a chip comprising a processor. The processor is configured to invoke and run a computer program stored in a memory to perform corresponding operations and / or procedures performed by a policy control network element in the service assurance method provided by the application. Optionally, the chip further comprises a memory connected to the processor via a circuit or a wire. The processor is configured to read and execute the computer program in the memory. Further optionally, the chip further comprises a communication interface connected to the processor. The communication interface is configured to receive data and / or information to be processed. The processor obtains the data and / or information from the communication interface and processes the data and / or information. The communication interface can be an input / output interface.

[0784] The application further provides a chip comprising a processor. The processor is configured to invoke and run a computer program stored in a memory to perform corresponding operations and / or procedures performed by an application network element in the service assurance method provided by the application. Optionally, the chip further comprises a memory connected to the processor via a circuit or a wire. The processor is configured to read and execute the computer program in the memory. Further optionally, the chip further comprises a communication interface connected to the processor. The communication interface is configured to receive data and / or information to be processed. The processor obtains the data and / or information from the communication interface and processes the data and / or information. The communication interface can be an input / output interface.

[0785] The application further provides a chip comprising a processor. The processor is configured to invoke and run a computer program stored in a memory to perform corresponding operations and / or procedures performed by a user plane network element in the service assurance method provided by the application. Optionally, the chip further comprises a memory connected to the processor via a circuit or a wire. The processor is configured to read and execute the computer program in the memory. Further optionally, the chip further comprises a communication interface connected to the processor. The communication interface is configured to receive data and / or information to be processed. The processor obtains the data and / or information from the communication interface and processes the data and / or information. The communication interface can be an input / output interface.

[0786] Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the application.

[0787] It should be understood that the above-mentioned chip can also be replaced by a chip system, which will not be described here.

[0788] The terms "comprising" and "having" and any variations thereof in the present application are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device that includes a list of steps or units not necessarily limited to those clearly listed, but can include other steps or units not clearly listed or inherent to such processes, methods, products or devices.

[0789] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized in electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solutions. Those of ordinary skill in the art can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0790] Those of ordinary skill in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0791] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be realized by other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0792] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e. can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0793] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0794] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0795] In addition, the term "and / or" in the present application only describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects are an "or" relationship; the term "at least one" in the present application can represent "one" and "two or more", for example, at least one of A, B and C, which can represent the following seven cases: A exists alone, B exists alone, C exists alone, A and B exist together, A and C exist together, C and B exist together, and A, B and C exist together.

[0796] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for ensuring service availability, applied when a remote terminal device accesses a network via a relay terminal device, characterized in that: include: The policy control network element obtains the first identifier of the remote terminal device, and the first identifier is used to obtain the subscription data of the remote terminal device; The policy control network element generates a first quality of service (QoS) parameter in the policy charging control (PCC) rule based on the subscription data of the remote terminal device, and generates a second QoS parameter in the PCC rule based on the subscription data of the relay terminal device. The first QoS parameter is the QoS parameter of the first communication interface, and the second QoS parameter is the QoS parameter of the second communication interface. The policy control network element sends the PCC rule to the session management network element. Wherein, the first communication interface is the communication interface between the relay terminal device and the access network device, the second communication interface is the communication interface between the relay terminal device and the remote terminal device, the first QoS parameter is used to generate the first QoS rule corresponding to the first communication interface, and the second QoS parameter is used to generate the second QoS rule corresponding to the second communication interface.

2. The method according to claim 1, characterized in that, The method further includes: The policy control network element obtains the Internet Protocol IP address information of the remote terminal device; The policy control network element determines flow description information based on the IP address information, and the flow description information is carried in the PCC rule.

3. The method according to claim 1 or 2, characterized in that, The strategy control network element obtains the first identifier by: The policy control network element receives a second message from the session management network element, the second message including the first identifier; or... The policy control network element receives a policy authorization request message from the application network element. The policy authorization request message includes a second identifier of the remote terminal device, wherein the second identifier is used to determine the first identifier.

4. The method according to claim 3, characterized in that, The second identifier includes at least one of the following identifiers: The identifier consists of the remote terminal device's General Public User Identifier (GPSI), the remote terminal device's user identifier assigned by a third party, the remote terminal device's Internet Protocol version 6 (IPv6) address, the remote terminal device's IPv6 address prefix, the relay terminal device's Internet Protocol version 4 (IPv4) address, and the Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) port number.

5. The method according to claim 3, characterized in that, The second message also includes session management subscription data of the remote terminal device, the session management subscription data including the aggregated maximum bit rate (AMBR) of the remote terminal device, and the second QoS parameter including the AMBR that the remote terminal device can use.

6. The method according to claim 3, characterized in that, The policy authorization request message also includes: The service identifier and / or QoS parameter requirements, wherein the service identifier is used to indicate the service type, and the QoS parameter requirements are used to assist the policy control network element in generating the PCC rules.

7. The method according to claim 6, characterized in that, The identifier of the service includes at least one of the following: First relay service code, second relay service code, application identifier (APP ID), and nearby service application name (ProSe APP ID); Wherein, the first relay service code is the relay service code configured for the remote terminal device, and the second relay service code is the relay service code configured for the relay terminal device.

8. The method according to claim 3, characterized in that, Before the policy control network element receives the policy authorization request message from the application network element, the method further includes: The policy control network element receives a subscription message from the application network element, and the subscription message is used to subscribe to whether the remote terminal device is online; The policy control network element sends a notification message to the application network element, and the notification message is used to instruct the remote terminal device to go online.

9. The method according to claim 8, characterized in that, The notification message includes the first identifier and the identifier of the service, wherein the identifier of the service is used to identify the service type.

10. The method according to claim 3, characterized in that, The second message and / or policy authorization request message also includes: First trunk service code and / or second trunk service code, Wherein, the first relay service code is the relay service code configured for the remote terminal device, and the second relay service code is the relay service code configured for the relay terminal device. The policy control network element generates the PCC rules based on the subscription data of the remote terminal device, including: The policy control network element generates the PCC rule based on the subscription data of the remote terminal device and the first relay service code and / or the second relay service code.

11. The method according to claim 10, characterized in that, The method further includes: The policy control network element determines the service type based on the first trunk service code and / or the second trunk service code; or... The policy control network element learns the service type from the 5G Neighborhood Service Name Management (DDNMF) network element based on the first relay service code and / or the second relay service code.

12. The method according to claim 1 or 2, characterized in that, The first identifier includes: The user identifier assigned to the remote terminal device by the General Public User Identifier (GPSI) and / or by a third-party application.

13. A method for business assurance, characterized in that, include: Application network element determines policy authorization request message; The application network element sends a policy authorization request message to the policy control network element. The policy authorization request message includes a second identifier of the remote terminal device, which is a terminal device that accesses the network through a relay terminal device. Wherein, the second identifier is used to determine the first identifier of the remote terminal device, the first identifier is used to obtain the subscription data of the remote terminal device, the subscription data of the remote terminal device is used to determine the second Quality of Service (QoS) rule, the second QoS rule is the QoS rule corresponding to the second communication interface between the relay terminal device and the remote terminal device; the first QoS rule corresponding to the communication interface between the relay terminal device and the access network device is determined based on the subscription data of the relay terminal device.

14. The method according to claim 13, characterized in that, Before the application network element determines the policy authorization request message, the method further includes: The application network element sends a subscription message to the policy control network element, and the subscription message is used to subscribe to whether the remote terminal device is online. The application network element receives a notification message from the policy control network element, the notification message being used to instruct the remote terminal device to go online; or, The application network element obtains information about the policy control network element by querying request messages.

15. The method according to claim 14, characterized in that, The application network element determination policy authorization request message includes: The application network element determines the policy authorization request message based on the first identifier and the service identifier, wherein the service identifier is used to identify the service type. The first identifier and the service identifier are carried in the notification message, or the first identifier and the service identifier are obtained by the application network element through user plane perception.

16. The method according to claim 15, characterized in that, When the first identifier and the service identifier are obtained by the application network element through user plane perception, the method further includes: The application network element senses the online status of the remote terminal device through the user plane.

17. A method for service assurance, applied when a remote terminal device accesses a network through a relay terminal device, characterized in that, include: The session management network element receives a first message from the relay terminal device, the first message including a first identifier of the remote terminal device; The session management network element sends a second message to the policy control network element. The second message includes the first identifier and also includes the identifier of the relay terminal device. Wherein, the first identifier is used to obtain the subscription data of the remote terminal device, the subscription data of the remote terminal device is used to determine the second quality of service (QoS) rule, the second QoS rule is the QoS rule corresponding to the second communication interface between the relay terminal device and the remote terminal device, the identifier of the relay terminal device is used to obtain the subscription data of the relay terminal device, the subscription data of the relay terminal device is used to determine the first quality of service (QoS) rule, the first QoS rule is the QoS rule corresponding to the first communication interface between the relay terminal device and the access network device.

18. The method according to claim 17, characterized in that, The method further includes: The session management network element receives policy charging control (PCC) rules from the policy control network element. The PCC rules include a first QoS parameter of a first communication interface and a second QoS parameter of a second communication interface. The first communication interface is the communication interface between the relay terminal device and the access network device. The session management network element generates a first QoS rule corresponding to the first communication interface based on the first QoS parameter, and generates a second QoS rule based on the second QoS parameter.

19. A method for service assurance, applied when a remote terminal device accesses a network through a relay terminal device, characterized in that, include: The relay terminal device sends a first message to the session management network element, the first message including a first identifier of the remote terminal device; The relay terminal device receives a second Quality of Service (QoS) rule from the session management network element, the second QoS rule being generated based on the subscription data of the remote terminal device corresponding to the first identifier; The relay terminal device provides QoS guarantee for the second communication interface between the relay terminal device and the remote terminal device based on the second QoS rule; The first QoS rule corresponding to the communication interface between the relay terminal device and the access network device is determined based on the subscription data of the relay terminal device.

20. The method according to claim 19, characterized in that, The method further includes: The relay terminal device sends the second QoS rule to the remote terminal device.

21. The method according to claim 19 or 20, characterized in that, The first message also includes: A first relay service code and / or a second relay service code, wherein the first relay service code or the second relay service code is used to determine the second QoS rule; Wherein, the first relay service code is the relay service code configured for the remote terminal device, and the second relay service code is the relay service code configured for the relay terminal device.

22. The method according to claim 21, characterized in that, The first relay service code and / or the second relay service code are associated with the session management subscription data of the remote terminal device.

23. The method according to claim 19 or 20, characterized in that, The method further includes: The relay terminal device receives a fourth message from the session management network element. The fourth message includes session management subscription data of the remote terminal device, and the session management subscription data includes the aggregated maximum bit rate (AMBR) of the remote terminal device. The relay terminal device determines the AMBR of the PC5 link between itself and the remote terminal device based on the AMBR of the remote terminal device.

24. A method for service assurance, applied when a remote terminal device accesses a network through a relay terminal device, characterized in that, include: The remote terminal device receives a second Quality of Service (QoS) rule from the relay terminal device, the second QoS rule being generated based on the subscription data of the remote terminal device. The remote terminal device provides QoS protection for the second communication interface between the relay terminal device and the remote terminal device based on the second QoS rule; The first QoS rule corresponding to the communication interface between the relay terminal device and the access network device is determined based on the subscription data of the relay terminal device.

25. An apparatus for business assurance, characterized in that, Includes units for implementing the method as described in any one of claims 1-12.

26. An apparatus for business assurance, characterized in that, Includes units for implementing the method as described in any one of claims 13-16.

27. An apparatus for business assurance, characterized in that, Includes units for implementing the method as described in claim 17 or 18.

28. A device for ensuring business operations, characterized in that, Includes units for implementing the method as described in any one of claims 19-23.

29. An apparatus for business assurance, characterized in that, Includes units for implementing the method as described in claim 24.

30. A communication device, characterized in that, include: The memory is used to store computer programs; A transceiver, the transceiver being used to perform the sending and receiving steps; A processor, the processor being configured to call and run the computer program from the memory, causing the communication device to perform the method of any one of claims 1-12, or to perform the method of any one of claims 13-16, or to perform the method of claims 17 or 18, or to perform the method of any one of claims 19-23, or to perform the method of claim 24.

31. A computer-readable storage medium, characterized in that, include: The computer-readable medium stores a computer program; when the computer program is run on a computer, it causes the computer to perform the method of any one of claims 1-12, or the method of any one of claims 13-16, or the method of claims 17 or 18, or the method of any one of claims 19-23, or the method of claim 24.

32. A communication system, characterized in that, include: The business assurance apparatus of claim 25, the business assurance apparatus of claim 26, the business assurance apparatus of claim 27, the business assurance apparatus of claim 28, and the business assurance apparatus of claim 29.

Images