CN115553045A

CN115553045A - Session establishing method, device, equipment and storage medium

Info

Publication number: CN115553045A
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: 2022-12-30
Also published as: WO2022021355A1

Abstract

The application discloses a session establishing method, a session establishing device, session establishing equipment and a storage medium, and belongs to the technical field of communication. The method comprises the step that the relay equipment sends a first session establishment request to the first core network equipment, the first session establishment request is used for requesting to establish a PDU session between the relay equipment and the DN, and the first session establishment request comprises a first RSC. According to the technical scheme provided by the embodiment of the application, 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 the RSC is represented as the service code and has the characteristic of being difficult to crack and leak.

Description

Session establishing method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a session establishment method, apparatus, device, and storage medium.

Background

The 3GPP (3 rd Generation Partnership Project) introduced the concept of relaying communication in the R13 (Release 13, 13 th version) ProSe (Proximity Service) architecture.

The relay communication refers to a UE (User Equipment) -to-Network (terminal Equipment connected to a Network) based on an IP (Internet Protocol) layer relay. That is, the Remote UE (Remote device) accesses the network through the Relay UE (Relay device). The Relay UE plays a role of IP layer Relay, and transmits data between the Relay UE and a network to establish communication connection between the Relay UE and the network, illustratively, the network comprises access network equipment and core network equipment, and the Relay UE sends the data from the Relay UE to the access network equipment and can further send the data to the core network equipment by the access network equipment; or, the access network equipment sends the data from the core network equipment to the Relay UE, and then the Relay UE sends the data from the access network equipment to the Remote UE.

However, in order for the Relay UE to transmit Data between the Remote UE and the network, a proper PDU (Protocol Data Unit) session needs to be established. For different service types to be developed by Remote UEs, how to establish a PDU session corresponding to the service type needs to be further discussed and studied.

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, which is applied to a relay device, and the method includes:

sending 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 a DN (data 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, and the method includes:

receiving a first session establishment request from a relay device, wherein the first session establishment request is used for requesting the establishment of a PDU session between the relay device and a DN, and the first session establishment request comprises a first RSC.

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

receiving a second session establishment request from a first core network device, wherein the second core network device is 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 another aspect, an embodiment of the present application provides a session establishing apparatus, configured in a relay device, where the apparatus includes:

the first request sending module 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 a further aspect, an embodiment of the present application provides a session establishment apparatus, configured in a first core network device, where the apparatus includes:

the device comprises a first request receiving module, a second request receiving module and a first RSC sending module, wherein the first request receiving module is used for receiving a first session establishment request from the relay equipment, the first session establishment request is used for requesting to establish a PDU session between the relay equipment and the DN, and the first session establishment request comprises the first RSC.

In a further aspect, an embodiment of the present application provides a session establishing apparatus, where the session establishing apparatus is disposed in a second core network device, and the apparatus includes:

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

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

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

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

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

the transceiver is configured to receive a first session establishment request from a relay device, where the first session establishment request is used to request 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 the first RSC;

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

In a further aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the storage medium, where the computer program is used for being executed by a processor of a relay device to implement the relay device side session establishment method described above.

In a further aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used for being executed by a processor of a core network device to implement the first core network device-side session establishment method.

In a further aspect, an embodiment of the present application provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is used for being executed by a processor of a core network device to implement the second core network device-side session establishment method.

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

In a further aspect, an embodiment of the present application provides a chip, where the chip includes a programmable logic circuit and/or a program instruction, and when the chip runs on a core network device, the chip is configured to implement the first core network device-side session establishment method.

In a further aspect, an embodiment of the present application provides a chip, where the chip includes a programmable logic circuit and/or a program instruction, and when the chip runs on a core network device, the chip is configured to implement the second core network device-side session establishment method as described above.

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

In another aspect, an embodiment of the present application provides a computer program product, which when running on a core network device, causes a computer to execute the first core network device side session establishment method.

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

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

the method and the device have the advantages that the relay device sends the session establishment request to the core network device, the RSC corresponding to the service attribute is carried in the session establishment request, the RSC is represented as a service code, and the characteristics of being difficult to crack and leak are achieved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

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 provided in an embodiment of the present application;

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

fig. 4 is a schematic diagram of a system architecture of a 5GS system provided by 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 diagram illustrating a remote device accessing a network and obtaining IP services according to an embodiment of the application;

fig. 7 is a flowchart of a relay device establishing a PDU session according to an embodiment of the present application;

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

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

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

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

fig. 12 is a block diagram of a session setup apparatus according to an embodiment of the present application;

fig. 13 is a block diagram of a session setup device according to another embodiment of the present application;

fig. 14 is a block diagram of a session setup apparatus according to still another embodiment of the present application;

fig. 15 is a block diagram of a session setup device according to another embodiment of the present application;

fig. 16 is a block diagram of a session setup device according to still another embodiment of the present application;

fig. 17 is a block diagram of a relay device 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

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it can be known by a person skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.

The technical scheme provided by the embodiment of the application can be applied to various communication systems, such as: a GSM (Global System for Mobile communications) System, a CDMA (Code Division Multiple Access) System, an ECDMA (Wideband Code Division Multiple Access) System, a GPRS (General Packet Radio Service), an LTE (Long Term Evolution ) System, an FDD (Radio Division Duplex, LTE Duplex) System, a TDD (Time Division Duplex, LTE Time Division Duplex) System, an UMTS (Universal Mobile telecommunications System ), a WiMAX (world Interoperability for Microwave Access), a Global interconnect Microwave Access (GSM) Communication System, a 5GS or New Radio (NR) System, or other Evolution systems.

Referring to fig. 1, a schematic diagram of a system architecture of a communication system according to an embodiment of the present application is shown. As shown in fig. 1, the system architecture 100 may include: a terminal device 10, an access network device 20 and a core network device 30.

Terminal equipment 10 may refer to a UE, access terminal, subscriber unit, subscriber station, mobile, remote station, remote terminal, mobile device, wireless communication device, user agent, or user device. Alternatively, the terminal device may also be a cellular phone, a cordless phone, an SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal digital Assistant), a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in 5GS or a terminal device in a PLMN (public Land mobile Network) evolved in the future, and the like, which is not limited in this embodiment.

The access network device 20 is a device deployed in an access network to provide wireless communication functions for terminal devices. The access network equipment 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different Radio access technologies, names of devices having functions of access network devices may be different, for example, in a 5G (5 th-Generation, fifth Generation mobile communication) NR (New Radio, new air interface) System, the devices are called a NodeB or a gNB, and in an EPS (Evolved Packet System), the devices of the access network may be called an eNodeB (Evolved node b, evolved base station). As communication technology evolves, the name "access network equipment" may change. For convenience of description, in the embodiments of the present application, the above-mentioned 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 refers to a device that can provide functions such as session management, mobility relationship, policy management, security authentication, and the like for the terminal device. In this embodiment, 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. Exemplarily, in the 5GS system, the first Core network may be implemented as AMF (Core Access and Mobility Management Function), and the second Core network device may be implemented as SMF (Session Management Function); 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).

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, illustratively, relay device 14 transmits data from remote device 12 to access network device 20 and may further be transmitted by access network device 20 to core network device 30; alternatively, the access network device 20 transmits data from the core network device 30 to the relay device 14, and the relay device 14 then transmits data from the access network device 20 to the remote device 12.

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

1. and (3) EUTRAN: the network composed of a plurality of eNodeBs realizes the functions of wireless physical layer, resource scheduling and wireless resource management, wireless access control and mobility management. The enodebs may be connected via an X2 interface and may be used to transmit data during an X2-based handover. The eNodeB is connected to the SGW through a User Plane interface SI-U, and uses GTP-U (General Packet Radio System General Tunneling Protocol User Plane) to transmit User data: the control plane interface SI-E is connected with the MME, and the SI-AP protocol is adopted to realize the functions of wireless access bearing control and the like.

2. MME: all control plane functions mainly responsible for user session management include NAS (Non-Access-Stratum) signaling and security, tracking Area List management (Tracking Area List), P-GW (Packet data Network Gateway) and SGW selection, and the like.

3. SGW: the serving mobility anchor point is mainly responsible for data transmission, forwarding, route switching, and the like of the ue, and is used as a local mobility anchor point when the ue switches between enodebs (each user is provided with only one SGW serving each time).

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

5. SGSN (Serving GPR Supporting Node, serving GPRs support Node): the Access node is an Access node of a 2G Access Network GERAN (GSM/EDGE Radio Access Network ), a 3G Access Network UTRAN (Universal Terrestrial Radio Access Network) and an EPS core Network EPC, and is responsible for establishing a load from the GERAN, the UTRAN and the EPC and forwarding data.

6. HSS (Home Subscriber Server): and storing the subscription data of the mobile user.

7. PCRF (Policy and Charging Rules Function): and is responsible for Charging management and Policy Control, including PCC (Policy and Charging Control) rules and QoS (Quality of Service) rules.

Fig. 3 shows a schematic diagram of a system architecture of the 5GS system provided by the embodiment of the present application. As shown in fig. 3, the system architecture 200 may include: UE, RAN (Radio Access Network), core (Core Network), and DN. The UE, RAN and Core are the main components constituting the architecture, and they may be logically divided into two parts, namely a user plane and a control plane, where 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.

UE: the method is an entrance for interaction between a mobile user and a network, can provide basic computing capacity and storage capacity, displays a business window for the user, and accepts operation input of the user. The UE establishes signal connection and data connection with the RAN using a next generation air interface technology, thereby transmitting control signals and service data to the mobile network.

RAN: similar to a base station in a traditional network, the base station is deployed at a position close to the UE, provides a network access function for authorized users in a specific area, and can transmit user data by using transmission tunnels with different qualities according to the level of the users, the service requirements and the like. RAN can manage its own resources, make reasonable use of the resources, provide access services for UE as required, and forward control signals and user data between UE and a core network.

Core: and the mobile terminal is responsible for maintaining subscription data of the mobile network, managing network elements of the mobile network, and providing functions of session management, mobility management, policy management, security authentication and the like for the UE. When the UE is attached, network access authentication is provided for the UE; when the UE has a service request, network resources are distributed to the UE; updating network resources for the UE when the UE moves; when the UE is idle, a fast recovery mechanism is provided for the UE: when the UE is detached, releasing network resources for the UE; when the UE has service data, providing a data routing function for the UE, such as forwarding uplink data to DN: or receiving UE downlink data from the DN, forwarding the UE downlink data to the RAN, and sending the UE downlink data to the RAN.

DN: the UE is a data network providing service for users, and generally, the client is 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, an external Network that is not controlled by an operator, such as the Internet, or a private Network that is co-deployed by an operator, such as in order to configure an IMS (IP Multimedia Network Subsystem) service.

Fig. 4 is a detailed architecture determined on the basis of fig. 3, wherein the core network User Plane comprises a UPF (User Plane Function); the core Network Control plane includes an AUSF (Authentication Server Function), an AMF, an SMF, an NSSF (Network Slice Selection Function), an NEF (Network Exposure Function), an NRF (NF replication Function, network functional entity warehousing Function), an UDM (Unified Data Management ), a PCF (Policy Control Function), and an AF (Application Function). The functions of these functional entities are as follows:

and (4) UPF: executing user data packet forwarding according to the routing rule of the SMF;

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 a network function to a third party in a northbound API interface mode;

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

UDM: user contract context management;

PCF: managing user policies;

AF: and managing the user application.

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 of the RAN and the AMF and is used for sending NAS information and the like; the N3 interface is a reference point between the RAN and the UPF and is used for transmitting data of a user plane and the like; the N4 interface is a reference point between the SMF and the UPF and is used for transmitting tunnel identification information, data cache indication information, downlink data notification information and other information of the N3 connection; the N6 interface is a reference point between the UPF and the DN, and is used for transmitting data of a user plane and the like.

It should be noted that the name of the interface between each network element in fig. 3 and fig. 4 is only an example, and the name of the interface in the specific implementation may be other names, which is not specifically limited in this embodiment of the present application. The names of the respective network elements (such as SMF, AF, UPF, etc.) included in fig. 3 and 4 are also only examples, and the functions of the network elements themselves are not limited. In 5GS and other future networks, the network elements may also be named otherwise, and this is not specifically limited in this 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, and may also use other names, and so on, which are described herein in a unified manner and will not be described again below. Furthermore, it should be understood that the name of the transmitted message (or signaling) between the network elements is only an example, and the function of the message itself is not limited in any way.

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 includes three parts: a radio subsystem part, an EPC (Evolved Packet Core) part, and a near field communication service part.

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

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

The near field communication service part, i.e., the ProSe architecture part, includes a PF (ProSe Function), a PAS (near field communication Application Server), a Relay device (Relay UE), and a Remote device (Remote UE). Wherein: PF: the system is used for authorizing the near field communication of the terminal equipment, providing discovery assistance among the terminal equipment and the like; PAS: the system is used for providing specific near field communication service support; the Relay UE: the relay access support is provided for the Remote UE; remote UE: the method is used for accessing to the network through the Relay UE to obtain IP (Internet Protocol, protocol for interconnection between networks) service. In one example, as shown in fig. 5, PA (proximity Application) is installed in each of Relay UE and Remote UE.

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

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

At step 620, the remote device discovers a relay device. In one example, in the process of discovering the relay device, the remote device uses an APN (Access Point Name) supported by the relay device as reference information.

At step 630, the remote device requests the relay device to establish a one-to-one communication. The remote device may request the relay device to establish One-to-One (One-2-One) communication through the PC5 interface, and optionally, the request sent by the remote device carries an APN. Optionally, simultaneously with or after performing step 630, step 632 may be 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.

Step 650, the relay device sends a remote terminal report to the MME. Optionally, the Remote terminal report carries an Identifier (e.g., an Identifier (ID)) of the Remote device, an IP address, and the like.

In step 660, the mme sends a remote terminal report to the PGW. After receiving the remote terminal report of the relay device, the MME may send the remote terminal report to the PGW, so that the PGW locally stores information of the remote device, and a subsequent PGW may use the information to gate uplink and downlink data of the remote device, that is, whether transmission of the uplink and downlink data is allowed. Optionally, after step 660, the method further includes: the remote device sends uplink IP data or receives downlink IP data, the IP data passes through the relay device, and the IP data is loaded in a PDN connection which is established by the relay device for the remote device and is used for relaying.

As can be seen 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 the relay device determines which PDU session to use for transmitting the relay data. Generally, in the PDU session establishment process, the relay device determines the parameters required for establishing the PDU session according to the URSP (UE path selection policy) configured by the network. Referring to fig. 7, a flowchart of a relay device establishing a PDU session according to an embodiment of the present application 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, a Relay device (Relay UE) sends a session establishment request message to the AMF entity, where the session establishment request message is used to request the establishment of a PDU session. In one example, the session request setup message includes at least one of: the PDU session management-Network slice selection information includes S-NSSAI (session management-Network slice selection information) corresponding to the PDU session, DNN (Date Network Name) corresponding to the PDU session, PDU session identifier, request type (request type), N1SM information (N1 session management information), and PDU type.

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

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

In step 704, the smf sends a subscription data request message to the UDM. When the SMF entity does not acquire the SM related subscription information of the Relay UE from the UDM entity, the SMF entity needs to send a subscription data request message to the UDM entity to acquire subscription data. In one example, the subscription data request message includes at least one of: subscription identity (subscriber permanent ID), DNN.

Step 705, the udm sends subscription data to the SMF. After receiving the subscription data request message, the UDM entity may send a subscription data response (subscription data response) message to the SMF entity. In one example, the subscription data response message includes subscription information. Then, the SMF may perform an authorization check on the subscription information, and send NAS (Non Access Stratum) signaling to the Relay UE when the SMF entity confirms that the authorization check fails, where the NAS signaling is used to indicate that the session establishment request of the Relay UE is rejected.

The smf completes the authorization/authentication of the establishment of the PDU session, step 706. Under the condition that the SMF entity needs to authorize/authenticate the establishment of the PDU session, the SMF entity needs to select the UPF entity according to a certain rule, and then the SMF entity triggers the authorization/authentication of the establishment of the PDU session so as to complete the authorization/authentication of the establishment of the PDU session.

In step 707, the smf selects the PCF. In the case of requiring dynamic PCC (Policy Control and Charging) deployment, the SMF entity needs to select a PCF entity according to a certain rule.

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

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

In step 710, the SMF initiates a PDU-CAN session establishment procedure. When the dynamic PCC is deployed and the PDU-CAN session establishment process is not executed, the SMF entity CAN initiate the PDU-CAN session establishment process to the PCF entity, and then the SMF entity obtains a default PCC rule from the PCF entity. And under the condition that the request type sent by the Relay UE indicates that the PDU session requested to be established is the existing PDU session, the SMF entity initiates a PDU-CAN session modification process, and sends the IP address of the allocated Relay UE to the PCF entity.

Step 711, the smf initiates the N4 session establishment/modification procedure to the UPF. Under the condition that 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 the UPF entity with packet detection, reporting rules, CN tunnel information (tunnel info), and the like.

Step 712, the upf sends an N4 session setup/modify response message to the SMF. The UPF entity may send an N4 session establishment/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, the SM response message includes at least one of: cause value (cause), N2 reference point session management information (N2 SM information), N1SM information, and the like.

In step 714, the amf sends an N2PDU session request message to the RAN. In one example, the N2PDU session request message includes at least one of: n2SM information, NAS messages, etc.

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 configuration) message to the Relay UE, and allocate necessary RAN resources according to a QoS (Quality of Service) rule. 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. The Relay UE may send an RRC connection reconfiguration response message to the RAN entity after receiving the RRC connection reconfiguration message of the RAN entity.

In 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: PDU session identification, cause value, N2SM message.

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/modify request message to the UPF, step 719. Under the condition that the N4 session is not established, the SMF entity can send an N4 session establishment message to the UPF entity; in the case of N4 session establishment, the SMF entity may send AN N4 session modification message to the UPF entity to update Access Network (Access Network, AN) tunnel information and Core Network (Core Network, CN) tunnel information.

Step 720, the upf sends an N4 session setup/modify response message to the SMF. The UPF entity, upon receiving the N4 session establishment/modification message, may send a corresponding N4 session establishment/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.

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

And 723, releasing the user plane resource by the SMF. In case the PDU session is triggered due to a 3GPP or non-3 GPP handover, the SMF entity also needs to release the user plane resources on the original access side.

In step 724, the smf triggers the unified data management registry 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 interaction of the service request is performed between the SMF entity and the PCF entity, the UDM entity. The address of the SMF entity, the DNN, the identity of the SMF entity that the UDM entity needs to save, the address of the SMF entity, the associated DNN, etc. are included in the service request.

As can be seen from the above description, the Relay UE needs to establish a proper PDU session in order to transmit data between the Relay UE and the network. For different service types that the Remote UE needs to develop, there is no relevant mechanism in the related art to establish a PDU session corresponding to the service type. Based on this, embodiments of the present application provide a session establishment method, and a technical solution of the present application is described below through several exemplary embodiments.

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

step 810, the relay device sends a first session establishment request to the first core network device, 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 the first RSC.

In the case that there is a data transmission requirement between a Relay device (Relay UE) and a DN, a PDU session between the Relay device and the DN, that is, a data transmission channel between the Relay device and the DN, may be established. To this end, the relay device sends a first session establishment request to the first core network device, where the first session establishment request is used to request establishment of a first PDU session. Optionally, the first core network device is implemented as the AMF (or referred to as "AMF entity", "AMF network element", or the like); or, in subsequent technical evolution, the core network device is implemented as other core network devices with device access management and mobility management functions.

In an embodiment of the present application, the first session establishment request includes the first RSC. Compared with the situation that the service attribute is directly carried in the session establishment request, the RSC (relay service code) corresponding to the service attribute is carried in the session establishment request, so that the service attribute leakage is possibly caused to affect the system security, the RSC corresponding to the service attribute is carried in the session establishment request, the privacy protection aiming at the service attribute is also ensured under the condition that the core network is ensured to clearly determine the service attribute, and the system security is improved. Optionally, the first session establishment request is the session establishment request message in step 701, so that the difference between step 810 and step 701 is that the first session establishment request in step 810 includes the first RSC.

Optionally, there is one-to-one correspondence between RSCs and service attributes, that is, one RSC corresponds to one service attribute. The service attribute refers to an attribute corresponding to a service requested by the device, and optionally, the service attribute includes at least one of the following: DNN information, slice information, session type information, PLMN information, qoS information, and the like. Optionally, the first RSC is determined by Remote equipment (Remote UE) and sent to the relay device, for example, when the Remote equipment needs to initiate a service and wants to find a relay device for relay communication, the Remote equipment needs to determine the first RSC according to the service to be established by the Remote equipment and send the determined first RSC to the relay device; alternatively, the first RSC is preset in the relay device, for example, corresponding to a certain relay device, assuming that it can only originate a specific type of traffic, and thus the RSC corresponding to the traffic it originates may also be fixed, so that the RSC can be preset in the relay device.

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

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

and step 820, the first core network device selects a second core network device according to the first RSC, and the second core network device is used for establishing 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, the device is implemented as other core network devices 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. Optionally, the first core network device may select the second core network device according to other information besides the first RSC, such as a rule for selecting the second core network device mentioned in the related art. For a specific selection process of the second core network device, please refer to the following embodiments, which are not described herein again. Optionally, the step 702 is that the first core network device selects the second core network device, so that the difference between the step 820 and the step 702 is that, in the step 820, the basis for the first core network device to select 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 content of the second session establishment request is not limited in the embodiment of the application, and optionally, the second session establishment request includes the first RSC; or, the second session establishment request includes session parameter information related to the PDU session requested to be established. The embodiment of the present application does not limit the content of the first session establishment request and the second session establishment request, and optionally, the content of the first session establishment request is the same as that of the second session establishment request, 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 content of 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 content of the received 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.

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 then according to the parameter information obtained by analysis, the PDU session between the relay device and the DN can be established. For an introduction description of the process of establishing the PDU session by the second core network device, please refer to the following embodiments, which are not described herein again.

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

After the second core network device establishes the PDU session, the first core network device may be notified that the PDU session establishment is completed, in this application embodiment, a manner of notifying the PDU session establishment completion by the second core network device is not limited, 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.

And after receiving the notification of the completion of the PDU session establishment, the first core network equipment sends a first session establishment response to the relay equipment, wherein the first session establishment response is used for indicating the completion of the PDU session establishment, so that the establishment of a data transmission channel between the relay equipment and the DN is completed. In the embodiment of the present application, a bearer manner of the first session establishment response is not limited, and optionally, the first core network device sends the first session establishment response to the relay device alone to notify the relay device that the PDU session establishment is completed; 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, so as to notify the relay device that the PDU session establishment is completed. Optionally, the first session establishment response includes the first RSC, so that the relay device specifies a service or RSC corresponding to the first session establishment response.

In summary, according to the technical scheme provided by the embodiment of the present application, the relay device sends the session establishment request to the core network device, the session establishment request carries the RSC corresponding to the service attribute, and since the RSC is represented as a service code, the RSC has a characteristic of being not easy to crack and leak.

In addition, according to the technical scheme provided by the embodiment of the application, another suitable core network device is selected to establish the PDU session through the core network device according to the RSC carried in the session establishment request, so as to establish a data transmission channel between the relay device and the DN. Because different core network devices with session management functions have different service attributes supported by the core network devices, the embodiment of the application fully considers 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 establishing the PDU session.

As can be seen from the description of the above embodiment, the first core network device may select the second core network device by the first RSC, and in the embodiment of the present application, two ways are provided for selecting the second core network device, where 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 a PDU session according to the first RSC, and then select the second core network device corresponding to the session parameter information.

First, a first embodiment will be described.

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

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

The first configuration information includes a correspondence between the RSC and the second core network device. The number of the corresponding relationships included in the first configuration information is not limited in the embodiment of the present application, and optionally, the corresponding relationships are one or more. In the embodiment of the application, the corresponding mode between the RSC and the second core network device is not limited, and optionally, the RSC and the second core network device are in one-to-one correspondence; or, the RSCs correspond to a second core network device; alternatively, one RSC corresponds to a plurality of second core network devices, which is not limited in this embodiment of the present application. 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; alternatively, the first configuration information is predefined in the communication protocol, which is not limited in this embodiment of the present application.

Based on this, as shown in fig. 10, the step 830 includes: step 832, 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 the first RSC in the session establishment request sent to the second core network device, so that the second core network device determines session parameter information used in the process of establishing the PDU session according to the first RSC. The embodiment of the present application does not limit the manner in which the second core network device determines the session parameter information of the PDU session, and several manners 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: step 842, the second core network device determines session parameter information corresponding to the first RSC according to third configuration information, where the third configuration information includes a correspondence between the RSC and the session parameter information; step 844, the second core network device establishes the PDU session according to the session parameter information.

The third configuration information includes a correspondence between the RSC and the session parameter information. The number of the corresponding relationships included in the third configuration information is not limited in the embodiment of the present application, and optionally, the corresponding relationships are one or more. In the embodiment of the present application, the corresponding manner between the RSC and the session parameter information is not limited, and optionally, the RSC and the session parameter information correspond to each other one to one; alternatively, the plurality of RSCs correspond to one session parameter information; alternatively, one RSC corresponds to a plurality of pieces of session parameter information, which is not limited in this embodiment of the present application. Optionally, the third configuration information is preconfigured in the second core network device, that is, the third configuration information is local configuration information of the second core network device; alternatively, the third configuration information is predefined in the communication protocol; or, the third configuration information is configured to the second core network device by another core network device, for example, the first core network device is configured to the second core network device, which is not limited in this embodiment of the present application.

The second core network device may determine session parameter information corresponding to the first RSC according to the third configuration information, and then establish a PDU session according to the session parameter information. The session parameter information is 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 pattern information, and session type information, and the specific content of the session parameter information is not limited in this embodiment.

Optionally, as shown in fig. 10, the step 840 includes: step 846, the second core network device determines session parameter information according to the first information domain in the first RSC; step 848, the second core network device establishes PDU session 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, in an 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 establish the PDU session using the session parameter information. In the embodiment of the present application, the bit number of the first information field is not limited, and optionally, the first information field is 1 bit or multiple bits, and in practical application, the bit number of the first information field may 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:

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 this embodiment of the 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 an introduction description that the third core network device selects the second core network device according to the first RSC, please refer to the above method embodiment, which is not described herein again. Optionally, the third core network device includes at least one of the following devices: NRF entity (or called "NRF"), PCF entity (or called "PCF").

Step 826, the third core network device sends device information to the first core network device, where the device information is used to indicate 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 corresponding to the first RSC and selected by the third core network device. The embodiment of the present application does not limit the specific content of the device information, and optionally, the device information includes at least one of the following: address information of the second core network device, and identification information of the second core network device, where the address information of the second core network device is used to indicate an address (such as a network address, a physical address, and the like) of the second core network device; the identification information of the second core network device is used to indicate an identification (such as a device unique identifier, a device ID, etc.) of the second core network device.

Optionally, as shown in fig. 10, the step 830 includes: in step 832, 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 to establish a PDU session, and the second session establishment request includes the first RSC. For the introduction of step 832, please refer to the above embodiments, which are not repeated herein.

Optionally, as shown in fig. 10, the step 840 includes: step 842, the second core network device determines, according to the third configuration information, session parameter information corresponding to the first RSC, where the third configuration information includes a correspondence between the RSC and the session parameter information; step 844, the second core network device establishes the PDU session according to the session parameter information. Optionally, as shown in fig. 10, the step 840 includes: step 846, the second core network device determines session parameter information according to the first information domain in the first RSC; step 848, the second core network device establishes PDU session according to the session parameter information. For descriptions of steps 842, 844, 846, 848, please refer to the above embodiments, which are not repeated herein.

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

Next, a description will be given of a second embodiment.

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 this embodiment, the first core network device may send the first RSC to the third core network device, and the third core network device determines, according to the first RSC, session parameter information required to establish the PDU session. Optionally, the third core network device includes at least one of the following devices: NRF entity (or called "NRF"), PCF entity (or called "PCF").

In step 823, the third core network device sends the session parameter information corresponding to the first RSC to the first core network device.

After the third core network device receives the first RSC, the session parameter information may be determined according to the second configuration information. For the introduction description of determining the session parameter information and the second configuration information by the third core network device according to the first RSC, please refer to the following embodiments in which the first core network device determines the session parameter information, which is not described herein again. Optionally, the session parameter information comprises at least one of: slice information, DNN information, SSC pattern information, and session type information, and the specific content of the session parameter information is not limited in this embodiment.

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

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

The third configuration information includes a corresponding relationship between the RSC and the session parameter information, and 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; alternatively, the third configuration information is predefined in the communication protocol, which is not limited in this embodiment of the present application. For other descriptions of the third configuration information, please refer to the above method embodiment, which is not repeated herein.

Based on this, as shown in fig. 11, the step 830 includes: in step 831, 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.

Since 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 directly establishes the PDU session according to the session parameter information.

Based on this, as shown in fig. 11, the step 840 includes: in step 841, the second core network device establishes the 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, according to the second configuration information, session parameter information corresponding to the first RSC, where the second configuration information includes a correspondence between the RSC and the session parameter information.

The second configuration information includes a correspondence between the RSC and the session parameter information. The number of the corresponding relationships included in the second configuration information is not limited in the embodiment of the present application, and optionally, the corresponding relationships are one or more. In the embodiment of the present application, the corresponding manner between the RSC and the session parameter information is not limited, and optionally, the RSC and the session parameter information correspond to each other one to one; alternatively, the plurality of RSCs correspond to one session parameter information; alternatively, one RSC corresponds to a plurality of pieces of session parameter information, which is not limited in this embodiment of the present application. Optionally, the second configuration information is preconfigured in the first core network device, that is, the first configuration information is local configuration information of the first core network device; alternatively, the first configuration information is predefined in the communication protocol, which is not limited in this embodiment of the present application. The first core network device may determine, according to the second configuration information, session parameter information corresponding to the first RSC, so as to further determine, according to the session parameter information, a second core network device. Optionally, the session parameter information comprises at least one of: slice information, DNN information, SSC pattern information, and session type information, and the specific content of the session parameter information is not limited in this embodiment.

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

For an introduction description of step 829, please refer to step 825 above, which is not described herein again.

Based on this, as shown in fig. 11, the step 830 includes: in step 831, 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: in step 841, the second core network device establishes the PDU session according to the session parameter information. For descriptions of step 831 and step 841, please refer to the above embodiments, which are not repeated herein.

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

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

For the introduction description of the first information field, please refer to the introduction descriptions of step 846 and step 848, which are not described herein again. The first core network device may determine, according to the first information field in the first RSC, session parameter information for establishing a PDU session, 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 pattern information, session type information.

And 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 corresponding relationship between the session parameter information and the second core network device.

For an introduction description of step 82B, please refer to step 825 mentioned above, which is not described herein.

Based on this, as shown in fig. 11, the step 830 includes: in step 831, 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: in step 841, the second core network device establishes PDU session according to the session parameter information. For descriptions of step 831 and step 841, please refer to the above embodiments, which are not repeated herein.

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

It should be further noted that, in this embodiment, 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 the 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 used to limit configuration information of one core network device.

To sum up, according to the technical solution provided in the embodiment of the present application, the core network device corresponding to the RSC carried in the session establishment request is selected according to the correspondence between the RSC and the core network device, so that 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 subjects and a plurality of selection modes, and the selection subjects and the selection modes can be combined in a plurality of forms, so that the flexibility of core network equipment selection is improved.

It should be noted that, in the above method embodiment, description is mainly given to the session establishment method provided in this application 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 can be independently realized to be a relay device side session establishing method; the steps executed by the first core network device may be implemented separately as a session establishment method at the first core network device side; the steps executed by the second core network device may be implemented separately as a session establishment method on the side of the second core network device.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

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

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

In one example, the first RSC is configured to select a second core network device, and the second core network device is configured 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, where the first session establishment response is used to indicate that the PDU session establishment is completed.

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

To sum up, according to the technical scheme provided by the embodiment of the present application, the relay device sends the session establishment request to the core network device, where the session establishment request carries the RSC corresponding to the service attribute, and since the RSC is represented as a service code, the RSC has a characteristic of being not easy to crack or leak.

Referring to fig. 13, a block diagram of a session setup 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 by executing corresponding software by hardware. The apparatus may be the first core network device described above, or may be disposed 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 apparatus, where the first session establishment request is used to request establishment of a PDU session between the relay apparatus 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, 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, as shown in fig. 15, the device selection module 1420 is configured to: and selecting second core network equipment corresponding to the first RSC according to first configuration information, wherein the first configuration information comprises a corresponding relation between the RSC and the second core network equipment.

In one example, as shown in fig. 15, the device selection module 1420 is configured to: sending the first RSC to a third core network device; and receiving equipment information from the third core network equipment, wherein the equipment information is used for indicating second core network equipment corresponding to the first RSC.

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

In one example, as shown in fig. 15, the device selection module 1420 is configured to: 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, wherein the session parameter information is used for establishing the PDU session; and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.

In one example, as shown in fig. 15, the device selection module 1420 is configured to: determining session parameter information corresponding to the first RSC according to second configuration information, wherein the session parameter information is used for establishing the PDU session, and the second configuration information comprises a corresponding relation between the RSC and the session parameter information; and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.

In one example, as shown in fig. 15, the device selection module 1420 is configured to: determining session parameter information according to a first information domain in the first RSC, wherein the session parameter information is used for establishing the PDU session; and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.

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

In one example, the third core network device includes at least one of: NRF entity, 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 includes: a first response sending module 1440 configured to send a first session establishment response to the relay device, where the first session establishment response is used to indicate that the PDU session establishment is completed.

Referring to fig. 16, a block diagram of a session setup apparatus according to an embodiment of the present application is shown. The device has the function of realizing the example of the second core network equipment side method, and the function can be realized by hardware or by executing corresponding software by hardware. The apparatus may be the second core network device described above, and may also be disposed in the second core network device. As shown in fig. 16, the apparatus 1600 may comprise: 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 establishing module 1620, configured to establish a PDU session between the relay device and the DN according to the second session establishing request.

In one example, the first RSC is included in the second session establishment request; the session establishing module 1620 configured to: determining session parameter information corresponding to the first RSC according to third configuration information, wherein the third configuration information comprises a corresponding relation between the RSC and the session parameter information; and establishing the PDU session according to the session parameter information.

In one example, the first RSC is included in the second session establishment request; the session establishing module 1620 configured to: determining session parameter information according to a first information domain in the first RSC; and establishing 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; the session establishing module 1620, configured to: and establishing the PDU session according to the session parameter information.

It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of each functional module is illustrated, and in practical applications, the above functions may be distributed by different functional modules according to actual needs, that is, the content structure of the device may be divided into different functional modules to implement all or part of the functions described above.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Referring to fig. 17, a schematic structural diagram of a relay device 170 according to an embodiment of the present application is shown, for example, the relay device may be configured to execute the above-described relay device side session establishment method. 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, the transceiver 172 is a communication chip.

In one example, the relay device 170 further includes: a memory and a bus. The memory is connected with the processor through a bus. The memory may be used for storing a computer program for execution by the processor for carrying out the steps performed by the relay device in the above-described method embodiments.

Further, the memory may be implemented by any type or combination of volatile or non-volatile storage 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 technologies, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc), or other optical storage, magnetic 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 an example, the transceiver 172 is further configured to receive a first session setup response from the first core network device, where the first session setup response is used to indicate that the PDU session setup is completed.

Please refer to fig. 18, which illustrates a schematic structural diagram of a core network device 180 according to an embodiment of the present application, for example, the core network device may be configured to execute the first core network device side session establishment method; or, the method is used for executing the session establishment method on the first core network device side. 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. Optionally, the transceiver 182 is a communication chip.

In one example, the core network device 180 further includes: a memory and a bus. The memory is connected to the processor by a bus. The memory may be configured to store a computer program, and the processor is configured to execute the computer program to implement the steps performed by the first core network device or the second core network device in the above-described method embodiments.

Further, the memory may be implemented by any type or combination of volatile or non-volatile storage 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 storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, magnetic tape cartridge, magnetic tape, magnetic disk storage or other magnetic storage devices. Wherein:

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

the transceiver 182 is configured to receive a first session establishment request from a relay device, where the first session establishment request is used to request 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 processor 181 is configured to select a second core network device according to the first RSC, where the second core network device is configured to establish the PDU session.

In an example, the processor 181 is configured to select, according to first configuration information, a second core network device corresponding to the first RSC, 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 transmit the first RSC to a third core network device; the transceiver 182 is configured to 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 transceiver 182 is configured to transmit 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; the processor 181 is configured to 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 the session parameter information and the second core network device.

In one example, the processor 181 is configured to: determining session parameter information corresponding to the first RSC according to second configuration information, wherein the session parameter information is used for establishing the PDU session, and the second configuration information comprises a corresponding relation between the RSC and the session parameter information; and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.

In one example, the processor 181 is configured to: determining session parameter information according to a first information domain in the first RSC, wherein the session parameter information is used for establishing the PDU session; and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.

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

In an example, the transceiver 182 is configured to send a second session establishment request to the second core network device, where the second session establishment request is used to request 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 execute the second core network device side session establishment method:

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

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

In one example, the first RSC is included in the second session establishment request; the processor 181 is configured to: determining session parameter information corresponding to the first RSC according to third configuration information, wherein the third configuration information comprises a corresponding relation between the RSC and the session parameter information; and establishing the PDU session according to the session parameter information.

In one example, the first RSC is included in the second session establishment request; the processor 181 is configured to: determining session parameter information according to a first information domain in the first RSC; and establishing 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; the processor 181 is configured to: and establishing the PDU session according to the session parameter information.

In a further aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used for being executed by a processor of a core network device, so as to implement the first core network device side session establishment method.

In a further aspect, an embodiment of the present application provides a chip, where the chip includes a programmable logic circuit and/or program instructions, and when the chip runs on a relay device, the chip is configured to implement the relay device side session establishment method as described above.

In a further aspect, an embodiment of the present application provides a chip, where the chip includes a programmable logic circuit and/or a program instruction, and when the chip runs on a core network device, the chip is configured to implement the above first core network device side session establishment method.

In another aspect, an embodiment of the present application provides a computer program product, which when the computer program product runs on a core network device, causes a computer to execute the first core network device side session establishment method.

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

Those skilled in the art will recognize 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, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above description is only exemplary of the application and should not be taken as limiting the application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the application should be included in the protection scope of the application.

Claims

A session establishment method is applied to a relay device, and the method comprises the following steps:

and sending a first session establishment request to first core network equipment, wherein the first session establishment request is used for requesting to establish a Protocol Data Unit (PDU) session between the relay equipment and a Data Network (DN), and the first session establishment request comprises a first Relay Service Code (RSC).
The method of claim 1, wherein the first RSC is configured to select a second core network device, and wherein the second core network device is configured to establish the PDU session.
The method according to claim 1 or 2, characterized in that the method further comprises:

and receiving a first session establishment response from the first core network equipment, wherein the first session establishment response is used for indicating that the PDU session establishment is completed.
The method of claim 3, wherein the first RSC is included in the first session establishment response.
A session establishment method is applied to a first core network device, and the method comprises the following steps:

receiving a first session establishment request from a relay device, wherein the first session establishment request is used for requesting to establish a Protocol Data Unit (PDU) session between the relay device and a Data Network (DN), and the first session establishment request comprises a first relay business service code (RSC).
The method of claim 5, wherein after receiving the first session request from the relay device, further comprising:

and selecting second core network equipment according to the first RSC, wherein the second core network equipment is used for establishing the PDU session.
The method of claim 6, wherein the selecting the second core network device according to the first RSC comprises:

and selecting second core network equipment corresponding to the first RSC according to first configuration information, wherein the first configuration information comprises a corresponding relation between the RSC and the second core network equipment.
The method of claim 6, wherein the selecting the second core network device according to the first RSC comprises:

sending the first RSC to a third core network device;

and receiving equipment information from the third core network equipment, wherein the equipment information is used for indicating second core network equipment corresponding to the first RSC.
The method of claim 8, wherein 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.
The method of claim 6, wherein the selecting the 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, wherein the session parameter information is used for establishing the PDU session;

and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.
The method of claim 6, wherein the selecting the second core network device according to the first RSC comprises:

determining session parameter information corresponding to the first RSC according to second configuration information, wherein the session parameter information is used for establishing the PDU session, and the second configuration information comprises a corresponding relation between the RSC and the session parameter information;

and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.
The method of claim 6, wherein the selecting the second core network device according to the first RSC comprises:

determining session parameter information according to a first information domain in the first RSC, wherein the session parameter information is used for establishing the PDU session;

and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.
The method according to any of claims 10 to 12, wherein the session parameter information comprises at least one of: slice information, data network name DNN information, session and service continuity SSC pattern information, session type information.
The method according to any of claims 8 to 10, wherein the third core network device comprises at least one of: a storage function NRF entity and a strategy control function PCF entity of the network function entity.
The method according to any one of claims 7 to 9, further comprising:

and sending a second session establishment request to the second core network device, wherein the second session establishment request is used for requesting to establish the PDU session, and the second session establishment request comprises the first RSC.
The method according to any one of claims 10 to 13, further comprising:

and sending a second session establishment request to the second core network device, wherein the second session establishment request is used for requesting to establish the PDU session and comprises the session parameter information.
The method of any one of claims 5 to 16, further comprising:

and sending a first session establishment response to the relay equipment, wherein the first session establishment response is used for indicating that the PDU session establishment is completed.
The method of claim 17, wherein the first RSC is included in the first session establishment response.
A session establishment method, applied to a second core network device, the method comprising:

receiving a second session establishment request from first core network equipment, wherein the second core network equipment is selected by the first core network equipment based on a first Relay Service Code (RSC);

and establishing a Protocol Data Unit (PDU) session between the relay equipment and the data network DN according to the second session establishment request.
The method of claim 19, wherein the first RSC is included in the second session establishment request;

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

determining session parameter information corresponding to the first RSC according to third configuration information, wherein the third configuration information comprises a corresponding relation between the RSC and the session parameter information;

and establishing the PDU session according to the session parameter information.
The method of claim 19, wherein the first RSC is included in the second session establishment request;

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

determining session parameter information according to a first information domain in the first RSC;

and establishing the PDU session according to the session parameter information.
The method of claim 19, wherein the second session setup request includes session parameter information corresponding to the first RSC;

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

and establishing the PDU session according to the session parameter information.
The method according to any of claims 20 to 22, wherein said session parameter information comprises at least one of: slice information, data network name DNN information, session and service continuity SSC pattern information, session type information.
A session establishment apparatus provided in a relay device, the apparatus comprising:

the first request sending module is used for sending a first session establishment request to first core network equipment, wherein the first session establishment request is used for requesting to establish a Protocol Data Unit (PDU) session between the relay equipment and a Data Network (DN), and the first session establishment request comprises a first Relay Service Code (RSC).
The apparatus of claim 24, wherein the first RSC is configured to select a second core network device, and wherein the second core network device is configured to establish the PDU session.
The apparatus of claim 24 or 25, further comprising:

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

the device comprises a first request receiving module and a second request receiving module, wherein the first request receiving module is used for receiving a first session establishment request from the relay equipment, the first session establishment request is used for requesting to establish a Protocol Data Unit (PDU) session between the relay equipment and a Data Network (DN), and the first session establishment request comprises a first relay business service code (RSC).
The apparatus of claim 28, further comprising:

and the device selection module is used for selecting second core network devices according to the first RSC, and the second core network devices are used for establishing the PDU session.
The apparatus of claim 29, wherein the device selection module is configured to:

and selecting second core network equipment corresponding to the first RSC according to first configuration information, wherein the first configuration information comprises a corresponding relation between the RSC and the second core network equipment.
The apparatus of claim 29, wherein the device selection module is configured to:

sending the first RSC to a third core network device;

and receiving device information from the third core network device, wherein the device information is used for indicating the second core network device corresponding to the first RSC.
The apparatus of claim 31, wherein 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.
The apparatus of claim 29, wherein the device selection module is configured to:

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, wherein the session parameter information is used for establishing the PDU session;

and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.
The apparatus of claim 29, wherein the device selection module is configured to:

determining session parameter information corresponding to the first RSC according to second configuration information, wherein the session parameter information is used for establishing the PDU session, and the second configuration information comprises a corresponding relation between the RSC and the session parameter information;

and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.
The apparatus of claim 29, wherein the device selection module is configured to:

determining session parameter information according to a first information field in the first RSC, wherein the session parameter information is used for establishing the PDU session;

and selecting second core network equipment corresponding to the session parameter information according to third configuration information, wherein the third configuration information comprises a corresponding relation between the session parameter information and the second core network equipment.
The apparatus according to any of claims 33 to 35, wherein the session parameter information comprises at least one of: slice information, data network name DNN information, session and service continuity SSC pattern information, session type information.
The apparatus according to any of claims 31 to 33, wherein the third core network device comprises at least one of: a storage function NRF entity and a strategy control function PCF entity of the network function entity.
The apparatus of any one of claims 30 to 32, further comprising:

a second request sending module, configured to send a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of the PDU session, and the second session establishment request includes the first RSC.
The apparatus as claimed in any one of claims 33 to 36, further comprising:

a second request sending module, configured to send a second session establishment request to the second core network device, where the second session establishment request is used to request establishment of the PDU session, and the second session establishment request includes the session parameter information.
The apparatus as claimed in any one of claims 29 to 39, further comprising:

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

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 relay service code RSC;

and the session establishing module is used for establishing a Protocol Data Unit (PDU) session between the relay equipment and the data network DN according to the second session establishing request.
The apparatus of claim 42, wherein the first RSC is included in the second session establishment request; the session establishing module is configured to:

determining session parameter information corresponding to the first RSC according to third configuration information, wherein the third configuration information comprises a corresponding relation between the RSC and the session parameter information;

and establishing the PDU session according to the session parameter information.
The apparatus of claim 42, wherein the first RSC is included in the second session establishment request; the session establishing module is configured to:

determining session parameter information according to a first information domain in the first RSC;

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

and establishing the PDU session according to the session parameter information.
The apparatus according to any of claims 43 to 45, wherein the session parameter information comprises at least one of: slice information, data network name DNN information, session and service continuity SSC pattern information, session type information.
A relay device, characterized in that the relay device comprises: a processor, and a transceiver coupled to the processor; wherein:

the transceiver is configured to send a first session establishment request to a first core network device, where the first session establishment request is used to request 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).
A core network device, characterized in that the core network device comprises: a processor, and a transceiver coupled to the processor; wherein:

the transceiver is configured to receive a first session establishment request from a relay device, where the first session establishment request is used to request 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).
A core network device, characterized in that the core network device comprises: a processor, and a transceiver coupled to the processor; wherein:

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 relay service code RSC;

and the processor is used for establishing a Protocol Data Unit (PDU) session between the relay equipment and the data network DN according to the second session establishment request.
A computer-readable storage medium, in which a computer program is stored which is for execution by a processor of a relay device to implement a session establishment method according to any one of claims 1 to 4.
A computer-readable storage medium, in which a computer program is stored, the computer program being adapted to be executed by a processor of a core network device to implement the session establishment method according to any one of claims 5 to 18.
A computer-readable storage medium, in which a computer program is stored, the computer program being adapted to be executed by a processor of a core network device to implement the session establishment method according to any one of claims 14 to 26.