CN115190562A

CN115190562A - Method and device for determining relay PDU session establishment and terminal

Info

Publication number: CN115190562A
Application number: CN202110358431.5A
Authority: CN
Inventors: 王文; 谢振华; 柯小婉
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-04-01
Filing date: 2021-04-01
Publication date: 2022-10-14
Also published as: WO2022206662A1

Abstract

The application discloses a method, a device and a terminal for determining relay PDU session establishment, belonging to the technical field of communication, wherein the method comprises the following steps: the method comprises the steps that a relay terminal receives first information sent by a far-end terminal, wherein the first information is used for determining a user terminal routing strategy URSP; the relay terminal determines the URSP according to the first information; the relay terminal determines a routing descriptor matched with the URSP based on PDU session parameters; the relay terminal determines whether a relay PDU session matching the route descriptor exists; and the relay PDU session is a PDU session for relaying and forwarding the service data of the remote terminal by the relay terminal. By the method and the device, the problem that the relay terminal cannot determine the route descriptor or the URSP in the prior art, and the relay PDU session cannot be established subsequently is solved.

Description

Method and device for determining relay PDU session establishment and terminal

Technical Field

The application belongs to the technical field of communication, and particularly relates to a method and a device for determining relay PDU session establishment, and a terminal.

Background

In the prior art, a relay terminal (relay UE) may send a plurality of different relay service codes (relay service codes) in a discovery phase, where a session parameter of a Data Protocol Unit (PDU) corresponding to one relay service code corresponds to a plurality of service descriptors. Therefore, the relay terminal cannot determine the corresponding PDU session parameter (such as a Routing descriptor) or a User Equipment Routing Policy (URSP), which results in that the relay PDU session cannot be established subsequently.

Disclosure of Invention

The embodiment of the application provides a method, a device and a terminal for determining relay PDU session establishment, and can solve the problem that in the prior art, a relay terminal cannot determine a route descriptor or URSP, so that a relay PDU session cannot be established subsequently.

In a first aspect, a method for determining a relay data protocol unit PDU session establishment is provided, where the method includes: the method comprises the steps that a relay terminal receives first information sent by a far-end terminal, wherein the first information is used for determining a user terminal routing strategy URSP; the relay terminal determines the URSP according to the first information; the relay terminal determines a routing descriptor matched with the URSP based on PDU session parameters; the relay terminal determines whether a relay PDU session matching the route descriptor exists; and the relay PDU session is a PDU session for relaying and forwarding the service data of the remote terminal by the relay terminal.

In a second aspect, a method for determining a relay PDU session establishment is provided, including: the method comprises the steps that a remote terminal sends first information to a relay terminal, wherein the first information is used for determining a user terminal routing strategy URSP:

in a third aspect, a device for determining relay PDU session establishment is provided, where a relay terminal is applied, and the device includes: a first receiving module, configured to receive first information sent by a remote terminal, where the first information is used to determine a user equipment routing policy URSP; a first determining module, configured to determine the URSP according to the first information; a second determining module for determining a routing descriptor matching the URSP based on PDU session parameters; a third determining module for determining whether there is a relay PDU session matching the route descriptor; and the relay PDU session is a PDU session for relaying and forwarding the service data of the remote terminal by the relay terminal.

In a fourth aspect, a device for determining relay PDU session establishment is provided, which is applied to a remote terminal, and includes: the relay device comprises a first sending module, a second sending module and a third sending module, wherein the first sending module is used for sending first information to the relay terminal, and the first information is used for determining a user terminal routing strategy URSP.

In a fifth aspect, there is provided a terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the method according to the first aspect.

A sixth aspect provides a terminal, including a processor and a communication interface, where the communication interface is configured to receive first information sent by a remote terminal, where the first information is used to determine a user terminal routing policy, URSP; the processor is used for determining the URSP according to the first information, determining a routing descriptor matched with the URSP based on PDU session parameters, and determining whether a relay PDU session matched with the routing descriptor exists; and the relay PDU session is a PDU session for relaying and forwarding the service data of the remote terminal by the relay terminal.

In a seventh aspect, there is provided a readable storage medium on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the steps of the method according to the first aspect or implement the steps of the method according to the second aspect.

In an eighth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to execute a program or instructions to implement the method according to the third aspect, the 8230, or the method according to the second aspect.

In a ninth aspect, there is provided a computer program/program product stored on a non-volatile storage medium, the program/program product being executable by at least one processor to perform the method steps as described in the first aspect or to perform the method steps as described in the second aspect.

In this embodiment of the present application, the relay terminal may determine a corresponding URSP according to the received first information, further determine a routing descriptor matching the URSP according to the session parameter, and further determine whether a matching relay PDU session exists according to the routing descriptor. Therefore, by the embodiment of the application, the relay terminal can determine the URSP and the corresponding routing descriptor, namely, the basis for establishing the subsequent relay PDU session is determined, so that the problem that the relay terminal cannot determine the routing descriptor or the URSP in the prior art, which causes the subsequent relay PDU session to be unable to be established is solved.

Drawings

FIG. 1 illustrates a block diagram of a wireless communication system to which embodiments of the present application are applicable;

fig. 2 is a flowchart of a setup process of L3 according to an embodiment of the present application;

fig. 3 is a flowchart of a method for determining a relay PDU session establishment according to an embodiment of the present application;

fig. 4 is a second flowchart of a method for determining a relay PDU session establishment according to the embodiment of the present application;

fig. 5 is a flow chart of relay PDU session establishment according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a relay PDU session establishment determination apparatus according to an embodiment of the present application;

fig. 7 is a second schematic structural diagram of a method for determining relay PDU session establishment according to the embodiment of the present application;

fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below clearly with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in other sequences than those illustrated or otherwise described herein, and that the terms "first" and "second" used herein generally refer to a class and do not limit the number of objects, for example, a first object can be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may 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 techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, but the techniques may also be applied to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: smart watches, bracelets, earphones, glasses, and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and 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 a specific type of the Base Station is not limited.

First, explanation is made on related terms in the embodiments of the present application;

1. relay service code (Relay service code)

The relay service code is used to identify the connection service provided by the relay UE and the authorized user to which the relay UE will provide service, and may select related security policies or information, such as: authentication and authorization between the remote UE and the relay UE.

For L3 relay, each relay service code will associate a set of PDU session parameters as UE policy configuration to the relay terminal and the remote terminal, wherein the PDU session parameters include at least one of the following: PDU Session Type, data Network Name (DNN), service and Session Continuity (SSC) mode, network Slice Selection Assistance Information (NSSAI), access Type Preference (Access Type Preference).

When the relay terminal and the remote terminal execute the corresponding discovery process, the relay service code is carried in the discovery message, and the remote terminal determines whether to select the relay terminal (mode A) based on the relay service code sent by the relay terminal.

2. L3 establishment procedure

As shown in fig. 2, in the step 110, when or after the remote terminal establishes the one-to-one L2 link with the relay terminal, a relay PDU session is established for the remote terminal to relay/forward the service data of the remote terminal.

3. PDU session establishment principles

The establishment of the PDU session is determined based on the URSP, and for the L3 relay, the relay PDU session belongs to the relay terminal, so the relay terminal establishes the relay PDU session based on its own URSP, and for this reason, the remote terminal and the relay terminal must have a unified understanding on the establishment of the relay PDU session, otherwise the PDU session established by the relay terminal is not in accordance with the service requirement of the relay terminal. The current unified understanding can determine how to establish the PDU session from the configured relay service code and PDU session parameter association relationship, and since the relay terminal and the relay terminal may be the same for the above configuration, the parameters for relay PDU session establishment are in accordance with the requirement of remote UE.

The method for determining the relay PDU session establishment provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings through some embodiments and application scenarios thereof.

As shown in fig. 3, an embodiment of the present application provides a method for determining a relay PDU session establishment, where the method includes:

step 302, a relay terminal receives first information sent by a remote terminal, wherein the first information is used for determining a user terminal routing strategy URSP;

step 304, the relay terminal determines URSP according to the first information;

step 306, the relay terminal determines a routing descriptor matched with the URSP based on the PDU session parameter;

step 308, the relay terminal determines whether a relay PDU session matched with the route descriptor exists; the relay PDU session is a PDU session for relaying and forwarding the service data of the remote terminal by the relay terminal.

Through the above steps 302 to 308 of the embodiment of the present application, the relay terminal may determine the corresponding URSP according to the received first information, and then determine the route descriptor matched with the URSP according to the session parameter, and further determine whether there is a matched relay PDU session according to the route descriptor. Therefore, by the embodiment of the application, the relay terminal can determine the URSP and the corresponding routing descriptor, namely, the basis for establishing the subsequent relay PDU session is determined, so that the problem that the relay terminal cannot determine the routing descriptor or the URSP in the prior art, which causes the subsequent relay PDU session to be unable to be established is solved.

In an alternative implementation of the embodiment of the present application, the method of the embodiment of the present application further includes one of:

step 310, the relay terminal establishes a relay PDU session under the condition that a first PDU session matched with the route descriptor exists and the first PDU session is not used for relaying and forwarding service data of the remote terminal;

step 312, in the case that there is a second PDU session matching with the route descriptor and the second PDU session is used for relay forwarding of the service data of the remote terminal, the relay terminal reuses the second PDU session as a relay PDU session;

in step 314, the relay terminal establishes a relay PDU session in case there is no PDU session matching with the route descriptor.

As can be seen from steps 310 to 314, in the case that there is no PDU session matching the route descriptor, the relay terminal may establish a relay PDU session, and if there is a PDU session matching the route descriptor and the PDU session is not used for relaying and forwarding the service data of the remote terminal, it is also necessary to establish a relay PDU session, and if the PDU session is used for relaying and forwarding the service data of the remote terminal, it is not necessary to establish a new relay PDU session, the PDU session is multiplexed into the relay PDU session. In any case, the relay terminal can establish the relay PDU session, or multiplex the PDU session capable of being used for relay forwarding of the remote service data into the relay PDU session, so as to determine the relay PDU session meeting the requirements of the remote terminal.

It should be noted that the relay terminal in this embodiment of the application is a relay terminal selected by the remote terminal based on a relay service code in the discovery phase, where the relay service code is a relay service code that meets the service requirement and is selected by the remote terminal in the discovery phase.

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:

1) A Traffic descriptor (Traffic descriptor); 2) Application descriptors (Application descriptors);

3) Internet Protocol (IP) descriptors; 4) Non-IP descriptors (Non-IP descriptors); 5) Domain descriptors (Domain descriptors); 6) A data network name DNN; 7) Connection Capabilities (Connection Capabilities); 8) Destination address information.

It should be noted that the service descriptor may also be referred to as a traffic descriptor in other application scenarios. The destination address information may refer to a destination IP, a destination MAC, or the like.

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

step 304-11, the relay terminal selects a first service descriptor matched with the service descriptor in the first information from the service descriptors in the configured URSP rule;

step 304-12, the relay terminal selects the URSP that matches the first traffic descriptor.

Through the above steps 304-11 and 304-12, the service descriptor in the first information needs to be matched 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.

In an optional implementation manner of the embodiment of the present application, before the relay terminal determines, based on the PDU session parameter, a routing descriptor matching the URSP, the method of the embodiment of the present application further includes one of the following steps:

step 300, the relay terminal obtains a relay service code from local;

step 301, a relay terminal receives second information sent by a remote terminal, wherein the remote terminal carries a relay service code;

wherein, the relay service code has an association relation with the PDU session parameter.

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

in the mode 1, a relay terminal acquires a relay service code from local and determines a PDU session parameter associated with the relay service code according to an association relation;

and in the mode 2, the relay terminal acquires the relay service code from the second information and determines the PDU session parameter associated with the relay service code according to the association relation.

It can be seen that, in the embodiment of the present application, the relay service code may be obtained locally, or the relay service code may be obtained from the second information sent by the remote terminal, and then the corresponding PDU session parameter is determined according to the relay service code and the association relationship. That is to say, in the embodiment of the present application, the corresponding PDU session parameter may also be determined as needed, so as to continue the establishment of the PDU session.

In an optional implementation manner of the embodiment of the present application, the PDU session parameter in the embodiment of the present application includes at least one of the following: service and Session Continuity mode (SSC), PDU Session type, DNN, network slice selection assistance information NSSAI, preferred access type.

Fig. 3 is a diagram for explaining the embodiment of the present application from the relay terminal side, and the present application will be explained from the remote terminal side.

As shown in fig. 4, an embodiment of the present application further provides a method for determining PDU session establishment, where the method includes:

step 402, the remote terminal sends first information to the relay terminal, wherein the first information is used for determining a user terminal routing strategy URSP.

Through step 402 of the embodiment of the present application, the remote terminal may send the first information for determining the URSP to the relay terminal, and then the relay terminal may use the first information as a basis for determining the URSP and establishing a subsequent relay PDU session, thereby solving the problem that the relay terminal cannot determine the route descriptor or the URSP in the prior art, which causes the subsequent relay PDU session to be unable to be established.

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

and step 404, the remote terminal sends second information to the relay terminal, wherein the remote terminal carries a relay service code, and the relay service code has an association relation with the PDU session parameter.

1) A service descriptor; 2) An application descriptor; 3) An IP descriptor; 4) A non-IP descriptor; 5) A domain descriptor; 6) A data network name DNN; 7) A connection capability; 8) Destination address information.

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 through a message of at least one of the following:

1) Directly establishing a request message; 2) A direct link authentication reply message; 3) A direct link security command completion message; 4) A direct link change request message; 5) A direct link change reply message.

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 the safe connection between the remote terminal and the relay terminal is established, the remote terminal sends first information to the relay terminal.

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 the safe connection between the remote terminal and the relay terminal is established, the remote terminal sends second information to the relay terminal;

wherein the second information comprises at least one of: service and session continuity mode, PDU session type, DNN, NSSAI.

The present application will now be described by way of example with reference to the following specific embodiments of examples thereof.

The specific embodiment provides a method for determining a relay PDU session, and as shown in fig. 5, the method includes the steps of:

step 501, the remote UE discovers and selects a relay UE based on the matched relay service code in the discovery stage;

step 502, the remote UE sends the first information and/or the second information to the relay UE;

wherein the first information comprises at least one of:

1) A service descriptor (a remote UE sends to a relay UE) or a traffic descriptor, where the service descriptor is a service descriptor that the remote UE needs to relay a service matching;

2) And an application descriptor, wherein the application descriptor is an application descriptor matched with the relay forwarding service required by the remote UE.

3) The IP descriptor is matched with the relay forwarding service needed by the remote UE;

4) A non-IP descriptor, wherein the non-IP descriptor is a non-IP descriptor matched with a relay forwarding service required by remote UE;

5) The domain descriptor is matched with the relay forwarding service needed by the remote UE;

6) DNN, wherein the DNN character is a DNN matched with the relay forwarding service required by the remote UE;

7) And the connection capability is the connection capability that the remote UE needs to relay and forward the service matching.

Further, the second information in this particular embodiment includes at least one of:

1) A Relay service code, where the Relay service code corresponds to a connectivity service and an associated PDU session parameter that a remote UE needs to forward, and the associated PDU session parameter includes at least one of the following: PDU session Type, DNN, traffic and session continuity mode, NSSAI, preferred Access Type (Access Type Preference).

2) A PDU Session type, which is a Session type of a first PDU Session that a remote UE needs to establish;

3) DNN, wherein the DNN is the DNN of the first PDU session established by the remote UE;

4) A service and session continuity Mode (SSC Mode), wherein SSC Mode is the SSC Mode that a remote UE needs the first PDU session established by the relay UE;

5) The Access Type Preference is a first Access Type Preference established by the relay UE required by the remote UE.

It should be noted that, in the embodiment of the present application, the first information and the second information are sent after being securely established with the relay UE.

Further, in the case where the second information includes a relay service code, the second information may be transmitted before security establishment with the relay UE

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

a) Directly establishing a request message;

b) A direct link authentication reply message;

c) A direct link security command completion message;

d) Direct link change request/reply messages.

In 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.

Wherein the first operation comprises at least one of:

1) And matching the URSP which accords with the first information based on the first information.

2) And selecting the matched route descriptor in the URSP based on the PDU session parameter associated with the relay service code.

And if the relay UE acquires the second information, the second information selects the matched route descriptor in the URSP.

3) And judging whether a matched PDU session exists currently or not based on the matched routing descriptor.

It should be noted that, if there is a matching PDU session but is not suitable for relay forwarding of the service data of the remote UE, a first PDU session establishment is performed, where the first PDU session is used for relay forwarding of the service data of the remote UE. And if the matched PDU session exists, the matched PDU session is also used for relay forwarding of the service data of the remote UE, and the matched PDU session is reused. And if no matched PDU session exists, performing first PDU session establishment, wherein the first PDU session is used for relay forwarding of remote UE service data.

It should be noted that, in the method for determining relay PDU session establishment provided in the embodiment of the present application, the execution subject may be a determination apparatus for relay PDU session establishment, or a control module in the determination apparatus for relay PDU session establishment, configured to execute the method for determining relay PDU session establishment. In the embodiment of the present application, a method for determining a relay PDU session establishment performed by a relay PDU session establishment determination device is taken as an example, and the relay PDU session establishment determination device provided in the embodiment of the present application is described.

As shown in fig. 6, an embodiment of the present application provides a device for determining a relay PDU session establishment, where a relay terminal is applied, and the device includes:

a first receiving module 62, configured to receive first information sent by a remote terminal, where the first information is used to determine a user terminal routing policy URSP;

a first determining module 64, configured to determine the URSP according to the first information;

a second determining module 66 for determining a route descriptor matching the URSP based on the PDU session parameter;

a third determining module 68 for determining whether there is a relay PDU session matching the route descriptor; the relay PDU session is a PDU session for relaying and forwarding service data of the remote terminal by the relay terminal.

By the device, the corresponding URSP can be determined according to the received first information, the route descriptor matched with the URSP is further determined according to the session parameters, and whether the matched relay PDU session exists or not is further determined according to the route descriptor. Therefore, by the device of the embodiment of the application, the URSP and the corresponding routing descriptor thereof can be determined, that is, the basis for establishing the subsequent relay PDU session is determined, so that the problem that the relay terminal in the prior art cannot determine the routing descriptor or the URSP, which causes the subsequent relay PDU session to be unable to be established is solved.

Optionally, the apparatus according to the embodiment of the present application may further include one of:

the first establishing module is used for establishing a relay PDU session under the condition that a first PDU session matched with the route descriptor exists and the first PDU session is not used for relaying and forwarding the service data of the remote terminal;

the reuse module is used for reusing the second PDU session as a relay PDU session under the condition that the second PDU session matched with the route descriptor exists and is used for relaying and forwarding the service data of the remote terminal;

and a second establishing module for establishing the relay PDU session in the absence of a PDU session matching the route descriptor.

Optionally, the first information in this embodiment includes at least one of the following: a service descriptor; an application descriptor; an internet protocol, IP, descriptor; a non-IP descriptor; a domain descriptor; a data network name DNN; a connection capability; destination address information.

Optionally, the first determining module 64 in this embodiment of the application further includes: a first selection unit, configured to select, from the traffic descriptors in the configured URSP rule, a first traffic descriptor that matches the traffic descriptor in the first information; and the first selection unit is used for selecting the URSP matched with the first service descriptor.

Optionally, the apparatus in this embodiment of the present application further includes one of:

a first obtaining module, configured to obtain a relay service code from local before determining a routing descriptor matching the URSP based on the PDU session parameter;

the second receiving module is used for receiving second information sent by the far-end terminal, wherein the far-end terminal carries a relay service code;

Optionally, the apparatus in this embodiment of the present application further includes:

a second obtaining module, configured to determine a PDU session parameter in at least one of the following manners:

mode 1) acquiring a relay service code from local, and determining a PDU session parameter associated with the relay service code according to the association relation;

and 2) acquiring the relay service code from the second information, and determining a PDU session parameter associated with the relay service code according to the association relation.

Optionally, the PDU session parameter in this embodiment includes at least one of the following: service and session continuity mode, PDU session type, DNN, network slice selection assistance information NSSAI, preferred access type.

As shown in fig. 7, an embodiment of the present application further provides a device for determining relay PDU session establishment, which is applied to a remote terminal, and the device includes:

a first sending module 72, configured to send first information to the relay terminal, where the first information is used to determine a user terminal routing policy URSP.

By the device in the embodiment of the application, the first information for determining the URSP can be sent to the relay terminal, and then the relay terminal can be used as a basis for determining the URSP and establishing a subsequent relay PDU session according to the first information, so that the problem that the relay terminal cannot determine the route descriptor or the URSP in the prior art, and the subsequent relay PDU session cannot be established is solved.

Optionally, the apparatus in this embodiment of the present application may further include: and the second sending module is used for sending second information to the relay terminal, wherein the remote terminal carries a relay service code, and the relay service code and the PDU session parameter have an association relation.

Optionally, the first information in the embodiment of the present application includes at least one of: a service descriptor; an application descriptor; an internet protocol, IP, descriptor; a non-IP descriptor; a domain descriptor; a data network name DNN; a connection capability; destination address information.

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: directly establishing a request message; a direct link authentication reply message; a direct link security command completion message; a direct link change request message; a direct link change reply message.

Optionally, the first sending module in this embodiment of the application is further configured to send the first information to the relay terminal after the secure connection between the remote terminal and the relay terminal is established.

Optionally, the second sending module in this embodiment is further configured to send the second information to the relay terminal after the secure connection between the remote terminal and the relay terminal is established; wherein the second information comprises at least one of: service and session continuity mode, PDU session type, DNN, NSSAI.

The determining device for relay PDU session establishment in the embodiment of the present application may be a device, a device or an electronic device having an operating system, or may be a component, an integrated circuit, or a chip in a terminal. The device or the electronic equipment can be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

The apparatus for determining relay PDU session establishment provided in embodiment of the present application, in fig. 6, can implement each process implemented in the method embodiment of fig. 3, and achieve the same technical effect, and the apparatus for determining relay PDU session establishment provided in embodiment of the present application, in fig. 7, can implement each process implemented in the method embodiment of fig. 4, and achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Optionally, as shown in fig. 8, an embodiment of the present application further provides a communication device 800, which includes a processor 801, a memory 802, and a program or an instruction stored on the memory 802 and executable on the processor 801, for example, when the communication device 800 is a terminal, the program or the instruction is executed by the processor 801 to implement each process of the above-mentioned relay PDU session establishment determination method embodiment, and can achieve the same technical effect. When the communication device 800 is a network device, the program or the instruction is executed by the processor 801 to implement the processes of the above-described method for determining relay PDU session establishment, and can achieve the same technical effects, and in order to avoid repetition, the detailed description is omitted here.

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the communication interface is used for receiving first information sent by a far-end terminal, and the first information is used for determining a routing strategy URSP of a user terminal; the processor is configured to determine the URSP from the first information, determine a routing descriptor matching the URSP based on PDU session parameters, and determine whether a relay PDU session matching the routing descriptor exists; and the relay PDU session is a PDU session for relaying and forwarding the service data of the remote terminal by the relay terminal. The terminal embodiment corresponds to the terminal-side method embodiment, and all implementation processes and implementation manners of the method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, fig. 9 is a schematic diagram of a hardware structure of a terminal for implementing the embodiment of the present application.

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

Those skilled in the art will appreciate that the terminal 100 may further comprise a power supply (e.g., a battery) for supplying power to various components, and the power supply may be logically connected to the processor 110 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The terminal structure shown in fig. 8 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.

It should be understood that, in the embodiment of the present application, the input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, and the Graphics Processing Unit 1041 processes image data of a still picture or a video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing 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, or the like. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also referred to as a touch screen. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In the embodiment of the present application, the radio frequency unit 101 receives downlink data from a network side device and then processes the downlink data to the processor 110; in addition, the uplink data is sent to the network side equipment. Typically, 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, and the like.

The memory 109 may be used to store software programs or instructions and various data. The memory 109 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 109 may include a high-speed random access Memory, and may further include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (Erasable PROM, EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 110 may include one or more processing units; alternatively, the processor 110 may integrate an application processor, which primarily handles operating system, user interface, and applications or instructions, etc., and a modem processor, which primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

Wherein, if the terminal is a relay terminal, the radio frequency unit 101 is configured to receive first information sent by a remote terminal, where the first information is used to determine a user terminal routing policy URSP

A processor 110 for determining a URSP from the first information, and determining a routing descriptor matching the URSP based on the PDU session parameter, and determining whether there is a relay PDU session matching the routing descriptor; the relay PDU session is a PDU session for relaying and forwarding service data of the remote terminal by the relay terminal.

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

under the condition that a first PDU session matched with the route descriptor exists and the first PDU session is not used for relaying and forwarding the service data of the remote terminal, establishing a relay PDU session;

under the condition that a second PDU session matched with the route descriptor exists and is used for relay forwarding of service data of the remote terminal, reusing the second PDU session as a relay PDU session;

in the absence of a PDU session matching the route descriptor, a relay PDU session is established.

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.

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

acquiring a relay service code from a local place;

receiving second information sent by a far-end terminal, wherein the far-end terminal carries a relay service code; wherein, the relay service code has an association relation with the PDU session parameter.

Optionally, the processor 110 is further configured to determine the PDU session parameter by at least one of:

acquiring a relay service code from local, and determining PDU session parameters associated with the relay service code according to the association relation;

and acquiring the relay service code from the second information, and determining a PDU session parameter associated with the relay service code according to the association relation.

In addition, if the terminal is a remote terminal, the radio frequency unit 101 is configured to send first information to the relay terminal, where the first information is used to determine a user terminal routing policy URSP.

Optionally, the radio frequency unit 101 is further configured to send second information to the relay terminal, where the remote terminal carries a relay service code, and the relay service code has an association relationship with the PDU session parameter.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing relay PDU session establishment determining method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Wherein, 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 Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a program or an instruction to implement each process of the embodiment of the method for determining relay PDU session establishment, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one of 8230, and" comprising 8230does not exclude the presence of additional like elements in a process, method, article, or apparatus comprising the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may 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 instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the present embodiments are not limited to those precise embodiments, which are intended to be illustrative rather than restrictive, and that various changes and modifications may be effected therein by one skilled in the art without departing from the scope of the appended claims.

Claims

1. A method for determining a relay data protocol unit (PDU) session establishment is characterized by comprising the following steps:

the method comprises the steps that a relay terminal receives first information sent by a far-end terminal, wherein the first information is used for determining a user terminal routing strategy URSP;

the relay terminal determines the URSP according to the first information;

the relay terminal determines a routing descriptor matched with the URSP based on PDU session parameters;

the relay terminal determines whether a relay PDU session matching the route descriptor exists; and the relay PDU session is a PDU session for relaying and forwarding the service data of the remote terminal by the relay terminal.

2. The method of claim 1, further comprising one of:

the relay terminal establishes the relay PDU session under the condition that a first PDU session matched with the route descriptor exists and the first PDU session is not used for relaying and forwarding the service data of the remote terminal;

in the case that a second PDU session matched with the routing descriptor exists and the second PDU session is used for relay forwarding of the service data of the remote terminal, the relay terminal reuses the second PDU session as the relay PDU session;

the relay terminal establishes the relay PDU session in the absence of a PDU session matching the route descriptor.

3. The method of claim 1, wherein the first information comprises at least one of:

a service descriptor Traffic descriptor;

application descriptor Application descriptors;

internet protocol IP descriptors;

Non-IP descriptors;

domain descriptors;

a data network name DNN;

connection Capabilities;

destination address information.

4. The method of claim 3, wherein the relay terminal determining the URSP based on the first information comprises:

the relay terminal selects a first service descriptor matched with the service descriptor in the first information from the service descriptors in the configured URSP rule;

and the relay terminal selects the URSP matched with the first service descriptor.

5. The method of claim 1, wherein prior to the relay terminal determining a routing descriptor matching the URSP based on PDU session parameters, the method further comprises one of:

the relay terminal acquires a relay service code from local;

the relay terminal receives second information sent by the far-end terminal, wherein the far-end terminal carries a relay service code;

wherein the relay service code has an association relationship with the PDU session parameter.

6. The method of claim 5, wherein the relay terminal determines the PDU session parameters by at least one of:

acquiring the relay service code from the local, and determining the PDU session parameter associated with the relay service code according to the association relation;

and acquiring the relay service code from the second information, and determining the PDU session parameter associated with the relay service code according to the association relation.

7. The method according to claim 1 or 5, wherein the PDU session parameters comprise at least one of:

service and session continuity mode, PDU session Type, DNN, network slice selection assistance information NSSAI, preferred Access Type Access Preference.

8. A method for determining a relay PDU session establishment, comprising:

the remote terminal sends first information to the relay terminal, wherein the first information is used for determining a user terminal routing strategy URSP.

9. The method of claim 8, further comprising:

and the remote terminal sends second information to the relay terminal, wherein the remote terminal carries a relay service code, and the relay service code and the PDU session parameter have an association relation.

10. The method of claim 8, wherein the first information comprises at least one of:

a service descriptor Traffic descriptor;

application descriptors;

internet protocol IP descriptors;

Non-IP descriptors;

domain descriptors;

a data network name DNN;

connection Capabilities;

destination address information.

11. The method of claim 9, wherein the first information and the second information are transmitted via messages of at least one of:

directly establishing a request message;

a direct link authentication reply message;

a direct link security command completion message;

a direct link change request message;

a direct link change reply message.

12. The method of claim 8, wherein the sending, by the remote terminal, the first information to the relay terminal comprises:

and after the safe connection between the remote terminal and the relay terminal is established, the remote terminal sends the first information to the relay terminal.

13. The method of claim 9, wherein the sending, by the remote terminal, the second information to the relay terminal comprises:

after the safe connection between the remote terminal and the relay terminal is established, the remote terminal sends second information to the relay terminal;

wherein the second information includes at least one of: service and session continuity mode, PDU session type, DNN, NSSAI.

14. A device for determining relay PDU session establishment, applying a relay terminal, comprising:

a first receiving module, configured to receive first information sent by a remote terminal, where the first information is used to determine a user terminal routing policy URSP;

a first determining module, configured to determine the URSP according to the first information;

a second determining module for determining a routing descriptor matching the URSP based on PDU session parameters;

a third determining module for determining whether there is a relay PDU session matching the route descriptor; and the relay PDU session is a PDU session for relaying and forwarding the service data of the remote terminal by the relay terminal.

15. The apparatus of claim 14, further comprising one of:

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

a reuse module, configured to reuse a second PDU session matched with the route descriptor as the relay PDU session when the second PDU session is used for relaying and forwarding service data of the remote terminal;

a second establishing module for establishing the relay PDU session in the absence of a PDU session matching the route descriptor.

16. The apparatus of claim 14, wherein the first information comprises at least one of:

a service descriptor Traffic descriptor;

application descriptors;

internet protocol IP descriptors;

Non-IP descriptors;

domain descriptors;

a data network name DNN;

connection Capabilities;

destination address information.

17. The apparatus of claim 16, wherein the first determining module comprises:

a first selection unit, configured to select, from the traffic descriptors in the configured URSP rule, a first traffic descriptor that matches the traffic descriptor in the first information;

a first selecting unit, configured to select the URSP with which the first service descriptor matches.

18. The apparatus of claim 14, further comprising one of:

a first obtaining module, configured to obtain 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, where the remote terminal carries a relay service code;

19. The apparatus of claim 18, further comprising:

a second obtaining module, configured to determine the PDU session parameter in at least one of the following manners:

20. The apparatus according to claim 14 or 18, wherein the PDU session parameters comprise at least one of:

21. A device for determining the relay PDU session establishment, applied to a remote terminal, is characterized in that the device comprises:

the relay device comprises a first sending module, a second sending module and a third sending module, wherein the first sending module is used for sending first information to the relay terminal, and the first information is used for determining a user terminal routing strategy URSP.

22. The apparatus of claim 21, further comprising:

and the second sending module is used for sending second information to the relay terminal, wherein the remote terminal carries a relay service code, and the relay service code and the PDU session parameter have an association relationship.

23. The apparatus of claim 21, wherein the first information comprises at least one of:

a Traffic descriptor;

application descriptors;

internet protocol IP descriptors;

Non-IP descriptors;

domain descriptors;

a data network name DNN;

connection Capabilities;

destination address information.

24. The apparatus of claim 22, wherein the first information and the second information are transmitted via messages of at least one of:

directly establishing a request message;

a direct link authentication reply message;

a direct link security command completion message;

a direct link change request message;

a direct link change reply message.

25. The apparatus of claim 21,

the first sending module is further configured to send the first information to the relay terminal after the secure connection between the remote terminal and the relay terminal is established.

26. The apparatus of claim 22,

the second sending module is further configured to send second information to the relay terminal after the secure connection between the remote terminal and the relay terminal is established;

27. A terminal comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the method steps of any of claims 1 to 7 or implementing the method steps of any of claims 8 to 13.

28. A readable storage medium, characterized in that a program or instructions are stored on the readable storage medium, which program or instructions, when executed by a processor, implement the method steps of any of claims 1 to 7, or implement the method steps of any of claims 8 to 13.