Method, device and terminal for determining establishment of relay PDU session

Abstract

The present application discloses a method, device and terminal for determining the establishment of a relay PDU session, which belongs to the field of communication technology. The method of an embodiment of the present application includes: a relay terminal receives first information sent by a remote terminal, wherein the first information is used to determine a user terminal routing selection policy URSP; the relay terminal determines the URSP according to the first information; the relay terminal determines a routing descriptor matching the URSP based on PDU session parameters; the relay terminal determines whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal. Through the present application, the problem that the relay terminal cannot determine the routing descriptor or URSP in the prior art, resulting in the inability to establish a relay PDU session later, is solved.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a method, device and terminal for determining the establishment of a relay PDU session. Background Art

[0002] In the prior art, during the discovery phase, a relay UE will issue multiple different relay service codes, where a data protocol unit (PDU) session parameter corresponding to a relay service code corresponds to multiple service descriptors. Therefore, the relay UE cannot determine the corresponding PDU session parameters (such as routing descriptors) or user equipment routing selection policies (URSP), resulting in the inability to establish a relay PDU session later. Summary of the invention

[0003] The embodiments of the present application provide a method, device and terminal for determining the establishment of a relay PDU session, which can solve the problem in the prior art that the relay terminal cannot determine the routing descriptor or URSP, resulting in the subsequent inability to establish a relay PDU session.

[0004] In a first aspect, a method for determining establishment of a relay data protocol unit (PDU) session is provided, comprising: a relay terminal receives first information sent by a remote terminal, wherein the first information is used to determine a user terminal routing selection policy (URSP); the relay terminal determines the URSP based on the first information; the relay terminal determines a routing descriptor matching the URSP based on PDU session parameters; the relay terminal determines whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal.

[0005] In a second aspect, a method for determining establishment of a relay PDU session is provided, comprising: a remote terminal sending first information to a relay terminal, wherein the first information is used to determine a user terminal routing selection strategy URSP:

[0006] According to a third aspect, a device for determining establishment of a relay PDU session is provided, which is applied to a relay terminal and includes: a first receiving module for receiving first information sent by a remote terminal, wherein the first information is used to determine a user terminal routing selection policy URSP; a first determining module for determining the URSP according to the first information; a second determining module for determining a routing descriptor matching the URSP based on PDU session parameters; and a third determining module for determining whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal.

[0007] In a fourth aspect, a device for determining establishment of a relay PDU session is provided, which is applied to a remote terminal and includes: a first sending module, used to send first information to the relay terminal, wherein the first information is used to determine a user terminal routing selection strategy URSP.

[0008] In a fifth aspect, a terminal is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0009] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive first information sent by a remote terminal, wherein the first information is used to determine a user terminal routing selection strategy URSP; the processor is used to determine the URSP based on the first information, and determine a routing descriptor matching the URSP based on PDU session parameters, and determine whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal.

[0010] In the seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0011] In an eighth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in aspect..., or to implement the method described in aspect 2.

[0012] In the ninth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement the method steps as described in the first aspect, or to implement the method steps as described in the second aspect.

[0013] In the embodiment of the present application, the relay terminal can determine the corresponding URSP according to the received first information, and then determine the routing descriptor matching the URSP according to the session parameters, and then determine whether there is a matching relay PDU session according to the routing descriptor. It can be seen that through the embodiment of the present application, the relay terminal can determine the URSP and its corresponding routing descriptor, that is, determine the basis for establishing the subsequent relay PDU session, thereby solving the problem in the prior art that the relay terminal cannot determine the routing descriptor or URSP, resulting in the subsequent inability to establish a relay PDU session. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 A block diagram showing a wireless communication system to which the embodiments of the present application can be applied;

[0015] Figure 2 is a flowchart of the establishment process of L3 in an embodiment of the present application;

[0016] Figure 3 It is one of the flowcharts of the method for determining the establishment of a relay PDU session in an embodiment of the present application;

[0017] Figure 4 This is the second flowchart of the method for determining the establishment of a relay PDU session in an embodiment of the present application;

[0018] Figure 5 is a flow chart of establishing a relay PDU session in an embodiment of the present application;

[0019] Figure 6 It is one of the structural diagrams of the apparatus for determining the establishment of a relay PDU session according to an embodiment of the present application;

[0020] Figure 7 This is a second structural diagram of a method for determining the establishment of a relay PDU session according to an embodiment of the present application;

[0021] Figure 8 is a schematic diagram of the structure of a communication device according to an embodiment of the present application;

[0022] Fig. 9 It is a schematic diagram of the structure of the terminal of an embodiment of the present application. DETAILED DESCRIPTION

[0023] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0024] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0025] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0026] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a smart watch, a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0027] First, the relevant terms in the embodiments of the present application are explained;

[0028] 1. Relay service code

[0029] The relay service code is used to identify the connection service provided by the relay UE and the authorized user to whom the relay UE will provide the service, and may select related security policies or information, such as those required for authentication and authorization between the remote UE and the relay UE.

[0030] For L3 relay, each relay service code will be associated with a set of PDU session parameters as UE prose policy configuration to the relay terminal and the remote terminal, where the PDU session parameters include at least one of the following: PDU session type, data network name (Data Network Name, DNN), service and session continuity (Service and Session Continuity, SSC) mode, network slice selection assistance information (Network Slice Selection Assistance Information, NSSAI), and preferred access type (Access Type Preference).

[0031] When the relay terminal and the remote terminal perform corresponding discovery processes, the discovery message will carry a relay service code, and the remote terminal determines whether to select the relay terminal (mode A) based on the relay service code sent by the relay terminal.

[0032] 2. The establishment process of L3

[0033] like Figure 2 As shown, in the above step 110, when or after establishing a one-to-one L2 link with the relay terminal, the remote terminal establishes a relay PDU session for the remote terminal for relaying / forwarding the service data of the remote terminal.

[0034] 3. Principles for establishing PDU sessions

[0035] The establishment of a PDU session is determined based on the URSP. For the L3 relay mentioned above, the relay PDU session belongs to the relay terminal, so the relay terminal also establishes the relay PDU session based on its own URSP. Therefore, the remote terminal and the relay terminal must have a unified understanding of the establishment of the relay PDU session, otherwise the PDU session established by the relay terminal does not meet the service requirements of the relay terminal. The current unified understanding can determine how to establish a PDU session from the association between the configured relay service code and the PDU session parameters. Since the relay terminal and the relay terminal may have the same configuration as above, the parameters for establishing the relay PDU session meet the requirements of the remote UE.

[0036] The following, in combination with the accompanying drawings, describes in detail the method for determining the establishment of a relay PDU session provided in the embodiment of the present application through some embodiments and their application scenarios.

[0037] like Figure 3 As shown, an embodiment of the present application provides a method for determining the establishment of a relay PDU session, the steps of the method comprising:

[0038] Step 302: The relay terminal receives first information sent by the remote terminal, wherein the first information is used to determine the user terminal routing selection strategy URSP;

[0039] Step 304: The relay terminal determines the URSP according to the first information;

[0040] Step 306, the relay terminal determines a routing descriptor matching the URSP based on the PDU session parameters;

[0041] Step 308: The relay terminal determines whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal.

[0042] Through the above steps 302 to 308 of the embodiment of the present application, the relay terminal can determine the corresponding URSP according to the received first information, and then determine the routing descriptor matching the URSP according to the session parameters, and then determine whether there is a matching relay PDU session according to the routing descriptor. It can be seen that through the embodiment of the present application, the relay terminal can determine the URSP and its corresponding routing descriptor, that is, determine the basis for establishing the subsequent relay PDU session, thereby solving the problem in the prior art that the relay terminal cannot determine the routing descriptor or URSP, resulting in the inability to establish the relay PDU session subsequently.

[0043] In an optional implementation manner of the embodiment of the present application, the method of the embodiment of the present application further includes one of the following:

[0044] Step 310: if there is a first PDU session matching the routing descriptor and the first PDU session is not used for relaying service data of the remote terminal, the relay terminal establishes a relay PDU session;

[0045] Step 312: if there is a second PDU session matching the routing descriptor, and the second PDU session is used to relay and forward the service data of the remote terminal, the relay terminal reuses the second PDU session as the relay PDU session;

[0046] Step 314: When there is no PDU session matching the routing descriptor, the relay terminal establishes a relay PDU session.

[0047] It can be known from the above steps 310 to 314 that, in the absence of a PDU session matching the routing descriptor, the relay terminal will establish a relay PDU session. If there is a PDU session matching the routing descriptor, and the PDU session is not used to relay the service data of the remote terminal, a relay PDU session also needs to be established. If the PDU session is used to relay the service data of the remote terminal, there is no need to establish a new relay PDU session, and the PDU session is multiplexed as a relay PDU session. It can be seen that in either case, the relay terminal can establish the relay PDU session, or multiplex the PDU session that can be used to relay and forward remote service data into a relay PDU session to determine the relay PDU session that meets the needs of the remote terminal.

[0048] It should be noted that the relay terminal in the embodiment of the present application is a relay terminal selected by the remote terminal during the discovery phase based on the relay service code. The relay service code is a relay service code that meets business requirements and is selected by the remote terminal during the discovery phase.

[0049] In an optional implementation manner of the embodiment of the present application, the first information in the embodiment of the present application includes at least one of the following:

[0050] 1) Traffic descriptor; 2) Application descriptors;

[0051] 3) Internet Protocol (IP) descriptors (IP descriptors); 4) Non-IP descriptors (Non-IP descriptors); 5) Domain descriptors (Domain descriptors); 6) Data Network Name DNN; 7) Connection Capabilities; 8) Target address information.

[0052] It should be noted that the service descriptor may also be referred to as a traffic descriptor in other application scenarios. In addition, the target address information may refer to a target IP, a target MAC, and the like.

[0053] In an optional implementation manner of the embodiment of the present application, the manner in which the relay terminal determines the URSP according to the first information involved in step 304 of the present application may further include:

[0054] Step 304-11, the relay terminal selects a first service descriptor that matches the service descriptor in the first information from the service descriptors in the configured URSP rule;

[0055] Step 304-12: The relay terminal selects a URSP that matches the first service descriptor.

[0056] Through the above steps 304-11 and 304-12, it is necessary to match the service descriptor in the first information with the service descriptor in the configured URSP rule, so as to further select the corresponding URSP according to the matched service descriptor, that is, the required URSP can be accurately determined.

[0057] In an optional implementation manner of the embodiment of the present application, before the relay terminal determines the routing descriptor matching the URSP based on the PDU session parameters, the method steps of the embodiment of the present application further include one of the following:

[0058] Step 300, the relay terminal obtains the relay service code from the local;

[0059] Step 301: The relay terminal receives second information sent by the remote terminal, wherein the remote terminal carries a relay service code;

[0060] Among them, the relay service code is associated with the PDU session parameter.

[0061] Based on the above steps 300 and 301, the relay terminal determines the PDU session parameters by at least one of the following methods:

[0062] Mode 1: The relay terminal obtains the relay service code locally and determines the PDU session parameters associated with the relay service code based on the association relationship;

[0063] Mode 2: The relay terminal obtains the relay service code from the second information, and determines the PDU session parameter associated with the relay service code according to the association relationship.

[0064] It can be seen that in the embodiment of the present application, the relay service code can be obtained locally, or it can be obtained from the second information sent by the remote terminal, and then the corresponding PDU session parameters are determined according to the relay service code and the association relationship. In other words, in the embodiment of the present application, the corresponding PDU session parameters can also be determined as needed to facilitate the establishment of the subsequent relay PDU session.

[0065] In an optional implementation manner of an embodiment of the present application, the PDU session parameters in the embodiment of the present application include at least one of the following: service and session continuity mode (Service and Session Continuity, SSC), PDU session type, DNN, network slice selection auxiliary information NSSAI, and preferred access type.

[0066] Figure 3 The embodiments of the present application are explained from the relay terminal side, and the present application will be explained from the remote terminal side below.

[0067] like Figure 4 As shown, the embodiment of the present application also provides a method for determining the establishment of a PDU session, the steps of the method comprising:

[0068] Step 402: The remote terminal sends first information to the relay terminal, wherein the first information is used to determine a user terminal routing selection policy URSP.

[0069] Through step 402 of the embodiment of the present application, the remote terminal can send the first information for determining the URSP to the relay terminal, and then the relay terminal can use the first information as a basis for determining the URSP and the subsequent establishment of the relay PDU session, thereby solving the problem in the prior art that the relay terminal cannot determine the routing descriptor or URSP, resulting in the subsequent inability to establish a relay PDU session.

[0070] In an optional implementation manner of the embodiment of the present application, the method of the embodiment of the present application may further include:

[0071] Step 404: The remote terminal sends second information to the relay terminal, wherein the remote terminal carries a relay service code, wherein the relay service code is associated with the PDU session parameter.

[0072] In an optional implementation manner of the embodiment of the present application, the first information in the embodiment of the present application includes at least one of the following:

[0073] 1) Service descriptor; 2) Application descriptor; 3) IP descriptor; 4) Non-IP descriptor; 5) Domain descriptor; 6) Data network name DNN; 7) Connection capability; 8) Target address information.

[0074] In an optional implementation manner of the embodiment of the present application, the first information and the second information in the embodiment of the present application are transmitted by at least one of the following messages:

[0075] 1) Direct link establishment request message; 2) Direct link authentication reply message; 3) Direct link security command completion message; 4) Direct link change request message; 5) Direct link change reply message.

[0076] In an optional implementation manner of the embodiment of the present application, the manner in which the remote terminal sends the first information to the relay terminal involved in step 402 of the embodiment of the present application may further include: after a secure connection between the remote terminal and the relay terminal is established, the remote terminal sends the first information to the relay terminal.

[0077] In an optional implementation manner of the embodiment of the present application, the manner in which the remote terminal sends the second information to the relay terminal involved in step 404 of the embodiment of the present application may further include: after a secure connection between the remote terminal and the relay terminal is established, the remote terminal sends the second information to the relay terminal;

[0078] The second information includes at least one of the following: service and session continuity mode, PDU session type, DNN, and NSSAI.

[0079] The present application is illustrated below with reference to the specific implementation manner of the embodiments of the present application.

[0080] This specific implementation provides a method for determining a relay PDU session, such as Figure 5 As shown, the steps of the method include:

[0081] Step 501, the Remote UE discovers and selects a relay UE based on the matching relay service code during the discovery phase;

[0082] Step 502, the Remote UE sends the first information and / or the second information to the relay UE;

[0083] The first information includes at least one of the following:

[0084] 1) Service descriptor (sent from remote UE to relay UE) or traffic descriptor, where the service descriptor is the service descriptor that the remote UE needs to match with the relay forwarding service;

[0085] 2) Application descriptor, where the application descriptor is an application descriptor that the remote UE needs to match with the relay forwarding service.

[0086] 3) IP descriptor, where the IP descriptor is the IP descriptor that the remote UE needs to match with the relay forwarding service;

[0087] 4) Non-IP descriptor, where the non-IP descriptor is a non-IP descriptor that the remote UE needs to match with the relay forwarding service;

[0088] 5) Domain descriptor, where the domain descriptor is the domain descriptor that the remote UE needs to match with the relay forwarding service;

[0089] 6) DNN, where DNN is the DNN that the remote UE needs to match with the relay forwarding service;

[0090] 7) Connection capability: The connection capability is the connection capability that the remote UE needs to match the relay forwarding service.

[0091] In addition, the second information in this specific implementation includes at least one of the following:

[0092] 1) Relay service code. The relay service code corresponds to the connectivity service and associated PDU session parameters that the remote UE needs to relay. The associated PDU session parameters include at least one of the following: PDU session type, DNN, service and session continuity mode, NSSAI, and preferred access type (Access Type Preference).

[0093] 2) PDU Session type: PDU session type is the session type of the first PDU session established by the remote UE that needs to be relayed to the UE;

[0094] 3) DNN, where DNN is the DNN of the first PDU session established by the remote UE that needs to be relayed;

[0095] 4) Service and Session Continuity Mode (SSC Mode), where the SSC mode is the SSC mode of the first PDU session established by the remote UE that needs to be relayed;

[0096] 5) Access Type Preference, where Access Type Preference is the first Access Type Preference that the remote UE needs to establish with the relay UE.

[0097] It should be noted that the first information and the second information in the embodiment of the present application are sent after security is established with the relay UE.

[0098] In addition, when the second information includes a relay service code, the relay service code may be sent before the security establishment with the relay UE.

[0099] Optionally, the first information and the second information are included in at least one of the following messages:

[0100] A) directly establish a request message;

[0101] B) direct link authentication reply message;

[0102] C) Direct Link Security Command Complete message;

[0103] D) Direct Link Change Request / Reply Message.

[0104] Step 503: The Relay UE receives the first information and / or the second information, and performs a first operation based on the first information and / or the second information.

[0105] The first operation includes at least one of the following:

[0106] 1) Matching a URSP that matches the first information based on the first information.

[0107] 2) Select the matching routing descriptor in the URSP based on the PDU session parameters associated with the relay service code.

[0108] If the relay UE obtains the second information, the second information selects the routing descriptor in the matching URSP.

[0109] 3) Based on the matching routing descriptor, determine whether there is a matching PDU session currently.

[0110] It should be noted that if there is a matching PDU session, but it is not suitable for relaying the service data of the remote UE, the first PDU session establishment is executed, and the first PDU session is used to relay the service data of the remote UE. If there is a matching PDU session, which is also used to relay the service data of the remote UE, the matching PDU session is reused. If there is no matching PDU session, the first PDU session establishment is executed, and the first PDU session is used to relay the service data of the remote UE.

[0111] It should be noted that the method for determining the establishment of a relay PDU session provided in the embodiment of the present application may be executed by a determining device for establishing a relay PDU session, or a control module for executing the method for determining the establishment of a relay PDU session in the determining device for establishing a relay PDU session. In the embodiment of the present application, the method for determining the establishment of a relay PDU session is executed by a determining device for establishing a relay PDU session as an example to illustrate the device for determining the establishment of a relay PDU session provided in the embodiment of the present application.

[0112] like Figure 6 As shown, an embodiment of the present application provides a device for determining the establishment of a relay PDU session, which is applied to a relay terminal, and the device includes:

[0113] A first receiving module 62, configured to receive first information sent by a remote terminal, wherein the first information is used to determine a user terminal routing selection strategy URSP;

[0114] A first determination module 64, configured to determine a URSP according to the first information;

[0115] A second determination module 66, configured to determine a routing descriptor matching the URSP based on the PDU session parameters;

[0116] The third determination module 68 is used to determine whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal.

[0117] Through the device of the embodiment of the present application, the corresponding URSP can be determined according to the received first information, and then the routing descriptor matching the URSP can be determined according to the session parameters, and then whether there is a matching relay PDU session can be determined according to the routing descriptor. It can be seen that through the device of the embodiment of the present application, the URSP and its corresponding routing descriptor can be determined, that is, the basis for establishing the subsequent relay PDU session is determined, thereby solving the problem in the prior art that the relay terminal cannot determine the routing descriptor or URSP, resulting in the subsequent inability to establish a relay PDU session.

[0118] Optionally, the device of the embodiment of the present application may further include one of the following:

[0119] A first establishing module, configured to establish a relay PDU session when there is a first PDU session matching the routing descriptor and the first PDU session is not used for relaying service data of a remote terminal;

[0120] A reuse module, configured to reuse the second PDU session as a relay PDU session when there is a second PDU session matching the routing descriptor and the second PDU session is used to relay and forward service data of a remote terminal;

[0121] The second establishing module is used to establish a relay PDU session when there is no PDU session matching the routing descriptor.

[0122] Optionally, the first information in the embodiment of the present application includes at least one of the following: service descriptor; application descriptor; Internet protocol IP descriptor; non-IP descriptor; domain descriptor; data network name DNN; connection capability; target address information.

[0123] Optionally, the first determination module 64 in the embodiment of the present application may further include: a first selection unit, used to select a first service descriptor matching the service descriptor in the first information from the service descriptors in the configured URSP rules; and a first selection unit, used to select a URSP matching the first service descriptor.

[0124] Optionally, the device in the embodiment of the present application further includes one of the following:

[0125] A first acquisition module, configured to acquire a relay service code from a local device before determining a routing descriptor matching the URSP based on the PDU session parameters;

[0126] A second receiving module, configured to receive second information sent by a remote terminal, wherein the remote terminal carries a relay service code;

[0127] Among them, the relay service code is associated with the PDU session parameter.

[0128] Optionally, the device in the embodiment of the present application further includes:

[0129] The second acquisition module is used to determine the PDU session parameter by at least one of the following methods:

[0130] Method 1) Obtain the relay service code locally and determine the PDU session parameters associated with the relay service code based on the association relationship;

[0131] Method 2) Obtain the relay service code from the second information, and determine the PDU session parameters associated with the relay service code based on the association relationship.

[0132] Optionally, the PDU session parameters in the embodiment of the present application include at least one of the following: service and session continuity mode, PDU session type, DNN, network slice selection auxiliary information NSSAI, and preferred access type.

[0133] like Figure 7 As shown, the embodiment of the present application also provides a device for determining the establishment of a relay PDU session, which is applied to a remote terminal, and the device includes:

[0134] The first sending module 72 is used to send first information to the relay terminal, wherein the first information is used to determine the user terminal routing selection policy URSP.

[0135] Through the device in the embodiment of the present application, the first information for determining the URSP can be sent to the relay terminal, and then the relay terminal can use the first information as a basis for determining the URSP and the subsequent establishment of the relay PDU session, thereby solving the problem in the prior art that the relay terminal cannot determine the routing descriptor or URSP, resulting in the subsequent inability to establish a relay PDU session.

[0136] Optionally, the device in the embodiment of the present application may further include: a second sending module, used to send second information to the relay terminal, wherein the remote terminal carries a relay service code, wherein the relay service code is associated with the PDU session parameter.

[0137] Optionally, the first information in the embodiment of the present application includes at least one of the following: service descriptor; application descriptor; Internet protocol IP descriptor; non-IP descriptor; domain descriptor; data network name DNN; connection capability; target address information.

[0138] Optionally, the first information and the second information in the embodiment of the present application are transmitted through at least one of the following messages: a direct establishment request message; a direct link authentication reply message; a direct link security command completion message; a direct link change request message; and a direct link change reply message.

[0139] Optionally, the first sending module in the embodiment of the present application is further used to send the first information to the relay terminal after a secure connection between the remote terminal and the relay terminal is established.

[0140] Optionally, the second sending module in the embodiment of the present application is also used to send second information to the relay terminal after a secure connection is established between the remote terminal and the relay terminal; wherein the second information includes at least one of the following: service and session continuity mode, PDU session type, DNN, NSSAI.

[0141] The determining device for establishing a relay PDU session in the embodiment of the present application may be a device, a device or an electronic device having an operating system, or a component, an integrated circuit, or a chip in a terminal. The device or electronic device may be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal may include but is not limited to the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0142] Embodiments of the present application Figure 6 The provided relay PDU session establishment determination device can achieve Figure 3 The various processes implemented by the method embodiment of the present application and the same technical effect are achieved. Figure 7 The provided relay PDU session establishment determination device can achieve Figure 4 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0143] Optional, such as Figure 8As shown, the embodiment of the present application also provides a communication device 800, including a processor 801, a memory 802, and a program or instruction stored in the memory 802 and executable on the processor 801. For example, when the communication device 800 is a terminal, the program or instruction is executed by the processor 801 to implement the various processes of the embodiment of the method for determining the establishment of the relay PDU session, and the same technical effect can be achieved. When the communication device 800 is a network-side device, the program or instruction is executed by the processor 801 to implement the various processes of the embodiment of the method for determining the establishment of the relay PDU session, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0144] An embodiment of the present application also provides a terminal, including a processor and a communication interface, the communication interface is used to receive first information sent by a remote terminal, wherein the first information is used to determine a user terminal routing selection strategy URSP; the processor is used to determine the URSP according to the first information, and determine a routing descriptor matching the URSP based on PDU session parameters, and determine whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect. Specifically, Fig. 9 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0145] The terminal 100 includes but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and at least some of the components of a processor 110.

[0146] Those skilled in the art will appreciate that the terminal 100 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 110 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 8 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0147] It should be understood that in the embodiment of the present application, the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0148] In the embodiment of the present application, the radio frequency unit 101 receives downlink data from the network side device and sends it to the processor 110 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 101 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0149] The memory 109 can be used to store software programs or instructions and various data. The memory 109 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 109 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0150] The processor 110 may include one or more processing units; optionally, the processor 110 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 110.

[0151] If the terminal is a relay terminal, the radio frequency unit 101 is used to receive first information sent by a remote terminal, wherein the first information is used to determine the user terminal routing selection strategy URSP

[0152] The processor 110 is used to determine the URSP according to the first information, determine the routing descriptor matching the URSP based on the PDU session parameters, and determine whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal.

[0153] Optionally, the processor 110 is further configured to perform at least one of the following operations:

[0154] If there is a first PDU session matching the routing descriptor and the first PDU session is not used for relaying service data of a remote terminal, establishing a relay PDU session;

[0155] If there is a second PDU session matching the routing descriptor, and the second PDU session is used to relay and forward the service data of the remote terminal, reuse the second PDU session as a relay PDU session;

[0156] In the event that no PDU session matching the routing descriptor exists, a relay PDU session is established.

[0157] Optionally, the processor 110 is further configured to select a first service descriptor matching the service descriptor in the first information from the service descriptors in the configured URSP rule, and select a URSP matching the first service descriptor.

[0158] Optionally, the processor 110 is further configured to perform one of the following operations before the relay terminal determines a routing descriptor matching the URSP based on the PDU session parameter:

[0159] Get the relay service code from the local;

[0160] Receive second information sent by a remote terminal, wherein the remote terminal carries a relay service code; wherein the relay service code is associated with a PDU session parameter.

[0161] Optionally, the processor 110 is further configured to determine the PDU session parameter in at least one of the following ways:

[0162] Obtain the relay service code from the local, and determine the PDU session parameters associated with the relay service code according to the association relationship;

[0163] A relay service code is obtained from the second information, and a PDU session parameter associated with the relay service code is determined according to the association relationship.

[0164] In addition, if the above-mentioned terminal is a remote terminal, the radio frequency unit 101 is used to send first information to the relay terminal, wherein the first information is used to determine the user terminal routing selection strategy URSP.

[0165] Optionally, the radio frequency unit 101 is further used to send second information to the relay terminal, wherein the remote terminal carries a relay service code, wherein the relay service code is associated with the PDU session parameter.

[0166] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned determination method embodiment for establishing a relay PDU session is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0167] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0168] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method for determining the establishment of a relay PDU session, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0169] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0170] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0171] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0172] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for determining the establishment of a relay data protocol unit PDU session, characterized in that: include: The relay terminal receives first information sent by the remote terminal, wherein the first information is used to determine the user terminal routing selection strategy URSP; The relay terminal determines the URSP according to the first information; The relay terminal determines, based on the PDU session parameters, a routing descriptor matching the URSP; The relay terminal determines whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal.

2. The method according to claim 1, characterized in that The method further comprises one of the following: In a case where there is a first PDU session matching the routing descriptor and the first PDU session is not used for relaying and forwarding service data of the remote terminal, the relay terminal establishes the relay PDU session; In a case where there is a second PDU session matching the routing descriptor, and the second PDU session is used to relay and forward the service data of the remote terminal, the relay terminal reuses the second PDU session as the relay PDU session; In the case that there is no PDU session matching the routing descriptor, the relay terminal establishes the relay PDU session.

3. The method according to claim 1, characterized in that The first information includes at least one of the following: Traffic descriptor; Application descriptors Internet Protocol IP descriptors IP descriptors; Non-IP descriptors; Domain descriptors Data network name DNN; Connection Capabilities; Target address information.

4. The method according to claim 3, characterized in that The relay terminal determines the URSP according to the first information, including: The relay terminal selects, from the service descriptors in the configured URSP rule, a first service descriptor that matches the service descriptor in the first information; The relay terminal selects the URSP that matches the first service descriptor.

5. The method according to claim 1, characterized in that Before the relay terminal determines the routing descriptor matching the URSP based on the PDU session parameter, the method further includes one of the following: The relay terminal obtains a relay service code locally; The relay terminal receives the second information sent by the remote terminal, wherein the remote terminal carries a relay service code; The relay service code is associated with the PDU session parameter.

6. The method according to claim 5, characterized in that The relay terminal determines the PDU session parameter by at least one of the following methods: Acquire the relay service code locally, and determine the PDU session parameter associated with the relay service code according to the association relationship; The relay service code is acquired from the second information, and the PDU session parameter associated with the relay service code is determined according to the association relationship.

7. The method according to claim 1 or 5, characterized in that: The PDU session parameter includes at least one of the following: Service and session continuity mode, PDU session type, DNN, network slice selection auxiliary information NSSAI, and preferred access type Access Type Preference.

8. A method for determining the establishment of a relay PDU session, characterized in that: include: The remote terminal sends first information to the relay terminal, wherein the first information is used to determine a user terminal routing selection strategy URSP.

9. The method according to claim 8, characterized in that The method further comprises: The remote terminal sends second information to the relay terminal, wherein the remote terminal carries a relay service code, and wherein the relay service code is associated with a PDU session parameter.

10. The method according to claim 8, characterized in that The first information includes at least one of the following: Traffic descriptor; Application descriptors Internet Protocol IP descriptors IP descriptors; Non-IP descriptors; Domain descriptors Data network name DNN; Connection Capabilities; Target address information.

11. The method according to claim 9, characterized in that The first information and the second information are transmitted by at least one of the following messages: Create a request message directly; Direct link authentication reply message; Direct Link Security Command Complete message; Direct link change request message; Direct link change reply message.

12. The method according to claim 8, characterized in that The remote terminal sending the first information to the relay terminal includes: After a secure connection is established between the remote terminal and the relay terminal, the remote terminal sends the first information to the relay terminal.

13. The method according to claim 9, characterized in that The remote terminal sending the second information to the relay terminal includes: After a secure connection is established between the remote terminal and the relay terminal, the remote terminal sends second information to the relay terminal; Among them, the second information includes at least one of the following: service and session continuity mode, PDU session type, DNN, NSSAI.

14. A device for determining the establishment of a relay PDU session, using a relay terminal, characterized in that: include: A first receiving module, configured to receive first information sent by a remote terminal, wherein the first information is used to determine a user terminal routing selection strategy URSP; A first determining module, configured to determine the URSP according to the first information; A second determining module, configured to determine a routing descriptor matching the URSP based on a PDU session parameter; The third determination module is used to determine whether there is a relay PDU session matching the routing descriptor; wherein the relay PDU session is a PDU session in which the relay terminal relays and forwards the service data of the remote terminal.

15. The device according to claim 14, characterized in that The device also includes one of the following: A first establishing module, configured to establish the relay PDU session when there is a first PDU session matching the routing descriptor and the first PDU session is not used for relaying and forwarding the service data of the remote terminal; A reuse module, configured to reuse the second PDU session as the relay PDU session when there is a second PDU session matching the routing descriptor and the second PDU session is used to relay and forward the service data of the remote terminal; The second establishing module is used to establish the relay PDU session when there is no PDU session matching the routing descriptor.

16. The device according to claim 14, characterized in that The first information includes at least one of the following: Traffic descriptor; Application descriptors Internet Protocol IP descriptors IP descriptors; Non-IP descriptors; Domain descriptors Data network name DNN; Connection Capabilities; Target address information.

17. The device according to claim 16, characterized in that The first determining module comprises: A first selection unit, configured to select a first service descriptor matching the service descriptor in the first information from the service descriptors in the configured URSP rule; The first selection unit is configured to select the URSP that matches the first service descriptor.

18. The device according to claim 14, characterized in that The device also includes one of the following: A first acquisition module, configured to acquire a relay service code from a local before determining a routing descriptor matching the URSP based on a PDU session parameter; A second receiving module, configured to receive second information sent by the remote terminal, wherein the remote terminal carries a relay service code; The relay service code is associated with the PDU session parameter.

19. The device according to claim 18, characterized in that The device also includes: The second acquisition module is used to determine the PDU session parameter by at least one of the following methods: Acquire the relay service code locally, and determine the PDU session parameter associated with the relay service code according to the association relationship; The relay service code is acquired from the second information, and the PDU session parameter associated with the relay service code is determined according to the association relationship.

20. The device according to claim 14 or 18, characterized in that The PDU session parameter includes at least one of the following: Service and session continuity mode, PDU session type, DNN, network slice selection auxiliary information NSSAI, and preferred access type Access Type Preference.

21. A device for determining the establishment of a relay PDU session, applied to a remote terminal, characterized in that: include: The first sending module is used to send first information to the relay terminal, wherein the first information is used to determine the user terminal routing selection strategy URSP.

22. The device according to claim 21, characterized in that The device also includes: The second sending module is used to send second information to the relay terminal, wherein the remote terminal carries a relay service code, and wherein the relay service code is associated with a PDU session parameter.

23. The device according to claim 21, characterized in that The first information includes at least one of the following: Traffic descriptor; Application descriptors Internet Protocol IP descriptors IP descriptors; Non-IP descriptors; Domain descriptors Data network name DNN; Connection Capabilities; Target address information.

24. The device according to claim 22, characterized in that The first information and the second information are transmitted by at least one of the following messages: Create a request message directly; Direct link authentication reply message; Direct Link Security Command Complete message; Direct link change request message; Direct link change reply message.

25. The device according to claim 21, characterized in that The first sending module is further configured to send the first information to the relay terminal after a secure connection between the remote terminal and the relay terminal is established.

26. The device according to claim 22, characterized in that The second sending module is further configured to send second information to the relay terminal after a secure connection between the remote terminal and the relay terminal is established; Among them, the second information includes at least one of the following: service and session continuity mode, PDU session type, DNN, NSSAI.

27. A terminal, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method steps as claimed in any one of claims 1 to 7, or implements the method steps as claimed in any one of claims 8 to 13.

28. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the method steps according to any one of claims 1 to 7 are implemented, or the method steps according to any one of claims 8 to 13 are implemented.

Images