WO2022021355A1

WO2022021355A1 - Session establishment method and apparatus, and device and storage medium

Info

Publication number: WO2022021355A1
Application number: PCT/CN2020/106278
Authority: WO
Inventors: 刘建华; 杨皓睿
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2022-02-03
Also published as: CN115553045A

Abstract

Disclosed are a session establishment method and apparatus, and a device and a storage medium, which belong to the technical field of communications. The method comprises: a relay device sending a first session establishment request to a first core network device, wherein the first session establishment request is used for requesting the establishment of a PDU session between the relay device and a DN, and the first session establishment request comprises a first RSC. In the technical solution provided in the embodiments of the present application, a session establishment request is sent to a core network device by means of a relay device, wherein the session establishment request carries an RSC corresponding to a service attribute. Since the RSC represents a service code and has the characteristics of being difficult to crack and to leak, in comparison with directly carrying the service attribute in the session establishment request being likely to leak the service attribute and thus affect the system security, the embodiments of the present application also guarantee privacy protection for the service attribute when it is ensured that a core network is clear about the service attribute, thereby improving the system security.

Description

Session establishment method, apparatus, device and storage medium

technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a method, apparatus, device, and storage medium for establishing a session.

Background technique

3GPP (3rd Generation Partnership Project, 3rd Generation Partnership Project) introduced the concept of relay communication in the R13 (Release 13, 13th version) ProSe (Proximity Service, short-range communication service) architecture.

Relay communication refers to UE (User Equipment, terminal equipment)-to-Network (terminal equipment connected to the network) based on IP (Internet Protocol, Internet Protocol) layer relay. That is, the Remote UE (remote device) accesses the network through the Relay UE (relay device). The Relay UE undertakes the function of IP layer relay, and transmits data between the Remote UE and the network to establish a communication connection between the Remote UE and the network. Exemplarily, the network includes access network equipment and core network equipment, The Relay UE sends the data from the Remote UE to the access network device, which can be further sent by the access network device to the core network device; or, the access network device sends the data from the core network device to the Relay UE, and then The data from the access network device is sent by the Relay UE to the Remote UE.

However, in order to transmit data between the Remote UE and the network, the Relay UE needs to establish an appropriate PDU (Protocol Data Unit, Protocol Data Unit) session. According to the different service types that Remote UE needs to carry out, how to establish a PDU session corresponding to the service type needs further discussion and research.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a session establishment method, apparatus, device, and storage medium. The technical solution is as follows:

On the one hand, an embodiment of the present application provides a session establishment method, which is applied to a relay device, and the method includes:

Send a first session establishment request to the first core network device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and a DN (Date Network, data network), and the first session The establishment request includes the first RSC (Relay Service Code, relay service code).

On the other hand, an embodiment of the present application provides a session establishment method, which is applied to a first core network device, and the method includes:

Receive a first session establishment request from a relay device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session establishment request includes the first RSC .

In another aspect, an embodiment of the present application provides a session establishment method, which is applied to a second core network device, and the method includes:

receiving a second session establishment request from a first core network device, where the second core network device is selected by the first core network device based on the first RSC;

According to the second session establishment request, a PDU session between the relay device and the DN is established.

In another aspect, an embodiment of the present application provides an apparatus for establishing a session, which is set in a relay device, and the apparatus includes:

A first request sending module, configured to send a first session establishment request to a first core network device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session establishment request is The session establishment request includes the first RSC.

In another aspect, an embodiment of the present application provides an apparatus for establishing a session, which is set in a first core network device, and the apparatus includes:

A first request receiving module, configured to receive a first session establishment request from a relay device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session establishment request is The session establishment request includes the first RSC.

In another aspect, an embodiment of the present application provides an apparatus for establishing a session, which is set in a second core network device, and the apparatus includes:

a second request receiving module, configured to receive a second session establishment request from a first core network device, where the second core network device is selected by the first core network device based on the first RSC;

A session establishment module, configured to establish a PDU session between the relay device and the DN according to the second session establishment request.

In another aspect, an embodiment of the present application provides a relay device, where the relay device includes: a processor, and a transceiver connected to the processor; wherein:

The transceiver is configured to send a first session establishment request to a first core network device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session The setup request includes the first RSC.

In another aspect, an embodiment of the present application provides a core network device, where the network device includes: a processor, and a transceiver connected to the processor; wherein:

The transceiver is configured to receive a first session establishment request from a relay device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session The setup request includes the first RSC.

the transceiver, configured to receive a second session establishment request from a first core network device, where the second core network device is selected by the first core network device based on the first RSC;

The processor is configured to establish a PDU session between the relay device and the DN according to the second session establishment request.

In another aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a relay device, so as to realize the above-mentioned relay device Side session establishment method.

In another aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a core network device, so as to implement the above-mentioned first core A method for establishing a session on the network device side.

In another aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a core network device to implement the second core as described above. A method for establishing a session on the network device side.

In another aspect, an embodiment of the present application provides a chip, where the chip includes a programmable logic circuit and/or program instructions, and when the chip runs on a relay device, it is used to implement the above-mentioned relay device side session build method.

In another aspect, an embodiment of the present application provides a chip, where the chip includes a programmable logic circuit and/or program instructions, and when the chip runs on a core network device, it is used to implement the above-mentioned first core network device Side session establishment method.

In another aspect, an embodiment of the present application provides a chip, where the chip includes a programmable logic circuit and/or program instructions, and when the chip runs on a core network device, it is used to implement the above-mentioned second core network device Side session establishment method.

In another aspect, an embodiment of the present application provides a computer program product, which, when the computer program product runs on a relay device, enables a computer to execute the above-mentioned method for establishing a session on the relay device side.

In another aspect, an embodiment of the present application provides a computer program product, which when the computer program product runs on a core network device, enables a computer to execute the above-mentioned method for establishing a session on the side of the first core network device.

In another aspect, an embodiment of the present application provides a computer program product, which, when the computer program product runs on a core network device, enables a computer to execute the above-mentioned method for establishing a session on the device side of the second core network.

The technical solutions provided by the embodiments of the present application may include the following beneficial effects:

A session establishment request is sent to the core network device through the relay device. The session establishment request carries the RSC corresponding to the service attribute. Since the RSC is represented as a service code, it is not easy to be cracked and leaked. Compared with the direct session establishment request Carrying service attributes may cause service attribute leakage and affect system security. In the case of ensuring that the core network specifies service attributes, the embodiments of the present application also ensure privacy protection for service attributes and improve system security.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that are used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

2 is a schematic diagram of a system architecture of an EPS system provided by an embodiment of the present application;

3 is a schematic diagram of a system architecture of a 5GS system provided by an embodiment of the present application;

4 is a schematic diagram of a system architecture of a 5GS system provided by another embodiment of the present application;

5 is a schematic diagram of a relay communication system provided by an embodiment of the present application;

6 is a flowchart of a remote device accessing a network and obtaining an IP service provided by an embodiment of the present application;

7 is a flowchart of a relay device establishing a PDU session provided by an embodiment of the present application;

8 is a flowchart of a session establishment method provided by an embodiment of the present application;

FIG. 9 is a flowchart of a session establishment method provided by another embodiment of the present application;

10 is a flowchart of a session establishment method provided by still another embodiment of the present application;

11 is a flowchart of a session establishment method provided by another embodiment of the present application;

12 is a block diagram of a session establishment apparatus provided by an embodiment of the present application;

13 is a block diagram of a session establishment apparatus provided by another embodiment of the present application;

14 is a block diagram of a session establishment apparatus provided by still another embodiment of the present application;

FIG. 15 is a block diagram of a session establishment apparatus provided by another embodiment of the present application;

16 is a block diagram of a session establishment apparatus provided by still another embodiment of the present application;

17 is a structural block diagram of a relay device provided by an embodiment of the present application;

FIG. 18 is a structural block diagram of a core network device provided by an embodiment of the present application.

detailed description

In order to make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

The network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. The evolution of new business scenarios and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

The technical solutions provided in the embodiments of the present application can be applied to various communication systems, such as: GSM (Global System of Mobile Communication) system, CDMA (Code Division Multiple Access, code division multiple access) system, ECDMA (Wideband Code Division Multiple Access, Wideband Code Division Multiple Access) system, GPRS (General Packet Radio Service, General Packet Radio Service), LTE (Long Term Evolution, Long Term Evolution) system, FDD (Frequency Division Duplex, LTE Frequency Division Duplex) system, TDD (Time Division Duplex, LTE Time Division Duplex) system, UMTS (Universal Mobile Telecommunication System, Universal Mobile Telecommunications System), WiMAX (Worldwide Interoperability for Microwave Access, Worldwide Interoperability for Microwave Access) communication system, 5GS or New Radio (New Radio) , NR) system, or other subsequent evolution systems, etc.

Please refer to FIG. 1 , which shows a schematic diagram of a system architecture of a communication system provided by an embodiment of the present application. As shown in FIG. 1 , the system architecture 100 may include: a terminal device 10 , an access network device 20 and a core network device 30 .

Terminal equipment 10 may refer to a UE, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent, or user equipment. Optionally, the terminal device may also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol, session initiation protocol) phone, a WLL (Wireless Local Loop, wireless local loop) station, a PDA (Personal Digital Assistant, personal digital processing), Handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5GS, or in the future evolved PLMN (Pub1ic Land Mobi1e Network) terminal equipment, etc., which are not limited in this embodiment of the present application.

The access network device 20 is a device deployed in the access network to provide wireless communication functions for terminal devices. The access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different wireless access technologies, the names of devices with access network device functions may be different, for example, in 5G (5th-Generation, fifth-generation mobile communication) NR (New Radio, new air interface) In the system, it is called gNodeB or gNB, and in EPS (Evolved Packet System, Evolved Packet System) system, the access network device may be called eNodeB (Evolved NodeB, evolved base station). As communication technology evolves, the name "Access Network Equipment" may change. For convenience of description, in the embodiments of the present application, the above-mentioned apparatuses for providing wireless communication functions for terminal equipment are collectively referred to as access network equipment.

The core network device 30 refers to a device that can provide a terminal device with functions such as session management, mobility relationship, policy management, and security authentication. In this embodiment of the present application, the core network device 30 may include a first core network device and a second core network device, where the first core network device is responsible for access management and mobility management of terminal devices, and the second core network device is responsible for terminal devices Session management for devices. Exemplarily, in the 5GS system, the first core network can be implemented as AMF (Core Access and Mobility Management Function, core network access and mobility management function), and the second core network equipment can be implemented as SMF (Session Management Function, session management function); in the EPS system, the first core device may be implemented as an MME (Mobility Management Entity, mobility management entity), and the second core network device may be implemented as an SGW (Serving Gateway, serving network element).

In an example, as shown in FIG. 1 , the terminal devices include a remote (Remote) terminal device 12 and a relay (Relay) terminal device 14 . The relay device 14 can perform data transmission with the remote device 12 to establish a communication connection between the remote device 12 and the access network device 20 and the core network device 30. Exemplarily, the relay device 14 will be from the remote device 12 is sent to the access network device 20, and may be further sent by the access network device 20 to the core network device 30; or, the access network device 20 sends the data from the core network device 30 to the relay device 14, The data from the access network device 20 is then sent to the remote device 12 by the relay device 14 .

FIG. 2 shows a schematic diagram of a system architecture of an EPS system provided by an embodiment of the present application. As shown in Figure 2, the system architecture may include the following network entities:

1. EUTRAN: A network composed of multiple eNodeBs to implement wireless physical layer functions, resource scheduling and wireless resource management, wireless access control and mobility management functions. The eNodeBs can be connected through the X2 interface, which can be used to transmit data in the X2-based handover process. The eNodeB is connected to the SGW through the user plane interface SI-U, and uses GTP-U (General Packet Radio System General Tunneling Protocol User Plane, General Packet Radio System Tunneling Protocol user plane) to transmit user data: through the control plane interface SI-E and MME The SI-AP protocol is used to realize functions such as wireless access bearer control.

2. MME: It is mainly responsible for all control plane functions of user, namely session management, including NAS (Non-Access-Stratum, non-access stratum) signaling and security, management of tracking area list (Tracking Area List) management, P- Selection of GW (Packet Date Network Gateway, packet data network gateway) and SGW, etc.

3. SGW: It is mainly responsible for the data transmission, forwarding and route switching of the user equipment, and serves as the local mobility anchor point when the user equipment switches between eNodeBs (for each user, there is only one SGW at each moment). services).

4. P-GW: As the anchor point of PDN (Packet Date Network) connection, it is responsible for IP address allocation of user equipment, data packet filtering, rate control, and generation of billing information for user equipment.

5. SGSN (Serving GPR Supporting Node, Serving GPRS Supporting Node): 2G access network GERAN (GSM/EDGE Radio Access Network, GSM/EDGE wireless access network), 3G access network UTRAN (Universal Terrestrial Radio Access Network, Universal Terrestrial Radio Access) and the access node of the EPS core network EPC, responsible for the establishment and data forwarding from GERAN, UTRAN to EPC bearer.

6. HSS (Home Subscriber Server, Home Subscriber Server): stores the subscription data of mobile users.

7. PCRF (Policy and Charging Rules Function, policy and charging rule function): responsible for charging management and policy control, including PCC (Policy and Charging Control, policy and charging control) rules, QoS (Quality of Service, quality of service) )rule.

FIG. 3 shows a schematic diagram of a system architecture of a 5GS system provided by an embodiment of the present application. As shown in FIG. 3 , the system architecture 200 may include: UE, RAN (Radio Access Network, radio access network), Core (core network) and DN. Among them, UE, RAN, and Core are the main components of the architecture. Logically, they can be divided into two parts: the user plane and the control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data. In the figure, the NG2 reference point is located between the RAN control plane and the Core control plane, the NG3 reference point is located between the RAN user plane and the Core user plane, and the NG6 reference point is located between the Core user plane and the data network.

UE: It is the portal for mobile users to interact with the network. It can provide basic computing capabilities and storage capabilities, display service windows to users, and accept user operation input. The UE will use the next-generation air interface technology to establish a signal connection and a data connection with the RAN, thereby transmitting control signals and service data to the mobile network.

RAN: Similar to the base station in the traditional network, it is deployed close to the UE to provide network access functions for authorized users in a specific area, and can use transmission tunnels of different quality to transmit user data according to user levels and service requirements. The RAN can manage its own resources, utilize them rationally, provide access services for the UE on demand, and forward control signals and user data between the UE and the core network.

Core: Responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication for the UE. When the UE is attached, it provides network access authentication for the UE; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates the network resources for the UE; when the UE is idle, it provides a fast recovery mechanism for the UE: When the UE is detached, it releases network resources for the UE; when the UE has service data, it provides data routing functions for the UE, such as forwarding uplink data to the DN; or receiving the downlink data of the UE from the DN, forwarding it to the RAN, and then sending it to the UE .

DN: It is a data network that provides business services for users. Generally, the client is located in the UE, and the server is located in the data network. The data network can be a private network, such as a local area network, or an external network that is not controlled by operators, such as the Internet, or a private network jointly deployed by operators, such as in order to configure IMS (IP Multimedia Core Network Subsystem, IP Multimedia Core Network Subsystem, IP Multimedia Core Network Subsystem, IP Multimedia Core Network Subsystem). network subsystem) services.

Figure 4 is a detailed architecture determined on the basis of Figure 3, wherein the core network user plane includes UPF (User Plane Function, user plane function); the core network control plane includes AUSF (Authentication Server Function, authentication server function), AMF, SMF , NSSF (Network Slice Selection Function, Network Slice Selection Function), NEF (Network Exposure Function, Network Open Function), NRF (NF Repository Function, Network Function Entity Storage Function), UDM (Unified Data Management, Unified Data Management), PCF (Policy Control Function, policy control function), AF (Application Function, application function). The functions of these functional entities are as follows:

UPF: perform user data packet forwarding according to the routing rules of SMF;

AUSF: perform security authentication of the UE;

AMF: UE access management and mobility management;

SMF: UE session management;

NSSF: select network slice for UE;

NEF: Open network functions to third parties in the form of northbound API interfaces;

NRF: Provides the storage function and selection function of network function entity information for other network elements;

UDM: user subscription context management;

PCF: User Policy Management;

AF: User Application Management.

In the architecture shown in Figure 4, the N1 interface is the reference point between the UE and the AMF; the N2 interface is the reference point between the RAN and the AMF, used for sending NAS messages, etc.; the N3 interface is the reference point between the RAN and the UPF, It is used to transmit data on the user plane, etc.; the N4 interface is the reference point between the SMF and the UPF, and is used to transmit information such as the tunnel identification information of the N3 connection, the data buffer indication information, and the downlink data notification message; the N6 interface is the UPF and the UPF. The reference point between DNs, used to transmit data on the user plane, etc.

It should be noted that the name of the interface between each network element in FIG. 3 and FIG. 4 is just an example, and the name of the interface in specific implementation may be other names, which are not specifically limited in this embodiment of the present application. The names of each network element (such as SMF, AF, UPF, etc.) included in FIG. 3 and FIG. 4 are only an example, and the functions of the network elements themselves are not limited. In 5GS and other future networks, each of the foregoing network elements may also have other names, which are not specifically limited in this embodiment of the present application. For example, in a 6G network, some or all of the above-mentioned network elements may use the terminology in 5G, and may also use other names, etc., which will be uniformly described here, and will not be repeated below. In addition, it should be understood that the names of the messages (or signaling) transmitted between the above network elements are only an example, and do not constitute any limitation on the functions of the messages themselves.

Please refer to FIG. 5 , which shows a schematic diagram of a relay communication system provided by an embodiment of the present application. The relay communication system shown in FIG. 5 mainly includes three parts: a wireless subsystem part, an EPC (Evolved Packet Core, Evolved Packet Core) part, and a short-range communication service part.

The radio subsystem part, namely EUTRAN, includes one or more eNodeBs, and can also be called the access network equipment part in the EPS system.

The EPC part includes the above-mentioned HSS, MME, SGW, PGW, etc.

The short-range communication service part, that is, the ProSe architecture part, includes PF (ProSe Function, short-range communication service function), PAS (ProSe Application Server, short-range communication application server), relay equipment (Relay UE), remote equipment (Remote UE) ). Among them: PF: used to authorize short-range communication of terminal devices, provide discovery assistance between terminal devices, etc.; PAS: used to provide specific short-range communication service support; Relay UE: used to provide relay access for Remote UE Support; Remote UE: used to access the network through Relay UE to obtain IP (Internet Protocol, protocol for interconnection between networks) services. In an example, as shown in FIG. 5 , a PA (ProSe Application, short-range communication service) is installed in both the Relay UE and the Remote UE.

Based on the relay communication system architecture shown in FIG. 5 , FIG. 6 shows a flowchart of a remote device accessing the network through the relay device and obtaining an IP service. As shown in Figure 6, the process for a remote device to access the network includes the following steps:

Step 610, the relay device attaches to the network and/or the relay device requests to establish a PDN connection. The relay device can request to establish a PDN (Public Data Network, public data network) connection while being attached to the network.

Step 620, the remote device discovers the relay device. In an example, in the process of discovering the relay device, the remote device uses the APN (Access Point Name, access point name) supported by the relay device as reference information.

Step 630, the remote device requests the relay device to establish one-to-one communication. The remote device may request the relay device to establish one-to-one (One-2-One) communication through the PC5 interface, optionally, the request sent by the remote device carries the APN. Optionally, while or after step 630 is performed, step 632 may also be performed, where the relay device requests to establish a new PDN connection.

Step 640, the relay device assigns an IP address to the remote device. This embodiment of the present application does not limit the content of the IP address. Optionally, the IP address is a private IPv4 address or an IPv6 prefix.

Step 650, the relay device sends a remote terminal report to the MME. Optionally, the remote terminal report carries the identifier of the remote device (such as Remote UE ID (Identifier, identifier)), IP address, and the like.

Step 660, the MME sends a remote terminal report to the PGW. After the MME receives the remote terminal report of the relay device, it can send the remote terminal report to the PGW, so that the PGW stores the information of the remote device locally, and the PGW can use the information subsequently to gate the uplink and downlink data of the remote device. control, that is, whether to allow the transmission of uplink and downlink data. Optionally, after step 660, the method further includes: the remote device sends uplink IP data, or receives downlink IP data, the IP data passes through the relay device, and the IP data is carried in the application created by the relay device for the remote device. within the subsequent PDN connection.

It can be known from the above step 630 that, in order to transmit the relay data of the remote device, the relay device needs to use an appropriate PDU session, and which PDU session to use to transmit the relay data is determined by the relay device. Generally, during the establishment of the PDU session, the relay device determines the parameters required for establishing the PDU session according to the URSP (UE Path Selection Policy) configured by the network. Please refer to FIG. 7 , which shows a flowchart of establishing a PDU session by a relay device according to an embodiment of the present application. As shown in Figure 7, the process includes the following steps:

Step 701, the relay device sends a session establishment request message to the AMF. After the relay device (Relay UE) registers with the AMF entity, it will send a session establishment request message to the AMF entity, and the session establishment request message is used to request the establishment of a PDU session. In an example, the session request establishment message includes at least one of the following: S-NSSAI (session management-network slice selection assistance information, session management-network slice selection assistance information) corresponding to the PDU session, DNN (Date) corresponding to the PDU session Network Name, data network name), PDU session identifier, request type (request type), N1SM information (N1session management information), PDU type.

Step 702, the AMF selects the SMF. After the AMF entity receives the session establishment request message, it can select an SMF entity according to certain rules.

Step 703, the AMF sends an SM request message to the SMF. After selecting the SMF entity, the AMF entity may send an SM (Session Management, session management) request message to the SMF entity. Optionally, the SM request message includes at least one of the following: subscriber permanent ID (subscriber permanent ID), DNN, S-NSSAI, PDU session ID, N1SM information, user location information (user location information), access technology type .

Step 704, the SMF sends a subscription data request message to the UDM. If the SMF entity has not acquired the SM-related subscription information of the Relay UE from the UDM entity, the SMF entity needs to send a subscription data request message to the UDM entity to acquire subscription data. In one example, the subscription data request message includes at least one of the following: subscription identifier (subscriber permanent ID), DNN.

Step 705, the UDM sends subscription data to the SMF. After receiving the subscription data request message, the UDM entity may send a subscription data response (subscription data response) message to the SMF entity. In one example, the subscription data response message includes subscription information. Then the SMF can perform authorization check on the subscription information, and in the case that the SMF entity confirms that the authorization check fails, it sends a NAS (Non Access Stratum, non-access stratum) signaling to the Relay UE, and the NAS signaling is used to indicate the rejection of the Relay UE. session establishment request.

Step 706, the SMF completes the authorization/authentication of the establishment of the PDU session. In the case that the SMF entity needs to authorize/authenticate the establishment of the PDU session, the SMF entity needs to select the UPF entity according to certain rules, and then the SMF entity triggers the authorization/authentication of the establishment of the PDU session to complete the authorization/authentication of the establishment of the PDU session .

Step 707, the SMF selects the PCF. In the case of dynamic PCC (Policy Control and Charging) deployment, the SMF entity needs to select the PCF entity according to certain rules.

Step 708, the SMF obtains the PCC rule. The SMF entity sends a PDU-CAN (Controller Area Network, Controller Area Network) session establishment request to the selected PCF entity, so as to obtain the PCC rule corresponding to the PDU session.

Step 709, the SMF selects the UPF. If in step 706, the SMF entity does not select a UPF, then at this time, the SMF entity may select a UPF entity.

Step 710, the SMF initiates a PDU-CAN session establishment process. When dynamic PCC is deployed and the PDU-CAN session establishment process has not been executed, the SMF entity may initiate the PDU-CAN session establishment process to the PCF entity, and then the SMF entity obtains the default PCC rules from the PCF entity. In the case where the request type sent by the Relay UE indicates that the PDU session requested to be established is an existing PDU session, the SMF entity initiates the PDU-CAN session modification process, and the SMF entity sends the assigned IP address of the Relay UE to PCF entity.

Step 711, the SMF initiates an N4 session establishment/modification process to the UPF. If the request type is the initial request type, the SMF entity initiates the N4 session establishment process to the UPF entity; otherwise, the SMF entity initiates the N4 session modification process to the UPF entity. Optionally, the SMF entity may also provide the UPF entity with packet detection, reporting rules, and CN tunnel information (tunnel info).

Step 712, the UPF sends an N4 session establishment/modification response message to the SMF. After receiving the initiation request from the SMF entity, the UPF entity may send an N4 session establishment/modification response message to the SMF entity.

Step 713, the SMF sends an SM response message to the AMF. In an example, the SM response message includes at least one of the following: a cause value (cause), N2 reference point session management information (N2SM information), N1SM information, and the like.

Step 714, the AMF sends an N2PDU session request message to the RAN. In an example, the N2PDU session request message includes at least one of the following: N2SM information, NAS message, and the like.

Step 715, the RAN sends an RRC connection reconfiguration message to the relay device. The RAN entity may send an RRC (Radio Resource Control, Radio Resource Control) connection reconfiguration message to the Relay UE, and the RAN entity allocates necessary RAN resources according to QoS (Quality of Service, quality of service) rules. Optionally, the RAN entity may also forward the NAS message to the Relay UE.

Step 716, the relay device sends an RRC connection reconfiguration response message to the RAN. After receiving the RRC connection reconfiguration message from the RAN entity, the Relay UE may send an RRC connection reconfiguration response message to the RAN entity.

Step 717, the RAN sends an N2PDU session establishment response message to the AMF. In one example, the N2PDU session response message includes at least one of the following: a PDU session identifier, a cause value, and an N2SM message.

Step 718, the AMF sends an SM request message to the SMF. The SM request message includes the N2SM message in the above step 717, and further, the AMF entity may forward the N2SM message from the RAN entity to the SMF entity.

Step 719, the SMF sends an N4 session establishment/modification request message to the UPF. In the case that the N4 session is not established, the SMF entity can send an N4 session establishment message to the UPF entity; when the N4 session is established, the SMF entity can send an N4 session modification message to the UPF entity to update the access network (Access Network, AN) tunnel information and core network (Core Network, CN) tunnel information.

Step 720, the UPF sends an N4 session establishment/modification response message to the SMF. In the case of receiving the N4 session establishment/modification message, the UPF entity may send a corresponding N4 session establishment/modification response message to the SMF entity.

Step 721, the SMF sends an SM response message to the AMF. In one example, the SM response message includes a cause value.

Step 722, the SMF sends an IPv6 route advertisement message to the UPF. In one example, the IPv6 router advertisement message (IPv6 Router Advertisement) includes the IPv6 address prefix assigned by the SMF entity.

Step 723, the SMF releases user plane resources. In the case that the PDU session is triggered by 3GPP or non-3GPP handover, the SMF entity also needs to release user plane resources on the original access side.

Step 724, the SMF triggers the unified data management registration service network function service. In the case that the identity of the SMF entity is not included in step 705, the SMF needs to trigger the unified data management registration service network function service, so that the SMF entity, the PCF entity, and the UDM entity perform service request interaction. The service request includes the address of the SMF entity, the identifier of the SMF entity that the DNN and the UDM entity need to save, the address of the SMF entity, the associated DNN, and the like.

It can be seen from the above description that in order to transmit data between the Remote UE and the network, the Relay UE needs to establish an appropriate PDU session. For different service types that the Remote UE needs to carry out, there is no relevant mechanism in the related art to establish a PDU session corresponding to the service type. Based on this, the embodiments of the present application provide a method for establishing a session, and the technical solutions of the present application are described below through several exemplary embodiments.

Please refer to FIG. 8 , which shows a flowchart of a session establishment method provided by an embodiment of the present application. The method may be applied to the system architecture shown in FIG. 1 , and the method may include the following steps:

Step 810, the relay device sends a first session establishment request to the first core network device, the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session establishment request includes the first RSC .

When there is a data transmission requirement between the relay device (Relay UE) and the DN, a PDU session between the relay device and the DN can be established, that is, a data transmission channel between the relay device and the DN can be established. To this end, the relay device sends a first session establishment request to the first core network device, where the first session establishment request is used to request the establishment of the first PDU session. Optionally, the first core network device is implemented as the above-mentioned AMF (or referred to as "AMF entity", "AMF network element", etc.); or, in the subsequent technological evolution, implemented as other equipment with access management and mobility. Core network equipment for management functions.

In this embodiment of the present application, the first session establishment request includes the first RSC. The RSC (relay service code) corresponds to the service attribute requested by the device. Compared with directly carrying the service attribute in the session establishment request, the service attribute may leak and affect system security. The RSC corresponding to the service attribute ensures the privacy protection of the service attribute and improves the security of the system while ensuring that the core network specifies the service attribute. Optionally, the first session establishment request is the session establishment request message in the above step 701, so the difference between the step 810 and the above step 701 is that the first session establishment request in the step 810 includes the first RSC.

Optionally, there is a one-to-one correspondence between RSCs and service attributes, that is, one RSC corresponds to one service attribute. The service attribute refers to the attribute corresponding to the service requested by the device. Optionally, the service attribute includes at least one of the following: DNN information, slice (slice) information, session type information, PLMN information, QoS information, and the like. This embodiment of the present application does not limit the manner of determining the first RSC. Optionally, the first RSC is determined by a remote device (Remote UE) and sent to the relay device. For example, the remote device needs to initiate a service and wants to When a relay device is found to perform relay communication, the remote device needs to first determine the first RSC according to the service to be established, and send the determined first RSC to the relay device; or, the first RSC is preset on the relay device. In the device, for example, corresponding to a certain relay device, it is assumed that it can only initiate a specific type of service, so the RSC corresponding to the service initiated by the device may also be fixed, so that the RSC can be preset in the relay device.

The first core network device receives the first session establishment request, and parses the first session establishment request to obtain the first RSC. Since there are multiple core network devices (or called "entities", "network elements", etc.) that can establish PDU sessions in the core network system architecture, the service attributes supported by each core network device are different, for example, some Core network equipment supports DNN information, and some core network equipment supports session type information. Therefore, for different service attributes, different core network devices need to be used to establish PDU sessions. The following describes a process in which the first core network device selects an appropriate core network device based on the first RSC to establish a PDU session.

In an example, as shown in FIG. 9, after the above step 810, the following steps are further included:

Step 820, the first core network device selects a second core network device according to the first RSC, and the second core network device is used to establish a PDU session.

The second core network device is the core network device used to establish the PDU session. Optionally, the second core network device is implemented as SMF; or, in the subsequent technological evolution, implemented as other core network devices with device session management functions . The selection basis of the second core network device includes the first RSC, and the first core network device selects the second core network device corresponding to the service attribute according to the first RSC to establish the PDU session, so that the established PDU session satisfies the service of the remote device need. Optionally, in addition to selecting the second core network device according to the first RSC, the first core network device may also select the second core network device according to other information, such as selecting the second core network as mentioned in the related art. Device rules. For the specific selection process of the second core network device, please refer to the following embodiments, and details are not repeated here. Optionally, the first core network device selects the second core network device as the above step 702, so the difference between step 820 and the above step 702 is that in step 820, the first core network device selects the second core network device. Including the first RSC.

Step 830: The first core network device sends a second session establishment request to the second core network device.

After the first core network device selects an appropriate second core network device, a second session establishment request may be sent to the second core network device to request to establish a PDU session between the relay device and the DN. This embodiment of the present application does not limit the content of the second session establishment request. Optionally, the second session establishment request includes the first RSC; or, the second session establishment request includes session parameter information related to the PDU session requested to be established. This embodiment of the present application does not limit the contents of the first session establishment request and the second session establishment request. Optionally, the contents of the first session establishment request and the second session establishment request are the same, that is, the first core network device will receive The received first session establishment request from the relay device is forwarded to the second core network device; or, the content of the first session establishment request and the second session establishment request are different, that is, the first core network device does not receive the The content of the first session establishment request from the relay device is processed to obtain a second session establishment request, and the second session establishment request is sent to the second core network device.

Step 840, the second core network device establishes a PDU session between the relay device and the DN according to the second session establishment request.

After receiving the second session establishment request, the second core network device parses the second session establishment request to obtain some parameter information and the like, and then establishes a PDU session between the relay device and the DN according to the parameter information obtained by parsing. For an introduction and description of the process of establishing a PDU session by the second core network device, please refer to the following embodiments, and details are not repeated here.

Step 850, the first core network device sends a first session establishment response to the relay device, where the first session establishment response is used to indicate that the PDU session establishment is completed.

After the second core network device establishes the PDU session, it may notify the first core network device that the establishment of the PDU session is completed. This embodiment of the present application does not limit the manner in which the second core network device notifies the establishment of the PDU session. The network device carries a notification message in the SM response message sent to the first core network device in the above step 713, and the notification message is used to indicate that the establishment of the PDU session is completed; or, the second core network device sends a notification to the first core network device alone. message, the notification message is used to indicate that the establishment of the PDU session is completed.

After receiving the notification that the PDU session establishment is completed, the first core network device sends a first session establishment response to the relay device. The data transmission channel is established. This embodiment of the present application does not limit the bearing mode of the first session establishment response. Optionally, the first core network device sends the first session establishment response to the relay device independently to notify the relay device that the PDU session establishment is completed; A core network device carries the first session establishment response in the RRC connection reconfiguration message sent to the relay device in the above step 715 to notify the relay device that the PDU session establishment is completed. Optionally, the first session establishment response includes the first RSC, so that the relay device can specify the service or RSC corresponding to the first session establishment response.

To sum up, in the technical solutions provided by the embodiments of the present application, a session establishment request is sent to the core network device through the relay device, and the session establishment request carries the RSC corresponding to the service attribute. Compared with directly carrying service attributes in the session establishment request, which may cause service attribute leakage and affect system security, the embodiment of the present application also ensures privacy protection for service attributes while ensuring that the core network specifies service attributes. , to improve the security of the system.

In addition, according to the technical solutions provided by the embodiments of the present application, the core network device selects another suitable core network device to establish a PDU session according to the RSC carried in the session establishment request, so as to establish a data transmission channel between the relay device and the DN. Since different core network devices with session management functions support different service attributes, the embodiments of the present application fully consider the factors that affect the PDU session establishment process, and use the RSC corresponding to the service attribute to select the service attribute for establishing the PDU session. The core network equipment ensures that the selected core network equipment supports the attributes corresponding to the services requested by the remote equipment, which improves the success rate of PDU session establishment.

It can be seen from the description of the above embodiment that the first core network device can select the second core network device by the first RSC. The embodiment of the present application provides two methods for the selection of the second core network device. One method is to select the second core network device. For the second core network device corresponding to one RSC, another way is to determine session parameter information of the PDU session according to the first RSC, and then select the second core network device corresponding to the session parameter information.

First, the first method will be introduced and explained.

In one example, as shown in FIG. 10 , the above step 820 includes:

Step 822, the first core network device selects a second core network device corresponding to the first RSC according to the first configuration information, where the first configuration information includes the correspondence between the RSC and the second core network device.

The first configuration information includes the correspondence between the RSC and the second core network device. This embodiment of the present application does not limit the number of correspondences included in the first configuration information, and optionally, the correspondences are one or more. This embodiment of the present application does not limit the correspondence between the RSC and the second core network device. Optionally, there is a one-to-one correspondence between the RSC and the second core network device; or, multiple RSCs correspond to one second core network device Or, one RSC corresponds to multiple second core network devices, which is not limited in this embodiment of the present application. Optionally, the first configuration information is pre-configured in the first core network device, that is, the first configuration information is local configuration information of the first core network device; or, the first configuration information is pre-configured in the communication protocol. For definition, this embodiment of the present application does not limit this.

Based on this, as shown in FIG. 10 , the above step 830 includes: step 832 , the first core network device sends a second session establishment request to the second core network device, and the second session establishment request includes the first RSC.

The first core network device includes the first RSC in the session establishment request sent to the second core network device, so that the second core network device determines session parameter information used in the process of establishing the PDU session according to the first RSC. The embodiments of the present application do not limit the manner in which the second core network device determines the session parameter information of the PDU session, and several manners for the second core network device to determine the session parameter information are provided below.

Optionally, as shown in FIG. 10, the above step 840 includes: step 842, the second core network device determines session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes the RSC and session parameter information The corresponding relationship between them; Step 844, the second core network device establishes a PDU session according to the session parameter information.

The third configuration information includes the correspondence between the RSC and the session parameter information. This embodiment of the present application does not limit the number of correspondences included in the third configuration information, and optionally, the correspondences are one or more. This embodiment of the present application does not limit the correspondence between the RSC and the session parameter information. Optionally, there is a one-to-one correspondence between the RSC and the session parameter information; or, multiple RSCs correspond to one session parameter information; or, one RSC corresponds to For multiple session parameter information, this is not limited in this embodiment of the present application. Optionally, the third configuration information is pre-configured in the second core network device, that is, the third configuration information is local configuration information of the second core network device; or, the third configuration information is pre-configured in the communication protocol. Alternatively, the third configuration information is configured by other core network devices to the second core network device, such as configured by the first core network device to the second core network device, which is not limited in this embodiment of the present application.

The second core network device may determine session parameter information corresponding to the first RSC according to the third configuration information, and then establish a PDU session according to the session parameter information. The session parameter information is the session parameter information corresponding to the PDU session to be established by the second core network device, that is, the session parameter information corresponding to the PDU session requested by the relay device to be established. Optionally, the session parameter information includes at least one of the following: slice information, DNN information, SSC mode information, and session type information, and the specific content of the session parameter information is not limited in this embodiment of the present application.

Optionally, as shown in FIG. 10, the above step 840 includes: step 846, the second core network device determines session parameter information according to the first information field in the first RSC; step 848, the second core network device determines the session parameter information according to the session parameter information to establish a PDU session.

The session parameter information corresponding to the PDU session may also be indicated by the information field of the first RSC. In this embodiment of the present application, the first information field of the first RSC is used to indicate the session parameter information, and the second core network device may use the first information according to the first information. field to determine session parameter information to use to establish a PDU session. This embodiment of the present application does not limit the number of bits of the first information field. Optionally, the first information field is one or more bits. In practical applications, the number of bits of the first information field may be combined with the length of the session parameter information, the The length of an RSC, etc. is determined. This embodiment of the present application also does not limit the number of the first information fields. Optionally, the first information fields include one or more information fields in the first RSC.

In another example, as shown in FIG. 10 , the above step 820 includes:

Step 824, the first core network device sends the first RSC to the third core network device.

The second core network device may also be selected by the third core network device. In this embodiment of the present application, the first core network device may send the first RSC to the third core network device, and the third core network device selects and communicates with the first RSC. The corresponding second core network device. For an introduction and description of the third core network device selecting the second core network device according to the first RSC, please refer to the above method embodiments, and details are not repeated here. Optionally, the above-mentioned third core network device includes at least one of the following devices: an NRF entity (or referred to as "NRF"), a PCF entity (or referred to as "PCF").

Step 826, the third core network device sends device information to the first core network device, where the device information is used to indicate the second core network device corresponding to the first RSC.

In order to indicate the selected second core network device to the first core network device, the third core network device needs to send device information to the first core network device, where the device information is used to instruct the third core network device to select the device that is the same as the first core network device. The second core network device corresponding to the RSC. The specific content of the device information is not limited in this embodiment of the present application. Optionally, the device information includes at least one of the following: address information of the second core network device, and identification information of the second core network device, wherein the second core network device The address information of the second core network device is used to indicate the address of the second core network device (such as network address, physical address, etc.); the identification information of the second core network device is used to indicate the identification of the second core network device (such as device unique identification, device ID, etc. ).

Optionally, as shown in FIG. 10 , the above step 830 includes: step 832, the first core network device sends a second session establishment request to the second core network device, the second session establishment request is used to request the establishment of a PDU session, and the first core network device sends a second session establishment request to the second core network device. The second session establishment request includes the first RSC. For the introduction and description of step 832, please refer to the above-mentioned embodiment, and details are not repeated here.

Optionally, as shown in FIG. 10, the above step 840 includes: step 842, the second core network device determines session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes the RSC and session parameter information The corresponding relationship between them; Step 844, the second core network device establishes a PDU session according to the session parameter information. Optionally, as shown in FIG. 10, the above step 840 includes: step 846, the second core network device determines session parameter information according to the first information field in the first RSC; step 848, the second core network device determines the session parameter information according to the session parameter information to establish a PDU session. For the introduction and description of steps 842 , 844 , 846 and 848 , please refer to the above-mentioned embodiment, which will not be repeated here.

It should be noted that, in the embodiment of the present application, the steps of the above method can be arbitrarily combined on the premise that the logic is not violated. For example, the above step 832 is executed after the above step 822, and then the above steps 842 and 844 are executed; for another example, After the above-mentioned step 822, perform the above-mentioned step 832, and then perform the above-mentioned steps 846 and 848; for another example, after the above-mentioned steps 824 and 826, perform the above-mentioned step 832, and then perform the above-mentioned steps 842 and 844; for example, the above-mentioned steps 824 and 844 After 826, the above-mentioned step 832 is performed, and then the above-mentioned steps 846 and 848 are performed. It should be understood that these should all fall within the protection scope of the present application.

Next, the second method is introduced and explained.

In yet another example, as shown in FIG. 11 , the above step 820 includes:

Step 821, the first core network device sends the first RSC to the third core network device.

In this embodiment of the present application, the first core network device may send the first RSC to the third core network device, and the third core network device determines session parameter information required for establishing a PDU session according to the first RSC. Optionally, the above-mentioned third core network device includes at least one of the following devices: an NRF entity (or referred to as "NRF"), a PCF entity (or referred to as "PCF").

Step 823: The third core network device sends session parameter information corresponding to the first RSC to the first core network device.

After receiving the first RSC, the third core network device may determine session parameter information according to the second configuration information. For the introduction and description of the third core network device determining the session parameter information and the second configuration information according to the first RSC, please refer to the following embodiment of the first core network device determining the session parameter information, which is not repeated here. Optionally, the session parameter information includes at least one of the following: slice information, DNN information, SSC mode information, and session type information, and the specific content of the session parameter information is not limited in this embodiment of the present application.

After the third core network device determines the session parameter information, the session parameter information may be sent to the first core network device, so that the first core network device selects the second core network device according to the session parameter information.

Step 825: The first core network device selects the second core network device corresponding to the session parameter information according to the third configuration information, where the third configuration information includes the correspondence between the session parameter information and the second core network device.

The third configuration information includes the correspondence between the RSC and the session parameter information. Optionally, the third configuration information is pre-configured in the first core network device, that is, the third configuration information is the first core network device. local configuration information; or, the third configuration information is predefined in the communication protocol, which is not limited in this embodiment of the present application. For other descriptions of the third configuration information, please refer to the above method embodiments, and details are not repeated here.

Based on this, as shown in FIG. 11 , the above step 830 includes: step 831 , the first core network device sends a second session establishment request to the second core network device, and the second session establishment request includes session parameter information.

Since the first core network device has determined the session parameter information, the second session establishment request sent by the first core network device to the second core network device may include the session parameter information, so that the second core network device can directly rely on the session The parameter information establishes a PDU session.

Based on this, as shown in FIG. 11 , the above step 840 includes: step 841 , the second core network device establishes a PDU session according to the session parameter information.

After the second core network device receives the second session establishment request, it parses the second session establishment request to obtain session parameter information, so that the second core network device establishes a PDU session according to the session parameter information obtained by parsing, so as to establish a communication between the relay device and the relay device. Data transmission channel between DNs.

In yet another example, as shown in FIG. 11 , the above step 820 includes:

Step 827: The first core network device determines session parameter information corresponding to the first RSC according to the second configuration information, where the second configuration information includes the correspondence between the RSC and the session parameter information.

The second configuration information includes the correspondence between the RSC and the session parameter information. This embodiment of the present application does not limit the number of correspondences included in the second configuration information, and optionally, the correspondences are one or more. This embodiment of the present application does not limit the correspondence between the RSC and the session parameter information. Optionally, there is a one-to-one correspondence between the RSC and the session parameter information; or, multiple RSCs correspond to one session parameter information; or, one RSC corresponds to For multiple session parameter information, this is not limited in this embodiment of the present application. Optionally, the second configuration information is preconfigured in the first core network device, that is, the first configuration information is local configuration information of the first core network device; or, the first configuration information is preconfigured in the communication protocol. For definition, this embodiment of the present application does not limit this. The first core network device may determine session parameter information corresponding to the first RSC according to the second configuration information, so as to further determine the second core network device according to the session parameter information. Optionally, the session parameter information includes at least one of the following: slice information, DNN information, SSC mode information, and session type information, and the specific content of the session parameter information is not limited in this embodiment of the present application.

Step 829, the first core network device selects the second core network device corresponding to the session parameter information according to the third configuration information, where the third configuration information includes the correspondence between the session parameter information and the second core network device.

For the description of step 829, please refer to the above-mentioned step 825, and details are not repeated here.

Based on this, as shown in FIG. 11 , the above step 830 includes: step 831 , the first core network device sends a second session establishment request to the second core network device, and the second session establishment request includes session parameter information. Based on this, as shown in FIG. 11 , the above step 840 includes: step 841 , the second core network device establishes a PDU session according to the session parameter information. For the introduction and description of step 831 and step 841, please refer to the above-mentioned embodiment, and details are not repeated here.

In yet another example, as shown in FIG. 11 , the above step 820 includes:

Step 82A, the first core network device determines session parameter information according to the first information field in the first RSC, and the session parameter information is used to establish a PDU session.

For the description of the introduction of the first information field, please refer to the description of the above-mentioned steps 846 and 848, and details are not repeated here. The first core network device may determine session parameter information for establishing a PDU session according to the first information field in the first RSC, so as to select the second core network device according to the session parameter information. Optionally, the above session parameter information includes at least one of the following: slice information, DNN information, SSC mode information, and session type information.

Step 82B, the first core network device selects the second core network device corresponding to the session parameter information according to the third configuration information, where the third configuration information includes the correspondence between the session parameter information and the second core network device.

For the description of step 82B, please refer to the above-mentioned step 825, and details are not repeated here.

It should be noted that, in the embodiment of the present application, the steps of the above method can be arbitrarily combined on the premise that the logic is not violated. For example, the above step 831 is executed after the above step 821, step 823 and step 825, and then the above step 841 is executed; For another example, the above-mentioned step 831 is executed after the above-mentioned steps 827 and 829, and then the above-mentioned step 841 is executed; for another example, the above-mentioned step 831 is executed after the above-mentioned steps 82A and 82B, and then the above-mentioned step 841 is executed. It should be understood that these should all fall within the protection scope of the present application.

It should also be noted that the first configuration information in this embodiment of the present application is only used to indicate the configuration information that includes the correspondence between the first RSC and the second core network device, and the second configuration information is only used to indicate that the first configuration information includes the first RSC and the second core network device. One is the configuration information of the corresponding relationship between the RSC and the session parameter information, and the third configuration information is only used to represent the configuration information including the corresponding relationship between the session parameter information and the second core network device. It should be understood that the first configuration information, The second configuration information and the third configuration information are not used to limit the configuration information of a certain core network device.

To sum up, the technical solutions provided by the embodiments of the present application, by selecting the core network equipment corresponding to the RSC carried in the session establishment request according to the corresponding relationship between the RSC and the core network equipment, realizes the core network equipment according to the RSC. specific method of selection. Moreover, the embodiments of the present application provide multiple selection subjects and multiple selection methods, and these selection subjects and selection methods can be combined in various forms, which improves the flexibility of core network device selection.

It should be noted that, in the above method embodiments, the session establishment method provided by the present application is described mainly from the perspective of interaction among the relay device, the first core network device and the second core network device. The above-mentioned steps performed by the relay device can be independently implemented as a method for establishing a session on the relay device side; the above-mentioned steps performed by the first core network device can be implemented independently as a method for establishing a session on the side of the first core network device; The steps performed by the core network device may be independently implemented as a second core network device-side session establishment method.

The following are apparatus embodiments of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

Please refer to FIG. 12 , which shows a block diagram of a session establishment apparatus provided by an embodiment of the present application. The apparatus has the function of implementing the above example of the method on the relay device side, and the function may be implemented by hardware or by executing corresponding software in hardware. The apparatus may be the relay device described above, or may be set in the relay device. As shown in FIG. 12 , the apparatus 1200 may include: a first request sending module 1210 .

The first request sending module 1210 is configured to send a first session establishment request to the first core network device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session establishment request is A session establishment request includes the first RSC.

In an example, the first RSC is used to select a second core network device, and the second core network device is used to establish the PDU session.

In an example, as shown in FIG. 13 , the apparatus 1200 further includes: a first response receiving module 1220, configured to receive a first session establishment response from the first core network device, the first session establishment The response is used to indicate that the PDU session establishment is complete.

In one example, the first session establishment response includes the first RSC.

Please refer to FIG. 13 , which shows a block diagram of a session establishment apparatus provided by an embodiment of the present application. The apparatus has the function of implementing the above-mentioned method example on the device side of the first core network, and the function may be implemented by hardware or by executing corresponding software in hardware. The apparatus may be the above-mentioned first core network device, or may be provided in the first core network device. As shown in FIG. 14 , the apparatus 1400 may include: a first request receiving module 1410 .

The first request receiving module 1410 is configured to receive a first session establishment request from a relay device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN. A session establishment request includes the first RSC.

In an example, as shown in FIG. 15 , the apparatus 1400 further includes: a device selection module 1420, configured to select a second core network device according to the first RSC, and the second core network device is configured to establish the PDU session.

In an example, as shown in FIG. 15 , the device selection module 1420 is configured to: select a second core network device corresponding to the first RSC according to first configuration information, where the first configuration information includes the RSC The corresponding relationship with the second core network device.

In an example, as shown in FIG. 15 , the device selection module 1420 is configured to: send the first RSC to a third core network device; receive device information from the third core network device, the The device information is used to indicate the second core network device corresponding to the first RSC.

In an example, the device information includes at least one of the following: address information of the second core network device, and identification information of the second core network device.

In an example, as shown in FIG. 15 , the device selection module 1420 is configured to: send the first RSC to a third core network device; Session parameter information corresponding to an RSC, the session parameter information is used to establish the PDU session; according to third configuration information, the second core network device corresponding to the session parameter information is selected, and the third configuration information includes the session Correspondence between the parameter information and the second core network device.

In an example, as shown in FIG. 15 , the device selection module 1420 is configured to: determine session parameter information corresponding to the first RSC according to the second configuration information, where the session parameter information is used to establish the PDU session, the second configuration information includes the correspondence between the RSC and the session parameter information; according to the third configuration information, the second core network device corresponding to the session parameter information is selected, and the third configuration information includes the session Correspondence between the parameter information and the second core network device.

In an example, as shown in FIG. 15 , the device selection module 1420 is configured to: determine session parameter information according to the first information field in the first RSC, where the session parameter information is used to establish the PDU session; selecting a second core network device corresponding to the session parameter information according to third configuration information, where the third configuration information includes a correspondence between the session parameter information and the second core network device.

In one example, the session parameter information includes at least one of the following: slice information, DNN information, SSC mode information, and session type information.

In an example, the third core network device includes at least one of the following devices: an NRF entity, a PCF entity.

In an example, as shown in FIG. 15 , the apparatus 1400 further includes: a second request sending module 1430, configured to send a second session establishment request to the second core network device, the second session establishment request using In the request to establish the PDU session, and the second session establishment request includes the first RSC.

In an example, as shown in FIG. 15 , the apparatus 1400 further includes: a second request sending module 1430, configured to send a second session establishment request to the second core network device, the second session establishment request using In the request to establish the PDU session, and the second session establishment request includes the session parameter information.

In an example, as shown in FIG. 15 , the apparatus 1400 further includes: a first response sending module 1440, configured to send a first session establishment response to the relay device, where the first session establishment response is used to indicate The PDU session establishment is completed.

Please refer to FIG. 16 , which shows a block diagram of an apparatus for establishing a session provided by an embodiment of the present application. The apparatus has the function of implementing the above-mentioned method example on the device side of the second core network, and the function may be implemented by hardware or by executing corresponding software in hardware. The apparatus may be the above-mentioned second core network device, or may be provided in the second core network device. As shown in FIG. 16 , the apparatus 1600 may include: a second request receiving module 1610 and a session establishing module 1620 .

The second request receiving module 1610 is configured to receive a second session establishment request from a first core network device, where the second core network device is selected by the first core network device based on the first RSC.

The session establishment module 1620 is configured to establish a PDU session between the relay device and the DN according to the second session establishment request.

In an example, the second session establishment request includes the first RSC; the session establishment module 1620 is configured to: determine session parameter information corresponding to the first RSC according to the third configuration information, The third configuration information includes the correspondence between the RSC and the session parameter information; the PDU session is established according to the session parameter information.

In an example, the second session establishment request includes the first RSC; the session establishment module 1620 is configured to: determine session parameter information according to the first information field in the first RSC; The session parameter information is used to establish the PDU session.

In an example, the second session establishment request includes session parameter information corresponding to the first RSC; the session establishment module 1620 is configured to: establish the PDU session according to the session parameter information.

It should be noted that, when the device provided in the above embodiment realizes its functions, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be allocated to different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

Please refer to FIG. 17 , which shows a schematic structural diagram of a relay device 170 provided by an embodiment of the present application. For example, the relay device can be used to execute the above-mentioned method for establishing a session on the relay device side. Specifically, the relay device 170 may include: a processor 171, and a transceiver 172 connected to the processor 171; wherein:

The processor 171 includes one or more processing cores, and the processor 171 executes various functional applications and information processing by running software programs and modules.

Transceiver 172 includes a receiver and a transmitter. Optionally, transceiver 172 is a communication chip.

In one example, the relay device 170 further includes: a memory and a bus. The memory is connected to the processor through a bus. The memory can be used to store a computer program, and the processor is used to execute the computer program, so as to implement each step performed by the relay device in the above method embodiments.

In addition, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: RAM (Random-Access Memory, random access memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory, Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory, Electrically Erasable Programmable Read-Only Memory) ), flash memory or other solid-state storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc, high-density digital video disc) or other optical storage, tape cassettes, tapes, disk storage or other magnetic storage devices. in:

The transceiver 172 is configured to send a first session establishment request to a first core network device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session establishment request is The session establishment request includes the first RSC.

In an example, the transceiver 172 is further configured to receive a first session establishment response from the first core network device, where the first session establishment response is used to indicate that the PDU session establishment is completed.

Please refer to FIG. 18 , which shows a schematic structural diagram of a core network device 180 provided by an embodiment of the present application. For example, the core network device can be used to execute the above-mentioned first core network device-side session establishment method; or, used to execute The above-mentioned method for establishing a session on the device side of the first core network. Specifically, the core network device 180 may include: a processor 181, and a transceiver 182 connected to the processor 181; wherein:

The processor 181 includes one or more processing cores, and the processor 181 executes various functional applications and information processing by running software programs and modules.

Transceiver 182 includes a receiver and a transmitter. Optionally, transceiver 182 is a communication chip.

In one example, the core network device 180 further includes: a memory and a bus. The memory is connected to the processor through a bus. The memory can be used to store a computer program, and the processor is used to execute the computer program, so as to implement various steps performed by the first core network device or the second core network device in the above method embodiments.

For the case where the core network device 180 is configured to execute the first core network device-side session establishment method:

The transceiver 182 is configured to receive a first session establishment request from a relay device, where the first session establishment request is used to request the establishment of a PDU session between the relay device and the DN, and the first session establishment request is The session establishment request includes the first RSC.

In an example, the processor 181 is configured to select a second core network device according to the first RSC, where the second core network device is configured to establish the PDU session.

In an example, the processor 181 is configured to select a second core network device corresponding to the first RSC according to first configuration information, where the first configuration information includes the relationship between the RSC and the second core network device corresponding relationship.

In an example, the transceiver 182 is configured to send the first RSC to a third core network device; the transceiver 182 is configured to receive device information from the third core network device, the The device information is used to indicate the second core network device corresponding to the first RSC.

In an example, the transceiver 182 is configured to send the first RSC to a third core network device; the transceiver 182 is configured to receive the communication with the third core network device from the third core network device. Session parameter information corresponding to an RSC, the session parameter information is used to establish the PDU session; the processor 181 is configured to select the second core network device corresponding to the session parameter information according to the third configuration information, The third configuration information includes the correspondence between the session parameter information and the second core network device.

In an example, the processor 181 is configured to: determine session parameter information corresponding to the first RSC according to the second configuration information, where the session parameter information is used to establish the PDU session, the second The configuration information includes the correspondence between the RSC and the session parameter information; according to the third configuration information, a second core network device corresponding to the session parameter information is selected, and the third configuration information includes the session parameter information and the second core network device Correspondence between devices.

In an example, the processor 181 is configured to: determine session parameter information according to the first information field in the first RSC, where the session parameter information is used to establish the PDU session; according to the third configuration information , selecting the second core network device corresponding to the session parameter information, and the third configuration information includes the correspondence between the session parameter information and the second core network device.

In an example, the transceiver 182 is configured to send a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of the PDU session, and the second session The establishment request includes the first RSC.

In an example, the transceiver 182 is configured to send a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of the PDU session, and the second session The establishment request includes the session parameter information.

In an example, the transceiver 182 is configured to send a first session establishment response to the relay device, where the first session establishment response is used to indicate that the PDU session establishment is completed.

For the case where the core network device 180 is used to execute the second core network device-side session establishment method:

The transceiver 182 is configured to receive a second session establishment request from a first core network device, where the second core network device is selected by the first core network device based on the first RSC;

The processor 181 is configured to establish a PDU session between the relay device and the DN according to the second session establishment request.

In an example, the second session establishment request includes the first RSC; the processor 181 is configured to: determine session parameter information corresponding to the first RSC according to the third configuration information, the The third configuration information includes the correspondence between the RSC and the session parameter information; the PDU session is established according to the session parameter information.

In an example, the second session establishment request includes the first RSC; the processor 181 is configured to: determine session parameter information according to the first information field in the first RSC; Session parameter information to establish the PDU session.

In an example, the second session establishment request includes session parameter information corresponding to the first RSC; the processor 181 is configured to: establish the PDU session according to the session parameter information.

In another aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a core network device, so as to implement the above-mentioned second core A method for establishing a session on the network device side.

Those skilled in the art should realize that, in one or more of the above examples, the functions described in the embodiments of the present application may be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

The above are only exemplary embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the protection of the present application. within the range.

Claims

A session establishment method, characterized in that it is applied to a relay device, the method comprising:

Send a first session establishment request to the first core network device, where the first session establishment request is used to request the establishment of a protocol data unit PDU session between the relay device and the data network DN, and the first session establishment request It includes the first relay service service code RSC.
The method according to claim 1, wherein the first RSC is used to select a second core network device, and the second core network device is used to establish the PDU session.
The method according to claim 1 or 2, wherein the method further comprises:

A first session establishment response from the first core network device is received, where the first session establishment response is used to indicate that the PDU session establishment is completed.
The method according to claim 3, wherein the first session establishment response includes the first RSC.
A session establishment method, characterized in that, applied to a first core network device, the method comprising:

Receive a first session establishment request from a relay device, the first session establishment request is used to request the establishment of a protocol data unit PDU session between the relay device and the data network DN, and the first session establishment request It includes the first relay service service code RSC.
The method according to claim 5, wherein after the receiving the first session request from the relay device, the method further comprises:

A second core network device is selected according to the first RSC, and the second core network device is used to establish the PDU session.
The method according to claim 6, wherein the selecting a second core network device according to the first RSC comprises:

According to the first configuration information, the second core network device corresponding to the first RSC is selected, and the first configuration information includes the correspondence between the RSC and the second core network device.
The method according to claim 6, wherein the selecting a second core network device according to the first RSC comprises:

sending the first RSC to the third core network device;

Receive device information from the third core network device, where the device information is used to indicate the second core network device corresponding to the first RSC.
The method according to claim 8, wherein the device information includes at least one of the following: address information of the second core network device, and identification information of the second core network device.
The method according to claim 6, wherein the selecting a second core network device according to the first RSC comprises:

sending the first RSC to the third core network device;

receiving session parameter information corresponding to the first RSC from the third core network device, where the session parameter information is used to establish the PDU session;

According to the third configuration information, the second core network device corresponding to the session parameter information is selected, and the third configuration information includes the correspondence between the session parameter information and the second core network device.
The method according to claim 6, wherein the selecting a second core network device according to the first RSC comprises:

determining, according to the second configuration information, session parameter information corresponding to the first RSC, where the session parameter information is used to establish the PDU session, and the second configuration information includes the correspondence between the RSC and the session parameter information;

According to the third configuration information, the second core network device corresponding to the session parameter information is selected, and the third configuration information includes the correspondence between the session parameter information and the second core network device.
The method according to claim 6, wherein the selecting a second core network device according to the first RSC comprises:

determining session parameter information according to the first information field in the first RSC, where the session parameter information is used to establish the PDU session;

According to the third configuration information, the second core network device corresponding to the session parameter information is selected, and the third configuration information includes the correspondence between the session parameter information and the second core network device.
The method according to any one of claims 10 to 12, wherein the session parameter information includes at least one of the following: slice information, data network name DNN information, session and service continuous SSC mode information, session type information.
The method according to any one of claims 8 to 10, wherein the third core network device comprises at least one of the following devices: a warehousing function NRF entity and a policy control function PCF entity of a network function entity.
The method according to any one of claims 7 to 9, wherein the method further comprises:

Sending a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of the PDU session, and the second session establishment request includes the first RSC.
The method according to any one of claims 10 to 13, wherein the method further comprises:

Sending a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of the PDU session, and the second session establishment request includes the session parameter information.
The method according to any one of claims 5 to 16, wherein the method further comprises:

A first session establishment response is sent to the relay device, where the first session establishment response is used to indicate that the PDU session establishment is completed.
The method of claim 17, wherein the first session establishment response includes the first RSC.
A session establishment method, characterized in that it is applied to a second core network device, the method comprising:

receiving a second session establishment request from a first core network device, where the second core network device is selected by the first core network device based on the first relay service service code RSC;

According to the second session establishment request, a protocol data unit PDU session between the relay device and the data network DN is established.
The method according to claim 19, wherein the second session establishment request includes the first RSC;

The establishing the PDU session between the relay device and the DN according to the second session establishment request includes:

determining session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes a correspondence between the RSC and the session parameter information;

According to the session parameter information, the PDU session is established.
The method according to claim 19, wherein the second session establishment request includes the first RSC;

The establishing the PDU session between the relay device and the DN according to the second session establishment request includes:

determining session parameter information according to the first information field in the first RSC;

According to the session parameter information, the PDU session is established.
The method according to claim 19, wherein the second session establishment request includes session parameter information corresponding to the first RSC;

The establishing the PDU session between the relay device and the DN according to the second session establishment request includes:

According to the session parameter information, the PDU session is established.
The method according to any one of claims 20 to 22, wherein the session parameter information includes at least one of the following: slice information, data network name DNN information, session and service continuous SSC mode information, and session type information.
A session establishment apparatus, characterized in that it is set in a relay device, and the apparatus includes:

a first request sending module, configured to send a first session establishment request to a first core network device, where the first session establishment request is used to request to establish a protocol data unit PDU session between the relay device and the data network DN, And the first session establishment request includes the first relay service service code RSC.
The apparatus according to claim 24, wherein the first RSC is used to select a second core network device, and the second core network device is used to establish the PDU session.
The device according to claim 24 or 25, wherein the device further comprises:

A first response receiving module, configured to receive a first session establishment response from the first core network device, where the first session establishment response is used to indicate that the PDU session establishment is completed.
The apparatus of claim 26, wherein the first session establishment response includes the first RSC.
A session establishment apparatus, characterized in that it is set in a first core network device, and the apparatus includes:

a first request receiving module, configured to receive a first session establishment request from a relay device, where the first session establishment request is used to request the establishment of a protocol data unit PDU session between the relay device and the data network DN, And the first session establishment request includes the first relay service service code RSC.
The apparatus of claim 28, wherein the apparatus further comprises:

A device selection module, configured to select a second core network device according to the first RSC, where the second core network device is configured to establish the PDU session.
The apparatus according to claim 29, wherein the device selection module is configured to:

According to the first configuration information, the second core network device corresponding to the first RSC is selected, and the first configuration information includes the correspondence between the RSC and the second core network device.
The apparatus according to claim 29, wherein the device selection module is configured to:

sending the first RSC to the third core network device;

Receive device information from the third core network device, where the device information is used to indicate the second core network device corresponding to the first RSC.
The apparatus according to claim 31, wherein the device information includes at least one of the following: address information of the second core network device, and identification information of the second core network device.
The apparatus according to claim 29, wherein the device selection module is configured to:

sending the first RSC to the third core network device;

receiving session parameter information corresponding to the first RSC from the third core network device, where the session parameter information is used to establish the PDU session;

According to the third configuration information, the second core network device corresponding to the session parameter information is selected, and the third configuration information includes the correspondence between the session parameter information and the second core network device.
The apparatus according to claim 29, wherein the device selection module is configured to:

determining, according to the second configuration information, session parameter information corresponding to the first RSC, where the session parameter information is used to establish the PDU session, and the second configuration information includes the correspondence between the RSC and the session parameter information;

According to the third configuration information, the second core network device corresponding to the session parameter information is selected, and the third configuration information includes the correspondence between the session parameter information and the second core network device.
The apparatus according to claim 29, wherein the device selection module is configured to:

determining session parameter information according to the first information field in the first RSC, where the session parameter information is used to establish the PDU session;

According to the third configuration information, the second core network device corresponding to the session parameter information is selected, and the third configuration information includes the correspondence between the session parameter information and the second core network device.
The apparatus according to any one of claims 33 to 35, wherein the session parameter information includes at least one of the following: slice information, data network name DNN information, session and service continuous SSC mode information, and session type information.
The apparatus according to any one of claims 31 to 33, wherein the third core network device includes at least one of the following devices: a warehousing function NRF entity of a network function entity, and a policy control function PCF entity.
The device according to any one of claims 30 to 32, wherein the device further comprises:

A second request sending module, configured to send a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of the PDU session, and the second session establishment request includes the Describe the first RSC.
The device according to any one of claims 33 to 36, wherein the device further comprises:

A second request sending module, configured to send a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of the PDU session, and the second session establishment request includes the the session parameter information.
The device according to any one of claims 29 to 39, wherein the device further comprises:

A first response sending module, configured to send a first session establishment response to the relay device, where the first session establishment response is used to indicate that the PDU session establishment is completed.
The apparatus of claim 40, wherein the first session establishment response includes the first RSC.
A session establishment apparatus, characterized in that it is set in a second core network device, and the apparatus includes:

a second request receiving module, configured to receive a second session establishment request from a first core network device, where the second core network device is selected by the first core network device based on the first relay service service code RSC;

The session establishment module is configured to establish a protocol data unit PDU session between the relay device and the data network DN according to the second session establishment request.
The apparatus according to claim 42, wherein the second session establishment request includes the first RSC; and the session establishment module is configured to:

determining session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes a correspondence between the RSC and the session parameter information;

According to the session parameter information, the PDU session is established.
The apparatus according to claim 42, wherein the second session establishment request includes the first RSC; and the session establishment module is configured to:

determining session parameter information according to the first information field in the first RSC;

According to the session parameter information, the PDU session is established.
The apparatus according to claim 42, wherein the second session establishment request includes session parameter information corresponding to the first RSC; the session establishment module is configured to:

According to the session parameter information, the PDU session is established.
The apparatus according to any one of claims 43 to 45, wherein the session parameter information includes at least one of the following: slice information, data network name DNN information, session and service continuous SSC mode information, and session type information.
A relay device, characterized in that the relay device comprises: a processor, and a transceiver connected to the processor; wherein:

the transceiver, configured to send a first session establishment request to the first core network device, where the first session establishment request is used to request the establishment of a protocol data unit PDU session between the relay device and the data network DN, and The first session establishment request includes the first relay service service code RSC.
A core network device, characterized in that the core network device comprises: a processor, and a transceiver connected to the processor; wherein:

the transceiver, configured to receive a first session establishment request from a relay device, the first session establishment request being used to request establishment of a protocol data unit PDU session between the relay device and a data network DN, and The first session establishment request includes the first relay service service code RSC.
A core network device, characterized in that the core network device comprises: a processor, and a transceiver connected to the processor; wherein:

the transceiver, configured to receive a second session establishment request from a first core network device, where the second core network device is selected by the first core network device based on the first relay service service code RSC;

The processor is configured to establish a protocol data unit PDU session between the relay device and the data network DN according to the second session establishment request.
A computer-readable storage medium, characterized in that, a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a relay device, so as to realize any one of claims 1 to 4. the session establishment method.
A computer-readable storage medium, characterized in that, a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a core network device, so as to realize any one of claims 5 to 18. the session establishment method.
A computer-readable storage medium, characterized in that, a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a core network device, so as to realize any one of claims 14 to 26. the session establishment method.