CN115553045B

CN115553045B - Session establishment method, device, equipment and storage medium

Info

Publication number: CN115553045B
Application number: CN202080100873.3A
Authority: CN
Inventors: 刘建华; 杨皓睿
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2025-02-14
Anticipated expiration: 2040-07-31
Also published as: WO2022021355A1; CN115553045A

Abstract

The application discloses a session establishment method, a session establishment device, session establishment equipment and a session establishment storage medium, and belongs to the technical field of communication. The method comprises the steps that the relay equipment sends a first session establishment request to first core network equipment, the first session establishment request is used for requesting to establish a PDU session between the relay equipment and a DN, and the first session establishment request comprises a first RSC. According to the technical scheme provided by the embodiment of the application, the session establishment request is sent to the core network equipment through the relay equipment, the RSC corresponding to the service attribute is carried in the session establishment request, and because the RSC is represented as a service code, the RSC has the characteristics of difficult cracking and leakage, and compared with the condition that the service attribute is carried in the session establishment request directly to possibly cause the service attribute leakage to influence the safety of the system, the embodiment of the application ensures the privacy protection aiming at the service attribute under the condition that the clear service attribute of the core network is ensured, and the safety of the system is improved.

Description

Session establishment method, device, equipment and storage medium

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a method, a device, equipment and a storage medium for establishing a session.

Background

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

Relay communication refers to UE (User Equipment) -to-Network (terminal Equipment connected to a Network) relayed based on an IP (Internet Protocol ) layer. That is, a Remote UE (Remote device) accesses the network through a Relay UE (Relay device). The Relay UE takes over the function of the 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, where the network includes an access network device and a core network device, and the Relay UE sends the data from the Remote UE to the access network device and may further be 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 Relay UE sends the data from the access network device to the Remote UE.

However, the Relay UE needs to establish an appropriate PDU (Protocol Data Unit ) session in order to transfer data between the Remote UE and the network. How to establish a PDU session corresponding to a service type for different service types that the Remote UE needs to develop needs further discussion and study.

Disclosure of Invention

The embodiment of the application provides a session establishment method, a session establishment device, session establishment equipment and a storage medium. The technical scheme is as follows:

In one aspect, an embodiment of the present application provides a session establishment method, applied to a relay device, where the method includes:

a first session establishment request is sent to a first core Network device, where the first session establishment request is used to request establishment of a PDU session between the relay device and a DN (Date Network), and the first session establishment request includes a first RSC (RELAY SERVICE Code).

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

A first session establishment request is received from a relay device, the first session establishment request being for requesting establishment of a PDU session between the relay device and a DN, and the first session establishment request including a first RSC.

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

Receiving a second session establishment request from a first core network device, the second core network device being selected by the first core network device based on a first RSC;

and establishing a PDU session between the relay equipment and the DN according to the second session establishment request.

In still another aspect, an embodiment of the present application provides a session establishment apparatus, provided in a relay device, including:

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 establishment of a PDU session between the relay device and the DN, and the first session establishment request includes a first RSC.

In still another aspect, an embodiment of the present application provides a session establishment apparatus, provided in a first core network device, where 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 establishment of a PDU session between the relay device and a DN, and the first session establishment request includes a first RSC.

In still another aspect, an embodiment of the present application provides a session establishment apparatus, provided in a second core network device, where 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 a first RSC;

And the session establishment module is used for establishing the PDU session between the relay equipment and the DN according to the second session establishment request.

In yet 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, where:

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 establishment of a PDU session between the relay device and the DN, and the first session establishment request includes a first RSC.

In yet 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, where:

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 establishment of a PDU session between the relay device and a DN, and the first session establishment request includes a first RSC.

The transceiver 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 a 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 still another aspect, an embodiment of the present application provides a computer readable storage medium having stored therein a computer program for execution by a processor of a relay device to implement a relay device side session establishment method as described above.

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

In yet another aspect, an embodiment of the present application provides a computer readable storage medium, where a computer program is stored, where the computer program is configured to be executed by a processor of a core network device to implement a second core network device side session establishment method as described above.

In yet 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 is running on a relay device, the chip is configured to implement a method for establishing a session on a relay device side as described above.

In yet 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 is running on a core network device, the chip is configured to implement a method for establishing a session on a first core network device side as described above.

In yet 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 is running on a core network device, the chip is configured to implement a second core network device side session establishment method as described above.

In yet another aspect, an embodiment of the present application provides a computer program product, which when executed on a relay device, causes the computer to perform the above-mentioned relay device side session establishment method.

In yet another aspect, an embodiment of the present application provides a computer program product, which when executed on a core network device, causes the computer to perform the above-mentioned first core network device side session establishment method.

In yet another aspect, an embodiment of the present application provides a computer program product, which when executed on a core network device, causes the computer to perform the second core network device side session establishment method described above.

The technical scheme provided by the embodiment of the application can have the following beneficial effects:

The relay equipment sends the session establishment request to the core network equipment, the session establishment request carries the RSC corresponding to the service attribute, and because the RSC is represented as a service code, the RSC has the characteristics of difficult cracking and leakage, compared with the condition that the service attribute is carried in the session establishment request directly to possibly cause the leakage of the service attribute to influence the safety of the system, the embodiment of the application ensures the privacy protection aiming at the service attribute under the condition that the core network definitely confirms the service attribute, and improves the safety of the system.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a system architecture provided by one embodiment of the present application;

FIG. 2 is a schematic diagram of a system architecture of an EPS system according to an embodiment of the present application;

Fig. 3 is a schematic diagram of a system architecture of a 5GS system according to an embodiment of the present application;

Fig. 4 is a schematic diagram of a system architecture of a 5GS system according to another embodiment of the present application;

fig. 5 is a schematic diagram of a relay communication system according to an embodiment of the present application;

FIG. 6 is a flow chart of a remote device accessing a network and obtaining IP services according to one embodiment of the present application;

fig. 7 is a flow chart of a relay device establishing a PDU session according to one embodiment of the present application;

FIG. 8 is a flow chart of a session establishment method provided by one embodiment of the present application;

fig. 9 is a flowchart of a session establishment method according to another embodiment of the present application;

fig. 10 is a flowchart of a session establishment method according to still another embodiment of the present application;

fig. 11 is a flowchart of a session establishment method according to still another embodiment of the present application;

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

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

fig. 14 is a block diagram of a session establishment apparatus provided in yet another embodiment of the present application;

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

fig. 16 is a block diagram of a session establishment apparatus provided by a further embodiment of the present application;

fig. 17 is a block diagram of a relay apparatus according to an embodiment of the present application;

fig. 18 is a block diagram of a core network device according to an embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided by the embodiments of the present application is applicable to similar technical problems.

The technical scheme provided by the embodiment of the application can be applied to various communication systems, such as a GSM (Global System of Mobile Communication, global system for mobile communication) system, a CDMA (Code Division Multiple Access ) system, a ECDMA (Wideband Code Division Multiple Access, wideband code division multiple access) system, a GPRS (GENERAL PACKET Radio Service), an LTE (Long Term Evolution ) system, an FDD (Frequency Division Duplex, LTE frequency division duplex) system, a TDD (Time Division Duplex, LTE time division duplex) system, a UMTS (Universal Mobile Telecommunication System, a universal mobile communication system), a WiMAX (Worldwide Interoperability for Microwave Access, global interconnection microwave access) communication system, a 5GS or New air interface (New Radio, NR) system, or subsequent other evolution systems and the like.

Fig. 1 is a schematic diagram of a system architecture of a communication system according to an embodiment of the 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, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user equipment. Alternatively, the terminal device may also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol ) phone, a WLL (Wireless Local Loop, wireless local loop) station, a PDA (Personal digital assistant) DIGITAL ASSISTANT, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in 5GS or a terminal device in a future evolved PLMN (Public Land Mobile Network ), etc., which the embodiment of the present application is not limited to.

The access network device 20 is a device deployed in an access network to provide wireless communication functionality 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 employing different Radio access technologies, the names of devices with access network device functions may be different, for example, in a 5G (5 th-Generation, fifth Generation mobile communication) NR (New Radio) system, referred to as gNodeB or gNB, and in an EPS (Evolved PACKET SYSTEM ) system, the access network device may be referred to as an eNodeB (Evolved NodeB). As communication technology evolves, the name "access network device" may change. For convenience of description, in the embodiment of the present application, the above-mentioned apparatus for providing a wireless communication function for a terminal device is collectively referred to as an access network device.

The core network device 30 is a device that can provide session management, mobility relation, policy management, security authentication, and other functions for the terminal device. In the 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 the terminal device, and the second core network device is responsible for session management of the terminal device. Illustratively, in the 5GS system, the first Core network may be implemented as an AMF (Core ACCESS AND Mobility Management Function, core network access and Mobility management function), the second Core network device may be implemented as an SMF (Session Management Function ), and in the EPS system, the first Core device may be implemented as an MME (Mobility MANAGEMENT ENTITY ), and the second Core network device may be implemented as an SGW (SERVING GATEWAY, serving network element).

In one example, as shown in fig. 1, the terminal devices include a Remote (Remote) terminal device 12 and a Relay (Relay) terminal device 14. Relay device 14 may communicate data with remote device 12 to establish a communication connection between remote device 12 and access network device 20 and core network device 30. Relay device 14 may illustratively send data from remote device 12 to access network device 20 and may further be sent by access network device 20 to core network device 30, or access network device 20 may send data from core network device 30 to relay device 14 and then relay device 14 may send data from access network device 20 to remote device 12.

Fig. 2 shows a schematic diagram of a system architecture of an EPS system according to an embodiment of the application. As shown in fig. 2, the system architecture may include the following network entities:

1. EUTRAN, a network composed of a plurality of eNodeBs, realizing the functions of wireless physical layer, resource scheduling and wireless resource management, wireless access control and mobility management. The enodebs may be connected by an X2 interface and may be used to transmit data during an X2 based handover. eNodeB is connected with SGW through user interface SI-U, uses GTP-U (GENERAL PACKET Radio SYSTEM GENERAL Tunneling Protocol User Plane, general packet Radio system tunnel protocol user plane) to transfer user data, is connected with MME through control interface SI-E, and adopts SI-AP protocol to realize functions of Radio access bearer control and the like.

2. MME is mainly responsible for all control plane functions of user, namely session management, including NAS (Non-Access-Stratum) signaling and security, management of tracking area list (TRACKING AREA LIST), selection of P-GW (PACKET DATE Network Gateway) and SGW, and the like.

3. SGW is mainly responsible for data transmission, forwarding, and routing handover of user equipment, and serves as a local mobility anchor point when the user equipment switches between enodebs (each is set for each user, only one SGW serves it at each moment).

4. The P-GW is used as an anchor point of PDN (PACKET DATE Network) connection and is responsible for IP address allocation of the user equipment, data message filtering of the user equipment, rate control, generation of charging information and the like.

5. SGSN (Serving GPRSupporting Node, serving GPRS support node) is an access node for 2G access network GERAN (GSM/EDGE Radio Access Network ), 3G access network UTRAN (Universal Terrestrial Radio Access Network, universal terrestrial radio access) and EPS core network EPC, responsible for establishment of bearers and forwarding of data from GERAN, UTRAN to EPC.

6. HSS (Home Subscriber Server ) stores subscription data of mobile subscribers.

7. PCRF (Policy AND CHARGING Rules Function), responsible for charging management and Policy Control, including PCC (Policy AND CHARGING Control) Rules, qoS (Quality of Service) Rules.

Fig. 3 is a schematic diagram of a system architecture of a 5GS system according to an embodiment of the present application. As shown in fig. 3, the system architecture 200 may include a UE, a RAN (Radio Access Network ), a Core (Core network), and a DN. Wherein UE, RAN, core is a main component constituting the architecture, and logically they can be divided into two parts, namely a user plane and a control plane, the control plane is responsible for management of the mobile network, and the user plane is responsible for 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.

The UE is an entrance for interaction between the mobile user and the network, can provide basic computing capacity and storage capacity, displays a service window for the user, and accepts user operation input. The UE may use the next generation air interface technology to establish a signal connection and a data connection with the RAN, so as to transmit control signals and service data to the mobile network.

RAN is similar to base station in traditional network, and is deployed near UE to provide network access function for authorized user in specific area, and can use transmission tunnel with different quality to transmit user data according to user level, service requirement, etc. The RAN can manage own resources, reasonably utilize, provide access service for the UE according to the requirement, and forward control signals and user data between the UE and a core network.

Core is responsible for maintaining subscription data of the mobile network, managing network elements of the mobile network, and providing session management, mobility management, policy management, security authentication and other functions for the UE. Providing network access authentication for the UE when the UE attaches, allocating network resources for the UE when the UE has a service request, updating the network resources for the UE when the UE moves, providing a quick recovery mechanism for the UE when the UE is idle, releasing the network resources for the UE when the UE is detached, and providing a data routing function for the UE when the UE has service data, such as forwarding uplink data to DN, or receiving downlink data of the UE from DN, forwarding to RAN, and sending to the UE.

DN is a data network providing business service for users, and the client is generally located in the UE, and the server is located in the data network. The data network may be a private network, such as a local area network, or an external network not under the control of an operator, such as the Internet, or a proprietary network co-deployed by an operator, such as for configuring IMS (IP Multimedia Core Network Subsystem, IP multimedia network subsystem) services.

Fig. 4 is a detailed architecture determined based on fig. 3, in which the core network user plane includes UPF (User Plane Function ), the core network control plane includes AUSF (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 repository function), UDM (Unified DATA MANAGEMENT ), PCF (Policy Control Function, policy control function), AF (Application Function ). The functions of these functional entities are as follows:

UPF, executing user data packet forwarding according to SMF routing rules;

AUSF performing security authentication of the UE;

AMF, UE access management and mobility management;

SMF, UE session management;

NSSF selecting a network slice for the UE;

NEF, opening network functions to a third party in a northbound API interface mode;

NRF, providing storage function and selection function of network function entity information for other network elements;

UDM, user signing context management;

PCF, user strategy management;

AF, user application management.

In the architecture shown in fig. 4, the N1 interface is a reference point between the UE and the AMF, the N2 interface is a reference point between the RAN and the AMF for sending NAS messages, the N3 interface is a reference point between the RAN and the UPF for transmitting data of the user plane, etc., the N4 interface is a reference point between the SMF and the UPF for transmitting information such as tunnel identification information, data buffer indication information, and downlink data notification messages of the N3 connection, and the N6 interface is a reference point between the UPF and the DN for transmitting data of the user plane, etc.

It should be noted that the names of interfaces between the network elements in fig. 3 and fig. 4 are only an example, and the names of interfaces in the specific implementation may be other names, which is not limited in particular by the embodiment of the present application. The names of the individual network elements (e.g., SMF, AF, UPF, etc.) included in fig. 3 and 4 are also merely examples, and the functions of the network elements themselves are not limited. In 5GS and other networks in the future, the above-mentioned network elements may also be named as other names, which are not particularly limited in the embodiment of the present application. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, possibly use other names, etc., which are described in detail herein, and will not be described in detail herein. Furthermore, it should be understood that the names of the transmitted messages (or signaling) between the various network elements described above are also merely an example, and do not constitute any limitation on the functionality of the messages themselves.

Referring to fig. 5, a schematic diagram of a relay communication system according to an embodiment of the present application is shown. The relay communication system shown in fig. 5 mainly comprises a radio subsystem part, an EPC (Evolved Packet Core, evolved packet core network) part and a short-distance communication service part.

The radio subsystem part, EUTRAN, comprises one or more enodebs, which may also be referred to as access network equipment part in the EPS system.

The EPC portion includes HSS, MME, SGW, PGW and the like described above.

The proximity communication service part, i.e., proSe architecture part, includes PF (ProSe Function), PAS (ProSe Application Server, proximity communication application server), relay device (Relay UE), remote device (Remote UE). The system comprises a PF, PAS, relay UE and Relay UE, wherein the PF is used for authorizing the near-field communication of the terminal equipment, providing discovery assistance among the terminal equipment and the like, the PAS is used for providing specific near-field communication service support, the Relay UE is used for providing Relay access support for the Relay UE, and the Relay UE is used for accessing a network through the Relay UE to obtain IP (internet Protocol) service. In one example, as shown in fig. 5, PA (ProSe Application, short-range communication service) is installed in both the Relay UE and the Remote UE.

Based on the above-described relay communication system architecture shown in fig. 5, fig. 6 shows a flowchart in which a remote device accesses a network through a relay device and obtains an IP service. As shown in fig. 6, the process of accessing the network by the remote device includes the following steps:

In step 610, the relay device attaches to the network and/or the relay device requests establishment of a PDN connection. The relay device may request establishment of a PDN (Public Data Network ) connection while attached to the network.

In step 620, the remote device discovers the relay device. In one example, the remote device uses APNs (Access Point Name, access point names) supported by the relay device as reference information in discovering the relay device.

In step 630, the remote device requests a relay device to establish one-to-one communication. The remote device may request to establish One-to-One (One-2-One) communication from the relay device via the PC5 interface, optionally with an APN carried in the request sent by the remote device. Optionally, step 632 may also be performed, either simultaneously with step 630 or after step 630 is performed, where the relay device requests to establish a new PDN connection.

In step 640, the relay device assigns an IP address to the remote device. The content of the IP address is not limited in the embodiment of the present application, and optionally, the IP address is a private IPv4 address or an IPv6 prefix.

In step 650, the relay device sends a remote terminal report to the MME. Optionally, the Remote terminal report carries an Identifier (such as a Remote UE ID), an IP address, etc. of the Remote device.

In step 660, the mme sends a remote terminal report to the PGW. After receiving the report of the remote terminal of the relay device, the MME may send the report of the remote terminal to the PGW, so that the PGW locally stores information of the remote device, and the subsequent PGW may use the information to gate uplink and downlink data of the remote device, i.e. whether to allow transmission of the uplink and downlink data. Optionally, after step 660, the remote device sends upstream IP data or receives downstream IP data, the IP data passing through the relay device and the IP data being carried within the PDN connection established by the relay device for the remote device for relaying.

As is clear from the above step 630, the relay device needs to use the appropriate PDU session in order to transmit the relay data of the remote device, and which PDU session to use for transmitting the relay data is determined by the relay device. Typically, during the establishment of a PDU session, the relay device determines the parameters required to establish the PDU session according to URSP (UE path selection policy) of the network configuration. Referring to fig. 7, a flow chart of a relay device according to an embodiment of the present application for establishing a PDU session is shown. As shown in fig. 7, the process includes the following steps:

In step 701, the relay device sends a session establishment request message to the AMF. After registering with the AMF entity, the Relay device (Relay UE) sends a session establishment request message to the AMF entity, where the session establishment request message is used to request establishment of a PDU session. In one example, the session request setup message includes at least one of S-NSSAI (session management-network slice selection assistance information ) corresponding to the PDU session, DNN (Date Network Name, data network name) corresponding to the PDU session, PDU session identification, request type (request type), N1SM information (N1 session management information), PDU type.

In step 702, the AMF selects SMF. After receiving the session establishment request message, the AMF entity may select an SMF entity according to a certain rule.

The amf sends an SM request message to the SMF, step 703. The AMF entity may send an SM (Session Management ) request message to the SMF entity after selecting the SMF entity. Optionally, the SM request message includes at least one of a subscriber permanent identity (subscriber PERMANENT ID), DNN, S-NSSAI, PDU session identity, N1SM information, subscriber location information (user location information), access technology type.

In step 704, the smf sends a subscription data request message to the UDM. When the SMF entity does not acquire 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 a subscription identification (subscriber PERMANENT ID), a DNN.

In 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. The SMF may then perform an authorization check on the subscription, and in case the SMF entity confirms that the authorization check fails, send NAS (Non Access Stratum, non-access stratum) signaling to the Relay UE, where the NAS signaling is used to indicate that the session establishment request of the Relay UE is denied.

In 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 establishment of the PDU session, the SMF entity needs to select the UPF entity according to a certain rule, and then the SMF entity triggers the authorization/authentication of establishment of the PDU session to complete the authorization/authentication of establishment of the PDU session.

In step 707, the smf selects the PCF. In the case where dynamic PCC (Policy Control AND CHARGING) deployment is required, the SMF entity needs to select the PCF entity according to a certain rule.

At step 708, the smf obtains PCC rules. The SMF entity sends a PDU-CAN (Controller Area Network ) session establishment request to the selected PCF entity, thereby acquiring the PCC rule corresponding to the PDU session.

In step 709, the smf selects UPF. If the SMF entity does not select a UPF in step 706, then the SMF entity may select a UPF entity.

Step 710, the smf initiates a PDU-CAN session establishment procedure. Under the condition that dynamic PCC is deployed and the PDU-CAN session establishment process is not executed yet, the SMF entity CAN initiate the PDU-CAN session establishment process to the PCF entity, and then the SMF entity acquires the default PCC rule from the PCF entity. In the case that 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 a PDU-CAN session modification procedure, and the SMF entity sends the IP address of the distributed Relay UE to the PCF entity.

Step 711, the smf initiates an N4 session setup/modification procedure to the UPF. And if the request type is the initial request type, the SMF entity initiates an N4 session establishment process to the UPF entity, otherwise, the SMF entity initiates an N4 session modification process to the UPF entity. Optionally, the SMF entity may also provide packet detection, reporting rules, CN tunnel info (tunnel info), etc. to the UPF entity.

The upf sends an N4 session setup/modification response message to the SMF, step 712. The UPF entity may send an N4 session setup/modification response message to the SMF entity after receiving the initiation request of the SMF entity.

In step 713, the smf sends an SM response message to the AMF. In one example, at least one of a cause value (cause), N2 reference point session management information (N2 SM information), N1SM information, and the like is included in the SM response message.

The amf sends an N2PDU session request message to the RAN, step 714. In one example, the N2PDU session request message includes at least one of N2SM information, NAS message, and the like.

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

In step 716, the relay device sends an RRC connection reconfiguration response message to the RAN. After receiving the RRC connection reconfiguration message of 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 setup response message to the AMF. In one example, the N2PDU session response message includes at least one of a PDU session identification, a cause value, and an N2SM message.

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

The smf sends an N4 session setup/modification request message to the UPF, step 719. In case of N4 session establishment, the SMF entity may send AN N4 session establishment message to the UPF entity, and in case of N4 session establishment, the SMF entity may send AN N4 session modification message to the UPF entity to update Access Network (AN) tunnel information and Core Network (CN) tunnel information.

The upf sends an N4 session setup/modification response message to the SMF, step 720. The UPF entity, upon receiving the N4 session setup/modification message, may send a corresponding N4 session setup/modification response message to the SMF entity.

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

At step 722, the smf sends an IPv6 routing advertisement message to the UPF. In one example, an IPv6 address prefix assigned by the SMF entity is included in an IPv6 routing advertisement message (IPv 6 Router Advertisement).

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

In step 724, the smf triggers a unified data management registration service network function service. In case 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 interacts with the PCF entity, the UDM entity for service requests. The service request includes an address of the SMF entity, and DNN, an identifier of the SMF entity that the UDM entity needs to store, an address of the SMF entity, an associated DNN, and the like.

As can be seen from the description above, relayUE is required to establish a suitable PDU session in order to transfer data between RemoteUE and the network. For different service types that need to be developed by Remote UE, there is no related mechanism in the related art to establish PDU session corresponding to the service type. Based on this, the embodiment of the application provides a session establishment method, and the technical scheme of the application is described by several exemplary embodiments.

Referring to fig. 8, a flowchart of a session establishment method according to an embodiment of the present application is shown, where the method may be applied to the system architecture shown in fig. 1, and the method may include the following steps:

in step 810, 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 establishment of a PDU session between the relay device and the DN, and the first session establishment request includes a first RSC.

In case of a data transmission requirement between a Relay device (Relay UE) and a DN, a PDU session between the Relay device and the DN may be established, i.e. a data transmission channel between the Relay device and the DN is established. To this end, the relay device sends a first session establishment request to the first core network device, the first session establishment request being for requesting establishment of a first PDU session. Optionally, the first core network device is implemented as the above-mentioned AMF (or referred to as an "AMF entity", "AMF network element", etc.), or in subsequent technical evolution, as another core network device with device access management and mobility management functions.

In the embodiment of the present application, the first session establishment request includes a first RSC. Compared with the situation that the service attribute is carried in the session establishment request directly to possibly cause the leakage of the service attribute to affect the system safety, the embodiment of the application ensures the privacy protection for the service attribute and improves the system safety by carrying the RSC corresponding to the service attribute in the session establishment request under the condition of ensuring the clear service attribute of the core network. Optionally, the first session establishment request is a session establishment request message in the above step 701, so that 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.

Alternatively, there is a one-to-one correspondence between RSCs and traffic attributes, i.e., one RSC corresponds to one traffic attribute. The service attribute refers to an attribute corresponding to the service requested by the device, and optionally, the service attribute comprises at least one of DNN information, slice information, session type information, PLMN information, qoS information and the like. The method for determining the first RSC is not limited in the embodiment of the present application, alternatively, the first RSC is determined by a Remote device (Remote UE) and sent to a relay device, for example, when the Remote device needs to initiate a service and wants to discover a relay device to perform relay communication, the Remote device needs to 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 in the relay device, for example, corresponding to a certain relay device, provided that it can only initiate a specific type of service, so that the RSC corresponding to the service initiated by the Remote device may also be fixed, thereby the RSC may 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 a first RSC. Since there are a plurality of core network devices (or referred to as "entities", "network elements", etc.) that can establish a PDU session in the core network system architecture, service attributes supported by each of the core network devices are different, for example, a part of the core network devices support DNN information, and a part of the core network devices support session type information. Thus, for different traffic attributes, different core network devices need to be used to establish PDU sessions. The procedure for selecting an appropriate core network device for establishing a PDU session based on the first RSC for the first core network device will be described below.

In one example, as shown in fig. 9, after the step 810, the following steps are further included:

in step 820, the first core network device selects a second core network device according to the first RSC, where the second core network device is configured to establish a PDU session.

The second core network device is a core network device for establishing a PDU session, and optionally, the second core network device is implemented as an SMF, or in subsequent technical evolution, is implemented as another core network device with a device session management function. The selection basis of the second core network equipment comprises a first RSC, and the first core network equipment selects the second core network equipment corresponding to the service attribute according to the first RSC to establish the PDU session so that the established PDU session meets the service requirement of the remote equipment. Alternatively, the first core network device may select the second core network device according to other information, such as the rule for selecting the second core network device mentioned in the related art, in addition to selecting the second core network device according to the first RSC. For a specific selection procedure of the second core network device, please refer to the following embodiments, which are not repeated here. Optionally, the first core network device selects the second core network device as the step 702, so that the difference between the step 820 and the step 702 is that, in the step 820, the basis of the first core network device selecting the second core network device includes the first RSC.

In 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 a suitable second core network device, a second session establishment request may be sent to the second core network device to request establishment of a PDU session between the relay device and the DN. The embodiment of the application does not limit the content of the second session establishment request, and optionally, the second session establishment request comprises the first RSC, or the second session establishment request comprises the session parameter information related to the PDU session requested to be established. The embodiment of the application does not limit the content of the first session establishment request and the second session establishment request, alternatively, the content of the first session establishment request and the second session establishment request are the same, that is, the first core network device forwards the received first session establishment request from the relay device to the second core network device, or the first session establishment request is different from the content of the second session establishment request, that is, the first core network device performs some processing on the received content of the first session establishment request from the relay device to obtain the second session establishment request, and sends the second session establishment request to the second core network device.

In 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 analyzes the second session establishment request to obtain some parameter information and the like, and then establishes the PDU session between the relay device and the DN according to the parameter information obtained by analysis. For a description of the procedure of establishing the PDU session by the second core network device, please refer to the following embodiments, which are not repeated here.

In 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 PDU session establishment is complete.

After the second core network device establishes the PDU session, the first core network device may be notified of the PDU session establishment completion, which is not limited by the manner in which the second core network device notifies the second core network device of the PDU session establishment completion, and optionally, the second core network device carries a notification message in the SM response message sent to the first core network device in step 713, where the notification message is used to indicate that the PDU session establishment is completed, or the second core network device separately sends a notification message to the first core network device, where the notification message is used to indicate that the PDU session establishment is completed.

After receiving the notification of the completion of the PDU session establishment, 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 the completion of the PDU session establishment, so that the establishment of a data transmission channel between the relay device and the DN is completed. The bearer manner of the first session establishment response is not limited in the embodiment of the present application, alternatively, the first core network device sends the first session establishment response to the relay device alone to notify the relay device of the completion of the PDU session establishment, or the first core network device carries the first session establishment response in the RRC connection reconfiguration message sent to the relay device in step 715 above to notify the relay device of the completion of the PDU session establishment. Optionally, the first session establishment response includes the first RSC, so that the relay device definitely determines a service or RSC corresponding to the first session establishment response.

In summary, according to the technical scheme provided by the embodiment of the application, the 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, so that the RSC is characterized by being difficult to crack and leak, and compared with the situation that the service attribute is carried directly in the session establishment request to possibly cause the service attribute to leak so as to influence the safety of the system, the embodiment of the application ensures the privacy protection aiming at the service attribute under the condition that the core network definitely has the service attribute, and improves the safety of the system.

In addition, according to the technical scheme provided by the embodiment of the application, the core network equipment selects another proper core network equipment to establish the PDU session according to the RSC carried in the session establishment request so as to establish a data transmission channel between the relay equipment and the DN. Because different core network devices with session management function have different supported service attributes, the embodiment of the application fully considers the factors influencing the PDU session establishment process, selects the core network device for establishing the PDU session through the RSC corresponding to the service attribute, ensures that the selected core network device supports the attribute corresponding to the service requested by the remote device, and improves the success rate of PDU session establishment.

As can be seen from the description of the above embodiments, the first core network device may select the second core network device by using the first RSC, and the embodiment of the present application provides two ways for selecting the second core network device, one way is to select the second core network device corresponding to the first RSC, and the other 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, description will be made with respect to a first embodiment.

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

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

The first configuration information includes a correspondence between RSCs and the second core network device. The number of the corresponding relations contained in the first configuration information is not limited in the embodiment of the application, and optionally, one or more corresponding relations are used. The embodiment of the application does not limit the corresponding mode between the RSC and the second core network equipment, alternatively, the RSC and the second core network equipment are in one-to-one correspondence, or a plurality of RSCs correspond to one second core network equipment, or one RSC corresponds to a plurality of second core network equipment, and the embodiment of the application does not limit the corresponding mode. Optionally, the first 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 predefined in a communication protocol, which is not limited by the embodiment of the present application.

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

The first core network device includes a first RSC in a 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 method for determining the session parameter information of the PDU session by the second core network device is not limited in the embodiment of the present application, and several ways for determining the session parameter information by the second core network device are provided below.

Optionally, as shown in fig. 10, the step 840 includes a step 842 of the second core network device determining session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes a correspondence between RSC and session parameter information, and a step 844 of the second core network device establishing a PDU session according to the session parameter information.

The third configuration information includes a correspondence between RSC and session parameter information. The number of the corresponding relations contained in the third configuration information is not limited in the embodiment of the present application, and optionally, the corresponding relations are one or more. The embodiment of the application does not limit the corresponding mode between the RSC and the conversation parameter information, alternatively, the RSC and the conversation parameter information are in one-to-one correspondence, or a plurality of RSCs correspond to one conversation parameter information, or one RSC corresponds to a plurality of conversation parameter information, and the embodiment of the application does not limit the same. Optionally, the third configuration information is preconfigured in the second core network device, i.e. the third configuration information is local configuration information of the second core network device, or the third configuration information is predefined in the communication protocol, or the third configuration information is configured to the second core network device by other core network devices, e.g. by the first core network device, which the embodiment of the application is not limited to.

The second core network device can determine the session parameter information corresponding to the first RSC according to the third configuration information, and then establish the PDU session according to the session parameter information. The session parameter information is session parameter information corresponding to a PDU session to be established by the second core network device, that is, session parameter information corresponding to a PDU session requested to be established by the relay device. Optionally, the session parameter information comprises at least one of slice information, DNN information, SSC mode information and session type information, and the embodiment of the application does not limit the specific content of the session parameter information.

Optionally, as shown in fig. 10, the step 840 includes a step 846 of determining session parameter information by the second core network device according to the first information field in the first RSC, and a step 848 of establishing a PDU session by the second core network device according to the session parameter information.

The session parameter information corresponding to the PDU session may also be indicated by an information field of the first RSC, and 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 determine the session parameter information according to the first information field, so as to use the session parameter information to establish the PDU session. The embodiment of the application does not limit the bit number of the first information field, alternatively, the first information field is 1 bit or more, and in practical application, the bit number of the first information field can be determined by combining the length of the session parameter information, the length of the first RSC, and the like. The number of the first information fields is also not limited in the embodiment of the present application, and optionally, the first information fields include one or more information fields in the first RSC.

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

In 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 a third core network device, and in the 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 the second core network device corresponding to the first RSC. For description of the third core network device selecting the second core network device according to the first RSC, please refer to the above method embodiment, which is not repeated here. Optionally, the third core network device includes at least one of an NRF entity (or referred to as "NRF"), a PCF entity (or referred to as "PCF").

In step 826, the third core network device sends device information to the first core network device, where the device information is used to indicate a 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 indicate the second core network device selected by the third core network device and corresponding to the first RSC. The embodiment of the application does not limit the specific content of the device information, and optionally, the device information comprises at least one of address information of the second core network device and identification information of the second core network device, wherein the address information of the second core network device is used for indicating an address (such as a network address, a physical address and the like) of the second core network device, and the identification information of the second core network device is used for indicating an identification (such as a unique device identification, a device ID and the like) of the second core network device.

Optionally, as shown in fig. 10, the step 830 includes step 832, where the first core network device sends a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of a PDU session, and the second session establishment request includes the first RSC. For the description of step 832, please refer to the above embodiments, and the description thereof is omitted here.

Optionally, as shown in fig. 10, the step 840 includes a step 842 of the second core network device determining session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes a correspondence between RSC and session parameter information, and a step 844 of the second core network device establishing a PDU session according to the session parameter information. Optionally, as shown in fig. 10, the step 840 includes a step 846 of determining session parameter information by the second core network device according to the first information field in the first RSC, and a step 848 of establishing a PDU session by the second core network device according to the session parameter information. For a description of steps 842, 844, 846, 848, please refer to the above embodiments, and the description thereof is omitted here.

It should be noted that, in the embodiment of the present application, the steps of the method may be arbitrarily combined without violating logic, for example, the step 822 is followed by the step 832, then the step 842 and the step 844, for example, the step 822 is followed by the step 832, then the step 846 and the step 848, for example, the step 824 and the step 826 are followed by the step 832, then the step 842 and the step 844, and for example, the step 824 and the step 826 are followed by the step 832, then the step 846 and the step 848. It should be understood that these are all intended to be within the scope of the present application.

Next, description will be made on the second mode.

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

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

In the embodiment of the application, the first core network device can send the first RSC to the third core network device, and the third core network device determines the session parameter information needed for establishing the PDU session according to the first RSC. Optionally, the third core network device includes at least one of 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 the third core network device receives the first RSC, session parameter information may be determined according to the second configuration information. The description of the third core network device determining the session parameter information and the second configuration information according to the first RSC will be omitted herein for brevity. Optionally, the session parameter information comprises at least one of slice information, DNN information, SSC mode information and session type information, and the embodiment of the application does not limit the specific content of the session parameter information.

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.

In step 825, the first core network device selects 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.

The third configuration information includes a correspondence between RSC and session parameter information, optionally, the third configuration information is preconfigured in the first core network device, that is, the third configuration information is local configuration information of the first core network device, or the third configuration information is predefined in a communication protocol, which is not limited by the embodiment of the present application. For other description of the third configuration information, please refer to the above method embodiment, and the description is omitted here.

Based on this, as shown in fig. 11, the step 830 includes a step 831 in which the first core network device sends a second session establishment request to the second core network device, where the second session establishment request includes session parameter information.

Because the first core network device has already 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 establishes the PDU session directly according to the session parameter information.

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

After receiving the second session establishment request, the second core network device analyzes 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 analysis to establish a data transmission channel between the relay device and the DN.

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

in step 827, the first core network device determines session parameter information corresponding to the first RSC according to second configuration information, where the second configuration information includes a correspondence between RSC and session parameter information.

The second configuration information includes a correspondence between RSC and session parameter information. The number of the corresponding relations contained in the second configuration information is not limited in the embodiment of the application, and optionally, one or more corresponding relations are used. The embodiment of the application does not limit the corresponding mode between the RSC and the conversation parameter information, alternatively, the RSC and the conversation parameter information are in one-to-one correspondence, or a plurality of RSCs correspond to one conversation parameter information, or one RSC corresponds to a plurality of conversation parameter information, and the embodiment of the application does not limit the same. 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 predefined in a communication protocol, which is not limited by the embodiment of the present application. The first core network device may determine session parameter information corresponding to the first RSC according to the second configuration information, so as to determine the second core network device further according to the session parameter information. Optionally, the session parameter information comprises at least one of slice information, DNN information, SSC mode information and session type information, and the embodiment of the application does not limit the specific content of the session parameter information.

Step 829, the first core network device selects 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.

For a description of step 829, please refer to step 825 above, which is not repeated here.

Based on this, as shown in fig. 11, the step 830 includes a step 831 in which the first core network device sends a second session establishment request to the second core network device, where the second session establishment request includes session parameter information. Based on this, as shown in fig. 11, the step 840 includes step 841, where the second core network device establishes a PDU session according to the session parameter information. For the description of step 831 and step 841, please refer to the above embodiment, and the description is omitted here.

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

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

For the description of the first information field, please refer to the description of the above steps 846 and 848, which 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 session parameter information includes at least one of slice information, DNN information, SSC mode information, session type information.

In step 82B, the first core network device selects 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.

For a description of step 82B, please refer to step 825 above, and further description is omitted herein.

It should be noted that, in the embodiment of the present application, the steps of the method may be arbitrarily combined without violating logic, for example, the steps 821, 823, and 825 are performed after the step 831 is performed, then the step 841 is performed, for example, the steps 827 and 829 are performed after the step 831 is performed, then the step 841 is performed, and for example, the steps 82A and 82B are performed after the step 831 is performed, and then the step 841 is performed. It should be understood that these are all intended to be within the scope of the present application.

It should be further noted that, in the embodiment of the present application, the first configuration information is only used to indicate configuration information including a correspondence between the first RSC and the second core network device, the second configuration information is only used to indicate configuration information including a correspondence between the first RSC and session parameter information, and the third configuration information is only used to indicate configuration information including a correspondence between the session parameter information and the second core network device, and it should be understood that the first configuration information, the second configuration information, and the third configuration information are not limited to configuration information of a certain core network device.

In summary, according to the technical solution provided in the embodiments of the present application, by selecting a core network device corresponding to the RSC carried in the session establishment request according to the correspondence between the RSC and the core network device, a specific manner of selecting the core network device according to the RSC is implemented. In addition, the embodiment of the application provides a plurality of selection bodies and a plurality of selection modes, and the selection bodies and the selection modes can be combined in a plurality of modes, so that the flexibility of selecting the core network equipment is improved.

It should be noted that, in the above embodiment of the method, the session establishment method provided by the present application is mainly described from the perspective of interaction among the relay device, the first core network device and the second core network device. The steps executed by the relay device may be implemented solely as a relay device side session establishment method, the steps executed by the first core network device may be implemented solely as a first core network device side session establishment method, and the steps executed by the second core network device may be implemented solely as a second core network device side session establishment method.

The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.

Referring to fig. 12, a block diagram of a session establishment apparatus according to an embodiment of the present application is shown. The device has the function of realizing the relay equipment side method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The apparatus may be the relay device described above, or may be provided in the relay device. As shown in fig. 12, the apparatus 1200 may include a first request transmitting module 1210.

A first request sending module 1210 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 establishment of a PDU session between the relay device and the DN, and the first session establishment request includes a first RSC.

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

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

In one example, the first RSC is included in the first session establishment response.

Referring to fig. 13, a block diagram of a session establishment apparatus according to an embodiment of the present application is shown. The device has the function of realizing the first core network equipment side method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The apparatus may be the first core network device described above, 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.

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

In one example, as shown in FIG. 15, the apparatus 1400 further includes a device selection module 1420 to select a second core network device to establish the PDU session based on the first RSC.

In one 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 a correspondence between the RSC and the second core network device.

In one example, as shown in fig. 15, the device selection module 1420 is configured to send the first RSC to a third core network device, and receive device information from the third core network device, where the device information is used to indicate a second core network device corresponding to the first RSC.

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

In one 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 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, and select 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 session parameter information and the second core network device.

In one 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 second configuration information, where the session parameter information is used to establish the PDU session, the second configuration information includes a correspondence between RSC and session parameter information, and select, according to third configuration information, a second core network device corresponding to the session parameter information, where the third configuration information includes a correspondence between session parameter information and the second core network device.

In one example, as shown in fig. 15, the device selection module 1420 is configured to determine session parameter information according to a first information field in the first RSC, where the session parameter information is used to establish the PDU session, and select 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 slice information, DNN information, SSC mode information, session type information.

In one example, the third core network device comprises at least one of an NRF entity, a PCF entity.

In one 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, where the second session establishment request is used to request to establish the PDU session, and the second session establishment request includes the first RSC.

In one 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, where the second session establishment request is used to request to establish the PDU session, and the second session establishment request includes the session parameter information.

In one example, as shown in FIG. 15, the apparatus 1400 further comprises a first response transmitting module 1440 configured to transmit 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 complete.

Referring to fig. 16, a block diagram of a session establishment apparatus according to an embodiment of the present application is shown. The device has the function of realizing the second core network equipment side method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The apparatus may be the second core network device described above, 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, a session establishing module 1620.

A second request receiving module 1610, 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 1620, configured to establish a PDU session between the relay device and the DN according to the second session establishment request.

In one example, the second session establishment request includes the first RSC, and the session establishment module 1620 is configured to determine session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes a correspondence between RSCs and session parameter information, and establish the PDU session according to the session parameter information.

In one example, the second session establishment request includes the first RSC, and the session establishment module 1620 is configured to determine session parameter information according to a first information field in the first RSC, and establish the PDU session according to the session parameter information.

In one example, the second session establishment request includes session parameter information corresponding to the first RSC, and 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 apparatus provided in the foregoing embodiment performs the functions thereof, only the division of the respective functional modules is used as an example, in practical application, the foregoing functional allocation may be performed by different functional modules according to actual needs, that is, the content structure of the device is divided into different functional modules, so as to perform all or part of the functions described above.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Referring to fig. 17, a schematic structural diagram of a relay device 170 according to an embodiment of the present application is shown, and the relay device may be used to perform the above-mentioned session establishment method 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.

The 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 may be used to store a computer program for execution by the processor to perform the steps performed by the relay device in the method embodiments described above.

Furthermore, the Memory may be implemented by any type or combination of volatile or nonvolatile Memory devices including, but not limited to, RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory), flash Memory or other solid state Memory technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc, high density digital video disk) or other optical storage, tape cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Wherein:

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 establishment of a PDU session between the relay device and the DN, and the first session establishment request includes a first RSC.

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

Referring to fig. 18, a schematic structural diagram of a core network device 180 according to an embodiment of the present application is shown, and the core network device may be used to perform the first core network device side session establishment method or the first core network device side session establishment method, for example. Specifically, the core network device 180 may include a processor 181, and a transceiver 182 coupled 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.

The transceiver 182 includes a receiver and a transmitter. Alternatively, the transceiver 182 is a communication chip.

In one example, the core network device 180 also includes a memory and a bus. The memory is connected to the processor through a bus. The memory may be used for storing a computer program, and the processor is used for executing the computer program to implement the steps executed 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 perform 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 for requesting establishment of a PDU session between the relay device and a DN, and the first session establishment request includes a first RSC.

In one 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 one 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 a correspondence between the RSC and the second core network device.

In one example, the transceiver 182 is configured to send the first RSC to a third core network device, and the transceiver 182 is configured to receive device information from the third core network device, where the device information is configured to indicate a second core network device corresponding to the first RSC.

In one example, the transceiver 182 is configured to send the first RSC to a third core network device, the transceiver 182 is configured to receive 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, and the processor 181 is configured to select 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 session parameter information and the second core network device.

In one example, the processor 181 is configured to determine session parameter information corresponding to the first RSC according to second configuration information, where the session parameter information is used to establish the PDU session, the second configuration information includes a correspondence between RSC and session parameter information, and select 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 session parameter information and a second core network device.

In one example, the processor 181 is configured to determine session parameter information according to a first information field in the first RSC, where the session parameter information is used to establish the PDU session, and select 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 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 establishment request includes the first RSC.

In one 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 to establish the PDU session, and the second session establishment request includes the session parameter information.

In one example, the transceiver 182 is configured to send a first session setup response to the relay device, where the first session setup response is used to indicate that the PDU session setup is complete.

For the case where the core network device 180 is configured to perform 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 a 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 one example, the second session establishment request includes the first RSC, and the processor 181 is configured to determine session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes a correspondence between RSC and session parameter information, and establish the PDU session according to the session parameter information.

In one example, the second session establishment request includes the first RSC, the processor 181 is configured to determine session parameter information according to a first information field in the first RSC, and establish the PDU session according to the session parameter information.

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

Those skilled in the art will appreciate that in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, these 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 media may be any available media that can be accessed by a general purpose or special purpose computer.

The foregoing description of the exemplary embodiments of the application is not intended to limit the application to the particular embodiments disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the application.

Claims

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

Sending a first session establishment request to the 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 a first relay service code (RSC);

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, wherein the data network DN is different from the second core network device.

2. The method according to claim 1, characterized in that the method further comprises:

A first session establishment response is received from the first core network device, where the first session establishment response is used to indicate that the PDU session establishment is complete.

3 . The method according to claim 2 , wherein the first session establishment response includes the first RSC.

4. A session establishment method, characterized in that it is applied to a first core network device, and the method comprises:

receiving a first session establishment request from a relay device, wherein the first session establishment request is 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 a first relay service code (RSC); and

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, wherein the data network DN is different from the second core network device.

5. The method according to claim 4, characterized in that the selecting the second core network device according to the first RSC comprises:

According to first configuration information, a second core network device corresponding to the first RSC is selected, and the first configuration information includes a corresponding relationship between the RSC and the second core network device.

6. The method according to claim 4, characterized in that the selecting the second core network device according to the first RSC comprises:

Sending the first RSC to a 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.

7. The method according to claim 6 is characterized in that 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.

8. The method according to claim 4, wherein selecting a second core network device according to the first RSC comprises:

Sending the first RSC to a 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, a second core network device corresponding to the session parameter information is selected, and the third configuration information includes a correspondence between the session parameter information and the second core network device.

9. The method according to claim 4, wherein selecting a second core network device according to the first RSC comprises:

Determine, according to the second configuration information, session parameter information corresponding to the first RSC, the session parameter information being used to establish the PDU session, the second configuration information including a correspondence between the RSC and the session parameter information;

10. The method according to claim 4, wherein selecting a second core network device according to the first RSC comprises:

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;

11. The method according to any one of claims 5 to 10 is characterized in that the session parameter information includes at least one of the following: slice information, data network name DNN information, session and service continuity SSC mode information, and session type information.

12. The method according to any one of claims 6 to 8 is characterized in that the third core network device includes at least one of the following devices: a storage function NRF entity and a policy control function PCF entity of a network function entity.

13. The method according to any one of claims 5 to 7, characterized in that the method further comprises:

A second session establishment request is sent 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.

14. The method according to any one of claims 8 to 10, characterized in that the method further comprises:

A second session establishment request is sent 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.

15. The method according to any one of claims 4 to 10, characterized in that 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 complete.

16. The method according to claim 15, characterized in that the first session establishment response includes the first RSC.

17. 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 a first relay service code RSC, wherein the first RSC is included in a first session establishment request received by the first core network device from a relay device, and the first session establishment request is used to request establishment of a protocol data unit (PDU) session between the relay device and a data network DN, wherein the data network DN is different from the second core network device;

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

18. The method according to claim 17, wherein the second session establishment request includes the first RSC;

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

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

The PDU session is established according to the session parameter information.

19. The method according to claim 17, wherein the second session establishment request includes the first RSC;

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

The PDU session is established according to the session parameter information.

20. The method according to claim 17, wherein the second session establishment request includes session parameter information corresponding to the first RSC;

The PDU session is established according to the session parameter information.

21. The method according to any one of claims 18 to 20 is characterized in that the session parameter information includes at least one of the following: slice information, data network name DNN information, session and service continuity SSC mode information, and session type information.

22. A session establishment device, characterized in that it is arranged in a relay device, and the device comprises:

A first request sending module is used to send a first session establishment request to a first core network device, wherein 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 a first relay business service code RSC; 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, wherein the data network DN is different from the second core network device.

23. The device according to claim 22, characterized in that the device further comprises:

The first response receiving module is used 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.

24. The device according to claim 23, characterized in that the first session establishment response includes the first RSC.

25. A session establishment device, characterized in that it is set in a first core network device, and the device comprises:

a first request receiving module, configured to receive a first session establishment request from a relay device, wherein the first session establishment request is used to request to establish a protocol data unit (PDU) session between the relay device and a data network DN, and the first session establishment request includes a first relay service code (RSC); and

A device selection module is used to select a second core network device according to the first RSC, and the second core network device is used to establish the PDU session, wherein the data network DN is different from the second core network device.

26. The apparatus according to claim 25, wherein the device selection module is used to:

27. The apparatus according to claim 25, wherein the device selection module is used to:

Sending the first RSC to a third core network device;

28. The apparatus according to claim 27 is characterized in that 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.

29. The apparatus according to claim 25, wherein the device selection module is used to:

Sending the first RSC to a third core network device;

30. The apparatus according to claim 25, wherein the device selection module is used to:

31. The apparatus according to claim 25, wherein the device selection module is used to:

32. The device according to any one of claims 29 to 31 is characterized in that the session parameter information includes at least one of the following: slice information, data network name DNN information, session and service continuity SSC mode information, and session type information.

33. The apparatus according to any one of claims 27 to 29 is characterized in that 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.

34. The device according to any one of claims 26 to 28, characterized in that the device further comprises:

The second request sending module is used to send a second session establishment request to the second core network device, where the second session establishment request is used to request to establish the PDU session, and the second session establishment request includes the first RSC.

35. The device according to any one of claims 29 to 31, characterized in that the device further comprises:

The second request sending module is used to send a second session establishment request to the second core network device, where the second session establishment request is used to request to establish the PDU session, and the second session establishment request includes the session parameter information.

36. The device according to any one of claims 25 to 31, characterized in that the device further comprises:

The first response sending module is used 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.

37. The device according to claim 36 is characterized in that the first session establishment response includes the first RSC.

38. A session establishment device, characterized in that it is set in a second core network device, and the device comprises:

a second request receiving module, configured to receive a second session establishment request from a first core network device, the second core network device being selected by the first core network device based on a first relay service code RSC, wherein the first RSC is included in a first session establishment request received by the first core network device 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, wherein the data network DN is different from the second core network device;

The session establishing module is used to establish a protocol data unit PDU session between the relay device and the data network DN according to the second session establishment request.

39. The device according to claim 38, wherein the second session establishment request includes the first RSC; and the session establishment module is used to:

The PDU session is established according to the session parameter information.

40. The device according to claim 38, wherein the second session establishment request includes the first RSC; and the session establishment module is used to:

The PDU session is established according to the session parameter information.

41. The device according to claim 38, wherein the second session establishment request includes session parameter information corresponding to the first RSC; and the session establishment module is used to:

The PDU session is established according to the session parameter information.

42. The device according to any one of claims 38 to 41 is characterized in that the session parameter information includes at least one of the following: slice information, data network name DNN information, session and service continuity SSC mode information, and session type information.

43. A relay device, characterized in that the relay device comprises: a processor, and a transceiver and a memory connected to the processor; wherein: the memory is used to store a computer program, and the processor is used to execute the computer program to cooperate with the transceiver to implement the session establishment method described in any one of claims 1-3.

44. A core network device, characterized in that the core network device comprises: a processor, a transceiver and a memory connected to the processor; wherein: the memory is used to store a computer program, and the processor is used to execute the computer program to cooperate with the transceiver to implement the session establishment method described in any one of claims 4-16.

45. A core network device, characterized in that the core network device comprises: a processor, a transceiver and a memory connected to the processor; wherein: the memory is used to store a computer program, and the processor is used to execute the computer program to cooperate with the transceiver to implement the session establishment method described in any one of claims 17-21.

46. 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 to implement the session establishment method according to any one of claims 1 to 3.

47. 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 to implement the session establishment method as described in any one of claims 4 to 16.

48. 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 to implement the session establishment method as described in any one of claims 17 to 21.