WO2021135295A1 - 建立连接和获取中继服务代码的方法和通信装置 - Google Patents

建立连接和获取中继服务代码的方法和通信装置 Download PDF

Info

Publication number
WO2021135295A1
WO2021135295A1 PCT/CN2020/111204 CN2020111204W WO2021135295A1 WO 2021135295 A1 WO2021135295 A1 WO 2021135295A1 CN 2020111204 W CN2020111204 W CN 2020111204W WO 2021135295 A1 WO2021135295 A1 WO 2021135295A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay service
application
service code
terminal device
parameter
Prior art date
Application number
PCT/CN2020/111204
Other languages
English (en)
French (fr)
Inventor
丁辉
张迪
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20908647.9A priority Critical patent/EP4072234A4/en
Publication of WO2021135295A1 publication Critical patent/WO2021135295A1/zh
Priority to US17/851,403 priority patent/US20220330361A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • This application relates to the field of wireless communication, and more specifically, to a method and communication device for establishing a connection and obtaining a relay service code.
  • the remote user equipment (UE) and the relay UE establish a PC5 through a pre-configured relay service code (relay service code). connection.
  • relay service code a pre-configured relay service code
  • the relay UE receives the user routing selection policy (UE routing selection policy, URSP) rule based on the service.
  • the application establishes a protocol data unit (PDU) session, that is, the session parameters selected according to the service or application at this time are the session parameters configured by the operator for the relay UE.
  • PDU protocol data unit
  • the remote UE For the remote UE, it may have opened a corresponding value-added service or subscribed to a value-added package, so that the operator may configure the remote UE with higher priority session parameters. Therefore, the remote UE is matched to the relay UE based on the current pre-configured intermediate service code, which may not be able to provide the service guarantee required by the remote UE.
  • This application provides a method for establishing a connection and obtaining a relay service code. According to the method provided by this application, a relay UE matched by a remote UE can provide the service guarantee required by the remote UE.
  • a method for establishing a connection includes: a first terminal device sends a first broadcast message, the first broadcast message includes a first relay service code, and the first relay service code includes a first relay service code.
  • Parameter information the first parameter is the parameter corresponding to the access to the first application, the first application is the application to be launched by the first terminal device; the first terminal device receives the response message from the second terminal device, the response message It is used to indicate that the second terminal device supports accessing the first application with the first parameter.
  • the first relay service code included in the first broadcast message sent by the remote UE may include the information of the first parameter. Therefore, the relay UE matched by the first broadcast message can access the application to be launched with the session parameters required by the remote UE, that is, the relay UE can provide the service guarantee required by the remote UE.
  • the first parameter includes one or more of the following parameters: data network name (DNN), single-slice selection auxiliary information (single- network slice selection assistance information, S-NSSAI), session and service continuity mode (SSC) mode, PDU session type, access mode priority, non-third generation partnership project (3rd Generation Partnership Project, 3GPP) ) Diversion instructions.
  • DNN data network name
  • S-NSSAI single-slice selection assistance information
  • SSC session and service continuity mode
  • PDU session type PDU session type
  • access mode priority non-third generation partnership project (3rd Generation Partnership Project, 3GPP)
  • the first relay service code is associated with the first application.
  • the first relay service code is associated with a second application
  • the second application is an application for the second terminal device to support a relay service.
  • the method further includes: the first terminal device sends a first policy control (policy control) to a first policy control (policy) through an access and mobility management (AMF) network element.
  • policy control policy control
  • AMF access and mobility management
  • PCF policy control function
  • the network element sends a first request message, the first request message is used to request to obtain the first relay service code; the first terminal device receives the first relay service from the first PCF network element Code.
  • the first request message includes the following information: identification information of the first terminal device, request type, and identifier of the application.
  • the first request message further includes downgrade indication information, and the downgrade indication information is used to indicate whether the first terminal device accepts the service downgrade.
  • a method for establishing a connection includes: a second terminal device receives a first broadcast message, the first broadcast message includes a first relay service code, and the first relay service code includes a first relay service code.
  • Parameter information the first parameter is the parameter corresponding to the access to the first application, the first application is the application to be launched by the first terminal device; the second terminal device sends a response message to the first terminal, and the response message is used Instructing the second terminal device to support access to the first application with the first parameter.
  • the first relay service code included in the first broadcast message sent by the remote UE may include the information of the first parameter. Therefore, the relay UE matched by the first broadcast message can access the application to be launched with the session parameters required by the remote UE, that is, the relay UE can provide the service guarantee required by the remote UE.
  • the first parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • the method before the second terminal device sends a response message to the first terminal device, the method further includes: the second terminal device determines whether to support using the first terminal device. Parameter access to this first application.
  • the first relay service code is associated with the first application
  • the method further includes: the second terminal device determines whether the first relay service code is It is the same as or equivalent to the second relay service code, determines whether to support access to the first application with the first parameter, the second relay service code is associated with the first application or the second application, and the second application is the The second terminal device supports the application of the relay service, and the second relay service code is the relay service code saved by the second terminal device.
  • the first relay service code is associated with a second application
  • the second application is an application for the second terminal device to support the relay service
  • the method further The method includes: the second terminal device determines whether to support access to the first application with the first parameter according to whether the first relay service code is the same as or equivalent to the second relay service code, and the second relay service code is the same as the second relay service code.
  • the second application is associated, and the second relay service code is a relay service code saved by the second terminal device.
  • a method for obtaining a relay service code includes: a first PCF network element receiving a first request message from a first terminal device, the first request message being used to request to obtain a first relay Service code, the first relay service code includes information about a first parameter, the first parameter is a parameter corresponding to accessing a first application, the first application is an application to be launched by the first terminal device; the first PCF network The element decides the relay service code according to the first parameter; the first PCF network element sends the first relay service code to the first terminal device through the AMF network element.
  • the first PCF can allocate the first relay service code including the information of the first parameter to the remote UE according to the request of the remote UE. Further, the relay UE matched by the remote UE according to the first relay service code can provide the relay service required by the remote UE.
  • the first parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • the first relay service code is associated with the first application, and the first PCF network element decides the first relay service according to the first parameter
  • the code includes: the first PCF network element determines the first relay service code according to the first parameter and the following information: the subscription information of the first terminal device, and the identifier of the first application.
  • the first relay service code is associated with the first application, and the first PCF network element decides the relay service code according to the first parameter, Including: the first PCF network element determines the first relay service code according to the first parameter and the following information: subscription information of the first terminal device, identifier of the first application, downgrade indication information, and downgrade indication information It is used to indicate whether the first terminal device accepts service degradation.
  • the first relay service code is associated with a second application
  • the second application is an application for the terminal device to support the relay service
  • the first PCF The network element deciding the first relay service code according to the first parameter includes: the first PCF network element sends a second request message to the second PCF network element, and the second request message is used to request to obtain the second relay service Code, the second relay service code is associated with the second application, the request message includes the first parameter and the identifier of the first application; the first PCF network element receives the second PCF network element The second relay service code; the first PCF network element decides the first relay service code according to the second relay service code.
  • the first PCF can allocate the first relay service code associated with the relay UE to the remote UE, and the relay UE corresponding to the first relay service code can provide the relay required by the remote UE service. Therefore, the relay UE matched by the remote UE according to the first relay service code can meet the requirements of the remote UE.
  • the method further includes: the first PCF network element sends a third request message to the unified data repository (UDR) network element, and the third The request message is used to request to obtain the information of the second PCF; the first PCF network element receives the information of the second PCF from the UDR network element.
  • UDR unified data repository
  • the first request message includes the following information: identification information of the first terminal device, request type, and identifier of the first application.
  • the first request message further includes downgrade indication information, and the downgrade indication information is used to indicate whether the first terminal device accepts the service downgrade.
  • a method for establishing a connection includes: a first terminal device sends a first broadcast message, the first broadcast message includes a third relay service code and a first parameter, and the first parameter is access The parameter corresponding to the first application, the first application is the application to be launched by the first terminal device; the first terminal device receives a response message from the second terminal device, and the response message is used to indicate that the second terminal device supports The first parameter accesses the first application.
  • the first broadcast message sent by the remote UE may include the information of the first parameter. Therefore, the relay UE matched by the first broadcast message can access the application to be launched with the session parameters required by the remote UE, that is, the relay UE can provide the service guarantee required by the remote UE.
  • the first parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, and PDU session type.
  • a method for establishing a connection includes: a second terminal device sends a second broadcast message, the second broadcast message includes a second relay service code, and the second relay service code includes a second relay service code.
  • Parameter information the second parameter is the parameter corresponding to the access to the second application, the second application is the application for the second terminal device to support the relay service; the second terminal device receives the fourth request message from the first terminal device The fourth request message is used to request to establish a PC5 connection with the second terminal device.
  • the second relay service code included in the second broadcast message sent by the relay UE may include the information of the second parameter. Therefore, the relay UE can access the application to be initiated by the remote UE according to the session parameters required by the remote UE matched by the second broadcast message, that is, the relay UE can provide the service guarantee required by the remote UE.
  • the second parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • the second relay service code is associated with the second application.
  • the second relay service code is associated with a first application
  • the first application is an application to be launched by the first terminal device.
  • the method further includes: the second terminal device sends a fifth request message to the second PCF network element through the AMF network element, and the fifth request message is used to request Acquiring the second relay service code; the second terminal device receives the second relay service code from the second PCF network element.
  • the fifth request message includes the following information: identification information of the second terminal device, request type, and identifier of the second application.
  • a method for establishing a connection includes: a first terminal device receives a second broadcast message, the second broadcast message includes a second relay service code, and the second relay service code includes a second relay service code.
  • Parameter information the second parameter is a parameter corresponding to accessing a second application, the second application is an application for which the second terminal device supports a relay service; the first terminal device sends a fourth request message to the second terminal device The fourth request message is used to request to establish a PC5 connection with the second terminal device.
  • the second relay service code included in the second broadcast message sent by the relay UE may include the information of the second parameter. Therefore, the relay UE can access the application to be initiated by the remote UE according to the session parameters required by the remote UE matched by the second broadcast message, that is, the relay UE can provide the service guarantee required by the remote UE.
  • the second parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • the method before the second terminal device sends the fourth request message to the first terminal device, the method further includes: the first terminal device determines that the second terminal device Whether the device supports accessing a first application with a first parameter, the first application is an application to be launched by the first terminal device, and the first parameter is a parameter corresponding to accessing the first application.
  • the second relay service code is associated with the second application
  • the method further includes: the first terminal device determines whether the second relay service code is It is the same or equivalent to the first relay service code to determine whether the second terminal device supports accessing the second application with the first parameter.
  • the first relay service code is the relay service code saved by the first terminal device.
  • the first relay service code is associated with the second application or the first application, the first application is an application to be launched by the first terminal device, and the first parameter is a parameter corresponding to the access to the first application.
  • the second relay service code is associated with a first application
  • the first application is an application to be launched by the first terminal device
  • the method further includes: The first terminal device determines whether the second terminal device supports accessing the first application with the first parameter according to whether the second relay service code is the same or equivalent to the first relay service code, the first relay service code Is a relay service code saved by the first terminal device, the second relay service code is associated with the first application, and the first parameter is a parameter corresponding to accessing the first application.
  • the first parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • a method for obtaining a relay service code includes: a second PCF network element receiving a fifth request message from a second terminal device, the fifth request message being used to request to obtain a second relay Service code, the second relay service code includes information about a second parameter, the second parameter is a parameter corresponding to accessing a second application, and the second application is an application for the second terminal device to support the relay service; the second The PCF network element decides the second relay service code according to the second parameter; the second PCF network element sends the second relay service code to the second terminal device through the AMF network element.
  • the second PCF may allocate the second relay service code including the information of the second parameter to the relay UE according to the request of the relay UE. Further, the relay UE may provide the required relay service for the remote UE matched according to the first relay service code.
  • the second parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • the second relay service code is associated with the second application, and the second PCF network element decides the second relay service according to the second parameter
  • the code includes: the second PCF network element determines the second relay service code according to the second parameter and the following information: the subscription information of the second terminal device, and the identifier of the second application.
  • the second relay service code is associated with the second application, and the second PCF network element decides the second relay service according to the second parameter
  • the code includes: the second PCF network element determines the second relay service code according to the second parameter and the following information: the subscription information of the second terminal device, and the identifier of the second application.
  • the second relay service code is associated with the first application
  • the first application is the application to be launched by the first terminal device
  • the element deciding the second relay service code according to the second parameter includes: the second PCF network element sends a sixth request message to the first PCF network element, and the sixth request message is used to request to obtain the first relay service code ,
  • the first relay service code is associated with the first application
  • the sixth request message includes the second parameter and the identifier of the second application;
  • the second PCF network element receives the information from the first PCF network element The first relay service code;
  • the second PCF network element determines the second relay service code according to the first relay service code.
  • the second PCF can allocate the second relay service code associated with the remote UE to the relay UE, and the relay UE can provide the remote UE corresponding to the second relay service code with its needs Relay service.
  • the method further includes: the second PCF network element sends a seventh request message to the UDR network element, where the seventh request message is used to request to obtain the information of the first PCF. Information; the second PCF network element receives the first PCF information from the UDR network element.
  • the fifth request message includes the following information: identification information of the second terminal device, request type, and identifier of the second application.
  • a method for establishing a connection includes:
  • the second terminal device sends a second broadcast message, the second broadcast message includes a second relay service code and a second parameter, the second parameter is a parameter corresponding to the access to the second application, and the second application is the second terminal device Applications supporting relay services; the second terminal device receives a request message from the first terminal device, and the request message is used to request the establishment of a PC5 connection with the second terminal device.
  • the second broadcast message sent by the relay UE may include the information of the second parameter. Therefore, the relay UE can access the application to be initiated by the remote UE according to the session parameters required by the remote UE matched by the second broadcast message, that is, the relay UE can provide the service guarantee required by the remote UE.
  • the second parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • a communication device in a ninth aspect, includes a transceiving unit: the transceiving unit is configured to send a first broadcast message, the first broadcast message including a first relay service code, and the first relay service code
  • the information includes the first parameter, the first parameter is the parameter corresponding to the access to the first application, and the first application is the application to be launched by the communication device; the transceiver unit is also used to: receive a response message from the second terminal device, The response message is used to indicate that the second terminal device supports accessing the first application with the first parameter.
  • the first parameter includes one or more of the following parameters: DNN, S-NSSAI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • the first relay service code is associated with the first application.
  • the first relay service code is associated with a second application
  • the second application is an application for the second terminal device to support a relay service.
  • the transceiver unit is further configured to: send a first request message to the first PCF network element through the AMF network element, and the first request message is used to request to obtain the first PCF network element.
  • a relay service code the first terminal device receives the first relay service code from the first PCF network element.
  • the first request message includes the following information: identification information of the communication device, request type, and identifier of the first application.
  • the first request message further includes downgrade indication information, and the downgrade indication information is used to indicate whether the communication device accepts service downgrade.
  • a communication device in a tenth aspect, includes a transceiving unit and a processing unit: the transceiving unit is configured to receive a first broadcast message, the first broadcast message including a first relay service code, and the first The subsequent service code includes information about the first parameter, the first parameter is a parameter corresponding to the access to the first application, and the first application is the application to be launched by the first terminal device; the transceiver unit is also used to: Send a response message, where the response message is used to indicate that the communication device supports accessing the first application with the first parameter.
  • the first parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, Non-3GPP offload indication.
  • the processing unit is configured to determine whether to support access to the first application with the first parameter.
  • the first relay service code is associated with the first application
  • the processing unit is further configured to: according to whether the first relay service code is associated with the second application If the relay service code is the same or equivalent, it is determined whether to support access to the first application with the first parameter, the second relay service code is associated with the first application or the second application, and the second application is supported by the communication device
  • the second relay service code is the relay service code saved by the communication device.
  • the first relay service code is associated with a second application
  • the second application is an application for the communication device to support the relay service
  • the processing unit also uses Yu: Determine whether to support access to the first application with the first parameter according to whether the first relay service code is the same or equivalent to the second relay service code, and the second relay service code is associated with the second application
  • the second relay service code is a relay service code saved by the communication device.
  • a communication device in an eleventh aspect, includes a transceiving unit and a processing unit: the transceiving unit is configured to receive a first request message from a first terminal device, and the first request message is used to request acquisition of the first terminal device.
  • a relay service code the first relay service code includes information about a first parameter, the first parameter is a parameter corresponding to accessing a first application, and the first application is an application to be launched by the first terminal device; this processing
  • the unit is configured to determine the relay service code according to the first parameter; the transceiver unit is further configured to: send the first relay service code to the first terminal device through the AMF network element.
  • the first parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority Level, non-3GPP offload indication.
  • the first relay service code is associated with the first application, and the processing unit is specifically configured to: make a decision based on the first parameter and the following information
  • the first relay service code the subscription information of the first terminal device, and the identifier of the first application.
  • the first relay service code is associated with the first application, and the processing unit is specifically configured to: make a decision based on the first parameter and the following information
  • the first relay service code the subscription information of the first terminal device, the identifier of the first application, and downgrade indication information, where the downgrade indication information is used to indicate whether the first terminal device accepts service downgrade.
  • the first relay service code is associated with a second application
  • the second application is an application for the terminal device to support the relay service
  • the transceiver The unit is used to send a second request message to a second PCF network element, the second request message is used to request to obtain a second relay service code, the second relay service code is associated with the second application, and the second The request message includes the first parameter and the identifier of the first application;
  • the transceiving unit is further configured to: receive the second relay service code from the second PCF network element; and the processing unit is configured to: according to the second The relay service code decides the first relay service code.
  • the transceiver unit is further configured to: send a third request message to the UDR network element, and the third request message is used to request information about the second PCF
  • the transceiver unit is also used to: receive information from the second PCF of the UDR network element.
  • the first request message includes the following information: identification information of the first terminal device, request type, and identifier of the first application.
  • the first request message further includes downgrade indication information, and the downgrade indication information is used to indicate whether the first terminal device accepts the service downgrade.
  • a communication device in a twelfth aspect, includes a transceiving unit: the transceiving unit is configured to send a first broadcast message, the first broadcast message including a first relay service code and a first parameter, and the second A parameter is a parameter corresponding to the access to the first application, and the first application is the application to be launched by the communication device; the transceiver unit is also used to: receive a response message from the second terminal device, the response message being used to indicate the second The terminal device supports accessing the first application with the first parameter.
  • the first parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, and PDU session type.
  • a communication device in a thirteenth aspect, includes a transceiving unit: the transceiving unit is configured to send a second broadcast message, the second broadcast message including a second relay service code, and the second relay service
  • the code includes the information of the second parameter, the second parameter is the parameter corresponding to the access to the second application, the second application is the application of the communication device supporting the relay service; the transceiver unit is also used to: receive the information from the first terminal device A fourth request message, which is used to request to establish a PC5 connection with the communication device.
  • the second parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority Level, non-3GPP offload indication.
  • the second relay service code is associated with the second application.
  • the second relay service code is associated with a first application
  • the first application is an application to be launched by the first terminal device.
  • the transceiver unit is further configured to: send a fifth request message to the second PCF network element through the AMF network element, and the fifth request message is used to request acquisition The second relay service code; the transceiver unit is further configured to: receive the second relay service code from the second PCF network element.
  • the fifth request message includes the following information: identification information of the second terminal device, request type, and identifier of the second application.
  • a communication device in a fourteenth aspect, includes a transceiving unit and a processing unit: the transceiving unit is configured to: receive a second broadcast message, the second broadcast message including a second relay service code, and the second The relay service code includes information about a second parameter, the second parameter is a parameter corresponding to the access to the second application, and the second application is an application for the second terminal device to support the relay service; the transceiver unit sends to the second terminal device A fourth request message, which is used to request to establish a PC5 connection with the second terminal device.
  • the second parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority Level, non-3GPP offload indication.
  • the processing unit before the transceiver unit sends the fourth request message to the second terminal device, the processing unit is configured to: determine whether the second terminal device supports The first parameter accesses a first application, the first application is an application to be launched by the communication device, and the first parameter is a parameter corresponding to accessing the first application.
  • the second relay service code is associated with the second application
  • the processing unit is further configured to: according to whether the second relay service code is associated with The first relay service code is the same or the same, and it is determined whether the second terminal device supports access to the second application with the first parameter.
  • the first relay service code is the relay service code stored by the communication device. After the service code is associated with the second application or the first application, the first application is an application to be launched by the communication device, and the first parameter is a parameter corresponding to the access to the first application.
  • the second relay service code is associated with a first application
  • the first application is an application to be launched by the communication device
  • the processing unit also uses Yu: According to whether the second relay service code is the same or equivalent to the first relay service code, it is determined whether the second terminal device supports accessing the first application with the first parameter, and the first relay service code is the communication A relay service code saved by the device, the second relay service code is associated with the first application, and the first parameter is a parameter corresponding to accessing the first application.
  • the first parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority Level, non-3GPP offload indication.
  • a communication device in a fifteenth aspect, includes a transceiving unit and a processing unit: the transceiving unit is configured to receive a fifth request message from a second terminal device, and the fifth request message is used to request to obtain the second terminal device.
  • a relay service code where the second relay service code includes information about a second parameter, the second parameter is a parameter corresponding to accessing a second application, and the second application is an application for the second terminal device to support the relay service;
  • the processing unit is configured to: decide the second relay service code according to the second parameter; the transceiver unit is further configured to: send the second relay service code to the second terminal device through an AMF network element.
  • the second parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority Level, non-3GPP offload indication.
  • the second relay service code is associated with the second application, and the processing unit is specifically configured to: make a decision based on the second parameter and the following information
  • the second relay service code the subscription information of the second terminal device, and the identifier of the second application.
  • the second relay service code is associated with the second application, and the processing unit is specifically configured to: make a decision based on the second parameter and the following information
  • the second relay service code the subscription information of the second terminal device, and the identifier of the second application.
  • the second relay service code is associated with a first application, the first application being an application to be launched by the first terminal device, and the transceiver unit Used to: send a sixth request message to the first PCF network element, where the sixth request message is used to request to obtain a first relay service code, the first relay service code is associated with the first application, and the sixth request
  • the message includes the second parameter and the identifier of the second application; the transceiver unit is further configured to: receive the first relay service code from the first PCF network element; and the processing unit is configured to: The second relay service code is decided after the service code.
  • the transceiver unit is further configured to: send a seventh request message to the UDR network element, where the seventh request message is used to request information about the first PCF;
  • the transceiving unit is further configured to receive the information of the first PCF from the UDR network element.
  • the fifth request message includes the following information: identification information of the second terminal device, request type, and identifier of the second application.
  • a communication device in a sixteenth aspect, includes a transceiving unit: the transceiving unit is configured to: send a second broadcast message, the second broadcast message including a second relay service code and a second parameter, the first The second parameter is the parameter corresponding to the access to the second application, the second application is the application for the communication device to support the relay service; the communication device is also used to: receive a request message from the first terminal device, the request message is used to request communication with The communication device establishes a PC5 connection.
  • the second parameter includes one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority Level, non-3GPP offload indication.
  • a communication device including a processor.
  • the processor is coupled with the memory, and can be used to execute instructions or data in the memory to implement the first aspect and any one of the possible implementation manners of the first aspect, the fourth aspect and any one of the possible implementation manners of the fourth aspect, The sixth aspect and the method in any one of the possible implementation manners of the sixth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is a first terminal device.
  • the communication interface may be a transceiver or an input/output interface.
  • the communication device is a chip or a chip system configured in the first terminal device.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a communication device including a processor.
  • the processor is coupled with the memory, and can be used to execute instructions or data in the memory to implement any one of the above-mentioned second aspect and the possible implementation manner of the second aspect, the fifth aspect and any one of the possible implementation manners of the fifth aspect, The eighth aspect and the method in any one of the possible implementation manners of the eighth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is a second terminal device.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip or a chip system configured in the second terminal device.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a communication device including a processor.
  • the processor is coupled with the memory and can be used to execute instructions or data in the memory to implement the third aspect and the method in any one of the possible implementation manners of the third aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is the first PCF network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip or a chip system configured in the first PCF network element.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a communication device including a processor.
  • the processor is coupled with the memory and can be used to execute instructions or data in the memory to implement the seventh aspect and the method in any one of the possible implementation manners of the seventh aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is a second PCF network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip or a chip system configured in the second PCF network element.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and send a signal through the output circuit, so that the processor executes any one of the first aspect to the eighth aspect and the first aspect to the eighth aspect. The method in the way.
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits, etc.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • the signal output by the output circuit may be, for example, but not limited to, output to the transmitter and transmitted by the transmitter
  • the circuit can be the same circuit, which is used as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, receive signals through a receiver, and transmit signals through a transmitter, so as to implement any one of the first to eighth aspects and any one of the possible implementation manners of the first to eighth aspects In the method.
  • the processor is one or more
  • the memory is one or more
  • the memory may be integrated with the processor, or the memory and the processor may be provided separately.
  • the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.
  • ROM read only memory
  • sending instruction information may be a process of outputting instruction information from the processor
  • receiving capability information may be a process of receiving input capability information by the processor.
  • the data output by the processor can be output to the transmitter, and the input data received by the processor can come from the receiver.
  • the transmitter and receiver can be collectively referred to as a transceiver.
  • the processing device in the foregoing twenty-second aspect may be one or more chips, or may also be a chip system.
  • the processor in the processing device can be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory, and the memory may Integrated in the processor, may be located outside the processor, and exist independently.
  • a computer program product includes: a computer program (also called code, or instruction), which when the computer program is executed, causes the execution of the first aspect to The eighth aspect and the method in any one of the possible implementation manners of the first to eighth aspects.
  • a computer program also called code, or instruction
  • a computer-readable storage medium stores a computer program (also called code, or instruction) when it runs on a computer, so that the computer executes the above-mentioned first
  • a computer program also called code, or instruction
  • a communication system including: the aforementioned first terminal device, the second terminal device, and/or the aforementioned first PCF network element, and/or, the aforementioned second PCF network element .
  • FIG. 1 is a schematic diagram of an application scenario applicable to the method provided in the embodiment of the present application.
  • Fig. 2 is a schematic flowchart of a method for establishing a connection provided by an embodiment of the present application.
  • Fig. 3 is a schematic flowchart of a method for obtaining a relay service code provided by an embodiment of the present application.
  • Fig. 4 is a schematic flowchart of a method for establishing a connection provided by an embodiment of the present application.
  • Fig. 5 is a schematic flowchart of a method for obtaining a relay service code provided by an embodiment of the present application.
  • 6 to 9 are schematic flowcharts of methods for establishing a connection provided by embodiments of the present application.
  • FIG. 10 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • 5G 5th Generation
  • NR New Radio
  • the embodiments of the present application do not specifically limit the specific structure of the execution subject of the methods provided in the embodiments of the present application, as long as the program that records the codes of the methods provided in the embodiments of the present application can be executed according to the embodiments of the present application.
  • the provided method can be used for communication.
  • the execution subject of the method provided in the embodiments of the present application may be a terminal or a network-side device, or a functional module in a user device or a network-side device that can call and execute the program.
  • FIG. 1 is a schematic diagram of a network architecture applicable to the method provided in the embodiment of the present application. As shown in the figure, the network architecture may specifically include the following network elements:
  • User equipment it can be called terminal equipment, terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, wireless communication equipment, User agent or user device.
  • the terminal device can also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), and wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • UE#A and UE#B are shown in the figure. Among them, UE#B is connected to the next generation radio access network (NG-RAN) through the Uu interface, and then UE#B is connected to the 5G core network (5G core network, 5GC) through NG-RAN . UE#A is connected to UE#B through the PC5 interface.
  • NG-RAN next generation radio access network
  • 5G core network 5G core network
  • Access network Provides network access functions for authorized users in a specific area, and can use transmission tunnels of different quality according to user levels and service requirements.
  • the access network may be an access network using different access technologies.
  • 3GPP access technologies There are two types of current wireless access technologies: 3GPP access technologies and non-third-generation partnership project (non-3GPP) access technologies.
  • 3GPP access technologies such as the radio access network technology used in the 3rd generation (3G) system, the radio access network technology used in the 4G system, or the NG-RAN technology in Figure 1 (such as 5G) The wireless access technology used in the system).
  • 3GPP access technology refers to an access technology that complies with 3GPP standard specifications, and an access network that adopts 3GPP access technology is called a radio access network (RAN). Among them, the access network equipment in the 5G system is called the next generation Node Base station (gNB).
  • gNB next generation Node Base station
  • a non-3GPP access technology refers to an access technology that does not comply with the 3GPP standard specifications, for example, an air interface technology represented by an access point (AP) in wifi.
  • An access network that implements access network functions based on wireless communication technology may be called a radio access network (RAN).
  • the wireless access network can manage wireless resources, provide access services for the terminal, and then complete the forwarding of control signals and user data between the terminal and the core network.
  • the radio access network can be, for example, a base station (NodeB), an evolved NodeB (eNB or eNodeB), a base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an AP in a WiFi system, etc., It can also be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or the access network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, and a network in the future 5G network Equipment or network equipment in the future evolved PLMN network, etc.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the radio access network device.
  • Access and mobility management function (AMF) entities mainly used for mobility management and access management, etc., and can be used to implement mobility management entity (mobility management entity, MME) functions in addition to sessions Functions other than management, such as lawful interception, or access authorization (or authentication) functions. In the embodiment of this application, it can be used to realize the functions of access and mobility management of network elements.
  • MME mobility management entity
  • Session management function (SMF) entity mainly used for session management, UE's Internet Protocol (IP) address allocation and management, selection of manageable user plane functions, policy control, or charging function interfaces End point and downlink data notification, etc. In the embodiment of this application, it can be used to realize the function of the session management network element.
  • IP Internet Protocol
  • User Plane Function (UPF) entity that is, the data plane gateway. It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc.
  • User data can be connected to the data network (DN) through this network element. In the embodiment of the present application, it can be used to realize the function of the user plane gateway.
  • DN data network
  • Data network A network used to provide data transmission.
  • the network of the operator's business the Internet network, the business network of a third party, and so on.
  • Figure 1 shows an application server deployed by a third party.
  • Network exposure function (NEF) entity used to safely open services and capabilities provided by 3GPP network functions to the outside world.
  • PCF Policy control function
  • Unified data management (UDM) entity used for unified data management, 5G user data management, processing user identification, access authentication, registration, or mobility management, etc.
  • Application function (AF) entity used to route data affected by applications, access network open function network elements, or interact with policy frameworks for policy control, etc.
  • the AF can be a third-party functional entity or an application service deployed by an operator, such as an IP multimedia subsystem (IMS) voice call service.
  • IMS IP multimedia subsystem
  • the application function entity of a third-party application it can also be authorized by the NEF entity when interacting with the core network.
  • the third-party application function directly sends a request message to the NEF entity, and the NEF entity determines whether the AF entity is allowed to send the request. If the verification succeeds, the request message will be forwarded to the corresponding PCF entity or UDM entity.
  • Unified data repository (UDR) entity used to access contract data, policy data, application data and other types of data.
  • the N6 interface is the reference point between the UPF entity and the DN, and is used to transmit user plane data.
  • the above-mentioned network architecture applied to the embodiment of the present application is only an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture, and the network architecture applicable to the embodiment of the present 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 the present application.
  • AMF entity, SMF entity, UPF entity, NEF entity, PCF entity, UDM entity, AF entity, and UDR entity shown in FIG. 1 can be understood as network elements used to implement different functions in the core network, for example, Combine into network slices as needed.
  • These core network elements may be independent devices, or they may be integrated in the same device to implement different functions, which is not limited in this application.
  • the entity used to implement AMF is referred to as the access and mobility management network element
  • the entity used to implement SMF is referred to as the session management network element
  • the entity used to implement UPF is referred to as the user plane gateway.
  • the entity used to implement the UDR function is recorded as a unified data warehouse network element
  • the entity used to implement the PCF is recorded as a policy control network element.
  • the name of the interface between the various network elements in FIG. 1 is only an example, and the name of the interface in a specific implementation may be other names, which is not specifically limited in this application.
  • the name of the message (or signaling) transmitted between the various network elements described above is only an example, and does not constitute any limitation on the function of the message itself.
  • the UE can establish a PDU session based on certain URSP rules.
  • the URSP rules are only supported by the home-policy control function (H-PCF) entity.
  • the URSP rules are mainly used for the UE to decide how to select the routing strategy for the service data flow to be transmitted, for example, the service data flow to be transmitted Whether the service data stream supports offloading to non-3GPP access, or selects specific DNN, S-NSSAI, SSC mode, PDU session type and other information for the service data stream to be transmitted.
  • the structure of URSP is mainly composed of two parts: traffic descriptor, which defines the characteristics that can be used for traffic identification in URSP; and list of route selection descriptor.
  • the UE When the UE determines that a specific service/application needs to be initiated, it will match the service/application to be initiated with the traffic descriptor in the URSP rule received by the UE according to the priority of the URSP rule. If it matches the specific URSP Rule (the matched URSP rule may be the default rule, that is, the traffic descriptor in the URSP rule matches all services/applications), the UE continues to determine whether an existing PDU session conforms to the matched URSP rule The definition of the routing descriptor.
  • the UE can Choose to initiate a PDU session modification request based on an existing PDU session.
  • the PDU session modification request message can carry the following parameters: PDU session identifier, N1 interface session management container (N1 SM Container).
  • N1 SM Container N1 interface session management container
  • the PDU session identifier is used to associate the access and mobility management network element with the specific session context
  • the N1 SM Container is transparently transmitted from the access and mobility management network element to the session management network element.
  • N1 SM Container includes a PDU session modification request
  • the PDU session modification request includes: PDU session identifier, packet filter, operation, and requested service of quality (QoS).
  • the PDU session establishment request message can carry the following parameters: newly allocated PDU session identifier, DNN, S-NASSI, N1 SM Container.
  • the newly allocated PDU session identifier is used to identify the PDU session corresponding to the PDU session establishment request
  • DNN and S-NASSI are used as parameters for the access and mobility management network element to select the session management network element for the PDU session establishment request.
  • N1 SM Container is transparently transmitted from the access and mobility management network element to the selected session management network element.
  • N1 SM Container includes SSC mode and PDU session type.
  • the UE when the UE is in a marginal area where the operator’s network coverage is weak, or is outside the operator’s network coverage, if the UE needs to initiate a specific service or application, it can communicate with the neighboring The UE establishes a PC5 connection, thereby indirectly accessing the 5G network. For example, when UE#A shown in FIG. 1 needs to initiate a specific service or application, it can connect to the 5GC by establishing a PC5 connection with UE#B.
  • the UE that uses the relay service will be denoted as a remote UE
  • the UE that will provide the relay service for the remote UE will be denoted as a relay UE.
  • UE#A shown in FIG. 1 corresponds to a remote UE
  • UE#B corresponds to a relay UE.
  • the relay UE sends a broadcast message on the corresponding frequency band according to the frequency point information received from the policy control network element.
  • the broadcast message may include: (a) Relay UE identifier: link layer identifier (link layer identifier) ; (B) Relay UE information: can include the layer 2 identification of the relay UE or application layer user information; (c) Relay service code: can include business information, security policy, and optionally, authorization permission List of connected UEs. Among them, the relay service code is locally pre-configured by the relay UE.
  • the remote UE monitors the broadcast message in the corresponding frequency band according to the frequency information received from the policy control network element. Further, the remote UE parses the relay service code in the monitored broadcast information, and if the monitored relay service code can correspond to the relay service code pre-configured locally by the remote UE, the remote UE can determine The relay UE can provide relay services for applications or services that the remote UE needs to initiate. Furthermore, the remote UE initiates a PC5 establishment request to the relay UE, thereby establishing a PC5 connection with the relay UE.
  • the remote UE sends a broadcast message on the corresponding frequency band according to the frequency point information received from the policy control network element.
  • the broadcast message may include: (a) Information of the remote UE: may include the link layer identifier of the remote UE or Application layer user information; (b) Relay service code: It can include business information and security policies. Among them, the relay service code is locally pre-configured by the remote UE. If the remote UE can obtain the identifier of the relay UE in advance, the broadcast information may also include the identifier of the relay UE.
  • the relay UE monitors the broadcast message in the corresponding frequency band according to the frequency information received from the policy control network element. Further, the relay UE analyzes the relay service code in the monitored broadcast message, and if the monitored relay service code can correspond to the relay service code pre-configured locally by the relay UE, the relay UE can determine It can provide the remote UE with the relay service of the application or business that the remote UE needs to initiate.
  • the relay UE sends a response message to the remote UE, and the response message may include: (a) the identifier of the relay UE: a link layer identifier; (b) the information of the remote UE.
  • the remote UE initiates a PC5 establishment request to the relay UE, thereby establishing a PC5 connection with the relay UE.
  • the locally pre-configured relay service code of the remote UE corresponds to the relay service code locally configured by the relay UE. It can be understood that the relay service code locally configured by the remote UE corresponds to the relay service code locally configured by the relay UE.
  • the code is the same or equivalent, or the peer-to-peer information can be obtained through a specific encryption/decryption algorithm.
  • the relay service code of the remote UE and the relay service code of the relay UE correspond to the same application identifier (application identifier).
  • the relay service codes stored in the remote UE and the relay UE are pre-configured, and the relay service codes Directly related to public safety business.
  • the relay service is no longer limited to public safety scenarios. If the pre-configured relay service code continues to be used, the relay service may not be able to reflect the actual application and does not have the flexibility of dynamic adjustment. Sex.
  • the relay UE when the current remote UE initiates a service or application through the relay UE, the relay UE establishes a PDU session for the service or application based on the URSP rules it receives, that is, the service or application is selected at this time
  • the information such as DNN, S-NASSI, SSC mode, PDU session type and so on are the parameters configured by the operator for the relay UE.
  • the remote UE it may have opened the corresponding value-added service or subscribed to the value-added package, so that the operator can configure the remote UE with higher priority DNN, S-NASSI, SSC mode, PDU Information such as session type. If the remote UE matches the relay UE based on the method described above, the matched relay UE may not be able to provide the service guarantee required by the remote UE.
  • an embodiment of the present application provides a method for establishing a connection, which can enable a remote UE to be matched to a relay UE that supports access to a specific application service in a manner required by the remote UE.
  • AMF can correspond to access and mobility management network elements
  • UDR can correspond to unified data warehouse network elements
  • PCF can correspond to policy management network elements.
  • the name of each network element is only defined for distinguishing different functions, and should not constitute any limitation in this application. This application does not exclude the possibility of defining other network elements to achieve the same or similar functions.
  • the first relay service code mentioned in the embodiment of this application corresponds to the relay service code saved by UE#A (remote UE).
  • the specific content of the first relay service code may be multiple, for example, the first relay service code (corresponding to the relay service code #1 below) may be associated with the application to be launched by UE#A, and The information of the first parameter is not included; or, the first relay service code (corresponding to the relay service code #2 below) may be related to the application to be launched by UE#A or the application that UE#B supports the relay service And includes the information of the first parameter; or, the first relay service code (corresponding to the relay service code #3 below) may be associated with the application that UE#B supports the relay service, and does not include Information about the first parameter.
  • the first parameter here may be one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, non-3GPP offload indication.
  • the second relay service code mentioned in the embodiment of this application corresponds to the relay service code saved by UE#B (relay UE).
  • the specific content of the second relay service code can be multiple, for example, the second relay service code (corresponding to the relay service code #4 below) can be associated with the application that UE#B supports the relay service.
  • the second relay service code (corresponding to the relay service code #5 in the following) may be the same as the application to be launched by UE#A or UE#B supporting relay service
  • the application is associated and includes the information of the second parameter; or, the second relay service code (corresponding to the relay service code #6 below) may be associated with the application to be launched by UE#A, and does not include Information about the second parameter.
  • the second parameter here may be one or more of the following parameters: DNN, S-NASSI, SSC mode, PDU session type, access mode priority, non-3GPP offload indication.
  • Fig. 2 shows a schematic flowchart of a method for establishing a connection provided by an embodiment of the present application.
  • the method shown in FIG. 2 may be executed by UE#A and UE#B in the system shown in FIG. 1, where UE#A corresponds to the first terminal device, and UE#B corresponds to the second terminal device.
  • the method for establishing a connection between UE#A and UE#B described in the method 200 corresponds to mode B, that is, the remote UE sends a broadcast message.
  • the method includes S210 and S220. Each step is described in detail below.
  • UE#A may send the first broadcast message on the corresponding frequency band according to the frequency information received from the policy control network element serving the UE#A.
  • UE#B may receive the first broadcast message on the corresponding frequency band according to the frequency information received from the policy control network element serving the UE#B.
  • the first broadcast message is used to discover UE#B that can provide a relay service for UE#A.
  • the embodiment of the present application does not limit the specific content of the first broadcast message.
  • the first broadcast message may include the following information: information of UE#A, relay service code #1 (an example of the first relay service code), and first parameters.
  • the information of UE#A is used to identify the UE#A, and the information of UE#A may include the link layer identification of UE#A or the application layer user information of UE#A.
  • the relay service code #1 is associated with the first application.
  • the first application is the application to be launched by UE#A.
  • the relay service code #1 may include the information of the application to be launched by UE#A.
  • the The relay service code #1 may also include the relay service security policy of UE#A.
  • the relay service code #1 may be locally pre-configured by UE#A, or it may be obtained by UE#A from the policy control network element that it serves, which is not limited in the embodiment of the present application.
  • the method for UE#A to obtain the relay service code #1 from the policy control network element serving it will be described later in conjunction with other embodiments. For the sake of brevity, it will not be described in detail here.
  • the first parameter is a parameter corresponding to the access to the first application, that is, the first parameter is a parameter that UE#A needs to use to access the first application, or is a parameter that is allowed by UE#A to access the first application. That is, the first parameter is a parameter in the routing description information in the URSP rule configured by the operator for the application to be launched by UE#A.
  • the first parameter may be one or more of the parameters in the routing description information: DNN, S-NAASI, SSC mode, PDU session type, access mode priority, non-3GPP offload indication, etc.
  • the first parameter may be obtained by UE#A from the policy control network element serving it.
  • the first broadcast message may include the following information: information of UE#A, relay service code #2 (an example of the first relay service code).
  • the information of UE#A is used to identify the UE#A, and the information of UE#A may include the link layer identification of UE#A or the application layer user information of UE#A.
  • the relay service code #2 includes the information of the first parameter.
  • the information that the relay service code #2 includes the first parameter can be understood as the relay service code #2 includes the code corresponding to the first parameter, or the relay service code #2 includes the first parameter.
  • the first parameter can be parsed from the relay service code #2.
  • the embodiment of this application does not limit the specific form of the relay service code #2.
  • the relay service code #2 is associated with the first application, and it can also be understood that the relay service code #2 is associated with UE#A.
  • the relay service code #2 may also include the information of the first application.
  • the relay service code #2 may also include the relay service security policy of UE#A.
  • the relay service code #2 is associated with a second application, and the second application is an application for UE#B to support relay services. It can also be understood that the relay service code #2 is related to UE#B. United. In this case, the relay service code #2 may include the information of the second application. Optionally, the relay service code #2 may also include the relay service security policy of UE#B.
  • the relay service code #2 may be obtained by UE#A from the policy control network element serving it.
  • the method for UE#A to obtain the relay service code #2 from the policy control network element serving it will be described in detail later in conjunction with other embodiments. For the sake of brevity, it will not be described in detail here.
  • the first broadcast message may include the following information: information of UE#A, relay service code #3 (an example of the first relay service code).
  • the information of UE#A is used to identify the UE#A, and the information of UE#A may include the link layer identification of UE#A or the application layer user information of UE#A.
  • the relay service code #3 is associated with the second application, and it can also be understood that the relay service code #3 is associated with UE#B. And the UE#B corresponding to the relay service code #3 can provide the relay service for UE#A. In other words, the relay service code #3 is an available relay service code.
  • the relay service code #3 may include the information of the second application.
  • the relay service code #3 may also include the relay service security policy of UE#B.
  • the relay service code #3 may be obtained by UE#A from the policy control network element serving it.
  • the method for UE#A to obtain the relay service code #3 from the policy control network element serving it will be described in detail later in conjunction with other embodiments. For the sake of brevity, it will not be described in detail here.
  • the first broadcast message may include the following information: information of UE#A, relay service code #1 (an example of the first relay service code).
  • the information of UE#A is used to identify the UE#A, and the information of UE#A may include the link layer identification of UE#A or the application layer user information of UE#A.
  • the relay service code #1 is associated with the first application.
  • the first application is the application to be launched by UE#A.
  • the relay service code #1 may include the information of the application to be launched by UE#A.
  • the The relay service code #1 may also include the relay service security policy of UE#A.
  • the relay service code #1 may be locally pre-configured by UE#A, or it may be obtained by UE#A from the policy control network element that it serves, which is not limited in the embodiment of the present application.
  • the method for UE#A to obtain the relay service code #1 from the policy control network element serving it will be described later in conjunction with other embodiments. For the sake of brevity, it will not be described in detail here.
  • the response message is used to indicate that UE#B supports accessing the first application with the first parameter.
  • the response message may include the identifier of UE#B and the information of UE#A. Wherein, the identifier of UE#B is used to identify UE#B, and the identifier of UE#B may include the link layer identifier of UE#B.
  • the first broadcast message sent by UE#A may include different contents.
  • the first broadcast message sent by UE#A includes the following information: information of UE#A, relay service code #1 (an example of the first relay service code), and first parameters.
  • UE#B after UE#B receives the first broadcast message sent by UE#A, it first parses the relay service code #1 in the first broadcast message to determine whether it can provide UE#A to be initiated. Application relay service.
  • UE#B When UE#B analyzes the relay service code #1 in the first broadcast message, it can be understood that UE#B judges the relay service code #1 in the broadcast message and the relay service code #4 configured by UE#B. (An example of the second relay service code) Is it the same, or, is it the same, or, whether the relay service code #1 and the relay service code #4 are subjected to a specific encryption/decryption algorithm to obtain peer-to-peer information . For example, whether UE#B performs a specific decryption algorithm on relay service code #1 and relay service code #4 to obtain the same application identifier.
  • the relay service code #4 configured by UE#B can also be a filter for the target relay service code.
  • UE#B can determine whether the relay service code #1 meets the filter requirements. , That is, whether UE#B can support the provision of the relay service of the application to be initiated by UE#A for the UE#A corresponding to the relay service code #1.
  • the relay service code #4 is associated with the second application, and can also be understood as the relay service code #4 is associated with UE#B.
  • Relay service code #4 is the relay service code saved by UE#B. It can be pre-configured locally by UE#B, or it can be obtained by UE#B from the policy control network element that it serves. This is not limited.
  • the method for UE#B to obtain the relay service code #4 from the policy control network element it serves can refer to the method for UE#A to obtain the relay service code #1. For brevity, details are not described in the embodiment of this application.
  • UE#B determines that relay service code #1 is the same as relay service code #4, or is equivalent, or performs a specific encryption/decryption algorithm to obtain peer-to-peer information, UE#B continues to determine whether it supports the first Parameter access to the first application.
  • UE#B determines that it supports access to the first application with the first parameter, UE#B determines that it can provide the relay service of the first application. Then, UE#B can reply with a response message to UE#A.
  • UE#B may determine whether it supports accessing the first application with the first parameter according to whether the first parameter is consistent or equivalent to the second parameter.
  • the second parameter is a parameter for accessing the second application. If the first parameter is consistent or equivalent to the second parameter, UE#B determines that it supports accessing the first application with the first parameter.
  • UE#B may determine that it can provide the first application with at least one parameter in the first parameter.
  • Relay service For example, if the first parameter includes DNN and S-NAASI, UE#B determines that it can provide the relay service of the first application when it determines that it can access the first application with the DNN in the first parameter; Or UE#B determines that it can use the S-NAASI in the first parameter to access the first application, and determines that it can provide the relay service of the first application; or UE#B determines that it can use the S-NAASI in the first parameter to access the first application. When the DNN and S-NAASI visit the first application, it is determined that they can provide the relay service of the first application.
  • the first broadcast message sent by UE#A includes the following information: information of UE#A, relay service code #2 (an example of the first relay service code).
  • UE#B after UE#B receives the first broadcast message sent by UE#A, it can parse the relay service code #2 in the first broadcast message to determine whether it can provide the relay of the first application. service.
  • UE#B's analysis of the relay service code #2 in the first broadcast message can be understood to mean that UE#B judges the relay Whether service code #2 is the same as or equivalent to the relay service code #5 (an example of the second relay service code) obtained in advance by UE#B, it can also be understood that UE#B obtained relay service code #2 includes The information of the first parameter.
  • the relay service code #2 can be successfully parsed. For example, if the policy control network element serving UE#B configures the relay service code #5 for UE#B, and the policy control network element serving UE#A configures the relay service code #2 for UE#A In the same manner, UE#B can know how the policy control network element serving UE#A configures the relay service code #2 for UE#A. Among them, the relay service code #5 is associated with the second application. Alternatively, UE#B may obtain the information of the first parameter in the relay service code #2 after performing a specific encryption/decryption algorithm on the relay service code #2. The above shows the method for UE#B to parse the relay service code #2 by way of example, which should not limit the embodiment of the present application.
  • UE#B can successfully parse the relay service code #2, that is, it can successfully obtain the information of the first parameter included in the relay service code #2, UE#B continues to determine whether it can support the first parameter. Parameter access to the first application.
  • UE#B determines that it supports access to the first application with the first parameter, UE#B determines that it can provide the relay service of the first application. Then, UE#B can reply with a response message to UE#A.
  • UE#B may determine whether it supports accessing the first application with the first parameter according to whether the first parameter is the same or equivalent to the second parameter.
  • the second parameter is a parameter for accessing the second application. If the first parameter is the same or the same as the second parameter, UE#B determines that it supports accessing the first application with the first parameter.
  • UE#B determines that it can provide a relay of the first application if it determines that it can access the first application with at least one parameter in the first parameter. service. For example, if the first parameter includes DNN and S-NAASI, UE#B determines that it can provide the relay service of the first application when it determines that it supports the DNN in the first parameter to access the first application; Or UE#B determines that it supports access to the first application with the S-NAASI in the first parameter, and determines that it can provide the relay service of the first application; or UE#B determines that it supports using the S-NAASI in the first parameter to access the first application. When the DNN and S-NAASI visit the first application, it is determined that they can provide the relay service of the first application.
  • UE#B's analysis of the relay service code #2 in the first broadcast message can be understood to mean that UE#B judges the Whether the relay service code #2 is the same or the same as the relay service code #5 obtained by UE#B in advance.
  • UE#B can determine whether the relay service code #2 and the relay service code #5 are the same or equivalent according to whether the prefixes of the relay service code #2 and the relay service code #5 are the same or equivalent.
  • UE#B can provide a relay service for UE#A corresponding to the relay service code #5, that is, support the first parameter to access the first application.
  • the relay service code #5 is associated with the first application.
  • UE#B determines that the relay service code #2 in the first broadcast message is the same as or the same as the relay service code #5 obtained in advance by UE#B, it can be determined that it can provide the relay service of the first application. , Which supports access to the first application with the first parameter. Then, UE#B can reply with a response message to UE#A.
  • relay service codes #5 obtained by UE#B in advance. If the relay service code #2 is equal to or the same as one of the relay service codes #5, UE#B can determine that it can provide the first relay service code #5. An application relay service.
  • UE#B's analysis of the relay service code #2 in the first broadcast message can be understood as UE#B judging the relay Whether the service code #2 and the relay service code #5 saved by UE#B are the same or the same.
  • UE#B can determine whether the relay service code #2 and the relay service code #5 are the same or equivalent according to whether the prefixes of the relay service code #2 and the relay service code #5 are the same or equivalent.
  • the relay service code #5 is associated with the second application.
  • UE#B determines that the relay service code #2 is the same as or equivalent to the relay service code #5
  • UE#B determines that it can provide the relay service of the first application, that is, UE#B determines that it supports the first parameter Visit the first application. Then, UE#B can reply with a response message to UE#A.
  • the broadcast message may further include the following information: information of UE#A, relay service code #3 (an example of the first relay service code).
  • UE#B after UE#B receives the first broadcast message sent by UE#A, it first parses the relay service code #3 in the broadcast message to determine whether it can provide the relay service of the first application. .
  • the analysis of the relay service code #3 by UE#B can be understood as: UE#B judges the relay service code #3 and the relay service code #4 stored by UE#B (the value of the second relay service code) One example) Is it the same or equivalent.
  • UE#B can determine whether the relay service code #3 and the relay service code #3 are the same or equivalent according to whether the prefixes of the relay service code #3 and the relay service code #3 are the same or equivalent.
  • the relay service code #4 is associated with the second application.
  • UE#B determines that the relay service code #3 is the same or the same as the relay service code #4, UE#B determines that it can provide the relay service of the first application, that is, UE#B determines that it supports access with the first parameter The first application. Then, UE#B can reply with a response message to UE#A.
  • the broadcast message may further include the following information: information of UE#A, relay service code #1 (an example of the first relay service code).
  • UE#B after UE#B receives the first broadcast message sent by UE#A, it first parses the relay service code #1 in the broadcast message to determine whether it can provide the relay service of the first application. .
  • UE#B's analysis of the relay service code #1 can be understood as: UE#B judges the relay service code #1 and the relay service code #6 (the second relay service code) stored by UE#B. One example) Is it the same or equivalent. Exemplarily, UE#B can determine whether the relay service code #2 and the relay service code #5 are the same or equivalent according to whether the prefixes of the relay service code #1 and the relay service code #6 are the same or equivalent. Among them, the relay service code #6 is associated with the first application.
  • UE#B determines that the relay service code #1 is the same or the same as the relay service code #6, UE#B determines that it can provide the relay service of the first application, that is, UE#B determines that it supports access with the first parameter The first application. Then, UE#B can reply with a response message to UE#A.
  • relay service codes #6 saved by UE#B. If the relay service code #1 is equal to or the same as one of the relay service codes #6, UE#B can determine that it can provide the first relay service code #6. An application relay service.
  • UE#A may send a PC5 connection request message to UE#B to establish a PC5 connection with UE#B.
  • UE#B determines that there is no PDU session available locally, it performs URSP matching according to the identifier of the first application, and selects the route according to the matched URSP rule
  • the descriptor list initiates the PDU session establishment process.
  • one or more of the DNN, S-NSSAI, SSC mode, PDU session type and other parameters requested by the PDU session establishment request are consistent or equivalent to the session parameters required by UE#A.
  • the first broadcast message sent by UE#A may include the first parameter, or the first relay service code may include information about the first parameter, or alternatively, the first broadcast message sent by UE#A It may include the available relay service codes obtained from the policy control network element. Therefore, the UE#B matched according to the first broadcast message can access the first application with the session parameters (that is, the first parameters) required by the UE#A.
  • Fig. 3 shows a schematic flowchart of a method for a first terminal device (UE#A shown in the figure) to obtain a first relay service code.
  • AMF#1, PCF#1, and UDR#1 shown in the figure all provide services for UE#A, and PCF#2 provides services for the second terminal device (not shown in the figure).
  • the method 300 includes S310-S330, and each step is described in detail below.
  • UE#A sends a request message #1 (the first request message) to PCF#1 (an example of the first policy control network element) through AMF#1 (an example of the access and mobility management network element) An example of).
  • the request message #1 is used to request to obtain the first relay service code.
  • the method for UE#A to send request message #1 to PCF#1 through AMF#1 may be:
  • UE#A first sends a registration request message to AMF#1, and the registration request message may include one or more of the following information: identification information of UE#A and an identifier of the first application.
  • the identification information of UE#A may be a subscriber concealed identifier (SUCI) or a globally unique temporary identity (GUTI).
  • SUCI subscriber concealed identifier
  • GUI globally unique temporary identity
  • the identification information of UE#A is used to identify UE#A, and is used for AMF#1 mapping to obtain a subscriber permanent identifier (SUPI).
  • SUPI subscriber permanent identifier
  • the identifier of the first application is used to indicate the application to be launched by UE#A.
  • the registration request message may also include downgrade indication information, and the downgrade indication information is used to indicate whether UE#A accepts service downgrade.
  • Service degradation can be understood as session parameter degradation, for example, whether UE#A accepts access to the first application with a low-priority session parameter.
  • the degradation indication information is used to indicate that UE#A does not accept service degradation, indicating that UE#A only allows access to the first application with the session parameters required by UE#A.
  • the degradation indication information is used to indicate that UE#A accepts a service degradation, indicating that UE#A may allow access to the first application with session parameters having a lower priority than the session parameters required by UE#A.
  • UE#A is currently in a non-operator network coverage area. In order to access the operator’s network as much as possible, UE#A can allow access to the first with low priority DNN, S-NASSI, SSC mode, PDU session type and other parameters. application.
  • AMF#1 After receiving the registration request message from UE#A, AMF#1 sends a request message #1 to PCF#1.
  • the embodiment of the application does not limit the specific form of the request message #1.
  • the request message #1 may be a user policy association establishment request message.
  • the request message #1 may be a user policy association update request message.
  • the request message #1 may include the following information: the identification information of UE#A and the identifier of the first application. Among them, the identification information of UE#A is SUPI.
  • the request message #1 may also include downgrade indication information.
  • the content of the request message #1 may correspond to the content of the registration request message.
  • the request message #1 also includes the identification information of UE#A and the identifier of the first application.
  • the request message #1 also includes the identification information of UE#A, the identifier of the first application, and the downgrade indication information.
  • UE#A first sends a proximity (proximity based service, ProSe) discovery request message to AMF#1.
  • the ProSe discovery request message may include one or more of the following information: UE#A’s identification information, request type, first The identifier of the application.
  • the identification information of UE#A may be SUCI or GUTI.
  • the identification information of UE#A is used to identify UE#A, and is used to map AMF#1 to obtain SUPI.
  • the identifier of the first application is used to indicate the application to be launched by UE#A.
  • the request type is used to indicate whether UE#A requests to be a relay UE node or a remote UE node.
  • the registration request message may also include downgrade indication information, and the downgrade indication information is used to indicate whether UE#A accepts service downgrade.
  • Service degradation can be understood as session parameter degradation, for example, whether UE#A accepts access to the first application with a low-priority session parameter.
  • the degradation indication information is used to indicate that UE#A does not accept service degradation, indicating that UE#A only allows access to the first application with the session parameters required by UE#A.
  • the degradation indication information is used to indicate that UE#A accepts a service degradation, which means that UE#A may allow access to the first application with session parameters having a lower priority than the session parameters required by UE#A.
  • UE#A is currently in a non-operator network coverage area. In order to access the operator’s network as much as possible, UE#A can allow access to the first with low priority DNN, S-NASSI, SSC mode, PDU session type and other parameters. application.
  • AMF#1 After receiving the ProSe discovery request message from UE#A, AMF#1 sends a request message #1 to PCF#1.
  • the request message #1 may include the following information: identification information of UE#A, identifier of the first application, and request type. Among them, the identification information of UE#A is SUPI, and the identification information can be understood as AMF#1 obtained by mapping SUCI or GUTI.
  • the request message #1 may also include the downgrade indication information.
  • the content of the request message #1 may correspond to the content of the ProSe discovery request message.
  • the request message #1 also includes the identification information of UE#A and the identifier of the first application.
  • the request message #1 also includes the identification information of UE#A, the identifier of the first application, and the downgrade indication information. information.
  • the embodiment of the application does not limit the method for PCF#1 to determine the first relay service code.
  • PCF#1 may decide the first relay service code according to the first parameter.
  • the first relay service code may correspond to the relay service code #2 described above.
  • the first parameter is a parameter corresponding to the access to the first application, that is, the first parameter is a parameter that UE#A needs to use to access the first application, or is a parameter that is allowed by UE#A to access the first application. That is, the first parameter is a parameter in the routing description information in the URSP rule configured by the operator for the application supporting the relay service of UE#A.
  • the first parameter may be one or more of the parameters in the routing description information: DNN, S-NAASI, SSC mode, PDU session type, access mode priority, non-3GPP offload indication, etc.
  • PCF#1 may perform a hash operation on the code corresponding to the first parameter to obtain the first relay service code.
  • PCF#1 may use key encryption on the code corresponding to the first parameter to obtain the first relay service code.
  • PCF#1 may decide the first relay service code according to the first parameter and the following information: the subscription information of UE#A, and the identifier of the first application.
  • the first relay service code may correspond to the relay service code #2 described above.
  • PCF#1 can hash the code corresponding to the first parameter and the code corresponding to the above-mentioned information together or use key encryption to obtain the first relay service code.
  • PCF#1 may decide the first relay service code according to the first parameter and the following information: the subscription information of UE#A, the identifier of the first application, and the downgrade indication information.
  • the first relay service code may correspond to the relay service code #2 described above.
  • PCF#1 can hash the code corresponding to the first parameter and the code corresponding to the above information or use key encryption to obtain the first relay Service code.
  • the encoding corresponding to the session parameter whose priority is lower than the first parameter can be hashed with the encoding corresponding to the above information or encrypted with a key to obtain the first Relay service code.
  • PCF#1 decides the first relay service encoding. It is understandable that PCF#1 can also use other encoding methods to make the first decision.
  • the relay service code is not limited in this embodiment of the application.
  • PCF#1 can obtain the first parameter from UDR#1 (an example of the data management warehouse network element), or obtain the URSP corresponding to the first application Rule or routing description information, so as to obtain the first parameter from the URSP rule or routing description information.
  • the request message #2 is used to request to obtain the first parameter, or to request to obtain the URSP rule corresponding to the first application, or to request to obtain routing description information.
  • the request message #2 is also used to request to verify whether UE#A is allowed to use the first service.
  • the request message #2 is also used to request verification of whether UE#A is allowed to be a relay UE node or a remote UE node.
  • the request message #2 includes the following information: the identification information of UE#A and the identifier of the first application.
  • UDR#1 first obtains the operator for UE#A according to the request message #2 The URSP rules of the first application configuration. Further, if the request message #2 is used to request to obtain routing description information, UDR#1 can obtain the routing description information from the URSP rule; if the request message #2 is used to request to obtain the first parameter, UDR# 1 The routing description information can be obtained from the URSP rules first, and then the first parameter can be obtained from the routing description information.
  • UDR#1 may also obtain the subscription information of UE#A.
  • UDR#1 may also send the subscription information of UE#A to PCF#1.
  • PCF#1 may decide the first relay service code according to the second relay service code from PCF#2. If the second relay service code includes the information of the second parameter, the first relay service code determined by PCF#1 according to the second relay service code corresponds to the above-mentioned relay service code #2; if The second relay service code does not include the information of the second parameter, and the first relay service code determined by PCF#1 according to the second relay service code corresponds to the relay service code #3 described above.
  • PCF#1 may not process the second relay service code, and decide the second relay service code as the first relay service code.
  • PCF#1 can process the second relay service code to obtain the first relay service code. For example, PCF#1 may decide the prefix of the second relay service code as the first relay service code. For another example, PCF#1 may generate a first relay service code according to the second relay service code, and the first relay service code corresponds to the second relay service code.
  • PCF#1 can obtain the second relay service code from PCF#2.
  • S3201b PCF#1 sends request message #3 (an example of the third request message) to UDR#1.
  • the request message #2 is used to request information about PCF#2.
  • UDR#1 sends PCF#2 information to PCF#1.
  • UDR#1 after UDR#1 receives the request message #3 from PCF#1, it can send to PCF#1 the identification information of the public land mobile network (PLMN) of the visited place where UE#A is located and/ Or the identification information of the neighboring PLMN. Then, the PCF#1 searches for the PCF#2 information in the visited PLMN network and/or the neighboring PLMN network according to the identification information of the visited PLMN and/or the neighboring PLMN.
  • PLMN public land mobile network
  • UDR#1 can also directly carry the identification information of the visited PLMN and/or the identification information of the neighboring PLMN in the response message sent to PCF#1, and the PLMN network and/or the neighboring PLMN network of the visited PLMN.
  • PCF#2 information can also directly carry the identification information of the visited PLMN and/or the identification information of the neighboring PLMN in the response message sent to PCF#1, and the PLMN network and/or the neighboring PLMN network of the visited PLMN.
  • UDR#1 sends the multiple PCF#2 information and/or multiple PLMN identification information to PCF#1.
  • PCF#1 receives the identification information of the visited PLMN and/or the identification information of the neighboring PLMN, PCF#1 can also query the visited PLMN and/or neighboring PLMN through the network repository function (NRF) network element PCF#2 in the information.
  • NRF network repository function
  • PCF#1 sends a request message #4 (an example of the second request message) to PCF#2.
  • the request message #4 is used to request to obtain the second relay service code.
  • the request message #4 includes the following information: the first parameter and the identifier of the first application.
  • the request message #4 may also include UE#A identification information.
  • the request message #4 may also include downgrade indication information.
  • PCF#1 can receive multiple pieces of PCF#2 information, therefore, PCF#1 sends the request message #4 to each PCF#2.
  • PCF#2 sends the second relay service code to PCF#1.
  • PCF#2 After PCF#2 receives request message #4, it first determines whether the UE#B it serves supports access to the first application with the first parameter. For example, PCF#2 determines the session in the URSP rule configured by the operator for UE#B Whether the parameter is the same or the same as the first parameter, if the same or the same, the PCF#2 determines that the UE#B it serves supports accessing the first application with the first parameter. Then, PCF#2 sends the second relay service code decided by UE#B to PCF#1. For another example, PCF#2 can also determine the second relay service code that supports the provision of the first parameter to access the relay service of the first application according to the relay service code list saved locally, and select one or more qualified ones. The second relay service code sends PCF#1.
  • the PCF#2 can also determine whether the UE#B served by the PCF#2 is allowed to provide a relay service for the UE#A. If allowed, PCF#2 sends the second relay service code decided by UE#B to PCF#1.
  • the request message #4 also includes downgrade indication information
  • PCF#2 determines that the session parameter in the URSP rule configured by the operator for UE#B has a lower priority than the first parameter, it is also It can be sent to PCF#1 as the second relay service code decided by UE#B.
  • PCF#2 can also determine the second relay service code that supports the provision of the second parameter after the first parameter is downgraded to access the relay service of the first application according to the relay service code list saved locally, and Send one or more second relay service codes that meet the conditions to PCF#1.
  • PCF#1 may decide the first relay service code according to the following information: the subscription information of UE#A, and the identifier of the first application.
  • the first relay service code may correspond to the relay service code #1 described above.
  • PCF#1 can hash the code corresponding to the above-mentioned information or use key encryption to obtain the first relay service code.
  • PCF#1 sends the first relay service code to UE#A through AMF#1.
  • PCF#1 may first send a response message to AMF#1, where the response message includes the first relay service code, and then AMF#1 sends the first relay service code to UE#A.
  • the response message sent by PCF#1 to AMF#1 may also include the identifier of the first application.
  • the message sent by AMF#1 to UE#A may also include the identifier of the first application.
  • the response message sent by PCF#1 to AMF#1 may also include radio parameters corresponding to the first broadcast message sent by UE#A, such as frequency band information, frequency band applicable geographic area, effective time, and so on.
  • the message sent by AMF#1 to UE#A may also include information such as wireless parameters and valid time.
  • the PCF#1 may allocate the first relay service code including the information of the first parameter to the UE#A according to the request of the UE#A. Further, UE#B matched by UE#A according to the first relay service code can provide the relay service required by UE#A. Alternatively, PCF#1 may also allocate the first relay service code associated with UE#B to UE#A, and UE#B corresponding to the first relay service code may provide the relay service required by UE#A. Therefore, UE#B matched by UE#A according to the first relay service code can meet the requirements of UE#A.
  • Fig. 4 shows a schematic flowchart of a method for establishing a connection provided by an embodiment of the present application.
  • the method shown in FIG. 4 may be executed by UE#A and UE#B in the system shown in FIG. 1, where UE#A corresponds to the first terminal device, and UE#B corresponds to the second terminal device.
  • the method for establishing a connection between UE#A and UE#B described in the method 200 corresponds to mode A, that is, the relay UE sends a broadcast message.
  • the method includes S410 and S420. Each step is described in detail below.
  • UE#B may send the second broadcast message on the corresponding frequency band according to the frequency point information received from the policy control network element serving the UE#B.
  • UE#A may receive the second broadcast message on the corresponding frequency band according to the frequency information received from the policy control network element serving the UE#A.
  • the second broadcast message is used to be discovered by UE#A that needs a relay service.
  • the embodiment of the present application does not limit the specific content of the second broadcast message.
  • the broadcast message may include the following information: information of UE#B, relay service code #4 (an example of the second relay service code), and second parameters.
  • the information of UE#B is used to identify the UE#B, and the information of UE#B may include the link layer identification of UE#B or the application layer user information of UE#B.
  • Relay service code #4 is associated with a second application, which is an application for UE#B to support relay services, and relay service code #4 may include information about the second application.
  • the relay service code #4 may also include the relay service security policy of UE#B.
  • the relay service code #4 may be locally pre-configured by UE#B, or it may be obtained by UE#B from the policy control network element serving it, which is not limited in the embodiment of the present application.
  • the method for UE#B to obtain the relay service code #4 from the policy control network element serving it will be described later in conjunction with other embodiments. For the sake of brevity, it will not be described in detail here.
  • the second parameter is a parameter corresponding to the access to the second application, that is, the second parameter is a parameter that UE#B needs to use to access the second application, or is a parameter that is allowed by UE#B to access the second application. That is, the second parameter is a parameter in the routing description information in the URSP rule configured by the operator for the application supporting the relay service of UE#B.
  • the second parameter may be one or more of the parameters in the routing description information: DNN, S-NAASI, SSC mode, PDU session type, priority of access mode, non-3GPP offload indication, etc.
  • the second parameter is obtained by UE#B from the policy control network element serving it.
  • the broadcast message may include the following information: information of UE#B, and relay service code #5.
  • the information of UE#B is used to identify the UE#B, and the information of UE#B may include the link layer identification of UE#B or the application layer user information of UE#B.
  • the relay service code #5 includes the information of the second parameter.
  • the information that the relay service code #5 includes the second parameter can be understood as that the relay service code #5 includes the code corresponding to the second parameter, or the relay service code #5 includes the second parameter.
  • the second parameter can be parsed from the relay service code #5.
  • the embodiment of this application does not limit the specific form of the relay service code #5.
  • the relay service code #5 is associated with the second application, and it can also be understood that the relay service code #5 is associated with UE#B.
  • the relay service code #5 may also include the information of the second application.
  • the relay service code #5 may also include the relay service security policy of UE#B.
  • the relay service code #5 is associated with a first application, and the first application is an application to be launched by UE#A. It can also be understood that the relay service code #5 is associated with UE#A. In this case, the relay service code #5 may also include the information of the first application. Optionally, the relay service code #5 may also include the relay service security policy of UE#A.
  • the relay service code #5 may be obtained by UE#B from the policy control network element serving it.
  • the method for UE#B to obtain the relay service code #5 from the policy control network element serving it will be described in detail later in conjunction with other embodiments. For the sake of brevity, it will not be described in detail here.
  • the first broadcast message may include the following information: information of UE#B, and relay service code #6 (an example of the second relay service code).
  • the information of UE#B is used to identify the UE#B, and the information of UE#B may include the link layer identification of UE#B or the application layer user information of UE#B.
  • the relay service code #6 is associated with the first application, and it can also be understood that the relay service code #6 is associated with UE#A. And UE#B can provide a relay service for UE#A corresponding to the relay service code #6. In other words, the relay service code #6 is an available relay service code.
  • the relay service code #6 may include the information of the first application.
  • the relay service code #6 may also include the relay service security policy of UE#A.
  • the relay service code #6 may be obtained by UE#B from the policy control network element serving it.
  • the method for UE#B to obtain the relay service code #6 from the policy control network element serving it will be described in detail later in conjunction with other embodiments. For the sake of brevity, it will not be described in detail here.
  • the first broadcast message may include the following information: information of UE#B, relay service code #4 (an example of the second relay service code).
  • the information of UE#B is used to identify the UE#B, and the information of UE#B may include the link layer identification of UE#B or the application layer user information of UE#B.
  • the relay service code #4 is associated with the second application.
  • the relay service code #4 may include the information of the second application.
  • the relay service code #4 may also include the relay service security policy of UE#B. .
  • the relay service code #4 may be locally pre-configured by UE#B, or it may be obtained by UE#B from the policy control network element serving it, which is not limited in the embodiment of the present application.
  • the method for UE#B to obtain the relay service code #1 from the policy control network element serving it will be described later in conjunction with other embodiments. For the sake of brevity, it will not be described in detail here.
  • the request message #5 is used to request to establish a PC5 connection with UE#B.
  • the second broadcast message sent by UE#B may include different content.
  • the first broadcast message sent by UE#B includes the following information: information of UE#B, relay service code #4 (an example of the second relay service code), and second parameters.
  • UE#A after UE#A receives the second broadcast message sent by UE#B, it first parses the relay service code #4 in the second broadcast message to determine whether UE#B can provide itself to be initiated Application relay service.
  • UE#A's analysis of the relay service code #4 in the second broadcast message can be understood as: UE#A judges the relay service code #4 in the second broadcast message and the relay service code stored by UE#A #1 (an example of the first relay service code) is the same, or, is it the same, or, whether the relay service code #1 and the relay service code #4 are encrypted/decrypted by a specific encryption/decryption algorithm to get the And other information. For example, whether UE#A performs a specific decryption algorithm on relay service code #1 and relay service code #4 to obtain the same application identifier.
  • the relay service code #1 configured by UE#A can also be a filter for the target relay service code.
  • UE#A can determine whether the relay service code #4 meets the filter requirements. , That is, whether the UE#B corresponding to the relay service code #4 can provide the relay service of the application to be initiated by the UE#A for the UE#A.
  • the relay service code #1 is associated with the first application, and can also be understood as the relay service code #1 is associated with UE#A.
  • Relay service code #1 is the relay service code saved by UE#A. It can be pre-configured locally by UE#A, or it can be obtained by UE#A from the policy control network element that it serves. This is not limited.
  • the method for UE#A to obtain the relay service code #1 from the policy control network element it serves can refer to the method for UE#B to obtain the relay service code #4. For the sake of brevity, details are not described in the embodiment of this application.
  • UE#A determines that relay service code #1 is the same as relay service code #4, or is equivalent, or performs a specific encryption/decryption algorithm to obtain peer-to-peer information, UE#A continues whether the second parameter is the first The parameters are consistent or equivalent, and the first parameter is a parameter corresponding to the access first application.
  • UE#A determines that the second parameter is consistent or equivalent to the first parameter, UE#A determines that UE#B can provide the relay service of the first application. Then, UE#A may send a request message #5 to UE#B.
  • UE#A may determine that it can provide the first parameter when it is determined that at least one parameter in the second parameter is consistent or equivalent to the parameter in the first parameter.
  • An application relay service For example, if the second parameter includes DNN and S-NAASI, UE#A determines that the DNN in the second parameter is consistent or equivalent to the DNN in the first parameter, and it is determined that UE#B can provide the first application
  • UE#A determines that the S-NASSI in the second parameter is consistent or equivalent to the S-NASSI in the first parameter, it is determined that UE#B can provide the relay service of the first application; then When UE#A determines that DNN and S-NASII in the second parameter are consistent or equivalent to DNN and S-NASSI in the first parameter, it is determined that UE#B can provide the relay service of the first application.
  • the second broadcast message sent by UE#B includes the following information: information of UE#B, relay service code #5 (an example of the second relay service code).
  • UE#A after UE#A receives the second broadcast message sent by UE#B, it can analyze the relay service code #5 in the second broadcast message to determine whether UE#B can provide the first application. Relay service.
  • UE#A's analysis of the relay service code #5 in the second broadcast message can be understood to mean that UE#A judges the relay Whether the service code #5 is the same as or equivalent to the relay service code #2 obtained by UE#A in advance, it can also be understood that UE#A obtains the information of the second parameter included in the relay service code #5.
  • the relay service code #5 can be successfully parsed. For example, if the policy control network element serving UE#A configures the relay service code #2 (an example of the first relay service code) for UE#A, the same way as the policy control network element serving UE#B The manner of configuring the relay service code #5 for UE#B is the same, and then UE#A can know how the policy control network element serving UE#B configures the relay service code #5 for UE#B. Among them, the relay service code #2 is associated with the first application.
  • UE#A may obtain the information of the second parameter in the relay service code #5 after performing a specific encryption/decryption algorithm on the relay service code #5.
  • the above shows the method for UE#A to parse the relay service code #5 by way of example, which should not limit the embodiment of the present application.
  • UE#A may be the same as the first parameter. Consistent or equivalent.
  • UE#A determines that the second parameter is consistent or equivalent to the first parameter, UE#A determines that UE#B can provide the relay service of the first application. Then, UE#A may send a request message #5 to UE#B.
  • UE#A may determine that it can provide the first parameter when it is determined that at least one parameter in the second parameter is consistent or equivalent to the parameter in the first parameter.
  • An application relay service For example, if the second parameter includes DNN and S-NAASI, UE#A determines that the DNN in the second parameter is consistent or equivalent to the DNN in the first parameter, and it is determined that UE#B can provide the first application Or UE#A determines that the S-NASSI in the second parameter is consistent or equivalent to the S-NASSI in the first parameter, and determines that UE#B can provide the relay service of the first application; or When UE#A determines that DNN and S-NASII in the second parameter are consistent or equivalent to DNN and S-NASSI in the first parameter, it is determined that UE#B can provide the relay service of the first application.
  • UE#A's analysis of the relay service code #5 in the second broadcast message can be understood to mean that UE#A judges the Whether the relay service code #5 is the same or the same as the relay service code #2 acquired in advance by UE#A.
  • UE#A can determine whether the relay service code #2 and the relay service code #5 are the same or equivalent according to whether the prefixes of the relay service code #2 and the relay service code #5 are the same or equivalent.
  • UE#B corresponding to the relay service code #2 can provide a relay service for UE#A, that is, it supports access to the first application with the first parameter.
  • the relay service code #2 is associated with the second application.
  • UE#A determines that the relay service code #5 in the second broadcast message is equal to or the same as the relay service code #2 saved by UE#A, it can be determined that UE#B can provide the medium of the first application. Following the service, that is, UE#B supports accessing the first application with the first parameter. Then, UE#A may send a request message #5 to UE#B.
  • relay service codes #2 saved by UE#A. If the relay service code #5 is equal to or the same as one of the relay service codes #2, UE#A can determine that UE#B can Provide the relay service of the first application.
  • UE#A's analysis of the relay service code #5 in the second broadcast message can be understood as UE#A judging the relay Whether the service code #5 is the same or the same as the relay service code #2 stored by UE#A.
  • UE#A can determine whether the relay service code #2 and the relay service code #5 are the same or equivalent according to whether the prefixes of the relay service code #2 and the relay service code #5 are the same or equivalent.
  • the relay service code #2 is associated with the first application.
  • UE#A determines that the relay service code #5 is the same as or equivalent to the relay service code #2, then UE#A determines that UE#B can provide the relay service of the first application, that is, it determines that UE#B supports the first parameter Visit the first application. Then, UE#A may send a request message #5 to UE#B.
  • the broadcast message may further include the following information: information of UE#A, relay service code #6 (an example of the second relay service code).
  • UE#A after UE#A receives the second broadcast message sent by UE#B, it first parses the relay service code #6 in the second broadcast message to determine whether UE#B can provide the first application Relay service.
  • the analysis of the relay service code #6 by UE#A can be understood as: UE#A judges that the relay service code #6 and the relay service code #1 stored by UE#A (the value of the first relay service code) One example) Is it the same or equivalent. Exemplarily, UE#A can determine whether the relay service code #1 relay service code #6 is the same or equivalent according to whether the prefixes of the relay service code #6 and the relay service code #1 are the same or equivalent. Among them, the relay service code #1 is associated with the first application.
  • UE#A determines that the relay service code #6 is the same or the same as the relay service code #1, then UE#A determines that UE#B can provide the relay service of the first application, that is, it determines that UE#B supports the first parameter Visit the first application. Then, UE#A may send a request message #5 to UE#B.
  • the broadcast message may further include the following information: information of UE#A, relay service code #4 (an example of the second relay service code).
  • UE#A after UE#A receives the second broadcast message sent by UE#B, it first parses the relay service code #4 in the second broadcast message to determine whether UE#B can provide the first application Relay service.
  • the analysis of the relay service code #4 by UE#A can be understood as: UE#A judges that the relay service code #4 and the relay service code #3 stored by UE#A (the value of the first relay service code #3) One example) Is it the same or equivalent. Exemplarily, UE#A can determine whether the relay service code #3 and the relay service code #4 are the same or equivalent according to whether the prefixes of the relay service code #3 and the relay service code #4 are the same or equivalent. Among them, the relay service code #3 is associated with the second application.
  • UE#A determines that the relay service code #4 is the same or the same as the relay service code #3, then UE#A determines that UE#B can provide the relay service of the first application, that is, it determines that UE#B supports the first parameter Visit the first application. Then, UE#A may send a request message #5 to UE#B.
  • relay service codes #3 saved by UE#A. If the relay service code #4 is equal to or the same as one of the relay service codes #3, UE#A can determine that UE#B can Provide the relay service of the first application.
  • UE#B determines that there is no PDU session available locally, it performs URSP matching according to the identifier of the first application, and selects the route according to the matched URSP rule
  • the descriptor list initiates the PDU session establishment process.
  • one or more of the parameters such as DNN, S-NSSAI, SSC mode, and PDU session type requested by the PDU session establishment request are consistent or equivalent to the session parameters required by UE#A.
  • the second broadcast message sent by UE#B may include the second parameter, or the second relay service code may include information about the second parameter, or alternatively, the second broadcast message sent by UE#B It may include the available relay service codes obtained from the policy control network element. Therefore, UE#B can provide the relay service required by UE#A for UE#A matched according to the second broadcast message, that is, UE#B can access the UE#A to be initiated with the session parameters required by UE#A. application.
  • FIG. 5 shows a schematic flowchart of a method for a second terminal device (UE#B shown in the figure) to obtain a second relay service code.
  • AMF#2, PCF#2, and UDR#2 shown in the figure provide services for UE#B, and PCF#1 provides services for the first terminal device (not shown in the figure).
  • the method 500 includes S510-S530, and each step is described in detail below.
  • UE#B sends a request message #6 (the fifth request message) to PCF#2 (an example of the second policy control network element) through AMF#2 (an example of the access and mobility management network element) An example of).
  • the request message #6 is used to request to obtain the second relay service code.
  • the method for UE#B to send request message #6 to PCF#2 through AMF#2 may be:
  • UE#B first sends a registration request message to AMF#2, and the registration request message may include one or more of the following information: identification information of UE#B and an identifier of the second application.
  • the identification information of UE#B may be SUCI or GUTI.
  • the identification information of UE#B is used to identify UE#B, and is used to map AMF#2 to obtain SUPI.
  • the identifier of the first application is used to indicate that UE#B supports the application of the relay service.
  • AMF#2 After receiving the registration request message from UE#B, AMF#2 sends a request message #6 to PCF#2.
  • the embodiment of this application does not limit the specific form of the request message #6.
  • the request message received by AMF#2 is an initial registration request message, that is, a user policy association has not yet been established between AMF#2 and PCF#2
  • the request message #6 may be a user policy association establishment request message.
  • the registration request message received by AMF#2 is a registration request message sent by UE#B location update, or a registration request message sent periodically by UE#B, that is, between AMF#2 and PCF#2
  • the user policy association is still active, and the request message #6 may be a user policy association update request message.
  • the request message #6 may include the following information: the identification information of UE#B and the identifier of the second application. Among them, the identification information of UE#B is SUPI.
  • the content of the request message #6 may correspond to the content of the registration request message.
  • the request message #6 also includes the identification information of UE#B and the identifier of the second application.
  • the UE#B first sends a ProSe discovery request message to AMF#2.
  • the ProSe discovery request message may include one or more of the following information: identification information of UE#B, request type, and identifier of the second application.
  • the identification information of UE#B may be SUCI or GUTI.
  • the identification information of UE#B is used to identify UE#B and to map SUPI to AMF#2.
  • the identifier of the second application is used to indicate that UE#B supports the application of the relay service.
  • the request type is used to indicate whether UE#B requests to be a relay UE node or a remote UE node.
  • AMF#2 After receiving the ProSe discovery request message from UE#A, AMF#2 sends a request message #6 to PCF#2.
  • the request message #6 may include the following information: identification information of UE#B, identifier of the second application, and request type.
  • identification information of UE#B is SUPI, and the identification information can be understood as AMF#2 obtained by mapping SUCI or GUTI.
  • the content of the request message #6 may correspond to the content of the ProSe discovery request message.
  • the request message #6 also includes the identification information of UE#B and the identifier of the second application.
  • the embodiment of the present application does not limit the method for PCF#2 to determine the second relay service code.
  • PCF#2 may decide the second relay service code according to the second parameter.
  • the second relay service code may correspond to the relay service code #5 described above.
  • the second parameter is a parameter corresponding to the access to the second application, that is, the second parameter is a parameter that UE#B needs to use to access the second application, or is a parameter that is allowed by UE#B to access the second application. That is, the second parameter is a parameter in the routing description information in the URSP rule configured by the operator for the application supporting the relay service of UE#B.
  • the first parameter may be one or more of the following parameters in the routing description information: DNN, S-NAASI, SSC mode, PDU session type, access mode priority, non-3GPP offload indication, etc.
  • PCF#2 may perform a hash operation on the code corresponding to the second parameter to obtain the second relay service code.
  • PCF#2 may use key encryption on the code corresponding to the second parameter to obtain the second relay service code.
  • PCF#2 may decide the second relay service code according to the second parameter and the following information: the subscription information of UE#B and the identifier of the second application.
  • the second relay service code may correspond to the relay service code #5 described above.
  • PCF#2 can hash the code corresponding to the second parameter and the code corresponding to the above-mentioned information together or use key encryption to obtain the second relay service code.
  • PCF#2 can obtain the second parameter from UDR#2 (an example of the data management warehouse network element), or obtain the URSP corresponding to the second application Rule or routing description information, so as to obtain the second parameter from the URSP rule or routing description information.
  • UDR#2 an example of the data management warehouse network element
  • PCF#2 sends a request message #7 to UDR#2.
  • the request message #7 is used to request to obtain the second parameter, or to request to obtain the URSP rule corresponding to the second application, or to request to obtain the routing description information.
  • the request message #7 is also used to request to verify whether UE#B is allowed to use the second application.
  • the request message #7 received by PCF#2 includes the request type
  • the request message #7 is also used to request verification of whether UE#B is allowed to be a relay UE node or a remote UE node.
  • the request message #7 includes the following information: the identification information of UE#B and the identifier of the second application.
  • UDR#2 first obtains the operator for UE#B according to the request message #7 The URSP rule of the second application configuration. Further, if the request message #7 is used to request to obtain routing description information, UDR#2 can obtain the routing description information from the URSP rule; if the request message #7 is used to request to obtain the second parameter, UDR# 2 The routing description information can be obtained from the URSP rule first, and then the second parameter can be obtained from the routing description information.
  • UDR#2 may also obtain the subscription information of UE#B.
  • UDR#2 may also send the subscription information of UE#B to PCF#2.
  • PCF#2 may decide the second relay service code according to the first relay service code from PCF#1. If the first relay service code includes the information of the first parameter, the second relay service code determined by PCF#2 according to the first relay service code corresponds to the above-mentioned relay service code #5; if The first relay service code does not include the information of the first parameter, and the second relay service code determined by PCF#2 according to the first relay service code corresponds to the relay service code #6 described above.
  • PCF#2 may not process the first relay service code, and decide the first relay service code as the second relay service code.
  • PCF#2 can process the first relay service code to obtain the second relay service code. For example, PCF#2 may decide the prefix of the first relay service code as the second relay service code. For another example, PCF#2 may generate a second relay service code according to the first relay service code, and the second relay service code corresponds to the first relay service code.
  • PCF#2 can obtain the first relay service code from PCF#1.
  • PCF#2 sends a request message #8 (an example of the seventh request message) to UDR#2.
  • the request message #8 is used to request to obtain the information of PCF#1.
  • UDR#2 sends PCF#1 information to PCF#2.
  • UDR#2 may send to PCF#2 the identification information of the visited PLMN where UE#B is located and/or the identification information of neighboring PLMNs. Then, the PCF#2 searches for the PCF#1 information in the visited PLMN and/or the neighboring PLMN network according to the identification information of the visited PLMN and/or the neighboring PLMN identification information.
  • UDR#2 can also directly carry the identification information of the visited PLMN and/or the identification information of the neighboring PLMN in the response message sent to the PCF#2, and the identification information of the visited PLMN and/or the neighboring PLMN network.
  • PCF#1 information can also directly carry the identification information of the visited PLMN and/or the identification information of the neighboring PLMN in the response message sent to the PCF#2, and the identification information of the visited PLMN and/or the neighboring PLMN network.
  • UDR#2 sends the multiple pieces of PCF#1 information and/or multiple pieces of PLMN identification information to PCF#2.
  • PCF#2 can also query the visited PLMN and/or PCF#1 information in the neighboring PLMN through the NRF network element.
  • PCF#2 sends a request message #9 (an example of the sixth request message) to PCF#1.
  • the request message #9 is used to request to obtain the first relay service code.
  • the request message #9 includes the following information: the second parameter and the identifier of the second application.
  • the request message #9 may also include UE#B identification information.
  • PCF#2 can receive multiple pieces of information of PCF#1. Therefore, PCF#2 sends the request message #9 to each PCF#1.
  • PCF#1 sends the first relay service code to PCF#2.
  • PCF#1 After PCF#1 receives request message #9, it first determines whether the second parameter in request message #9 is the same or equivalent to the first parameter required by UE#A it serves. If it is the same or equivalent, then PCF#1 It is determined that UE#B served by PCF#2 supports the provision of the relay service of the first application. Then, PCF#1 sends the first relay service code decided by UE#A to PCF#2. For another example, PCF#1 can also determine the first relay service code in which the corresponding first parameter is the same or equivalent to the second parameter according to the list of relay service codes stored locally, and identify one or more The first relay service code is sent to PCF#2.
  • the PCF#1 may also determine whether the UE#A served by the PCF#1 is allowed to establish a connection with the UE#B. If allowed, PCF#1 sends the first relay service code decided by UE#A to PCF#2.
  • PCF#2 may determine the second relay service code based on the following information: the subscription information of UE#B, and the identifier of the second application.
  • the second relay service code may correspond to the relay service code #4 described above.
  • PCF#2 may perform hash operation on the code corresponding to the above information or use key encryption to obtain the second relay service code.
  • PCF#2 sends the second relay service code to UE#B through AMF#2.
  • PCF#2 may first send a response message to AMF#2, the response message includes the second relay service code, and then AMF#2 sends the second relay service code to UE#B.
  • the response message sent by PCF#2 to AMF#2 may also include the identifier of the second application.
  • the message sent by AMF#2 to UE#B may also include the identifier of the second application.
  • the response message sent by PCF#2 to AMF#2 may also include radio parameters corresponding to the second broadcast message sent by UE#B, such as frequency band information, frequency band applicable geographic area, effective time, and so on.
  • the message sent by AMF#2 to UE#B may also include information such as wireless parameters and valid time.
  • PCF#2 may allocate the second relay service code including the information of the second parameter to UE#B according to the request of UE#B. Further, UE#B may provide a relay service for UE#A matched according to the second relay service code. Alternatively, PCF#2 may also allocate a second relay service code associated with UE#A to UE#B, and may provide a relay service for UE#A corresponding to the second relay service code. Therefore, UE#B can meet the requirements of UE#A matched according to the second relay service code.
  • UE#A shown in Figures 6 to 9 corresponds to the remote UE
  • PCF#1 provides services for UE#A
  • UE#B corresponds to the relay UE
  • PCF#2 provides services for UE#B service.
  • FIG. 6 shows a schematic flowchart of a method for establishing a connection provided by an embodiment of the present application. As shown in Figure 6, the method includes S610-S650, and each step is described in detail below.
  • the relay service code #2 contains the information of the first parameter.
  • the method for UE#A to obtain the relay service code #2 can refer to method 300, which is not repeated here for brevity.
  • the relay service code #2 is associated with the application to be launched by UE#A, that is, it is associated with UE#A.
  • the relay service code #2 is associated with the application that UE#B supports the relay service, that is, it is associated with UE#B.
  • the relay service code #5 contains the information of the second parameter.
  • the relay service code #5 is associated with the application that UE#B supports the relay service, that is, it is associated with UE#B.
  • the relay service code #5 is associated with the application to be launched by UE#A, that is, it is associated with UE#A.
  • the first broadcast message includes relay service code #2.
  • S640 UE#B sends a response message to UE#A.
  • the response message is used to indicate that UE#B supports access to the application to be launched by UE#A with the first parameter.
  • the relay service code #2 included in the first broadcast message is associated with the application to be launched by UE#A, then the relay service code #5 acquired at UE#B is associated with the application to be launched by UE#A, or with In the case that UE#B is associated with an application supporting the relay service, UE#B can determine whether it supports access to UE# with the first parameter based on judging whether the relay service code #2 is the same as or equivalent to the relay service code #5.
  • a application to be launched please refer to method 200. For the sake of brevity, it will not be repeated here.
  • the relay service code #5 obtained at UE#B is the same as that of UE#B supporting the relay service.
  • UE#B can determine whether it supports access to the application to be launched by UE#A with the first parameter based on judging whether the relay service code #2 is the same or equivalent to the relay service code #5.
  • method 200 For the sake of brevity, it will not be repeated here.
  • S650 UE#A sends a request message #5 to UE#B.
  • the request message #5 is used to request to establish a PC5 connection with UE#B.
  • the method 600 may perform S620 first, and then perform S610; or, it may also perform S610 and S630 first, and then perform S620.
  • FIG. 7 shows a schematic flowchart of a method for establishing a connection provided by an embodiment of the present application. As shown in Figure 7, the method includes S710-S770, and each step is described in detail below.
  • the relay service code #1 does not include the information of the first parameter, and the intermediate service code #1 is associated with the application to be launched by UE#A, that is, it is associated with UE#A.
  • the method for UE#A to obtain the relay service code #1 refer to method 300. For brevity, details are not repeated here.
  • S710 may not be performed.
  • method 300 For the method for UE#A to obtain the first parameter, refer to method 300, which is not repeated here for brevity.
  • S720 may not be executed.
  • the relay service code #4 does not include the information of the second parameter, and the intermediate service code #4 is associated with the application that UE#B supports the relay service, that is, it is associated with UE#B.
  • the method for UE#A to obtain the relay service code #4 refer to method 500. For brevity, details are not repeated here.
  • S740 may not be executed.
  • the first broadcast message includes the relay service code #1 and the first parameter.
  • the response message is used to indicate that UE#B supports access to the application to be launched by UE#A with the first parameter.
  • UE#B can determine whether it supports access to UE#A with the first parameter by judging whether the relay service code #1 is the same or equivalent to the relay service code #4, and whether the first parameter and the second parameter are consistent or equivalent. Initiated application. For the detailed judgment method, please refer to method 200. For brevity, it will not be repeated here.
  • the request message #5 is used to request to establish a PC5 connection with UE#B.
  • the method 700 may execute S720 first, and then execute S710; or, it may also execute S730-S740 first, and then execute S710-S720.
  • FIG. 8 shows a schematic flowchart of a method for establishing a connection provided by an embodiment of the present application. As shown in Figure 8, the method includes S810-S850, and each step is described in detail below.
  • the relay service code #1 does not include the information of the first parameter, and the intermediate service code #1 is associated with the application to be launched by UE#A, that is, it is associated with UE#A.
  • the method for UE#A to obtain the relay service code #1 refer to method 300. For brevity, details are not repeated here.
  • S810 may not be performed.
  • the relay service code #6 is associated with the application to be launched by UE#A, that is, it is associated with UE#A.
  • UE#B For the method for UE#B to obtain the relay service code #6, refer to method 500.
  • UE#B For brevity, details are not described herein again.
  • the first broadcast message includes relay service code #1.
  • the response message is used to indicate that UE#B supports access to the application to be launched by UE#A with the first parameter.
  • UE#B can determine whether it supports access to the application to be launched by UE#A with the first parameter based on judging whether the relay service code #1 is the same or equivalent to the relay service code #6.
  • the relay service code #1 is the same or equivalent to the relay service code #6.
  • the request message #5 is used to request to establish a PC5 connection with UE#B.
  • the method 800 may perform S820 first, and then perform S810; or, it may also perform S810 and S830 first, and then perform S820.
  • FIG. 9 shows a schematic flowchart of a method for establishing a connection provided by an embodiment of the present application. As shown in Figure 9, the method includes S910-S950, and each step is described in detail below.
  • S910 UE#A obtains relay service code #3 from PCF#1.
  • the relay service code #3 is associated with the application supporting the relay service with UE#B, that is, it is associated with UE#B.
  • UE#A For the method for UE#A to obtain the relay service code #3, refer to method 300. For brevity, details are not repeated here.
  • the relay service code #4 does not include the information of the second parameter, and the intermediate service code #4 is associated with the application that UE#B supports the relay service, that is, it is associated with UE#B.
  • the method for UE#A to obtain the relay service code #4 refer to method 500. For brevity, details are not repeated here.
  • the first broadcast message includes relay service code #3.
  • the response message is used to indicate that UE#B supports access to the application to be launched by UE#A with the first parameter.
  • UE#B can determine whether it supports access to the application to be launched by UE#A with the first parameter based on determining whether the relay service code #3 is the same or equivalent to the relay service code #4.
  • the relay service code #3 is the same or equivalent to the relay service code #4.
  • UE#A sends a request message #5 to UE#B.
  • the request message #5 is used to request to establish a PC5 connection with UE#B.
  • the method 900 may perform S920 first, and then perform S910; or, it may also perform S910 and S930 first, and then perform S920.
  • the above shows the method for establishing a PC5 connection between the remote UE and the relay UE in the mode B scenario.
  • the method for establishing a PC5 connection between the remote UE and the relay UE can refer to the above method. For brevity, here No longer.
  • FIG. 10 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the communication device 2000 may include a processing unit 2100 and a transceiving unit 2200.
  • the communication device 2000 may correspond to the first terminal device in the above method embodiment, for example, it may be the first terminal device, or a component (such as a chip or a component) configured in the first terminal device. Chip system).
  • the communication device 2000 may correspond to the first terminal device in the method 200, the method 300, the method 400, the method 600, the method 700, the method 800, and the method 900 according to the embodiments of the present application, and the communication device 2000 may include In performing the method 200 in FIG. 2, the method 300 in FIG. 3, the method 400 in FIG. 4, the method 600 in FIG. 6, the method 700 in FIG. 7, the method 800 in FIG. 8, and the method 900 in FIG. The unit of the method performed by the first terminal device.
  • the units in the communication device 2000 and the other operations and/or functions described above are respectively intended to implement the method 200 in FIG. 2, the method 300 in FIG. 3, the method 400 in FIG. 4, the method 600 in FIG. 6, and the method 600 in FIG.
  • the transceiver unit 2200 in the communication device 2000 may be implemented by a transceiver, for example, it may correspond to the transceiver 3020 in the terminal device 3000 shown in FIG. 11.
  • the processing unit 2100 in the communication device 2000 may be implemented by at least one processor, for example, may correspond to the processor 3010 in the terminal device 3000 shown in FIG. 11.
  • the transceiver unit 2200 in the communication device 2000 may be implemented through an input/output interface, and the processing unit 2100 in the communication device 2000 may It is realized by the processor, microprocessor or integrated circuit integrated on the chip or chip system.
  • the communication device 2000 may correspond to the second terminal device in the above method embodiment, for example, it may be the second terminal device, or a component (such as a chip) configured in the second terminal device. Or chip system).
  • the communication device 2000 may correspond to the second terminal device in the method 200, method 300, method 500, method 600, method 700, method 800, and method 900 according to the embodiments of the present application, and the communication device 2000 may include In performing the method 200 in FIG. 2, the method 300 in FIG. 3, the method 500 in FIG. 5, the method 600 in FIG. 6, the method 700 in FIG. 7, the method 800 in FIG. 8, and the method 900 in FIG. The unit of the method performed by the second terminal device. In addition, each unit in the communication device 2000 and other operations and/or functions described above are used to implement the method 200 in FIG. 2, the method 300 in FIG. 3, the method 500 in FIG. 5, the method 600 in FIG. 6, and the method 600 in FIG. 7 respectively.
  • the transceiver unit 2200 in the communication device 2000 may be implemented by a transceiver, for example, it may correspond to the transceiver 3020 in the terminal device 3000 shown in FIG. 11.
  • the processing unit 2100 in the communication device 2000 may be implemented by at least one processor, for example, may correspond to the processor 3010 in the terminal device 3000 shown in FIG. 11.
  • the transceiver unit 2200 in the communication device 2000 may be implemented through an input/output interface, and the processing unit 2100 in the communication device 2000 may It is realized by the processor, microprocessor or integrated circuit integrated on the chip or chip system.
  • the communication device 2000 may correspond to the first policy control network element in the above method embodiment, for example, may be the first policy control network element, or be configured in the first policy control network element Components in (such as chips or chip systems).
  • the communication device 2000 may correspond to the first policy control network element in the method 300, the method 600, the method 700, the method 800, and the method 900 according to the embodiments of the present application.
  • the units in the communication device 2000 and the other operations and/or functions described above are used to implement the method 300 in FIG. 3, the method 600 in FIG. 6, the method 700 in FIG. 7, the method 800 in FIG. 8, and the method 800 in FIG. 9 respectively.
  • the communication device 2000 may correspond to the second policy control network element in the above method embodiment, for example, it may be the second policy control network element, or be configured in the second policy control network element Components in (such as chips or chip systems).
  • the communication device 2000 may correspond to the second policy control network element in the method 500, the method 600, the method 700, the method 800, and the method 900 according to the embodiments of the present application.
  • the units in the communication device 2000 and the other operations and/or functions described above are respectively intended to implement the method 500 in FIG. 5, the method 600 in FIG. 6, the method 700 in FIG. 7, the method 800 in FIG. 8, and the method 800 in FIG.
  • FIG. 11 is a schematic structural diagram of a terminal device 3000 provided by an embodiment of the present application.
  • the terminal device 3000 can be applied to the system shown in FIG. 1 to perform the functions of the terminal device in the foregoing method embodiment.
  • the terminal device 3000 includes a processor 3010 and a transceiver 3020.
  • the terminal device 3000 further includes a memory 3030.
  • the processor 3010, the transceiver 3002, and the memory 3030 can communicate with each other through an internal connection path to transfer control and/or data signals.
  • the memory 3030 is used to store computer programs, and the processor 3010 is used to download from the memory 3030. Call and run the computer program to control the transceiver 3020 to send and receive signals.
  • the terminal device 3000 may further include an antenna 3040 for transmitting the uplink data or uplink control signaling output by the transceiver 3020 through a wireless signal.
  • the foregoing processor 3010 and the memory 3030 may be combined into a processing device, and the processor 3010 is configured to execute the program code stored in the memory 3030 to implement the foregoing functions.
  • the memory 3030 may also be integrated in the processor 3010 or independent of the processor 3010.
  • the processor 3010 may correspond to the processing unit 2100 in FIG. 10.
  • the foregoing transceiver 3020 may correspond to the transceiver unit 2200 in FIG. 10, and may also be referred to as a transceiver unit.
  • the transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.
  • the terminal device 3000 shown in FIG. 11 can implement various processes involving the first terminal device in the method embodiments shown in FIGS. 2, 3, 4, and 6-9.
  • the operations and/or functions of each module in the terminal device 3000 are respectively for implementing the corresponding processes in the foregoing method embodiments.
  • the above-mentioned processor 3010 may be used to execute the actions implemented by the first terminal device described in the foregoing method embodiments, such as determining whether the second parameter is the same or equivalent to the first parameter.
  • the transceiver 3020 may be used to perform the actions sent or received by the first terminal device described in the foregoing method embodiments, such as sending broadcast messages and request messages, receiving response messages, and so on. For details, please refer to the description in the previous method embodiment, which will not be repeated here.
  • terminal device 3000 shown in FIG. 11 can implement each process involving the second terminal device in the method embodiments shown in FIG. 2 and FIG. 4 to FIG. 9.
  • the operations and/or functions of each module in the terminal device 3000 are respectively for implementing the corresponding processes in the foregoing method embodiments.
  • the above-mentioned processor 3010 may be used to perform the actions described in the foregoing method embodiments implemented internally by the second terminal device, such as determining whether to support the provision of the relay service of the first application, and so on.
  • the transceiver 3020 may be used to perform the actions described in the foregoing method embodiments for the second terminal device to send to or receive from the first terminal device, such as sending broadcast messages and response messages, receiving request messages, and so on. For details, please refer to the description in the previous method embodiment, which will not be repeated here.
  • the aforementioned terminal device 3000 may further include a power supply 3050 for providing power to various devices or circuits in the terminal device.
  • the terminal device 3000 may also include one or more of the input unit 3060, the display unit 3070, the audio circuit 3080, the camera 3090, and the sensor 3100.
  • the audio circuit may also include a speaker 3082, a microphone 3084, and so on.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the method in any of the foregoing method embodiments.
  • the aforementioned processing device may be one or more chips.
  • the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or It is a central processor unit (CPU), it can also be a network processor (NP), it can also be a digital signal processing circuit (digital signal processor, DSP), or it can be a microcontroller (microcontroller unit). , MCU), it can also be a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processing circuit
  • microcontroller unit microcontroller unit
  • MCU programmable logic device
  • PLD programmable logic device
  • each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as execution and completion by a hardware processor, or execution and completion by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components .
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the present application also provides a computer program product.
  • the computer program product includes: computer program code.
  • the computer program code runs on a computer, the computer executes the steps shown in FIGS. 2-9. The method respectively performed by the first terminal device, the second terminal device, the first policy control network element, and the second policy control network element in the illustrated embodiment is shown.
  • the present application also provides a computer-readable medium that stores program code, and when the program code runs on a computer, the computer executes the steps shown in FIGS. 2 to 9
  • the method respectively performed by the first terminal device, the second terminal device, the first policy control network element, and the second policy control network element in the illustrated embodiment is shown.
  • the present application also provides a system, which includes the aforementioned one or more terminal devices and one or more policy control network elements.
  • the policy control network element in each of the above device embodiments completely corresponds to the policy control network element or terminal equipment in the terminal equipment and method embodiments, and the corresponding module or unit executes the corresponding steps, for example, the communication unit (transceiver) executes the method implementation In the example of receiving or sending steps, other steps except sending and receiving can be executed by the processing unit (processor).
  • the processing unit processor
  • the functions of specific units refer to the corresponding method embodiments. Among them, there may be one or more processors.
  • component used in this specification are used to denote computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution.
  • the component may be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a program, and/or a computer running on a processor.
  • the application running on the computing device and the computing device can be components.
  • One or more components may reside in processes and/or threads of execution, and components may be located on one computer and/or distributed among two or more computers.
  • these components can be executed from various computer readable media having various data structures stored thereon.
  • the component can be based on, for example, a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.
  • a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • each functional unit may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented by software, it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions (programs).
  • programs When the computer program instructions (programs) are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk, SSD)) etc.
  • a magnetic medium for example, a floppy disk, a hard disk, and a magnetic tape
  • an optical medium for example, a high-density digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state disk, SSD
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Abstract

本申请提供了一种建立连接和获取中继服务代码的方法。该方法包括：第一终端设备发送第一广播消息，该第一广播消息包括第一中继服务代码，该第一中继服务代码包括第一参数的信息，该第一参数是访问第一应用对应的参数，该第一应用是该第一终端设备待发起的应用；该第一终端设备接收来自第二终端设备的响应消息，该响应消息用于指示该第二终端设备支持以该第一参数访问该第一应用。第一终端设备根据该第一中继服务代码匹配到的第二终端设备，可以提供第一终端设备所需的中继服务。

Description

建立连接和获取中继服务代码的方法和通信装置
本申请要求于2019年12月30日提交中国专利局、申请号为201911391368.4、申请名称为“建立连接和获取中继服务代码的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，并且更具体地，涉及一种建立连接和获取中继服务代码的方法和通信装置。
背景技术
在第四代(4th generation，4G)系统中所定义的邻近中继方案中，远端用户设备(user equipment，UE)与中继UE通过预配置的中继服务代码(relay service code)建立PC5连接。远端UE与中继UE建立PC5连接之后，远端UE通过中继UE发起业务或应用时，中继UE基于自身所收到的用户路由选择策略(UE routing selection policy，URSP)规则为该业务或应用建立协议数据单元(protocol data unit，PDU)会话，即此时根据该业务或应用所选择的会话参数是运营商为中继UE所配置的会话参数。而对于远端UE而言，其可能开通了相应增值业务，或是订购了增值套餐，从而运营商为该远端UE配置的可以是优先级更高的会话参数。因此，远端UE基于当前预配置的中级服务代码匹配到中继UE，可能无法提供远端UE所需要的业务保障。
发明内容
本申请提供一种建立连接和获取中继服务代码的方法，根据本申请提供的方法，远端UE匹配的中继UE可以提供远端UE需要的业务保障。
第一方面，提供了一种建立连接的方法，该方法包括：第一终端设备发送第一广播消息，该第一广播消息包括第一中继服务代码，该第一中继服务代码包括第一参数的信息，该第一参数是访问第一应用对应的参数，该第一应用是该第一终端设备待发起的应用；该第一终端设备接收来自第二终端设备的响应消息，该响应消息用于指示该第二终端设备支持以该第一参数访问该第一应用。
基于上述技术方案，远端UE发送的第一广播消息中包括的第一中继服务代码可以包括第一参数的信息。因此，根据该第一广播消息匹配到的中继UE，能够以远端UE所需要的会话参数访问其待发起的应用，即该中继UE可以提供远端UE需要的业务保障。
结合第一方面，在第一方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：数据网络名称(data network name，DNN)、单切片选择辅助信息(single-network slice selection assistance information，S-NSSAI)、会话和服务连续(session and service continuity mode，SSC)模式、PDU会话类型、接入方式优先级、非第三代合作伙伴计划 (3rd Generation Partnership Project，3GPP)分流指示。
结合第一方面，在第一方面的某些实现方式中，该第一中继服务代码与该第一应用相关联。
结合第一方面，在第一方面的某些实现方式中，该第一中继服务代码与第二应用相关联，该第二应用是该第二终端设备支持中继服务的应用。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一终端设备通过接入和移动管理(access and mobility management function，AMF)网元向第一策略控制(policy control function，PCF)网元发送第一请求消息，该第一请求消息用于请求获取该第一中继服务代码；该第一终端设备接收来自该第一PCF网元的该第一中继服务代码。
结合第一方面，在第一方面的某些实现方式中，该第一请求消息包括以下信息：该第一终端设备的标识信息、请求类型、该应用的标识符。
结合第一方面，在第一方面的某些实现方式中，该第一请求消息还包括降级指示信息，该降级指示信息用于指示该第一终端设备是否接受服务降级。
第二方面，提供了一种建立连接的方法，该方法包括：第二终端设备接收第一广播消息，该第一广播消息包括第一中继服务代码，该第一中继服务代码包括第一参数的信息，该第一参数是访问第一应用对应的参数，该第一应用是该第一终端设备待发起的应用；该第二终端设备向该第一终端发送响应消息，该响应消息用于指示该第二终端设备支持以该第一参数访问该第一应用。
基于上述技术方案，远端UE发送的第一广播消息中包括的第一中继服务代码可以包括第一参数的信息。因此，根据该第一广播消息匹配到的中继UE，能够以远端UE所需要的会话参数访问其待发起的应用，即该中继UE可以提供远端UE需要的业务保障。
结合第二方面，在第二方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第二方面，在第二方面的某些实现方式中，在该第二终端设备向该第一终端设备发送响应消息之前，该方法还包括：该第二终端设备确定是否支持以该第一参数访问该第一应用。
结合第二方面，在第二方面的某些实现方式中，该第一中继服务代码与该第一应用相关联，该方法还包括：该第二终端设备根据该第一中继服务代码是否与第二中继服务代码相同或等同，确定是否支持以该第一参数访问该第一应用，该第二中继服务代码与该第一应用或第二应用相关联，该第二应用是该第二终端设备支持中继服务的应用，该第二中继服务代码是该第二终端设备保存的中继服务代码。
结合第二方面，在第二方面的某些实现方式中，该第一中继服务代码与第二应用相关联，该第二应用是该第二终端设备支持中继服务的应用，该方法还包括：该第二终端设备根据该第一中继服务代码是否与第二中继服务代码相同或等同，确定是否支持以该第一参数访问该第一应用，该第二中继服务代码与该第二应用相关联，该第二中继服务代码是该第二终端设备保存的中继服务代码。
第三方面，提供了一种获取中继服务代码的方法，该方法包括：第一PCF网元接收来自第一终端设备的第一请求消息，该第一请求消息用于请求获取第一中继服务代码，该第一中继服务代码包括第一参数的信息，该第一参数是访问第一应用对应的参数，该第一 应用是该第一终端设备待发起的应用；该第一PCF网元根据该第一参数决策该中继服务代码；该第一PCF网元通过AMF网元向该第一终端设备发送该第一中继服务代码。
基于上述技术方案，第一PCF根据远端UE的请求，可以为远端UE分配包括第一参数的信息的第一中继服务代码。进一步地，远端UE根据该第一中继服务代码匹配的中继UE可以提供远端UE需要的中继服务。
结合第三方面，在第三方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第三方面，在第三方面的某些实现方式中，该第一中继服务代码与该第一应用相关联，以及该第一PCF网元根据该第一参数决策该第一中继服务代码，包括：该第一PCF网元根据该第一参数和以下信息决策该第一中继服务代码：该第一终端设备的签约信息、该第一应用的标识符。
结合第三方面，在第三方面的某些实现方式中，该第一中继服务代码与该第一应用相关联，以及该第一PCF网元根据该第一参数决策该中继服务代码，包括：该第一PCF网元根据该第一参数和以下信息决策该第一中继服务代码：该第一终端设备的签约信息、该第一应用的标识符、降级指示信息，该降级指示信息用于指示该第一终端设备是否接受服务降级。
结合第三方面，在第三方面的某些实现方式中，该第一中继服务代码与第二应用相关联，该第二应用是该终端设备支持中继服务的应用，以及该第一PCF网元根据该第一参数决策该第一中继服务代码，包括：该第一PCF网元向第二PCF网元发送第二请求消息，该第二请求消息用于请求获取第二中继服务代码，该第二中继服务代码与该第二应用相关联，该请求消息包括该第一参数和该第一应用的标识符；该第一PCF网元接收来自该第二PCF网元的该第二中继服务代码；该第一PCF网元根据该第二中继服务代码决策该第一中继服务代码。
基于上述技术方案，第一PCF可以为远端UE分配与中继UE相关联的第一中继服务代码，并且该第一中继服务代码对应的中继UE可以提供远端UE需要的中继服务。因此，远端UE根据该第一中继服务代码匹配的中继UE可以满足远端UE的需求。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该第一PCF网元向该统一数据仓库(unified data repository，UDR)网元发送第三请求消息，该第三请求消息用于请求获取第二PCF的信息；该第一PCF网元接收来自该UDR网元的该第二PCF的信息。
结合第三方面，在第三方面的某些实现方式中，该第一请求消息包括以下信息：该第一终端设备的标识信息、请求类型、该第一应用的标识符。
结合第三方面，在第三方面的某些实现方式中，该第一请求消息还包括降级指示信息，该降级指示信息用于指示该第一终端设备是否接受服务降级。
第四方面，提供了一种建立连接的方法，该方法包括：第一终端设备发送第一广播消息，该第一广播消息包括第三中继服务代码和第一参数，该第一参数是访问第一应用对应的参数，该第一应用是该第一终端设备待发起的应用；该第一终端设备接收来自第二终端设备的响应消息，该响应消息用于指示该第二终端设备支持以该第一参数访问该第一应用。
基于上述技术方案，远端UE发送的第一广播消息中可以包括第一参数的信息。因此，根据该第一广播消息匹配到的中继UE，能够以远端UE所需要的会话参数访问其待发起的应用，即该中继UE可以提供远端UE需要的业务保障。
结合第四方面，在第四方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型。
第五方面，提供了一种建立连接的方法，该方法包括：第二终端设备发送第二广播消息，该第二广播消息包括第二中继服务代码，该第二中继服务代码包括第二参数的信息，该第二参数是访问第二应用对应的参数，该第二应用是该第二终端设备支持中继服务的应用；该第二终端设备接收来自第一终端设备的第四请求消息，该第四请求消息用于请求与该第二终端设备建立PC5连接。
基于上述技术方案，中继UE发送的第二广播消息中包括的第二中继服务代码可以包括第二参数的信息。因此，该中继UE可以以根据该第二广播消息匹配到的远端UE所需要的会话参数，访问远端UE待发起的应用，即该中继UE可以提供远端UE需要的业务保障。
结合第五方面，在第五方面的某些实现方式中，该第二参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第五方面，在第五方面的某些实现方式中，该第二中继服务代码与该第二应用相关联。
结合第五方面，在第五方面的某些实现方式中，该第二中继服务代码与第一应用相关联，该第一应用是该第一终端设备待发起应用。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：该第二终端设备通过AMF网元向第二PCF网元发送第五请求消息，该第五请求消息用于请求获取该第二中继服务代码；该第二终端设备接收来自该第二PCF网元的该第二中继服务代码。
结合第五方面，在第五方面的某些实现方式中，该第五请求消息包括以下信息：该第二终端设备的标识信息、请求类型、该第二应用的标识符。
第六方面，提供了一种建立连接的方法，该方法包括：第一终端设备接收第二广播消息，该第二广播消息包括第二中继服务代码，该第二中继服务代码包括第二参数的信息，该第二参数是访问第二应用对应的参数，该第二应用是该第二终端设备支持中继服务的应用；该第一终端设备向该第二终端设备发送第四请求消息，该第四请求消息用于请求与该第二终端设备建立PC5连接。
基于上述技术方案，中继UE发送的第二广播消息中包括的第二中继服务代码可以包括第二参数的信息。因此，该中继UE可以以根据该第二广播消息匹配到的远端UE所需要的会话参数，访问远端UE待发起的应用，即该中继UE可以提供远端UE需要的业务保障。
结合第六方面，在第六方面的某些实现方式中，该第二参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第六方面，在第六方面的某些实现方式中，在该第二终端设备向该第一终端设备发送第四请求消息之前，该方法还包括：该第一终端设备确定该第二终端设备是否支持以第一参数访问第一应用，该第一应用是该第一终端设备待发起的应用，该第一参数是访问 该第一应用对应的参数。
结合第六方面，在第六方面的某些实现方式中，该第二中继服务代码与该第二应用相关联，该方法还包括：该第一终端设备根据该第二中继服务代码是否与第一中继服务代码相同或等同，确定该第二终端设备是否支持以第一参数访问该第二应用，该第一中继服务代码是该第一终端设备保存的中继服务代码，该第一中继服务代码与该第二应用或第一应用相关联，该第一应用是该第一终端设备待发起的应用，该第一参数是访问该第一应用对应的参数。
结合第六方面，在第六方面的某些实现方式中，该第二中继服务代码与第一应用相关联，该第一应用是该第一终端设备待发起的应用，该方法还包括：该第一终端设备根据该第二中继服务代码是否与第一中继服务代码相同或等同，确定该第二终端设备是否支持以第一参数访问该第一应用，该第一中继服务代码是该第一终端设备保存的中继服务代码，该第二中继服务代码与该第一应用相关联，该第一参数是访问该第一应用对应的参数。
结合第六方面，在第六方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
第七方面，提供了一种获取中继服务代码的方法，该方法包括：第二PCF网元接收来自第二终端设备的第五请求消息，该第五请求消息用于请求获取第二中继服务代码，该第二中继服务代码包括第二参数的信息，该第二参数是访问第二应用对应的参数，该第二应用是该第二终端设备支持中继服务的应用；该第二PCF网元根据该第二参数决策该第二中继服务代码；该第二PCF网元通过AMF网元向该第二终端设备发送该第二中继服务代码。
基于上述技术方案，第二PCF根据中继UE的请求，可以为中继UE分配包括第二参数的信息的第二中继服务代码。进一步地，中继UE可以为根据该第一中继服务代码匹配的远端UE提供其需要的中继服务。
结合第七方面，在第七方面的某些实现方式中，该第二参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第七方面，在第七方面的某些实现方式中，该第二中继服务代码与该第二应用相关联，以及该第二PCF网元根据该第二参数决策该第二中继服务代码，包括：该第二PCF网元根据该第二参数和以下信息决策该第二中继服务代码：该第二终端设备的签约信息、该第二应用的标识符。
结合第七方面，在第七方面的某些实现方式中，该第二中继服务代码与该第二应用相关联，以及该第二PCF网元根据该第二参数决策该第二中继服务代码，包括：该第二PCF网元根据该第二参数和以下信息决策该第二中继服务代码：该第二终端设备的签约信息、该第二应用的标识符。
结合第七方面，在第七方面的某些实现方式中，该第二中继服务代码与第一应用相关联，该第一应用是该第一终端设备待发起应用，以及该第二PCF网元根据该第二参数决策该第二中继服务代码，包括：该第二PCF网元向第一PCF网元发送第六请求消息，该第六请求消息用于请求获取第一中继服务代码，该第一中继服务代码与该第一应用相关联，该第六请求消息包括该第二参数和该第二应用的标识符；该第二PCF网元接收来自该第一PCF网元的该第一中继服务代码；该第二PCF网元根据该第一中继服务代码决策 该第二中继服务代码。
基于上述技术方案，第二PCF可以为中继UE分配与远端UE相关联的第二中继服务代码，并且该中继UE可以为该第二中继服务代码对应的远端UE提供其需要的中继服务。
结合第七方面，在第七方面的某些实现方式中，该方法还包括：该第二PCF网元向UDR网元发送第七请求消息，该第七请求消息用于请求获取第一PCF的信息；该第二PCF网元接收来自该UDR网元的该第一PCF的信息。
结合第七方面，在第七方面的某些实现方式中，该第五请求消息包括以下信息：该第二终端设备的标识信息、请求类型、该第二应用的标识符。
第八方面，提供了一种建立连接的方法，该方法包括：
第二终端设备发送第二广播消息，该第二广播消息包括第二中继服务代码和第二参数，该第二参数是访问第二应用对应的参数，该第二应用是该第二终端设备支持中继服务的应用；该第二终端设备接收来自第一终端设备的请求消息，该请求消息用于请求与该第二终端设备建立PC5连接。
基于上述技术方案，中继UE发送的第二广播消息中可以包括第二参数的信息。因此，该中继UE可以以根据该第二广播消息匹配到的远端UE所需要的会话参数，访问远端UE待发起的应用，即该中继UE可以提供远端UE需要的业务保障。
结合第八方面，在第八方面的某些实现方式中，该第二参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
第九方面，提供了一种通信装置，该通信装置包括收发单元：该收发单元用于：发送第一广播消息，该第一广播消息包括第一中继服务代码，该第一中继服务代码包括第一参数的信息，该第一参数是访问第一应用对应的参数，该第一应用是该通信装置待发起的应用；该收发单元还用于：接收来自第二终端设备的响应消息，该响应消息用于指示该第二终端设备支持以该第一参数访问该第一应用。
结合第九方面，在第九方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NSSAI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第九方面，在第九方面的某些实现方式中，该第一中继服务代码与该第一应用相关联。
结合第九方面，在第九方面的某些实现方式中，该第一中继服务代码与第二应用相关联，该第二应用是该第二终端设备支持中继服务的应用。
结合第九方面，在第九方面的某些实现方式中，该收发单元还用于：通过AMF网元向第一PCF网元发送第一请求消息，该第一请求消息用于请求获取该第一中继服务代码；该第一终端设备接收来自该第一PCF网元的该第一中继服务代码。
结合第九方面，在第九方面的某些实现方式中，该第一请求消息包括以下信息：该通信装置的标识信息、请求类型、该第一应用的标识符。
结合第九方面，在第九方面的某些实现方式中，该第一请求消息还包括降级指示信息，该降级指示信息用于指示该通信装置是否接受服务降级。
第十方面，提供了一种通信装置，该通信装置包括收发单元和处理单元：该收发单元用于：接收第一广播消息，该第一广播消息包括第一中继服务代码，该第一中继服务代码包括第一参数的信息，该第一参数是访问第一应用对应的参数，该第一应用是该第一终端 设备待发起的应用；该收发单元还用于：向该第一终端发送响应消息，该响应消息用于指示该通信装置支持以该第一参数访问该第一应用。
结合第十方面，在第十方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第十方面，在第十方面的某些实现方式中，该处理单元用于：确定是否支持以该第一参数访问该第一应用。
结合第十方面，在第十方面的某些实现方式中，该第一中继服务代码与该第一应用相关联，该处理单元还用于：根据该第一中继服务代码是否与第二中继服务代码相同或等同，确定是否支持以该第一参数访问该第一应用，该第二中继服务代码与该第一应用或第二应用相关联，该第二应用是该通信装置支持中继服务的应用，该第二中继服务代码是该通信装置保存的中继服务代码。
结合第十方面，在第十方面的某些实现方式中，该第一中继服务代码与第二应用相关联，该第二应用是该通信装置支持中继服务的应用，该处理单元还用于：根据该第一中继服务代码是否与第二中继服务代码相同或等同，确定是否支持以该第一参数访问该第一应用，该第二中继服务代码与该第二应用相关联，该第二中继服务代码是该通信装置保存的中继服务代码。
第十一方面，提供了一种通信装置，该通信装置包括收发单元和处理单元：该收发单元用于：接收来自第一终端设备的第一请求消息，该第一请求消息用于请求获取第一中继服务代码，该第一中继服务代码包括第一参数的信息，该第一参数是访问第一应用对应的参数，该第一应用是该第一终端设备待发起的应用；该处理单元用于：根据该第一参数决策该中继服务代码；该收发单元还用于：通过AMF网元向该第一终端设备发送该第一中继服务代码。
结合第十一方面，在第十一方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第十一方面，在第十一方面的某些实现方式中，该第一中继服务代码与该第一应用相关联，以及该处理单元具体用于：根据该第一参数和以下信息决策该第一中继服务代码：该第一终端设备的签约信息、该第一应用的标识符。
结合第十一方面，在第十一方面的某些实现方式中，该第一中继服务代码与该第一应用相关联，以及该处理单元具体用于：根据该第一参数和以下信息决策该第一中继服务代码：该第一终端设备的签约信息、该第一应用的标识符、降级指示信息，该降级指示信息用于指示该第一终端设备是否接受服务降级。
结合第十一方面，在第十一方面的某些实现方式中，该第一中继服务代码与第二应用相关联，该第二应用是该终端设备支持中继服务的应用，以及该收发单元用于：向第二PCF网元发送第二请求消息，该第二请求消息用于请求获取第二中继服务代码，该第二中继服务代码与该第二应用相关联，该第二请求消息包括该第一参数和该第一应用的标识符；该收发单元还用于：接收来自该第二PCF网元的该第二中继服务代码；该处理单元用于：根据该第二中继服务代码决策该第一中继服务代码。
结合第十一方面，在第十一方面的某些实现方式中，该收发单元还用于：向该UDR 网元发送第三请求消息，该第三请求消息用于请求获取第二PCF的信息；该收发单元还用于：接收来自该UDR网元的该第二PCF的信息。
结合第十一方面，在第十一方面的某些实现方式中，该第一请求消息包括以下信息：该第一终端设备的标识信息、请求类型、该第一应用的标识符。
结合第十一方面，在第十一方面的某些实现方式中，该第一请求消息还包括降级指示信息，该降级指示信息用于指示该第一终端设备是否接受服务降级。
第十二方面，提供了一种通信装置，该通信装置包括收发单元：该收发单元用于：发送第一广播消息，该第一广播消息包括第一中继服务代码和第一参数，该第一参数是访问第一应用对应的参数，该第一应用是该通信装置待发起的应用；该收发单元还用于：接收来自第二终端设备的响应消息，该响应消息用于指示该第二终端设备支持以该第一参数访问该第一应用。
结合第十二方面，在第十二方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型。
第十三方面，提供了一种通信装置，该通信装置包括收发单元：该收发单元用于：发送第二广播消息，该第二广播消息包括第二中继服务代码，该第二中继服务代码包括第二参数的信息，该第二参数是访问第二应用对应的参数，该第二应用是该通信装置支持中继服务的应用；该收发单元还用于：接收来自第一终端设备的第四请求消息，该第四请求消息用于请求与该通信装置建立PC5连接。
结合第十三方面，在第十三方面的某些实现方式中，该第二参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第十三方面，在第十三方面的某些实现方式中，该第二中继服务代码与该第二应用相关联。
结合第十三方面，在第十三方面的某些实现方式中，该第二中继服务代码与第一应用相关联，该第一应用是该第一终端设备待发起应用。
结合第十三方面，在第十三方面的某些实现方式中，该收发单元还用于：通过AMF网元向第二PCF网元发送第五请求消息，该第五请求消息用于请求获取该第二中继服务代码；收发单元还用于：接收来自该第二PCF网元的该第二中继服务代码。
结合第十三方面，在第十三方面的某些实现方式中，该第五请求消息包括以下信息：该第二终端设备的标识信息、请求类型、该第二应用的标识符。
第十四方面，提供了一种通信装置，该通信装置包括收发单元和处理单元：该收发单元用于：接收第二广播消息，该第二广播消息包括第二中继服务代码，该第二中继服务代码包括第二参数的信息，该第二参数是访问第二应用对应的参数，该第二应用是第二终端设备支持中继服务的应用；该收发单元向该第二终端设备发送第四请求消息，该第四请求消息用于请求与该第二终端设备建立PC5连接。
结合第十四方面，在第十四方面的某些实现方式中，该第二参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第十四方面，在第十四方面的某些实现方式中，在该收发单元向该第二终端设备 发送第四请求消息之前，该处理单元用于：确定该第二终端设备是否支持以第一参数访问第一应用，该第一应用是该通信装置待发起的应用，该第一参数是访问该第一应用对应的参数。
结合第十四方面，在第十四方面的某些实现方式中，该第二中继服务代码与该第二应用相关联，该处理单元还用于：根据该第二中继服务代码是否与第一中继服务代码相同或等同，确定该第二终端设备是否支持以第一参数访问该第二应用，该第一中继服务代码是该通信装置保存的中继服务代码，该第一中继服务代码与该第二应用或第一应用相关联，该第一应用是该通信装置待发起的应用，该第一参数是访问该第一应用对应的参数。
结合第十四方面，在第十四方面的某些实现方式中，该第二中继服务代码与第一应用相关联，该第一应用是该通信装置待发起的应用，该处理单元还用于：根据该第二中继服务代码是否与第一中继服务代码相同或等同，确定该第二终端设备是否支持以第一参数访问该第一应用，该第一中继服务代码是该通信装置保存的中继服务代码，该第二中继服务代码与该第一应用相关联，该第一参数是访问该第一应用对应的参数。
结合第十四方面，在第十四方面的某些实现方式中，该第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
第十五方面，提供了一种通信装置，该通信装置包括收发单元和处理单元：该收发单元用于：接收来自第二终端设备的第五请求消息，该第五请求消息用于请求获取第二中继服务代码，该第二中继服务代码包括第二参数的信息，该第二参数是访问第二应用对应的参数，该第二应用是该第二终端设备支持中继服务的应用；该处理单元用于：根据该第二参数决策该第二中继服务代码；该收发单元还用于：通过AMF网元向该第二终端设备发送该第二中继服务代码。
结合第十五方面，在第十五方面的某些实现方式中，该第二参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
结合第十五方面，在第十五方面的某些实现方式中，该第二中继服务代码与该第二应用相关联，以及该处理单元具体用于：根据该第二参数和以下信息决策该第二中继服务代码：该第二终端设备的签约信息、该第二应用的标识符。
结合第十五方面，在第十五方面的某些实现方式中，该第二中继服务代码与该第二应用相关联，以及该处理单元具体用于：根据该第二参数和以下信息决策该第二中继服务代码：该第二终端设备的签约信息、该第二应用的标识符。
结合第十五方面，在第十五方面的某些实现方式中，该第二中继服务代码与第一应用相关联，该第一应用是该第一终端设备待发起应用，以及该收发单元用于：向第一PCF网元发送第六请求消息，该第六请求消息用于请求获取第一中继服务代码，该第一中继服务代码与该第一应用相关联，该第六请求消息包括该第二参数和该第二应用的标识符；该收发单元还用于：接收来自该第一PCF网元的该第一中继服务代码；该处理单元用于：根据该第一中继服务代码决策该第二中继服务代码。
结合第十五方面，在第十五方面的某些实现方式中，该收发单元还用于：向UDR网元发送第七请求消息，该第七请求消息用于请求获取第一PCF的信息；该收发单元还用 于：接收来自所述UDR网元的所述第一PCF的信息。
结合第十五方面，在第十五方面的某些实现方式中，该第五请求消息包括以下信息：该第二终端设备的标识信息、请求类型、该第二应用的标识符。
第十六方面，提供了一种通信装置，该通信装置包括收发单元：该收发单元用于：发送第二广播消息，该第二广播消息包括第二中继服务代码和第二参数，该第二参数是访问第二应用对应的参数，该第二应用是该通信装置支持中继服务的应用；该通信装置还用于：接收来自第一终端设备的请求消息，该请求消息用于请求与该通信装置建立PC5连接。
结合第十六方面，在第十六方面的某些实现方式中，该第二参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
第十七方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第一方面以及第一方面中任一种可能实现方式、第四方面以及第四方面中任一种可能实现方式、第六方面以及第六方面中任一种可能实现方式中的方法。其中，该通信装置还包括存储器。其中，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为第一终端设备。当该通信装置为第一终端设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于第一终端设备中的芯片或芯片系统。当该通信装置为配置于第一终端设备中的芯片或芯片系统时，该通信接口可以是输入/输出接口。
其中，该收发器可以为收发电路。其中，该输入/输出接口可以为输入/输出电路。
第十八方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第二面以及第二方面中任一种可能实现方式、第五方面以及第五方面中任一种可能实现方式、第八方面以及第八方面中任一种可能实现方式中的方法。其中，该通信装置还包括存储器。其中，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为第二终端设备。当该通信装置为第二终端设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于第二终端设备中的芯片或芯片系统。当该通信装置为配置于第二终端设备中的芯片或芯片系统时，该通信接口可以是输入/输出接口。
其中，所述收发器可以为收发电路。其中，所述输入/输出接口可以为输入/输出电路。
第十九方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第三方面以及第三方面中任一种可能实现方式中的方法。其中，该通信装置还包括存储器。其中，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为第一PCF网元。当该通信装置为第一PCF网元时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于第一PCF网元中的芯片或芯片系统。当 该通信装置为配置于第一PCF网元中的芯片或芯片系统时，该通信接口可以是输入/输出接口。
其中，该收发器可以为收发电路。其中，该输入/输出接口可以为输入/输出电路。
第二十方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第七方面以及第七方面中任一种可能实现方式中的方法。其中，该通信装置还包括存储器。其中，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为第二PCF网元。当该通信装置为第二PCF网元时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于第二PCF网元中的芯片或芯片系统。当该通信装置为配置于第二PCF网元中的芯片或芯片系统时，该通信接口可以是输入/输出接口。
其中，该收发器可以为收发电路。其中，该输入/输出接口可以为输入/输出电路。
第二十一方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发送信号，使得所述处理器执行第一方面至第八方面以及第一方面至第八方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第二十二方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第八方面以及第一方面至第八方面中任一种可能实现方式中的方法。
其中，该处理器为一个或多个，该存储器为一个或多个。
其中，该存储器可以与所述处理器集成在一起，或者该存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第二十二方面中的处理装置可以是一个或多个芯片，或者，也可以是一个芯片系统。该处理装置中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中， 可以位于该处理器之外，独立存在。
第二十三方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得执行上述第一方面至第八方面以及第一方面至第八方面中任一种可能实现方式中的方法。
第二十四方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第八方面以及第一方面至第八方面中任一种可能实现方式中的方法。
第二十五方面，提供了一种通信系统，包括：前述的第一终端设备，第二终端设备，和/或，前述的第一PCF网元，和/或，前述的第二PCF网元。
附图说明
图1适用于本申请实施例提供的方法的应用场景的示意图。
图2是本申请实施例提供的建立连接的方法的示意性流程图。
图3是本申请实施例提供的获取中继服务代码的方法的示意性流程图。
图4是本申请实施例提供的建立连接的方法的示意性流程图。
图5是本申请实施例提供的获取中继服务代码的方法的示意性流程图。
图6至图9是本申请实施例提供的建立连接的方法的示意性流程图。
图10是本申请实施例提供的通信装置的示意性框图。
图11是本申请实施例提供的终端设备的结构示意图。
具体实施方式
下面结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、第五代(5th Generation，5G)系统或新无线(New Radio，NR)、或未来的通信系统等。
应理解，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端或网络侧设备，或者，是用户设备或网络侧设备中能够调用程序并执行程序的功能模块。
为便于理解本申请实施例，首先结合图1详细说明本申请实施例的一个应用场景。
图1是适用于本申请实施例提供的方法的网络架构的示意图。如图所示，该网络架构具体可以包括下列网元：
1、用户设备(user equipment，UE)：可以称终端设备、终端、接入终端、用户单元、 用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。如图1所示，图中示出了UE#A和UE#B。其中，UE#B通过Uu接口与下一代无线接入网(next generation radio access network，NG-RAN)相连，然后UE#B再通过NG-RAN接入到5G核心网(5G core network，5GC)。UE#A通过PC5接口与UE#B相连。
2、接入网(access network，AN)：为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道。接入网络可以为采用不同接入技术的接入网络。目前的无线接入技术有两种类型：3GPP接入技术和非第三代合作伙伴计划(non-3GPP)接入技术。其中，3GPP接入技术，例如第三代(3rd generation，3G)系统中采用的无线接入网技术、4G系统中采用的无线接入网技术、或图1中的NG-RAN技术(如5G系统中采用的无线接入技术)。3GPP接入技术是指符合3GPP标准规范的接入技术，采用3GPP接入技术的接入网络称为无线接入网络(radio access network，RAN)。其中，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)。非3GPP接入技术是指不符合3GPP标准规范的接入技术，例如，以wifi中的接入点(access point，AP)为代表的空口技术。
基于无线通信技术实现接入网络功能的接入网可以称为无线接入网(radio access network，RAN)。无线接入网能够管理无线资源，为终端提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
无线接入网例如可以是基站(NodeB)、演进型基站(evolved NodeB，eNB或eNodeB)、5G移动通信系统中的基站(gNB)、未来移动通信系统中的基站或WiFi系统中的AP等，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该接入网设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等。本申请的实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
3、接入和移动管理功能(access and mobility management function，AMF)实体：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。在本申请实施例中，可用于实现接入和移动管理网元的功能。
4、会话管理功能(session management function，SMF)实体：主要用于会话管理、UE的网际协议(Internet Protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中，可用于实现会话管理网元的功能。
5、用户平面功能(User Plane Function，UPF)实体：即，数据面网关。可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。用户数据可通 过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网关的功能。
6、数据网络(DN)：用于提供传输数据的网络。例如，运营商业务的网络、因特(Internet)网、第三方的业务网络等。如图1中示出了第三方部署的应用服务器。
7、网络开放功能(network exposure function，NEF)实体：用于安全地向外部开放由3GPP网络功能提供的业务和能力等。
8、策略控制功能(policy control function，PCF)实体：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
9、统一数据管理(unified data management，UDM)实体：用于统一数据管理、5G用户数据管理、处理用户标识、接入鉴权、注册、或移动性管理等。
10、应用功能(application function，AF)实体：用于进行应用影响的数据路由，接入网络开放功能网元，或，与策略框架交互进行策略控制等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP multimedia subsystem，IMS)语音呼叫业务。对于第三方应用的应用功能实体，其与核心网进行交互时还可经由NEF实体进行授权处理，例如第三方应用功能直接向NEF实体发送请求消息，NEF实体判断该AF实体是否被允许发送该请求消息，若验证通过，则将转发该请求消息至对应PCF实体或UDM实体。
11、统一数据仓库(unified data repository，UDR)实体：用于签约数据、策略数据、应用数据等类型数据的存取。
在该网络架构中，N6接口为UPF实体和DN之间的参考点，用于传输用户面的数据等。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1中所示的AMF实体、SMF实体、UPF实体、NEF实体、PCF实体、UDM实体、AF实体、UDR实体可以理解为核心网中用于实现不同功能的网元，例如可以按需组合成网络切片。这些核心网网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，本申请对此不做限定。
下文中，为便于说明，将用于实现AMF的实体记作接入和移动管理网元，将用于实现SMF的实体记作会话管理网元，将用于实现UPF的实体记作用户面网关，将用于实现UDR功能的实体记作统一数据仓库网元，将用于实现PCF的实体记作策略控制网元。应理解，上述命名仅为用于区分不同的功能，并不代表这些网元分别为独立的物理设备，本申请对于上述网元的具体形态不作限定，例如，可以集成在同一个物理设备中，也可以分别是不同的物理设备。此外，上述命名仅为便于区分不同的功能，而不应对本申请构成任何限定，本申请并不排除在5G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。在此进行统一说明，以下不再赘述。
还应理解，图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息 (或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
在UE建立PDU会话的过程中，UE可以基于一定的URSP规则建立PDU会话。其中，URSP规则仅支持由归属地策略控制功能(home-policy control function，H-PCF)实体提供，URSP规则主要用于UE决策如何为待传输的业务数据流选择路由策略，例如，该待传输的业务数据流是否支持分流至non-3GPP接入，或者，为该待传输的业务数据流选择特定的DNN、S-NSSAI、SSC模式、PDU会话类型等信息。
URSP的结构主要由两部分内容组成：流量描述符(traffic descriptor)，定义URSP中可用于流量识别的特性；路由选择描述符列表(list of route selection descriptor)。
UE执行URSP匹配的过程可简要描述如下：
当UE判断需发起特定的业务/应用时，将按照URSP规则的优先级，按顺序对待发起的业务/应用与UE所收到的URSP规则中的流量描述符进行匹配，若匹配到具体的URSP规则(该匹配到的URSP规则可能是默认的规则，即该URSP规则中的流量描述符与所有的业务/应用都匹配)，则UE继续判断是否已有PDU会话符合该匹配到的URSP规则中的路由选择描述符的定义。
若已有PDU会话所对应的DNN、S-NASSI、SSC模式、PDU会话类型等信息与待发起的业务/应用所对应的DNN、S-NASSI、SSC模式等PDU会话类型信息一致，则UE可以选择在已有的PDU会话基础上发起PDU会话修改请求。PDU会话修改请求消息中可以携带以下参数：PDU会话标识符、N1接口会话管理容器(N1 SM Container)。其中，PDU会话标识符用于接入和移动管理网元关联至具体会话上下文，N1 SM Container则由接入和移动管理网元透传至会话管理网元。其中，N1 SM Container包括PDU会话修改请求，PDU会话修改请求中包括：PDU会话标识符、分组过滤器、操作、请求的服务质量(service of quality，QoS)。
若已有的PDU所对应的DNN、S-NASSI、SSC模式、PDU会话类型等信息均无法与待发起的业务/应用所对应的DNN、S-NASSI、SSC模式、PDU会话类型等信息匹配，则UE将为该待发起的业务/应用发起PDU会话建立请求。PDU会话建立请求消息中可以携带以下参数：新分配的PDU会话标识符、DNN、S-NASSI、N1 SM Container。其中，新分配的PDU会话标识符用于标识该PDU会话建立请求所对应的PDU会话，DNN和S-NASSI作为接入与移动管理网元为该PDU会话建立请求选择会话管理网元的参数，N1 SM Container则由接入和移动管理网元透传至所选择的会话管理网元。其中，N1 SM Container包括SSC模式、PDU会话类型。
在中继接入场景下，当UE处于运营商网络覆盖较弱的边缘区域，或者处于运营商网络覆盖范围之外的情况下，若该UE需发起特定的业务或应用，则可以通过与邻近的UE建立PC5连接，从而间接地接入到5G网络中。例如，图1所示的UE#A在需要发起特定的业务或应用的情况下，可以通过与UE#B建立PC5连接，从而接入到5GC中。
为了便于理解，后文将使用中继服务的UE记为远端(remote)UE，将为远端UE提供中继服务的UE记为中继(relay)UE。例如，图1所示的UE#A对应的是远端UE，UE#B对应的是中继UE。
远端UE与中继UE建立PC5连接的方式有以下两种：
模式A：
中继UE根据从策略控制网元收到的频点信息在相应的频带上发送广播消息，该广播消息可以包括：(a)中继UE的标识符：链路层标识符(link layer identifier)；(b)中继UE的信息：可以包括中继UE的层2标识或应用层用户信息；(c)中继服务代码：可以包括业务信息、安全策略，可选地，还可以包括授权允许接入的UE列表。其中，中继服务代码是中继UE本地预配置的。
相对应地，远端UE根据从策略控制网元收到的频点信息在相应的频带对广播消息进行监听。进一步地，远端UE对监听到的广播信息中的中继服务代码进行解析，若监听到的中继服务代码能与远端UE本地预配置的中继服务代码对应，则远端UE可以判断该中继UE能够提供远端UE所需要发起的应用或业务的中继服务。再进一步地，远端UE向该中继UE发起PC5建立请求，从而与该中继UE建立PC5连接。
模式B：
远端UE根据从策略控制网元收到的频点信息在相应的频带上发送广播消息，该广播消息可以包括：(a)远端UE的信息：可以包括远端UE的链路层标识或应用层用户信息；(b)中继服务代码：可以包括业务信息、安全策略。其中，中继服务代码是远端UE本地预配置的。若远端UE能够预先获取到中继UE的标识符，则该广播信息中还可以包括中继UE的标识符。
相对应地，中继UE根据从策略控制网元收到的频点信息在相应的频带对广播消息进行监听。进一步地，中继UE对监听到的广播消息中的中继服务代码进行解析，若监听到的中继服务代码能与中继UE本地预配置的中继服务代码对应，则中继UE可以判断自身能够为远端UE提供远端UE需要发起的应用或业务的中继服务。
进一步地，中继UE向远端UE发送响应消息，该响应消息可以包括：(a)中继UE的标识符：链路层标识符；(b)远端UE的信息。相对应地，远端UE接收到该响应消息之后，向中继UE发起PC5建立请求，从而与该中继UE建立PC5连接。
其中，远端UE本地预配置的中继服务代码与中继UE本地配置的中继服务代码对应可以理解为，远端UE本地配置的中继服务代码与中继UE本地预配置的中继服务代码相同，或者等同，又或者通过特定的加密/解密算法可以得到对等信息，例如远端UE的中继服务代码与中继UE的中继服务代码对应同一个应用标识符(application identifier)。
在4G系统中所定义的邻近中继方案中，由于中继业务仅用于公共安全业务，因此远端UE与中继UE中所保存的中继服务代码为预配置方式，且中继服务代码与公共安全业务直接关联。然而在当前5G系统的讨论中，中继业务不再局限于公共安全场景，若继续沿用预配置中继服务代码的方式，可能会导致中继业务无法反应实际应用，且不具备动态调整的灵活性。
除此之外，当前远端UE在通过中继UE发起业务或应用时，中继UE基于自身所收到的URSP规则为该业务或应用建立PDU会话，即此时根据该业务或应用所选择的DNN、S-NASSI、SSC模式、PDU会话类型等信息是运营商为中继UE所配置的参数。而对于远端UE而言，其可能开通了相应增值业务，或是订购了增值套餐，从而运营商为该远端UE配置的可以是优先级更高的DNN、S-NASSI、SSC模式、PDU会话类型等信息。若远端UE基于上文所述的方法匹配中继UE，则匹配到的中继UE可能无法提供远端UE所需要的业务保障。
有鉴于此，本申请实施例提供一种建立连接的方法，可以使远端UE能够匹配到支持以远端UE需要的方式接入特定的应用服务的中继UE。
下面将结合附图详细说明本申请实施例提供的方法。
需要说明的是，在下文中结合附图描述实施例的过程中，图中仅为便于理解而示意，不应对本申请构成任何限定。此外，图中示出AMF可对应于接入和移动管理网元，UDR可对应于统一数据仓库网元，PCF可对应于策略管理网元。各网元名称仅为区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除定义其他网元来实现相同或相似功能的可能。
还需要说明的是，本申请实施例中提及的第一中继服务代码对应于UE#A(远端UE)保存的中继服务代码。该第一中继服务代码的具体内容可以有多种，例如，该第一中继服务代码(对应于下文中的中继服务代码#1)可以与UE#A待发起的应用相关联，且不包括第一参数的信息；或者，该第一中继服务代码(对应于下文中的中继服务代码#2)可以与UE#A待发起的应用或UE#B支持中继服务的应用相关联，且包括第一参数的信息；又或者，该第一中继服务代码(对应于下文中的中继服务代码#3)可以与UE#B支持中继服务的应用相关联，且不包括第一参数的信息。这里的第一参数可以是以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
还需要说明的是，本申请实施例中提及的第二中继服务代码对应于UE#B(中继UE)保存的中继服务代码。该第二中继服务代码的具体内容可以有多种，例如，该第二中继服务代码(对应于下文中的中继服务代码#4)可以与UE#B支持中继服务的应用相关联，且不包括第二参数的信息；或者，该第二中继服务代码(对应于下文中的中继服务代码#5)可以与UE#A待发起的应用或UE#B支持中继服务的应用相关联，且包括第二参数的信息；又或者，该第二中继服务代码(对应于下文中的中继服务代码#6)可以与UE#A待发起的应用相关联，且不包括第二参数的信息。这里的第二参数可以是以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
还需要说明的是，本申请实施例提及的应用包括应用和/或业务。
图2示出了本申请实施例提供的建立连接的方法的示意性流程图。图2所示的方法可以由图1所示的系统中的UE#A和UE#B执行，其中UE#A对应于第一终端设备，UE#B对应于第二终端设备。该方法200中所描述的UE#A与UE#B建立连接的方法对应于模式B，即由远端UE发送广播消息。如图2所示，该方法包括S210和S220。下面详细描述每个步骤。
S210，UE#A发送第一广播消息。
UE#A可以根据从为其服务的策略控制网元收到的频点信息在相应的频带上发送该第一广播消息。相对应地，UE#B可以根据从为其服务的策略控制网元收到的频点信息在相应的频带上接收该第一广播消息。
该第一广播消息用于发现可以为UE#A提供中继服务的UE#B。
本申请实施例对该第一广播消息的具体内容不做限定。
在一种实现方式中，该第一广播消息可以包括以下信息：UE#A的信息、中继服务代码#1(所述第一中继服务代码的一例)以及第一参数。
其中UE#A的信息用于标识该UE#A，UE#A的信息可以包括UE#A的链路层标识或 者UE#A的应用层用户信息。
中继服务代码#1与第一应用相关联，该第一应用是UE#A待发起的应用，中继服务代码#1可以包括UE#A待发起的应用的信息，可选的，该中继服务代码#1还可包括UE#A的中继服务安全策略。
中继服务代码#1可以是UE#A本地预配置的，也可以是UE#A从为其服务的策略控制网元获取的，本申请实施例对此不做限定。后文会结合其他实施例对UE#A从为其服务的策略控制网元获取中继服务代码#1的方法进行描述，为了简洁，此处暂不详述。
第一参数是访问第一应用对应的参数，即该第一参数是UE#A访问该第一应用需要使用的参数，或者是UE#A访问该第一应用允许使用的参数。也就是说，该第一参数是运营商为UE#A待发起的应用配置的URSP规则中的路由选择描述信息中的参数。该第一参数可以是所述路由选择描述信息中的参数里的一种或多种：DNN、S-NAASI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示等。
该第一参数可以是UE#A从为其服务的策略控制网元获取的。
在另一种实现方式中，该第一广播消息可以包括以下信息：UE#A的信息、中继服务代码#2(所述第一中继服务代码的一例)。
其中，UE#A的信息用于标识该UE#A，UE#A的信息可以包括UE#A的链路层标识或者UE#A的应用层用户信息。
中继服务代码#2包括第一参数的信息。中继服务代码#2包括第一参数的信息可以理解为，中继服务代码#2包括第一参数对应的编码，或者，中继服务代码#2包括第一参数。换句话说，从中继服务代码#2中可以解析出第一参数。
本申请实施例对中继服务代码#2的具体形式不做限定。
作为一个示例，该中继服务代码#2与第一应用相关联，也可以理解为该中继服务代码#2与UE#A相关联。在此情况下，该中继服务代码#2还可以包括第一应用的信息，可选地，该中继服务代码#2还可以包括UE#A的中继服务安全策略。
作为另一个示例，该中继服务代码#2与第二应用相关联，该第二应用是UE#B支持中继服务的应用，也可以理解为该中继服务代码#2与UE#B相关联。在此情况下，该中继服务代码#2可以包括第二应用的信息，可选地，该中继服务代码#2还可以包括UE#B的中继服务安全策略。
该中继服务代码#2可以是UE#A从为其服务的策略控制网元获取的。后文会结合其他实施例详细描述UE#A从为其服务的策略控制网元获取中继服务代码#2的方法，为了简洁，此处暂不详述。
在又一种实施方式中，该第一广播消息可以包括以下信息：UE#A的信息、中继服务代码#3(所述第一中继服务代码的一例)。
其中UE#A的信息用于标识该UE#A，UE#A的信息可以包括UE#A的链路层标识或者UE#A的应用层用户信息。
中继服务代码#3与第二应用相关联，也可以理解为该中继服务代码#3与UE#B相关联。且该中继服务代码#3对应的UE#B能够为UE#A提供中继服务。换句话说，该中继服务代码#3是可用中继服务代码。中继服务代码#3可以包括第二应用的信息，可选地，该中继服务代码#3还可以包括UE#B的中继服务安全策略。
其中，中继服务代码#3可以是UE#A从为其服务的策略控制网元获取的。后文会结合其他实施例详细描述UE#A从为其服务的策略控制网元获取中继服务代码#3的方法，为了简洁，此处暂不详述。
在又一种实施方式中，该第一广播消息可以包括以下信息：UE#A的信息、中继服务代码#1(所述第一中继服务代码的一例)。
其中UE#A的信息用于标识该UE#A，UE#A的信息可以包括UE#A的链路层标识或者UE#A的应用层用户信息。
中继服务代码#1与第一应用相关联，该第一应用是UE#A待发起的应用，中继服务代码#1可以包括UE#A待发起的应用的信息，可选地，该中继服务代码#1还可以包括UE#A的中继服务安全策略。
中继服务代码#1可以是UE#A本地预配置的，也可以是UE#A从为其服务的策略控制网元获取的，本申请实施例对此不做限定。后文会结合其他实施例对UE#A从为其服务的策略控制网元获取中继服务代码#1的方法进行描述，为了简洁，此处暂不详述。
S220，UE#B向UE#A发送响应消息。
该响应消息用于指示UE#B支持以第一参数访问第一应用。该响应消息可以包括：UE#B的标识符、UE#A的信息。其中，UE#B的标识符用于标识UE#B，UE#B的标识符可以包括UE#B的链路层标识符。
如前文所述，UE#A发送的第一广播消息可以包括不同的内容。
在一种实现方式中，UE#A发送的第一广播消息包括以下信息：UE#A的信息、中继服务代码#1(所述第一中继服务代码的一例)以及第一参数。
在此情况下，UE#B接收到UE#A发送的第一广播消息之后，首先对该第一广播消息中的中继服务代码#1进行解析，判断自身是否能够提供UE#A待发起的应用的中继服务。
UE#B对该第一广播消息中的中继服务代码#1解析可以理解为，UE#B判断该广播消息中的中继服务代码#1与UE#B所配置的中继服务代码#4(所述第二中继服务代码的一例)是否相同，或者，是否等同，又或者，是否对中继服务代码#1与中继服务代码#4进行特定的加密/解密算法可以得到对等信息。例如，UE#B对中继服务代码#1与中继服务代码#4进行特定的解密算法是否可以得到同一个应用标识符。再例如，UE#B所配置的中继服务代码#4也可以是目标中继服务代码的过滤器，根据该过滤器，UE#B可判断该中继服务代码#1是否符合该过滤器需求，即UE#B是否可以为该中继服务代码#1所对应的UE#A支持提供UE#A待发起的应用的中继服务。
其中，中继服务代码#4与第二应用相关联，也可以理解为中继服务代码#4与UE#B相关联。中继服务代码#4是UE#B保存的中继服务代码，可以是UE#B本地预配置的，也可以是UE#B从为其服务的策略控制网元获取的，本申请实施例对此不做限定。UE#B从为其服务的策略控制网元获取中继服务代码#4的方法可以参考UE#A获取中继服务代码#1的方法，为了简洁，本申请实施例不再赘述。
若UE#B确定中继服务代码#1与中继服务代码#4相同，或者，等同，或者进行特定的加密/解密算法可以得到对等信息，则UE#B继续判断自身是否支持以第一参数访问第一应用。
若UE#B确定自身支持以第一参数访问第一应用，则UE#B确定自身能够提供第一应 用的中继服务。然后，UE#B可以向UE#A回复一个响应消息。
示例性地，UE#B可以根据第一参数是否与第二参数一致或等同，确定自身是否支持以第一参数访问第一应用。第二参数是访问第二应用的参数。若第一参数与第二参数一致或等同，则UE#B确定自身支持以第一参数访问第一应用。
可选地，若该第一参数中包括多个参数，则UE#B可以在确定自身能够以该第一参数中的至少一个参数访问第一应用的情况下，确定自身能够提供第一应用的中继服务。例如，若该第一参数中包括DNN和S-NAASI，则UE#B确定自身能够以该第一参数中的DNN访问第一应用的情况下，确定自身能够提供第一应用的中继服务；或者UE#B确定自身能够以该第一参数中的S-NAASI访问第一应用的情况下，确定自身能够提供第一应用的中继服务；或者UE#B确定自身能够以该第一参数中的DNN和S-NAASI访问第一应用的情况下，确定自身能够提供第一应用的中继服务。
在另一种实现方式中，UE#A发送的第一广播消息包括以下信息：UE#A的信息、中继服务代码#2(所述第一中继服务代码的一例)。
在此情况下，UE#B接收到UE#A发送的第一广播消息之后，可以对该第一广播消息中的中继服务代码#2进行解析，判断自身是否能够提供第一应用的中继服务。
作为一个示例，在中继服务代码#2与第一应用相关联的情况下，UE#B对该第一广播消息中的中继服务代码#2解析可以理解为，UE#B判断该中继服务代码#2是否与UE#B预先获取的中继服务代码#5(所述第二中继服务代码的一例)相同或等同，也可以理解为UE#B获取中继服务代码#2中包括的第一参数的信息。
若UE#B可以知道为UE#A服务的策略控制网元是如何为UE#A配置中继服务代码#2的，则可以成功解析中继服务代码#2。例如，若为UE#B服务的策略控制网元为UE#B配置中继服务代码#5的方式，与为UE#A服务的策略控制网元为UE#A配置中继服务代码#2的方式相同，则UE#B可以知道为UE#A服务的策略控制网元是如何为UE#A配置中继服务代码#2的。其中，中继服务代码#5与第二应用相关联。或者，UE#B有可能可以通过对中继服务代码#2进行特定的加密/解密算法之后，得到中继服务代码#2中的第一参数的信息。以上以举例的方式示出了UE#B解析中继服务代码#2的方法，不应对本申请实施例造成限定。
进一步地，若UE#B可以成功解析中继服务代码#2，即可以成功获取中继服务代码#2中包括的第一参数的信息，则UE#B继续确定自身能否支持以该第一参数访问第一应用。
若UE#B确定自身支持以该第一参数访问第一应用，则UE#B确定自身能够提供第一应用的中继服务。然后，UE#B可以向UE#A回复一个响应消息。
示例性地，UE#B可以根据第一参数是否与第二参数相同或等同，确定自身是否支持以第一参数访问第一应用。第二参数是访问第二应用的参数。若第一参数与第二参数相同或等同，则UE#B确定自身支持以第一参数访问第一应用。
可选地，若该第一参数中包括多个参数，则UE#B确定自身能够以该第一参数中的至少一个参数访问第一应用的情况下，确定自身能够提供第一应用的中继服务。例如，若该第一参数中包括DNN和S-NAASI，则UE#B确定自身支持以该第一参数中的DNN访问第一应用的情况下，确定自身能够提供第一应用的中继服务；或者UE#B确定自身支持以该第一参数中的S-NAASI访问第一应用的情况下，确定自身能够提供第一应用的中继服 务；或者UE#B确定自身支持以该第一参数中的DNN和S-NAASI访问第一应用的情况下，确定自身能够提供第一应用的中继服务。
作为另一个示例，在该中继服务代码#2与第一应用相关联的情况下，UE#B对该第一广播消息中的中继服务代码#2解析可以理解为，UE#B判断该中继服务代码#2是否与UE#B预先获取的中继服务代码#5相同或等同。示例性地，UE#B可以根据该中继服务代码#2与中继服务代码#5的前缀是否相同或等同，判断该中继服务代码#2中继服务代码#5是否相同或等同。其中，UE#B能够为中继服务代码#5所对应的UE#A提供中继服务，即支持第一参数访问第一应用。中继服务代码#5与第一应用相关联。
因此，若UE#B确定该第一广播消息中的中继服务代码#2与UE#B预先获取的中继服务代码#5等同或相同，则可以确定自身能够提供第一应用的中继服务，即支持以第一参数访问第一应用。然后，UE#B可以向UE#A回复一个响应消息。
可选地，UE#B预先获取的中继服务代码#5有多个，若中继服务代码#2与其中一个中继服务代码#5等同或相同，则UE#B可以确定自身能够提供第一应用的中继服务。
作为另一个示例，在中继服务代码#2与第二应用相关联的情况下，UE#B对该第一广播消息中的中继服务代码#2解析可以理解为UE#B判断该中继服务代码#2与UE#B所保存的中继服务代码#5是否相同或等同。示例性地，UE#B可以根据该中继服务代码#2与中继服务代码#5的前缀是否相同或等同，判断该中继服务代码#2中继服务代码#5是否相同或等同。其中，中继服务代码#5与第二应用相关联。
若UE#B确定中继服务代码#2与中继服务代码#5相同或等同，则UE#B确定自身能够提供第一应用的中继服务，即UE#B确定自身支持以该第一参数访问第一应用。然后，UE#B可以向UE#A回复一个响应消息。
在又一种实现方式中，该广播消息还可以包括以下信息：UE#A的信息、中继服务代码#3(所述第一中继服务代码的一例)。
在此情况下，UE#B接收到UE#A发送的第一广播消息之后，首先对该广播消息中的中继服务代码#3进行解析，以判断自身是否能够提供第一应用的中继服务。
UE#B对该中继服务代码#3解析可以理解为，UE#B判断该中继服务代码#3与UE#B所保存的中继服务代码#4(所述第二中继服务代码的一例)是否相同或等同。示例性地，UE#B可以根据该中继服务代码#3与中继服务代码#3的前缀是否相同或等同，判断该中继服务代码#3中继服务代码#3是否相同或等同。其中，中继服务代码#4与第二应用相关联。
若UE#B确定中继服务代码#3与中继服务代码#4相同或等同，则UE#B确定自身能够提供第一应用的中继服务，即UE#B确定自身支持以第一参数访问第一应用。然后，UE#B可以向UE#A回复一个响应消息。
在又一种实现方式中，该广播消息还可以包括以下信息：UE#A的信息、中继服务代码#1(所述第一中继服务代码的一例)。
在此情况下，UE#B接收到UE#A发送的第一广播消息之后，首先对该广播消息中的中继服务代码#1进行解析，以判断自身是否能够提供第一应用的中继服务。
UE#B对该中继服务代码#1解析可以理解为，UE#B判断该中继服务代码#1与UE#B所保存的中继服务代码#6(所述第二中继服务代码的一例)是否相同或等同。示例性地， UE#B可以根据该中继服务代码#1与中继服务代码#6的前缀是否相同或等同，判断该中继服务代码#2中继服务代码#5是否相同或等同。其中，中继服务代码#6与第一应用相关联。
若UE#B确定中继服务代码#1与中继服务代码#6相同或等同，则UE#B确定自身能够提供第一应用的中继服务，即UE#B确定自身支持以第一参数访问第一应用。然后，UE#B可以向UE#A回复一个响应消息。
可选地，UE#B所保存的中继服务代码#6有多个，若中继服务代码#1与其中一个中继服务代码#6等同或相同，则UE#B可以确定自身能够提供第一应用的中继服务。
可选地，在UE#A收到UE#B的响应消息之后，可以向UE#B发送PC5连接请求消息，以与UE#B建立PC5连接。
进一步地，UE#A与UE#B建立PC5连接之后，若UE#B判断本地无可用的PDU会话，则根据第一应用的标识符执行URSP匹配，并根据匹配到的URSP规则中的路由选择描述符列表发起PDU会话建立流程。其中，该PDU会话建立请求所请求的DNN、S-NSSAI、SSC模式、PDU会话类型等参数中的一个或多个与UE#A所需要的会话参数一致或等同。
在本申请实施例中，UE#A发送的第一广播消息中可以包括第一参数，或者第一中继服务代码可以包括第一参数的信息，又或者，UE#A发送的第一广播消息中可以包括从策略控制网元获取的可用中继服务代码。因此，根据该第一广播消息匹配到的UE#B能够以UE#A所需要的会话参数(即所述第一参数)访问第一应用。
图3示出了第一终端设备(图中所示的UE#A)获取第一中继服务代码的方法的示意性流程图。图中所示的AMF#1、PCF#1以及UDR#1都为UE#A提供服务，PCF#2为第二终端设备(图中未画出)提供服务。如图3所示，该方法300包括S310-S330，下面详细描述每个步骤。
S310，UE#A通过AMF#1(所述接入和移动管理网元的一例)向PCF#1(所述第一策略控制网元的一例)发送请求消息#1(所述第一请求消息的一例)。
其中，该请求消息#1用于请求获取第一中继服务代码。
UE#A通过AMF#1向PCF#1发送请求消息#1的方法可以是：
方式一：
UE#A首先向AMF#1发送注册请求消息，该注册请求消息中可以包括以下信息中的一种或多种：UE#A的标识信息、第一应用的标识符。
其中，UE#A的标识信息可以是用户隐藏标识符(subscriber concealed identifier，SUCI)，或者是全球唯一临时标识(globally unique temporary identity，GUTI)。UE#A的标识信息用于标识UE#A，以及用于AMF#1映射得到用户永久标识符(subscriber permanent identifier，SUPI)。
第一应用的标识符用于指示UE#A待发起的应用。
可选地，该注册请求消息中还可以包括降级指示信息，该降级指示信息用于指示UE#A是否接受服务降级。服务降级可以理解为会话参数降级，例如，UE#A是否接受以低优先级的会话参数访问第一应用。
作为一个示例，该降级指示信息用于指示UE#A不接受服务降级，表示UE#A只允许以UE#A需要的会话参数访问第一应用。
作为另一个示例，该降级指示信息用于指示UE#A接受服务降级，表示UE#A可以允许以比UE#A需要的会话参数的优先级低的会话参数访问第一应用。例如，UE#A当前处于无运营商网络覆盖区域，为了尽可能接入运营商网络，UE#A可以允许以低优先级的DNN、S-NASSI、SSC模式、PDU会话类型等参数访问第一应用。
然后，AMF#1收到来自UE#A的注册请求消息之后，向PCF#1发送请求消息#1。
本申请实施例对该请求消息#1的具体形式不做限定。例如，若AMF#1收到的注册请求消息是初始注册请求消息，即AMF#1与PCF#1之间还没有建立用户策略关联，则该请求消息#1可以是用户策略关联建立请求消息。又例如，若AMF#1收到的注册请求消息是由于UE#A位置更新发出的注册请求消息，或者是UE#A周期性发出的注册请求消息，即AMF#1与PCF#1之间的用户策略关联还处于激活状态，则该请求消息#1可以是用户策略关联更新请求消息。
该请求消息#1可以包括以下信息：UE#A的标识信息、第一应用的标识符。其中，UE#A的标识信息是SUPI。
可选地，该请求消息#1还可以包括降级指示信息。
可以理解，该请求消息#1的内容可以与注册请求消息的内容对应。例如，注册请求消息中包括UE#A的标识信息和第一应用的标识符，则请求消息#1也包括UE#A的标识信息和第一应用的标识符。又例如，注册请求消息中包括UE#A的标识信息、第一应用的标识符和降级指示信息，则请求消息#1也包括UE#A的标识信息、第一应用的标识符和降级指示信息。
方式二：
UE#A首先向AMF#1发送邻近(proximity based service，ProSe)发现请求消息，该ProSe发现请求消息可以包括以下信息中的一种或多种：UE#A的标识信息、请求类型、第一应用的标识符。
其中，UE#A的标识信息可以SUCI，或者是GUTI。UE#A的标识信息用于标识UE#A，以及用于AMF#1映射得到SUPI。
第一应用的标识符用于指示UE#A待发起的应用。
请求类型用于指示UE#A请求作为中继UE节点还是远端UE节点。
可选地，该注册请求消息中还可以包括降级指示信息，该降级指示信息用于指示UE#A是否接受服务降级。服务降级可以理解为会话参数降级，例如，UE#A是否接受以低优先级的会话参数访问第一应用。
作为一个示例，该降级指示信息用于指示UE#A不接受服务降级，表示UE#A只允许以UE#A需要的会话参数访问第一应用。
作为另一个示例，该降级指示信息用于指示UE#A接受服务降级，表示UE#A可以允许以比UE#A需要的会话参数的优先级低的会话参数访问第一应用。例如，UE#A当前处于无运营商网络覆盖区域，为了尽可能接入运营商网络，UE#A可以允许以低优先级的DNN、S-NASSI、SSC模式、PDU会话类型等参数访问第一应用。
然后，AMF#1收到来自UE#A的ProSe发现请求消息之后，向PCF#1发送请求消息#1。
该请求消息#1可以包括以下信息：UE#A的标识信息、第一应用的标识符、请求类型。 其中，UE#A的标识信息是SUPI，该标识信息可以理解为AMF#1根据SUCI或GUTI映射得到。
可选地，该请求消息#1还可以包括所述降级指示信息。
可以理解，该请求消息#1的内容可以与ProSe发现请求消息的内容对应。例如，ProSe发现请求消息包括UE#A的标识信息和第一应用的标识符，则请求消息#1也包括UE#A的标识信息和第一应用的标识符。又例如，ProSe发现请求消息中包括UE#A的标识信息、第一应用的标识符和降级指示信息，则请求消息#1也包括UE#A的标识信息、第一应用的标识符和降级指示信息。
S320，PCF#1决策第一中继服务代码。
本申请实施例对PCF#1决策第一中继服务代码的方法不做限定。
在一种实现方式中，PCF#1可以根据第一参数决策第一中继服务代码。该第一中继服务代码可对应于上文所述的中继服务代码#2。
第一参数是访问第一应用对应的参数，即该第一参数是UE#A访问该第一应用需要使用的参数，或者是UE#A访问该第一应用允许使用的参数。也就是说，该第一参数是运营商为UE#A支持中继服务的应用配置的URSP规则中的路由选择描述信息中的参数。该第一参数可以是所述路由选择描述信息中的参数里的一种或多种：DNN、S-NAASI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示等。
作为一个示例，PCF#1可以对第一参数对应的编码进行哈希运算，得到第一中继服务代码。
作为另一个示例，PCF#1可以对第一参数对应的编码采用密钥加密，得到第一中继服务代码。
在另一种实现方式中，PCF#1可以根据第一参数和以下信息决策第一中继服务代码：UE#A的签约信息、第一应用的标识符。该第一中继服务代码可对应于上文所述的中继服务代码#2。
同样地，PCF#1可以将第一参数对应的编码，和上述信息对应的编码一起进行哈希运算或采用密钥加密得到第一中继服务代码。
在又一种实现方式中，PCF#1可以根据第一参数和以下信息决策第一中继服务代码：UE#A的签约信息、第一应用的标识符、降级指示信息。该第一中继服务代码可对应于上文所述的中继服务代码#2。
若该降级指示信息用于指示UE#A不接受服务降级，则PCF#1可以将第一参数对应的编码，和上述信息对应的编码一起进行哈希运算或采用密钥加密得到第一中继服务代码。
若该降级指示信息用于指示UE#A接受服务降级，则可以将优先级低于第一参数的会话参数对应的编码，和上述信息对应的编码进行哈希运算或采用密钥加密得到第一中继服务代码。
上文中本申请实施例仅以哈希运算和密钥加密作为示例，对PCF#1决策第一中继服务编码的方式进行说明，可以理解，PCF#1还可以采用其他的编码方式决策第一中继服务代码，本申请实施例对此不做限定。
可以理解，若PCF#1处没有保存第一参数，则PCF#1可以从UDR#1(所述数据管理 仓库网元的一例)处获取第一参数，或是通过获取第一应用对应的URSP规则或路由选择描述信息，从而从URSP规则或路由选择描述信息中获取所述第一参数。
S3201a，PCF#1向UDR#1发送请求消息#2。
该请求消息#2用于请求获取第一参数，或者用于请求获取第一应用对应的URSP规则，再或者是用于请求获取路由选择描述信息。
可选地，该请求消息#2还用于请求验证UE#A是否被允许使用第一业务。
可选地，若PCF#1收到的请求消息#1中包括请求类型，则该请求消息#2还用于请求验证UE#A是否被允许作为中继UE节点或远端UE节点。
该请求消息#2中包括以下信息：UE#A的标识信息、第一应用的标识符。
可以理解，该请求消息#2不论是用于请求获取第一参数，还是用于请求URSP规则或路由选择描述信息，UDR#1都是首先根据该请求消息#2获取运营商为UE#A下的第一应用配置的URSP规则。进一步地，若该请求消息#2用于请求获取路由选择描述信息，则UDR#1可以从URSP规则中获取路由选择描述信息；若该请求消息#2用于请求获取第一参数，则UDR#1可以先从URSP规则中获取路由选择描述信息，然后再从路由选择描述信息中获取第一参数。
可选地，UDR#1还可以获取UE#A的签约信息。
S3202a，UDR#1向PCF#1发送第一参数。
可选地，UDR#1还可以向PCF#1发送UE#A的签约信息。
在又一种实现方式中，PCF#1可以根据来自PCF#2的第二中继服务代码决策第一中继服务代码。若该第二中继服务代码包括第二参数的信息，则PCF#1根据该第二中继服务代码决策的第一中继服务代码对应于上文所述的中继服务代码#2；若该第二中继服务代码不包括第二参数的信息，则PCF#1根据该第二中继服务代码决策的第一中继服务代码对应于上文所述的中继服务代码#3。
作为一个示例，PCF#1可以不对第二中继服务代码做处理，将第二中继服务代码决策为第一中继服务代码。
作为另一个示例，PCF#1可以对第二中继服务代码做处理，得到第一中继服务代码。例如，PCF#1可以将第二中继服务代码的前缀决策为第一中继服务代码。再例如，PCF#1可以根据该第二中继服务代码生成第一中继服务代码，该第一中继服务代码与第二中继服务代码对应。
可以理解，若PCF#1处没有保存第二中继服务代码，则PCF#1可以从PCF#2处获取第二中继服务代码。
S3201b，PCF#1向UDR#1发送请求消息#3(所述第三请求消息的一例)。
该请求消息#2用于请求获取PCF#2的信息。
S3202b，UDR#1向PCF#1发送PCF#2的信息。
作为一个示例，UDR#1接收到来自PCF#1的请求消息#3之后，可以向PCF#1发送UE#A所在的拜访地公共陆地移动网络(public land mobile network，PLMN)的标识信息和/或邻近PLMN的标识信息。然后，由PCF#1根据该拜访地PLMN的标识信息和/或邻近PLMN的标识信息，查找该拜访地PLMN网络和/或邻近PLMN网络中的PCF#2的信息。
作为另一个示例，UDR#1也可在发送至PCF#1的响应消息中直接携带拜访地PLMN的标识信息和/或邻近PLMN的标识信息，以及该拜访地PLMN网络和/或邻近PLMN网络中的PCF#2的信息。
可以理解，与UE#A所在的PLMN网络邻近的PLMN网络可以有多个，或者，UE#A所在的PLMN网络和邻近的PLMN网络中分别可以有多个PCF#2，对应地，UDR#1可以获得多个PCF#2的信息。
然后，UDR#1将该多个PCF#2的信息和/或多个PLMN标识信息发送至PCF#1。
若PCF#1收到的是拜访地PLMN标识信息和/或邻近PLMN标识信息，则PCF#1还可通过网络存储功能(network repository function，NRF)网元查询该拜访地PLMN和/或邻近PLMN中的PCF#2的信息。
S3203b，PCF#1向PCF#2发送请求消息#4(所述第二请求消息的一例)。
该请求消息#4用于请求获取第二中继服务代码。
该请求消息#4包括以下信息：第一参数、第一应用的标识符。
可选地，该请求消息#4还可以包括UE#A标识信息。
可选地，该请求消息#4还可以包括降级指示信息。
可以理解，PCF#1可以收到多个PCF#2的信息，因此，PCF#1向每个PCF#2都发送该请求消息#4。
S3204b，PCF#2向PCF#1发送第二中继服务代码。
PCF#2收到请求消息#4之后，首先判断自身所服务的UE#B是否支持以第一参数访问第一应用，例如，PCF#2判断运营商为UE#B配置的URSP规则中的会话参数是否与第一参数等同或相同，若相同或等同，则PCF#2确定自身所服务的UE#B支持以第一参数访问第一应用。然后，PCF#2将其为UE#B决策的第二中继服务代码发送至PCF#1。再例如，PCF#2还可根据本地所保存的中继服务代码列表，判断其中支持提供第一参数访问第一应用的中继服务的第二中继服务代码，并将符合条件的一个或多个第二中继服务代码发送PCF#1。
可选地，若该请求消息#4中还包括UE#A的标识信息，则PCF#2还可以判断自身所服务的UE#B是否允许为UE#A提供中继服务。若允许，则PCF#2将其为UE#B决策的第二中继服务代码发送至PCF#1。
可选地，若该请求消息#4中还包括降级指示信息，则在PCF#2判断运营商为UE#B配置的URSP规则中的会话参数比第一参数优先级更低的情况下，也可以将其为UE#B决策的第二中继服务代码发送至PCF#1。可选地，PCF#2还可根据本地所保存的中继服务代码列表，判断其中支持提供第一参数降级后的第二参数访问第一应用的中继服务的第二中继服务代码，并将符合条件的一个或多个第二中继服务代码发送至PCF#1。
在又一种实现方式中，PCF#1可以根据以下信息决策第一中继服务代码：UE#A的签约信息、第一应用的标识符。该第一中继服务代码可以对应于上文所述的中继服务代码#1。
PCF#1可以将上述信息对应的编码进行哈希运算或采用密钥加密得到第一中继服务代码。
S330，PCF#1通过AMF#1向UE#A发送第一中继服务代码。
PCF#1可以先向AMF#1发送一个响应消息，该响应消息中包括该第一中继服务代码， 然后AMF#1将该第一中继服务代码发送至UE#A。
可选地，PCF#1向AMF#1发送的响应消息中还可以包括第一应用的标识符。相对应地，AMF#1向UE#A发送的消息中也可以包括第一应用的标识符。
可选地，PCF#1向AMF#1发送的响应消息中还可以包括UE#A发送第一广播消息对应的无线参数，例如，频带信息、频带适用地理区域、有效时间等。相对应地，AMF#1向UE#A发送的消息中也可以包括无线参数、有效时间等信息。
在本申请实施例中，PCF#1根据UE#A的请求可以为UE#A分配包括第一参数的信息的第一中继服务代码。进一步地，UE#A根据该第一中继服务代码匹配的UE#B可以提供UE#A需要的中继服务。或者，PCF#1还可以为UE#A分配与UE#B相关联的第一中继服务代码，并且该第一中继服务代码对应的UE#B可以提供UE#A需要的中继服务。因此，UE#A根据该第一中继服务代码匹配的UE#B可以满足UE#A的需求。
图4示出了本申请实施例提供的建立连接的方法的示意性流程图。图4所示的方法可以由图1所示的系统中的UE#A和UE#B执行，其中UE#A对应于第一终端设备，UE#B对应于第二终端设备。该方法200中所描述的UE#A与UE#B建立连接的方法对应于模式A，即由中继UE发送广播消息。如图4所示，该方法包括S410和S420。下面详细描述每个步骤。
S410，UE#B发送第二广播消息。
UE#B可以根据从为其服务的策略控制网元收到的频点信息在相应的频带上发送该第二广播消息。相对应地，UE#A可以根据从为其服务的策略控制网元收到的频点信息在相应的频带上接收该第二广播消息。
该第二广播消息用于被需要中继服务的UE#A发现。
本申请实施例对该第二广播消息的具体内容不做限定。
在一种实现方式中，该广播消息可以包括以下信息：UE#B的信息、中继服务代码#4(所述第二中继服务代码的一例)以及第二参数。
其中UE#B的信息用于标识该UE#B，UE#B的信息可以包括UE#B的链路层标识或者UE#B的应用层用户信息。
中继服务代码#4与第二应用相关联，该第二应用是UE#B支持中继服务的应用，中继服务代码#4可以包括第二应用的信息可选地，该中继服务代码#4还可以包括UE#B的中继服务安全策略。
中继服务代码#4可以是UE#B本地预配置的，也可以是UE#B从为其服务的策略控制网元获取的，本申请实施例对此不做限定。后文会结合其他实施例对UE#B从为其服务的策略控制网元获取中继服务代码#4的方法进行描述，为了简洁，此处暂不详述。
第二参数是访问第二应用对应的参数，即该第二参数是UE#B访问该第二应用需要使用的参数，或者是UE#B访问该第二应用允许使用的参数。也就是说，该第二参数是运营商为UE#B支持中继服务的应用配置的URSP规则中的路由选择描述信息中的参数。该第二参数可以所述路由选择描述信息中的参数里的一种或多种：DNN、S-NAASI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示等。
该第二参数是UE#B从为其服务的策略控制网元获取的。
在另一种实现方式中，该广播消息可以包括以下信息：UE#B的信息、中继服务代码 #5。
其中UE#B的信息用于标识该UE#B，UE#B的信息可以包括UE#B的链路层标识或者UE#B的应用层用户信息。
中继服务代码#5包括第二参数的信息。中继服务代码#5包括第二参数的信息可以理解为，中继服务代码#5包含第二参数对应的编码，或者，中继服务代码#5包含第二参数。换句话说，从中继服务代码#5中可以解析出第二参数。
本申请实施例对中继服务代码#5的具体形式不做限定。
作为一个示例，该中继服务代码#5与第二应用相关联，也可以理解为该中继服务代码#5与UE#B相关联。在此情况下，该中继服务代码#5还可以包括第二应用的信息，可选地，该中继服务代码#5还可以包括UE#B的中继服务安全策略。
作为另一个示例，该中继服务代码#5与第一应用相关联，该第一应用是UE#A待发起应用，也可以理解为该中继服务代码#5与UE#A相关联。在此情况下，该中继服务代码#5还可以包括第一应用的信息，可选地，该中继服务代码#5还可以包括UE#A的中继服务安全策略。
该中继服务代码#5可以是UE#B从为其服务的策略控制网元获取的。后文会结合其他实施例详细描述UE#B从为其服务的策略控制网元获取中继服务代码#5的方法，为了简洁，此处暂不详述。
在又一种实施方式中，该第一广播消息可以包括以下信息：UE#B的信息、中继服务代码#6(所述第二中继服务代码的一例)。
其中UE#B的信息用于标识该UE#B，UE#B的信息可以包括UE#B的链路层标识或者UE#B的应用层用户信息。
中继服务代码#6与第一应用相关联，也可以理解为该中继服务代码#6与UE#A相关联。且UE#B能够为该中继服务代码#6对应的UE#A提供中继服务。换句话说，该中继服务代码#6是可用中继服务代码。中继服务代码#6可以包括第一应用的信息，可选地，该中继服务代码#6还可以包括UE#A的中继服务安全策略。
其中，中继服务代码#6可以是UE#B从为其服务的策略控制网元获取的。后文会结合其他实施例详细描述UE#B从为其服务的策略控制网元获取中继服务代码#6的方法，为了简洁，此处暂不详述。
在又一种实施方式中，该第一广播消息可以包括以下信息：UE#B的信息、中继服务代码#4(所述第二中继服务代码的一例)。
其中UE#B的信息用于标识该UE#B，UE#B的信息可以包括UE#B的链路层标识或者UE#B的应用层用户信息。
中继服务代码#4与第二应用相关联，中继服务代码#4可以包括第二应用的信息，可选地，该中继服务代码#4还可以包括UE#B的中继服务安全策略。
中继服务代码#4可以是UE#B本地预配置的，也可以是UE#B从为其服务的策略控制网元获取的，本申请实施例对此不做限定。后文会结合其他实施例对UE#B从为其服务的策略控制网元获取中继服务代码#1的方法进行描述，为了简洁，此处暂不详述。
S420，UE#A向UE#B发送请求消息#5(所述第四请求消息的一例)。
该请求消息#5用于请求与UE#B建立PC5连接。
如前文所述，UE#B发送的第二广播消息可以包括不同的内容。
在一种实现方式中，UE#B发送的第一广播消息包括以下信息：UE#B的信息、中继服务代码#4(所述第二中继服务代码的一例)以及第二参数。
在此情况下，UE#A接收到UE#B发送的第二广播消息之后，首先对该第二广播消息中的中继服务代码#4进行解析，判断UE#B是否能够提供自身待发起的应用的中继服务。
UE#A对该第二广播消息中的中继服务代码#4解析可以理解为，UE#A判断该第二广播消息中的中继服务代码#4与UE#A所保存的中继服务代码#1(所述第一中继服务代码的一例)是否相同，或者，是否等同，又或者，是否对中继服务代码#1与中继服务代码#4进行特定的加密/解密算法可以得到对等信息。例如，UE#A对中继服务代码#1与中继服务代码#4进行特定的解密算法是否可以得到同一个应用标识符。再例如，UE#A所配置的中继服务代码#1也可以是目标中继服务代码的过滤器，根据该过滤器，UE#A可判断该中继服务代码#4是否符合该过滤器需求，即该中继服务代码#4所对应的UE#B是否可以为UE#A提供UE#A待发起的应用的中继服务。
其中，中继服务代码#1与第一应用相关联，也可以理解为中继服务代码#1与UE#A相关联。中继服务代码#1是UE#A保存的中继服务代码，可以是UE#A本地预配置的，也可以是UE#A从为其服务的策略控制网元获取的，本申请实施例对此不做限定。UE#A从为其服务的策略控制网元获取中继服务代码#1的方法可以参考UE#B获取中继服务代码#4的方法，为了简洁，本申请实施例不再赘述。
若UE#A确定中继服务代码#1与中继服务代码#4相同，或者，等同，或者进行特定的加密/解密算法可以得到对等信息，则UE#A继续该第二参数是否第一参数一致或等同，第一参数是访问第一应用对应的参数。
若UE#A确定该第二参数与第一参数一致或等同，则UE#A确定UE#B能够提供第一应用的中继服务。然后，UE#A可以向UE#B发送请求消息#5。
可选地，若该第一参数中包括多个参数，则UE#A可以在确定该第二参数中的至少一个参数与第一参数中的参数一致或等同的情况下，确定自身能够提供第一应用的中继服务。例如，若该第二参数中包括DNN和S-NAASI，则UE#A确定该第二参数中的DNN与第一参数中的DNN一致或等同的情况下，确定UE#B能够提供第一应用的中继服务；则UE#A确定该第二参数中的S-NASSI与第一参数中的S-NASSI一致或等同的情况下，确定UE#B能够提供第一应用的中继服务；则UE#A确定该第二参数中的DNN和S-NASII与第一参数中的DNN和S-NASSI一致或等同的情况下，确定UE#B能够提供第一应用的中继服务。
在另一种实现方式中，UE#B发送的第二广播消息包括以下信息：UE#B的信息、中继服务代码#5(所述第二中继服务代码的一例)。
在此情况下，UE#A接收到UE#B发送的第二广播消息之后，可以对该第二广播消息中的中继服务代码#5进行解析，判断UE#B是否能够提供第一应用的中继服务。
作为一个示例，在中继服务代码#5与第二应用相关联的情况下，UE#A对该第二广播消息中的中继服务代码#5解析可以理解为，UE#A判断该中继服务代码#5是否与UE#A预先获取的中继服务代码#2相同或等同，也可以理解为UE#A获取中继服务代码#5中包括的第二参数的信息。
若UE#A可以知道为UE#B服务的策略控制网元是如何为UE#B配置中继服务代码#5的，则可以成功解析中继服务代码#5。例如，若为UE#A服务的策略控制网元为UE#A配置中继服务代码#2(所述第一中继服务代码的一例)的方式，与为UE#B服务的策略控制网元为UE#B配置中继服务代码#5的方式相同，则UE#A可以知道为UE#B服务的策略控制网元是如何为UE#B配置中继服务代码#5的。其中，中继服务代码#2与第一应用相关联。或者，UE#A有可能可以通过对中继服务代码#5进行特定的加密/解密算法之后，得到中继服务代码#5中的第二参数的信息。以上以举例的方式示出了UE#A解析中继服务代码#5的方法，不应对本申请实施例造成限定。
进一步地，若UE#A可以成功解析中继服务代码#5，即可以成功获取中继服务代码#5中包括的第二参数的信息，则UE#A该第二参数或否与第一参数一致或等同。
若UE#A确定该第二参数与第一参数一致或等同，则UE#A确定UE#B能够提供第一应用的中继服务。然后，UE#A可以向UE#B发送请求消息#5。
可选地，若该第二参数中包括多个参数，则UE#A可以在确定该第二参数中的至少一个参数与第一参数中的参数一致或等同的情况下，确定自身能够提供第一应用的中继服务。例如，若该第二参数中包括DNN和S-NAASI，则UE#A确定该第二参数中的DNN与第一参数中的DNN一致或等同的情况下，确定UE#B能够提供第一应用的中继服务；或者UE#A确定该第二参数中的S-NASSI与第一参数中的S-NASSI一致或等同的情况下，确定UE#B能够提供第一应用的中继服务；或者UE#A确定该第二参数中的DNN和S-NASII与第一参数中的DNN和S-NASSI一致或等同的情况下，确定UE#B能够提供第一应用的中继服务。
作为另一个示例，在该中继服务代码#5与第二应用相关联的情况下，UE#A对该第二广播消息中的中继服务代码#5解析可以理解为，UE#A判断该中继服务代码#5是否与UE#A预先获取的中继服务代码#2相同或等同。示例性地，UE#A可以根据该中继服务代码#2与中继服务代码#5的前缀是否相同或等同，判断该中继服务代码#2中继服务代码#5是否相同或等同。其中，中继服务代码#2所对应的UE#B能够为UE#A提供中继服务，即支持以第一参数访问第一应用。中继服务代码#2与第二应用相关联。
因此，若UE#A确定该第二广播消息中的中继服务代码#5与UE#A所保存的中继服务代码#2等同或相同，则可以确定UE#B能够提供第一应用的中继服务，即UE#B支持以第一参数访问第一应用。然后，UE#A可以向UE#B发送请求消息#5。
可选地，UE#A所保存的中继服务代码#2有多个，若中继服务代码#5与其中一个中继服务代码#2等同或相同，则UE#A可以确定UE#B能够提供第一应用的中继服务。
作为另一个示例，在中继服务代码#5与第一应用相关联的情况下，UE#A对该第二广播消息中的中继服务代码#5解析可以理解为UE#A判断该中继服务代码#5与UE#A所保存的中继服务代码#2是否相同或等同。示例性地，UE#A可以根据该中继服务代码#2与中继服务代码#5的前缀是否相同或等同，判断该中继服务代码#2中继服务代码#5是否相同或等同。其中，中继服务代码#2与第一应用相关联。
若UE#A确定中继服务代码#5与中继服务代码#2相同或等同，则UE#A确定UE#B能够提供第一应用的中继服务，即确定UE#B支持以第一参数访问第一应用。然后，UE#A可以向UE#B发送请求消息#5。
在又一种实现方式中，该广播消息还可以包括以下信息：UE#A的信息、中继服务代码#6(所述第二中继服务代码的一例)。
在此情况下，UE#A接收到UE#B发送的第二广播消息之后，首先对该第二广播消息中的中继服务代码#6进行解析，以判断UE#B是否能够提供第一应用的中继服务。
UE#A对该中继服务代码#6解析可以理解为，UE#A判断该中继服务代码#6与UE#A所保存的中继服务代码#1(所述第一中继服务代码的一例)是否相同或等同。示例性地，UE#A可以根据该中继服务代码#6与中继服务代码#1的前缀是否相同或等同，判断该中继服务代码#1中继服务代码#6是否相同或等同。其中，中继服务代码#1与第一应用相关联。
若UE#A确定中继服务代码#6与中继服务代码#1相同或等同，则UE#A确定UE#B能够提供第一应用的中继服务，即确定UE#B支持以第一参数访问第一应用。然后，UE#A可以向UE#B发送请求消息#5。
在又一种实现方式中，该广播消息还可以包括以下信息：UE#A的信息、中继服务代码#4(所述第二中继服务代码的一例)。
在此情况下，UE#A接收到UE#B发送的第二广播消息之后，首先对该第二广播消息中的中继服务代码#4进行解析，以判断UE#B是否能够提供第一应用的中继服务。
UE#A对该中继服务代码#4解析可以理解为，UE#A判断该中继服务代码#4与UE#A所保存的中继服务代码#3(所述第一中继服务代码的一例)是否相同或等同。示例性地，UE#A可以根据该中继服务代码#3与中继服务代码#4的前缀是否相同或等同，判断该中继服务代码#3中继服务代码#4是否相同或等同。其中，中继服务代码#3与第二应用相关联。
若UE#A确定中继服务代码#4与中继服务代码#3相同或等同，则UE#A确定UE#B能够提供第一应用的中继服务，即确定UE#B支持以第一参数访问第一应用。然后，UE#A可以向UE#B发送请求消息#5。
可选地，UE#A所保存的中继服务代码#3有多个，若中继服务代码#4与其中一个中继服务代码#3等同或相同，则UE#A可以确定UE#B能够提供第一应用的中继服务。
进一步地，UE#A与UE#B建立PC5连接之后，若UE#B判断本地无可用的PDU会话，则根据第一应用的标识符执行URSP匹配，并根据匹配到的URSP规则中的路由选择描述符列表发起PDU会话建立流程。其中，该PDU会话建立请求所请求的DNN、S-NSSAI、SSC模式、、PDU会话类型等参数中的一个或多个与UE#A所需要的会话参数一致或等同。
在本申请实施例中，UE#B发送的第二广播消息中可以包括第二参数，或者第二中继服务代码可以包括第二参数的信息，又或者，UE#B发送的第二广播消息中可以包括从策略控制网元获取的可用中继服务代码。因此，UE#B可以为根据该第二广播消息匹配到的UE#A提供该UE#A所需要中继服务，即UE#B可以以UE#A需要的会话参数访问UE#A待发起的应用。
图5示出了第二终端设备(图中所示的UE#B)获取第二中继服务代码的方法的示意性流程图。图中所示的AMF#2、PCF#2以及UDR#2为UE#B提供服务，PCF#1为第一终端设备(图中未画出)提供服务。如图5所示，该方法500包括S510-S530，下面详细描 述每个步骤。
S510，UE#B通过AMF#2(所述接入和移动管理网元的一例)向PCF#2(所述第二策略控制网元的一例)发送请求消息#6(所述第五请求消息的一例)。
其中，该请求消息#6用于请求获取第二中继服务代码。
UE#B通过AMF#2向PCF#2发送请求消息#6的方法可以是：
方式一：
UE#B首先向AMF#2发送注册请求消息，该注册请求消息中可以包括以下信息中的一种或多种：UE#B的标识信息、第二应用的标识符。
其中，UE#B的标识信息可以是SUCI，或者是GUTI。UE#B的标识信息用于标识UE#B，以及用于AMF#2映射得到SUPI。
第一应用的标识符用于指示UE#B支持中继服务的应用。
然后，AMF#2收到来自UE#B的注册请求消息之后，向PCF#2发送请求消息#6。
本申请实施例对该请求消息#6的具体形式不做限定。例如，若AMF#2收到的注册请求消息是初始注册请求消息，即AMF#2与PCF#2之间还没有建立用户策略关联，则该请求消息#6可以是用户策略关联建立请求消息。又例如，若AMF#2收到的注册请求消息是由于UE#B位置更新发出的注册请求消息，或者是UE#B周期性发出的注册请求消息，即AMF#2与PCF#2之间的用户策略关联还处于激活状态，则该请求消息#6可以是用户策略关联更新请求消息。
该请求消息#6可以包括以下信息：UE#B的标识信息、第二应用的标识符。其中，UE#B的标识信息是SUPI。
可以理解，该请求消息#6的内容可以与注册请求消息的内容对应。例如，注册请求消息中包括UE#B的标识信息和第二应用的标识符，则请求消息#6也包括UE#B的标识信息和第二应用的标识符。
方式二：
UE#B首先向AMF#2发送ProSe发现请求消息，该ProSe发现请求消息可以包括以下信息中的一种或多种：UE#B的标识信息、请求类型、第二应用的标识符。
其中，UE#B的标识信息可以是SUCI，或者是GUTI。UE#B的标识信息用于标识UE#B，以及用于AMF#2映射SUPI。
第二应用的标识符用于指示UE#B支持中继服务的应用。
请求类型用于指示UE#B请求作为中继UE节点还是远端UE节点。
然后，AMF#2收到来自UE#A的ProSe发现请求消息之后，向PCF#2发送请求消息#6。
该请求消息#6可以包括以下信息：UE#B的标识信息、第二应用的标识符、请求类型。其中，UE#B的标识信息是SUPI，该标识信息可以理解为AMF#2根据SUCI或GUTI映射得到的。
可以理解，该请求消息#6的内容可以与ProSe发现请求消息的内容对应。例如，ProSe发现请求消息包括UE#B的标识信息和第二应用的标识符，则请求消息#6也包括UE#B的标识信息和第二应用的标识符。
S520，PCF#2决策第二中继服务代码。
本申请实施例对PCF#2决策第二中继服务代码的方法不做限定。
在一种实现方式中，PCF#2可以根据第二参数决策第二中继服务代码。该第二中继服务代码可对应于上文所述的中继服务代码#5。
第二参数是访问第二应用对应的参数，即该第二参数是UE#B访问该第二应用需要使用的参数，或者是UE#B访问该第二应用允许使用的参数。也就是说，该第二参数是运营商为UE#B支持中继服务的应用配置的URSP规则中的路由选择描述信息中的参数。该第一参数可以是以下所述路由选择描述信息中的参数中里的一种或多种：DNN、S-NAASI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示等。
作为一个示例，PCF#2可以对第二参数对应的编码进行哈希运算，得到第二中继服务代码。
作为另一个示例，PCF#2可以对第二参数对应的编码采用密钥加密，得到第二中继服务代码。
在另一种实现方式中，PCF#2可以根据第二参数和以下信息决策第二中继服务代码：UE#B的签约信息、第二应用的标识符。该第二中继服务代码可对应于上文所述的中继服务代码#5。
同样地，PCF#2可以将第二参数对应的编码，和上述信息对应的编码一起进行哈希运算或采用密钥加密得到第二中继服务代码。
上文中本申请实施例仅以哈希运算和密钥加密作为示例，对PCF#2决策第二中继服务编码的方式进行说明，可以理解，PCF#2还可以采用其他的编码方式决策第二中继服务代码，本申请实施例对此不做限定。
可以理解，若PCF#2处没有保存第二参数，则PCF#2可以从UDR#2(所述数据管理仓库网元的一例)处获取第二参数，或是通过获取第二应用对应的URSP规则或路由选择描述信息，从而从URSP规则或路由选择描述信息中获取所述第二参数。
S5201a，PCF#2向UDR#2发送请求消息#7。
该请求消息#7用于请求获取第二参数，或者用于请求获取第二应用对应的URSP规则，再或者是用于请求获取路由选择描述信息。
可选地，该请求消息#7还用于请求验证UE#B是否被允许使用第二应用。
可选地，若PCF#2收到的请求消息#7中包括请求类型，则该请求消息#7还用于请求验证UE#B是否被允许作为中继UE节点或远端UE节点。
该请求消息#7中包括以下信息：UE#B的标识信息、第二应用的标识符。
可以理解，该请求消息#7不论是用于请求获取第二参数，还是用于请求URSP规则或路由选择描述信息，UDR#2都是首先根据该请求消息#7获取运营商为UE#B下的第二应用配置的URSP规则。进一步地，若该请求消息#7用于请求获取路由选择描述信息，则UDR#2可以从URSP规则中获取路由选择描述信息；若该请求消息#7用于请求获取第二参数，则UDR#2可以先从URSP规则中获取路由选择描述信息，然后再从路由选择描述信息中获取第二参数。
可选地，UDR#2还可以获取UE#B的签约信息。
S5202a，UDR#2向PCF#2发送第二参数。
可选地，UDR#2还可以向PCF#2发送UE#B的签约信息。
在又一种实现方式中，PCF#2可以根据来自PCF#1的第一中继服务代码决策第二中继服务代码。若该第一中继服务代码包括第一参数的信息，则PCF#2根据该第一中继服务代码决策的第二中继服务代码对应于上文所述的中继服务代码#5；若该第一中继服务代码不包括第一参数的信息，则PCF#2根据该第一中继服务代码决策的第二中继服务代码对应于上文所述的中继服务代码#6。
作为一个示例，PCF#2可以不对第一中继服务代码做处理，将第一中继服务代码决策为第二中继服务代码。
作为另一个示例，PCF#2可以对第一中继服务代码做处理，得到第二中继服务代码。例如，PCF#2可以将第一中继服务代码的前缀决策为第二中继服务代码。再例如，PCF#2可以根据该第一中继服务代码生成第二中继服务代码，该第二中继服务代码与第一中继服务代码对应。
可以理解，若PCF#2处没有保存第一中继服务代码，则PCF#2可以从PCF#1处获取第一中继服务代码。
S5201b，PCF#2向UDR#2发送请求消息#8(所述第七请求消息的一例)。
该请求消息#8用于请求获取PCF#1的信息。
S5202b，UDR#2向PCF#2发送PCF#1的信息。
作为一个示例，UDR#2接收到来自PCF#2的请求消息#8之后，可以向PCF#2发送UE#B所在的拜访地PLMN的标识信息和/或邻近PLMN的标识信息。然后由PCF#2根据该拜访地PLMN的标识信息和/或邻近PLMN标识信息查找该拜访地PLMN和/或邻近PLMN网络中的PCF#1的信息。
作为另一个示例，UDR#2也可在发送至PCF#2的响应消息中直接携带拜访地PLMN的标识信息和/或邻近PLMN的标识信息，以及该拜访地PLMN和/或邻近PLMN网络中的的PCF#1的信息。
可以理解，与UE#B所在的PLMN网络邻近的PLMN网络可以有多个，或者，UE#A所在的PLMN网络和邻近的PLMN网络中分别可以有多个PCF#1，对应地，UDR#2可以获得多个PCF#1的信息。
然后，UDR#2将该多个PCF#1的信息和/或多个PLMN标识信息发送至PCF#2。
若PCF#2收到的是拜访地PLMN标识信息和/或邻近PLMN标识信息，则PCF#2还可通过NRF网元查询该拜访地PLMN和/或邻近PLMN中的PCF#1的信息。
S5203b，PCF#2向PCF#1发送请求消息#9(所述第六请求消息的一例)。
该请求消息#9用于请求获取第一中继服务代码。
该请求消息#9包括以下信息：第二参数、第二应用的标识符。
可选地，该请求消息#9还可以包括UE#B标识信息。
可以理解，PCF#2可以收到多个PCF#1的信息，因此，PCF#2向每个PCF#1都发送该请求消息#9。
S5204b，PCF#1向PCF#2发送第一中继服务代码。
PCF#1收到请求消息#9之后，首先判断该请求消息#9中的第二参数是否与自身所服务的UE#A需要的第一参数相同或等同，若相同或等同，则PCF#1确定PCF#2服务的UE#B支持提供第一应用的中继服务。然后，PCF#1将其为UE#A决策的第一中继服务代码发送 至PCF#2。再例如，PCF#1还可根据本地所保存的中继服务代码列表，判断其中对应的第一参数与第二参数相同或等同的第一中继服务代码，并将符合条件的一个或多个第一中继服务代码发送至PCF#2。
可选地，若该请求消息#9中还包括UE#B的标识信息，则PCF#1还可以判断自身所服务的UE#A是否允许与UE#B建立连接。若允许，则PCF#1将其为UE#A决策的第一中继服务代码发送至PCF#2。
在又一种实现方式中，PCF#2可以根据以下信息决策第二中继服务代码：UE#B的签约信息、第二应用的标识符。该第二中继服务代码可以对应于上文所述的中继服务代码#4。
PCF#2可以将上述信息对应的编码进行哈希运算或采用密钥加密得到第二中继服务代码。
S530，PCF#2通过AMF#2向UE#B发送第二中继服务代码。
PCF#2可以先向AMF#2发送一个响应消息，该响应消息中包括该第二中继服务代码，然后AMF#2将该第二中继服务代码发送至UE#B。
可选地，PCF#2向AMF#2发送的响应消息中还可以包括第二应用的标识符。相对应地，AMF#2向UE#B发送的消息中也可以包括第二应用的标识符。
可选地，PCF#2向AMF#2发送的响应消息中还可以包括UE#B发送第二广播消息对应的无线参数，例如，频带信息、频带适用地理区域、有效时间等。相对应地，AMF#2向UE#B发送的消息中也可以包括无线参数、有效时间等信息。
在本申请实施例中，PCF#2根据UE#B的请求可以为UE#B分配包括第二参数的信息的第二中继服务代码。进一步地，UE#B可以为根据该第二中继服务代码匹配的UE#A提供中继服务。或者，PCF#2还可以为UE#B分配与UE#A相关联的第二中继服务代码，并且可以为该第二中继服务代码对应的UE#A提供中继服务。因此，UE#B可以满足根据该第二中继服务代码匹配的UE#A的需求。
下文结合图6至图9说明远端UE和中继UE以模式B建立PC5连接的方法。需要说明的是，图6至图9中示出的UE#A对应于远端UE，PCF#1为UE#A提供服务；UE#B对应于中继UE，PCF#2为UE#B提供服务。
图6示出了本申请实施例提供的建立的连接的方法的示意性流程图。如图6所示，该方法包括S610-S650，下面详细说明每个步骤。
S610，UE#A从PCF#1获取中继服务代码#2。
该中继服务代码#2包含第一参数的信息。UE#A获取中继服务代码#2的方法可参考方法300，为了简洁，此处不再赘述。
在一种实现方式中，该中继服务代码#2与UE#A待发起的应用相关联，即与UE#A相关联。
在另一种实现方式中，该中继服务代码#2与UE#B支持中继服务的应用相关联，即与UE#B相关联。
S620，UE#B从PCF#2获取中继服务代码#5。
该中继服务代码#5包含第二参数的信息。UE#B获取中继服务代码#5的方法可以参考方法500，为了简洁，此处不再赘述。
在一种实现方式中，该中继服务代码#5与UE#B支持中继服务的应用相关联，即与 UE#B相关联。
在另一种实现方式中，该中继服务代码#5与UE#A待发起的应用相关联，即与UE#A相关联。
S630，UE#A发送第一广播消息。
该第一广播消息中包括中继服务代码#2。
S640，UE#B向UE#A发送响应消息。
该响应消息用于指示UE#B支持以第一参数访问UE#A待发起的应用。
若第一广播消息包括的中继服务代码#2与UE#A待发起的应用相关联，则在UE#B获取的中继服务代码#5与UE#A待发起的应用相关联，或者与UE#B支持中继服务的应用相关联的情况下，UE#B可以根据判断中继服务代码#2是否与中继服务代码#5相同或等同，确定自身是否支持以第一参数访问UE#A待发起的应用。详细的判断方法可以参考方法200，为了简洁，此处不再赘述。
若第一广播消息包括的中继服务代码#2与UE#B支持中继服务的应用相关联，则在UE#B获取的中继服务代码#5同样是与UE#B支持中继服务的应用相关联的情况下，UE#B可以根据判断中继服务代码#2是否与中继服务代码#5相同或等同，确定自身是否支持以第一参数访问UE#A待发起的应用。详细的判断方法可以参考方法200，为了简洁，此处不再赘述。
S650，UE#A向UE#B发送请求消息#5。
该请求消息#5用于请求与UE#B建立PC5连接。
需要说明的是，上文描述的方法600中的各个步骤的先后顺序仅为示例，不应对本申请实施例造成限定。例如，该方法600可以先执行S620，再执行S610；或者，还可以先执行S610和S630，再执行S620。
图7示出了本申请实施例提供的建立的连接的方法的示意性流程图。如图7所示，该方法包括S710-S770，下面详细说明每个步骤。
S710，UE#A从PCF#1获取中继服务代码#1。
该中继服务代码#1不包含第一参数的信息，且该中级服务代码#1与UE#A待发起的应用相关联，即与UE#A相关联。UE#A获取中继服务代码#1的方法可参考方法300，为了简洁，此处不再赘述。
若UE#A本地预配置了中继服务代码#1，则可以不执行S710。
S720，UE#A从PCF#1获取第一参数。
UE#A获取第一参数的方法可参考方法300，为了简洁，此处不再赘述。
若UE#A本地保存了第一参数，则可以不执行S720。
S730，UE#B从PCF#2获取中继服务代码#4。
该中继服务代码#4不包含第二参数的信息，且该中级服务代码#4与UE#B支持中继服务的应用相关联，即与UE#B相关联。UE#A获取中继服务代码#4的方法可参考方法500，为了简洁，此处不再赘述。
若UE#B本地预配置了中继服务代码#4，则可以不执行S730。
S740，UE#B从PCF#2获取第二参数。
若UE#B本地保存了第二参数，则可以不执行S740。
UE#B获取第二参数的方法可参考方法500，为了简洁，此处不再赘述。
S750，UE#A发送第一广播消息。
该第一广播消息中包括中继服务代码#1和第一参数。
S760，UE#B向UE#A发送响应消息。
该响应消息用于指示UE#B支持以第一参数访问UE#A待发起的应用。
UE#B可以根据判断中继服务代码#1是否与中继服务代码#4相同或等同，以及第一参数和第二参数是否一致或等同，确定自身是否支持以第一参数访问UE#A待发起的应用。详细的判断方法可以参考方法200，为了简洁，此处不再赘述。
S770，UE#A向UE#B发送请求消息#5。
该请求消息#5用于请求与UE#B建立PC5连接。
需要说明的是，上文描述的方法700中的各个步骤的先后顺序仅为示例，不应对本申请实施例造成限定。例如，该方法700可以先执行S720，再执行S710；或者，还可以先执行S730-S740，再执行S710-S720。
图8示出了本申请实施例提供的建立的连接的方法的示意性流程图。如图8所示，该方法包括S810-S850，下面详细说明每个步骤。
S810，UE#A从PCF#1获取中继服务代码#1。
该中继服务代码#1不包含第一参数的信息，且该中级服务代码#1与UE#A待发起的应用相关联，即与UE#A相关联。UE#A获取中继服务代码#1的方法可参考方法300，为了简洁，此处不再赘述。
若UE#A本地预配置了中继服务代码#1，则可以不执行S810。
S820，UE#B从PCF#2获取中继服务代码#6。
该中继服务代码#6与UE#A待发起的应用相关联，即与UE#A相关联。UE#B获取中继服务代码#6的方法可参考方法500，为了简洁，此处不再赘述。
S830，UE#A发送第一广播消息。
该第一广播消息中包括中继服务代码#1。
S840，UE#B向UE#A发送响应消息。
该响应消息用于指示UE#B支持以第一参数访问UE#A待发起的应用。
UE#B可以根据判断中继服务代码#1是否与中继服务代码#6相同或等同，确定自身是否支持以第一参数访问UE#A待发起的应用。详细的判断方法可以参考方法200，为了简洁，此处不再赘述。
S850，UE#A向UE#B发送请求消息#5。
该请求消息#5用于请求与UE#B建立PC5连接。
需要说明的是，上文描述的方法800中的各个步骤的先后顺序仅为示例，不应对本申请实施例造成限定。例如，该方法800可以先执行S820，再执行S810；或者，还可以先执行S810和S830，再执行S820。
图9示出了本申请实施例提供的建立的连接的方法的示意性流程图。如图9所示，该方法包括S910-S950，下面详细说明每个步骤。
S910，UE#A从PCF#1获取中继服务代码#3。
该中继服务代码#3与与UE#B支持中继服务的应用相关联，即与UE#B相关联。UE#A 获取中继服务代码#3的方法可参考方法300，为了简洁，此处不再赘述。
S920，UE#B从PCF#2获取中继服务代码#4。
该中继服务代码#4不包含第二参数的信息，且该中级服务代码#4与UE#B支持中继服务的应用相关联，即与UE#B相关联。UE#A获取中继服务代码#4的方法可参考方法500，为了简洁，此处不再赘述。
若UE#B本地预配置了中继服务代码#4，则可以不执行S930。
S930，UE#A发送第一广播消息。
该第一广播消息中包括中继服务代码#3。
S940，UE#B向UE#A发送响应消息。
该响应消息用于指示UE#B支持以第一参数访问UE#A待发起的应用。
UE#B可以根据判断中继服务代码#3是否与中继服务代码#4相同或等同，确定自身是否支持以第一参数访问UE#A待发起的应用。详细的判断方法可以参考方法200，为了简洁，此处不再赘述。
S950，UE#A向UE#B发送请求消息#5。
该请求消息#5用于请求与UE#B建立PC5连接。
需要说明的是，上文描述的方法900中的各个步骤的先后顺序仅为示例，不应对本申请实施例造成限定。例如，该方法900可以先执行S920，再执行S910；或者，还可以先执行S910和S930，再执行S920。
上文示出了模式B场景下，远端UE与中继UE建立PC5连接的方法，模式A场景下，远端UE与中继UE建立PC5连接的方法可参考上述方法，为了简洁，此处不再赘述。
以上，结合图2至图9详细说明了本申请实施例提供的方法。以下，结合图10至图11详细说明本申请实施例提供的装置。
图10是本申请实施例提供的通信装置的示意性框图。如图10所示，该通信装置2000可以包括处理单元2100和收发单元2200。
在一种可能的设计中，该通信装置2000可对应于上文方法实施例中的第一终端设备，例如，可以为第一终端设备，或者配置于第一终端设备中的部件(如芯片或芯片系统)。
应理解，该通信装置2000可对应于根据本申请实施例的方法200、方法300、方法400、方法600、方法700、方法800、方法900中的第一终端设备，该通信装置2000可以包括用于执行图2中的方法200、图3中的方法300、图4中的方法400、图6中方法600、图7中的方法700、图8中的方法800、图9中的方法900中的第一终端设备执行的方法的单元。并且，该通信装置2000中的各单元和上述其他操作和/或功能分别为了实现图2中的方法200、图3中的方法300、图4中的方法400、图6中方法600、图7中的方法700、图8中的方法800、图9中的方法900的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置2000为第一终端设备时，该通信装置2000中的收发单元2200可以通过收发器实现，例如可对应于图11中示出的终端设备3000中的收发器3020，该通信装置2000中的处理单元2100可通过至少一个处理器实现，例如可对应于图11中示出的终端设备3000中的处理器3010。
还应理解，该通信装置2000为配置于第一终端设备中的芯片或芯片系统时，该通信 装置2000中的收发单元2200可以通过输入/输出接口实现，该通信装置2000中的处理单元2100可以通过该芯片或芯片系统上集成的处理器、微处理器或集成电路等实现。
在另一种可能的设计中，该通信装置2000可对应于上文方法实施例中的第二终端设备，例如，可以为第二终端设备，或者配置于第二终端设备中的部件(如芯片或芯片系统)。
应理解，该通信装置2000可对应于根据本申请实施例的方法200、方法300、方法500、方法600、方法700、方法800、方法900中的第二终端设备，该通信装置2000可以包括用于执行图2中的方法200、图3中的方法300、图5中的方法500、图6中方法600、图7中的方法700、图8中的方法800、图9中的方法900中的第二终端设备执行的方法的单元。并且，该通信装置2000中的各单元和上述其他操作和/或功能分别为了实现图2中的方法200、图3中的方法300、图5中的方法500、图6中方法600、图7中的方法700、图8中的方法800、图9中的方法900的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置2000为第二终端设备时，该通信装置2000中的收发单元2200可以通过收发器实现，例如可对应于图11中示出的终端设备3000中的收发器3020，该通信装置2000中的处理单元2100可通过至少一个处理器实现，例如可对应于图11中示出的终端设备3000中的处理器3010。
还应理解，该通信装置2000为配置于第二终端设备中的芯片或芯片系统时，该通信装置2000中的收发单元2200可以通过输入/输出接口实现，该通信装置2000中的处理单元2100可以通过该芯片或芯片系统上集成的处理器、微处理器或集成电路等实现。
在另一种可能的设计中，该通信装置2000可对应于上文方法实施例中的第一策略控制网元，例如，可以为第一策略控制网元，或者配置于第一策略控制网元中的部件(如芯片或芯片系统)。
应理解，该通信装置2000可对应于根据本申请实施例的方法300、方法600、方法700、方法800、方法900中的第一策略控制网元，该通信装置2000可以包括用于执行图3中的方法300、图6中方法600、图7中的方法700、图8中的方法800、图9中的方法900中的第一策略控制网元执行的方法的单元。并且，该通信装置2000中的各单元和上述其他操作和/或功能分别为了实现图3中的方法300、图6中方法600、图7中的方法700、图8中的方法800、图9中的方法900的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该通信装置2000可对应于上文方法实施例中的第二策略控制网元，例如，可以为第二策略控制网元，或者配置于第二策略控制网元中的部件(如芯片或芯片系统)。
应理解，该通信装置2000可对应于根据本申请实施例的方法500、方法600、方法700、方法800、方法900中的第二策略控制网元，该通信装置2000可以包括用于执行图5中的方法500、图6中方法600、图7中的方法700、图8中的方法800、图9中的方法900中的第二策略控制网元执行的方法的单元。并且，该通信装置2000中的各单元和上述其他操作和/或功能分别为了实现图5中的方法500、图6中方法600、图7中的方法700、图8中的方法800、图9中的方法900的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
图11是本申请实施例提供的终端设备3000的结构示意图。该终端设备3000可应用于如图1所示的系统中，执行上述方法实施例中终端设备的功能。如图所示，该终端设备3000包括处理器3010和收发器3020。可选地，该终端设备3000还包括存储器3030。其中，处理器3010、收发器3002和存储器3030之间可以通过内部连接通路互相通信，传递控制和/或数据信号，该存储器3030用于存储计算机程序，该处理器3010用于从该存储器3030中调用并运行该计算机程序，以控制该收发器3020收发信号。可选地，终端设备3000还可以包括天线3040，用于将收发器3020输出的上行数据或上行控制信令通过无线信号发送出去。
上述处理器3010可以和存储器3030可以合成一个处理装置，处理器3010用于执行存储器3030中存储的程序代码来实现上述功能。具体实现时，该存储器3030也可以集成在处理器3010中，或者独立于处理器3010。该处理器3010可以与图10中的处理单元2100对应。
上述收发器3020可以与图10中的收发单元2200对应，也可以称为收发单元。收发器2020可以包括接收器(或称接收机、接收电路)和发射器(或称发射机、发射电路)。其中，接收器用于接收信号，发射器用于发射信号。
应理解，图11所示的终端设备3000能够实现图2、图3、图4以及图6至图9中所示方法实施例中涉及第一终端设备的各个过程。终端设备3000中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详细描述。
上述处理器3010可以用于执行前面方法实施例中描述的由第一终端设备内部实现的动作，如确定第二参数是否与第一参数相同或等同等。收发器3020可以用于执行前面方法实施例中描述的第一终端设备发送或从第二终端设备接收的动作，如发送广播消息和请求消息，接收响应消息等。具体请见前面方法实施例中的描述，此处不再赘述。
还应理解，图11所示的终端设备3000能够实现图2以及图4至图9中所示方法实施例中涉及第二终端设备的各个过程。终端设备3000中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详细描述。
上述处理器3010可以用于执行前面方法实施例中描述的由第二终端设备内部实现的动作，如确定是否支持提供第一应用的中继服务等。收发器3020可以用于执行前面方法实施例中描述的第二终端设备向第一终端设备发送或从第一终端设备接收的动作，如发送广播消息和响应消息，接收请求消息等。具体请见前面方法实施例中的描述，此处不再赘述。
其中，上述终端设备3000还可以包括电源3050，用于给终端设备中的各种器件或电路提供电源。
除此之外，为了使得终端设备的功能更加完善，该终端设备3000还可以包括输入单元3060、显示单元3070、音频电路3080、摄像头3090和传感器3100等中的一个或多个，所述音频电路还可以包括扬声器3082、麦克风3084等。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器用于执行上述任一方法实施例中的方法。
应理解，上述处理装置可以是一个或多个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图2至图9所示实施例中第一终端设备、第二终端设备、第一策略控制网元和第二策略控制 网元分别执行的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图2至图9所示实施例中第一终端设备、第二终端设备、第一策略控制网元和第二策略控制网元分别执行的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的一个或多个终端设备以及一个或多个策略控制网元。
上述各个装置实施例中策略控制网元与终端设备和方法实施例中的策略控制网元或终端设备完全对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，各功能单元的功能可以全部或部分地通过软件、硬件、固件或者其 任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令(程序)。在计算机上加载和执行所述计算机程序指令(程序)时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (45)

  1. 一种建立连接的方法，其特征在于，包括：
    第一终端设备发送第一广播消息，所述第一广播消息包括第一中继服务代码，所述第一中继服务代码包括第一参数的信息，所述第一参数是访问第一应用对应的参数，所述第一应用是所述第一终端设备待发起的应用；
    所述第一终端设备接收来自第二终端设备的响应消息，所述响应消息用于指示所述第二终端设备支持以所述第一参数访问所述第一应用。
  2. 根据权利要求1所述的方法，其特征在于，所述第一参数包括以下参数中的一种或多种：数据网络名称DNN、单切片选择辅助信息S-NASSI、会话和服务连续SSC模式、协议数据单元PDU会话类型、接入方式优先级、非第三代合作伙伴计划3GPP分流指示。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一中继服务代码与所述第一应用相关联。
  4. 根据权利要求1或2所述的方法，其特征在于，所述第一中继服务代码与第二应用相关联，所述第二应用是所述第二终端设备支持中继服务的应用。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端设备通过接入和移动管理AMF网元向第一策略控制PCF网元发送第一请求消息，所述第一请求消息用于请求获取所述第一中继服务代码；
    所述第一终端设备接收来自所述第一PCF网元的所述第一中继服务代码。
  6. 根据权利要求5所述的方法，其特征在于，所述第一请求消息包括以下信息：所述第一终端设备的标识信息、请求类型、所述第一应用的标识符。
  7. 根据权利要求6所述的方法，其特征在于，所述第一请求消息还包括降级指示信息，所述降级指示信息用于指示所述第一终端设备是否接受服务降级。
  8. 一种建立连接的方法，其特征在于，包括：
    第二终端设备接收第一广播消息，所述第一广播消息包括第一中继服务代码，所述第一中继服务代码包括第一参数的信息，所述第一参数是访问第一应用对应的参数，所述第一应用是所述第一终端设备待发起的应用；
    所述第二终端设备向所述第一终端发送响应消息，所述响应消息用于指示所述第二终端设备支持以所述第一参数访问所述第一应用。
  9. 根据权利要求8所述的方法，其特征在于，所述第一参数包括以下参数中的一种或多种：数据网络名称DNN、单切片选择辅助信息S-NASSI、会话和服务连续SSC模式、协议数据单元PDU会话类型、接入方式优先级、非第三代合作伙伴计划3GPP分流指示。
  10. 根据权利要求8或9所述的方法，其特征在于，在所述第二终端设备向所述第一终端设备发送响应消息之前，所述方法还包括：
    所述第二终端设备确定是否支持以所述第一参数访问所述第一应用。
  11. 根据权利要求8或9所述的方法，其特征在于，所述第一中继服务代码与所述第一应用相关联，
    所述方法还包括：
    所述第二终端设备根据所述第一中继服务代码是否与第二中继服务代码相同或等同，确定是否支持以所述第一参数访问所述第一应用，所述第二中继服务代码与所述第一应用或第二应用相关联，所述第二应用是所述第二终端设备支持中继服务的应用，所述第二中继服务代码是所述第二终端设备保存的中继服务代码。
  12. 根据权利要求8或9所述的方法，其特征在于，所述第一中继服务代码与第二应用相关联，所述第二应用是所述第二终端设备支持中继服务的应用，
    所述方法还包括：
    所述第二终端设备根据所述第一中继服务代码是否与第二中继服务代码相同或等同，确定是否支持以所述第一参数访问所述第一应用，所述第二中继服务代码与所述第二应用相关联，所述第二中继服务代码是所述第二终端设备保存的中继服务代码。
  13. 一种获取中继服务代码的方法，其特征在于，包括：
    第一策略控制PCF网元接收来自第一终端设备的第一请求消息，所述第一请求消息用于请求获取第一中继服务代码，所述第一中继服务代码包括第一参数的信息，所述第一参数是访问第一应用对应的参数，所述第一应用是所述第一终端设备待发起的应用；
    所述第一PCF网元根据所述第一参数决策所述第一中继服务代码；
    所述第一PCF网元通过接入和移动管理AMF网元向所述第一终端设备发送所述第一中继服务代码。
  14. 根据权利要求13所述的方法，其特征在于，所述第一参数包括以下参数中的一种或多种：数据网络名称DNN、单切片选择辅助信息S-NASSI、会话和服务连续SSC模式、协议数据单元PDU会话类型、接入方式优先级、非第三代合作伙伴计划3GPP分流指示。
  15. 根据权利要求13或14所述的方法，其特征在于，所述第一中继服务代码与所述第一应用相关联，以及
    所述第一PCF网元根据所述第一参数决策所述第一中继服务代码，包括：
    所述第一PCF网元根据所述第一参数和以下信息决策所述第一中继服务代码：
    所述第一终端设备的签约信息、所述第一应用的标识符。
  16. 根据权利要求13或14所述的方法，其特征在于，所述第一中继服务代码与所述第一应用相关联，以及
    所述第一PCF网元根据所述第一参数决策所述中继服务代码，包括：
    所述第一PCF网元根据所述第一参数和以下信息决策所述第一中继服务代码：
    所述第一终端设备的签约信息、所述第一应用的标识符、降级指示信息，所述降级指示信息用于指示所述第一终端设备是否接受服务降级。
  17. 根据权利要求13或14所述的方法，其特征在于，所述第一中继服务代码与第二应用相关联，所述第二应用是所述终端设备支持中继服务的应用，以及
    所述第一PCF网元根据所述第一参数决策所述第一中继服务代码，包括：
    所述第一PCF网元向第二PCF网元发送第二请求消息，所述第二请求消息用于请求获取第二中继服务代码，所述第二中继服务代码与所述第二应用相关联，所述第二请求消息包括所述第一参数和所述第一应用的标识符；
    所述第一PCF网元接收来自所述第二PCF网元的所述第二中继服务代码；
    所述第一PCF网元根据所述第二中继服务代码决策所述第一中继服务代码。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    所述第一PCF网元向统一数据仓库UDR网元发送第三请求消息，所述第三请求消息用于请求获取第二PCF的信息；
    所述第一PCF网元接收来自所述UDR网元的所述第二PCF的信息。
  19. 根据权利要求13至18中任一项所述的方法，其特征在于，所述第一请求消息包括以下信息：所述第一终端设备的标识信息、请求类型、所述第一应用的标识符。
  20. 根据权利要求19所述的方法，其特征在于，所述第一请求消息还包括降级指示信息，所述降级指示信息用于指示所述第一终端设备是否接受服务降级。
  21. 一种建立连接的方法，其特征在于，包括：
    第二终端设备发送第二广播消息，所述第二广播消息包括第二中继服务代码，所述第二中继服务代码包括第二参数的信息，所述第二参数是访问第二应用对应的参数，所述第二应用是所述第二终端设备支持中继服务的应用；
    所述第二终端设备接收来自第一终端设备的第四请求消息，所述第四请求消息用于请求与所述第二终端设备建立PC5连接。
  22. 根据权利要求21所述的方法，其特征在于，所述第二参数包括以下参数中的一种或多种：数据网络名称DNN、单切片选择辅助信息S-NASSI、会话和服务连续SSC模式、协议数据单元PDU会话类型、接入方式优先级、非第三代合作伙伴计划3GPP分流指示。
  23. 根据权利要求21或22所述的方法，其特征在于，所述第二中继服务代码与所述第二应用相关联。
  24. 根据权利要求21或22所述的方法，其特征在于，所述第二中继服务代码与第一应用相关联，所述第一应用是所述第一终端设备待发起应用。
  25. 根据权利要求21至24中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二终端设备通过接入和移动管理AMF网元向第二策略控制PCF网元发送第五请求消息，所述第五请求消息用于请求获取所述第二中继服务代码；
    所述第二终端设备接收来自所述第二PCF网元的所述第二中继服务代码。
  26. 根据权利要求25所述的方法，其特征在于，所述第五请求消息包括以下信息：所述第二终端设备的标识信息、请求类型、所述第二应用的标识符。
  27. 一种建立连接的方法，其特征在于，包括：
    第一终端设备接收第二广播消息，所述第二广播消息包括第二中继服务代码，所述第二中继服务代码包括第二参数的信息，所述第二参数是访问第二应用对应的参数，所述第二应用是所述第二终端设备支持中继服务的应用；
    所述第一终端设备向所述第二终端设备发送第四请求消息，所述第四请求消息用于请求与所述第二终端设备建立PC5连接。
  28. 根据权利要求27所述的方法，其特征在于，所述第二参数包括以下参数中的一种或多种：数据网络名称DNN、单切片选择辅助信息S-NASSI、会话和服务连续SSC模式、协议数据单元PDU会话类型、接入方式优先级、非第三代合作伙伴计划3GPP分流指示。
  29. 根据权利要求27或28所述的方法，其特征在于，在所述第一终端设备向所述第二终端设备发送第四请求消息之前，所述方法还包括：
    所述第一终端设备确定所述第二终端设备是否支持以第一参数访问第一应用，所述第一应用是所述第一终端设备待发起的应用，所述第一参数是访问所述第一应用对应的参数。
  30. 根据权利要求27或28所述的方法，其特征在于，所述第二中继服务代码与所述第二应用相关联，
    所述方法还包括：
    所述第一终端设备根据所述第二中继服务代码是否与第一中继服务代码相同或等同，确定所述第二终端设备是否支持以第一参数访问所述第二应用，所述第一中继服务代码是所述第一终端设备保存的中继服务代码，所述第一中继服务代码与所述第二应用或第一应用相关联，所述第一应用是所述第一终端设备待发起的应用，所述第一参数是访问所述第一应用对应的参数。
  31. 根据权利要求27或28所述的方法，其特征在于，所述第二中继服务代码与第一应用相关联，所述第一应用是所述第一终端设备待发起的应用，
    所述方法还包括：
    所述第一终端设备根据所述第二中继服务代码是否与第一中继服务代码相同或等同，确定所述第二终端设备是否支持以第一参数访问所述第一应用，所述第一中继服务代码是所述第一终端设备保存的中继服务代码，所述第二中继服务代码与所述第一应用相关联，所述第一参数是访问所述第一应用对应的参数。
  32. 根据权利要求29至31中任一项所述的方法，其特征在于，所述第一参数包括以下参数中的一种或多种：DNN、S-NASSI、SSC模式、PDU会话类型、接入方式优先级、非3GPP分流指示。
  33. 一种获取中继服务代码的方法，其特征在于，包括：
    第二策略控制PCF网元接收来自第二终端设备的第五请求消息，所述第五请求消息用于请求获取第二中继服务代码，所述第二中继服务代码包括第二参数的信息，所述第二参数是访问第二应用对应的参数，所述第二应用是所述第二终端设备支持中继服务的应用；
    所述第二PCF网元根据所述第二参数决策所述第二中继服务代码；
    所述第二PCF网元通过接入和移动管理AMF网元向所述第二终端设备发送所述第二中继服务代码。
  34. 根据权利要求33所述的方法，其特征在于，所述第二参数包括以下参数中的一种或多种：数据网络名称DNN、单切片选择辅助信息S-NASSI、会话和服务连续SSC模式、协议数据单元PDU会话类型、接入方式优先级、非第三代合作伙伴计划3GPP分流指示。
  35. 根据权利要求33或34所述的方法，其特征在于，所述第二中继服务代码与所述第二应用相关联，以及
    所述第二PCF网元根据所述第二参数决策所述第二中继服务代码，包括：
    所述第二PCF网元根据所述第二参数和以下信息决策所述第二中继服务代码：
    所述第二终端设备的签约信息、所述第二应用的标识符。
  36. 根据权利要求33或34所述的方法，其特征在于，所述第二中继服务代码与第一应用相关联，所述第一应用是所述第一终端设备待发起应用，以及
    所述第二PCF网元根据所述第二参数决策所述第二中继服务代码，包括：
    所述第二PCF网元向第一PCF网元发送第六请求消息，所述第六请求消息用于请求获取第一中继服务代码，所述第一中继服务代码与所述第一应用相关联，所述第六请求消息包括所述第二参数和所述第二应用的标识符；
    所述第二PCF网元接收来自所述第一PCF网元的所述第一中继服务代码；
    所述第二PCF网元根据所述第一中继服务代码决策所述第二中继服务代码。
  37. 根据权利要求36所述的方法，其特征在于，所述方法还包括：
    所述第二PCF网元向统一数据仓库UDR网元发送第七请求消息，所述第七请求消息用于请求获取第一PCF的信息；
    所述第二PCF网元接收来自所述UDR网元的所述第一PCF的信息。
  38. 根据权利要求33至37中任一项所述的方法，其特征在于，所述第五请求消息包括以下信息：
    所述第二终端设备的标识信息、请求类型、所述第二应用的标识符。
  39. 一种建立连接的方法，其特征在于，包括：
    第一终端设备发送第一广播消息，所述第一广播消息包括第三中继服务代码和第一参数，所述第一参数是访问第一应用对应的参数，所述第一应用是所述第一终端设备待发起的应用；
    所述第一终端设备接收来自第二终端设备的响应消息，所述响应消息用于指示所述第二终端设备支持以所述第一参数访问所述第一应用。
  40. 根据权利要求39所述的方法，其特征在于，所述第一参数包括以下参数中的一种或多种：数据网络名称DNN、单切片选择辅助信息S-NASSI、会话和服务连续SSC模式、协议数据单元PDU会话类型、接入方式优先级、非第三代合作伙伴计划3GPP分流指示。
  41. 一种建立连接的方法，其特征在于，包括：
    第二终端设备发送第二广播消息，所述第二广播消息包括第二中继服务代码和第二参数，所述第二参数是访问第二应用对应的参数，所述第二应用是所述第二终端设备支持中继服务的应用；
    所述第二终端设备接收来自第一终端设备的请求消息，所述请求消息用于请求与所述第二终端设备建立PC5连接。
  42. 根据权利要求41所述的方法，其特征在于，所述第二参数包括以下参数中的一种或多种：数据网络名称DNN、单切片选择辅助信息S-NASSI、会话和服务连续SSC模式、协议数据单元PDU会话类型、接入方式优先级、非第三代合作伙伴计划3GPP分流指示。
  43. 一种通信装置，其特征在于，包括用于实现如权利要求1至42中任一项所述的方法的单元。
  44. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机指令，以使得所述装置执行：如权利要求1至42中任一项所述的方法。
  45. 一种计算机可读存储介质，其特征在于，其上存储有计算机程序，所述计算机程序被执行时，以使得执行如权利要求1至42中任一项所述的方法。
PCT/CN2020/111204 2019-12-30 2020-08-26 建立连接和获取中继服务代码的方法和通信装置 WO2021135295A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20908647.9A EP4072234A4 (en) 2019-12-30 2020-08-26 PROCEDURE FOR ESTABLISHING A CONNECTION AND OBTAINING A RELAY SERVICE CODE AND COMMUNICATION DEVICE
US17/851,403 US20220330361A1 (en) 2019-12-30 2022-06-28 Method for establishing connection and obtaining relay service code and communications apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911391368.4 2019-12-30
CN201911391368.4A CN113133085B (zh) 2019-12-30 2019-12-30 建立连接和获取中继服务代码的方法和通信装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/851,403 Continuation US20220330361A1 (en) 2019-12-30 2022-06-28 Method for establishing connection and obtaining relay service code and communications apparatus

Publications (1)

Publication Number Publication Date
WO2021135295A1 true WO2021135295A1 (zh) 2021-07-08

Family

ID=76686395

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/111204 WO2021135295A1 (zh) 2019-12-30 2020-08-26 建立连接和获取中继服务代码的方法和通信装置

Country Status (4)

Country Link
US (1) US20220330361A1 (zh)
EP (1) EP4072234A4 (zh)
CN (2) CN114885439A (zh)
WO (1) WO2021135295A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023283901A1 (zh) * 2021-07-15 2023-01-19 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端设备、网络设备
WO2023143459A1 (zh) * 2022-01-29 2023-08-03 华为技术有限公司 授权方法及装置

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210352767A1 (en) * 2020-05-11 2021-11-11 Qualcomm Incorporated Relay adaptation protocol layer configuration
WO2022156517A1 (en) * 2021-01-25 2022-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for relay service code management
US11792726B2 (en) * 2021-05-06 2023-10-17 Apple Inc. Network slice configuration for device to device communication
CN115915022A (zh) * 2021-08-16 2023-04-04 大唐移动通信设备有限公司 组播广播业务数据传输方法、装置、设备以及存储介质
US20230090671A1 (en) * 2021-09-23 2023-03-23 Qualcomm Incorporated Configuration and signaling techniques for scheduled wireless communications
CN117296351A (zh) * 2022-04-18 2023-12-26 北京小米移动软件有限公司 中继通信方法、装置、通信设备及存储介质
CN114928871B (zh) * 2022-05-13 2024-02-06 中国电信股份有限公司 中继流量的方法、网络接入方法及终端、介质及设备
CN117460019A (zh) * 2022-07-19 2024-01-26 中国电信股份有限公司 确定中继终端的方法、装置和系统
WO2024031725A1 (zh) * 2022-08-12 2024-02-15 北京小米移动软件有限公司 中继通信的安全机制校验方法和装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107409429A (zh) * 2015-03-25 2017-11-28 高通股份有限公司 中继发现和关联消息
WO2018084788A1 (en) * 2016-11-02 2018-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Mobility management for relaying
CN109429361A (zh) * 2017-07-18 2019-03-05 华为技术有限公司 会话处理方法及装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104113821A (zh) * 2013-04-16 2014-10-22 中兴通讯股份有限公司 一种用户设备间的发现方法、系统及装置
CN108770074B (zh) * 2014-12-22 2022-09-30 中兴通讯股份有限公司 实现设备直通中继选择的方法、网络控制节点和用户设备
US10609744B2 (en) * 2015-10-22 2020-03-31 Lg Electronics Inc. Method for direct communication between terminals in wireless communication system and apparatus for method
WO2018126452A1 (zh) * 2017-01-06 2018-07-12 华为技术有限公司 授权验证方法和装置
CN115297555A (zh) * 2017-01-09 2022-11-04 Idac控股公司 无线通信系统的中继
US10932175B2 (en) * 2017-03-21 2021-02-23 Lg Electronics Inc. Method for relay terminal to select remote terminal where access control is applied due to network congestion and relay terminal performing method
CN113301518A (zh) * 2018-04-09 2021-08-24 华为技术有限公司 通信方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107409429A (zh) * 2015-03-25 2017-11-28 高通股份有限公司 中继发现和关联消息
WO2018084788A1 (en) * 2016-11-02 2018-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Mobility management for relaying
CN109429361A (zh) * 2017-07-18 2019-03-05 华为技术有限公司 会话处理方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4072234A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023283901A1 (zh) * 2021-07-15 2023-01-19 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端设备、网络设备
WO2023143459A1 (zh) * 2022-01-29 2023-08-03 华为技术有限公司 授权方法及装置

Also Published As

Publication number Publication date
US20220330361A1 (en) 2022-10-13
EP4072234A4 (en) 2023-02-22
CN113133085B (zh) 2022-05-13
CN113133085A (zh) 2021-07-16
CN114885439A (zh) 2022-08-09
EP4072234A1 (en) 2022-10-12

Similar Documents

Publication Publication Date Title
WO2021135295A1 (zh) 建立连接和获取中继服务代码的方法和通信装置
CN110366271B (zh) 通信方法和通信装置
KR102050201B1 (ko) 네트워크 슬라이스 선택
RU2741946C1 (ru) Радиотерминал, радиостанция, узел базовой сети и способ в них
US11706705B2 (en) Multimedia priority service
WO2020029938A1 (zh) 安全会话方法和装置
WO2020248828A1 (zh) 通信方法、装置及系统
US20220217611A1 (en) Service Configuration Method, Communication Apparatus, and Communication System
WO2019062499A1 (zh) 一种策略确定的方法及通信装置
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
US20210168151A1 (en) Method for implementing user plane security policy, apparatus, and system
CN111404814B (zh) 一种数据传输的方法及通信装置
TWI757595B (zh) 截取感知接取點選擇技術
US20220110023A1 (en) Method, Apparatus, and System for Managing Background Data Transfer Policy
US11102656B2 (en) Network access authorization method, related device, and system
CN110557846B (zh) 一种数据传输方法、终端设备及网络设备
WO2019196680A1 (zh) 通信方法和通信装置
WO2019223425A1 (zh) 一种用于终止接入和移动性管理策略关联的方法和装置
WO2023051430A1 (zh) 通信的方法和装置
WO2023011630A1 (zh) 授权验证的方法及装置
CN113329392B (zh) 家庭网关接入网络的方法和通信装置
WO2020233496A1 (zh) 安全会话方法和装置
CN114916018A (zh) 通信方法及通信装置
US20230413216A1 (en) Information processing method and apparatus, communication device, and readable storage medium
CN112153647B (zh) 通信方法和相关设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20908647

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020908647

Country of ref document: EP

Effective date: 20220705

NENP Non-entry into the national phase

Ref country code: DE